Serviceguard Version A.11.16 Release Notes, 2nd Edition, September 2004

Serviceguard Version A.11.16 Release Notes, Second Edition
Compatibility Information and Installation Requirements
Chapter 120
Serviceguard Manager checks two places for access: once when the user
logs in to the Session Server, and again when the Session Server contacts
the target node. For more information about Serviceguard Manager
policies, see the Serviceguard Manager Release Notes, or the online help.
For versions earlier than A.11.16, the /.rhosts file must not allow write
access by group or other. If /.rhosts file write permission is enabled
for other or group, Serviceguard commands will fail, logging a
“Permission denied for user” message. This situation can arise when the
Serviceguard remote security file, /etc/cmcluster/cmclnodelist, is
not used and remote node security is resolved with the .rhosts facility
instead. (These rules apply only to target nodes with versions earlier
than Serviceguard A.11.16.)
Upgraded Serviceguard
If you have a cluster with entries in cmclnodelist, those entries are also
updated when you update to version A.11.16.
Every <host_node> <user_name> pair is now in the cluster
configuration file as an Access Control Policy triplet, with:
• USER_NAME <user_name>
• USER_HOST <host_node>
• USER_ROLE Monitor
If you had a wild-card + (plus), you see an access policy with wildcards:
• USER_NAME ANY_USER
• USER_HOST ANY_SERVICEGUARD_NODE
• USER_ROLE Monitor
Memory Requirements
The memory requirement for Serviceguard depends partly on the
number of packages configured in the cluster. The following equation
provides a rough estimate of how much lockable memory is needed:
Total Memory = 6MB + 100 KB/package
in cluster
The total amount is needed on all nodes in the cluster, regardless of
whether a given package is on that node or not.