Verifying the health of the MetroCluster configuration
You should check the health of the MetroCluster configuration to verify proper operation.
- Check that the MetroCluster is configured and in normal mode on each cluster: metrocluster show
cluster_A::> metrocluster show
Cluster Entry Name State
------------------------- ------------------- -----------
Local: cluster_A Configuration state configured
Mode normal
AUSO Failure Domain auso-on-cluster-disaster
Remote: cluster_B Configuration state configured
Mode normal
AUSO Failure Domain auso-on-cluster-disaster - Check that mirroring is enabled on each node: metrocluster node show
cluster_A::> metrocluster node show
DR Configuration DR
Group Cluster Node State Mirroring Mode
----- ------- -------------- -------------- --------- --------------------
1 cluster_A
node_A_1 configured enabled normal
cluster_B
node_B_1 configured enabled normal
2 entries were displayed. - Check that the MetroCluster components are healthy: metrocluster check run
cluster_A::> metrocluster check run
Last Checked On: 10/1/2014 16:03:37
Component Result
------------------- ---------
nodes ok
lifs ok
config-replication ok
aggregates ok
4 entries were displayed.
Command completed. Use the "metrocluster check show -instance" command or sub-commands in "metrocluster check" directory for detailed results.
To check if the nodes are ready to do a switchover or switchback operation, run "metrocluster switchover -simulate" or "metrocluster switchback -simulate", respectively. - Check that there are no health alerts: system health alert show
- Simulate a switchover operation:
- From any node's prompt, change to the advanced privilege level: set -privilege advanced You need to respond with y when prompted to continue into advanced mode and see the advanced mode prompt (*>).
- Perform the switchover operation with the -simulate parameter: metrocluster switchover -simulate
- Return to the admin privilege level: set -privilege admin
- From any node's prompt, change to the advanced privilege level: set -privilege advanced
- For MetroCluster IP configurations using the ONTAP Mediator service, confirm that the Mediator service is up and operating.
- Check that the Mediator disks are visible to the system: storage failover mailbox-disk show The following example shows that the mailbox disks have been recognized.
node_A_1::*> storage failover mailbox-disk show
Mailbox
Node Owner Disk Name Disk UUID
------------- ------ ----- ----- ----------------
sti113-vsim-ucs626g
.
.
local 0m.i2.3L26 7BBA77C9:AD702D14:831B3E7E:0B0730EE:00000000:00000000:00000000:00000000:00000000:00000000
local 0m.i2.3L27 928F79AE:631EA9F9:4DCB5DE6:3402AC48:00000000:00000000:00000000:00000000:00000000:00000000
local 0m.i1.0L60 B7BCDB3C:297A4459:318C2748:181565A3:00000000:00000000:00000000:00000000:00000000:00000000
.
.
.
partner 0m.i1.0L14 EA71F260:D4DD5F22:E3422387:61D475B2:00000000:00000000:00000000:00000000:00000000:00000000
partner 0m.i2.3L64 4460F436:AAE5AB9E:D1ED414E:ABF811F7:00000000:00000000:00000000:00000000:00000000:00000000
28 entries were displayed. - Change to the advanced privilege level: set -privilege advanced
- Check that the mailbox LUNs are visible to the system:: storage iscsi-initiator show The output will show the presence of the mailbox LUNs:
Node Type Label Target Portal Target Name Admin/Op
---- ---- -------- --------- --------- -------------------------------- --------
.
.
.
.node_A_1
mailbox
mediator 172.16.254.1 iqn.2012-05.local:mailbox.target.db5f02d6-e3d3 up/up
.
.
.
17 entries were displayed. - Return to the administrative privilege level: set -privilege admin
- Check that the Mediator disks are visible to the system: storage failover mailbox-disk show
Give documentation feedback