Registering a Critical Device

In the R81.10.X releases, this command is available starting from the R81.10.00 version.

Important - In a Cluster, 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 configured 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

cphaconf set_pnote -d <Name of Critical Device> -t <Timeout in Sec> -s {ok | init | problem} [-p] register

Notes:

  • The "-t" flag specifies how frequently to expect the periodic reports from this Critical Device.

    If no periodic reports should be expected, then enter the value 0 (zero).

  • The "-p" flag makes these changes permanent (survive reboot).

Related topics