Specifying the Direction of Interesting Trafficīy default, the dialer idle-timeout is reset back to maximum by interesting traffic in the outbound direction. Refer to the section Configuring Idle Timeout and Interesting Traffic for more information on configuring interesting traffic. However, if you need give a granular interesting traffic definition (for example, if HTTP traffic is interesting, but Telnet traffic is not) you need to use the dialer-list command in conjunction with an access-list. The simple method (using only the dialer-list command) specifies an entire protocol (such as IP or IPX) as either interesting or uninteresting.
There are two methods for defining interesting traffic. The dialer idle-timeout command statement under the interface configuration. For more information on ppp timeout idle, refer to the document PPP Per-User Timeouts.) (Another commonly-used command, ppp timeout idle, which is used on virtual access interfaces, is outside the scope of this document. The key idle timeout command is dialer idle-timeout, which is an interface configuration command for async, group-async, ISDN and dialer interfaces. This is probably caused by a high dialer idle timeout value along with a loose interesting traffic definition. This is probably due to a low dialer idle timeout value combined or a restrictive interesting traffic definition.Ĭalls do not disconnect. This disconnection is normally due to the idle-timeout being configured (using the dialer idle-timeout command), while the interesting traffic definition is either not defined or is not applied to the interface.Ĭalls disconnect prematurely. Because the default idle-timeout is not visible, a 120 second disconnect is often misdiagnosed.Ĭalls get disconnected every x minutes after the connection is established. Although the dialer in-band command enables a default idle timeout of 120 seconds on the interface, this value does not appear in the show running-configuration output. This disconnection is normally due to the default idle-timeout of 120 seconds being enabled, while the interesting traffic definition is either not defined or is not applied to the interface. The following symptoms may indicate issues related to the idle timeout:Ĭalls get disconnected every two minutes (120 seconds) after the connection is established. Conventionsįor more information on document conventions, see the Cisco Technical Tips Conventions.
If your network is live, make sure that you understand the potential impact of any command. All of the devices used in this document started with a cleared (default) configuration. The information in this document was created from the devices in a specific lab environment.
#Time wait unreplied router software
This document is not restricted to specific software and hardware versions.
There are no specific requirements for this document. This document focuses on configuring and troubleshooting idle timeout issues.
This can result in high toll charges for connections that are charged based on the time the call is connected. However, one of the most common causes for unexpected call drops is the expiry of the idle timeout.Īnother common idle timeout issue is that the link does not disconnect since the idle timeout never expires. The reasons for this vary from hardware failures, to issues within the Telco. A common issue affecting dialup links is unexpected call drops.
0 kommentar(er)
