OSPF advertises external route learnt via RIP even after route is removed from routing table
The RIP routes exported as AS EXT 2 route by one of the OSPF neighbor is not getting aged out or cleared in the peer even though the RIP routes are no longer present in the advertised router.
EXOS ALL Summit and BlackDiamond switches
The issue happens only when the RIP enabled VLAN is still active. Even though the port in the RIP enabled VLAN through which the RIP route is learnt is down, as long as the VLAN is active, the switch is exporting the learnt route as an EXT route. However, the same route is not present in the routing table as a RIP origin route.
This is identified as a bug.
CR xos0071613 is created for this issue. Track the fix via the mentioned CR. Contact GTAC if you need more information. As a work-around, we could disable the command to export the rip routes.