Switch zoning for Hitachi HUS VM systems
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, as the Hitachi HUS VM system can virtualize storage itself, it must be zoned separately from other storage that Storwize® V3700 can detect to prevent issues with Storwize V3700 LUNs.
The Hitachi HUS VM systems present themselves by default to the Storwize V3700 system as separate controllers for each port that is zoned to the Storwize V3700 system. For example, if one of these storage systems has four ports that are zoned to the Storwize V3700 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 Storwize V3700 system through all controller ports that are zoned to the Storwize V3700 system by using the same logical unit number (LUN).
Fabric zoning
When you zone a Hitachi HUS VM storage system to the Storwize V3700 backend ports, be sure to have multiple zones or multiple Hitachi HUS VM storage system and Storwize V3700 ports per zone to enable multipathing.
Target port sharing
The Hitachi HUS VM 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 Storwize V3700 system and a Hitachi HUS VM system at the same time.