HP StorageWorks SAN Virtualization Services Platform administrator guide (5697-0109, July 2009)

Back-end zones for capacity-based zoning
Each VSM fabric has a back-end zone to connect the DPM initiator ports, VSM server, Command
View EVA server, and the storage array. The first column of the table describes the zones and is given
a name (called an alias), which mainly describes the components in that zone. Some abbreviations
used in the aliases are back-end (BE), VSM server 1 on blue fabric (VSM_1B), and VSM server 2 on
blue fabric (VSM_2B).
DPM initiator port zoning
Guidelines for zoning all DPM initiator ports:
The DPM initiators, ports 1 and 3 of each quad, connect to the back-end zone. This can create
up to four zones with two DPMs and two redundant fabrics.
No more than two paths (per DPM, per fabric) to any one array port (for example, one DPM quad
per fabric per storage array).
One DPM initiator per DPM per back-end zone.
VSM server zoning
VSM servers are in two sets of zones. In the first set of zones, each VSM server is a target to each
DPM quad. In the second set of zones, each VSM server is an initiator to all storage arrays that will
be presenting storage to the SVSP domain.
Array zoning
Guidelines for zoning an array are:
Use zoning to separate arrays from each other.
Limit the number of targets in a zone to one array that is on the same fabric.
At most four array ports (generally one-half an array) per back-end zone
For example, an EVA8x00 storage array can be connected to two quads with four ports per quad.
Front-end zones for capacity-based zoning
DPM target port zoning
Guidelines for zoning the two DPMs per DPM group:
The DPM targets, ports 0 and 2 of each quad, connect to the front-end zone. This can create up
to four zones with two DPMs and two redundant fabrics.
No more than two paths (per DPM, per fabric) to any one server (that is, one DPM quad per
fabric per server). This is a limit of 8 total paths per server.
Limit the number of targets in a zone to one DPM quad per DPM within a DPM group.
Host zoning
Use one OS per zone (either front-end servers or back-end DPM). See the OS zoning restrictions in
the HP SAN design guide at http://www/hp.com/go/sandesignguide
Zoning50