vCloud Director not reporting CPU Utilization

I came across a customer site recently where their vCloud Director (vCD) 5.1 implementation was not reporting CPU utilization for Organisation Virtual Datacenters (Org VDCs). RAM and storage allocation was fine, just CPU was not showing a usage bar, and the mouse over tip reported 0% allocated. Turns out this is a known issue with vCloud Director 5.1, and VMware have released KB 2054043 relating to this issue. Their advice (via the KB) is to: Upgrade vCloud Director to version 5.1.2 or later. Enable Elastic Allocation Pool mode for vCloud Director. To do this: Login to vCD as a System Administrator user. Navigate to Home > Administration > General. Unter the Miscellaneous section, check the box next to 'Make … [Read more...]

Public Catalog Access for vApp Authors fails post-v5.5.1 Upgrade


This one stumped me for a little bit. The private cloud in my lab is fairly simple in layout - 2 RHEL cells with a vCNS load balancer, shared NFS server and DB server. The Organisations are provisioned such that of the 3 tenants, one is a master tenant that is only used for creating and maintaining vApp templates, via a Public Catalog for sharing the templates for cloud provisioning and vCAC blueprint testing. Running this configuration in with no changes to the default vCloud Director (vCD) roles worked fine - delegated LDAP users in the 2 user organisations were able to select vApp templates from the Public Catalog and deploy them locally. All good. The issue came when the cells for vCD were upgraded to the latest v5.5.1 build. … [Read more...]

vCloud Director 5.1 to 5.5 Cell Upgrade ‘cpio: chown failed’


Upgrading my lab environment from vCloud Director v5.1 to v5.5, I came across an interesting error whilst upgrading the cells. My lab has the following vCD configuration: 2 x RHEL 6.2 Cells 1 x RHEL 6.2 NFS Server 2 x vShield load balancer instances 1 x Windows 2008 R2 DB server running SQL Server 2005 The upgrade process was: Quiesce the cell using the Cell Management Tool commands. (Upgrade Guide) Upload the vCD .BIN file to the /install directory of the cell (using WinSCP or similar). Change the execution parameters for the vCD .BIN file. (Upgrade Guide) Running the installation .BIN file. (Upgrade Guide) Confirm the existing v5.1 cell instance can be upgraded. This is where the interesting error came in. The … [Read more...]

Troubleshooting vCloud Automation Center Endpoints and vCloud Director 5.1

BACKGROUND Note: For this troubleshooting article, I'm using vCloud Director 5.1 and vCloud Automation Center 5.2. Having fun with my lab. Lots of fun - and as readers may have noticed, my current focus is around deploying vCloud Director (vCD) and integrating it with vCloud Automation Center (vCAC). However, all is not plain sailing. Firstly, the installation of vCAC v5.2 is much better than installing v5.1. By better I mean more streamlined, the deployment packages retain more explanation, and lots of the installation 'gotchas' have been either removed, fixed or simply hidden from the installation process. I'll not detail the installation process here as there are lots of other guides out there. This break-fix article is about a … [Read more...]

vCloud Director vApp Error ‘Cannot Update’

vcloud error

Came across another strange issue in a production environment the other day that was also a bit of a facepalm monent. Users of a private vCloud Director instance were complaining of issues with updating vApps - specifically around adding and managing assigned storage associated with these vApps. The errors presented within the vCloud interface were randomly brief and not a little vague - 'Details: Error, Status: Error' etc. This error in the example was taken directly from the vCloud GUI, with no associated vSphere Tasks (that list being blank). The error presented wether the vApp was running or stopped, and wether the VM concerned was running or stopped - each time it was the same. Looking a little deeper into the vCloud logs … [Read more...]

vCAC Agent Install ‘RepoUtil.exe’ Error


Like many out there, I am upgrading my lab environment to the new vCloud Automation Center, since 5.2 was released. The installation process is a little different, and shows evidence of the transition from the old DynamicOps product to one more inline with the other vCloud Suite offerings. I will write-up another post about the full installation of vCAC 5.2 in due course, but in the meantime this is a quick heads-up to make sure to read the requirements documents before completing the install. vCould Automation Center 5.1 used to require DotNet 4.0 to be installed for Endpoint agents to run correctly. If you are in a lab environment and are happy to build and burn your existing vCAC deployment, then mostly an installation in situ will … [Read more...]

Manual vCNS / vShield Edge HA Little Gem!


Recently, I have been doing lots with vCNS and manual creation / manipulation of vShield Edge devices (posts coming soon). One thing that drive me crazy is a tiny little thing that prompted me to write this quick Little Gem - 'Edge HA' sat on my to do list, and gloated at me..... When creating a manual vShield Edge device in vCNS, there is the usual opportunity to create an pair of appliances for running the pair in High Availability mode. Trouble is, the options for deployment are limited and not very clear. (This might be clear / obvious to some, but weren't to me!) When creating an HA pair, in the vShield Manager console editing the Edge device in question under Settings - the HA Configuration gives few options. Essentially, … [Read more...]

Fixing vCloud Director ‘HTTP NFC Error’ & Sysprep


Recently I've been doing some work on vCloud Director deployments, typically new VMs within Organisations. On powering-on VMs or deploying vApps, I got the error 'Unable to start vApp '<vApp Name>'. The more specific error related to one or more of the following errors: 'HTTP NFC Error'. Cannot deploy package from /opt/vmware/vcloud-director/.... etc etc. Unable to start vApp. Unable to start virtual machines in resource pool. Broken pipe. Broken pipe. Solution: A little bit of digging on the vCloud cell (RHEL in this case) showed the permissions were incorrect on the 'guestcustomization' folder, and that changing these fixed the problem. A little more investigation showed-up the … [Read more...]

Site-2-Site VPN Issue between vShield 5.1 and Checkpoint

I came across an interesting issue whilst configuring a site-2-site VPN connection between a vCloud Director 5.1 customer vDC and a remote customer site. The requirement was for the VPN to be configured to pass through the perimeter hardware firewalls and terminate on the external interface of the vShield Edge device connected to the vCloud external network. Firewall configuration was done on the vShield device connecting the vDC routed organisation network and the vCloud external network - defining the peer and local network configurations, plus vShield firewall rules to allow traffic through the Edge device to reach the VMs inside the organisation. The problems we had in this instance were multiple - the customer only had a change … [Read more...]