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

If a fabric segments, the newly elected principal RBridge determines whether transaction data are
retained. If a segment retains the original principal, it also retains ongoing transaction data. If a
segment elects a new principal, the transaction is aborted.
The zone startup configuration is always equal to the running configuration. The running configuration
will always be overwritten by the information from the master copy of the zoning database in
nonvolatile memory at startup, so you always start up with the previous running configuration. It is not
necessary to copy the running configuration to the startup configuration explicitly.
You can save a snapshot of the current running configuration using the copy running-config file
command. You can add configuration entries from a saved configuration using the copy file running-
config command. When saving the snapshot you must ensure that the saved running configuration
contains no zoning transaction data, otherwise failures will occur when you attempt to restore
configuration entries from the saved file. Any transaction data would cause such a failure, including
empty configuration definitions or empty zones.
Notes
• When you re-enable the enabled-configuration (using the zoning enabled-configuration
command) on the principal switch in the cluster, the system propagates the enabled-configuration
across the cluster. There is a slight risk of doing this in that the defined-configuration may contain
configuration edits that you may not want to enable yet. This feature prevents switches in the cluster
from having mismatched enabled-configurations.
• When restoring the running configuration, Brocade recommends copying the file to the running
configuration in the absence of any other command line input.
• When you restore a configuration using the copy command, the contents of the file are added to
the defined configuration; they do not replace the defined configuration. The result is cumulative, is
as if the input came from the command line.
Understanding and managing default zoning access modes
The default zoning mode controls device access if zoning is not implemented or if there is no enabled
zone configuration. Default zoning has two access modes:
• All Access — All devices within the fabric can communicate with all other devices.
• No Access — Devices in the fabric cannot access any other device in the fabric.
The default setting is All Access. Changing the default access mode requires committing the ongoing
transaction for the change to take effect.
The default zoning mode takes effect when you disable the effective zone configuration. If your default
zone has a large number of devices, to prevent RSCN storms from overloading those devices, you
should set the default zoning mode to No Access before attempting to disable the zone configuration.
If your default zone includes more than 300 devices, the zoning software prevents you from disabling
the zoning configuration if the default zoning mode is All Access.
Setting the default zoning mode
1. In privileged EXEC mode, enter the configure terminal command to enter the global configuration
mode.
2. Enter one of the following commands, depending on the default access mode you want to
configure:
• To set the default access mode to All Access, enter zoning enabled-configuration default-
zone-access allaccess.
• To set the default access mode to No Access, enter zoning enabled-configuration default-
zone-access noaccess.
Understanding and managing default zoning access modes
176 Network OS Administrator’s Guide
53-1003225-04