HP 7102dl - ProCurve Secure Router Configuration Manual page 163

Viewing Backup Configurations and Troubleshooting Backup Connections
Verify that the SPID(s) and/or LDN(s) are correct. If you are located in North
America, double-check whether your public carrier has assigned you one or
two SPIDs. When you use both B channels, public carriers that use National
ISDN and Northern Telecom DMS-100 sometimes require you to configure a
SPID for each channel.
Troubleshooting a BRI Interface. When you activate the BRI interface, it
exchanges a series of messages with the switch at the CO. First, the interface
and the switch complete a handshaking process to bring up the Physical Layer.
Then the CO switch polls the line for terminal equipment identifiers (TEIs).
The TEI identifies the ISDN line.
bri 1/3 is DOWN
Line status: getting TEI #1
Caller ID will be used to route incoming calls
Caller ID normal
Switch protocol: AT&T 5ESS
SPID 1 25655522220101, LDN 1 5552222
SPID 2 n/a, LDN 2 n/a
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 0 bits/sec, 0 packets/sec
1115 packets input, 0 bytes, 0 no buffer
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame
0 abort, 0 discards, 0 overruns
1117 packets output, 0 bytes, 0 underruns
Figure 3-22. Troubleshooting a BRI Interface
The TEI #1 identifies the first B channel, and the TEI #2 identifies the second.
The BRI interface sends the SPIDs and/or LDNs that you have configured for
it to the switch (SPID1 for the TEI #1 and SPID2 for the TEI #2). After the
switch receives the correct SPIDs, the ISDN line goes up.
The line status indicates the point at which this process derails. For example,
in Figure 3-22, the line status indicates that the CO switch is attempting to get
the BRI interface's SPID1. See Table 3-13 for problems that can cause a
particular line status.
Configuring Backup WAN Connections
The switch at the CO
cannot identify
the interface.
Check the SPID and
LDN
3-75