nanog mailing list archives
MPLS Reference Designs
From: Alain Hebert <ahebert () pubnix net>
Date: Fri, 27 May 2016 14:36:35 -0400
Hi,
( it might be a bit much to look for that here, but meh its Friday )
Goals
Usual Multi-point L2 services, with L3 path(s) to the Internet
-and/or- inter-site L3 routing (VRF per customer).
This is a simple project involving upgrading a L2 MAN into and more
flexible and isolated (MACs wise) MPLS infrastructure.
Road blocks
We're wasting way too much time with sales rep/engineer, for then,
ending up finding some irrelevant limitation after having spent ~20h of
man power looking at their offering.
Question
( Obviously interoperability is just ridiculous when talking MPLS... )
Thus I'm looking for reference designs from different vendor viewpoint.
Simple enough, but I would like to put the "make/model of the actual
device capable" of doing the function at the P, PE and CE level of their
design.
Too many times we ended up finding boxes that look the part but are
limited in such a way to accomplish only the task that fit the vendor
own MPLS paradigm.
( TLDR: Make us spend more $$$ than needed =D long gone is the
swiss-knife concept )
Offlist answers are fine.
Current thread:
- Preferring RSVP for only one l2circuit. Mohamed Kamal (May 27)
- RE: Preferring RSVP for only one l2circuit. Timothy Creswick (May 27)
- Re: Preferring RSVP for only one l2circuit. Mohamed Kamal (May 27)
- MPLS Reference Designs Alain Hebert (May 27)
- Re: MPLS Reference Designs Mark Tinka (May 27)
- Re: Preferring RSVP for only one l2circuit. Mark Tinka (May 27)
- Re: Preferring RSVP for only one l2circuit. Mohamed Kamal (May 27)
- RE: Preferring RSVP for only one l2circuit. Timothy Creswick (May 27)
