Chapter 10. Copy services 555
10.6.5 IP partnership and terminology
The IP partnership terminology and abbreviations that are used are listed in Table 10-7.
Table 10-7 Terminology for IP partnership
IP partnership terminology Description
Remote copy group or Remote copy port group The following numbers group a set of IP addresses that are
connected to the same physical link. Therefore, only IP
addresses that are part of the same remote copy group can
form remote copy connections with the partner system:
0 – Ports that are not configured for remote copy
1 – Ports that belong to remote copy port group 1
2 – Ports that belong to remote copy port group 2
Each IP address can be shared for iSCSI host attach and
remote copy functionality. Therefore, appropriate settings must
be applied to each IP address.
IP partnership Two systems that are partnered to perform remote copy over
native IP links.
FC partnership Two systems that are partnered to perform remote copy over
native Fibre Channel links.
Failover Failure of a node within an I/O group causes the volume access
to go through the surviving node. The IP addresses fail over to
the surviving node in the I/O group. When the configuration
node of the system fails, management IPs also fail over to an
alternative node.
Failback When the failed node rejoins the system, all failed over IP
addresses are failed back from the surviving node to the
rejoined node, and virtual disk access is restored through
this node.
linkbandwidthmbits Aggregate bandwidth of all physical links between two sites
in Mbps.
IP partnership or partnership over native IP links These terms are used to describe the IP partnership feature.
Discovery Process by which two IBM Spectrum Virtualize systems
exchange information about their IP address configuration. For
IP-based partnerships, only IP addresses configured for
Remote Copy are discovered.
For example, the first Discovery takes place when the user is
running the mkippartnership CLI command. Subsequent
Discoveries can take place as a result of user activities
(configuration changes) or as a result of hardware failures (for
example, node failure, ports failure, and so on).
To Next Page
Loading...
Need help?
General