HP Fabric OS v7.0.1, Administrator'S Manual

Page: 400 / 584

362 Fabric OS Administrator’s Guide
53-1002446-01
SAN management with Admin Domains
17
Admin Domains, zones, and zone databases
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.
AD-level zone information is merged with the root zone configuration and enforced.
•
AD zone databases
Each AD (AD1 through AD254) has its own zone database, with the defined and effective zone
configurations and all related zone objects (zones, zone aliases, and zone members). Each AD
has its own zone transaction buffer. Within an Admin Domain, you can configure zoning only
with the devices that are present in that Admin Domain.
FICON Admin Domains support FICON. However, you must perform additional steps because
FICON management 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 iSCSI operations are supported only in AD0.
LSAN zoning Refer to “Admin Domains and LSAN zones” on page 363 for details.
Management
applications 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.
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.
Port swapping and PID
formats 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, refer to Chapter 3,
“Performing Advanced Configuration Tasks” .
RSCN Admin Domains do not introduce any RSCN changes to devices or hosts.
Virtual Fabrics 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 Fabrics-enabled switch, the link
is segmented with the reason “VF AD conflict.”
Zoning Refer to “Admin Domains, zones, and zone databases” on page 362 for details.
TABLE 63 Admin Domain interaction with Fabric OS features (Continued)
Fabric OS feature Admin Domain interaction