Serviceguard Manager Version A.05.01 Release Notes, February 2007

Serviceguard Manager Version A.05.01 Release Notes
What You See
Chapter 112
How it Works
You can install Serviceguard Manager on a system running HP-UX,
Linux, or Windows.
From the system running Serviceguard Manager, you connect to a
Serviceguard Node (HP-UX or Linux) to establish your management
session.
When you establish a Session Server connection, which is a cluster
member node that the administrator connects to through Serviceguard
Manager and displays the discovered clusters. The component of
Serviceguard that interfaces with Serviceguard Manager is called the
COM (Cluster Object Manager). The version of the Session Server’s COM
is shown in its properties.
When you log in to a Session Server, it goes out on its subnets to discover
Serviceguard nodes configured for these types of clusters:
• Serviceguard, Version A.10.10 through A.11.17.01
• Serviceguard Extension for RAC, Version A.11.15.00 and later.
• Metrocluster, all versions
• Continentalclusters, all versions
You can do administrative commands if the Session Server and the
target Serviceguard node or cluster has version A.11.13.00 through
A.11.17.01. There is one set of rules for access in Serviceguard versions
A.11.13.00 to A.11.15.00. Different access methods are used in version
A.11.16.00 and A.11.17.01. See Table 1-2 on page 18.
The Session Server queries Serviceguard nodes on its subnet for status
and configuration information. If the discovered node has allowed the
Session Server to query, the information will appear in your map, tree,
Properties, and Alerts. (See “Before Installing Serviceguard Manager,”
below, for a description of configuring node access permissions.)
NOTE Continentalclusters are always on more than one subnet, therefore,
Serviceguard Manager sees them as two clusters. To see all the
information about a Continentalcluster, open two separate sessions, one
for each subnet.