EasyManua.ls Logo

NetApp AFF - Page 18

NetApp AFF
1152 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...
The healthy controller is the HA partner of the impaired controller.
Check onboard encryption keys - AFF C190
Prior to shutting down the impaired controller and checking the status of the onboard
encryption keys, you must check the status of the impaired controller, disable automatic
giveback, and check what version of ONTAP the system is running.
Prior to shutting down the impaired controller and checking the status of the onboard encryption keys, you
must check the status of the impaired controller, disable automatic giveback, and check the version of ONTAP
that is running.
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 the
NetApp Encryption overview with the CLI.
Steps
1. Check the status of the impaired controller:
If the impaired controller is at the login prompt, log in as
admin.
If the impaired controller is at the LOADER prompt and is part of HA configuration, log in as
admin on
the healthy controller.
If the impaired controller is in a standalone configuration and at LOADER prompt, contact
mysupport.netapp.com.
2. 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
3. Check the version of ONTAP the system is running on the impaired controller if up, or on the partner
controller if the impaired controller is down, using the
version -v command:
If <lno-DARE> or <1Ono-DARE> is displayed in the command output, the system does not support
NVE, proceed to shut down the controller.
If <lno-DARE> is not displayed in the command output, and the system is running ONTAP 9.6 or later,
go to the next section.
4. If the impaired controller is part of an HA configuration, disable automatic giveback from the healthy
controller:
storage failover modify -node local -auto-giveback false or storage
failover modify -node local -auto-giveback-after-panic false
Check NVE or NSE on systems running ONTAP 9.6 and later
Before shutting down the impaired controller, you need to verify whether the system has either NetApp Volume
Encryption (NVE) or NetApp Storage Encryption (NSE) enabled. If so, you need to verify the configuration.
1.
Verify whether NVE is in use for any volumes in the cluster:
volume show -is-encrypted true
If any volumes are listed in the output, NVE is configured and you need to verify the NVE configuration. If
no volumes are listed, check whether NSE is configured and in use.
16

Related product manuals