Preview Tool

Cisco Bug: CSCvs22023 - Always Prefer IP FabricLooseNode Over MAC FabricLooseNode

Last Modified

Oct 03, 2020

Products (1)

  • Cisco Application Policy Infrastructure Controller (APIC)

Known Affected Releases


Description (partial)

If pre-provision is not in place, there can be a complete outage to VMM integrated endpoints. If the host discovery is not successful, the policy will not be dynamically pushed to the leaf switches because virtual machines are attached.

You will see the following faults on the APIC:

Operational issues detected on LooseNode: xx:xx:xx:xx:xx:xx, error: [LooseNode with hosts attached is disconnected from Network. This typically indicates that the ports connecting to leaf Node(s) are either down or not connected.]

If you check the uplink information in VMware vCenter, you will see both a MAC management address and IP management address reported by LLDP. Due to this, the Cisco APIC will install a fabricLooseNode object for both an IP and MAC entry, and the hvsAdj objects will only show the ESXI hosts sitting behind the MAC fabricLooseNode because it seems that the MAC info is reported last.
moquery -c fabricLooseNode | egrep dn <--- checks fabricLooseNode objects
moquery -c hvsAdj <--- checks adjacency info which is reported from VC
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.