For Hyper-V environments, when not configuring network redundancy for L-Servers on blade servers, or when using servers other than blade servers, the functionality for VM guests to connect to a virtual network that has been created in advance is only provided if the NICs of those VM guests are configured with IP addresses and VLAN IDs for that virtual network.
When manually configuring a virtual network in advance while also using server virtualization software other than Hyper-V with the same manager, configure names for the virtual switch, virtual network, and virtual bridge of Hyper-V that are different from those configured on the other server virtualization software.
Preparations
Create the virtual network
Create a virtual network with the same name (including the use of uppercase and lowercase) on all VM hosts in the cluster.
This virtual network enables VM guests to migrate between VM hosts. When using System Center 2012 Virtual Machine Manager or later versions as VM management software, only "External" can be used for the type of virtual network which is the connection destination for the VM guest.
For details on creating external virtual networks, refer to the System Center Virtual Machine Manager help.
Configure the virtual network communication settings
Perform configuration of the LAN switch blade so that virtual networks with the same name can communicate with each other using tagged VLAN communication.
In the server resource tree of the ROR console, right-click the relevant LAN switch blade, and then select [Modify]-[Network Settings] in the displayed menu.
The [VLAN Settings] dialog is displayed.
Configure the VLAN settings.
Definitions of Correspondences Between Virtual Networks and VLAN IDs
The following Resource Orchestrator definition file contains correspondences between virtual networks and VLAN IDs.
Format of the Definition File
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
vnetwork_hyperv.rcxprop
[Windows Manager]
UTF-8
[Windows Manager]
CR/LF
Define each line of the definition file as follows.
"Name_of_the_virtual_network_created_on_the_VM_host"=VLAN ID[,VLAN ID...]Specify a value between 1 and 4094 for each VLAN ID. When specifying a sequence of numbers, include a hyphen ("-"), as in "1-4094".
Example
"Network A"=10
"Network B"=21,22,23
"Network C"=100-200,300-400,500
Any spaces before or after an equal sign ("=") or a comma (",") will be ignored.
Ensure that you specify the name of the virtual network using exactly the same notation as on the VM host, including the use of uppercase and lowercase.
Save the file in the UTF-8 character code.
When there are multiple lines with the same virtual network name, all of the lines are valid.
When there are multiple lines with the same VLAN ID but different virtual network names, the line closest to the top of the file is treated as valid, and all lower lines are ignored.
Example
"Network D"=11
"Network D"=12 (*1)
"Network E"=11,15 (*2)
*1: These two lines could also be written as one line, as in '"Network D"=11,12'.
*2: "11" is ignored.
Functionality is provided for connecting networks created on XenServer to virtual NICs.
Manually configure the networks on XenServer in advance. To connect networks created on XenServer to
virtual NICs, use a different VLAN ID for each XenServer network.
Preparations
Create XenServer networks
It is necessary to create networks on VM hosts for L-Servers to connect to.
Create a network with the same name (including the use of uppercase and lowercase) on all VM hosts in the cluster.
This virtual network enables VM guests to migrate between VM hosts.
When configuring a XenServer network while also using server virtualization software other than XenServer with the same manager, configure names for the virtual switch, virtual network, and virtual bridge of XenServer that are different from those configured on the other server virtualization software.
For how to create networks on XenServer, refer to the manuals for Citrix XenServer.
Configure the XenServer network communication settings
Perform configuration of the LAN switch blade so that networks created in XenServer with the same name can communicate with each other using tagged VLAN communication.
In the server resource tree of the ROR console, right-click the relevant LAN switch blade, and then select [Modify]-[Network Settings] in the displayed menu.
The [VLAN Settings] dialog is displayed.
Configure the VLAN settings.
Definitions of Correspondences Between Networks Created on XenServer and VLAN IDs
The following Resource Orchestrator definition file contains correspondences between networks created on XenServer and VLAN IDs.
Format of the Definition File
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
vnetwork_citrixxen.rcxprop
[Windows Manager]
UTF-8
[Windows Manager]
CR/LF
Define each line of the definition file as follows.
"Name_of_the_virtual_network_created_on_XenServer"=VLAN ID[,VLAN ID...]Specify a value between 1 and 4094 for each VLAN ID. When specifying a sequence of numbers, include a hyphen ("-"), as in "1-4094".
Example
"Network A"=10
"Network B"=21,22,23
"Network C"=100-200,300-400,500
Any spaces before or after an equal sign ("=") or a comma (",") will be ignored.
Ensure that you specify the name of the virtual network using exactly the same notation as on the VM host, including the use of uppercase and lowercase.
Save the file in the UTF-8 character code.
When there are multiple lines with the same virtual network name, all of the lines are valid.
When there are multiple lines with the same VLAN ID but different virtual network names, the line closest to the top of the file is treated as valid, and all lower lines are ignored.
Example
"Network D"=11
"Network D"=12 (*1)
"Network E"=11,15 (*2)
*1: These two lines could also be written as one line, as in '"Network D"=11,12'.
*2: "11" is ignored.