Virtual machine lose network connectivity when running the services.sh restart command on the ESXi host when using Link Aggregation Control Protocol (LACP) LAG on the vSphere Distributed Switch

Products

• VMware vSphere ESXi

Issue/Introduction

When using Link Aggregation Control Protocol (LACP) Link Aggregation Group (LAG) in the VMware vSphere Distributed Switch (vDS), you experience these symptoms:

• Virtual machines lose network connectivity after restarting the VMware ESXi host Management Agents using this command services.sh restart.
• You are using Link Aggregation Control Protocol (LACP) Link Aggregation Groups (LAG) in the VMware vSphere Distributed Switch (vDS).

Environment

VMware vSphere ESXi 5.5.x

VMware vSphere ESXi 6.0.x
VMware vSphere ESXi 6.5
VMware vSphere ESXi 7.x
VMware vSphere ESXi 8.x

Cause

This issue occurs due to the LACP module on the ESXi host restarting with all the other management services as this is part of the init.d scripts.

The virtual machines lose network connectivity at the time of the LACP module restart in both active and passive mode of LACP LAG on the vSphere Distributed Switch (vDS).

Resolution

This is a known issue affecting VMware ESXi 5.5.x and ESXi 6.0.x.

Currently, there is no resolution.

To confirm if LACP is in use run the following command:
esxcli network vswitch dvs vmware lacp status get

To work around the issue, restart the specific ESXi host Management Agent individually instead of using the services.sh restart command.

Note: You can individually restart a specific ESXi host Management Agent.

To individually restart a specific ESXi host Management Agent:

1. Log in as root to the ESXi host using SSH.
2. To restart a specific agent, run this command:
   
   /etc/init.d/Agent_Name restart
   
   For example:
   
   /etc/init.d/ntpd restart
   
   Note: Usage: <Agent> {start|stop|status|restart}

Additional Information

Impact/Risks:

VMware vSAN environment where LACP is configured may also be impacted when the ESXi Management Agents is restarted using the command services.sh restart.

https://knowledge.broadcom.com/external/article/419051/

https://knowledge.broadcom.com/external/article/320280/

https://knowledge.broadcom.com/external/article?articleNumber=318706