Enabling Tape Drives on vSphere Hosts
KB ID 0000417 Problem Over the next few weeks I’ve got a couple of Hewlett Packard LTO Ultrium 5 Tape drives to deploy with ESXi 4.1 U1. These will work just fine, there is however a problem presenting SCSI U320 drives now, so thanks to my colleague (Andrew Dorrian) for giving me the heads up on the problems I would face with older drives. Make sure you have enabled SSH access on your ESX Host. Note: With the release of vSphere...
VMware error on HP Proliant “Host Baseboard Management Controller status”
KB ID 0000418 Problem Saw this today on a HP Proliant DL380 G7 Server. Solution 1. It’s a simple one to solve, the server was built with the HP ESXi build, and the management agents are complaining because the iLO is not connected to the network. 2. When you connect the iLO socket to the network the alarm should change as shown below. 3. Once you have connected or disabled it you can reset the alarm. 4. Take the opportunity to...
VMware VIM (vCenter) Where to put the sysprep files in Server 2008?
KB ID 0000420 Problem For newer servers I don’t really use templates anymore, but if you are deploying a lot of 2003 Windows servers in vSphere, then they can save you some time. Back in the days of vCenter 2.5 you just uploaded those sysprep files to the relevant folder in, C:Documents and SettingsAll UsersApplication DataVmwareVmware Virtual Centersysprep But that location no longer exists (since Server 2008). Solution The...
VMware – {hostname} could not reach isolation address: none specified
KB ID 0000445 Problem Seen on vSphere: Error Host {hostname} could not reach isolation address:none specified. Solution 1. In my case the host did NOT have a default gateway, (this had occurred because the subnet mask of the server had been entered incorrectly when the server was built. So the default gateway appeared to be on a different network). 2. With the offending host selected, Configuration > DNS and Routing >...
ESX 4 to ESX 5 Upgrade Warning ‘Custom VIB Warning’
KB ID 0000500 Problem Seen when upgrading ESXi 4.1 U1 to ESX 5. Error: <3RD_PARTY_SOFTWARE_WARNING: Host contains third-party VIB(s) that have no substitute on the ISO. [‘oem-vmware-esx-drivers-net-vxge’, ‘oem-vmware-esx-drivers-scsi-3w-9xxx’]> If attempting to upgrade with VMware update manager you will see the following; Solution Luckily this was on a test box so I was somewhat more cavalier in my...