[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
MPLS in the campus Network?
- Subject: MPLS in the campus Network?
- From: mark.tinka at seacom.mu (Mark Tinka)
- Date: Sat, 22 Oct 2016 21:29:22 +0200
- In-reply-to: <CAExkOzw-74TU1kmdt5dfLYzCmtU8MhyMOg=SZ82QqxLhGrFZ+g@mail.gmail.com>
- References: <[email protected]> <[email protected]> <CAExkOzw-74TU1kmdt5dfLYzCmtU8MhyMOg=SZ82QqxLhGrFZ+g@mail.gmail.com>
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 use-case here. If you are going to use the same /24
(or whatever prefix applies to you) across multiple locations, you will
need some kind of overlay. Be it IP-in-IP, GRE, MPLS (l2vpn's or
l3vpn's) or plain old Ethernet, you will need something.
MPLS makes a lot of sense to me. It's native in hardware, upper-layer
agnostic, mature, and reasonably affordable even at low scale. While I
would not say MPLS is simple from a "complexity in your network"
standpoint, it does provide a notable amount of simplicity when you're
looking for an overlay that is transparent to all manner of Layer 2 and
Layer 3 applications that a packet-based network needs to transport.
Mark.