After you create a virtual appliance, by default, all its virtual ports are connected to vSwitch0 on the ESXi host. The vSwitch0 virtual switch should include:
The Management Network, which includes the physical management interface for the ESXi host (VMkernel Port)
The Virtual Machine (VM Network) port group, which includes the virtual appliances
The virtual NDR Console has two interfaces. The ether0 interface is used for management. The optional ether1 interface can be used to set up a multi-node cluster. Connect the ether0 interface to the management network. Connect the ether1 interface to a private switch that is only used for internal traffic for the cluster
By default, one NIC is associated with the OVA. Connect it to the ESXi network that can provide an IP address via DHCP when it boots.
If you plan to set up a cluster, add a secondary NIC to the virtual machine. Connect the secondary NIC to a private router within VCloud and add a static IP address manually in the private IP space. This traffic is unencrypted.
Task list for the virtual NDR network
The following table lists network tasks for a virtual NDR Console appliance.
Make sure the instance is shut down.
Create a new virtual port group on a vSphere standard switch that is bound to a physical adapter on the ESXi server. See Configuring a virtual NDR Console network.
Move the adapter on the virtual Network Detection and Response Console appliance that is associated with the ether1 interface from the VM Network port group to the new virtual port group. See Configuring a virtual NDR Console network.
Start the instance and configure basic network settings as described in Performing the initial NDR Console configuration.
Note
You can create sub-interfaces of the network ports of a virtual NDR Console appliance based on VLAN or CIDR. However, this is beyond the scope of this document.
Important
The navigation instructions and user interface may vary based on your version of VMware ESXi, vSphere Web Client, and VMware vCenter Server.