I believe you have to configure net-snmp on those boxes. So you just want to monitor the ESX box or the guests? With vSphere 4, VMWare no longer populates their MIB's we traditionally used with ESX 3.5 to gather guest info etc.
Thanks for the quick response but this was already tried and it does not change anything.
I folloed vsp_4_snmp_config.pdf and added the Proxy command in snmpd.conf and also run the vicfg-snmp.pl commands as per instruction successfully but still it shows only CPU and Memory only in Solarwinds?
Please let me know if I am missing something specific or a detailed command line to follow if you can?
Thanks in advance.
Good NEWS for all:
I used this snmpd.conf which wasn't changed from 3.5 to 4. It is still the same and is working:
rwcommunity <string> 127.0.0.1
rocommunity <string> 127.0.0.1
rocommunity <string> <server IP or FQDN>
trapsink r<server IP or FQDN> <string>
syscontact <Contact Information>
dlmod SNMPESX /usr/lib/vmware/snmp/libSNMPESX.so
Please pass this info to others who are still having issues.
Unfortunately, the above is not a solution. On a virgin ESX4 install that directory and library is not available -- I suspect it is a holdover from an in-place upgrade?
Nevertheless, the bottom-line is neither SW nor VMware are making much headway in providing a solution **FOR THE IMMEDIATE NEEDS** of the customer base. VMware abandoned Net-SNMP for obvious reasons (they needed hostd to provide a full SNMP agent on both ESX and ESXi platforms) and SW is dropping *native* SNMP support for ESX4 in favor of going after the API's.
Either way the end-user is left holding the bag.
kupjones, can you elaborate on this comment of SW dropping native support for ESX4 for SNMP? If we could use SNMP to gather the data like we did with ESX 3.5 we would, however, all the data we gathered is no longer populated in the VMWare MIB, so the only route to get this data for vSphere 4 is to go through the API.
I can only tell you what I got from Denny and what I got from VMware.
From Denny (paraphrased) "VMware has dropped supporting SNMP from ESX4 therefore we (SW) are not updating Orion to support ESX4 via SNMP out-of-the-box. Vmware is not fully populating the VMware MIBs so there is no point. SW is building in support for Vmware API in order to get the data."
From VMware (paraphrased): "Absolutelly all MIBs are being populated with the data as before, with a few non-essential vars not being populated (yet). They will be on the next update. The primary change was to go to HOSTd rather than Net-SNMP so that full SNMP culd be supported for both ESX and ESXi."
End result? The customers are caught in the cross-fire asking "Who is right, who is wrong here?" Also, does it really matter? The current SNMP support in ESX4 *can* be accessed and *can* provide some data. The sad truth is SW is not doing the following:
1> Going ahead and provideding a built-in workaround for what is exposed (I can see the data through MIB Walker) via an NPM patch
2> Building a UnDP for the masses that we can at least use in the meantime.
I see neither, just a "Wait for the release that supports the API." Not helpful