[c-nsp] OSPFv3 down every 34 minutes

[Eric Van Tol]

Wow, first of all, thanks to everyone who responded.  I didn't expect so many responses on the weekend!

One suggestion was to make the interface IPv4 only.  I could do this, but I'm not sure what it would get me.  The VLAN2 interface runs OSPF and OSPFv3 and only OSPFv3 has this weird problem.

The VLAN is not configured as a P2P interface in the OSPFv3 config and I am not using authentication on the v3 OSPF session.  I also checked the standby counters and I'm not experiencing any state changes.  I also seriously doubt that it's related to periodic traffic - the fact that it's *every* 34 minutes, even overnight when there's just a couple of megs on the wire, I think rules that out.  I am also pretty sure that I don't have a Cylon problem.  ;-)  My MTU sizes all look fine, both in v4 and v6.

I just threw a Hail Mary and killed the IPv6/OSPFv3 config on this interface and reconfigured it, so I'll see how that goes.  I'll re-visit some of the other suggestions everyone's made once I have some more coffee in me.

Thanks again,
evt
________________________________________
From: Mike Louis [MLouis at nwnit.com]
Sent: Sunday, April 13, 2008 9:02 PM
To: Mike Louis; Brad Henshaw; Ben Steele; Eric Van Tol
Cc: cisco-nsp at puck.nether.net
Subject: RE: [c-nsp] OSPFv3 down every 34 minutes

What type of link is this running? NBMA or PTP? Are you using authentication on the link?

________________________________________
From: cisco-nsp-bounces at puck.nether.net [cisco-nsp-bounces at puck.nether.net] On Behalf Of Mike Louis [MLouis at nwnit.com]
Sent: Sunday, April 13, 2008 7:54 PM
To: Brad Henshaw; Ben Steele; Eric Van Tol
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] OSPFv3 down every 34 minutes

>From what I recall, OSPF does a periodic sanity check every 30 minutes where it flushes its SPF table or something like that. Could this timing be related to something during that process? Wild guess, but I have seen issues with bouncing EIGRP adjacencies that were related to MTU sizes being set incorrectly on Gigabit and 10/100 interfaces facing each other. The problem only occurred when certain packets with DF bit were set.

Just a thought. Like I said , wild guess.



-----Original Message-----
From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-bounces at puck.nether.net] On Behalf Of Brad Henshaw
Sent: Sunday, April 13, 2008 7:23 PM
To: Ben Steele; Eric Van Tol
Cc: cisco-nsp at puck.nether.net
Subject: Re: [c-nsp] OSPFv3 down every 34 minutes

Ben Steele wrote:

> might also be worth setting up an ip sla probe

Definitely. Since it happens fairly predictably, you should also be
able to set the load-interval to 30 on the interfaces connecting to
those neighbours and check if there's a momentary increase of traffic
on those interfaces when the problem occurs.

Can you route around the problem while you troublshoot? (maybe force
a high ip ospf cost on the L3 interfaces)

Regards,
Brad
_______________________________________________
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/


Note: This message and any attachments is intended solely for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, legally privileged, confidential, and/or exempt from disclosure.  If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited.  If you have received this communication in error, please notify the original sender immediately by telephone or return email and destroy or delete this message along with any attachments immediately.

_______________________________________________
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/

Note: This message and any attachments is intended solely for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, legally privileged, confidential, and/or exempt from disclosure.  If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited.  If you have received this communication in error, please notify the original sender immediately by telephone or return email and destroy or delete this message along with any attachments immediately.