From: Sean C (Upp_and_Upp@hotmail.com)
Date: Sun May 15 2005 - 16:40:24 GMT-3
Hi Long,
Unfortunately, I don't have the lab in front of me, so I'm not sure of the
requirements. But I see that you have router4 set as a level-2 only, is
router5 set similarly? Also, the configs posted are missing some items, but
I'll assume you've configured usernames and pws on both routes, the callback
map-class, as well as define the isis routing process and net statement on
each router. From just eyeballing the config and assuming what I mentioned
above, you can always troubleshoot down to the basics and work your way up.
Strip off the callback features and just see if you can get a straight CLNS
neighbor relationship when R5 calls R4. Have you tried any debug clns
commands? I'm assuming IP pings work when the call is up. To answer your
original question, if everything is configured properly and assuming no IOS
bugs etc..., yes, I believe should see clns neighbors over ISDN.
HTH,
Sean
----- Original Message -----
From: "Long Kwok" <lkwok@ccieunix.com>
To: "Sean C" <Upp_and_Upp@hotmail.com>; <ccielab@groupstudy.com>
Sent: Sunday, May 15, 2005 3:14 PM
Subject: RE: ISIS Adjacency formation over ISDN IE lab 2
> Sure Sean here is config as it sits now
>
> TIA , Long
>
>
> Rack1R4#show run int bri0/0
> Building configuration...
>
> Current configuration : 417 bytes
> !
> interface BRI0/0
> 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 CALL
> broadcast 5272015
> dialer map ip 132.1.45.5 name ROUTER5 class CALL 5272015
> isdn switch-type basic-ni
> isdn spid1 5272014
> ppp callback accept
> ppp authentication chap
> ppp chap hostname ROUTER4
> isis circuit-type level-2-only
> end
>
> Rack1R4#
> Rack1R4#
>
>
>
> Rack1R5#show run int bri0/0
> Building configuration...
>
> Current configuration : 332 bytes
> !
> interface BRI0/0
> 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
> 5272014
> dialer map ip 132.1.45.4 name ROUTER4 5272014
> dialer-group 1
> isdn switch-type basic-ni
> isdn spid1 5272015
> ppp callback request
> ppp chap hostname ROUTER5
> end
>
> Rack1R5#
>
> Dialer-list 1 protocol clns_is permit
>
> -----Original Message-----
> From: Sean C [mailto:Upp_and_Upp@hotmail.com]
> Sent: Sunday, May 15, 2005 12:03 PM
> To: ccielab@groupstudy.com
> Subject: Re: ISIS Adjacency formation over ISDN IE lab 2
>
> Hi Long,
>
> You mention that ISIS is configured properly both globally and at the
> BRI
> int level. Does this include defining clns in a dialer map? That one
> always used to get me until I beat it in my brain. If you're having
> trouble, can you post your configs?
> Sean
> ----- Original Message -----
> From: "Long Kwok" <lkwok@ccieunix.com>
> To: <ccielab@groupstudy.com>
> Sent: Sunday, May 15, 2005 2:32 PM
> Subject: ISIS Adjacency formation over ISDN IE lab 2
>
>
>> Hi, in IE lab 2 there is a DDR problem discussing clns_is for the
> only
>> protocol to bring up the isdn circuit from R5's side , so when this
>> isdn circuit is up , would you expect to be able to issue a "show clns
>> neigh" command and see a isis adjacency , assuming that all isis is
>> configured properly both globally and at the bri interface level ? As
>> when isdn is up I do not see an isis adjacency forming ??
>>
>>
>>
>> TIA , Long
>>
>>
> _______________________________________________________________________
>> Subscription information may be found at:
>> http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
This archive was generated by hypermail 2.1.4 : Fri Jun 03 2005 - 10:11:58 GMT-3