Home

BrocadeVCSFabric-TestCases_V1-0_2013-02

1. 3 2 6 show vnetwork dvs show vnetwork dvs shows the distributed virtual switch information 3 2 7 show vnetwork dvpgs show vnetwork dvpgs command shows the distributed virtual port group information Strategic Solutions Lab Page 29 BROCADE 23 4 Brocade VCS Fabric Layer 3 Features There are a number of methods that an end host can use to determine its first hop router to a particular destination IP address These include a dynamic routing protocol such as OSPF or a statically configured default route Running a dynamic routing protocol on every end host may be infeasible for a number of reasons Neighbor or router discovery protocols may require active participation by all hosts on a network The use of a statically configured default route is quite popular it minimizes configuration and processing overhead on the end host and is supported by virtually every host s IP implementation The Virtual Router Redundancy Protocol VRRP is designed to eliminate the single point of failure inherent in a static default routed environment The next sections review OSPF and VRRP E configuration for a VCS Fabric of VDX switches These Layer 3 routing protocols were first introduced with NOS release 3 O 4 1 OSPF OSPF is a link state routing protocol designed to be run within a single Autonomous System Each OSPF router maintains an identical database describing the Autonomous System s topology From this database a routing table i
2. A network administrator can assign a virtual IP address to the entire VCS Fabric The virtual IP address is always tied to the VCS Fabric coordinator switch If the coordinator switch fails a new coordinator is automatically re elected and the virtual IP address fails over to it Configure the virtual IP address for the VCS Fabric RB1 conf t RB1 vcs virtual ip address ipv4 address prefix Length RB1 exit Strategic Solutions Lab Page 79 BROCADE 23 9 3 In band management via VLAN Physical or Port Channel Interfaces In band management can be configured on VLAN physical or port channel interfaces The in band management test verifies connectivity and functionality of in band management 9 3 1 Configure In band Management via VLAN RB1 conf t RB1 int vlan 2 RB1 ip address ipv4 address prefix Length RB1 ip mtu 1200 RB1 arp ageing timeout 300 RB1 do clear arp cache no refresh RB1 ip proxy arp RB1 exit RB1 show ip int vlan 2 9 3 2 Configure In band Management via Physical Interface RB1 conf t RB1 int te 1 0 1 RB1 ip address ipv4 address prefix Length RB1 ip mtu 1200 RB1 arp ageing timeout 300 RB1 do clear arp cache no refresh RB1 ip proxy arp RB1 exit RB1 show ip int te 1 0 1 9 3 3 Configure In band Management via Port Channel RB1 conf t RB1 int po 2 RB1 ip address ipv4 address prefix Length RB1 ip mtu 1200 RB1 arp ageing timeout 300 RB1 do clear arp cache no refresh
3. DT Failover Time us LAG T997 45 475 45 49 576 06 50 204 51 68 14 9 43 DS 64 Bytes LAG 50 129 53 93 81 19 38 19 38 49 826 46 50 266 63 49 573 90 9000 Bytes LAG 1518 Bytes ISL Trunk 64 Bytes ISL Trunk 123 123 2 46 qo 0 00 0 00 4 92 1518 Bytes These tests demonstrate the superiority of a Brocade ISL Trunk compared to LAG for link utilization latency and link resiliency ISL Trunk 9000 Bytes Strategic Solutions Lab Page 18 BROCADE 23 2 Automatic Migration of Port Profiles VCS Fabric includes the Automatic Migration of Port Profile AMPP feature that automates network configuration changes when VM migration occurs An AMPP policy is defined for a Port Group and then the Port Group is associated with MAC addresses This means security and network policies are defined once and are enforced fabric wide They are not limited to a single port on a single switch In a dynamic environment with VM migration AMPP the policies in the physical network always apply to the VM MAC no matter what port on a VCS Fabric that traffic appears on The following tests are based on the test plan used by Brocade for verification of the AMPP feature The diagram below shows an example of the test topology 2 1 Topology used HES Datastore amp Brocade 8000 EE 7 118 0 419 04 0 8 11803 119 013 VDX 6720 60 _ E VDX 6720 60 I E PA i A VDX 671048 VOX 6204 VDX 6720 24 ees
4. RB1 ip proxy arp RB1 exit RB1 show ip int po 2 9 4 Supportsave Automation The supportsave interactive command is used for data collection by the Brocade Technical Assistance Center TAC Supportsave functionality can be automated to interactively upload the data collected during a supportsave to a USB drive or external host by using the copy support interactive command This test verifies the support interactive command automates data collection available from a supportsave 9 4 1 Supportsave to a USB drive RB1 usb on RB1 copy support usb directory support directory Strategic Solutions Lab Page 80 BROCADE 23 9 4 2 Supportsave to an External Host RB1 copy support interactive Server Name or IP Address Protocol ftp scp User Password Directory VCS support y n y 9 5 Network Time Protocol NTP and Local Clock NTP Network Time Protocol is used to ensure consistent configuration of system time stamps using an external time source The NTP test confirms NTP functionality in the VDX platform If a time server is not available the local system clock can be configured including the time zone 9 5 1 Verify NTP Operation RB1 conf t RB1 ntp server 192 168 222 180 RB1 exit RB1 show clock rbridge id 1 2012 05 28 18 04 29 Europe Madrid RB1 show ntp status rbridge id 1 active ntp server is 192 168 222 180 9 5 2 Verify Local Clock Operation RB1 conf t RB1 no ntp server 192 168 222 1
5. 4 FCR6510 root fcrphydevshow Device WWN Physical Exists PID in Fabric 10 15 7e 00 11 0d 00 00 02 0433e4 120 10 00 00 05 33 48 71 8a c92b00 lt Truncated gt Total devices displayed 8 Verify Shared Devices From the VCS Edge Fabric 1 Verify the translate domain of the SAN edge fabric is seen in the VCS Fabric and reflects the correct FID In the below example fcr_xd_1_10 is the translate domain for the SAN edge fabric with FID 10 RB201 68 fc24 show fabric all VCS Id 8192 Strategic Solutions Lab Page 5 BROCADE 23 Config Mode Local Only Rbridge id WWN IP Address Name 50 50 00 51 ED 2D C0 1E 78 0 0 0 0 fcr fd 50 60 50 00 53 31 37 A3 EE 78 0 0 0 0 fcr fd 60 201 10 00 00 05 33 6F 3C 6A 10 20 52 68 RB201 68 fc24 202 10 00 00 05 33 6F 3A 1A 10 20 52 69 gt RB202_69 fc60 The Fabric has 5 Rbridge s Verify the LSAN Zone member from the SAN edge fabric is correctly reflected in the name server of the VCS Fabric The command Show name server zonemember wwn lt WWN gt shows the information of the corresponding zoned WWN that exists on the name server RB201 68 fc244 show name server zonemember wwn 10 00 00 05 33 48 71 8a PID c92b00 Port Name 10 00 00 05 33 48 71 8A Node Name 20 00 00 05 33 48 71 8A FCAs FCP PortSymb 78 Brocade 1020 2 3 0 2 TBW2K8X6455 Windows Server 2008 R2 Datacenter N A NodeSymb NULL Fabric Port Name 20 2B 00 05 33 6F 3C 6A Device type Physical Initi
6. Domain for a given FCR FCR6510 root portcfgexport 28 a 1 f 120 m 5 d 60 2011 03 12 07 36 30 FCR 1071 616 FID 128 INFO FCR6510 Port 28 is changed from non FCR port to FCR port FCR6510 root portcfgexport 29 a 1 f 120 m 5 d 60 FCR6510 root portcfgexport 30 a 1 f 120 m 5 d 60 FCR6510 root portcfgexport 31 a 1 f 120 m 5 d 60 3 Enable the ports FCR6510 root portenable 28 FCR6510 root portenable 29 FCR6510 root portenable 30 FCR6510 root portenable 31 4 Verify EX ports are correctly configured FCR6510 root portcfgexport 28 Port 28 info State NOT OK Pid format Not Applicable Front WWN 50 00 53 31 37 a3 ee 78 Fabric Parameters Auto Negotiate Strategic Solutions Lab Page 69 BROCADE 23 R A TOV Not Applicable E D TOV Not Applicable Authentication Type None DH Group N A Hash Algorithm N A Edge fabric s primary wwn N A Edge fabric s version stamp N A This port can now be connected to the VCS Edge Fabric Verify all EX ports are correctly configured 5 Physically attach the Inter Fabric Link IFL from the Fibre Channel Router to the VDX 6730 switch in the VCS Fabric NOTE A Fibre Channel Router can interconnect multiple fabrics EX ports attached to more than one Edge Fabric have a different Fabric ID for each Edge Fabric Configuring EX Ports in Brocade Native Mode Mode O for Fibre Channel SAN Edge Fabric 1 Disable the ports on the Fibre Chan
7. IETF standard monitoring specification that allows various network agents and console devices to exchange network monitoring data The RMON specification defines a set of statistics and functions that can be exchanged between RMON compliant console managers and network probes The RMON test verifies supported RMON functionality Create an RMON event an Ethernet group statistics collection and an RMON alarm that tests every sample for a rising threshold RB1 conf t RB1 rmon event 1 description TestRMON RB1 interface te 1 0 1 RB1 rmon collection stats 200 RB1 rmon alarm 5 1 3 6 1 2 1 16 1 1 1 5 65535 interval 30 absolute rising threshold 95 event 1 RB1H exit 9 12 RADIUS Remote Authentication Dial In User Server Service RADIUS is used to manage authentication authorization and accounting AAA services centrally The supported management access channels that integrate with RADIUS are serial port Telnet and SSH The RADIUS test validates RADIUS access accounting and interoperability Configure a RADIUS server for authentication and verify the configuration RB1 conf t RB1 radius server host ip address protocol pap key shared secret string timeout 10 retransmit 3 RB1 exit RB1 show running config radius server 9 13 Terminal Access Controller Access Control System Plus TACACS The Terminal Access Controller Access Control System Plus TACACS is a protocol used in AAA server environments that consist of a central
8. Target is attached NOTE Use identical LSAN Zone names for ease of identification and administration however this is not a requirement For complete details on FOS Zoning and LSAN Zone configuration refer to the Fabric OS Administrator s Guide for the FOS release T 5300 114 FID128 root zonecreate LSAN host target _1 10 00 00 05 33 48 71 8a 15 7e 00 11 0d 00 00 02 T 5300 114 FID128 root cfgcreate cfg fid10 LSAN host target 1 T 5300 114 FID128 root cfgenable cfg fid10 T 5300 114 FID128 root cfgshow lt Truncated gt Strategic Solutions Lab Page 67 BROCADE 23 1 2 6 Enabling Fibre Channel Routing FCR Service on FOS Switch In order for the VCS Fabric to connect to Fibre Channel SAN the VDX6730 Fibre Channel ports should be connected to a FOS Switch running Fibre Channel Routing Service FCR To establish an Inter fabric link the Fibre Channel ports on the FCR connected to the VDX 6730 must be configured as EX ports for Brocade NOS Fabric Mode or mode 5 NOTE Fibre Channel routing is a licensed feature that requires the Integrated Routing IR license for sharing between Fibre Channel devices in two Fibre Channel SAN fabrics The IR license is NOT required for sharing devices in a VCS Fabric and a Fibre Channel SAN fabric or between two VCS Fabrics Without an IR license device sharing will be blocked between Fibre Channel devices in Fibre Channel Edge Fabrics For details on FCR licensing supported platforms and
9. lacp timeout long RB2 no shutdown RB2 int te 2 0 7 RB2 channel group 20 mode active type standard RB2 lacp timeout long RB2 no shutdown RB2 exit Then configure the port channel interface as a trunk interface for VLAN 1 RB1 conf t RB1 int po 20 RB1 description vlag to n7k RB1 switchport RB1 switchport mode trunk RB1 switchport trunk allowed vlan 1 RB1 no shutdown RB1 exit RB1 conf t RB1 int po 20 RB1 description vlag to n7k RB1 switchport RB1 switchport mode trunk RB1 switchport trunk allowed vlan 1 RB1 no shutdown RB1 exit Strategic Solutions Lab Page 44 BROCADE Next set up the port channel on the appropriate interfaces of the Nexus 7000 vPC pair and connect the cables between the Nexus 7000 vPC pair and the VCS Fabric Verify that the port channel interfaces are up on both RBridges Start traffic between a server attached to the Nexus 7000 vPC pair and another one connected to the VCS Fabric and verify the traffic is load balanced across all the vLAG members based on the hashing algorithm 5 1 2 Create a vLAG Between VCS Fabric and a Server The same way a Layer 2 Ethernet switch can establish a LAG terminating on multiple VCS Fabric members a server can configure an active active NIC team that terminates on two VCS Fabric members First assign two interfaces on different VDX switches to the new port channel Define the port channel as an access interface for VLAN
10. show license 2 Add the FCoE license RB201 68 fc24 license add licStr lt FCOE BASE LICENSE STRING For license to take effect it may be necessary to disable enable ports or switch 3 Disable enable switch RB201 68 fc24 chassis disable Are you sure you want to disable all chassis ports now y n y Strategic Solutions Lab Page 56 BROCADE 23 RB201 68 fc24 RB201 68 fc24 Chassis enable 4 Verify the FCoE license is added correctly RB201 68 fc24 show license rbridge id 201 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX FCoE Base license Feature name FCOE BASE XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 6 2 Enabling FCoE port on interface TenGigabitEthernet 1 Configure FCoE on the TenGigabitEthernet interface RB201_68_fc24 configure terminal Entering configuration mode terminal RB201_68_fc24 config interface TenGigabitEthernet 2901 0 19 RB201_68_fc24 conf if te 201 0 19 fcoeport default RB201 68 fc24 conf if te 201 0 19 no shutdown 2 Verify the FCoE configuration RB201 68 fc24 show running config interface tengigabitethernet 201 0 19 interface TenGigabitEthernet 201 0 19 fabric isl enable fabric trunk enable no shutdown l 3 Verify the FCoE device login and note the device WWN and the corresponding FCoE Port interface RB201_68_fc24 show fcoe login Total number of Logins 1 NOTE Repeat step 2 for each and every port where FCoE CNA FCoE targets are connected 6 3 Creating LUNs Cre
11. 00 05 33 6F 3A 1A 10 20 52 69 RB202 69 fc60 The Fabric has 5 Rbridge s Verify Connectivity From Fibre Channel SAN Edge Fabric 1 Verify the corresponding E port on the Fibre Channel SAN switch in the Edge Fabric the Front Domain ID of the Fibre Channel router and the Translate domain of the VCS Edge Fabric where the FCoE device Host is attached This device WWN is the one added to the LSAN Zone T 5300 114 FID128 root switchshow switchName T 5300 114 switchType 64 3 switchState Online switchMode Native switchRole Subordinate switchDomain 4 switchId Fffc04 switchWwn 10 00 00 05 33 41 39 02 zoning ON cfg fid10 switchBeacon OFF FC Router OFF Allow XISL Use OFF LS Attributes FID 128 Base Switch No Default Switch Yes Address Mode 0 Index Port Address Media Speed State Proto lt Truncated gt T 5300 114 FID128 root islshow 1 0 gt 10 00 00 05 1e 0f 28 16 30 T 300 115 sp 8 000G bw 8 000G 2 1 gt 1 10 00 00 05 1e 0f 28 16 30 T 300 115 sp 8 000G bw 8 000G 3 2 2 10 00 00 05 1e 0f 28 16 30 T 300 115 sp 8 000G bw 8 000G 4 3 3 10 00 00 05 1e 0f 28 16 30 T 300 115 sp 8 000G bw 8 000G 5 72 gt 200 50 00 51 ed 2d c0 1e 0a 50 fcr fd 50 sp 8 000G bw 32 000G TRUNK T 5300 114 FID128 root fabricshow Switch ID Worldwide Name Enet IP Addr FC IP Addr Name 1 fffc01 50 00 51 ed 2d ce 1f b2 0 0 0 0 0 0 0 0 fcr_xd_1_20 2 fffcO2 50 00 51 ed 2d ce 1f c9 0 0 0 0 0 0 0 0 fcr xd
12. 1 Using the server adapter management tools configure an active active NIC team and connect the server to the port channel member interfaces Verify the port channel is up on both RBridges Strategic Solutions Lab Page 45 BROCADE 23 RB3 show po 40 Establish traffic between SRV3 and another server in the VCS Fabric and verify that traffic is load balanced between the two vLAG members based on the hashing algorithm 5 2 Integration with Classic Layer 3 IP The purpose of this test is to demonstrate Layer 2 Layer 3 interoperability of OSPF within a VCS Fabric using NOS 3 x 5 2 1 Test Topology The following diagram shows the topology for testing OSPF in a VCS Fabric OSPF support was introduced with NOS release 3 0 0 MCT TESS cllk cc c d M 5 2 2 Build Two Node VCS Fabric with OSFP 5 2 2 1 Setting Up OSPF VRRP and VE between two VDXs Note OSPF is configured under the RBridge ID VDX6720 75 interface vlan 100 shutdown Strategic Solutions Lab Page 46 BROCADE VDX inserted this and the next line 5 2 2 2 Verify VCS Fabric is Running OSFP VRRP and VE 5 2 2 2 1 OSFP Check 5 2 2 2 2 VRRP Check Strategic Solutions Lab Page 47 BROCADE 5 2 2 2 3 VE Check 5 2 2 3 Create a vLAG Between VCS Fabric and the PC on Nexux 7K Configure a vLAG on the selected VDX switches This is automatically inserted by NOS lt VDX inserted this automatically Stra
13. 16 Port 16 info State NOT OK Pid format Not Applicable Front WN 50 00 53 31 37 a3 ee 0a Fabric Parameters Auto Negotiate R A TOV Not Applicable E D TOV Not Applicable Authentication Type None DH Group N A Hash Algorithm N A Edge fabric s primary wwn N A Edge fabric s version stamp N A This port can now be connected to the Fibre Channel SAN Edge Fabric Verify that all EX ports are correctly configured e Physically attach the IFL from the Fibre Channel Router to the Fibre Channel SAN Edge Fabric switch switch T 5300 1 2 8 Verifying Connectivity Between the Backbone and Edge Fabrics Once the cables between the FCR and VDX 6730 switch in the VCS Fabric and the FCR and Fibre Channel SAN Edge Fabric switch are physically attached verify connectivity Verify Connectivity From FCR 1 Verify the EX port Edge Fabric ID VCS FC name of the edge VDX 6730 switch and name of the edge FC fabric switch are correct FCR6510 root switchshow lt Truncated gt 16 16 061300 id N8 Online fabric id 10 Trunk master 17 17 061000 id N8 Online Trunk port master is Port 16 18 18 061200 id N8 Online Trunk port master is Port 16 19 19 061100 id N8 Online Trunk port master is Port 16 lt Truncated gt 28 28 061c00 id N8 Online fabric id 120 Trunk master 29 29 O061f00 id N8 Online Trunk port master is Port 28 30 30 06le00 id N8 Online Trunk port master is Port 28 31 31 061d00 id
14. 1880 5780 1880 6340 1900 6700 1920 24300 RunD012 1518 h mb wh mh o mh mh o mh mh mh k 7 91 4447115 319 27 91 3754056 400 27 91 2294146 612 27 91 640936 509 57 81 57 81 57 81 57 081 57 81 781 249 952 416 991 128 217 240 200 110 751 872 75 091 160 12 818 736 1 375 483 524 791 249 952 416 931 126 217 340 200 110 751 872 88 542 260 75 081 160 12 819 736 D 0 00 D 0 00 D DD D 0 00 DH 0 00 D 0 00 D 0 00 D 0 00 Table 2 RFC2889 Fully Meshed Aggregate Results for Spanning Tree Network The following graphs compare the VCS Fabric and RSTP network performance at different frame sizes using the RFC 2889 Fully Meshed performance test cases Strategic Solutions Lab Page 10 BROCADE 23 VCS Fabric vs Spaning Tree RFC2889 Fully Meshed VCS Fabric vs Spaning Tree RFC2889 Fully Meshed Throughput in 4 Switches Mesh Average Latency in 4 Switches Mesh 120 12000 10000 E 8000 4 6000 B VCS Fabric B VCS Fabric mRSTP 4000 m RSTP Bi 0 0 64 128 256 64 128 256 512 512 1024 1280 1518 2500 9000 1024 1280 1518 2500 9000 Frame Size 8 oo o gt o Average Latency ns Througput of Line Rate eo o N o Frame Size Public Cloud Simulation Test The cloud simulation test determines the performance of the DUT when forwarding a mixture of north south and east west traffic typical of cloud computing applications Test p
15. 2 Backup routers as well send backup advertisement messages which are different from master advertisement message Following are VRRP and VRRP E configuration highlights on a Brocade VCS router a Both VRRP and VRRP E protocol can be enabled at the same time on router b Both VRRP and VRRP E sessions can be configured on an interface at the same time c VRRP and VRRP E sessions cannot share the same VRID in a broadcast domain 4 2 2 VRRP E Parameters and Configuration 4 2 2 1 Short path forwarding Feature In standard VRRP packets destined to IP subnets which are local to the standby router cannot be routed by the standby These packets destined to the standby router with DA VMAC would be switched to the master and the master might route the packet back to the standby for routing Brocade uses short path forwarding to enhance this behavior in a VRRP E configuration The standby router will try to route frames with DA VMAC Additionally the VRRP virtual IP subnet is not configured Strategic Solutions Lab Page 34 BROCADE 23 as a local subnet on the standby instead a routing entry for the virtual IP subnet is installed pointing toward the master For test short path forwarding or VRRP E Active Active configurations please refer to test case 2 in section 4 2 4 2 Short path forwarding specific configurations M8_159 config rbridge id 159 M8 159 config rbridge id 159 4 protocol vrrp M8 159 config rbridge id 159 4
16. 2 100 Strategic Solutions Lab Page 74 BROCADE 23 Translate Domain 4 fffc04 10 00 00 05 33 41 39 02 10 20 52 114 0 0 0 0 T 5300 114 30 fffcle 10 00 00 05 1e 0f 28 16 10 20 52 115 0 0 0 0 T 300 115 50 fffc32 50 00 51 ed 2d c0 1e 0a 0 0 0 0 0 0 0 0 fcr fd 50e Front Domain of FCR6510 The Fabric has 7 switches 1 2 9 Verifying Devices are Correctly Shared Between Edge Fabrics Verify the connectivity between the VCS Edge Fabric and the Fibre Channel router Verify the proper LSAN Zones are configured for devices in the VCS Edge Fabric and the Fibre Channel SAN Edge Fabric Verify the Fibre Channel router shows the target and initiator devices are imported and shared between the Edge Fabrics Verify Shared Devices From the Fibre Channel Router 1 Verify the LSAN zoned devices attached to one edge fabric are successfully imported into the other edge fabric through the FCR FCR6510 root lsanzoneshow s Zone Name LSAN host target 1 10 00 00 05 33 48 71 8a 15 7e 00 11 0d 00 00 02 Fabric ID 120 Zone Name LSAN_host_target_1 10 00 00 05 33 48 71 8a 15 7e 00 11 0d 00 00 02 2 Verify the shared device WWNs and Proxy device PIDs and its corresponding Physical device PIDs FCR6510 root fcrproxydevshow Proxy WWN Proxy Device Physical State Created PID Exists PID in Fabric in Fabric 10 10 00 00 05 33 48 71 8a ua 120 Ee Imported 120 15 7e 00 11 0d 00 00 02 10 Imported lt Truncated gt Total devices displayed
17. 2 USO RET 84 9 14 3 Create RULES TO Ma ROIG G ENE 84 vo ed ES ENOI c X A 84 A 85 Strategic Solutions Lab Page v BROCADE 23 Introduction This document provides a series of test cases that demonstrate and validate features and functions provided in Brocade VDX Switches running Brocade Network Operating System NOS VDX switches include Brocade VCS Fabric technology that removes many of the limitations facing datacenter networks supporting virtualization cloud computing and ever larger amounts of data storage The test cases demonstrate the benefits of a VCS Fabric including improved performance availability and simple configuration and management and also show interoperability of a VCS Fabric with classic Ethernet environments using Spanning Tree Protocol STP For environments where Fiber Channel over Ethernet FCoE is used there are configuration and test cases covering FCoE and FCOE to Fibre Channel connectivity The commands listed in the various test cases are provided as working examples Other NOS commands may be accomplish similar test results Test cases do not cover every configuration step required to run a particular test but show key commands with sufficient description to create a complete test case It is expected that the engineer cond
18. 4 1 2 Melo ride OF OSPF 31 e e TE 33 4 2 1 MISBIPAIS VOR PEL aD iren Is ote EMI ieu ds rub IS U sete pane Goeecne exe ast met dead Ur IR RUUUEEE 33 4 2 2 VRRP E Parameters and Configuration EN 34 4 2 3 VRRP E Venticato n ana StQUSUCS sica o o oo o 38 4 2 4 TeSt SC AA eo oo o Or A 41 5 BROCADE VCS FABRIC INTEGRATION WITH CLASSIC ETHERNET Ae at en Sonia EEEE 44 5 1 INTEGRATION WITH CLASSIC LAYER 2 ETHERNET solo ias 44 5 1 1 Create a vLAG Between VCS Fabric and Nexus 7000 Core 44 5 12 Create a vLAG Between VCS Fabric and a Genera 45 5 2 INTEGRATION WITH CLASSIC LAYER Ebert eege deeg 46 Strategic Solutions Lab Page ii BROCADE 23 o o MOR ONG y P a aeene0setaenemsoeecaanuace 46 5 2 2 Build Two Node VCS Fabric with OSPERN 46 udo Create OSFP Neighbors Between Nexus 7000 and VU 50 A A c c 56 DE E e LICENSE E 56 6 2 ENABLING FCOE PORT ON INTERFACE TENGIGABITETHERNET seeeeee nennen nennen nnne nnn nnns 57 SC e TE KEE El E 57 64A DISCOVERING LUNS c 57 6 5 STARTING FCOE TRAFFIC THROUGH A WINDOWS Hoer 58 4 OOE TO FC BRIDGING sissisodan EAE ERREEN 60 b SUPPORTED TOROLOGIES aus 60 7 1 1 VCS Fabrics as Fibre Channel Edge Fabrics with Fibre Channel Backbone Fabric 60 1 1 2 Edge to Edge Sharing Using a Single Fibre Channel Backbone Fabric 61 1 1 3 Edge to Edge Sharing Ssing Dual Back
19. Fabric For devices to be shared between a VCS Fabric and a SAN Fabric via Fibre Channel routing Logical SAN LSAN Zoning should be used An LSAN Zone is similar to a traditional Fibre Channel zone and is created using the zoning tools but uses a special naming prefix LSAN LSAN Zones define which devices can send traffic to each other when they are located in independent fabrics either VCS Fabrics or SAN Fabrics NOTE Please refer Network OS Administrator s Guide v2 1 0 or higher for details on zoning configuration and administration LSAN zoning must be enabled in all fabrics that share devices to other fabrics e Edge to edge routing edge fabrics e Backbone to edge routing backbone and edge fabrics 1 View the default existing zoning configuration on any VDX switch in the VCS Fabric RB201 68 fc24 show running config zoning zoning enabled configuration cfg name zoning enabled configuration default zone access allaccess zoning enabled configuration cfg action cfg save 2 Have the list of WWNs of the devices to be shared between fabrics 3 Define the LSAN zone and add the WWNs of the devices to be connected between fabrics RB201 68 fc24 configure terminal Entering configuration mode terminal RB201 68 fc24 config amp t zoning defined configuration zone LSAN host target 1 Strategic Solutions Lab Page 66 BROCADE 23 RB201 68 fc24 config zone LSAN host target 1 4 member entry 10 00 00 05 33 48 71 8a RB201 68 fc2
20. MAC entries Enable the ports on RB1 and RB2 connected to the servers and configure them for access mode with Ping from VM1 to VM2 to create a traffic flow through the network and then check the MAC address table on each VDX switch RBi amp show mac address table Strategic Solutions Lab Page 6 BROCADE 23 RB2 show mac address table RB3 show mac address table Verify that the MAC addresses of VM1 and VM2 have been updated on RB3 even if it didn t participate in the forwarding of frames between the two virtual machines 1 6 Shortest path Forwarding ECMP and Load Balancing Brocade VCS Fabric is based on TRILL and Fibre Shortest Path First FSPF to provide shortest path forwarding between switches in the fabric This provides equal cost multipath ECMP forwarding when there are two or more equal cost Layer 2 paths between switches In addition Brocade hardware creates ISL Trunks that frame stripe all traffic across links in the ISL Trunks This provides the highest utilization of links in the ISL Trunk Verify there are two equal cost paths between RB1 and RB2 and one dual hop path through RB3 RB1 show fabric route topology Generate traffic between VM1 on RB1 and VM2 on RB2 To better show traffic load balancing across equal cost paths use a traffic generation tool such as lOMeter to create traffic between the two VMs instead of ping Verify the traffic uses the shortest path s in the fabric and that it is balanc
21. SMAC2 migrating to int te 0 0 5 from int te 0 0 1 and int te 1 0 10 Note the change in bridge ld Repeat this test case in Standalone mode as well 2 5 6 Multiple MACs From Different Ports to One Interface Using Different Port Profiles Verify that multiple MAC addresses associate to different port profiles resume traffic when migrated to a single interface It is expected that performance will be affected when they use the same physical interface Also note that the port profiles associated do not have any conflicting rules Example PP1 is associated to SMAC1 and PP2 is associated to SMAC2 SMAC1appears initially on int te 0 0 1 and SMAC2 appears on int te 0 0 10 Now both SMAC1 and SMAC2 migrates to int te 0 0 5 Then repeat the test with both SMAC1 and SMAC2 migrating to int te 0 0 5 from int te O O 1 and int te 1 0 10 Note the change in bridge ld Strategic Solutions Lab Page 26 BROCADE 23 3 VMware Network Automation 3 1 Configuring and Verifying vCenter NOS Integration In order for a VCS Fabric to detect the ESX hosts CDP has to be enabled on all the virtual switches and distributed virtual switches in the vCenter Inventory Refer to VMware KB article 1003885 for further details Step 1 Standard vSwitch Enabling CDP on virtual switches Login as root to the ESX ESXi Host Verify the current CDP settings root server root esxcfg vswitch b vSwitch1 down Enable CDP for a given virtual switch Possible
22. Strategic Solutions Lab Page 39 BROCADE Strategic Solutions Lab Page 40 BROCADE 23 4 2 3 4 Clear VRRP E Statistics M8 1594 clear vrrp statistics Possible completions interface Interface information session Session Output modifiers cr M8 1594 clear vrrp statistics interface Possible completions fortygigabitethernet FortyGigabit Ethernet interface gigabitethernet Gigabit Ethernet interface port channel Port channel interface tengigabitethernet TenGigabit Ethernet interface ve Ve interface M8 1594 clear vrrp statistics interface ve 10 Possible completions cr M8 1594 clear vrrp statistics interface ve 10 M8 1594 4 2 4 Test Scenarios 4 2 4 1 Test Case 1 Configure VRRP Over vLAG in a VCS Fabric This test verifies that VRRP traffic is forwarded appropriately VRRP within a VCS Fabric should be configured on VE interfaces which enable VRRP advertisement frames to be send over the VCS Fabric A typical example of VRRP deployment is shown below Layer 3 Cloud interface ve 100 ip addr 20 0 0 1 24 vrrp group 100 virtual ip 20 0 0 100 interface ve 100 ip addr 20 0 0 2 24 vrrp group 100 virtual ip 20 0 0 100 VCS Cloud Typical VRRP deployment in VCS cluster In the above R1 and R2 form a VRRP group with R1 as Master and R2 as Backup VRRP advertisement frames are broadcast by R1 on VLAN 100 Since the VCS Fabric ports on all of the VDX switches forward all VLAN traffic R1 and R2 a
23. Verify all ESX ESXi host s uplinks connected are shown Switch show vnetwork hosts Host Uplink Name Uplink MAC d Virtual Switch Switch Interface ESX 4921 vmnic0 e4 1f 13 43 54 90 vSwitchO vmnic2 00 1b 21 8f 4a f0 dvSwitch Production 115 0 5 vmnic4 00 05 33 26 3e ba vSwitch3 115 0 1 vmnic5 00 05 33 26 3e bb dvSwitch Production ESX 4922 vmnic0 e4 1f 13 43 95 5c vSwitchO vmnic2 00 05 33 26 2d 90 dvSwitch Production 115 0 10 vmnic3 00 05 33 26 2d 91 dvSwitch Production 115 0 11 vmnic5 00 05 1e eb f9 94 vSwitch3 115 0 2 NOTE In Fabric Cluster FC mode only the locally connected interface information will be shown For example in the above output ESX 4921 vmnicb is not connected to this node Rbridge ID 115 3 2 2 Verify show vnetwork vms Shows All Virtual Machines in vCenter show vnetwork vms will display the virtual machine information including host information and associated MAC addresses of all VMs vNIC MACs These MAC are automatically associated to the respective Port Profile Please refer to the show vnetwork vmpolicy command for more details Switch show vnetwork vms Virtual Machine Associated MAC IP Addr Host CentOS 4921 00 50 56 8e 00 4b ESX 4921 englab brocade com 00 50 56 8e 00 4d ESX 4921 englab brocade com CentOS 4922 00 50 56 8e 00 50 ESX 4922 englab brocade com 00 50 56 8e 00 51 ESX 4922 englab brocade com 3 2 3 Verify show vnetwork vmpolicy macaddr Shows all VM vmkernel MAC
24. a Port in a Different Switch in the VCS Fabric 25 2 5 3 Multiple MACs From One Port to Another port in the Same Port Profile 25 2 5 4 Multiple MACs From One Port to Another Port in a Different Port Profile 25 Strategic Solutions Lab Page i BROCADE 23 210 0 Multiple MACs From Different Ports in Same Port Profile to Port in Same or Different Switch 25 2 5 6 Multiple MACs From Different Ports to One Interface Using Different Port Profiles 26 3 VMWARE NETWORK AUTOMATION eersee ener nere enn RECKEN Ken 21 3 1 CONFIGURING AND VERIFYING VCENTER NOS INTEGRATION ENEE 27 3 2 VERIFYING THAT DATA IS GATHERED FROM VCENTER BY NOS 28 3 2 1 Verify show vnetwork hosts Shows All Hosts Discovered by vCenter 28 3 2 2 Verify show vnetwork vms Shows All Virtual Machines in vCenter 28 3 2 3 Verify show vnetwork vmpolicy macaddr Shows all VM vmkernel MAC Addresses 28 3 2 4 c ge hueso uc e r EEE 29 3 2 5 SNOW VACTWONK epes 29 3 2 6 SuOW VNEIN OIE ONS iora T 29 3 2 1 SNOW Ruiz e qod qE 29 4 BROCADE VCS FABRIC LAYER 3 FEATURES 1 eere ren 30 MEE m o o A oo E ee en ee ee 30 4 1 1 TOPOLOV USGO M O Y 30
25. above tests for a Tengigabit Ethernet Strategic Solutions Lab Page 24 BROCADE 23 b LAG VLAG 10G Note For LAG and VLAG user needs to go to the individual member interface and execute the fcoeport default command option ii 2 5 Migration of Virtual Machine s and validation of AMPP 2 5 1 Single MAC from One Port to Another Port in the Same Switch Verify the associated Port Profile moves with the VM MAC address when it migrates to a different physical port in the same switch Verify traffic resumes from the VM within 250ms Example Port Profile 1 is associated with SMAC1 SMAC1 appears initially on int te 0 0 1 and migrates to int te 0 0 5 Repeat this test case in Standalone mode as well 2 5 2 Single MAC From One Port to a Port in a Different Switch in the VCS Fabric Verify the associated Port Profile moves with the VM MAC address when it migrates to a port in a different switch in VCS Fabric Verify traffic resumes from the VM within 250ms Example PP1 is associated to SMAC1 SMAC1 appears initially on int te O 0 1 and migrates to int te 1 0 5 2 5 3 Multiple MACs From One Port to Another port in the Same Port Profile Verify that multiple MAC addresses all associated to same port profile will resume traffic when some of them are migrated to a different physical interface in the same switch and some to a port in a different switch Example PP1 is associated to SMAC1 as well as SMAC2 SMAC1and SMAC2 appea
26. acl ABC Strategic Solutions Lab Page 88
27. configuration refer to the Fabric OS Administrator s Guide for the FOS release It is recommended that Physical connections between the VCS Fabric and the FCR be done after the FCR EX ports are configured Viewing and Configuring FCR 1 Check whether the FC Routing service is enabled FCR6510 root fosconfig show iSCSI service Service not supported on this Platform iSNS client service Service not supported on this Platform Virtual Fabric disabled Ethernet Switch Service Service not supported on this Platform 2 Enable the FC Routing service FCR6510 root fosconfig enable fcr 2011 11 17 05 50 41 FCR 1069 306719 INFO FCR6510 The FC Routing service is enabled FC Routing service is enabled 3 Verify the FC Routing service is enabled FCR6510 root fosconfig show iSCSI service Service not supported on this Platform iSNS client service Service not supported on this Platform Virtual Fabric disabled Ethernet Switch Service Service not supported on this Platform 1 2 1 Configuring Inter fabric link IFL on the Fibre Channel Router FCR To create an Inter fabric link IFL between the Fibre Channel ports on the VDX 6 30 and the ports on the Fibre Channel Router the corresponding Fibre Channel ports on the FCR must be configured to support Brocade NOS Fabric Mode or Mode 5 The Fiber Channel ports on the FCR connected to the Fibre Channel SAN Edge Fabric switches need not specify any mode Mode O is the defau
28. int ve 10 M8_159 config Ve 10 vrrp extended group 128 M8_159 config vrrp extended group 128 short path forwarding M8_159 config vrrp extended group 128 exit 4 2 2 2 Track Port and Priority Command Ports other than the VRRP instance interface can be tracked for up down events When port tracking is enabled in a VRRP instance the tracked port s link status is monitored When a link down event is detected on a tracked port the track priority is subtracted from the current router s priority value Similarly when link up event is detected on the tracked port the track priority is added to the router s current priority value This dynamic change of router priority can trigger mastership switchover if the preemption is enabled The maximum number of interfaces that can be tracked for a virtual router is 16 Track port and priority specific configurations M8_159 config rbridge id 159 M8 159 config rbridge id 159 4 protocol vrrp M8 159 config rbridge id 159 4 int ve 10 M8 159 config Ve 10 s vrrp extended group 128 MS 159 config vrrp extended group 128 4 track port tengigabitethernet 1 1 48 priority 20 MS 159 config vrrp extended group 128 4 track port fortygigabitethernet 1 5 48 priority 20 M8 159 config vrrp extended group 128 4 track port port channel 10 priority 20 M8_159 config vrrp extended group 128 exit 4 2 2 3 Hold Time Command Hold time is the maximum number of seconds that elapse before a high priority backup router pr
29. name test profile status Port Profile PPID Activated Associated MA Interface Test profile 2 Yes 0005 1ed7 8def Te 236 0 8 VDX 2 4 Validation of Port Profile Capabilities VLAN ACL QoS and FCoE port Please refer section 3 1 3 for commands to create activate associate port profiles 2 4 1 Validation of VLAN Configuration The following tests verifiy the switchport capabilities enabled on a physical port once a Port Profile is successfully applied Setup Use Topology in section 3 1 1 Use following commands to change VLAN allow disallow combinations Example To set a port profile for accepting untagged frames alone VDX_49113 config port profile test_profile VDX_49113 config port profile test_profile vlan profile VDX_49113 config vlan profile switchport VDX_49113 config vlan profile switchport mode access VDX_49113 config vlan profile Set a VLAN profile to a desired configuration Access Trunk allow add remove etc VDX 49113 config port profile test profile VDX_49113 config port profile test_profile vlan profile VDX 49113 config vlan profile s switchport Possible completions access Set the Layer2 interface as Access mode Set mode of the Layer2 interface trunk Set the Layer2 interface as trunk cr VDX_49113 config vlan profile switchport trunk Possible completions allowed Set the VLANs that will Xmit Rx through the Layer2 interface native vlan Set the native VLAN to classify untagged tr
30. output does not show the configured ports as FC EX Port or the portcfgexport lt port gt shows State NOT OK or the VDX 6730 shows the corresponding Fibre Channel port on show fabric islports output as 53 Fi 201 0 5 Down Down ESC NOS incompatible Then perform a shut no shut on the Fibre Channel interface on VDX 6730 as shown below and re verify RB201 68 fc24 configure terminal Strategic Solutions Lab Page 72 BROCADE 23 Entering configuration mode terminal RB201 68 fc24 config in fi 201 0 5 RB201 68 fc24 config FibreChannel 201 0 5 shut RB201 68 fc24 config FibreChannel 201 0 5 no shut N View all edge fabric switch names and ensure links are working as expected FCR6510 root gt fcrfabricshow FC Router WWN 10 00 00 05 33 13 7a 3e Dom ID 6 Info 10 20 52 197 FCR6510 EX Port FID Neighbor Switch Info enet IP WWN name 21 20 10 20 52 116 10 00 00 05 1e c3 1e 14 T 7800 116 Truncated Verify Connectivity From VCS Edge Fabric 1 Verify the corresponding Fibre Channel E port on the VDX 6730 the Front Domain ID of the FCR and the Translate Domain of the SAN Edge Fabric where the Fibre Channel device Target is attached This device WWN is the one added to the LSAN Zone RB201 68 fc24 show fabric islports Name RB201 68 fc24 Type 96 2 State Online Role Fabric Subordinate VCS Id 8192 Config Mode Local Only Rbridge id 201 WIN 10 00 00 05 33 6f 3c 6a FCF MAC 00 0
31. the same VLAN Source MAC in VRRP control packets is virtual MAC address Gratuitous ARP request is sent only once when the VRRP router becomes master When track port goes down the current priority is reduced to the track port priority Preemption is turned on by default Even if preemption is disabled it does not affect the owner router since owner preempts the active master Mastership switchover causes unnecessary temporary network disruption VRRP control packets have IP protocol type as 112 reserved for VRRP and are sent to VRRP multicast address 224 0 0 18 Backup routers do not send any advertisement messages Only master sends the advertisement message Table 1 VRRP and VRRP E comparison table BROCADE 23 02 e0 52 is Foundry s 24 bit MAC OUI vrid is user configured 1 byte value Same VRID can be used for two or more virtual router groups in the same VLAN Source MAC in VRRP control packets is physical MAC address Gratuitous ARP requests are sent every 2 seconds by the virtual router master This is because VRRP control packets do not use virtual MAC address and thus virtual MAC address entry in interconnecting switches might get aged out When track port goes down the current priority is reduced by the track port priority Preemption is turned off by default and there is no owner VRRP packets are UDP packets destined to port 8888 and are sent to all router multicast address 224 0 0
32. values here are advertise or both root server root esxcfg vswitch B both vSwitch1 Step 1 Distributed vSwitch Distributed switches get CDP capability using following steps a Connect to vCenter Server using the vSphere Client b Inthe vCenter Server home page click Networking c Right click the vDS and click Edit Settings d Select Advanced under Properties e Using the checkbox and the dropdown change the CDP settings Step 2 Adding the vCenter IP in NOS In order to authenticate with a specific vCenter configure the URL user name and password properties on the VDX switch Switch config vcenter MYVC url https 125 2 2 2 username user password pass Step 3 Activating vCenter After adding the vCenter activate the configured vCenter instance switch confio veenter MYVC activate Right after activating vCenter for the first time NOS will start the virtual asset discovery process User will be able to see the current status using the show vnetwork vcenter status command Switch show vnetwork vcenter status vCenter Start Elapsed sec Status MYVC 2011 09 07 14 08 42 10 Verify that once discovery process is complete In Progress will become Success Strategic Solutions Lab Page 27 BROCADE 23 3 2 Verifying That Data is Gathered from vCenter by NOS 3 2 1 Verify show vnetwork hosts Shows All Hosts Discovered by vCenter show vnetwork hosts will display ESX ESXi host information
33. y VOX e E e met y N DX 5720 24 NONE Platforms prominently used Description VDX 6270 24 VDX6730 24 VDX with 24 106 ports VDX 6270 60 VDX6730 60 VDX with 60 106 ports VDX 6210 48 DES 48 1G ports server facing and 6 10G Strategic Solutions Lab Page 19 BROCADE 23 2 2 AMPP Test Considerations Any explicit reference to VDX 87xx and NOS 3 0 0 is hardware software currently under test not yet fully qualified Below are considerations to keep in mind when testing the AMPP feature a The AMPP feature can be tested with all VDX products VDX 6720 both 24 and 60 ports VDX6730 both 24 and 60 ports VDX6710 VDX 8710 4 slot and 8 slot b Referto release notes for full list of features and supported scalability values c Capability to provision VLAN allow disallow ability permit deny data traffic using standard extended ACLs and provision traffic scheduling prioritization using Layer 2 QoS capabilities all built into a port profile d Special capability to give different ACL treatments to different MACs on same interfaces physical LAG at the same time on VDX 87xx feature under test in NOS3 0 0 e Port profile s can follow the MAC address s associated to it when the Virtual Machine migrates VMotion from one physical interface to another f User can allow traffic from non profiled MACs through a global knob feature under test in NOS3 0 0 g The port profile will not get activated until a
34. 0 10 20 55 77 s 10G 6 10G 5 6 10 20 55 78 1 2 3 VDX6720 VDX6720 Connected with LAG IXIA 1 4 1 IXIA 1 4 2 IXIA 1 4 3 1 2 3 VDX6720 10 20 55 77 5 106 5 VDX6720 6 10G 6 10 20 55 78 3 7 10G 7 1 BROCADE 23 r IXIA 1 4 4 IXIA 1 4 5 4 IXIA 1 4 6 r IXIA 1 4 4 7 IXIA 1 4 5 4 IXIA 1 4 6 The following diagram shows two VDX6 720 switches in VCS Fabric mode connected with two or three 10G links Brocade ISL Trunk and six IXIA 10Gbps tester ports connections use in the testing VDX6720 Connected with ISL Trunk IXIA 1 4 1 IXIA 1 4 2 IXIA 1 4 3 1 2 A VCSID 71 VDX6720 10 20 55 79 10G 10G O Ol 5 6 VDX6720 10 20 55 177 2 VCS ID 1 3 1 la IXIA 1 44 a IXIA 1 4 5 IXIA 1 4 6 VDX6720 Connected with ISL Trunk IXIA 1 4 1 IXIA 1 4 2 IXIA 1 4 3 1 VDX6720 2 10 20 55 79 3 VCSID 71 5 10G 6 106G 10G 7 5 6 VDX6720 1 10 20 55 177 2 VCSID 1 3 a4 IXIA 1 4 4 1 IXIA 1 4 5 IXIA 1 4 6 For the following tests the same traffic flows are used with each configuration Comparing Configuration and Management Strategic Solutions Lab Page 14 BROCADE 23 Configuring LAG involves l
35. 1 1 S 2h8m 2 9 1 1 0 24 100 1 1 3 Ve 100 15 1 S 2h5m M8_159 4 2 VRRP VRRP E The Internet Engineering Task Force IETF has defined VRRP in RFC 2338 VRRP Virtual Router Redundancy Protocol introduces the concept of a virtual router which consists of a virtual router identifier VRID and one or more IP addresses Hosts use the virtual router s IP address es as their default gateway s just as they would with any router The virtual router has a virtual MAC address which is used for resolving ARP address resolution protocol requests VRRP protocols are designed to eliminate a single point of failure in a default route environment VRRP requires a master router and one or more backup routers Routers running VRRP dynamically elect master and backup routers The VRRP master router controls the IP address s associated with a virtual router The Master forwards packets sent to these IP addresses The election process provides dynamic fail over in the forwarding responsibility should the Master become unavailable Any of the virtual router s IP addresses on a LAN can then be used as the default first hop router by the end hosts VRRP provides higher availability for the default path without requiring configuration of dynamic routing or router discovery protocols on every end host Typical deployments use one backup router The Brocade implementation of VRRP follows RFC 3768 and also provides the following additional features e Track p
36. 1 2 3 Viewing and Configuring FC Ports on a VDX 6730 The Fibre Channel ports on the VDX 6730 must be connected to a Brocade Fibre Channel router for FCOE to Fibre Channel interconnectivity The Fibre Channel ports on VDX 6730 are pre provisioned to connect to a Brocade Fibre Channel router Viewing and Configuring VDX 6730 Fibre Channel ports 1 View default Fibre Channel ports state and Fibre Channel interface configuration RB201 68 fc24 show fabric islports Strategic Solutions Lab Page 64 BROCADE 23 Name RB201 68 fc24 Type 96 2 State Online Role Fabric Subordinate VCS Id 8192 Config Mode Local Only Rbridge id 201 WIN 10 00 00 05 33 6f 3c 6a FCF MAC 00 05 33 6f 3c 6a Index Interface State Operational State 1 Te 201 0 1 Down 2 Te 201 0 2 Down lt Truncated gt 22 Te 201 0 22 Down 23 Te 201 0 23 Down 24 Te 201 0 24 Down RB201 68 fc244 show running config interface FibreChannel 201 0 1 interface FibreChannel 201 0 1 desire distance 0 no isl r_rdy trunk enable no shutdown 2 Optional To modify default existing Fibre Channel configuration navigate to the FibreChannel interface in the running config Default configuration is recommended and FibreChannel interfaces are pre provisioned to connect to Brocade FCR RB201_68_fc24 configure terminal Entering configuration mode terminal RB201_68_fc24 config interface FibreChannel 201 0 1 RB201_68_fc24 config FibreChannel 201 0 1 Possible comp
37. 2 RB1 conf t RB1 int te 1 0 1 RB1 shutdown RB1 exit RB1 show interface include Input RB1 show interface include Output Restore all links between RB1 and RB2 and verify that traffic re routes to the shortest path and is appropriately load balanced RB1 conf t RB1 int te 1 0 1 RB1 no shutdown RB1 int te 1 0 2 RB1 no shutdown RB1 int te 1 0 13 RB1 no shutdown RB1 exit RB1 show interface include Input RB1 show interface include Output Note that all of this has happened without any manual intervention on the part of the network administrator 1 8 Ethernet Fabric Vs Spanning Tree Protocol STP These tests show the performance advantage of a VCS Fabric vs STP The topology is a full mesh network The test uses industry standard RFC 2889 Fully Meshed test cases to measure throughput and also the Lippis Cloud Simulation Test to measure latency for cloud application traffic The tests are performed using Ixia XM12 chassis running IxNetwork Version 5 0 352 8 and IxAutomate 6 90 102 3 GA SP1 The exact same tests are run once while switches are in VCS Fabric and then again while switches are in standalone mode with Spanning Tree protocol enabled The following diagram shows the four VDX 6720 switches in VCS Fabric mode in a full mesh topology with eight IXIA 10Gbps testing ports Strategic Solutions Lab Page 8 IXIA 1 4 1 IXIA 1 4 5 IXIA 1 4 3 IXIA 1 4 7 BROCADE 23 Four VD
38. 4 config zone LSAN host target LI member entry 15 7e 00 11 0d 00 00 02 4 Define a cfg and add the defined LSAN Zone to the cfg RB201 68 fc24 config zoning defined configuration cfg cfg vcs8192 RB201 68 fc24 config cfg cfg vcs8192 member zone LSAN host target 1 5 Verify the zoning defined configuration and enabled configuration RB201 68 fc24 config do show running config zoning defined configuration zoning defined configuration cfg cfg vcs8192 member zone LSAN host target 1 zoning defined configuration zone LSAN host target 1 member entry 10 00 00 05 33 48 71 8a member entry 15 7e 00 11 0d 00 00 02 RB201_68_fc24 config do show running config zoning enabled configuration zoning enabled configuration cfg name zoning enabled configuration default zone access allaccess zoning enabled configuration cfg action cfg none 6 Enable the zoning defined cfg RB201 68 fc24 config zoning enabled configuration cfg name cfg vcs8192 RB201_68_fc24 config f Verify the zoning enabled configuration again to check the cfg is now enabled RB201 68 fc24 config show running config zoning enabled configuration zoning enabled configuration cfg name zoning enabled configuration default zone access allaccess zoning enabled configuration cfg action cfg save 1 2 5 Creating and Enabling LSAN Zoning Configuration in Fibre Channel SAN Fabric Create and enable an identical LSAN Zone in the SAN Fabric where the Fibre Channel device
39. 4 protocol vrrp M8 159 config rbridge id 159 4 int ve 10 M8_159 config Ve 10 vrrp extended group 128 M8_159 config vrrp extended group 128 priority 254 M8_159 config vrrp extended group 128 exit 4 2 2 11 Virtual IP Command A virtual router s VRRP E session is identified by its unique virtual ip address Any Master can respond to ICMP echo requests and IP packets for virtual IP address in VRRP E context virtual ip specific configurations M8_159 config rbridge id 159 M8_159 config rbridge id 159 protocol vrrp M8_159 config rbridge id 159 int ve 10 M8_159 config Ve 10 vrrp extended group 128 M8_159 config vrrp extended group 128 virtual ip 10 1 1 157 M8_159 config vrrp extended group 128 enable 4 2 3 VRRP E Verification and Statistics 4 2 3 1 Verify VRRP License VRRP VRRP E are included with the Layer 3 license and do not require a license of their own M8 159 show license rbridge id 159 XXXXXXXXXXX OO0000000000 XXXXXXXXX ayer 3 license Feature name LAYER 3 Feature name VCS FABRIC M8 159i 4 2 3 2 Verify Master Election Occurs Verify that the election process occurred and one of the switches is elected as Master while the other is Backup Strategic Solutions Lab Page 38 BROCADE 4 2 3 3 Verify the Virtual Router MAC is Present in the ARP Table Additionally verify that the other VRRP E parameters such as virtual IP short path forwarding advertisement interval etc are set
40. 5 33 6f 3c 6a Index Interface State Operational State a Te 201 0 1 Down Te 201 0 2 Down poe RB201 68 fc24 show fab isl Rbridge id 201 ISLs 8 Src Src Nbr Nbr Index Interface Index Interface Nbr WWN BW Trunk Nbr Name 7 Te 201 0 7 9 Te 202 0 9 10 00 00 05 33 6F 3A 1A 20G Yes RB202 69 fc60 10 Te 201 0 10 20 Te 202 0 20 10 00 00 05 33 6F 3A 1A 20G Yes RB202 69 fc60 11 Te 201 0 11 29 Te 202 0 29 10 00 00 05 33 6F 3A 1A 20G Yes RB202 69 fc60 13 Te 201 0 13 39 Te 202 0 39 10 00 00 05 33 6F 3A 1A 20G Yes RB202 69 fc60 15 Te 201 0 15 49 Te 202 0 49 10 00 00 05 33 6F 3A 1A 20G Yes RB202 69 fc60 SS E 201 0 18 60 is 202 0 60 Rene E ES 20G v RB202 69 fc60 i 201 0 1 80 i 50 50 0 32G fcr fd 50 Strategic Solutions Lab Page 73 BROCADE 23 The Nbr Interface 60 indicates the neighbor is a Fibre Channel router with Front Domain 60 The Front Domain is also listed in the Nbr Name as fcr fd 60 The Source Interface 201 0 5 is the Trunk Primary of the four 8 Gbps Fibre Channel member links between the VDX 6730 and the Fibre Channel router with the corresponding EX port port 28 on the Fibre Channel router The total bandwidth of the four links equals 32 Gbps RB201 68 fc24 show fabric all VCS Id 8192 Config Mode Local Only Rbridge id WWN IP Address Name Translate Domain 50 50 00 51 ED 2D C0 1E 78 0 0 0 0 fcr fd 50 Front Domain of FCR6510 201 10 00 00 05 33 6F 3C 6A 10 20 52 68 RB201 68 fc24 202 10 00
41. 80 RB1 exit RB1 clock set CCYY MM DDTHH MM SS RB1 show clock 9 5 3 Configure Time Zone RB1 clock timezone region city 9 6 Syslog Syslog is an IP based service that allows systems messages to be sent to a remote logging server The Syslog test confirms functionality of remote logging functionality RB1 conf t RB1 logging syslog server ipv4_address RB1 exit RB1 show running config logging syslog server 9 7 SFlow SFlow is a traffic sampling mechanism that collects traffic information from sampled packet headers via an sFlow agent in hardware This information is forwarded to a collector that uses graphical representation to display traffic trending for network management and potentially billing purposes The intent of the sFlow test is to confirm sFlow functionality RB1 conf t RB1 sflow enable RB1 sflow collector ip address Strategic Solutions Lab Page 81 BROCADE 23 RB1 sflow polling interval interval RB1 sflow sample rate sample rate RB1 exit RB1 show running config sflow 9 8 Simple Network Management Protocol SNMP SNMP Simple Network Management Protocol is a proven method to manage network devices An SNMP server polls MIB variables from SNMP agents contained within networking devices and presents the information graphically This tests SNMP functionality and interoperability RB1 conf t RB1 snmp server community string ro rw RB1 snmp server host ip address ipv4_address RB1 snm
42. Addresses show vnetwork vmpolicy macaddr lists all vNIC and vmkernel MAC addresses and shows the respective Port Group and automatically created VCS Fabric Port Profile information switch show vnetwork vmpolicy macaddr all Associated MAC Virtual Machine dv PortGroup Port Profile 00 50 56 72 42 4c ProductionVMs auto ProductionVMs 00 50 56 78 69 36 VMkernel auto VMkernel 00 50 56 7b e5 41 ProductionvVMs auto ProductionVMs 00 50 56 7d 96 16 VMkernel auto VMkernel 00 50 56 8e 00 4b CentOS 4921 ProductionV auto ProductionVMs 00 50 56 8e 00 4d CentOS 4921 TestVMs auto TestVMs 00 50 56 8e 00 50 CentOS 4922 TestVMs auto TestVMs 00 50 56 8e 00 51 CentOS 4922 ProductionVMs auto ProductionVM NOTE As shown in the show vnetwork vmpolicy output NOS will automatically create Port Profiles for vCenter Port Groups using the prefix auto All vNIC and VMkernel MAC addresses are associated with the automatically created VCS Fabric Port Profiles Strategic Solutions Lab Page 28 BROCADE 3 2 4 show vnetwork vss This command shows which vSwitch uplink is connected to which physical switch interface 3 2 5 show vnetwork pgs show vnetwork pgs shows the standard virtual switch Port Group information NOTE show vnetwork pgs will quickly identify whether there is a VLAN misconfiguration If the VLAN IDs doesn t match across the hosts for a given port group most probably it may be due to a user error
43. Brocade VCS Fabric Technology Test Cases for Validating VCS Fabric Features and Functions BROCADE 23 Index INTRODUC TION ecu E 1 1 BROCADE VCS FABRIC LAYER 2 FUNCTIONALITY 2 aL TOPOLOG USE ee 2 1 2 CONFIGURE VCS ID AND RBRIDGE DS comesssnriaima tico UPS RUM anaana 2 1 3 AUTOMATIC CREATION OF VOS Te 3 1 4 AUTOMATIC CREATION OF ISLS AND LEHNEN eEeg 4 tS MAC ADDRESS LEARNING contessa a a 6 1 6 SHORTEST PATH FORWARDING ECMP AND LOAD BALANCING cerne nnn nnns 7 1 7 VERIFY TRAFFIC FLOWS WHEN LINKS AND ISL TRUNkRSEWL En 7 1 8 ETHERNET FABRIC VS SPANNING TREE PROTOCOL GI 8 1 9 ETHERNET LAG VS BROCADE ISL ET 13 2 AUTOMATIC MIGRATION OF PORT PROFILES 19 PNE Ee eier M 19 22 AMPP EE 20 2 3 SETUP AND VERIFY PROCEDURE CREATE ASSOCIATE ACTIVATE AND APPLY A PORT PROFILE 20 2 4 VALIDATION OF PORT PROFILE CAPABILITIES VLAN ACL QOS AND FCOE PORT eeeeeeeeeeeennn 22 2 4 1 Validation of VLAN Configuration EEN 22 2 4 2 Validation of ACL Configuration EN 23 2 4 3 ss Pa 23 2 4 4 YWAN c EERS 24 2 5 MIGRATION OF VIRTUAL MACHINE S AND VALIDATION OF AMPP ee 25 2 5 1 Single MAC from One Port to Another Port in the Same Switch 25 2 5 2 Single MAC From One Port to
44. Help Targets O O Start Stop Test Planning Test Running Test Analysis BY 2k8 5694 10 20 43 20 Microsoft Windows herz 1 5 Logical e rad bd Gef L 00 00 System A VMware Virtual disk 1 B MEE 2000 NETAPP LUN IEF New Test Plan J Physical Hi Configurations Se FhusicalDir zt System 4 VMwalNETAPP LUN aui Se PhusicalDir zr Partitions NETAPP LUN B 15 File System gt Configurations ER y User Configurations ELCH Medusa Sample Configurations Ep Medusa 2 5 Configurations ELCH 10 Gig f f Mam 10G Continuous Jitter Pattern H Fibre Channel Targets 1 07 2k8 5594 e D Stark Stop Test Planning Test Running Test Analysis S New Test Plan 00 0013 361 88 37205 321 00 289500 283686 297638 255800 0 lf Maim 10G Continuous 00 00 13 361 88 36486 37205 om 289500 283886 297638 255800 O BCEE 00 00 13 em 36486 mam om 289500 283886 297638 255800 O D 00 00 13 em 35486 37205 321 00 289500 263886 297638 2568 00 0 Strategic Solutions Lab Page 59 BROCADE 23 7 FCoE to FC Bridging The Brocade VDX 6730 Switches have Ethernet and Fibre Channel ports and can provide an interconnect for the FCoE servers attached to a VCS based FCOE fabric with storage devices and services attached to FOS Fibre Channel fabrics The VDX6730 32 has 24 Ethernet ports and 8 Fibre Channel ports and VDX 6730 76 has 60 Ethernet ports and 16 Fibre Channel ports With the release of th
45. N8 Online Trunk port master is Port 28 FCR6510 root portcfgexport 28 Port 28 info Admin enabled Pid format Not Applicable Front WN 50 00 53 31 37 a3 6e 78 Principal Switch 202 Principal WWN 10 00 00 05 33 6f 3a 1a Fabric Parameters Auto Negotiate R A TOV 10000 N Strategic Solutions Lab Page 71 E D TOV DH Group N A Hash Algorithm N A 2000 N Authentication Type None Edge fabric s primary wwn N A Edge fabric s version stamp N A FCR6510 root portcfgshow 28 Area Number Octet Speed Combo Speed Level Fill Word On Active Fill Word Current 28 1 16G 8G 4G 2G AUTO SW 0 Idle Idle 0 Idle Idle BROCADE 2 AL_PA Offset 13 OFF Trunk Port ON lt Truncated gt lt Truncated gt FCR6510 root portcfgexport 16 Port 16 info Admin enabled Pid format core N Front WWN 50 00 53 31 37 a3 ee 0a Principal Switch 30 Principal WWN 10 00 00 05 1e 0f 28 16 Fabric Parameters Auto Negotiate R A TOV 10000 N E D TOV 2000 N Authentication Type None DH Group N A Hash Algorithm N A Edge fabric s primary wwn N A Edge fabric s version stamp N A FCR6510 root portcfgshow 16 Area Number 19 Octet Speed Combo Speed Level Fill Word On Active Fill Word Current 1 16G 8G 4G 2G AUTO SW 0 Idle Idle 0 Idle Idle AL_PA Offset 13 OFF Trunk Port ON lt Truncated gt lt Truncated gt NOTE For the FCR to VDX IFL if the FCR switchshow
46. NOS to NOS NOS to FOS and FOS to FOS scenarios In this case Fiber Channel routing is within the Backbone Fabric but Fiber Channel Devices are connected to independent Fiber Channel Edge Fabrics VCS Fabrics connect FCOE initiator and target devices Represent ISL connectivity between 2 FCRs in single BB FOS NOS t Fabric NOS FOS Fabric Figure 2 Edge to edge sharing using a single backbone 1 1 3 Edge to Edge Sharing Ssing Dual Backbone EX EX Backbone Fabric 2 Figure 3 Edge to edge sharing using dual backbone The configuration provides high availability with dual Fibre Channel Backbone Fabrics Should a Backbone Fabric fail traffic will automatically reroute through the remaining Backbone Fabric Strategic Solutions Lab Page 61 BROCADE 23 1 2 Configuring FCoE FC Interconnect NOTE Before connecting new VDX6730 switches into an existing VCS Fabric make sure all the switches in the existing VCS Fabric are upgraded to NOS v2 1 1 or higher and the new VDX6730 switches are also running NOS v2 1 1 or higher 1 2 1 Installing FCoE BASE License on VDX 6720 6730 The FCoE BASE license is required on VDX 6720 6730 switches that have FCoE servers targets directly attached For details on VDX switch licenses such as VCS Dynamic Ports on Demand DPOD etc refer the Network OS Administrator s Guide for the NOS release Adding FCoE License 1 View existing licenses on the switch RB201 68 fc24 show lice
47. VRRP extended group 1 under interface ve 10 with virtual ip address 162 85 1 5 on both R1 and R2 Enable the group 1 on both R1 and R2 Verify that the VMAC is learned on both R1 and R2 Verify that traffic forwarding works as expected using various show commands Strategic Solutions Lab Page 43 BROCADE 23 5 Brocade VCS Fabric Integration with Classic Ethernet Architectures 5 1 Integration with Classic Layer 2 Ethernet 5 1 1 Create a vLAG Between VCS Fabric and Nexus 7000 Core All members of a Brocade VCS Fabric behave as a single logical Layer 2 Ethernet switch As such it is possible to create a link aggregation group LAG that spans multiple VCS Fabric members This is known as a virtual LAG vLAG Externally facing ports support all classic Ethernet protocols to interoperate with any standards compliant Layer 2 Ethernet switch In the following example we will configure a vLAG between a Brocade VCS Fabric and a pair of Nexus 7000 switches configured with virtual port channels vPC First create a port channel interface with four members spanning two VDX switches two members per switch RB1 conf t RB14 int te 1 0 6 RB1 channel group 20 mode active type standard RB1 lacp timeout long RB1 no shutdown RB1 int te 1 0 7 RB1 channel group 20 mode active type standard RB1 lacp timeout long RB1 no shutdown RB1 exit RB2 conf t RB2 int te 2 0 6 RB2 channel group 20 mode active type standard RB2
48. X 6720 Switches Full Mesh VCS Fabric Li IXIA 1 4 2 lt q IXIA 1 4 6 VDX6720 10G VDX6720 10 20 55 77 10 20 55 78 S NS S VDX6720 10G VDX6720 10 20 55 79 10 20 55 177 a IXIA 1 4 4 t IXIA 1 4 8 The following diagram shows the effective topology when the four VDX switches operate as stand alone switching with STP used for frame forwarding The red dotted line indicates paths that STP blocks and disables to prevent loops IXIA 1 4 1 IXIA 1 4 5 IXIA 1 4 3 IXIA 1 4 7 Throughput Performance Test Four VDX 6720 Switches Full Mesh with RSTP Li IXIA 1 4 2 a IXIA 1 4 6 VDX6720 ue ee er 10 20 55 77 10 20 55 78 N i N N S S S N N VDX6720 10 20 55 79 10G 3 ME M STP ROOT ESA IXIA 1 4 4 L IXIA 1 4 8 Spanning tree disabled links Throughput describes the highest rate at which a switch forwards traffic with zero frame loss It s a critical metric as even a single dropped frame can have adverse effects on application performance This test measures throughput for unicast traffic as defined in RFC 2889 Tests involved a fully meshed pattern of traffic between 8 switch ports for duration of 20 seconds per iteration using IxAutomate Strategic Solutions Lab Page 9 all other ports in an evenly distributed rou
49. affic VDX 49113 config vlan profile s switchport trunk allowed Possible completions vlan VLAN s that will be added removed VDX 49113 config vlan profile s switchport trunk allowed vlan Possible completions add Allow these VLANs to Xmit Rx through the Layer2 interface all Allow all VLANs to Xmit Rx through the Layer2 interface except Allow all VLANs except this vlan range to Xmit Rx through the Layer2 interface none Allow no VLANs to Xmit Rx through the Layer2 interface remove Remove a VLAN range that Xmit Tx through the Layer2 interface VDX_49113 config vlan profile switchport trunk allowed vlan Repeat the test for a VLAN Profile with 1 Access versus Trunk 2 Various types of ingress traffic versus VLAN configuration on port profile Strategic Solutions Lab Page 22 BROCADE 23 See the Appendix for detailed steps Repeat both tests for a Fengigabit Ethernet b Gigabit Ethernet C LAG VLAG both 1G and 10G 2 4 2 Validation of ACL Configuration Setup the following 1 Create a port profile with desired VLAN configuration using Section 3 1 3 2 Create an extended Layer 2 MAC ACL using following procedure VDX_49113 config mac access list extended acl1 VDX_49113 conf macl ext permit host 0050 0000 0001 host 0050 0000 0004 count VDX_49113 conf macl ext deny host 0050 0000 0001 host 0050 0000 0003 count 3 Create a security profile and attach the above access list to it VDX 49113 config port profile tes
50. allow all enable Trunk VID 400 Should receive mode allowed all SE with VID 400 PP application Yes Flood Yes if Dst mac is not learnt Forward Yes if DST mac is in mac table Trunk allow all disable Trunk Untagged Should receive mode allowed all untagged PP application Yes Flood Yes Strategic Solutions Lab Page 86 6 Trunk allow all mode T Trunk allow all mode Trunk allow all mode Strategic Solutions Lab disable disable disable Trunk allowed all Trunk allowed all Trunk allowed all VID 0 VID 1 VID 400 BROCADE 23 Learning Yes PP application Yes Flood Yes Learning Yes PP application Yes Flood Yes PP application Yes Flood Yes if Dst mac is not learnt Forward Yes if DST mac is in mac table Should receive untagged Should receive untagged Should receive VID 400 Page 87 BROCADE 23 3 Conflict Matrix YES Can co exists NO Cannot co exists VLAN Sub Profile Conflicts access vlan access trunk vlan trunk native vian native vlan X vlan Y X vlan Y X Y QoS Sub Profile Conflicts cee qos qos qos qos qos qos map cos Y cos COS flowco flowco flowco Y trust traffic ntrol tx ntrol rx ntrol i class off off pause Y Y LE d LLL LLL ws eee Eee es LU o Weibel e Wl ba Wf A R e WE WEE We We Jm T Reo e Wf eee eee e fhe fis he fp UT ht A Security Sub Profile Conflicts NEN port acl ABC vlan
51. arameters include traffic type traffic rate frame size offered traffic behavior and traffic mesh The test measures the throughput latency jitter and frame loss on a per application traffic type basis across a set of 8 port topologies The following traffic types were tested web HTTP database server server database iSCSI storage server iSCSI server storage client server plus server client The north south client server traffic simulates Internet browsing the database traffic simulates server server lookup and data retrieval while the storage traffic simulates IP based IO When all traffic types are instantiated the throughput latency jitter and frame loss pare measured for each traffic type The following tables show the result of the cloud simulation test for a VCS Fabric and Spanning Tree configured network Traffic Item Tx Frames Store Store Store First Last Forward Avg Forward Forward TimeStamp TimeStamp Latency ns Min Latency Max ns Latency ns NS Client to Server 221 941 19 221 941 19 2 244 17 080 00 03 2 02 52 8 0 0 NS Server to Client 53 308 309 53 308 309 un 2 951 196 360 00 03 2 02 52 8 EW HTTP 320 535 10 320 535 10 4 580 219 200 00 03 2 02 52 8 4 4 EW 1 033 921 1 1 033 921 1 1 846 1 080 10 980 00 03 2 02 52 8 Server to Database 52 52 EW 64 306 383 64 306 383 216 880 00 03 2 02 52 8 Database to Server a li i iSCSI 27 391 296 27 391 296 904 10 580 00 03 2 02 52 8 Server_to_S
52. ate the appropriate LUN and LUN masks on the FCoE FC target Please refer to the appropriate storage array user manual for a detailed description of the configuration procedure 6 4 Discovering LUNs After creating the appropriate LUN masks the server can discover the LUNs through the servers CNA The following shows how to verify LUNs in a Windows environment Strategic Solutions Lab Page 5 BROCADE 23 Right Click on My Computer gt Manage Server Manager Storage gt Disk Management gt Rescan Disks R Server Manager File Action View Help ga HE Server Manager 2K8 5694j E Roles Features 3m Diagnostics Disk Management volume List Graphical View Volume Layout Type File System Status Left Simple Basic NTFS Healthy System Boo EN Configuration Ca Did Simple Basic RAW Healthy Primary Part E a Storage He windows Server Backup cs Disk Management Refresh EE All Tasks b TIE k Help L pisk 0 AAA Basic LC 30 00 Gb 50 00 GB NTFS Online Healthy System Boot Page File Active Note In Linux fdisk 1 should show the visible luns 6 5 Starting FCoE traffic through a Windows Host After discovering the LUNs start the FCoE traffic The following show sample screenshots from the Medusa Labs Test Tools application in a Windows environment Strategic Solutions Lab Page 58 BROCADE 23 Medusa Labs Test Tools 3 0 137 File View
53. ator Interface Fcoe 1 201 19 Physical Interface Te 201 0 19 Share Area No PID 01f001 Port Name Node Name FC4s FCP PortSymb 26 BRE 41 A 2 L3 25016 01B FW NodeSymb NULL Fabric Port Name 50 00 51 ED 2D CA 1A 82 Device type Physical Unknown initiator target Share Area No 15 7E 00 11 0D 00 00 02 15 7E 00 11 0D 00 00 02 Found 2 zone member s for WWN 10 00 00 05 33 48 71 8a Verify Shared Devices From the Fibre Channel SAN Edge Fabric 1 Verify the translate domain of the VCS edge fabric is seen in the SAN edge fabric T 5300 114 FID128 root fabricshow Switch ID Worldwide Name Enet IP Addr FC IP Addr Name 1 fffc01 50 00 51 ed 2d ce 1f b2 0 0 0 0 0 0 0 0 fcr xd 1 20 2 fffc02 50 00 51 ed 2d ce 1f c9 0 0 0 0 0 0 0 0 fcr xd 2 100 4 fffc04 10 00 00 05 33 41 39 02 10 20 52 114 0 0 0 0 T 5300 114 30 fffcle 10 00 00 05 1e 0f 28 16 10 20 52 115 0 0 0 0 T 300 115 50 fffc32 50 00 51 ed 2d c0 1e 0a 0 0 0 0 0 0 0 0 fer fd 59 The Fabric has 7 switches Strategic Solutions Lab BROCADE 23 2 Verify the LSAN Zone member from the VCS edge fabric is correctly reflected in the name server of the SAN edge fabric Strategic Solutions Lab Page 77 BROCADE 23 8 Hardware Resiliency Testing 8 1 Power Supply Unit PSU and fan failover and serviceability Brocade VDX products all feature dual redundant hot swappable power supplies and fan assemblies This test verifies the hitless failover behavior o
54. bone sees seen nnne 61 7 2 CONFIGURING FCOE FC INTERCONNECT 5axuxcxucseetexmbkexuve ni v sdauu Scil tuc Erase eebe 62 1 2 1 Installing FCoE BASE License on VDX G Z0O D 20 62 1 2 2 Viewing and Configuring FCoE ports on VDX 6720 6730 sees 62 1 2 3 Viewing and Configuring FC Ports on a VDX GU 64 1 2 4 Defining and Enabling LSAN Zoning Configuration in a VCS Fabric 66 AS Creating and Enabling LSAN Zoning Configuration in Fibre Channel SAN Fabric 67 1 2 6 Enabling Fibre Channel Routing FCR Service on FOS Switch sss 68 1 2 1 Configuring Inter fabric link IFL on the Fibre Channel Router FCR 68 1 2 8 Verifying Connectivity Between the Backbone and Edge Fabrics 11 1 2 9 Verifying Devices are Correctly Shared Between Edge Fabrics 15 8 HARDWARE RESILIENCY TESTING erre erre neueren KEE Ken 78 8 1 POWER SUPPLY UNIT PSU AND FAN FAILOVER AND SERWVICEABILITN esee seen 78 9 SYSTEMS MANAGEMENT TESTING eese erre rere rere RENE nna 79 Strategic Solutions Lab Page iii BROCADE 23 9 1 OUT 0F BAND MANAGEMENT VIA THE ETHERNET MANAGEMENT INTERFACE ENEE 79 9 1 1 Configure a Static IPv4 Address on the Management Interface s
55. congestion on a link in the LAG Said differently LAG with hashing can not ensure full link utilization under arbitrary traffic flows VDX6720 Connected with LAG Problematic Hashing VDX6720 VDX6720 OE ITA yy 2AN IXIA 1 4 4 AANA Hi coe A 06 2 OS VE m IXIA 1 4 2 2 E D IXIA 1 4 5 ee 6 10G 6 CON IXIA 1 4 3 gt 3 3d IXIA 1 4 6 Strategic Solutions Lab Page 15 BROCADE 23 Brocade ISL trunks do not use hashing to balance traffic across the individual ISL links in an ISL trunk Frames are sprayed across all links in the ISL Trunk regardless of the flow the frame belongs to The ASICs ensure in order delivery of all frames and that jitter is within acceptable limits The result is automatic near perfect load balancing across all links in an ISL Trunk with any arbitrary combination of traffic flows VDX6720 Connected with ISL Trunk Frame Level Spraying Stripping VDX6720 VDX6720 MM AN x IXIA 1 4 4 VIRI e EE Mi 1 06 Do ed e E E IXIA 1 4 2 aSo c0 EN m cO NM IXIA 1 4 5 EN AA 06 ooo c c IXIA 1 4 3 NEUEN A ELT EE co P IXIA 1 4 6 The following snapshot from the IxNetwork test shows congestion on switch port 5 in the LAG setup The 64 and 1518 byte traffic flows coming from port 1 and 2 have massive frame loss although the traffic generator is operating at 50 of line rate for these ports With the Brocade ISL Trunk all available links are ful
56. e Brocade Network Operating System NOS v2 1 1 Brocade protects existing investments by bridging Fibre Channel SAN and Ethernet fabrics Organizations can utilize FCoE capabilities on various Brocade VDX switches and connect to Fibre Channel SAN fabrics running FOS v7 0 1 or later using Brocade VDX 6730 and Brocade Fibre Channel Router FCR In the following section NOS refers to a Brocade VCS Fabric running the Brocade Network Operating System and FOS refers to a Brocade Fiber Channel fabric running the Brocade Fabric Operating System NOTE FCoE to Fibre Channel interconnect is supported with Brocade NOS v2 1 1 or higher connected to Brocade FOS v7 0 1 or higher 1 1 Supported Topologies Below are the set of topologies supported for interconnecting edge fabrics using Brocade Fibre Channel routers 1 1 1 VCS Fabrics as Fibre Channel Edge Fabrics with Fibre Channel Backbone Fabric Represents IFL EX E connectivity in Trunk or non Trunk manner Backbone Fabric st Figure 1 NOS VCS Fabric edge to FOS backbone sharing Each pink NOS Fabric is treated as a Fiber Channel Edge Fabric and each one is an independent VCS Fabric with FCoE traffic The blue Backbone Fabric is a Fiber Channel Backbone Fabric with Fiber Channel routing and Fiber Channel devices Strategic Solutions Lab Page 60 BROCADE 23 1 1 2 Edge to Edge Sharing Using a Single Fibre Channel Backbone Fabric Edge to edge sharing is supported for
57. ed across both equal cost paths and weighted based on each path s bandwidth RB1 show interface include Output RB1 show interface include Input 1 7 Verify Traffic Flows When Links and ISL Trunks Fail A VCS Fabrics is self healing When an ISL Trunk link fails traffic is automatically and non disruptively re distributed among the remaining links in the trunk without administrator intervention If a complete path fails the fabric re routes all traffic to the remaining least cost paths in the These actions are sub second and do not generally disrupt user traffic With traffic running between the two VMs remove a link in an ISL Trunk group between RB1 and RB2 to demonstrate that no traffic interruption has occurred and traffic automatically fails over to remaining links in the trunk group RB1 conf t RB1 int te 1 0 2 RB1 shutdown RB1 exit RB1 show interface include Input RB1 show interface include Output Next remove a link not in an ISL Trunk which is a separate path between two to demonstrate how traffic fails over to remaining link between RB1 and RB2 RB1 conf t RB1 int te 1 0 13 RB1 shutdown RB1 exit Strategic Solutions Lab Page 7 BROCADE 23 RB1 show interface include Input RB1 show interface include Output Finally remove the last link between RB1 and RB2 and verify that traffic fails over to the two hop path through RB3 which is now the least cost path in the fabric between RB1 and RB
58. eempts the master router Hold time is configured to allow all the software components to converge on the backup router before preemption is triggered A default value means switchover to higher priority backup can immediately occur after the backup router comes online Hold time ranges from 60 3600 seconds The default hold time is 60 seconds When a hold time greater than the default value is provided the backup router comes online after it waits for the hold time interval and does not participate in the election protocol So even if a backup router has come online that has a higher priority than the current master the backup does not try to become master until the hold time period has expired Hold time specific configurations Strategic Solutions Lab Page 35 BROCADE 23 M8_159 config rbridge id 159 M8 159 config rbridge id 159 4 protocol vrrp M8 159 config rbridge id 159 4 int ve 10 M8_159 config Ve 10 vrrp extended group 128 M8_159 config vrrp extended group 128 hold time M8 159 config vrrp extended group 128 3 no advertise backup M8_159 config vrrp extended group 128 exit 4 2 2 4 Advertise Backup Command Backup routers send VRRP E advertisement messages similar to the VRRP E master except that the type field in the VRRP packet signifies that the message is a VRRP E backup advertisement message When the master receives a backup advertisement it updates the list of backup routers Similarly when a VRRP E backup receiv
59. efore configuring them under the qos sub profile Please refer to the NOS admin guide for exact configuration steps 4 Send the profiled traffic and verify QoS is being applied using the following commands VDX_49113 show qos queue int t x y z VDX 491134 show qos flowcontrol int t x y z Repeat above tests for a Fengigabit Ethernet b Gigabit Ethernet Note Only specific QoS options are available for 1G C LAG VLAG both 1G and 10G 2 4 4 Validation of FCoE Setup the following 1 Create a Port Profile with desired VLAN configuration using Section 3 1 3 2 Usercan enable the FCoE capability through 2 options l FCoE capability enabled for all the Port Profiles through the Default Port Profile Switch wide FCoE enablement VDX 49113 config port profile default VDX_49113 config port profile default fcoe profile VDX_49113 config fcoe profile fcoeport default NOTE There shouldn t be any active port profiles on the switch If there are any active pps this command will error out User needs to manually deactivate the activated port profiles using no port profile pp name activate ii Enable FCoE port capability on a specific port profile port NOTE Go inside an interface that is already have port profile port command and execute the following command VDX_49113 conf if te 113 0 1 fcoeport default 3 Verify the FCoE logins are successful through the following command VDX_49113 show fcoe login Repeat
60. es a backup advertisement message it updates the list of the other backup routers in the group Advertise backup specific configurations M8_159 config rbridge id 159 M8 159 config rbridge id 159 4 protocol vrrp M8 159 config rbridge id 159 4 int ve 10 M8_159 config Ve 10 vrrp extended group 128 M8_159 config vrrp extended group 128 advertise backup M8_159 config vrrp extended group 128 exit 4 2 2 5 Advertisement Interval Command Advertisement interval is the interval after which VRRP E advertisement messages are resent by the Master This advertisement interval is in seconds and can be in the range of 1 255 seconds Advertisement interval specific configurations M8_159 config rbridge id 159 M8_159 config rbridge id 159 protocol vrrp M8_159 config rbridge id 159 int ve 10 M8_159 config Ve 10 vrrp extended group 128 M8 159 config vrrp extended group 128 4 advertisement interval 5 M8_159 config vrrp extended group 128 exit 4 2 2 6 Backup Advertisement Interval Command Backup advertisement interval is the interval after which the Backup resends VRRP E advertisement messages to the Master This backup advertisement interval is un seconds and can be in the range of 60 3600 seconds Backup advertisement interval specific configurations M8_159 config rbridge id 159 M8_159 config rbridge id 159 protocol vrrp M8_159 config rbridge id 159 int ve 10 M8_159 config Ve 10 vrrp extended group 128 M8_159 conf
61. f the field replaceable PSUs and fan trays Description Commande Observations Pass Fail Verify switch 8 1 1 Remove PSU continues to operate 8 Verify switch 1 3 Remove fan tray continues to operate Strategic Solutions Lab Page 78 BROCADE 23 9 Systems Management Testing 9 1 Out of band Management via the Ethernet Management Interface The Ethernet Management Interface EMI provides out of band management via an IPv4 or IPv6 address The EMI s IP address and default gateway can be assigned statically or dynamically using DHCP Dynamic Host Configuration Protocol The EMI test verifies connectivity and the functionality of the Ethernet Management Interface After each of these tests verify that the EMI is reachable via Tenlet SSH and SCP protocols 9 1 1 Configure a Static IPv4 Address on the Management Interface RB1 conf t RB1 int management 1 0 RB1 no ip address dhcp RB1 ip address ipv4 address prefix Length RB1 ip gateway address ipv4 address gateway RB1 exit 9 1 2 Configure a Dynamic IPv4 Address Using DHCP RB1 conf t RB1 int management 1 0 RB1 ip address dhcp RB1 exit 9 1 3 Configure a Static IPv6 Address RB1 conf t RB1 int management 1 0 RB1 no ipv6 address autoconfig RB1 ipv6 address ipv6 address prefix Length RB1 exit 9 1 4 Configure a Dynamic IPv6 Address RB1 conf t RB1 int management 1 0 RB1 ipv6 address autoconfig RB1 exit 9 2 VCS Fabric IP address
62. he FCoE device login and note the device WWN and corresponding FCoE Port interface Strategic Solutions Lab Page 63 BROCADE 23 Total number of Logins 1 RB201 68 fc24 show fcoe interface brief FCOE IF Mode Status Binding Num Config Current Config Proto VN Ports 1 201 1 VF VF Up Down Te 201 0 1 0 1 201 2 VF VF Up Down Te 201 0 2 0 1 201 3 VF VF Up Down Te 201 0 3 0 truncated 1 201 17 VF VF Up Down Te 201 0 17 0 1 201 18 VF VF Up Down Te 201 0 18 0 1 201 20 VF VF Up Down Te 201 0 20 0 truncated Total number of Interfaces 24 7 View the FCoE interface statistics RB201 68 fc24 show interface fcoe 1 201 19 Interface Fcoe 1 201 19 Fcoe 1 201 19 is Up Line protocol is Up Ethernet port is TenGigabitEthernet 201 0 19 Interface index ifindex is 403898386 Config Mode is VF Current Mode is VF Last clearing of show interface counters 2011 11 17 21 12 50 846992 RX Statistics Num of FIP VLAN Discovery Requests 1 Num of FIP Discovery Solicitations 1 Num of FIP FLOGIs ST Num of FIP NPIV FDISCs Num of FIP LOGOs 0 Num of FIP Enode Keep Alives 255 399 Num of FIP VN Port Keep Alives 124 Errors 20 TX Statistics Num of FIP VLAN Discovery Responses 1 Num of FIP Discovery SA t Num of FIP Discovery UA 1427 Num of FLOGI FDISC ACCs SD Num of LS RJT FLOGI FDISC LOGO 0 Num of CVLs 0 Time since last status change 2011 11 17 21 13 33 483007 Total number of Interfaces 1
63. icense RB1 show license id RB1 show license RB1 license add licstr LicenseString Strategic Solutions Lab Page 84 Appendix BROCADE 23 This appendix provides information documenting AMPP settings that are available in a VCS Fabric SI no 1 Access VLAN profile table for verification VLAN Profile Access mode Access mode Access mode Access mode Access mode Access mode VLAN Config VID 1 default VID 1 default VID 1 default VID 1 default VID 1 default VID 1 default Strategic Solutions Lab Vian dot1q native enable enable enable enable Destination Port Trunk allowed all Trunk allowed all Trunk allowed all Trunk allowed all Trunk allowed all Trunk allowed all Ingress Traffic With AMPP Port application wg VID 0 VID 1 VID 400 PP application Yes Flood Yes if Dst mac is not learnt Forward Yes if DST mac is in mac table PP application Yes Flood Yes if Dst mac is not learnt Forward Yes if DST mac is in mac table Learning Yes PP application Yes Flood Forward No Learning Yes on vlan 400 PP application No Flood Forward No VID 0 PP application Yes Flood Yes if Dst mac is not learnt Forward Yes if DST mac is in mac table PP application Yes Flood Yes if Dst mac is not learnt Expected captured trace on Destination port Should recei
64. ig vrrp extended group 128 backup advertisement interval 180 M8_159 config vrrp extended group 128 exit 4 2 2 7 Description Command Any virtual router s VRRP E session is identified by its unique description field in the running config Strategic Solutions Lab Page 36 BROCADE 23 Description specific configurations M8_159 config rbridge id 159 M8 159 config rbridge id 159 4 protocol vrrp M8 159 config rbridge id 159 4 int ve 10 M8 159 config Ve 10 s vrrp extended group 128 M8_159 config vrrp extended group 128 description VRRP VCS 1 M8_159 config vrrp extended group 128 exit 4 2 2 8 Enable Command Determines the administrative state of the virtual router which can be either one of the following disabled The virtual router is configured on the interface but VRRP or VRRP E has not been activated on the interface e enabled VRRP or VRRP E has been activated on the interface VRRP VRRP E enable specific configurations M8_159 config rbridge id 159 M8 159 config rbridge id 159 4 protocol vrrp M8 159 config rbridge id 159 4 enable M8_159 config rbridge id 159 no enable M8 159 config rbridge id 159 4 exit 4 2 2 9 Preempt Mode Command By default a Backup that has a higher priority than another Backup that has become the Master can preempt the Master and take over the role of Master The user has to disable preemption to prevent this behavior Preemption applies only to Backup routers and takes effect on
65. it 9 14 2 Create a New User Create a security admin user RB1 conf t RB1 username SecAdminUser role NetworkSecurityAdmin password password RB1 exit 9 14 3 Create Rules for a Role Create rules for a security admin user RB1 conf t RB1 RB1 RB1 RB1 RB1 RB1 RB1 rule rule rule rule rule rule exit Verify a user can log in with the new 9 15 system 10 11 12 13 14 15 action action action action action action accept accept accept accept accept accept Licensing The Brocade Network Operating System Network OS includes platform support in standalone and VCS modes as well as optional features that are enabled by license keys You can purchase Brocade licenses per product or per feature Each switch in a fabric needs its own licenses but universal licenses for multiple switches are available The licensing test verifies the licenses installed in the operation operation operation operation operation operation read write read write read write read write read write read write role role role role role role NetworkSecurityAdmin NetworkSecurityAdmin NetworkSecurityAdmin NetworkSecurityAdmin NetworkSecurityAdmin NetworkSecurityAdmin command command command command command command role rule username aaa radius server config SecAdminUser user and it has the appropriate permissions Display switch license ID display licenses information and add a new l
66. ized authentication server and multiple Network Access Servers NAS or clients With TACACS support management of Brocade switches seamlessly integrates into these environments Once configured to use TACACS a Brocade switch becomes a Network Access Server NAS The TACACS test verifies TACACS functionality and interoperability Configure a TACACS server for authentication and verify the configuration RB1 conf t RB1 tacacs server host ip address protocol pap key shared secret string timeout 10 retries 3 RB1 exit RB1 show running config tacacs server 9 14 Role Based Access Control RBAC Role based access control RBAC is an authorization mechanism You can create roles dynamically and associate them with rules to define the permissions applicable to a particular role User accounts must be associated with a role and every user account can only be associated with a single role Strategic Solutions Lab Page 83 BROCADE 23 Permissions cannot be assigned directly to the user accounts and can only be acquired through the associated role RBAC is the function of specifying access rights to resources for roles When a user executes a command privileges are evaluated to determine access to the command based on the role of the user The RBAC test verifies RBAC functionality 9 14 1 Create a New role Create a security administrator role RB1 conf t RB1 role name NetworkSecurityAdmin desc Manages Security CLIs RB1 ex
67. letions desire distance Configure Desired distance for LS and LD mode do Run an operational mode command exit Exit from current mode fill word Configure Fill Word help Provide help information isl r_rdy Enable ISL R_rdy Mode long distance Configure Long Distance no Negate a command or set its defaults pwd Display current mode path shutdown Shutdown the selected interface speed Configure Speed top Exit to top level and optionally run command trunk enable Enable Trunk vc link init Enable VC Link Init 3 View the FC interface statistics RB201_68_fc24 show interface Fibrechannel 2901 0 1 fibrechannel 201 0 1 is up In Sync Protocol state is up connected Pluggable media present Strategic Solutions Lab Page 65 BROCADE 23 LineSpeed Actual 8G Auto PortSpeed N8Gbps portDisableReason None Portld c93100 PortIfId 43020021 PortWwn 20 31 00 05 33 6f 3c 6a Distance normal Last clearing of show interface counters 00 35 53 Interrupts 0 Link failure 0 EAT 0 Unknown 0 Loss of sync 0 Fbsy 0 Lli 0 Loss of sig O0 Proc rqrd 0 Protocol err 0 Timed out 0 Invalid word 0 Rx flushed 0 Invalid crc 0 Tx unavail 0 Delim err 0 Free buffer 0 Address err 0 Overrun 0 Lr_in 0 Suspended 0 Lr out 0 Parity err 0 Ols in 0 2 parity err 0 Ols out 0 Rate info Bandwidth 8 00G Tx performance B sec Rx performance 85 7MB sec 1 2 4 Defining and Enabling LSAN Zoning Configuration in a VCS
68. ll the dependencies are resolved h The fabric can allow multiple port profiles to be applied on a single port but in case of conflict then the application of later port profile will fail with appropriate RASLOG i User can control the application of port profile by activating or deactivating the port profile j Key feature added on NOS2 1 Network OS vCenter Integration aka VMWare Network Automation 2 3 Setup and Verify Procedure Create Associate Activate and Apply a Port Profile a Create a port profile VDX config port profile test profile VDX config vlan profile switchport VDX config vlan profile switchport mode access VDX config vlan profile switchport access vlan 1 b Activate the port profile VDX config port profile test profile activate c Identify the MAC address of a Virtual Machine For VMWare vCenter Strategic Solutions Lab Page 20 BROCADE 23 CentOS 4971 Virtual Machine Properties Hardware Options Resources Show Al Devices Adapter Type Current adapter Flexible Hardware MN Memory MAC Address LJ CPUs DEE El Video card C9 WMCI device Automatic Manual 9 SCSI controller LSI Logic Parallel WS Hard disk 1 Virtual Disk HB Network adapter 1 PraductionvMs dvSwit Ba Network adapter 2 TestVMs For Microsoft Hyper V i Failover Cluster Manager de Action View Help cala a Failover Cluster Manager A 5 SS DK ER Gent ES Recent Cluster Event
69. lt mode Configuring Fibre Channel Router EX Ports in Mode 5 for VCS Fabrics Connectivity Strategic Solutions Lab Page 68 BROCADE 23 NOTE If the FCR ports are connected to the VDX 6730 before configuring them as EX ports mode 5 the VDX 6730 may show the port operational state in show fabric islports as below 53 Fi 201 0 5 Down Down ESC NOS incompatible Configure the EX ports on FCR as below and then perform a shut no shut on the Fibre Channel interface 1 Disable the ports that are to be configured as EX ports the ones connected to VDX 6730 In the example below ports 28 29 30 31 of the FCR6510 would be physically connected to VDX 6730 ports 5 6 7 8 FCR6510 root portdisable 28 FCR6510 root portdisable 29 FCR6510 root portdisable 30 FCR6510 root portdisable 31 2 Configure each port that connects to the VDX 6730 as an EX port e Setthe Fabric ID for the VCS Fabric avoid using fabric IDs 1 and 128 which are the default IDs for backbone connections 120 in example below e Optional Set the unique Front Domain ID to identify the FCR on the edge VCS Fabric 60 in example below e Set the operational mode to 5 Brocade NOS fabric TIP If the VDX 6730 switch is connected to more than one FCR you can customize and manually configure a Front Domain ID FD for each FCR while configuring the EX ports on it This helps to easily identifying the FCR from all its Edge Fabrics Make sure you use the same unique Front
70. ly utilized for the 64 1518 and 9000 byte flows allowing the ISL Trunk to 10096 throughput i e 5096 of the line rate or 5Gbps from each port without frame loss Traffic Item Tx Frame Rx Frame Tx Frames Rx Frames Frames Delta Loss 96 Rate Rate IXIA 1 4 1 LAG 14 880 953 3 926 472 991 581 400 261 637 212 729 944 188 73 61 lt gt 1 4 4 64 Bytes IXIA 1 4 2 LAG 812 744 598 405 54 156 592 39 874 342 14 282 250 26 37 lt gt 1 4 5 1518 Bytes IXIA 1 4 3 LAG 138 581 138 581 9 234 240 9 234 234 lt gt 1 4 6 9000 Bytes IXIA 1 4 1 ISL Trunk 14 880 953 14 880 956 991 581 399 991 581 340 59 lt gt 1 4 4 64 Bytes IXIA 1 4 2 ISL Trunk 812 744 812 744 54 156 592 54 156 588 lt gt 1 4 5 1518 Bytes IXIA 1 4 3 ISL Trunk 138 581 138 581 9 234 240 9 234 238 lt gt 1 4 6 9000 Bytes Strategic Solutions Lab Page 16 BROCADE 23 Flow control can be used to prevent frame loss for certain traffic flows when congestion occurs The following table shows the effective data rate for each traffic flow when using flow control When using LAG all three flows experience a bottleneck with the 64 bytes flow only achieving 36 996 of the desired flow rate the 1518 byte flow achieves 76 of desired rate and the 9000 byte flow achieves 87 1 of the desired flow For the Brocade ISL Trunk configuration all three flows achieve 10096 of the desired flow rate Traffic Item Intended Effective Loss 96 Effective Blocking Frame Rate Frame Ra
71. ly when the Master has failed and a Backup has assumed ownership of the virtual router This feature prevents a Backup with a higher priority from taking over as Master from another Backup that has a lower priority but has already become the Master of the virtual router Preemption is especially useful for preventing link flaps in situations where there are multiple Backups and a Backup with a lower priority than another Backup has assumed ownership since Backup with the higher priority was unavailable when ownership changed If the non preempt mode thus disabling the preemption feature is enabled on all the Backups the Backup that becomes the Master following the disappearance of the Master continues to be Master The new Master is not preempted Preempt mode specific configurations M8_159 config rbridge id 159 M8 159 config rbridge id 159 4 protocol vrrp M8 159 config rbridge id 159 4 int ve 10 M8 159 config Ve 10 s vrrp extended group 128 M8_159 config vrrp extended group 128 preempt mode M8_159 config vrrp extended group 128 exit Strategic Solutions Lab Page 37 BROCADE 23 4 2 2 10 Priority Command During negotiation the router with the highest priority becomes the Master If two or more devices are tied with the highest priority the Backup interface with the highest IP address becomes the Master for the virtual router Priority specific configurations M8_159 config rbridge id 159 M8 159 config rbridge id 159
72. nd robin type fashion BROCADE 23 The RFC 2889 Fully Meshed Throughput Test determines the total number of frames that the Device Under Test DUT can handle when it receives frames on all ports All ports transmit and receive traffic at a specified transmission rate such that each switch interface transmits and receives frames to from all of the other switches and their interfaces Each switch port being tested sends frames to The VCS Fabric mode network achieves 100 line rate throughput for all frame sizes that 256 bytes or greater with no frame loss The results are shown in the following table r cz8823 Fully Meshed Aggregate Results 512 1024 1280 1518 2500 5000 100 00 1109647 450 Rate Aga Tx E DNE Agg Rx Count 1 964 284 616 1 417 567 104 724 637 646 3 5 839 815 191 570 948 153 B45 112 129 670 104 79 365 048 22 172 920 Agg Frame TIS Loss Loss D o0 D oo D o0 D Dm D oo D Dm D Dm D Dm D o0 Table 1 RFC2889 Fully Meshed Aggregate Results for VCS Fabric Network When the switches are reconfigured with RSTP the maximum throughput without frame loss is only Flaoded co m mi co P co co Om 57 8 of full line rate using the same testing ports The results are shown in the following table AE IxAutomate Report r c2883 Fully Meshed Aggregate Results SE trio att icd Agg Rx Count AggFrame NE Fr frames 1780 2900 1820 3250 1880 3940 1880 5160
73. nel router that will be configures as EX ports connecting to switches in the Fibre Channel SAN Edge Fabric In the example below ports 16 17 18 19 of the FCR6510 are connected to FC SAN Edge Fabric switch T 5300 on its ports 76 77 78 79 FCR6510 root portdisable 16 FCR6510 root portdisable 17 FCR6510 root portdisable 18 FCR6510 root portdisable 19 2 Configure each port on the Fibre Channel router that connects to the T 5300 as an EX port e Setthe Fabric ID for the FC SAN edge fabric avoid using fabric IDs 1 and 128 which are the default IDs for backbone connections 10 in example below e Optional Set the unique Front Domain ID to identify the FCR on the edge FC SAN fabric 60 in example below same as set on this FCR for VCS Fabric e optional Default is mode O Set the operational mode to Brocade Native mode O FCR6510 root portcfgexport 16 a 1 f 10 d 60 2000 03 13 03 30 02 FCR 1071 620 FID 128 INFO FCR6510 Port 16 is changed from non FCR port to FCR port FCR6510 root portcfgexport 17 a 1 f 10 d 60 FCR6510 root portcfgexport 18 a 1 f 10 d 60 FCR6510 root portcfgexport 19 a 1 f 10 d 60 3 Enable the ports on the Fibre Channel router FCR6510 root portenable 16 FCR6510 root portenable 17 FCR6510 root portenable 18 FCR6510 root portenable 19 Strategic Solutions Lab Page 70 BROCADE 23 4 Verify the EX ports are correctly configured FCR6510 root portcfgexport
74. ng the tests RB1 6 LEPE 6 i RB2 0 6 1 2 1 2 ee j aiaa i T1743 2 A des DIIS IS 13 13 RTS aiu N SM Be x 4 A NIS p A S Ki ND AS f N ir EM P e d bk e NOM m d b o 7 j p S ip Y 100004 e we F VM1 AA O VM2 IP 192 168 1 1 RB3 dad ES IP 192 168 1 2 SRV1 MAC 0001 0001 0001 MAC 0001 0001 0002 SRV2 p SE iP 102 468 4 5 MAC 0004 0001 0008 1 2 Confisure VCS ID and RBridse IDs In a VCS Fabric every member switch has a unique identifier called Routing Bridge RBridge ID Additionally every switch in the same VCS Fabric must have the same VCS Fabric ID or VCS ID The only prerequisites for two VDX switches to connect and form a fabric are they have the same VCS ID and unique RBridge IDs The first task will be to make sure that the three VDX switches are properly configured to form a fabric Strategic Solutions Lab Page 2 BROCADE Configure a unique RBridge ID on each RBridge with the same VCS ID and reboot the switches 1 3 Automatic Creation of VCS Fabric Once the RBridge and VCS IDs have been configured for every fabric member we just need to connect the cables between them and the fabric will automatically form All members will automatically be discovered along with the routes between each member in the fabric The following tests will demonstrate how the fabric will automatically form when connecting the cables between the VDX switches Log in to RB1 and demons
75. nse 2 Add the FCoE license RB201 68 fc24 license add licStr FCOE BASE LICENSE STRING gt For license to take effect it may be necessary to disable enable ports or switch 3 Disable enable the switch RB201 68 fc24 chassis disable Are you sure you want to disable all chassis ports now y n y RB201 68 fc24 RB201 68 fc24 chassis enable 4 Verify the FCoE license is added correctly RB201 68 fc24 show license rbridge id 201 XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX FCoE Base license Feature name FCOE BASE XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX 1 2 2 Viewing and Configuring FCoE ports on VDX 6720 6730 FCoE enabled servers should be directly connected to VDX 6720 6730 switches via CNAs supporting FC BB 5 compliant FCoE services Viewing and Configuring FCoE Parameters 1 View the default existing FCoE parameters RB201 68 fc24 show fcoe fabric map default 1002 D 128 D 3 D Oxefcee bD 8000 D Enabled D Total number of Fabric Maps 1 RB201 68 fc24 show running config fcoe fcoe fabric map default vlan 1002 Strategic Solutions Lab Page 62 BROCADE 2 Optional To modify the default existing FCoE parameters enter the config fcoe fabric map command in the running config Default configuration is recommended Enabling FCoE Port on Interface TenGigabitEthernet 4 Configure FCoE on the TenGigabitEthernet interface 5 Verify the FCoE configuration fcoeport default 6 Verify t
76. ogging into both switches and going through several configuration steps as shown below For VCS Fabrics the only action required to establish a Brocade ISL Trunk is connecting cables to the two switches that are within the same Port Group in each switch No additional configuration is required Configuring LAG for 2 members Configuring ISL Trunking for up to 8 members Execute the following commands on one switch configure terminal interface port channel 1 switchport switchport mode trunk switchport trunk allowed vlan all qos flowcontrol tx on rx on mtu 9208 no shutdown Absolutely no configuration required interface tengigabitethernet 1 0 5 channel group 1 mode active type standard Total commands O no shutdown interface tengigabitethernet 1 0 6 channel group 1 mode active type standard no shutdown exit Repeat same commands on other end switch Total commands 30 Link Utilization and Load Balancing To avoid too much traffic on a given link in a LAG the hashing algorithm has to have enough entropy for the various traffic flows so traffic will be allocated without exceeding the bandwidth of any single link In the test case below three traffic flows from port 1 2 and 3 are hashed to a single link in the LAG causing unexpected congestion and a bottleneck to occur Changing how the hash allocates traffic to links requires manual configuration changes and in some configurations it can be hard or impossible to avoid
77. orts and track priority e Hold time e Capability of non owner master to accept packets destined to virtual IP address The VRRP standard protocol in RFC 3768 has a few limitations drawbacks A proprietary version of VRRP that overcomes these limitations in VRRP E VRRP Extended developed by Brocade for use in Brocade IP enabled devices 4 2 1 VRRP vs VRRP E The following table summarizes the differences between VRRP and VRRP E protocols There are only master and backups There is no owner All routers are backup at startup and the backup with highest priority becomes the master Only virtual router owner responds to Any master can respond to the ICMP the ICMP and IP packets destined to and IP packets destined to the virtual the virtual IP address IP address 00 00 5e 00 01 vrid where 02 e0 52 hash value vrid where VRRP router that has virtual router s Virtual Router IP address es as real interface Owner address is the owner of virtual router and has the highest priority Packets destined to Virtual IP e vrid is user configured 1 hash value is lower 2 byte byte virtual router identifier value of BBCC 25 Hex Same VRID cannot be used 99AA when virtual IP address for two virtual router groups is say OXO9AABBCC Virtual MAC Strategic Solutions Lab Page 33 Source MAC in VRRP Control Packets Gratuitous ARP Track Priority Preemption VRRP IP Control Packets Backup advertisement in
78. oughput of a VCS Fabric exceeds an STP network at close to 2 1 margin In public cloud application latency testing STP network latency is 50 to 60 times greater than VCS Fabric latency This is an enormous advantage for a VCS Fabric It is clear that VCS Fabric technology employs superior routing switching and load balancing high performance with very low latency in a mesh network topology 1 9 Ethernet LAG Vs Brocade ISL Trunking Link aggregation bundles multiple physical Ethernet links into a single logical link or trunk The logical trunk is called a Link Aggregation Group LAG Brocade ISL Trunking is one of the Brocade ASIC features that bundles multiple Inter Switch Links ISL into a single logical ISL trunk When a switch is connected to a VCS Fabric ISLs automatically form between directly connected switches When more than one ISL connects two switches a Brocade ISL Trunk can automatically form if the ISLs are in the same ASCI Port Group boundary in each switch Brocade ISL Trunking is a true plug and play feature that does not require special configuration procedures or user intervention LAG and Brocade ISL Trunking appear similar but very different in how they are implemented and how they perform In the diagram below two switches are connected with multiple links but use LAG Strategic Solutions Lab Page 13 VDX6720 Connected with LAG IXIA 1 4 1 IXIA 1 4 2 IXIA 1 4 3 1 2 3 VDX672
79. p server contact string location string sys descr string RB1 exit RB1 show running config snmp server 9 9 Host Name A host name can be from 1 through 30 characters long It must begin with a letter and can contain letters numbers and underscore characters The default host name is swO The host name is displayed at the system prompt This test confirms hostname configuration RB1 conf t RB1 switch attributes rbridge ID host name hostname RB1 exit RB1 show running config switch attributes host name 9 10 Switched Port Analyzer SPAN Switched Port Analyzer is used on a network switch to send a copy of network packets seen on one switch port to a network monitoring connection on another switch port If you are interested in listening or snooping on traffic that passes through a particular port Switched Port Analyzer SPAN copies the packets to a port connected to a packet analyzer 9 10 1 Bi directional Mirroring RB1 conf t RB1 monitor session 1 RB1 source te 1 0 1 destination te 1 0 2 direction both RB1 exit 9 10 2 Ingress Mirroring RB1 conf t RB1 monitor session 1 RB1 source te 1 0 1 destination te 1 0 2 direction rx RB1 exit 9 10 3 Egress Mirroring RB1 conf t RB1 monitor session 1 RB1 source te 1 0 1 destination te 1 0 2 direction tx RB1 exit Strategic Solutions Lab Page 82 BROCADE 23 9 11 Remote Monitoring RMON Remote monitoring RMON is an Internet Engineering Task Force
80. re able to see each other s advertisement frames Strategic Solutions Lab Page 41 BROCADE 23 Virtual MAC address VMAC is distributed to all the VCS nodes within the cluster When a VCS node becomes VRRP master it triggers VMAC distribution across the cluster which is then added to each individual node s MAC table as an entry pointing towards the master node To begin initially configure VRRP use commands described in section 3 2 3 1 for the above mentioned topology a Configure VRRP group 100 under interface ve 10 with virtual ip address 20 0 0 100 on both R1 and R2 b Enablethe group 100 on both R1 and R2 c Verify that the VMAC is learnt on R1 which is the Master d Verify traffic forwarding works as expected using various show commands 4 2 4 2 Test Case 2 Configure Active Active VRRP E Over vLAG in a VCS Fabric In addition to the above mentioned VRRP configuration VRRP E short path forwarding feature is also available in VCS mode on VE interfaces as mentioned in Sec Error Reference source not found A backup router participates in VRRP E session only when short path forwarding is configured and hence has its effect only on the backup router though all VCS nodes are aware of VRRP E session and participating nodes in each session Once short path forwarding is configured a backup router routes the frames destined to the VMAC instead of switching them to the master interface ve 10 E ip address 162 85 1 1 24
81. rs initially on int te 0 0 1 and migrates to int te 0 0 5 Then repeat the test with SMAC1 migrating to int te 0 0 5 and SMAC2 migrating to int te 1 0 5 Repeat this test case in Standalone mode as well 2 5 4 Multiple MACs From One Port to Another Port in a Different Port Profile Verify that multiple MAC addresses associated to different port profiles resume traffic when some of them are migrated to physical interface in the same switch and some to port in a different switch Example PP1 is associated to SMAC1 and PP2 is associated to SMAC2 SMAC1and SMAC2 appears initially on int te O O 1 and migrates to int te 0 O 5 Then repeat the test with SMAC1 migrating to int te 0 0 5 and SMAC2 migrating to int te 1 0 5 Repeat this test case in Standalone mode as well 2 5 5 Multiple MACs From Different Ports in Same Port Profile to Port in Same or Different Switch Verify that multiple MAC addresses on different ports in the same switch that are associated to the same Port Profile resume traffic when migrated to a single interface in the same switch or to different switches Note It is expected that performance will be affected when they use the same physical interface Strategic Solutions Lab Page 25 BROCADE 23 Example PP1 is associated to SMAC1 as well as SMAC2 SMAC1appears initially on int te O O 1 and SMAC2 appears on int te 0 0 10 Now both SMAC1 and SMAC2 migrates to int te 0 0 5 Then repeat the test with both SMAC1 and
82. s dt 3 Services and applications E Summary of VM 58 X vM 58 vM 58 2 VM S9 01 Ee E eas ER VM en 02 Status Offline Auto Start Yes VM 60 01 Alerts none vM 60 02 Preferred Owners PMENONSS wINH 721 amp v28 CD2 wIN ETAPUMAS3OT WIN TNGS0DH3 vM 61 DI PR settings for M_58 Ma El vM 61 02 Sek poa amp Hardware 4j Legacy Network Adapter d TI Add Hardware l d jk BIOS Specify the configuration of the network adapter or remove the network adapter d WIN ELAPUNASO o Boot from Legacy Network adapter Network d WIN TNQSODH91 x Local rea Connection 4 Vrtualtiebmork 8 e Cluster Shared Volum m ich Local Area Connection 4 Virtual Network m Storage E MAC Address E 33 Networks Marisol sas nde teas Cluster Events gai IR 4 S IDE Controller 0 Static Hard Drive aaa MER s E E IDE Controller 1 ee A a d Associate VM MAC addresses to the appropriate port profile VDX config port profile test profile static 0005 1ed7 8def e Enable AMPP on the physical interface or port channel that connects to the server say ESX hosting a VM VDX config interface tengigabitethernet 236 0 8 VDX config port profile port f Start ping or any traffic Since a Port Profile has Access capability the ingress traffic is expected to be untagged The Port Profile is applied to traffic received on this interface Strategic Solutions Lab Page 21 BROCADE 23 VDX show port profile
83. s calculated by constructing a shortest path tree OSPF recalculates routes quickly in the face of topological changes utilizing a minimum of routing protocol traffic OSPF provides support for equal cost multipath An area routing capability is provided enabling an additional level of routing protection and a reduction in routing protocol traffic In addition all OSPF routing protocol exchanges are authenticated 4 1 1 Topology used The topology used for testing Layer 3 on Brocade VDX switches is as shown below Strategic Solutions Lab Page 30 BROCADE 4 1 2 Validation of OSPF Step 1 Configuring OSPF on VCS switches initially begins by acquiring a Layer 3 License Step 2 Enable OSPF globally on the rbridge id Step 3 Configure required area id under router OSPF command Step 4 Configure interfaces under interfaces ve or Layer 3 as required Step 5 Verify OSPF neighbors are up Step 6 Use other show commands to verify OSPF configuration and route table Strategic Solutions Lab Page 31 BROCADE 2i Step 7 f desired configure static routes with different cost metric distance values and verify that the static route configuration is present in the routing table Strategic Solutions Lab BROCADE 23 ISIS Codes L1 Level 1 L2 Level 2 OSPF Codes i Inter Area 1 External Type 1 2 External Type 2 s Sham Link Destination Gateway Port Cost Type Uptime 1 0 0 0 0 0 10 20 232 1 mgmt 1
84. sss 19 9 1 2 Configure a Dynamic IPv4 Address Using DHCP a 19 9 1 3 Configure a Static IPVO AQU EE 19 9 1 4 Configure a Dynamic IIPVG AQUIESS ia 19 di BE IG UP ADDRESS aE 79 9 3 IN BAND MANAGEMENT VIA VLAN PHYSICAL OR PORT CHANNEL INTERFACES eene 80 9 3 1 Configure In band Management via VLAN a 80 9 3 2 Configure In band Management via Physical Interface sees 80 9 3 3 Configure In band Management via Port Channel 80 94 SUPPORTS AVE AUTOMATION it pub 80 9 4 1 Suppontsave tod USB CIV 6 Eege Ee 80 9 4 2 Supportsave to an External Host NENNEN 81 9 5 NETWORK TIME PROTOCOL NTP AND LOCAL CLOCK geed 81 9 5 1 very NTP ODeratiO iR E 81 9 5 2 Verify Local Clock Operation EN 81 9 5 3 Sa a T T Im 81 SENE OOO S 81 WA 60 c MH 81 9 8 SIMPLE NETWORK MANAGEMENT PROTOCOL SNMP NENNEN 82 Ss og t 82 9 10 SWITCHED PORT ANALYZER SPAN EE 82 9 10 1 Bi directional Mirroring Au 82 9 10 2 Jee SC dee E EE m em 82 9 10 3 ESOS IV ONS 82 9 11 REMOTE MONITORING IHMONT NEEN 83 SAL RADIU cc icons 83 Strategic Solutions Lab Page iv BROCADE 23 9 13 TERMINAL ACCESS CONTROLLER ACCESS CONTROL SYSTEM PLUS TACACST EE 83 9 14 ROLE BASED ACCESS CONTROL RBA EEN 83 9 14 1 eE EE 84 9 14 2 Create a
85. t profile VDX_49113 config port profile test_profile security profile VDX_49113 config security profile mac access group acl1 in NOTE Make sure to associate the MAC addresses defined in Security Profile ACL to the port profile Section 3 1 3 step d 4 Sendthe traffic and verify the application of the access list using following command VDX 491134 show statistics access list mac acl1 in NOTE User should see acl1 is getting applied through the port profile Repeat above tests for a Fengigabit Ethernet b Gigabit Ethernet C LAG VLAG both 1G and 10G 2 4 3 Validation of QoS Setup the following 1 Create a port profile with the desired VLAN configuration using Section 3 1 3 2 Create a QoS profile using following procedure VDX_49113 config port profile test profile VDX_49113 config port profile test_profile qos profile 3 The following qos and cee options are available under the QoS profile Strategic Solutions Lab Page 23 BROCADE 23 VDX_49113 config qos profile t gos Possible completions COS Configure default Class of Service CoS cos mutation Configure CoS to CoS mutation Max Size 32 cos traffic class Configure CoS to Traffic Class map Max Size 32 flowcontrol IEEE 802 3x Flow Control trust Configure QoS Trust VDX_49113 config qos profile cee Possible completions lt string gt NOTE User needs to configure appropriate cos mutation maps cos traffic class maps and cee maps b
86. te Rate 96 Pausing 96 IXIA 1 4 1 lt gt LAG 14 880 953 00 5 491 509 00 IXIA 1 4 4 64 Bytes IXIA 1 4 2 lt gt LAG 812 744 00 617 778 50 IXIA 1 4 5 1518 Bytes IXIA 1 4 3 lt gt LAG 138 581 00 120 703 00 IXIA 1 4 6 IXIA 1 4 1 lt gt ISL Trunk 14 880 953 00 14 880 953 00 IXIA 1 4 4 64 Bytes IXIA 1 4 2 lt gt ISL Trunk 812 744 00 812 744 00 IXIA 1 4 5 1518 Bytes IXIA 1 4 3 lt gt ISL Trunk 138 581 00 138 581 00 IXIA 1 4 6 9000 Bytes Link Resiliency To test link resiliency and measure how fast a link can failover the second topology with three links in a trunk can be used One link in the trunk shut off with bi directional traffic flows of 64 1518 and 9000 bytes using the the trunk at a rate of 5 Gbps each Using IxNetwork statistics the failover time is measured for each traffic flow 64 5G 1 ab 64 1518 5G 2 246720 VDX6720 gt Las 1518 5 106 5 9000 5G 3 3 Lean 9000 7 10G Strategic Solutions Lab Page 17 BROCADE 23 The flowing table shows data collected from 7 trial runs when failing any one of the links in the trunk The test results are for both a LAG and Brocade ISL Trunk configuration The link failover required for LAG is over 50 milliseconds while the link failover required for the Brocade ISL Trunk is no greater than 7 22 micro seconds The LAG failover is on the order of 7 times as long as the Brocade ISL Trunk failover
87. tegic Solutions Lab Page 48 BROCADE Next we ll configure all four ports on the Nexus 7000 that will be part of our port channel that will be connected to the VCS Fabric 5 2 2 4 VCS vLAG and Cisco NX OS Port Channel Verification Verify the vLAG is configured in the VCS Fabric you want to see this you want to see this Verify the vLAG connection on the Nexus 7000 Note Next to po200 we see SU from the flags this is telling you that this PC is switched and up which is what we want Also next to each of the ports in our PC we see each port with the letter P next to it which indicates that the port is up and a member in our PC Strategic Solutions Lab Page 49 BROCADE 5 2 3 Create OSFP Neighbors Between Nexus 7000 and VCS 5 2 3 1 Configure Two Ports on Each VDX with OSPF area O Note Some of the NOS messages to the console were removed for clarity 5 2 3 2 Configure Two Ports on Each Nexus 7000 with OSFP area O Strategic Solutions Lab Page 5O BROCADE 5 2 3 3 OSPF Verification 5 2 3 4 Nexus 7000 OSPF Route Checking Note On each Nexus 7000 verify some number of intra area routes exist via the show ip route command done on each of the two Nexus 7000s Strategic Solutions Lab Page 51 BROCADE 23 5 2 3 5 VCS OSFP Route Checking Strategic Solutions Lab BROCADE 23 5 2 3 6 Nexus 7000 with VRF up to VCS Fabric with OSPF Next configure VRF or Layer 3 Virt
88. torage iSCSI 13 695 648 13 695 648 5 879 54 720 00 03 2 02 52 8 Storage_to_Server Strategic Solutions Lab Page 11 Lippis Cloud Test Result for VCS Fabric Network Traffic Item Tx Frames Loss Store 96 Forward Avg Latency ns NS Client to Server 177 428 68 177 428 62 58 027 6 9 NS Server_to_Client 42 616 800 42 616 770 uli 83 870 Store Forward Min Latency ns BROCADE 23 Store First Last Forward TimeStamp TimeStamp Max Latency ns 106 460 00 03 2 02 18 8 238 840 00 03 2 dli 18 8 EW HTTP z 019 30 SC 019 17 E 69 538 321 080 00 03 2 dii 18 8 SCH 761 64 D 761 34 55 922 1 040 98 120 00 03 2 02 18 8 o EW 46 516 783 46 516 730 81 356 230 920 00 03 2 02 18 8 Database to Server iSCSI 19 465 773 19 465 764 55 037 99 740 00 03 2 02 18 8 Server_to_Storage iSCSI 10 948 850 10 948 842 82 636 235 260 00 03 2 02 18 8 Storage to Server Lippis Cloud Test Result for Spanning Tree Network The following graph compares the average latency for cloud computing applications when using VCS Fabric and STP The STP network has substantially higher latency than a VCS Fabric Strategic Solutions Lab Page 12 BROCADE 23 Latency Comparism of VCS Fabric vs Spanning 1 Switches Fully Meshed Topology with Lippis Cloud Test Tree in 90 000 80 000 70 000 D o o O o B VCS Fabric Average Latency ns B RSTP Based on these results for a four switch full mesh network thr
89. trate fabric comprises a single unit Enable the link between RB1 and RB2 Show that the fabric has formed with two VDX switches Strategic Solutions Lab Page 3 BROCADE 1 4 Automatic Creation of ISLs and Trunk Groups A VCS Fabric simplifies the configuration and operation of Layer 2 Ethernet networks New links between switches are automatically configured and require no manual simplifying configuration The following tests show how ISLs and Trunk Groups form automatically when cables are connected Add a second link between RB1 and RB2 on different port group Add third link between RB1 and RB2 on same port group as the first link Strategic Solutions Lab Page 4 BROCADE 2i Add a link from RB3 to both RB1 and RB2 and verify the fabric updates the topology automatically Strategic Solutions Lab BROCADE 1 5 MAC Address Learning A feature of a VCS Fabric is the distributed control plane connecting all switches in the fabric The Ethernet name server eNS is a distributed service that maintains information about the MAC address attached of all devices connected to the fabric and the switch port the devices is connected to The following tests will demonstrate that the MAC address table is distributed across all switches in the fabric Verify that the MAC address table is empty on all RBridges in the fabric At this point since we haven t initiated any traffic across the fabric there should be no
90. ualization NX OS speak on the 30 network to provide some isolation as is commonly done for a data center service provider environment Create VRF on a Nexus 7000 Enable VRF under the OSFP process Enable VRF on the 30 network interface that is running OSPF in the VCS Fabric VRF OSFP verification Notice the 30 network is no longer visible in the default VRF as expected The default VRF like the default VDC cannot be deleted on a Nexus 7000 Show the VDX switch in the OSPF VCS Fabric with the VRF OSPF neighbor The 30 network is up and running Verify the VRF configuration on the Nexus 7000 Strategic Solutions Lab Page 53 BROCADE 23 Strategic Solutions Lab Page 54 BROCADE 23 Strategic Solutions Lab Page 55 BROCADE 23 6 Multi hop FCoE Leveraging Brocade VCS Fabric technology Brocade VDX Data Center Switches provide the foundation for Ethernet fabrics revolutionizing the design of Layer 2 networks and enabling cloud optimized networking One of the key differentiators of Brocade VCS Fabric technology is the support for multi hop FCoE functionality Users can connect FCOE initiators and FCoE targets anywhere in the VCS Fabric and run FCOE traffic Calisto Calisto FCoE Host CNA 6 1 Install FCoE License The FCoE BASE license is required on VDX 6720 6730 switches that have FCoE servers targets directly attached 1 View existing licenses on switch RB201 68 fc24
91. ucting testing will have a working knowledge of Brocade VDX Switches Brocade NOS and have access to the latest Brocade Network Operating System Administrator Guide The following documents are valuable resources for the designer In addition any Brocade release notes that have been published for NOS FOS the Fibre Channel switching and VDX Switch products should be at hand before conducting these test cases Related Documents References e Brocade Network OS NOS Administrator Guide v3 0 1 e Brocade Fabric OS Administrator Guide R7 0 1 Document History 2013 02 27 Initial Version with NOS 3 0 1 and FOS 7 0 1 Strategic Solutions Lab Page 1 BROCADE 23 1 Brocade VCS Fabric Layer 2 Functionality 1 1 Topology used Below is the test configuration It consists of the following devices and constraints e Three Brocade VDX 6720 24 switches running either NOS v2 1 1 or v3 0 e Only Layer 2 connectivity tests are provided e Connectivity to a core consisting of a pair of Cisco Nexus 7000 is tested The two Nexus 7000 use virtual Port Channel vPC so the Nexus 7000 appear as a single logical Layer 2 switch e The test cases are not restricted to specific servers or OS versions Typically more than one server is connected to the fabric if VM mobility and the VCS Fabric Automated Migration of Port Profiles AMPP feature is being tested e Servers are configured with virtual machines VM that are used to create traffic duri
92. ve with VID 1 Should receive with VID 1 It can receive for short period of time with VID 1 and it should stop flooding after 250 ms This can also be verified in manner such that after 30 sec say we should not see flooding It can receive for short period of time with VID 400 and it should stop flooding after 250 ms This can also be verified in manner such that after 30 sec say we should not see flooding Should receive untagged Should receive untagged Page 85 BROCADE 23 Forward Yes if DST mac is in mac table 7 Access VID 1 default disable Trunk allowed all VID 1 Should receive untagged mode only initial packets PP application Yes Flood Forward No Access disable VID 400 Learning Yes on vlan Should receive with mode VID 1 default 400 VID 400 only initial packets PP application No Flood No 2 Trunk VLAN profile table for verification VLAN VLAN Vlan Destination Ingress With AMPP Port Expected Profile Config dot1q Port Traffic application captured trace native on Destination port Trunk allow all Trunk Untagged Should not receive mode allowed all anything Trunk allow all enable Trunk VID 0 Should not receive mode allowed all anything PP application Yes Flood No Trunk allow all enable Trunk VID 1 Should receive mode allowed all with VID 1 PP application Yes Flood Yes if Dst mac is not learnt Forward Yes if DST mac is in mac table Trunk
93. vrrp entended group 1 virtual ip 162 85 1 5 short path forwarding interface ve 10 p address 162 85 1 2 24 vrrp entended group 1 virtualip 162 85 1 5 short path forwarding VCS Cloud IP 162 85 1 100 G w IP 162 85 1 5 IP 162 85 1 101 G w IP 162 85 1 5 Active Active VRRP E load balancing in VCS The VRRP E active active load balancing scenario is shown in the figure above where VRRP E with short path forwarding SPF is configured on R1 amp R2 Other switches R3 amp R4 do not participate in VRRP E but are aware of the VRRP E sessions and members in VCS Switches R1 R2 exchanges advertisement frames over VLAN 10 and elect a master say R1 Since SPF is enabled on R2 when a frame is received which has to be routed by the VRRP E master R2 routes the frame locally Switches R3 amp R4 have the Virtual MAC Layer 2 entry pointed to a virtual node which is uniquely allocated for each VRRP E session in the VCS Fabric A virtual node is a grouping of physical nodes in Strategic Solutions Lab Page 42 BROCADE 23 the VCS Fabric Each frame which enters into the VCS Fabric via R3 R4 hits this entry and the packet is load balanced among the virtual node group members viz R1 amp R2 The packet load balancing is performed in the fast path using hardware based hashing To begin initially configure VRRP E use commands described in section 3 2 3 1 for the above mentioned topology a b C d Configure

BrocadeVCSFabric-TestCases_V1-0_2013-02

Contents

Download Pdf Manuals

Related Search

Related Contents