Work - HP 7102dl - ProCurve Secure Router Configuration Manual

interface demand 1
connect-order sequential
connect-sequence attempts 3
connect-sequence 10 dial-string 5551212 forced-isdn busyout-threshold 3
connect-sequence 20 dial-string 5552222 forced-analog busyout-threshold 1
connect-sequence interface-recovery retry-interval 60 max-retries 5
resource pool Pool
Understanding How the connect-sequence Commands Work
Because you can configure a number of settings for connect sequences, it is
important to understand how these settings interrelate. For example, consider
the configuration shown in Figure 3-8.
Figure 3-8. Connection Instructions for a Demand Interface
The resource pool for this configuration contains two members: a BRI inter-
face and a modem interface. If the primary interface for a connection goes
down and interesting traffic is forwarded to this demand interface, the
ProCurve Secure Router will first process connect sequence 10, which
requires an ISDN connection. If the BRI interface is available, Figure 3-8 shows
that the ProCurve Secure Router will try to call 5551212.
If the ISDN connection is not established, the ProCurve Secure Router will try
to process connect sequence 20, which requires an analog connection.
Because the busyout-threshold is set to 1, the ProCurve Secure Router will
try this connection only once. If the analog connection is unsuccessful, the
ProCurve Secure Router will try connect sequence 10 up to two more times
(for a total of three cycles).
If the ProCurve Secure Router processes all of the connect sequences and
cannot establish a dial-up connection, the connect sequence attempt fails. For
the configuration shown in Figure 3-8, the ProCurve Secure Router will make
three activation attempts—that is, it will process all connect sequence 10 up
to nine times and connect sequence 20 up to three times.
If all three attempts are unsuccessful, the ProCurve Secure Router will change
the status of the demand interface to "down (recovery active)." It will then
remove the IP address and any routes referencing the interface, allowing any
routes with higher metrics to take their place.
Configuring Backup WAN Connections
Configuring Demand Routing for Backup Connections
3-33