The Switch implements three versions of the Spanning Tree Protocol,the Multiple Spanning Tree Protocol (MSTP) as defined by the IEEE 802.1s,the Rapid
Spanning
Tree Protocol (RSTP) as defined by the IEEE 802.1w specification and a version compatible with the IEEE 802.1d STP.RSTP can operate with legacy
equipment implementing IEEE 802.1d,however the advantages of using RSTP will be lost.
The IEEE 802.1w Rapid Spanning Tree Protocol (RSTP) evolved from the 802.1d STP standard.RSTP was developed in order to overcome some limitations of
STP that impede the function of some recent switching innovations,in particular,certain Layer 3 functions that are increasingly handled by Ethernet switches.The
basic function and much of the terminology is the same as STP.Most of the settings configured for STP are also used for RSTP.This section introduces some new
Spanning Tree concepts and illustrates the main differences between the two protocols.
Port Transition States
An essential difference between the three protocols is in the way ports transition to a forwarding state and in the way this transition relates to the role of the
port (forwarding or not forwarding) in the topology.MSTP and RSTP combine the transition states disabled,blocking and listening used in 802.1d and creates a
single state Discarding.In either case,ports do not forward packets.In the STP port transition states disabled,blocking or listening or in the RSTP/MSTP port
state discarding,there is no functional difference,the port is not active in the network topology.Table 6-1 below compares how the three protocols differ
regarding the port state transition.
All three protocols calculate a stable topology in the same way.Every segment will have a single path to the root bridge.All bridges listen for BPDU packets.
However,BPDU packets are sent more frequently – with every Hello packet.BPDU packets are sent even if a BPDU packet was not received.Therefore,each link
between bridges is sensitive to the status of the link.Ultimately this difference results in faster detection of failed links,and thus faster topology adjustment.A
draw-back of 802.1d is this absence of immediate feedback from adjacent bridges.
RSTP is capable of a more rapid transition to a forwarding state – it no longer relies on timer configurations – RSTP compliant bridges are sensitive to feedback
from other RSTP compliant bridge links.Ports do not need to wait for the topology to stabilize before transitioning to a forwarding state.In order to allow this
rapid transition,the protocol introduces two new variables:the edge port and the point-to-point (P2P) port.
Edge Port
The edge port is a configurable designation used for a port that is directly connected to a segment where a loop cannot be created.An example would be a port
connected directly to a single workstation.Ports that are designated as edge ports transition to a forwarding state immediately without going through the
listening and learning states.
An edge por
t loses its status if it receives a BPDU packet,immediately becoming a normal spanning tree port.
P2P Port
A P2P por
t is also ca
pable of ra
pid transition.P2P ports may be used to connect to other bridges.Under RSTP/MSTP,all ports operating in full-duplex mode are
considered to be P2P ports,unless manually overridden through configuration.
802.1d / 802.1w / 802.1s Compatibility
MSTP or RSTP can interoperate with legacy equipment and is capable of automatically adjusting BPDU packets to 802.1d format when necessary.However,any
segment using 802.1d STP will not benefit fr
om the ra
pid transition and ra
pid topolog
y change detection of MSTP or RSTP
.
The pr
otocol also provides for a
variable used for migration in the event that legacy equipment on a segment is updated to use RSTP or MSTP.
The Spanning Tree Protocol (STP) operates on two levels:
Libble takes abuse of its services very seriously. We're committed to dealing with such abuse according to the laws in your country of residence. When you submit a report, we'll investigate it and take the appropriate action. We'll get back to you only if we require additional details or have more information to share.
Product:
Forumrules
To achieve meaningful questions, we apply the following rules:
First, read the manual;
Check if your question has been asked previously;
Try to ask your question as clearly as possible;
Did you already try to solve the problem? Please mention this;
Is your problem solved by a visitor then let him/her know in this forum;
To give a response to a question or answer, do not use this form but click on the button 'reply to this question';
Your question will be posted here and emailed to our subscribers. Therefore, avoid filling in personal details.
Register
Register getting emails for Allied Telesis AT-9724TS at:
new questions and answers
new manuals
You will receive an email to register for one or both of the options.
Get your user manual by e-mail
Enter your email address to receive the manual of Allied Telesis AT-9724TS in the language / languages: English as an attachment in your email.
The manual is 8,71 mb in size.
You will receive the manual in your email within minutes. If you have not received an email, then probably have entered the wrong email address or your mailbox is too full. In addition, it may be that your ISP may have a maximum size for emails to receive.
The manual is sent by email. Check your email
If you have not received an email with the manual within fifteen minutes, it may be that you have a entered a wrong email address or that your ISP has set a maximum size to receive email that is smaller than the size of the manual.
The email address you have provided is not correct.
Please check the email address and correct it.
Your question is posted on this page
Would you like to receive an email when new answers and questions are posted? Please enter your email address.
