vSphere ‘Invalid configuration for device ’0′ error’ Solution

Using vSphere 4 hosts (in this case a legacy un-patched host that was being migrated off and decommissioned), we came across an interesting and ambiguois error – ‘Invalid configuration for device ’0′, plus a note of time, the target object and the vCenter Server.

In this case, I was trying to migrate a powered-off VM to different storage – resulting in the error. I also found that the issue was related to the second disk attached to the VM. Editing the VM showed the size as 0MB, but removing this disk also threw the error in vCenter.

The solution was to follow these steps:

  • Remove the VM from the vCenter inventory.
  • Update the VM VMX file. There are 2 ways to do this – SSH to the host / datastore using a tool like Putty, or use the datastore browser to download the VMX file, then edit the it in Notepad.
  • Inside the VMX file. look for the following entries:

scsi0:1.present = “true”

scsi0:1.fileName = “vmname.vmdk”

Update these entries to the following:

scsi0:1.present = “false

scsi0:1.fileName = “vmname.vmdk”

  • Re-add the VM to the vCenter inventory, either through the GUI or using ‘vmware-cmd -s register \path\to\your\vm.vmdk’.
  • Check the VM properties, you should now show the offending drive as missing and it can be re-added from the datastore.

Manual vCNS / vShield Edge HA Little Gem!

vCNS-HARecently, 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, ‘Enabled’ or ‘Disabled’, vNIC, Declared Dead Time and Management IPs. Here’s where my confusion was based. Management IPs. So many questions……!

The option for Management IPs is even outlined. 2 IP entry boxes, and note text: ‘You can specify pair of IPs (in DIDR format with /30 subnet. Management IPs must not overlap with any vnic subnets’.

OK, so I need Management IPs to manually create a HA pair. What /30 address range do I need to specify? Can the IP range share an existing vNIC, or does the Edge device need another interface or uplink. Where do I define the /30 addresses. Do they need their own vLANs? Must I create a whole new private address range specifically for HA heartbeat? Like I said – so many questions. Scour the documentation, Google ‘vShield Edge Management IPs’ produces no helpful results. So – to the LAB!

Turns out, you don’t need Management IPs at all. Simply change the HA Status to ‘Enable’, select a vNIC to support HA heartbeat, and add a second Edge appliance via the green plus symbol (it will prompt for the parameters) to deploy the HA pair! When both report as ‘Deployed’, HA is configured and your Edge device is protected.

Sigh. Like I said. This might seem obvious to some, but it wasn’t to me. ‘Edge HA’ is no longer on my to-do list!

vOpenData – Shared Virtual Infrastructure Statistics

Whether you love or loathe VMware and their products, one area that you can’t fault is the community that’s built up around them. In that community blood, sweat, tears and a dash of brilliance have produced many amazing things. vOpenData looks like it could be one of them.

vOpenData is the brainchild of Ben Thomas and was built with William Lam and assistance from several other VMware community members. Essentially it is a public database of VMware Virtual Infrastructure statistics / configurations. Users download a script that collects some anonymous data about their infrastructure. Once uploaded and added to the database, the data contributes to a plethora of publicly available statistics.

At the time of writing there are over 50,000 VMs in the database. The average VMDK size is just over 70Gb. For me, as a techie / evangelist / consultant, this is useful information and there’s so much more there besides. Here’s a quick grab from the public dashboard:

screenshot341

As a community project, its value is huge and will get even better the more people contribute data to it. Head over to the vOpenData website and find out more.

The End of the VMTN Saga?

vmtn_storeIf you don’t know what VMTN is, you might be new to VMware virtualisation or the IT industry. Either way, I have an older post that covers it a bit. I posted it in November 2011 just as the campaign to get the VMTN subscription re-instated by VMware was kicking off.

Here we are though, nearly 18 months later, and it looks like it’s not going to happen. One of VMTN’s biggest proponents, Mike Laverick, posted on the VMware Communities thread related to VMTN today that it looks unlikely. In his words:

The prevailing view appears to be that other projects will be sufficient… Such as Project Nee…

Project NEE is VMware’s online learning resource that’s currently being put through its paces. If you read around what it does, you can see why VMware would consequently view the resurrection of VMTN as unnecessary. Whilst it’s a disappointment to people who run home lab setups, want to run legitimate workplace labs and prototypes etc., I don’t think that it’s necessarily the end of the world. The level of automation / orchestration possible in VMware’s suite of products means that re-installs don’t have to take an age to complete. In fact, I want to rip and rebuild my lab regularly because it’s exactly those sorts of tasks and skills that I want to hone. I don’t want my lab to sit and age like some legacy infrastructure. I appreciate though that others may not share my views or enthusiasm.

Either way, my advice is not to hold your breath in the hope of a change of heart. If it’s true that VMTN is going to stay dead, VMware have made this decision with their heads and not their hearts. My head says, keep calm and roll with it*.

* (@h0bbel, another one for your collection?)

Are you a vExpert?

vEXPERT_2013_fakeVMware’s vExpert award isn’t something that you can study for. It’s not something that you know, it’s something that you are!

This is the 5th year that VMware have operated the the programme (“program” for any US readers) and applications for the 2013 award are open now. If you’ve contributed any of your time in 2012 to enhancing the VMware community in some way then it might be worth your while applying.