Fabric OS 5.2.x administrator guide 363
4.
Enter the
cfgShow
command to verify the renamed zone object is present.
5.
If you want the change preserved when the switch reboots, save it to nonvolatile (also known as “flash”)
memory by entering the
cfgSave
command.
6.
For the change to become effective, enable the appropriate zone configuration using the
cfgEnable
command.
For more details about the
zoneObjectCopy
,
cfgShow
,
cfgEnable
, and
cfgSave
commands, refer
to the
Fabric OS Command Reference Manual
.
Managing Zoning configurations in a fabric
To modify an existing zone configuration, you can add, delete, or remove individual elements to create the
desired configuration. After the changes have been made, save the configuration to ensure the
configuration is permanently saved in the switch and that the configuration is replicated throughout
the fabric.
The switch configuration file can also be uploaded to the host for archiving and it can be downloaded from
the host to a switch in the fabric. Refer to ”
Backing up a configuration
” on page 147, ”
Restoring a
configuration
” on page 149, or the
configUpload
and
configDownload
commands in the
Fabric OS
Command Reference Manual
.
Adding a new switch or fabric
When a new switch is added to the fabric, it automatically takes on the zone configuration information
from the fabric. Use the
cfgActvShow
command to verify that the Zoning information is the same on each
switch in the fabric
If you are adding a switch that is already configured for Zoning, use the
cfgClear
and
cfgSave
commands (or use
cfgClear
and
cfgDisable
if there is an effective configuration) before connecting it
to the zoned fabric.
Adding a new fabric that has no zone configuration information to an existing fabric is very similar to
adding a new switch. All switches in the new fabric inherit the Zoning configuration data. If a zone
configuration is in effect, then the same configuration becomes the enabled configuration. The
cfgActvShow
command will display the same information on all switches in the newly formed fabric.
Before the new fabric can merge successfully, it must pass the following criteria:
•
Before merging zones
To facilitate merging, check the following before merging switches or fabrics.
• Zoning licenses—All switches must have a Zoning license enabled.
• Native operating mode—All switches must be in the native operating mode.
• Secure Fabric OS—If one switch has Secure Fabric OS enabled, all switches in the fabric must have
Secure Fabric OS. Refer to the
Secure Fabric OS Administrator’s Guide
for more information.
•
Merging and segmentation
The fabric is checked for segmentation during power-up or when a switch is disabled or enabled, or
when a new switch is added.
The database is the zone configuration database. This is the data displayed as the “defined
configuration” in the
cfgShow
command. It is stored in nonvolatile memory by the
cfgSave
command. This database is a replicated database, which means that all switches in the fabric will have
copy of this database. When a change is made to the defined configuration, the switch where the
changes were made must close its transaction for the change to get propagated throughout the fabric.
Summary of Contents for AE370A - Brocade 4Gb SAN Switch 4/12
Page 18: ...18 ...
Page 82: ...82 Managing user accounts ...
Page 102: ...102 Configuring standard security features ...
Page 126: ...126 Maintaining configurations ...
Page 198: ...198 Routing traffic ...
Page 238: ...238 Using the FC FC routing service ...
Page 260: ...260 Administering FICON fabrics ...
Page 280: ...280 Working with diagnostic features ...
Page 332: ...332 Administering Extended Fabrics ...
Page 414: ...398 Configuring the PID format ...
Page 420: ...404 Configuring interoperability mode ...
Page 426: ...410 Understanding legacy password behaviour ...
Page 442: ...426 ...
Page 444: ......
Page 447: ......