![NetApp FAS8300 Скачать руководство пользователя страница 70](http://html.mh-extra.com/html/netapp/fas8300/fas8300_manual_1669893070.webp)
Recable the system and reassign disks - FAS8300 and FAS8700
You must complete a series of tasks before restoring your system to full operation.
Step 1: Recable the system
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.
Step 2: Reassign disks
If the storage system is in an HA pair, the system ID of the new controller module is
automatically assigned to the disks when the giveback occurs at the end of the
procedure. In a stand-alone system, you must manually reassign the ID to the disks.
You must use the correct procedure for your configuration:
Controller redundancy
Then use this procedure…
HA pair
Option 1: Verify the system ID change on an HA system
]
Two-node MetroCluster
configuration
Option 2: Manually reassign the system ID on systems in a two-node
MetroCluster configuration
Option 1: Verify the system ID change on an HA system
You must confirm the system ID change when you boot the
replacement
node and then
verify that the change was implemented.
This procedure applies only to systems running ONTAP in an HA pair.
1. If the
replacement
node is in Maintenance mode (showing the
*>
prompt, exit Maintenance mode and go
to the LOADER prompt:
halt
2. From the LOADER prompt on the
replacement
node, boot the node, entering
y
if you are prompted to
override the system ID due to a system ID mismatch:
3. Wait until the
Waiting for giveback…
message is displayed on the
replacement
node console and
then, from the healthy node, verify that the new partner system ID has been automatically assigned:
storage failover show
68