HP StorageWorks Fabric OS 6.x administrator guide (5697-7344, March 2008)

Fabric OS 6.x administrator guide 151
AD database exactly matches both the defined and effective configurations of the local AD database. If the
AD database merge fails, the E_Port is segmented with “AD conflict” error code.
Compatibility
Admin Domains can be implemented in fabrics with a mix of AD-aware switches and AD-unaware
switches. The following considerations apply:
• In mixed-fabric configurations, the legacy switches allow unfiltered access to the fabric and its devices;
hence, these legacy switches should be managed by the physical fabric administrator.
• You must zone all ports and devices from legacy switches in the AD0 root zone database.
• If you have legacy switches in your AD-activated fabric, you must ensure that all new AD resources have
enough interconnectivity so that they do not get isolated into subfabrics with a legacy subfabric
interposed in the middle, as shown in Figure 7.
Figure 7 Isolated subfabrics
Firmware upgrade and downgrade scenarios
You cannot perform a firmware downgrade to a Fabric OS version earlier than 5.2.0 if ADs are configured
in the fabric. Following are special scenarios for director class products only:
• If the primary and secondary CPs are running pre-Fabric OS 5.2.0 and are in HA-Sync, and if
firmwaredownload is used to upgrade one CP alone (using the firmwaredownload -s option),
then that CP will run in an AD-unaware mode (AD creation operations will fail and the local switch will
show up as an AD-unaware switch in the fabric).
• If the primary and secondary CPs are running Fabric OS 5.2.0 or later, and if ADs are configured, any
attempt to downgrade one or both CPs to pre-Fabric OS 5.2.0 versions will fail. The Admin Domain
configuration must be cleared before you can perform the downgrade (see ”Deleting all user-defined
Admin Domains” on page 158).
Managing Admin Domains
This section is for physical fabric administrators who are managing Admin Domains. You must be a
physical fabric administrator to perform the tasks in this section.
• ”Implementing Admin Domains” on page 153
• ”Creating an Admin Domain” on page 153
• ”Assigning a user to an Admin Domain” on page 154
• ”Activating and deactivating Admin Domains” on page 155
• ”Adding and removing Admin Domain members” on page 156
• ”Renaming an Admin Domain” on page 157
• ”Deleting an Admin Domain” on page 157
• ”Deleting all user-defined Admin Domains” on page 158
• ”Validating an Admin Domain member list” on page 158
AD-aware fabric AD-aware fabricAD-unaware fabric
These two subfabrics have
different AD databases but
the same root zone database.