
Configuring Dial Services
1-20 114062 Rev. A
How Lines, Pools, and Circuits Work Together
For each leased circuit or demand circuit, you assign a pool ID. If the line or
bundle becomes congested, the router activates a secondary line. The secondary
circuit that runs over this line inherits the configuration and protocol
characteristics of the leased circuit.
You can assign the same bandwidth pool ID to more than one circuit. If you want
a pool of secondary lines dedicated to one specific bandwidth circuit, assign that
pool exclusively to that circuit. Remember to first configure a leased or demand
connection before configuring a bandwidth-on-demand configuration.
Activating Secondary Lines
If the secondary line from the bandwidth pool does not relieve the congestion, the
router adds up to 29 lines until the congestion is relieved. The router activates a
secondary line only for a congested line, not for a failed line.
PPP multilink detects a state of congestion based on byte counts and the
user-configurable monitor parameters. The monitor parameters let you define
congestion thresholds for the leased circuit. If data traffic exceeds a threshold, the
router tries activating a secondary line. Once the amount of traffic on the
congested line falls below the congestion threshold, the router again uses only the
leased line, demand line, or bundle. Refer to Chapter 10 for details about the
monitor parameters.
Terminating Secondary Lines
The router brings down secondary lines for any of these reasons:
• The leased line or multilink bundle fails.
• The leased circuit is no longer congested.
• The remote router terminates the connection.
• There is a physical problem with the dial-up line.
Note: Byte counts are measured prior to data compression.
Comentarios a estos manuales