RE: Still having BRI stress! [7:11653]
ISDN configuration is good at layer 2 you receive also tei from your ISDN switch.Try ro do an debug ppp ...to see what is happening and post the results Best Regards Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=11751&t=11653 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Still having BRI stress! [7:11653]
I would just take them off i.e remove the access-group statements for both just to eliminate any restrictive movement. Phil. --- Uche Ishionwu wrote: > Ok,I'll try it without the access lists...but I > guess access list '99' has > to remain 'cause it's tied to Dialer list 2. Right > ??? > cheers. >-Uche. [EMAIL PROTECTED] Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=11683&t=11653 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Still having BRI stress! [7:11653]
Ok,I'll try it without the access lists...but I guess access list '99' has to remain 'cause it's tied to Dialer list 2. Right ??? cheers. -Uche. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=11682&t=11653 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Still having BRI stress! [7:11653]
I don't think that the ppp negotiation is getting started but cannot work out why !!! Regs, Phil. --- Charles Manafa wrote: > Uche, > You may have an end-to-end connectivity problem. > What does "debug ppp > negotiation" give you. I believe your ISDN line is > good, and the problem > might be the other end. Also, try dropping ppp > multilink. > > CM > > > -Original Message- > > From: Uche Ishionwu [mailto:[EMAIL PROTECTED]] > > Sent: 10 July 2001 11:28 > > To: [EMAIL PROTECTED] > > Subject: RE: Still having BRI stress! [7:11653] > > > > > > Christian, > > I have IOS version 12.0. currently > running..see config > > below I also > > configured the line as ppp multilink..just > check out the > > config, and let > > me know what's wrong. > > > > PS: Are u in Germany by any chance - please > let me know. > > cheers! > > > > config-> > > > > > > > > oks#sh conf > > Using 1721 out of 29688 bytes > > ! > > version 12.0 > > service timestamps debug uptime > > service timestamps log uptime > > no service password-encryption > > ! > > hostname oks > > ! > > no logging monitor > > enable secret 5 $1$IU9Q$qYwqs3CXuKmsl1y1GjcM30 > > enable password oks > > ! > > username msn password 0 msn > > ! > > ! > > ! > > ! > > memory-size iomem 15 > > ip subnet-zero > > no ip domain-lookup > > ! > > isdn switch-type basic-net3 > > isdn voice-call-failure 0 > > isdn tei-negotiation first-call > > ! > > ! > > ! > > interface FastEthernet0/0 > > ip address 192.168.0.2 255.255.255.0 > > no ip directed-broadcast > > duplex auto > > speed auto > > ! > > interface BRI0/0 > > description OKS testing interface! > > no ip address > > no ip directed-broadcast > > encapsulation ppp > > dialer pool-member 1 > > dialer pool-member 2 > > isdn switch-type basic-net3 > > isdn twait-disable > > ! > > interface Dialer1 > > description connected to ELSATEST > > ip unnumbered BRI0/0 > > ip access-group 1 in > > ip directed-broadcast > > encapsulation ppp > > dialer remote-name msn > > dialer pool 1 > > dialer idle-timeout 2147483 either > > dialer wait-for-carrier-time 90 > > dialer string 0192658 > > dialer hold-queue 100 > > dialer-group 1 > > no cdp enable > > ppp authentication chap > > ppp multilink > > ! > > interface Dialer2 > > ip address 192.168.8.3 255.255.255.0 > > ip access-group 1 in > > ip directed-broadcast > > encapsulation ppp > > dialer pool 2 > > dialer idle-timeout 2147483 either > > dialer wait-for-carrier-time 90 > > dialer string 0192658 > > dialer hold-queue 100 > > dialer-group 2 > > no cdp enable > > ppp authentication chap > > ppp multilink > > ! > > ip classless > > ip route 0.0.0.0 0.0.0.0 Dialer1 > > no ip http server > > ! > > access-list 1 permit any > > access-list 99 permit any > > dialer-list 1 protocol ip permit > > dialer-list 1 protocol ipx permit > > dialer-list 2 protocol ip list 99 > > ! > > line con 0 > > transport input none > > line aux 0 > > line vty 0 4 > > password uche1 > > login > > ! > > end > > > > oks# [EMAIL PROTECTED] Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=11679&t=11653 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Still having BRI stress! [7:11653]
Uche, Can you take the access-lists off until you get this working ? Regs, Phil. --- Uche Ishionwu wrote: > Debug ppp seems to be issuing no results. However > this the outcome of the > other debug querries. > > oks# > oks#sh isdn st > Global ISDN Switchtype = basic-net3 > ISDN BRI0/0 interface > dsl 0, interface ISDN Switchtype = > basic-net3 > Layer 1 Status: > ACTIVE > Layer 2 Status: > TEI = 108, Ces = 1, SAPI = 0, State = > MULTIPLE_FRAME_ESTABLISHED > Layer 3 Status: > 0 Active Layer 3 Call(s) > Activated dsl 0 CCBs = 0 > The Free Channel Mask: 0x8003 > > oks#deb isdn ? > L2-Sock-Proc ISDN L2 Socket Process packets > eventsISDN events > q921 ISDN Q921 packets > q931 ISDN Q931 packets > > oks#deb isdn ev > ISDN events debugging is on > oks#deb isdn q92 > ISDN Q921 packets debugging is on > oks#deb isdn q93 > ISDN Q931 packets debugging is on > oks# > oks# > 03:20:21: ISDN BR0/0: RX RRf sapi = 0 tei = 108 > nr = 82 > oks# > 03:20:31: ISDN BR0/0: RX RRf sapi = 0 tei = 108 > nr = 82 > 03:20:176093659136: ISDN BR0/0: TX -> RRp sapi = 0 > tei = 108 nr = 82 > 03:20:41: ISDN BR0/0: RX RRf sapi = 0 tei = 108 > nr = 82 > 03:20:41: ISDN BR0/0: RX RRf sapi = 0 tei = 108 > nr = 82 > 03:21:4294967296: ISDN BR0/0: TX -> RRp sapi = 0 > tei = 108 nr = 82 > 03:21:01: ISDN BR0/0: RX RRf sapi = 0 tei = 108 > nr = 82 > 03:21:01: ISDN BR0/0: RX RRf sapi = 0 tei = 108 > nr = 82 > 03:21:90194313216: ISDN BR0/0: TX -> RRp sapi = 0 > tei = 108 nr = 82 > 03:21:21: ISDN BR0/0: RX RRf sapi = 0 tei = 108 > nr = 82 > 03:21:21: ISDN BR0/0: RX RRf sapi = 0 tei = 108 > nr = 82 > 03:21:176093659136: ISDN BR0/0: TX -> RRp sapi = 0 > tei = 108 nr = 82 > 03:21:41: ISDN BR0/0: RX RRf sapi = 0 tei = 108 > nr = 82 > 03:21:41: ISDN BR0/0: RX RRf sapi = 0 tei = 108 > nr = 82 > 03:22:01: ISDN BR0/0: RX RRf sapi = 0 tei = 108 > nr = 82 > 03:22:11: ISDN BR0/0: RX RRf sapi = 0 tei = 108 > nr = 82 > 03:22:21: ISDN BR0/0: RX RRf sapi = 0 tei = 108 > nr = 82 > 03:22:31: ISDN BR0/0: RX RRf sapi = 0 tei = 108 > nr = 82 > 03:22:176093659136: ISDN BR0/0: TX -> RRp sapi = 0 > tei = 108 nr = 82 > 03:22:41: ISDN BR0/0: RX RRf sapi = 0 tei = 108 > nr = 82 > 03:22:41: ISDN BR0/0: RX RRf sapi = 0 tei = 108 > nr = 82 > 03:23:4294967296: ISDN BR0/0: TX -> RRp sapi = 0 > tei = 108 nr = 82 > 03:23:01: ISDN BR0/0: RX RRf sapi = 0 tei = 108 > nr = 82 > 03:23:01: ISDN BR0/0: RX RRf sapi = 0 tei = 108 > nr = 82 > 03:23:90194313216: ISDN BR0/0: TX -> RRp sapi = 0 > tei = 108 nr = 82 > 03:23:21: ISDN BR0/0: RX RRf sapi = 0 tei = 108 > nr = 82 > 03:23:21: ISDN BR0/0: RX RRf sapi = 0 tei = 108 > nr = 82 > 03:23:41: ISDN BR0/0: RX RRf sapi = 0 tei = 108 > nr = 82 > 03:23:51: ISDN BR0/0: RX RRf sapi = 0 tei = 108 > nr = 82 > 03:24:01: ISDN BR0/0: RX RRf sapi = 0 tei = 108 > nr = 82 > 03:24:11: ISDN BR0/0: RX RRf sapi = 0 tei = 108 > nr = 82 > > ___ > > > oks#debug dialer > Dial on demand events debugging is on > oks#debug dialer ev > Dial on demand events debugging is on > oks#debug dialer p > Dial on demand packets debugging is on > oks# > 03:29:12: BR0/0 DDR: cdp, 342 bytes, outgoing > uninteresting (no dialer-group > def > ined) > 03:29:12: BR0/0 DDR: sending broadcast to default > destination -- failed, not > con > nected [EMAIL PROTECTED] Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=11681&t=11653 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Still having BRI stress! [7:11653]
Hey Phil, 'WHY'...is what I've been asking myself for the past 7 days. cheers.. be glad to receive any brainwaves. -Uche. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=11680&t=11653 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Still having BRI stress! [7:11653]
Uche, You may have an end-to-end connectivity problem. What does "debug ppp negotiation" give you. I believe your ISDN line is good, and the problem might be the other end. Also, try dropping ppp multilink. CM > -Original Message- > From: Uche Ishionwu [mailto:[EMAIL PROTECTED]] > Sent: 10 July 2001 11:28 > To: [EMAIL PROTECTED] > Subject: RE: Still having BRI stress! [7:11653] > > > Christian, > I have IOS version 12.0. currently running..see config > below I also > configured the line as ppp multilink..just check out the > config, and let > me know what's wrong. > > PS: Are u in Germany by any chance - please let me know. > cheers! > > config-> > > > > oks#sh conf > Using 1721 out of 29688 bytes > ! > version 12.0 > service timestamps debug uptime > service timestamps log uptime > no service password-encryption > ! > hostname oks > ! > no logging monitor > enable secret 5 $1$IU9Q$qYwqs3CXuKmsl1y1GjcM30 > enable password oks > ! > username msn password 0 msn > ! > ! > ! > ! > memory-size iomem 15 > ip subnet-zero > no ip domain-lookup > ! > isdn switch-type basic-net3 > isdn voice-call-failure 0 > isdn tei-negotiation first-call > ! > ! > ! > interface FastEthernet0/0 > ip address 192.168.0.2 255.255.255.0 > no ip directed-broadcast > duplex auto > speed auto > ! > interface BRI0/0 > description OKS testing interface! > no ip address > no ip directed-broadcast > encapsulation ppp > dialer pool-member 1 > dialer pool-member 2 > isdn switch-type basic-net3 > isdn twait-disable > ! > interface Dialer1 > description connected to ELSATEST > ip unnumbered BRI0/0 > ip access-group 1 in > ip directed-broadcast > encapsulation ppp > dialer remote-name msn > dialer pool 1 > dialer idle-timeout 2147483 either > dialer wait-for-carrier-time 90 > dialer string 0192658 > dialer hold-queue 100 > dialer-group 1 > no cdp enable > ppp authentication chap > ppp multilink > ! > interface Dialer2 > ip address 192.168.8.3 255.255.255.0 > ip access-group 1 in > ip directed-broadcast > encapsulation ppp > dialer pool 2 > dialer idle-timeout 2147483 either > dialer wait-for-carrier-time 90 > dialer string 0192658 > dialer hold-queue 100 > dialer-group 2 > no cdp enable > ppp authentication chap > ppp multilink > ! > ip classless > ip route 0.0.0.0 0.0.0.0 Dialer1 > no ip http server > ! > access-list 1 permit any > access-list 99 permit any > dialer-list 1 protocol ip permit > dialer-list 1 protocol ipx permit > dialer-list 2 protocol ip list 99 > ! > line con 0 > transport input none > line aux 0 > line vty 0 4 > password uche1 > login > ! > end > > oks# Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=11678&t=11653 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Still having BRI stress! [7:11653]
I just simply connected the router to the isdn network-over BRI, and tried to dial in to the internet...remember that 'ip' was specified as interesting traffic(see config)?...so what went wrong then? Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=11677&t=11653 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Still having BRI stress! [7:11653]
Christian, I have IOS version 12.0. currently running..see config below I also configured the line as ppp multilink..just check out the config, and let me know what's wrong. PS: Are u in Germany by any chance - please let me know. cheers! config-> oks#sh conf Using 1721 out of 29688 bytes ! version 12.0 service timestamps debug uptime service timestamps log uptime no service password-encryption ! hostname oks ! no logging monitor enable secret 5 $1$IU9Q$qYwqs3CXuKmsl1y1GjcM30 enable password oks ! username msn password 0 msn ! ! ! ! memory-size iomem 15 ip subnet-zero no ip domain-lookup ! isdn switch-type basic-net3 isdn voice-call-failure 0 isdn tei-negotiation first-call ! ! ! interface FastEthernet0/0 ip address 192.168.0.2 255.255.255.0 no ip directed-broadcast duplex auto speed auto ! interface BRI0/0 description OKS testing interface! no ip address no ip directed-broadcast encapsulation ppp dialer pool-member 1 dialer pool-member 2 isdn switch-type basic-net3 isdn twait-disable ! interface Dialer1 description connected to ELSATEST ip unnumbered BRI0/0 ip access-group 1 in ip directed-broadcast encapsulation ppp dialer remote-name msn dialer pool 1 dialer idle-timeout 2147483 either dialer wait-for-carrier-time 90 dialer string 0192658 dialer hold-queue 100 dialer-group 1 no cdp enable ppp authentication chap ppp multilink ! interface Dialer2 ip address 192.168.8.3 255.255.255.0 ip access-group 1 in ip directed-broadcast encapsulation ppp dialer pool 2 dialer idle-timeout 2147483 either dialer wait-for-carrier-time 90 dialer string 0192658 dialer hold-queue 100 dialer-group 2 no cdp enable ppp authentication chap ppp multilink ! ip classless ip route 0.0.0.0 0.0.0.0 Dialer1 no ip http server ! access-list 1 permit any access-list 99 permit any dialer-list 1 protocol ip permit dialer-list 1 protocol ipx permit dialer-list 2 protocol ip list 99 ! line con 0 transport input none line aux 0 line vty 0 4 password uche1 login ! end oks# Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=11676&t=11653 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Still having BRI stress! [7:11653]
There is no fault with your ISDN line but there was no interesting traffic for the router to bring the link up - the 2 messages were for CDP on the physical interface and a broadcast (probably a routing protocol). They are not able to activate the link. You need to ping across to the other side of the Dialer1 connection while those debugs are running - we should be able to see what the problem is then. --- Uche Ishionwu wrote: > Debug ppp seems to be issuing no results. However this the outcome > of the > other debug querries. > > oks# > oks#sh isdn st > Global ISDN Switchtype = basic-net3 > ISDN BRI0/0 interface > dsl 0, interface ISDN Switchtype = basic-net3 > Layer 1 Status: > ACTIVE > Layer 2 Status: > TEI = 108, Ces = 1, SAPI = 0, State = > MULTIPLE_FRAME_ESTABLISHED > Layer 3 Status: > 0 Active Layer 3 Call(s) > Activated dsl 0 CCBs = 0 > The Free Channel Mask: 0x8003 > > oks#deb isdn ? > L2-Sock-Proc ISDN L2 Socket Process packets > eventsISDN events > q921 ISDN Q921 packets > q931 ISDN Q931 packets > > oks#deb isdn ev > ISDN events debugging is on > oks#deb isdn q92 > ISDN Q921 packets debugging is on > oks#deb isdn q93 > ISDN Q931 packets debugging is on > oks# > oks# > 03:20:21: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 > oks# > 03:20:31: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 > 03:20:176093659136: ISDN BR0/0: TX -> RRp sapi = 0 tei = 108 nr = > 82 > 03:20:41: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 > 03:20:41: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 > 03:21:4294967296: ISDN BR0/0: TX -> RRp sapi = 0 tei = 108 nr = > 82 > 03:21:01: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 > 03:21:01: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 > 03:21:90194313216: ISDN BR0/0: TX -> RRp sapi = 0 tei = 108 nr = > 82 > 03:21:21: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 > 03:21:21: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 > 03:21:176093659136: ISDN BR0/0: TX -> RRp sapi = 0 tei = 108 nr = > 82 > 03:21:41: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 > 03:21:41: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 > 03:22:01: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 > 03:22:11: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 > 03:22:21: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 > 03:22:31: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 > 03:22:176093659136: ISDN BR0/0: TX -> RRp sapi = 0 tei = 108 nr = > 82 > 03:22:41: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 > 03:22:41: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 > 03:23:4294967296: ISDN BR0/0: TX -> RRp sapi = 0 tei = 108 nr = > 82 > 03:23:01: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 > 03:23:01: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 > 03:23:90194313216: ISDN BR0/0: TX -> RRp sapi = 0 tei = 108 nr = > 82 > 03:23:21: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 > 03:23:21: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 > 03:23:41: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 > 03:23:51: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 > 03:24:01: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 > 03:24:11: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 > > ___ > > > oks#debug dialer > Dial on demand events debugging is on > oks#debug dialer ev > Dial on demand events debugging is on > oks#debug dialer p > Dial on demand packets debugging is on > oks# > 03:29:12: BR0/0 DDR: cdp, 342 bytes, outgoing uninteresting (no > dialer-group > def > ined) > 03:29:12: BR0/0 DDR: sending broadcast to default destination -- > failed, not > con > nected [EMAIL PROTECTED] Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=11675&t=11653 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Still having BRI stress! [7:11653]
Hi there, could you tell me which kind of IOS version do you have on your Router? I installed a huge heap of this kind of router without probs... Sometimes it helps when you simply reboot after made config. How does the isdn line look like? (i mean config point2point..ecc ...) thks and g'luck Chris > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of > Charlie Hartwell > Sent: Tuesday, July 10, 2001 11:26 AM > To: [EMAIL PROTECTED] > Subject: RE: Still having BRI stress! [7:11653] > > > Unfortunately, "debug isdn events" is widely regarded as broken, the > information it gives can be inaccurate. Besides, if the problem isn't > simple (maybe a misconfigured telco switch at the far end - we'd need > cause codes to diagnose that) then we'd only be sending Uche back off > to do more work. I think it's better to get too much info than too > little. > > Cheers > > Charlie > > --- Fomes Iain wrote: > Just do debug isdn > events it gives you all that in one go. When > > you do > > Show ISDN status check that you have a TEI number and the Multiple > > frame IS > > established. If not your ISDN line is knackered. > > > > regards > > Iain Fomes > > [EMAIL PROTECTED] > > > > > > > > > > > > > -----Original Message- > > > From: Charlie Hartwell [SMTP:[EMAIL PROTECTED]] > > > Sent: 10 July 2001 09:39 > > > To: [EMAIL PROTECTED] > > > Subject: Re: Still having BRI stress! [7:11653] > > > > > > The config looks fine but we will need a bit more info to help. > > The > > > error message isn't much use on it's own, so if you do "show isdn > > > status", then run "debug isdn q931", "debug isdn q921" and "debug > > > dialer", then try to make a call it should give you more > > information. > > > If you have any trouble deciphering the output then paste it all > > in > > > an email to the group and we'll try to help out some more. > > > > > > Cheers > > > > > > Charlie > > > > > > --- Uche Ishionwu wrote: > Hello,... > > > >I changed my configuration somewhat, and removed a module. > > But > > > > my cisco > > > > 2620 still wont dial out.!!.can someone look at the > > > > configuration and > > > > the error out put and let me know what may still be the > > > > cause.(Layer 1. and > > > > layer 2. -isdn events- are ok, but theres still no connection) > > > >-Uche. > > > > config---> > > > > > > > > > > > > oks>en > > > > Password: > > > > oks#sh conf > > > > Using 1496 out of 29688 bytes > > > > ! > > > > version 12.0 > > > > service timestamps debug uptime > > > > service timestamps log uptime > > > > no service password-encryption > > > > ! > > > > hostname oks > > > > ! > > > > no logging console > > > > no logging monitor > > > > enable secret 5 $1$IU9Q$qYwqs3CXuKmsl1y1GjcM30 > > > > enable password oks > > > > ! > > > > username msn password 0 msn > > > > ! > > > > ! > > > > ! > > > > ! > > > > memory-size iomem 15 > > > > ip subnet-zero > > > > no ip domain-lookup > > > > ! > > > > isdn switch-type basic-net3 > > > > ! > > > > ! > > > > ! > > > > interface FastEthernet0/0 > > > > ip address 192.168.0.2 255.255.255.0 > > > > no ip directed-broadcast > > > > duplex auto > > > > speed auto > > > > ! > > > > interface BRI0/0 > > > > description OKS testing interface! > > > > no ip address > > > > no ip directed-broadcast > > > > encapsulation ppp > > > > dialer pool-member 1 > > > > dialer pool-member 2 > > > > isdn switch-type basic-net3 > > > > ! > > > > interface Dialer1 > > > > description connected to ELSATEST > > > > ip address 192.168.8.2 255.255.255.0 > > > > no ip directed-broadcast > > > > encapsulation ppp > > > > dialer pool 1 > > > > dialer wait-for-carrier-time 90 > > > > dialer
RE: Still having BRI stress! [7:11653]
Debug ppp seems to be issuing no results. However this the outcome of the other debug querries. oks# oks#sh isdn st Global ISDN Switchtype = basic-net3 ISDN BRI0/0 interface dsl 0, interface ISDN Switchtype = basic-net3 Layer 1 Status: ACTIVE Layer 2 Status: TEI = 108, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED Layer 3 Status: 0 Active Layer 3 Call(s) Activated dsl 0 CCBs = 0 The Free Channel Mask: 0x8003 oks#deb isdn ? L2-Sock-Proc ISDN L2 Socket Process packets eventsISDN events q921 ISDN Q921 packets q931 ISDN Q931 packets oks#deb isdn ev ISDN events debugging is on oks#deb isdn q92 ISDN Q921 packets debugging is on oks#deb isdn q93 ISDN Q931 packets debugging is on oks# oks# 03:20:21: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 oks# 03:20:31: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 03:20:176093659136: ISDN BR0/0: TX -> RRp sapi = 0 tei = 108 nr = 82 03:20:41: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 03:20:41: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 03:21:4294967296: ISDN BR0/0: TX -> RRp sapi = 0 tei = 108 nr = 82 03:21:01: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 03:21:01: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 03:21:90194313216: ISDN BR0/0: TX -> RRp sapi = 0 tei = 108 nr = 82 03:21:21: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 03:21:21: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 03:21:176093659136: ISDN BR0/0: TX -> RRp sapi = 0 tei = 108 nr = 82 03:21:41: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 03:21:41: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 03:22:01: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 03:22:11: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 03:22:21: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 03:22:31: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 03:22:176093659136: ISDN BR0/0: TX -> RRp sapi = 0 tei = 108 nr = 82 03:22:41: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 03:22:41: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 03:23:4294967296: ISDN BR0/0: TX -> RRp sapi = 0 tei = 108 nr = 82 03:23:01: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 03:23:01: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 03:23:90194313216: ISDN BR0/0: TX -> RRp sapi = 0 tei = 108 nr = 82 03:23:21: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 03:23:21: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 03:23:41: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 03:23:51: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 03:24:01: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 03:24:11: ISDN BR0/0: RX RRf sapi = 0 tei = 108 nr = 82 ___ oks#debug dialer Dial on demand events debugging is on oks#debug dialer ev Dial on demand events debugging is on oks#debug dialer p Dial on demand packets debugging is on oks# 03:29:12: BR0/0 DDR: cdp, 342 bytes, outgoing uninteresting (no dialer-group def ined) 03:29:12: BR0/0 DDR: sending broadcast to default destination -- failed, not con nected Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=11673&t=11653 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Still having BRI stress! [7:11653]
...*LOL*.thx so much for your consideration Charlie! This router is beginning to push me off the edge! Is there anything else that could possibly be done? Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=11671&t=11653 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
RE: Still having BRI stress! [7:11653]
Sorry - missed a bit. "Multiple Frame Established" is the most desirable state for layer 2 to be in but "TEI Assigned" is not necessarily a problem. A lot of telcos power down the d-channel if the connection hasn't been used for a while, the router will then report TEI Assigned but this will go back to Multiple Frame Established when a call is attempted inbound or outbound. ___ Unfortunately, "debug isdn events" is widely regarded as broken, the information it gives can be inaccurate. Besides, if the problem isn't simple (maybe a misconfigured telco switch at the far end - we'd need cause codes to diagnose that) then we'd only be sending Uche back off to do more work. I think it's better to get too much info than too little. Cheers Charlie --- Fomes Iain wrote: > Just do debug isdn events it gives you all that in one go. When > you do > Show ISDN status check that you have a TEI number and the Multiple > frame IS > established. If not your ISDN line is knackered. > > regards > Iain Fomes > [EMAIL PROTECTED] > > > > > > > -Original Message- > > From: Charlie Hartwell [SMTP:[EMAIL PROTECTED]] > > Sent: 10 July 2001 09:39 > > To: [EMAIL PROTECTED] > > Subject:Re: Still having BRI stress! [7:11653] > > > > The config looks fine but we will need a bit more info to help. > The > > error message isn't much use on it's own, so if you do "show isdn > > status", then run "debug isdn q931", "debug isdn q921" and "debug > > dialer", then try to make a call it should give you more > information. > > If you have any trouble deciphering the output then paste it all > in > > an email to the group and we'll try to help out some more. > > > > Cheers > > > > Charlie > > > > --- Uche Ishionwu wrote: > Hello,... > > >I changed my configuration somewhat, and removed a module. > But > > > my cisco > > > 2620 still wont dial out.!!.can someone look at the > > > configuration and > > > the error out put and let me know what may still be the > > > cause.(Layer 1. and > > > layer 2. -isdn events- are ok, but theres still no connection) > > >-Uche. > > > config---> > > > > > > > > > oks>en > > > Password: > > > oks#sh conf > > > Using 1496 out of 29688 bytes > > > ! > > > version 12.0 > > > service timestamps debug uptime > > > service timestamps log uptime > > > no service password-encryption > > > ! > > > hostname oks > > > ! > > > no logging console > > > no logging monitor > > > enable secret 5 $1$IU9Q$qYwqs3CXuKmsl1y1GjcM30 > > > enable password oks > > > ! > > > username msn password 0 msn > > > ! > > > ! > > > ! > > > ! > > > memory-size iomem 15 > > > ip subnet-zero > > > no ip domain-lookup > > > ! > > > isdn switch-type basic-net3 > > > ! > > > ! > > > ! > > > interface FastEthernet0/0 > > > ip address 192.168.0.2 255.255.255.0 > > > no ip directed-broadcast > > > duplex auto > > > speed auto > > > ! > > > interface BRI0/0 > > > description OKS testing interface! > > > no ip address > > > no ip directed-broadcast > > > encapsulation ppp > > > dialer pool-member 1 > > > dialer pool-member 2 > > > isdn switch-type basic-net3 > > > ! > > > interface Dialer1 > > > description connected to ELSATEST > > > ip address 192.168.8.2 255.255.255.0 > > > no ip directed-broadcast > > > encapsulation ppp > > > dialer pool 1 > > > dialer wait-for-carrier-time 90 > > > dialer string 00192658 > > > dialer hold-queue 10 > > > dialer-group 1 > > > ppp authentication chap > > > ! > > > interface Dialer2 > > > ip address 192.168.8.3 255.255.255.0 > > > no ip directed-broadcast > > > encapsulation ppp > > > dialer pool 2 > > > dialer wait-for-carrier-time 90 > > > dialer string 00192658 > > > dialer hold-queue 10 > > > dialer-group 2 > > > no cdp enable > > > ppp authentication chap > > > ! > > > ip classless > > > ip route 0.0.0.0 0.0.0.0 Dialer1 > > > no ip http server > > > ! >
RE: Still having BRI stress! [7:11653]
Unfortunately, "debug isdn events" is widely regarded as broken, the information it gives can be inaccurate. Besides, if the problem isn't simple (maybe a misconfigured telco switch at the far end - we'd need cause codes to diagnose that) then we'd only be sending Uche back off to do more work. I think it's better to get too much info than too little. Cheers Charlie --- Fomes Iain wrote: > Just do debug isdn events it gives you all that in one go. When > you do > Show ISDN status check that you have a TEI number and the Multiple > frame IS > established. If not your ISDN line is knackered. > > regards > Iain Fomes > [EMAIL PROTECTED] > > > > > > > -Original Message- > > From: Charlie Hartwell [SMTP:[EMAIL PROTECTED]] > > Sent: 10 July 2001 09:39 > > To: [EMAIL PROTECTED] > > Subject:Re: Still having BRI stress! [7:11653] > > > > The config looks fine but we will need a bit more info to help. > The > > error message isn't much use on it's own, so if you do "show isdn > > status", then run "debug isdn q931", "debug isdn q921" and "debug > > dialer", then try to make a call it should give you more > information. > > If you have any trouble deciphering the output then paste it all > in > > an email to the group and we'll try to help out some more. > > > > Cheers > > > > Charlie > > > > --- Uche Ishionwu wrote: > Hello,... > > >I changed my configuration somewhat, and removed a module. > But > > > my cisco > > > 2620 still wont dial out.!!.can someone look at the > > > configuration and > > > the error out put and let me know what may still be the > > > cause.(Layer 1. and > > > layer 2. -isdn events- are ok, but theres still no connection) > > >-Uche. > > > config---> > > > > > > > > > oks>en > > > Password: > > > oks#sh conf > > > Using 1496 out of 29688 bytes > > > ! > > > version 12.0 > > > service timestamps debug uptime > > > service timestamps log uptime > > > no service password-encryption > > > ! > > > hostname oks > > > ! > > > no logging console > > > no logging monitor > > > enable secret 5 $1$IU9Q$qYwqs3CXuKmsl1y1GjcM30 > > > enable password oks > > > ! > > > username msn password 0 msn > > > ! > > > ! > > > ! > > > ! > > > memory-size iomem 15 > > > ip subnet-zero > > > no ip domain-lookup > > > ! > > > isdn switch-type basic-net3 > > > ! > > > ! > > > ! > > > interface FastEthernet0/0 > > > ip address 192.168.0.2 255.255.255.0 > > > no ip directed-broadcast > > > duplex auto > > > speed auto > > > ! > > > interface BRI0/0 > > > description OKS testing interface! > > > no ip address > > > no ip directed-broadcast > > > encapsulation ppp > > > dialer pool-member 1 > > > dialer pool-member 2 > > > isdn switch-type basic-net3 > > > ! > > > interface Dialer1 > > > description connected to ELSATEST > > > ip address 192.168.8.2 255.255.255.0 > > > no ip directed-broadcast > > > encapsulation ppp > > > dialer pool 1 > > > dialer wait-for-carrier-time 90 > > > dialer string 00192658 > > > dialer hold-queue 10 > > > dialer-group 1 > > > ppp authentication chap > > > ! > > > interface Dialer2 > > > ip address 192.168.8.3 255.255.255.0 > > > no ip directed-broadcast > > > encapsulation ppp > > > dialer pool 2 > > > dialer wait-for-carrier-time 90 > > > dialer string 00192658 > > > dialer hold-queue 10 > > > dialer-group 2 > > > no cdp enable > > > ppp authentication chap > > > ! > > > ip classless > > > ip route 0.0.0.0 0.0.0.0 Dialer1 > > > no ip http server > > > ! > > > access-list 99 permit any > > > dialer-list 1 protocol ip permit > > > dialer-list 1 protocol ipx permit > > > dialer-list 2 protocol ip list 99 > > > ! > > > line con 0 > > > transport input none > > > line aux 0 > > > line vty 0 4 > > > password uche1 > > > login > > > ! > > > no scheduler allocate > > > end >
RE: Still having BRI stress! [7:11653]
Just do debug isdn events it gives you all that in one go. When you do Show ISDN status check that you have a TEI number and the Multiple frame IS established. If not your ISDN line is knackered. regards Iain Fomes [EMAIL PROTECTED] > -Original Message- > From: Charlie Hartwell [SMTP:[EMAIL PROTECTED]] > Sent: 10 July 2001 09:39 > To: [EMAIL PROTECTED] > Subject: Re: Still having BRI stress! [7:11653] > > The config looks fine but we will need a bit more info to help. The > error message isn't much use on it's own, so if you do "show isdn > status", then run "debug isdn q931", "debug isdn q921" and "debug > dialer", then try to make a call it should give you more information. > If you have any trouble deciphering the output then paste it all in > an email to the group and we'll try to help out some more. > > Cheers > > Charlie > > --- Uche Ishionwu wrote: > Hello,... > >I changed my configuration somewhat, and removed a module. But > > my cisco > > 2620 still wont dial out.!!.can someone look at the > > configuration and > > the error out put and let me know what may still be the > > cause.(Layer 1. and > > layer 2. -isdn events- are ok, but theres still no connection) > >-Uche. > > config---> > > > > > > oks>en > > Password: > > oks#sh conf > > Using 1496 out of 29688 bytes > > ! > > version 12.0 > > service timestamps debug uptime > > service timestamps log uptime > > no service password-encryption > > ! > > hostname oks > > ! > > no logging console > > no logging monitor > > enable secret 5 $1$IU9Q$qYwqs3CXuKmsl1y1GjcM30 > > enable password oks > > ! > > username msn password 0 msn > > ! > > ! > > ! > > ! > > memory-size iomem 15 > > ip subnet-zero > > no ip domain-lookup > > ! > > isdn switch-type basic-net3 > > ! > > ! > > ! > > interface FastEthernet0/0 > > ip address 192.168.0.2 255.255.255.0 > > no ip directed-broadcast > > duplex auto > > speed auto > > ! > > interface BRI0/0 > > description OKS testing interface! > > no ip address > > no ip directed-broadcast > > encapsulation ppp > > dialer pool-member 1 > > dialer pool-member 2 > > isdn switch-type basic-net3 > > ! > > interface Dialer1 > > description connected to ELSATEST > > ip address 192.168.8.2 255.255.255.0 > > no ip directed-broadcast > > encapsulation ppp > > dialer pool 1 > > dialer wait-for-carrier-time 90 > > dialer string 00192658 > > dialer hold-queue 10 > > dialer-group 1 > > ppp authentication chap > > ! > > interface Dialer2 > > ip address 192.168.8.3 255.255.255.0 > > no ip directed-broadcast > > encapsulation ppp > > dialer pool 2 > > dialer wait-for-carrier-time 90 > > dialer string 00192658 > > dialer hold-queue 10 > > dialer-group 2 > > no cdp enable > > ppp authentication chap > > ! > > ip classless > > ip route 0.0.0.0 0.0.0.0 Dialer1 > > no ip http server > > ! > > access-list 99 permit any > > dialer-list 1 protocol ip permit > > dialer-list 1 protocol ipx permit > > dialer-list 2 protocol ip list 99 > > ! > > line con 0 > > transport input none > > line aux 0 > > line vty 0 4 > > password uche1 > > login > > ! > > no scheduler allocate > > end > > > > oks# > > > > > 00:13:236223201280: ISDN ERROR: Module-CCBRI Function-_Go > > Error-Event > > receive > > d for an unrecognized call. Data- B6, 0 > [EMAIL PROTECTED] > > > Do You Yahoo!? > Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk > or your free @yahoo.ie address at http://mail.yahoo.ie * DISCLAIMER: The information contained in this e-mail may be confidential and is intended solely for the use of the named addressee. Access, copying or re-use of the e-mail or any information contained therein by any other person is not authorized. If you are not the intended recipient please notify us immediately by returning the e-mail to the originator. Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=11666&t=11653 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Still having BRI stress! [7:11653]
Uche, Have you tried 'debug ppp' ? Since this is the layer that isn't connecting. Can U post the debug output ? Regs, Phil. --- Uche Ishionwu wrote: > Hello,... >I changed my configuration somewhat, and removed > a module. But my cisco > 2620 still wont dial out.!!.can someone look at > the configuration and > the error out put and let me know what may still be > the cause.(Layer 1. and > layer 2. -isdn events- are ok, but theres still no > connection) >-Uche. > config---> > > > oks>en > Password: > oks#sh conf > Using 1496 out of 29688 bytes > ! > version 12.0 > service timestamps debug uptime > service timestamps log uptime > no service password-encryption > ! > hostname oks > ! > no logging console > no logging monitor > enable secret 5 $1$IU9Q$qYwqs3CXuKmsl1y1GjcM30 > enable password oks > ! > username msn password 0 msn > ! > ! > ! > ! > memory-size iomem 15 > ip subnet-zero > no ip domain-lookup > ! > isdn switch-type basic-net3 > ! > ! > ! > interface FastEthernet0/0 > ip address 192.168.0.2 255.255.255.0 > no ip directed-broadcast > duplex auto > speed auto > ! > interface BRI0/0 > description OKS testing interface! > no ip address > no ip directed-broadcast > encapsulation ppp > dialer pool-member 1 > dialer pool-member 2 > isdn switch-type basic-net3 > ! > interface Dialer1 > description connected to ELSATEST > ip address 192.168.8.2 255.255.255.0 > no ip directed-broadcast > encapsulation ppp > dialer pool 1 > dialer wait-for-carrier-time 90 > dialer string 00192658 > dialer hold-queue 10 > dialer-group 1 > ppp authentication chap > ! > interface Dialer2 > ip address 192.168.8.3 255.255.255.0 > no ip directed-broadcast > encapsulation ppp > dialer pool 2 > dialer wait-for-carrier-time 90 > dialer string 00192658 > dialer hold-queue 10 > dialer-group 2 > no cdp enable > ppp authentication chap > ! > ip classless > ip route 0.0.0.0 0.0.0.0 Dialer1 > no ip http server > ! > access-list 99 permit any > dialer-list 1 protocol ip permit > dialer-list 1 protocol ipx permit > dialer-list 2 protocol ip list 99 > ! > line con 0 > transport input none > line aux 0 > line vty 0 4 > password uche1 > login > ! > no scheduler allocate > end > > oks# > > 00:13:236223201280: ISDN ERROR: Module-CCBRI > Function-_Go Error-Event > receive > d for an unrecognized call. Data- B6, 0 [EMAIL PROTECTED] Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=11664&t=11653 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
Re: Still having BRI stress! [7:11653]
The config looks fine but we will need a bit more info to help. The error message isn't much use on it's own, so if you do "show isdn status", then run "debug isdn q931", "debug isdn q921" and "debug dialer", then try to make a call it should give you more information. If you have any trouble deciphering the output then paste it all in an email to the group and we'll try to help out some more. Cheers Charlie --- Uche Ishionwu wrote: > Hello,... >I changed my configuration somewhat, and removed a module. But > my cisco > 2620 still wont dial out.!!.can someone look at the > configuration and > the error out put and let me know what may still be the > cause.(Layer 1. and > layer 2. -isdn events- are ok, but theres still no connection) >-Uche. > config---> > > > oks>en > Password: > oks#sh conf > Using 1496 out of 29688 bytes > ! > version 12.0 > service timestamps debug uptime > service timestamps log uptime > no service password-encryption > ! > hostname oks > ! > no logging console > no logging monitor > enable secret 5 $1$IU9Q$qYwqs3CXuKmsl1y1GjcM30 > enable password oks > ! > username msn password 0 msn > ! > ! > ! > ! > memory-size iomem 15 > ip subnet-zero > no ip domain-lookup > ! > isdn switch-type basic-net3 > ! > ! > ! > interface FastEthernet0/0 > ip address 192.168.0.2 255.255.255.0 > no ip directed-broadcast > duplex auto > speed auto > ! > interface BRI0/0 > description OKS testing interface! > no ip address > no ip directed-broadcast > encapsulation ppp > dialer pool-member 1 > dialer pool-member 2 > isdn switch-type basic-net3 > ! > interface Dialer1 > description connected to ELSATEST > ip address 192.168.8.2 255.255.255.0 > no ip directed-broadcast > encapsulation ppp > dialer pool 1 > dialer wait-for-carrier-time 90 > dialer string 00192658 > dialer hold-queue 10 > dialer-group 1 > ppp authentication chap > ! > interface Dialer2 > ip address 192.168.8.3 255.255.255.0 > no ip directed-broadcast > encapsulation ppp > dialer pool 2 > dialer wait-for-carrier-time 90 > dialer string 00192658 > dialer hold-queue 10 > dialer-group 2 > no cdp enable > ppp authentication chap > ! > ip classless > ip route 0.0.0.0 0.0.0.0 Dialer1 > no ip http server > ! > access-list 99 permit any > dialer-list 1 protocol ip permit > dialer-list 1 protocol ipx permit > dialer-list 2 protocol ip list 99 > ! > line con 0 > transport input none > line aux 0 > line vty 0 4 > password uche1 > login > ! > no scheduler allocate > end > > oks# > > 00:13:236223201280: ISDN ERROR: Module-CCBRI Function-_Go > Error-Event > receive > d for an unrecognized call. Data- B6, 0 [EMAIL PROTECTED] Do You Yahoo!? Get your free @yahoo.co.uk address at http://mail.yahoo.co.uk or your free @yahoo.ie address at http://mail.yahoo.ie Message Posted at: http://www.groupstudy.com/form/read.php?f=7&i=11662&t=11653 -- FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
