Wan Solution

What to choose as a WAN solution, Ethernet or MPLS?

Hi Experts,
I am doing a study on which to choose as a best solution for a WAN connection, MPLS or Ethernet, the key-words am concerned about are:
1) Availability
2) Scalability
3) QoS
4) Securtity
5) Compatibility with WAN acceleration and Optimization
6) Bandwidth
7) VoIP support

I have read some articles on the internet where some suggest Ethernet over MPLS and vice versa. However from my readings and studies I am biasing to MPLS.
I would Highly appreciate your input , hints, and suggestions on this.

Many thanks in advance
Based upon your criteria, I can see that MPLS offers the best of almost all. With an MPLS network, you can get end-to-end ethernet connectivity. Also, your network will have higher availability, scalability and Qos due to the inherent nature of MPLS. You can check up on traffic engineering and backup LSPs to understand how they can exactly help you. With MPLS, your current investment in Ethernet or other protocols is also protected due to the Any transport over MPLS model. www.cisco.com/warp/public/cc/so/neso/vpn/unvpnst/atomf_ov.htm

All telcos around the world are moving to a converged IP core being managed by MPLS with their existing FR/ATM/Ethernet networks all being managed by one MPLS network. As always, you can talk to your equipment vendor. I will bet my money on MPLS. :)

Links:
http://www.cisco.com/warp/public/cc/so/neso/vpn/unvpnst/atomf_ov.htm
http://www.mplsrc.com

I completely agree with you. If you are looking for a stable and scalable line type, and are interested in QoS than you should definitely go for an MPLS based solution.

Ethernet traffic is very hard to control, and one would have need for additional appliances to shape and prioritize your traffic. (Something that is crucial for VOIP or Video Conference). This all comes with the package in an MPLS solution.

There are however also clear advantages of an Ethernet based solutions. First of all it is usually cheaper, which can help you increasing your bandwidth. Furthermore, for certain types of applications, the MPLS solution is less suited: typically these would included the traditional client-server type of software.

Focussing on availability, I do not think tere will be a huge difference between the two. For a secure WAN I would advise to use VPN, regardless of the solution selected.

In most cases your quality is the same and will support the same applications (i.e. VOIP) what need to consider I think are two important areas

1. How is the product delivered over DSL technology or over fibre or Copper? and what redundancy do eachof these methods bring. For example having MPLS over DSL maybe great but if the line breaks it gives you no advantage over Ethernet but it usally more expensive.

2. I would also consider the capabilities of your own internal staff, one limitation of MPLS currently avaliable is you are heavily dependant on your MPLS provider to work with you where as most good IT staff and Engineers can amke anything work over Ethernet

Another item which is so important is look at the countires in which your business operates or would like ot operate int eh future and see what the road map is for MPLS as if many countires have limited MPLS networks where at least you can always buy a basic DSL service and convert to ethernet. Another point is MPLS may limit you on teh equipment you use within your own core network, but that is operator dependant

Given your criteria above, Ethernet is your best bet. The track record (historically) of telecom specific protocols has not been stellar as opposed to more broadly based protocols (such s Ethernet). You will have a lot more options with a commodity protocal than a relatively proprietary one.

Through appropriate selection of networking equipment you can accomplish all of your goals listed using Ethernet and be in a lower risk exposure environment for the future, should MPLS be displaced by "the next big thing." Ethernet isn't likely to vanish in the foreseeable future. The price difference doesn't hurt either.

the reality is that it all comes down to what you are wanting to carry over the WAN connection ... and how much bandwidth you have to play with.

QoS would be implemented in the same way for both, and the application (VoIP) is irrelevant as MPLS would simply be implementing a "tunnel" from one point in the network to another. Security can be argued as with an MPLS tunnel nothing in between will touch anything beyond the MPLS header ... but without encryption it's also kind of an irrelevant point.

Ethernet would certainly be the simpler approach and would provide the maximum bandwidth (as you don't have the MPLS overhead) but is more limited in terms of scalability for a larger network. In the same way, Ethernet over multiple links with a flavour of RSTP, MLPPP or EtherChannel will increase your availability on a point to point network, whilst MPLS provides a much better solution "end-to-end". There's a reason why simple Ethernet interfaces are cheaper ... but it really comes down to your application as to which would be "best".

this is also depending on the availability and the possibilities your ISP has. A simple solution is to write a (detailed) RFI or RFP and send it to a couple of ISP's who have presents in the area(s) you want to connect and see what they come up with.

With MPLS you will have your own VPN, with Ethernet over WAN they have E-VPN which is much cheaper and has higher bandwidth.

As I work for BT check out our website which has a lot of info regarding these subjects.

If you need more info or want to connect via Linked In, please do not hesitate to send me an email.

Best regards,
Johan den Hartog.

Links:
http://www.bt.com

I just checked the references.

GRE/Ethernet is a terminal adaptation (L2) of Ethernet to DSL. The WAN connection is DSL.

MANs can be self-provided using a network of interconnected switches or a network of interconnected routers. Here Ethernet acts as the network interface at L3 or switch interface at L2. It is pure Ethernet. However to increase the range between the switches/routers an adaption to a WAN L1/L2 interface is required, such as GRE!

Ethernet/Sonet is just another terminal adaptation!