
Configuring Dial Services
1-14
How Bandwidth-on-Demand Pools and Circuits Work Together
For each primary line that requires bandwidth-on-demand service, you assign a
pool ID. If a secondary line comes up, the circuit that runs over this line inherits
the configuration and protocol characteristics of the circuit running over the
primary line. Note that you must first configure a leased circuit and a bandwidth-
on-demand pool before you configure a bandwidth-on-demand circuit.
You can assign the same bandwidth pool ID to more than one primary line. If you
want only one secondary line dedicated to a primary line, configure only one line
in the pool and assign that pool exclusively to that circuit.
Activating Secondary Lines
When the router detects congestion on the primary line, it selects a secondary line
from a bandwidth-on-demand pool. If the secondary line does not relieve the
congestion, a third and possibly a fourth line are added. The router activates a line
only when the primary line is congested. Unlike dial backup, the additional line
does not activate if the primary line fails.
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 primary line. If the data traffic exceeds a threshold,
the router attempts to activate a secondary line. Once the amount of traffic on the
primary line falls below the congestion threshold, the router again uses only that
line. Refer to “Monitoring Congestion on the Primary Circuit,” in Chapter 5, for
details about the monitor parameters.
Terminating Secondary Lines
The router brings down secondary lines for any of these reasons:
• The primary line fails
• The primary line is no longer congested
• The remote router terminates the connection
• There is a physical problem with the line
Komentáře k této Příručce