Managing HP Serviceguard A.11.20.20 for Linux, March 2014

• HP_SGNodePackage
• HP_SGPService
• HP_SGPackagePService
• HP_SGNodePService
• HP_SGLockLunDisk
• HP_SGRemoteQuorumService
• HP_SGLockObject
• HP_SGQuorumServer
• HP_SGLockLun
• HP_SGLockDisk
For more information about WBEM provider classes, see Managed Object Format (MOF) files for
properties. When SGProviders is installed, the MOF files are copied to the /opt/sgproviders/
mof/ directory on SUSE Linux Enterprise Server and /usr/local/sgproviders/mof/ directory
on Red Hat Enterprise Linux server.
NOTE: WBEM queries for the previous classes on SUSE Linux Enterprise Server might fail because
of access denied issues, if Serviceguard is not able to validate the credentials of the WBEM request.
Small Footprint CIM Broker (SFCB) which is the CIM server in SUSE Linux Enterprise Server 11 SP1
and SP2 has a configuration parameter doBasicAuth which enables basic authentication for
HTTP and HTTPS connections. This parameter must be set to true in the /etc/sfcb/sfcb.cfg
file. Otherwise, the user credentials of any WBEM request is not passed to Serviceguard WBEM
Provider.
3.1.2.4 WBEM Indications
For an indication to be received on occurrence of a Serviceguard event, a WBEM subscription
must exist for one of the following indication classes:
• CIM_AlertIndication
• HP_ServiceguardIndication
3.2 How the Cluster Manager Works
The cluster manager is used to initialize a cluster, to monitor the health of the cluster, to recognize
node failure if it should occur, and to regulate the re-formation of the cluster when a node joins or
leaves the cluster. The cluster manager operates as a daemon process that runs on each node.
During cluster startup and re-formation activities, one node is selected to act as the cluster
coordinator.Although all nodes perform some cluster management functions, the cluster coordinator
is the central point for inter-node communication.
3.2.1 Configuration of the Cluster
The system administrator sets up cluster configuration parameters and does an initial cluster startup;
thereafter, the cluster regulates itself without manual intervention in normal operation. Configuration
parameters for the cluster include the cluster name and nodes, networking parameters for the cluster
heartbeat, cluster lock information, and timing parameters (discussed in detail in Chapter 4
(page 79) ). Cluster parameters are entered by editing the cluster configuration file (see “Configuring
the Cluster” (page 153)). The parameters you enter are used to build a binary configuration file
which is propagated to all nodes in the cluster. This binary cluster configuration file must be the
same on all the nodes in the cluster.
38 Understanding Serviceguard Software Components