Help

The idle timeout is based on the URL used to access the GUI. Therefore when you access the GUI on cluster 1 and set the idle
timeout, it will apply only to cluster 1. If you log into cluster 2, the idle timeout dialog will not have the same value as that of
cluster 1, because the URL is different.
The value of the timeout field can be an integer value between 1 and 12 if the field unit value is set to hours. The value of the
Timeout field can be an integer value between 1 and 720 if the field unit value is set to minutes.
NOTE: The value for Timeout is stored in a file named using the URL with which you accessed the GUI. If you access
the GUI for a cluster using different URLs (For example, using the DNS name of the cluster or using the IP address), the
timeout value for each URL used will be different.
Provision storage data reload policy
Select one of the following options to define how often data is reloaded when navigating through provisioning views.
● Always — Always reload data upon navigation to a storage object view. This is the default setting.
● Never — Never reload data upon navigation to a storage object view.
● After — The number of hours or minutes after which to reload data when you navigate to a storage object view. Enter a
number in the field and then select the time interval. Once you navigate to an object view, the data will automatically reload
at the specified time interval.
The data reload policy setting applies only to the URL and client used to access the GUI when you set the policy. Therefore, if
you log in to the GUI again using a different client (laptop versus desktop) or a different URL (cluster 1 versus cluster 2), the
reload policy setting will not be applied to that GUI session.
To manually refresh the data, click the Refresh icon
in the upper-right corner of the screen title bar or the Last Refreshed
link at the bottom of the screen.
Metro node cluster status
The following table defines the values for the metro node cluster states.
Status Type
Values Definition
Operational Status OK The cluster is functioning normally.
Degraded The cluster is not operating as configured. This may indicate one
or more of the following problems: degraded redundancy level (for
example, a director is dead), suspended virtual volumes or exported
volumes, storage volumes not visible from all directors, or the metadata
volume is not yet processed.
Unknown Metro node encountered a problem determining the operational status
of the cluster. This may indicate a degraded state, since it usually means
that at least one of the directors is not responding or is communicating
abnormally.
Transitioning The cluster is reacting to external events and may not be operating as
configured. I/O may be suspended during the transition period.
Isolated The cluster is not communicating with any other clusters.
Not-running All directors in any one of the clusters are in Stopped state and when
the VPN is stopped between clusters.
Transitioning Indication Suspended exports Cluster lost local quorum during the unvaulting state. This is possibly due
to a disk not visible from all directors, no active meta-volume, delayed
cluster transition, metadata, not all directors are present, or no quorum.
Suspended volumes The distributed device is not accepting new I/O; pending I/O requests
are frozen.
Health state OK The cluster is functioning normally.
152 Help