virtual grind thoughts from the virtual world

31Mar/110

VMware vCloud Partners

VMware has recently posted a new site for vCloud Partners. This site contains a lot of information on vCloud Certified partners that provide services around vCD, as well as other features.

Check it out here.

Tagged as: , , No Comments
28Mar/110

Link To vSphere 4.0 iSCSI SAN Configuration Guide

When working with iSCSI arrays, this guide is worth gold.

Get the guide here.

28Mar/110

Enabling ARP Redirect For Compellent Arrays

In order for controller failover to work correctly when using ESX and Compellent arrays, you must enable arp redirect on your ESX hosts. If, for instance, you have a vmhba numbered vhmba33, you can check to see if arp redirect is enabled by connecting to the console and typing:

esxcfg-hwiscsi -l vmhba33

If arp redirect is not enabled, you can simply enable it with the following command:

esxcfg-hwiscsi -a allow vmhba33

18Mar/110

vCMA – Manage vSphere From Your iPad

VMware Labs recently released version 1.0 of the vCenter Mobile Access (vCMA) appliance. The virtual appliance is based on CentOS 5.2 Linux.

To install, you will simply download the appliance (~300MB) and import via vCenter. Once you import the appliance, the appliance will pick up an IP address via DHCP and start a management console on port 5480. Browse to https://IPADDRESS:5480 and log in with the default user/pass of root/vmware. If you are not using DHCP on your network, open up the console of the appliance and set the IP address there.

Once configured, access the the appliance via https://IPADDRESS/vim. From here, you can log in to your vCenter server via a valid user name and password and begin to manage your environment from your iPad or mobile device!

You can read more about the vCMA and download the appliance here.

4Mar/110

Collecting vShield Manager Logs

I ran in to some issues with the vShield Manager interaction with vCenter Chargeback. In order to troubleshoot, the vShield Manager logs need to be exported via the vShield Manager web interface or CLI.

To get the logs from the web interface, simply log in to the IP address of the web interface, click "Settings & Reports", then click "Audit Logs". Note that you can also download the logs to your local computer by clicking "Configuration", then "Support", then "Initiate". Once initiated, you can download the logs by clicking "Download".

For the CLI, simply log in via the console or ssh and issue a "show tech-support".

2Mar/110

vCloud Director 1.0.1 Upgrade Fails with “cpio: chown failed – Operation not permitted”

VMware requires that the vCloud Director installation .bin file is executed as root. This file is run to perform a new installation or upgrade to an existing vCloud Director cell. I have recently run into an issue with NFS's "root squashing" feature, which prevents the upgrade from completing.

As the NFS Sourceforge page states:

Default NFS server behavior is to prevent root on client machines from having privileged access to exported files. Servers do this by mapping the "root" user to some unprivileged user (usually the user "nobody") on the server side. This is known as root squashing. Most servers, including the Linux NFS server, provide an export option to disable this behaviour and allow root on selected clients to enjoy full root privileges on exported file systems.

Unfortunately, an NFS client has no way to determine that a server is squashing root. Thus the Linux client uses NFS Version 3 ACCESS operations when an application is running on a client as root. If an application runs as a normal user, a client uses it's own authentication checking, and doesn't bother to contact the server.

If you are not using the "no_root_squash" option on your NFS exports on your NFS server, you will receive the error "cpio: chown failed - Operation not permitted". This option is needed since the /opt/vmware/cloud-director/data/transfer directory on the vCloud Director cell is actually mounted to your NFS server.

Once you enable the no_root_squash option on your NFS exports, such as:

/export/dir hostname(rw,no_root_squash)

...you will be able to write to the directory as root and the upgrade will complete.