Powering off a MetroCluster site

You must power off a site and all of the equipment before site maintenance or relocation can begin.

Before you begin, check that any non-mirrored aggregates at the site are offline.
Verify the operation of the MetroCluster configuration in ONTAP:
1. Check whether the system is multipathed: node run -node node-name sysconfig -a
2. Check for any health alerts on both clusters: system health alert show
3. Confirm the MetroCluster configuration and that the operational mode is normal: metrocluster show
4. Perform a MetroCluster check: metrocluster check run
5. Display the results of the MetroCluster check:metrocluster check show
6. Check for any health alerts on the switches (if present): storage switch show
Enter the following command to implement the switchover: metrocluster switchover
The operation can take several minutes to complete.
Attention
In MetroCluster FC configurations, the unmirrored aggregates will only be online after a switchover if the remote disks in the aggregate are accessible. If the ISLs fail, the local node may be unable to access the data in the unmirrored remote disks. The failure of an aggregate can lead to a reboot of the local node.

Monitor and verify the completion of the switchover: metrocluster operation show

Example

cluster_A::*> metrocluster operation show
  Operation: Switchover
 Start time: 10/4/2012 19:04:13
State: in-progress
   End time: -
     Errors: 

cluster_A::*> metrocluster operation show
  Operation: Switchover
 Start time: 10/4/2012 19:04:13
      State: successful
   End time: 10/4/2012 19:04:22
     Errors: -

If you are in a MetroCluster IP configuration running ONTAP 9.6 or later, wait for the disaster site plexes to come online and the healing operations to automatically complete.
In MetroCluster IP configurations running earlier versions of ONTAP, the disaster site nodes do not automatically boot to ONTAP and the plexes remain offline.

Depending on your configuration and ONTAP version, identify and move offline affected plexes that are located at the disaster site.

Note

This step is required in the following configurations:

All MetroCluster FC configurations.
MetroCluster IP configurations running ONTAP version 9.6 or later.

You should move the following plexes offline:

Non-mirrored plexes residing on disks located at the disaster site.
If you do not move the non-mirrored plexes at the disaster site offline, an outage might result when the disaster site is later powered off.
Mirrored plexes residing on disks located at the disaster site for aggregate mirroring.

Once they are moved offline, the plexes are inaccessable.

Example

Identify the affected plexes.

Plexes that are owned by nodes at the surviving site consist of Pool1 disks. Plexes that are owned by nodes at the disaster site consist of Pool0 disks.

Note

Home refers to the home owner, not the current owner.

Cluster_A::> storage aggregate plex show -fields aggregate,status,is-online,Plex,pool
aggregate    plex  status        is-online pool
------------ ----- ------------- --------- ----
Node_B_1_aggr0 plex0 normal,active true     0
Node_B_1_aggr0 plex1 normal,active true     1

Node_B_2_aggr0 plex0 normal,active true     0
Node_B_2_aggr0 plex5 normal,active true     1

Node_B_1_aggr1 plex0 normal,active true     0
Node_B_1_aggr1 plex3 normal,active true     1

Node_B_2_aggr1 plex0 normal,active true     0
Node_B_2_aggr1 plex1 normal,active true     1

Node_A_1_aggr0 plex0 normal,active true     0
Node_A_1_aggr0 plex4 normal,active true     1

Node_A_1_aggr1 plex0 normal,active true     0
Node_A_1_aggr1 plex1 normal,active true     1

Node_A_2_aggr0 plex0 normal,active true     0
Node_A_2_aggr0 plex4 normal,active true     1

Node_A_2_aggr1 plex0 normal,active true     0
Node_A_2_aggr1 plex1 normal,active true     1
14 entries were displayed.

Cluster_A::>

The affected plexes are those that are remote to cluster A. The following table shows whether the disks are local or remote relative to cluster A:

Node	Disks in pool	Should the disks be set offline?	Example of plexes to be moved offline
Node _A_1 and Node _A_2	Disks in pool 0	No. Disks are local to cluster A.	-
Node _A_1 and Node _A_2	Disks in pool 1	Yes. Disks are remote to cluster A.	Node_A_1_aggr0/plex4 Node_A_1_aggr1/plex1 Node_A_2_aggr0/plex4 Node_A_2_aggr1/plex1
Node _B_1 and Node _B_2	Disks in pool 0	Yes. Disks are remote to cluster A.	Node_B_1_aggr1/plex0 Node_B_1_aggr0/plex0 Node_B_2_aggr0/plex0 Node_B_2_aggr1/plex0
Node _B_1 and Node _B_2	Disks in pool 1	No. Disks are local to cluster A.	-

Move the affected plexes offline: storage aggregate plex offline
```
storage aggregate plex offline -aggregate Node_B_1_aggr0 -plex plex0
```
Note
Perform this for all plexes that have disks that are remote to Cluster_A.

Persistently offline the switchports according to the switch type.

Note

This step is only required for MetroCluster FC configurations. Skip this step if your configuration is a MetroCluster IP configuration or a stretched MetroCluster configuration with FC backend switches.

Switch type Action

If the FC switches are Brocade switches...

Use the portpersistentdisable port command to persistently disable the ports as shown in the following example. This must be done on both switches at the surviving site.
Switch_A_1:admin> portcfgpersistentdisable 14 Switch_A_1:admin> portcfgpersistentdisable 15 Switch_A_1:admin>

Verify that the ports are disabled using the switchshow command shown in the following example:

 Switch_A_1:admin> switchshow
 switchName:Switch_A_1
 switchType:109.1
 switchState:Online   
 switchMode:Native
 switchRole:Principal
 switchDomain:2
 switchId:fffc02
 switchWwn:10:00:00:05:33:88:9c:68
 zoning:ON (T5_T6)
 switchBeacon:OFF
 FC Router:OFF
 FC Router BB Fabric ID:128
 Address Mode:0
 
  Index Port Address Media Speed State     Proto
  ==============================================
 ...
 14  14   020e00  id  16G   No_Light  FC  Disabled (Persistent) 
 15  15   020f00  id  16G   No_Light  FC  Disabled (Persistent) 
 ...
 Switch_A_1:admin>

If the FC switches are Cisco switches...

Use the interface command to persistently disable the ports. The following example shows ports 14 and 15 being disabled:

 Switch_A_1# conf t
 Switch_A_1(config)# interface fc1/14-15
 Switch_A_1(config)# shut

 Switch_A_1(config-if)# end
 Switch_A_1# copy running-config startup-config
 
 

Verify that the switch port is disabled using the show interface brief command as shown in the following example:
Switch_A_1# show interface brief Switch_A_1

Power off the site.

The following equipment needs to be turned off in no specific order:

Configuration type	Equipment to be powered off
In a MetroCluster IP configuration, power off...	MetroCluster IP switches Storage controllers Storage shelves
In a MetroCluster FC configuration, power off...	MetroCluster FC switches Storage controllers Storage shelves Atto FibreBridges (if present)

Give documentation feedback