System management homepage not available.

[Colin Yates]

Trying to connect to a remote servers smh when connecting to :2301 and "the page cannot be displayed" error message is returned. I can sign onto the server itself and run the smh locally no problem. I've tried running the repair agents applet to no effect. Has anyone any suggestions?

[david mcdonald_5]

Did you try changing the port from 2301 to 2381 ??

[Colin Yates]

Yes, same issue on either tcp port.

[david mcdonald_5]

did you also check the trap settings so they point to the SIM server, and can the server accept packets from any host under the security tab for the SNMP service, if so you could restart the agents and see what happens. the only other thing i can think of off hand is the trust settings how are they configured ??

[Rich Purvis]

Colin,

[Rich Purvis]

Colin,
You might try checking the SMH settings. There is one for IP restrictions, that if set, would only allow you to browse from machines using that IP range. That may be blocking you from connecting.

-Rich

[Rich Purvis]

Oh I guess it also could be a DNS issue - have you tried browsing using the IP address instead of the servername?

http://:2301


-Rich

[FrankW]

Does this server have more than one IP address?

I have this issue since I applied a baseline containing SMH v2.1.0.121. If I specity https://:2381 then explorer fails to display anything, even using a FQDN for servername. If I specify https://10.1.1.10:2381 (the server's primary IP) then same result, BUT if I use https://10.1.1.20:2381 (one of the secondary IP's) then it works just fine.

This is resulting in a "trust issue" being reported by SIM4.2sp2 for version control status.

I do NOT have IP Binding turned on, and my efforts to experiment with it have not at all improved the situation.

[Gregory J. Kotula]

I am also having this problem with SMH 2.1.0.121 on machines with multiple IP addresses. I can browse to https://secondaryipaddress:2381, but not to https://primaryipaddres:2371.

[Sakti Chakravarty]

I had a similar issue which turned out to be related to the browser proxy settings.

I had a proxy server set, but had to specify the domain name for the CMS in the list of addresses to bypass the proxy.

Give that a go, maybe it will help ...

[FrankW]

Not proxy-related. Again, forgetting at all about hostnames, our tests have focused around using IP addresses in the URL's. As well, the SIM server does not use a proxy at all.

I would like to re-iterate that this ONLY happens with managed servers with more than one IP address, such as MSCS clusters and IIS servers with multiple IP's.

[NJK-Work]

I have the same problem with 3 machines after upgrading to SMH 2.1.0.121.

Got two working by rebooting. However one of the two still has a trust problem, but at least it will prompt for a user name and password.

The third one still not working is behind a firewall. So that may be complicating

All three servers have 2 NICs.

Fixed the slow logout due to the SMH - now we have this fun problem to deal with....

Nelson

[NJK-Work]

Actually, my trust relationship went away now (just checked it again). So the two are back to normal.

I think all I did was reboot them to fix the problem. But I may have reinstalled the SMH 2.1.0.121 on one of them before the reboot.

Nelson

[John Richards_9]

I was wondering if there is a fix for SIM on a server that has multiple IP's. We have two W2K3 servers that are clustered ie. the second IP on both servers is the same. I can get to one home page but not the other.

Thanks

[Rich Purvis]

Is this a failover cluster? If so, 2 servers cannot have the same IP at the same time. Do you mean that the cluster IP is active on one server and when it fails over to the 2nd server the SMH will not come up on the cluster IP when it goes active on the 2nd server? If you stop and restart the SMH service it will pick up the new IP address. In the future there may be a configuration entry for the SMH that will cause it to restart and pick up new IP addresses upon an IP configuration change that occur after initial startup. Because of unknowns that can occur in the dev/qa cycle the best that can be said right now is that it is being looked at for a possible future release.

[Ferry Steenvoorde]

Colin,

Apart from the clustering issues, there may be network issues as well.
If your managed systems are behind a quite restrictive firewall, you will need both ports 2301 and 2381 from and to the HPSIM-server. When Automatic Discovery is running, the process tests whether it is able to connect using these ports. If so, you should be able to connect directly from the HPSIM-server to the SMH and the Version Control Manager.

If these ports were not open during the last Automatic Discovery, you will not be able to connect.

[John Richards_9]

I have found the solution. HP now has a new fix available. From HP (Version 2.1.3.132):

Resolved the following:
IP Binding issue wherein Windows systems with System Management Homepage 2.1.0 or 2.1.2 installed, which have more than one IP address assigned to any of the systems network adapters, will only recognize one IP address per adapter.

I have installed it and works like a charm.

Thanks

[Nouvel1]

Hi,

does this issue has been solved by HP? In fact I have the pb with the latest version of SMH (v2.1.6.156) on a Proliant DL380 G4 server. The HP Agents are also up-to-date (v7.60.0.0).
I have 2 IP on my machine, and SMH only bind on one IP instead of the 2 IPs, in fact I noticed that it always binds on the last IP in the IP list of the machine. This is a pb for me as it is mandatory for me to have the bind on the first IP.
Thanks.

[Holger_4]

Hello,

this issue seems not to be related with HP System Management Homepage v2.1.6.156 because I tested to bind additional IP addresses to the NIC and after a restart of the SMH the connection worked on all IP addresses. a Check with "netstat -a -n" shows for all IP addresses LISTENING for ports x.x.x.x:2301 and x.x.x.x:2381.

Do you see the same?