Partners Blog Contact Us

Preparing Specific IP and FQDN Values for Your VP1, VP2, and Cluster


In order to implement Hot Standby, you need an IP address and FQDN for each of your VidyoPortals. You also need an IP address and FQDN for the Cluster.


When the Hot Standby option is used correctly, the Cluster IP and FQDN always direct traffic to the Active VidyoPortal. The Active VidyoPortal takes the Cluster IP and FQDN during Hot Standby activation.

The following diagrams show Hot Standby system configurations, both without and with the Management Interface enabled on your system.




The Management Interface IPs remain static and always accessible. There is no virtualization applied to them, as done with the Cluster IP.

The Management Interface is not virtualized; meaning, when using the Management Interface and Hot Standby changes which VidyoPortal is Active and which one becomes the Standby, no IP address virtualization takes place and respective Management Interface IPs remain unchanged.

The following diagram illustrates how your Hot Standby Cluster relates to the Active VidyoPortal.


Tip: Prepare for configuring your Hot Standby setup by printing this page and writing down the specific IP and FQDN values that you want for your VP1, VP2, and Cluster. You will need this information during various Hot Standby configuration procedures.



If you are upgrading from VidyoPortal 2.x to 3.x and are now using FQDN licensing, your Public FQDNs and Cluster FQDNs on both of your VidyoPortals must be identical before upgrading.

The Hot Standby option creates the mechanism that allows for storing both a Native IP address and FQDN and a Cluster IP address and FQDN on each of your VidyoPortals in the following manner.


The Cluster IP address and FQDN are stored on both machines and are ready for use when the VidyoPortal is designated as the Active VidyoPortal.

Remember if you are adding a VidyoPortal to your existing setup in order to leverage the Hot Standby option, Vidyo strongly recommends that you change your VidyoPortal’s existing Native IP address and FQDN to new ones so that the existing ones can be used as the Cluster IP address and FQDN.

Always reboot machines after making any IP address and DNS changes.

Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.