ESX 4 Device only shows CPU and Memory??? How to configure to see Disk and Interface??

HI,

I need to add ESX 4.0 Servers in Solarwinds 9.1. but it shows only CPU and Memory in List resources. Please let me know if tihs is a known issues or I need to configure Solarwinds / ESX 4.0 to resolve this and would appreciate if you can mention the details of configuration?

Thanks in advance.

Ravi

Find more posts tagged with

VMware

9.1

vmware_esx

Accepted answers

ravirsc

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>
trapcommunity <string>
trapsink r<server IP or FQDN> <string>
trapsink localhost
syscontact <Contact Information>
syslocation <Location>
dlmod SNMPESX /usr/lib/vmware/snmp/libSNMPESX.so

Please pass this info to others who are still having issues.

All comments

bshopp

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.

pacetti

The following Knowledge Base article provides a link to documentation that may be helpful:

"How do I monitor VMware vSphere (ESX Server 4) clouds?"

ravirsc

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.

Ravi

ravirsc

Good NEWS for all:

Please pass this info to others who are still having issues.

kupjones

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.