HP StorageWorks SAN Virtualization Services Platform administrator guide (5697-0204, January 2010)

VSM-VSM zoning
The VSM-VSM zone allows the VSMs in an HP SVSP configuration to communicate with each other
over the SAN in order to determine VSM connectivity state and manage failover behavior between
the VSMs. This special purpose zone is not classified as a front-end or back-end zone since it does
not involve any storage devices or hosts. In this type of zone, a VSM is not strictly classified as a
target or initiator. The only rule for creating VSM-VSM zones is that each port on a VSM must be
zoned to all ports on the other VSM. This can be accomplished by simply creating a single zone that
includes all ports from both VSMs. Figure 18 illustrates the zoning between VSMs using a single zone
that includes all ports between both VSMs for full connectivity.
Figure 18 Zoning between two VSMs
.
Figure 8: Zoning between VSMs using a single zone including all ports between both VSMs for full
connectivity.
Cleaning up after zoning changes
Over a period of time, items removed from a zone, or items that are no longer necessary, are kept
around or can build up in the configuration. These remnants can lead to confusion or errors if not
removed. The following procedure is a way to eliminate these remnants that serve no use in the
configuration:
1. Open the VSM GUI.
2. Browse to Entities > Back-End LUs.
• Look for LUs with a status of Partial.
• For each Partial LU, select the Access Path tab, right-click on each failed or absent path (indic-
ated with a red X in the icon), and click Delete.
• Repeat this for all Partial LUs.
HP StorageWorks SAN Virtualization Services Platform administrator guide 55