Mailing List Archive

120 is the default timeout ;-)
This is why it is not shown....


Aragon Gouveia wrote:

> Hi,
>
> I have an AS5200 (yea, I know) running IOS 12.1.20. It's accepting ISDN
> calls fine, but persistently disconnects them 2 minutes after connecting
> regardless of line activity. Reason for disconnection in radius accounting
> logs is "Idle-Timeout".
>
> The idle timeout period is not being set from anywhere in the NAS's
> configuration (that I can see), and neither from radius. If I do a "show
> interface" on a connected interface it does register line activity in the
> "Last input" and "Last output" counters. However, the idle timeout counter
> is never reset and eventually runs down to 0 when the line is disconnected.
>
> Anyone know why this is happening?
>
>
> Thanks,
> Aragon
>
>
> _______________________________________________
> cisco-nas mailing list
> cisco-nas@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nas
>

--
***********************************
Chatzithomaoglou Anastasios
Network Design & Operations Center
FORTHnet S.A.
<achatz@forthnet.gr>
***********************************

Hi,

it seems like you forgot to identify the dialer-list command.
There is no definition of interesting traffic, therefore after
a timeout of 120s, the isdn line is disconnected.

For Example:

Int dialer 2
..
..
dialer-group 1


dialer-list 1 protocol ip permit

Regads,
Ahmad Cheikh-Moussa



Aragon Gouveia wrote:
> Hi,
>
> I have an AS5200 (yea, I know) running IOS 12.1.20. It's accepting ISDN
> calls fine, but persistently disconnects them 2 minutes after connecting
> regardless of line activity. Reason for disconnection in radius accounting
> logs is "Idle-Timeout".
>
> The idle timeout period is not being set from anywhere in the NAS's
> configuration (that I can see), and neither from radius. If I do a "show
> interface" on a connected interface it does register line activity in the
> "Last input" and "Last output" counters. However, the idle timeout counter
> is never reset and eventually runs down to 0 when the line is disconnected.
>
> Anyone know why this is happening?
>
>
> Thanks,
> Aragon
>
>
> _______________________________________________
> cisco-nas mailing list
> cisco-nas@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nas


--
Ahmad Cheikh-Moussa
NetUSE AG
Dr.-Hell-Stra?e, 24107 Kiel, Federal Republic of Germany
Telefon: +49 431 386435 00 -- Telefax: +49 431 386435 99
Service: Service@NetUSE.DE -- http://NetUSE.DE/

Thank you. It's working. :)


| By Ahmad Cheikh Moussa <acm@netuse.de>
| [ 2003-09-25 12:03 +0200 ]
> Hi,
>
> it seems like you forgot to identify the dialer-list command.
> There is no definition of interesting traffic, therefore after
> a timeout of 120s, the isdn line is disconnected.
>
> For Example:
>
> Int dialer 2
> ..
> ..
> dialer-group 1
>
>
> dialer-list 1 protocol ip permit
>
> Regads,
> Ahmad Cheikh-Moussa
>
>
>
> Aragon Gouveia wrote:
> >Hi,
> >
> >I have an AS5200 (yea, I know) running IOS 12.1.20. It's accepting ISDN
> >calls fine, but persistently disconnects them 2 minutes after connecting
> >regardless of line activity. Reason for disconnection in radius accounting
> >logs is "Idle-Timeout".
> >
> >The idle timeout period is not being set from anywhere in the NAS's
> >configuration (that I can see), and neither from radius. If I do a "show
> >interface" on a connected interface it does register line activity in the
> >"Last input" and "Last output" counters. However, the idle timeout counter
> >is never reset and eventually runs down to 0 when the line is disconnected.
> >
> >Anyone know why this is happening?
> >
> >
> >Thanks,
> >Aragon
> >
> >
> >_______________________________________________
> >cisco-nas mailing list
> >cisco-nas@puck.nether.net
> >https://puck.nether.net/mailman/listinfo/cisco-nas
>
>
> --
> Ahmad Cheikh-Moussa
> NetUSE AG
> Dr.-Hell-Stra?e, 24107 Kiel, Federal Republic of Germany
> Telefon: +49 431 386435 00 -- Telefax: +49 431 386435 99
> Service: Service@NetUSE.DE -- http://NetUSE.DE/
>

This is a fun one...try adding dialer idle-timeout 500000

interface Serial0:23
ip unnumbered Loopback0
encapsulation ppp
no ip route-cache


dialer idle-timeout 500000


dialer-group 1
isdn switch-type primary-ni
isdn tei-negotiation first-call
isdn incoming-voice modem
peer default ip address pool default
no fair-queue
no cdp enable
ppp authentication pap secure
ppp multilink
hold-queue 75 in


Chad Lander
CPINTERNET



-----Original Message-----
From: Anastassios Chatzithomaoglou [mailto:achatz@forthnet.gr]
Sent: Thursday, September 25, 2003 4:30 AM
To: Aragon Gouveia
Cc: cisco-nas@puck.nether.net
Subject: Re: [cisco-nas] AS5200 ISDN idle timeout problem


120 is the default timeout ;-)
This is why it is not shown....


Aragon Gouveia wrote:

> Hi,
>
> I have an AS5200 (yea, I know) running IOS 12.1.20. It's accepting ISDN
> calls fine, but persistently disconnects them 2 minutes after connecting
> regardless of line activity. Reason for disconnection in radius
accounting
> logs is "Idle-Timeout".
>
> The idle timeout period is not being set from anywhere in the NAS's
> configuration (that I can see), and neither from radius. If I do a "show
> interface" on a connected interface it does register line activity in the
> "Last input" and "Last output" counters. However, the idle timeout
counter
> is never reset and eventually runs down to 0 when the line is
disconnected.
>
> Anyone know why this is happening?
>
>
> Thanks,
> Aragon
>
>
> _______________________________________________
> cisco-nas mailing list
> cisco-nas@puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nas
>

--
***********************************
Chatzithomaoglou Anastasios
Network Design & Operations Center
FORTHnet S.A.
<achatz@forthnet.gr>
***********************************

_______________________________________________
cisco-nas mailing list
cisco-nas@puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nas