Creating and Attaching a Secondary VNIC
On Compute Cloud@Customer, you can add more VNICs to an instance.
The number of secondary VNICs that you can add to an instance depends on the shape of the instance. See Compute Shapes.
After you attach a secondary VNIC, log onto the instance to configure the instance OS to use the new interface. See Configuring the Instance OS for a Secondary VNIC.
Avoid entering confidential information in names and tags.
- In the Compute Cloud@Customer Console navigation menu, click Compute, then click Instances.
- At the top of the page, select the compartment that contains the instance to which you want to add a secondary VNIC.
-
Click the name of the instance.
-
Under Resources, click Attached VNICs.
The primary VNIC and any secondary VNICs attached to the instance are displayed.
-
Click Create VNIC Attachment.
-
In the Subnet section of the Create VNIC Attachment dialog box, specify the subnet to use for the VNIC. You might need to select a different compartment to find the VCN and subnet that you want.
Note
Specifying the same subnet for this VNIC that's specified for another VNIC for this instance can introduce asymmetric routing.
Instead of creating a VNIC in the same subnet as an existing VNIC for this instance, consider creating a secondary private IP address for the existing VNIC that's in this subnet.
-
Specify whether to disable source/destination checks.
By default, a VNIC looks at the source and destination listed in the header of each network packet. If the VNIC isn't the source or destination, then the packet is dropped.
If the VNIC needs to forward traffic (for example, if the VNIC needs to perform Network Address Translation), check the box to disable this source/destination check.
-
If you selected a public subnet, you can specify whether to automatically assign a public IPv4 address object to the VNIC private IP address object.
-
(Optional) Specify the following private IP information.
-
Private IP Address: An address that's within the CIDR block range assigned to the subnet and not already in use. If you don't enter an address, an IP address is automatically assigned.
-
Hostname: A hostname to be used for DNS within the cloud network. This option is available only if the VCN and subnet both have DNS labels. The hostname can be up to 63 letters, numbers, and hyphens. No spaces are allowed.
-
-
(Optional) Add this VNIC to an NSG.
By default, the new VNIC isn't attached to any NSG. Check the box labeled Enable Network Security Groups to add this VNIC to one or more NSGs.
-
Select an NSG from the drop-down list. You might need to change the compartment to find the NSG you want.
-
Click Add Another NSG to attach to another NSG.
-
To remove an NSG from the list, click the trash can to the right of that NSG. To remove the last NSG or all NSGs, clear the Enable Network Security Groups box.
See Controlling Traffic with Network Security Groups for information about NSGs.
-
-
Click Create Attachment.
The secondary VNIC is created and then displayed on the Attached VNICs list for the instance.
-
Configure the instance OS to use the secondary VNIC. See Configuring the Instance OS for a Secondary VNIC.
Use the oci compute instance attach-vnics command and required parameters to create a secondary VNIC and attaches it to the specified instance. You can specify either –subnet-id or –vlan-id for this create request, but not both.
oci compute instance attach-vnic [OPTIONS]For a complete list of CLI commands, flags, and options, see the Command Line Reference.
Use the AttachVnic operation to create a secondary VNIC and attaches it to the specified instance.
For information about using the API and signing requests, see REST APIs and Security Credentials. For information about SDKs, see Software Development Kits and Command Line Interface.