I have the latest vib installed on my ESXi host
~ # esxupdate query
---------Bulletin ID--------- -----Installed----- -------------Summary-------------
ESXi410-Update01 2011-05-02T03:20:23 VMware ESXi 4.1 Complete Update 1
ESXi410-Update02 2011-11-10T08:09:05 VMware ESXi 4.1 Complete Update 2
ESXi410-201201402-BG 2012-02-06T05:41:34 Updates VMware Tools
ESXi410-201201401-SG 2012-02-06T05:41:34 Updates Firmware
Dell_OpenManage_ESXi410_OM650 2012-02-17T06:02:15 OpenManage 6.5 for ESXi410
~ # /usr/lib/ext/dell/srvadmin/bin/dataeng status
dsm_sa_datamgrd (pid 6126 ) is running
dsm_sa_eventmgrd (pid 6666 ) is running
dsm_sa_snmpd (pid 6680 ) is running
C:\Program Files (x86)\VMware\VMware vSphere CLI>vicfg-snmp.pl --server ServerIP --show
Enter username: root
Current SNMP agent settings:
Enabled : 1
UDP port : 162
Notification targets :
but on my OME server
When I run the SNMP test in Troubleshooting tool, i get:
The SNMP read request has failed for Get Community name - xxxx
Under the machine details - Software Agent Information
Server Administrator is flagged as yellow with Agent Version showing as N/A
Hi Lester, thanks for the post.
First I will point you at this thread for setting up ESXi and OME. Be sure to have a look.
for ESXi you just need WSMan, not SNMP for discovery.
The SNMP part for ESXi only comes into play for "traps", not discovery. So the TS tool SNMP test is not relevant here.
I have read the first link before so like Mikey in the 2nd thread, the SNMP configuration threw me a curve ball.
I managed to access the OMSA via another server so that's working fine but it's not showing up in OME, so it's being flagged with a warning.
Lester - I am still in a bit of a pickle with mine, but I might be able to assist you a bit, eventhough I am using 5 and not 4.1
During your discovery/Inventory - what are you using? You should only be using WS-MAN I used Root/Password, checked "secure mode" and "trusted site"
Give that a whirl....
Yeah I did that already after Rob pointed out that SNMP is only used for traps. WS-MAN is setup like yours and working for most part except that I'm not getting anything for OMSA
I misunderstood your statement of "but it's not showing up in OME, so it's being flagged with a warning." meaning that it was still showing as Unknown.
I on the other hand still cannot access my ESXi5 through another server....
Being a guinea pig is not fun
did you try running this from SSH or local tech support mode to check if OMSA is running?
This looks working as expected to me. We don’t get inventory from OMSA in ESXi so I guess we are not getting the OMSA version and are hardcoding it to “N/A”. The health is showing up as warning which is correct and in fact we show that agent row for displaying the health.
We are adding more inventory for this in an upcoming release (not the Q1 release).
Since we are unable to get inventory from OMSA, which includes hardware status. Does it mean that if we have a failure on a harddisk or RAM, there will be no alerts being issued?
We *do* monitor health which includes hardware health. We *don't* get other inventory from OMSA. That is the difference.
But that will not prevent us from telling you when there is a hardware failure. The health status shown in the OMSA Agent row is indicative of hardware health. You can get additional info on the warning status by opening OMSA and drilling in.
This can be a bit confusing and we are doing more work on this in a subsequent release.