In 3.5 i would modify the cd/etc/snmp/snmpd.conf file to setup SNMP.
A sample of the file is below
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.
#syscontact root@localhost (edit snmpd.conf)
#syslocation room1 (edit snmpd.conf)
#rocommunity public
#trapcommunity public
#trapsink localhost
syscontact server tech
syslocation Server Room
rwcommunity xxxxxx
VMware MIB modules. To enable/disable VMware MIB items
add/remove the following entries.
#dlmod SNMPESX /usr/lib/vmware/snmp/libSNMPESX.so
smuxpeer .x.x.x.x.x.xxxx.x.x.x.x.x.x.x
how would i get the same info into ESXI?
You can also try this. Fromyour Virtual center, Click on the Administration link, The one to the right of the Inventory link, Click the VirtualCenter Management Server configuration, Click on the SNMP link, Add all your information here.
Hope that helped.
im talking about configuring SNMP on the ESXI host not Virtual center
With ESXi you can use the RCLI command vicfg-snmp to configure SNMP. Note that the SNMP agent for ESXi only supports traps and not gets. For details see page 97 - https://www.vmware.com/pdf/vi3_35/esx_3/r35/vi3_35_25_admin_guide.pdf
anyone get this to work with solarwinds?
I am having problems too getting SNMP to turn on.
I am using ESXi installable, and when I use the vicfg-snmp command for anything, I get this error:
Failed : fault.RestrictedVersion.summary
I'm using a Dell PowerEdge 2950 without a DRAC card... but I'm trying to get things working with the built in BMC card. The damn thing only works over IPMI, and it too doesn't have SNMP either.
It seemed somene mentioned in these forums that SNMP doesn't work on ESXi installable.. does anyone know if this is true?
i was able to get it to work by doing the following
vicfg-snmp --server <ESX_IP_addr> --username root --password <password> -c <community> -p 161 -t <solarwinds server name>@161/<community>
vicfg-snmp --server <ESX_IP_addr> --username root --password <password> -E
vicfg-snmp --server <ESX_IP_addr> --username root --password <password> -s
vicfg-snmp --server <ESX_IP_addr> --username root --password <password> -T
You may want to check your licensing. There were apparently some issues with OEM licenses that caused this type of issue. Open an SR and vmware may have a fix for you.
-KjB
I am using ESXi installable, and when I use the vicfg-snmp command for anything, I get this error:
Failed : fault.RestrictedVersion.summary
See a thread around this: http://communities.vmware.com/message/841499
I'm using a Dell PowerEdge 2950 without a DRAC card... but I'm trying to get things working with the built in BMC card. The damn thing only works over IPMI, and it too doesn't have SNMP either.
I believe BMC supports SNMP traps. You need to go the BMC menu and enable the traps. It has been a while and i might be wrong, but i think you have to go to "lan parameter" and enable "lan alert" and provide the alert destination.
It seemed somene mentioned in these forums that SNMP doesn't work on ESXi installable.. does anyone know if this is true?
SNMP does work with ESXi. Here is a Dell document that you might find useful. http://support.dell.com/support/edocs/software/eslvmwre/EN/VES_3i/Systems%20Management%20Document/PD.... The link may break if the doc is updated. You can find the document at: http://support.dell.com/support/edocs/software/eslvmwre/
Hope this helps.
Bala
Dell Inc
I don¹t have an OEM version. I bought and got the licenses direct from
Vmware.
I¹ve tried in the Advanced Config/Vmkernel options to disable the OEM
extensions, still with no luck.
I'm going to double check if I have the lan alert on.
Using the BMC card for SNMP will be a good workaround, but ESXi should allow
you to use these things.
In the VI client, the health status shows the status of all my hardware, so
it's not like it can't interface w/ the CIM.
Thanks for the tip Bala.
-Chris
I was able to get to work if I changed the licensing to unlisenced server or to evaluation mode.
Once I did that, vicfg-snmp worked just like it was expected too.
So it does indeed seem to be a lisence issue.
Try tempoarily switching your lisence settings and see if it works for you guys too.
Now the question is will support help me even though I didn't pay for support, and are they going to tell me that my ESXi Installable Standalone for 2 CPUs lisence does not entitle me to the SNMP agent.
I will kill someone if that is true.
-Chris