<div dir="ltr">Before only a hardware failure was an spof. Now we've added a configuration and routing protocol spof too. :)</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Feb 28, 2013 at 10:40 AM, Bart Kus <span dir="ltr"><<a href="mailto:me@bartk.us" target="_blank">me@bartk.us</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>Steve,<br>
<br>
I believe I said exactly this in my email. :) It's the
advantages we both pointed out here that have me kind of excited
for this approach.<br>
<br>
Ben,<br>
<br>
The centralization here is not a new danger. With a single switch
@ each site, there was always a <a href="http://en.wikipedia.org/wiki/Single_point_of_failure" target="_blank">SPoF</a>.
A site going down needs to be pulled into redundancy planning.<span class="HOEnZb"><font color="#888888"><br>
<br>
--Bart</font></span><div><div class="h5"><br>
<br>
<br>
On 02/28/2013 08:55 AM, Steve wrote:<br>
</div></div></div><div><div class="h5">
<blockquote type="cite">
<div>If you are using Microtik routers... why would you not use
their multiport router/switches? Keep it all in the same
famility. Their cost is not that much even if you just used it
as a switch compaired to Cisco. And you never know when the
router part might be handy.</div>
<div> </div>
<div>The main reason is you might run into some compatibility
issues down the road. Also, that means you have to learn and
keep in your head mutiliple CLI's and OS's. What a pain.</div>
<div> </div>
<div>Just my 2 cents from working in a mixed router / switch
enviroment. It sucks.... :-) Yes, your tied to one vendor, but
your sorta doing that already by selecting Microtik as your main
wireless radio. </div>
<div> </div>
<div>Or am I missing something here?? </div>
<div> </div>
<div>Steve N0FPF</div>
<div><br>
<br>
</div>
<div class="gmail_quote">On Thu, Feb 28, 2013 at 3:50 AM, Benjamin
Krueger <span dir="ltr"><<a href="mailto:ben.krueger@gmail.com" target="_blank">ben.krueger@gmail.com</a>></span>
wrote:<br>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">
<div dir="ltr">They look good. I'll take a more detailed
review tomorrow. Do remember that if we centralize routing,
we're also centralizing failure. One bad switch can now take
down an entire site.</div>
<div class="gmail_extra"><br>
<br>
<div class="gmail_quote">
<div>
<div>On Thu, Feb 28, 2013 at 3:15 AM, Bart
Kus <span dir="ltr"><<a href="mailto:me@bartk.us" target="_blank">me@bartk.us</a>></span>
wrote:<br>
</div>
</div>
<blockquote style="BORDER-LEFT:#ccc 1px solid;MARGIN:0px 0px 0px 0.8ex;PADDING-LEFT:1ex" class="gmail_quote">
<div>
<div>
<div bgcolor="#FFFFFF" text="#000000">Dear
Ben-Jammin',<br>
<br>
So you might recall our recent discussion where
you weighed in favor of putting "real" switches
into the cell sites to tie the radios together.
My major pushback to you was the price of a
typical Cisco/etc switch.<br>
<br>
Well, I've updated the "<a href="https://www.hamwan.org/t/tiki-index.php?page=Ethernet+Switch+-+8+port&structure=HamWAN" target="_blank">Ethernet Switch - 8 port</a>"
page with 3 new alternatives! They're a miniscule
amount of money more than the D-Link smart switch,
and are in fact full blown RouterOS routers. They
also feature 2 more ports (10 total) than the
8-port requirement, but the catch is only 5 of the
ports are GigE. This might be OK since all the
5SHPn radios are 100Mbit only. The GigE
requirement was for future-proofing only.<br>
<br>
The other super nice thing is they can do MPLS-TE
and preserve QoS. This might simplify the network
structure a lot by moving routing off of the
modems and into these routers. Instead of 7
linked routers at a busy cell site, we'd have 1.
The routing tables get a lot easier. These
routers also have more routing horsepower than
what's in the modems. Especially the $105 model,
which features a faster CPU and twice the RAM.<br>
<br>
2 of the 3 are also rack-mountable, which might be
a good thing in most sites.<br>
<br>
Finally, the idea of using a single OS for all
networking is appealing. No need for fragmented
administrator education, and all the gear is
designed to work together.<br>
<br>
Let me know what you think. I'm kinda psyched
about this approach. I ordered a
RB2011UAS-2HnD-IN for my personal home use to
replace my AP+router here. We'll see how it works
out here.<br>
<br>
--Bart<br>
<br>
<div>RB2011UAS2HnDIN</div>
</div>
<br>
</div>
</div>
_______________________________________________<br>
PSDR mailing list<br>
<a href="mailto:PSDR@hamwan.org" target="_blank">PSDR@hamwan.org</a><br>
<a href="http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org" target="_blank">http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org</a><br>
<br>
</blockquote>
</div>
<span><font color="#888888"><br>
<br clear="all">
<div><br>
</div>
-- <br>
<div dir="ltr">Benjamin<br>
</div>
</font></span></div>
<br>
_______________________________________________<br>
PSDR mailing list<br>
<a href="mailto:PSDR@hamwan.org" target="_blank">PSDR@hamwan.org</a><br>
<a href="http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org" target="_blank">http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org</a><br>
<br>
</blockquote>
</div>
<br>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
PSDR mailing list
<a href="mailto:PSDR@hamwan.org" target="_blank">PSDR@hamwan.org</a>
<a href="http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org" target="_blank">http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org</a>
</pre>
</blockquote>
<br>
<br>
</div></div></div>
<br>_______________________________________________<br>
PSDR mailing list<br>
<a href="mailto:PSDR@hamwan.org">PSDR@hamwan.org</a><br>
<a href="http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org" target="_blank">http://mail.hamwan.org/mailman/listinfo/psdr_hamwan.org</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div dir="ltr">Benjamin<br></div>
</div>