Admin Domains, Zones, And Zone Databases - HP A7533A - Brocade 4Gb SAN Switch Base Administrator's Manual

Table 48 Admin Domain interaction with Fabric OS features (continued)
Fabric OS feature
FICON
iSCSI
Management
applications
Port-Swapping and
PID formats
RSCN
Refer to the Fabric OS Command Reference Manual for detailed information about the commands. The
following sections describe Admin Domain interactions with zones, zone databases, and LSAN zones.

Admin Domains, zones, and zone databases

Each Admin Domain has its own zone database, with both defined and effective zone configurations and
all related zone objects (zones, zone aliases, and zone members). Within an Admin Domain, you can
configure zoning only with the devices that are present in that Admin Domain.
With a hierarchical zoning model, the name space for each Admin Domain and the root zones are
separate; configurations are supported with the same zone object name appearing in the root zone
database and different ADs (for example, the same zoneset name in AD1 and AD2).
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 Admin Domain
zoneset are enforced. The enforcement policy encompasses zones in the effective zoneset of the root zone
database and the effective zonesets of each AD.
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 defzone mode of noaccess alone. Before configuring any Admin Domain, you
must set the defzone to noaccess mode. Admin Domains without effective zone configurations are
presented with no access. See
Admin Domain interaction
Admin Domains support FICON. However, you must perform additional steps
because FICON management (CUP) requires additional physical control of the
ports. You must set up the switch as a physical member of the FICON AD.
DCC and SCC policies are supported only in AD0 and AD255, since ACL
configurations are supported only in AD0 and AD255.
iSCSI operations are supported only in AD0.
Management interfaces that access the fabric without a user's credentials
continue to get the physical fabric view. Examples include: SNMPV1, Web Tools,
Fabric Manager; http access, unzoned management server query, FAL in-band CT
requests from FAL Proxy to FAL Target, and FC-CT based management
applications (such as Tivoli).
Access from applications or hosts using Management Server calls can be
controlled using the Management Server ACL support provided by the
msConfigure command. Note that this is a switch-specific setting and not a
fabric-wide setting.
Admin Domain port members are specified in (domain, port) format.
Based on the PID format, a (domain, port) member indicates a slot/port
in the switch. The (domain, port) member is effectively a member of that
AD. If the PID format changes, all (domain, port) AD members with a port
index of less than 128 are automatically converted to meet the new PID
format.
Port swapping has no effect on AD support as port swapping swaps only
the area numbers of two ports and Admin Domains are specified using
(domain, port) member.
For detailed information about configuring the PID format, see
"Configuring the PID format" on page 423.
Admin Domains do not introduce any RSCN changes to devices or hosts.
"Activating default zones" on page 381 for more information.
Fabric OS 5.3.0 administrator guide 169