Adding a secondary IP address to an existing virtual network interface in the console

To add a secondary IP address to an existing virtual network interface, follow these steps.

1. From your browser, open the IBM Cloud console and log in to your account.
2. Select the Navigation menu , then click Infrastructure > Network > Virtual network interfaces.
3. Click the name of the virtual network interface that you want to add a secondary IP address to in the Virtual network interfaces for VPC table.
4. Click the Attached resources tab.
5. In the Secondary IPs section, click Attach.
6. In the Attach secondary IPs panel that appears, specify whether you want an address created for you, or if you want to type in your own address.
   • If you select to have an address created for you, specify the quantity of addresses you want to create.
   • If you select to specify your own address, you can select from a list of existing IP addresses, or type in an IP address in the field provided.
7. Select whether you want auto-release enabled for the secondary IP addresses.
8. Click Attach to attach the secondary IP address to your virtual network interface, or click Cancel.

Adding a secondary IP address to an existing virtual network interface from the CLI

Before you begin, set up your CLI environment.

export IBMCLOUD_IS_FEATURE_VNI_PHASE_II=true

Then run the following command:

ibmcloud is virtual-network-interface-update VIRTUAL_NETWORK_INTERFACE --name NEW_NAME [--allow-ip-spoofing false | true] [--auto-delete false | true] [--enable-infrastructure-nat false | true] [--output JSON] [-q, --quiet]

Where:

VIRTUAL_NETWORK_INTERFACE

ID or name of the virtual network interface.

--name

Name of the virtual network interface.

--allow-ip-spoofing

Indicates whether source IP spoofing is allowed on this interface. If false, source IP spoofing is prevented on this interface. If true, source IP spoofing is allowed on this interface. One of: false, true.

--auto-delete

Indicates whether this virtual network interface will be automatically deleted when target is deleted. Must be false if the virtual network interface is unbound. One of: false, true.

--enable-infrastructure-nat

If true, the VPC infrastructure performs any needed NAT operations. If false, packets are passed unchanged to/from the network interface, allowing the workload to perform any needed NAT operations. One of: false, true.

--output

Specify output format, only JSON is supported. One of: JSON.

-q, --quiet

Suppress verbose output.

Attaching a secondary IP to an existing virtual network interface from the API

1. Set up your API environment with the right variables.

2. Store any additional variables to be used in the API commands; for example:

   • version (string): The API version, in format YYYY-MM-DD.
   • virtual_network_interface_id (string): The virtual network interface identifier.
   • secondary_ip (array): The information about the secondary IP that you want to attach.

3. When all variables are initiated, add the secondary IP to the existing virtual network interface:

   curl -X PATCH \
   "$vpc_api_endpoint/v1/virtual_network_interfaces/$virtual_network_interface_id?version=$version&generation=2" \
   -H "Authorization: Bearer $iam_token" \
   -d '{
         "name": "my-virtual-network-interface-updated"
   }'
   

Adding a secondary IP to an existing virtual network interface with Terraform

The following example adds a secondary IP to an existing virtual network interface by using Terraform:

resource "ibm_is_virtual_network_interface" "my_virtual_network_interface_instance" {
  allow_ip_spoofing = true
  auto_delete = false
  enable_infrastructure_nat = true
  name = "my-virtual-network-interface-2"
  subnet = ibm_is_subnet.my_subnet.id
}