Verify networking and storage status for MetroCluster configurations after an ONTAP upgrade
-
PDF of this doc site
- Cluster administration
-
Volume administration
- Logical storage management with the CLI
-
NAS storage management
- Configure NFS with the CLI
- Manage NFS with the CLI
-
Manage SMB with the CLI
- Manage file access using SMB
- SAN storage management
- Security and data encryption
-
Data protection and disaster recovery
- Data protection with the CLI
Collection of separate PDF docs
Creating your file...
After you upgrade an ONTAP cluster in a MetroCluster configuration, you should verify the status of the LIFs, aggregates, and volumes for each cluster.
-
Verify the LIF status:
network interface show
In normal operation, LIFs for source SVMs must have an admin status of up and be located on their home nodes. LIFs for destination SVMs are not required to be up or located on their home nodes. In switchover, all LIFs have an admin status of up, but they do not need to be located on their home nodes.
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.
-
Verify the state of the aggregates:
storage aggregate show -state !online
This command displays any aggregates that are not online. In normal operation, all aggregates located at the local site must be online. However, if the MetroCluster configuration is in switchover, root aggregates at the disaster recovery site are permitted to be offline.
This example shows a cluster in normal operation:
cluster1::> storage aggregate show -state !online There are no entries matching your query.
This example shows a cluster in switchover, in which the root aggregates at the disaster recovery site are offline:
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.
-
Verify the state of the volumes:
volume show -state !online
This command displays any volumes that are not online.
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.
This example shows a cluster in normal operation, in which the volumes at the disaster recovery site are not online.
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.
-
Verify that there are no inconsistent volumes:
volume show -is-inconsistent true
See the Knowledge Base article Volume Showing WAFL Inconsistent on how to address the inconsistent volumes.