Skip to main content
A newer release of this product is available.

system node reboot

Contributors
Suggest changes
PDFs

Reboot a node

Availability: This command is available to cluster administrators at the admin privilege level.

Description

The system node reboot command restarts a node. You can supply a reason for the reboot, which is stored in the audit log. You can also keep partner nodes from performing storage takeover during the reboot and instruct the rebooted node to create a core dump.

Parameters

-node {<nodename>|local} - Node

Specifies the node that is to be restarted. The value "local" specifies the current node.

[-f, -inhibit-takeover <true>] - Disallow Storage Takeover by Partner

If set to true , this parameter specifies that the node's failover partner is not allowed to take over for the node when the node is rebooted. LIFs will migrate prior to reboot even when inhibit-takeover is set to true . To prevent LIF migration, skip-lif-migration-prior-to-reboot should be set to true . In a two-node MetroCluster configuration, this parameter prevents automatic unplanned switchover. If you enter this command without using this parameter, its effective value is false and storage takeover is allowed. If you enter this parameter without a value, it is automatically set to true and storage takeover is disabled during reboot.

[-reason <text>] - Reason for Reboot

Use this parameter to enter a brief note to indicate the reason for the restart, which will be stored in the audit log. Providing this information assists support personnel with troubleshooting efforts.

[-d, -dump <true>] - Create a Core Dump

If you would like the node to create a core dump before restarting, specify the true value with this parameter. If you enter this command without using this parameter, its effective value is false and the node doesn't create a core dump. If you enter this parameter without a value, it is automatically set to true and the node creates a core dump.

[-skip-lif-migration-before-reboot <true>] - Skip Migrating LIFs Away from Node Prior to Reboot

If this parameter is specified, LIF migration prior to the reboot will be skipped. However if LIFs on this node are configured for failover, those LIFs may still failover after the reboot has occurred. The default is to migrate LIFs prior to the reboot. In the default case, the command attempts to synchronously migrate data and cluster management LIFs away from the node prior to reboot. If the migration fails or times out, the reboot will be aborted.

[-ignore-quorum-warnings <true>] - Skip Quorum Check Before Reboot

If this parameter is specified, quorum checks will be skipped prior to the reboot. The operation will continue even if there is a possible data outage due to a quorum issue.

[-ignore-strict-sync-warnings <true>] - Skip SnapMirror Synchronous Strict Sync Check Before Reboot

If this parameter is specified, the check for volumes that are in SnapMirror Synchronous relationships with policy of type strict-sync-mirror will be skipped. The operation will continue even if there is a possible data outage due to not being able to fully sync data.

Examples

The command in the following example restarts the node named cluster1 for a software upgrade:

cluster1::> system node reboot -node cluster1 -reason "software upgrade"