ESX4 “Web Access” 503 Service Unavailable Error
KB ID 0000150 Problem If you connect to an ESX4 Server and attempt to “Log onto Web Access” you get a 503 Service Unavailable error. This is because unlike EXS3 the web console is disabled, well not strictly true the service is usually running but the firewall (on the ESX server) is blocking it. Solution 1. Log into the ESX Host with the VI Client software. (Note: If you don’t have the VI client you would...
VMware Error – Host {name} currently has no management network redundancy
KB ID 0000231 Problem Seen in Vmware ESX / Vmware Vsphere environments with both ESX and ESXi hosts. Solution As far as errors go this one’s pretty straight forward (and very common). I’ve seen it in ESX3 and VSphere networks, with high availability clusters. It’s complaining because there is only one physical NIC presented to the Service Console (I know ESXi does not have a service console, but it has a management...
VMware ESX Error “cmd addnode failed for primary node: Internal AAM error”
KB ID 0000298 Problem Seen in a Virtual Center HA environment – even after selecting “Reconfigure for HA” on the ESX host. Errors: cmd addnode failed for the primary node:Internal AAM error – agent could not start – Unknown HA error. Cannot complete the configuration of the HA agent on the host – See the task details for additional information. Other HA configuration error. Solution 1. How...
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 – {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 >...