From: Richard Dumoulin (richard.dumoulin@vanco.es)
Date: Thu May 13 2004 - 16:25:09 GMT-3
Why not use pap ? With pap no challenges are done. Just a suggestion.
-----Original Message-----
From: Sharma, Mohit [mailto:mohit.sharma@hp.com]
Sent: jueves, 13 de mayo de 2004 21:06
To: MMoniz; ccielab@groupstudy.com
Subject: RE: ISIS over ISDN
Hi Mike,
I have no issues with ISDN, callback is working fine.
The problem is that even with ISDN up and running I get an IIH encapsulation
failure.
Actually this is a task from the IE workbook and the authors wanted this to
run with this setup including making R5 not to authenticate. This is where
the issue lies. As if I give ppp authentication chap on both routers
everything works fine.
But when I remove the ppp authentication chap command from R5(to fulfill the
criteria), somehow the ISIS adjacency is also effected and never comes up.
Maybe the authors of the lab would find something.
Smiles,
Mohit.
-----Original Message-----
From: MMoniz [mailto:ccie2002@tampabay.rr.cm]
Sent: Thursday, May 13, 2004 8:41 PM
To: Sharma, Mohit; samccie2004@yahoo.co.uk; ccielab@groupstudy.com
Subject: RE: ISIS over ISDN
Mohit, I noticed in your first post you were doing callback request, is that
actually working?
I would try removing all but the necessary things to make it work and then
add the other stuff. I was just going over this the other day as well. Here
is a copy of my working config from one of the routers. MAybe you can spot
something that is missing
R5
interface BRI0/0
ip address 133.5.53.5 255.255.255.0
ip router isis
encapsulation ppp
dialer idle-timeout 60
dialer map clns 49.0005.7777.0000.0000.00 name ATM broadcast 5551414 dialer
map clns 49.0005.7777.0000.0000.00 name ATM broadcast 5551515 dialer map ip
133.5.53.7 name ATM broadcast 5551414 dialer map ip 133.5.53.7 name ATM
broadcast 5551515 dialer load-threshold 128 either dialer-group 1 isdn
switch-type basic-ni isdn spid1 55512120101 isdn spid2 55513130101 no
peer neighbor-route ppp multilink isis circuit-type level-1 isis
hello-interval 1800
dialer-list 1 protocol clns_is permit
dialer-list 1 protocol ip permit
R5#sho isis top
IS-IS IP paths to level-1 routers
System Id Metric Next-Hop Interface SNPA
R5 --
ATM 10 ATM BR0/0 *PPP*
IS-IS IP paths to level-2 routers
System Id Metric Next-Hop Interface SNPA
R5 --
ATM **
R5#
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
Sharma, Mohit
Sent: Thursday, May 13, 2004 1:54 PM
To: samccie2004@yahoo.co.uk; ccielab@groupstudy.com
Subject: RE: ISIS over ISDN
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