Dot Hill Systems AssuredSAN 4544, Setup Manual

Page: 40 / 100

40 Connecting hosts
• Controller A port 3: 10.11.10.130
• Controller B port 0: 10.10.10.140
• Controller B port 1: 10.11.10.150
• Controller B port 2: 10.10.10.160
• Controller B port 3: 10.11.10.170
In addition to setting the port-specific options described above, you can also set common options. In
RAIDar‘s Configuration View panel, right-click the system and select Configuration > System Settings >
Host Interfaces . See the “To change iSCSI host interface settings” topic within the RAIDar user guide or online
help.
Connecting a management host on the network
The management host directly manages storage systems out-of-band over an Ethernet network.
1. Connect an RJ-45 Ethernet cable to the network port on each controller.
2. Connect the other end of each Ethernet cable to a network that your management host can access
(preferably on the same subnet).
NOTE: Connections to this device must be made with shielded cables—grounded at both ends—with
metallic RFI/EMI connector hoods, in order to maintain compliance with FCC Rules and Regulations. See
AssuredSAN Product Regulatory Compliance and Safety (included in your product’s ship kit).
Alternatively, you can access the document online. See Dot Hill’s customer resource center (CRC) web site
for additional information: http://crc.dothill.com .
Select AssuredSAN & R/Evolution Products > 4004 Series to download the PRC&S document.
Connecting two storage systems to replicate volumes
AssuredRemote™ replication is a licensed disaster-recovery feature that performs asynchronous (batch)
replication of block-level data from a volume on a local (primary) storage system to a volume that can be
on the same system or a second, independent system. The second system can be located at the same site
as the first system, or at a different site.
The two associated standard volumes form a replication set, and only the primary volume (source of data)
can be mapped for access by a server. Both systems must be licensed to use AssuredRemote, and must be
connected through switches to the same fabric or network (i.e., no direct attach). The server accessing the
replication set need only be connected to the primary system. If the primary system goes offline, a
connected server can access the replicated data from the secondary system.
Replication configuration possibilities are many, and can be cabled—in switch attach fashion—to support
the CNC-based 4844 systems on the same network, or on physically-split networks (4544 SAS systems do
not support replication). 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 local or remote.
• Assign specific ports for replication whenever possible. By specifically assigning ports available for
replication, you free the controller from scanning and assigning the ports at the time replication is
performed.
• For remote replication, ensure that all ports assigned for replication are able to communicate
appropriately with the remote replication system (see verify remote-link in the CLI Reference Guide for
more information).
• Allow two ports to perform replication. This permits the system to balance the load across those ports as
I/O demands rise and fall. On dual-controller enclosures, 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.