Performance Management Pack

[Nikos101]

Hi there

I am currently running SIM 5.1. monitoring around 70 servers and all is fine and dandy!

The only problem that I have is that I want to be able to use PMP but when I enable the service the MXPASSWORD.exe service thrashes the CPU to near constant 100%. If I turn it off it returns to normal.

Any ideas what might be causing this and how I can resolve the situation?

Thanks in advance.

[Rob Buxton]

I also had an issue with PMP, but in our case it was the HPSIM Database that got thrashed with excessive I/O as soon as the PMP service was started.

It didn't get fixed until I completely rebuilt HPSIM on a new server, fresh install of everything.
I think our issues originated from a server name change / replacement for a PMP licensed server.

You may need to log a call with HP on that one.

[Nikos101]

I was hoping a rebuild wouldn't be the solution!

What benefits does running PMP provide?

[pkrai]

I think SIM service credential got changed & since PMP relies on those credential for accessing SIM service, now it is continuously trying to get that connectivity.

I think it's better to follow documented steps for changing any user credential.

Thanks.

[Nikos101]

All SIM services are running on the correct SIM account? The mxpassword.exe only goes through the roof when switching on the PMP service.

It is fine when not on.

[pkrai]

As the PMP saved password for accessing HPSIM is different from the HPSIM current service password, this issue could be occuring. In order to sync PMP's saved password to that of HPSIM, please try the steps below

1. Stop the HP Performance Management Pack service
2. Launch the MxPassword GUI by running the following command:
a) ~HP\Systems Insight Manager\bin\mxpassword â g
b) Modify the password of the MxHPSIMServicePassword key to reflect the new password
3. Start the HP Performance Management Pack service

See if this helps.

Thanks.

[Nikos101]

I understand what you're saying but I don't understand what I need to change the MxHPSIMservice password to? Will it effect anything else if I do this?

[Nikos101]

I think I have sorted it with your suggestion.

Ran mxpassword util and changed the password, restarted the service. The mxpassword.exe process isn't kicking up at the moment but will keep my eye on it!

Thanks again for your help!