![NetApp HCI Manual Download Page 236](http://html1.mh-extra.com/html/netapp/hci/hci_manual_1669957236.webp)
{
"cluster": "domain-1"
}
g. Click
Execute
to run a health check on the cluster.
The code 200 response gives a
"resourceLink"
URL with the task ID appended that is needed to
confirm the health check results.
{
"resourceLink":
"https://10.117.150.84/vcenter/1/compute/tasks/[This is the task ID
for health check task results]",
"serviceName": "vcenter-v2-svc",
"taskId": "ab12c345-06f7-42d7-b87c-7x64x56x321x",
"taskName": "VCenter service health checks"
}
h. Copy the task ID portion of the
"resourceLink"
URL to verify the task result.
3. Verify the result of the health checks:
a. Return to the compute service REST API UI on the management node:
https://[management node IP]/vcenter/1/
b. Click
GET /compute/tasks/{task_id}
.
c. Click
Try it out
.
d. Enter the task ID portion of the
"resourceLink"
URL from the
POST /compute
/{CONTROLLER_ID}/health-checks
code 200 response in the
task_id
parameter field.
e. Click
Execute
.
f. If the
status
returned indicates that there were problems regarding compute node health, do the
following:
i. Go to the specific KB article (
KbLink
) listed for each issue or perform the specified remedy.
ii. If a KB is specified, complete the process described in the relevant KB article.
iii. After you have resolved cluster issues, run
POST /compute/{CONTROLLER_ID}/health-checks
again (see step 2).
If health checks complete without issues, the response code 200 indicates a successful result.
Compute node health checks made by the service
Compute health checks, whether performed by HCC or API methods, make the following checks per node.
Depending on your environment, some of these checks might be skipped. You should re-run health checks
after resolving any detected issues.
Summary of Contents for HCI
Page 95: ...NetApp HCI Resources page...
Page 308: ......