Manually deploying a Conferencing Node on a Hyper-V host
To manually deploy a new Conferencing Node on to a Hyper-V host:
- Go to and select .
- From the Deployment type field, select Manual (Hyper-V 2012).
- Select .
-
You are now asked to provide information regarding the CPUs and memory of the Conferencing Node VM, by completing the following fields:
Option Description Number of virtual CPUs to assign Enter the number of CPUs to assign to the Conferencing Node. We do not recommend that you assign more virtual CPUs than there are physical cores on a single processor on the host server. For example, if the host server has 2 processors each with 8 physical cores, we recommend that you assign no more than 8 virtual CPUs. System memory (in megabytes) to assign Enter the amount of RAM (in megabytes) to assign to the Conferencing Node. The number entered must be a multiple of 4.
We recommend 1024 MB (1 GB) RAM for each CPU.
- Select .
-
You are now asked to provide the network configuration to be applied to the Conferencing Node, by completing the following fields:
Option Description Name Enter the name that will be used to refer to this Conferencing Node in the Pexip Infinity Administrator interface. Description An optional field where you can provide more information about the Conferencing Node. IP address Enter the IP address to be assigned to this Conferencing Node when it is created. Network mask Enter the IP network mask to be assigned to this Conferencing Node. Gateway IP address Enter the IP address of the default gateway to be assigned to this Conferencing Node. Hostname Domain
Enter the hostname and domain to be assigned to this Conferencing Node. Each Conferencing Node and Management Node must have a unique hostname.
The Hostname and Domain together make up the Conferencing Node's DNS name or FQDN. We recommend you assign valid DNS names to all your Conferencing Nodes. For more information, see Assigning hostnames and FQDNs.
System location Select the physical location of this Conferencing Node.
If the system location does not already exist, you can create a new one here by clicking to the right of the field. This will open up a new window showing the About system locations.
page. For further information seeIPv6 address The IPv6 address for this Conferencing Node. Each Conferencing Node must have a unique IPv6 address. Gateway IPv6 address The IPv6 address of the default gateway. IPv4 static NAT address The public IPv4 address used by this Conferencing Node when it is located behind a NAT device. Note that if you are using NAT, you must also configure your NAT device to route the Conferencing Node's IPv4 static NAT address to its IPv4 address.
For more information, see Configuring Pexip Infinity nodes to work behind a NAT device.
Static routes From the list of Available Static routes, select the routes to assign to the node, and then use the right arrow to move the selected routes into the Chosen Static routes list. For more information, see Managing static routes. SSH password Enter the password to be used when logging in to this Conferencing Node's Linux operating system over SSH. The username will always be admin.
Logging in to the operating system is required when changing passwords or for diagnostic purposes only, and should generally be done under the guidance of Pexip support. In particular, do not change any configuration using SSH — all changes should be made using the Pexip Infinity Administrator interface.
-
Select
.You will be taken to the
page. -
Select
.A zip file with the name pexip-<hostname>.<domain>.zip will be downloaded.
-
When you wish to deploy the
:- Copy the zip file to the server running Hyper-V and unzip it.
You will see a subfolder called Virtual Machines, containing an XML file which contains the configuration for the Conferencing Node VM. - Open the Hyper-V Manager and select .
-
Follow the on-screen prompts to deploy the Conferencing Node VM.
When prompted, select the Virtual Machines folder and the Hyper-V manager will automatically discover the XML file.
Select the type of import most appropriate for your environment (if you are unsure, select Restore the virtual machine).
- Copy the zip file to the server running Hyper-V and unzip it.
After deploying a new Conferencing Node, it typically takes 15-20 minutes before the node is available for conference hosting and for its status to be updated on the Management Node. (Until it is available, the Management Node will report the status of the Conferencing Node as having a last contacted and last updated date of "Never".)
Enabling automatic startup
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.