Contact US

Log In

Come Join Us!

Are you a
Computer / IT professional?
Join Tek-Tips Forums!
  • Talk With Other Members
  • Be Notified Of Responses
    To Your Posts
  • Keyword Search
  • One-Click Access To Your
    Favorite Forums
  • Automated Signatures
    On Your Posts
  • Best Of All, It's Free!

*Tek-Tips's functionality depends on members receiving e-mail. By joining you are opting in to receive e-mail.

Posting Guidelines

Promoting, selling, recruiting, coursework and thesis posting is forbidden.

Students Click Here

BayStack 28115 Switch - Rebuild Spanning Tree

BayStack 28115 Switch - Rebuild Spanning Tree

BayStack 28115 Switch - Rebuild Spanning Tree


How long should it take for a switch to construct a spanning tree? That is, minutes, hours,....days?

Is there anyway to determine if this process is taking place, apart from the display of 'Configuring RUN' on the display?

RE: BayStack 28115 Switch - Rebuild Spanning Tree

Spanning tree converges in as little as 120 seconds for a properly configured tree. Large and poorly configured tree's can take longer. Improperly configured tree's may never properly converge.

LATTISPAN changes a few variables, hence, mileage may be different.

General spanning tree tips.

    1) Choose ROOT bridge priority carefully. You should have some idea which one or two bridges need to compete for the ROOT. They should either be in the core section of the network (backbone) or be the closest to network conversion hardware (FDDI to Ethernet, etc).

    2) Other bridges should become leaf bridges. Set the priority higher for these so they can't compete for ROOT unless the LAN becomes partitioned by failure. Since spanning tree allows multiple links, this should not happen, but.....

    3) Spanning tree allows multiple links, but, don't fill every port with a link to every other switch. This will cause convergence delays. Having a couple of links between main ROOT candidate bridges and one link from each ROOT candidate to each LEAF bridge should be enough. (This will allow for a ROOT candidate failure, and still maintain integrity -- should take about 60 seconds to fail-over).

    More complex bridge setups are possible. My suggestion for these is:
    SETUP a TEST LAN. Don't play with this on a production LAN until you have a majority of the SPAN issues solved. A test LAN will take care of all problems except those generated by heavy traffic and protocol interaction. The test LAN can also be made to simulate bad hardware, by creating failure scenarios. Don't move into production without taking advantage of this type of test.

Spanning tree can either be a great redundancy tool or one of the worst LAN nightmares in the business. Your diligence beforehand pays off in the end....

Reply-to:      netwraith@pcrd.net
thenetwraith    (There is a picture here, but, you just can't see it!)

Red Flag This Post

Please let us know here why this post is inappropriate. Reasons such as off-topic, duplicates, flames, illegal, vulgar, or students posting their homework.

Red Flag Submitted

Thank you for helping keep Tek-Tips Forums free from inappropriate posts.
The Tek-Tips staff will check this out and take appropriate action.

Reply To This Thread

Posting in the Tek-Tips forums is a member-only feature.

Click Here to join Tek-Tips and talk with other members! Already a Member? Login

Close Box

Join Tek-Tips® Today!

Join your peers on the Internet's largest technical computer professional community.
It's easy to join and it's free.

Here's Why Members Love Tek-Tips Forums:

Register now while it's still free!

Already a member? Close this window and log in.

Join Us             Close