4500X VSS with 3.6(4) - OSPF adjacencies don't come up after shelf-reload

[Robert Saurer]

A working 4500X VSS pair with 3.6(4) SW and OSPF adjacencies in one SVI is reloaded (shelf-reload). The system comes up but the OSPF adj won't come up no matter how long you wait.

If you then only do another shelf-reload of the 4500X VSS, everything works.

Unfortunately I don't have any debugging output or show commands during the problem from neither side.

Side A: 4500X VSS

Side B: Nexus 7000 (dual sups)

OSPF Area x (NSSA)

OSPF MD5 Auth

OSPF Hello Interval 1s

The OSPF Peer (N7K) is is pingable during the problem.

If anyone knows this and a bug ID, this would be cool. Otherwise we'll have to wait for the next occurance and debug (optional with TAC).

!4500X

interface Vlan3201
 description TS-OSPFDIR-1
 ip address x.x.x.x 255.255.255.248
 no ip redirects
 ip pim query-interval 1
 ip pim sparse-mode
 ip ospf authentication message-digest
 ip ospf message-digest-key 1 md5 7 xxxx
 ip ospf hello-interval 1
 ip ospf priority 5
 ip ospf 1 area 201
 no ipv6 redirects

!

router ospf 1
 router-id x.x.x.x
 ispf
 auto-cost reference-bandwidth 100000
 nsf ietf
 area 201 nssa
 timers throttle spf 10 100 5000
 timers throttle lsa 10 100 5000
 timers lsa arrival 80000
 timers pacing lsa-group 15
 passive-interface default
 no passive-interface Vlan3201
 network 0.0.0.0 255.255.255.255 area 201

[Reza Sharifi]

There seem to be a hello interval mismatch, as I see this only on one side.

For testing, you may want to eliminate this command and maybe the timers commands before rebooting and see if there is a change.

 ip ospf hello-interval 1

[paul driver]

Hello

Is this one of many ospf adjecencys by the only one that doesn't re establish ?

Regards the shelf reload do you have DAD enabled for gel link failure?

Res

Paul