New version of HP Insight Management Agents for ESX 3.0.x is available in hp.com. It can be downloaded from the URL http://h18007.www1.hp.com/support/files/server/us/download/27853.html
Note also that I don't think VMware has "blessed" these agents yet. Its been our experience that if you install agents before they give them the green light they won't support the configuration when you have problems that may be associated with them.
The reason I mentioned it is because we had a storage outage for all the hosts in one of our 2.5.3 farms that VMware attributed to the HP storage agents locking our LUN's. We were using HP agents that were a revision ahead of what they had blessed. I don't think they ever definitively identified the problem since it only happened once but they can and will place blame if given the chance.
I'm not talking about the Management Agents - I'm talking about the managment home page. This is the webserver that provides a interface from a browser, generally via https over TCP 2381, to the management agents.
I guess the real question is ESX 3.02 based on x86 or EM64T?
I removed 7.7 agents and went to 7.9 now I'm having issues with cmahostd spawning zombie processes every 5 minutes.
root 401 1 0 13:49 pts/0 00:00:00 cmahostd -p 15 -s OK
The sh <defunct> keeping growing, new one every 5 minutes. If I service hpasm restart they clear but start coming back. Anyone else seeing this?
Good catch, I would open a ticket with VMware on it. Since VMware has "blessed" the agents, that supposedly means they've tested and approved them so I would assume they could channel the work through HP, but they may just point the finger. Let us know what you find, we're sticking with 7.8 for now.
we have exactly the same issue !!!!
All ESX host DL385 G1 and G2 are running 3.0.2
We have updated the agents to 7.9.0 last week, and now we have those defunct processes on all systems.
Any news ? Did you already open a SR with VMware or HP ?
Same issue here as well on BL685C G1 and DL585G1/G2.
Opened case with HP a little while ago. They are aware of this issue but so far no solution. Anyone get any valuable information from HP?
I will update as I get more information from HP.