Recently I was at a customers site doing a vSphere 4.1 upgrade, and SAN expansion. I configured ESX hosts with SNMP monitoring for proactive support with Insight Remote Support for call home functionality with alerting incase of hardware failures. Here are three good points I came across in dealing with SNMP monitoring configurations:
1) If you deploy the latest 4.1 image through HP Insight Server Deployment Console you won’t have to install the HP agents. I really like this saves a lot of time.
Note: If your not using the HP Insight Server Deployment then you can get the agent here at this link you will have to manually install it. It is pretty lengthy more than just an RPM. You can just take all the defaults then modify what I am showing in step 2 below.
2) The easiest way to configure the settings is post install through the systems management homepage. You can just configure one system then copy its configuration show in the System Management Homepage to other ESX hosts System Management Homepage. Below is the information that you will want to copy from the host. Alternatively, if you are just starting out fill out the information below in <> to your desired configuration and your good to go.
dlmod cmaX /usr/lib64/libcmaX64.so
rwcommunity <your private community name>127.0.0.1
rocommunity <your public community name> 127.0.0.1
rwcommunity <your private community name> <your ip of Insight Control server w/ Remote Support>
rocommunity <your public community name> <your ip of Insight Control server w/ Remote Support>
trapcommunity <your public community name>
trapsink <your ip of Insight Control server w/ Remote Support> <your public community name>
syscontact Root <root@localhost> (configure /etc/snmp/snmp.local.conf)
syslocation Unknown (edit /etc/snmp/snmpd.conf)
3) Don’t forget when sending test traps you have to comment out the line in /etc/sudoers on each ESX box “Defaults requiretty” 
on 
on 
Twitter
RSS
LinkedIn