Configuring Hyper-V for Pexip Infinity
Version 14.1 of Pexip Infinity supports Microsoft Hyper-V in the form of Microsoft Hyper-V Server 2012 and later, or Windows Server 2012 and later.
You must have a suitable Hyper‑V environment already installed.
All host servers must be synchronized with accurate time before you install the Pexip Infinity Management Node or Conferencing Nodes on them.
- NTP must also be enabled on the Management Node VM before you deploy any Conferencing Nodes (this is done during installation of the Management Node).
- We strongly recommend that you configure at least three distinct NTP servers or NTP server pools on all your host servers and the Management Node itself. This will ensure that log entries from all nodes are properly synchronized.
In Hyper-V, all time synchronization is configured using the Active Domain Controller. You must ensure that all VMs and host servers are using the same time. Consult your Hyper-V documentation for information on how to do this in your environment.
We recommend using a static MAC address for the virtual machine hosting your Management Node. This will ensure that the licenses on your Management Node do not become invalid if, for example, the node reboots and comes up on a different physical blade.
You must create an external virtual switch on the host server to allow VMs on that host to access external network resources. To do this:
- Log in to Hyper-V.
- Right-click on the host server and select
The Virtual Switch Manager window opens.
- Select External and then .
- Enter a Name for the switch.
- Either accept the default options, or select the options appropriate for your environment.
By default, virtual machines deployed using Hyper-V are configured to restart automatically if they were running when the host server was shut down or powered off. We recommend that you leave this setting as is for the Management Node and all Conferencing Nodes.
We strongly recommend that you disable processor compatibility mode on all Hyper-V Conferencing Node virtual machines. If processor compatibility mode is enabled, the Conferencing Node may assume it is running on older hardware, and may stop working, with the message CPU instruction set is not supported; system will be placed in maintenance mode.
For more information, see https://technet.microsoft.com/en-us/library/dn859550.aspx.
To look at the steps taken in setting up an example lab deployment of a Conferencing Node in Microsoft Hyper-V, see http://www.graham-walsh.com/2016/02/setting-up-pexip-infinity-with-microsoft-hyper-v-server-2012/.