[122453] in North American Network Operators' Group
RE: Recommendations for router with routed copper gig-e ports?
daemon@ATHENA.MIT.EDU (Eric Morin)
Sun Feb 14 21:11:27 2010
Date: Sun, 14 Feb 2010 22:11:03 -0400
From: "Eric Morin" <EricMo@BarrettXplore.com>
To: "Jason Lixfeld" <jason@lixfeld.ca>
Cc: North American Network Operators Group <nanog@merit.edu>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
I actually think the 912 is different then the 904 and 906, as I was
discouraged from buying the 912, and I REALLY wanted the extra ports.
That's not to say that the 904/906 doesn't have the same problems. I use
it for a router with a bunch of connected networks, DHCP relay, and BGP.
Other then the below mentioned DHCP-relay bug, and an FTP command bug
(which was also quickly fixed) they have served us well.
Eric RR Morin
-----Original Message-----
From: Jason Lixfeld [mailto:jason@lixfeld.ca]=20
Sent: Sunday, February 14, 2010 9:54 PM
To: Eric Morin
Cc: North American Network Operators Group
Subject: Re: Recommendations for router with routed copper gig-e ports?
The OS906 may be different than the OS912, but be warned that I had =20
major issues with OS912 relating to LDP and OSPF. Constant crashes of =20
both LDP and OSPF made the device totally unusable. We had to ship =20
all 20 back to them. It was really messy. This was about 6 months =20
ago, and their code may have been fixed, so YMMV.
On 2010-02-14, at 8:47 PM, "Eric Morin" <EricMo@BarrettXplore.com> =20
wrote:
> I have found the MRV OS906 (6 port 10/100/1000/SFP + Eth OBM) to be a
> very cost effective and an extremely flexible device. It's a linux =20
> based
> device with a router shell but all forwarding is done in hardware
> (ASICs). It has a very flexible implementation of many L2 features =20
> (QnQ,
> inner or outer tag swapping, eth OAM, ERP) but also sports standard
> routing switch features and protocols like BGP, OSPF, even IS-IS!
>
> The cost of the device is 1/4 of a 3560G (etc).
>
> MRV's support has been very good. We found a bug in the DHCP-Relay
> function where it would not broadcast back to a client that
> discovered/requested with the broadcast bit set. They provided a new
> spin of code with the fix within days!
>
> http://www.mrv.com/product/MRV-OS-OS900-SDB
>
> I hope this helps
> Eric RR Morin
>
> -----Original Message-----
> From: Lorell Hathcock [mailto:lorell@hathcock.org]
> Sent: Sunday, February 14, 2010 4:42 PM
> To: 'North American Network Operators Group'
> Subject: Recommendations for router with routed copper gig-e ports?
>
> All:
>
>
>
> I'm involved in a project where we are cutting over a WISP from =20
> being a
> single broadcast domain into the grownup real world of routing between
> tower
> nodes. Of course the equipment is all Mikrotik and the single =20
> broadcast
> domain was easy to implement, so that's why it was done this way.
>
>
>
> My problem on the redesign is I want to provide routed, copper gig-e
> ports
> at a reasonable price per port.
>
>
>
> My thought is to provide one copper gig-e port for all of the APs at a
> tower
> and a copper gig-e port for each backhaul to other towers (typically 2
> to
> 4). On the core nodes, I want to have one fiber gig-e port for the
> internet
> connection. BGP would be implemented on the routers that connect to =20
> the
> internet. OSPF would be implemented on all of the backhaul ports.
>
>
>
> So number of routed, copper gig-e ports at each tower would be:
>
>
>
> 1 - AP network (need suggestion for cost effective gig-e switch)
>
> 2 to 4 - back haul ports
>
> 1 - internet port (on one out of every 4 towers or so) (and most =20
> likely
> fiber instead of copper)
>
>
>
> Does anyone have any suggestions?
>
>
>
> Sincerely,
>
>
>
> Lorell Hathcock
>
>
>
> OfficeConnect.net | 832-665-3400 x101 (o) | 713-992-2343 (f) |
> lorell@officeconnect.net
>
> Texas State Security Contractor License | ONSSI Certified Channel
> Partner
>
> Axis Communications Channel Partner | BICSI Corporate Member
>
> Leviton Authorized Installer
>
>
>
>
> --=20
> This message has been scanned by MailScanner
>
>
--=20
This message has been scanned by MailScanner
