From: Jonathan Hays (nomad@gfoyle.org)
Date: Fri Mar 19 2004 - 21:16:28 GMT-3
you wrote:
>-----Original Message-----
>From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On
>Behalf Of Packet Man
>Sent: Friday, March 19, 2004 5:37 PM
>To: alsontra@hotmail.com; ccielab@groupstudy.com
>Subject: Re: Lab Tips - ISDN
>
>
>Hey Alsontra,
>
>That's a GREAT tip. I wasn't even aware of those commands.
>sounds like
>they can be very useful. But, what the difference and benefit
>between using
>this method and using the old method (pinging the remote BRI
>interface)?
>
= = =
Packet Man,
I must admonish you for sleeping in class. ;-) I see many posts in the
GS archives on this subject, some dated over a year ago.
Until recently you could use 'isdn call interface' and 'disconnect' but
more recent versions of the IOS warn that you had better add 'test'
because the old syntax is going away.
The 'isdn test call interface' command can be used to test the
connection as soon as the router has completed its basic connection to
the ISDN switch. You don't need an ip address, PPP, dialer maps,
interesting traffic, or any of that jazz configured to successfully
execute the command and verify the ISDN link is working through the
switch.
I don't consider it all that useful for the CCIE lab exam, with one
exception (see below). I think of this command as a more useful to those
new to ISDN, or those who are extremetly conservative about building up
their ISDN configuration in a new, unfamiliar WAN environment.
A very careful, incremental ISDN configuration might be built up by
first configuring switch type and SPIDs on both sides. Then verifying
they are valid ('sh isdn status'). And then using the 'isdn test call
interface' command to verify the link and switch operation. Then you can
add an ip address, and dialer maps, dialer-lists and try pinging. Then
the authentication or callback, etc.
But IMHO, once you have practiced ISDN for hours and hours, know most of
the ins and out, and are close to passing the CCIE lab you probably
won't want to bother with this command, especially in your home lab. You
will probably just configure everything all at once, using your debug
knowledge to isolate minor problems in minutes.
Now on the lab exam, with the added tension and stress, if you throw in
a basic ppp config and can't get it to ping, it might be worth falling
back to 'isdn test call interface' to verify the ISDN switch and link
are working and that it's just your nervousness and mucked up config
that are at fault.
Here's an example from my notes on the use of 'isdn test caller
interface'.
R2#
R2#sh run int bri1/0
Building configuration...
Current configuration : 132 bytes
!
interface BRI1/0
no ip address
encapsulation hdlc
isdn switch-type basic-ni
isdn spid1 0835866201
isdn spid2 0835866401
end
R2#sh isdn active
------------------------------------------------------------------------
--------
ISDN ACTIVE CALLS
------------------------------------------------------------------------
--------
Call Calling Called Remote Seconds Seconds Seconds
Charges
Type Number Number Name Used Left Idle
Units/Currency
------------------------------------------------------------------------
--------
------------------------------------------------------------------------
--------
R2#sh isdn status
Global ISDN Switchtype = basic-ni
ISDN BRI1/0 interface
dsl 0, interface ISDN Switchtype = basic-ni
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 121, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
TEI = 122, Ces = 2, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
TEI 121, ces = 1, state = 8(established)
spid1 configured, no LDN, spid1 sent, spid1 valid
Endpoint ID Info: epsf = 0, usid = 2, tid = 1
TEI 122, ces = 2, state = 8(established)
spid2 configured, no LDN, spid2 sent, spid2 valid
Endpoint ID Info: epsf = 0, usid = 4, tid = 1
Layer 3 Status:
0 Active Layer 3 Call(s)
Active dsl 0 CCBs = 0
The Free Channel Mask: 0x80000003
ISDN BRI1/1 interface
dsl 1, interface ISDN Switchtype = basic-ni
Layer 1 Status:
DEACTIVATED
Layer 2 Status:
Layer 2 NOT Activated
Layer 3 Status:
0 Active Layer 3 Call(s)
Active dsl 1 CCBs = 0
The Free Channel Mask: 0x00000000
Total Allocated ISDN CCBs = 0
R2#
Tserver>5
[Resuming connection 5 to r5_3620 ... ]
[OK]
R5#
R5#sh run int bri1/0
Building configuration...
Current configuration : 132 bytes
!
interface BRI1/0
no ip address
encapsulation hdlc
isdn switch-type basic-ni
isdn spid1 0835866101
isdn spid2 0835866301
end
R5#sh isdn active
------------------------------------------------------------------------
--------
ISDN ACTIVE CALLS
------------------------------------------------------------------------
--------
Call Calling Called Remote Seconds Seconds Seconds
Charges
Type Number Number Name Used Left Idle
Units/Currency
------------------------------------------------------------------------
--------
------------------------------------------------------------------------
--------
R5#sh isdn status
Global ISDN Switchtype = basic-ni
ISDN BRI1/0 interface
dsl 8, interface ISDN Switchtype = basic-ni
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 119, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
TEI = 120, Ces = 2, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
TEI 119, ces = 1, state = 8(established)
spid1 configured, no LDN, spid1 sent, spid1 valid
Endpoint ID Info: epsf = 0, usid = 1, tid = 1
TEI 120, ces = 2, state = 8(established)
spid2 configured, no LDN, spid2 sent, spid2 valid
Endpoint ID Info: epsf = 0, usid = 3, tid = 1
Layer 3 Status:
0 Active Layer 3 Call(s)
Active dsl 8 CCBs = 0
The Free Channel Mask: 0x80000003
Total Allocated ISDN CCBs = 0
R5#
Tserver>2
[Resuming connection 2 to r6_2620 ... ]
R2#isdn test call interface bri1/0 8358662
R2#
*Apr 5 03:38:24.794: %LINK-3-UPDOWN: Interface BRI1/0:2, changed state
to up
*Apr 5 03:38:24.958: %LINK-3-UPDOWN: Interface BRI1/0:1, changed state
to up
*Apr 5 03:38:25.798: %LINEPROTO-5-UPDOWN: Line protocol on Interface
BRI1/0:2, changed state to up
R2#
*Apr 5 03:38:25.962: %LINEPROTO-5-UPDOWN: Line protocol on Interface
BRI1/0:1, changed state to up
R2#sh isdn acti
*Apr 5 03:38:30.798: %ISDN-6-CONNECT: Interface BRI1/0:2 is now
connected to unknown
*Apr 5 03:38:30.958: %ISDN-6-CONNECT: Interface BRI1/0:1 is now
connected to 8358662
R2#sh isdn active
------------------------------------------------------------------------
--------
ISDN ACTIVE CALLS
------------------------------------------------------------------------
--------
Call Calling Called Remote Seconds Seconds Seconds
Charges
Type Number Number Name Used Left Idle
Units/Currency
------------------------------------------------------------------------
--------
In ---N/A--- 8358662 8 111 8
Out ---N/A--- 8358662 7 112 7 0
------------------------------------------------------------------------
--------
R2#sh isdn status
Global ISDN Switchtype = basic-ni
ISDN BRI1/0 interface
dsl 0, interface ISDN Switchtype = basic-ni
Layer 1 Status:
ACTIVE
Layer 2 Status:
TEI = 121, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
TEI = 122, Ces = 2, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED
TEI 121, ces = 1, state = 8(established)
spid1 configured, no LDN, spid1 sent, spid1 valid
Endpoint ID Info: epsf = 0, usid = 2, tid = 1
TEI 122, ces = 2, state = 8(established)
spid2 configured, no LDN, spid2 sent, spid2 valid
Endpoint ID Info: epsf = 0, usid = 4, tid = 1
Layer 3 Status:
2 Active Layer 3 Call(s)
CCB:callid=8002, sapi=0, ces=1, B-chan=1, calltype=DATA
CCB:callid=37, sapi=0, ces=1, B-chan=2, calltype=DATA
Active dsl 0 CCBs = 2
The Free Channel Mask: 0x80000000
ISDN BRI1/1 interface
dsl 1, interface ISDN Switchtype = basic-ni
Layer 1 Status:
DEACTIVATED
Layer 2 Status:
Layer 2 NOT Activated
Layer 3 Status:
0 Active Layer 3 Call(s)
Active dsl 1 CCBs = 0
The Free Channel Mask: 0x00000000
Total Allocated ISDN CCBs = 2
R2#isdn test disconnect interface bri1/0 all
R2#
*Apr 5 03:38:59.994: %ISDN-6-DISCONNECT: Interface BRI1/0:1
disconnected from 8358662 , call lasted 35 seconds
*Apr 5 03:38:59.994: %ISDN-6-DISCONNECT: Interface BRI1/0:2
disconnected from unknown , call lasted 35 seconds
R2#
*Apr 5 03:39:00.090: %LINK-3-UPDOWN: Interface BRI1/0:1, changed state
to down
*Apr 5 03:39:00.162: %LINK-3-UPDOWN: Interface BRI1/0:2, changed state
to down
*Apr 5 03:39:01.090: %LINEPROTO-5-UPDOWN: Line protocol on Interface
BRI1/0:1, changed state to down
R2#
*Apr 5 03:39:01.162: %LINEPROTO-5-UPDOWN: Line protocol on Interface
BRI1/0:2, changed state to down
R2#
HTH,
Jonathan
This archive was generated by hypermail 2.1.4 : Thu Apr 01 2004 - 08:15:39 GMT-3