Page 1 of 1

Proper STP configuration for back-up link

Posted: Mon Feb 27, 2017 6:32 pm
by cwachs
Wish I knew how to do this but it is a bit foreign to me. I have a Netonix on both ends of a wireless link. We just installed a new licensed radio on that link so there are now two radio links between the switches - acting as backhauls. Right now, we have the port at the far end for the new radio turned off until we configure this properly.

What I am after is having all traffic pass over the new licensed link (port 2 on both ends) unless it goes down - then run all traffic over the old unlicensed link (port 4 at the far end).

I am assuming this is a STP configuration but I am not sure how to configure it and if it needs to be configured on both ends or just the far (client) end.

Current STP configuration at the client end image is uploaded. Sorry for such a simple question...

Re: Proper STP configuration for back-up link

Posted: Mon Feb 27, 2017 6:48 pm
by sirhc
I would use Path Cost to determine which link you want to have used first.

You would set the path cost on both switches.

Read this and understand RSTP: https://en.wikipedia.org/wiki/Spanning_ ... e_Protocol

Our switches follow the IEEE protocol standards:
STP - 802.1D
RSTP - 802.1W
MSTP - 802.1S
LACP - 802.1ad

And our UI/CLI use standard nomenclature / verbiage so a simple read of wikipedia should answer all your questions.

In your case you could enable both links with RSTP enabled to prevent a loop then play with the costs and make sure the one you want is getting used first.

Then you can test your failover by logging into the primary link and telling the radio to reboot or doing a port bounce in the switch to force the radio to reboot which should cause the link to fail over which you can monitor by using a constant ping across the links.

I am a firm believer in the whole "teach a man to fish" ideology instead of simply giving people the answer.