I have been experimenting in our test environment with attached-host routes on a vxlan network.
We have are using asymmetric IRB across our vxlan infrastructure as it is (for the moment at least) simple enough for this not to cause us an issue. We want to use attached-host to ensure that the correct pair of leaf switches are used for routing “southbound” traffic. In the production environment there will be 5 pairs of leaf switches which will be routing traffic for the edge vlan. Behind this vlan are ~50 nodes that are connected with MLAG to the pairs of (7060CX) leaf switches.
What we’re seeing in test is that as soon as we enable `ip attached-host route export` in the vlan configuration we only see the ARP for the end devices on one of the MLAG pair. So when this is exported to the Spine switches we only see one host route for the end device.
Is this expected behaviour? I would expect to see a route exported from both switches in the MLAG pair and the spine switches to use ECMPR symantics to load balance between the switches.
It may be that this isn’t significant in the production environment as there will be sufficient nodes for the load to be balanced across the links.
Post your Answer
You must be logged in to post an answer.