Unable to access HP Insight Managment Homepage after upgrade

[John Ferrell]

I've upgraded several HP ProLiant servers (W2K3) to Support Pack 7.3 and HP Systems Management Homepage for Windows to 2.1.0.121. Now I am unable to access any of these systems remotely using http://systemanme:2381. I can open the Homepage if I am logged onto the server. But from my insight Manager, I can no longer determine the version of software or access any of the server links to one of the servers I've upgraded if the OS is W2K3. I upgraded a couple W2K server with the same support packs and they still work fine.

I've checked the security settings and am still using default values. I do trust by certificate and do have a valid certificate to the IM server.

Any thoughts as to what I can do?

[John Ferrell]

Sorry. I meant to type https://:2381.

[Asaf Ben Harrush]

Hi John

I had the same problem in my servers.
I resolved it with this procedures:

- uninstall the hp homepage from the problemtic server

- Uninstall the HP version control repository agent from the problemtic server

- restart the server
- copy the server certificate file from c:\hp\hpsmh\certs Ex. mrhmgm61.pem to temp directory.

- install manualy the hp home page (cp005390) and in the user authority section fill "domain name"\domain ,in the section of the certificate trust browes to the certifacate that in the temp folder and finish the installation.

- check the connection from the remote computer to the server.

- install the version control agent.

I've done that and the problem resolved.
I hope that I've helped you .

Best regards
Asaf Ben Harrush

[Tom Parker_1]

Are your computers multihomed on the same NIC? This seems to be a problem with 2.1.0.121. It listens on the wrong IP address. If this is the case downgrading should fix the problem.

[John Ferrell]

It appears the problem is only occurring on my web servers. It does not appear to happen on other servers. Perhaps there is some conflict between the web application and the web server services?

[Tom Parker_1]

Your web servers are the only ones that are multihomed probably. If you are running 2.1.0.121, then downgrade to the prior version. I have done three of them today and it has fixed the problem immediately.

[Mark Hassman]

Not sure if this helps, but in v2.1.0.121.. it will only listen on the secondary ip on a nic (haven't tried more than two ips yet) - completely ignores the primary ip. I've even tried manually specifying the primary ip within smhpd.conf.. just removes the entry on startup. Reinstalling v2.0.2.106 fixed it.

fyi.. if this happens on your version control manager server, all agents loose version control capability.


-Mark

[Tom Parker_1]

I have found exactly the same thing as Mark. In fact I first noticed it on my version control repository server. A call to HP was not helpful and prompted such questions a why would anyone want to bind more than one IP address to a NIC. Luckily I discovered downgrading solved the problem.