10-07-2003 06:31 AM - edited 03-02-2019 10:49 AM
I was hoping this was a simple config, but a fault has thrown me a little, am I missing something?
Dispite the idle timer being set to never timeout, the router (803) still becomes disconnected.
Here is the config...
interface BRI0
description connected to Internet
no ip address
encapsulation ppp
dialer pool-member 1
isdn switch-type basic-net3
no cdp enable
!
interface Dialer1
description connected to Internet
ip address *
ip nat outside
encapsulation ppp
no ip split-horizon
dialer pool 1
dialer idle-timeout 0
dialer string *
dialer load-threshold 2 either
dialer-group 1
no peer default ip address
no cdp enable
ppp authentication pap callin
ppp pap sent-username * password 7 *
ppp multilink
crypto map clientmap
The dialer shows me the following:
BRI0:1 - dialer type = ISDN
Idle timer (never), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is data link layer up
Dial reason: ip (s=*, d=*)
Interface bound to profile Di1
Current call connected 00:06:46
Connected to * (*)
BRI0:2 - dialer type = ISDN
Idle timer (never), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is multilink member
Dial reason: Multilink bundle overloaded
Interface bound to profile Di1
Current call connected 00:06:36
Connected to * (*)
Di1 - dialer type = DIALER PROFILE
Load threshold for dialing additional calls is 2
Idle timer (never), Fast idle timer (20 secs)
Wait for carrier (30 secs), Re-enable (15 secs)
Dialer state is physical layer up
Number of active calls = 2
Dial String Successes Failures Last DNIS Last status
* 384 0 00:06:44 successful Default
Any help would be greatly appreciated.
Thanks for your time in advance.
Solved! Go to Solution.
10-08-2003 11:44 AM
yes you are correct these command are pretty much the same , using an acl you can add the key word 'log' to the end , this will let you know what ip is initiating the dialing
10-07-2003 07:53 AM
What does the remote end look like ? If you have a dialer interface on the remote end this interface could be counting down the dialer idle timer .
10-08-2003 01:20 AM
The remote end is actually an ISP that I dial direct. It is apparently a permanently nailed up connection.
10-08-2003 03:33 AM
If they have a dialer-group configured on that router if no interesting traffic passes over that interface during the idle-timeout period , the connection will drop , to be prudent I would check with the ISP on exactly how that interface is configured .
10-08-2003 03:54 AM
I see where your coming from.
Great advice, thanks for taking the time to respond.
10-08-2003 05:27 AM
Can you explain the difference between these commands please? I applied the second set to the router and the connection has not dropped (2 1/2 hours continual connection up to yet).
1: dialer-list 1 protocol ip permit
2: access-list 101 permit ip any any
dialer-list 1 protocol ip list 101
I'm under the impression that they both do the same thing, so why does one work and not the other?
10-08-2003 07:38 AM
It appears that you were indeed correct, the ISP I was using had a default idle timeout option set on the line. This has now been removed and the fault cleared. Please respond to this post so that I may indicate it contains the resolution.
Thank you again for you time and effort.
10-08-2003 11:44 AM
yes you are correct these command are pretty much the same , using an acl you can add the key word 'log' to the end , this will let you know what ip is initiating the dialing
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: