Cisco ACI Routing advertise same network from different BorderLeaf and server's connected on BoderLeaf
Hi support forum,
I attach a picture of my topology where you can see one ACI Fabric on different physical CPD's but connected by dark fiber (500 meters between them).
We have border leaf on two sites where connect some legacy equipment’s and servers.
Two routers legacy that we connect to border work as Active-Standby, the problem is when we connect a Server on the same border (i know that is not the site but we need to do) because on the border where the active legacy router is connected the routing table see the same network 10.0.0.0/24 learned local by OSPF (preferred) and from the fabric by MBGP. This is right.
But on the border where is connected the standby legacy router the server the routing table for 10.0.0.0/24 is learned from ospf standby legacy router and from MBGP from the fabric, in this case the server connected to this border will use the local ospf route.
Any idea for how to force the border where the standby legacy router is connected to use the route of the border where is connected the active legacy router, in other words we want to have symmetric traffic.
We have some ideas:
1) Connect border's and legacy routers on the same L3 out sharing the same network segment.
2) Modify the BGP admin distance (don't know if possible on ACI) to a lower value that ospf.
Hello,I understand that Contracts in ACI that are enfored by the leafs are stateless ACL. When is an ACI Contract stateful?- as far as I know when using AVS/AVE?- what about when using Kubernetes/Openstack integration with ovs?
*This event has been rescheduled for causes beyond our control, we appreciate your understanding.
[ The link to the discussion will be published on December 7th ]
This event is an opportunity to have your questions answered on tools available for Nexus 30...
I'm having a strange problem redistributing iBGP routes to OSPF on Nexus 9000. Initially I had an open prefix list to get things working. Some of the routes weren't being redistributed to OSPF and I found this article which helped which said you nee...