increasing number of correctable error correction codes (ECC); failure to do so causes a
system panic.
All other components in the system must be functioning properly; if not, you must contact technical support.
You must replace the failed component with a replacement FRU component you received from your provider.
Step 1: Shut down the impaired controller
You can shut down or take over the impaired controller using different procedures,
depending on the storage system hardware configuration.
Option 1: Most configurations
After running diagnostics, you must recable the controller module’s storage and network connections.
Steps
1. Recable the system.
2. Verify that the cabling is correct by using
.
a. Download and install Config Advisor.
b. Enter the information for the target system, and then click Collect Data.
c. Click the Cabling tab, and then examine the output. Make sure that all disk shelves are displayed and
all disks appear in the output, correcting any cabling issues you find.
d. Check other cabling by clicking the appropriate tab, and then examining the output from Config Advisor.
Option 2: Controller is in a MetroCluster
Do not use this procedure if your system is in a two-node MetroCluster configuration.
To shut down the impaired node, you must determine the status of the node and, if necessary, take over the
node so that the healthy node continues to serve data from the impaired node storage.
• 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 node shows false for eligibility and health, you must correct the issue before shutting down the
impaired node; see the
Administration overview with the CLI
• If you have a MetroCluster configuration, you must have confirmed that the MetroCluster Configuration
State is configured and that the nodes are in an enabled and normal state (
metrocluster node show
).
Steps
1. If AutoSupport is enabled, suppress automatic case creation by invoking an AutoSupport message:
system node autosupport invoke -node * -type all -message
MAINT=number_of_hours_downh
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 node:
storage failover modify –node
local -auto-giveback false
3. Take the impaired node to the LOADER prompt:
895
Summary of Contents for AFF A700
Page 4: ...AFF and FAS System Documentation 1...
Page 208: ...3 Close the controller module cover and tighten the thumbscrew 205...
Page 248: ...2 Close the controller module cover and tighten the thumbscrew 245...
Page 308: ...Power supply Cam handle release latch Power and Fault LEDs Cam handle 305...
Page 381: ...Power supply Cam handle release latch Power and Fault LEDs Cam handle 378...
Page 437: ...1 Locate the DIMMs on your controller module 434...
Page 605: ...602...
Page 1117: ...3 Close the controller module cover and tighten the thumbscrew 1114...
Page 1157: ...2 Close the controller module cover and tighten the thumbscrew 1154...
Page 1228: ...Power supply Cam handle release latch Power and Fault LEDs Cam handle 1225...
Page 1300: ...Power supply Cam handle release latch Power and Fault LEDs Cam handle 1297...
Page 1462: ...Installing SuperRail to round hole four post rack 1459...
Page 1602: ...1599...
Page 1630: ...1627...
Page 1634: ...Orange ring on horizontal bracket Cable chain 1631...
Page 1645: ...Guide rail 1642...
Page 1669: ...Attention LED light on 1666...