.Part 5 Storage Security Best Practices and Support Information HP SAN Design Reference Guide 785355-001

• Application
• Port allocation
Zoning by operating system
Zoning by operating system is the minimal required zoning method. This method allows multiple
HBAs with the same operating system to be grouped with the accessed storage ports. Zoning by
operating system prevents the interaction of HBAs with incompatible operating systems.
This method limits the number of zones in a fabric. A large zone can be divided into multiple zones
within the operating system type. Zoning by operating system type limits disruptions and the number
of fabric change notifications.
Certain situations require zoning by HBA, for example, configuring server access to multiple storage
types. For additional zoning requirements, see:
• “Common server access, different storage system types” (page 209)
• “Zoning limits and enforcement” (page 149) (H-series)
• “Zoning limits and enforcement” (page 120) (B-series)
• “Zoning limits and enforcement” (page 138) (C-series)
Zoning by HBA
For zoning by HBA, each zone has only one HBA (initiator); each of the target devices is added
to the zone. Typically, a zone is created for the HBA and the disk storage ports are added. If the
HBA also accesses tape devices, HP recommends that a second zone be created for the HBA and
associated tape devices. For zoning requirements with different HBA models on the same server,
see “Common server, different HBAs” (page 209).
This zoning philosophy is the preferred method for both standalone and clustered systems; zoning
by single HBA requires the creation of numerous zones; each containing only a few members.
Zone changes affect a small number of devices, minimizing the effect of an incorrect zone change.
Zoning by HBA port
Zoning by HBA port applies when you are utilizing dual-ported HBAs. From a zoning perspective,
you can view each port as if it were a separate HBA. As such, you would use the same criteria as
described above in the Zoning by HBA section. In this case however, each HBA port should be
thought of as a separate HBA.
Zoning by NPIV port
With NPIV, one physical link is shared by multiple virtual ports and each is assigned a different
WWPN. Similar to zoning by HBA port, from a zoning perspective, each virtual port should be
viewed as if it were a separate HBA.
Zoning with 3PAR persistent ports
HP 3PAR Persistent Ports technology allows for a completely non-disruptive software upgrade
environment (from the host pathing point of view) where host-based multipathing software will not
be involved in the software upgrade process. Additionally, HP 3PAR Persistent Ports technology
renders an array node failure transparent to hosts using the array, avoiding the need for the
multipathing software of the host to maintain host connectivity for node failure recovery. For
information about zoning when using this feature, see the "HP 3PAR Persistent Ports technical
whitepaper (4AA4-4545ENW), available on the HP storage website: http://
h18006.www1.hp.com/storage/saninfrastructure/index.html. The whitepaper has a separate
section on "Best practice and zoning and multipathing considerations".
388 Best practices