EasyManua.ls Logo

NetApp FAS - Page 609

NetApp FAS
704 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
powered on:
::> system controller slot module insert -node node1 -slot 6-2
Warning: NVMe module in slot 6-2 of the node localhost will be powered
on and initialized.
Do you want to continue? (y|n): `y`
The module has been successfully powered on, initialized and placed into
service.
7.
Verify the slot status using the
system controller slot module show command.
Make sure that command output reports status for slot 6-1 or 6-2 as
powered-on and ready for operation.
8. Verify that the replacement caching module is online and recognized, and then visually confirm that the
amber attention LED is not lit:
sysconfig -av slot_number
If you replace the caching module with a caching module from a different vendor, the new
vendor name is displayed in the command output.
9. After you replace the part, you can return the failed part to NetApp, as described in the RMA instructions
shipped with the kit. Contact technical support at
NetApp Support, 888-463-8277 (North America), 00-800-
44-638277 (Europe), or +800-800-80-800 (Asia/Pacific) if you need the RMA number or additional help
with the replacement procedure.
Chassis
Overview of chassis replacement - AFF A700 and FAS9000
All other components in the system must be functioning properly; if not, you must contact
technical support.
You can use this procedure with all versions of ONTAP supported by your system.
This procedure is disruptive. For a two-node cluster, you will have a complete service outage and a partial
outage in a multi-node cluster.
Shut down the controllers - AFF A700 and FAS9000
To replace the chassis, you must shutdown the controllers.
Option 1: Shut down the controllers
You must shut down the controller or controller in the chassis prior to moving them to the new chassis.
About this task
If you have a cluster with more than two controllers, 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 the Administration overview with the CLI.
607

Related product manuals