HP Serviceguard for Linux Version A.11.19 Release Notes, April 2009

Changes First Introduced in Older Releases
The following important changes have either been introduced since the previous edition
of the Serviceguard Release Notes was published, or may affect the upgrade from an
earlier release.
• As of A.11.16, Serviceguard uses Access Control Policies to control access to, and
administrative control over, the cluster.
See “Access changes as of A.11.16” (page 29).
Access changes as of A.11.16
Serviceguard version A.11.16 introduced a new access method. As of A.11.16,
Serviceguard uses Access Control Policies, also known as Role-Based Access, rather
than cmclnodelist or .rhosts, to authenticate users.
For more information about Access Control Policies, see Chapter 5 of the the Managing
Serviceguard for Linux manual (docs.hp.com -> High Availability), the
Serviceguard Manager Help (under Defining Cluster Roles), and the cluster
and package configuration files themselves.
Considerations when Upgrading Serviceguard
• .rhosts
If you relied on .rhosts for access in the previous version of the cluster, you
must now configure Access Control Policies for the cluster users. For instructions
on how to proceed, see the subsection “Allowing Root Access to an Unconfigured
Node” under “Configuring Root-Level Access” in Chapter 5 of the Managing
Serviceguard for Linux manual.
• cmclnodelist
When you upgrade from an earlier version, Serviceguard converts entries into
new entries written into the cluster configuration file during the upgrade, as
follows:
USER_NAME <user_name>
USER_HOST <host_node>
USER_ROLE Monitor
A wild-card + (plus) is converted as follows:
USER_NAME ANY_USER
USER_HOST ANY_SERVICEGUARD_NODE
USER_ROLE Monitor
After you complete the upgrade, use cmgetconf to create and save a copy of the
new configuration. If you do a cmapplyconf, you want to be sure it applies the
newly migrated Access Control Policies.
What’s in this Release 29