Configuring the Instance OS for a Secondary VNIC
On Compute Cloud@Customer, after you create a secondary VNIC, log in to the instance OS and configure the OS to use the new VNIC.
For Linux and Microsoft Windows, you can use utilities and scripts that are provided by Oracle. The scripts use information from the instance metadata. See Retrieving Instance Metadata from Within the Instance for instructions about how to view that data on the instance OS, including how to show the VNIC data.
Linux Instance OS Configuration
Use the oci-network-config utility to perform the OS configuration required for secondary VNICs on instances that run Oracle Linux.
Microsoft Windows Instance OS Configuration
You must configure the secondary VNIC within the OS. You can configure the secondary VNIC manually in the Microsoft Windows OS, or create a PowerShell script.
Ensure that the script includes these actions:
- Check if the network interface has an IP address and a default route.
- Enable the OS to recognize the secondary VNIC, the script must overwrite the IP address and default route with static settings (which effectively disables DHCP). The script should prompt you with a choice: to overwrite with the static settings, or exit.
Overall Process to Add a Secondary VNIC
- Create and attach a secondary VNIC to the instance. Keep the VNIC's OCID handy so you can provide it later when you run the configuration script.
- Connect to the instance with Remote Desktop.
- Run your script as an administrator.
Oracle Solaris Instance OS Configuration
Use the ipadm command to configure network interfaces persistently.