ESX RAM DISK FULL Errors

Please follow the below steps for RAM Disk Full Error, This issue may occur effect for migration of Vm 's from one Host to another Host .
1. Connect to the ESXi host using SSH. For more information, see .
2. 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.
3. 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
4. Change directory to /etc/vmware/ and back up the snmp.xml file by running the commands:
# cd /etc/vmware # mv snmp.xml snmp.xml.bkup
5. Create a new file named snmp.xml and open it using a text editor. For more information, see .
6. Copy and paste these contents to the file: false161 indicationsinfo
7. Save and close the file.
8. Reconfigure SNMP on the affected host by running the command: # esxcli system snmp set –-enable=true
9. To confirm the SNMP services are running normally again, run the command: # esxcli system snmp get Here is an example of the output: /etc/vmware # esxcli system snmp get Authentication: Communities: Enable: true Engineid: 00000063000000a10a0121cf Hwsrc: indications Loglevel: info Notraps: Port: 161 Privacy: Remoteusers: Syscontact: Syslocation: Targets: Users: V3targets: To ensure that the issue does not recur, you can temporarily disable snmpd to stop logging. To stop the snmpd service, run this command: # /etc/init.d/snmpd stop Note: In the event that the host has run out of inodes, attempt to stop vpxa on the host to free up an inode:
1. Connect to the host with the vSphere Client.
2. Click Configuration > Security Profile.
3. Under Services, click Properties.
4. Click vpxa, then click Options.
5. Under Startup Policy, click Stop.
6. Click OK.
7. Click OK.