"Logical Switch State has failed" alert is active but the logical switch is functioning in NSX

Products

• VCF Operations/Automation (formerly VMware Aria Suite)

Issue/Introduction

The "Logical Switch State has failed" alert is active in Aria Operations but the logical switch is functioning in NSX

Environment

Aria Operations 8.x

Cause

Aria Operations collects the value of the logical switch state from the NSX API via the configured NSX adapter. If the API is reporting the logical switch state is failed, the cause will need to be investigated by the NSX team.

Resolution

To review the API response that Aria Operations is evaluating:

1. Log in as root to the Aria Operations node or cloud proxy where the NSX adapter is collected and run the following commands
   
   
2. u=<username>
   
   Note: Replace <username> with the collection user from the NSX adapter configuration
   
   
3. p=$(systemd-ask-password)
   
   Note: Provide the password for the collection user from the NSX adapter configuration
   
   
4. curl -k https://<nsx_manager_fqdn>/api/v1/logical-switches/state --user "${u}:${p}"

Review the response for any logical switches where the state is failed to verify the alert is valid.

Additional Information

Additional KBs that may help resolve the underlying issue in NSX:

• vROPs alarm: Logical Switch State has failed
• Logical Switches in failed state upon upgrade to VMware NSX 4.1.x
• Logical Switch State has failed alarm in vROps with no stale vDS entries identified

The API command provided in this KB is for NSX environments that have not converted to Policy Mode. If using Policy Mode, the correct API to use is:

/policy/api/v1/infra/tier-1s/{tier-1-id}/segments/{segments-id}/state/policy/api/v1/infra/segments/{segments-id}/state

where tier-1-id and segments-id would need to be provided accordingly.

Workaround:

Edit the affected segment in NSX and add a description then save the changes. This helps in syncing the logical switch's current state.