I have not been able to find a way to not introduce the management ports IP/network in the routing table when using the newer CSS code. Is it possible to revert back to the behavior of prior releases of Webns?
With it in the routing table, it seems to prevent traffic from taking the correct path, which was via a different interface.
For example, I have a 192.168.252.0/24 network assigned to the management port. I also have some devices in that network I would like to route through the CSS to reach. This no longer works since my former static route for 192.168.252.0/24 is gone and replaced by the management port route.
VMware Trunk Port Group is supported from ACI version 2.1
VMM integration must be configured properly
ASA device package must be uploaded to APIC
ASAv version must be compatible with ACI and device package version
In the Previous articles of ACI Automation, we are using Postman/Newman as the Rest API tool to automate the ACI Configuration.
In this article I’m going to discuss on usin...
One of the first steps in building your ACI Fabric is to go through Fabric Discovery. While Fabric Discovery is usually a straightforward process, there are various issues that may prevent you from discovering an ACI switch. This article wil...