[c-nsp] OSPF dead timer problem

[Church, Chuck]

Are you sure the circuit is running clean?  I've seen marginal T1s where
there was enough packet loss to cause routing protocol drops, yet the
interfaces always said 'up'.  What does the CSU side of things tell you?
You can always try a larger hello to dead interval ratio, like 1:5,
2:10, etc to see if that helps.  Are the CPUs running ok on both
routers? 


Chuck Church
Lead Design Engineer
CCIE #8776, MCNE, MCSE
Netco Government Services - Design & Implementation Team
1210 N. Parker Rd.
Greenville, SC 29609
Home office: 864-335-9473
Cell: 703-819-3495
cchurch at netcogov.com
PGP key: http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x4371A48D 


-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net
[mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Matt Bazan
Sent: Wednesday, March 23, 2005 2:28 PM
To: cisco-nsp at puck.nether.net
Subject: [c-nsp] OSPF dead timer problem

Hello,
	I'm no OSPF expert (by any stretch) and I'm seeing a strange
anomaly between two of our 3640 routers.  What's happening is that the
dead timer is expiring between on one of our T1 p2p links even though
the circuit between the two routers is fine (everyting is up/up).  This
is causing a brief (few seconds or so) loss of communication between the
devices but not long enough to trigger an ospf re-convergence (if I have
my terminology correct).  Ideas as to what is going on?  Thanks,

  Matt


_______________________________________________
cisco-nsp mailing list  cisco-nsp at puck.nether.net
https://puck.nether.net/mailman/listinfo/cisco-nsp
archive at http://puck.nether.net/pipermail/cisco-nsp/