Administrators Guide (Supporting Fabric OS v7.3.0) User Manual

FIGURE 64 Filtered fabric views when using Admin Domains
Admin Domain features
Admin Domains allow you to do the following:
• Define the scope of an Admin Domain to encompass ports and devices within a switch or a fabric.
• Share resources across multiple Admin Domains. For example, you can share array ports and tape
drives between multiple departments. In Figure 63 on page 456, one of the storage devices is shared
between AD1 and AD2.
• Have a separate zone database for each Admin Domain. Refer to Admin Domains, zones, and zone
databases on page 468 for more information.
• Move devices from one Admin Domain to another without traffic disruption, cable reconnects, or
discontinuity in zone enforcement.
• Provide strong fault and event isolation between Admin Domains.
• Have visibility of all physical fabric resources. All switches, E_Ports, and FRUs (including blade
information) are visible.
• Continue to run existing third-party management applications. Prior and existing versions of third-
party management applications continue to work with admin IDs and user IDs.
Requirements for Admin Domains
Implementing Admin Domains in a fabric has the following requirements:
• The default zone mode setting must be set to No Access before you create Admin Domains (refer to
Setting the default zoning mode on page 319 for instructions).
• Virtual Fabrics must be disabled before you create Admin Domains (refer to Disabling Virtual Fabrics
mode on page 285 for instructions).
• Gigabit Ethernet (GbE) ports cannot be members of an Admin Domain.
• Traffic Isolation Zoning is supported within Admin Domains, with some restrictions, as described in
Admin Domain considerations for Traffic Isolation Zoning on page 360.
• If the fabric includes LSAN zones:
Admin Domain features
Fabric OS Administrators Guide 457
53-1003130-01