VMware Cloud Community
Anonymous
Not applicable
Jump to solution

ESXi 5.1 SNMP configuration issues - .trp files accumulating after SNMP is disabled

Hi,

We have encoutered 2 issues with our new ESXi 5.1a servers:

1. vMotions fail at 13%

2. Some of the VMs are not accesible through their consoles. (Unable to contack MKS)

In order to solve these issues, I came accross the following KB:

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=204070...

I have performed the step needed and even created a new host profile where the SNMP agent is disabled. However, upon a succesful remmediation of the new profile, .trp files continue to accumulate in /var/spool/snmp (Above 3000 files in 2 days) and I have no idea what is creating these trap files and why.

Can anyone shed some light on this issue?

Tags (2)
Reply
0 Kudos
1 Solution

Accepted Solutions
venkyVM
Enthusiast
Enthusiast
Jump to solution

This is resolved in the latest release of vSphere 5.1 Update 1.

Release Notes :: https://www.vmware.com/support/vsphere5/doc/vsphere-esxi-51u1-release-notes.html

ESXi 5.x host appears disconnected in vCenter Server and logs the ramdisk (root) is full message in the vpxa.log file
If Simple Network Management Protocol (SNMP) is unable to handle the number of SNMP trap files (.trp) in the/var/spool/snmp folder of ESXi, the host might appear as disconnected in vCenter Server. You might not be able to perform any task on the host.
The vpxa.log contains several entries similar to the following:
WARNING: VisorFSObj: 1954: Cannot create file
/var/run/vmware/f4a0dbedb2e0fd30b80f90123fbe40f8.lck for process vpxa because the inode table of its ramdisk (root) is full.
WARNING: VisorFSObj: 1954: Cannot create file
/var/run/vmware/watchdog-vpxa.PID for process sh because the inode table of its ramdisk (root) is full.

This issue is resolved in this release.

View solution in original post

Reply
0 Kudos
1 Reply
venkyVM
Enthusiast
Enthusiast
Jump to solution

This is resolved in the latest release of vSphere 5.1 Update 1.

Release Notes :: https://www.vmware.com/support/vsphere5/doc/vsphere-esxi-51u1-release-notes.html

ESXi 5.x host appears disconnected in vCenter Server and logs the ramdisk (root) is full message in the vpxa.log file
If Simple Network Management Protocol (SNMP) is unable to handle the number of SNMP trap files (.trp) in the/var/spool/snmp folder of ESXi, the host might appear as disconnected in vCenter Server. You might not be able to perform any task on the host.
The vpxa.log contains several entries similar to the following:
WARNING: VisorFSObj: 1954: Cannot create file
/var/run/vmware/f4a0dbedb2e0fd30b80f90123fbe40f8.lck for process vpxa because the inode table of its ramdisk (root) is full.
WARNING: VisorFSObj: 1954: Cannot create file
/var/run/vmware/watchdog-vpxa.PID for process sh because the inode table of its ramdisk (root) is full.

This issue is resolved in this release.

Reply
0 Kudos