Configuring Demand Routing for Primary ISDN Modules
Troubleshooting Demand Routing
interface demand 1
idle-timeout 240
resource pool Pool
match-interesting list Call out
match-interesting reverse list Call in
connect-sequence 1 dial-string 9633333 forced-isdn-64k busyout-threshold 3
connect-sequence 2 dial-string 9634444 forced-isdn-64k busyout-threshold 3
connect-sequence interface-recovery retry-interval 120 max-retries 0
ip address
10.1.1.1
ppp authentication pap
ppp multilink
ppp multilink maximum 2
username procurve password procurve
ppp pap sent-username procurve password procurve
no shutdown
8-68
Figure 8-23 shows the running-config for a demand interface that is configured
to use MLPPP and PPP authentication.
255.255.255.0
Figure 8-23. Viewing the Running-Config for a Demand Interface
Troubleshooting Demand Routing
After you configure demand routing, you should test your configuration to
ensure that it is working correctly. Is the right traffic triggering the connection,
and can the BRI interface successfully establish a connection to the far-end
router? Are your settings for the idle-timeout and the fast-idle sufficient for
your WAN environment?
Checking the Demand Interface
The first step you should take to check your configuration is also the first step
you should take to troubleshoot demand routing. You should ensure that the
demand interface and its associated BRI interfaces are ready to make a
connection.
Use the show interfaces demand command to view the status of the demand
interface, which should be up (spoofing). If the demand interface is down,
ensure that you have assigned it a valid IP address. If you configured the
demand interface as an unnumbered interface, make sure that the interface
with the actual IP address is up.
Need help?
Do you have a question about the ProCurve Secure 7000dl Series and is the answer not in the manual?
Questions and answers