HP Serviceguard for Linux Version A.11.19 Deployment Guide, September 2012

2. If not installed, locate the lm_sensors rpm on the DVD under the Server directory, and install

it. For example:

3. To check if net-snmp is installed, run the following command:

NOTE: By default, net-snmp-libs is already installed. Inspect the output carefully to determine

if net-snmp-5.3.1-24.el5, for example, is installed.

4. If not installed, locate the net-snmp rpm on the DVD under the Server directory, and install it.

For example:

The libXp package is required for Serviceguard Manager.

1. To check if libXp is installed, run the following command:

2. If not installed, locate the libXp rpm on the DVD under the Server directory, and install it. For

example:

rpm -ihv libXp-1.0.0-8.1.el5.i386.rpm

The Serviceguard CIM provider requires the tog-pegasus package.

1. To check if tog-pegasus is installed, run the following command:

2. If not installed, locate the tog-pegasus rpm on the DVD under the Server directory, and install

it. For example:

Storage Array Configuration

The following instructions are for the MSA2000. It has a built-in browser-based management

interface called SMU (Storage Management Utility). The device can also be configured using the CLI.

This document has instructions to use the CLI to configure the IP address, then the remainder of the

configuration steps are shown using SMU.

In this section there are instructions for creating external shared storage to be used for the cluster lock

and for package data.

Connecting the MSA2000 to the Servers

Once the OS has been installed on each server, plug the Fibre Channel cables from the MSA2000

into each server. Make sure the green lights on the cards and controllers are on. If not, double check

that the cables are completely plugged in. See Figure 2 for the wiring specification.

To avoid a single point of failure (SPOF), a path from each server to each storage controller should be

created, providing two paths from each server. The MSA2000 has a feature called “host port

interconnects” that provides high availability using internal connections between the host ports,

providing redundancy in the event that one controller fails. This feature will be configured in a later

step.