Loading...
Loading...
NA
++ OSPF would add the route to URIB incorrectly even if the route was received by a peer within the fabric advertising the same transit tag to the route. ++ The issue is predominantly seen if the initial check fails by OSPF to deny any route being added to the OSPF routing DB with the same transit tag configured in this OSPF instance. ++ Traffic blackhole/ Routing loop might occur as the packet is bounced around within the fabric.
++ Routing protocol should accept a route with the same tag as the one configured in the VRF. This usually happens due to a defect in policymgr. ++ Routing protocol should send more than one NH for evaluation to RPM at the same time. Issue is not seen with single NH evaluation. ++ You will see a match entry in RPM eval. 2026-03-26T06:47:02.105393000+00:00 ospf default [30548]: TID 31719:rpm_upd_tmap_nhop_entry_match_result:4198: Matched nhop X.X.X.X, intf Vlan5, Result RPM_MATCH_ACCEPT, seq 20000, jump_seq 0, reason rte-match >>>>>>>>>>>>>>>>>>>
Cisco Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.