Filter
Top Products
324 Fabric OS Administrator’s Guide
53-1002745-02
Zone creation and maintenance
11
alias: loop1 21:00:00:20:37:0c:76:85; 21:00:00:20:37:0c:71:df
3. Enter the zone --validate command to list all zone members that are not part of the current
zone enforcement table. Note that zone configuration names are case-sensitive; blank spaces
are ignored.
switch:admin> zone --validate "White_zone"
4. Enter the following command to validate all zones in the zone database in the defined
configuration.
switch:admin> zone --validate -m 1
Defined configuration:
cfg: cfg1 zone1
cfg: cfg2 zone1; zone2
zone: zone1 1,1; ali1
zone: zone2 1,1; ali2
alias: ali1 10:00:00:05:1e:35:81:7f*; 10:00:00:05:1e:35:81:7d*
alias: ali2 10:00:00:05:1e:35:81:09*; 10:00:00:05:1e:35:81:88*
------------------------------------
~ - Invalid configuration
* - Member does not exist
The mode flag -m can be used to specify the zone database location. Supported mode flag
values are:
• 0 - zone database from the current transaction buffer
• 1 - zone database stored from the persistent storage
• 2 - currently effective zone database.
If no mode options are given, the validated output of all three buffers is shown.
If the -f option is specified, all the zone members that are not enforceable would be expunged
in the transaction buffer. This pruning operation always happens on the transaction and
defined buffers. You cannot specify a mode option or specify a zone object as an argument
with the -f option. This mode flag should be used after the zone has been validated.
Inconsistencies between the Defined and Effective Zone Databases
If you edit zone objects in the Defined Zone configuration that also exist in the Effective Zone
Configuration and then issue the cfgSave command, a warning message stating that mismatch is
observed between defined and effective configurations is posted, and you are asked to confirm
that you want cfgSave to continue. If you enter “y”, then the updated configuration will be saved;
if you enter “n”, then the updated configuration will be discarded.
Example warning message
switch: admin> cfgsave
WARNING!!!
The changes you are attempting to save will render the
Effective configuration and the Defined configuration inconsistent.
The inconsistency will result in different Effective Zoning
configurations for switches in the fabric if a zone merge or
HA failover happens. To avoid inconsistency it is recommended to
commit the configurations using the 'cfgenable' command.
Do you want to proceed with saving the Defined
zoning configuration only? (yes, y, no, n): [no] yes