HP A7533A HP StorageWorks Fabric OS 6.1.1 administrator guide (5697-0235, Dece - Page 161

Compatibility Admin Domains can be implemented in fabrics with a mix of AD-capable switches and non-AD-capable switches. The following considerations apply: • In mixed-fabric configurations, the legacy switches allow unfiltered access to the fabric and its devices; therefore, 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 10. AD-capable fabric non-AD-capable fabric AD-capable fabric Figure 10 Isolated subfabrics Firmware upgrade considerations These two subfabrics have different AD databases but the same root zone database. The following scenario is for enterprise-class products only: • If the primary and secondary CPs are running pre-Fabric OS 5.2.0 and HA state is synchronized, and if firmwareDownload is used to upgrade one CP alone (using the firmwareDownload -s option), that CP will run in a non-AD-capable mode (AD creation operations will fail and the local switch will show up as a non-AD-capable switch in the fabric). Admin Domain management for physical fabric administrators 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. • "Setting the default zone mode" on page 162 • "Creating an Admin Domain" on page 162 • "Assigning a user to an Admin Domain" on page 163 • "Activating and deactivating Admin Domains" on page 165 • "Adding and removing Admin Domain members" on page 166 • "Renaming an Admin Domain" on page 167 • "Deleting an Admin Domain" on page 167 • "Deleting all user-defined Admin Domains" on page 168 • "Validating an Admin Domain member list" on page 168 Understanding the AD transaction model Use the ad command to perform most of the tasks in this section. This command follows a batched-transaction model, which means that changes to the Admin Domain configuration occur in the transaction buffer. An Admin Domain configuration can exist in several places: • Effective configuration-The Admin Domain configuration that is currently in effect. • Defined configuration-The Admin Domain configuration that is saved in flash memory. There might be differences between the effective configuration and the defined configuration. • Transaction buffer-The Admin Domain configuration that is in the current transaction buffer and has not yet been saved or canceled. Fabric OS 6.1.1 administrator guide 161