Using HP Insight Software from a Highly Available Central Management Server with Microsoft Cluster Service

MS SQL Server 2005 may automatically assign a TCP/IP port number to the SQL Server instance.

The port number is required to install Insight software components. Generally, the Insight Control

Manager installer will automatically determine the SQL Server port number. However, the TCP/IP

port of the SQL Server instance may be determined by following these steps:

a. Run SQL Server Configuration Manager

b. Expand SQL Server 2005 Network Configuration in the left panel

c. Select Protocols for

InstanceName

in the left panel, where

InstanceName

is a placeholder

for the named instance of SQL Server 2005

d. Double-click TCP/IP in the right panel

e. In the Protocol tab, note the value of the Listen All item

f. In the IP Addresses tab:

i) If the value of Listen All is yes, the TCP/IP port number for this instance of SQL Server

2005 is the value of the TCP Dynamic Ports item under IPAll

ii) If the value of Listen All is no, the TCP/IP port number for this instance of SQL Server

2005 is the value of the TCP Dynamic Ports item for a specific IP address

Refer to the article “How to connect to a named instance of SQL Server 2005 or SQL Server 2000

by using the client tools in the earlier version of SQL Server” at http://support.microsoft.com (search

for “How to connect to a named instance of SQL Server 2005 or SQL Server 2000 by using the

client tools in the earlier version of SQL Server”), or the article “How to configure an instance of

SQL Server to listen on a specific TCP port or a dynamic port” at http://support.microsoft.com (search

for “How to configure an instance of SQL Server to listen on a specific TCP port or a dynamic port”)

for more information on how to determine the port where the SQL Server instance is listening.

9. Continue to follow the ICM installation instructions.

10.When prompted for VSE Local Data Storage directory, be sure to specify a directory that is on the

shared disk.

11.Click Install. The installation of ICM components is initiated.

REMINDER: The installation of ICM components will cause a reboot. Be sure the other node of the

cluster is now shutdown; otherwise physical resources such as shared disks, SQL server, etc. will

failover to the other node resulting in a failed ICM installation.

12. To specify that any configuration change in the list of available IP addresses should automatically

reconfigure System Management Homepage (SMH), restarting it when needed, edit the smhpd.xml

file located in the c:\hp\hpsmh\conf directory to insert:

<monitor-ip-changes>1</monitor-ip-changes>

immediately following:

<localaccess-type>Anonymous</localaccess-type>

and save the file. Restart the “HP System Management Homepage” service from Services console

under Administrative tools.

Installing Insight software components on the secondary system

To have a clustered installation of HP ICM, the second system in the cluster must complete the

installation process as well, with a few differences in the procedure to account for the existing

program files on the cluster disk.