Installing and upgrading HP Insight Management 7.2 on Windows Server 2012 Failover Clusters

White paper | HP Insight Management 7.2
15 | March 2013
Create the shared disks W:, T:, S:, and V: on the SAN and present them to the cluster nodes,
but do not “online,” “initialize,” or “create” a volume for any disk until instructed to do so in
Creating the Failover Cluster.
Supporting Systems
It is assumed that an existing Active Directory domain infrastructure and DNS services suitable for
hosting the cluster are available. Multi-site clusters are not supported.
If the Insight Management SQL instance is to be hosted in another cluster, that cluster must be in
the same domain as the Insight Management cluster.
Network
Microsoft Failover Clusters require that each virtual server in a cluster have a unique 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 15.199.242.161 and the name is CMS-C16-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
15.199.242.164 and the name is CMS-C16-MATRIX.
3. Microsoft SQL Server virtual server and client access point
Function: To act as the virtual server IP address and name for the Microsoft SQL Server
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 15.199.242.163 and the name is CMS-C16-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. In the examples discussed in this white paper, the IP address is
15.199.242.162 and the name is CMS-C16-DTC.
Another two static IP addresses and names are needed for the primary and secondary
systems.