Delete a CIFS server configuration
You can use this workflow to delete a CIFS server configuration for an existing Cloud Volumes ONTAP system.
Choose the correct workflow depending on the type of the Cloud Volumes ONTAP deployment:
Delete CIFS server configuration for a single node
You can use this workflow to delete a CIFS server configuration for a single node system.
Step 1. Select the system
Perform the workflow Get systems and choose the publicId
value of the system for the workingEnvironmentId
path parameter.
Step 2. Delete the CIFS configurations
You can issue the REST API call to delete CIFS configurations.
This REST API call uses the following method and endpoint.
HTTP method | Path |
---|---|
POST |
/occm/api/vsa/working-environments/{workingEnvironmentId}/delete-cifs |
curl --request POST \
--location "https://api.bluexp.netapp.com/occm/api/vsa/working-environments/<WORKING_ENV_ID>/delete-cifs" \
--header "Content-Type: application/json" \
--header "x-agent-id: <AGENT_ID>" \
--header "Authorization: Bearer <ACCESS_TOKEN>"
The JSON input example includes the minimum list of parameters.
Parameter | Type | Required | Description |
---|---|---|---|
|
Path |
Yes |
Identifies the system ID |
{
"activeDirectoryUsername": "string",
"activeDirectoryPassword": "string",
"svmName": "string"
}
None.
Delete CIFS server configuration for a high availability pair
You can use this workflow to delete a CIFS server configuration for an HA system.
Step 1. Select the system
Perform the workflow Get systems and choose the publicId
value of the system for the workingEnvironmentId
path parameter.
Step 2. Delete the CIFS configurations
You can issue a REST API call to delete CIFS configurations.
This REST API call uses the following method and endpoint.
HTTP method | Path |
---|---|
POST |
/occm/api/aws/ha/working-environments/{workingEnvironmentId}/delete-cifs |
curl --location
--request POST 'https://api.bluexp.netapp.com/occm/api/aws/ha/working-environments/<WORKING_ENV_ID>/delete-cifs'
--header 'Content-Type: application/json'
--header 'x-agent-id: <AGENT_ID>'
--header 'Authorization: Bearer <ACCESS_TOKEN>'
The JSON input example includes the minimum list of parameters.
Parameter | Type | Required | Description |
---|---|---|---|
|
Path |
Yes |
Identifies the system ID |
{
"activeDirectoryUsername": "string",
"activeDirectoryPassword": "string",
"svmName": "string"
}
None.