Retry Limit Exceeded Event
LSP Event
Retry limit exceeded
Sample Output 1
user@R1> show mpls lsp extensive
[...Output truncated...]
10.0.0.6
From: 10.0.0.1, State: Dn, ActiveRoute: 0, LSPname: R1-to-R6
ActivePath: (none)
LoadBalance: Random
Encoding type: Packet, Switching type: Packet, GPID: IPv4
Primary State: Dn
RetryCount: 13
RetryLimit: 1
12 Jan 14 15:39:30 Clear Call
11 Jan 14 15:39:30 Retry limit exceeded
10 Jan 14 15:39:10 10.1.12.1: MPLS label allocation failure[11 times]
[...Output truncated...]
Sample Output 2
user@R1> show mpls lsp extensive [...Output truncated...] 10.0.0.6 From: 10.0.0.1, State: Dn, ActiveRoute: 0, LSPname: R1-to-R6 ActivePath: (none) LoadBalance: Random Encoding type: Packet, Switching type: Packet, GPID: IPv4 Primary State: Dn 14 Jan 14 15:44:07 10.1.12.1: MPLS label allocation failure[3 times] 13 Jan 14 15:43:58 Originate Call 12 Jan 14 15:39:30 Clear Call 11 Jan 14 15:39:30 Retry limit exceeded 10 Jan 14 15:39:10 10.1.12.1: MPLS label allocation failure[11 times] [...Output truncated...]
Meaning
This LSP event indicates that the number of CSPF path computations for a particular path exceeded a configured retry limit. After this point, the path is not recomputed or signaled, unless the user intervenes.
Cause
The number of CSPF path computations for an LSP path exceeded the configured non-zero retry limit. Sample Output 1 shows that a configured retry limit of 1 was exceeded by the retry count of 13.
Action
Enter the clear mpls lsp command to disconnect and restart the LSP. Sample Output 2 shows that events 13 and 14 were generated after the clear mpls lsp command was issued. This operation disconnects existing RSVP sessions on the ingress router, releases the routes and states associated with the LSPs, and starts a new LSP. Issuing this command might impact traffic travelling along the LSP, because of a time lag that can occur between the old path being torn down and the new path being set up.