HP Serviceguard A.11.20.00 for Linux Release Notes, August 2012

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.
Considerations when Installing Serviceguard
When you install Serviceguard for the first time on a node, the node is not yet part of a cluster,
and so there is no Access Control Policy. 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.
Ports Requirements
Serviceguard uses the ports listed below. Before installing, make sure that no other program uses
these ports.
Ports Needed on Red Hat:
• icmp 8/icmp
• hacl-hb 5300/TCP High Availability (HA) Cluster heartbeat
• hacl-hb 5300/UDP High Availability (HA) Cluster heartbeat
• hacl-cfg 5302/TCP HA Cluster TCP configuration
• hacl-cfg 5302/UDP HA Cluster UDP configuration
• hacl-local 5304/TCP HA Cluster Commands
If you are using SNMP:
• snmp 161/UDP
• snmptrap 162/UDP
If you are using the WBEM provider (used by Serviceguard Manager):
• wbem-http TCP/5988
• wbem-https TCP/5989
Compatibility and Installation Requirements 11