Cisco Support Community
Showing results for 
Search instead for 
Did you mean: 
New Member

STP limitations


I once read the limitation of the maximum switches that can be connected in a loop within single STP domain, but I can’t find any document today...

Knowing that we can modify the timers, we are aiming for a fast converging network, so we won’t increase the standard timers/delays.

(1) Can someone provide me the answer (and/or -any- URL)? And does Rapid STP change that amount?

(2) A second thought is, imagine we create a “ring” with the maximum amount of switches, but each one of them connecting another directly. Do we exceed the limit now? Or in other words, must we count these switches too to define the maximum hops?




Re: STP limitations

1.RSTP flooding may cause duplicaion of packets due to successive flush of forwarding CAM table entries.

2.As like the routers in AS the switches also have some limitations.And the limitation depends on the need fot he customers

Re: STP limitations

From the root bridge, BPDUs can cross a maximum number of bridges before being discarded. With RSTP or between MST region, this limit is max age (the age field has been more or less hijacked and is now in fact rather a hop count). Inside MST regions, you have a max-hops limit. Max age goes up to 40, and in the latest IOS implementation, max-hops is 255. So you should be able to go through 40*255 bridges by combining MST regions.

You don't need to tune any timer with RSTP/MST. It's actually recommended you don't tune any timer. They have no impact on convergence time if you network is adapted to these protocols (ie links are point to point and edge ports correctly identified).

Whether in a ring or any other topology, just make sure that the bpdus sent by the root can reach the edge of the network, even after some link failure (for instance in the ring, the distance from the root to the edge could double in case of a single link failure).



CreatePlease to create content