SNMP and ESX 4

[NYSDHCR]

Has anyone configured SNMP traps in comjunction with ESX 4 yet? The snmpd.conf file is quite different. del does not have their OpenManage Guide updated yet.

[adamy · Accepted solution]

I am using HP and HP agents, but I used the old SNMP.conf file from a 3.5 U4 system. It works perfectly.

I

[NYSDHCR]

Did you simply copy it over from an ESX 3.5 host and replace the existing one?

[adamy]

yes.

HP is a little different you can use a config file to setup everything you need so you don't have to set up the communities and sink locations, etc, but I copied over the SNMP file and used the same config file

I removed my community strings and placed "use yours here" instead

# vi /etc/snmp/snmpd.conf

1. Following entries were added by HP Insight Management Agents at

2. Mon Oct 12 16:36:05 CDT 2009

dlmod cmaX /usr/lib64/libcmaX64.so

rwcommunity "use yours here" 127.0.0.1

rocommunity "use yours here" 127.0.0.1

rwcommunity "use yours here" bcdseapp01.hrbinc.hrblock.net

rocommunity "use yours here" bcdseapp01.hrbinc.hrblock.net

trapcommunity "use yours here"

trapsink bcdseapp01.hrbinc.hrblock.net "use yours here"

syscontact DL - DS Engineers

syslocation BT11

1. ---------------------- END --------------------

###############################################################################

#

1. snmpd.conf:

2. An example configuration file for configuring the ucd-snmp snmpd agent.

#

###############################################################################

#

1. This file is intended to only be as a starting point. Many more

2. configuration directives exist than are mentioned in this file. For

3. full details, see the snmpd.conf(5) manual page.

#

1. All lines beginning with a '#' are comments and are intended for you

2. to read. All other lines are configuration commands for the agent.

###############################################################################

1. Access Control

###############################################################################

1. As shipped, the snmpd demon will only respond to queries on the

2. system mib group until this file is replaced or modified for

3. security purposes. Examples are shown below about how to increase the

4. level of access.

1. By far, the most common question I get about the agent is "why won't

2. it work?", when really it should be "how do I configure the agent to

3. allow me to access it?"

#

1. By default, the agent responds to the "public" community for read

2. only access, if run out of the box without any configuration file in

3. place. The following examples show you other ways of configuring

4. the agent so that you can change the community names, and give

5. yourself write access to the mib tree as well.

[NYSDHCR]

Thanks for the advice. I just copied one of my snmpd.conf files over from of of my ESX 3.5 U2 boxes, renamed the .conf file on the ESX 4 host, opened the firewall port, restarted the snmpd service, and was good to go!

[adamy]

Your welcome.

Don't forget to award points.