brocade vdx 6740 deployment guide for vmware®...

53-1003742-0524 April 2015

Brocade VDX 6740Deployment Guide forVMware® EVO:RAIL

© 2015, Brocade Communications Systems, Inc. All Rights Reserved.

ADX, Brocade, Brocade Assurance, the B-wing symbol, DCX, Fabric OS, HyperEdge, ICX, MLX, MyBrocade, OpenScript, The EffortlessNetwork, VCS, VDX, Vplane, and Vyatta are registered trademarks, and Fabric Vision and vADX are trademarks of BrocadeCommunications Systems, Inc., in the United States and/or in other countries. Other brands, products, or service names mentioned may betrademarks of others.

Notice: This document is for informational purposes only and does not set forth any warranty, expressed or implied, concerning anyequipment, equipment feature, or service offered or to be offered by Brocade. Brocade reserves the right to make changes to this documentat any time, without notice, and assumes no responsibility for its use. This informational document describes features that may not becurrently available. Contact a Brocade sales office for information on feature and product availability. Export of technical data contained inthis document may require an export license from the United States government.

The authors and Brocade Communications Systems, Inc. assume no liability or responsibility to any person or entity with respect to theaccuracy of this document or any loss, cost, liability, or damages arising from the information contained herein or the computer programs thataccompany it.

The product described by this document may contain open source software covered by the GNU General Public License or other opensource license agreements. To find out which open source software is included in Brocade products, view the licensing terms applicable tothe open source software, and obtain a copy of the programming source code, please visit http://www.brocade.com/support/oscd.

http://www.brocade.com/support/oscd

Contents

Brocade VDX 6740 Deployment Guide for VMware® EVO:RAIL.................................................. 4Overview........................................................................................................... 4Configuration.....................................................................................................6

Example Configuration............................................................................................................18

Basic Configuration Worksheet............................................................................................... 23

VLAN Worksheet......................................................................................................................24

Creating A Serial Connection...................................................................................................25

Brocade VDX 6740 Deployment Guide for VMware® EVO:RAIL 353-1003742-05

Brocade VDX 6740 Deployment Guide for VMware® EVO:RAIL

● Overview......................................................................................................................... 4● Configuration...................................................................................................................6

OverviewThe goal of this document is to guide an installer through the process of connecting EVO:RAILappliances to VDX 6740 top-of-rack switches and configuring the switches to connect to an endcustomer's IP network.

VMware® EVO:RAIL combines VMware compute, networking, and storage resources into a hyper-converged infrastructure appliance to create a simple, easy to deploy, all-in-one solution. TheEVO:RAIL hyper-converged infrastructure appliance enables power-on to VM creation in minutes,radically easy VM deployment, easy non-disruptive patch and upgrades and simplified scale-out.

In VMware's current release, up to eight EVO:RAIL appliances can be grouped together as a singleEVO:RAIL cluster serviced by a single Virtual SAN Datastore. Each EVO:RAIL appliance contains fourserver nodes and each server node has two 10GbE ports which connect to the VDX switches asshown in Figure 1 below.

This guide walks you through the steps to add a single cluster of EVO:RAIL appliances to either one ortwo VDX 6740 top-of-rack switches. Additional clusters may be connected to the VDX 6740 switches.If you are adding more than one cluster, print out multiple copies of Table 4 on page 24 and fill themout separately for each cluster. For the second and additional clusters, refer to the VDX portassignments shown in Table 1 on page 13 and Table 2 on page 14 and use the next available portgroupings for each additional cluster. For example, if you used VDX ports 1-4 and 33-36 for the firstcluster and the second cluster is the same number of EVO:RAIL appliances, you can use VDX ports5-8 and 39-42.


4 Brocade VDX 6740 Deployment Guide for VMware® EVO:RAIL53-1003742-05

FIGURE 1 VMware® EVO:RAIL with Brocade VDX 6740 Top-of-Rack switch solution

The EVO:RAIL appliances must be connected to the IP network before they can be configured and thisrequires both physical connectivity to the customer's network as well as some basic knowledge of thecustomer's network.

Basic requirements include knowledge of

• The customer's default IP gateway address and subnet mask.• Whether VDX switch management will be in-band or out-of-band, and the IP address for switch

management.• The number and type of Ethernet ports required for EVO:RAIL appliance connectivity.• The number and type of Ethernet ports for the VDX inter-switch links (ISLs) which are used to

interconnect the switches to each other.• The number and type of Ethernet ports for the VDX network uplinks used to connect the switches to

the customer’s existing network.



The VDX 6740 switch comes with 24 10GbE ports enabled. If more than 24 10GbE ports are needed,or if 40GbE ports are needed, one or more license keys need to be installed on the VDX. It is assumedthe installer has the required license keys.

There are references to "Rbridge" and "Rbridge id" in the document. An Rbridge refers to a single VDX6740, and rbridge-id refers to the unique switch identifier.

There are references to in-band and out-of-band management in the document. This refers to whetherswitch management traffic is routed to an "out-of-band" management port on the switch (#5 in Figure 2on page 7) or whether management traffic is routed "in-band" to one of the other Ethernet ports. Inthis document, the serial console management port is used to configure the switch via a serial cableattached to the laptop. After this initial configuration, the VDX switch will be configured for either in-band or out-of-band management.

This guide requires no working knowledge of the VDX 6740, it walks the installer through all of therequired steps. Some of the configuration commands or terms may be unfamiliar to the installer, butthe guide is designed to walk the installer through the configuration step-by-step without requiring anyfurther knowledge of the commands or terms used. Simply following step-by-step instructions and ifyou're not sure about a given value, use the recommended value.

Configuration1. This guide assumes that the installer has a basic familiarity with the EVO:RAIL appliance

requirements, including how many appliances will be installed, and whether the EVO:RAILdeployment will use VLANs or will be flat. The installer should also know how many ports areavailable on the upstream switches that the VDX 6740 will connect to and whether they are 10GbEor 40GbE ports.

2. Installer laptop

a. Serial console port: The laptop needs to connect to the console port of the VDX 6740 (port#4 in Figure 2 ). A serial cable with an RJ-45 connector is provided with the VDX 6740 forthe purpose of connecting to the console port of the VDX. An appropriate adaptor may berequired for the laptop.

b. Serial console software: The installer will be required to perform the configuration via theserial port. A terminal emulator program, for example "PuTTY" or "Screen," is required forconsole access.

c. For more detail on configuring the serial connection to the serial console port, refer to Creating A Serial Connection on page 25 below.

Configuration


FIGURE 2 VDX 6740 front side

3. Installer laptop rights

a. Must be able to set up and use the serial console port, using a terminal emulator programon the laptop such as PuTTY or Screen.

4. Brocade VDX 6740

a. NOS 5.0.1a or later must be installed.b. The VDX is expected to be in the "factory default" configuration. If it is not in the factory

default state, reset the VDX as follows. First, login to the switch, the defaults are:

Username = admin

Password = password

You can either do a complete reset to factory default, which erases all configuration andinstalled license keys, or you can use an optional configuration parameter to reset all userconfigurations except the management IP address and any installed licenses (such asadditional 10GbE or 40GbE port licenses).

Do one of the following two steps:

i. Perform a simple reset to factory default erasing all configuration and installed licensekeys. Enter the global command: write eraseii. Reset all user configurations except the management IP address and optional licenses.Enter the global command: write erase rbridgeid <n>Where <n> is the configured RbridgeID number. If you are not sure of the RbridgeIDnumber, you can display it using the show rbridge-id command.

Required VDX Switch Configuration Information

5. Check if optional 10GbE or 40GbE licenses have been installed on the switch.

a. If a 10GbE or 40GbE license needs to be installed, apply the licenses to the VDX 6740using the instructions in this step. Otherwise skip to the next step.

To install a license key, enter the license add licstr command followed by the license key.

The license key is printed between the XML start <licKey> and end </licKey> tags in thelicense file.



Be sure to copy the entire string, including spaces and non-alphanumeric characters. If the licensekey includes spaces, you must enclose the entire string in double quotation marks. Repeat thiscommand for each software license key found in the license file. See the example below.

FIGURE 3 Adding a license key to a switch

NOTEFor steps 6 - 11, use the worksheets in Table 3 on page 23 and Table 4 on page 24 to recordthe answers.

6. How many EVO:RAIL appliances will be deployed? (default = 1, range = 1-8)

7. Will the network be flat or will it use VLANs? If flat, go to Step 8. If using VLANs, you may need toask the customer what their VLAN addressing scheme is. If they are not sure, then use the defaultsbelow including a single shared VM Network VLAN.

a. Management VLAN ID (default =1, the Native VLAN.)

Assign the name "Management" for this VLAN. The VDX Management VLAN must beVLAN ID 1 because EVO:RAIL management traffic is untagged by default and needs to beforwarded on the VDX's Native VLAN, which is VLAN ID 1. Traffic forwarded on VDXVLAN ID 1 is also untagged by default.

b. vSphere vMotion VLAN ID (default = 20)

Assign the name “vMotion” for this VLAN.c. Virtual SAN VLAN ID (default = 30)

Assign the name “VSAN” for this VLAN.d. VM Network VLAN

How many VM networks are required? (Optional, default = 1, range = 1 - 4K)

VM network VLAN naming and numbering can be defined by the customer, or if they donot have a preference you can use the names suggested in this step.

As a best practice, VLAN names can be “VM Network A”, “VM Network B”, and continuealphabetically. The VLAN ID's can start with 110, then increment in 10's. So the second is120, third is 130, etc. If a conflict exists with Management, vMotion or Virtual SAN VLANs,then skip to next VLAN ID number.

8. How many VDX switches are going to be provisioned? (range = 1-2). Each switch needs uplinkports to connect to upstream switches in the network. If you have two switches, you will also needto interconnect them using “inter-switch link” ports (ISLs).

a. If one switch, there is no need for any ISL connections. Go to step 9.b. If two switches will be provisioned, are the ISLs 10GbE or 40GbE? Both switches will have

the same ISL configuration.

i. If the ISL is 10GbE, how many ports are in the trunk group (default = 2, range = 1-8)?

ii. If the ISL is 40GbE, how many ports are in the trunk group (default = 2, range = 1-2)?



9. How many uplink ports are needed to connect to the upstream network? If two switches are beingdeployed, both switches will have the same port configuration.

a. 10GbE or 40GbE ports?b. Number of network ports?

i. 10GbE (default = 2, range = 1-8)

ii. 40GbE (default = 2, range - 1-4 minus any 40GbE ports selected for ISL trunks)

10. Will the out-of-band VDX Ethernet Management port be configured, or will in-band management beused instead? The out-of-band VDX Ethernet Management port is port #5 in Figure 2 above. You willneed to ask the customer for the management IP address, subnet mask, and gateway. The out-of-band management port is used when the customer deploys a separate out-of-band managementnetwork.

a. You will need the VDX Management IP Address - this is required for either in-band or out-of-band management

b. You will also need the IP default gateway and subnet mask in CIDR notation formanagement network. For example, 10.1.1.1/24.

VDX Configuration Actions

11. You will now configure the switch or switches using the parameters and values chosen and recordedin Table 3 on page 23 and Table 4 on page 24 worksheets as explained in the steps below.

Power on the switch, connect the laptop's serial cable to the VDX console port, and log in.

When you first log in to the switch, the defaults are as follows:

Username = admin

Password = password

It is highly recommended that you change the password.

Enter the command configure terminal and then enter the global command:

username admin password <new-password>

12. Configure an Rbridge ID for each switch. It is a mandatory switch identifier. Each switch needs aunique number. If you have two switches, you can simply use 1 and 2. Enter the value(s) you usedinto the worksheet in Table 3 on page 23 below.

rbridge-id <number>Where <number> is a unique number from 1-239.

13. Optionally, enter a name for the switch using the command

switch-attributes host-name <your chosen name>

14. In-band VDX management setup (from Step 10 above).

If out-of-band VDX switch management is to be used instead, skip to the next step.

Enter the IP default gateway address. From the rbridge-id 1 context, enter the management virtualrouting and forwarding context (VRF) by typing the command:

vrf mgmt-vrfNext enter the IPv4 context by typing the command:

address-family ipv4 unicastEnter the command:

ip route 0.0.0.0/0 <w.x.y.z>



Where <w.x.y.z> is the IP default gateway address you chose in Table 3 on page 23 below.

Enter the command: endNext create the virtual interface (VE) that is to be used for in-band management and bind it tomanagement VLAN-ID 1:

interface ve 1Add this interface to the management VRF created earlier:

vrf forwarding mgmt-vrfSet the IP address and subnet mask for in-band management:

ip address <a.b.c.d>/<subnet mask>

Where <a.b.c.d>/<mask> is the IP address and subnet mask you chose in Table 3 on page23. Enable the virtual interface:

no shutdownThe following is an example of the configuration above:rbridge-id 1switch-attributes host-name foovrf mgmt-vrf address-family ipv4 unicast ip route 0.0.0.0/0 10.5.1.1 !!interface Ve 1 vrf forwarding mgmt-vrf ip proxy-arp ip address 10.5.1.2/24 no shutdown!

15. Out-of-band VDX Management port setup (From Step 10 above)

If you have set up in-band VDX switch management, skip to the next step. For setting up the out-of-band VDX Management port, follow the steps below.

Enter the command configure terminalthen enter the global command:

rbridge-id <number you configured in step 12>Next enter the management virtual routing and forwarding context (VRF) by typing the command:

vrf mgmt-vrfEnter the IPv4 context by typing the command:

address-family ipv4 unicastEnter the command:

ip route 0.0.0.0/0 <w.x.y.z>Where <w.x.y.z> is the IP default gateway address you chose in Table 3 on page 23 below.

Enter the command:

endTo return to the command prompt.

Enter the command configure terminal then enter the global command:

interface Management <rbridge-id number you configured in step 12>/0Enter the command:



ip address <a.b.c.d>/<subnet mask>Where <a.b.c.d>/<mask> is the IP address and subnet mask you chose in Table 3 on page 23below.

Enter the command:

endTo return to the command prompt.

The following is an example of the out-of-band VDX management port setup.rbridge-id 1 switch-attributes host-name foo vrf mgmt-vrf address-family ipv4 unicast ip route 0.0.0.0/0 10.5.1.1interface Management 1/0 ip address 10.5.1.70/16!

16. Configure EVO:RAIL appliance-facing Ethernet ports and optional VLAN interfaces based on thenumber of appliances and switches selected.

If the network is flat, you do not need to configure additional VLANs.

If the network uses VLANs, you must create each VLAN interface, then enable the Ethernet portsand specify which VLANs are allowed to be included in each Ethernet port’s trunk, per Table 3 onpage 23 and Table 4 on page 24 below. The Management VLAN must be IPv4 IGMP snoopingand IPv6 MLD snooping enabled, and VSAN VLANs must be IPv4 IGMP snooping enabled. Thesnooping querier function will also be enabled.

Generally speaking, any Ethernet port can be used to connect to any host, appliance or upstreamswitch. However for optimal performance, it is best to balance the use of the ports across the two"Packet Buffer Banks", one from ports 1 - 32, the other from ports 33 - 52. Each packet buffer bankhas its own dedicated memory, so by balancing the use of ports across the two packet buffer banksyou take full advantage of the buffering capabilities of the switch. See Figure 4 below.

Use Table 1 and Table 2 to determine which VDX switch ports to enable based on the values chosenin Table 3 on page 23 worksheet. These port selections make optimal use of the switches bufferingcapabilities.

FIGURE 4 VDX 6740: port configuration and buffer banks



FIGURE 5 VDX 6740 Inter-Switch Link (ISL) trunk groups

You may deploy one or two switches for EVO:RAIL. A single switch provides the lowest cost optionthough it is a single point of failure. A single switch topology is not recommended if you plan todeploy more than 4 EVO:RAIL appliances. Two switches provide redundancy for high availabilityand is the recommended approach.

Figure 6 is an example of a single switch topology and Figure 7 is an example of dual-switchtopology.

In the single switch topology, each node connects to a single VDX switch. The VDX may connectto one or two upstream switches.

FIGURE 6 Example of a single switch topology

In the dual-switch topology, each node will connect to both switches. When two switches aredeployed, inter-switch links (ISLs) are needed. ISLs are used to interconnect the switches, you cancombine multiple Ethernet links to create trunks. These trunks are a bundle of Ethernet interfacesand are automatically configured when they are connected. When creating a trunk, all of theEthernet ports used in the trunk must belong to ports in the same trunk group. See Figure 5 above.



The steps that follow guide you which ports to use based on the answers given in the worksheetshown in Table 4 on page 24 below.

FIGURE 7 Example of a dual-switch topology

In the current version of VMware EVO:RAIL, you can have up to eight EVO:RAIL appliancesrepresented as one cluster and serviced by one Virtual SAN datastore. Each EVO:RAIL appliance iscomprised of four ESX hosts configured into a single cluster under the management of vCenterServer, and serviced by a single Virtual SAN datastore. The following are key rules and assumptionsfor deployment:

• Each EVO:RAIL appliance has exactly eight 10GbE connections to the VDX top-of-rack switch.• All EVO:RAIL appliances are grouped into a single EVO:RAIL cluster.• Up to 8 EVO:RAIL appliances can be deployed for a total of 32 server nodes.

Table 1 below defines the optimal VDX port selection for a single-switch toplogy. Table 2 belowdefines the optimal VDX port selection for a dual-switch toplogy.

Single-switch topology: appliance-facing network port assignmentsTABLE 1

Number of EVO:RAIL Appliances VDX Port Assignments

1 Ports 1-4,

33-36

2 Ports 1-8,

33-40

3 Ports 1-12,

33-44

4 Ports 1-16,

33-48



Dual-switch topology: appliance-facing network port assignmentsTABLE 2

Number of EVO:RAIL Appliances VDX Port Assignments

1 Ports 1-2,

33-34

2 Ports 1-4,

33-36

3 Ports 1-6,

33-38

4 Ports 1-8,

33-40

5 Ports 1-10,

33-42

6 Ports 1-12,

33-44

7 Ports 1-14,

33-36

8 Ports 1-16,

33-48

For the following steps, refer to the worksheets in Table 3 on page 23 and Table 4 on page 24for the VLAN IDs and names you've chosen, and to Table 1 above for the port assignments.

17. Configure the Management VLAN interface, which will be using the switches default Native VLANID, using the command:

interface vlan 1Then enter the VLAN name using the command:

name <VLAN name>For the Management VLAN, you also need to enable IPv4 IGMP snooping, IPv6 MLD snooping,and the snooping queriers. Enter the following commands:

ip igmp snooping enableip igmp snooping querier enableipv6 mld snooping enableipv6 mld snooping querier enableEnter the command: exitYou are now returned to the top level configuration mode.

18. Disable tagging of untagged traffic on the Native VLAN (Management VLAN).

Enter the global command: no vlan dot1q tag native

19. If the network is flat (no VLANs), skip to the step 20. If using VLANs, begin configuring VLANinterfaces using the command:



interface vlan <x>Where <x> is the name of the VLAN ID.

Then enter the VLAN name using the command:

name <VLAN name>For the VSAN VLANs, you need to enable IPv4 IGMP snooping and the snooping querier. Enter thefollowing commands for those VLANs:

ip igmp snooping enableip igmp snooping querier enableEnter the command: exitTo return to the top level configuration mode. Repeat the above steps for all VLAN interfaces.

The following is an example of this portion of the configuration.

!no vlan dot1q tag native!interface Vlan 1 name Management ip igmp snooping enable ip igmp snooping querier enable ipv6 mld snooping enable ipv6 mld snooping querier enable!interface Vlan 30 name VSAN ip igmp snooping enable ip igmp snooping querier enable!

20. Configure the server-facing network interfaces

a. Recall that each switch has a unique Rbridge number, refer to the worksheet in Table 3 onpage 23 for the values you chose. For VDX 6740's, the slot number is always 0.

Configure the ports on the switch which connect to the EVO:RAIL nodes based on thevalues in Table 1 for a single switch topology and Table 2 for a dual-switch topology.

Enter the command:

interface tengig <rbridge-id/slot/port>Note that to make port configuration quicker, you can configure a range of ports with onecommand. For example to configure ports 1 – 4 enter the command:

interface tengig 1/0/1-4Next put the port into trunk mode by entering the following two commands:

switchportswitchport trunk mode

21. If the network is flat (no VLANs), skip to step 22.

If using VLANs, refer to Table 4 on page 24 for the VLAN IDs and names you have chosen. Theseare then added to the trunk with the following command. Management VLAN 1 is forwarded bydefault and should not be included. Use a comma to separate multiple VLAN IDs.

switchport trunk allowed vlan add <vlan ID, vlan ID, vlan ID…>

22. Enabling Inter-Switch Links (ISL trunks).



You can use any of these ports of ISL connectivity, these are the ports that connect the switchestogether.

Port Type Use Ports in Range

10GbE 17 - 24

40GbE 49 - 52

For ISLs, there is no configuration required. Just plug in the correct optics and cables and it willautomatically form the ISL.

23. Configure the network-facing uplink ports as LAGs as shown in the example below. This exampleis shown for both 10GbE and 40GbE interfaces. You will need to configure only the interfaces youare using for the uplink connections.

Port Type Use Ports in Range

10GbE 25 - 32

40GbE 49 - 52

Network-facing ports (uplinks) are configured as LAGs or as trunk ports. Typically, if you have an L2network (no routing) with VLANs, you bundle the uplink ports into a LAG.

Link aggregation allows you to bundle multiple physical Ethernet links to form a single logical trunkproviding enhanced performance and redundancy. The aggregated trunk is referred to as a LinkAggregation Group (LAG). The LAG is viewed as a single link by connected devices, the SpanningTree Protocol, IEEE 802.1Q VLANs, and so on. When one physical link in the LAG fails, the otherlinks stay up and there is no disruption to traffic. To configure links to form a LAG, the physical linksmust be the same speed and all links must go to the same upstream switch unless the upstreamswitches support a multi-chassis LAG capability, such as Cisco vPC, MLAG or Brocade VLAG.

Once you are in the config mode (config t), enter the following:

interface Port-channel <n>Where <n> is the port-channel interface number. It can be any number from 1-6144. Next, put theport-channel in trunk mode and bring it up by typing the following commands.

switchportswitchport mode trunkno shutdownNow, pick the interfaces from each switch (Rbridge1 and Rbridge2) which are connected to theupstream switches (Switch A and Switch B) and configure them to belong to port-channel <n>.Refer to Figure 7 above.

If you are using 10G interfaces for uplinks, you can configure them as shown below

interface tengig 1/0/31-32channel-group <n> mode activeWhere <n> is the port channel interface number.

If you are using 40G interfaces for uplinks, you can configure 40G ports 49-50 as shown below.

interface fortygig 1/0/49-50channel-group <n> mode activeWhere <n> is the port channel interface number.

Management VLAN 1 is forwarded by default. No other VLANs need to be forwarded on thenetwork-facing ports.



Here is an example of this section of the configuration where the port-channel number is 10.!interface TenGigabitEthernet 1/0/31 channel-group 10 mode active type standard!interface TenGigabitEthernet 1/0/32 channel-group 10 mode active type standard!interface Port-channel 10 switchport switchport mode trunk no shutdown!

24. For best performance in an EVO:RAIL environment it is a good idea to set the interface MTU to thelargest value, also known as enabled "jumbo frames". However it is important that the upstreamswitches and hosts connected to the VDX are also configured to the same interface MTU size. TheVDX supports a maximum MTU of 9216. Make sure to check the host and upstream networkinterface settings. Not all hosts or switches can support full 9216 byte jumbo frames. If you are notsure, skip this step and check later.

As an example, assume that your server's interface and upstream network switch ports are set to anMTU of 9000. Then enter the command:mtu 9000Enter the command end to return to the command prompt.

As a simple example, the following is an MTU configuration for an appliance facing trunk port andnetwork-facing uplink port.!interface TenGigabitEthernet 1/0/1 mtu 9000 switchport switchport mode trunk switchport trunk allowed vlan add 20,30,110,120!interface Port-channel 10 mtu 9000 switchport switchport mode trunk no shutdown!

25. Performance Optimization

To optimize the switches forwarding performance for an EVO:RAIL environment, you should allocatea little more buffering for bursty traffic.

Enter the command configure terminal. Then enter the global command:

rbridge-id <number>Use the rbridge number you chose in Table 3 on page 23 below.

Enter the following two commands:

qos rcv-queue limit 2000qos tx-queue limit 2000Enter the end command to finish the configuration.

26. Save the configuration. This is the most important step!

copy running-config startup-config



Example Configuration

Consider the following appliance/switch combination. The VLAN configuration method was chosenand each switch has two VM networks.

Number of EVO:RAIL Appliances Number of Switches VDX Port Assignments

2 2 Ports 1-4, 33-36

In addition, we configure two 10GbE uplink ports and connect two 10GbE ISLs. Note that noconfiguration is needed for the ISLs, you just plug them into the correct ports.

You can verify the VLAN configurations by issuing the show vlan brief command. The commandshow fabric isl shows you ISL connectivity (for example below, Ten 1/0/23 and 1/0/24 are ISLs).

Two samples of the required VDX configuration commands on Rbridge1 are shown below, one for out-of-band and one for in-band management. You can verify the configuration by issuing the showrunning config command. Note this is the partial output of the show running configcommand. It includes some default commands that were not entered in the steps above, for examplethe fabric isl enable command is a default command shown on all interfaces regardless ofwhether or not they are used as ISL ports.

Rbridge1 (with Out-of-band VDX management):

no vlan dot1q tag native! interface Vlan 1 name Management ip igmp snooping enable ip igmp snooping querier enable ipv6 mld snooping enable ipv6 mld snooping querier enable!interface Vlan 20 name VMOTION!interface Vlan 30 name VSAN ip igmp snooping enable ip igmp snooping querier enable!interface Vlan 110 name VM NETWORK_A!interface Vlan 120 name VM NETWORK_B!rbridge-id 1 switch-attributes chassis-name VDX6740 switch-attributes host-name VDX-TOR-1 vrf mgmt-vrf address-family ipv4 unicast ip route 0.0.0.0/0 10.5.1.1 ! address-family ipv6 unicast ! ! qos tx-queue limit 2000 qos rcv-queue limit 2000 !interface Management 1/0 vrf forwarding mgmt-vrf no tcp burstrate ip icmp unreachable ip icmp echo-reply no ip address dhcp ip address 10.5.1.70/24



ipv6 icmpv6 unreachable no shutdown!interface TenGigabitEthernet 1/0/1 fabric isl enable fabric trunk enable mtu 9000 switchport switchport mode trunk switchport trunk allowed vlan add 20,30,110,120 switchport trunk tag native-vlan spanning-tree shutdown no shutdown!interface TenGigabitEthernet 1/0/2 fabric isl enable fabric trunk enable mtu 9000 switchport switchport mode trunk switchport trunk allowed vlan add 20,30,110,120 switchport trunk tag native-vlan spanning-tree shutdown no shutdown!interface TenGigabitEthernet 1/0/3 fabric isl enable fabric trunk enable mtu 9000 switchport switchport mode trunk switchport trunk allowed vlan add 20,30,110,120 switchport trunk tag native-vlan spanning-tree shutdown no shutdown!interface TenGigabitEthernet 1/0/4 fabric isl enable fabric trunk enable mtu 9000 switchport switchport mode trunk switchport trunk allowed vlan add 20,30,110,120 switchport trunk tag native-vlan spanning-tree shutdown no shutdown!interface TenGigabitEthernet 1/0/23 fabric isl enable fabric trunk enable no shutdown!interface TenGigabitEthernet 1/0/24 fabric isl enable fabric trunk enable no shutdown!interface TenGigabitEthernet 1/0/31 fabric isl enable fabric trunk enable channel-group 10 mode active type standard lacp timeout long no shutdown!interface TenGigabitEthernet 1/0/32 fabric isl enable fabric trunk enable channel-group 10 mode active type standard lacp timeout long no shutdown!interface TenGigabitEthernet 1/0/33 fabric isl enable fabric trunk enable mtu 9000 switchport switchport mode trunk switchport trunk allowed vlan add 20,30,110,120



switchport trunk tag native-vlan spanning-tree shutdown no shutdown!interface TenGigabitEthernet 1/0/34 fabric isl enable fabric trunk enable mtu 9000 switchport switchport mode trunk switchport trunk allowed vlan add 20,30,110,120 switchport trunk tag native-vlan spanning-tree shutdown no shutdown!interface TenGigabitEthernet 1/0/35 fabric isl enable fabric trunk enable mtu 9000 switchport switchport mode trunk switchport trunk allowed vlan add 20,30,110,120 switchport trunk tag native-vlan spanning-tree shutdown no shutdown!interface TenGigabitEthernet 1/0/36 fabric isl enable fabric trunk enable mtu 9000 switchport switchport mode trunk switchport trunk allowed vlan add 20,30,110,120 switchport trunk tag native-vlan spanning-tree shutdown no shutdown!interface Port-channel 10 vlag ignore-split mtu 9000 switchport switchport mode trunk switchport trunk tag native-vlan spanning-tree shutdown no shutdown!

Rbridge1 (with In-band VDX management):

no vlan dot1q tag native! interface Vlan 1 name Management ip igmp snooping enable ip igmp snooping querier enable ipv6 mld snooping enable ipv6 mld snooping querier enable!interface Vlan 20 name VMOTION!interface Vlan 30 name VSAN ip igmp snooping enable ip igmp snooping querier enable!interface Vlan 110 name VM NETWORK_A!interface Vlan 120 name VM NETWORK_B!rbridge-id 1 switch-attributes chassis-name VDX6740 switch-attributes host-name VDX-TOR-1 vrf mgmt-vrf address-family ipv4 unicast



ip route 0.0.0.0/0 10.5.1.1 ! address-family ipv6 unicast ! ! qos tx-queue limit 2000 qos rcv-queue limit 2000 !interface ve 1 vrf forwarding mgmt-vrf ip proxy-arp ip address 10.5.1.2/24 no shutdown!interface TenGigabitEthernet 1/0/1 fabric isl enable fabric trunk enable mtu 9000 switchport switchport mode trunk switchport trunk allowed vlan add 20,30,110,120 switchport trunk tag native-vlan spanning-tree shutdown no shutdown!interface TenGigabitEthernet 1/0/2 fabric isl enable fabric trunk enable mtu 9000 switchport switchport mode trunk switchport trunk allowed vlan add 20,30,110,120 switchport trunk tag native-vlan spanning-tree shutdown no shutdown!interface TenGigabitEthernet 1/0/3 fabric isl enable fabric trunk enable mtu 9000 switchport switchport mode trunk switchport trunk allowed vlan add 20,30,110,120 switchport trunk tag native-vlan spanning-tree shutdown no shutdown!interface TenGigabitEthernet 1/0/4 fabric isl enable fabric trunk enable mtu 9000 switchport switchport mode trunk switchport trunk allowed vlan add 20,30,110,120 switchport trunk tag native-vlan spanning-tree shutdown no shutdown!interface TenGigabitEthernet 1/0/23 fabric isl enable fabric trunk enable no shutdown!interface TenGigabitEthernet 1/0/24 fabric isl enable fabric trunk enable no shutdown!interface TenGigabitEthernet 1/0/31 fabric isl enable fabric trunk enable channel-group 10 mode active type standard lacp timeout long no shutdown!interface TenGigabitEthernet 1/0/32 fabric isl enable fabric trunk enable



channel-group 10 mode active type standard lacp timeout long no shutdown!interface TenGigabitEthernet 1/0/33 fabric isl enable fabric trunk enable mtu 9000 switchport switchport mode trunk switchport trunk allowed vlan add 20,30,110,120 switchport trunk tag native-vlan spanning-tree shutdown no shutdown!interface TenGigabitEthernet 1/0/34 fabric isl enable fabric trunk enable mtu 9000 switchport switchport mode trunk switchport trunk allowed vlan add 20,30,110,120 switchport trunk tag native-vlan spanning-tree shutdown no shutdown!interface TenGigabitEthernet 1/0/35 fabric isl enable fabric trunk enable mtu 9000 switchport switchport mode trunk switchport trunk allowed vlan add 20,30,110,120 switchport trunk tag native-vlan spanning-tree shutdown no shutdown!interface TenGigabitEthernet 1/0/36 fabric isl enable fabric trunk enable mtu 9000 switchport switchport mode trunk switchport trunk allowed vlan add 20,30,110,120 switchport trunk tag native-vlan spanning-tree shutdown no shutdown!interface Port-channel 10 vlag ignore-split mtu 9000 switchport switchport mode trunk switchport trunk tag native-vlan spanning-tree shutdown no shutdown!



Basic Configuration Worksheet

Basic Configuration WorksheetTABLE 3

Worksheet Setting Required Worksheet Value

Number of EVO:RAIL Appliances yes

Number of VDX switches yes (at least one)

Number of 10GbE network-facingports (uplinks)

At least one uplink

Number of 40GbE network-facingports (uplinks)

At least one uplink

Number of 40GbE inter-switch links(ISLs)

At least one ISL if using dual-switchtopology

Number of 10GbE inter-switch links(ISLs)

At least one ISL if using dual-switchtopology

Management IP address for Rbridge1

yes

Management IP address for Rbridge2

yes

Management default gateway andmask

yes

IP default gateway for in-band data yes

Switch 1 Rbridge ID yes

Switch 2 Rbridge ID yes


VLAN Worksheet

VLAN Worksheet TABLE 4

Worksheet Setting Required VLAN ID VLAN Name

Management VLAN yes 1

vSphere vMotion VLAN yes

Virtual SAN VLAN yes

VM Network VLAN no

VM Network VLAN no

VM Network VLAN no

VM Network VLAN no

VM Network VLAN no

VM Network VLAN no

VM Network VLAN no

VM Network VLAN no

VM Network VLAN no

VM Network VLAN no

The table above shows entries for up to ten VM Network VLANs. If needed, more VM Network VLANscan be added.

VLAN Worksheet


Creating A Serial Connection

You perform all configuration tasks using a serial connection from a workstation or terminal to theswitch.

Complete the following steps to create a serial connection to the switch:

1. Connect the serial cable to the serial port on the switch and to an RS-232 serial port on theworkstation or terminal device.

If the serial port on the workstation or terminal device is RJ45 instead of RS-232, remove the adapteron the end of the serial cable and insert the exposed RJ45 connector into the RJ45 serial port on theworkstation.

2. Open a terminal emulator application (such as HyperTerminal on a PC, or TERM, TIP, or Kermit in aUNIX environment), and configure the application as follows:

In a Windows environment, enter the following values: 9600 bits per second, 8 databits, no parity, 1stop bit, and no flow control.

In a UNIX environment using TIP, enter the following string at the prompt:

tip /dev/ttyb -9600If ttyb is already in use, use ttya instead.

The serial port is located on the port side of the VDX 6740 switches. The VDX 6740 uses an RJ-45connector for the serial port. The VDX 6740T and VDX 6740T-1G use a mini-USB connector for theserial port. An RJ-45 to DB9 adapter is also provided with the switch. The cable supplied is a rollovercable.

NOTETo protect the serial port from damage, keep the cover on the port when not in use. The serial port canbe used to connect to a workstation to configure the IP address for the VDX 6740 before connecting theswitch to a fabric or IP network. The serial port's parameters are fixed at 9600 baud, 8 data bits, and noparity, with flow control set to None.

Serial cable pinoutsTABLE 5

PIN Signal Description

1 Not supported NA

2 Not supported NA

3 TXD Transmit data

4 GND Logic ground

5 Not supported NA

6 RXD Receive data

7 Not supported NA

8 Not supported NA


brocade vdx 6740 deployment guide for vmware®...

Documents