Registering a Critical Device

Important - You must configure all the Cluster Members in the same way.

Description

You can add a user-defined critical device to the default list of critical devices. Use this command to register <device> as a critical process, and add it to the list of devices that must run for the Cluster Member to be considered active. If <device> fails, then the Cluster Member is seen as failed.

If a Critical Device fails to report its state to the Cluster Member in the defined timeout, the Critical Device, and by design the Cluster Member, are seen as failed.

Define the status of the Critical Device that is reported to ClusterXL upon registration. This initial status can be one of these:

• ok - Critical Device is alive.
• init - Critical Device is initializing. The Cluster Member is Down. In this state, the Cluster Member cannot become Active.
• problem - Critical Device failed. If this state is reported to ClusterXL, the Cluster Member immediately goes Down. This causes a failover.

Syntax

Shell	Command
Gaia Clish	N/A
Expert mode	cphaconf set_pnote -d <Name of Critical Device> -t <Timeout in Sec> -s {ok | init | problem} [-p] [-g] register

Notes:

• The name of the Critical Device must have no more than 15 characters, and must not include white spaces.
• For no timeout, use the value 0.
• The -p flag makes these changes permanent. After you reboot the Cluster Member, the status of critical devices that were registered with this flag is saved.
• The -g flag applies the command to all configured Virtual Systems.

Restrictions:

• Total number of critical devices (pnotes) on Cluster Member is limited to 16.
• Name of any critical device (pnote) on Cluster Member is limited to 16 characters.