ComputeContainer removeNetworkInterface request

Description

This API removes a virtual Network Interface Card (NIC) from a compute container. It supports the VMware hypervisor and Microsoft Windows and Red Hat Linux guest operating systems.

The following constraints apply to this API:

You can remove NICs only from virtual machines (VMs). You cannot remove NICs from physical servers.
You can remove NICs only from VMs that have been commissioned via BMC Cloud Lifecycle Management.
The VM must be running. You cannot remove a NIC from a VM that is stopped.
You must not remove the NIC from a management network.
The API does not validate the input parameters that it receives. You must ensure that all input parameters are correct and that the NIC that you specify is not a management NIC.
If the NIC belongs to a virtual firewall or load balancer pool, you must remove the NIC from those pools before removing it from the compute container because this API does not remove NICs from those pools.

If the request fails for a NIC that has a static IP address, the static IP address associated with the NIC is not released to the resource pool.

API stability classification

Unstable

Availability

Available in BMC Cloud Lifecycle Management version 2.1 SP2 and later

API overview

HTTP request message

Query string parameters

This API does not use query string parameters.

Request message headers

This API uses only common request headers listed in HTTP-request-and-response-headers.

Request message body

This API uses the following objects in the request message body JSON:

The following table lists the input parameters to include in the operationParams object:

HTTP response message

Response message headers

This API uses only common response headers listed in HTTP-request-and-response-headers.

Response message body

The response message body contains a Task object.

Unknown macro: confluence_report-block.