Você está na página 1de 30

EMC Connectrix B-Series VDX-6740B

Integration Workshop
Lab Guide
Connectivity Diagram of the Brocade VDX Hands-on Lab Environment

2
Configuring Management Connectivity
1. Before you can start using this lab guide, you should first be logged in to the
desktop of a Windows Server system specifically provided for this purpose. This
desktop is the user environment through which you will perform the following lab
exercises. (Login: administrator / password).

To begin, you will first establish a serial console session with the VDX1 switch.

Since the IP address information is not yet configured, you will need to connect
through the switchs serial console port. A remote access COM serial port switch
has been provided.

Use PuTTy to connect to the VDX1 console port through the remote access
COM port switch. A PuTTy pre-saved serial COM port session has been
configured for each VDX switch you will use during this lab.

Select the session for the VDX1 switch. Click Load and then Open.

3
The VDX1 console will open a terminal session as if your computers COM port were
directly connected to it:

When the terminal appears log into the switch with the following credentials:

Login: admin
Password: password

2. Change the host name to VDX1:

sw0# configure
Entering configuration mode terminal
Sw0(config)# switch-attributes 1 host-name VDX1
VDX1(config-switch-attributes-1)#...Switch name has been
successfully changed to VDX1.

Navigate back to privileged EXEC mode by pressing Ctrl+Z.

3. Show the current configuration for the management port by typing the following
command:

show running-config interface Management 1/0

4. Except for the IP address specifically set to accommodate the lab environment,
the configuration shown is the default configuration for each rbridge management
interface port in the fabric. By default, before the vcs fabric is configured, each
switchs management port is 1/0; where 1 is the rbridge id of the switch.

4
5. Configure the management interface and default gateway for the switch that will
be VDX1.
a. Enter the Global Configuration mode and add a static IP for the management
port (A.B.C.D/L):

VDX1# configure
Entering configuration mode terminal
VDX1 (config)# interface Management 1/0
VDX1(config-Management-1/0)# ip address 10.126.86.24/24

After the brief messages stop scrolling press <ENTER> to return to the command
prompt. Then exit back to the Global Configuration mode:

VDX1(config-Management-1/0)# exit

b. From Global Configuration mode add a route for the Default Gateway
(0.0.0.0/0 A.B.C.D). A.B.C.D is the default gateway address.
VDX1(config)# rbridge-id 1
Enter the management virtual router and forwarding context (VRF) by typing:
VDX1(config-rbridge-id-1)# vrf mgmt-vrf

VRF stands for Virtual Routing and Forwarding and is a technology that controls
information flow within a network, isolating the traffic by partitioning the network into
different logical VRF domains.

Next enter the IPv4 context by typing the command


VDX1(config-vrf-mgmt-vrf)# address-family ipv4 unicast

There are a number of address-family commands where usage depends on the


context. When used in the VRF context, the command enables the IPv4 or IPv6
address-family configuration mode to configure a variety of VRF unicast routing options.

Finally, enter the ip route command to add the gateway:


VDX1(vrf-ipv4-unicast)# ip route 0.0.0.0/0 10.126.86.1
VDX1(vrf-ipv4-unicast)# <Ctrl+Z>
VDX1# copy run start

5
Open a command prompt on your Windows desktop and ping the VDX1
management IP address to verify connectivity over the LAN:

On the VDX1 console navigate back to privileged EXEC mode by pressing Ctrl+Z
then close the Telnet session window.

6. Use PuTTy to connect to the VDX2 console port through the remote access
COM port switch.

Select the session for the VDX2 switch. Click Load and then Open.

Log into the switch with the user credentials admin and password.

6
7. Change the host name to VDX2:

sw0# configure
Entering configuration mode terminal
Sw0(config)# switch-attributes 1 host-name VDX2
VDX2(config-switch-attributes-1)#...Switch name has been
successfully changed to VDX2.

Bring the command prompt back up to configuration mode:

VDX2(config-switch-attributes-2)# top
VDX2(config)#

a. Enter the Global Configuration mode and add a static IP for the management
port (A.B.C.D/L):
VDX2(config)# interface Management 1/0
VDX2 (config-Management-2/0)# ip address 10.126.86.25/24

After the brief messages stop scrolling press <Enter> to return to the command
prompt. Then exit back to the Global Configuration mode:

VDX2(config-Management-1/0)# exit

b. From Global Configuration mode add a route for the Default Gateway (0.0.0.0/0
A.B.C.D). A.B.C.D is the default gateway address.
VDX2 (config)# rbridge-id 1
Enter the management virtual router and forwarding context (VRF) by typing:
VDX2(config-rbridge-id-2)# vrf mgmt-vrf
Next enter the IPv4 context by typing the command
VDX2(config-vrf-mgmt-vrf)# address-family ipv4 unicast
Finally enter the ip route command to add the gateway:
VDX2(vrf-ipv4-unicast)# ip route 0.0.0.0/0 10.126.86.1
VDX2(vrf-ipv4-unicast)# <Ctrl+Z>
VDX2# copy run start

7
Open a command prompt on your Windows desktop and ping the VDX1
management IP address to verify connectivity over the LAN:

On the VDX2 console navigate back to privileged EXEC mode by pressing Ctrl+Z
then close the Telnet session window.

8. Use PuTTy to connect to the VDX6730 console port through the remote access
COM port switch.

Select the session for the VDX6730 switch. Click Load and then Open.

8
Log into the switch with the user credentials admin and password.

9. Change the host name to VDX6730:

sw0# configure
Entering configuration mode terminal
Sw0(config)# switch-attributes 1 host-name VDX6730
VDX6730(config-switch-attributes-1)#...Switch name has been
successfully changed to VDX6730.

Bring the command prompt back up to configuration mode:

VDX6730 (config-switch-attributes-2)# top


VDX6730 (config)#

a. Enter the Global Configuration mode and add a static IP for the management
port (A.B.C.D/L):
VDX6730(config)# interface Management 1/0
VDX6730(config-Management-1/0)# ip address 10.126.86.26/24

b. From Global Configuration mode add a route for the Default Gateway (0.0.0.0/0
A.B.C.D). A.B.C.D is the default gateway address.
VDX6730(config-Management-1/0)# top
VDX6730(config)# ip route 0.0.0.0/0 10.126.86.1
VDX6730(config)# <Ctrl+Z>
VDX6730# copy run start

Open a command prompt on your Windows desktop and ping the VDX6730
management IP address to verify connectivity over the LAN:

On the VDX6730 console navigate back to privileged EXEC mode by pressing


Ctrl+Z. Close the command prompt window.

9
Navigating NOS
1. Open a PuTTy SSH session to VDX1IP address and login. The console will
enter into Privileged EXEC mode.
a. Type a ? to display a list of commands to enter. The list will stop part of the
way, press the <SPACEBAR> to continue scrolling down the list. Press <ENTER>
to continue one line at a time. Type q or <ESC> to end the listing of possible
commands.
b. Begin typing in the first letter of show and press the <TAB> key to complete the
word in line. Notice that if you dont type enough letters for a unique word
completion, a list of possible completions will be displayed. After show type ?
to display possible options.

2. Complete the command to run show version. This will display the firmware
version running on the VDX. The second line of the output will show the active
version running on the switch.

Write down the version of NOS running on the switch.


____________________________________________________________________

a. Type show interface tengigabitethernet 1/0/1 and press <ENTER>.


Press the <SPACEBAR> to scroll through the output until the console returns to
the prompt. This time type show interface tengigbitethernet 1/0/1
| include Rate to only see the lines that contain the word Rate.
3. Enter the global configuration mode by typing config t.
a. Type show ip interface brief. Notice the error returned by the console.

What is the syntax error displayed?


____________________________________________________________________

b. Press the <UP ARROW> key to insert the previous line in the current line. Type
<CTRL>+A to move the cursor to the beginning of the line and insert the word
do followed by a space. Type <CTRL>+E to move the cursor to the end of the
line and press <ENTER>.

Notice that the command was taken. When in global config mode, prepend do to the
commands that are intended to be run from Privileged EXEC mode (like show
commands).

10
Enabling Brocade Logical Chassis Mode
Use the vcs command to configure the VCS Fabric parameters, VCS ID, switch
RBridge ID, and to enable VCS Fabric Mode.

1. Open a PuTTy SSH session to the VDX1IP address and login.

Login: admin
Password: password

2. Verify the current VCS Config mode state is Local-Only. Verify that the VCS
mode is Fabric Cluster.

VDX1# show vcs

How many nodes are listed?


____________________________________________________________________

Leave the SSH session open.

3. Establish a PuTTy SSH connection to your second Brocade VDX switch, VDX2.

a. Login: admin
b. Password: password

4. Verify the current VCS Config mode state is Local-Only. Verify that the VCS
mode is Fabric Cluster.

VDX2# show vcs

Leave the SSH session open.

5. Connect to your third Brocade VDX switch, VDX6730.


a. Login: admin
b. Password: password

6. Verify the current VCS Fabric mode state is disabled.


VDX6730# show vcs

Leave the SSH session open

NOTE: If the VDX6730 switch has VCS Fabric mode enabled, run the command:
VDX6730# no vcs enable

Answer Y to the question, this will reboot the switch and clear the configuration and
bring the switches back up in standalone mode.

11
7. Return to the VDX1 SSH session.

8. Enable VCS Fabric mode on the first Brocade VDX 6740 switch, VDX1.

VDX1# vcs vcsid 10 rbridge-id 1 logical-chassis enable

9. Answer y to the prompt. The switch will reboot resulting in the SSH session
closing.

10. Return to the VDX2 SSH session. Enable VCS Fabric mode on VDX2.

VDX2# vcs vcsid 10 rbridge-id 2 logical-chassis enable

Answer y to the prompt. The switch will reboot resulting in the SSH session closing.

Note: As an alternative, all switches in the fabric can be configured in logical chassis
mode using the rbridge-id all option

11. Wait at least 10 minutes for the switches to reboot and form the fabric.

a. Open a PuTTy SSH session to the VDX1IP switch and login.

Login: admin
Password: password

12. View the current VCS Fabric mode state.


sw0# show vcs

The Config Mode should be Distributed, which means the switch is in VCS
Logical Chassis Fabric mode. The vcsid should be 10 and RBridgeIDs should show
both 1 and 2. Information is listed displaying the member RBridges, their associated
WWNs, HostName, and IP addresses. How many rbridges are listed?
____________________________________________________________________

You should see 2 switches in the fabric. If you dont, wait for at least another 1-2
minutes and then repeat the show vcs command. What mode is displayed under
VCS Mode?
____________________________________________________________________

13. To see similar information in a summary format, view the fabric members by
typing the show fabric all command.

12
14. To view detailed information about the cluster, type the show vcs detail
command.

Which RBridge is the Co-ordinator switch?


____________________________________________________________________

15. From an SSH session to VDX1, re-apply the host name for the switch.
sw0# configure
sw0(config)# switch-attributes 1 host-name VDX1

Notice that the command prompt has changed to VDX1#.

16. Configure the telnet session timeout value by typing the following commands:
VDX1(config-switch-attributes-1)# line vty
VDX1(config-line-vty)# exec-timeout 0
VDX1(config-line-vty)# end

17. Connect to VDX2.

a. Login: admin
b. Password: password
c.

18. From a telnet session to VDX2, apply a host name for the switch.

sw0# configure
sw0(config)# switch-attributes 2 host-name VDX2

Is the command successful? How do you resolve the error?


____________________________________________________________________

19. Configure the telnet session timeout value by typing the following commands:
Sw0(config)#
VDX2(config)# line vty
VDX2(config-line-vty)# exec-timeout 0
VDX2(config-line-vty)# end

20. Connect to VDX6730.


a. Login: admin
b. Password: password

21. Apply a host name for the switch.


sw0# configure
sw0(config)# switch-attributes host-name VDX6730

13
Note that an rbridge id is not required because the VDX6730 is in standalone mode and
not part of the VCS fabric.

22. Configure the telnet session timeout value by typing the following commands:
VDX6730(config)# line vty
VDX6730(config-line-vty)# exec-timeout 0
VDX6730(config-line-vty)# end
VDX6730# copy run start

Note that since the VDX6730 is not in logical chassis mode, the configuration must be
manually saved.

23. From the SSH session to VDX1, display the ISL connections between VDX1 and
VDX2 in the fabric, by issuing the show fabric isl command. If you
reference the lab diagram earlier in this lab, you noticed that there are:
Four ISLs between the two VDXs
Three ISLs form a trunk
One ISL is the lone member of a trunk

The three ISL trunk is considered one logical interface. The trunk master port is listed as
the source port.

Identify the bandwidth configured for each trunk between VDX1 and VDX2.
____________________________________________________________________

24. To identify each physical ISL connection between VDX1 and the other two
RBridges in the fabric, type the show fabric islports command.

For the 30 Gbps trunk, what is the port interface for the Trunk Primary?
____________________________________________________________________
What role does this RBridge serve? (Principal or Subordinate)
____________________________________________________________________
Document the RBridge WWN and FCF MAC.
____________________________________________________________________

25. To further identify each physical ISL connection betweenVDX1 and the other two
RBridges in the fabric, type the show fabric trunk command.

26. To view the Ethernet fabric routing table, type the show fabric route
topology command.

14
How many equal cost paths are available to the VDX2?
____________________________________________________________________
Reviewing the cost of each path and comparing it to the bandwidth of each path, why
are the two paths the same cost?
____________________________________________________________________

What is the hop count?


____________________________________________________________________
27. To view multicast routing information, type the show fabric route
multicast command.

Which switch is the multicast root? (Domain = RBridge ID)


____________________________________________________________________

28. Since all configuration commands must be issued on the coordinator switch while
running in LC mode it is recommended to configure a Virtual IP. This address will
always be bound to the switch that is the current coordinator switch.

Issue the following commands to configure a Virtual IP:

VDX1# config
VDX1(config)# vcs virtual ip address 10.126.86.27/24
VDX1(config)# end

29. Issue the show vcs virtual-ip command to verify the correct configuration.
Which switch is associated with the virtual ip address?
____________________________________________________________________

Configuring Host Ports


1. Open an SSH session to the VCS cluster using the virtual ip address and show
the current configuration for the port your NIC is attached to by typing the
following command:

VDX1# show running-config interface tengigabitethernet 2/0/19

2. The configuration shown is the default configuration for all physical interface
ports. This allows the ports to form ISLs automatically when connected. We
need to convert this port to an L2 switchport.

3. Configure port 19 on VDX1 for a client that is a member of VLAN 10.


a. Enter the Global Configuration mode and create the VLAN:

VDX1# configure
VDX1(config)# interface vlan 10

15
b. Configure the port for Layer 2:
Choices are access port or trunk port. Access port only allows one vlan,
whereas trunk port allows multiple vlans or are used with connecting devices
using vlan tagging.

VDX1(config-Vlan-10)# exit
VDX1(config)# int te 2/0/19
VDX1(conf-if-te-2/0/19)# switchport

c. Configure the port mode as an untagged port:


VDX1(conf-if-te-2/0/19)# switchport mode access

d. Configure the port VLAN:


VDX1(conf-if-te-2/0/19)# switchport access vlan 10
VDX1(conf-if-te-2/0/19)# end

4. Confirm the port configuration by typing the following command:

show running-config interface tengigabitethernet 2/0/19

5. Confirm that the CNA is communicating with the switch properly by typing the
show ip interface brief rbridge-id 2 command. Port 19 has a
status of up and a protocol message of up. This indicates that the CNA is
communicating with the switch.

6. Confirm that the VLAN is up and that Interface 2/0/19 is a member of VLAN 10
by issuing the command show vlan 10.

7. View the MAC address table by issuing the show mac-address-table


command.

If the end device does not show in the MAC table, toggle the interface with the shut
and no shut commands.

VDX1# config
VDX1(config)# interface tengigabitethernet 2/0/19
VDX1(conf-if-te-2/0/19)# shutdown
VDX1(conf-if-te-2/0/19)# no shutdown
VDX1(conf-if-te-2/0/19)# end

Then run the show mac-address-table command again.

What is the mac address of the connected device?


____________________________________________________________________

16
Note: If the host or VM is using VLAN tagging, then the port will need to be configured
as a trunk port instead of an access port. This will allow tagged frames to enter the
switch port. Also if the interface needs to allow more than one vlan, the port needs to
be configured as a trunk port.
Configuring FCoE
FCoE requires Data Center Bridging (DCB) to prioritize FCoE traffic from other traffic
types.

Data Center Bridging is an enhancement to existing 802.1 bridge specifications


standards that involves four technological enhancements. These are Priority-based
Flow Control (PFC), Congestion Notification (CN), Enhanced Transmission Selection
(ETS) and Data Center Bridging Exchange Protocol (DCBx) which is a discovery and
capability exchange protocol used to convey capabilities and configurations of the other
three DCB features between neighbors to ensure consistent configuration across the
network.

The VDX has default DCB configurations that are optimized for FCoE, but these
configurations can be changed.

1. Configure FCoE to enable FCoE logins on the VDX.


a. Display the DCB configurations.

VDX1# show cee maps default

This command displays the CEE default settings for FCoE. Information displayed
includes Priority Flow Control, Enhanced Transmission Selection, CoS, and Priority
Groups.

Which Priority Group is assigned a CoS of 3 under the priority table?


____________________________________________________________________

How much weight is assigned to Priority Group 2?


____________________________________________________________________

b. Show the current FCoE login status

VDX1# show fcoe login rbridge-id 1


VDX1# show fcoe login rbridge-id 2

2. Configure port 1/0/16 on VDX1 as an FCoE port. There is a CNA adapter


connected to this port for FCoE.

VDX1(config)# interface TenGigabitEthernet 1/0/16


VDX1(conf-if-te-1/0/16)# fcoeport default

17
This command applies the default fcoe cee map to the port.

a. Display the FCoE logins on VDX1

VDX1(conf-if-te-1/0/16)# do show fcoe login rbridge-id 1

How many devices are logged in on VDX1?


____________________________________________________________________

b. Return to EXEC mode


VDX1(conf-if-te-1/0/16)# end
VDX1#

3. Customize the bandwidth allocation enforced by DCB.


a. Change the DCB priority to reflect the following configuration:
Priority Group Table 1: 20% with PFC enabled
Priority Group Table 2: 80% with PFC disabled

VDX1# configure terminal


VDX1(config)# cee-map default
VDX1(config-cee-map-default)# priority-group-table 1 weight 20
pfc on
VDX1(config-cee-map-default)# priority-group-table 2 weight 80
pfc off

4. Display the new DCB configurations.

VDX1(config-cee-map-default)# do show cee maps default

a. Return to EXEC mode

VDX1(conf-cee-map-default)# end
VDX1#

18
Configuring Uplink Ports
In this lab, youll be configuring a trunk port on the VDX6740 as an uplink to a third party
switch. Well be using a Brocade 6730 as a substitute for a third party switch. The
6730 has been configured in standalone mode which means it is configured to work as
a standard Ethernet switch.

1. From your current connection to VDX1, show the current configuration for the
port you will use to connect to a third party device by typing the following
command show running-config interface tengigabitethernet
1/0/7.

The configuration shown is the default configuration for all physical interface ports. This
allows the ports to form ISLs automatically when connected. However when connecting
a VDX switch to a third party switch, traditional L2 ports must be used. If more than one
port is used, then this would be a traditional LAG or Port Channel. This will be
discussed in the next lab.

2. Configure port 1/0/7 on VDX1 as an L2 trunk port uplink.


a. Enter the Global Configuration mode:
VDX1# configure
VDX1(config)# interface tengigabitethernet 1/0/7

b. Configure the port for Layer 2:


VDX1(conf-if-te-1/0/7)# switchport

c. Configure the port mode as a tagged port:


VDX1(conf-if-te-1/0/7)# switchport mode trunk

d. Configure allowed VLANs for the interface:


VDX1(conf-if-te-1/0/7)# switchport trunk allowed vlan add 10
VDX1(conf-if-te-1/0/7)# do show vlan brief

e. Confirm the port configuration by typing the following command do show


running-config interface tengigabitethernet 1/0/7.

f. Remove allowed VLANs (vlan 10) from the interface:


VDX1(conf-if-te-1/0/7)# switchport trunk allowed vlan remove
10
VDX1(conf-if-te-1/0/7)# switchport trunk allowed vlan all
VDX1(conf-if-te-1/0/7)# end

This command removes vlan 10 and as an alternative allows all vlans.

19
3. Confirm the port configuration by typing the following command show
running-config interface tengigabitethernet 1/0/7.

We will now work with the VDX 6730. Leave the VDX1 SSH session open.

Open a PuTTy SSH session to the VDX6730 and log into the CLI.

4. Configure port 0/7 on VDX6730 as an L2 trunk port. (First, create VLAN 10 in switch
VDX6730)

a. Enter the Global Configuration mode and create the VLAN:


VDX6730# configure
VDX6730(config)# interface vlan 10
VDX6730(config-Vlan-10)# exit

b. Enter Global Configuration mode:


VDX6730(config)# interface tengigabitethernet 0/7

c. Configure the port for Layer 2:


VDX6730(conf-if-te-0/7)# switchport

d. Configure the port mode as a tagged port:


VDX6730(conf-if-te-0/7)# switchport mode trunk

e. Configure allowed VLANs for the interface:


VDX6730(conf-if-te-0/7)# switchport trunk allowed vlan all
VDX6730(conf-if-te-0/7)# no shut
VDX6730(conf-if-te-0/7)# do show vlan brief
VDX6730(conf-if-te-0/7)# do copy run start

In this lab, you configured a single trunk port between the 6740 and a third party switch.
In the next two labs, youll configure link aggregation and create port channels
consisting of multiple links between the 6740 and a third party switch.
Link Aggregation
The grouping of multiple physical links that connect to other devices that are not VDXs
is referred to as link aggregation. A Link Aggregation Group (LAG) is a standard
software-based mechanism to achieve resiliency and the utilization of multiple
redundant links. In the context of the VDX, it is called a port channel when referring to
the logical interface and a channel group when referring to the interface configuration.
In this demo, we will create the different types of LAGs supported by the VDX.

When configuring a LAG, the Port Channel itself is configured as an L2 switchport, not
the interfaces. Since the last lab had you configure a single trunk port, the interface
itself was configured as an L2 switchport. Therefore before creating a LAG we must
remove the configuration from the trunk interface that we configured in the previous lab.

20
Lab Clean Up

1. On VDX1 remove the L2 configuration from interfaces.


VDX1# configure
VDX1(config)# interface tengigbitethernet 1/0/7
VDX1(conf-if-te-1/0/7)# no switchport
VDX1(conf-if-te-1/0/7)# exit

2. On VDX6730 remove the L2 configuration from interfaces.


VDX6730(conf-if-te-1/0/7)# no switchport
VDX6730(conf-if-te-1/0/7)# exit

Create a Static LAG

1. On VDX1 create a port channel interface by issuing the following commands:


VDX1(config)# interface port-channel 10

2. Configure the port channel as a trunk port:


VDX1(config-Port-channel-10)# switchport
VDX1(config-Port-channel-10)# switchport mode trunk
VDX1(config-Port-channel-10)# switchport trunk allowed vlan
all
VDX1(config-Port-channel-10)# no shutdown
VDX1(config-Port-channel-10)# exit

3. Add the uplink ports from VDX1 to the LAG(port channel).


VDX1(config)# interface TenGigabitEthernet 1/0/7
VDX1(conf-if-te-1/0/7)# channel-group 10 mode on type
standard
VDX1(conf-if-te-1/0/7)# exit
VDX1(config)# interface TenGigabitEthernet 1/0/9
VDX1(conf-if-te-1/0/9)# channel-group 10 mode on type
standard

4. Verify configuration of the port-channel and the physical interfaces


VDX1(conf-if-te-1/0/9)# do show port-channel 10

5. On VDX6730 create a port channel interface by issuing the following commands:


VDX6730# configure
VDX6730(config)# interface port-channel 10

21
6. Configure the port channel as a trunk port:
VDX6730(config-Port-channel-10)# switchport
VDX6730(config-Port-channel-10)# switchport mode trunk
VDX6730(config-Port-channel-10)# switchport trunk allowed
vlan all
VDX6730(config-Port-channel-10)# no shutdown
VDX6730(config-Port-channel-10)# exit

7. Add the uplink ports from VDX6730 to the LAG


VDX6730(config)# interface tengigabitethernet 0/7,9
VDX6730(conf-if-te-0/7,9)# channel-group 10 mode on type
standard
VDX6730(conf-if-te-0/7,9)# no shut
VDX6730(conf-if-te-0/7,9)# exit
VDX6730(config)# do show port-channel 10

Write down the member ports of port-channel 10.


____________________________________________________________________

What is the Aggregator type of port-channel 10?


____________________________________________________________________

Create an LACP LAG

The configuration of an LACP LAG is the same as the Static LAG but instead of using
the on mode, you would use active mode. This allows LACP to negotiate and
automatically form the LAG.

8. Using the range command, remove the previous channel group command on
interfaces 7 and 9 on both VDX1 and VDX 6730 switches.
VDX1(conf-if-te-1/0/9)# exit
VDX1(config)# no interface port-channel 10

On the VDX 6730:

VDX6730(config)# no interface port-channel 10

9. Configure the interfaces as an LACP LAG on both switch VDX1 and VDX6730
switches.
VDX1(config)# interface tengigabitethernet 1/0/7,9
VDX1(conf-if-te-1/0/7,9)# channel-group 10 mode active type
standard

VDX6730(config)# interface tengigabitethernet 0/7,9


VDX6730(conf-if-te-0/7,9)# channel-group 10 mode active type
standard

22
10. Configure the port channel as a trunk port. (Return to configuration mode first).
VDX1(config)# interface port-channel 10
VDX1(config-Port-channel-10)# switchport
VDX1(config-Port-channel-10)# switchport mode trunk
VDX1(config-Port-channel-10)# switchport trunk allowed vlan
all
VDX1(config-Port-channel-10)# no shutdown
VDX1(config-Port-channel-10)# end

Return to the VDX 6730. (Return to configuration mode first).

VDX6730(config)# interface port-channel 10


VDX6730(config-Port-channel-10)# switchport
VDX6730(config-Port-channel-10)# switchport mode trunk
VDX6730(config-Port-channel-10)# switchport trunk allowed
vlan all
VDX6730(config-Port-channel-10)# no shutdown
VDX6730(config-Port-channel-10)# end

11. Verify the port-channel:


VDX1# show port-channel detail
VDX6730# show port-channel detail

Write down the member ports of port-channel 10.


____________________________________________________________________

What does sync: 1 indicate?


____________________________________________________________________

What does the * indicate under Member ports?


____________________________________________________________________
What is the Aggregator type of port-channel 10?
____________________________________________________________________

Verify that the Partner system ID on VDX1 is the Aggregator system ID on VDX6730?
Is it?
____________________________________________________________________

In this lab you configured a static and an LACP LAG between switches VDX1 and
VDX6730. In the next lab youll configure a vLAG between the VDX6730 and the two
VDX6740 switches.

23
Creating vLAGs
You will create a vLAG that connects both of your Brocade VDX 6740 switches to the
external traditional Ethernet switch. The vLAG will encompass two links from each
RBridge (1 and 2). In this lab, the VDX6730 is not in VCS mode. Its in standalone
mode so it is functioning as a standard Ethernet switch.

The configuration for a standards LAG and vLAG are the same, but the difference is
that a vLAG is a LAG that spans two separate switches. In the diagram below notice
that the LAG is between the VDX6730 and the two VDX6740s. Its virtual because it
logically spans the two 6740 switches. The most important thing to note when
configuring a vLAG is that in order for the two 6740 switches to know that the LAG
spans two physical switches, the Admin Key has to be identical. Otherwise the vLAG
will not form. The Admin Key is the port channel number assigned when creating the
port channel interface.

Lab Cleanup

1. Before configuring the vLAG, we must remove the port channel configuration
from the previous lab.
VDX1# configure
VDX1(config)# no interface port-channel 10
VDX1(config)# exit

Return to the VDX 6730. (Return to configuration mode first).

VDX6730(config)# no interface port-channel 10


VDX6730(config)# exit

24
Create a vLAG
In this lab well configure the port channel to allow only traffic on vlans 10 and 20.

1. Create a port channel interface by issuing the following commands:


VDX1# configure
VDX1(config)# interface port-channel 10

2. Configure the port channel as a trunk port:


VDX1(config-Port-channel-10)# no shut
VDX1(config-Port-channel-10)# switchport
VDX1(config-Port-channel-10)# switchport mode trunk
VDX1(config-Port-channel-10)# switchport trunk allowed vlan
add 10,20

What is the error?


____________________________________________________________________

What do you do to fix it?


____________________________________________________________________

3. Since vlan 10 is already created from the previous labs, youll only need to add
vlan 20.
VDX1(config-Port-channel-10)# exit
VDX1(config)# interface vlan 20
VDX1(config-vlan-20)# exit

Go back and complete steps 1 and 2.

4. From the Virtual IP add the uplink port from VDX1 to the vLAG. (Enter
configuration mode).
VDX1(config)# interface TenGigabitEthernet 1/0/7
VDX1(conf-if-te-1/0/7)# channel-group 10 mode active type
standard
VDX1(conf-if-te-1/0/7)# no shut

25
5. Verify configuration of the port-channel and the physical interfaces
VDX1(conf-if-te-1/0/7)# do show run interface port-channel

The output should show these settings:


interface Port-channel 10
vlag ignore-split
switchport
switchport mode trunk
switchport trunk vlan 10,20
switchport trunk tag native-vlan
spanning-tree shutdown
no shutdown

VDX1(conf-if-te-1/0/7)# do show run interface te 1/0/7

The output should show these settings:


interface TenGigabitEthernet 1/0/7
fabric isl enable
fabric trunk enable
channel-group 10 mode active type standard
lacp timeout long
no shutdown

6. Still from the Virtual IP add the uplink port from VDX2 to the vLAG.
VDX1(conf-if-te-1/0/7)# exit
VDX1(config)# interface TenGigabitEthernet 2/0/8
VDX1(conf-if-te-2/0/8)# channel-group 10 mode active type
standard
VDX1(conf-if-te-2/0/8)# no shut
VDX1(conf-if-te-2/0/8)# end

7. Link aggregation now must be configured on the VDX6730.


a. Since vlan 10 was already created in the last lab, we need to create vlan 20.
VDX6730(config)# interface vlan 20
VDX6730(config-vlan-20)# exit

b. To configure a lag, associate ports 0/7 and 0/8 to the vLAG and enter the
following commands:
VDX6730(config)# interface port-channel 10

8. Configure the port channel as access/edge port:


VDX6730(config-Port-channel-10)# switchport
VDX6730(config-Port-channel-10)# switchport mode trunk
VDX6730(config-Port-channel-10)# switchport trunk allowed vlan
add 10,20
VDX6730(config-Port-channel-10)# no shutdown
VDX6730(config-Port-channel-10)# exit

26
9. Add the uplink ports from 6730 to the vLAG.
VDX6730(config)# interface TenGigabitEthernet 0/7-8
VDX6730(conf-if-te-0/7-8)# channel-group 10 mode active type
standard
VDX1(conf-if-te-0/7-8)# no shut

10. Verify configuration of the port-channel and the physical interfaces


VDX6730(conf-if-te-0/7-8)# do show run interface port-channel

The output should show these settings:


interface Port-channel 10
switchport
switchport mode trunk
switchport trunk vlan 10,20
spanning trunk tag native-vlan
no shutdown

VDX6730(conf-if-te-0/7-8)# do show run interface te 0/7

The output should show these settings:


interface TenGigabitEthernet 0/7
channel-group 10 mode active type standard
lacp timeout long
no shutdown

VDX6730(conf-if-te-0/7-8)# do show run interface te 0/8

The output should show these settings:


interface TenGigabitEthernet 0/8
channel-group 10 mode active type standard
lacp timeout long
no shutdown

11. Return to the Virtual IP SSH session and view the port-channel status by issuing
the do show interface port-channel 10 command.
a. Is the port channel in an up state?
____________________________________________________________________
b. What is the current allowed member speed of the port-channel
____________________________________________________________________

12. Return to the VDX1 SSH session and view the vLAG and its status by issuing the
do show port-channel detail command.
a. How many member switches are there?
____________________________________________________________________
b. Are all ports syncd and active on this port-channel?
____________________________________________________________________

27
Converting to VCS Fabric Mode
Every lab so far has been completed in Logical Chassis Cluster mode. In this lab well
convert the VCS LC mode to VCS Cluster mode. For this lab we will not be backing up
the configuration.

IMPORTANT: Please note that when converting between VCS modes, all configuration
information is lost UNLESS the configuration of each switch in the fabric is saved.

1. View VCS parameters on VDX1.


a. Open a telnet session to VDX1 and login.
b. In the Privileged EXEC mode, type show vcs to see the VCS configurations
on the VDX.

VDX1# show vcs

c. Enter the following information from the output:


Config Mode:
____________________________________________________________________
VCS Mode:
____________________________________________________________________
VCS ID:
____________________________________________________________________
Total number of nodes:
____________________________________________________________________

d. From the same output, find the Rbridge-Id with the WWN that has the asterisk (*)
indicating the system you are currently logged into and fill in the following
information.
Rbridge-Id:
____________________________________________________________________
Hostname:
____________________________________________________________________

e. Find the Rbridge-Id with the WWN that has the greater-than symbol (>) indicating
the principal switch and fill in the following information.
Rbridge-Id:
____________________________________________________________________
Hostname:
____________________________________________________________________

28
2. Configure VCS parameters on the VDX.
a. Open a telnet session to VDX1 and login.
b. Run the VCS command to convert the cluster from VCS Logical chassis mode to
VCS cluster mode.

VDX1# no vcs logical-chassis enable rbridge-id all default-


config

3. Since we are already in logical chassis mode, we need to disable LC mode. We


will run this command on all rbridges using the all option, but this command can
be run on each individual switch as well.

a. Type y to confirm changing VCS configurations, resetting running configurations


to default and rebooting the switch.

b. Allow both switches to reboot.

4. Confirm new VCS settings


a. Open a telnet session to VDX1 and login.
b. In the Privileged EXEC mode, type show vcs to see the VCS configurations
on the VDX.
c. Enter the following information from the output:
Config Mode:
____________________________________________________________________
VCS Mode:
____________________________________________________________________
VCS ID:
____________________________________________________________________
d. Repeat steps a. through c. for VDX2.
Config Mode:
____________________________________________________________________
VCS Mode:
____________________________________________________________________
VCS ID:
____________________________________________________________________
5. Gather VCS fabric information using show commands.
a. Get the member information from all Rbridge nodes in the fabric.

29
2015 Brocade Communications Systems, Inc. All Rights Reserved. 07/15
ADX, Brocade, Brocade Assurance, Brocade One, the B-wing symbol, DCX, Fabric OS,
ICX, MLX, MyBrocade, SAN Health, VCS, and VDX are registered trademarks, and
AnyIO, HyperEdge, NET Health, OpenScript, and The Effortless Network 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 their respective owners.

30

Você também pode gostar