HP StorageWorks 8/80 HP StorageWorks Fabric OS 6.2 administrator guide (5697-0 - Page 213

See "Validating a zone" on page 249 for instructions on using the zone --validate command. For more information about the zone command and its use with Admin Domains, see the Fabric OS Command Reference. 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 noaccess only. Before configuring any Admin Domain, you must set the default zone to noaccess mode. Admin Domains without effective zone configurations are presented with noaccess. See "Default zoning mode" on page 250 for more information. If the administrative domain feature is not active (AD1-AD254 are not configured and no explicit members are added to AD0), AD0 supports both allaccess and noaccess default zone modes. Admin Domains introduce two types of zone database nomenclature and behavior: • Root zone database If you do not use Admin Domains, there is only one zone database. This legacy zone database is known as the root zone database. If you create Admin Domains, several zone databases exist: the root zone database, which is owned by AD0, and other zone databases, one for each user-defined Admin Domain. • During the zone update process, only the root zone database is sent to non-AD-capable switches. • AD-level zone information is merged with the root zone configuration and enforced. • Zone databases The Admin Domains each have separate zone databases and zone transaction buffers. You can concurrently edit the separate zone databases. The AD zone database also has the following characteristics: • Each Admin Domain (AD1 through AD254) has its own zone definitions. These zone definitions include defined and effective zone configurations and all related zone objects including zones, zone aliases, and zone members. For example, you can define a zone name of test_z1 in more than one Admin Domain. • Each zone database has its own namespace. • 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 view only the complete hierarchical zone database, which is made up of the zone databases in AD0 through AD254. • With AD support, zoning updates are supported selectively at each AD level. For example, a zone change in AD1 results in an update request for the AD1 zone database only. Admin Domains and LSAN zones LSANs under each Admin Domain are collated into a single name space and sent out to FCR phantom domains using the following format: _AD 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 (for example, in the above example, if AD0 contains lsan_for_linux_farm_AD005, this causes a name collision). Fabric OS does not detect or report such name clash. LSAN zone names greater than 57 characters are not converted or sent to the FCR phantom domain. See Chapter 17, "Using the FC-FC routing service" on page 367 for information about LSAN zones. Fabric OS 6.2 administrator guide 211