Comments on: Why I dislike agents in my Service Console

By: Dean

Dean — Thu, 04 Sep 2008 14:19:58 +0000

Are you using HPSIM 8.1? 8.1 is required for 3.5 U2

http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?swItem=MTX-62350b0bf98a442fb3c1cb1154&lang=en&cc=us&idx=0&mode=4&

By: Jason Boche

Jason Boche — Tue, 02 Sep 2008 13:09:23 +0000

Duncan FYI:

VMware KB article: Feature by feature comparison of ESX versus ESXi

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1006543

Duncan, do you have an email address that you could give me? Thank you, Jas

By: Geir Ingebrigtsen

Geir Ingebrigtsen — Tue, 02 Sep 2008 08:36:40 +0000

I must agree with Susan as well.

While agents on the Service Console is not always a good thing, this time the problem clearly lies with the Pegasus service in ESX, and not with the agents from HP.

In other words – we must wait for VMware to create a patch, and meanwhile configure our SIM servers correctly.

By: Duncan Epping

Duncan Epping — Mon, 01 Sep 2008 14:40:39 +0000

@ john: via a perl or powershell script from within a VM or the VC it should be possible if you have a IP-Enabled UPS.

By: Awinkel

Awinkel — Mon, 01 Sep 2008 10:27:20 +0000

I agree with Susan. Today I had the same issue and after making a local account at the ESX servers and changing the config of SIM anything seems to work fine. But the rest of the day I keep my fingers crossed.
See also this topic: http://communities.vmware.com/thread/159728?tstart=0

By: Susan Larden

Susan Larden — Sun, 31 Aug 2008 22:22:29 +0000

Heads up on this – the answer is within your SIM console set the WBEM user id and password under system protocols to be a valid user on the esx host. This seems to resolve the issue. By default it uses a domain account that has been set as a global account to use

By: Everett Alvarez

Everett Alvarez — Thu, 28 Aug 2008 20:25:19 +0000

I was in an HP enviroment and we ran into multiple issues with HP agents running on ESX. As previously posted before they told us to upgrade the firmware and etc….. So boo for agents running in esx…

-everett

By: John

John — Thu, 28 Aug 2008 15:01:15 +0000

OK – question though. How are we going to make the ESXi systems UPS aware?

I just bought a big Symmetra box but even at 43% load I only get 35 minutes of run time.

By: Virtualization Short Take #17 - blog.scottlowe.org - The weblog of an IT pro specializing in virtualization, storage, and servers

Thu, 28 Aug 2008 14:08:42 +0000

[...] alerts us to a potential problem with HP Insight Manager agents on VMware ESX 3.5 Update 2. I share Duncan’s view; I try to avoid agents in the Service Console wherever possible. [...]

By: Dave Convery

Dave Convery — Thu, 28 Aug 2008 11:49:44 +0000

This isn’t something new with the SIM agents. Ever since ESX 3.0 came out and HP released an agent, there has been SOMETHING wrong with each version. HP’s response is to upgrade the firmware and agent version. You get to the highest level of each and there is a new problem. I have heard about the cimservera stuff for a while now…