Академический Документы
Профессиональный Документы
Культура Документы
Course outline
to 7302-7360 ISAM
1. Welcome
Technologies
1.
STPCap.
RSTP
MSTP Tech
High
NT/5520
AMS - Redundancy configurations
2. NE Operation
1. Technologies
1.
IHUB RSTP LAG NTRedundancy
1. STP RSTP MSTP Tech
2. NE Operation
1. IHUB RSTP LAG NTRedundancy
3
@@PRODUCT
@@COURSENAME
Course objectives
Upon
completion
of this course, you should be able to:
7302-7360
ISAM
High Cap.
NT/5520
AMSProtocol
- Redundancy
configurations
Describe
Rapid
Spanning Tree
(STP),
Describe Rapid Spanning Tree Protocol (RSTP),
Describe
Mulitiple
Tree
Upon completion
of Spanning
this course,
youProtocol
should be(MSTP),
able to:
Describe the most important xSTP parameters,
Describe and configure Link Aggregation (LAG),
Describe
Describe and
Rapidcompare
Spanningthe
Tree
different
Protocol scenarios
(STP),
for access resiliency (NT redundancy),
Configure
NT
protection.
Describe Rapid Spanning Tree Protocol (RSTP),
Describe Mulitiple Spanning Tree Protocol (MSTP),
Describe the most important xSTP parameters,
Describe and configure Link Aggregation (LAG),
Describe and compare the different scenarios for access resiliency (NT redundancy),
Configure NT protection.
4
@@PRODUCT
@@COURSENAME
Section 1
Technologies
Module 1
STP RSTP MSTP Tech
TAC42058_HO01 Edition I2.0
7302-7360 ISAM
High Cap. NT/5520 AMS - Redundancy configurations
TAC42059_V1.1-SG Edition 2.0
111
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
Blank page
112
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
Document History
Edition
Date
Author
Remarks
01
2013-01-22
First edition
02
Jan/2014
ALU-University Madrid
Module objectives
After completing this section, youll be able to:
Describe Spanning Tree Protocol
Bridge Ids and Root Selection
BPDU format
Bridge and Port Definitions
Port States and Convergence
113
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
114
Table of Contents
1 Spanning Tree Protocol - Principles
2 Rapid
Spanning Tree Protocol
1 Spanning Tree Protocol - Principles
1.1 What is Spanning
Redundancy and
Why?
3 Multiple
Tree
Protocol
Page
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
29
30
31
32
33
34
35
7
20
31
116
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
ThisCOPYRIGHT
page ALCATEL-LUCENT
is left blank
intentionally
2013. ALL RIGHTS RESERVED.
117
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
118
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
Many companies and organizations increasingly rely on computer networks for their
operations. Access to file servers, databases, the Internet, intranets, and extranets is
critical for successful businesses. If the network is down, productivity and customer
satisfaction decline.
If a path or device fails, the redundant path or device can take over the tasks.
LOOP !!!
PC2
P1
Port nbr
2
M1
M2
M1
M2
PC1
1
MAC2
M1
M2
MAC1
4
M1
M2
M1
M2
1 1 10
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
Port nbr
P1
P1
An example of a loop is depicted in the following drawing. A loop can appear in a meshed
network topology or where link redundancy is desired. The goal of Link redundancy is if a
particular link fails another one can take over making sure frames are forwarded towards
the network.
In our example two switches connect two network segments. [1]In this case when PC 1 sends
a message to PC 2, both switches receive this message with the source address of PC 1 and
destination address of PC 2, their respective MACs. [2]The source address of PC 1, MAC1 is
learned at both switches in port1. Since both switches dont know the destination address,
MAC2, they will broadcast the Ethernet frames to all the ports. In this example port 2 of the
switches. [3]So lets say the upper switch sends first the frame. [4]Not only will PC 2 will
receive the frame but also the lower switch in port 2. [5] The lower switch will think that PC
1 has moved so it overwrites the previous entry in its self learning table and broadcasts this
frame to all its ports, in this case port 1 [6]. This creates a loop which endlessly travels
through the network consuming available bandwidth [7]. To solve this problem STP could be
activated. The STP will make sure there is only one active path out of multiple paths
available between the two end points [8].
1 1 11
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
Like mentioned before, in switch networks, redundant paths can cause loops
The Spanning Tree Protocol (STP) prevents loops by allowing only one single
path between any pair of hosts. The STP is transparent to hosts
The STP relies on BPDU messages: Bridged Protocol Data Units
and its Key functions are:
find
By
and
discover failures
Bridge
MAC-Address
Priority
2 Bytes
6 Bytes
Range: 0 65,535
Default: 32768
1 1 13
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
By default the priority value set to 32768. The network administrator has to be very careful
about setting the priority value of the bridges in the switching domain. Because, in case of
equal priorities, the switch with the lowest Mac-Address will be elected as a root switch.
That may result in selecting the oldest one as a root switch which may be the least powerful
router.
Root BID
Sender BID
Port ID
BPDU
1 1 14
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
D
100 M
D
1G
R
D
100 M
10 M
Alternate port
(Blocked)
1 1 15
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
Spanning tree works in first instance by selecting a root bridge on the LAN. This particular bridge is
elected through the exchange of BPDU. The switch that has the lower Bridge-ID becomes the Root
Switch. If the Bridge-IDs are the same for all switches, then the switch with the lower Mac-Address will
be elected as Root Switch.
When the root bridge is selected, then each other bridge selects one of its ports with the least path cost
to the root bridge. The least cost path is determined by STP looking at the bandwidth of the link.
All ports on the root bridge are known as designated ports and are in what is known as forwarding state.
Forwarding state ports can send and receive traffic.
All of the other bridges present are known as non-root bridges. They choose a port known as a root port
which sends and receives traffic.
On non-root bridges only one port can be designated and all others are blocked. Designated ports
forward MAC addresses. Designated ports are selected after the bridge determines the lowest cost path
to get to the root bridge.
By using this method, the redundant links are closed down. They can be opened again if there is a
change in network topology and the link is needed once more.
PORT ROLES
The Root Port and Designated Port remains with the same functionality, but a Blocking Port has two
roles now. Backup Port and Alternate Port. Spanning Tree Algorithm defines ports based on BPDUs.
Within the value inside BPDU messages, the port can be compared with others and the action can be
taken accordingly.
Alternate Port: The interface that we are receiving better BPDU values to access to the Root Bridge.
When the Designated Port fails on the switch then the alternate port will be used for the path.
Copyright 2013 Alcatel-Lucent. All Rights Reserved.
TAC42058_HO01 Edition I2.0
Propagation delays can occur when protocol information passes through a switched LAN. As
a result, topology changes can take place at different times and at different places in a
switched network. When a Layer 2 interface transitions directly from non-participation in
the spanning tree topology to the forwarding state, it can create temporary data loops.
Ports must wait for new topology information to propagate through the switched LAN before
starting to forward frames. They must allow the frame lifetime to expire for frames that
have been forwarded under the old topology.
Switch ports running STP can be in one of four (five) states:
Blocking Port will decide whether it is a Root Port , Designated Port or Blocked Port.
During this stage the port listens but will not forward frames, the port is not used by
user traffic.
Listening and Learning Switch determines if there are any other paths to Root Switch
or not. The path with the least cost becomes Root Port for Non-root Switches and
Designated Port for the Root Switch. BPDUs are still being processed in both states but
BPDUs can not be read in listening state. The port is still not used but the bridge can
already learn mac-addresses from this port.
Forwarding - Sends and receives frames on the port, the port is used to carry user
traffic
(Disabled virtually non-operational)
root
0
2
Bridge
(identifier)
11
4
path cost
12
LAN
10
13
9
19
19
19
4
19
1 1 17
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
Path cost
100
100
100
8
10Mbps 100
100Mbps 19
1000Mbps 4
10Gbps 2
So here you have it. This is the result of activating the STP in the network. Most likely there are more links
than what is shown here but the STP has blocked them in order to avoid loops. Every green circle is a switch
with its corresponding bridge id [1] and the root switch having the lowest BID [2]. The Path cost corresponds
to each link [3] which has a relation with the link bandwidth (lower cost means higher bandwidth [4]). With
this loop free topology if switch id 4 wants to send traffic to switch id 6 then it must take the following path
via the root switch 5].
Lets sum up on how the Spanning-Tree Protocol eliminates loops in the network:
1 The switch with the lowest switch identifier among all switches on all LAN segments is the root switch. The
network administrator can assign a lower switch priority to a selected switch to control which switch
becomes the root, or the administrator can use default switch priorities and allow the Spanning-Tree
Protocol to determine the root.
2 Each switch port is associated with a path cost.
The path cost represents the cost of transmitting a frame to a switched segment through that port. A
network administrator typically configures a cost for each port based on the speed of the link
3 Each switch determines its root port and root path cost.
The root port is the port that represents the shortest path from itself to the root switch. The root path cost is
the total cost to the root. All ports on the root switch have a zero cost.
4 All participating switches elect a designated switch from among the switches on that LAN segment. A
designated switch is the switch on each LAN segment that provides the minimum root path cost. Only the
designated switch is allowed to forward frames to and from that LAN segment towards the root.
5 All participating switches select ports to be included in the spanning tree. The selected ports will be the
root port plus the designated ports for the designated switch. Designated ports are those where the
designated switch has the best path to reach the root. In cases where two or more switches have the same
root path cost, the switch with the lowest switch identifier becomes the designated switch.
6 Using the preceding steps, all but one of the switches directly connected to each LAN segment are
eliminated, thereby removing all multiple LAN loops.
Spanning tree reconfiguration
The root switch is in charge of periodically sending BPDUs on the network. If a given switch does not receive any root
BPDU for a max_age timer (usually 20 s), it will request a new root election and will compute its ports state again.
All ports then pass in listening state for a forward_delay period (usually 15 s). This is supposed to be the time the
switch needs to collect information and take a decision regarding the port state. The port should then go into a
blocked or learning state.
The learning state will last forward_delay again. This elapse of time is necessary to ensure the new spanning tree
configuration has been seen by all switches on the network and avoid any temporary loops. Yet the switch can
already learn addresses from this port. Finally the port may change to forwarding state or even blocked if new
information has told the switch to block it.
If a switch sees a local topology change it will immediately send a topology change notification to the root, which will
notify this change to other switches asking them to refresh their address database.
Copyright 2013 Alcatel-Lucent. All Rights Reserved.
TAC42058_HO01 Edition I2.0
1st: TC is generated
and sent to Root.
TCA
TC BPDU
TCA
TC : Topology Change
TCA: TC Ack
1 1 18
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
When an 802.1D bridge detects a topology change, it uses a reliable mechanism to first
notify the root bridge.
Once the root bridge is aware of a change in the topology of the network, it sets the TC flag
on the BPDUs it sends out, which are then relayed to all the bridges (TCAs: Topology Change
Acknowledgements) in the network. When a bridge receives a BPDU with the TCA flag bit
set, it reduces its bridging-table aging time to forward delay seconds. This ensures a
relatively quick flush of stale information.
1 1 19
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
In case of a failure:
1) Port physically down: The switch detects loss of carrier and immediately declares the
port down. Since, it was the port with the best BPDU, the switch immediately invalidates
it, and selects the next best candidate which is the alternate port as the new root port.
The new port will go through Listening and Learning states, which takes 2 x Forward_Time.
Therefore, the connectivity is restored in 2xForward_Time=30 seconds by default.
2) Failure receiving BPDUs: The switch does not detect the loss of carrier (for instance, the
uplink is fiber connected to a converter or connects through a hub), and thus the port
remains up. The root port loses the continuous stream of BPDUs. The stored BPDU
information is no longer updated. Based on the default procedure, it takes time Max_Age
to expire the stored information. After this, the switch considers the BPDU stored with the
alternate port, and unblock the new port. It will take another 2xForward_Delay to bring
the port to forwarding state. Therefore, the connectivity is restored in
2xForward_Time+(Max_Age) =50 seconds by default.
within this period, the alternate port will be enabled for forwarding after listening and
learning states of course.)
Copyright 2013 Alcatel-Lucent. All Rights Reserved.
TAC42058_HO01 Edition I2.0
1 1 20
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
Is Port Included in
Is Port Learning
Active Topology?
Mac-Addresses?
STP
RSTP
Disabled
Discarding
No
No
Blocking
Discarding
No
No
Listening
Discarding
No
No
Learning
Learning
Yes
Yes
Forwarding
Forwarding
Yes
Yes
1 1 21
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
TC
Proposal
Port Role
Learning
Forwarding
Agreement
1 1 22
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
TCA
STP
BPDU
handling
RSTP
Bridge sends BPDU on all ports
BPDU Aging
Transition to
forwarding
state
Max-Age)
1 1 23
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
real generation.
RSTP: The switch generates within the interval even it doesnt receive any from the
root.
Faster Aging of Information
If BPDUs are not received after 3 consecutive times, protocol information will be
the root.
Priority = 32K
Priority = 4096
Blocking
Listening
Forwarding
Better
BPDU
C
D
BPDU
I am the ROOT
Priority = 16K
1 1 24
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
LINK TYPE
(SHARED)
EDGETYPE
(P2P)
EDGETYPE
(SHARED)
LINK TYPE
(P2P)
1 1 25
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
The initiator of the TC floods as opposed to STP where only the root
did
1 1 26
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
TC=Topology Change
Switches forward Ethernet frames based on their MAC address tables (filtering tables) that
bind MAC addresses to egress ports. When a change in topology occurs (e.g. a link failure)
the MAC address tables may appear to be invalid, as the paths between switches have
changed. The switches may eventually re-learn the new information, but it may take
considerable time, especially if the traffic is scarce and MAC address aging time is large (5
minutes by default). Based on that, if switch detects a change in the topology (e.g. link
going up or down), it should notify all other switches that something has changed. In
response to this notification, all switches will reduce their MAC address aging time to
Forward_Time (15 seconds by default) effectively hastening the aging process.
In STP:
Topology
changes are signalled via special TC BPDU, which is being sent upstream from the originating switch
(the one that detected the change) to the root switch via the root ports. As the root switch hears the TC
BPDU, it will set TC ACK flag in all its outgoing configuration BPDUs for the duration of Max_Age +
Forward_Time. All switches that see this flag, will set their MAC address tables aging time to Forward_Time.
Once the switch that originated the TC BPDU will hear the TC ACK, it will stop signalling about the topology
change.
Network
performance. Shortening the MAC address table aging time results in less stable topology. When a
switch loses a MAC address, it starts flooding frames for this destination, effectively acting like a hub. If the
flow of packets in your network is not intense enough, the switches may start losing MAC address table
information, resulting in excessive traffic flooding. The issue might become pretty dangerous with high
number of topology changes. Excessive flooding might severely impact your network performance. Note, that
this issue also pertains to L2 topologies that runs RSTP, as the topology changes are handled in the similar
way. In order to reduce the number of topology changes, configure all edge ports in the topology (connected
to hosts, IP Phones, servers) as spanning-tree edge-type ports. Edge-type ports do not generate TC events
when they go up or down.
STP
RSTP
Topology
change
Topology
ACKs
1 1 28
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
Another reason why RSTP is faster than the STP. In the RSTP if a switch detects
a topology change it communicates it to everybody where in STP it sends it to
the Root switch. Also in the STP there are TCAs (Topology Change
Acknowledges) where in the RSTP they dont exist.
A little bit of information on how and what the switches exchange. Switches
forward Ethernet frames based on their MAC address tables (filtering tables)
that bind MAC addresses to egress ports. When a change in topology occurs
(e.g. a link failure) the MAC address tables may appear to be invalid, as the
paths between switches have changed. The switches may eventually re-learn
the new information, but it may take considerable time, especially if the
traffic is scarce and MAC address aging time is large (5 minutes by default).
Based on that, if a switch detects a change in the topology (e.g. link going up
or down), it should notify all other switches that something has changed. In
response to this notification, all switches will reduce their MAC address aging
time to Forward_Time (15 seconds by default) reducing the aging process.
1: Proposal
3: Agreement, p1
Forwarding
p0
p1
p0: designated port
p2
P3
p4
2: sync
(unchanged)
2: sync
(block)
2: sync
(unchanged)
1 1 29
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
STP waits 30 seconds before it transitions to the forwarding state. (When the port is
selected to become a designated port)
During sync process there wont be any change for two type of criteria:
Blocking Ports
Edge Ports
The proposal agreement mechanism is very fast, because it doesnt rely on an aging
mechanism and there is no timer for that. The way of handshakes propagates quickly
towards the edge of the network.
If a designated port in discarding state, sends a proposal and doesnt receive any
agreement from the port then, it slowly falls back to STP states. Means the stages of
listening and learning and so on... This case can occur when the remote bridge port is in
blocking mode and doesnt understand any RSTP BPDUs.
SYNC
PROCESS
D
B
D
R
R B
B D
D
R
EDGETYPE
1 1 30
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
EDGETYPE
blocks the non-edge root ports. This operation is called sync. Once sync completed, A
authorizes R to put its port in the forwarding state.
At this stage, the newly blocked ports on A also negotiate a quick transition so called
the process. For instance, the links on B except the root ports towards A.
Remember there can not be a loop. As, after the link is set as forwarding between A and
R, the root port(s) will be blocked. Now, the possible loop cut at different location in
the switches and this cut travels down in the network along with the new BPDUs from
the root switch.
Note: When the new link (Between Switch A and Root) is converged. The BPDU value
sent out from Switch A to Switch C will also change (new link has converged and we have
now a different path-cost to Root). Swicth C is also receiving BPDUs from D. There will
be comparison between received BPDUs about the root path cost. if C is sending a
better one comparing D, the process will restart between the switches A and C. For the
process, see Link Designations slide on Rapid Spanning Tree Protocol Chapter.
Copyright 2013 Alcatel-Lucent. All Rights Reserved.
TAC42058_HO01 Edition I2.0
1 1 31
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
VLAN 200
VLAN 200
VLAN 100
PC-A
PC-B
1 1 32
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
(R)STP decisions in selecting what paths form the spanning tree are not based on VLAN
availability. For the best path to the destination, the bandwidth will be evaluated with the
defined cost values and as a result of this the link(s) will be either in a blocked state or not.
That may not be convenient for some VLANs. For example, PC-A wants to communicate
with PC-B, so the path it will take will be switches B, A, Root, D and C.
MSTP was originally defined in IEEE 802.1s but later merged into the IEEE 802.1Q-2005
standard. The idea is that several VLANs can be grouped into a spanning tree instance (or
1 VLAN per instance) called MSTI, with each instance having a spanning-tree topology
independent of other spanning-tree instances. Therefore an MSTI can contain any number of
VLANs, but a VLAN can belong to only one MSTI at a time.
.
This architecture provides multiple forwarding paths for data traffic, enables load balancing
and reduces the number of spanning-tree instances required to support a large number of
VLANs.
Therefore, each spanning tree instance (or MSTI) converges separately and has its own root
switch.
This allows for seamless interoperability between areas of the network that do not support
multiple spanning tree processes with others that do.
In the drawing the link between switch A and C is blocked for Vlan 200 [Animation 1] and the
link between switch C and D is blocked for Vlan 100 [Animation 2]. If we take the same
example as before, PC-A wants to communicate with PC-B then in this case the path it will
take will be switches B, A and C.
So what is MSTP?
It is an extension of the RSTP protocol to further develop the usefulness of virtual LANs
(VLANs). Therefore MSTP is VLAN aware.
If there is only one VLAN in the network, single (R)STP works appropriately. If the network
contains more than one VLAN, we can go for MSTP.
1 1 34
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
If the switches have 1 or more different attributes, they belong to different regions
Each switch running MST in the network has a single MST configuration that consists of these
three attributes:
An alphanumeric configuration name (Region-Name)
A configuration revision number (two bytes)
A 4096-element table that associates each of the potential 4096 VLANs instance
A common Region Name, Format Selector, and Revision Level are used to logically group
switches into a Region. This allows for greater scalability, since each region now defines the
logical boundary of the spanning tree network.
VLAN
Instances
MST Region
MSTP allows formation of MST regions that can run multiple MST instances (MSTI).
An MSTP region is a collection of switches, sharing the same view of physical topology
partitioning into set of logical topologies.
The concept of MSTP region allows for bounding STP re-computations. Since MSTIs in every
region are independent, any change affecting MSTI in one region will not affect MSTIs in
other regions. This is a direct result of the fact that M-Record information is not exchanged
between the regions.
Each switch running MST (Multiple Spanning Tree) in the network has a single MST
configuration that consists of the following attributes:
An
A
A
If the switches have 1 or more different attributes, they belong to different regions.
Switches grouped into regions allows for greater scalability, since each region now defines
the logical boundary of the spanning tree network.
MST Region
1 1 36
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
The boundary ports of a MST region do not send MSTI BPUs, the M-records, outside the region. This is the
reason that an MST region is seen as one virtual switch.
Module summary
After completing this section, you are able to:
Describe Spanning Tree Protocol
Bridge Ids and Root Selection
BPDU format
Bridge and Port Definitions
Port States and Convergence
1 1 37
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
End of module
STP RSTP MSTP Tech
1 1 38
Technologies STP RSTP MSTP Tech
7302-7360 ISAM High Cap. NT/5520 AMS - Redundancy configurations
Document Historyy
Edition
Date
Author
Remarks
01
Mar/2013
ALU-University Madrid
02
Aug/2013
ALU-University China
02
Jan/2014
ALU-University Madrid
Only Cosmetic
Page
1 Spanning Tree Protocol
1.1 802.1w Rapid Spanning Tree Protocol
1.2 802.1s Multiple Spanning Tree Protocol
1.3 Redundancy is needed- How about loops?
1.4 Bridge and Port Definitions
1.5 ISAM - IP Stack --- xSTP Implementation
1.6 ISAM m-VPLS Implementation
1.7 VLAN Tagging options
1 8 xSTP Configuration and Parameters - CLI
1.8
1.9 Basic Configuration - CLI
1.10 MSTP Configuration Example - CLI
1.11 M-VPLS Creation
1.12 STP Parameters
1.13 Ports to be added under STP --- M-VPLS
1.14 Creating MSTP Instances
1.15 xSTP Troubleshooting
2 Link Aggregation
2 1 LAG - Primary port
2.1
2.2 LAG Port Category
2.3 LAG Auto negotiation
2.4 Physical Ports & Link Aggregation Group Configuration CLI
2.5 Create LAG
2.6 Add Port to Link Aggregation Group
2.7 Add LAG to a Service (VPLS)
2.8 Link aggregation Troubleshooting
3 NT Redundancy and Load-sharing
3.1 Why is redundancy needed?
3.2 Equipment Protection vs Link Protection
3.3 Where needed?
3.4 Ethernet switch aggregation: RSTP
3.5 Ethernet switch aggregation: MSTP
3.6 Ethernet switch aggregation: MPLS
3.7 Configure NT protection group (only impacting OAM)
3.8 Configure NT protection element (only impacting OAM)
3.9 Show status commands
3.10 Load-sharing for HiCap LT boards
3 11 Load
3.11
Load-sharing
sharing for legacy LT boards
4 Exercises
4.1 Exercise 1
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
24
25
26
27
28
29
31
33
34
35
37
38
39
40
41
42
43
44
45
46
47
49
51
52
upon reconfiguration, bridge ports must wait for new topology information to propagate
through the domain before transitioning from blocking to forwarding state (30-60
(30 60
second expiry timer) hence limitation of 7 hops
MSTP is the 802.1s IEEE standard.The idea is that several VLANs can be grouped into a
spanning tree instance, with each instance having a spanning-tree topology independent
of other spanning-tree instances.
This architecture provides multiple forwarding paths for data traffic, enables load balancing
and reduces the number of spanning-tree instances required to support a large number of
VLANs.
A common Region Name,Format Selector, and Revision Level logically group switches into a
Region. This allows for greater scalability, since each region now defines the logical
boundary of the spanning tree network.
Therefore, each spanning tree instance converges separately and has its own root bridge.
This allows for seamless interoperability between areas of the network that do not support
multiple
l i l spanning
i tree processes with
i h others
h
that
h d
do.
Every bridge/switch has a single MST configuration with following attributes:
A config revision nr
If the switches have 1 or more different attributes, they belong to different regions.
Spanning tree works in first instance by selecting a root bridge on the LAN. This particular
bridge is elected through the exchange of BPDU.
All ports on the root bridge are known as designated ports and are in Forwarding State.
Forwarding state ports can send and receive traffic.
All of the other bridges present are known as non-root bridges, they choose a port known as
a root port which sends and receives traffic.
traffic
On non-root bridges only one port can be designated, all others are blocked. Designated
ports forward MAC addresses. Designated ports are selected after the bridge determines the
lowest cost path to get to the root bridge.
By using this method, the redundant links are closed down. They can be opened again if
there is a change in network topology and the link is needed once more.
PORT ROLES
The Root Port and Designated Port perform the same functionality, but Blocking Ports have
two roles: Backup Port and Alternate Port. Spanning Tree Algorithm defines port roles based
on BPDUs. Within the value inside BPDU messages, the port can be compared with others
and the action can be taken accordingly.
Backup Port: The redundant port for a shared network. This port is not for accessing to the
Root Switch. It provides backup for another part of the shared switched network.
Alternate Port: The interface that we are receiving traffic has better BPDU values to access
to the Root Bridge. When the Designated Port fails on the switch then the alternate port will
be used for the path.
Copyright 2013 Alcatel-Lucent. All Rights Reserved.
TAC42059_HO01 Edition I2.0
rstp: Rapid Spanning Tree Protocol (RSTP) compliant with IEEE 802.1D-2004 - default mode.
comp-dot1w: Operation as in IEEE 802.1w but backwards compatible with IEEE 802.1d (this mode was introduced
for interoperability with some MTU types).
p Compliant
p
with the Multiple
p Spanning
p
g Tree Protocol specified
p
in IEEE 802.1Q-REV/D5.0-09/200.
Q
mstp:
pmstp: Provider MSTP mode is implemented according to 802.1ad (provider bridges) . The provider functionality is
implemented and the provider edge functionality is not.
While the 7302 ISAM initially uses the mode configured for the m-VPLS, it will dynamically fall back (on a per-SAP basis) to
STP (IEEE 802.1D-1998) based on the detection of a BPDU of a different format. A trap or log entry is generated for every
change in spanning tree variant.
Some older 802.1W compliant RSTP implementations may have problems with some of the features added in the 802.1D2004 standard. Interworking with these older systems is improved with the comp-dot1w mode. The differences between
the RSTP mode and the comp-dot1w
comp dot1w mode are: the RSTP mode implements the improved convergence over shared media
feature, for example, RSTP will transition from discarding to forwarding in 4 seconds when operating over shared media.
The comp-dot1w mode does not implement this 802.1D-2004 improvement and transitions conform to 802.1w in 30
seconds (both modes implement fast convergence over point-to-point links).
In the RSTP mode, the transmitted BPDUs contain the port's designated priority vector (DPV) (conforms to 802.1D-2004).
Older implementations may be confused by the DPV in a BPDU and may fail to recognize an agreement BPDU correctly.
This would result in a slow transition to a forwarding state (30 seconds). For this reason, in the comp-dot1w mode, these
BPDUs contain the port's port priority vector (conforms to 802.1w).
The 7302 ISAM supports two BDPU encapsulation formats
formats, and can dynamically switch between these (again on a per
per-SAP
SAP
basis):
Cisco PVST
Copyright 2013 Alcatel-Lucent. All Rights Reserved.
TAC42059_HO01 Edition I2.0
[no] edge-port
[no] link-type
link type
mst-instance
[no] path-cost
- Configure path-cost
[no] port-num
[no] priority
[ ] root-guard
[no]
d
- Enable/disable
E bl /di bl STP root-guard
d
[no] shutdown
LAG sub-group
IPD supports grouping of links for a given LAG into a "subgroup" and amongst the
subgroups within a LAG, one subgroup is chosen to be "Active" and within this chosen
subgroup links become Active links (the other subgroup's links are either Standby or
failed)
LAG sub-group
b
will
ill nott b
be supported
t d iin th
the fi
firstt release
l
att NANT-D
NANT D
Alarms
LAG down alarm will be supported
LAG will be down when all links are down or number of active links reaches/goes
below a configured threshold
yp LAG,, and alarm-index should identifyy the LAG
A new alarm-type:
Each LAG instance has its own id and is considered as a new, logical port in all later
configuration, the LAG can be referred to as:
lag-<lag-id>
LACP (Link Aggregation Protocol)
LACP periodic transmission machine supports both the fast (1s) and the slow (30s)
periodic time
A/A: Active/Active
A/S: Active/Standby
The
h slide
l d shows
h
ad
duall h
homing scenario where
h
ad
device is connected
d to the
h network
k via
two independent access points (points of attachment). One access point is the primary
connection; the other is a standby connection that is activated in case the primary
connection fails.
802.1w Rapid Spanning Tree Protocol runs over ISAM uplinks
RSTP runs over ISAM network links, not over subtending links or user links.
RSTP protects against:
link failure
aggregation node failure
RSTP doesnt offer load balancing!
RSTP can be combined with link aggregation (LACP offers load balancing between the
links in a LAG).
In that case, combined link and NT protection recommended (forced switch-over to
full backup LAG instead of bandwidth drop upon failure of a defined number of links
in the LAG you can configure the threshold for switchover how many links in the
LAG must always be operational?)
(Persistency of subscriber management characteristics in 7x50 nodes requires regular
exchanging state info between both switches.)
Copyright 2013 Alcatel-Lucent. All Rights Reserved.
TAC42059_HO01 Edition I2.0
Congratulations
You have finished the training
Thank you!
@@PRODUCT
@@COURSENAME