I have an issue whereby when the VDS is manufactured by VMM domain within ACI, the vCenter environment receives the VDS, the proper settings, etc, but the NICs state that CDP and LLDP is not available? The VDS that was created shows LLDP is enabled?  The vCenter environment has hosts within 3 clusters. Each host in each cluster was already configured to use two of the 4 NICs (Dell Server with 4 10Gb nics, identical, same driver) attached to a pre-existing VDS that is using CDP. On those two NICs, CDP is available and functioning. The two NICs are VMNIC2 and VMNIC3. They are performing all of the management functions for the vSphere environment on each host. The remaining two NICs were attached to the ACI created vDS per each host. (VMNIC0 and VMNIC1). When viewing the Phyical Adapters property in the Web Client and selecting any of these two NICs on any host, the same message appears for the Discovery protocols: "Link Layer Discovery Protocol is not available on this physicall network adapter" As i stated, the VDS that was created shows that LLDP is enabled. Also, anything that is created functions.  When creating EPGs within ACI, the dvPortGroups appear on the VDS and they are functional. But, i have 6 faults, one per each of the VMNICs of the six hosts (2 host per 3 clusters).The fault notes that CDP/LLDP adjacency information for the physical adapters on the host.  "[FSM:FAILED]: Get LLDP/CDP adjacency information for the physical adapters on the host: host1.tenant1.local (TASK:ifc:vmmmgr:CompHvGetHpNicAdj)" dn="uni/vmmp-VMware/dom-Tenant1-VMM/ctrlr-vcsa02.corp.local/fd-[comp/prov-VMware/ctrlr-[Tenant1-VMM]-host1.tenant1.local/hv-host-25]-fault-F606391" domain="infra" highestSeverity="major" lastTransition="2016-09-13T15:39:17.640+00:00" lc="raised" occur="1" origSeverity="major" prevSeverity="major" rule="fsm-get-hp-nic-adj-fsm-fail" severity="major" status="" subject="task-ifc-vmmmgr-comp-hv-get-hp-nic-adj" type="config"/></imdata> Any help with this?  Paul ... View more