Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

How to shutdown and power up of the netapp cluster mode storage system

7,099 views

Published on

This slide will guide you how to shutdown and power up of the Netapp cluster mode storage system in command mode. (It will depict you environmental shutdown process (SAN environment in a DataCenter)

Published in: Technology

How to shutdown and power up of the netapp cluster mode storage system

  1. 1. How to do Power off (shutdown) and power on of Cluster mode NetApp storage system Power down process(SAN Environment)  Need to shutdown all hosts which are connected to the SAN and then shutdown all connected switches (Stop all the I/O ‘s)  Shutdown the controllers first, once both are in zero state wait for 2-3 minutes then, jump to step3  Remove the respective power cords from disk shelves (shutdown the disk shelves)
  2. 2. Login into the storage by using the console IP address preferably using serial console or RLM/SP  First login into the storage system by using the console IPs if you don’t know that then login into the storage by using the management IP through Putty as below.  Execute the command to find out console IP address.
  3. 3. How to do Power off (shutdown) of NetApp cluster mode storage system Login into the storage system by using the console IP address as below (one example) login as: admin admin@10.190.198.63's password: SP liftnetappa> SP liftnetappa> system console Type Ctrl-D to exit. SP-login: admin Password: ***************************************************** * This is an SP console session. Output from the * * serial console is also mirrored on this session. * ***************************************************** liftnetapp::>
  4. 4. How to do Power off (shutdown) of NetApp cluster mode storage system  Disconnect and, if needed, shut down all of the connected CIFS/NFS clients.  If there are any hosts that have FCP or iSCSI-based LUNs, shut them down before shutting down the storage system.  If running ONTAP version prior to 8.2, perform the following steps: If on a 2-node cluster, run the following: ::> cluster ha modify –configured false (Now high- availability will be disable) If on a 4+-node cluster, run the following: ::> storage failover modify -node * -enabled false  Log in to all nodes, one at a time (preferably using serial console or RLM/SP) and run: ::> halt local -inhibit-takeover true (It will halt the node and takeover will not be possible)
  5. 5. Command output  liftnetapp::> cluster ha modify -configured false  Notice: HA is disabled.  liftnetapp::> halt local -inhibit-takeover true  (system node halt)  Warning: This operation will cause node "liftnetappb" to be marked as  unhealthy. Unhealthy nodes do not participate in quorum voting. If the  node goes out of service and one more node goes out of service there  will be a data serving failure for the entire cluster. This will cause  a client disruption. Use "cluster show" to verify cluster state. If  possible bring other nodes online to improve the resiliency of this  cluster.
  6. 6. Command output  Do you want to continue? {y|n}: y  SP-login: Terminated  Uptime: 99d13h52m31s  Top Shutdown Times (ms): {shutdown_fm=1020, shutdown_wafl=531(multivol=0, sfsr=0, abort_scan=0, snapshot=0, hit_update=0, start=120, sync1=100, sync2=1, mark_fs=310), if_reset=460, shutdown_raid=101, wafl_sync_tagged=93, iscsimgt_notify_shutdown_appliance=20}  Shutdown duration (ms): {CIFS=3233, NFS=3233, ISCSI=3213, FCP=3213}  System halting...  ¦  Phoenix SecureCore(tm) Server  Copyright 1985-2008 Phoenix Technologies Ltd.  All Rights Reserved  BIOS version: 8.3.0  Portions Copyright (c) 2008-2014 NetApp, Inc. All Rights Reserved
  7. 7. Command output  CPU = 1 Processors Detected, Cores per Processor = 2  Intel(R) Xeon(R) CPU C3528 @ 1.73GHz  Testing RAM  512MB RAM tested  18432MB RAM installed  256 KB L2 Cache per Processor Core  4096K L3 Cache Detected  System BIOS shadowed  USB 2.0: MICRON eUSB DISK  BIOS is scanning PCI Option ROMs, this may take a few seconds...  ...................  Boot Loader version 4.3  Copyright (C) 2000-2003 Broadcom Corporation.  Portions Copyright (C) 2002-2014 NetApp, Inc. All Rights Reserved.  CPU Type: Intel(R) Xeon(R) CPU C3528 @ 1.73GHz  LOADER-B> Go to the second node and execute the “halt” command will get the same message as above and LOADER-A> prompt will come
  8. 8. Power up process SAN Environment  Power up all the disk shelves first, then wait 5 to 10Mins, if all looks good (LEDs are in green colour) then jump to next step  Power up both the controllers  power on the connected switches  Power on all the connected hosts
  9. 9. POST VERIFICATION-: For clustered ONTAP systems, check cluster show and storage failover show to confirm CFO/SFO is configured/enabled. If on version prior to 8.2 in which cluster ha and/or storage failover were disabled, run the following commands: ::> cluster ha modify –configured true (High-availability is enabled) ::> storage failover modify –node * –enabled true Then login into all the SAN connected host machines and check if all the LUNs are online or not, if not then check it out in the storage systems if all LUNs are online and mapped.
  10. 10. Thank You!

×