Brocade Fabric OS Administrators Guide (Supporting Fabric OS v7.3.0) - Manual (Page 469)

• There is no zone database linked to the physical fabric (AD255) and no support for zone database
updates. In the physical fabric context (AD255), you can only view the complete hierarchical zone
database, which is all of the zone databases in AD0 through AD254.
• You can concurrently edit the separate zone databases.
• With AD support, zoning updates are supported selectively at each AD level. For example, a zone
change in AD1 results in an update request only for the AD1 zone database.
Zoning operations ignore any resources not in the Admin Domain, even if they are specified in the zone.
The behavior functions similarly to specifying offline devices in a zone. All zones from each AD zone
configuration are enforced. The enforcement policy encompasses zones in the effective zone
configuration of the root zone database and the effective zone configurations of each AD.
NOTE
You must define the Admin Domain members in the same way that they are defined as zone members.
That is, if an object is defined by WWN in a zone, it must be defined by WWN in an Admin Domain. If it
is defined by domain,index in a zone, it must be defined by domain,index in the Admin Domain. If both
zoning schemes are used, then objects must be defined in the Admin Domain by both WWN and
domain,index
Using the zone --validate command, you can see all zone members that are not part of the current
zone enforcement table but are part of the zoning database. A member might not be part of the zone
enforcement table for the following reasons:
• The device is offline.
• The device is online but is not part of the current Admin Domain.
Refer to Validating a zone on page 316 for instructions on using the zone --validate command.
NOTE
AD zone databases do not have an enforced size limit. The zone database size is calculated by the
upper limit of the AD membership definition and the sum of all the zone databases for each AD.
Admin Domains support the default zone mode of No Access only. Before configuring any Admin
Domain, you must set the default zone to No Access mode. Admin Domains without effective zone
configurations are presented with No Access. Refer to
Default zoning mode on page 319 for more
information.
If the administrative domain feature is not active (AD1 through AD254 are not configured and no explicit
members are added to AD0), AD0 supports both All Access and No Access default zone modes.
Admin Domains and LSAN zones
Logical storage area networks (LSANs) under each Admin Domain are collated into a single name
space and sent out to FCR phantom domains using the following format:
<original_LSAN_name>_AD<AD_num>
For example, a zone with name lsan_for_linux_farm in AD5 is internally converted to
lsan_for_linux_farm_AD005.
LSAN zone names in AD0 are never converted for backward-compatibility reasons.
The auto-converted LSAN zone names might collide with LSAN zone names in AD0 (in the example, if
AD0 contains lsan_for_linux_farm_AD005, this causes a name collision). Fabric OS does not detect or
report such name clashes.
LSAN zone names greater than 57 characters are not converted or sent to the FCR phantom domain.
Admin Domains and LSAN zones
Fabric OS Administrators Guide 469
53-1003130-01