Re: Dialup connection problem

gbero · ‎04-18-2002

I am very fresh in this area. Now faced the first challenge! I have users who use asynchronous dial-up connections. Recently some have been complaining that the connections are being terminated with in very few minutes. The error message that I observed from one users laptop is as follows:

100 tty 100 dvschindle Async interface 00:00:00 Modem definitionen for dialup 12 Modems

Apr 18 07:44:56.372: %LINK-5-CHANGED: Interface Async100, changed state to reset

Apr 18 07:44:57.372: %LINEPROTO-5-UPDOWN: Line protocol on Interface Async100, changed state to down

Apr 18 07:45:01.372: %LINK-3-UPDOWN: Interface Async100, changed state to down

The partial out put of sh logg is as follows:

Apr 18 09:16:46.677: TTY130: timer type 1 expired

Apr 18 09:16:46.677: TTY130: Exec timer (continued)

Apr 18 09:17:45.811: As98 DDR: idle timeout

Apr 18 09:17:45.811: As98 DDR: disconnecting call

Apr 18 09:17:45.811: TTY98: Async Int reset: Dropping DTR

Apr 18 09:17:45.827: Modem 3/1 Mica: in modem state TERMINATING

Apr 18 09:17:45.859: Modem 3/1 Mica: in modem state IDLE

Apr 18 09:17:45.903: %ISDN-6-DISCONNECT: Interface Serial2/0:0 disconnected fro

m 008983910 , call lasted 339 seconds

Apr 18 09:17:45.907: Modem 3/1 Mica: DISCONNECT after 00:05:38, due to reason (0

xDF00) Host Disconnect.

Apr 18 09:17:46.679: TTY98: DSR was dropped

Apr 18 09:17:46.679: tty98: Modem: READY->(unknown)

Apr 18 09:17:47.687: TTY98: dropping DTR, hanging up

Apr 18 09:17:47.687: tty98: Modem: HANGUP->(unknown)

Apr 18 09:17:47.811: %LINK-5-CHANGED: Interface Async98, changed state to reset

Apr 18 09:17:48.691: TTY98: cleanup pending. Delaying DTR

Apr 18 09:17:49.691: TTY98: cleanup pending. Delaying DTR

Apr 18 09:17:50.691: TTY98: cleanup pending. Delaying DTR

Apr 18 09:17:50.811: TTY98: no timer type 0 to destroy

Apr 18 09:17:50.811: TTY98: no timer type 1 to destroy

Apr 18 09:17:50.811: TTY98: no timer type 3 to destroy

Apr 18 09:17:50.811: TTY98: no timer type 4 to destroy

Apr 18 09:17:50.811: TTY98: no timer type 2 to destroy

Apr 18 09:17:50.811: Async98: allowing modem_process to continue hangup

Apr 18 09:17:51.691: TTY98: restoring DTR

Apr 18 09:17:52.699: TTY98: autoconfigure probe started

Apr 18 09:17:52.811: %LINK-3-UPDOWN: Interface Async98, changed state to down

Apr 18 09:18:02.812: As98 DDR: re-enable timeout

Apr 18 09:19:24.706: TTY131: timer type 1 expired

Apr 18 09:19:24.706: TTY131: Exec timer (continued)

Can anyone elaborate this problem and direct me in finding a solution.

Thanks

tepatel · ‎04-18-2002

Here is the problem

Apr 18 09:17:45.811: As98 DDR: idle timeout

So you can see the call got disconnected because of idle-timeout has expired..Now Idle-timeout is a "inactivity" timer. By default it is 120 secs. Its good to have "sh run" fron the router but...You can increase tha timer using following interface commands

intercace group-async x

dialer in-band

dialer idle-timeout xxxxx <----xxxx in secs

dialer-group 1

Pl. note that you can enter above commands in any Async interface too.

Now in global config enter following command

dialer-list 1 protocol ip permit

Above config will reset the idle-time to max value (xxxx in secs) everytime any ip packet is passed..

tepatel · ‎04-18-2002

Here is the problem

Apr 18 09:17:45.811: As98 DDR: idle timeout

So you can see the call got disconnected because of idle-timeout has expired..Now Idle-timeout is a "inactivity" timer. By default it is 120 secs. Its good to have "sh run" from the router but...You can increase tha timer using following interface commands

intercace group-async x

dialer in-band

dialer idle-timeout xxxxx <----xxxx in secs

dialer-group 1

Pl. note that you can enter above commands in any Async interface too.

Now in global config enter following command

dialer-list 1 protocol ip permit

Above config will reset the idle-time to max value (xxxx in secs) everytime any ip packet is passed..