The "Logical Switch State has failed" alert is active in Aria Operations but the logical switch is functioning in NSX
Aria Operations 8.x
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.
To review the API response that Aria Operations is evaluating:
u=<username>
<username>
with the collection user from the NSX adapter configurationp=$(systemd-ask-password)
Review the response for any logical switches where the state is failed to verify the alert is valid.
The API command provided 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.
Additional symptoms:
-The Logical switch was reported in failed state on aria operations after upgrading NSX from 3.2.3 to 4.1.2.5.
- After running api call to the logical switches we observed that two logical switches were in failed state. Despite this, VMs operating on the affected segment continued to function without any network connectivity issues.
Workaround:
-As a workaround we edited the affected segment and added a description to the same. The changes made were then saved. This helps in syncing the logical switches current state.