I am working on a simple CSS design using Active/Backup with VIP and interface redundancy. My servers are dual homed to the Active and Backup CSS's using teaming. I am sure this has been done before, but I have not found any documentation on how this would work, and how to best configure the teaming (Active/Active, Active/Passive, etc). Has anyone seen any documentation on this, or implemented a similar scenario? My concern is that when the Active CSS takes itself out of service for a component failure, how will this affect the teaming. In an Active/Passive teaming config, will the Active Nic continue to forward traffic to the now downed CSS since the link is still up? In an Active/Active teaming config, I have the same concern. Will half of the traffic still go to the downed CSS? Any info would be much appreciated.
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...