High number of "LLDP_ProcessPort: Failed to get status of port" messages in syslog.log

Products

• VMware vSphere ESXi

Issue/Introduction

- Syslog servers and syslog.log file show continuous "LLDP_ProcessPort: Failed to get status of port" messages for ESXi hosts.

[YYYY-MM-DDTHH:MM:SS] snmpd[###]: get_pnic_pkt_stats: fetch VSI_NODE_net_openPorts_type failed Not found
[YYYY-MM-DDTHH:MM:SS] snmpd[###]: get_pnic_pkt_stats: fetch VSI_NODE_net_openPorts_type failed Not found
[YYYY-MM-DDTHH:MM:SS] snmpd[###]: get_pnic_pkt_stats: fetch VSI_NODE_net_openPorts_type failed Not found
[YYYY-MM-DDTHH:MM:SS] snmpd[###]: LLDP_ProcessPort: Failed to get status of port -##########: Bad parameter
[YYYY-MM-DDTHH:MM:SS] snmpd[###]: LLDP_ProcessSwitch: Failed to parse lldp data for port -##########: Bad parameter
[YYYY-MM-DDTHH:MM:SS] snmpd[###]: LLDP_RebuildMIB: Loading lldp mib failed while parsing switch vSwitch0



- LLDP information cannot be received using an SNMP monitoring tool.

Environment

VMware vSphere ESXi 7.x
VMware vSphere ESXi 8.x

Cause

The port value exceeds the maximum integer limit.
As a result, the SNMP daemon reports a "Bad port" error while retrieving LLDP data.

Resolution

This issue is fixed in ESXi 7.0 U3q, 8.0 U3 and above.