Option 1: Most systems
To shut down the impaired controller, you must determine the status of the controller and, if necessary,
take over the controller so that the healthy controller continues to serve data from the impaired controller
storage.
About this task
•
If you have a SAN system, you must have checked event messages (
cluster kernel-service
show
) for the impaired controller SCSI blade. The cluster kernel-service show command
(from priv advanced mode) displays the node name, quorum status of that node, availability status of
that node, and operational status of that node.
Each SCSI-blade process should be in quorum with the other nodes in the cluster. Any issues must
be resolved before you proceed with the replacement.
• If you have a cluster with more than two nodes, it must be in quorum. If the cluster is not in quorum or
a healthy controller shows false for eligibility and health, you must correct the issue before shutting
down the impaired controller; see
Synchronize a node with the cluster.
Steps
1. If AutoSupport is enabled, suppress automatic case creation by invoking an AutoSupport message:
system node autosupport invoke -node * -type all -message MAINT=<# of
hours>h
The following AutoSupport message suppresses automatic case creation for two hours: cluster1:>
system node autosupport invoke -node * -type all -message MAINT=2h
2.
Disable automatic giveback from the console of the healthy controller:
storage failover modify
–node local -auto-giveback false
When you see Do you want to disable auto-giveback?, enter y.
3. Take the impaired controller to the LOADER prompt:
If the impaired controller is
displaying…
Then…
The LOADER prompt Go to the next step.
Waiting for giveback…
Press Ctrl-C, and then respond y when prompted.
System prompt or password
prompt
Take over or halt the impaired controller from the healthy
controller:
storage failover takeover -ofnode
impaired_node_name
When the impaired controller shows Waiting for giveback…, press
Ctrl-C, and then respond
y.
Option 2: Controller is in a MetroCluster
To shut down the impaired controller, you must determine the status of the controller and, if necessary,
67
To Next Page
Loading...
