VSAN
Mostafa Khalil  

Restarting management services may result in VSAN network partition if LACP is configured

An issue was observed where a VSAN node gets partitioned after running at the host’s console:

#services.sh restart

The host rejoins the cluster after the services restat.

The root cause was attributed to restarting the “lacpd” service which results in tearing down the LAG group then re-forming it. During which time, the host is disconnected from the VSAN network. I will update this post when a fix is available.

1 Comment

  1. Jeff Wong

    Great find. Looking forward to the fix.

Got comments?

This site uses Akismet to reduce spam. Learn how your comment data is processed.

3d book display image of Storage Design and Implementation in vSphere 6

Looking for a Great Book on vSphere Storage Virtualization? Look No Further!

A one stop resource on all storage types used with VMware vSphere 6.x. Includes vSAN up to v6.6, VVols, NFS 3.0 and 4.1 and more

Get Your Copy Today>>