From: Lab Candidate (labccie@xxxxxxxxx)
Date: Sun Mar 24 2002 - 03:43:52 GMT-3
Sean,
Yesterday, I was having problems with ISDN BRI's on both r2 and r3.
from time to time, I got "spid Not valid" errors, and after a couple
of reboots and wait for like 5 mins, it finally came up all fine.
I noticed in your configs, you've got only spids configured without
tel. numbers specified, I did it with mine too, but I'm not sure if
it's required or just listed there for caller ID features to work?
I loaded v12.2 image assuming it does everything that 12.1 does.
or what else am I missing by practising on V12.2 ?
Go get the number this Tuesday, Sean.
------ "Sean C." <Upp_and_Upp@hotmail.com> wrote: > That's good that the configs worked the 2nd time around. Your configs > looked fine the first time. Your concern is merited, I have the same. I > never doubted your multilink, I just knew that multilink in my lab had a > history of acting quirky. Also, I noticed your routers have 12.2 > installed, I think the lab uses 12.1. > > Don't you just luv ISDN? Happy routing, > Sean > ----- Original Message ----- > From: "Lab Candidate" <labccie@yahoo.com> > To: "Sean C." <Upp_and_Upp@hotmail.com>; "Nick Shah" <nshah@connect.com.au>; > "Ahmed Mamoor Amimi" <mamoor@ieee.org>; <ccielab@groupstudy.com> > Sent: Saturday, March 23, 2002 9:08 PM > Subject: Re: ISDN callback scenario - solved > > > I logged on the rack today and redid everything, it just worked like a > charm. > I still don't know what went wrong yesterday. Sean, I don't think the ppp > multilink matters in my case. to prove it, I configured it with and without, > and also configured one-sided, it all worked. This kind of situation and > problem > is what I'm afraid most when it comes to lab date, which is this coming > Thursday. > To all that are interested in solution, I pasted the final working config > below: > > ==================== r2 ======================= > > 2#sh conf > Using 1721 out of 29688 bytes > ! > version 12.2 > service timestamps debug uptime > service timestamps log uptime > no service password-encryption > ! > hostname r2 > ! > boot system flash:c2600-jk9o3s-mz.122-7a.bin > ! > username r3 password 0 cisco > ip subnet-zero > ! > interface BRI0/0 > ip address 40.40.40.2 255.255.255.0 > encapsulation ppp > dialer idle-timeout 60 > dialer map ip 40.40.40.3 name r3 broadcast 3589 > dialer-group 1 > isdn switch-type basic-ni > isdn spid1 2588 > isdn spid2 3588 > no cdp enable > ppp callback request > ppp authentication chap > ppp multilink > ! > ip classless > ip http server > ip pim bidir-enable > ! > dialer-list 1 protocol ip permit > ! > bridge 1 protocol ieee > ! > dial-peer cor custom > ! > line con 0 > line aux 0 > line vty 0 4 > login > ! > end > > r2# > > ==================== r3 ======================= > > Using 2109 out of 29688 bytes > ! > version 12.2 > service timestamps debug uptime > service timestamps log uptime > no service password-encryption > ! > hostname r3 > ! > ! > username r2 password 0 cisco > ip subnet-zero > ! > isdn switch-type basic-ni > call rsvp-sync > ! > interface BRI0/0 > ip address 40.40.40.3 255.255.255.0 > encapsulation ppp > dialer callback-secure > dialer map ip 40.40.40.2 name r2 class dc1 broadcast 2588 > dialer load-threshold 1 outbound > dialer-group 1 > isdn switch-type basic-ni > isdn spid1 3589 > isdn spid2 2589 > no cdp enable > ppp callback accept > ppp authentication chap > ! > ip classless > ip http server > ip pim bidir-enable > ! > ! > map-class dialer dc1 > dialer callback-server username > access-list 101 permit ip host 172.16.2.2 host 172.16.2.1 > dialer-list 1 protocol ip permit > dialer-list 1 protocol ipx permit > ! > line con 0 > line aux 0 > line vty 0 4 > ! > end > > r3# > > > --- "Sean C." <Upp_and_Upp@hotmail.com> wrote: > > Hello, > > > > Well, I just took my stab at the callback scenario and it worked fine > using > > the configs from Lab candidate (do you need to be that anonymous?). I > also > > added the commands 'dialer enable-timeout 5' on the callback router and > > 'dialer wait-for-carrier 10' but the callback worked whether these were > > configured or not. > > > > The only thing I can't guarantee is my multilink. I have it enabled on > both > > sides butttt sometimes the multilink works, sometimes multilink doesn't > > work. I have a feeling it's more my simulator or the code than anything. > > The calls still go through, just sometimes the 2nd channel doesn't get > > brought up. > > > > IOS r5 - Version 12.1(8) > > IOS r6 - Version 12.1(12) > > ! > > hostname r5 > > ! > > username r6 password 0 cisco > > ! > > interface BRI0 > > description Callback router > > ip address 40.40.40.2 255.255.255.0 > > encapsulation ppp > > dialer callback-secure > > dialer enable-timeout 5 > > dialer map ip 40.40.40.1 name r6 class test broadcast 2221 > > dialer map ip 40.40.40.1 name r6 class test broadcast 2222 > > dialer load-threshold 3 either > > dialer-group 1 > > isdn switch-type basic-net3 > > isdn spid1 1111 > > isdn spid2 1112 > > ppp callback accept > > ppp authentication chap > > ppp multilink > > ! > > map-class dialer test > > dialer callback-server username > > ! > > dialer-list 1 protocol ip permit > > ! > > ============================= > > hostname r6 > > ! > > username r5 password 0 cisco > > ! > > interface BRI0 > > description Calling router > > ip address 40.40.40.1 255.255.255.0 > > encapsulation ppp > > dialer wait-for-carrier-time 10 > > dialer map ip 40.40.40.2 name r5 broadcast 1111 > > dialer map ip 40.40.40.2 name r5 broadcast 1112 > > dialer load-threshold 3 either > > dialer-group 1 > > isdn switch-type basic-net3 > > isdn spid1 2221 > > isdn spid2 2222 > > no peer neighbor-route > > ppp callback request > > ppp authentication chap > > ppp multilink > > ! > > dialer-list 1 protocol ip permit > > ! > > > === message truncated ===
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:57:20 GMT-3