we have configured the tracking feature for a vPC domain to have the primary switch deactivate its interfaces in the event of a peer link failure and let the secondary take over. Unfortunately, one morning, both switches deactivated all of their interfaces due to the tracking feature:
You don't need to use the track feature during remote switch failure. By default, without tracking feature, if SW1 failed, which peer-link and peer keepalive both will bed failed. There is a keepalive timeout on the PKL link and once SW2 detected the timeout, it will become vPC primary switch. This is done automatically, no tracking is needed.
There is only one instance that you want to use tracking feature, which is single 10GE line card with L3 described in the below link:
Jerry, thanks for the reply. I understand that tracking isn't needed if I have at least two line cards. However, in this case, there was only one card in place to configure the peer link, the keepalive link and everything else.
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...