0% found this document useful (0 votes)
3 views2 pages

Diffrence Between STP and RSTP

Uploaded by

fgtfortigate01
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
3 views2 pages

Diffrence Between STP and RSTP

Uploaded by

fgtfortigate01
Copyright
© All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd

STP (802.1d) Rapid STP (802.

1w)
In stable topology all
In stable topology only the root sends
bridges generate BPDU every Hello (2 sec) :
BPDU and relayed by others.
used as “keepalives” mechanism.

Port states

Disabled
Blocking Discarding (replace disabled, blocking and
listening)
Listening
Learning
Learning
Forwarding
Forwarding

Port roles

Root (Forwarding)
Root (Forwarding)
Designated (Forwarding)
Designated (Forwarding)
Alternate (Discarding)
Non-Designated (Blocking)
Backup (Discarding)

- An edge port (end node port) is an


Additional configuration to make an end
integrated Link type which depends on the
node port a port fast (in case a BPDU is
duplex : Point-to-point for full duplex &
received).
shared for half duplex).

Topology changes and convergence

Use timers for convergence (advertised by - Introduce proposal and


the root): agreement process for synchronization (<
1 sec).- Hello, Max Age and Forward delay
Hello (2 sec)
timer used only for backward compatibility
with standard STP
Max Age (20 sec)
Only RSTP port receiving STP (802.1d)

Forward delay timer (15 sec) messages will behaves as standard STP.
Faster transition on point-to-point and edge
ports only:Less states – No learning state,
Slow transition (50sec):Blocking (20s)
doesn’t wait to be informed by others,
=>Listening (15s) =>Learning (15s)
instead, activelylooks for possible failure
=>Forwarding
by RLQ (Request Link Query) a feedback
mechanism.

Use other 6 bits of the flag octet (BPDU type


2/version 2):Bit 1 : Proposal

Bit 2, 3 : Port role

Use only 2 bits from the flag octet:Bit 7 :


Bit 4 : Learning
Topology Change Acknowledgment

Bit 5 : Forwarding
Bit 0 : Topology Change

Bit 6 : Agreement

Bit 0, 7 : TCA & TCN for backward


compatibility

The bridge that discover a change in the


TC is flooded through the network, every
network inform the root, that in turns
bridge generate TC (Topology change) and
informs all others by sending BPDU with TCA
inform its neighbors when it is aware of a
bit set and instruct them to clear their DB
topology change and immediately delete
entries after “short timer” (~Forward
old DB entries.
delay)expire.

If a non-root bridge doesn’t receive Hello for


10*Hello (advertised from the root), start Wait for 3*Hello (advertised from the root)
claiming the root role by generating its own before deciding to act.
Hello.

Wait until TC reach the root + short timer Delete immediately local DB except MAC of
(~Forward delay) expires, then flash all root the port receiving the topology changes
DB entries (proposal)

You might also like