Figure 3-10 shows a storage subsystem zoning example. SVC-Storwize V7000 Zone 1: Fabric Domain ID, Port  11,0 - 11,1 - 11,2 - 11,3  –  11,8  SVC-EMC Zone 1:  11,0 - 11,1 - 11,2 - 11,3  –  11,9  SVC-Storwize V7000 Zone 2: Fabric Domain ID, Port  12,0 - 12,1 - 12,2 - 12,3  –  12,8  SVC-EMC Zone 2:  12,0 - 12,1 - 12,2 - 12,3  –  12,9  Fabric ID 12  Fabric ID 11  Fabric ID 22  Fabric ID 21  Fabric  1  Fabric  2  1  2  1  2  1  1  3  3  SVC #  Port # SVC  0  1  2  3  Port # Switch  1  2 1  2  2  2 4  4  SVC #  Port # SVC  0  1 2  3  Port # Switch V1  V2  E2  E1  Zoning Info:  All storage ports  and all SVC ports  Storwize Family EMC ²  Ports 0 1 2 3 8 9  Ports 0 1 2 3 8 9  ISL ISL Figure 3-10 Storage subsystem zoning example There might be particular zoning rules governing attachment of specific back-end storage  systems. Review the guidelines at the following website to verify whether you need to  consider additional policies when planning zoning for your back end systems: https://ibm.biz/BdzPhi Hosts must be zoned to the I/O Group to be able to access volumes presented by this I/O  Group. The preferred zoning policy is to create a separate zone for each host HBA port, and place  exactly one port from each node in each I/O group that the host accesses in this zone. For  deployments with more than 64 hosts defined in the system, this host zoning scheme is  mandatory. If you plan to use NPIV, review additional host zoning requirements on IBM Knowledge  Center: https://ibm.biz/BdzPhj When a dual-core SAN design is used, it is a requirement that no internode communications  use the ISL link. When you create host zones in this type of configuration, ensure that each  system port in the host zone is attached to the same Fibre Channel switch. 3.6.5 Host zones 60  Implementing the IBM System Storage SAN Volume Controller with IBM Spectrum Virtualize V8.2.1