Pages

Monday, October 1, 2007

SNMP, Dell OMSA and VMware

If you are using VMware ESX on Dell hardware you need to make sure you have the OpenManage agents installed on the host so that you can get hardware alerts. That said, I ran into some issues last week making six new ESX hosts talk back to the central OMSA server and I found this link. Because the internet changes I will post the important steps that you must take in order to have your ESX hosts show up as something other than “unknown” in the IT Assistant interface.

First, the esx firewall needs to be opened up to allow the various trafic.

esxcfg-firewall -o 1311,tcp,in,OpenManageRequest
esxcfg-firewall -o 162,udp,out,snmptrap
esxcfg-firewall -o 162,udp,in,snmptrap
esxcfg-firewall -o 161,tcp,in,snmp
esxcfg-firewall -o 161,tcp,out,snmp
esxcfg-firewall -o 161,udp,in,snmp
esxcfg-firewall -o 161,udp,out,snmp

Second, make your /etc/snmp/snmpd.conf file look something like this:

### snmpd.conf configuration file

# sec.name source community
com2sec ita 192.168.1.50 ITACommunity

# group.name sec.model sec.name
group itagroup v1 ita
group itagroup v2c ita

# name incl/excl subtree mask(optional)
view all included .1

# group.name context sec.model sec.level prefix read write notif
access itagroup "" any noauth exact all all none

# Added for support of bcm5820 cards.
pass .1.3.6.1.4.1.4413.4.1 /usr/bin/ucd5820stat

# Send traps to the ita box.
trapsink 192.168.1.50 ITACommunity

# Allow Systems Management Data Engine SNMP to connect to using SMUX
smuxpeer .1.3.6.1.4.1.674.10892.1

# VMware MIB modules.
dlmod SNMPESX /usr/lib/vmware/snmp/libSNMPESX.so

Of course you will need to change the ip address to point to your OMSA server and you may want to change the community name as well.

Thanks to the folks over at VMTN for creating such a good resource!