Serviceguard Manager Version A.04.02 Release Notes, February 2005

Serviceguard Manager Version A.04.02 Release Notes
What’s in this Version
Chapter 1 11
From the management station, you connect to a Session Server with
Serviceguard installed (HP-UX or Linux). Each Session Server
connection is displayed on the tree with the clusters it discovered. 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 and later
• Serviceguard Extension for RAC, Version A.11.14.01 or later
• ServiceGuard OPS Edition, Version A.11.13 and later
• Metrocluster, all versions
• Continentalclusters, all versions
• Serviceguard Extension for Faster Failover, all versions.
You can do administrative commands if the Session Server and the
target Serviceguard node or cluster has version A.11.13 or later. The
rules for access are different in Serviceguard versions A.11.13 to A.11.15
than in version A.11.16. See Table 1-1 on page 17.
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: Because Continental Clusters are always on more than one subnet,
Serviceguard Manager sees them as two clusters. To see all the
information about a Continental cluster, open two separate sessions, one
on each subnet.