How to Design STP Loop Free Network

Considering the impact that STP Loop can cause in the Network, I would like to know in real world whether there is granularity in configuration to fend off the loop or just set up VLANs normal way, use the VLAN Interfaces to communicate between VLANs and ignore the granular configuration.

What I mean by granular, to cite just few examples:
- Manually configure for each VLAN a specific Switch to be the Root for that VLAN
- Manually configure Access ports to be Portfast and at the same time configure the Ports with BPDUGUARD
- Manually configure on each VLAN each Blocked port with Loop Guard and UDLD
-Manually configure each VLAN with Root Guad,
Etc....
Etc...

if that's the case there should be a Config Template, that encompasses all those concerns.

Any clarifications on that ?

Thank you
jskfanAsked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Predrag JovicConnect With a Mentor Network EngineerCommented:
Basically that is design question and what are actual needs for specific network.
You can find guidelines for L2 (and other layers) implementation Campus Network for High Availability Design Guide , but details are scattered across the page.

if that's the case there should be a Config Template, that encompasses all those concerns.
Yes. Typically companies create template(s) how specific port type should be configured.
You do not have to use everything that there is there to protect your network, you need to create your own template for that purpose, although those rules are not  enough since in addition there should be general design guide how network should be designed. The reason for that is that you can have different potential problems according to network design.
0
 
jskfanAuthor Commented:
The Example of Network I will use  is a Company that has a Data Center in Site A (the main Site) and has Branches in site B ,C,D,E,F . Each Branch has around 300 computer Users.
Sites are connected with WAN Connection.
 

All the Servers are in Site A, which means client requests will have to come to Site A to retrieve and Update the Information.
0
 
Predrag JovicConnect With a Mentor Network EngineerCommented:
That actually depends on your network design.
Typically you should have for each location separate VTP domain (with it's own VLANs) and connect main site with branch offices over L3 links. Also typically you will have one VTP server per domain (for that VTP domain) and you can use the same VLAN numbers on for each location.
If you have one VTP domain for all locations it is currently considered as a bad design (L2 end-to-end network). Currently recommendation is to use L3 links wherever it is possible.
0
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

 
jskfanAuthor Commented:
Assuming Everything is set up properly..and we are running RPVST.
what do you do next to prevent STP loops ?
Do you have a Configuration Example that you can use on every single VLAN ?
0
 
jskfanAuthor Commented:
Each Site is connected to the DataCenter (Core) as shown below:
stp
0
 
jskfanAuthor Commented:
What Configuration Template will you apply on Access /Distribution/Core Switches in order to avoid STP Loops ?
0
 
jskfanAuthor Commented:
I will do some reading later
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.