"LACPUplinkEventCB: Suppress uplink event" is logged for vmnics not configured with LACP

Products

• VMware vSphere ESXi

Issue/Introduction

In the ESXi vmkernel.log, you may observe log messages similar to the following for physical adapters (vmnics) that are not part of a Link Aggregation Group (LAG/LACP):

YYYY-MM-DDThh:mm:ss.SSSZ In(182) vmkernel: cpu<XX>:<XXXXXXX>)lacp: LACPUplinkEventCB:3115: Suppress uplink block event on uplink vmnic<X>
YYYY-MM-DDThh:mm:ss.SSSZ In(182) vmkernel: cpu<XX>:<XXXXXXX>)lacp: LACPUplinkEventCB:3095: Suppress uplink disconnected event on uplink vmnic<X>
YYYY-MM-DDThh:mm:ss.SSSZ In(182) vmkernel: cpu<XX>:<XXXXXXX>)lacp: LACPUplinkEventCB:3115: Suppress uplink unblocked event on uplink vmnic<X>
YYYY-MM-DDThh:mm:ss.SSSZ In(182) vmkernel: cpu<XX>:<XXXXXXX>)lacp: LACPUplinkEventCB:3074: Suppress uplink connected event on uplink vmnic<X>

Environment

VMware ESXi 8.0

Cause

This is an expected behavior when LACP is enabled on the ESXi host.
These logs are informational and do not indicate a functional error or misconfiguration.

When LACP is configured on the host, all physical uplink events are forwarded to the LACP daemon.
The daemon evaluates whether the event originates from a vmnic that is a member of a LAG.
If the event is for a vmnic that is not managed by LACP, the daemon "suppresses" the event for its own processing and records these messages.

Resolution

These messages can be safely ignored.

There is no impact on the functionality of the LACP (LAG) or the connectivity of the individual vmnics not participating in the LACP configuration.

Additional Information

LACP を構成していない vmnic において "LACPUplinkEventCB: Suppress uplink event" がログに記録される