|
This is going to be an ESX config issue - I know at least one person has this working with ESX 3, so I'm pretty sure that it can work - but since I don't have an ESX 3 server here I can't do anything to track down what the required config should be.
The 'No VMware SNMP sub-agent' message is caused when the script is unable to walk the vmware OID tree, either because
1) no response from the SNMP agent - not running?
2) the vmware snmp helper agent is not running
3) there is a firewall blocking communication
4) the community string is wrong
5) everything is too slow and times out
6) ... something else ...
Try getting version 2.4 of check_esx2 -- this gives slightly better help messages, and is better with v3 -- but I don't think this will solve the issue. If anyone out there can confirm it is working with ESX3, please post here and say what you needed to set up for the SNMP to work.
_________________ Steve Shipway UNIX Systems, ITSS, University of Auckland, NZ Woe unto them that rise up early in the morning... -- Isaiah 5:11
|