HP StorageWorks SAN Virtualization Services Platform Administrator Guide (5697-0934, May 2011)

a single back-end storage related zone. However, VSM ports which have both target and
initiator behavior should only be regulated to a single port in any given zone.
Interaction between different zones must be taken into account if they share any devices. For
example, if two different hosts are accessing the same DPM front-end port through separate
zones, it is important to consider the possibility that the port might become a bottleneck in the
configuration if both hosts are accessing it simultaneously.
Following these guidelines when implementing an HP SVSP zoning configuration allows for simple,
easy-to-understand zones that provide a high degree of control over the activity and allocation of
resources in the SAN. Some exceptions to these general guidelines can be made but only in the
case when the properties of all devices in the zone are well-defined and fully understood. Devices
can be added or removed from the SAN by adding or removing the respective zones to which
they are a member from the active configuration without reconfiguring zones and potentially
impacting other devices. Using super zones with a large number of devices is highly discouraged
with HP SVSP, since this can lead to unpredictable communication between devices over the SAN
and makes the zone configuration harder to adjust in the future.
Zoning components in HP SVSP
This section describes zoning between specific components in HP SVSP. Given the complex nature
of the HP SVSP with multiple devices and interactions, the overall zoning configuration can be
difficult to understand if presented in its entirety. By examining each type of zone and providing
general zoning templates, the material in this section can be applied to a wide range of
configurations with different devices. The following zone types will be examined in detail in this
section:
DPM-Host zone
DPM-Storage zone
DPM-VSM zone
VSM-Storage zone
VSM-VSM zone
Figure 6 (page 34) illustrates a high-level view of the interaction between devices displaying the
types of zones. Each two-way arrow represents a zone type. Table 3 (page 34) shows an example
of zone naming conventions for each HP SVSP zone type. Table 4 (page 34) shows an example
of an alias naming convention for each HP SVSP device port type.
Zoning components in HP SVSP 33