1750 Dials up every 10 minutes

[Haldane]

We have a ISDN Dialup link between a 1750 and a 1720.

It wasn't until I got the phone bill that I found the 1750 was dialing the 1720 every 10 minutes and would stay online for about 32 seconds.

The 1720 was also doing a similar thing dialing the 1750 about 6 times a day and staying online for about 17 minutes.

I want the 1720 to be the only one to make the call and only when instructed by a user on the 1720 network

I hope someone can help, It's already cost $1200 in extra call charges.

Cheers

Brendon

 

[brandondaly]

If you could post the configuration then we can take a look through it for you, but my initial thought is that its likely to be caused by RIP updates. These are broadcast by the routers every few minutes or so and will cause the ISDN lines to dial up. If this does appear to be the case then instead of RIP, program in some static routes.
If its not the case then please post the config.

 

[Saeed42]

The culprit in this case could be anything since we don't really know anything about your network, the first place to look at is what you specified as interesting traffic, and make sure you place the dialer interface in passive mode so no routing broadcast can bring the line up, I would also get packet sniffer and try to find out what's bringing the line up and place that in access list that denies that to bring the line up.

Hope that helps
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Don't be content with being average. Average is as close to the bottom as it is to the top
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

 

[c24070]

no need for a sniffer, several debugs or even a sh dialer will tell you what is bring up your line......

are u sure your wan connection isn't dropping or taking hits causing your dial connection to come up ?

 

[Haldane]

Thank you for responding.

As you can probably tell I'm very much a learner with regards to routers.

The 1720 is on a small 25 user win2000 network with the gateway specified on their server.

On demand (hopefully) they dial our 1750 and connect to a win2000 terminal server, the gateway is only specified on this server not our PDC.

The users on the 1720 are able to logon to our terminal server and run the desired apps, A printer has been setup on our terminal server using a standard TCP/IP port IP_192.168.0.192 to enable the 1720 users to print to their end.

I have included the configuration of Both routers

Cheers

Brendon

1750 Configuration
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
no service tcp-small-servers
no service udp-small-servers
!
hostname Cisco1750
!
enable password ***********
username Cisco1720 password ********
!
no ip name-server
!
isdn switch-type basic-nznet3
!
ip subnet-zero
no ip domain-lookup
ip routing
!
interface Dialer 1
description connected to Cisco1720
ip address 172.16.1.1 255.255.255.0
no ip split-horizon
encapsulation ppp
dialer in-band
dialer idle-timeout 120
dialer hold-queue 10
dialer load-threshold 10
dialer map snapshot 1 name Cisco1720 broadcast
dialer map ip 172.16.1.5 name Cisco1720 speed 64 broadcast *********
dialer-group 1
ppp authentication chap
ppp multilink
snapshot server 15 dialer
no cdp enable
!
interface FastEthernet 0
no shutdown
description connected to EthernetLAN
ip address 10.0.0.200 255.255.255.0
keepalive 10
!
interface BRI 0
no shutdown
description connected to Cisco1720
no ip address
dialer rotary-group 1
!
interface Serial 0
no description
no ip address
shutdown
!
! Dialer Control List 1
!
no dialer-list 1
dialer-list 1 protocol ip permit
!
router rip
version 2
network 172.16.0.0
network 10.0.0.0
no auto-summary
!
!
ip classless
no ip http server
snmp-server community public RO
snmp-server location
snmp-server contact
!
line console 0
exec-timeout 0 0
password ***********
login
!
line vty 0 4
password ***********
login
!
! The following commands are not recognized by Cisco ConfigMaker
! and are therefore appended here.
!
no parser cache
no service single-slot-reload-enable
logging rate-limit console 10 except errors
memory-size iomem 15
mmi polling-interval 60
no mmi auto-configure
no mmi pvc
mmi snmp-timeout 180
no ip dhcp-client network-discovery
!
interface FastEthernet 0
speed auto
!
end

1720 Configuration
!
service timestamps debug uptime
service timestamps log uptime
no service password-encryption
no service tcp-small-servers
no service udp-small-servers
!
hostname Cisco1720
!
enable password ***********
username Cisco1750 password ***********
!
no ip name-server
!
isdn switch-type basic-nznet3
!
ip subnet-zero
no ip domain-lookup
ip routing
!
interface Dialer 1
description connected to Cisco1750
ip address 172.16.1.5 255.255.255.0
no ip split-horizon
encapsulation ppp
dialer in-band
dialer idle-timeout 120
dialer hold-queue 10
dialer load-threshold 10
dialer map snapshot 1 name Cisco1750 broadcast *********
dialer map ip 172.16.1.1 name Cisco1750 speed 64 broadcast *********
dialer-group 1
ppp authentication chap
ppp multilink
snapshot client 15 360 suppress-statechange-update dialer
no cdp enable
!
interface FastEthernet 0
no shutdown
description connected to EthernetLAN_2
ip address 192.168.0.5 255.255.255.0
keepalive 10
!
interface BRI 0
no shutdown
description connected to Cisco1750
no ip address
dialer rotary-group 1
!
interface BRI 1
no description
no ip address
shutdown
!
! Dialer Control List 1
!
no dialer-list 1
dialer-list 1 protocol ip permit
!
router rip
version 2
network 172.16.0.0
network 192.168.0.0
no auto-summary
!
!
ip classless
no ip http server
snmp-server community public RO
snmp-server location
snmp-server contact
!
line console 0
exec-timeout 0 0
password ***********
login
!
line vty 0 4
password ***********
login
!
! The following commands are not recognized by Cisco ConfigMaker
! and are therefore appended here.
!
memory-size iomem 25
!
interface FastEthernet 0
speed auto
!
end

 

[blahblip]

Any broadcast will bring up your line. you need to specify an access list to allow specific traffic. I dont really see the need for you to run RIP, try using static routes.

 

[pnoo]

If you still did not solve this problem, remove the line "dialer map snapshot 1 name Cisco1750 broadcast *********". Probably you made the configuration with Configmaker. Configmaker adds this line which causes the line to come up.

 

[routerman]

In order to diagnose a problem like this you need to debug the dialer to find out whats activating the line.
2 ways you can do this, both need you to connect up a console to the console port if you have local access.

Fisrt way, if router is bringing up line frequently is to wait until line activates, the console output will tell you when. Then issue `show dialer' command at both ends, one will tell you which ip address and TCP/UDP port which activated the line.

The other is to `debug dialer'this will provide the details of the device that activated the line. However this method wont show you output from the remote device, for that you'll need to telnet in, set the exec timeout on the vty line to `exec-timeout 0 0' and issue `term mon'
These commands stop the telnet session timing out and bring back the console messages from the remote router to you.

Stick another post in when you have this info. If you say that this occurs every 10 mins, thats not RIP, probably a server trying to make a persistant drive connection, this test should give a better clue.