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 Lenovo Storage V7000 can detect to prevent issues with Lenovo Storage V7000 LUNs.
The Hitachi HUS VM systems present themselves by default to a Lenovo Storage V7000 system as separate controllers for each port that is zoned to Lenovo Storage V7000. For example, if one of these storage systems has four ports that are zoned to Lenovo Storage V7000, each port appears as a separate controller rather than one controller with four WWPNs. A given logical unit (LU) must be mapped to Lenovo Storage V7000 through all controller ports that are zoned to Lenovo Storage V7000 by using the same logical unit number (LUN).
When you zone a Hitachi HUS VMstorage system to the Lenovo Storage V7000 backend ports, be sure to have multiple zones or multiple Hitachi HUS VMstorage system and Lenovo Storage V7000 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 a Lenovo Storage V7000 system and a Hitachi HUS VM system at the same time.
Performance issues might be caused by splitting controllers. Ideally, configure so that Lenovo Storage V7000 has exclusive access to the controller. Hitachi HUS VMstorage system LUNs that are mapped to the Lenovo Storage V7000 system cannot be mapped to other hosts. LUNs that are not presented to Lenovo Storage V7000 can be mapped to other hosts.