HP StorageWorks 8/80 HP StorageWorks Fabric OS 6.2 administrator guide (5697-0 - Page 201

• 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 25. AD-capable fabric non-AD-capable fabric AD-capable fabric Figure 25 Isolated subfabrics These two subfabrics have different AD databases but the same root zone database. Firmware upgrade considerations 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 you use firmwareDownload 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. You 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: • In the effective configuration: The Admin Domain configuration that is currently in effect. • In the defined configuration: The Admin Domain configuration that is saved in flash memory. There might be differences between the effective configuration and the defined configuration. • In the transaction buffer: The Admin Domain configuration that is in the current transaction buffer and has not yet been saved or canceled. How you end the transaction determines the disposition of the Admin Domain configuration in the transaction buffer. The following commands end the Admin Domain transaction: ad --save Saves the changes in the transaction buffer to the defined configuration in persistent storage and propagates the defined configuration to all switches in the fabric. Note that for delete and clear operations, if one or more of the deleted Admin Domains are in the effective configuration, you cannot use --save, but must use --apply instead. ad --apply Saves the changes to the defined configuration in persistent storage and enforces the defined configuration on all switches in the fabric, replacing the effective configuration. ad --transabort Aborts the transaction and clears the transaction buffer. The effective and defined configurations remain unchanged. You can enter the ad --transshow command at any time to display the ID of the current Admin Domain transaction. Fabric OS 6.2 administrator guide 199