Viewing Metro and Global Mirror properties

Use the Viewing Metro and Global Mirror Properties panel in the SAN Volume Controller Console to view Metro Mirror and Global Mirror properties related to the cluster.

Introduction

This panel displays two sets of properties that are related to cluster partnerships. The first table contains properties that pertain to all the partnerships that are defined on the selected cluster. The second table displays properties for each of the clusters that are defined in partnerships with the selected cluster.

Attributes

The following properties pertain to the Global Mirror partnerships:

Link Tolerance
Displays the length of time that the primary response time remains impacted before relationships are suspended. Valid values are 0 - 86400 seconds. A value of zero disables this feature. The default value is 300 seconds.
InterCluster Delay Simulation
Displays the amount of time to delay I/O writes to the intercluster secondary VDisk. Valid values are 0 - 100 milliseconds. A value of zero disables this feature. The default value is zero.
IntraCluster Delay Simulation
Displays the amount of time to delay I/O writes to the intracluster secondary VDisk. Valid values are 0 - 100 milliseconds. A value of zero disables this feature. The default value is zero.

Attributes

The following attributes are displayed for the selected cluster that is defined in the partnership:
Cluster Name
Displays the name of the selected cluster.
IP address (IPv4)
Displays the IPv4 IP address of the local or remote partner cluster.
IP address (IPv6)
Displays the IPv6 IP address of the local or remote partner cluster.
Location
Displays whether the selected cluster is a local or remote partner cluster.
State
Displays the current state of the partnership. The following values are possible:
Partially Configured
Indicates that only one cluster partner is defined from a local or remote cluster to the displayed cluster and is started. For the displayed cluster to be configured fully and to complete the partnership, you must define the cluster partnership from the cluster that is displayed to the corresponding local or remote cluster. You can do this by issuing the mkpartnership command on the local and remote cluster that are in the partnership, or by using the SAN Volume Controller Console to create a partnership on both the local and remote clusters.
Fully Configured
Indicates that the partnership is defined on the local and remote clusters and is started.
Remote Not Present
Indicates that the remote cluster is not present to the partnership.
Partially Configured (Local Stopped)
Indicates that the local cluster is only defined to remote cluster and the local cluster is stopped.
Fully Configured (Local Stopped)
Indicates that a partnership is defined on both the local and remote clusters and the remote cluster is present, but the local cluster is stopped.
Fully Configured (Remote Stopped)
Indicates that a partnership is defined on both the local and remote clusters and the remote cluster is present, but the remote cluster is stopped.
Fully Configured (Local Excluded)
Indicates that a partnership is defined between a local and remote cluster; however, the local cluster has been excluded. Usually this state occurs when the fabric link between the two clusters has been compromised by too many fabric errors or slow response times of the cluster partnership. Check the error log for 1720 errors by selecting Service and Maintenance > Analyze Error Log to resolve these errors.
Fully Configured (Remote Excluded)
Indicates that a partnership is defined between a local and remote cluster; however, the remote cluster has been excluded. Usually this state occurs when the fabric link between the two clusters has been compromised by too many fabric errors or slow response times of the cluster partnership. Check the error log for 1720 errors by selecting Service and Maintenance > Analyze Error Log to resolve these errors.
Fully Configured (Remote Exceeded)
Indicates that a partnership is defined between a local and remote cluster and the remote is available; however, the remote cluster exceeds the number of allowed clusters within a cluster network. The maximum of four clusters can be defined in a network. If the number of clusters exceeds that limit, SAN Volume Controller determines the inactive cluster or clusters by sorting all the clusters by their unique identifier in numerical order. The inactive cluster partner which is not in the top four of the cluster unique identifiers displays Fully Configured (Remote Exceeded).
Bandwidth (MBps)
Displays the bandwidth that was specified, shown in megabytes per second (MBps).

Actions

The following action is available:

Close
Click this button to exit the panel.
Library | Support | Terms of use | Feedback
© Copyright IBM Corporation 2003, 2009. All Rights Reserved.