INTRODUCTION
The RPI Cisco Network Academy lab implements at least twelve (12)
router pods with ISDN BRI connectivity for the Remote Access and
Troubleshooting labs. ISDN BRI connectivity is provided through an
ADTRAN Atlas 800 ISDN switch. For the students to configure ISDN BRI
circuits properly, the Atlas 800 switch must be configured with correct
SPIDs, LDNs (optional), and other BRI parameters.
The purpose of this document is to describe how to configure the
Atlas 800 switch to support to BRI-based labs of the Cisco Network
Academy courses. A basic method for verifying the configuration of the
BRIs on the switch is described.
HARDWARE USED IN DIALUP LAB
The hardware implemented in the RPI Cisco Network Academy for the
ISDN BRI-based labs dialup are:
1. ADTRAN Atlas 800 ISDN switch
This switch has 16 ISDN BRI U interfaces and 4 T1/PRI interfaces.
PRI interfaces can be configured as one of the following switch
types: Lucent 5ESS, Northern DMS-100, National ISDN, AT&T 4ESS.
BRI interfaces can be configured as on of the following switch
types: Lucent 5ESS, Northern DMS-100, National ISDN. Supports
robbed bit signaling (RBS), and a wide variety of other options.
2. External ISDN NT1 units
3. Cisco 4700 routers (and other models) with ISDN BRI S/T modules.
4. Category 5 (or better) twisted-pair straight-through cables.
The hardware setup for the lab is simple. Connect each router's
ISDN BRI interface to the S/T port of the external NT1 unit with a
straight-through cable. Next, connect each external NT1 unit's U
port (labeled "NETWORK" to the U interface of the Atlas 800 with a
straight-through cable. The final step is to configure the BRI
interfaces of the Atlas 800.
ADTRAN ATLAS 800 SWITCH CONFIGURATION
This section describes how the BRI interfaces on the Atlas 800 were
configured in a basic manner sufficient to support the ISDN BRI-based
labs. Other steps taken to configure parts of the switch not directly
related to the BRI interfaces (e.g. system configuration, ISDN PRI
interfaces) are not described herein.
The steps are as follows:
1. With a laptop, attach an RJ-45/RJ-45 flat, straight-through cable
from the Atlas 800's console interface (labeled "IN" on the
"CONTROL/CHAIN" card) to the RJ-45/DB-9F adapter provided for the
Atlas 800. Connect the adapter to the RS-232 DB-9M port of the
laptop.
2. Using your favorite terminal software (e.g., HyperTerminal,
TeraTerm, Putty), establish a serial connection to the Atlas 800.
The following terminal settings are known to work:
Terminal type:
Bit (Baud) rate:
Data bits:
Stop bits:
Parity:
Flow control:
VT100
9600
8
1
none
none
3. Once you establish a connection, enter the password to access the
Atlas 800. The main system menu is similar to that shown in
Figure 1.
Figure 1.
Main system menu of Atlas 800 switch
4. Go to Dial Plan -> User Term. The screen "aaa/Dial Plan/User Term"
will appear (see Fig. 2). With the cursor on the "[+]" entry, press
Enter to get to the window displaying the BRI U interface entries
and PRI interfaces (see Fig. 3).
5. Move the cursor to the right and onto the row corresponding to the
BRI U-interface port you want to configure.
NOTE: The BRI U interfaces are numbered contiguously in the "#"
column, starting from 1. The slot a BRI U interface is in on the
Atlas 800 is given in the "Slot" column. For the Atlas 800 unit in
the lab, two 8-port BRI U-interface cards are installed in slots 1
and 5. As shown in figure 3, the first BRI U-interface in slot 1 is
numbered 1, and the first BRI U-interface in slot 5 is numbered 9.
Incidentally, the slot type can be changed by pressing Enter on the
entry in the "Slot" column and selecting the type from the pop-up
menu (e.g., "5)U-BRI" for the BRI card in slot 5). Normally, you
should not have to change this entry.
Figure 2.
Figure 3.
User terminal window of Atlas 800 switch
BRI/PRI interface list of Atlas 800 switch
Figure 4.
Slot type selection for the Atlas 800 switch
6. Move the cursor to the entry in the "Port" column and press Enter to
bring up the port selection menu (see Fig. 5). This menu allows you
to select from one of 8 BRI U interfaces on the card in the slot
(given in the corresponding "Slot" column).
NOTE: For the purpose of the Cisco Network Academy lab, the
following # / Slot / Port mappings should be used on the Atlas 800:
#
--1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
Slot
-------1)U-BRI
1)U-BRI
1)U-BRI
1)U-BRI
1)U-BRI
1)U-BRI
1)U-BRI
1)U-BRI
5)U-BRI
5)U-BRI
5)U-BRI
5)U-BRI
5)U-BRI
5)U-BRI
5)U-BRI
5)U-BRI
Port
--------------1)Octal BRI/U
2)Octal BRI/U
3)Octal BRI/U
4)Octal BRI/U
5)Octal BRI/U
6)Octal BRI/U
7)Octal BRI/U
8)Octal BRI/U
1)Octal BRI/U
2)Octal BRI/U
3)Octal BRI/U
4)Octal BRI/U
5)Octal BRI/U
6)Octal BRI/U
7)Octal BRI/U
8)Octal BRI/U
Figure 5.
BRI U-interface port selection menu
7. Move the cursor to the entry in the "In#Accept" column and press
Enter; the "Incoming Number Accept List" window will appear (see
Fig. 6). To add a phone number (called an LDN) for each B-channel,
a. Move the cursor to the right to the "#" column, then press the
I key; a new row will be inserted
b. Move the cursor to the "Accept Number" column and press Enter
c. Enter the phone number for the corresponding B-channel (1 or 2
in the "#" column)
d. The settings for the other columns should be left to their
default settings, as shown in figure 6
e. Repeat steps a->e to add a phone number for the second B channel
When the two phone numbers are added, move the cursor to the left
until you arrive at the BRI/PRI interface list.
8. Move the cursor to the entry in the "Out#Rej" column and press
Enter; the "Outgoing Number Reject List" window will appear (see
Fig. 7). There should be no reject number entries listed. If there
are, then move the cursor to the right and press the D key to remove
each entry. When all the entries (if any) are removed, move the
cursor to the left until you arrive at the BRI/PRI interface list.
Figure 6.
Incoming number accept list for BRI U interface
Figure 7.
Outgoing number reject list for BRI U interface
9. Move the cursor to the entry in the "Ifce Config" column and press
Enter; the "Interface Configuration" window will appear (see
Fig. 8). Configure the interface by doing the following:
a. Move the cursor to the right, to the "Switch Type" field, and
press Enter; the switch type pop-up list will appear. Select
"National ISDN" for the ISDN switch type.
Figure 8.
Figure 9.
Interface configuration for BRI U interface
ISDN switch type list for BRI U interface
b. Move the cursor down to the "SPID list" field and press Enter;
the "SPID list" window will appear (see Fig. 10).
c. Move the cursor to the right to the "#" column, then press the
I key; a new row will be inserted
d. Move the cursor to the "Phone #" column and press Enter
e. Enter the phone number for the corresponding B-channel (1 or 2
in the "#" column). This will be the same number entered in
step 7
f. Move the cursor to the "SPID #" column and press Enter
g. Enter the SPID for the corresponding B-channel (1 or 2
in the "#" column). Enter this number as a contiguous string
of digits
h. The settings for the other columns should be left to their
default settings, as shown in figure 10
i. Repeat steps c->h to add a SPID for the second B channel
When the two SPIDs are added, move the cursor to the left until you
arrive at the BRI/PRI interface list.
Figure 10.
SPID entries for the B channels of the BRI U interface
Repeat steps 6 through 9 to configure the remaining BRI U interfaces.
Once finished, you can log out of the Atlas 800 by typing CTRL-L.
TESTING THE ADTRAN ATLAS 800 SWITCH CONFIGURATION
To verify a pod router with an ISDN BRI interface can establish a
connection with the Atlas 800, use the configuration given in figure
11. For the "isdn spid1" and "isdn spid2" lines, change the SPID and
LDN to those that corresponded to the BRI circuit your pod router is
connected to (see Table 1).
config t
!
interface BRI0
ip address 1.1.1.1 255.255.255.252
encapsulation ppp
isdn switch-type basic-ni
isdn twait-disable
isdn spid1 50355501000101 5550100
isdn spid2 50355501010101 5550101
!
end
Figure 11.
Table 1.
Pod Router
P1r1
P2r1
P3r1
P4r1
P5r1
P6r1
P7r1
P8r1
P9r1
P10r1
P11r1
P12r1
P13r1
Configuration for BRI interface of router
ISDN BRI SPIDs and LDNs for Pod Routers
SPIDs for B-Channels
LDNs for B-Channels
50355501000101
50355501010101
50355502000101
50355502010101
50355503000101
50355503010101
50355504000101
50355504010101
50355505000101
50355505010101
50355506000101
50355506010101
50355507000101
50355507010101
50355508000101
50355508010101
50355509000101
50355509010101
50355510000101
50355510010101
50355511000101
50355511010101
50355512000101
50355512010101
50355513000101
50355513010101
5550100
5550101
550200
5550201
5550300
5550301
5550400
5550401
5550500
5550501
5550600
5550601
5550700
5550701
5550800
5550801
5550900
5550901
5551000
5551001
5551100
5551101
5551200
5551201
5551300
5551301
After configuring the BRI interface of the router, run the IOS command
'show isdn status briN' (where N is the BRI interface number). If an
ISDN BRI connection to the Atlas 800 switch was successfully
established, you should see output similar to that in figure 12. In
particular,
* Layer 1 status should be ACTIVE
* At layer 2, each B-channel should be assigned a terminal endpoint
identifier (TEI), and its state will be MULTIPLE_FRAME_ESTABLISHED
as well as in the init state
* At layer 2, each B-channel should indicate "spidN configurd, spidN
sent, spidN valid" (where is the B-channel number, 1 or 2)
* The top of the output of 'show controllers bri N' should show
"Layer 1 is ACTIVATED. (ISDN L1 State F7)" (see Fig. 13)
Figure 14 shows the debug output from 'debug isdn q921' and 'debug isdn
'q931' for a BRI interface that comes up successfully.
p1r1#show isdn status bri0
Global ISDN Switchtype = basic-ni
ISDN BRI0 interface
dsl 0, interface ISDN Switchtype = basic-ni
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 64, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
TEI = 65, Ces = 2, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
TEI 64, ces = 1, state = 5(init)
spid1 configured, spid1 sent, spid1 valid
Endpoint ID Info: epsf = 0, usid = 70, tid = 1
TEI 65, ces = 2, state = 5(init)
spid2 configured, spid2 sent, spid2 valid
Endpoint ID Info: epsf = 0, usid = 70, tid = 2
Layer 3 Status:
0 Active Layer 3 Call(s)
Active dsl 0 CCBs = 0
The Free Channel Mask: 0x80000003
Number of L2 Discards = 0, L2 Session ID = 14
Total Allocated ISDN CCBs = 0
Figure 12.
'show isdn status bri 0' output for a working BRI interface
p6r1#show controllers bri 0
BRI slot 2 unit 0 subunit 0
Layer 1 is ACTIVATED. (ISDN L1 State F7)
Master clock for slot 2 is bri subunit 0.
Total chip configuration successes: 103, failures: 0, timeouts: 0
D Channel Information:
Interrupt Queue Element(index=670): interrupt is enabled
0x0000000 0x0000000 0x0000000 0x0000000 0x0000000 0x0000000
0x0000000 0x0000000 0x0000000 0x0000000 0x0000000 0x0000000
0x0000000 0x0000000 0x0000000 0x0000000 0x0000000 0x0000000
0x0000000 0x0000000 0x0000000 0x0000000 0x0000000 0x0000000
0x0000000 0x0000000 0x0000000 0x0000000 0x0000000 0x0000000
Channel state: UP Channel IDB: 61A95A94
RX ring entries: 5, buffer size 1524
RX descriptor ring: head = 40059FB8, tail = 40059F98
RX pak ring: head = 61C66D24, tail = 61C66D14
00 params=0x25F40000 status=0x80000000 data ptr=0x4026CE6C next ptr=0x40059F88
01 params=0x25F40000 status=0x80000000 data ptr=0x4026ACC0 next ptr=0x40059F98
02 params=0x65F40000 status=0x80000000 data ptr=0x4026C7B0 next ptr=0x40059FA8
03 params=0x25F40000 status=0x80000000 data ptr=0x4026BA38 next ptr=0x40059FB8
04 params=0x25F40000 status=0x80000000 data ptr=0x4026C0F4 next ptr=0x40059F78
TX ring entries: 3, in use: 0, buffer size 1524
TX descriptor ring: head = 40341748, tail = 40341748
TX pak ring: head = 6190DCD8, tail = 6190DCD8
00 params=0xE0000000 data ptr=0x40264C28 next ptr=0x4034173C
01 params=0xA0000000 data ptr=0x40264C28 next ptr=0x40341748
02 params=0xA0000000 data ptr=0x40264C28 next ptr=0x40341730
List of timeslots (sw): 2
List of all timeslots (hw):
00:00FF00FF 01:01FF01FF 02:02C002C0 03:03FF03FF 04:04FF04FF 05:05C005C0
06:06FF06FF 07:07FF07FF 08:08C008C0 09:09FF09FF 10:0AFF0AFF 11:0BC00BC0
12:20002000 13:20002000 14:20002000 15:20002000 16:20002000 17:20002000
18:20002000 19:20002000 20:20002000 21:20002000 22:20002000 23:20002000
24:20002000 25:20002000 26:20002000 27:20002000 28:20002000 29:20002000
30:20002000 31:20002000
Bandwidth: 16, idle channel: Unassigned, idle ts bitfield: 0x0
0 missed datagrams, 0 overruns
0 bad datagram encapsulations, 0 memory errors
0 transmitter underruns, 0 throttles, 0 enables, 0 bad interrupt elements
B1 Channel Information:
Interrupt Queue Element(index=676): interrupt is enabled
0x0000000 0x0000000 0x0000000 0x0000000 0x0000000 0x0000000
0x0000000 0x0000000 0x0000000 0x0000000 0x0000000 0x0000000
0x0000000 0x0000000 0x0000000 0x0000000 0x0000000 0x0000000
0x0000000 0x0000000 0x0000000 0x0000000 0x0000000 0x0000000
0x0000000 0x0000000 0x0000000 0x0000000 0x0000000 0x0000000
Channel state: UP Channel IDB: 61A98D00
RX ring entries: 17, buffer size 1524
RX descriptor ring: head = 40341780, tail = 40341870
RX pak ring: head = 61D037EC, tail = 61D03864
00 params=0x25F40000 status=0x80000000 data ptr=0x40274E60 next ptr=0x40341790
01 params=0x25F40000 status=0x80000000 data ptr=0x4027551C next ptr=0x403417A0
02 params=0x25F40000 status=0x80000000 data ptr=0x40275BD8 next ptr=0x403417B0
03 params=0x25F40000 status=0x80000000 data ptr=0x40276294 next ptr=0x403417C0
04 params=0x25F40000 status=0x80000000 data ptr=0x40276950 next ptr=0x403417D0
05 params=0x25F40000 status=0x80000000 data ptr=0x4027700C next ptr=0x403417E0
06 params=0x25F40000 status=0x80000000 data ptr=0x402776C8 next ptr=0x403417F0
07 params=0x25F40000 status=0x80000000 data ptr=0x40277D84 next ptr=0x40341800
08 params=0x25F40000 status=0x80000000 data ptr=0x40278440 next ptr=0x40341810
09 params=0x25F40000 status=0x80000000 data ptr=0x40278AFC next ptr=0x40341820
10 params=0x25F40000 status=0x80000000 data ptr=0x402791B8 next ptr=0x40341830
11 params=0x25F40000 status=0x80000000 data ptr=0x40279874 next ptr=0x40341840
12 params=0x25F40000 status=0x80000000 data ptr=0x40279F30 next ptr=0x40341850
13 params=0x25F40000 status=0x80000000 data ptr=0x4027A5EC next ptr=0x40341860
14 params=0x25F40000 status=0x80000000 data ptr=0x4027ACA8 next ptr=0x40341870
15 params=0x65F40000 status=0x80000000 data ptr=0x4027B364 next ptr=0x40341880
16 params=0x25F40000 status=0x80000000 data ptr=0x4027BA20 next ptr=0x40341780
TX ring entries: 3, in use: 0, buffer size 1524
TX descriptor ring: head = 40083F0C, tail = 40083F0C
TX pak ring: head = 6190D110, tail = 6190D110
00 params=0xE0000000 data ptr=0x40264C28 next ptr=0x40083F18
01 params=0xA0000000 data ptr=0x40264C28 next ptr=0x40083F24
02 params=0xA0000000 data ptr=0x40264C28 next ptr=0x40083F0C
List of timeslots (sw): 0
List of all timeslots (hw):
00:00FF00FF 01:01FF01FF 02:02C002C0 03:03FF03FF 04:04FF04FF 05:05C005C0
06:06FF06FF 07:07FF07FF 08:08C008C0 09:09FF09FF 10:0AFF0AFF 11:0BC00BC0
12:20002000 13:20002000 14:20002000 15:20002000 16:20002000 17:20002000
18:20002000 19:20002000 20:20002000 21:20002000 22:20002000 23:20002000
24:20002000 25:20002000 26:20002000 27:20002000 28:20002000 29:20002000
30:20002000 31:20002000
Bandwidth: 64, idle channel: Unassigned, idle ts bitfield: 0x0
0 missed datagrams, 1 overruns
0 bad datagram encapsulations, 0 memory errors
0 transmitter underruns, 0 throttles, 0 enables, 0 bad interrupt elements
B2 Channel Information:
Interrupt Queue Element(index=676): interrupt is enabled
0x0000000 0x0000000 0x0000000 0x0000000 0x0000000 0x0000000
0x0000000 0x0000000 0x0000000 0x0000000 0x0000000 0x0000000
0x0000000 0x0000000 0x0000000 0x0000000 0x0000000 0x0000000
0x0000000 0x0000000 0x0000000 0x0000000 0x0000000 0x0000000
0x0000000 0x0000000 0x0000000 0x0000000 0x0000000 0x0000000
Channel state: UP Channel IDB: 61A9C864
RX ring entries: 17, buffer size 1524
RX descriptor ring: head = 40059BD0, tail = 40059CC0
RX pak ring: head = 61C670DC, tail = 61C67154
00 params=0x25F40000 status=0x80000000 data ptr=0x402891A0 next ptr=0x40059BE0
01 params=0x25F40000 status=0x80000000 data ptr=0x4028985C next ptr=0x40059BF0
02 params=0x25F40000 status=0x80000000 data ptr=0x40289F18 next ptr=0x40059C00
03 params=0x25F40000 status=0x80000000 data ptr=0x4028A5D4 next ptr=0x40059C10
04 params=0x25F40000 status=0x80000000 data ptr=0x4028AC90 next ptr=0x40059C20
05 params=0x25F40000 status=0x80000000 data ptr=0x4028B34C next ptr=0x40059C30
06 params=0x25F40000 status=0x80000000 data ptr=0x4028BA08 next ptr=0x40059C40
07 params=0x25F40000 status=0x80000000 data ptr=0x4028C0C4 next ptr=0x40059C50
08 params=0x25F40000 status=0x80000000 data ptr=0x4028C780 next ptr=0x40059C60
09 params=0x25F40000 status=0x80000000 data ptr=0x4028CE3C next ptr=0x40059C70
10 params=0x25F40000 status=0x80000000 data ptr=0x4028D4F8 next ptr=0x40059C80
11 params=0x25F40000 status=0x80000000 data ptr=0x4028DBB4 next ptr=0x40059C90
12 params=0x25F40000 status=0x80000000 data ptr=0x4028E270 next ptr=0x40059CA0
13 params=0x25F40000 status=0x80000000 data ptr=0x4028E92C next ptr=0x40059CB0
14 params=0x25F40000 status=0x80000000 data ptr=0x4028EFE8 next ptr=0x40059CC0
15 params=0x65F40000 status=0x80000000 data ptr=0x4028F6A4 next ptr=0x40059CD0
16 params=0x25F40000 status=0x80000000 data ptr=0x4028FD60 next ptr=0x40059BD0
TX ring entries: 3, in use: 0, buffer size 1524
TX descriptor ring: head = 40083F5C, tail = 40083F5C
TX pak ring: head = 61AC0528, tail = 61AC0528
00 params=0xE0000000 data ptr=0x40264C28 next ptr=0x40083F68
01 params=0xA0000000 data ptr=0x40264C28 next ptr=0x40083F74
02 params=0xA0000000 data ptr=0x40264C28 next ptr=0x40083F5C
List of timeslots (sw): 1
List of all timeslots (hw):
00:00FF00FF 01:01FF01FF 02:02C002C0 03:03FF03FF 04:04FF04FF 05:05C005C0
06:06FF06FF 07:07FF07FF 08:08C008C0 09:09FF09FF 10:0AFF0AFF 11:0BC00BC0
12:20002000 13:20002000 14:20002000 15:20002000 16:20002000 17:20002000
18:20002000 19:20002000 20:20002000 21:20002000 22:20002000 23:20002000
24:20002000 25:20002000 26:20002000 27:20002000 28:20002000 29:20002000
30:20002000 31:20002000
Bandwidth: 64, idle channel: Unassigned, idle ts bitfield: 0x0
0 missed datagrams, 0 overruns
0 bad datagram encapsulations, 0 memory errors
0 transmitter underruns, 0 throttles, 0 enables, 0 bad interrupt elements
Figure 13.
p1r1#
2d23h:
2d23h:
2d23h:
2d23h:
2d23h:
2d23h:
2d23h:
2d23h:
p1r1#
2d23h:
2d23h:
p1r1#
2d23h:
2d23h:
2d23h:
2d23h:
2d23h:
2d23h:
p1r1#
2d23h:
p1r1#
2d23h:
ISDN
ISDN
ISDN
ISDN
ISDN
ISDN
ISDN
ISDN
'show controllers bri 0' output for a working BRI interface
BR0: EI2 Received when IF is DOWN - Error
BR0: L1 is IF_ACTIVE
BR0 EVENT: isdn_sw_cstate: State = 4, Old State = 4
BR0: L2-TERM: ces/tei=1/64 INIT->TERM_DOWN
BR0: L2-TERM: ces/tei=2/65 usid/tid=112/2 INIT->TERM_DOWN
BR0: Incoming call id = 0x0006, dsl 0
BR0: L2-TERM: ces/tei=1/64 TERM_DOWN->AWAIT_ESTABLISH
BR0: TX -> SABMEp c/r=0 sapi=0 tei=64
ISDN BR0: TX -> SABMEp c/r=0 sapi=0 tei=64
ISDN BR0: TX -> SABMEp c/r=0 sapi=0 tei=64
ISDN BR0: TX -> SABMEp c/r=0 sapi=0 tei=64
%ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0, TEI 64 changed to down
ISDN BR0: LIF_EVENT: ces/callid 1/0x0 HOST_DISCONNECT_ACK
ISDN: get_isdn_service_state(): idb 0x619CE8A4 bchan 2 is_isdn 1 Not a Pri
ISDN BR0: HOST_DISCONNECT_ACK: call type is INTERNAL
ISDN BR0: TX -> IDVER ri=0 ai=64
ISDN BR0: TX -> IDVER ri=0 ai=64
ISDN BR0: TX -> IDVER ri=0 ai=64
2d23h: ISDN BR0: RX <- IDCKRQ ri=0 ai=64
2d23h: ISDN BR0: TX -> IDCKRP ri=11550 ai=64
p1r1#
2d23h: ISDN BR0: RX <- IDCKRQ ri=0 ai=64
2d23h: ISDN BR0: TX -> IDCKRP ri=65279 ai=64
p1r1#
2d23h: ISDN BR0: RX <- IDREM ri=0 ai=64
2d23h: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BRI0, TEI 64 changed to down
2d23h: ISDN BR0: L2-TERM: ces/tei=1/64 AWAIT_ESTABLISH->TERM_DOWN
2d23h: ISDN BR0: Incoming call id = 0x0007, dsl 0
2d23h: ISDN BR0: L2-TERM: ces/tei=1/0 TERM_DOWN->AWAIT_ESTABLISH
2d23h: ISDN BR0: TX -> IDREQ ri=61168 ai=127
2d23h: ISDN BR0: RX <- IDASSN ri=61168 ai=64
2d23h: ISDN BR0: TX -> SABMEp c/r=0 sapi=0 tei=64
2d23h: ISDN BR0: RX <- UAf c/r=0 sapi=0 tei=64
2d23h: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0, TEI 64 changed to up
2d23h: ISDN BR0: L2-TERM: ces/tei=1/64 AWAIT_ESTABLISH->ESTABLISHED
2d23h: ISDN BR0: L2-TERM: ces/tei=1/64 ESTABLISHED->AWAIT_INIT
2d23h: ISDN BR0: TX -> INFOc sapi=0 tei=64 ns=0 nr=0
i=0x08007B3A0E3530333535353031303030313031
2d23h:
INFORMATION pd = 8 callref = (null)
SPID Information i = '50355501000101'
2d23h: ISDN BR0: RX <- RRr sapi=0 tei=64 nr=1
x08007B3B02F081: RX <- INFOc sapi=0 tei=64 ns=0 nr=1 i=0
2d23h:
INFORMATION pd = 8 callref = (null)
ENDPOINT IDent i = 0xF081
2d23h: ISDN BR0: TX -> RRr sapi=0 tei=64 nr=1
2d23h: CCBRI_Go Fr L3 pkt (Len=7) :
2d23h: 7B 0 93 3B 2 F0 81
2d23h:
2d23h: ISDN BR0: L2-TERM: ces/tei=1/64 usid/tid=112/1 AWAIT_INIT->INIT
2d23h: ISDN BR0: Received EndPoint ID
2d23h: ISDN BR0: Incoming call id = 0x0008, dsl 0
2d23h: ISDN BR0: L2-TERM: ces/tei=2/65 usid/tid=112/2 TERM_DOWN->AWAIT_ESTABLISH
2d23h: ISDN BR0: TX -> SABMEp c/r=0 sapi=0 tei=65
2d23h: ISDN BR0: TX -> SABMEp c/r=0 sapi=0 tei=65
p1r1#
p1r1#
2d23h: ISDN BR0: TX -> SABMEp c/r=0 sapi=0 tei=65
2d23h: ISDN BR0: TX -> SABMEp c/r=0 sapi=0 tei=65
p1r1#
2d23h: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0, TEI 65 changed to down
p1r1#
2d23h: ISDN BR0: LIF_EVENT: ces/callid 2/0x0 HOST_DISCONNECT_ACK
2d23h: ISDN: get_isdn_service_state(): idb 0x619CE8A4 bchan 2 is_isdn 1 Not a Pri
2d23h: ISDN BR0: HOST_DISCONNECT_ACK: call type is INTERNAL
2d23h: ISDN BR0: TX -> IDVER ri=0 ai=65
p1r1#
2d23h: ISDN BR0: TX -> IDVER ri=0 ai=65
2d23h: ISDN BR0: RX <- IDCKRQ ri=0 ai=65
2d23h: ISDN BR0: TX -> IDCKRP ri=56817 ai=65
p1r1#
2d23h: ISDN BR0: RX <- IDCKRQ ri=0 ai=65
2d23h: ISDN BR0: TX -> IDCKRP ri=48386 ai=65
p1r1#
2d23h: ISDN BR0: RX <- IDREM ri=0 ai=65
2d23h: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BRI0, TEI 65 changed to down
2d23h: ISDN BR0: Incoming call id = 0x0009, dsl 0
2d23h: ISDN BR0: RX <- RRp sapi=0 tei=64 nr=1
2d23h: ISDN BR0: TX -> RRf sapi=0 tei=64 nr=1
2d23h: ISDN BR0: TX -> IDREQ ri=36131 ai=127
2d23h: ISDN BR0: RX <- IDASSN ri=36131 ai=65
2d23h: ISDN BR0: TX -> SABMEp c/r=0 sapi=0 tei=65
2d23h: ISDN BR0: RX <- UAf c/r=0 sapi=0 tei=65
2d23h: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0, TEI 65 changed to up
2d23h: ISDN BR0: L2-TERM: ces/tei=2/65 AWAIT_ESTABLISH->ESTABLISHED
2d23h: ISDN BR0: L2-TERM: ces/tei=2/65 ESTABLISHED->AWAIT_INIT
2d23h: ISDN BR0: TX -> INFOc sapi=0 tei=65 ns=0 nr=0
i=0x08007B3A0E3530333535353031303130313031
2d23h:
INFORMATION pd = 8 callref = (null)
SPID Information i = '50355501010101'
2d23h: ISDN BR0: RX <- RRr sapi=0 tei=65 nr=1
2d23h: ISDN BR0: RX <- INFOc sapi=0 tei=65 ns=0 nr=1 i=0x08007B3B02F082
pd = 8 callref = (null)
ENDPOINT IDent i = 0xF082
2d23h: ISDN BR0: TX -> RRr sapi=0 tei=65 nr=1
2d23h: CCBRI_Go Fr L3 pkt (Len=7) :
2d23h: 7B 0 93 3B 2 F0 82
2d23h:
2d23h: ISDN BR0: L2-TERM: ces/tei=2/65 usid/tid=112/2 AWAIT_INIT->INIT
2d23h: ISDN BR0: Received EndPoint ID
p1r1#
p1r1#
2d23h: ISDN BR0: RX <- RRp sapi=0 tei=64 nr=1
2d23h: ISDN BR0: TX -> RRf sapi=0 tei=64 nr=1
2d23h: ISDN BR0: RX <- RRp sapi=0 tei=65 nr=1
2d23h: ISDN BR0: TX -> RRf sapi=0 tei=65 nr=1
p1r1#
2d23h: ISDN BR0: RX <- RRp sapi=0 tei=64 nr=1
2d23h: ISDN BR0: TX -> RRf sapi=0 tei=64 nr=1
2d23h: ISDN BR0: RX <- RRp sapi=0 tei=65 nr=1
2d23h: ISDN BR0: TX -> RRf sapi=0 tei=65 nr=1
p1r1#
2d23h: ISDN BR0: RX <- RRp sapi=0 tei=64 nr=1
2d23h: ISDN BR0: TX -> RRf sapi=0 tei=64 nr=1
2d23h: ISDN BR0: RX <- RRp sapi=0 tei=65 nr=1
2d23h: ISDN BR0: TX -> RRf sapi=0 tei=65 nr=1
p1r1#
2d23h: ISDN BR0: RX <- RRp sapi=0 tei=64 nr=1
2d23h: ISDN BR0: TX -> RRf sapi=0 tei=64 nr=1
2d23h: ISDN BR0: RX <- RRp sapi=0 tei=65 nr=1
2d23h: ISDN BR0: TX -> RRf sapi=0 tei=65 nr=1
p1r1#
2d23h: ISDN BR0: RX <- RRp sapi=0 tei=64 nr=1
2d23h: ISDN BR0: TX -> RRf sapi=0 tei=64 nr=1
2d23h: ISDN BR0: RX <- RRp sapi=0 tei=65 nr=1
2d23h: ISDN BR0: TX -> RRf sapi=0 tei=65 nr=1
Figure 14.
Debug output for ISDN BRI link coming up successfully
ISDN BRI LAYER 1 TROUBLESHOOTING NOTES
With an external NT1 unit between the connection of the ISDN
terminal equipment (router) and ISDN switch, a common layer 1 problem
is improper cabling. As indicated before, the cabling from the router
to the S/T port of the NT1 unit, and from the network port of the NT1
unit to the U interface of the ISDN switch, must be a straight-through
twisted-pair cable. Thus, a bad cable can exist in one of two places
in the path. When there is a layer 1 problem, 'show isdn status' will
show a layer 1 status of "DEACTIVATED."
The key to troubleshooting these issues is interpreting the L1
state of the BRI interface from the 'show controllers' command and the
state of the LEDs on the NT1 unit. When the layer 1 connection is OK,
'show isdn status' will show a layer 1 status of "ACTIVE," and 'show
controllers bri N' indicates the ISDN L1 state is F7.
PROBLEM:
Bad cable between NT1 and router (S/T connection).
OBSERVATIONS: The NT1 unit shows ERROR LED lit red, and the READY LED
blinking green. 'show controllers bri N' indicates the ISDN L1 state
is F3.
PROBLEM:
Bad cable between NT1 and ISDN switch (U connection).
OBSERVATIONS: The NT1 unit shows ERROR LED lit red, and the READY LED
off (unlit). 'show controllers bri N' indicates the ISDN L1 state is
F2.
PROBLEM:
Both cables are bad in path from router to ISDN switch.
OBSERVATIONS: The NT1 unit shows ERROR LED lit red, and the READY LED
off (unlit). 'show controllers bri N' indicates the ISDN L1 state is
F2.
See Also:
- http://www.cisco.com/warp/public/129/bri-layer1.html
- Section 6.2 of ITU-T I.430 specification
(http://www.mit.edu/afs/net.mit.edu/reference/ccitt/1988/ascii/3_8_05.txt)
MISCELLANEOUS ISDN BRI NOTES
1. SPID is a number assigned to an initializing ISDN terminal
equipment, which enables the Stored Program Control Switching System
(SPCS) to uniquely identify the ISDN TE at layer 3 of the D-channel
signaling protocol (Q.931).
2. For National ISDN switches, the SPID is often of the form
NPANXXXXXX0101; NPA is the local area code, and NXX is the access
number.
3. LDN stands for local directory number. Although not necessary for
establishing ISDN connections, it must be specified if 1) you want to
receive incoming calls on the second B channel, or 2) if two SPIDs are
configured. If the LDN is not configured, incoming calls to the second
B channel may fail.
4. Although a BRI interface can use PPP or HDLC encapsulation, the main
reason why PPP is often used is because HDLC cannot use both B channels
simultaneously. With HDLC, both B channels will come up, but one
channel must be used for sending traffic and the other for receiving
traffic. Thus, with HDLC, the BRI link operates at half duplex. Since
each B channel has the capability of providing full duplex
transmission, HDLC encapsulation essentially cuts the possible data
rate in half.
5. A third type of ISDN channel is the H channel. The H channel
provides a way to bond multiple B channels; this is not normally used
in North America. H channels implemented:
* H0 - 384 kbps (6 B channels)
[ I have seen this used at a Schenectady office ]
* H10 - 1.472 Mbps (23 B channels)
* H11 - 1.536 Mbps (24 B channels)
* H12 - 1.92 Mbps (30 B channels)
* H4 - 150 Mbps (~2343 B channels)