Brocade Fabric OS Administrators Guide (Supporting Fabric OS v7.3.0) - Manual (Page 317)

1,0; loop1
zone: White_zone
1,3; 1,4
alias: array1 21:00:00:20:37:0c:76:8c; 21:00:00:20:37:0c:71:02
alias: array2 21:00:00:20:37:0c:76:22; 21:00:00:20:37:0c:76:28
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.
If the -i option is specified, all zone members for a given pattern are listed without case distinction
Example validating the zone members beginning with gre, regardless of the case
switch:admin> zone --validate -i gre*
Defined configuration:
zone: GREEN 44, 4; 21:00:00:20:37:0c:71:02; 8,9
zone: green 2,2*; 2,3*; 21:00:00:20:37:0c:76:8c*
Effective configuration:
zone: green 2,2*
2,3*
21:00:00:20:37:0c:76:8c*
------------------------------------
~ - Invalid configuration
* - Member does not exist
# - Invalid usage of broadcast zone
Inconsistencies between the defined and effective configurations
If you edit zone objects in the defined configuration that also exist in the effective configuration and then
issue the cfgSave command, a warning message stating that a mismatch is observed between the
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.
Inconsistencies between the defined and effective configurations
Fabric OS Administrators Guide 317
53-1003130-01