Mejoras al STP

INDICE

 Rapid Spanning-Tree Protocol (RSTP) - (IEEE802.1w)

 Per-VLAN Spanning-Tree (PVST+)

 Multiple Spanning-Tree Protocol (MSTP)

2
Rapid Spanning Tree Protocol
(RSTP)
IEEE 802.1w
 BIBLIOGRAFÍA
W. Wojdak , “Rapid Spanning Tree Protocol: A new solution from
an old technology” CompactPCI Systems -2003
(PDF en web asignatura)

“Understanding Rapid Spanning Tree Protocol (802.1w)”, Cisco White paper

(http://www.cisco.com/c/en/us/support/docs/lan-switching/spanning-tree-protocol/24062-146.html)

4
 RSTP IEEE 802.1w
01 02
111 Bloqueado
111,0
03 04
Designated
Port-ID
01 02 01 02 Root
Bridge-ID
222 333 Cost
111,10 111,10
03 04 03 04 Edge
Root-ID

01 02
444 Objetivo de RSTP = mejorar los tiempos
de reconfiguración del árbol
111,20
03 04
STP  [segundos … un minuto]
RSTP  [menos de 1 seg … pocos seg.]
Figura 1 5
 PORT STATUS & ROLE: DIFERENCIAS

“RSTP splits the Blocking Port role

into Backup and Alternate port roles”
Port role
STP RSTP backup

Root port igual

Designated port igual (*) alternate alternate
Blocking port ---------- Backup o Alternate

Designated Port alternativo (*) Designated-Edge ports

para una misma LAN Root Port alternativo
siempre en Forwarding 6
 BACKUP VS ALTERNATE PORTS
01 02

111 Root
111,0
03 04

01 02 Alternate Port

222
111,10
03 04
Backup Port

Figura 3 Figura 4
7
 ROL DE LOS PUERTOS
 Una vez el algoritmo RSTP converge a un estado estable, el rol de los
puertos queda determinado de la siguiente manera:

En cada puente hacer:

Si mi Bridge-ID es el más bajo entonces soy el puente ROOT y todos mis
puertos son “designated-port”
(excepción: si hay más de un puerto conectado a un mismo segmento  el backup
puerto con número más bajo roll=“designated-port” (estado=forwarding) y el resto
roll=backup-port (estado=discarting) )

En resto de puentes no-ROOT:

(1) el puerto por donde se recibe el “mejor mensaje”  “root-port” (forwarding)
(2) (resto de puertos) Si el mensaje BPDU que se transmite en ese puerto es mejor que los
mensajes que se reciben en ese puerto entonces “designated-port” sino “blocked-port”
(3) Si el puerto es “blocked-port”,
entonces si por ese puerto recibe un “mejor mensaje” de él mismo
entonces backup-port”
y si el mejor mensaje viene de otro puente entonces “alternate-port”
8
 ROL PUERTOS
Ejercicio:
Indique el rol-estado de los puertos

Switch ID
A
Port # 1 2 3 4 5

1 2 1 2 3 4

C B
3 4 5 6

1 2

1 2

D
9
ROL PUERTOS
Estado Rol
forwarding r  root port
 Solución: d  designated port

A
blocking a  alternate port
b  backup port
1 2 3 4 5
d d b d
d

Active link

r a r a a a
1 2 1 2 3 4

C B
3 4 5 6
a a d b

1 2
Inactive link

r a
1 2

D
10
 FORMATO DE LAS BPDUs
Prácticamente el mismo que el de STP.
Diferencias:
STP usa sólo 2 bits del campo “flags”: TC y TCA
RSTP usa 4 bits para codificar ROL y ESTADO del puerto que manda la DPDU
y 2 bits para manejar el mecanismo proposal/agreement.

BPDU
STP  RSTP
Protocol identifier 0  0
version 0  2
menssage type 0/128 2 (sólo existe el de configuración)
TCA, reserved, TC
root-ID
cost
bridge-ID
port-ID
message age 00 Unknown
max. Age 01 Alternate/Backup
10 Root
hello time 11 Designated
forward delay
11
 DIFERENCIAS OPERATIVAS STP - RSTP

 Basado en temporizadores  Necesario Full-Duplex

 SYNC handshake/operation

 No se comunica a los vecinos el  Backup – Alternate

rol/status de los puertos

 Perdida de conexión con Root  Perdida de conexión con Root

 Max Age (tip. 20 seg) 3 Hello consecutivos (3x2 seg)
Si punto-a-punto detección hardware
(link test pulse) (50-150 mseg) (VTC)

 Cambios de Topología  Cambios de Topología

1) TC a Root y de Root a hojas (seg) 1) TC en BPDU a vecinos (inundación)
2) TimeOut corto (+seg) 2) No TimeOut  eliminación inmediata
3) Forward delay (+15+15 seg) 3) Alternate  root port inmediato
 Comprobación de Edge Ports
Edge Ports siempre en Forwarding

12
 01 02 01 02
STP vs RSTP 111 111
111,0 111,0
03 04 03 04

01 02 01 02 01 02 01 02
222 333 222 333
111,10 111,10 111,30 111,10
03 04 03 04 03 04 03 04

root port 01 02 alternate port designate port 01 02 root port

444 444
111,20 111,20
03 04 03 04
Figura 6

13
 SYNC operation
Designated + Discarding port

Designated + Discarding ports

Root-port

New link between Switch A and the 2. 3.

Root switch becomes available:
1.
The link between Switch A and the
root bridge is blocked, and both
bridges exchange BPDUs
Root pone el puerto en
(designated+discarding) y…
…Root sets the proposal bit on the
BPDUs it sends out
a) Switch A blocks the non-edge
designated ports (sync).
b) bridge A explicitly authorizes the
root bridge to put its port in the
forwarding state (agreenment
bit)
At this stage, the newly blocked ports
on Switch A also negotiate a quick
transition to the forwarding state with
their neighbor ports on Switch B and
Switch C that both initiate a sync
operation.
Switch B only has edge designated
ports. Therefore, it has no port to
block.

 The final network topology is reached, just in the time necessary for the new BPDUs
to travel down the tree. No timer is involved in this quick convergence. 14
 PROPOSAL/AGREEMENT SEQUENCE
edge
alternate designated
In order to illustrate the effect of the sync
mechanism on different kind of ports, suppose there
exists an alternate port p2, a designated forwarding
port p3, and an edge port p4 on Switch A. Notice
that p2 and p4 already meet one of the criteria. In
order to be in sync (see step 2 of the preceding
diagram), Switch A just needs to block port p3, and
assign it the discarding state. Now that all of its ports
are in sync, Switch A can unblock its newly selected
root port p1 and send an agreement message to
reply to the root.
Once p0 receives that agreement, it can
immediately transition to the forwarding state.
This is step 4 of the preceding figure. Notice
that port p3 is left in a designated discarding
state after the sync. In step 4, that port is in the
exact same situation as port p0 is in step 1. It
then starts to propose to its neighbor, and
attempts to quickly transition to the forwarding
state.
15
PROPOSAL  SYNC  AGREENMENT

proposal agreenment

proposal
sync
alternate edge
designated

16
 APÉNDICE: FAULT FINDER: IDENTIFYING CABLE PROBLEMS WITH VCT
In this article, we'll explore a new technology
for detecting faults on cable lines that is built
directly into the Ethernet PHY

TDR Provides the Key

VCT technology uses time domain reflectometry
(TDR) to diagnose the attached cable plant.
Similar to the principle of radar, TDR is the
analysis of a conductor by sending a pulsed
signal into the conductor, and then examining
the reflection of that pulse. When the transmitted
pulse reaches the end of the cable, or a fault
along the cable, part or all of the pulse energy is
reflected back to the source. The VCT algorithm
measures the time it takes for the signal to travel
down the cable, see the problem and reflect
back. This measured time is converted to
distance and made available through internal
registers in the Ethernet PHY.

17
http://www.commsdesign.com/showArticle.jhtml;jsessionid=WHFVZMH04YV0YQSNDLPCKH0CJUNN2JVN?articleID=16505651