Closed ipspace closed 6 months ago
that's strange...
root@hippo:~/TOPOLOGIES/bugs/vrf16# netlab validate
[session] Check BGP sessions with DUT [ node(s): x1,x2 ]
[PASS] x1: Neighbor 10.1.0.1 (dut) is in state Established
[PASS] x2: Neighbor 10.1.0.5 (dut) is in state Established
[PASS] Test succeeded
[prefix] Check whether DUT propagates the beacon prefix [ node(s): x2 ]
[PASS] x2: The prefix 172.0.42.0/24 is in the BGP table
[PASS] Test succeeded
[std_comm] Check standard community propagation on VRF EBGP sessions [ node(s): x2 ]
[PASS] x2: The prefix 172.0.42.0/24 contains the expected communities
[PASS] Test succeeded
[ext_comm] Check extended community propagation on VRF EBGP sessions [ node(s): x2 ]
[PASS] x2: The prefix 172.0.42.0/24 contains the expected communities
[PASS] Test succeeded
[SUCCESS] Tests passed: 5
and
dut# sh run
Current configuration:
!
!Version ArubaOS-CX Virtual.10.13.0005
! [cut]
!
router bgp 65000
!
vrf red
bgp router-id 10.0.0.1
neighbor 10.1.0.2 remote-as 65010
neighbor 10.1.0.2 description x1
neighbor 10.1.0.6 remote-as 65011
neighbor 10.1.0.6 description x2
address-family ipv4 unicast
neighbor 10.1.0.2 send-community standard
neighbor 10.1.0.2 activate
neighbor 10.1.0.6 send-community standard
neighbor 10.1.0.6 activate
redistribute connected
redistribute local loopback
exit-address-family
!
Yeah, I have no idea what was going on. Now it works :(
Also, as of this moment, ArubaCX has zero validation errors ;) Great job!
neighbor send-community has to be configured on VRF EBGP sessions as well