Linux Storage - MDS running configuration of the zoning, VSAN 12
Linux Storage Solution · Config document · referenced from FC aliases, zones and zonesets
Z_FC1_b3_FC1_e2_V12 and the zoneset ZONESET_V12 next to the new ones. They are not active, and the notes do not delete them. The old zone in this listing has two members, while the active copy of it shown before the activation had three; see below.The zoning part of the running configuration of FCSwitch1 for VSAN 12 (DMZ), as the switch printed it after PROD-DMZ had been activated. The active zone database first, members resolved to port WWNs; then the full zone database with the aliases, zones and zonesets as typed, old and new together.
| Item | Value |
|---|---|
| Switch | FCSwitch1, Cisco MDS 9124e |
| Command | sh run zone vsan 12 (show running-config zone vsan 12), run from configuration mode as admin |
| Time in the listing | Fri Dec 6 04:31:15 2013, about an hour before the VSAN 11 listing |
| NX-OS | 5.2(8), the version line |
| Active zoneset | PROD-DMZ with HV03-Storage1, HV04-Storage1 |
| Also defined | ZONESET_V12 with Z_FC1_b3_FC1_e2_V12, no longer active |
| How it got there | FC alias and zoning commands |
The listing
The command, at the configuration prompt of FCSwitch1.
$ sh run zone vsan 12
The listing as printed. Lines beginning with ! that are not !Command:, !Time: or the two section markers are my comments and were not in the output.
!Command: show running-config zone vsan 12 !Time: Fri Dec 6 04:31:15 2013 version 5.2(8) !Active Zone Database Section for vsan 12 ! What is enforced now: the zones of PROD-DMZ with every alias ! resolved to its port WWN. zone name HV03-Storage1 vsan 12 member pwwn 50:01:43:80:12:34:57:90 member pwwn 21:11:00:02:ac:00:ab:cd zone name HV04-Storage1 vsan 12 member pwwn 50:01:43:80:12:34:57:92 member pwwn 21:11:00:02:ac:00:ab:cd zoneset name PROD-DMZ vsan 12 member HV03-Storage1 member HV04-Storage1 zoneset activate name PROD-DMZ vsan 12 do clear zone database vsan 12 !Full Zone Database Section for vsan 12 ! Everything defined in this VSAN, active or not: the aliases first. fcalias name HV03 vsan 12 member pwwn 50:01:43:80:12:34:57:90 fcalias name HV04 vsan 12 member pwwn 50:01:43:80:12:34:57:92 fcalias name Storage1-C0P1 vsan 12 member pwwn 21:11:00:02:ac:00:ab:cd ! The old interface-based zone, members by switch WWN and port. zone name Z_FC1_b3_FC1_e2_V12 vsan 12 member interface bay3 swwn 20:00:54:7f:ee:ab:cd:18 member interface ext2 swwn 20:00:54:7f:ee:ab:cd:18 ! The new zones, members by alias. zone name HV03-Storage1 vsan 12 member fcalias HV03 member fcalias Storage1-C0P1 zone name HV04-Storage1 vsan 12 member fcalias HV04 member fcalias Storage1-C0P1 ! The old zoneset, no longer active, and the new one. zoneset name ZONESET_V12 vsan 12 member Z_FC1_b3_FC1_e2_V12 zoneset name PROD-DMZ vsan 12 member HV03-Storage1 member HV04-Storage1
Reading the listing
| Part | What it shows |
|---|---|
!Active Zone Database Section | the zoneset the fabric enforces, PROD-DMZ; its zones list member pwwn lines because the switch resolved the aliases at activation |
zoneset activate name PROD-DMZ vsan 12 | the line that would re-activate it if the configuration were replayed |
do clear zone database vsan 12 | a line the switch prints between the two sections; do runs an exec command from configuration mode and clear zone database empties the full zone database of a VSAN. The notes do not say why it is there and the database below it is not empty; as I understand it NX-OS writes it so that a replay rebuilds the full database from scratch, which the notes do not confirm |
!Full Zone Database Section | every alias, zone and zoneset defined in VSAN 12, whether active or not |
member interface bay3 swwn 20:00:54:7f:ee:ab:cd:18 | the old way: a member is whatever logs in on port bay3 of the switch with WWN 20:00:54:7f:ee:ab:cd:18 |
member fcalias | the new way: a member is whatever presents the port WWN behind the alias, on any port |
One thing in this listing does not match the show zoneset active vsan 12 taken before the activation. There the active zone Z_FC1_b3_FC1_e2_V12 had three members, bay3, bay4 and ext2, and so put both DMZ servers and the storage port into one zone. Here the full-database copy of the same zone has two members, bay3 and ext2, and no zone for bay4 exists in the old set. The notes do not comment on it. The active and the full zone database are separate copies, so this is possible if the full database was edited after the old zoneset had been activated and never re-activated; that is my inference, not something the notes say. The same listing for VSAN 11 is running configuration of the zoning, VSAN 11, where the active and full copies of the old zones agree.
Checked against Cisco MDS NX-OS 9.4(5a)
| As built | Today |
|---|---|
show running-config zone vsan N with !Active Zone Database Section, zoneset activate …, do clear zone database vsan N, !Full Zone Database Section | Unchanged; the 9.x fabric guide's own example of this output shows the same lines, do clear zone database included |
member interface bay3 swwn … | Interface members are still a valid zone member type; the blade names bayN and extN exist only on the blade variants |
member fcalias, member pwwn | Unchanged; Cisco's guide now says "Device aliases should be used to simplify the management of world wide names (WWNs) whenever possible", in enhanced mode, which I read as device aliases instead of FC aliases |
version 5.2(8) | The last release for the MDS 9124 family is 5.2(8i); the switch reached its last date of support on 31 January 2019 |
The guide confirms the shape of the listing and nothing about the two-member versus three-member difference described above, which is a property of this switch's history and not of the software.