88
Installation
As you consider the physical connections of your system—specifically connections for replication—keep several
important points in mind:
•
Ensure that controllers have connectivity between systems, whether the destination system is co-located or
remotely located.
•
Qualified Converged Network Controller options can be used for host I/O or replication, or both.
•
The storage system does not provide for specific assignment of ports for replication. However, this can be
accomplished using virtual LANs for iSCSI and zones for FC, or by using physically separate infrastructure.
See also the paragraph above
•
For remote replication, ensure that all ports assigned for replication are able to communicate appropriately with
the replication system (see the CLI Reference Guide for more information):
For virtual replication, use the
query peer-connection
CLI command.
•
Allow a sufficient number of ports to perform replication. This permits the system to balance the load across
those ports as I/O demands rise and fall. If some of the volumes replicated are owned by controller A and others
are owned by controller B, then allow at least one port for replication on each controller module—and possibly
more than one port per controller module—depending on replication traffic load.
•
For the sake of system security, do not unnecessarily expose the controller module network port to an external
network connection.
Conceptual cabling examples are provided addressing cabling on the same network and cabling relative to different
networks.
IMPORTANT:
The replication feature must be licensed on all systems configured for replication, and the
controller module firmware must be compatible on all systems used for replication. See the topic about licensed
features in the Storage Manager Guide.
