Admin Domains, Zones, And Zone Databases - Brocade Communications Systems 1606 Administrator's Manual

15
SAN management with Admin Domains
TABLE 75
Fabric OS feature
FC-FC Routing Service
FDMI
FICON
iSCSI
Management
applications
Port-Swapping and PID
formats
RSCN
Virtual Fabrics

Admin Domains, zones, and zone databases

If you are working with zones, you should be aware of how they impact Admin Domains. Each AD
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).
360
Admin Domain interaction with Fabric OS features (Continued)
Admin Domain interaction
You can create LSAN zones as a physical fabric administrator or as an individual AD
administrator. The LSAN zone can be part of the root zone database or the AD zone
database.
FCR collects the LSAN zones from all ADs. If both edge fabrics have matching LSAN
zones and both devices are online, FCR triggers a device import.
LSAN zone enforcement in the local fabric occurs only if the AD member list contains
both of the devices (local and imported device) specified in the LSAN zone.
To support legacy applications, WWNs are reported based on the AD context using
NAA=5. As a result, you cannot use the NAA=5 field alone in the WWN to detect an FC
router.
FDMI operations are allowed only in AD0 and AD255.
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.
Device Connection Control (DCC) and Switch Connection Control (SCC) policies are
supported only in AD0 and AD255, because 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, 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,index format. Based on the PID
format, a domain,index member indicates a slot and port in the switch. The
domain,index member is effectively a member of that AD.
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,index members.
For detailed information about configuring the PID format, see
Advanced Configuration
Admin Domains do not introduce any RSCN changes to devices or hosts.
Virtual Fabrics and Admin Domains are mutually exclusive and are not supported at the
same time on a switch. To use Admin Domains, you must first disable Virtual Fabrics; to
use Virtual Fabrics, you must first delete all Admin Domains.
If you connect a switch with Admin Domains to a Virtual Fabric-enabled switch, the link is
segmented with the reason "VF AD conflict."
Tasks".
Chapter 3, "Performing
Fabric OS Administrator's Guide
53-1001763-01