Users Guide

28 Configuring the Virtual Network
• VM networks (as needed)
• VLANs or separate network fabrics must be used to segregate network
traffic
NOTE: Unlike other Windows Server 2008 clustered applications, clustered VMs do
not utilize the public IP address; instead, they maintain their own addresses for
each virtual network adapter in each guest operating system. The public address is
used to manage the cluster.
NOTE: VLAN tagging is available on a per-VM connection basis that is configured
on each network adapter of each VM, and for the parent partition that is configured
in the Virtual Network Manager for each virtual network. Third-party software may
be used to tag all other traffic presented exclusively to the parent partition.
Switch-based tagging may also be used to tag traffic from all physical
network adapters.
For special iSCSI network configuration best practices, see the Dell Storage
Solutions Guide for Microsoft Hyper-V
available on the Dell Support website at
support.dell.com .
The following sections provide Dell-specific configuration information for
each of the four virtual network configurations.
NOTE: These steps are not intended to be used serially, but rather they must be
used as needed to implement each of the different virtual network types.
Private Virtual Network
Private virtual networks are completely isolated from the parent partition and
the external network. No changes are made to either environment once you
complete the general installation and naming steps mentioned in the
previous sections.
Internal Virtual Network
The following steps are the best practice recommendations for configuring
the internal virtual network configurations within Hyper-V. These steps
assume that you have already performed the general installation and naming
steps mentioned in the previous sections.