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.
Introduction This article will help you understand the steps on how to
download the UCS licenses from the Cisco Systems website and then
installing it on the UCS. The redacted (blue lines) just covers up
certain numbers for privacy please do not take them...
Introduction This article will help you understand and educate the
customer on how to clear their "expired licenses"
(license-graceperiod-expired) from their UCS-M. If a customer just
purchased a license and needs a step by step guide on how to download
Introduction Prepositioning is a powerful tools on the WAAS platform but
it is not always easy to figure out why your jobs are failing when
trying to retrieve the files.Here is a method that should help you to
figure out the reason why they are not succes...