There are limitations in switch zoning for the SAN Volume Controller and
the HDS USP or NSC.
The SAN Volume Controller can
be connected to the HDS USP or NSC with the following restrictions:
- If an LU is mapped to a SAN Volume Controller port
as LUN x, the LU must appear as LUN x for all mappings
to target ports.
- Only fibre-channel connections can be used to connect a SAN Volume Controller to
the HDS USP or NSC system.
- Because the SAN Volume Controller limits
the number of worldwide node names (WWNNs) for each storage system
and the HDS USP and NSC present a separate WWNN for each port, the
number of target ports that the SAN Volume Controller can
resolve as one storage system is limited. Perform the following steps
to provide connections to more target ports:
- Divide the set of target ports into groups of 2 to
16.
- Assign a discrete set of LUs to each group.
The SAN Volume Controller can
then view each group of target ports and the associated LUs as separate
HDS USP or NSC systems. You can repeat this process to use all target
ports.
Note: The HDS USP and NSC systems present themselves
to a SAN Volume Controller cluster
as separate controllers for each port zoned to the SAN Volume Controller.
For example, if one of these storage systems has 4 ports zoned to
the SAN Volume Controller,
each port appears as a separate controller rather than one controller
with 4 WWPNs. In addition, a given logical unit (LU) must be mapped
to the SAN Volume Controller through
all controller ports zoned to the SAN Volume Controller using
the same logical unit number (LUN).
Controller splitting
You can split the HDS
USP or NSC between other hosts and the
SAN Volume Controller under
the following conditions:
- A host cannot be simultaneously connected to both an HDS USP or
NSC and a SAN Volume Controller.
- Port security must be enabled for target ports that are shared.
- An LU that is mapped to a SAN Volume Controller cannot
be simultaneously mapped to another host.