Downloads |
Table Of Contents
Configure Enhanced Load Balancing
Configure the DLSw+ Explorer Wait Time
DLSw+ Enhanced Load Balancing
Feature Summary
In a network with multiple capable paths, the DLSw+ Enhanced Load Balancing feature improves traffic load balancing between peers by distributing new circuits based on existing loads and the desired ratio.
Benefits
For each capable peer (peers that have the lowest or equal cost specified), the DLSw+ Enhanced Load Balancing feature calculates the difference between the desired and the actual ratio of circuits being used on a peer. It detects the path that is underloaded in comparison to the other capable peers and will assign new circuits to that path until the desired ratio is achieved.
When a DLSw+ router is deciding which path to use to start a new circuit, it checks to see what type of load balancing is configured. In , assume Router B and Router C have 8 circuits each and then Router B fails. As a result, Router C now has 8 circuits and Router B has 0. When Router B recovers, the recovered 8 circuits will be distributed in the following manner, depending on the type of load balancing that is configured:
•
Round-robin load balancing—The DLSw+ router distributes the new circuits in a round-robin fashion, resulting in 4 circuits on Router B and 12 circuits on Router C.
•
Figure 1 DLSw+ with Enhanced Load Balancing
If router B is a Cisco 7500 and router C is a Cisco 2500, the user can configure Router B with a circuit-weight of 20 and Router C with a circuit-weight of 10. In this case, router A knows that router B should be handling twice as many circuits as router C. Router A checks how many circuits it has with each peer and makes its decision based on a 2:1 ratio. The 8 new circuits are distributed to router B and when more circuits are created, all of the new circuits would come up through router B until there is a 2:1 ratio between router B and router C.
If router B fails and then recovers, the first 16 circuits go to router B to achieve the 2:1 balance because router C already has 8 circuits.
Restrictions
Only TCP and DLSw+ Lite encapsulation work with the DLSw+ Enhanced Load Balancing feature.
Platforms
This feature is supported on the following platforms:
•
•
•
•
•
•
•
•
•
Prerequisites
Because a DLSw+ peer selects its new circuit paths from within its reachability cache, the user must configure the dlsw timer explorer-wait-time command with enough time to allow for all the explorer responses to be received. If the new DLSw+ Enhanced Load Balancing Feature is enabled, a message is displayed on the console to alert the user that the timer is not set.
For multiple peer connections, peer costs must be applied. The DLSw+ Enhanced Load Balancing feature works only with the lowest (or equal) cost peers. For example, if the user specifies dlswrtr1, dlswrtr2 and dlswrtr3 with costs of 4, 3, and 3 respectively, DLSw+ establishes new circuits with only dlswrtr 2 and dlswrtr3.
Supported MIBs and RFCs
No MIBs are supported by this feature.
This feature supports the following RFCs:
•
•
Configuration Tasks
Configure Enhanced Load Balancing
To enable the DLSw+ Enhanced Load Balancing feature on the local router, use the following command in global configuration mode:
dlsw load-balance [round-robin | circuit count circuit-weight]
Configures the DLSw+ Enhanced Load Balancing feature on the local router.
To adjust the circuit weight for a remote peer with TCP encapsulation, use the following command in global configuration mode:
dlsw remote-peer tcp [circuit-weight value]
Adjust the circuit weight on the remote peer.
To adjust the circuit weight for a remote peer with DLSw+ Lite encapsulation, use the following command in global configuration mode:
dlsw remote-peer frame-relay interface serial number dlci number [circuit-weight value]
Adjust the circuit weight on the remote peer.
The circuit-weight of a remote peer controls the number of circuits that peer can take. If multiple, equally low-cost peers can reach a remote source, the circuits to that remote source are distributed among the remote peers based on the ratio of their configured circuit-weights. The peer with the highest circuit-weight takes more circuits.
Configure the DLSw+ Explorer Wait Time
To configure the amount of time needed for all the explorer responses to be received, use the following command in global configuration mode:
dlsw timer {explorer-wait-time}
Time to wait for all stations to respond to explorers.
Configuration Examples
shows DLSw+ configured with the DLSw+ Enhanced Load Balancing feature.
Figure 2 DLSw+ with Enhanced Load Balancing
Router A is configured for the DLSw+ Enhanced Load Balancing feature to load balance traffic among the DLSw+ remote peers B, C, and D.
Router A
dlsw local-peer 10.2.19.1dlsw remote-peer 0 tcp 10.2 24.2 circuit-weight 10dlsw remote-peer 0 tcp 10.2.19.5 circuit-weight 6dlsw remote-peer 0 tcp 10.2.20.1 circuit-weight 20dlsw load-balance circuit-countdlsw timer explorer-wait-time 100Router B
dlsw local-peer 10.2.24.2 cost 1 promiscuousRouter C
dlsw local-peer 10.2.19.5 cost 1 promiscuousRouter D
dlsw local-peer 10.2.20.1 cost 1 promiscuousCommand Reference
This section documents new or modified commands. All other commands used with this feature are documented in the Cisco IOS Release 12.0 command references.
dlsw load-balance
Use the dlsw load-balance global configuration command to enable load balancing and to select either round robin or circuit-count based load balancing.
dlsw load-balance [round-robin | circuit-count circuit-weight]
no dlsw load-balance [round-robin | circuit-count circuit-weight]Syntax Description
Default
Fault-tolerant mode is the default setting. The default value for the circuit-weight is 10.
Command Mode
Global configuration
Usage Guidelines
This command first appeared in 12.0(3)T.
A circuit is never be taken down and reestablished by the code in an attempt to rebalance the load. The DLSw+ Enhanced Load Balancing feature only changes the decision-making process at the time a new circuit is desired.
The dlsw load-balance command replaces the dlsw duplicate-path-bias load balance command. The latter command continues to be accepted, however, it will be converted to the new command if the configuration is displayed or saved.
Example
The following example enables the DLSw+ Enhanced Load Balancing feature:
dlsw load -balance circuit-count 10dlsw remote-peer frame-relay
Use the dlsw remote-peer frame-relay global configuration command to specify the remote peer with which the router will connect. Use the no form of this command to disable the previous assignments.
dlsw remote-peer list-number frame-relay interface serial number dlci-number
[backup-peer [ip-address | frame-relay interface serial number dlci-number |
interface name]] [bytes-netbios-out bytes-list-name] [circuit-weight weight] [cost cost]
[dest-mac mac-address] [dmac-output-list access-list-number]
[host-netbios-out host-list-name] [keepalive seconds] [lf size] [linger minutes]
[lsap-output-list list] [passive] pass-thru
no dlsw remote-peer list-number frame-relay interface serial number dlci-number
[backup-peer [ip-address | frame-relay interface serial number dlci-number |
interface name]] [bytes-netbios-out bytes-list-name] [circuit-weight weight] [cost cost]
[dest-mac mac-address] [dmac-output-list access-list-number]
[host-netbios-out host-list-name] [keepalive seconds] [lf size] [linger minutes]
[lsap-output-list list] [passive] pass-thruSyntax Description
Default
No remote peers are specified.
Command Mode
Global configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 11.0. The following keywords and arguments first appeared in Cisco IOS Release 11.2: dest-mac mac-address, dmac-output-list access-list-number, and linger minutes.
The cost keyword specified in a remote peer statement takes precedence over the cost learned as part of the capabilities exchange with the remote peer. The cost keyword is relevant only in fault tolerance mode.
When you need to permit access to only a single MAC address, the dest-mac option is a simpler configuration than the dmac-output-list option.
When pass-thru is not specified, traffic is locally acknowledged and reliably transported in LLC2 across the WAN.
Examples
The following example specifies a DLSw+ Lite peer as a backup to a primary direct peer:
dlsw remote-peer 0 frame-relay interface serial 1 40 pass-thrudlsw remote-peer 0 frame-relay interface serial 0 30 backup-peer frame-relay interface serial 1 40The following example specifies Frame Relay encapsulation connection for remote peer transport:
dlsw remote-peer 0 frame-relay interface 0 30Related Commands
dlsw remote-peer tcp
Use the dlsw remote-peer tcp global configuration command to identify the IP address of a peer with which to exchange traffic using TCP. Use the no form of this command to remove a remote peer.
dlsw remote-peer list-number tcp ip-address [backup-peer [ip-address | frame-relay
interface serial number dlci-number | interface name]] [bytes-netbios-out bytes-list-name]
[circuit-weight value] [cost cost] [dest-mac mac-address]
[dmac-output-list access-list-number] [dynamic] [host-netbios-out host-list-name]
[inactivity minutes] [dynamic] [keepalive seconds] [lf size] [linger minutes]
[lsap-output-list list] [no-llc minutes] [passive] [priority]
[rif-passthru virtual-ring-number] [tcp-queue-max size] [timeout seconds]
no dlsw remote-peer list-number tcp ip-address [backup-peer [ip-address | frame-relay
interface serial number dlci-number | interface name]] [bytes-netbios-out bytes-list-name]
[circuit-weight value] [cost cost] [dest-mac mac-address]
[dmac-output-list access-list-number] [dynamic] [host-netbios-out host-list-name]
[inactivity minutes] [dynamic] [keepalive seconds] [lf size] [linger minutes]
[lsap-output-list list] [no-llc minutes] [passive] [priority]
[rif-passthru virtual-ring-number] [tcp-queue-max size] [timeout seconds]
Syntax Description
Defaults
No peer IP address is identified.
The linger option is inactive. If the linger option is added with no minutes specified, the default is 5 minutes.
The dynamic option is not on by default. If the dynamic option is added without either the inactivity or no-llc argument specified, the default is to terminate the TCP connection to the remote peer after 5 minutes of no active LLC2 connection.
Command Mode
Global configuration
Usage Guidelines
This command first appeared in Cisco IOS Release 10.3. The following keywords and arguments first appeared in Cisco IOS Release 11.1: dynamic, inactivity minutes, linger minutes, no-llc minutes and timeout seconds. The following keywords and arguments first appeared in Cisco IOS Release 11.2: dest-mac mac-address, dmac-output-list access-list-number, linger minutes.
SNA Dial-on-Demand Routing allows switched links to be closed during idle periods. To enable this feature, set the keepalive option to 0 and configure the timeout option. When the dynamic option is configured, the keepalive option is automatically set to 0.
To enhance DDR cost-savings, you can configure the TCP connection to a remote peer to be dynamically established (that is, established only when there is DLSw data to send). You can further configure the TCP connection to terminate after a specified period of idle time on the peer or after a specified period of no active LLC sessions on the peer.
You cannot use both no-llc and inactivity in a command specifying a dynamic peer.
When you need to permit access to a single MAC address, the dest-mac option is a shortcut over the dmac-output-list option.
Use the linger option to specify that a backup peer will remain connected for a specified period of time after the primary connection is gone.
When the priority option on the dlsw remote-peer command is configured, DLSw+ automatically activates four TCP ports to that remote peer (ports 2065, 1981, 1982 and 1983) and assigns traffic to specific ports. Furthermore, if APPN is running with DLSw+ and you specify the priority option on the dlsw remote-peer command, then the SNA TOS maps APPN class COS to TCP TOS and preserves the APPN COS characteristics throughout the network.
The rif passthru option works only on Token Ring LANs via SRB. Other LAN types, such as SDLC and QLLC, are not supported. The RIF Passthru feature is supported with TCP encapsulation and it disables local acknowledgment.
The following features are not supported with the DLSw+ RIF Passthru feature:
•
•
•
•
Examples
The following example specifies a TCP encapsulation connection for remote peer transport:
dlsw remote-peer 0 tcp 10.2.17.8The following example specifies a TCP peer as backup to a primary FST peer:
dlsw remote-peer 0 fst 10.2.18.9dlsw remote-peer 0 tcp 10.2.17.8 backup-peer 10.2.18.9Related Commands
