Solved: ISDN back up...please check - Page 2

jsheriony · ‎07-03-2008

We have an ISDN link between 2 locations.

but when we tried to ping doesn't go thru

with each other...

Can please someone check if there7s a problem on the config??

We're not sure yet if it will work or not

if it happens that the main line is down.

Here's the config.i hope this is enough

***Site A****

interface BRI0/0

description ISDN_Call back_server

ip address 192.168.121.245 255.255.255.252

ip access-group 140 out

encapsulation ppp

load-interval 30

dialer idle-timeout 0

dialer map ip 192.168.121.246 name p***** class dial1 *********46756098

dialer hold-queue 100

dialer load-threshold 3 outbound

dialer callback-secure

isdn switch-type ***

no keepalive

no cdp enable

ppp callback accept

***Site B***

interface BRI0/3/0

description Backup_From _B

ip address 192.168.121.246 255.255.255.252

ip access-group 130 out

encapsulation ppp

load-interval 30

dialer idle-timeout 30 either

dialer map ip 192.168.121.245 name p***** *******163506

dialer hold-queue 100

dialer load-threshold 1 outbound

dialer-group 1

isdn switch-type basic-net3

isdn fast-rollover-delay 5

no keepalive

no fair-queue

no cdp enable

ppp callback request

ppp authentication chap

ppp multilink

Thanks

jsheriony · ‎07-03-2008

Rick,

i really appreciate this...

nothing shows on the first debug....

Richard Burts · ‎07-03-2008

Jayson

I am surprised that there is no output in the first debug. I wonder if the output is supressed for some reason. How are you looking for the debug output? Are you on the console or are you telnet/ssh connected to the router? Would you do the show log command and post the first screen or two of output? The initial output of show log gives some helpful information about how logging is configured and the severity levels for logging. Seeing this may be helpful.

Also, just to check on the obvious: you are trying to do the ping from B to A?

HTH

Rick

HTH

Rick

jsheriony · ‎07-03-2008

I kinda been trying from both CE

I'm doing it thru vty.Im not at the site...

when i do isdn test call from either side, it will appear as it's ok base on the sh isdn hist output...but still ping will be NG.

The connection will last for about 30 secs on either side as configured..

I can assume that ISDN wont work even when the main line is down...

jsheriony · ‎07-03-2008

Rick,

checked the logs on Site B and nothing there but the ISDN logs ccaused by my ISDN test calls...

plus this...

Asserion failed: file "/vws/bvb/CPY-v123_8_t_throttle.V123_8_T11/vob.ios.sys7/sys/obj-5k-c2801/../chips/gt96k/gt96k_timer.c", line 771

It does look like a bug....

Richard Burts · ‎07-03-2008

Jayson

Based on the lack of dialer-group and dialer-list on A I would expect ping from A to B to fail. I would expect ping from B to A to work - at least based on which one can initiate the connection.

If you are on vty did you do terminal monitor before running the debug? I still would be interested in seeing the first page of two of output from show log, just to verify that debug is not supressed.

The assertion failed message is almost certainly the sign of a software problem. It might be a good idea to plan for a code upgrade.

HTH

Rick

HTH

Rick

jsheriony · ‎07-03-2008

here's the logs

****SiteA*****

May 7 07:15:23.048 UTC: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to down

May 7 07:15:24.049 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/0:1, changed state to down

May 7 07:26:09.055 UTC: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/0, TEI 81 changed to down

May 7 07:26:31.772 UTC: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/0, TEI 83 changed to up

May 7 12:15:42.370 UTC: %SYS-5-CONFIG_I: Configured from console by vty0 (192.168.121.2)

May 7 12:19:03.376 UTC: %SYS-5-CONFIG_I: Configured from console by vty0 (192.168.121.2)

May 7 12:43:06.277 UTC: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to up

May 7 12:43:06.277 UTC: %ISDN-6-CONNECT: Interface BRI0/0:1 is now connected to *******8446756098 N/A

May 7 12:43:07.844 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/0:1, changed state to up

May 7 12:43:36.519 UTC: %ISDN-6-DISCONNECT: Interface BRI0/0:1 disconnected from *******8446756098 SiteB, call lasted 30 seco

nds

May 7 12:43:36.519 UTC: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to down

May 7 12:43:37.520 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/0:1, changed state to down

May 7 12:48:33.886 UTC: %LINK-3-UPDOWN: Interface BRI0/0:1, changed state to up

May 7 12:48:33.890 UTC: %ISDN-6-CONNECT: Interface BRI0/0:1 is now connected to *******8446756098 N/A

May 7 12:48:35.453 UTC: %LINEPROTO-5-UPDOWN: Line protocol on Interface BRI0/0:1, changed state to up

May 7 12:49:04.128 UTC: %ISDN-6-DISCONNECT: Interface BRI0/0:1 disconnected from *******8446756098 SiteB, call las

*****site B-****

May 7 15:02:33.346 UTC: ASSERTION FAILED: file "/vws/bvb/CPY-v123_8_t_throttle.V123_8_T11/vob/ios.sys7/sys/obj-5k-c2801/../chips/gt96k/gt96k_timer.c", line 771

May 7 15:03:06.031 UTC: BR0/3/0 DDR: Attempting to dial ******9163506

May 7 15:03:06.035 UTC: ASSERTION FAILED: file "/vws/bvb/CPY-v123_8_t_throttle.V123_8_T11/vob/ios.sys7/sys/obj-5k-c2801/../chips/gt96k/gt96k_timer.c", line 771

May 7 15:03:06.219 UTC: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/3/0, TEI 102 changed to up

May 7 15:03:07.679 UTC: BRI0/3/0: wait for isdn carrier timeout, call id=0x8522

May 7 15:03:07.679 UTC: DDR: Dialing failed, 0 packets unqueued and discarded

May 7 15:03:09.867 UTC: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/3/0, TEI 102 changed to down

May 7 15:03:16.290 UTC: ASSERTION FAILED: file "/vws/bvb/CPY-v123_8_t_throttle.V123_8_T11/vob/ios.sys7/sys/obj-5k-c2801/../chips/gt96k/gt96k_timer.c", line 771

May 7 15:03:59.314 UTC: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/3/0, TEI 103 changed to up

May 7 15:04:04.334 UTC: BR0/3/0 DDR: Attempting to dial ******9163506

May 7 15:04:05.790 UTC: BRI0/3/0: wait for isdn carrier timeout, call id=0x8523

May 7 15:04:05.790 UTC: DDR: Dialing failed, 0 packets unqueued and discarded

May 7 15:04:07.981 UTC: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/3/0, TEI 103 changed to down

May 7 15:04:09.409 UTC: ASSERTION FAILED: file "/vws/bvb/CPY-v123_8_t_throttle.V123_8_T11/vob/ios.sys7/sys/obj-5k-c2801/../chips/gt96k/gt96k_timer.c", line 771

May 7 15:06:05.626 UTC: BR0/3/0 DDR: Attempting to dial ******9163506

May 7 15:06:05.630 UTC: ASSERTION FAILED: file "/vws/bvb/CPY-v123_8_t_throttle.V123_8_T11/vob/ios.sys7/sys/obj-5k-c2801/../chips/gt96k/gt96k_timer.c", line 771

May 7 15:06:05.842 UTC: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/3/0, TEI 104 changed to up

May 7 15:06:07.290 UTC: BRI0/3/0: wait for isdn carrier timeout, call id=0x8524

May 7 15:06:07.290 UTC: DDR: Dialing failed, 0 packets unqueued and discarded

May 7 15:06:09.486 UTC: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/3/0, TEI 104 changed to down

May 7 15:06:15.937 UTC: ASSERTION FAILED: file "/vws/bvb/CPY-v123_8_t_throttle.V123_8_T11/vob/ios.sys7/sys/obj-5k-c2801/../chips/gt96k/gt96k_timer.c", line 771

jsheriony · ‎07-03-2008

I also made a debug at site B and run tests below...

SiteB#

SiteB#isdn test call interface BRI0/3/0 *****9163506

SiteB#

May 7 15:06:05.626 UTC: BR0/3/0 DDR: Attempting to dial *****9163506

May 7 15:06:05.630 UTC: ASSERTION FAILED: file "/vws/bvb/CPY-v123_8_t_throttle.V123_8_T11/vob/ios.sys7/sys/obj-5k-c2801/../chips/gt96k/gt96k_timer.c", line 771

SiteB#

May 7 15:06:05.842 UTC: %ISDN-6-LAYER2UP: Layer 2 for Interface BR0/3/0, TEI 104 changed to up

SiteB#

May 7 15:06:07.290 UTC: BRI0/3/0: wait for isdn carrier timeout, call id=0x8524

May 7 15:06:07.290 UTC: DDR: Dialing failed, 0 packets unqueued and discarded

SiteB#

May 7 15:06:09.486 UTC: %ISDN-6-LAYER2DOWN: Layer 2 for Interface BR0/3/0, TEI 104 changed to down

SiteB#

May 7 15:06:15.937 UTC: ASSERTION FAILED: file "/vws/bvb/CPY-v123_8_t_throttle.V123_8_T11/vob/ios.sys7/sys/obj-5k-c2801/../chips/gt96k/gt96k_timer.c", line 771

SiteB#

when I did the debug, yes i run term mon

thanks

Richard Burts · ‎07-03-2008

Jayson

Just verify - the output in the logs that you posted is generated when you do isdn test call and not any output is generated when you attempt to ping from B to A?

I am a bit puzzled at the fact that the logs from A seem to indicate successful connection with B but the logs on B show that dialing failed when attempting to call A. Since the date and time stamps are not accurate I can not tell whether they are in the same time range or not. Can you clarify this?

HTH

Rick

HTH

Rick

jsheriony · ‎07-03-2008

Rick,

ping test has been NG...thus...no output can

be taken for the ping tests...

and yes the output is when I did the isdn test call from site B to site A...Site A looks to be working fine

but however, it does look like that the error at site B is preventing the ISDN to work...

yes they are at the same time range....

uhhhh...i need more study...but Rick, you're really helping me a lot...I really appreciate it...

jsheriony · ‎07-03-2008

do you think it could be resolved by modifiying the configuration??

gonna be a big gumble though....

jsheriony · ‎07-03-2008

here's the sh isdn status output.

***SiteA***

Global ISDN Switchtype = ***

ISDN BRI0/0 interface

dsl 0, interface ISDN Switchtyoe = ***

Layer 1 Status:

ACTIVE

Layer 2 Status:

TEI = 83, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED

Layer 3 Status:

0 Active Layer 3 Call(s)

Active dsl 0 CCBs = 0

The Free Channel Mask; 0x80000003

Total Allocated ISDN CCBs = 0

*****Site B******

Global ISDN Switchtype = ***

ISDN BRI0/3/0 interface

dsl 6, interface ISDN Switchtype = basic-net3

Layer 1 Status:

ACTIVE

Layer 2 Status:

TEI = 101, Ces = 1, SAPI = 0, State = MULTIPLE_FRAME_ESTABLISHED

Layer 3 Status:

0 Active Layer 3 Call(s)

Active dsl 0 CCBs = 0

The Free Channel Mask; 0x80000003

Total Allocated ISDN CCBs = 0

Thanks