vCenter Host Gateway Appliance - Overview and Deployment.

By | March 15, 2015

vCenter Host Gateway (distributed as a virtual appliance) is a vCenter Server feature that lets you manage virtual environments that consist of various types of hypervisors. In this post you will find answers for the following questions:

  1. vCenter Host Gateway requirements
  2. vCenter Host Gateway 3rd supported hypervisors
  3. How to deploy and configure vCenter Host Gateway Appliance
  4. How to add and manage 3rd hypervisors.

vCenter Host Gateway requirements

There are following vCenter Host Gateway requirements:

  • vCenter Server 6.0 (how to deploy please follow a post available here)
  • Version 7 of Virtual Machine Hardware -  ESXi 4x or higher

vCenter Host Gateway 3rd supported hypervisors

Currently vCenter Host supports the following releases of Microsoft Hyper-V:

  • Microsoft Hyper-V Server 2012 R2
  • Microsoft Hyper-V Server 2012
  • Microsoft Hyper-V Server 2008 R2
  • Microsoft Hyper-V Server 2008

How to deploy and configure vCenter Host Gateway Appliance 

To deploy the vCenter Host Gateway appliance you must start the deployment wizard from the vSphere Web Client.

  1. In a Web browser, log in to vSphere Web Client as an administrator.
  2. Select an inventory object that is a valid parent object of a virtual machine, such as data center, folder, cluster, resource pool, or host.
  3. From the Actions menu, select Deploy OVF Template.
  4. The Deploy OVF Template wizard appears. Please follow the steps mentioned in wizard.
  5. Power On the appliance.

When you deploy the vCenter Host Gateway Appliance, please follow the below steps:

  1. In a Web browser, log in to the Web interface of the vCenter Host Gateway appliance.
  2. Click the Registration tab.
  3. In the IP or host name text box, enter the IP address of the Platform Services Controller. Enter a Single Sign-On administrator user name and password.  Click Register.vCenter Host Gateway Appliance - Overview and Deployment2
  4. When provided credentials are valid, the registration should be successful.vCenter Host Gateway Appliance - Overview and Deployment3

Note:  The time on vCenter Host Gateway Appliance and Platform Services Controller must be synced! Otherwise you get the following error:

vCenter Host Gateway Appliance - Overview and Deployment4Server rejected the provided time range...... This might be due to a clock skew problem! The Platform Services Controller time is ... seconds diffrent from the time of the vCenter Host Gateway.

Add Third-Party Hosts to the vCenter Server Inventory

  1. In the vSphere Web Client, navigate to a data center or host folder.
  2. Enter the name or IP address of the host, followed by the port.
  3. From the Type drop-down menu, select a third-party host type.vCenter Host Gateway Appliance - Overview and Deployment
  4. Click Next.
  5. If prompted, confirm that the connection is as secure as required.
  6. In the Username and Password text boxes, enter administrator credentials and click Next.
  7. Review the host summary information and click Next.
  8. Assign a licence key to the host and click Next.
  9. On the page that displays lockdown options, leave the default options selected, and click Next.
  10. Select a location for the virtual machines that already exist on the host and click Next.
  11. Review the summary information and click Finish.

Note: As shown on above figure, there is possible to choose another 3rd hypervisors such KVM and vCloud Air. However, it is not supported and implemented yet. Looks like, VMware added it for future 🙂

One thought on “vCenter Host Gateway Appliance - Overview and Deployment.

  1. hicham

    Hello! When I try to register with the information I configured in the Platform Services controller I get this error: "Unable to initialize CM CLient! Cannot connect to Platform Services Controller. Verify your network connectivity and try again.Connect to 192.168.1.10:80 [/192.168.1.10] failed: Connection refused" I have configured the firewall of the SuSE linux machine to accept http connections as well as https. Also I enabled http client in the ESX host's firewall through the vcenter server. but still get the same error. Looking forward for an answer.

    Reply

Leave a Reply

Your email address will not be published. Required fields are marked *