This article describes how to add an Additional NIC to an existing, deployed Cloud Server on a Network Domain.


  1. Only the Primary Administrator or a Sub-Administrator with the Network role can add an additional NIC to a Cloud Server.
  2. Additional NICs can only be added to a Cloud Server in MCP 2.0 Data Center locations. For an overview of the difference between MCP 1.0 and MCP 1.0, see Understanding MCP 1.0 vs. MCP 2.0 Data Center Locations.
  3. The Cloud Server must be in a Stopped state.
  4. For details on "Exclusively Reserved" addresses that may not be assigned to a NIC, see Introduction to IP Addressing in MCP 2.0.
  5. You can not add an additional NIC to a Cloud Server if the Cloud Server is the Source Server in a Consistency Group. See What Happens to a Source Server when it is added to a Consistency Group?

Content / Solution:

  1. From the Home page, select the Data Center where the Cloud Server to which you want to add an additional NIC is located:

  2. The Data Center dashboard will be displayed. Select the Network Domain where the Server on which you want to add an additional NIC is located:

  3. The Network Domain dashboard will be displayed. Select the (stopped) Cloud Server on which you want to add a NIC:

  4. The Server dashboard will be displayed. Click on the Networking tab, then click on the Actions button and select Add NIC from the drop-down menu:

    Note: The Server must be in a stopped state in order to add an additional NIC. If the Server is running, the Add NIC button will be unavailable and will display an error message: 

  5. The Add NIC / Add Server to VLAN dialog will be displayed:

  6. Fill out the form with the desired information:

    • VLAN - Select the VLAN that you want to add as an Additional NIC from the drop-down menu
    • IPv4 Address - Select the IPv4 Address that you want to assign to the NIC. For more information, see Introduction to IP Addressing in MCP 2.0
      • Note: If you select an IPv4 Address that is in use by another cloud resource, the system will ask you to confirm your choice. Using an IP Address that is in use by another cloud resource may cause an IP conflict.
      • Note: If you select an IPv4 Address that is exclusively reserved, you will not be able to add the NIC to the Server:
    • NIC Type - CloudControl supports five different "Network Adapters" (also referred to a "NIC Type") as defined by VMware in their KB article Choosing a network adapter for your virtual machine. These adapters define how the NIC will appear to the Guest Operating System. The five available types are:
      • E1000 - An emulated version of the Intel 82545EM Gigabit Ethernet NIC. The advantage of this NIC is that it will work even if VMware Tools is not running.
      • E1000e - This feature emulates a newer model of Intel Gigabit NIC (number 82574) in the virtual hardware. This is known as the "e1000e" vNIC. e1000e is available only on hardware version 8 (and newer) virtual machines in vSphere 5. It is the default vNIC for Windows 8 and newer (Windows) guest operating systems. For Linux guests, e1000e is not available from the UI (e1000, flexiblevmxnet, enhancedvmxnet, and vmxnet3 are available for Linux).
      • VMXNET2/Enhanced - The VMXNET 2 adapter is based on the VMXNET adapter but provides some high-performance features commonly used on modern networks, such as jumbo frames and hardware offloads. This virtual network adapter is available only for some guest operating systems on ESXi/ESX 3.5 and later. Because operating system vendors do not provide built-in drivers for this card, you must install VMware Tools to have a driver for the VMXNET 2 network adapter available.
      • VMXNET3 - VMware's paravirtualized NIC designed for ideal performance. It provides better performance but does not work unless VMware Tools is running. This means that if VMware Tools stops running, all network connectivity to and from the NIC will be lost until VMware Tools is restored.
      • PCNET32/Flexible - The Flexible network adapter identifies itself as a Vlance adapter when a virtual machine boots but initializes itself and functions as either a Vlance or a VMXNET adapter, depending on which driver initializes it. With VMware Tools installed, the VMXNET driver changes the Vlance adapter to the higher performance VMXNET adapter.

        Important Note

        Availability of these NICs varies by Operating System. For more details, see What Operating Systems are Currently Supported on CloudControl?

    • NIC State - Choose whether you want the NIC to be Connected, or Disconnected. For more information on NIC Connectivity, see Introduction to Cloud Server NICs in MCP 2.0

  7. Once the Add NIC / Add Server to VLAN form has been filled out, click the Add NIC button:

  8. The system will display a message indicating that the operation is in progress:


  9. The system will display the progress of the operation in the Status section of the Server dashboard:

    Note: This will take several minutes

  10. Once complete, the system will display a success message:

  11. You must now log into your Cloud Server, identify the NIC, and provision it within the Guest Operating System as described in:

    How do I Configure an Additional Virtual NIC on a Windows Server

    How do I Configure an Additional Virtual NIC on a Linux Server

    The system will show the IP address as shown below, but it is not configured on the Cloud Server until you perform those steps.

    Note: The Star icon  indicates which VLAN is the Primary NIC.