One kernel module parameter on the Intel X710 was all it took to get LLDP neighbour information back in vCenter for my Minisforum MS-A2 hosts.
In my V-LAB the MS-A2s connect to a UniFi switch with their two 10G SFP+ ports. Those ports are the uplinks of the VCF distributed switch. Everything worked, but in vCenter the LLDP tab of every X710 uplink stayed empty. No switch name, no port ID, no VLANs.

That matters more than it looks. LLDP is how you prove that vmnic2 really lands on the switch port you think it does, before you troubleshoot vSAN or NSX. It also shows the ESXi host and vmnic on the UniFi side. In this post I explain why the information was missing and how I fixed it the VCF way, one host at a time.
Root cause: the X710 LLDP agent eats the frames
The Intel X710 has its own LLDP agent in the NIC firmware, and it is enabled by default. That agent takes every incoming LLDP frame (EtherType 0x88CC) for itself, mainly to negotiate DCB. As a result the frames never reach the ESXi network stack, so the distributed switch has nothing to show.
The i40en driver controls this agent with the module parameter LLDP:
| Value | Meaning |
|---|---|
| 1 (default) | Firmware LLDP agent on, frames are consumed by the NIC |
| 0 | Firmware LLDP agent off, frames are passed to ESXi |
The parameter is a list with one value per i40en port. When it shows no value at all, the driver runs on its default, which is 1.
There is a second, separate cause with the same symptom. A vSphere Distributed Switch listens for CDP by default, and UniFi switches send LLDP, not CDP. So you need both: the NIC must pass the frames, and the VDS must listen for LLDP.
Step 1: set the distributed switch to LLDP
Start with the free fix, because it needs no reboot. In the vSphere Client:
- Go to Networking, select the VCF distributed switch and open Configure → Properties.
- Click Edit → Advanced → Discovery protocol.
- Set Type to Link Layer Discovery Protocol and Operation to Both.
I use Both instead of Listen. ESXi then also advertises itself, so the UniFi port overview shows the host name and vmnic for each port. With NSX on the VDS this one setting covers the NSX uplinks too.
A standard vSwitch only supports CDP. LLDP is a distributed switch feature.
Step 2: check the i40en ports and parameters
SSH to the host and look at two things first: how many i40en ports the host has, and which module parameters are already set.
esxcli network nic list | grep i40en
esxcli system module parameters list -m i40en | grep -i lldp
esxcli system module parameters list -m i40en
esxcfg-module -g i40en
The first command shows the X710 ports; on the MS-A2 that is two. The second shows LLDP with an empty Value column, which means the firmware agent is on. The third lists all i40en parameters, so you can see whether any Value is filled in. The last one prints the option string that is configured for the module right now; on a host with default settings it is empty.

That last check is important. esxcli system module parameters set -p replaces the complete parameter string of the module. It does not add one parameter. If you already set something else on i40en, put it in the same string, or it is gone after the reboot.
Step 3: disable the firmware LLDP agent, one host at a time
The driver reads its parameters only when it loads, so every host needs a reboot. In a vSAN cluster I treat that as a normal rolling maintenance:
- Check that vSAN Skyline Health is green and that no resync is running.
- Put the host in maintenance mode from vCenter with vSAN data migration set to Ensure accessibility.
- Set the parameter, one value per i40en port:
esxcli system module parameters set -m i40en -p LLDP=0,0. Check it withesxcli system module parameters list -m i40en | grep -i lldp; the Value column now shows0,0. With four X710 ports it would beLLDP=0,0,0,0. - Reboot the host.
- Exit maintenance mode and wait until the vSAN resync is complete.
- Repeat on the next MS-A2.

Count the values carefully. Broadcom documents a case where an invalid LLDP value stopped i40en from loading at all, so the X710 ports disappeared after a reboot (KB 392205). In a VCF cluster those are your vSAN, vMotion and TEP uplinks, so keep the Comet console or another out-of-band path ready before the first reboot.
The setting survives reboots, because it is stored in the host configuration. It does not survive a reinstall, which is why the last section of this post matters.
Step 4: verify X710 LLDP on both sides
First, check on the host that LLDP frames from the UniFi switch now reach ESXi. Replace vmnic2 with your X710 uplink:
pktcap-uw --uplink vmnic2 --ethtype 0x88cc -c 1 -o - | tcpdump-uw -enr -


UniFi sends LLDP every 30 seconds by default, so give it a moment. Then look at what ESXi learned from the neighbour:
vim-cmd hostsvc/net/query_networkhint --pnic-name=vmnic2
In the vSphere Client, go to the host → Configure → Networking → Virtual switches and click the info icon next to the physical adapter. The LLDP tab now shows the UniFi switch name, the port ID and the VLANs.

Everything you need to check the cabling is in that one screen. The System Name tells you which switch, the Port ID which port, and the System Description even shows the UniFi model and firmware.
On the UniFi side, open the switch in UniFi Network and look at the port list. With the VDS on Both, each port shows the ESXi host and its vmnic. That is the quickest way I know to check that the cabling of every MS-A2 matches the uplink mapping in VCF.
Make the X710 LLDP setting stick
A setting made by hand on one host is exactly the kind of drift VCF tries to avoid. I make sure it comes back in two places.
vSphere Configuration Profiles. When the cluster is managed with configuration profiles, a module parameter set by hand shows up as drift, and a later remediation can put it back to the default. Export the cluster configuration, add the i40en LLDP setting in the kernel module settings, import it and remediate. From then on the profile is the source of truth, also for new hosts.
Kickstart. My MS-A2s are installed with an automated ESXi Kickstart. I added the parameter to the %firstboot section, so a reinstalled host comes up with the agent already off:
%firstboot --interpreter=busybox
esxcli system module parameters set -m i40en -p LLDP=0,0
The parameter becomes active at the next driver load, so let the Kickstart end with a reboot.
One side effect to be aware of: DCB. Data Center Bridging is a set of Ethernet extensions for lossless traffic. Priority Flow Control pauses one traffic class instead of the whole link, and DCBX lets the NIC and the switch agree on those settings. DCBX travels inside LLDP frames, which is exactly why the X710 has its own LLDP agent. You need DCB for RoCE, for example vSAN over RDMA, not for vSAN over TCP. The X710 is not a RoCE NIC and my vSAN runs over TCP, so turning the agent off costs nothing here. If you use DCB on your X710s, keep the agent on and accept that the VDS won’t see the LLDP neighbours.
Wrap-up
Empty LLDP information on an X710 is not a UniFi problem and not a vCenter problem. The NIC simply keeps the frames for itself. Set the VDS to LLDP / Both, set LLDP=0,... on i40en with one value per port, reboot the hosts one by one in maintenance mode, and put the setting in your configuration profile and Kickstart.
The same fix applies to any host with an Intel 700-series NIC, not only the MS-A2. While you are at it, check the X710 firmware too: I covered that in updating Intel 700 Series NIC firmware on ESXi. With LLDP working, the next step for my lab is end-to-end jumbo frame validation between the MS-A2s, which deserves a post of its own.
Sources
- LLDP information missing on ESXi with Intel X710 adapters (Broadcom KB 367866): the firmware LLDP agent on Intel 700-series NICs, the
LLDP=0,...fix with one value per i40en port, maintenance mode and reboot; ESXi 8.x and 9.x. - X710 network cards invisible after upgrading to ESXi 8.0 Update 3b (Broadcom KB 392205): what happens when the i40en
LLDPparameter is invalid, with the 2-port and 4-port commands. - Switch discovery protocol (vSphere 8 networking docs): CDP versus LLDP, LLDP only on distributed switches, and the Listen, Advertise and Both modes.
- Packet capture on ESXi using the pktcap-uw tool (Broadcom KB 341568):
pktcap-uwoptions for capturing on an uplink. - LLDP support for vSphere 5 (Rickard Nobel): a new distributed switch starts with CDP in Listen mode.
