Hi All
Has anyone labbed VXLAN EVPN multi-site with on the Nexus 9000v?
I have a test topology in EVE-NG, with two sites. One site has two BGWs (also acting as a spine), the other has one. Each site has a VTEP leaf.
When sending unicast layer 2 traffic from the single BGW site to the multi-BGW site, in a capture on the DCI interface of the source BGW I see...
1 packet to the VIP
1 packet to the designated forwarder PIP
1 packet looped back from the designated forwarder PIP
All the packets make it down to the host on the multi-BGW site.
The l2fwder output from the single BGW site's BGW indicates that the unicast traffic should be tunnelled to the VIP of the other, multi-BGW site, but for some reason this is ignored and it also seems to be forwarded as BUM traffic too.
NXOS9# show system internal l2fwder mac Legend: * - primary entry, G - Gateway MAC, (R) - Routed MAC, O - Overlay MAC age - seconds since last seen,+ - primary entry using vPC Peer-Link, (T) - True, (F) - False, C - ControlPlane MAC VLAN MAC Address Type age Secure NTFY Ports ---------+-----------------+--------+---------+------+----+------------------ * 10 000c.291a.cfcf static - F F nve-peer1 192.168.101.3 G 101 5000.0009.0007 static - F F sup-eth1(R) G 20 5000.0009.0007 static - F F sup-eth1(R) G 10 5000.0009.0007 static - F F sup-eth1(R) * 10 b862.1f11.5641 static - F F nve-peer1 192.168.101.3 * 10 000c.29ec.ccd2 static - F F nve-peer3 192.168.88.1 <-- other site VIP G - 0200:c0a8:5802 static - F F sup-eth1(R) 1 1 -00:01:00:01:00:10 - 1
Does anyone else get the same duplicate traffic? I just want to check if this is a limitation of the l2fwder module of the VM (like maybe it's not storing the learned MACs correctly, causing the BUM treatment and split horizon being ignored), rather than an error in my config.
No comments:
Post a Comment