Cisco R.E.P - Resilient Ethernet Protocol

Started by Dieselboy, March 06, 2017, 09:03:03 PM

Previous topic - Next topic
Print
Go Down Pages1
User actions

deanwebb

#1
March 07, 2017, 08:59:03 AM
Already seeing some fun stuff in the "Limitations" section. Aside it being proprietary, that caveat about looping and limited redundancy raised my eyebrow.

:phone:
Take a baseball bat and trash all the routers, shout out "IT'S A NETWORK PROBLEM NOW, SUCKERS!" and then peel out of the parking lot in your Ferrari.
"The world could perish if people only worked on things that were easy to handle." -- Vladimir Savchenko
Вопросы есть? Вопросов нет! | BCEB: Belkin Certified Expert Baffler | "Plan B is Plan A with an element of panic." -- John Clarke
Accounting is architecture, remember that!
Air gaps are high-latency Internet connections.

Dieselboy

#2
March 07, 2017, 09:06:23 PM
I especially liked the bit about how if the engineer doesn't pay proper attention to config, then they can and probably will create a bridging loop. But the same is true for MST and I love MST when you have a network with equipment from multiple vendors, such as HP and Cisco. You just have to know how to architect it. It's not like RPVST+ where you can just plug it all in and be done with it or may be go one step further by plugging it all in, set the desired root bridge priority to the lowest value and then be done with it  :XD: :mrgreen:
Print
Go Up Pages1
User actions