Before and after performing an update in a MetroCluster configuration, you should verify the status of the LIFs, aggregates, and volumes for each cluster.
cluster1::> network interface show Logical Status Network Current Current Is Vserver Interface Admin/Oper Address/Mask Node Port Home ----------- ---------- ---------- ------------------ ------------- ------- ---- Cluster cluster1-a1_clus1 up/up 192.0.2.1/24 cluster1-01 e2a true cluster1-a1_clus2 up/up 192.0.2.2/24 cluster1-01 e2b true cluster1-01 clus_mgmt up/up 198.51.100.1/24 cluster1-01 e3a true cluster1-a1_inet4_intercluster1 up/up 198.51.100.2/24 cluster1-01 e3c true ... 27 entries were displayed.
cluster1::> storage aggregate show -state !online There are no entries matching your query.
cluster1::> storage aggregate show -state !online Aggregate Size Available Used% State #Vols Nodes RAID Status --------- -------- --------- ----- ------- ------ ---------------- ------------ aggr0_b1 0B 0B 0% offline 0 cluster2-01 raid_dp, mirror degraded aggr0_b2 0B 0B 0% offline 0 cluster2-02 raid_dp, mirror degraded 2 entries were displayed.
If the MetroCluster configuration is in normal operation (it is not in switchover state), the output should show all volumes owned by the cluster's secondary SVMs (those with the SVM name appended with "-mc").
Those volumes come online only in the event of a switchover.
cluster1::> volume show -state !online (volume show) Vserver Volume Aggregate State Type Size Available Used% --------- ------------ ------------ ---------- ---- ---------- ---------- ----- vs2-mc vol1 aggr1_b1 - RW - - - vs2-mc root_vs2 aggr0_b1 - RW - - - vs2-mc vol2 aggr1_b1 - RW - - - vs2-mc vol3 aggr1_b1 - RW - - - vs2-mc vol4 aggr1_b1 - RW - - - 5 entries were displayed.