Configuring Demand Routing for Primary ISDN Modules
Troubleshooting Demand Routing
If the demand interface went down because it could not establish a connection
during the recovery mode, its status will be down (recovery failed). In this
case, you must identify the problem causing the failure and then you must
clear the connection so that the status of the demand interface returns to up
(spoofing). Until then, the demand interface cannot establish an ISDN
connection.
To clear the ISDN connection, shut down the demand interface. From the
demand interface configuration mode context, enter:
ProCurve(config-demand 1)# shutdown
To re-activate the interface, enter:
ProCurve(config-demand 1)# no shutdown
Checking the BRI Interface
To ensure that the status of the BRI interface is up and the line status is ready,
enter the following command from the enable mode context:
ProCurve# show interface bri <slot>/<number>
If the BRI interface is administratively down, enter no shutdown to activate it.
When you activate the BRI interface, it exchanges a series of messages with
the ISDN switch at the CO. First, the BRI interface and the switch complete a
handshaking process to bring up the Physical Layer. Then the ISDN switch
polls the line for terminal equipment identifiers (TEIs), which identify the
ISDN line.
The TEI #1 identifies the first B channel, and the TEI #2 identifies the second.
The BRI interface sends the LDNs and/or SPIDs configured for the channels
(SPID1 for the TEI #1 and SPID2 for the TEI #2). After the switch receives the
correct SPIDs or LDNs, the ISDN line goes up.
When you enter the show interfaces bri command, the line status indicates
the point at which the handshaking process breaks down. For example, in
Figure 8-24 the ISDN switch is attempting to get the BRI interface's SPID1.
8-69
Need help?
Do you have a question about the ProCurve Secure 7000dl Series and is the answer not in the manual?
Questions and answers