Error scenario Cause/Corrective Action
Ingress Problem Error in the ingress side, mainly because of
wrong configuration.
CSPF configuration error Mismatch in the CSPF configuration, like
CSPF disable globally, but enabled in lsp
level etc. Cross check the configuration and
correct it
Egress configuration error Wrong Configuration in Egress side. Cross
check the configuration and correct it
PATH configuration error Wrong Path Configured, ensure mpls and
rsvp is enabled in the desired path. Cross
check the configuration and correct it.
First hop unreachable First hop not reachable. Configure the
required ip address/mask
Hop limit conflict Configured invalid/mismatched Hop limit for
the lsp. Cross check the configuration and
correct it
Setup priority conflict Configured invalid/mismatched setup priority
for
the lsp. Cross check the configuration and
correct it
If this does not isolate the problem, you can go to debug mode for further analysis.
More detailed analysis
For more detailed analysis you can issue the debug rsvp commands. If there are more
sessions, there will be more prints to the console and the user needs to filter this information
by lsp-id of the particular session to debug. The lsp-id will be printed in the debug output and
can be cross checked with the show command show mpls traffic-eng-lsp session
<session name>.
For RSVP start with debug rsvp events
- this will output all RSVP events. Make sure the
protocol messages are sending and receiving.
Make sure the state machine is functioning by issuing debug rsvp fsm. For further filtering
depending on the router, the user can give the options like ingress, egress, and transient. Make
sure the Finite state machine is functioning properly.
For RSVP sessions with CSPF enabled, check the CSPF flow with the command debug rsvp
cspf. This debug command combined with debug cspf lsp <lsp-name> will give more
detailed information and make sure there are no errors in the CSPF flow.
For RSVP sessions with QOS parameters, debug rsvp nsm will give more detailed
information about the flow and the interfaces with QOS.
Troubleshooting an MPLS problem
120 Troubleshooting August 2013
Comments? infodev@avaya.com
To Next Page
Loading...
