Checking The Acl That Defines The Interesting Traffic - HP ProCurve Secure 7000dl Series Basic Management And Configuration Manual

Status Meaning
getting TEI #2 The switch cannot identify the BRI
interface (second B channel).
TEI #2 OK The switch is having trouble
bringing the interface up.
Getting SPID #2
Miskeyed SPIDs and LDNs are the most common problems. Try reentering the
SPID and, if necessary, reloading the router so that the BRI interface will be
forced to re-initiate the handshaking process. Or enter maintenance reset
to reset the port hardware.
Remember, however, that the wrong configuration for the switch-type can also
cause the status to remain at "getting TE1 #1" or "getting TE1 #2." The switch-
type depends on the type of ISDN signaling the public carrier institutes on the
line, which depends on its software, not necessarily on the switch's
manufacturer.

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.
Configuring Demand Routing for Primary ISDN Modules
Troubleshooting Demand Routing
Next Best Step
• Check for a miskeyed SPID2 and/or LDN.
• If you should not have to enter a second SPID, the
interface may be configured for the wrong signaling type.
• Try resetting the connection. You may need to reload the
router, if possible.
8-71