Thank you very much Saku and Oliver. Just to summarize it up for the list.
Original symptom: The route appears in VRF BGP table with a "RIB-failure(2) - next-hop mismatch" and consequently is not installed in the VRF RIB. It happens when the NH of the particular prefix is overlapping with IP address attached to an interface in the target VRF - even though the router should be resolving the next-hop in global routing table. This is caused by a bug: CSCsi11807. In our case it the primary IP address on one of the interfaces in the VRF was the same as the NH for this failed route, so we changed the IP address on that interface to get this "GRT NH conflicting with VRF interface IP" issue resolved. ------------------- CSCsi11807 Bug Details. BGP VPNv4 routes not installed into VRF-RT by RIB-Failure. Symptom: BGP VPNv4 routes aren't installed into VRF Routing-Table by RIB-Failure. This behavior might occur when the peering-adderss by neighbor command to VPNv4 neighbor originating the target prefixes is overlapped with some local vrf-interface address. Workaround: configure different peering-adderss to VPNv4 neighbor so that it isn't overlapped with local vrf-interface addresss. adam _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
