Linux Storage - MDS running configuration of the zoning, VSAN 11
Linux Storage Solution · Config document · referenced from FC aliases, zones and zonesets
Z_FC1_b1_FC1_e1_V11, Z_FC1_b2_FC1_e1_V11, Z_FC1_b5_FC1_e1_V11 and the zoneset ZONESET_V11 next to the new ones. They are not active, and the notes do not delete them.The zoning part of the running configuration of FCSwitch1 for VSAN 11 (MGMT_DC), as the switch printed it after PROD-DC had been activated. It has two sections: the active zone database, where every member is resolved to a port WWN, and the full zone database, where the aliases, zones and zonesets are kept as they were typed, old and new together.
| Item | Value |
|---|---|
| Switch | FCSwitch1, Cisco MDS 9124e |
| Command | sh run zone vsan 11 (show running-config zone vsan 11), run from configuration mode as admin |
| Time in the listing | Fri Dec 6 05:28:58 2013 |
| NX-OS | 5.2(8), the version line |
| Active zoneset | PROD-DC with HV01-Storage1, HV02-Storage1, MGMT01-Storage1 |
| Also defined | ZONESET_V11 with the three Z_FC1_…_V11 zones, 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 11
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 11 !Time: Fri Dec 6 05:28:58 2013 version 5.2(8) !Active Zone Database Section for vsan 11 ! What is enforced now: the zones of PROD-DC with every alias ! resolved to its port WWN. zone name HV01-Storage1 vsan 11 member pwwn 50:01:43:80:12:34:56:c0 member pwwn 21:12:00:02:ac:00:ab:cd zone name HV02-Storage1 vsan 11 member pwwn 50:01:43:80:12:34:56:d4 member pwwn 21:12:00:02:ac:00:ab:cd zone name MGMT01-Storage1 vsan 11 member pwwn 50:01:43:80:12:34:40:2c member pwwn 21:12:00:02:ac:00:ab:cd zoneset name PROD-DC vsan 11 member HV01-Storage1 member HV02-Storage1 member MGMT01-Storage1 zoneset activate name PROD-DC vsan 11 do clear zone database vsan 11 !Full Zone Database Section for vsan 11 ! Everything defined in this VSAN, active or not: the aliases first. fcalias name HV01 vsan 11 member pwwn 50:01:43:80:12:34:56:c0 fcalias name HV02 vsan 11 member pwwn 50:01:43:80:12:34:56:d4 fcalias name MGMT01 vsan 11 member pwwn 50:01:43:80:12:34:40:2c fcalias name Storage1-C0P0 vsan 11 member pwwn 21:12:00:02:ac:00:ab:cd ! The old interface-based zones, members by switch WWN and port. zone name Z_FC1_b1_FC1_e1_V11 vsan 11 member interface bay1 swwn 20:00:54:7f:ee:ab:cd:18 member interface ext1 swwn 20:00:54:7f:ee:ab:cd:18 zone name Z_FC1_b2_FC1_e1_V11 vsan 11 member interface bay2 swwn 20:00:54:7f:ee:ab:cd:18 member interface ext1 swwn 20:00:54:7f:ee:ab:cd:18 zone name Z_FC1_b5_FC1_e1_V11 vsan 11 member interface bay5 swwn 20:00:54:7f:ee:ab:cd:18 member interface ext1 swwn 20:00:54:7f:ee:ab:cd:18 ! The new zones, members by alias. zone name HV01-Storage1 vsan 11 member fcalias HV01 member fcalias Storage1-C0P0 zone name HV02-Storage1 vsan 11 member fcalias HV02 member fcalias Storage1-C0P0 zone name MGMT01-Storage1 vsan 11 member fcalias MGMT01 member fcalias Storage1-C0P0 ! The old zoneset, no longer active, and the new one. zoneset name ZONESET_V11 vsan 11 member Z_FC1_b1_FC1_e1_V11 member Z_FC1_b2_FC1_e1_V11 member Z_FC1_b5_FC1_e1_V11 zoneset name PROD-DC vsan 11 member HV01-Storage1 member HV02-Storage1 member MGMT01-Storage1
Reading the listing
| Part | What it shows |
|---|---|
!Active Zone Database Section | the zoneset the fabric enforces, PROD-DC; its zones list member pwwn lines because the switch resolved the aliases at activation |
zoneset activate name PROD-DC vsan 11 | the line that would re-activate it if the configuration were replayed |
do clear zone database vsan 11 | a line the switch prints in this section; do runs an exec command from configuration mode, and clear zone database is the command that empties the full zone database of a VSAN. The notes do not say why it is there, and the full zone database below it is not empty. As I understand it this is how NX-OS writes the boundary between the two sections so that a replay of the file builds the full database cleanly; the notes do not confirm that |
!Full Zone Database Section | every alias, zone and zoneset defined in VSAN 11, whether active or not |
member interface bayN swwn 20:00:54:7f:ee:ab:cd:18 | the old way: a member is whatever logs in on port bayN 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 |
The same listing for VSAN 12 is running configuration of the zoning, VSAN 12. The old zoneset is harmless while it is not active, but a reader who comes to this switch later will find two zonesets per VSAN and will have to look at show zoneset active to know which one counts.
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 bay1 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 but still does not say why do clear zone database is printed where it is, so my reading of that line above stays a reading.