ACE failover recovery from secondary to primary too fast
I have yet another question that I hope that you can help me with.
I have configured redundancy with interface tracking. When I reboot the primary or an interface on it goes down the switch to the secondary ACE works very well and there is almost no interruption.
However, when a tracked interface on the primary comes back up, the failover to the primary goes so fast that the probes have not yet entered in SUCCESS state and the servers are unreachable for a while (I did not time it but I think around 40 seconds). Is there a way to slow down the process of making the primary active when it again has all the tracked interfaces available (or even better is there a way to get "no preempt" to work when using tracked interfaces)?
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...