HP StorageWorks Fabric OS 6.1.1 administrator guide (5697-0235, December 2009)

Fabric OS 6.1.1 administrator guide 201
Figure 12 shows a fabric with four non-overlapping hardware-enforced zones.
Figure 12 Hardware-enforced non-overlapping zones
Figure 13 shows the same fabric components, but with overlapping zones.
HP StorageWorks
4/8 SAN Switch,
4/16 SAN Switch,
Brocade 4Gb
SAN Switch for HP
p-Class
BladeSystem,
Brocade 4Gb
SAN Switch for HP
c-Class
BladeSystem, SAN
Switch 4/32,
4/64 SAN
Switch, SAN
Switch 4/32B,
400 MP Router,
8/8 SAN Switch,
8/24 SAN Switch,
8/40 SAN
Switch, and 8/80
SAN Switch,
4/256 SAN
Director, and the
DC SAN
Backbone Director
(short name, DC
Director)
Enable hardware-enforced zoning on
domain,port zones, and WWN zones.
Overlap of similar zone types does not result in
the loss of hardware enforcement. Overlap
with other zone type results in the loss of
hardware enforcement.
As in the Brocade 2000-series switches,
connecting a device specified by WWN to a
port specified in a domain,port zone results in
loss of the hardware enforcement in both
zones.
For the 4/256 SAN Director with an
FC4-48 port blade and the DC Director
with an FC8-48 port blade: If ports 16
through 47 on the FC4-48 port blade use
domain,port identifiers, session-based zoning
is enforced on these ports.
Use either WWN or
domain,port identifiers.
Mixed switches Enable hardware-enforced zoning according
to each switch type. Use the portZoneShow
command to find the zone type to which a
device is attached. See ”Identifying the
enforced zone type” on page 203.
Use domain,port identifiers.
You can use WWN
identifiers if you place disk
and tape targets on HP
2Gb and
SAN Director
2/128
models, and do not
use domain,port identifiers.
Table 55 Enforcing hardware zoning (continued)
Fabric type Methodology Best practice
Port_Zone1
Port_Zone2
Core
Switch
Zone Boundaries
WWN_Zone1
WWN_Zone2
22.2b(13.2)