348 Administering Advanced Zoning
name server returns only those devices that are in the same zone as the initiator. Devices that are not
part of the zone are not returned as accessible devices.
Table 82
shows the various switch models, the hardware Zoning methodology for each, and tips for best
usage.
Table 82
Enforcing hardware Zoning
Fabric Type
Methodology
Best practice
HP StorageWorks
1 GB
Enables hardware-enforced Zoning
only on domain, port zones; WWN or
mixed zones are not
hardware-enforced. Any domain, port
zone that overlaps a mixed or WWN
zone is not hardware-enforced.
An overlap occurs when a member
specified by WWN is connected to a
port in a domain, port zone. The
domain, port zone loses its hardware
enforcement even though a review of
the zone configuration does not
indicate it.
Use
domain, port
identifiers. Do
not identify a zone member by its
WWN.
HP StorageWorks
2/8 EL, HP
StorageWorks
MSA SAN Switch
2/8, HP
StorageWorks
2/16 EL,
HP StorageWorks
2/16, 4/16 SAN
Switch and 4/8
SAN Switch,
SAN Switch
4/32, 4/64 SAN
Switch, 400 MP
Router, SAN
Director 2/128,
and 4/256 SAN
Director models
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 HP StorageWorks 1 GB
switches, connecting a device
specified by WWN into a port
specified in a domain, port zone
results in loss of the hardware
enforcement in both zones.
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.
Use
domain, port
identifiers.
You can use WWN identifiers if
you place disk and tape targets
on 3000-series, and SAN Director
2/128 models, and do not use
domain, port
identifiers.
Summary of Contents for AE370A - Brocade 4Gb SAN Switch 4/12
Page 18: ...18 ...
Page 82: ...82 Managing user accounts ...
Page 102: ...102 Configuring standard security features ...
Page 126: ...126 Maintaining configurations ...
Page 198: ...198 Routing traffic ...
Page 238: ...238 Using the FC FC routing service ...
Page 260: ...260 Administering FICON fabrics ...
Page 280: ...280 Working with diagnostic features ...
Page 332: ...332 Administering Extended Fabrics ...
Page 414: ...398 Configuring the PID format ...
Page 420: ...404 Configuring interoperability mode ...
Page 426: ...410 Understanding legacy password behaviour ...
Page 442: ...426 ...
Page 444: ......
Page 447: ......