cancel
Showing results for 
Search instead for 
Did you mean: 

Loop for redundancy

Highlighted
New here

Loop for redundancy

We run a building with multiple switches placed on multiple floors.  Currently, the setup is a chain between the 1 floor -> 3rd floor -> 5th floor -> Penthouse switch.  All in line.  The problem is, obliviously, if one of the switches go down in line, the penthouse switches goes down as well.

 

We have ran a fiber line from the 1st floor to the penthouse switch and plugged in via SPF+ port.  

 

Question is, how do we properly configure both the uplink ports so that if one fails, it uses the other?  and does so automatically.  RTSP settings?  root guard?

 

 

2 REPLIES
New here
Head in the Cloud

Re: Loop for redundancy

@lp101 they wont be able to use link aggregation, as you need dual links (or more) between the same two switches (or switch stacks).

 

@Dasilva13 it would be better if you could change your switch design.  It would be better to have a pair of core switches, and then run a pair of links between that and each floor, rather than chaining them together floor to floor.

 

If you need to keep the current design then make each port connecting to another switch a trunk port.  Leave RSTP turned on, and it will knock one link out to get rid of the loop.  You should make one switch the "core" or "main switch", and lower its spanning tree priority (Switch/Switch Settings/under "STP bridge priority" choose the switch/lower the priority to something like 16384).

 

I would not both using root guard.  I would make sure every port that is not connected to something that does not need VLAN trunking (aka ports to workstations) are made access ports.