Compatibility Information and Installation Requirements

Before you begin an installation, read this entire document and any other Release Notes or READMEs you have.

Compatability

This section summarizes the compatability of this version of Serviceguard Manager with related products and their versions. For all versions (this and older), see the Serviceguard Manager Support Matrix posted on http://www.docs.hp.com/hpux/ha -> serviceguard -> white papers

Hardware Requirements

Serviceguard Manager will run on the HP 700 Series workstations and the HP 800 Series servers.

Serviceguard Manager will run on a PC with a Pentium II 450 MHz or higher, and a video adapter with resolution of SVGA or higher.

System Requirements

Serviceguard Manager version A.04.00 can be installed on a computer with one of the following operating systems:

HP-UX, Version 11.0 or later.
Viewing Serviceguard Manager through Reflection X is not supported.
Red Hat Linux Advanced Server Version 2.1
Red Hat Enterprise Linux Version 3
SuSE Linux Enterprise Server, Version 8 (SLES 8), United Linux version 1.0 (SuSE is available only in English.)
Microsoft Windows XP Professional Edition, or Windows 2000 Professional with Service Pack 1 or later, with a video adapter of SVGA or higher resolution. (With Serviceguard Manager version A.04.00, Windows NT is no longer supported.)

Memory Requirements

Running on HP-UX, these are the minimum requirements for Serviceguard Manager:

256 MB of available memory
120 MB of available hard disk space under /opt
1 MB of available hard disk space under /usr
1 MB of available hard disk space under /etc/opt/OV if OpenView is installed.
3-15 MB of available hard disk space under /var for log files.

Running on Red Hat or SuSE Linux, these are the minimum requirements for Serviceguard Manager:

128 MB of available memory
100 MB of available hard disk space under /usr/local
Up to 33 MB of additional hard disk space during the installation process.
15 MB of additional hard disk space available for log files created when Serviceguard Manager is run:
- Red Hat: /usr/local/sgmgr/log
- SuSE: /opt/sgmgr/log
100 MB of additional hard disk space in:
- Red Hat: /usr/local/sgmgr/
- SuSE: /opt/sgmgr/
Up to 33 MB of additional hard disk space during the install process.

Running on Windows, these are the minimum requirements for Serviceguard Manager:

256 MB of memory
55 MB of available hard disk space
1 MB for log files when Serviceguard Manager is run.
Up to 50 MB of additional hard disk space during the installation process.

Requirements for Capabilities

With Serviceguard version A.04.00, a new capablity was added. Now you can configure clusters and packages using nodes that have Serviceguard version A.11.16. Administration has changed from previous versions as well. Serviceguard version 11.16 now has Role Based Access as a way to assign administrative roles to non-root users to administer Serviceguard clusters and packages, either locally or from outside the cluster.

With Serviceguard Manger A.04.00, some of the capabilities you have depend on the Serviceguard version of the Session Server, the node you log in to and begin a session. Some depend on the target, the Serviceguard node, cluster, or package you will see in your map, tree, and Properties.

The table below summarizes the capabilities of different releases of Session Servers and target nodes in Serviceguard Manager A.04.00. The first column has the Serviceguard versions of the Session Server. The second column lists the Serviceguard version of target clusters you can reach with that Session Server. The next three columns describe the capabilities, and what is required for each: Monitor, Administration, and Configuration.

Table 1-1 Capabilities of Session Servers on Target clusters

Session Server’s Service guard version	Target cluster’s Service guard version	To Monitor	To Administer	To Configure
A.11.13, A.11.14, and A.11.15	A.11.10, A.11.11, and A.11.12	User can be any entry in Session Server’s /etc/passwd file Target must have <sess.serv><root> in `cmclnodelist` file.	not supported	not supported
A.11.13 A.11.14, and A.11.15	A.11.13 A.11.14, and A.11.15	User can be any entry in Session Server’s /etc/passwd file Target must have <sess.serv><root> in `cmclnodelist` file.	User must log in to Session Server as root. Target must have <sess.serv><root> in `cmclnodelist` file.	not supported
A.11.13, A.11.14, and A.11.15	A.11.16	User can be any entry in Session Server’s /etc/passwd file Target cluster must have an Access control Policy configured Host = Session Server User = any entry in Session Server’s /etc/passwd Role = Monitor	Not supported	Configurationmenu available when an A.11.16 object is selected User must supply root password for a cluster node
A.11.16	A.11.13, A.11.14, and A.11.15	User can be any entry in Session Server’s /etc/passwd file Target must have <sess.serv><root> in `cmclnodelist` file.	User must log in to Session Server as root. Target must have <sess.serv><root> in `cmclnodelist` file.	not supported
A.11.16	A.11.16	User can be any entry in Session Server’s /etc/passwd file Target cluster must have an Access control Policy configured Host = Session Server User = any entry in Session Server’s /etc/passwd Role = Monitor	User can be any entry in Session Server’s /etc/passwd file Target cluster must have an Access control Policy configured Host = Session Server User = any entry in Session Server’s /etc/passwd Role = Admin	User can be any entry in Session Server’s /etc/passwd file Target cluster User must supply root password for a cluster node

Port Requirements

Serviceguard Manager itself does not have any port requirements. If you want to receive SNMP traps in the Event Browser, you need the SNMP ports 161 and 162.

Serviceguard does have port requirements, particularly when interacting with internal firewalls. If you are using a firewall such as Bastille, and connecting to a Cluster Object Manager outside the cluster, these rules apply:

Each Serviceguard Manager node must allow these connections:

from the cluster nodes:
- udp on port 162

to the cluster nodes:
- udp on port 161

Each Serviceguard node must allow these connections:

from the Serviceguard Manager node:
- udp on port 161

to the Serviceguard Manager node:
- udp on port 162

to the COM node:
- tcp on port 5303 - and allow only packets with SYN flag.

Each cluster node must allow these connections:

from the COM node to the cluster nodes:
- tcp on port 5302 and allow only packets with the SYN flag
- udp on port 5302
to the COM node from the cluster nodes
- tcp and udp on port numbers 49152-65535 from the cluster nodes

The node running the COM must allow these connections:

from Serviceguard Manager to the COM node:
- tcp on port 5303 - and allow only packets with the SYN flag

from cluster nodes to the COM:
- tcp and udp on port numbers 49152-65535 from the cluster nodes

to the cluster nodes
- tcp on port 5302 - and allow only packets with the SYN flag
- udp on port 5302

Each cluster node should allow SNMP connections between it and the Serviceguard Manager node. The Event Browser in Serviceguard Manager can receive messages from SNMP traps. SNMP requires ports 161 and 162. The list of port assignments is in the /etc/services file.

Because SNMP uses a single dedicated port, only one application can receive messages. For more information about SNMP, open online help and go to Troubleshooting Clusters, SNMP Problems.