Standard STP convergence time?

Standard STP convergence time?

NewsGroups | Search | Tools
 comp.dcom.sys.cisco  Post an article  get this group's latest topics as an RSS feed add this group's latest topics to your My MSN content add this group's latest topics to your My Yahoo content  add this group's latest topics to your Google content  YahooMyWeb Yahoo!  Google Google  Windows Live Favorites Windows Live  del.icio.us del.icio.us  digg digg  Add to Netscape Netscape
Subject Author Date
Standard STP convergence time? aaabbb16 06-26-2008
Posted by on June 26, 2008, 12:04 am
If you were  Registered and logged in, you could reply and use other advanced thread options
stp convergence time =50s or 30-50s? why?

TIA,
st

Pure Networks
Posted by Andrey Tarasov on June 26, 2008, 12:26 am
If you were  Registered and logged in, you could reply and use other advanced thread options
aaabbb16@hotmail.com wrote:
> stp convergence time =50s or 30-50s? why?

For regular STP with default timers on Cisco equipment and properly
configured ports - it is 30 seconds.

Regards,
Andrey.

Posted by on June 26, 2008, 9:24 am
If you were  Registered and logged in, you could reply and use other advanced thread options
> aaabb...@hotmail.com wrote:
> > stp convergence time =50s or 30-50s? why?
>
> For regular STP with default timers on Cisco equipment and properly
> configured ports - it is 30 seconds.
>
> Regards,
> Andrey.

Hmmm. I would disagree with that.

I too was somewhat confused by observing that re-convergence
can take either about 30 seconds or about 45 seconds (maybe 35 and
50?).

I believe that it is like this.

For a port that is not connected that gets connected STP has to go
through
all of the states

Blocking
Listening
Learning
Forwarding
45-50 seconds - If I recall correctly

For a port that is already in the network and is Blocking
The transition to Forwarding is about 30-35 seconds

The default timers will be easy to find on the web.

Note that the times do not really range over the interval indicated
but I have specified a range since I cannot remember the correct
times and BPDUs are sent only every two seconds so there will
be a range of times introduced by the port state change possibly
occurring just before or just after a BPDU tx or rx event.

Of course there are other considerations.

For a newly connected port then there may be
physical speed/duplex negotiation
etherchannel negotiation
trunking negotiation

There are also various STP optimisations
portfast
uplink fast
backbone fast

Lastly of course there is Rapid STP which is substantially changed
from
traditional STP and has much lower convergence times. I have not
worked
with it but have the idea that convergence times of one to a few
seconds are
reasonable.



Posted by on June 26, 2008, 9:36 am
If you were  Registered and logged in, you could reply and use other advanced thread options
On 6=D4=C226=C8=D5, =C9=CF=CE=E76=CA=B124=B7=D6, Bo...@hotmail.co.uk wrote:
>
> > aaabb...@hotmail.com wrote:
> > > stp convergence time =3D50s or 30-50s? why?
>
> > For regular STP with default timers on Cisco equipment and properly
> > configured ports - it is 30 seconds.
>
> > Regards,
> > Andrey.
>
> Hmmm. I would disagree with that.
>
> I too was somewhat confused by observing that re-convergence
> can take either about 30 seconds or about 45 seconds (maybe 35 and
> 50?).
>
> I believe that it is like this.
>
> For a port that is not connected that gets connected STP has to go
> through
> all of the states
>
> Blocking
> Listening
> Learning
> Forwarding
> 45-50 seconds - If I recall correctly
>
> For a port that is already in the network and is Blocking
> The transition to Forwarding is about 30-35 seconds
>
> The default timers will be easy to find on the web.
>
> Note that the times do not really range over the interval indicated
> but I have specified a range since I cannot remember the correct
> times and BPDUs are sent only every two seconds so there will
> be a range of times introduced by the port state change possibly
> occurring just before or just after a BPDU tx or rx event.
>
> Of course there are other considerations.
>
> For a newly connected port then there may be
> physical speed/duplex negotiation
> etherchannel negotiation
> trunking negotiation
>
> There are also various STP optimisations
> portfast
> uplink fast
> backbone fast
>
> Lastly of course there is Rapid STP which is substantially changed
> from
> traditional STP and has much lower convergence times. I have not
> worked
> with it but have the idea that convergence times of one to a few
> seconds are
> reasonable.

Thanks,
I think 50s=3D2x15s(forwarding delay)+20s(max age time)
so the max. convergence time is 50s and min. is 30s. right?
why does max age time is from 0-20s?

st

Posted by Andrey Tarasov on June 26, 2008, 3:15 pm
If you were  Registered and logged in, you could reply and use other advanced thread options
Bod43@hotmail.co.uk wrote:
>> aaabb...@hotmail.com wrote:
>>> stp convergence time =50s or 30-50s? why?
>> For regular STP with default timers on Cisco equipment and properly
>> configured ports - it is 30 seconds.
>>
>> Regards,
>> Andrey.
>
> Hmmm. I would disagree with that.

That's fine. How about some facts?

> I too was somewhat confused by observing that re-convergence
> can take either about 30 seconds or about 45 seconds (maybe 35 and
> 50?).
>
> I believe that it is like this.
>
> For a port that is not connected that gets connected STP has to go
> through
> all of the states
>
> Blocking
> Listening
> Learning
> Forwarding
> 45-50 seconds - If I recall correctly

Why? 2 x forwarding delay is 28.5 sec. Where are additional 15-20 sec
coming from?

>
> For a port that is already in the network and is Blocking
> The transition to Forwarding is about 30-35 seconds

So what's the difference between newly connected vs already connected?

> The default timers will be easy to find on the web.
>
> Note that the times do not really range over the interval indicated
> but I have specified a range since I cannot remember the correct
> times and BPDUs are sent only every two seconds so there will
> be a range of times introduced by the port state change possibly
> occurring just before or just after a BPDU tx or rx event.
>
> Of course there are other considerations.
>
> For a newly connected port then there may be
> physical speed/duplex negotiation
> etherchannel negotiation
> trunking negotiation

Not relevant to original question. While etherchannel/trunking
negotiation indeed adds time, it's not part of STP convergence.

>
> There are also various STP optimisations
> portfast

That's enabled on edge ports only and doesn't affect convergence time at
all.

> uplink fast
> backbone fast

Cisco extensions and not part of original 802.1D spec.

> Lastly of course there is Rapid STP which is substantially changed
> from
> traditional STP and has much lower convergence times. I have not
> worked
> with it but have the idea that convergence times of one to a few
> seconds are
> reasonable.

Again, Rapid STP is completely different beast.

Regards,
Andrey.

Similar ThreadsPosted
BGP Route 'Convergence' March 26, 2008, 2:34 pm
OSPF and Static routes convergence December 21, 2004, 11:16 pm
Catalyst 2950 Standard vs Enhanced Image September 14, 2006, 12:47 am
standard vs extended access-list in pix7 September 15, 2006, 3:39 am
Cisco 2950 with Standard image and Access Lists September 7, 2005, 2:26 pm
Two (2) PIX525's set for standard failover, but both show as "Secondary" units August 17, 2007, 12:59 pm
Cisco 4402 Authenticating to Windows 2003 Standard Edition February 18, 2008, 5:25 pm
"Industry Standard" Compact Flash cards in Cisco 2811 routers? January 19, 2007, 11:37 am
One more time. November 5, 2004, 1:57 pm
keep getting a time out March 12, 2007, 6:46 pm

other useful resources:
The Federal Communications Commission (FCC)
Telecommunications Industry Association
Electronic and Software Security Products and Services
International Telecommunication Union

Custom CGI Perl and PHP programming by 1-Script.com

Contact Us | Privacy Policy
The site map in XML format XML site map