Checking the MetroCluster configuration
You can check that the components and relationships in the MetroCluster configuration are working correctly. You should do a check after initial configuration and after making any changes to the MetroCluster configuration. You should also do a check before a negotiated (planned) switchover or a switchback operation.
About this task
If the metrocluster check run command is issued twice within a short time on either or both clusters, a conflict can occur and the command might not collect all data. Subsequent metrocluster check show commands do not show the expected output.
- Check the configuration: metrocluster check run
Example
The command runs as a background job and might not be completed immediately.
cluster_A::> metrocluster check run
The operation has been started and is running in the background. Wait for
it to complete and run "metrocluster check show" to view the results. To
check the status of the running metrocluster check operation, use the command,
"metrocluster operation history show -job-id 2245" - Display more detailed results from the most recent metrocluster check run command: metrocluster check aggregate show metrocluster check cluster show metrocluster check config-replication show metrocluster check lif show metrocluster check node show
The metrocluster check show commands show the results of the most recent metrocluster check run command. You should always run the metrocluster check run command prior to using the metrocluster check show commands so that the information displayed is current.
Example
The following example shows the metrocluster check aggregate show command output for a healthy four-node MetroCluster configuration:
cluster_A::> metrocluster check aggregate show
Last Checked On: 8/5/2014 00:42:58
Node Aggregate Check Result
--------------- -------------------- --------------------- ---------
controller_A_1 controller_A_1_aggr0
mirroring-status ok
disk-pool-allocation ok
ownership-state ok
controller_A_1_aggr1
mirroring-status ok
disk-pool-allocation ok
ownership-state ok
controller_A_1_aggr2
mirroring-status ok
disk-pool-allocation ok
ownership-state ok
controller_A_2 controller_A_2_aggr0
mirroring-status ok
disk-pool-allocation ok
ownership-state ok
controller_A_2_aggr1
mirroring-status ok
disk-pool-allocation ok
ownership-state ok
controller_A_2_aggr2
mirroring-status ok
disk-pool-allocation ok
ownership-state ok
18 entries were displayed.The following example shows the metrocluster check cluster show command output for a healthy four-node MetroCluster configuration. It indicates that the clusters are ready to perform a negotiated switchover if necessary.
Last Checked On: 9/13/2017 20:47:04
Cluster Check Result
--------------------- ------------------------------- ---------
mccint-fas9000-0102
negotiated-switchover-ready not-applicable
switchback-ready not-applicable
job-schedules ok
licenses ok
periodic-check-enabled ok
mccint-fas9000-0304
negotiated-switchover-ready not-applicable
switchback-ready not-applicable
job-schedules ok
licenses ok
periodic-check-enabled ok
10 entries were displayed.