Guest

Preview Tool

Cisco Bug: CSCun71016 - OSPFv3 route stuck in routing table after failover

Last Modified

Feb 27, 2019

Products (1)

  • Cisco ASA 5500-X Series Firewalls

Known Affected Releases

9.1(4)

Description (partial)

Symptom:
The issue is seen in a redundant scenario with a failover pair of ASAs and two routes with different metrics to specific subnet. We shut down the primary/active ASA and one of the routers (the next hop for the route with the lower metric) 

After that failover happens and in the routing table of the Secondary/Active ASA we can see two routes to the same network (one correct and one pointing to the failed Primary router)

Before the shutdown:

OE2  2001:4b50:9f0:1::1/128 [110/20] 
     via fe80::21c:fff:fe5d:e500, outside seq 7
OE2  2001:4b50:9f0:2::1/128 [110/20] 
     via fe80::21c:fff:fe5d:e500, outside seq 7
OE2  2001:4b50:9f0:3::1/128 [110/20] 
     via fe80::204:deff:feab:6818, outside seq 7

After: 

OE2  2001:4b50:9f0:1::1/128 [110/100]	
     via fe80::21c:fff:fe5d:e500, outside seq 5    <-------------- This route points to a router that is down 
     via fe80::204:deff:feab:6818, outside seq 5 <--------------This route is correct
OE2  2001:4b50:9f0:3::1/128 [110/20]
     via fe80::204:deff:feab:6818, outside seq 5

Conditions:
+OSPFv3
+failover
+Primary/Active ASA and the next hop router DOWN
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.