Procedure 4-8 To Verify End-To-End Connectivity Of An Mpls Lsp Using Lsp Ping - Alcatel 5620 Troubleshooting Manual

Displayed message
Request Terminated
Far End: Originator-ID Invalid
Far End: Responder-ID Invalid
Far End:Resp-SDP Non-Existent
Far End:Resp-SDP Invalid
Far End:Resp-SDP Down
Success
(2 of 2)
Procedure 4-8 To verify end-to-end connectivity of an MPLS LSP
using LSP Ping
1
2
3
Alcatel 5620 Service Aware Manager, Release 2.1 R2
May 2005 95-5887-01-00-B
a If the Tunnel Ping passes, the network objects below the tunnel are operating
with no performance issues.
You have completed the troubleshooting workflow for services.
•
If the problem no longer exists on the service, you have completed the
troubleshooting workflow for services. Disable the OAM diagnostics to
conserve system resources. See the 5620 SAM User Guide.
•
If the service problem persists, another type of problem may exist on your
service. Go to section 4.2 and repeat the troubleshooting workflow. If the
troubleshooting workflow does not identify the problem with your service,
contact your Alcatel technical support representative. See section 1.4 for
more information.
b If the Tunnel Ping fails, go to step 9.b.iii in section 4.2 to verify the end-to-end
connectivity of services using MPLS LSP paths, if required.
Enable the OAM diagnostics for the service. See the 5620 SAM User Guide.
Open the LSP Ping configuration form and clear the results from the previous
diagnostic session, if any.
Note — You must use the LSP Ping diagnostic to test the service in both
directions for the connection.
Configure the parameters for the diagnostic session and run the diagnostic. Figure
4-15 shows the diagnostic configuration associated with an LSP Ping from site ID
10.1.200.51/32 to site ID 10.1.200.52/32 using the network in Figure 4-1.
Description
The operator terminated the request before a reply was received,
or before the timeout of the request occurred.
The request was received by the far-end, but the far-end
indicates that the originating SDP ID is invalid.
The request was received by the far-end, but the responder ID is
not the same destination SDP ID that was specified.
The reply was received, but the return SDP ID used to respond
to the request does not exist.
The reply was received, but the return SDP ID used to respond
to the request is invalid.
The reply was received, but the return SDP ID indicates that the
administrative or operational state of the SDP is Down.
The tunnel is in service and working as expected. A reply was
received without any errors.
4 — Troubleshooting services
4-19