Manual Autobandwidth Adjustment
Purpose
Manual autobandwidth adjustment is used on the active LSP path when you wish to trigger an autobandwidth adjustment before the next specified automatic bandwidth adjustment.
 |
NOTE: Request for manual autobandwidth adjustment is a feature introduced in JUNOS software Release 7.0. |
To manually trigger a bandwidth allocation adjustment, use the request mpls lsp adjust-autobandwidth command. You can trigger the command for all affected LSPs on the router, or you can specify a particular LSP. Once you execute the request mpls lsp adjust-autobandwidth command, the automatic bandwidth adjustment validation process is triggered. If all the criteria for adjustment are met, the LSP's active path bandwidth is adjusted to the set bandwidth value determined during the validation process.
For more information on configuring autobandwidth, see the JUNOS MPLS Applications Configuration Guide.
Autobandwidth success and failure is logged in the output of the show mpls lsp extensive command. The following manual autobandwidth adjustment events are included in this section:
Manual Autobandwidth Adjustment Failed Event
LSP Event
Manual Autobw adjustment failed
Sample Output
user@R1> show mpls lsp extensive
Ingress LSP: 3 sessions
10.0.0.3
From: 10.0.0.1, State: Up, ActiveRoute: 5, LSPname: R1-to-R3
ActivePath: (primary)
LoadBalance: Random
Metric: 1
Autobandwidth
MinBW: 155Mbps MaxBW: 155Mbps
AdjustTimer: 300 secs AdjustThreshold: 10%
Max AvgBW util: 392bps, Bandwidth Adjustment in 101 second(s).
Encoding type: Packet, Switching type: Packet, GPID: IPv4
*Primary State: Up
Bandwidth: 140Mbps
Computed ERO (S [L] denotes strict [loose] hops): (CSPF metric: 10)
10.1.13.2 S
Received RRO (ProtectionFlag 1=Available 2=InUse 4=B/W 8=Node 10=SoftPreempt):
10.1.13.2
13 Feb 17 21:23:51Manual Autobw adjustment failed
12 Feb 17 21:23:51 CSPF failed: no route toward 10.0.0.3
11 Feb 17 21:16:06 Record Route: 10.1.13.2
10 Feb 17 21:16:06 Up
[...Output truncated...]
What It Means
This LSP event indicates that autobandwidth adjustment was triggered manually for the LSP using the request mpls lsp adjust-autobandwidth name name command. This adjustment failed, and the LSP continued on the existing path with its current bandwidth. Manual autobandwidth adjustment is a JUNOS Release 7.0 feature that enables you to issue the request mpls lsp adjust-autobandwidth name name command to manually adjust the bandwidth.
Cause
This LSP event is caused by a Constrained Shortest Path First (CSPF) computation failure or a signaling failure on the new path. When you issue the request mpls lsp adjust-autobandwidth name name command, 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, traffic on the LSP is routed through the new path and the old path is removed in a make-before-break fashion. If the attempt fails, the traffic on the LSP continues to use its current path.
Action
Take the corrective action appropriate to the situation:
- Verify the MPLS and RSVP configurations on all available paths to the LSP endpoint. For more information on verifying the MPLS and RSVP configurations, see the JUNOS MPLS Network Operations Guide.
- Check available bandwidth on alternate paths using the
show rsvp interfacecommand. If not enough bandwidth is available on any available paths, adjust the minimum-bandwidth parameter for the LSP in order to establish or adjust the priority to allow the LSP to preempt another LSP of lesser priority. For an LSP to be preempted, its hold priority must be lower than the LSP you are trying to establish.
Manual Autobandwidth Adjustment Succeeded Event
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...]
What It Means
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.