I thought CDP at first too, but by default CDP sends packets every 60
seconds. Holdtime is 180 seconds. Since it's just a lab environment,
running a debug showing what triggers the line to come up would be an
excellent starting place to find the culprit.
In a production environment, using an extended access list would likely fix
the problem (as someone suggested previously).
-- Leigh Anne
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On Behalf Of
> Robert Fowler
> Sent: Monday, September 24, 2001 6:09 AM
> To: [EMAIL PROTECTED]
> Subject: RE: Legacy DDR won't keep quiet [7:20854]
>
>
> I'm taking a stab in the dark, but I think CDP sends traffic
> about every 90
> seconds... Do a SHOW CDP Interface and see how often it is
> sending packets.
> If that is the case turn CDP off. If nothing else activate the
> improbability
> drive.
>
> Robert
>
> -----Original Message-----
> From: Sean Wolfe [mailto:[EMAIL PROTECTED]]
> Sent: Sunday, September 23, 2001 7:48 PM
> To: [EMAIL PROTECTED]
> Subject: Legacy DDR won't keep quiet [7:20854]
>
>
> Howdy there folks, question for you. Studying for the BCRAN, I have a lab
> with two 1602R's with BRI modules. I am simulating a FR
> connection with BRI
> configured for backup in legacy dialer-string mode.
>
> The backup works fine; ie. I pull the FR cable and the backup comes up, I
> send interesting traffic and the BRI dials and routes the packet.
>
> Problem is, even when there is no interesting traffic (even when I put an
> access list on it with 'deny any') the BRI still dials
> periodically. As far
> as I can tell it's about 90 seconds between.
>
> At first I thought it was RIP. But I disabled RIP and it's still doing it!
>
> Here's the config on the spoke router (note Hitchhiker's Guide
> reference =)
> :
>
> -----------
>
> Marvin#sh run
> Building configuration...
>
> Current configuration:
> !
> version 12.0
> service timestamps debug uptime
> service timestamps log uptime
> no service password-encryption
> !
> hostname Marvin
> !
> !
> username marvin password 0 linka
> ip subnet-zero
> no ip domain-lookup
> ip host zaphod 172.30.1.1
> isdn switch-type basic-ni
> !
> !
> !
> interface Ethernet0
> ip address 172.16.1.1 255.255.255.0
> no ip directed-broadcast
> !
> interface Serial0
> backup interface BRI0
> ip address 172.30.1.2 255.255.255.0
> no ip directed-broadcast
> service-module 56k clock source line
> service-module 56k network-type dds
> !
> interface BRI0
> ip unnumbered Ethernet0
> no ip directed-broadcast
> dialer idle-timeout 15
> dialer string 6024384633
> dialer-group 1
> isdn switch-type basic-ni
> isdn spid1 60243844041111
> isdn spid2 60243845441111
> !
> ip classless
> ip route 172.20.2.0 255.255.255.0 BRI0 121
> !
> access-list 1 deny any
> dialer-list 1 protocol ip list 1
> !
> line con 0
> password cisco
> login
> transport input none
> line vty 0 4
> no login
> !
> end
>
> Marvin#
>
> ---------
>
> Why would this thing dial for no reason??? Let me know your thoughts.
>
> BTW congrats to the recent CCIE Written folks (there were a
> couple recently,
> no?)
>
> Thx, -Sean.
Message Posted at:
http://www.groupstudy.com/form/read.php?f=7&i=20911&t=20854
--------------------------------------------------
FAQ, list archives, and subscription info: http://www.groupstudy.com/list/cisco.html
Report misconduct and Nondisclosure violations to [EMAIL PROTECTED]
