VMware Cloud Community
thickclouds
Enthusiast
Enthusiast

SNMPD Errors

Anyone ever see these errors:

Jan 16 15:17:49 esxmachinename snmpd[2091]: SNMPVmodl: start refreshing cache...

Jan 16 15:17:50 esxmachinename snmpd[2091]: SNMPVmodlRefreshCache: Examining 14 VMs found.

Jan 16 15:17:50 esxmachinename snmpd[2091]: SetDiskResource: skipped disk not backed by vmfs Hard Disk 1.

Jan 16 15:17:51 esxmachinename snmpd[2091]: SetDiskResource: skipped disk not backed by vmfs Hard Disk 1.

Jan 16 15:17:51 esxmachinename snmpd[2091]: SetDiskResource: skipped disk not backed by vmfs Hard Disk 2.

Jan 16 15:17:51 esxmachinename snmpd[2091]: SetDiskResource: skipped disk not backed by vmfs Hard Disk 1.

Jan 16 15:17:51 esxmachinename snmpd[2091]: SetDiskResource: skipped disk not backed by vmfs Hard Disk 2.

Jan 16 15:17:51 esxmachinename snmpd[2091]: SetDiskResource: skipped disk not backed by vmfs Hard Disk 1.

Charlie Gautreaux vExpert http://www.thickclouds.com
0 Kudos
2 Replies
djaquays
Enthusiast
Enthusiast

I hate to gravedig this thread, but since no one answered, and I'm having the exact same issue, I decided to do this versus starting a new thread on the same topic.

My /var/log/messages for all of my esx hosts are filled with entries similar to what cpfcg posted, over and over again.

Aug 18 10:42:36 host snmpd[1884]: SNMPVmodl: start refreshing cache...

Aug 18 10:42:37 host snmpd[1884]: SNMPVmodlRefreshCache: Examining 11 VMs found.

Aug 18 10:42:37 host snmpd[1884]: SetDiskResource: skipped disk not backed by vmfs Hard Disk 1.

Aug 18 10:42:37 host snmpd[1884]: SetDiskResource: skipped disk not backed by vmfs Hard Disk 2.

Aug 18 10:42:38 host snmpd[1884]: SetDiskResource: skipped disk not backed by vmfs Hard Disk 1.

Aug 18 10:42:38 host last message repeated 2 times

Aug 18 10:42:38 host snmpd[1884]: SetDiskResource: skipped disk not backed by vmfs Hard Disk 2.

Aug 18 10:42:38 host snmpd[1884]: SetDiskResource: skipped disk not backed by vmfs Hard Disk 3.

Aug 18 10:42:38 host snmpd[1884]: SetDiskResource: skipped disk not backed by vmfs Hard Disk 1.

Aug 18 10:42:38 host snmpd[1884]: SetDiskResource: skipped disk not backed by vmfs Hard Disk 1.

Aug 18 10:42:38 host snmpd[1884]: SetDiskResource: skipped disk not backed by vmfs Hard Disk 2.

Aug 18 10:42:39 host snmpd[1884]: SetDiskResource: skipped disk not backed by vmfs Hard Disk 3.

Aug 18 10:42:39 host snmpd[1884]: SetDiskResource: skipped disk not backed by vmfs Hard Disk 1.

Aug 18 10:42:39 host snmpd[1884]: SetDiskResource: skipped disk not backed by vmfs Hard Disk 1.

Aug 18 10:42:39 host snmpd[1884]: SNMPVmodl: refreshing cache completed.

Aside from the above post, the only other result google finds for the message is to a thread suggesting that using the latest MIBs for your monitoring system would resolve the issue, so I copied the MIBs from one of the ESX hosts (/usr/lib/vmware/snmp/mibs/*.mib) over to our nagios server's mib directory, renamed them appropriately for Nagios and restarted the service. However, this doesn't appear to have resolved anything.

Any help that can be provided would be appreciated.

0 Kudos
MRSNMP
Enthusiast
Enthusiast

Appears this message (informationnal level) only appears for VM's with virtual disks that backed by files (vmdk) on filesystems which are not part of vmfs.

COS filesystem local disks and NFS disk mounted on COS come to mind.

The VMWARE-VMINFO-MIB describes it as follows

vmwHbaTgtNum OBJECT-TYPE

SYNTAX DisplayString

MAX-ACCESS read-only

STATUS current

DESCRIPTION

"Identifies the disk as seen from the host bus controller

VIM Property: Virtual Device's with index of 2000-2999,3000-3999.

MOB: https://esx.example.com/mob/?moid=vmwVmIdx&doPath=config%2ehardware"

::= { vmwHbaTgtEntry 3 }

The URL gives you a way to peek at the VIM API data that the snmp agent is using.

0 Kudos