Configuring Automatic Bandwidth Adjustment for MPLS TE Tunnels
This chapter describes how to configure automatic bandwidth adjustment for Multiprotocol Label Switching (MPLS) traffic engineering (TE) tunnels on Cisco NX-OS devices.
This chapter includes the following sections:
- Finding Feature Information
- Information About Automatic Bandwidth Adjustment for TE Tunnels, page 12-2
- Licensing Requirements for Automatic Bandwidth Adjustment for TE Tunnels, page 12-2
- Prerequisites for Automatic Bandwidth Adjustment for TE Tunnels, page 12-2
- Guidelines and Limitations for Automatic Bandwidth Adjustment for TE Tunnels, page 12-3
- Default Settings for Automatic Bandwidth Adjustment for TE Tunnels, page 12-3
- Configuring Automatic Bandwidth Adjustment for TE Tunnels, page 12-3
- Verifying the Automatic Bandwidth Configuration, page 12-6
- Configuration Examples for Automatic Bandwidth Adjustment for TE Tunnels, page 12-8
- Additional References, page 12-9
- Feature History for Automatic Bandwidth Adjustment for TE Tunnels, page 12-10
Information About Automatic Bandwidth Adjustment for TE Tunnels
The automatic bandwidth adjustment for TE tunnels feature allows you to configure MPLS to automatically monitor and adjust the bandwidth allocation for TE tunnels based on their measured traffic load. The automatic bandwidth behavior changes the configured bandwidth in the running configuration. If automatic bandwidth is configured for a tunnel, TE automatically adjusts the tunnel’s bandwidth.
The automatic bandwidth adjustment feature samples the average output rate for each tunnel that is marked for automatic bandwidth adjustment. For each marked tunnel and for the time frequency configured, the feature adjusts the tunnel’s allocated bandwidth to be the largest sample for the tunnel since the last adjustment.
The frequency with which the tunnel bandwidth is adjusted and the allowable range of adjustments is configurable on a per-tunnel basis. The sampling interval and the interval over which to average the tunnel traffic to obtain the average output rate are user configurable on a per-tunnel basis.
This feature adjusts the TE tunnel’s bandwidth, which is the amount of bandwidth requested by a tunnel. Tunnels only use linked with enough bandwidth left to accommodate this request. (TE link bandwidth is the pool of bandwidth from which TE tunnels allocate requested amount. Tunnels can traverse only those links with enough bandwidth left to satisfy the requirement.)
Licensing Requirements for Automatic Bandwidth Adjustment for TE Tunnels
The following table shows the licensing requirements for this feature:
|
|
Cisco NX-OS |
Automatic bandwidth adjustment for TE tunnels requires an MPLS license. For a complete explanation of the NX-OS licensing scheme and how to obtain and apply licenses, see the Cisco NX-OS Licensing Guide. |
Prerequisites for Automatic Bandwidth Adjustment for TE Tunnels
The automatic bandwidth adjustment for TE tunnels feature has the following prerequisites:
- You must enable the MPLS TE feature. MPLS TE can be enabled or disabled by the [ no ] feature mpls traffic-eng command and is enabled by default.
- You must configure the MPLS TE feature by using the mpls traffic-eng bandwidth command on each link that a tunnel crosses.
If the bandwidth command is configured for the tunnel, the command configures the initial tunnel bandwidth, which is adjusted by the automatic bandwidth operation.
Note If you configure a tunnel’s bandwidth with the bandwidth command and configure the minimum amount of automatic bandwidth with the auto-bw command, the minimum amount of automatic bandwidth adjustment is the lower of those two configured values.
Guidelines and Limitations for Automatic Bandwidth Adjustment for TE Tunnels
The automatic bandwidth adjustment feature has the following configuration guidelines and limitations:
- The automatic bandwidth adjustment feature adjusts the bandwidth for each tunnel according to the adjustment frequency configured for the tunnel and the sampled output rate for the tunnel since the last adjustment. The adjustment feature does not consider any adjustments previously made or pending for other tunnels.
- If a tunnel is brought down to calculate a new label switched path (LSP) because the LSP is not operational, the configured bandwidth is removed. If the router is reloaded, the system gives a new configured bandwidth.
- You cannot configure MPLS TE over the logical generic routing encapsulation (GRE) tunnel interface.
- MPLS traffic engineering should not be configure in more than one IGP process/instance.
Default Settings for Automatic Bandwidth Adjustment for TE Tunnels
Table 12-1 lists the default settings for automatic bandwidth adjustment for TE tunnels.
Table 12-1 Default Settings for Automatic Bandwidth Adjustment for TE Tunnels
|
|
Frequency |
86400 seconds |
Configuring Automatic Bandwidth Adjustment for TE Tunnels
This section includes these topics:
Enabling Automatic Bandwidth Adjustment on a Platform
You can enable automatic bandwidth adjustment on a platform and initiate sampling of the output rate for tunnels that are configured for bandwidth adjustment.
Note This task applies only to the TE headend router. The configuration applies to all locally configured TE headend interfaces.
Prerequisites
You must enable the MPLS TE feature (see the “Configuring MPLS TE”).
Ensure that you are in the correct VDC (or use the switchto vdc command).
SUMMARY STEPS
1. configure terminal
2. mpls traffic-eng
3. auto-bw timers [ frequency seconds ]
4. no auto-bw timers
5. end
DETAILED STEPS
|
|
|
Step 1 |
configure terminal Example: switch# configure terminal switch(config)# |
Enters global configuration mode. |
Step 2 |
mpls traffic-eng Example: switch(config)# mpls traffic–eng switch(config-te)# |
Enters traffic engineering global configuration mode. |
Step 3 |
auto-bw timers [ frequency seconds ] Example: switch(config-te)# auto–bw timers frequency 300 |
Enables automatic bandwidth adjustment on a platform and begins sampling the output rate for tunnels that have been configured for automatic bandwidth adjustment. The seconds argument specifies the interval, in seconds, for sampling the output rate of each tunnel configured for the automatic bandwidth adjustment. The range is from 1 through 604800. The recommended value is 300. |
Step 4 |
no auto-bw timers Example: switch(config-te)# no auto–bw timers |
(Optional) Disables the automatic bandwidth adjustment on a platform. Use the no version of the command, which terminates the output rate sampling and bandwidth adjustment for tunnels. In addition, the no form of the command restores the configured bandwidth for each tunnel where the configured bandwidth is determined as follows:
- If the tunnel bandwidth was explicitly configured with the bandwidth command after the running configuration was written to the startup configuration, the configured bandwidth is the bandwidth specified by that command.
- If the tunnel bandwidth was not explicitly configured with the bandwidth command, the configured bandwidth is the bandwidth specified for the tunnel in the startup configuration.
|
Step 5 |
end Example: switch(config-te)# end switch# |
Exits to EXEC mode. |
Enabling Automatic Bandwidth Adjustment for a TE Tunnel
You can enable the automatic bandwidth adjustment for a tunnel and specify the range of automatic bandwidth adjustments applied to the tunnel.
Tip Each auto-bw command supersedes the previous one. To specify multiple options for a tunnel, you must specify them all in a single auto-bw command.
SUMMARY STEPS
1. configure terminal
2. interface tunnel-te number
3. auto-bw [collect-bw] [[frequency seconds] [min-bw kbps] [max-bw kbps]]
4. end
DETAILED STEPS
|
|
|
Step 1 |
configure terminal Example: switch# configure terminal switch(config)# |
Enters global configuration mode. |
Step 2 |
interface tunnel-te number Example: switch(config)# interface tunnel-te 1 switch(config-if-te)# |
Enters TE interface configuration mode. The number argument identifies the tunnel number to be configured. |
Step 3 |
auto-bw [collect-bw] [[frequency seconds] [min-bw kbps] [max-bw kbps]]
Example: switch(config-if-te)# auto-bw max-bw 2000 min-bw 1000 frequency 300 |
Enables the automatic bandwidth adjustment for the tunnel and controls the manner in which the bandwidth for a tunnel is adjusted. NOTE: The collect-bw and min-bw/max-bw variables are mutually exclusive because the switch does not perform an actual application when you specify collect-bw. |
Step 4 |
end Example: switch(config-if-te)# end switch# |
Exits to EXEC mode. |
Verifying the Automatic Bandwidth Configuration
To verify the automatic bandwidth configuration, perform one of the following tasks:
|
|
|
|
show mpls traffic-eng tunnels |
Displays information about tunnels. It includes automatic bandwidth information for tunnels that have the feature enabled. |
|
show running-config interface tunnel-te id |
Verifies that the tunnel mpls traffic-eng auto bw command is set appropriately. |
The following example shows how to display information about tunnels. The command output shows the following:
- The auto-bw line indicates that the automatic bandwidth adjustment is enabled for the tunnel.
- 86400 is the time, in seconds, between bandwidth adjustments.
- 86258 is the time, in seconds, remaining until the next bandwidth adjustment.
- 0 is the largest bandwidth sample since the last bandwidth adjustment.
- 0 is the last bandwidth adjustment and the bandwidth currently requested for the tunnel.
switch# show mpls traffic-eng tunnels tunnel-te 2
Name: N7K-Get-well-R1_t2 (tunnel-te2) Destination: 10.0.0.4
Admin: up Oper: up Path: valid Signalling: connected
path option 1, type explicit path2(Basis for Setup, path weight 80)
Bandwidth: 500 kbps (Global) Priority: 7 7 Affinity: 0x0/0xffff
Metric Type: TE (default)
AutoRoute: disabled LockDown: disabled
auto-bw: (300/245) 583 Bandwidth Requested: 555
Samples Missed 1: Samples Collected 1
Active Path Option Parameters:
State: explicit path option 1 is active
BandwidthOverride: disabled LockDown: disabled Verbatim: disabled
OutLabel : Ethernet1/26, 2003
Src 10.0.0.2, Dst 10.0.0.4, Tun_Id 2, Tun_Instance 2
Explicit Route: 24.0.0.2.26.0.0.1.26.0.0.2 10.0.0.4
Tspec: ave rate=555 kbits, burst=1000 bytes, peak rate=555 kbits
Record Route: 24.0.0.2 26.0.0.2
Fspec: ave rate=555 kbits, burst=1000 bytes, peak rate=555 kbits
Shortest Unconstrained Path Info:
Explicit Route: 22.0.0.1 22.0.0.2 25.0.0.1 25.0.0.2
Time since created: 7 minutes, 43 seconds
Time since path change: 2 minutes, 21 seconds
Number of LSP IDs (Tun_Instances) used: 2
Uptime: 1 minutes, 23 seconds
Selection: reoptimization
Removal trigger: configuration changed
The following example shows how to verify that the tunnel mpls traffic-eng auto bw command is set appropriately. The command output shows that the bandwidth value has changed after adjustment (the bandwidth is 1500).
switch# show running-config interface tunnel-te1
!Time: Mon Nov 25 19:32:35 2013
auto-bw frequency 300 min-bw 300
path-option 1 explicit name path1
record-route
Configuration Examples for Automatic Bandwidth Adjustment for TE Tunnels
Figure 12-1 shows a sample MPLS topology. The following sections contain sample configuration examples about configuring an automatic bandwidth adjustment for MPLS TE tunnels that originate on Router 1 and enabling automatic bandwidth adjustment for Tunnel 1.
Figure 12-1 Sample MPLS Traffic Engineering Tunnel Configuration
This section provides the following configuration examples based on Figure 12-1:
The examples omit some configuration required for MPLS TE, such as the required Resource Reservation Protocol (RSVP) and Interior Gateway Protocol (IGP), and either Intermediate System-to-Intermediate System (IS-IS) or Open Shortest Path First (OSPF) configuration. The examples show the configuration for automatic bandwidth adjustment.
Example: Configuring the MPLS Traffic Engineering Automatic Bandwidth
The following example shows how to use the auto-bw timers command to enable an automatic bandwidth adjustment for Router 1. The command specifies that the output rate is to be sampled every 10 minutes for tunnels configured for automatic bandwidth adjustment.
auto-bw timers frequency 600 !Enable automatic bandwidth adjustment
ip address 192.168.11.11 255.255.255.0
Example: Tunnel Configuration for Automatic Bandwidth
The following example shows how to use the auto-bw command to enable an automatic bandwidth adjustment for Tunnel 1. The command specifies a maximum allowable bandwidth of 2000 kbps, a minimum allowable bandwidth of 1000 kbps, and a default automatic bandwidth adjustment frequency of once a day.
destination 192.168.17.17
auto-bw max-bw 2000 min-bw 1000 !Enable automatic bandwidth
Additional References
The following sections provide references related to the automatic bandwidth adjustment for TE tunnels feature.
Standards
|
|
No new or modified standards are supported by this feature, and support for existing standards has not been modified by this feature. |
— |
MIBs
|
|
MPLS Traffic Engineering MIB |
To locate and download MIBs for selected platforms, Cisco NX-OS releases, and feature sets, use Cisco MIB Locator found at the following URL: http://www.cisco.com/go/mibs |
RFCs
|
|
No new or modified RFCs are supported by this feature, and support for existing RFCs has not been modified. |
— |
Feature History for Automatic Bandwidth Adjustment for TE Tunnels
Table 12-2 lists the release history for this feature.
Table 12-2 Feature History for MPLS Traffic Engineering—Automatic Bandwidth Adjustment for TE Tunnels
|
|
|
Automatic Bandwidth Adjustment for TE Tunnels |
6.2(6) |
This feature was introduced. |