From: Sharma, Mohit (mohit.sharma@hp.com)
Date: Thu May 13 2004 - 14:54:26 GMT-3
HI Sam,
I didn't include the dialer list config as from the debug it was clear
that he dialer list is fine, but for clarity here it is -
dialer-list 1 protocol clns_is permit
dialer-list 1 protocol clns_es permit
dialer-list 1 protocol clns permit
Actually only the first statement is needed but I just wanted to make
sure and since the dialing occurs normally I ruled out the dialer-list.
Thanks,
Mohit.
-----Original Message-----
From: samccie2004@yahoo.co.uk [mailto:samccie2004@yahoo.co.uk]
Sent: Thursday, May 13, 2004 7:48 PM
To: Sharma, Mohit; ccielab@groupstudy.com
Subject: RE: ISIS over ISDN
Sorry if I missed something, but how about ur dialer-list is it waiting
for IP or CLN-is ?
Sam
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Sharma, Mohit
Sent: 13 May 2004 19:09
To: ccielab@groupstudy.com
Subject: ISIS over ISDN
Hello All,
I am trying a lab to configure ISIS over ISDN, but whatever I do I am
not able to bring up the adjacency for the two routers. The ISDN dials
without any problems but the router R5 (below) is giving encapsulation
failure in spite of the dialer map and the dialer list statements.-
Rack1R5#interface BRI0
ip address 132.1.45.5 255.255.255.248
ip router isis
encapsulation ppp
dialer map clns 49.0044.0001.0001.0004.00 name ROUTER4 broadcast 237340
dialer-group 1 isdn switch-type basic-net3 ppp callback request ppp
chap hostname ROUTER5 clns router isis End
The debug-
01:28:44: BR0 DDR: clns_is, 1499 bytes, outgoing interesting (clns_is
PERMIT)
01:28:44: BR0 DDR: sending broadcast to clns 49.0044.0001.0001.0004.00
-- failed, not connected
01:28:44: ISIS-Adj: Encapsulation failed on serial IIH (BRI0)
Rack1R5(config)#
01:28:45: %ISDN-6-CONNECT: Interface BRI0:2 is now connected to unknown
Rack1R5(config)#
01:28:51: ISIS-Adj: Rec serial IIH from *PPP* (BRI0), cir type L2, cir
id 00, length 1499
01:28:51: ISIS-Adj: rcvd state DOWN, old state INIT, new state INIT
01:28:51: ISIS-Adj: Action = GOING UP, new type = L2 Rack1R5(config)#^Z
Rack1R5#u
01:28:54: BR0 DDR: clns_is, 1499 bytes, outgoing interesting (clns_is
PERMIT)
01:28:54: BR0 DDR: sending broadcast to clns 49.0044.0001.0001.0004.00
-- failed, not connected
01:28:54: ISIS-Adj: Encapsulation failed on serial IIH (BRI0)
As you can see from the debug above ISDN works fine and this router also
reciever IIH on the Bri port and also consider isis as interesting but
still somehow gives the enacp failure. The config for other side is -
ack1R4# sh run int bri 0 Building configuration...
Current configuration : 342 bytes
!
interface BRI0
ip address 132.1.45.4 255.255.255.248
ip router isis
encapsulation ppp
dialer idle-timeout 0
dialer map clns 49.0035.0001.0001.0005.00 name ROUTER5 class dial
broadcast 230897 isdn switch-type basic-net3 ppp callback accept ppp
authentication chap ppp chap hostname ROUTER4 ppp chap refuse clns
router isis End
Would really appreciate if someone can point me in the right direction.
Many Thanks,
Mohit.
This archive was generated by hypermail 2.1.4 : Wed Jun 02 2004 - 11:12:11 GMT-3