Go to main content

Administering an Oracle® Solaris Cluster 4.4 Configuration

Exit Print View

Updated: March 2019
 
 

How to Enable the Automatic Rebooting of a Node When All Monitored Shared-Disk Paths Fail

When you enable this feature, a node automatically reboots, provided that the following conditions are met:

  • All monitored shared-disk paths on the node fail.

  • At least one of the disks is accessible from a different node in the cluster.

Rebooting the node restarts all resource groups and device groups that are mastered on that node on another node.

If all monitored shared-disk paths on a node remain inaccessible after the node automatically reboots, the node does not automatically reboot again. However, if any disk paths become available after the node reboots but then fail, the node automatically reboots again.

When you enable the reboot_on_path_failure property, the states of local-disk paths are not considered when determining if a node reboot is necessary. Only monitored shared disks are affected.


Note -  You can also edit the reboot_on_path_failure node property by using the Oracle Solaris Cluster Manager browser interface. For Oracle Solaris Cluster Manager log-in instructions, see How to Access Oracle Solaris Cluster Manager.
  1. On any node in the cluster, assume a role that provides solaris.cluster.modify authorization.
  2. For all nodes in the cluster, enable the automatic rebooting of a node when all monitored shared-disk paths to it fail.
    # clnode set -p reboot_on_path_failure=enabled +