Fix VRF gold BGP IPv4 activation on cores and border leafs
With 'no bgp default ipv4-unicast' set at the router level, VRF gold eBGP/iBGP neighbors were establishing but not exchanging any IPv4 prefixes, breaking inter-fabric transit between DC and Campus. Add an explicit 'address-family ipv4' block with 'neighbor X activate' under 'vrf gold' on both cores and all four border leafs. Also drop 'redistribute learned' from the border leaf VRF gold stanza: it is not a valid command in that context and was silently stripped by EOS.
This commit is contained in:
@@ -219,6 +219,14 @@ router bgp 65500
|
||||
neighbor 10.0.15.7 remote-as 66005
|
||||
neighbor 10.0.15.7 send-community extended
|
||||
neighbor 10.0.15.7 maximum-routes 12000 warning-only
|
||||
!
|
||||
address-family ipv4
|
||||
neighbor 10.0.14.5 activate
|
||||
neighbor 10.0.14.7 activate
|
||||
neighbor 10.0.15.5 activate
|
||||
neighbor 10.0.15.7 activate
|
||||
neighbor 10.0.200.130 activate
|
||||
!
|
||||
redistribute connected
|
||||
!
|
||||
end
|
||||
|
||||
Reference in New Issue
Block a user