Checking The Acl That Defines The Interesting Traffic; Troubleshooting The Isdn Connection - HP ProCurve 7000dl Series Basic Management And Configuration Manual

Configuring Demand Routing for Primary ISDN Modules
Troubleshooting Demand Routing

Checking the ACL That Defines the Interesting Traffic

If the demand interface is up, you should ensure that the interesting traffic
actually triggers the ISDN connection. Check the routing table to ensure that
the demand interface is listed as a directly connected interface and that the
route you entered for the far-end network lists the demand interface as the
forwarding interface. From the enable mode context, enter:
ProCurve# show ip route
If the route is correct, you can send some traffic to the far-end network to
determine if the ACL is triggering ISDN traffic. Even a simple ping command
should start the demand routing process (as long as the ping matches the
ACL—for example, you may need to use the extended ping commands to set
the source address for the ping to a local network address). Before you send
the sample traffic, enable debugging for demand routing. From the enable
mode context, enter:
ProCurve# debug demand-routing
If you have configured your ACL correctly, debug messages for demand
routing should appear immediately. If no messages appear, you may have
configured the ACL incorrectly. Double-check the permit statement you con-
figured, and ensure that you applied the ACL to the demand interface. To check
this information, enter the show running-config command from the enable
mode context.
If you can troubleshoot the problem after business hours (when you will not
inadvertently interrupt the flow of traffic to other interfaces), you may want
to change the ACL to select all traffic from any source to any destination. The
ACL should then trigger the ISDN connection. You can then begin to narrow
the scope of the ACL to limit the traffic selected.

Troubleshooting the ISDN Connection

If the interesting traffic triggers the ISDN connection, the ProCurve Secure
Router will find the appropriate connect-sequence command to process
(based on your configuration) and try to establish a connection. If the router
is unable to establish this connection, you will need to monitor the call setup.
The Secure Router OS provides a number of ISDN debug commands, which
are listed in Table 8-16.
8-73