Cisco Bug: CSCvt94412 - ACI marks vmnic as down (F1313) but vCenter displays vmnics as connected
Aug 27, 2020
- Cisco Nexus 9000 Series Switches
Known Affected Releases
Symptom: In a situation in which a virtual machine cannot reach the default gateway, Cisco ACI declares a VMNIC as down, but VMware vCenter displays that VMNIC as connected. Conditions: This issue happens on fabrics with ESX hosts connecting to leaf nodes, and there is a VMware domain with the controller connected to the VMware vCenter of the hosts. This issue is triggered by the following steps. 1. Set a leaf node to Maintenance Mode -> Fault "NIC operational state is down" is raised on HpNics (this is expected). 2. Recommission the leaf node after 10 minutes -> The faults persist on the HpNics (this is the issue). When a fabric is upgraded or downgraded, the above steps can happen when APICs finish the upgrade before the leaf node, thus might trigger this issue. However, if the leaf node is recommissioned within ~10 minutes after the NIC down event, a recurring task checking for host adjacency could capture the NIC state when it is up, thus not giving any issues.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.
Bug Details Include
- Full Description (including symptoms, conditions and workarounds)
- Known Fixed Releases
- Related Community Discussions
- Number of Related Support Cases