AS5800 and Idle-Timeout Issue|
|
|
Bookmark this page:
 Yahoo!
 Google
 Windows Live
 del.icio.us
 digg
 Netscape
|
|
||||||||||||||||
|
Posted by Matt on December 1, 2005, 3:21 pm
Please log in for more thread options
I have two AS5800 access servers. They seem to interpret Idle-Timeout and Ascend-Idle-Limit as Session-Limit or something like that. If I set the Idle-Timeout to 30 minutes, people seem to get kicked off line after 30 minutes with a reason of "Idle-Timeout" even if they were downloading a file. Any thoughts? My config for the groups and async is: interface Group-Async0 no ip address encapsulation slip no group-range ! interface Group-Async1 ip unnumbered FastEthernet0/1/0 ip access-group 105 in ip access-group 105 out encapsulation ppp dialer in-band dialer idle-timeout 0 async dynamic address async dynamic routing async mode interactive peer default ip address pool pool0 pool1 pool2 pool3 compress mppc ppp pfc remote ignore ppp acfc remote ignore ppp authentication chap pap ppp multilink group-range 1/6/00 1/11/143 ! interface Dialer1 ip unnumbered FastEthernet0/1/0 encapsulation ppp no ip route-cache no ip mroute-cache dialer in-band dialer idle-timeout 0 no peer default ip address no fair-queue ppp authentication chap pap ppp multilink ! | ||||||||||||||||
|
Posted by Matt on December 1, 2005, 3:40 pm
Please log in for more thread options However, it seems like the AS5800 is not reset the idle timeout when someone passes data!!! Any thoughts on this one?!?! Matt wrote: | ||||||||||||||||
|
Posted by Aaron Leonard on December 2, 2005, 4:08 pm
Please log in for more thread options If you want any traffic to be considered as interesting, and hence to
reset your idle timeout, then you would need to configure a dialer-group on the relevant interface (which I presume is group-async1, as there is no dialer rotary or dialer pool-member configured to bind it to dialer1), which dialer-group should point to a dialer-list. Cheers, Aaron -- ~ Actually it seems like it IS working.... ~ However, it seems like the AS5800 is not reset the idle timeout when ~ someone passes data!!! Any thoughts on this one?!?! ~ ~ ~ Matt wrote: ~ > Hi,
~ > I have two AS5800 access servers. They seem to interpret Idle-Timeout ~ > and Ascend-Idle-Limit as Session-Limit or something like that. ~ > ~ > If I set the Idle-Timeout to 30 minutes, people seem to get kicked off ~ > line after 30 minutes with a reason of "Idle-Timeout" even if they were ~ > downloading a file. ~ > ~ > Any thoughts? ~ > ~ > ~ > My config for the groups and async is: ~ > ~ > interface Group-Async0 ~ > no ip address ~ > encapsulation slip ~ > no group-range ~ > ! ~ > interface Group-Async1 ~ > ip unnumbered FastEthernet0/1/0 ~ > ip access-group 105 in ~ > ip access-group 105 out ~ > encapsulation ppp ~ > dialer in-band ~ > dialer idle-timeout 0 ~ > async dynamic address ~ > async dynamic routing ~ > async mode interactive ~ > peer default ip address pool pool0 pool1 pool2 pool3 ~ > compress mppc ~ > ppp pfc remote ignore ~ > ppp acfc remote ignore ~ > ppp authentication chap pap ~ > ppp multilink ~ > group-range 1/6/00 1/11/143 ~ > ! ~ > interface Dialer1 ~ > ip unnumbered FastEthernet0/1/0 ~ > encapsulation ppp ~ > no ip route-cache ~ > no ip mroute-cache ~ > dialer in-band ~ > dialer idle-timeout 0 ~ > no peer default ip address ~ > no fair-queue ~ > ppp authentication chap pap ~ > ppp multilink ~ > ! | ||||||||||||||||
|
Posted by Matt on December 5, 2005, 8:19 am
Please log in for more thread options Aaron,
Thanks I'm about to check this out today, as it's working on one of our AS5800's but not the other. How can I go about setting an amount of data to be "interesting" so that just leaving mail open doesn't keep a connection up? Aaron Leonard wrote: > If you want any traffic to be considered as interesting, and hence to
> reset your idle timeout, then you would need to configure a dialer-group > on the relevant interface (which I presume is group-async1, as there is > no dialer rotary or dialer pool-member configured to bind it to dialer1), > which dialer-group should point to a dialer-list. > > Cheers, > > Aaron > > -- > > ~ Actually it seems like it IS working.... > ~ However, it seems like the AS5800 is not reset the idle timeout when > ~ someone passes data!!! Any thoughts on this one?!?! > ~ > ~ > ~ Matt wrote: > ~ > Hi,
> ~ > I have two AS5800 access servers. They seem to interpret Idle-Timeout > ~ > and Ascend-Idle-Limit as Session-Limit or something like that. > ~ > > ~ > If I set the Idle-Timeout to 30 minutes, people seem to get kicked off > ~ > line after 30 minutes with a reason of "Idle-Timeout" even if they were > ~ > downloading a file. > ~ > > ~ > Any thoughts? > ~ > > ~ > > ~ > My config for the groups and async is: > ~ > > ~ > interface Group-Async0 > ~ > no ip address > ~ > encapsulation slip > ~ > no group-range > ~ > ! > ~ > interface Group-Async1 > ~ > ip unnumbered FastEthernet0/1/0 > ~ > ip access-group 105 in > ~ > ip access-group 105 out > ~ > encapsulation ppp > ~ > dialer in-band > ~ > dialer idle-timeout 0 > ~ > async dynamic address > ~ > async dynamic routing > ~ > async mode interactive > ~ > peer default ip address pool pool0 pool1 pool2 pool3 > ~ > compress mppc > ~ > ppp pfc remote ignore > ~ > ppp acfc remote ignore > ~ > ppp authentication chap pap > ~ > ppp multilink > ~ > group-range 1/6/00 1/11/143 > ~ > ! > ~ > interface Dialer1 > ~ > ip unnumbered FastEthernet0/1/0 > ~ > encapsulation ppp > ~ > no ip route-cache > ~ > no ip mroute-cache > ~ > dialer in-band > ~ > dialer idle-timeout 0 > ~ > no peer default ip address > ~ > no fair-queue > ~ > ppp authentication chap pap > ~ > ppp multilink > ~ > ! >
| ||||||||||||||||
|
Posted by Matt on December 5, 2005, 8:48 am
Please log in for more thread options Well,
The configuration on both of our access servers look exactly the same... hrmmm =\ Matt wrote: > Aaron,
> Thanks I'm about to check this out today, as it's working on one of our > AS5800's but not the other. How can I go about setting an amount of > data to be "interesting" so that just leaving mail open doesn't keep a > connection up? > > Aaron Leonard wrote: > >> If you want any traffic to be considered as interesting, and hence to
>> reset your idle timeout, then you would need to configure a dialer-group >> on the relevant interface (which I presume is group-async1, as there is >> no dialer rotary or dialer pool-member configured to bind it to dialer1), >> which dialer-group should point to a dialer-list. >> >> Cheers, >> >> Aaron >> >> -- >> >> ~ Actually it seems like it IS working.... >> ~ However, it seems like the AS5800 is not reset the idle timeout when >> ~ someone passes data!!! Any thoughts on this one?!?! >> ~ ~ ~ Matt wrote: >> ~ > Hi,
>> ~ > I have two AS5800 access servers. They seem to interpret >> Idle-Timeout ~ > and Ascend-Idle-Limit as Session-Limit or something
>> like that. >> ~ > ~ > If I set the Idle-Timeout to 30 minutes, people seem to get
>> kicked off ~ > line after 30 minutes with a reason of "Idle-Timeout"
>> even if they were ~ > downloading a file. >> ~ > ~ > Any thoughts?
>> ~ > ~ > ~ > My config for the groups and async is: >> ~ > ~ > interface Group-Async0 >> ~ > no ip address >> ~ > encapsulation slip >> ~ > no group-range >> ~ > ! >> ~ > interface Group-Async1 >> ~ > ip unnumbered FastEthernet0/1/0 >> ~ > ip access-group 105 in >> ~ > ip access-group 105 out >> ~ > encapsulation ppp >> ~ > dialer in-band >> ~ > dialer idle-timeout 0 >> ~ > async dynamic address >> ~ > async dynamic routing >> ~ > async mode interactive >> ~ > peer default ip address pool pool0 pool1 pool2 pool3 >> ~ > compress mppc >> ~ > ppp pfc remote ignore >> ~ > ppp acfc remote ignore >> ~ > ppp authentication chap pap >> ~ > ppp multilink >> ~ > group-range 1/6/00 1/11/143 >> ~ > ! >> ~ > interface Dialer1 >> ~ > ip unnumbered FastEthernet0/1/0 >> ~ > encapsulation ppp >> ~ > no ip route-cache >> ~ > no ip mroute-cache >> ~ > dialer in-band >> ~ > dialer idle-timeout 0 >> ~ > no peer default ip address >> ~ > no fair-queue >> ~ > ppp authentication chap pap >> ~ > ppp multilink >> ~ > ! >>
| ||||||||||||||||
| Similar Threads | Posted |
| AS5800 and Idle-Timeout Issue | December 1, 2005, 3:21 pm |
| Problem with AS5800 and Ascend attributes | November 23, 2005, 10:11 am |
| PIX VPN Issue | November 11, 2005, 12:15 pm |
| 501 ACL issue | March 7, 2006, 4:17 pm |
| PIX VPN issue | March 17, 2006, 4:13 pm |
| PIX issue | April 6, 2006, 1:28 pm |
| ASA and PAT issue | July 19, 2006, 6:28 pm |
| NAT VPN Issue | June 29, 2005, 4:26 pm |
| VPN Issue | October 15, 2006, 9:16 pm |
| T1 issue | December 28, 2006, 10:26 pm |
| FTP NAT over vpn issue | August 28, 2007, 7:35 am |
| vpn issue | November 23, 2007, 2:26 am |
| PIX 501 Issue | May 21, 2008, 11:36 am |
| PIX VPN issue | October 23, 2008, 6:50 pm |
| acl issue on asa | August 26, 2009, 2:29 am |
|
Home Cabling GuideFinally, an instantly downloadable book that saves you thousands in home improvement dollars! Enjoy living in 21st century technology-advanced home while increasing its selling value and competitive advantage on the real estate market. Whether your cabling is for home office or high-tech leisure, you can wire your home yourself or learn "wirish" to speak with your cabling contractors in their language! Learn More |
> I have two AS5800 access servers. They seem to interpret Idle-Timeout
> and Ascend-Idle-Limit as Session-Limit or something like that.
>
> If I set the Idle-Timeout to 30 minutes, people seem to get kicked off
> line after 30 minutes with a reason of "Idle-Timeout" even if they were
> downloading a file.
>
> Any thoughts?
>
>
> My config for the groups and async is:
>
> interface Group-Async0
> no ip address
> encapsulation slip
> no group-range
> !
> interface Group-Async1
> ip unnumbered FastEthernet0/1/0
> ip access-group 105 in
> ip access-group 105 out
> encapsulation ppp
> dialer in-band
> dialer idle-timeout 0
> async dynamic address
> async dynamic routing
> async mode interactive
> peer default ip address pool pool0 pool1 pool2 pool3
> compress mppc
> ppp pfc remote ignore
> ppp acfc remote ignore
> ppp authentication chap pap
> ppp multilink
> group-range 1/6/00 1/11/143
> !
> interface Dialer1
> ip unnumbered FastEthernet0/1/0
> encapsulation ppp
> no ip route-cache
> no ip mroute-cache
> dialer in-band
> dialer idle-timeout 0
> no peer default ip address
> no fair-queue
> ppp authentication chap pap
> ppp multilink
> !