topic VMWare ESX 3.5 update 2, SIM Agent 8.1.0 in Server Management - Systems Insight Manager

VMWare ESX 3.5 update 2, SIM Agent 8.1.0

Jon_175 — Thu, 20 Nov 2008 20:41:09 GMT

I have installed the VMWare 8.1.0 agents on 2 different DL380 G4 servers running VMWare ESX 3.5 update 2, and when I go to the health state screen it looks like the only agent working is the Utilization agent. All the other main agents are not green (they just have a purple box around them with no green check box) and can't pull up any useful information when I select them. The agents on the screen that don't appear to be working are (System, Recovery, and Storage). I don't see my nics agent at all. Not sure if this is normal or not. I would like to view details about the system from the agent. Any ideas?

Re: VMWare ESX 3.5 update 2, SIM Agent 8.1.0

Ervinck Kevin — Mon, 24 Nov 2008 14:31:58 GMT

Look if the hpasm service is running, you also might need to restart it.
Also check to install the latest VMware 8.1.1 agents which are now also supporting VMware ESX 3.5 update 3.

Re: VMWare ESX 3.5 update 2, SIM Agent 8.1.0

Jon_175 — Mon, 24 Nov 2008 14:36:08 GMT

I finally got it working. I did load the new 8.1.1 agents and when I configured them it walked me through the creation of a new snmpd.conf file. Apparently I was missing something in the conf file. The 8.1 agent install asked if you wanted to use the existing conf file but it didn't modify the file if answered no.
Not sure exactly what I was missing but having it re-create the snmpd.conf file corrected the issue and allowed the other agents to start functioning.

Re: VMWare ESX 3.5 update 2, SIM Agent 8.1.0

Ole Thomsen_1 — Mon, 24 Nov 2008 17:46:42 GMT

My experience when installing 8.1.0 is that if you answer "no" (to keep existing snmpd.conf) it actually resets configuration to default.

Happened to me on all servers in a 3-node cluster.

Ole Thomsen

Re: VMWare ESX 3.5 update 2, SIM Agent 8.1.0

Rob Buxton — Mon, 24 Nov 2008 19:08:19 GMT

I recommend editing up the hpmgmt.conf file and using that in a silent install.

For an updated release I just compare the two .example files to see if there are any differences and if not re-use the one from the previous install.
It gives a consistent and working snmpd.conf file each time.