HP P6000 Continuous Access Implementation Guide (T3680-96431, August 2012)

are placed into the configuration, separate replication zones should be created for those pairs
of arrays.
If array system fan-out is required, then the additional array should be added to a new
replication zone. Only arrays that will participate in data replication relationships should be
zoned together. Additional arrays (up to supported limits) can be added to either site. See
the HP P6000 Enterprise Virtual Array Compatibility Reference for the number of arrays
supported for system fan-out.
• HP P6000 Command View management zones—The zones for a HP P6000 Command View
management server must include both the source and destination arrays to enable the creation
of DR groups and proper management of the arrays. The management server must also have
at least one host port from each controller of the arrays zoned with the HP P6000 Command
View management server HBA. Additional array pairs are zoned in a similar manner for each
site. If an additional array is added to either site and it will participate in a DR relationship,
then two additional zones should be created for each of the HP P6000 Command View
management server HBA ports and the additional array’s host ports.
NOTE: The configurations shown assume HP P6000 Command View is installed on a stand
alone server. HP P6000 Command View could also be installed on an application server
running a supported version of Windows. When a server is used as both an application server
and HP P6000 Command View management server, virtual disks must be properly presented
from arrays to the intended hosts. Unintended cross-site virtual disk presentations should be
avoided.
A multipathing solution must be implemented that isolates the host I/O traffic to the targeted
I/O array host ports paths, which will maintain the desired traffic isolation. See the appropriate
multipathing documentation for path selection setup. Using a server for both host I/O and HP
P6000 Command View traffic should be avoided if traffic isolation is not available.
These zoning techniques provide a lower cost option than using discrete components to create the
multiple fabrics shown in “Fabric configuration drawings” (page 58). Zoning does not provide
physical separation of replication traffic over the intersite communication paths. These paths may
use dark fiber or FCIP connections between the local and remote sites. The lack of physical
separation in the configurations included here requires the zoning configuration be such that the
intersite communications be used to service only HP P6000 Continuous Access replication and HP
P6000 Command View management traffic. Application I/O should be limited to local arrays.
Cross-site presentation of virtual disks will result in host I/O traffic across the ISLs which may impact
HP P6000 Continuous Access performance. Cross-site presentations of virtual disks should be
avoided without a careful historical analysis of the utilization rate on the intersite communication
path.
Understanding the zoning drawings
The following sections illustrate the zones used for single-fabric and dual-fabric configurations. A
topology drawing showing the physical components for each configuration is shown first. The
zoning drawings use red and blue shading to identify the ports that comprise each zone. The ports
included in a zone are further identified using the same colors. Any port that is not colored is not
included in a zone.
Recommended single-fabric zoning configurations
The following zoning can be accomplished using a single fabric. This is a reduced availability
configuration consisting of a single switch at both the local and remote sites.
Creating fabrics and zones 71