How Do I Remediate the Health of a Workspace ONE Access Cluster

vRealize Suite Lifecycle Manager runs a notification for Workspace ONE Access cluster health every hour and provides its status as healthy or critical. If critical, you can run remediation as a Day 2 action using the Deployments Controller API.

Before you remediate cluster health:

• Verify that all general Day 2 prerequisites have been satisfied. See Performing Day 2 operations using vRealize Suite Lifecycle Manager APIs.

As a vRealize Suite Lifecycle Manager administrator, you remediate the health of a Workspace ONE Access cluster by performing the following request.

curl -X POST\
  '$url/lcm/lcops/api/v2/environments/globalenvironment/products/vidm/power-on' \  
  -H 'Authorization: Basic YWRtaW5AbG9jYWw6VGhpc0lzUGFzc3dvcmQ=' \
  -H 'Content-Type: application/json'
  -d '{
     "performRebootIfRequired": true
} | jq "."

Note:

• Remediation only applies to the Workspace ONE Access nodes installed in your environment. For Workspace ONE Access, the environment ID is globalenvironment by design.
• If "performRebootIfRequired": true, vRealize Suite Lifecycle Manager reboots the Workspace ONE Access nodes as needed. If you do not want to reboot during remediation, you can use "performRebootIfRequired": false. However, if vRealize Suite Lifecycle Manager determines that a reboot is necessary, the request will fail with a message to use "performRebootIfRequired": true.

A snippet from a successful response shows the request ID that you can use to check the status of the request through completion.

{
    "requestId": "1dac194a-6e1f-4772-a97d-af300ad5086c"
}