Switch zoning configurations for the Hitachi HUS VM system include fabric zoning, target port sharing, host splitting, and controller splitting.
The Hitachi HUS VM system has no zoning limitations. However, because the Hitachi HUS VM system can virtualize storage itself, it must be zoned separately from other storage that the system can detect to prevent issues with system's LUNs.
The Hitachi HUS VM 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 appears as a separate controller rather than one controller with 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 VMstorage system to the system's backend ports, be sure to have multiple zones or multiple Hitachi HUS VMstorage system and system ports per zone to enable multipathing.
The Hitachi HUS VMstorage 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 VM system at the same time.
Performance issues might be caused by splitting controllers. Ideally, in the configuration, the system should have exclusive access to the controller. Hitachi HUS VMstorage 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.