Switch zoning for Hitachi HUS 100 family storage systems
Switch zoning configurations for the Hitachi HUS 100 family system include fabric zoning, target port sharing, host splitting, and controller splitting.
The Hitachi HUS 100 family system has no zoning limitations.
The Hitachi HUS 100 family systems present themselves by default to the SAN Volume Controller system as separate controllers for each port that is zoned to the SAN Volume Controller system. For example, if one of these storage systems has four ports that are zoned to the SAN Volume Controller system, each port appears as a separate controller rather than one controller with four WWPNs. A given logical unit (LU) must be mapped to the SAN Volume Controller system through all controller ports that are zoned to the SAN Volume Controller system by using the same logical unit number (LUN).
Fabric zoning
When you zone a Hitachi HUS 100 family storage system to the SAN Volume Controller backend ports, be sure to have multiple zones or multiple Hitachi HUS 100 family storage system and SAN Volume Controller ports per zone to enable multipathing.
Target port sharing
The Hitachi HUS 100 family storage system can support LUN masking to enable multiple servers to access separate LUNs through a common controller port. In this setup, there are no issues with mixing workloads or server types.
Host splitting
To prevent multipathing driver incompatibility issues, avoid connecting a host to both the SAN Volume Controller system and a Hitachi HUS 100 family system at the same time.
Controller splitting
Performance issues might be caused by splitting controllers. Ideally, configure so that the SAN Volume Controller system has exclusive access to the controller. Hitachi HUS 100 family storage system LUNs that are mapped to the SAN Volume Controller system cannot be mapped to other hosts. LUNs that are not presented to the SAN Volume Controller system can be mapped to other hosts.