Update LSP Encoding Type Event
LSP Event
Sample Output
user@host>show mpls lsp extensiveIngress LSP: 1 sessions10.255.255.40From: 10.255.255.35, State: Up, ActiveRoute: 0, LSPname: gmpls-lsp1BidirectionalActivePath: path-lsp1 (primary)LoadBalance: RandomSignal type: STM-1Encoding type: SDH/SONET, Switching type: Fiber, GPID: PPP*Primary path-lsp1 State: UpBandwidth: 155.52MbpsComputed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 2)10.35.100.1 S 10.35.150.1 S 10.35.200.1 SReceived RRO:10.35.100.1 10.35.150.1 10.35.200.17 Nov 7 15:47:11 Selected as active path6 Nov 7 15:47:11 Record Route: 10.35.100.1 10.35.150.1 10.35.200.15 Nov 7 15:47:11 Up4 Nov 7 15:47:11Update LSP Encoding Type3 Nov 7 15:47:11 Originate Call2 Nov 7 15:47:11 CSPF: computation result accepted1 Nov 7 15:46:41 CSPF failed: no route toward 10.255.255.40Created: Thu Nov 7 15:46:38 2002Total 1 displayed, Up 1, Down 0What It Means
This LSP event indicates that the encoding type was updated based on the traffic engineering link selected as the first hop.
Cause
This LSP event occurs when the encoding type is not configured on a non-packet LSP. In this case, the encoding type is derived from the traffic engineering link that was selected as the first hop.
Action