Have a requirement to design a flat L2 network for a small manufacturing plant with different buildings. One of the requirement is to have physical layer redundancy, where there is a chance people would dig up the ground and cut off entire conduits. Thus the requirement of having multiple conduits between buildings.
This means a lot of L2 loops and daisy chaining of selected buildings (switch).
Is there a cleaner design to this rather than relying purely on STP to take care of things? Is there anything in particular that we should be aware of?
At this stage, I can see roughly 14 switches in the entire design, scattered across multiple buildings.
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
How clean your design might be would depend on not just the count of your switches, but what's possible for physical interconnections.
Besides STP (would recommend RSTP or MST), some switches support REP and some Cisco switches support Flex Links. There's also Etherchannel and switch stacking (e.g. 2960S, 2960X).
What's technologies you might use depend on your switches' features. Which might be best, again, depends on what you physical topology might support.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...