Installing and upgrading HP Insight Management 7.0 on Windows Server 2008 R2 Failover Clusters

10
Network
Microsoft Failover Clusters require that each virtual server in a cluster have a unique static IP address
and network name registered in the DNS. For the configuration described in this white paper, four
static IP addresses are required for the following four virtual servers. An additional two static IP
addresses are needed for the physical nodes.
1. Failover Cluster virtual server and the client access point
Function: To act as the virtual server IP address and name for the Failover Cluster software.
Suggested action: Windows management tools use this address to get the status and manage the
Failover Cluster software. In addition, Systems Insight Manager uses this address to discover the
Failover Cluster. For the examples discussed in this white paper, the IP address is 16.92.155.183
and the name is CMS-C2-CLUSTER.
2. Systems Insight Manager and Insight Management virtual server and the client access point
Function: To act as the virtual server IP address and name for Systems Insight Manager and Insight
Management. You specify this name and address to connect to Systems Insight Manager through
your browser.
Suggested action: All SNMP devices that report their events to Systems Insight Manager should use
this IP address and name for the location of the Event Consolidator, also known as the SNMP Trap
Destination. The host defined for the WMI Mapper proxy should use this name and IP address
(unless the WMI Mapper service runs on a system that is not a cluster member and the WMI
Mapper is not installed as part of Insight Management). For the examples discussed in this white
paper, the IP address is 16.92.155.186 and the name is CMS-C2-HPSIM.
3. Microsoft SQL Server 2008 R2 virtual server and client access point
Function: To act as the virtual server IP address and name for the Microsoft SQL Server 2008 R2
Enterprise database software. This software is used to extract, manipulate, or back up the Insight
Management and Systems Insight Manager databases.
Suggested action: The Systems Insight Manager Open Database Connectivity (ODBC) data source
uses this virtual server IP address and name as the location where the CMS Systems Insight
Manager DNS points. In the examples discussed in this white paper, the IP address is
16.92.155.185 and the name is CMS-C2-SQLSVR.
4. Microsoft Distributed Transaction Coordinator virtual server and client access point
Function: To act as the virtual server IP address and name for the Microsoft Distributed Transaction
Coordinator service. This service coordinates transactions that are distributed across a cluster.
Suggested action: Microsoft Distributed Transaction Coordinator is installed with Microsoft SQL
Server 2008 R2. In the examples discussed in this white paper, the IP address is 16.92.155.184
and the name is CMS-C2-DTC.
Another two static IP addresses and names are needed for the primary and secondary systems.
5. Failover Cluster primary system IP address and name
Function: To serve as the TCP/IP address and name of the specific Microsoft Windows server host.
Suggested action: Any software that references system-specific functions uses this address to
connect to this system. In the examples discussed in this white paper, the IP address is
16.92.155.179 and the name is CMS-C2-N1.
6. Failover Cluster secondary system IP address and name
Function: To serve as the TCP/IP address and name of the specific Microsoft Windows server host.
Suggested action: Any software that references system-specific functions uses this address to
connect to this system. For the examples discussed in this white paper, the IP address is
16.92.155.180 and the name is CMS-C2-N2.
The “16.” network referenced previously is the public network used by clients to access the clustered
services. Failover Clustering also requires a private network to be implemented for internal cluster
communication. The Failover Cluster primary and secondary systems each have static IP addresses on
the private network. In this white paper, the “10.” network is used as the private network.