LSP Event
Manual Autobw adjustment succeeded
Sample Output
user@R1> show mpls lsp extensive
[...Output truncated...]
user@R1> request mpls lsp adjust-autobandwidth name R1-to-R6
user@R1> show mpls lsp extensive
Ingress LSP: 3 sessions
10.0.0.6
From: 10.0.0.1, State: Up, ActiveRoute: 4, LSPname: R1-to-R6
ActivePath: (primary)
LoadBalance: Random
Metric: 1
Autobandwidth
MinBW: 5Mbps MaxBW: 80Mbps
AdjustTimer: 300 secs AdjustThreshold: 10%
Max AvgBW util: 736bps, Bandwidth Adjustment in 65 second(s).
Encoding type: Packet, Switching type: Packet, GPID: IPv4
*Primary State: Up
Bandwidth: 5Mbps
Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 20)
10.1.13.2 S 10.1.36.2 S
Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt):
10.1.13.2 10.1.36.2
11 Feb 17 21:16:22 Record Route: 10.1.13.2 10.1.36.2
10 Feb 17 21:16:22 Up
9 Feb 17 21:16:22 Manual Autobw adjustment succeeded
8 Feb 17 21:16:22 Originate make-before-break call
7 Feb 17 21:16:22 CSPF: computation result accepted
6 Feb 17 21:14:51 Selected as active path
5 Feb 17 21:14:51 Record Route: 10.1.13.2 10.1.36.2
4 Feb 17 21:14:51 Up
3 Feb 17 21:14:51 Originate Call
2 Feb 17 21:14:51 CSPF: computation result accepted
1 Feb 17 21:14:22 CSPF failed: no route toward 10.0.0.6[4 times]
[...Output truncated...]
Meaning
This LSP event indicates that the autobandwidth adjustment is triggered manually for the LSP using the request mpls lsp adjust-autobandwidth command. A new path for the LSP with the adjust bandwidth is successfully computed and signaled, resulting in the LSP (and traffic) switching over to the new adjusted path
Cause
When the CLI command to trigger the manual adjustment is issued, the autobandwidth adjustment validation runs. The current maximum average bandwidth usage is compared to the allocated bandwidth for the LSP. If the LSP needs more bandwidth, an attempt is made to set up a new path where bandwidth is equal to the current maximum average usage. If the attempt is successful, the LSP's traffic is routed through the new path and the old path is removed in a make-before-break fashion. If the attempt fails, the LSP continues to use its current path.
Action
No action needed. Manual autobandwidth adjustment succeeded.
