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 system as separate controllers for each port that is zoned to the system. For example, if one of these storage systems has four ports that are zoned to the system, each port is viewed as a separate controller rather than as one controller that has four WWPNs. A given logical unit (LU) must be mapped to the system through all controller ports that are zoned to the system by using the same logical unit number (LUN).
When you zone a Hitachi HUS 100 familystorage system to the system's backend ports, be sure to have multiple zones or multiple Hitachi HUS 100 familystorage system and system ports per zone to enable multipathing.
The Hitachi HUS 100 familystorage 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.
To prevent multipathing driver incompatibility issues, avoid connecting a host to both the system and a Hitachi HUS 100 family system at the same time.
Performance issues might be caused by splitting controllers. Ideally, configure so that the system has exclusive access to the controller. Hitachi HUS 100 familystorage system LUNs that are mapped to the system cannot be mapped to other hosts. LUNs that are not presented to the system can be mapped to other hosts.