On 24/Oct/16 22:13, Wayne Bouchard wrote:
> If the reason for L2 transport is purely customer driven and purely
> ptp, then a L2 VPN solution would be better than directly transporting
> the frames. If you don't have to bridge it directly, don't. Keep the
> core at layer 3 wherever possible. L2
If the reason for L2 transport is purely customer driven and purely
ptp, then a L2 VPN solution would be better than directly transporting
the frames. If you don't have to bridge it directly, don't. Keep the
core at layer 3 wherever possible. L2 can be very hard to debug when
there are issues.
On
On 22/Oct/16 23:59, Marian Ďurkovič wrote:
>
> The question here is, whether MPLS is the *optimal* solution for campus needs.
>
> The same functionality could be obviously achived by multiple technologies,
> and while MPLS is well supported on high-end SP routers, various limitations
> appear
On Sat, 22 Oct 2016 21:29:22 +0200, Mark Tinka wrote
> On 21/Oct/16 19:02, Javier Solis wrote:
> > With that said, what are the best options to be able to cost effectively
> > scale without using vlans and maintaining a routed core? What technology
> > would someone suggest (mpls, vxlan,etc) to
On 21/Oct/16 19:02, Javier Solis wrote:
> With that said, what are the best options to be able to cost
> effectively scale without using vlans and maintaining a routed core?
> What technology would someone suggest (mpls, vxlan,etc) to be the best
> possible solution?
>
IME, MPLS is a good
This is exactly what we are recommending and building for our customers in that
space. Most of the time the university network acts as a provider, so to me it
only makes sense to use that type of tech. The biggest problem then is
support, which could be something they are unwilling or unable
On Oct 21, 2016, at 4:18 PM, Youssef Ghorbal wrote,
in part:
>
> Until people start complaining they can no more auto discover their
> Time Capsule left in the other building whereas their colleagues in
> the other building can etc etc. All fancy discover protocols
> FWIW, if I had to solve the "college across buildings with common
> access control" problem I would create MPLS L3 VPN's, one subnet
> per building (where it is a VLAN inside of a building), with a
> "firewall in the cloud" somewhere to get between VLAN's with all
> of the policy in one place.
>
In a message written on Fri, Oct 21, 2016 at 12:02:24PM -0500, Javier Solis
wrote:
> In a campus network the challenge becomes extending subnets across your
> core. You may have a college that started in one building with their own
> /24, but now have offices and labs in other buildings. They
Our campus started off with L2 vlans spanning through the core, but we
migrated to routing in the core and moved our many spanning tree/broadcast
domains to the edge of buildings fronted by redundant routing with ecmp to
a redundant core utilizing ospf.
In a campus network the challenge becomes
On 21/Oct/16 16:19, Marian Ďurkovič wrote:
>
> Much easier to setup, operate & maintain than MPLS and obviously much
> lower cost. Based on 6-months production experience, my recommendation
> would be to stay away from MPLS in the campus.
I'd be curious to hear what MPLS-specific issues you
> Compared to MPLS, a L2 solution with 100 Gb/s interfaces between
> core switches and a 10G connection for each buildings looks so much
> cheaper. But we worry about future trouble using Trill, SPB, or other
> technologies, not only the "open" ones, but specifically the proprietary
> ones based
Mark Tinka wrote:
> Not sure what gear you're using now, but you'll get full routing and
> MPLS features on the platforms such as the Cisco ASR920. I'd have
> recommended the Cisco ME3600X, but they just announced EoS/EoL last
> night, which means that while you can still order it until October
On 20/Oct/16 18:45, Roland Dobbins wrote:
>
> Sure - but it's probably worth revisiting the origins of those
> requirements, and whether there are better alternatives.
Indeed.
What we've seen is customers who prefer to manage their own IP layer,
and just need transport. These types of
On 20 Oct 2016, at 23:32, Mark Tinka wrote:
Some requirements call for Ethernet transport as opposed to IP.
Sure - but it's probably worth revisiting the origins of those
requirements, and whether there are better alternatives.
---
Roland Dobbins
On 20/Oct/16 18:29, Jason Lixfeld wrote:
> Likely not at the PE, true, but he did say Internet access, so I err’d on the
> side of assuming DFZ, somewhere. If that assumption is true, FIB resources
> for the SP interconnect nodes and filtering towards the PEs, absolutely..
I assumed 0/0 +
On 20/Oct/16 18:24, Roland Dobbins wrote:
>
> And I'd definitely recommend figuring out why that's being done so
> broadly today, and working to reduce its prevalence and scope, moving
> forward.
Some requirements call for Ethernet transport as opposed to IP.
I don't know the details of the
> On Oct 20, 2016, at 12:23 PM, Mark Tinka wrote:
>
>
>
> On 20/Oct/16 17:12, Jason Lixfeld wrote:
>
>>
>> It’s only more expensive the more big vendor products you use. Sometimes
>> you need to (i.e.: Boxes with big RIB/FIBs for DFZ, or deep buffers), but
>> more
On 20 Oct 2016, at 23:17, Mark Tinka wrote:
especially looking at how much Layer 2 traffic you're hauling around.
And I'd definitely recommend figuring out why that's being done so
broadly today, and working to reduce its prevalence and scope, moving
forward.
On 20/Oct/16 17:12, Jason Lixfeld wrote:
>
> It’s only more expensive the more big vendor products you use. Sometimes you
> need to (i.e.: Boxes with big RIB/FIBs for DFZ, or deep buffers), but more
> and more, people are looking to OCP/White Box Switches [1][2].
It doesn't sound like the
On 20/Oct/16 17:05, Leo Bicknell wrote:
> I would challenge your port cost assumption for "routers". For
> instance the Arista 7280 could deliver can be had with 48 10GE SFP+
> ports with full Internet routing capabilities. If you're used
> to Cisco or Juniper, it is worth looking further
On 20/Oct/16 15:43, steven brock wrote:
>
> If you had to make such a choice recently, did you choose an MPLS design
> even at lower speed ?
> How would you convince your management that MPLS is the best solution for
> your campus network ? How would you justify the cost or speed difference ?
Hi,
> On Oct 20, 2016, at 9:43 AM, steven brock wrote:
>
> Compared to MPLS, a L2 solution with 100 Gb/s interfaces between
> core switches and a 10G connection for each buildings looks so much
> cheaper. But we worry about future trouble using Trill, SPB, or other
>
From what you describe I do think you have many options, including
more than just the ones you laid out. When you're under 10km and
own your own fiber the possibilities are virtually limitless.
First off, you don't want to be running spanning tree across a
campus. While I don't think you need
Dear NANOG members,
We operate a campus network reaching more than 100 buildings on 5 campuses.
We also operate a regional backbone and the interconnexion to our NREN.
The current architecture is made of a L2 backbone and a few routers.
Most of the buildings are connected with a 1 Gb/s link using
25 matches
Mail list logo