Start MetroCluster diagnostics or set up a periodic diagnostic schedule
- PDF of this doc site
Collection of separate PDF docs
Creating your file...
POST /cluster/metrocluster/diagnostics
Introduced In: 9.8
Start a MetroCluster diagnostic operation or set up a schedule for the diagnostics to be run periodically.
Parameters
Name | Type | In | Required | Description |
---|---|---|---|---|
schedule |
integer |
query |
False |
Shows the minutes of every hour when a job runs. Setting this parameter schedules the periodic job to be run to perform MetroCluster diagnostic. |
return_timeout |
integer |
query |
False |
The number of seconds to allow the call to execute before returning. When doing a POST, PATCH, or DELETE operation on a single record, the default is 0 seconds. This means that if an asynchronous operation is started, the server immediately returns HTTP code 202 (Accepted) along with a link to the job. If a non-zero value is specified for POST, PATCH, or DELETE operations, ONTAP waits that length of time to see if the job completes so it can return something other than 202.
|
Response
Status: 202, Accepted
Name | Type | Description |
---|---|---|
job |
Example response
{
"job": {
"_links": {
"self": {
"href": "/api/resourcelink"
}
},
"uuid": "string"
}
}
Headers
Name | Description | Type |
---|---|---|
Location |
Useful for tracking the resource location |
string |
Error
Status: Default
ONTAP Error Response Codes
Error Code | Description |
---|---|
2425734 |
An internal error occurred. Wait a few minutes, and try the operation again. For further assistance, contact technical support. |
2427132 |
MetroCluster is not configured on this cluster. |
2432833 |
Operation is already running. |
2432852 |
MetroCluster diagnostics start |
2432853 |
MetroCluster diagnostics job scheduled |
2432854 |
MetroCluster diagnostics complete |
2432855 |
MetroCluster diagnostics operation failed. Use the REST API GET method on "/api/cluster/metrocluster/operations?type=check&fields=*" for more information. |