Hi !
I'm using snmp on ESX3.0.1. But each snmp request from the management server generate many line on /var/log/message such as :
Apr 19 04:22:18 vmware-esx01 snmpd\[18206]: SNMPVmodlRefreshCache: Beginning refresh.
Apr 19 04:22:19 vmware-esx01 snmpd\[18206]: SNMPVmodlRefreshCache: Examining Virtual Machines.
Apr 19 04:22:19 vmware-esx01 snmpd\[18206]: SetVMInfo: Entering function.
Apr 19 04:22:19 vmware-esx01 snmpd\[18206]: Allocating string 'xxxxxxxxxxxxx'
Apr 19 04:22:19 vmware-esx01 snmpd\[18206]: Allocating string 'Red Hat Enterprise Linux 3'
Apr 19 04:22:19 vmware-esx01 snmpd\[18206]: Allocating string '/vmfs/volumes/xxxxxxxxxx'
Apr 19 04:22:19 vmware-esx01 snmpd\[18206]: Allocating string 'poweredOn'
Apr 19 04:22:19 vmware-esx01 snmpd\[18206]: Allocating string 'notRunning'
Apr 19 04:22:19 vmware-esx01 snmpd\[18206]: SetNicInfo: Entering function.
Apr 19 04:22:19 vmware-esx01 snmpd\[18206]: Allocating string 'Network Adapter 1'
Apr 19 04:22:19 vmware-esx01 snmpd\[18206]: Allocating string 'VM Network'
Apr 19 04:22:19 vmware-esx01 snmpd\[18206]: Allocating string 'monitor_dev'
Apr 19 04:22:19 vmware-esx01 snmpd\[18206]: SetStorageHBA: Entering function.
etc...
etc...
It seems to be produced by the call to "libSNMPESX.so".
I would like to know the way to stop this, all these informations are not usefull and increase the /var/log about 20MB each week...
Thanks for your help !
Message was edited by:
Erlo
If you have a 3rd party agent installed, then you might want to check out the instructions on page 62 of this document:
Thanks for your answer but unfortunally this document doesn't answer to my question.
Everything works well, it's just the log level which should be changed about the snmp daemon, and especially about the SNMPESX module. (which seems to be the source of generated log)
Is there any logging settings in your etc/snmp/snmpd.conf config file ?
Hey No ! that is the problem, the module is just loaded just by the following line
dlmod SNMPESX /usr/lib/vmware/snmp/libSNMPESX.so
I'll look on the side of syslog configuration, but i would prefer solve this directly from snmp daemon config...
Can you post up your /etc/init.d/snmpd script please ?
I don't have an ESX server to look on.
I post my snmpd.conf :
cmaX is a module for integrated information about the HP proliant Server into the MIB
the following script vmware-vmfs and vmware-stats integrated informations about the esx into the MIB.
i'm using net-snmp.
For the moment i set my syslog.conf to skip snmpd log.
\----
\# Following entries were added by HP Insight Management Agents at
\# Thu Mar 22 08:39:31 CET 2007
dlmod cmaX /usr/lib/libcmaX.so
rwcommunity public 127.0.0.1
rocommunity public xxx.xxx.xxx.xxx
trapcommunity public
trapsink xxx.xxx.xxx.xxx
syscontact root@localhost
syslocation Salle machine
\# \--
\# Sample snmpd.conf containing VMware MIB module entries.
\# This is a simple snmpd.conf that may help you test SNMP.
\# It is not recommended for production use. Consult the
\# snmpd.conf(5) man pages to set up a secure installation.
\# VMware MIB modules. To enable/disable VMware MIB items
\# add/remove the following entries.
dlmod SNMPESX /usr/lib/vmware/snmp/libSNMPESX.so
#exec .1.3.6.1.4.1.2021.1000.1 memory /bin/cat /proc/vmware/sched/mem
#exec .1.3.6.1.4.1.2021.1000.2 cpu /bin/cat /proc/vmware/sched/cpu
exec .1.3.6.1.4.1.2021.1000.10 vmware /opt/supervision/vmware-stats
exec .1.3.6.1.4.1.6876.800 vmware-vmfs /opt/supervision/vmware-vmfs
Looking at a man page for snmpd it might be able to control the logging level when the service is started, which is why I was interested to see what /etc/init.d/snmpd did.
According to the man page I was reading you might be able to use a -Lf option to direct the log messages to another file.
thank you for your help!
actually i remove the '-s' option to disable the syslog... It's a quite brutal but i won't have log increase probleme in the future
thanks!!
No problem.