HP StorageWorks Fabric OS 5.2.x administrator guide (5697-0014, November 2009)

356 Administering Advanced Zoning
Before linking two switches together, it is important that you know the zone database limit of adjacent
switches. For example, when switches running Fabric OS v3.2, v4.4.0, or 5.1.x discover that the zone
merge database is larger than its pre-determined zone database size limit, they issue a reject notification
before symmetrically segmenting their own ends of the ISL, thereby preventing the new switch from joining
the fabric.
Symmetrical segmentation occurs when both ends of an ISL are shut down. Subsequently, no frames are
exchanged between those two switches.
Asymmetrical segmentation not only prevents frames from being exchanged between switches, but also
causes routing inconsistencies.
The best way to avoid either type of segmentation is to know the zone database size limit of adjacent
switches. The following tables provide the expected behavior based on different database sizes after a
zone merge is specified..
3.x 128
3.1.x 96
3.2.x 256
4.x, 4.1.x, 4.2.x 128
4.4.x 256
5.0.1 256
5.0.x 256
5.1.x 256
5.2.x 1024
Table 83 Zoning database limitations (continued)
Fabric OS version Maximum database size (KB))
Table 84 Resulting database size: 0 to 96K
Receiver
Initiator
Fabric
OS 2.6
Fabric
OS 3.1
Fabric
OS 3.2
Fabric OS
4.0/4.1/4.2
Fabric OS
4.3/4.4.0
Fabric OS
5.0.0/
5.0.1/5.1.x
Fibre
Channel
Router
XPath 7.3
Fabric OS 2.6/3.1 Join Join Join Join Join Join Join Join
Fabric OS 3.2 Join Join Join Join Join Join Join Join
Fabric OS
4.0/4.1/4.2
Join Join Join Join Join Join Join Join
Fabric OS
4.3/4.4.0
Join Join Join Join Join Join Join Join
Fabric OS
5.0.0/5.0.1
Join Join Join Join Join Join Join Join
Fibre Channel
Router
Join Join Join Join Join Join Join Join
XPath 7.3 Join Join Join Join Join Join Join Join