Actions140
- Application Load Balancer Actions
- Contract Actions
- Datacenter Actions
- Firewall Rule Actions
- Image Actions
- IP Block Actions
- Kubernetes Cluster Actions
- LAN Actions
- Load Balancer Actions
- Location Actions
- NAT Gateway Actions
- Network Load Balancer Actions
- NIC Actions
- Node Pool Actions
- Private Cross-Connect Actions
- Request Actions
- Security Group Actions
- Server Actions
- Snapshot Actions
- Target Group Actions
- Volume Actions
NIC → Update
AI-generatedSummary
Update a specific NIC (Network Interface Card) of a server within a datacenter by modifying its LAN connection and optionally its name, DHCP status, and assigned IP addresses.
Inputs
- Datacenter ID (required) — The unique identifier of the datacenter containing the server.
- Server ID (required) — The unique identifier of the server to which the NIC is attached.
- NIC ID (required) — The unique identifier of the NIC to update.
- LAN (required) — The LAN ID to which the NIC is connected, must be 1 or greater.
- Additional Fields — Optional fields to update: the NIC's name, whether DHCP is enabled, and a comma-separated list of IP addresses to assign to the NIC.
- Include Request Status — Whether to include async operation tracking details such as request ID and status URL in the output.
- Include Response Headers — Whether to include HTTP response headers and status code alongside the response body in the output.
Output shape
a single object representing the updated NIC resource from the IONOS Cloud API
The response may include additional request tracking metadata or HTTP headers if the respective options are enabled. The output reflects the API response to the update operation on the specified NIC.
Examples
Example 1: Update NIC assigning it to a new LAN, renaming it, and disabling DHCP
Set Datacenter ID, Server ID, NIC ID, LAN to the desired value, specify 'Name' and set DHCP to false in Additional Fields.