To verify end-to-end connectivity of an MPLS LSP using LSP Ping

Steps
 
1 

Choose Tools→Service Test Manager (STM) from the NFM-P main menu. The Manage Tests form appears.

2 

Click Create.

3 

Choose MPLS→Create LSP Ping from the Create contextual menu. The LSP Ping (Create) form appears.

Note: You must use the LSP Ping diagnostic to test the service in both directions for the connection.

4 

Configure the required parameters for the diagnostic session and run the diagnostic. Target an LSP or an LSP path. Choose the MPLS site for the test, then configure the LSP you want to ping that is associated with the MPLS site, in this case, an LSP Ping from site ID 10.1.200.51/32 to site ID 10.1.200.52/32 using the network in Figure 6-1, Sample network.

Click on the Results tab to view the list of trace responses. Double-click on a row in the list to view its details. Double-click on the entry in the LSP Ping results form to view the diagnostic details.

5 

Review the diagnostic results and assess whether the configuration meets the network requirements.

The table below lists the displayed messages.

Table 6-5: LSP Ping OAM diagnostic results

Displayed message

Description

notApplicable (0)

The OAM diagnostic message does not apply to the OAM diagnostic performed.

fecEgress (1)

The replying router is an egress for the FEC.

The far-end egress point exists and is operating correctly. No action required.

fecNoMap (2)

The replying router has no mapping for the FEC.

notDownstream (3)

The replying router is not a downstream router.

downstream (4)

The replying router is a downstream router, and the mapping for this FEC on the router interface is the specified label.

downstreamNotLabel (5)

The replying router is a downstream router, and the mapping for this FEC on the router interface is not the specified label.

downstreamNotMac (6)

The replying router is a downstream router, but it does not have the specified MAC address.

downstreamNotMacFlood (7)

The replying router is a downstream router, but it does not have the specified MAC address and cannot flood the request to other routers.

malformedEchoRequest (8)

The received echo request is malformed.

tlvNotUnderstood (9)

One or more TLVs were not understood.

  1. If the LSP Ping passes, you have completed the workflow for troubleshooting services. Contact your technical support representative if the problem persists; see Chapter 1, NSP troubleshooting overview.

  2. If the LSP Ping fails, verify the administrative and operational status of the underlying L2 equipment.

6 

If the service problem persists, another type of service problem may be present. Perform the steps of Workflow to troubleshoot a service or connectivity problem.

7 

If the troubleshooting workflow does not identify the problem with your service, contact your technical support representative; see Chapter 1, NSP troubleshooting overview.

End of steps