Lab 9: Configuring Zones Complete this lab activity to practice what you learned in the related lesson.
Activity Objective In this activity, you will configure zoning and verify end-to-end connectivity across the zones. After completing this activity, you will be able to meet these objectives:
Configure device aliases for use in zone configurations
Enable Enhanced Zoning
Create zones and zonesets for devices in the primary and secondary VSANs
Configure the zoneset distribution feature and observe the results
Merge zones in a variety of configurations and observe the results
Import, export, back up, and recover a zone set
Visual Objective The figure illustrates what you will accomplish in this activity.
© 2007 Cisco Systems, Inc. All rights reserved. ICSNS v3.0—6
fc1/5 fc1/10 fc1/5 fc1/10
JBOD
fc1/6 fc1/6
MDS-1 MDS-2
HOST1 HOST2
HBAHBA
FC
HBAHBA
FC
Configuring Zones
VSAN 10
VSAN 10
VSAN 10
VSAN 20
VSAN 20
VSAN 20
VSAN 10 VSAN 20
Zone HOST1Primary
Zone HOST2Secondary
VSAN 10
DISK1pwwn1
DISK2pwwn2
Zone HOST1Secondary
Zone HOST2Primary
VSAN 20
© 2007 Cisco Systems, Inc. Lab Guide 93
94 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
Required ResourcesThese are the resources and equipment required to complete this activity:
2 MDS 9000 Series Fibre Channel switches
2 Windows 2000 management servers with Fabric Manager and Device Manager installed and each with a dual-port Qlogic Fibre Channel HBA
1 JBOD with at least three disks
© 2007 Cisco Systems, Inc. Lab Guide 95
Command List The table describes the commands used in this activity.
Command Description
show fcns database Displays the name server database for a specified VSAN or for all VSANs.
show flogi database Lists all the FLOGI sessions through all interfaces across all VSANs.
device-alias database Configures and activates the device alias database.
device-alias name name pwwn pwwn Configures device names in the device alias database.
device-alias commit Applies the pending configuration pertaining to the Distributed Device Alias Services (device alias) Cisco Fabric Services (CFS) distribution session.
show device-alias database Displays the entire device name database.
zone name name vsan X Creates a zone called name in VSAN X and enters configuration mode for that zone.
zoneset name name vsan X Creates a zoneset called name in VSAN X and enters configuration mode for that zoneset.
member zonename Adds zone zonename to the current zoneset.
zoneset activate name name vsan X Activates the zoneset called name in VSAN X.
zoneset export vsan X
Exports the zone set database to the adjacent switch on the specified interface. The active zone set in this switch becomes the activated zone set of the merged SAN. Makes the two switches’ zoning databases consistent.
debug zone database events Enables debugging of zone database events.
show zoneset Displays all the zonesets that are configured on the switch.
show zone [ vsan X ] Displays all the zones that are configured on the switch or in the specified VSAN.
show zone status [ vsan X ]
Displays the status of the zones that are configured on the switch or in the VSAN. Shows the default zone policy, the zonesets and zones in the full zone database, and which zoneset (if any) is the active zone.
show zoneset active [ vsan X ]
Displays the active zoneset, showing its name and the name of each active zone with all the members of all the zones listed.
show fcns database [ vsan X ]
Displays a list of all the ports that are logged in to the FC name server.
show interface fcx/y Displays the status of and statistics for interface fcx/y.
debug zone [ database | merge ]
Launches debugging for a specific zoning activity, such as database updates or zone merges.
show file Displays the contents of a file.
copy run start Saves the running configuration to startup config.
96 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
Task 1: Complete the Initial Switch Configuration In this task, you will use the CLI to complete the initial switch configuration process.
Note If you are working in teams within a pod, Team1 will configure MDS1 and Team2 will configure MDS2. If you are working alone, you will need to configure both switches.
Activity Procedure
Note If you are doing the labs in sequence, you can skip ahead to Task 2. Otherwise, perform this task on both MDS-1 and MDS-2 switches in your pod.
Complete the following steps on both MDS switches.
Step 1 Authenticate to your assigned switch (MDS-1 or MDS-2).
Switch login: admin
Password: 1234qwer
Step 2 Clear the current startup configuration.
# write erase
The following message is displayed:
Warning: This command will erase the startup-configuration.
Do you wish to proceed anyway? [y/n] [N]
Type y to proceed.
Step 3 Reboot the switch.
# reload
This command will reboot the system. (y/n)?
Type y to proceed.
Step 4 After the switch reboots, it will automatically launch the setup process. Answer the questions according to the following example, replacing your pod number where appropriate.
---- System Admin Account Setup ----
Enter the password for "admin": 1234qwer
Confirm the password for "admin":1234qwer
--- Basic System Configuration Dialog ---
This setup utility will guide you through the basic configuration of the system. Setup configures only enough connectivity for management of the system.
Please register Cisco MDS 9000 Family devices promptly with your supplier. Failure to register may affect response times for initial service calls. MDS devices must be registered to receive entitled support services.
© 2007 Cisco Systems, Inc. Lab Guide 97
Press Enter at anytime to skip a dialog. Use ctrl-c at anytime to skip the remaining dialogs.
Would you like to enter the basic configuration dialog (yes/no): y
Create another login account (yes/no) [n]: <Enter>
Configure read-only SNMP community string (yes/no) [n]: <Enter>
Configure read-write SNMP community string (yes/no) [n]: <Enter>
Enter the switch name: Pxx-MDS-x (where xx is your pod number and x is the switch number; for example: P01-MDS-1)
Continue with Out-of-band (mgmt0) management configuration? (yes/no) [y]: <Enter>
Mgmt0 IPv4 address : <10.0.X.N> (where X is the pod # and N is 5 for MDS-1 and 3 for MDS-2)
Mgmt0 IPv4 netmask : <255.255.255.0>
Configure the default gateway? (yes/no) [y]: <Enter>
IPv4 address of the default gateway : <10.0.X.254> (where X is the pod #)
Configure advanced IP options? (yes/no) [n]: <Enter>
Enable the telnet service? (yes/no) [y]: <Enter>
Enable the ssh service? (yes/no) [n]: <Enter>
Configure the ntp server? (yes/no) [n]: <Yes>
NTP server IP address: <10.0.0.253>
Configure default switchport interface state (shut/noshut) [shut]: <Enter>
Configure default switchport trunk mode (on/off/auto) [on]: <Enter>
Configure default zone policy (permit/deny) [deny]: <Enter>
Enable full zoneset distribution (yes/no) [n]: <Enter>
Step 5 A summary of the configuration will be displayed:
The following configuration will be applied:
switchname P29-MDS-1
interface mgmt0
ip address 10.0.29.5 255.255.255.0
no shutdown
ip default-gateway 10.0.29.254
telnet server enable
no ssh server enable
ntp server 10.0.0.253
system default switchport shutdown
system default switchport trunk mode on
no system default zone default-zone permit
no system default zone distribute full
98 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
Note The displayed running-config is from pod P29-MDS-1. Port numbers, IP addresses and names may differ from your pod.
Step 6 Press Enter twice to save the configuration.
Would you like to edit the configuration? (yes/no) [n]: <Enter>
Use this configuration and save it? (yes/no) [y]: <Enter>
Step 7 Log in to the console using the username admin and the password 1234qwer.
Step 8 Create VSANs 10 and 20 and assign interfaces on MDS-1.
MDS-1# config
MDS-1(config)# vsan database
MDS-1(config-vsan-db)# vsan 10
MDS-1(config-vsan-db)# vsan 20
MDS-1(config-vsan-db)# vsan 10 interface fc1/5, fc1/10, fc1/6
MDS-1(config-vsan-db)# end
Step 9 Create VSANs 10 and 20 and assign interfaces on MDS-2.
MDS-2# config
MDS-2 (config)# vsan database
MDS-2 (config-vsan-db)# vsan 10
MDS-2 (config-vsan-db)# vsan 20
MDS-2 (config-vsan-db)# vsan 20 interface fc1/5, fc1/10, fc1/6
MDS-2 (config-vsan-db)# end
© 2007 Cisco Systems, Inc. Lab Guide 99
Activity Verification Complete the following steps on both switches in your pod to verify your results.
Step 1 Log in to the console using the username admin and the password 1234qwer.
Step 2 Ping the TFTP server.
# ping 10.0.0.198
PING 10.0.0.198 (10.0.0.198) 56(84) bytes of data.
64 bytes from 10.0.0.198: icmp_seq=1 ttl=127 time=0.466 ms
64 bytes from 10.0.0.198: icmp_seq=2 ttl=127 time=0.407 ms
64 bytes from 10.0.0.198: icmp_seq=3 ttl=127 time=0.383 ms
64 bytes from 10.0.0.198: icmp_seq=4 ttl=127 time=0.369 ms
64 bytes from 10.0.0.198: icmp_seq=5 ttl=127 time=0.440 ms
Step 3 Press Ctrl-C to stop the ping command.
--- 10.0.0.198 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 3998ms
rtt min/avg/max/mdev = 0.369/0.413/0.466/0.035 ms
Step 4 Verify VSAN membership on both switches.
MDS-1# show vsan membership
vsan 1 interfaces:
fc1/1 fc1/2 fc1/3 fc1/4 fc1/7 fc1/8 fc1/9 fc1/11
fc1/12 fc1/13 fc1/14 fc1/15 fc1/16
vsan 10 interfaces:
fc1/5 fc1/10 fc1/6
vsan 20 interfaces:
MDS-2# show vsan membership
vsan 1 interfaces:
fc1/1 fc1/2 fc1/3 fc1/4 fc1/7 fc1/8 fc1/9 fc1/11
fc1/12 fc1/13 fc1/14 fc1/15 fc1/16
vsan 10 interfaces:
vsan 20 interfaces:
fc1/5 fc1/10 fc1/6
Task 2: Create Device Aliases In this task, you will create device aliases for devices in the primary and secondary VSANs for use in zone and zoneset creation.
Activity Procedure Complete the following steps on both switches.
Step 1 Access a Microsoft Windows 2000 server in your pod by clicking one of the green MSTS links in the LabGear interface:
Team 1, managing MDS-1, will use Windows 2000 Server 1.
Team 2, managing MDS-2, will use Windows 2000 Server 2
Step 2 Log in as administrator with the password cisco.
Step 3 Open Fabric Manager and log in to your switch with the username admin and the password 1234qwer.
Step 4 In the Fabric Manager Physical Attributes pane, expand Switches > Interfaces and select FC Physical.
100 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
Step 5 Locate the Status Admin column in the interface configuration information pane and click on the fields to change the administrative status to up for interfaces fc1/5, fc1/10 and fc1/6.
Step 6 Click the Apply Changes button.
Step 7 Scroll to the bottom of the Physical Attributes pane and select End Devices.
Note If you do not see the End Devices placeholder, you might need to wait a moment for discovery to complete, then click All VSANs in the Logical Domains pane.
© 2007 Cisco Systems, Inc. Lab Guide 101
Step 8 Click the Switch Interface column in the information pane to sort the attached devices listed on the Summary tab.
Step 9 Enter device alias names for the two QLogic HBAs. Double-click the field in the Alias column in the information pane to enter the identified host names for your switch.
Port MDS-1 MDS-2
fc1/5 HOST1-P1 HOST1-P2
fc1/10 HOST2-P1 HOST2-P2
Step 10 Enter device alias names from top to bottom for the Seagate disks. Each disk is dual-ported.
If you are configuring the MDS-1, your alias names will be DISKn-P1.
If you are configuring the MDS-2, your alias names will be DISKn-P2.
Note Not all pods will have six disks. Create a device alias for each disk in the JBOD.
MDS-1 MDS-2
DISK1-P1 DISK 1-P2
DISK 2-P1 DISK 2-P2
DISK 3-P1 DISK 3-P2
DISK 4-P1 DISK 4-P2
DISK 5-P1 DISK 5-P2
DISK 6-P1 DISK 6-P2
Note Device alias names are case sensitive. Be sure to enter the letters as shown.
102 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
Step 11 Your display should look similar to the following example.
Step 12 Verify the alias names are entered correctly, and then click the Apply Changes button.
Step 13 Highlight all the rows in the table, and then click the Alias -> Enclosure button.
Step 14 The Enclosure Name will change to reflect the first token of the entered device alias name.
Step 15 Click the Apply Changes button.
Step 16 Click the up arrow to view the fabric pane.
Step 17 Click the Layout Map icon on the fabric pane toolbar.
© 2007 Cisco Systems, Inc. Lab Guide 103
Step 18 Right-click the circular JBOD loop icon and select Expand.
Step 19 Click the Layout Map icon again to view the attached devices and their aliases.
Note Do not proceed until the preceding steps have been completed on both switches.
Step 20 Scroll to the bottom of the Physical Attributes pane and select End Devices.
Step 21 Locate the Status Admin column in the interface configuration information pane and click on the fields to change the administrative status to up for interfaces fc1/7, fc1/8 and fc1/9.
Step 22 Click the Apply Changes button.
Note Do not proceed until the preceding steps have been completed on both switches.
Step 23 Scroll to the bottom of the Physical Attributes pane and select End Devices.
104 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
Step 24 Click the Rediscover Current Fabric button.
Step 25 Click the Refresh Values button until the Alias column is completely populated with the device alias entries from both switches.
Step 26 Highlight all of the rows and columns in the End Devices detail pane (click on the first row and press CTRL-SHIFT-END) and click the Alias > Enclosure button.
Step 27 Click the Apply Changes button.
© 2007 Cisco Systems, Inc. Lab Guide 105
Step 28 Click the up arrow to view the fabric pane.
Step 29 Click the Layout Map icon on the fabric pane toolbar.
Step 30 Right-click the circular JBOD loop icon and select Expand.
Step 31 Click the Layout Map icon to view the attached devices and their aliases.
106 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
Task 3: Create Zones and Zone Sets In this task, you will create zones and zonesets for devices in the primary and secondary VSANs.
Activity Procedure Complete the following steps in sequence on the specified switch.
The team working on MDS-1 should complete the Steps 1-15 for VSAN 10.
The team working on MDS-2 should skip to Step 16.
Step 1 In Fabric Manager, locate the VSAN 10 folder in the tree view. Right-click and select Edit Local Full Zone Database.
Step 2 Confirm that the Switch field contains P0X-MDS-1. Right-click Zones and select
Insert….
© 2007 Cisco Systems, Inc. Lab Guide 107
Step 3 In the Create Zone window, in the Zone Name field, enter HOST1_PRIMARY and click OK.
Step 4 In the tree view, expand the Zones fo1der to make zone HOST1_PRIMARY visible.
Step 5 Hold down the CTRL key and with your left mouse button, select the HOST1-P1 and DISK1-P1 device aliases and drag them onto the HOST1_PRIMARY zone placeholder.
Step 6 Click zone HOST1_PRIMARY to verify that HOST1-P1 and DISK1-P1 are members.
Step 7 Repeat Steps 2-6 to create the HOST2_SECONDARY zone. Add the following members from the fcalias list:
108 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
HOST2-P1
DISK2-P1
Step 8 Click zone HOST2_SECONDARY to verify HOST2-P1 and DISK2-P1 are members.
Step 9 Right-click ZoneSets and select Insert.
Step 10 In the Zoneset Name window, enter ZoneSet10.
Step 11 Click OK.
© 2007 Cisco Systems, Inc. Lab Guide 109
Step 12 Expand the ZoneSets and Zones folders.
Step 13 Select and drag zones HOST1_PRIMARY and HOST2_SECONDARY to ZoneSet10 to add the zones as members of the zoneset.
Step 14 Click on ZoneSet10 to verify zone members HOST1_PRIMARY and HOST2_SECONDARY.
Step 15 From a command prompt, verify the configured zones.
P29-MDS-1# show zone
zone name HOST1_PRIMARY vsan 10
pwwn 21:00:00:e0:8b:07:a5:5a [HOST1-P1]
pwwn 21:00:00:04:cf:8c:5b:2a [Disk1-P1]
zone name HOST2_SECONDARY vsan 10
pwwn 21:00:00:e0:8b:05:d0:a7 [HOST2-P1]
pwwn 21:00:00:04:cf:8c:53:26 [Disk2-P1]
The team working on MDS-1 should now skip to Step 25.
110 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
The team working on MDS-2 should complete the following steps for VSAN 20.
Step 16 In Fabric Manager, locate the VSAN 20 folder in the tree view. Right-click and select Edit Local Full Zone Database.
Step 17 Confirm that the Switch field contains P0X-MDS-2. Right-click Zones and select
Insert….
Step 18 In the Create Zone window, in the Zone Name field, enter HOST2_PRIMARY
and click OK.
© 2007 Cisco Systems, Inc. Lab Guide 111
Step 19 In the tree view, expand the Zones fo1der to make zone HOST2_PRIMARY visible.
Step 20 Hold down the CTRL key, and with your left mouse button, select the HOST2-P2 and DISK2-P2 device aliases and drag them onto the HOST2_PRIMARY zone placeholder.
Step 21 Click on zone HOST2_PRIMARY to verify HOST2-P2 and DISK2-P2 are members.
Step 22 Repeat Steps 16-21 to create the HOST1_SECONDARY zone. Add the following members from the Device Alias list:
HOST1-P2
DISK1-P2
112 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
Step 23 Click on zone HOST1_SECONDARY to verify HOST1-P2 and DISK1-P2 are members.
Step 24 From a command prompt, verify the configured zones.
P29-MDS-2# show zone
zone name HOST2_PRIMARY vsan 20
pwwn 21:00:00:e0:8b:07:a5:5a [HOST2-P2]
pwwn 21:00:00:04:cf:8c:5b:2a [Disk2-P2]
zone name HOST1_SECONDARY vsan 20
pwwn 21:00:00:e0:8b:05:d0:a7 [HOST1-P2]
pwwn 21:00:00:04:cf:8c:53:26 [Disk1-P2]
Step 25 At this point, wait until the student(s) working on the opposite switch have created their zones. Then compare the results of the show zone command.
MDS-1, VSAN 10 MDS-2, VSAN 20
Zone Name:
Alias of Member1:
Alias of Member2:
Zone Name:
Alias of Member1:
Alias of Member2:
Zone Name:
Alias of Member1:
Alias of Member2:
Zone Name:
Alias of Member1:
Alias of Member2:
© 2007 Cisco Systems, Inc. Lab Guide 113
Step 26 On MDS-2, right-click ZoneSets and select Insert… from the pop-up menu.
Step 27 In the Zoneset Name window, enter ZoneSet20.
Step 28 Click OK.
Step 29 Expand the ZoneSets and Zones folders.
Step 30 Select and drag zones HOST2_PRIMARY and HOST1_SECONDARY to ZoneSet20 to add the zones as a member of the zoneset.
Step 31 Click on ZoneSet20 to verify zone members HOST2_PRIMARY and HOST1_SECONDARY.
114 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
© 2007 Cisco Systems, Inc. Lab Guide 115
Step 32 From the command prompt, verify the configured zoneset.
MDS-2# show zoneset
P29-MDS-2# show zoneset
zoneset name ZoneSet20 vsan 20
zone name HOST2_PRIMARY vsan 20
pwwn 21:00:00:04:cf:8c:5b:2a [Disk2-P2]
pwwn 21:00:00:e0:8b:07:a5:5a [HOST2-P2]
zone name HOST1_SECONDARY vsan 20
pwwn 21:00:00:e0:8b:05:d0:a7 [HOST1-P2]
pwwn 21:00:00:04:cf:8c:53:26 [Disk1-P2]
Task 4: Activate Zonesets Now that you have created zonesets on each switch in unique VSANs, from each switch you will activate the zoneset for your respective VSANs and observe the effect on the other switch. In this procedure, you will enable zone debugging and disable the ISLs between the pod switches prior to activating the zonesets.
Complete the following steps in sequence on the specified switch.
Step 1 On MDS-1, disable the switch ISLs by disabling interfaces fc1/7-9.
# config
(config)# interface fc1/7-9
(config-if)# shutdown
(config-if)# end
Step 2 On both switches, enable zone debugging at the switch console.
# no debug all
# debug zone database events
Step 3 On MDS-1, go to Fabric Manager and locate the VSAN 10 folder in the tree view. Right-click the folder and select Edit Local Full Zone Database…
Step 4 Confirm that P0X-MDS-1 is in the Switch field.
Step 5 Expand the ZoneSets folder. Right-click ZoneSet10and select Activate.
116 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
Step 6 Confirm that the Save Running to Startup Configuration checkbox is checked and click Continue Activation.
Step 7 On the MDS-2, repeat Steps 3-6 to activate ZoneSet20 in VSAN 20.
Step 8 On both switches, from the command prompt, observe the debug activity.
P29-MDS-1# 2007 Mar 16 22:49:10.221721 zone: creating new database..
2007 Mar 16 22:49:10.222001 zone: creating policies
2007 Mar 16 22:49:10.222036 zone: copying zoneset ZoneSet10 ..
2007 Mar 16 22:49:10.222071 zone: creating zoneset: ZoneSet10 on vsan 10..
2007 Mar 16 22:49:10.222118 zone: creating zone: HOST1_PRIMARY on vsan 10.
2007 Mar 16 22:49:10.222185 zone: adding zone HOST1_PRIMARY to zoneset ZoneSet10 on vsan 10
2007 Mar 16 22:49:10.222219 zone: creating zone: HOST2_SECONDARY on vsan 10
2007 Mar 16 22:49:10.222286 zone: adding zone HOST2_SECONDARY to zoneset ZoneSet10 on vsan 10
..
.
.
2007 Mar 16 22:49:10.222587 zone: active-zoneset size: 124 full-zoneset size: 236
2007 Mar 16 22:49:10.223126 zone: Initiated Fabric Change to activate zoneset ZoneSet10 on vsan 10
2007 Mar 16 22:49:10.223162 zone: Activate request status = 0x40200038 on vsan 10
2007 Mar 16 22:49:10.223254 zone: db_lock: getting lock on vsan: 10 sub-module:2
2007 Mar 16 22:49:10.223285 zone: db_lock: locked on vsan: 10 sub-module: 2 count: 1
2007 Mar 16 22:49:10.226808 zone: active-zoneset size: 124 full-zoneset size: 236
2007 Mar 16 22:49:10.236874 zone: db_lock: unlocking the database of vsan: 102007 Mar 16 22:49:10.236926 zone: db_lock: done. count: 0, submodule: 0
2007 Mar 16 22:49:10.237057 zone: db_lock: getting lock on vsan: 10 sub-module:3
2007 Mar 16 22:49:10.237090 zone: db_lock: locked on vsan: 10 sub-module: 3 count: 1
2007 Mar 16 22:49:10.237512 zone: Creating New Binding For VSAN: 10 FCID: 0x0b03e8 WWN: 22:00:00:04:cf:8c:53:26 FWWN: 20:06:00:0d:65:6a:17:c0 SYM-NODENAME: IP ADDR: null
2007 Mar 16 22:49:10.237578 zone: Found WWN: 22:00:00:04:cf:8c:53:26
.
.
© 2007 Cisco Systems, Inc. Lab Guide 117
118 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
Step 9 From the MDS-1 CLI, enable the switch ISLs by enabling interfaces ISL 1-3.
# config
(config)# interface fc1/7-9
(config-if)# no shutdown
(config-if)# end
Step 10 Observe the debug messages at the command prompt.
P29-MDS-1(config-if)# no shut
P29-MDS-1(config-if)# 2007 Mar 16 23:17:05.261148 zone: db_lock: getting read-lo
2007 Mar 16 23:17:05.261237 zone: db_lock: read-locked on vsan: 10 sub-module: 1
2007 Mar 16 23:17:05.261296 zone: active-zoneset size: 124 full-zoneset size: 0
2007 Mar 16 23:17:05.263283 zone: active-zoneset size: 124 full-zoneset size: 0
2007 Mar 16 23:17:05.264161 zone: active-zoneset size: 124 full-zoneset size: 0
2007 Mar 16 23:17:05.265153 zone: Active zoneset size : 0 Full zoneset size: 0
2007 Mar 16 23:17:05.265200 zone: Real Active zoneset size: 0 Real Full zoneset
2007 Mar 16 23:17:05.265232 zone: Active zoneset size : 0 Full zoneset size: 0
2007 Mar 16 23:17:05.265262 zone: Real Active zoneset size: 0 Real Full zoneset
2007 Mar 16 23:17:05.265294 zone: db_lock: getting lock on vsan: 10 sub-module:
2007 Mar 16 23:17:05.265400 zone: comparison result -1
2007 Mar 16 23:17:05.265433 zone: merging databases..
2007 Mar 16 23:17:05.265463 zone: creating new database..
2007 Mar 16 23:17:05.265528 zone: creating policies
2007 Mar 16 23:17:05.265561 zone: copying database..
2007 Mar 16 23:17:05.265602 zone: creating zone: HOST1_PRIMARY on vsan 10 ..
2007 Mar 16 23:17:05.265681 zone: creating zone: HOST2_SECONDARY on vsan 10 ..
2007 Mar 16 23:17:05.265744 zone: copying zoneset ZoneSet10 ..
2007 Mar 16 23:17:05.265776 zone: creating zoneset: ZoneSet10 on vsan 10 ..
2007 Mar 16 23:17:05.265821 zone: creating zone: HOST1_PRIMARY on vsan 10 ..
2007 Mar 16 23:17:05.265855 zone: adding zone HOST1_PRIMARY to zoneset ZoneSet10
on vsan 10
2007 Mar 16 23:17:05.265889 zone: creating zone: HOST2_SECONDARY on vsan 10 ..
2007 Mar 16 23:17:05.265921 zone: adding zone HOST2_SECONDARY to zoneset ZoneSet
10 on vsan 10
2007 Mar 16 23:17:05.265958 zone: comparing databases..
2007 Mar 16 23:17:05.265992 zone: comparing zoneset1 ZoneSet10 and zoneset2 Zone
Set10..
2007 Mar 16 23:17:05.266173 zone: removing zoning policies on vsan 10
2007 Mar 16 23:17:05.266205 zone: removing zoneset ZoneSet10 on vsan 10
2007 Mar 16 23:17:05.266243 zone: removing zone HOST1_PRIMARY on vsan 10
2007 Mar 16 23:17:05.266286 zone: removing zone HOST2_SECONDARY on vsan 10
2007 Mar 16 23:17:05.266438 zone: db_lock: unlocking the database of vsan: 10
2007 Mar 16 23:17:05.266470 zone: db_lock: done. count: 1, submodule: 1
2007 Mar 16 23:17:07.485620 zone: Getting other members for [ FCID: 0x0b0200 ]
2007 Mar 16 23:17:11.424070 zone: Received zs_pvt_get_other_members() request
2007 Mar 16 23:17:27.247421 zone: Storing member [ FCID: 0x0b03e8 ]
2007 Mar 16 23:17:27.248637 zone: Number of Members: 1 Size: 12
Step 11 In Fabric Manager, click the Rediscover Fabric icon.
© 2007 Cisco Systems, Inc. Lab Guide 119
Step 12 Display the active zonesets in Fabric Manager. In the fabric tree on the left, expand the VSAN 10 and VSAN 20 folders. The zonesets you created are displayed under the VSANs. Select either of the zones in the active zoneset in the tree and note that their members are highlighted in yellow in the fabric display.
Step 13 Disable the zone debugging on both switches.
# no debug all
Step 14 On both switches, use Device Manager to update the startup configuration.
120 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
Step 15 On both switches, copy your running-config to your TFTP server.
© 2007 Cisco Systems, Inc. Lab Guide 121
122 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
Activity Verification Complete the following steps to verify your configuration.
Step 1 Display the zones and zonesets on both switches.
P29-MDS-1# show zoneset
zoneset name ZoneSet10 vsan 10
zone name HOST1_PRIMARY vsan 10
pwwn 22:00:00:04:cf:8c:53:26 [Disk1-P1]
pwwn 21:00:00:e0:8b:07:2f:5b [HOST1-P1]
zone name HOST2_SECONDARY vsan 10
pwwn 21:00:00:e0:8b:07:c2:5a [HOST2-P1]
pwwn 22:00:00:04:cf:8c:5b:2a [Disk2-P1]
P29-MDS-2# show zoneset
zoneset name ZoneSet20 vsan 20
zone name HOST2_PRIMARY vsan 20
pwwn 21:00:00:04:cf:8c:5b:2a [Disk2-P2]
pwwn 21:00:00:e0:8b:07:a5:5a [HOST2-P2]
zone name HOST1_SECONDARY vsan 20
pwwn 21:00:00:e0:8b:05:d0:a7 [HOST1-P2]
pwwn 21:00:00:04:cf:8c:53:26 [Disk1-P2]
Step 2 Display the active zoneset on both switches.
P29-MDS-1# show zoneset active
zoneset name ZoneSet10 vsan 10
zone name HOST1_PRIMARY vsan 10
* fcid 0x0b03e8 [pwwn 22:00:00:04:cf:8c:53:26] [Disk1-P1]
* fcid 0x0b0200 [pwwn 21:00:00:e0:8b:07:2f:5b] [HOST1-P1]
zone name HOST2_SECONDARY vsan 10
* fcid 0x0b0100 [pwwn 21:00:00:e0:8b:07:c2:5a] [HOST2-P1]
* fcid 0x0b03dc [pwwn 22:00:00:04:cf:8c:5b:2a] [Disk2-P1]
zoneset name ZoneSet20 vsan 20
zone name HOST2_PRIMARY vsan 20
* fcid 0x1601dc [pwwn 21:00:00:04:cf:8c:5b:2a] [Disk2-P2]
* fcid 0x160000 [pwwn 21:00:00:e0:8b:07:a5:5a] [HOST2-P2]
© 2007 Cisco Systems, Inc. Lab Guide 123
zone name HOST1_SECONDARY vsan 20
* fcid 0x160200 [pwwn 21:00:00:e0:8b:05:d0:a7] [HOST1-P2]
* fcid 0x1601e8 [pwwn 21:00:00:04:cf:8c:53:26] [Disk1-P2]
P29-MDS-2# show zoneset active
zoneset name ZoneSet10 vsan 10
zone name HOST1_PRIMARY vsan 10
* fcid 0x0b03e8 [pwwn 22:00:00:04:cf:8c:53:26] [Disk1-P1]
* fcid 0x0b0200 [pwwn 21:00:00:e0:8b:07:2f:5b] [HOST1-P1]
zone name HOST2_SECONDARY vsan 10
* fcid 0x0b0100 [pwwn 21:00:00:e0:8b:07:c2:5a] [HOST2-P1]
* fcid 0x0b03dc [pwwn 22:00:00:04:cf:8c:5b:2a] [Disk2-P1]
zoneset name ZoneSet20 vsan 20
zone name HOST2_PRIMARY vsan 20
* fcid 0x1601dc [pwwn 21:00:00:04:cf:8c:5b:2a] [Disk2-P2]
* fcid 0x160000 [pwwn 21:00:00:e0:8b:07:a5:5a] [HOST2-P2]
zone name HOST1_SECONDARY vsan 20
* fcid 0x160200 [pwwn 21:00:00:e0:8b:05:d0:a7] [HOST1-P2]
* fcid 0x1601e8 [pwwn 21:00:00:04:cf:8c:53:26] [Disk1-P2]
Task 5: Configure Active Zoneset Distribution In this task, you will configure the zoneset distribution feature and observe the results. Each student will create a test zoneset in a different VSAN from the one used in the previous task.
On the MDS-1, you have configured HOST1 PRIMARY zone in ZoneSet10 in VSAN 10. In this task, you will configure a test zoneset (ZS92) in VSAN 20.
On the MDS-2, you have configured the HOST2 PRIMARY zone in ZoneSet20 in VSAN 20. In this task, you will configure a test zoneset (ZS91) in VSAN 10.
You will activate the new test zoneset and observe the zone merge behavior. Next, you will run the zoneset distribute full command in your original VSAN (from Task 1) and re-activate the original zoneset. This will propagate your configured zoneset database (the full zoneset ) to the other switch, which will overwrite the test zoneset and result in a copy of both full zonesets replicated on both switches.
124 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
Activity Procedure Complete the following steps in sequence on the specified switch to create test zonesets.
Step 1 On the MDS-1, create a zone and zoneset for testing in VSAN 20.
Zoneset name: ZS92
Zone name: zone92
Add member: FCID 0x123456
Step 2 On the MDS-2, create a zone and zoneset for testing in VSAN 10.
Zoneset name: ZS91
Zone name: zone91
Add member: FCID 0xabcdef
Step 3 On both switches, use the CLI to display the configured and active zonesets.
# show zoneset
# show zoneset active
© 2007 Cisco Systems, Inc. Lab Guide 125
126 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
MDS-1
VSAN Configured Zonesets Active Zonesets
VSAN 10
VSAN 20
MDS-2
VSAN Configured Zonesets Active Zonesets
VSAN 10
VSAN 20
Note The test zonesets ZS91 and ZS92 should appear only in the configured zoneset.
Step 4 Display the zone status for both VSANs.
P29-MDS-1# show zone status
. . .
VSAN: 10 default-zone: deny distribute: active only Interop: default
mode: basic merge-control: allow session: none
hard-zoning: enabled broadcast: enabled
Default zone:
qos: none broadcast: disabled ronly: disabled
Full Zoning Database :
Zonesets:1 Zones:2 Aliases: 0
Active Zoning Database :
Name: ZoneSet10 Zonesets:1 Zones:2
Status: Activation completed at 22:49:10 UTC Mar 16 2007
VSAN: 20 default-zone: deny distribute: active only Interop: default
mode: basic merge-control: allow session: none
hard-zoning: enabled broadcast: disabled
Default zone:
qos: none broadcast: disabled ronly: disabled
Full Zoning Database :
Zonesets:1 Zones:1 Aliases: 0
Active Zoning Database :
Name: ZoneSet20 Zonesets:1 Zones:2
Status: Activation completed at 23:24:55 UTC Mar 16 2007
Note The zone distribute setting should be set to active only.
In the following steps, you will activate the test zonesets and observe the results. Perform the steps in sequence on the specified switch.
Step 5 On MDS-1, activate zoneset ZS92 in VSAN 20.
Step 6 Clear the Save Running to Startup Configuration checkbox and select Proposed Changes.
Note When activating a new ZoneSet, Fabric Manager will identify the differences between the currently active ZoneSet and the new ZoneSet to be activated in the specified VSAN.
© 2007 Cisco Systems, Inc. Lab Guide 127
Step 7 Click Close.
Step 8 Click Continue Activation.
Step 9 On MDS-2, activate zoneset ZS91 on VSAN 10.
Step 10 Clear the Save Running to Startup Configuration checkbox and select Proposed
Changes.
Note When activating a new ZoneSet, Fabric Manager will identify the differences between the currently active ZoneSet and the new ZoneSet to be activated in the specified VSAN.
128 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
Step 11 Click Close.
Step 12 Click Continue Activation.
Step 13 On both switches, use the CLI to display the results.
# show zoneset
# show zoneset active
MDS-1
VSAN Configured Zonesets Active Zonesets
VSAN 10
VSAN 20
MDS-2
VSAN Configured Zonesets Active Zonesets
VSAN 10
VSAN 20
Step 14 On both switches, display the zone status for both VSANs.
The ZS9X zonesets should be displayed as active in both VSANs on both switches. Because the zoneset distribute parameter is set to active, the zoning databases (full ZoneSet) did not propagate when the test zonesets were activated, resulting in no change to the configured zonesets.
© 2007 Cisco Systems, Inc. Lab Guide 129
130 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
Task 6: Configure Full Zoneset Distribution In the following steps, you will set zoneset distribution to full on the VSAN that you originally configured on both switches, reactivate the original zonesets that you created, and observe the results. Perform the following steps in sequence on the specified switch.
Step 1 On the MDS-1, use the CLI to configure zoneset distribute full for VSAN 10, then re-activate the production zoneset that you created in the previous task.
P29-MDS-1# config
(config)# zoneset distribute full vsan 10
(config)# zoneset activate name ZoneSet10 vsan 10
(config)# end
Step 2 On the MDS-2, use the CLI to configure zoneset distribute full for VSAN 20, then re-activate the production zoneset that you created in the previous task.
P29-MDS-2# config
(config)# zoneset distribute full vsan 20
(config)# zoneset activate name ZoneSet20 vsan 20
(config)# end
© 2007 Cisco Systems, Inc. Lab Guide 131
Activity Verification Complete the following steps to verify your configuration. On both switches, use the CLI to display the results.
P29-MDS-1# show zone status vsan 10
VSAN: 10 default-zone: deny distribute: full Interop: default
mode: basic merge-control: allow session: none
hard-zoning: enabled broadcast: enabled
Default zone:
qos: none broadcast: disabled ronly: disabled
Full Zoning Database :
Zonesets:1 Zones:2 Aliases: 0
Active Zoning Database :
Name: ZoneSet10 Zonesets:1 Zones:2
Status: Activation completed at 00:44:24 UTC Mar 17 2007
P29-MDS-2# show zone status vsan 20
VSAN: 20 default-zone: deny distribute: full Interop: default
mode: basic merge-control: allow session: none
hard-zoning: enabled broadcast: disabled
Default zone:
qos: none broadcast: disabled ronly: disabled
Full Zoning Database :
Zonesets:1 Zones:2 Aliases: 0
Active Zoning Database :
Name: ZoneSet20 Zonesets:1 Zones:2
Status: Activation completed at 00:18:45 UTC Mar 17 2007
P29-MDS-1# show zoneset
zoneset name ZoneSet10 vsan 10
zone name HOST1_PRIMARY vsan 10
pwwn 22:00:00:04:cf:8c:53:26 [Disk1-P1]
pwwn 21:00:00:e0:8b:07:2f:5b [HOST1-P1]
zone name HOST2_SECONDARY vsan 10
pwwn 21:00:00:e0:8b:07:c2:5a [HOST2-P1]
pwwn 22:00:00:04:cf:8c:5b:2a [Disk2-P1]
zoneset name ZoneSet20 vsan 20
zone name HOST2_PRIMARY vsan 20
132 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
pwwn 21:00:00:04:cf:8c:5b:2a [Disk2-P2]
pwwn 21:00:00:e0:8b:07:a5:5a [HOST2-P2]
zone name HOST1_SECONDARY vsan 20
pwwn 21:00:00:e0:8b:05:d0:a7 [HOST1-P2]
pwwn 21:00:00:04:cf:8c:53:26 [Disk1-P2]
P29-MDS-2# show zoneset
zoneset name ZoneSet10 vsan 10
zone name HOST1_PRIMARY vsan 10
pwwn 22:00:00:04:cf:8c:53:26 [Disk1-P1]
pwwn 21:00:00:e0:8b:07:2f:5b [HOST1-P1]
zone name HOST2_SECONDARY vsan 10
pwwn 21:00:00:e0:8b:07:c2:5a [HOST2-P1]
pwwn 22:00:00:04:cf:8c:5b:2a [Disk2-P1]
zoneset name ZoneSet20 vsan 20
zone name HOST2_PRIMARY vsan 20
pwwn 21:00:00:04:cf:8c:5b:2a [Disk2-P2]
pwwn 21:00:00:e0:8b:07:a5:5a [HOST2-P2]
zone name HOST1_SECONDARY vsan 20
pwwn 21:00:00:e0:8b:05:d0:a7 [HOST1-P2]
pwwn 21:00:00:04:cf:8c:53:26 [Disk1-P2]
P29-MDS-1# show zoneset active
zoneset name ZoneSet10 vsan 10
zone name HOST1_PRIMARY vsan 10
* fcid 0x0b03e8 [pwwn 22:00:00:04:cf:8c:53:26] [Disk1-P1]
* fcid 0x0b0200 [pwwn 21:00:00:e0:8b:07:2f:5b] [HOST1-P1]
zone name HOST2_SECONDARY vsan 10
* fcid 0x0b0100 [pwwn 21:00:00:e0:8b:07:c2:5a] [HOST2-P1]
* fcid 0x0b03dc [pwwn 22:00:00:04:cf:8c:5b:2a] [Disk2-P1]
zoneset name ZoneSet20 vsan 20
zone name HOST2_PRIMARY vsan 20
* fcid 0x1601dc [pwwn 21:00:00:04:cf:8c:5b:2a] [Disk2-P2]
* fcid 0x160000 [pwwn 21:00:00:e0:8b:07:a5:5a] [HOST2-P2]
© 2007 Cisco Systems, Inc. Lab Guide 133
zone name HOST1_SECONDARY vsan 20
* fcid 0x160200 [pwwn 21:00:00:e0:8b:05:d0:a7] [HOST1-P2]
* fcid 0x1601e8 [pwwn 21:00:00:04:cf:8c:53:26] [Disk1-P2]
P29-MDS-1#
P29-MDS-2# show zoneset active
zoneset name ZoneSet10 vsan 10
zone name HOST1_PRIMARY vsan 10
* fcid 0x0b03e8 [pwwn 22:00:00:04:cf:8c:53:26] [Disk1-P1]
* fcid 0x0b0200 [pwwn 21:00:00:e0:8b:07:2f:5b] [HOST1-P1]
zone name HOST2_SECONDARY vsan 10
* fcid 0x0b0100 [pwwn 21:00:00:e0:8b:07:c2:5a] [HOST2-P1]
* fcid 0x0b03dc [pwwn 22:00:00:04:cf:8c:5b:2a] [Disk2-P1]
zoneset name ZoneSet20 vsan 20
zone name HOST2_PRIMARY vsan 20
* fcid 0x1601dc [pwwn 21:00:00:04:cf:8c:5b:2a] [Disk2-P2]
* fcid 0x160000 [pwwn 21:00:00:e0:8b:07:a5:5a] [HOST2-P2]
zone name HOST1_SECONDARY vsan 20
* fcid 0x160200 [pwwn 21:00:00:e0:8b:05:d0:a7] [HOST1-P2]
* fcid 0x1601e8 [pwwn 21:00:00:04:cf:8c:53:26] [Disk1-P2]
Note After you set zoneset distribute full, zoneset activation propagated the zoning database to all switches in that VSAN. Both switches should now have identical zone databases. In addition, propagating the production zonesets overwrote the test zonesets.
134 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
Task 7: Merge Zones In this task, you will merge zones in a variety of configurations and observe the results. On the MDS-2, you will edit one of the zones in VSAN 10 to create an inconsistent zone database between the two pod switches.
Note You set zoneset distribute to full in VSAN 10 previously on the MDS-1, but zoneset distribute is still set to active in VSAN 10 on the MDS-2.
You will troubleshoot the problem by determining the links that were isolated due to the failed merge, and you will perform a zone database export to resolve the database inconsistency. Finally, using Fabric Manager, you will perform a Zone Merge Analysis to verify that the merge will be successful.
Activity Procedure In this procedure, you will first disable the ISLs. Then, you will edit the HOST1_PRIMARY zone on the MDS-2. Zone HOST1_PRIMARY was originally configured on the MDS-1 then merged to the MDS-2 when you synchronized the zone databases in subsequent tasks. You will then launch zone debugging to observe the merge activity upon activating the ISLs.
Perform the following steps in sequence on the specified switch.
Step 1 On both switches, use the CLI to enable zone debugging and display the current ISL status.
# no debug all
# debug zone merge events
# show interface brief
# show interface fc1/7-9 trunk vsan
Are VSANs isolated on any ports? ______ The answer should be no.
Step 2 On MDS-1, disable the switch ISLs by disabling interfaces fc1/7-9.
Note If working in teams, disabling the interfaces on one switch will consequently disable the ISL
# config
(config)# interface fc1/7-9
(config-if)# shutdown
(config-if)# end
Step 3 On MDS-2, use Fabric Manager to make the following changes to zone HOST1_PRIMARY in VSAN 10.
ZoneSet name: ZoneSet10
Zone name: HOST1_PRIMARY
Add member: FCID 0x123abc
Add member: FCID 0x456def
Step 4 Activate zoneset ZoneSet10.
Note Clear the Save Running to Startup Configuration checkbox before clicking Continue Activation.
Step 5 From the MDS-1 CLI, enable the switch ISLs by enabling interfaces ISL1-3.
# config
(config)# interface fc1/7-9
(config-if)# no shutdown
(config-if)# end
© 2007 Cisco Systems, Inc. Lab Guide 135
136 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
Step 6 At the command prompt on both switches, observe the zone debugging messages. You should see several merge-failure error messages.
P29-MDS-2# 2007 Mar 17 01:09:49 P29-MDS-2 %ZONE-2-ZS_MERGE_FULL_DATABASE_MISMATCH: %$VSAN 10%$ Zone merge full database mismatch on interface fc1/8
2007 Mar 17 01:09:49 P29-MDS-2 %ZONE-2-ZS_MERGE_FAILED: %$VSAN 10%$ Zone merge failure, isolating interface fc1/8
2007 Mar 17 01:09:49 P29-MDS-2 %ZONE-2-ZS_MERGE_FULL_DATABASE_MISMATCH: %$VSAN 10%$ Zone merge full database mismatch on interface fc1/9
2007 Mar 17 01:09:49 P29-MDS-2 %ZONE-2-ZS_MERGE_FAILED: %$VSAN 10%$ Zone merge failure, isolating interface fc1/9
2007 Mar 17 01:09:49 P29-MDS-2 %ZONE-2-_MERGE_FULL_DATABASE_MISMATCH: %$VSAN 10%$ Zone merge full database mismatch on interface fc1/7
2007 Mar 17 01:09:49 P29-MDS-2 %ZONE-2-ZS_MERGE_FAILED: %$VSAN 10%$ Zone merge failure, isolating interface fc1/7
Step 7 On both switches, display the ISLs’ trunk VSAN status to confirm VSAN isolation.
MDS-1# show interface trunk vsan
fc1/7 is trunking
Vsan 1 is up (None), FCID is 0xd50002
Vsan 10 is down (Isolation due to zone merge failure)
Vsan 20 is up (None), FCID is 0x150102
fc1/8 is trunking
Vsan 1 is up (None), FCID is 0xd50000
Vsan 10 is down (Isolation due to zone merge failure)
Vsan 20 is up (None), FCID is 0x150100
fc1/9 is trunking
Vsan 1 is up (None), FCID is 0xd50001
Vsan 10 is down (Isolation due to zone merge failure)
Vsan 20 is up (None), FCID is 0x150101)
You should observe isolation on VSAN 10.
Step 8 On both switches, display the active zonesets and compare the zone members.
# show zoneset active
MDS-2 will display the extra FCIDs and MDS-1 will not appear in the active zoneset. The active zoneset on each switch is now inconsistent, resulting in isolation for VSAN 10 on the ISL.
In the following steps, you will reconcile the zoning databases between the switches. Complete the following steps in sequence on the specified switch.
Step 9 In Fabric Manager, observe the fabric tree in the Logical Domains pane to identify the segmented VSAN.
Step 10 From Fabric Manager select Zone > Merge Analysis.
Step 11 Select Check Switch 1: MDS-2 and Check Switch 2: MDS-1.
Step 12 Enter VSAN 10 in the VSAN Id field.
Step 13 Click Analyze to identify the inconsistencies in the active zonesets in VSAN 10 on MDS-1 and MDS-2.
Step 14 Click Close.
Step 15 From the CLI, export the VSAN 10 zoneset from EXEC mode.
MDS-1# zoneset export vsan 10
Note The export option overwrites the remote switch's active zoneset with the local switch's active zoneset.
Step 16 Observe the debugging output as the zoneset is exported from MDS-1 and overwritten on MDS-2.
© 2007 Cisco Systems, Inc. Lab Guide 137
138 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
1980 Jan 17 23:36:59.095961 zone: (M)Rcvd event (LINK_DOWN) on i/f fc1/7 (vsan 10), current state = Isolated, next state = Down
1980 Jan 17 23:36:59.103391 zone: (M)Rcvd event (LINK_DOWN) on i/f fc1/8 (vsan 10), current state = Isolated, next state = Down
1980 Jan 17 23:36:59.112292 zone: (M)Rcvd event (LINK_DOWN) on i/f fc1/9 (vsan 10), current state = Isolated, next state = Down
P29-MDS-1# 1980 Jan 17 23:37:14.127113 zone: (M)Rcvd event (LINK_UP) on i/f fc1/7 (vsan 10), current state = Down, next state = Get Nbr info
1980 Jan 17 23:37:14.127266 zone: rroken saved rrtoken 453172 for i/f fc1/7 vsan 10
1980 Jan 17 23:37:14.127878 zone: (M)Rcvd event (LINK_UP) on i/f fc1/9 (vsan 10), current state = Down, next state = Get Nbr info
1980 Jan 17 23:37:14.127938 zone: rroken saved rrtoken 453176 for i/f fc1/9 vsan 10
1980 Jan 17 23:37:14.128546 zone: (M)Rcvd event (LINK_UP) on i/f fc1/8 (vsan 10) , current state = Down, next state = Get Nbr info
1980 Jan 17 23:37:14.128598 zone: rroken saved rrtoken 453180 for i/f fc1/8 vsan 10
1980 Jan 17 23:37:14.128986 zone: CMD CODE: 0x34000000
1980 Jan 17 23:37:14.129064 zone: (M)Rcvd event (RCVD_MRRA) on i/f fc1/7 (vsan 10), current state = Get Nbr info, next state = Get Nbr info
1980 Jan 17 23:37:14.129298 zone: CMD CODE: 0x34000000
1980 Jan 17 23:37:14.129413 zone: (M)Rcvd event (RCVD_MRRA) on i/f fc1/8 (vsan 10), current state = Get Nbr info, next state = Get Nbr info
1980 Jan 17 23:37:14.129643 zone: CMD CODE: 0x34000000
1980 Jan 17 23:37:14.129676 zone: (M)Rcvd event (RCVD_MRRA) on i/f fc1/9 (vsan 10), current state = Get Nbr info, next state = Get Nbr info
1980 Jan 17 23:37:14.130024 zone: CMD CODE: 0x2200008c
1980 Jan 17 23:37:14.131822 zone: Rcvd get_eport_nbr acc rrtoken 453172
1980 Jan 17 23:37:14.131888 zone: Found get nbr info req for fc1/7 vsan 10
1980 Jan 17 23:37:14.131932 zone: Rcvd get_eport_nbr acc vsan 10 fc1/7 20:01:00:0b:fd:d0:68:81
1980 Jan 17 23:37:14.131973 zone: (M)Rcvd event (RCVD_ACC) on i/f fc1/7 (vsan 10), current state = Get Nbr info, next state = MRRA Req sent
1980 Jan 17 23:37:14.132018 zone: Sending MRRA
1980 Jan 17 23:37:14.132320 zone: Rcvd get_eport_nbr acc rrtoken 453176
1980 Jan 17 23:37:14.132484 zone: Found get nbr info req for fc1/9 vsan 10
1980 Jan 17 23:37:14.132525 zone: Rcvd get_eport_nbr acc vsan 10 fc1/9 20:01:00:0b:fd:d0:68:81
1980 Jan 17 23:37:14.132614 zone: (M)Rcvd event (RCVD_ACC) on i/f fc1/9 (vsan 10), current state = Get Nbr info, next state = MRRA Req sent
1980 Jan 17 23:37:14.132650 zone: Sending MRRA
1980 Jan 17 23:37:14.132900 zone: Rcvd get_eport_nbr acc rrtoken 453180
1980 Jan 17 23:37:14.133017 zone: Found get nbr info req for fc1/8 vsan 10
1980 Jan 17 23:37:14.133088 zone: Rcvd get_eport_nbr acc vsan 10 fc1/8 20:01:00:0b:fd:d0:68:81
© 2007 Cisco Systems, Inc. Lab Guide 139
1980 Jan 17 23:37:14.133134 zone: (M)Rcvd event (RCVD_ACC) on i/f fc1/8 (vsan 10), current state = Get Nbr info, next state = MRRA Req sent
1980 Jan 17 23:37:14.133169 zone: Sending MRRA
1980 Jan 17 23:37:14.133516 zone: CMD CODE: 0x2200008c
1980 Jan 17 23:37:14.133632 zone: CMD CODE: 0x2200008c
1980 Jan 17 23:37:14.133697 zone: CMD CODE: 0x2000000
1980 Jan 17 23:37:14.133774 zone: MRRA acc resp: 16777216
1980 Jan 17 23:37:14.133806 zone: (M)Rcvd event (RCVD_ACC) on i/f fc1/7 (vsan 10), current state = MRRA Req sent, next state = Req sent
1980 Jan 17 23:37:14.133844 zone: Cached MR found with length 0x0!!
1980 Jan 17 23:37:14.133936 zone: Dequeued the pending MR on i/f fc1/7 (vsan 10)
1980 Jan 17 23:37:14.134082 zone: (M)Rcvd event (RCVD_MR) on i/f fc1/7 (vsan 10), current state = Req sent, next state = Process MR-A
1980 Jan 17 23:37:14.134447 zone: (M)Rcvd event (ZDB_EQUAL) on i/f fc1/7 (vsan 10), current state = Process MR-A, next state = Req sent
1980 Jan 17 23:37:14.134700 zone: CMD CODE: 0x2000000
1980 Jan 17 23:37:14.134749 zone: MRRA acc resp: 16777216
1980 Jan 17 23:37:14.134781 zone: (M)Rcvd event (RCVD_ACC) on i/f fc1/9 (vsan 10), current state = MRRA Req sent, next state = Req sent
1980 Jan 17 23:37:14.134847 zone: Cached MR found with length 0x0!!
1980 Jan 17 23:37:14.134975 zone: Dequeued the pending MR on i/f fc1/9 (vsan 10)
1980 Jan 17 23:37:14.135119 zone: (M)Rcvd event (RCVD_MR) on i/f fc1/9 (vsan 10), current state = Req sent, next state = Process MR-A
1980 Jan 17 23:37:14.135448 zone: (M)Rcvd event (ZDB_EQUAL) on i/f fc1/9 (vsan 10), current state = Process MR-A, next state = Req sent
1980 Jan 17 23:37:14.135697 zone: CMD CODE: 0x1980 Jan 17 23:37:14.136057 zone19
80 Jan 17 23:37:24.357034 zone: Export operation on i/f fc1/7 complete
1980 Jan 17 23:37:24.357120 zone: i/f fc1/7 (vsan 10), SNMP notified with Merge Status 1.
1980 Jan 17 23:37:24.357195 zone: Export operation on i/f fc1/8 complete
1980 Jan 17 23:37:24.357239 zone: i/f fc1/8 (vsan 10), SNMP notified with Merge Status 1.
1980 Jan 17 23:37:24.357284 zone: Export operation on i/f fc1/9 complete
Step 17 Disable debugging:
# undebug all
Step 18 Save your configuration:
# copy run start
140 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
Activity Verification Complete the following steps to verify your configuration.
Step 1 Display the trunk VSAN status on your ISLs.
# show interface fc1/7-9 trunk vsan
fc1/7 is trunking
Vsan 1 is up (None), FCID is 0xd50002
Vsan 10 is up (None), FCID is 0x0b0200
Vsan 20 is up (None), FCID is 0x150102
fc1/8 is trunking
Vsan 1 is up (None), FCID is 0xd50000
Vsan 10 is up (None), FCID is 0x0b0202
Vsan 20 is up (None), FCID is 0x150100
fc1/9 is trunking
Vsan 1 is up (None), FCID is 0xd50001
Vsan 10 is up (None), FCID is 0x0b0201
Vsan 20 is up (None), FCID is 0x150101
There should be no isolated VSANs.
Step 2 On both switches, display the active zonesets and configured zonesets, and compare the results from both switches.
P29-MDS-1# show zoneset active
zoneset name ZoneSet10 vsan 10
zone name HOST1_PRIMARY vsan 10
* fcid 0x0b03e8 [pwwn 22:00:00:04:cf:8c:53:26] [Disk1-P1]
* fcid 0x0b0200 [pwwn 21:00:00:e0:8b:07:2f:5b] [HOST1-P1]
zone name HOST2_SECONDARY vsan 10
* fcid 0x0b0100 [pwwn 21:00:00:e0:8b:07:c2:5a] [HOST2-P1]
* fcid 0x0b03dc [pwwn 22:00:00:04:cf:8c:5b:2a] [Disk2-P1]
zoneset name ZoneSet20 vsan 20
zone name HOST2_PRIMARY vsan 20
* fcid 0x1601dc [pwwn 21:00:00:04:cf:8c:5b:2a] [Disk2-P2]
* fcid 0x160000 [pwwn 21:00:00:e0:8b:07:a5:5a] [HOST2-P2]
zone name HOST1_SECONDARY vsan 20
* fcid 0x160200 [pwwn 21:00:00:e0:8b:05:d0:a7] [HOST1-P2]
* fcid 0x1601e8 [pwwn 21:00:00:04:cf:8c:53:26] [Disk1-P2]
© 2007 Cisco Systems, Inc. Lab Guide 141
P29-MDS-2# show zoneset active
zoneset name ZoneSet10 vsan 10
zone name HOST1_PRIMARY vsan 10
* fcid 0x0b03e8 [pwwn 22:00:00:04:cf:8c:53:26] [Disk1-P1]
* fcid 0x0b0200 [pwwn 21:00:00:e0:8b:07:2f:5b] [HOST1-P1]
zone name HOST2_SECONDARY vsan 10
* fcid 0x0b0100 [pwwn 21:00:00:e0:8b:07:c2:5a] [HOST2-P1]
* fcid 0x0b03dc [pwwn 22:00:00:04:cf:8c:5b:2a] [Disk2-P1]
zoneset name ZoneSet20 vsan 20
zone name HOST2_PRIMARY vsan 20
* fcid 0x1601dc [pwwn 21:00:00:04:cf:8c:5b:2a] [Disk2-P2]
* fcid 0x160000 [pwwn 21:00:00:e0:8b:07:a5:5a] [HOST2-P2]
zone name HOST1_SECONDARY vsan 20
* fcid 0x160200 [pwwn 21:00:00:e0:8b:05:d0:a7] [HOST1-P2]
* fcid 0x1601e8 [pwwn 21:00:00:04:cf:8c:53:26] [Disk1-P2]
The zonesets on both switches should now be identical.
Task 8: Manage Zone Sets In this task, you will back up, and recover a zone set.
Activity Procedure Complete the following steps on MDS-1.
Step 1 In Fabric Manager, select VSAN 20 in the Logical Domains pane.
Step 2 Click the Edit Full Zone Database icon.
Step 3 Select File > Backup > This VSAN Zones from Edit Local Full Zone Database.
\
142 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
Step 4 Click Save.
Step 5 Wait for the file save to complete and observe the Success message in the lower left corner of the Edit Local Full Zone Database window.
Step 6 Select File > Restore from the Edit Local Full Zone Database window.
Step 7 Click the ellipsis button in the From Backup File field to browse to the location of the MDS-1_VSAN20_zones_cfg.txt backup file.
© 2007 Cisco Systems, Inc. Lab Guide 143
Step 8 Select the MDS-1_VSAN20_zones_cfg.txt backup file.
Step 9 Click Open.
Step 10 Click Continue Restore.
144 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
Step 11 Observe the operations in the Restore Zone Configuration dialog.
Step 12 Click Close.
Step 13 Repeat steps 1-12 on MDS-2 to back up and restore the zones and zoneset in VSAN 10.
© 2007 Cisco Systems, Inc. Lab Guide 145
146 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
Activity Verification Complete the following steps on both switches to verify your configuration.
Step 1 From the CLI, verify the contents of the RestoreZones.cfg file.
# show file bootflash:RestoreZones.cfg
clear zone database vsan 20
config terminal
zone name HOST2_PRIMARY vsan 20
member pwwn 22:00:00:04:cf:8c:5b:2a
member pwwn 21:00:00:e0:8b:05:d0:a7
zone name HOST1_SECONDARY vsan 20
member pwwn 22:00:00:04:cf:92:75:1d
member pwwn 21:00:00:e0:8b:07:a5:5a
zoneset name ZoneSet20 vsan 20
member HOST2_PRIMARY
member HOST1_SECONDARY
Step 2 Display the active zoneset for both switches.
P29-MDS-1# show zoneset active
zoneset name ZoneSet10 vsan 10
zone name HOST1_PRIMARY vsan 10
* fcid 0x0b03e8 [pwwn 22:00:00:04:cf:8c:53:26] [Disk1-P1]
* fcid 0x0b0200 [pwwn 21:00:00:e0:8b:07:2f:5b] [HOST1-P1]
zone name HOST2_SECONDARY vsan 10
* fcid 0x0b0100 [pwwn 21:00:00:e0:8b:07:c2:5a] [HOST2-P1]
* fcid 0x0b03dc [pwwn 22:00:00:04:cf:8c:5b:2a] [Disk2-P1]
zoneset name ZoneSet20 vsan 20
zone name HOST2_PRIMARY vsan 20
* fcid 0x1601dc [pwwn 21:00:00:04:cf:8c:5b:2a] [Disk2-P2]
* fcid 0x160000 [pwwn 21:00:00:e0:8b:07:a5:5a] [HOST2-P2]
zone name HOST1_SECONDARY vsan 20
* fcid 0x160200 [pwwn 21:00:00:e0:8b:05:d0:a7] [HOST1-P2]
* fcid 0x1601e8 [pwwn 21:00:00:04:cf:8c:53:26] [Disk1-P2]
P29-MDS-1#
© 2007 Cisco Systems, Inc. Lab Guide 147
Answer Key: Configuring Zones When you complete this activity, your switch running-configuration file will be similar to the following, with differences that are specific to your device or workgroup:
vsan database
vsan 10
vsan 20
fcdomain fcid database
vsan database
vsan 10 interface fc1/5
vsan 20 interface fc1/6
vsan 10 interface fc1/10
ip default-gateway 10.0.29.254
switchname P29-MDS-1
device-alias database
device-alias name DISK1-P1 pwwn 22:00:00:04:cf:92:75:1d
device-alias name DISK1-P2 pwwn 21:00:00:04:cf:8c:53:26
device-alias name DISK2-P1 pwwn 22:00:00:04:cf:8c:5b:2a
device-alias name DISK2-P2 pwwn 21:00:00:04:cf:8c:5b:2a
device-alias name DISK3-P1 pwwn 22:00:00:04:cf:92:73:ac
device-alias name DISK3-P2 pwwn 21:00:00:04:cf:92:73:ac
device-alias name DISK4-P1 pwwn 22:00:00:04:cf:92:74:f1
device-alias name DISK4-P2 pwwn 21:00:00:04:cf:92:74:f1
device-alias name DISK5-P1 pwwn 22:00:00:04:cf:92:74:f7
device-alias name DISK5-P2 pwwn 21:00:00:04:cf:92:74:f7
device-alias name DISK6-P1 pwwn 22:00:00:04:cf:8c:53:26
device-alias name DISK6-P2 pwwn 21:00:00:04:cf:92:75:1d
device-alias name HOST1-P1 pwwn 21:00:00:e0:8b:07:2f:5b
device-alias name HOST1-P2 pwwn 21:00:00:e0:8b:07:a5:5a
device-alias name HOST2-P1 pwwn 21:00:00:e0:8b:05:d0:a7
device-alias name HOST2-P2 pwwn 21:00:00:e0:8b:07:c2:5a
device-alias commit
zoneset distribute full vsan 10
zone name HOST1_PRIMARY vsan 10
member pwwn 21:00:00:04:cf:8c:53:26
member pwwn 21:00:00:e0:8b:07:2f:5b
zone name HOST2_SECONDARY vsan 10
member pwwn 21:00:00:04:cf:8c:5b:2a
member pwwn 21:00:00:e0:8b:07:c2:5a
zone name HOST2_PRIMARY vsan 20
148 Implementing Cisco Storage Networking Solutions (ICSNS) v3.0 © 2007 Cisco Systems, Inc.
member pwwn 22:00:00:04:cf:8c:5b:2a
member pwwn 21:00:00:e0:8b:05:d0:a7
zone name HOST1_SECONDARY vsan 20
member pwwn 22:00:00:04:cf:92:75:1d
member pwwn 21:00:00:e0:8b:07:a5:5a
zoneset name ZoneSet10 vsan 10
member HOST1_PRIMARY
member HOST2_SECONDARY
zoneset activate name ZoneSet10 vsan 10
zoneset name ZoneSet20 vsan 20
member HOST2_PRIMARY
member HOST1_SECONDARY
zoneset activate name ZoneSet20 vsan 20
interface fc1/5
no shutdown
interface fc1/6
no shutdown
interface fc1/7
no shutdown
interface fc1/8
no shutdown
interface fc1/9
no shutdown
interface fc1/10
no shutdown
interface mgmt0
switchport speed 100
ip address 10.0.29.5 255.255.255.0