Professional Documents
Culture Documents
March 2014
Rev 1.0
Index
No
1
2
3
4
5
6
Topic
VLAN
Inter-VLAN Routing
L2 Redundancy and Configuration
Link Aggregation
Multi-chassis trunking
Virtual router redundancy protocol enhanced
Page
2
5
7
13
16
20
BROCADE COMMUNICATIONS
TRAINING GUIDE
A. VLANs
VLAN is:
VLAN tagging allows multiple VLANs to span switches over a single physical link
VLAN tagging is needed when a link is connected between any two switches carrying traffic from
multiple VLANs
In example below, Since both sides of the link must be configured for 802.1Q tagging, ports 4
and 14 are tagged so that they can be in multiple VLANs
The switch looks at the VLAN ID to determine which VLAN gets the forwarded frame
BROCADE COMMUNICATIONS
TRAINING GUIDE
Port-based VLAN
BROCADE COMMUNICATIONS
TRAINING GUIDE
BROCADE COMMUNICATIONS
TRAINING GUIDE
B. Inter-VLAN Routing
Routing switch
SW-Switch(config)# vlan 10
SW-Switch(config-vlan-10)# untag ethernet 1/1 to 1/12
SW-Switch(config-vlan-10)# router-interface ve 10
SW-Switch(config-vlan-10)# interface ve10
SW-Switch(config-vif-10)# ip address 192.123.22.1/24
SW-Switch(config-vif-10)# vlan 20
SW-Switch(config-vlan-20)# untag ethernet 1/13 to 1/24
SW-Switch(config-vlan-20)# router-interface ve 20
SW-Switch(config-vlan-20)# interface ve20
SW-Switch(config-vif-20)# ip address 192.123.44.1/24
BROCADE COMMUNICATIONS
TRAINING GUIDE
Show commands
SW-Switch#Show ip interface
SW-Switch#Show ip route
Summary
A VLAN is a logical partitioning of a physical LAN into one or more Virtual LANs (VLANs)
VLAN tagging allows multiple VLANs to span switches over a single physical link
Configuring a tagged port as a dual-mode port allows it to accept and transmit both tagged
traffic and untagged traffic at the same time
BROCADE COMMUNICATIONS
TRAINING GUIDE
STP
With STP enabled, redundant links are blocked, and traffic is forwarded to its destination
BROCADE COMMUNICATIONS
TRAINING GUIDE
BROCADE COMMUNICATIONS
TRAINING GUIDE
Instance of STP
Root bridge
Set of bridge priorities
BPDUs
PVST can be used to load share Layer 2 traffic by sending traffic from different VLANs onto
different physical links
Traffic from one VLAN can be forwarded over another VLAN without causing a loop
VLAN 100
VLAN 201
BROCADE COMMUNICATIONS
TRAINING GUIDE
Fast Port Span is automatically disabled if the switch detects any of the following conditions on a
port:
a)
b)
c)
d)
10
BROCADE COMMUNICATIONS
TRAINING GUIDE
RSTP Configuration
To enable RSTP:
SW-Switch(config-vlan-2)# spanning-tree 802-1w
Topology Groups
A topology group is a group of VLANs configured together and assigned a single, shared instance
of STP, RSTP, VSRP, or MRP
Topology groups simplify configuration and enhance scalability of L2 protocols by allowing the
use of a single instance of an L2 protocol on multiple VLANs
Each topology group has a master VLAN, where the STP settings are defined
All other VLANs in the topology group are added as members
A topology group is one way around the limitations of Per-VLAN Spanning Tree
11
BROCADE COMMUNICATIONS
TRAINING GUIDE
Useful in the case where there are more VLANs than STP instances available
Topology groups are proprietary to Brocade Ethernet devices
Any STP configurations made in the master VLAN will be automatically applied to all member
VLANs
A VLAN may only be a member of a single topology group
SW-Switch(config)#vlan 10
SW-Switch(config-vlan-10)#tagged e1 to 4
SW-Switch(config-vlan-10)#vlan 20
SW-Switch(config-vlan-20)#tagged e1 to 4
SW-Switch(config-vlan-20)#vlan 30
SW-Switch(config-vlan-30)#tagged e1 to 4
Summary
The spanning tree algorithm ensures a loop free topology by enabling a single path through any
physical arrangement of bridges
BPDUs are messages exchanged between switches in a LAN or VLAN to form and maintain a
loop free topology
A path cost is the accumulated port cost from the root switch to the other switches in
the topology
Per-VLAN Spanning Tree can be used to load share Layer 2 traffic by sending traffic from
different VLANs onto different physical links
A topology group is a group of VLANs configured together and assigned a single, shared
instance of STP, RSTP, VSRP, or MRP
12
BROCADE COMMUNICATIONS
TRAINING GUIDE
D. Link Aggregation
Trunking = Link Aggregation
Link Aggregation allows an administrator to combine multiple Ethernet links into a larger logical
trunk known as a Link Aggregation Group (LAG)
The switch treats the trunk as a single logical link
The physical links must all be the same speed and duplex setting and must connect to the same
adjacent switch
LAG requirements may vary for different platforms, such as the number of links in the LAG,
specific port boundaries, etc.
Always check what is supported at both ends
LAG Benefits
Increased bandwidth
Increased availability
Load-sharing
Sub-second failover to the remaining links in the LAG
Types of LAGs
BROCADE COMMUNICATIONS
TRAINING GUIDE
Brocade switches support the use of static and dynamic LAGs on the same device2
Can use only one type of LAG for any given port
lag "Controller2" dynamic id 2
ports ethernet 1/1/5 to 1/1/6
primary-port 1/1/5
deploy
!
lag "MCT-ICL" static id 10
ports ethernet 1/1/7 ethernet 1/1/9
primary-port 1/1/7
deploy
14
BROCADE COMMUNICATIONS
TRAINING GUIDE
Summary
15
BROCADE COMMUNICATIONS
TRAINING GUIDE
E. Multi-chassis Trunking
MCT is a technology that allows two MCT supporting switches to cluster together and appear as
a single logical device. Trunking is a technology that allows multiple links of a device to appear
as one logical link.
The combination of MCT and trunking allows for creating a resilient network topology that
utilizes all links in the network, creating an ideal network topology for latency sensitive
applications.
MCT terminology
MCT cluster: A pair of devices (switches) that is clustered together using MCT to appear as a
single logical device. The devices are connected as peers through an Inter-Chassis Link (ICL).
MCT cluster device: One of the two devices in an MCT cluster.
MCT peer device: From the perspective of an MCT cluster device, the other device in the MCT
cluster.
MCT cluster client: A device that connects with MCT cluster devices through static or dynamic
trunks. It can be a switch or an endpoint server host in the single-level MCT topology or another
pair of MCT devices in a multi-tier MCT topology.
Inter-Chassis Link (ICL): A single-port or multi-port 1 GbE or 10 GbE interface between the two
MCT cluster devices. It provides the control path for CCP for the cluster and also serves as the
data path between the two devices.
MCT VLANs: VLANs on which MCT cluster clients are operating. Any VLAN that has an ICL port is
an MCT VLAN, even though it does not have any clients.
MCT session VLANs: The VLAN used by the MCT cluster for control operations. CCP protocol
runs over this VLAN. The interface can be a single link or a trunk group port. If it is a trunk group
port, it should be the primary port of the trunk group. The MCT session VLAN subnet is not
distributed in routing protocols using redistribute commands.
MCT keep-alive VLAN: The VLAN that provides a backup control path in the event that ICL goes
down.
Cluster Communication Protocol (CCP): A Brocade proprietary protocol that provides reliable,
point-to-point transport to synchronize information between MCT cluster devices. It is the
default MCT control path between the two peer devices. CCP comprises two main components:
CCP peer management and CCP client management. CCP peer management deals with
establishing, and maintaining a TCP transport session between peers, while CCP client
management provides event-based, reliable packet transport to CCP peers.
Cluster Client Edge Port (CCEP): A physical port or trunk group interface on an MCT cluster
device that is connected to client devices.
Cluster Edge Port (CEP): A port on an MCT cluster device that belongs to the MCT VLAN and
connects to an upstream core switch/router, but is neither a CCEP not an ICL.
16
BROCADE COMMUNICATIONS
TRAINING GUIDE
RBridgeID: RBridgeID is a value assigned to MCT cluster devices and clients to uniquely identify
them, and helps in associating the source MAC address with an MCT device.
The MCT initiates at a single MCT-unaware server or switch and terminates at two MCT-aware
devices.
Configuring MCT
This section provides basic configuration steps, which should be completed in the specified
order.
After completing these steps, you can verify the configuration by running the show cluster
command
Step 1: Configure LAG
BROCADE COMMUNICATIONS
TRAINING GUIDE
Configuration of the peer device involves the peer's IP address, RBridgeID, and ICL
specification. The cluster-id variable must be the same on both cluster devices.
The RBridgeID must be different from the cluster RBridge and any other client in the cluster.
device-1(config)#cluster SX 4000
device-1(config-cluster-SX)#rbridge-id 3
device-1(config-cluster-SX)#session-vlan 3000
device-1(config-cluster-SX)#keep-alive-vlan 3001
device-1(config-cluster-SX)#icl SX-MCT ethernet 1/7
device-1(config-cluster-SX)#peer 10.1.1.2 rbridge-id 2 icl SX-MCT
device-1(config-cluster-SX)#deploy
BROCADE COMMUNICATIONS
TRAINING GUIDE
Use the show cluster config command to display the peer device and client states.
device#show cluster SXR122 config
cluster SXR122 100
rbridge-id 100
session-vlan 1
keep-alive-vlan 3
icl SXR122-MCT ethernet 1/1
peer 172.17.0.2 rbridge-id 101 icl SXR122-MCT
deploy
client KL134
rbridge-id 14
client-interface ethernet 1/23
deploy
device#show cluster 1 client
Cluster 1 1
===================
Rbridge Id: 101, Session Vlan: 3999, Keep-Alive Vlan: 4001
Cluster State: Deploy
Client Isolation Mode: Loose
Configured Member Vlan Range: 100 to 105
Active Member Vlan Range: 100 to 105
MCT Peer's Reachability status using Keep-Alive Vlan: Peer Reachable
Client Info:
-----------Client: c1, rbridge-id: 300, Deployed
Client Port: 3/11
State: Up
Number of times Local CCEP down: 0
Number of times Remote CCEP down: 0
Number of times Remote Client undeployed: 0
Total CCRR packets sent: 4
Total CCRR packets received: 3
Some show commands for MCT troubleshooting
device#show cluster 1 ccp peer
device#show interface ethernet 7/1
device#show span
19
BROCADE COMMUNICATIONS
TRAINING GUIDE
VRRP-e is Brocades enhanced version of VRRP that overcomes limitations in the standard
protocol
20
BROCADE COMMUNICATIONS
TRAINING GUIDE
Configuring VRRP-e
To configure the first VRRP-e virtual router from the example on the privies slide1:
Router_A(config)# router vrrp-extended
Router_A(config-VRRP-e-router)# interface ethernet 1
Router_A(config-if-e100-1)# ip address 192.53.5.2/24
Router_A(config-if-e100-1)# ip vrrp-extended vrid 1
Router_A(config-if-e100-1-vrid-1)# backup priority 110 track-priority 20
Router_A(config-if-e100-1-vrid-1)# ip-address 192.53.5.1
21
BROCADE COMMUNICATIONS
TRAINING GUIDE
BROCADE COMMUNICATIONS
TRAINING GUIDE
Troubleshooting VRRP-e
Router_A(config)# show ip vrrp-e
Total number of VRRP-Extended routers defined: 2
Interface ethernet 1
auth-type no authentication
VRID 1
state initialize
administrative-status enabled
Virtual MAC 02e0.5279.a401
priority 110
current priority 110
track-priority 20
hello-interval 1 sec
dead-interval 0 sec
current dead-interval 3.500 sec
preempt-mode true
virtual ip address 192.53.5.1
advertise backup: disabled
track-port 16(up)
Router_A(config)# show ip vrrp-e
Total number of VRRP-Extended routers defined: 2
Interface ethernet 1
auth-type no authentication
VRID 1
state backup
administrative-status enabled
Virtual MAC 02e0.5279.a401
priority 110
current priority 90
track-priority 20
hello-interval 1 sec
dead-interval 0 sec
23
BROCADE COMMUNICATIONS
TRAINING GUIDE
Summary
VRRP and VRRP-e provide redundancy to default gateways servicing hosts on the same subnet
Allows an alternate router path for a host without changing the IP address or MAC
address of its gateway
Reliability is achieved by advertising a virtual router as the default gateway
VRRP-e is Brocades enhanced version of VRRP that overcomes limitations in the
standard protocol
VIP can be any unused IP address within the same subnet
Can ping VIP regardless of who is master
24
BROCADE COMMUNICATIONS
TRAINING GUIDE
25