ESXi 5.x host becomes unresponsive during vMotion How to solve errors when a VMware vCenter vMotion migration or a configuration change fails

Suddenly somehow we got a virtual machine which couldn’t be powered on, or ESXi 5.x host becomes unresponsive after attempting to migrate a virtual machine from VMware vCenter Server or configuration change fails.

Symptoms

  • VMware ESXi 5.x host becomes unresponsive after attempting to migrate a virtual machine from VMware vCenter Server;
  • Making a configuration change to the ESXi host renders the host unresponsive;
  • Migration fails at 13%;
  • Some of the virtual machines in the inventory become invalid;
  • vpxa fails to start;
  • You are unable to power on a virtual machine.

Resolution

  • Connect to the ESXi host using SSH.
  • Check if SNMP is creating too many .trp files in the /var/spool/snmp directory on the ESXi host by running the command:
    ls /var/spool/snmp | wc -l

Note: If the output indicates that the value is 2000 or more, this may be causing the full inodes.

vmware result_ls root disk full, esxi, host, vmotion, snmp, trap, maintenance
vmware result_ls

To be sure check che disk root usage running this command

vdf -h
vmware disk root_usage
vmware disk root_usage

If the available space is less than 3-4Mb (or usage ‘USE’ over 90%), it could be a problem.

  • Delete the .trp files in the /var/spool/snmp/ directory by running the commands:

# cd /var/spool/snmp
# for i in $(ls | grep trp); do rm -f $i;done

CLEAN_TRP_SNMP results
CLEAN_TRP_SNMP results root disk full problems snmp

Related Articles: VMware KB | Wh33ly’s Blog

Lascia un commento

Il tuo indirizzo email non sarà pubblicato. I campi obbligatori sono contrassegnati *