vCloud Director 5.5 Changes to DNS Settings Will Not Automatically be Applied to DHCP

Occurs when Changing Static IP Pool DNS server address

vCloud Director 5.5 Changes to DNS Settings Will Not Automatically be Applied to DHCP

vCloud Director 5.5 Changes to DNS Settings Will Not Automatically be Applied to DHCP

vCloud Director 5.5 Changes to DNS Settings Will Not Automatically be Applied to DHCP

This message appears when changing the static I pool DNs setting in vCloud Director Org (tenant) Network

Make any change in the DHCP, to ensure your DNS setting has changed . The change in DHCP can be removed afterwards.

Advertisements

vCloud Director Deploying VM from Catalog Does Not Create Drive to Specified Size

vcloud-driector-deployed-windows-server-vm-from-catalog-drive-not-automatically-created-to-specified-larger-size

When deploying a VM from a public catalog in vCloud Director, the VM is created wit hthe default tepmplate size and not the size specified when setting the deployment options.

An example of this is when a Windows Server 2008R2 VM was deployed from a template, the drive was not automatically extended to 80GB. It was the default of 40GB. This can occure if guest customizations is not enabled during the process of deploying the VM from catalog.

The drive has to be extended manually using Windows Disk Manager.

VSphere client unable to connect to the MKS – get black screen only

vmware-vsphere-client-unable-to-connect-to-the-MKS-black-screen

vmware-vsphere-client-unable-to-connect-to-the-MKS-black-screen

VMware client unable to connect to the MKS – get black screen only

The solution for me after spending some time and it could have been much more, a DNS problem. The names of the hosts could not be resolved. There was a recent DNS change in our office that triggered this problem.

VMWare vpxd Failed To Initialize.

Recreating or Resetting the vCenter Server embedded DB2 database repository for the vCenter Server Appliance 5.0 solved the problem. 

VPXD Failed to Initialize

vmware-vpxd_failed_to_initialize

Waiting for vpxd to initialize

After importing the ovf file in vmware for Vcenter Server appliance, the vmware-vpxd failed to initialize. One of the most simplest causes for this if this is a new vcenter server is the time and timezone not matching the host on which the vcenter server is operating on does not match. You may have to deploy another vcenter server virtual appliance to get around that. You can try the following fix if you continue to have a problem after you have set the time and timezones to match and re-deployed a new vcenter server.

Resetting the database worked to solve the problem for a vCenter Server version 5 installation.  This was done after the time matched and the correct timezone was set.

You can reset the embedded DB2 database through the:
  • Web Console
  • Command line

The command line method does not reset the license. At a command prompt on the vcenter server enter the following :

As mentioned, this method does not remove license key information from the vCenter Server database.
To reset the embedded DB2 database:
  1. SSH or open a virtual machine Console to vCenter Server Appliance and log in as root.
  2. Run the commands:
    • # service vmware-vpxd stop
    • # /usr/sbin/vpxd -b
    • # service vmware-vpxd start
    • service vmware-vpxd statusFor example:vmware-vpxd is running
      tomcat is running

PC Tech Go: Enable SSH on VMWare 5 ESXi

PC Tech Go: Enable SSH on VMWare 5 ESXi.

Enabling or activating SSH connections to a VMWare host in ESXi 4.0 or earlier of VMWare required physical access to the console to enable SSH connections. With ESXi and ESXi version 5 of vSphere, the process of enabling SSH conenctiviyt to the vmware server is much easier.

Enabling or activating SSH console access can now be accomplished via the vsphere client software.

As the image above shows, use the vsphere client, connect to each of your vmware host servers and choose Configuration, then go to Security profile, then select properties. Select the SSH option in Properties and choose options. Select “start” to start SSH on the host.

Please visit http://pctechgo.blogspot.com/2011/12/enable-ssh-on-vmware-5-esxi.html for a larger image and detailed instructions.

PC Tech Go: Enable SSH on VMWare 5 ESXi

PC Tech Go: Enable SSH on VMWare 5 ESXi.

Enabling SSH remote access to the console of an esxi 5.0 vmware host server is the same as in ESXi 4.1 (not 4.0 and earlier). In 5.0 vmware vSphere ESXi and 4.1 vmware vSphere ESXi it can be accomplished using the vSphere client.

Enable SSH on VMWare 5 ESXi

How to Enable SSH Access on VMWare vSphere 5 ESXi