Cannot Access System Management Homepage Remotely on NLB Cluster

[JonU]

Hello,

Allow me to explain my scenario:

I have a two-node Microsoft NLB cluster running Terminal Services and the Session Directory Service. Both nodes have are running the HP Insight Management Agents and the HP System Management Homepage. Also, I can access the SMH locally using the loopback network address (127.0.0.1).

Where things start to get hairy is with the network configuration for the production interface. I set up NIC teaming using the HP Network Configuration Utility, and I am using the Network Fault Tolerance Only mode (NFT-only) for load balancing.

The problem is that when I open the SMH locally on either node of the NLB cluster, I find that the management agents detect a problem with the production network NIC team. The SMH indicates that it thinks the NIC team is using Transmit Load Balancing (as opposed to NFT-only which is set via the HP network config utility). When I check the status on this network team in the SMH I see the following error: "Status: Unknown enumeration value 244."

I checked the port status of my server using "netstat -an" and it is clear that the server is not listening on any of the production interface's multiple IPs on ports 2301 or 2381. Could the problem have something to do with the fact that there are multiple IPs assigned to the production NIC team due to NLB clustering? I don't have a problem with this on my other non-NLB servers.

Does anybody have any ideas on this one?

Thanks in advance,

Jon

 P.S.This thread has been moved from ITRC server mgmt (Insight Manager 7) Forum to ITRC HP Systems Insight Manager Forum- HP Forums Moderator

[JonU]

Oh and most importantly, I cannot access the SMH for these 2 server remotely using the standard http://{server name}:2301.

[Rich Purvis]

What version of SMH do you have installed? There was an older issue where it would not correctly bind to all the IP addresses correctly, but that has been corrected in recent releases.

-Rich

[AldoGarcia]

Jon,

Did you solve the issue? I am having the same problem now.

Thanks,

AG

[Bryan P. Jones]

I found the same issue - but only occurring on the 2nd node of my 2 node NLB terminal services cluster. I too am using HP NIC teaming.

Running "netstat -an" I noticed that ports 2381 and 2301 were binding to the cluster IP rather than the dedicated machine IP on the 2nd node (even though my NLB cluster specified port 3389 ONLY).

I suspected that since NLB creates a secondary IP (the cluster IP) on the network interface that the SMS homepage decided to bind to this IP.

Taking a long shot, I stopped the node in the NLB cluster and deleted it from the cluster. Then I restarted the HP System Management Homepage service.

"netstat -an" now showed ports 2381 and 2301 binding to the machine IP (since the cluster IP doesn't exist anymore!).

I verified that SMS is accessible on the machine IP as well as the loopback IP, then added the node back to the NLB cluster.

After adding it back, SMS is still accessible on the machine's dedicated IP.

I just did this 10 minutes ago - we'll have to see if it continues to "stick" after normal NLB convergence occurs when these machines are rebooted!

[Bryan P. Jones]

Oh.. yea... Version 7.40 and Server 2003 SP1.

SMH is not reporting any problem with the NIC team, however.