6. Check to make sure the forwarding entry and route data base are in sync
7.
Check RSVP LSP statistics for transmitted packets show mpls stats-lsp
8. Check MPLS forwarding statistics for transmitted packets show mpls stats-ftn
Isolating the cause and corrective action
• Is CSPF at fault? For RSVP session with CSPF enabled, ensure that the underlying
protocol used is OSPF. Issue the command ip ospf-te database for the TE-database
information. You can isolate the problem by disabling CSPF from the LSP and check for
the session establishment.
• Is QOS at fault? Check to see if there any policies configured and if that is giving the
problem. Isolate the problem by removing the policies. Also isolate the problem by
removing the QoS parameters from the LSP.
• Is Forwarding at fault? Is Configuration correct in the peer routers, and in the entire Lsp
path? Execute the command traffic-eng-lsp-restart in lsp mode to restart the
particular lsp. Check to see if the session comes up after the traffic is flowing correctly.
Execute the command clear rsvp session all to restart all the rsvp sessions.
Check to see if the session comes up and the traffic is flowing correctly. Delete the
particular session and then create with the same configuration. Check for the session
establishment. Apart from the protocol the problem may be related to another system.
Shut down and restart the incoming and outgoing interfaces. If there is a problem, take
appropriate actions to fix it, then check to see if LSP is operating as expected. If problem
still exist, contact Avaya support for help.
Troubleshooting L2 circuit
This section details the steps and commands used to troubleshoot L2 circuits.
Troubleshooting an MPLS problem
122 Troubleshooting August 2013
Comments? infodev@avaya.com
To Next Page
Loading...
