Brocade Network OS Administrator’s Guide v4.1.1 - Manual (Page 175)

| cfg-disable} command or the zoning enabled-configuration cfg-name cfg_name command to
commit the operation before re-attempting a firmware download.
2. An open zone transaction in progress. You must either commit or abort the current open transaction
before re-attempting a firmware download. Use the zoning enabled-configuration cfg-action {cfg-
save | cfg-disable} command or the zoning enabled-configuration cfg-name cfg_name command
to commit the current open transaction. Alternately, use the zoning enabled-configuration cfg-
action cfg-transaction-abort command to abort the open transaction.
You cannot downgrade any switch in a Brocade VCS Fabric to Network OS 2.0 or earlier if any zone
definition exists in the defined configuration. Any attempt to do so will fail while attempting to
download the earlier firmware. For the downgrade to succeed, you must clear the defined
configuration, disable any active configuration, set the default zoning mode to All Access, and then
try again to download the firmware.
When you upgrade from Network OS 2.1.0 to versions 2.1.1 or later, the zone database is cleared.
CAUTION
Clearing the defined configuration clears the zoning database for the entire fabric. If you want
to downgrade just one switch without affecting the rest of the fabric, disconnect the switch
from the fabric before deleting the defined configuration.
Configuring and managing zones
Zone configuration management overview
You can perform zoning operations on any RBridge in the VCS Fabric, but they are always executed on
the principal RBridge. In Logical Chassis mode, any edits made to the zoning database are allowed only
from the principal RBridge, and you can issue show commands from non-principal switches in this
mode. In Fabric Cluster mode, you can make edits from any RBridge.
Automatic distribution of the zoning configuration ensures that the effects of these operations are
shared and instantly visible on all switches in the VCS Fabric. However, these operations are not
permanent until a transaction commit operation saves them to nonvolatile memory, which holds the
master copy of the zoning database. In fabric cluster mode, any user can commit the transaction on any
switch, and the commit operation saves the operations performed by all users. Once the zoning
configuration is saved in permanent memory, it persists across reboot operations.
A transaction commit occurs when you or another user initiates any of the following zoning operations:
• Saving the database to nonvolatile memory with the zoning enabled-configuration cfg-action cfg-
save command.
• Enable a specific zone configuration with the zoning enabled-configuration cfg-name command.
• Disabling the currently enabled zone configuration with the no zoning enabled-configuration cfg-
name command.
Executing the zoning enabled-configuration cfg-action cfg-transaction-abort command cancels the
currently open transaction.
If the principal RBridge reboots or goes down, Network OS selects a new principal and any pending
zoning transaction is rolled back to the last committed transaction, which is the effective zoning
configuration saved in nonvolatile memory. Any changes made to the effective configuration prior to an
abort operation must be re-entered.
If an RBridge other than the principal reboots or goes down, the ongoing transaction is not backed out.
Any zoning operations initiated by the RBridge are still part of the global transaction maintained on the
principal RBridge.
Configuring and managing zones
Network OS Administrator’s Guide 175
53-1003225-04