Unbinding NICs from a BMS
Function
This API is used to unbind one or more NICs from a BMS.
The primary NIC of a BMS has routing rules configured and cannot be unbound.
URI
POST /v1/{project_id}/baremetalservers/{server_id}/nics/delete
Parameter |
Mandatory |
Description |
---|---|---|
project_id |
Yes |
Specifies the project ID. For details about how to obtain the project ID, see Obtaining a Project ID. |
server_id |
Yes |
Specifies the BMS ID. You can obtain the BMS ID from the BMS console or by calling the Querying BMSs (Discarded). |
Request Parameters
Parameter |
Mandatory |
Type |
Description |
---|---|---|---|
nics |
Yes |
Array of objects |
Specifies the NICs to be unbound. For details, see Table 3. |
Example Request
{ "nics": [ { "id": "d32019d3-bc6e-4319-9c1d-6722fc136a23" } ] }
Response Parameters
Parameter |
Type |
Description |
---|---|---|
job_id |
String |
Specifies the task ID returned after a task command is issued. The task ID can be used to query the execution status of the task. For details about how to query the task execution status based on job_id, see Querying Task Statuses. |
Parameter |
Type |
Description |
---|---|---|
error |
Dictionary data structure |
Specifies the error returned when a task submission encounters an exception. For details, see Table 6. |
Example Response
- Normal response
1 2 3
{ "job_id": "70a599e0-31e7-49b7-b260-868f441e862b" }
Returned Values
Returned Values |
Description |
---|---|
200 |
The request has been successfully processed. |
For details about other returned values, see Status Codes.
Error Codes
See Error Codes.
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot