We have an MSN2700 based network. One site has 2 border switches (West & East) each with a unique ASN. The leafs are bonded to the borders and are not running BGP at all.
VLANs are created on the leafs are bonded to both borders and connect to storage. This means that VLAN traffic can appear on either border & therefore different ASNs.
What would be the effects of packets from the storage crossing the VLAN & appearing in either or both ASN routing domains?
Thank you for any help or thoughts on this configuration.
Are you stretching these VLANs over the BGP sessions using VXLAN or EVPN? Generally the border leafs being in different ASNs(eBGP) isn’t an issue but I would need a lot more detail about the environment/traffic and a topology to give you a more useful answer.
We are using VXLAN over BGP. There are a number of services running on the leafs with a teamed connection into each leaf. The topology is a ring of 3 data centres using an East & west border on each site. The major site has spines & many leafs. The smaller sites have bonded leafs connecting to the borders
This should work provided that the border leafs are running MLAG and are connected via a MLAG bond to the downstream leafs. That way no matter which border leaf a packet hashes to, the anycast IP would be advertised across the VXLAN fabric. However, typically in this setup both border leafs in the MLAG pair would be in the same ASN but I have seen this work fine in different ASNs as well.