Table of ContentsView in Frames

Determining if a volume is offline because its host cluster node is down

You can use the Unified Manager web UI to confirm or eliminate the possibility that a volume is offline because its host cluster node is down and that storage failover to its HA pair partner is unsuccessful.

Before you begin

The following requirements must be met:

About this task

To determine if the volume offline condition is caused by failure of the hosting cluster node and subsequent unsuccessful storage failover, perform the following actions:

Steps

  1. Locate and click the hypertext link displayed under SVM in the Related Devices pane of the offline volume's Volume details page.
    The Storage Virtual Machine details page displays information about the offline volume's hosting Storage Virtual Machine (SVM).
  2. In the Related Devices pane of the Storage Virtual Machine details page, locate and click hypertext link displayed under Volumes.
    The Volumes page displays a table of information about all the volumes hosted by the SVM.
  3. On the Volumes page State column header, click the filter symbol Icon for column filter, and then select the option Offline.
    Only the SVM volumes that are in offline state are listed.
  4. On the Volumes page, click the grid symbol Icon for grid view, and then select the option Cluster Node.
    You might need to scroll in the grid selection box to locate the Cluster Node option.
    The Cluster Node column is added to the volumes inventory and displays the name of the cluster node that hosts each offline volume.
  5. On the Volumes page, locate the listing for the offline volume and, in its Cluster Node column, click the name of its hosting cluster node.
    The Nodes tab on the Cluster details page displays the state of the HA pair of nodes to which the hosting cluster node belongs. The state of the hosting cluster node and the success of any cluster failover operation is indicated in the display.

After you finish

After you confirm that the volume offline condition exists because its host cluster node is down and storage failover to the HA pair partner has failed, contact the appropriate administrator or operator to manually restart the down cluster node and fix the storage failover problem.