Logical Switch State shows ‘Failed’ when vCenter has one or more disconnected ESXi hosts.
search cancel

Logical Switch State shows ‘Failed’ when vCenter has one or more disconnected ESXi hosts.

book

Article ID: 411256

calendar_today

Updated On:

Products

VMware NSX VMware vCenter Server 8.0

Issue/Introduction

  • vROps reports a critical NSX alarm that a "Logical Switch State has failed".
  • There is no impact on the dataplane.
  • NSX UI (Policy Mode) > Networking > Segments:  Status is 'Success'.
  • NSX UI (Manager Mode) > Networking > Logical Switches:  Config State is 'Failed'.
  • In the vCenter inventory, one or more ESXi hosts appear in a Not Responding or Disconnected state:
    /var/log/vmware/vpxd/vpxd.log
    YYYY-MM-DDTHH:MM:SS. warning vpxd[402397] [Originator@6876 sub=MoHost opID=HostSync-host-######-########] host [vim.HostSystem:host-######,[HOSTNAME] connection state changed to NO_RESPONSE
  • The ReconfigureNsxPortgroups API is returning the Logical Switch State as stateStatus = FAILED in/
    /var/log/proton/nsxapi.log
     
    YYYY-MM-DDTHH:MM:SS.  INFO l2VcFullSyncScheduler1 LogicalSwitchStateServiceImpl 77562 SWITCHING [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Updated LogicalSwitchState: LogicalSwitchState [id =LogicalSwitchState/########-####-####-####-############, revision = 291927, logicalSwitchName = ####-####-########## , stateStatus = FAILED, switchType = DEFAULT, logicalSwitchRevison = 1, portGroupStateRevision = 1, #vdsIdPortGroupStateMap = 1, #networkIdFolderStateMap = 0, nextRealizationTime = 0]

YYYY-MM-DDTHH:MM:SS. ERROR LogicalSwitchStateOperationScheduler1 NsxPortgroupExecuteVcUtils 77562 SWITCHING [nsx@6876 comp="nsx-manager" errorCode="MP8328" level="ERROR" subcomp="manager"] nsxpg Failed to update nsx portgroup for logicalSwitchId : LogicalSwitch/########-####-####-####-############ on vds : ## ## ## ## ## ## ## ##-## ## ## ## ## ## ## ##, PortGroupState : PortGroupState [portGroup =PortGroup [cmId =########-####-####-####-############, portGroupKey = dvportgroup-####], state = FailedForUpdate, inMovementState = null, outMovementState = null], because error: GENERALFAULT: Cannot complete a vSphere Distributed Switch operation for one or more host members.
  • The issue typically resolves when the host reconnects. The vpxd.log will show connection state changed to CONNECTED, and nsxapi.log will report the Logical Switch State as stateStatus = SUCCESS.
    /var/log/vmware/vpxd/vpxd.log
YYYY-MM-DDTHH:MM:SS. warning vpxd[402397] [Originator@6876 sub=MoHost opID=HostSync-host-######-########] host [vim.HostSystem:host-######,[HOSTNAME] connection state changed to CONNECTED

/var/log/proton/nsxapi.log
YYYY-MM-DDTHH:MM:SS.   INFO LogicalSwitchStateOperationScheduler1 LogicalSwitchStateServiceImpl 77562 SWITCHING [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Updated LogicalSwitchState: LogicalSwitchState [id =LogicalSwitchState/########-####-####-####-############, revision = 292457, logicalSwitchName = ####-####-##### , stateStatus = SUCCESS, switchType = DEFAULT, logicalSwitchRevison = 1, portGroupStateRevision = 1, #vdsIdPortGroupStateMap = 1, #networkIdFolderStateMap = 0, nextRealizationTime = 0]

    NB:  If the issue continues after the host(s) reconnects, the workaround described under the 'Resolution' section below can be applied.

Environment

VMware vCenter Server

VMware NSX

Cause

This issue is triggered when one or more ESXi hosts are disconnected from vCenter Server. In such cases, vCenter is unable to complete the ReconfigureNsxPortgroups operation and returns a DvsOperationBulkFault error.

Resolution

This issue is addressed in VMware vCenter Server 8.0.3 Patch 07.

Workaround

If the issue continues after the host(s) reconnects, the workaround below can be applied:

NSX UI > Networking > Segments:

  • Add a description to the impacted segment and save the changes.
Powered by Wolken Software