[Contents] [Prev] [Next] [Index] [Report an Error]


Up Event

LSP Event

Up

Sample Output

user@R1> show mpls lsp extensive
[...Output truncated...]
   48 Jan  4 18:10:44 RSVP error, subcode 4: protocol shutdown
   47 Jan  4 18:10:44 Down
   46 Jan  4 18:06:15 Up
   45 Jan  4 18:06:15 Down
[...Output truncated...]

What It Means

This LSP event indicates the state of the LSP on January 4 at 1800 hours, 6 minutes, and 15 seconds. The LSP was able to forward traffic, but was not necessarily the active path, it was simply up. For example, an LSP can be up but not active when it is a secondary LSP configured with the standby statement at the [edit protocols mpls] hierarchy level. Similarly, a primary LSP may have failed while waiting for two retry intervals before the LSP reverts back from the secondary LSP to the primary LSP.


[Contents] [Prev] [Next] [Index] [Report an Error]