FCoE Deployment Using PowerEdge. M I/O Aggregator and Brocade VDX-6730

Transcription

1 FCoE Deployment Using PowerEdge M I/O Aggregator and Brocade VDX-6730 Neal Beard Robert Luis Kevin Locklear

2 This document is for informational purposes only and may contain typographical errors and technical inaccuracies. The content is provided as is, without express or implied warranties of any kind Dell Inc. All rights reserved. Dell and its affiliates cannot be responsible for errors or omissions in typography or photography. Dell, the Dell logo, and PowerEdge are trademarks of Dell Inc. Intel and Xeon are registered trademarks of Intel Corporation in the U.S. and other countries. Microsoft, Windows, and Windows Server are either trademarks or registered trademarks of Microsoft Corporation in the United States and/or other countries. Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and names or their products. Dell disclaims proprietary interest in the marks and names of others. April 2013 Rev 1.0 2

3 Contents Introduction... 5 Dell PowerEdge I/O Aggregator switch configuration... 7 Brocade VDX switch configuration... 8 Brocade 5300 Switch configuration Appendix Tables Table 1. Common CLI commands Table 2. Infrastructure versions Table 3. BOM infrastructure list Figures Figure 1. Dell PowerEdge M I/0 Aggregator... 5 Figure 2. Brocade VDX Figure 3. Brocade Figure 4. FCoE topology diagram... 6 Figure 5. Show FIP-Snooping FCF... 7 Figure 6. Show FIP-Snooping enode... 7 Figure 7. Show FIP-Snooping sessions... 7 Figure 8. Management IP address configuration... 8 Figure 9. VDX License verification... 8 Figure 10. VCS Configuration Confirmation... 9 Figure 11. Lag (Port Channel) member configuration... 9 Figure 12. LAG (Port Channel) configuration... 9 Figure 13. LAG (Port Channel) confirmation Figure 14. Converged Enhanced Ethernet (CEE) map configuration Figure 15. Converged Enhanced Ethernet (CEE) map configuration Figure 16. FCoE map configuration Figure 17. FCoE map confirmation Figure 18. LLDP configuration Figure 19. LLDP confirmation Figure 20. FCoE login confirmation Figure 21. Brocade VDX Initiator WWPN Discovery Figure 22. Brocade 5300 target WWPN discovery Figure 23. VDX Lsan zone creation

4 Figure 24. VDX zone configuration creation Figure 25. VDX zone configuration activation Figure 26. VDX zone confirmation Figure IP address configuration Figure 28. Name server output Figure Lsan zone creation Figure Lsan configuration creation Figure Lsan Zone Enablement Figure Webtools GUI Figure EX Port configuration wizard Figure EX Port configuration wizard Figure EX Port configuration wizard Figure EX Port configuration report Figure EX Port configuration confirmation Figure FCRS confirmation Figure Lsan zone show command

5 Introduction This white paper discusses a Fibre Channel over Ethernet (FCoE) deployment using Dell s PowerEdge M I/O Aggregator as an FCoE Initialization Protocol (FIP) Snooping Bridge (FSB). The FCoE configuration process will be based on the interaction between the I/O Aggregator, a Brocade VDX Ethernet Fabric Switch, and a Brocade 5300 Fibre Channel (FC) switch. Discussion of the Converged Network Adapter (CNA) and storage array configuration are currently outside the scope of this document. Figure 1. Dell PowerEdge M I/0 Aggregator Figure 2. Brocade VDX Figure 3. Brocade

6 Figure 4. FCoE topology diagram As Figure 4 illustrates, the FCoE topology is comprised of the following components: Dell Compellent FC8 Array FC Target processing read/write requests Brocade 5300 FC switch providing native FC services to the initiators and targets Brocade VDX Ethernet Fabric switch providing Fiber Channel Forwarder (FCF) services to the initiators and targets Dell PowerEdge M I/O Aggregator Ethernet Layer 2 switch providing FSB services to the initiators in the M1000e Dell PowerEdge M620 Server with Broadcom 57810S CNA FCoE initiator originating read/write requests 6

7 Dell PowerEdge I/O Aggregator switch configuration The Dell PowerEdge I/O Aggregator (IOA) was designed for ease of use. Configuration consists simply of physically connecting the cables between the IOA and the Brocade VDX Once the cables are connected, the IOA automatically configures all uplink ports into a single Link Aggregation Group (LAG). Exceptions when configuring the IOA are that only one LAG is allowed per IOA based on FW Once the proper parameters are configured on the Brocade VDX and 5300 FC switch, there are a number of show commands that can be run on the IOA to confirm that the FSB features are functioning properly. Figure 5. Show FIP-Snooping FCF IOA_B2_9BF347#show fip-snooping fcf FCF MAC FCF Interface VLAN FC-MAP FKC_ADV_PERIOD No.of Enodes :27:f8:0b:54:5e Po e:fc: This show command confirms that the IOA is receiving the proper FCoE mapping information from the VDX. The main fields to make note of are the FCF MAC, FCF interface and VLAN. The FCF MAC is the MAC address of the VDX. The FCF interface is the default Port Channel ID of the IOA, and the VLAN is 200. The VLAN configuration will take place during the FCoE map configuration (Figure 12.) Figure 6. Show FIP-Snooping enode IOA_B2_9BF347#show fip-snooping enode Enode MAC Enode Interface FCF MAC VLAN FC-ID bc:30:5b:41:1d:a5 Te 0/4 00:27:f8:0b:54:5e :02:40 This command confirms that the FIP was successful due to there being a FC-ID of 14:02:40. This FC-ID actually comes from the Fabric Services running on the Brocade 5300 Fibre Channel switch connected to the VDX. Figure 7. Show FIP-Snooping sessions IOA_B2_9BF347#show fip-snooping sessions interface vlan 200 Enode MAC Enode Intf FCF MAC FCF Intf VLAN FCoE MAC FC-ID Port WWPN Port WWNN bc:30:5b:41:1d:a5 Te 0/4 00:27:f8:0b:54:5e Po e:fc:00:14:02:40 14:02:40 20:01:bc:30:5b:41:1d:a5 20:00:bc:30:5b:41:1d:a5 The show fip-snooping sessions interface vlan 200 command shows two important fields: the FCoE MAC address and the World Wide Port Name of the CNA. 7

8 Brocade VDX switch configuration Configuring the VDX to pass FCoE traffic between the server connected to the IOA and the storage array connected to the Brocade 5300 will require multiple steps. The initial configuration step is to connect a serial cable and set up a management port IP address. Note: Default login credentials are admin and password. Figure 8. Management IP address configuration VDX_rb_20_0B545E# config Entering configuration mode terminal VDX_rb_20_0B545E(config)# interface Management 20/0 VDX_rb_20_0B545E(config-Management-20/0)# no ip address dhcp VDX_rb_20_0B545E(config-Management-20/0)# ip address /16 VDX_rb_20_0B545E(config-Management-20/0)# Now that the IP address has been set on the VDX , the next step is to verify the proper licenses are loaded on the VDX. Figure 9. VDX License verification VDX_rb_20_0B545E# show license rbridge-id: 20 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx FCoE Base license Feature name:fcoe_base xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx Ports on Demand license - additional 8 port upgrade license Feature name:ports_on_demand_1 xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx VCS Fabric license Feature name:vcs_fabric Note: If the licenses discussed are absent this configuration will not function The licenses needed are the FCoE Base license, the Ports on Demand license, and the Virtual Cluster Switch (VCS) license. The FCoE base license and the VCS license are required to enable the activation of the FC ports as well as multi-hop FCoE traffic. The Ports on Demand (POD) license activates 8 ports per POD instance on the VDX The first 16 ports of the VDX are considered base ports, and are enabled by default 8

9 Figure 10. VCS Configuration Confirmation VDX_rb_20_0B545E# show vcs detail Config Mode : Local-Only VCS ID : 100 Total Number of Nodes : 1 Node :1 Serial Number : BWW2533H00A Condition : Good Status : Co-ordinator VCS Id : 100 Rbridge-Id : 20* Co-ordinator : YES WWN : 10:00:00:27:F8:0B:54:5E Switch MAC : 00:27:F8:0B:54:5E FCF MAC : 00:27:F8:0B:54:5E Switch Type : VDX Internal IP : Management IP : When enabling the VCS feature on the VDX switch, two parameters must be set. The first parameter is the VCS id, this id must be the same for all the VDX switches that will participate in the VCS fabric. The second parameter is the Rbridge-id, this id must be unique for every switch in the VCS fabric. The command to set these parameters is vcs rbridge-id X vcs-id Y enable. Note: The switch must be disabled to set these two parameters, hence the enable at the end of the command. Figure 11. Lag (Port Channel) member configuration VDX_rb_20_0B545E# config Entering configuration mode terminal VDX_rb_20_0B545E(config)# interface TenGigabitEthernet 20/0/12 VDX_rb_20_0B545E(conf-if-te-20/0/12)# channel-group 1 mode active type standard VDX_rb_20_0B545E(conf-if-te-20/0/12)# Once the Ethernet configuration sub-menu for port 12 has been entered, the LAG (Port Channel) configuration characteristics can be accessed. Channel-group 1 will be the LAG (Port Channel) numerical designation; mode active infers that the VDX will initiate Link Aggregation Control Protocol Data Units (LACPDU) regardless of whether or not the partner system sends LACPDU s. Type standard means that only 802.3ad LACP communications will occur. For this LAG (Port Channel) port 15 has also been configured in the same manner as port 12. Figure 12. LAG (Port Channel) configuration VDX_rb_20_0B545E# config Entering configuration mode terminal VDX_rb_20_0B545E(config)# interface Port-channel 1 VDX_rb_20_0B545E(config-Port-channel-1)# switchport VDX_rb_20_0B545E(config-Port-channel-1)# switchport mode trunk VDX_rb_20_0B545E(config-Port-channel-1)# switchport trunk allowed vlan all VDX_rb_20_0B545E(config-Port-channel-1)# switchport trunk tag native-vlan VDX_rb_20_0B545E(config-Port-channel-1)# fcoeport default VDX_rb_20_0B545E(config-Port-channel-1)# no shutdown 9

10 Entering the configuration menu for Port-Channel 1, the main configuration setting to take note of is the command fcoeport default. This command provisions all the members of the LAG (Port Channel) to carry only FCoE traffic. Figure 13. VDX_rb_20_0B545E# show port-channel 1 LACP Aggregator: Po 1 Aggregator type: Standard Ignore-split is enabled Admin Key: Oper Key 0001 Partner System ID - 0x8000,d0-67-e5-9b-f3-47 Partner Oper Key 0128 Member ports on rbridge-id 20: Link: Te 20/0/12 (0x B) sync: 1 Link: Te 20/0/15 (0x E) sync: 1 * LAG (Port Channel) confirmation From the output of the command show port-channel 1, ports 12 and 15 are confirmed as active members of this LAG (Port Channel). Figure 14. Converged Enhanced Ethernet (CEE) map configuration VDX_rb_20_0B545E# config Entering configuration mode terminal VDX_rb_20_0B545E(config)# cee-map default VDX_rb_20_0B545E(config-cee-map-default)# priority-group-table 1 weight 50 pfc on VDX_rb_20_0B545E(config-cee-map-default)# priority-group-table 2 weight 50 pfc off VDX_rb_20_0B545E(config-cee-map-default)# priority-table VDX_rb_20_0B545E(config-cee-map-default)# When setting up the CEE map for FCoE, 3 settings need to be configured: 1. ETS (Enhanced Transmission Selection) The command lines with the entries weight 50 are provisioning the bandwidth of 10-Gigabit Ethernet between FCoE and LAN traffic. 2. PFC (Priority Flow Control) The command lines with the entries pfc on or pfc off are setting up a lossless environment for FCoE frames assigned to a certain class of service. In this case we can see that Priority Group Table 1 is assigned to Class Of Service queue (COS) 3, while Priority Group Table 2 is assigned to COS queue s 0, 1, 2, and Priority Table The command priority-table is used to set what traffic types traverse which Class of Service queues. Note that 15.x typically assigned to COS 7 is a strict priority queue that can allocate all the bandwidth needed for tasks such as Inter Process Communications (IPC). COS queues 0, 1, 2, 3, and 4 use a Deficit Weighted Round Robin (DWRR) algorithm to allocate bandwidth during congestion events. One other special consideration is that COS queues 5, 6, and 7 are set for strict priority. This is due to the fact that the VDX has 8 priority groups, while the IOA has only 4 priority groups. Setting 15.2 on COS 5, 15.1 on COS 6, and 15.0 on COS 7 allows the FCoE priority groups to match between the IOA and VDX

11 Figure 15. VDX_rb_20_0B545E# show cee maps Converged Enhanced Ethernet (CEE) map configuration CEE Map 'default' Precedence: 1 Remap Fabric-Priority to Priority 0 Remap Lossless-Priority to Priority 0 Priority Group Table 1: Weight 50, PFC Enabled, BW% 50 2: Weight 50, PFC Disabled, BW% : PFC Disabled 15.1: PFC Disabled 15.2: PFC Disabled 15.3: PFC Disabled 15.4: PFC Disabled 15.5: PFC Disabled 15.6: PFC Disabled 15.7: PFC Disabled Priority Table CoS: PGID: Enabled on the following interfaces: Te 20/0/12, Te 20/0/15 The command output confirms that ETS, and PFC are configured correctly as well as the priority groups. Figure 16. FCoE map configuration VDX_rb_20_0B545E# VDX_rb_20_0B545E# config Entering configuration mode terminal VDX_rb_20_0B545E(config)# fcoe VDX_rb_20_0B545E(config-fcoe)# fabric-map default VDX_rb_20_0B545E(config-fcoe-fabric-map)# vlan 200 VDX_rb_20_0B545E(config-fcoe-fabric-map)# The FCoE Map (fabric-map) configuration step is for setting a vlan designation from the default vlan 1002 to, in this case, vlan 200. Figure 17. FCoE map confirmation VDX_rb_20_0B545E# show fcoe fabric-map default ====================================================================================== Fabric-Map VLAN VFID Pri FCMAP FKA Timeout Max-Enodes ====================================================================================== default [D] 3[D] 0xefc00[D] 8000[D] Disabled 256[D] Total number of Fabric Maps = 1 This command confirms that all FCoE traffic will traverse vlan

12 Figure 18. LLDP configuration VDX_rb_20_0B545E# config Entering configuration mode terminal VDX_rb_20_0B545E(config)# protocol lldp VDX_rb_20_0B545E(conf-lldp)# advertise dcbx-fcoe-app-tlv VDX_rb_20_0B545E(conf-lldp)# advertise dcbx-fcoe-logical-link-tlv VDX_rb_20_0B545E(conf-lldp)# advertise dcbx-tlv VDX_rb_20_0B545E(conf-lldp)# The Link Layer Discovery Protocol (LLDP) is a protocol used for Data Center Bridging exchange (DCBx) advertisement of information to other DCBx-aware devices. Typically LLDP is a transmit only protocol; for DCBx implementations, however, acknowledgments have been enabled. LLDP uses three Type Length Value frames to convey DCBx parameters to neighbor devices. advertise dcbx-fcoe-app-tlv is used to negotiate FCoE priority, PFC, and ETS. advertise dcbx-fcoe-logical-link-tlv is used to advertise the status of the logical link. advertise dcbx-tlv is used to advertise to any DCBx aware devices that the Type, Length, Value frames are compliant to IEEE specifications. Figure 19. LLDP confirmation VDX_rb_20_0B545E# show lldp interface tengigabitethernet 20/0/12 LLDP information for Te 20/0/12 State: Enabled Mode: Receive/Transmit Advertise Transmitted: 30 seconds Hold time for advertise: 120 seconds Tx Delay Timer: 1 seconds DCBX Version : CEE Auto-Sense : No Transmit TLVs: Chassis ID Port ID TTL IEEE DCBx DCBx FCoE App DCBx FCoE Logical Link DCBx FCoE Priority Values: 3 DCBx iscsi Priority Values: 4 This show command confirms that for port 12 LLDP is enabled and is advertising the application, logical link, and IEEE DCBx TLVs. Figure 20. FCoE login confirmation VDX_rb_20_0B545E# show fcoe login ====================================================================================== FCOE-Port Eth-port Device WWN Device MAC Session MAC ====================================================================================== Fcoe 1/20/2 Po 1 20:01:bc:30:5b:41:1d:a5 bc:30:5b:41:1d:a5 0e:fc:00:14:02:40 Fcoe 1/20/7 Po 1 20:01:bc:30:5b:41:1a:b8 bc:30:5b:41:1a:b8 0e:fc:00:14:03:00 Total number of Logins = 2 This command confirms that there is a working FCoE interface, which has been configured correctly. The next command below will show what devices are communicating. 12

13 Figure 21. Brocade VDX Initiator WWPN Discovery VDX_rb_20_0B545E# show name-server detail PID: Port Name: 20:01:BC:30:5B:41:1D:A5 Node Name: 20:00:BC:30:5B:41:1D:A5 SCR: 3 FC4s: FCP PortSymb: [43] "Broadcom Port1 pwwn 20:01:bc:30:5b:41:1d:a5" NodeSymb: [55] "Broadcom BCM57810 FCoE WIN-NNFMURD15T9" Fabric Port Name: 50:02:7F:80:B5:49:90:21 Permanent Port Name: 20:01:BC:30:5B:41:1D:A5 Device type: Physical Initiator Interface: Fcoe 1/20/2 Physical Interface: Te 20/255/65535 Share Area: Yes Redirect: No Now that the proper protocols and links have been configured between the IOA and the VDX, device attributes can be collected in the VDX s and 5300 s name server databases. The presence of a name server entry for the CNA confirms that the configuration is correct up to this point. The name server service is a database of device attributes that is typically used to collect those active devices in the fabric. In this instance we are using this service to discover the World Wide Port Name (WWPN) of a Broadcom CNA. Figure 22. Brocade 5300 target WWPN discovery SW5300:admin> nsshow { Type Pid COS PortName NodeName TTL(sec) N ; 3;50:00:d3:10:00:ec:46:08;50:00:d3:10:00:ec:46:00; na FC4s: FCP PortSymb: [116] "Compellent Port QLGC FC 8Gbps; Slot=02 Port=02 in Controller: SN of Storage Center: Storage Center 60486/60487" NodeSymb: [53] "Compellent Storage Center: Storage Center 60486/60487" Fabric Port Name: 20:08:00:05:1e:58:6a:2f Permanent Port Name: 50:00:d3:10:00:ec:46:08 Port Index: 8 Share Area: No Device Shared in Other AD: No Redirect: No Partial: No LSAN: Yes N ; 3;50:00:d3:10:00:ec:46:1e;50:00:d3:10:00:ec:46:02; na FC4s: FCP PortSymb: [116] "Compellent Port QLGC FC 8Gbps; Slot=02 Port=02 in Controller: SN of Storage Center: Storage Center 60486/60487" NodeSymb: [53] "Compellent Storage Center: Storage Center 60486/60487" Fabric Port Name: 20:09:00:05:1e:58:6a:2f Permanent Port Name: 50:00:d3:10:00:ec:46:1e Port Index: 9 Share Area: No Device Shared in Other AD: No Redirect: No Partial: No LSAN: Yes The Local Name Server has 2 entries } The Brocade 5300 nsshow command displays the target device attributes. The field here is the Permanent Port Name: field. This field value is what will be used when creating the lsan zoning definitions between the WWPN s of the storage array with the initiator WWPN s. 13

14 Note: Accessing the telnet service of the 5300 via an IP address is covered in Figure

15 Lsan Zoning Zoning is typically used in Fibre Channel networks to associate an initiator with the target devices with which it needs to communicate. Zoning is also used to limit the devices the initiator will receive when probing the name server for target devices the initiator will use to setup an I/O path. The zoning action performed here is a special case strictly used for FCRS s. The zone name must start with the prefix lsan_. This prefix to a zone name can be upper or lower case, or a mix of both. The key point is that when an lsan zone in two separate fabrics match initiator/target WWPNs, the FCRS will project these remote devices into each respective local fabric. These remote devices appear to all the local fabric services as if they are directly attached to the local switch. For more information on Brocade s Fiber Channel Routing Service please refer to chapter 23 of the Brocade Fabric OS Administrators Guide v Figure 23. VDX Lsan zone creation VDX_rb_20_0B545E# configure Entering configuration mode terminal VDX_rb_20_0B545E(config)# zoning defined-configuration zone lsan_vdx_20 VDX_rb_20_0B545E(config-zone-lsan_vdx_20)# member-entry 20:01:BC:30:5B:41:1D:A5;50:00:D3:10:00:EC:46:1B VDX_rb_20_0B545E(config-zone-lsan_vdx_20)# exit VDX_rb_20_0B545E(config)# zoning enabled-configuration cfg-action cfg-save Now that the CNA and storage array WWPNs have been discovered, the zoning process can begin. The command zoning defined-configuration zone is where the lsan_ zone name is created. A subconfiguration mode prompt for the member-entry command appears, and this is where the WWPNs for the initiators and targets are added. Once the WWPNs have been added, the final step for this zoning task is to save the configuration to nonvolatile memory with the command zoning enabledconfiguration cfg-action cfg-save. Figure 24. VDX zone configuration creation VDX_rb_20_0B545E(config)# zoning defined-configuration cfg lsanconfig VDX_rb_20_0B545E(config-cfg-lsanconfig)# member-zone lsan_vdx_20 VDX_rb_20_0B545E(config-cfg-lsanconfig)# exit VDX_rb_20_0B545E(config)# zoning enabled-configuration cfg-action cfg-save The command zoning defined-configuration cfg is where the zone configuration name is added. The next step is to add the zone lsan_vdx_20 with the command member-zone. With all zoning activities, the final step is to always save changes to nonvolatile memory with the command zoning enabled-configuration cfg-action cfg-save. Figure 25. VDX zone configuration activation VDX_rb_20_0B545E(config)# zoning enabled-configuration cfg-name lsanconfig The final command zoning enabled-configuration cfg-name lsanconfig activates the VDX zoning. 15

16 Figure 26. VDX zone confirmation VDX_rb_20_0B545E# show running-config zoning zoning defined-configuration cfg lsanconfig member-zone lsan_vdx_20! zoning defined-configuration zone lsan_vdx_20 member-entry 20:01:bc:30:5b:41:1d:a5 member-entry 50:00:d3:10:00:ec:46:1b member-entry 50:00:d3:10:00:ec:46:1e member-entry 50:00:d3:10:00:ec:46:08 member-entry 20:01:bc:30:5b:41:1a:b8! zoning enabled-configuration cfg-name lsanconfig zoning enabled-configuration default-zone-access allaccess zoning enabled-configuration cfg-action cfg-save zoning enabled-configuration enabled-zone lsan_vdx_20 member-entry 20:01:bc:30:5b:41:1d:a5 member-entry 50:00:d3:10:00:ec:46:1b member-entry 50:00:d3:10:00:ec:46:1e member-entry 50:00:d3:10:00:ec:46:08 member-entry 20:01:bc:30:5b:41:1a:b8! VDX_rb_20_0B545E# The command to confirm that the zoning configuration has been activated and has the correct zone members is show running-config zoning. The resulting output shows that the members are correct and the configuration is enabled. Now that the Brocade VDX is fully configured, the final phase is to setup the Brocade B5300 switch. 16

17 Brocade 5300 Switch configuration Figure 27. SW5300:admin> ipaddrset Ethernet IP Address [ ]: changes:0 Ethernet Subnetmask [ ]: Gateway IP Address [none]: DHCP [Off]: SW5300:admin> 5300 IP address configuration The initial configuration step is to connect a serial cable and run the command ipaddrset. This command can either set a static IP address or configure the switch for DHCP. Figure 28. Name server output SW5300:admin> nsshow { Type Pid COS PortName NodeName TTL(sec) N ; 3;50:00:d3:10:00:ec:46:08;50:00:d3:10:00:ec:46:00; na FC4s: FCP PortSymb: [116] "Compellent Port QLGC FC 8Gbps; Slot=02 Port=02 in Controller: SN of Storage Center: Storage Center 60486/60487" NodeSymb: [53] "Compellent Storage Center: Storage Center 60486/60487" Fabric Port Name: 20:08:00:05:1e:58:6a:2f Permanent Port Name: 50:00:d3:10:00:ec:46:08 Port Index: 8 Share Area: No Device Shared in Other AD: No Redirect: No Partial: No LSAN: Yes N ; 3;50:00:d3:10:00:ec:46:1e;50:00:d3:10:00:ec:46:02; na FC4s: FCP PortSymb: [116] "Compellent Port QLGC FC 8Gbps; Slot=02 Port=02 in Controller: SN of Storage Center: Storage Center 60486/60487" NodeSymb: [53] "Compellent Storage Center: Storage Center 60486/60487" Fabric Port Name: 20:09:00:05:1e:58:6a:2f Permanent Port Name: 50:00:d3:10:00:ec:46:1e Port Index: 9 Share Area: No Device Shared in Other AD: No Redirect: No Partial: No LSAN: Yes The Local Name Server has 2 entries } The command nsshow is run on the Brocade 5300 switch to see the target WWPNs that will need to be placed in the lsan zone along with the initiator WWPNs. Figure Lsan zone creation SW5300:admin> zonecreate "lsan_5300", "20:01:bc:30:5b:41:1a:b8;20:01:bc:30:5b:41:1d:a5;50:00:d3:10:00:ec:46:08;50:0 0:d3:10:00:ec:46:1b;50:00:d3:10:00:ec:46:1e" 17

18 Lsan zone creation on the Brocade 5300 series FC switch is very straightforward. Run the command zonecreate, name the zone lsan_, and add the member WWPNs. The lsan zone configuration on the 5300 must only match the lsan zone configuration on the VDX in one global parameter. There must be a match of at least one initiator/target WWPN pair between the two switches lsan_ zone configuration. Figure Lsan configuration creation SW5300:admin> cfgcreate "lsan_fabric", "comp_phy";lsan_5300" Once the lsan zones are created, these zones must be placed in a zone configuration. The command is cfgcreate, the configuration is then named, and the zones are placed in the configuration. Figure Lsan Zone Enablement SW5300:admin> cfgenable "lsan_fabric" You are about to enable a new zoning configuration. This action will replace the old zoning configuration with the current configuration selected. If the update includes changes to one or more traffic isolation zones, the update may result in localized disruption to traffic on ports associated with the traffic isolation zone changes Do you want to enable 'lsan_fabric' configuration (yes, y, no, n): [no] y zone config "lsan_fabric" is in effect Updating flash... Now that the lsan zones have been created and put inside a zone configuration, the last zoning step is to enable to the configuration. The command is cfgenable cfgname. 18

19 SW5300:admin> cfgshow Defined configuration: cfg: lsan_fabric comp_phy; lsan_ Lsan zone confirmation zone: comp_phy 50:00:d3:10:00:eb:e0:38; 50:00:d3:10:00:eb:e0:37 zone: lsan_ :01:bc:30:5b:41:1a:b8; 20:01:bc:30:5b:41:1d:a5; 50:00:d3:10:00:ec:46:08; 50:00:d3:10:00:ec:46:1b; 50:00:d3:10:00:ec:46:1e Effective configuration: cfg: lsan_fabric zone: comp_phy 50:00:d3:10:00:eb:e0:38 50:00:d3:10:00:eb:e0:37 zone: lsan_ :01:bc:30:5b:41:1a:b8 20:01:bc:30:5b:41:1d:a5 50:00:d3:10:00:ec:46:08 50:00:d3:10:00:ec:46:1b 50:00:d3:10:00:ec:46:1e The command cfgshow confirms that the zone configuration is correct and has been put into effect. Figure Webtools GUI 19

20 The final configuration step to enable an I/O path between the initiator and target is to set up an Inter Fabric Link (IFL) between the VDX and 5300 switches. The screenshot above is from Brocade s GUI called Webtools. The GUI has been chosen based on the fact that there is a built-in wizard for setting up EX-Ports (IFL s). In order to launch Webtools, enter the IP address of the switch into a browser. Once Webtools is loaded, click on the Port Admin tab and then select the port that is physically connected between the 5300 and VDX. Click the Edit Configuration tab to launch a port configuration wizard. Figure EX Port configuration wizard Once the wizard is launched, choose EX-Port, a Fabric ID that is different than the VDX s (the default is 1). Click the drop-down arrow next to Fabric ID and choose a numerical designation. In this case Fabric ID 2 was chosen. Finally, change the Interop Mode to Brocade NOS Fabric, then click Next. 20

21 Figure EX Port configuration wizard This screen allows default values to be changed in order to match the other switch. Leave the values at default for this particular configuration, and click Next. 21

22 Figure EX Port configuration wizard This screen is a final confirmation of all the settings collected. Click Save if all values look correct, or click Previous to change the incorrect parameters. 22

23 Figure EX Port configuration report This final screen confirms that all parameters have been accepted and written to nonvolatile ram. Click Close to exit the wizard and return to the Port Admin page. 23

24 Figure EX Port configuration confirmation Once the Port Admin page has come up, click the port on which the EX-Port was configured. Within a minute, the EX-Port should come online and show the VDX switch as a neighbor domain. Figure FCRS confirmation SW5300:admin> fcrproxydevshow Proxy WWN Proxy Device Physical State Created PID Exists PID in Fabric in Fabric :01:bc:30:5b:41:1a:b8 01f Imported 1 20:01:bc:30:5b:41:1d:a5 01f Imported 2 50:00:d3:10:00:ec:46:08 01fa Imported 2 50:00:d3:10:00:ec:46:1e 01f Imported Total devices displayed: 4 There are multiple commands to confirm that the FCRS s components are correct. One of the commands that gives the most information is fcrproxydevshow. This command shows that the CNA WWPN 20:01:BC:30:5B:41:1D:A5 has been imported into the Brocade 5300 fabric and has been given a proxy pid of 01f101. This command also shows that the CNA proxy attributes were created in Fabric ID 1 (VDX) and exists in Fabric ID 2 (5300). 24

25 Figure 39. SW5300:admin> lsanzoneshow -s Fabric ID: 1 Zone Name: lsan_ :01:bc:30:5b:41:1a:b8 Imported 20:01:bc:30:5b:41:1d:a5 Imported 50:00:d3:10:00:ec:46:08 EXIST 50:00:d3:10:00:ec:46:1b Configured 50:00:d3:10:00:ec:46:1e EXIST Fabric ID: 2 Zone Name: lsan_vdx_20 20:01:bc:30:5b:41:1d:a5 EXIST 50:00:d3:10:00:ec:46:1b Configured 50:00:d3:10:00:ec:46:1e Imported 50:00:d3:10:00:ec:46:08 Imported 20:01:bc:30:5b:41:1a:b8 EXIST 5300 Lsan zone show command The command lsanzoneshow s shows two important facts. First, that the CNA is being imported into the 5300 s fabric, and second, that the storage array is being imported into the VDX s fabric. 25

26 Appendix Table 1. Common CLI commands CLI commands VDX Interface management rbridge-id/port Show license Show vcs detail Interface te rbridge-id/slot/port Show port-channel x Cee-map default Show cee maps fcoe Show fcoe fabric-map default Protocol LLDP Show lldp int te rbridge-id/slot/port Show fcoe login Show name-server detail Zoning defined-configuration zone lsan_vdx_20 Zoning defined-configuration cfg lsanconfig Zoning enabled-configuration cfg-name lsanconfig Show running-config zoning CLI commands 5300 Nsshow Ipaddrset zonecreate cfgcreate cfgenable cfgshow switchshow fcrproxydevshow Lsanzoneshow -s Description Sets management ip address Shows license enabled features Shows vcs fabric parameters and mode Use this command to enter the interface configuration mode Shows Link Aggregation Group (LAG) information Use this command to enter the CEE map configuration mode Displace information on the CEE map configuration Enables the FCoE configuration mode Shows the current configuration of the FCoE fabricmap Use this command to enter the LLDP configuration mode Shows the current lldp interface information Shows fcoe login information Shows detailed namer server information about devices connected to the switch Creates a new zone or adds/removes members to an existing zone Creates a new zone configuration or adds/removes zones to an existing configuration Enables a zone configuration Shows the zone configuration Shows detailed namer server information about devices connected to the switch Sets the management ip address Creates the zone that the member devices are grouped in Creates the zone configuration Enables the zone configuration Shows the defined and effective (enabled) zoning configuration Shows switch, blade, and port status information Displays proxy (remote) devices presented by the Fibre Channel Routing Service to local fabrics Displays local and remote LSAN zone entries 26

27 CLI commands -- IOA Show fip-snooping fcf Show fip-snooping enode Show fip-snooping session interface vlan id Show interface tex/x dcbx detail Show fip-snooping config Show interface tex/x pcf/ets summary/detail/statistics Show fip-snooping statistics interface (vlan id, port/slot, port channel) Show fip-snooping system Show dcb stack-unit 0 Show cam mac stack unit 0 port set 0 Shows forwarder information Shows all hosts/cna s that logged into FCF Shows information on fip-snooped sessions on specific vlan Shows details of dcbx on that port. Shows fip snooping status and configured FC-MAP values Show details about ets or pfc for that port Shows statistics on the FIP packets snooped on all interfaces,including VLANs, physical ports, and port channels. Shows fip snooping global mode, number of FCoE VLAN s, FCF s, Enodes, and active sessions Shows dcb status, pfc port count, and pfc queue count Shows Vlan id, MAC address, and ports Table 2. Infrastructure versions Firmware information for the infrastructure components used in creating this document are as follows: Infrastructure Brocade a Brocade IOA M620 Server Compellent Array Firmware Revision Table 3. BOM infrastructure list Infrastructure Component BOM Description Brocade 5300 BASE,SWT,80PRT,FC8,8G,5300,BRD Brocade BASE,SWT,32PRT,F-R,VDX IOA SWT BOX,56P,10/40G,I/O-AGTR M620 Server PowerEdge M620 Blade Server Broadcom 57810S CNA CRD,NTWK,BCOM,10G,DP,57810S,KR Compellent Array Compellent SC040 (Series 40) Fiber Optic Cabling OM3 (25 Meter) Dell Optics - Ethernet GP-QSFP-40GE-ISR-40GBase-SR4 Brocade Optics - Ethernet GE SR Brocade Optics Fibre Channel G SW 27