Interconnecting Brocade VDX Switches with HP Virtual Connect Modules

Transcription

1 WHITE PAPER CONNECTIVITY FOR VDX AND VIRTUAL CONNECT Interconnecting Brocade VDX Switches with HP Virtual Connect Modules This document explains the configuration process for Ethernet, IP, and FCoE connectivity between Brocade VDX and HP Virtual Connect technologies. Specific information regarding FC and FCoE target connectivity is outside the scope of this document, but can be found in the Brocade Network OS Administrator s Guide and Brocade Fabric OS Administrator s Guide.

2 INTRODUCTION Ethernet, IP, and FCoE connectivity between the Brocade VDX switch family and the HP Virtual Connect family is supported by both Brocade and HP. Validation tests were conducted in Brocade s OEM Systems Engineering Labs, with additional support from the HP Virtual Connect team. 10GbE and 40 GbE connectivity have been validated between the Brocade VDX6720, 6730, 6740, and 6740T with the HP Virtual Connect FlexFabric 10Gb/24-port Module, HP Virtual Connect Flex-10/10D Module, and the new Virtual Connect Flex Fabric-20/40 F8 Module. The VDX 6720, 6730, or 6740 may be used as the uplink ToR switch for 10 GbE connectivity with or without multi-hop FCoE. These switches may be part of a larger VCS fabric. While FCoE traffic is supported in multiple hops within the fabric, Brocade strongly recommends separating the FCoE traffic to either its target or to a native FC SAN in as few hops as possible. It is assumed throughout this document that the Brocade VCS Fabric is already configured in Logical Chassis mode, and that the fabric is fully merged and stable. All commands shown shall be executed from the cluster Virtual IP address unless specifically stated otherwise. Interoperability concerns between different models of VDX or code levels are not addressed in this document. Please consult the Network OS Administrator s Guide and release notes for your versions of firmware. 2

3 CONFIGURING 10GBE CONNECTIVITY WITHOUT FCOE When configuring 10GbE connectivity between Brocade VDX and HP Virtual Connect without FCoE, both LACP standard LAGs and Brocade vlags may be used. For maximum resiliency in your design, it is recommended that you use vlags. The Brocade VDX model used in the Top of Rack position in this design may be a 6720, 6730, or The HP Virtual Connect module may be either a FlexFabric 10Gb/24-Port, Flex-10/10D, or FlexFabric-20/40 F8 module. Note that the adjacent slots in the chassis must contain the same Virtual Connect module type (i.e. Interconnect Bays 1 and 2 must both have the same model inserted. See the Virtual Connect User s Guide for more details). Both the Brocade VDX switch and the HP Virtual Connect modules require several configuration steps to prepare them for interconnectivity. The Shared Uplink Sets on the VC Module must be created and configured for the proper Ethernet VLANs. The Brocade VDXs must have port channels configured and provisioned for the proper VLANs. In this configuration, we will assume that the VDX switches have already been configured as an Ethernet Fabric in Logical Chassis mode, and that the required VLAN(s) have already been created. All VDX commands assume that the port being configured is in its default configuration. If a port is not in default configuration, please remove all added configuration items from the port before proceeding. VLAG Option 3

4 Preparing the HP Virtual Connect for connectivity. Two separate Shared Uplink Sets must be created, one for each module. 1. On the VC module in bay 1, create a Shared Uplink Set consisting of the uplink ports connected to the VDX. In this example, the 10GbE ports X1 and X2 are connected to 1/0/3 and 2/0/5, respectively (One port on each ToR VDX will result in a resilient vlag). The uplink set is given a name, and the timeout period for LACP is left at the default - short. 2. Add any VLANs required for VLAN tagging. In this example, VLAN 100 is used. This network is called Network_100A. If you are unsure what VLANs you need, or do not know if you require tagged or untagged VLAN access, consult your network administrator and the Virtual Connect User s Guide. 3. On the VC module in bay 2, create a second Shared Uplink Set consisting of the uplink ports connected to the other VDX switch. The second SUS in this example uses 10GbE ports X1 and X2 on the VC module, and ports 1/0/4 and 2/0/6 (One port on each ToR VDX will result in a resilient vlag). 4

5 4. Add any VLANs required for VLAN tagging. In this example, VLAN 100 is used. Note that you must also create this network as a separately defined network, even though they use the same VLANs. This network is called Network_100B. NIC teaming will be used to handle the multiple paths to the same network. If you are unsure what VLANs you need, or do not know if you require tagged or untagged VLAN access, consult your network administrator, and the Virtual Connect User s Guide. Preparing the Brocade VDX for Ethernet and IP Connectivity to the HP Virtual Connect Configure the VDX ports for port-channel connectivity to the Virtual Connect. Connect to the Logical Chassis VIP to configure ports in the fabric. In this example, VDX1 is configured as RBridge 1 and VDX2 is configured as RBridge Configure the port-channels sw0# config terminal Entering configuration mode terminal sw0(conf)# interface port-channel 10 sw0(config-port-channel-10)# switchport sw0(config-port-channel-10)# switchport mode trunk sw0(config-port-channel-10)# switchport trunk allowed vlan add 100 sw0(config-port-channel-10)# no shutdown sw0(config-port-channel-10)# interface port-channel 20 sw0(config-port-channel-20)# switchport sw0(config-port-channel-20)# switchport mode trunk sw0(config-port-channel-20)# switchport trunk allowed vlan add 100 sw0(config-port-channel-20)# no shutdown sw0(config)# interface TenGigabitEthernet 1/0/3 sw0(conf-if-te-1/0/3)# channel-group 10 mode active type standard sw0(conf-if-te-1/0/3)# lacp timeout short sw0(config)# interface TenGigabitEthernet 1/0/4 sw0(conf-if-te-1/0/4)# channel-group 20 mode active type standard sw0(conf-if-te-1/0/4)# lacp timeout short sw0(config)# interface TenGigabitEthernet 2/0/5 sw0(conf-if-te-2/0/5)# channel-group 10 mode active type standard sw0(conf-if-te-2/0/5)# lacp timeout short sw0(config)# interface TenGigabitEthernet 2/0/6 sw0(conf-if-te-2/0/6)# channel-group 20 mode active type standard sw0(conf-if-te-2/0/6)# lacp timeout short 5

6 This configuration will result in a resilient pair of vlag port-channels between the HP BladeSystem and the Brocade VCS Fabric. Standard LAG Option If standard LAGs were desired instead, the configuration of the Virtual Connect module remains the same (aside from the cabling, which would need to change to reflect the different topology. In this case, the 10GbE ports on VC1 X1 and X2 are connected to 1/0/3 and 1/0/4, respectively. Follow the same convention for VC2 and VDX2. 6

7 The VDX configuration would differ as follows: 1. Configure the port-channels sw0# config terminal Entering configuration mode terminal sw0(conf)# interface port-channel 10 sw0(config-port-channel-10)# switchport sw0(config-port-channel-10)# switchport mode trunk sw0(config-port-channel-10)# switchport trunk allowed vlan add 100 sw0(config-port-channel-10)# no shutdown sw0(conf)# interface port-channel 20 sw0(config-port-channel-20)# switchport sw0(config-port-channel-20)# switchport mode trunk sw0(config-port-channel-20)# switchport trunk allowed vlan add 100 sw0(config-port-channel-20)# no shutdown sw0(config)# interface TenGigabitEthernet 1/0/3 sw0(conf-if-te-1/0/3)# channel-group 10 mode active type standard sw0(conf-if-te-1/0/3)# lacp timeout short sw0(config)# interface TenGigabitEthernet 1/0/4 7

8 sw0(conf-if-te-1/0/4)# channel-group 10 mode active type standard sw0(conf-if-te-1/0/4)# lacp timeout short sw0(config)# interface TenGigabitEthernet 2/0/5 sw0(conf-if-te-2/0/5)# channel-group 20 mode active type standard sw0(conf-if-te-2/0/5)# lacp timeout short sw0(config)# interface TenGigabitEthernet 2/0/6 sw0(conf-if-te-2/0/6)# channel-group 20 mode active type standard sw0(conf-if-te-2/0/6)# lacp timeout short This configuration will result in a resilient pair of LACP port-channels between the HP BladeSystem and the Brocade VCS Fabric. CONFIGURING 40GBE CONNECTIVITY WITHOUT FCOE When configuring 40GbE connectivity between Brocade VDX and HP Virtual Connect without FCoE, both LACP standard LAGs and Brocade vlags may be used. For maximum resiliency in your design, it is recommended that you use vlags. The Brocade VDX model used in the Top of Rack position in this design may be a VDX 6740 or 6740T. The HP Virtual Connect module may be a FlexFabric-20/40 F8 module. The same topologies used for 10GbE connectivity are valid here. Note that breakout mode from the VC to the VDX is not supported at this time. Virtual Connect breakout mode uses a DAC Splitter Cable (HP BladeSystem c-class 40G QSFP+ to 4x10G SFP+ 3m Direct Attach Copper Splitter Cable B21 and HP BladeSystem c-class 40G QSFP+ to 4x10G SFP+ 5m Direct Attach Copper Splitter Cable B21), which is not supported on the VDX. Both the Brocade VDX switch and the HP Virtual Connect module require several configuration steps to prepare them for interconnectivity. The Shared Uplink Set on the VC Module must be created, and configured for the proper Ethernet VLANs. The Brocade VDX must have a port channel configured and provisioned for the proper VLANs. In this configuration, we will assume that the VDX switches have already been configured as an Ethernet Fabric in Logical Chassis mode, and that the required VLAN(s) have already been created. All VDX commands assume that the port being configured is in its default configuration. If a port is not in default configuration, please remove all added configuration items from the port before proceeding. The adjacent slots in the chassis must contain the same Virtual Connect module type (i.e. Interconnect Bays 1 and 2 must both have the same model inserted. See the Virtual Connect User s Guide for more details). 8

9 VLAG Option Preparing the HP Virtual Connect for connectivity. Two separate Shared Uplink Sets must be created, one for each module. 1. On the VC module, create a Shared Uplink Set, consisting of the uplink ports connected to the VDX. In this example, the 40GbE ports Q1.1 and Q2.1 are connected to 1/0/51 and 2/0/51, respectively (One port on each ToR VDX will result in a resilient vlag). The uplink set is given a name, and the timeout period for LACP left at the default - short. 9

10 2. Add any VLANs required for VLAN tagging. In this example, VLAN 100 is used. This network is called Network_100A. If you are unsure what VLANs you need, or do not know if you require tagged or untagged VLAN access, consult your network administrator and the Virtual Connect User s Guide. 3. On the VC module, create a second Shared Uplink Set, consisting of the uplink ports on the VC module in bay 2 that are connected to the other VDX switch. The second SUS in this example uses 40GbE ports Q1.1 and Q2.1 on the VC module, and ports 1/0/52 and 2/0/52 (One port on each ToR VDX will result in a resilient vlag). 4. Add any VLANs required for VLAN tagging. In this example, VLAN 100 is used. As in the case of the FCoE network, you must also create these networks as separately defined networks, even though they use the same VLANs. This network is named Network_100B. NIC teaming will be used to handle the multiple paths to the same network. If you are unsure what VLANs you need, or do not know if you require tagged or untagged VLAN access, consult your network administrator, and the Virtual Connect User s Guide. Preparing the Brocade VDX for Ethernet and IP Connectivity to the HP Virtual Connect Configure the VDX ports for port-channel connectivity to the Virtual Connect. Connect to the Logical Chassis VIP to configure ports in the fabric. In this example, VDX1 is configured as RBridge 1 and VDX2 is configured as RBridge 2. 10

11 1. Configure the port-channels sw0# config terminal Entering configuration mode terminal sw0(conf)# interface port-channel 10 sw0(config-port-channel-10)# speed sw0(config-port-channel-10)# switchport sw0(config-port-channel-10)# switchport mode trunk sw0(config-port-channel-10)# switchport trunk allowed vlan add 100 sw0(config-port-channel-10)# no shutdown sw0(conf-if-fo-2/0/52)# interface port-channel 20 sw0(config-port-channel-20)# speed sw0(config-port-channel-10)# switchport sw0(config-port-channel-20)# switchport mode trunk sw0(config-port-channel-20)# switchport trunk allowed vlan add 100 sw0(config-port-channel-20)# no shutdown sw0(config)# interface FortyGigabitEthernet 1/0/51 sw0(conf-if-fo-1/0/51)# channel-group 10 mode active type standard sw0(conf-if-fo-1/0/51)# lacp timeout short sw0(conf-if-fo-1/0/51)# shut sw0(conf-if-fo-1/0/51)# no shut sw0(config)# interface FortyGigabitEthernet 1/0/52 sw0(conf-if-fo-1/0/52)# channel-group 20 mode active type standard sw0(conf-if-fo-1/0/52)# lacp timeout short sw0(conf-if-fo-1/0/52)# shut sw0(conf-if-fo-1/0/52)# no shut sw0(config)# interface FortyGigabitEthernet 2/0/51 sw0(conf-if-fo-2/0/51)# channel-group 10 mode active type standard sw0(conf-if-fo-2/0/51)# lacp timeout short sw0(conf-if-fo-2/0/51)# shut sw0(conf-if-fo-2/0/51)# no shut sw0(config)# interface FortyGigabitEthernet 2/0/52 sw0(conf-if-fo-2/0/52)# channel-group 20 mode active type standard sw0(conf-if-fo-2/0/52)# lacp timeout short sw0(conf-if-fo-2/0/52)# shut sw0(conf-if-fo-2/0/52)# no shut This configuration will result in a resilient pair of vlag port-channels between the HP BladeSystem and the Brocade VCS Fabric. 11

12 Standard LAG Option If standard LAGs were desired, the configuration of the Virtual Connect module remains the same (aside from the cabling, which would need to change to reflect the different topology. In this case, the 40GbE ports on VC1 Q1.1 and Q2.1 are connected to 1/0/51 and 1/0/52, respectively. Follow the same convention for VC2 and VDX2. 12

13 The VDX configuration would then be as follows: 1. Configure the port-channels sw0# config terminal Entering configuration mode terminal sw0(conf)# interface port-channel 10 sw0(config-port-channel-10)# switchport sw0(config-port-channel-10)# speed sw0(config-port-channel-10)# switchport mode trunk sw0(config-port-channel-10)# switchport trunk allowed vlan add 100 sw0(config-port-channel-10)# no shutdown sw0(conf-if-fo-2/0/52)# interface port-channel 20 sw0(config-port-channel-20)# switchport sw0(config-port-channel-10)# speed sw0(config-port-channel-20)# switchport mode trunk sw0(config-port-channel-20)# switchport trunk allowed vlan add 100 sw0(config-port-channel-20)# no shutdown sw0(config)# interface FortyGigabitEthernet 1/0/51 sw0(conf-if-fo-1/0/51)# channel-group 10 mode active type standard sw0(conf-if-fo-1/0/51)# lacp timeout short sw0(conf-if-fo-1/0/51)# shut sw0(conf-if-fo-1/0/51)# no shut sw0(config)# interface FortyGigabitEthernet 1/0/52 sw0(conf-if-fo-1/0/52)# channel-group 10 mode active type standard sw0(conf-if-fo-1/0/52)# lacp timeout short sw0(conf-if-fo-1/0/52)# shut sw0(conf-if-fo-1/0/52)# no shut sw0(config)# interface FortyGigabitEthernet 2/0/51 sw0(conf-if-fo-2/0/51)# channel-group 20 mode active type standard sw0(conf-if-fo-2/0/51)# lacp timeout short sw0(conf-if-fo-2/0/51)# shut sw0(conf-if-fo-2/0/51)# no shut sw0(config)# interface FortyGigabitEthernet 2/0/51 sw0(conf-if-fo-2/0/51)# channel-group 20 mode active type standard sw0(conf-if-fo-2/0/52)# lacp timeout short sw0(conf-if-fo-2/0/52)# shut sw0(conf-if-fo-2/0/52)# no shut 13

14 This configuration will result in a resilient pair of LACP port-channels between the HP BladeSystem and the Brocade VCS Fabric. CONFIGURING BROCADE VDX AND HP VIRTUAL CONNECT FOR FCOE CONNECTIVITY The HP Virtual Connect module may be either a FlexFabric 10Gb/24-Port, Flex-10/10D, or FlexFabric-20/40 F 8 module. Adjacent slots in the chassis must contain the same Virtual Connect module type (i.e. Interconnect Bays 1 and 2 must both have the same model inserted. See the Virtual Connect User s Guide for more details). Only the standard LAG option is supported. A VLAG is not supported. All of the uplinks originating on one VC Module must terminate on the same VDX Switch. Failure to do this will result in unpredictable FCoE login behavior and is not supported. An FCoE network must be defined on each Shared Uplink Set (SUS). Both must use the same VLAN (1002 by default for connectivity to VDX) and be given unique names. The ports on the VDX connecting to a Virtual Connect module must be configured as a portchannel. The fcoeport default parameter on the VDX must be added to the port-channels and not the individual member links. These statements and requirements apply to both 10GbE and 40GbE connections. It is recommended to use the short timeout setting for LACP If 40 GbE is used for connection to a FlexFabric-20/40 F8, then the port channel s speed must be manually set to 40000, and the member ports reset by a shut no shut command execution. 14

15 10GbE and 40GbE Connectivity with FCoE The configuration process for adding FCoE functionality is nearly identical to that of the previous configuration tasks, but the Standard LAG option is the only supported topology. Follow the Standard LAG option instructions, but include the addition of a pair of FCoE networks to the Virtual Connect configuration, and add the fcoeport default parameter to the port-channels on the VDX, as shown in the next example, using 10GbE links (Follow the same modified procedure for doing this over 40GbE links). On the VC module, create a Shared Uplink Set, consisting of the uplink ports connected to the VDX 15

16 Create an FCoE Network to add to the SUS, ensuring that you use VLAN 1002 (Unless you have reconfigured FCoE on your Brocade VCS fabric. Add any VLANs required for VLAN tagging. In this example, VLAN 100 is used. If you are unsure what VLANs you need, or do not know if you require tagged or untagged VLAN access, consult your network administrator, and the Virtual Connect User s Guide. On the VC module, create a second Shared Uplink Set, consisting of the uplink ports connected to the other VDX switch. 16

17 Create an FCoE Network to add to the SUS, ensuring that you use VLAN 1002 (Unless you have reconfigured FCoE on your Brocade VCS fabric. Note that this needs to be a separate defined network in the Virtual Connect configuration, even though it will use the same VLAN. Host multipathing will be used to handle the multiple network paths. Add any VLANs required for VLAN tagging. In this example, VLAN 100 is used. As in the case of the FCoE network, you must also create these networks as separately defined networks, even though they use the same VLANs. NIC teaming will be used to handle the multiple paths to the same network. If you are unsure what VLANs you need, or do not know if you require tagged or untagged VLAN access, consult your network administrator, and the Virtual Connect User s Guide. Next, configure the VDX ports for port-channel connectivity to the Virtual Connect. Connect to the Logical Chassis VIP to configure ports in the fabric. In this example, VDX1 is configured as RBridge 1 and is connected to VC1. VDX2 is configured as RBridge 2 and is connected to VC2 sw0# config terminal Entering configuration mode terminal sw0(conf-if-te-1/0/4)# interface port-channel 10 sw0(config-port-channel-10)# switchport sw0(config-port-channel-10)# switchport mode trunk sw0(config-port-channel-10)# switchport trunk allowed vlan add 100 sw0(config-port-channel-10)# fcoeport default sw0(config-port-channel-10)# no shutdown sw0(config-port-channel-10)# interface port-channel 20 sw0(config-port-channel-20)# switchport sw0(config-port-channel-20)# switchport mode trunk sw0(config-port-channel-20)# switchport trunk allowed vlan add 100 sw0(config-port-channel-20)# fcoeport default sw0(config-port-channel-20)# no shutdown sw0(config)# interface TenGigabitEthernet 1/0/3 sw0(conf-if-te-1/0/3)# channel-group 10 mode active type standard sw0(conf-if-te-1/0/3)# lacp timeout short sw0(config)# interface TenGigabitEthernet 1/0/4 sw0(conf-if-te-1/0/4)# channel-group 10 mode active type standard sw0(conf-if-te-1/0/4)# lacp timeout short sw0(config)# interface TenGigabitEthernet 2/0/5 sw0(conf-if-te-2/0/5)# channel-group 20 mode active type standard sw0(conf-if-te-2/0/5)# lacp timeout short 17 sw0(config)# interface TenGigabitEthernet 2/0/6 sw0(conf-if-te-2/0/6)# channel-group 20 mode active type standard sw0(conf-if-te-2/0/6)# lacp timeout short

18 This configuration will result in a resilient pair of port-channels between the HP BladeSystem and the Brocade VCS Fabric. Traffic will be isolated between the VDX switches and Virtual Connect modules, similar to an A/B fabric, because of the separate network definitions on the Virtual Connect side. Traffic merges at the Brocade VCS fabric into a single Ethernet Fabric. Options for Storage Connectivity FCoE Native Storage may be connected to the Brocade VCS Fabric. Native FC SANs may be connected via FC-FC Routing Native FC SANs may be connected using Access Gateway mode (VDX6730 and 6740 only) For any of these options, the user should consult with the appropriate administrator s guides for all configuration specific information. Firmware level requirements, feature restrictions, or other concerns are all addressed in the admin guides and release notes for Brocade Fabric OS and Brocade Network OS. Equipment Validated Brocade VDX 6720 Brocade VDX 6730 Brocade VDX 6740 Brocade VDX 6740T HP Virtual Connect FlexFabric 10Gb/24-port Module HP Virtual Connect Flex-10/10D Module Virtual Connect Flex Fabric-20/40 F8 Module. OM-4 Fibre with LC-LC connectors OM-4 Fibre with MTP connectors References Brocade Network OS Administrator s Guide, v4.1.0 HP Virtual Connect for c-class BladeSystem Version 4.30 User Guide Brocade Fabric OS Administrator s Guide, v7.3 FCoE Cookbook for HP Virtual Connect 18

19 WHITE PAPER Corporate Headquarters San Jose, CA USA T: European Headquarters Geneva, Switzerland T: Asia Pacific Headquarters Singapore T: Brocade Communications Systems, Inc. All Rights Reserved. 09/14 HP-WP ADX, AnyIO, Brocade, Brocade Assurance, the B-wing symbol, DCX, Fabric OS, HyperEdge, ICX, MLX, MyBrocade, OpenScript, VCS, VDX, and Vyatta are registered trademarks, and The Effortless Network and The On-Demand Data Center are trademarks of Brocade Communications Systems, Inc., in the United States and/or in other countries. Other brands, products, or service names mentioned may be trademarks of others. Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning any equipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to this document at any time, without notice, and assumes no responsibility for its use. This informational document describes features that may not be currently available. Contact a Brocade sales office for information on feature and product availability. Export of technical data contained in this document may require an export license from the United States government.