Professional Documents
Culture Documents
Every effort has been made to remove any material in this project / thesis
where ownership of the copyright does not belong to the author. However,
should you be aware of additional material that may require exclusion due to
copyright restrictions, please contact DigitalLibrary@bcu.ac.uk or call
0121 331 5286.
The University and the Digital Library are not responsible for the inclusion of
any third party copyright material contained in this project / thesis.
STUDENT NUMBER
DATE 23/04/2015
UCEEL Copyright Waiver
________________________________________________________________________
Student Agreement
1. I confirm that Birmingham City University can electronically archive and make
accessible the project / thesis described above via the UCEEL Electronic Library system. I
retain all other ownership rights to the copyright of the document / project work described
above.
2. I confirm the above project / thesis is a true and unaltered representation of the
project / thesis as submitted to Birmingham City University course tutors and examiners.
3. I confirm that the above project / thesis includes / does not include (please delete
as appropriate) material copied from a source (e.g. a book) where ownership of the copyright
does not belong to myself.
If the project / thesis includes such material please supply the following details:
(If No, I understand the electronic copy of my project / thesis available on UCEEL will omit
these sections from view)
Date: 23/04/2015
N.B. If you are at anytime in consultation with a publisher regarding this work you will
need to declare the copy held on UCEEL. Some publishers may regard the UCEEL
copy as constituting prior publication. The copy can be removed from UCEEL if it
becomes an obstacle to future commercial publication.
IS228a/Oct07
Figure 1 MPLS (Roby, 2013)
ABSTRACT
Cell switched-based technologies incorporation
Forwarding performance growths
Layer 3 network layer routing scalability
Improved routing services delivery flexibility
All these problems listed above are very much key to the problems internetworking faces
today. These involves incorporating the several technologies that must exist side-by-side,
developing and scaling to accommodate future technologies, and offering improved
performance, with Internet services and applications.
The introduction of MPLS helped fix these problems and many more as explained in further
details in this Dissertation.
Competing technologies such as Multi-Protocol Label Switching (MPLS), Frame Relay,
Asynchronous Transfer Mode (ATM) and Virtual Private Network (VPN) were compared, a
description of what they are and their uses, stating their advantages and disadvantages,
then concludes on which is the best technology in terms of network efficiency, performance,
Quality of Service (QoS), scalability and extensibility.
MPLS was extensively researched, it highlighted features like Label Switching, MPLS
signalling protocols, Traffic Engineering, MPLS Security (how to defend against threats and
attacks), IPv6 on MPLS and the Disadvantages of MPLS which shows where MPLS could
be improved or why it may not be desirable.
Traffic Engineering This is used to manage network performance by monitoring,
predicting and controlling traffic. It helps to fix congestion by re-routing traffic through
a less congested path, when a path is congested.
MPLS Security This was split into two types of attacks which are Control Plane and
Data Plane, this helps preventing and defending against the attacks much easier as
its isolation means you can focus on which it is.
IPv6 on MPLS IPv6 was created to resolve many of the problems associated with
IPv4 such as auto-configuration, global extensibility and flexibility. IPv6 over MPLS
backbones allows IPv6 domains to interact over an MPLS IPv4 core network.
Finally, a conclusion was made to summarize and finalise the reasons why MPLS should be
implemented on networks, the benefits it brings to the network and its clear advantage over
competing technologies.
ACKNOWLEDGEMENTS
First of all I would like to thank God for helping me get through this Dissertation. Then I
would like to thank (Steve Barson, Dissertation Supervisor) and (Doctor Paul Thomas,
Teacher), Birmingham City University staffs for their guidance and assistance with the
writing and completion of this Dissertation.
Contents
ABSTRACT .......................................................................................................................................... 4
ACKNOWLEDGEMENTS .................................................................................................................. 5
TABLE OF FIGURES .......................................................................................................................... 8
CHAPTER 1 INTRODUCTION .......................................................................................................... 9
1.1 Brief Introduction ....................................................................................................................... 9
1.2 Aims .......................................................................................................................................... 10
1.3 Objectives ................................................................................................................................ 11
CHAPTER 2 LITERATURE REVIEW ............................................................................................. 11
2.1 What is a Virtual Private Network (VPN) ............................................................................. 11
.......................................................................................................................................................... 11
2.2 Asynchronous Transfer Mode (ATM) ................................................................................... 13
2.2.1 Disadvantages of ATM .................................................................................................... 14
2.2.2 Advantages of ATM ......................................................................................................... 14
2.3 Frame Relay ............................................................................................................................ 15
2.3.1 Disadvantages of Frame Relay ..................................................................................... 15
2.3.2 Advantages of Frame Relay ........................................................................................... 16
2.4 Multi Protocol Label Switching (MPLS) ................................................................................ 16
2.4.1 Advantages of MPLS ...................................................................................................... 17
2.4.2 Disadvantages of MPLS ................................................................................................. 18
2.5 Conclusion (Why MPLS is better?) ...................................................................................... 18
SCOPE ................................................................................................................................................ 19
CHAPTER 3 METHODOLOGY ....................................................................................................... 19
Waterfall Model .............................................................................................................................. 19
CHAPTER 4 MPLS MULTI PROTOCOL LABEL SWITCHING ............................................... 20
4.1 Label Switching ....................................................................................................................... 21
4.1.1 Advantages of Label Switching ...................................................................................... 21
4.2 How does MPLS work? .......................................................................................................... 22
4.2.1 MPLS Router Roles/Positions ........................................................................................ 22
4.3 Signalling Protocols for MPLS ............................................................................................... 23
4.4 IPv6 over MPLS ...................................................................................................................... 24
4.4.1 Advantages of Deploying IPv6 on MPLS Backbones ................................................. 24
4.5 Label Stacking ......................................................................................................................... 24
4.6 Penultimate Hop Popping (PHP) .......................................................................................... 25
4.7 Traffic Engineering (TE) ......................................................................................................... 25
4.7.1 Traffic Engineering in MPLS .......................................................................................... 26
4.8 Label Switched Path (LSP) Bandwidth ................................................................................ 29
4.9 Layer 2 Virtual Leased Line or Pseudowires ...................................................................... 29
4.9.1 Layer 3 Virtual Private Network (L3VPN) ..................................................................... 30
4.9.2 Virtual Private LAN service (VPLS) ............................................................................... 30
4.10 MPLS fast reroute ................................................................................................................. 30
4.11 MPLS Protection Methods ................................................................................................... 31
4.11.1 One to one protection ................................................................................................... 31
4.11.2 Many to one protection ................................................................................................. 31
4.12 Multi-Protocol Label Switching Auto-Bandwidth ............................................................... 33
CHAPTER 5 MULTI PROTOCOL LABEL SWITCHING SECURITY ......................................... 36
5.1 Control Plane ........................................................................................................................... 36
5.1.1 LSP Creation .................................................................................................................... 37
5.1.2 LSP Message Snooping ................................................................................................. 37
5.1.3 Control Plane Denial of Service ..................................................................................... 37
5.1.4 Cross-Connection of Users ............................................................................................ 37
5.2 Data Plane ............................................................................................................................... 37
5.3 How to defend against Threats and Attacks ....................................................................... 38
5.3.1 Access Controls ............................................................................................................... 38
5.3.2 Physical Security .............................................................................................................. 38
5.3.3 Control Plane Authentication .......................................................................................... 38
5.3.4 Cryptographic Methods and the MPLS Data Plane .................................................... 39
5.3.5 Security and Label-Based Forwarding ......................................................................... 40
5.4 Resource Reservation ProtocolTraffic Engineering Label Switched Path (RSVP-TE
LSP) Priorities ................................................................................................................................ 40
5.5 Label Switched Path Optimization ........................................................................................ 41
5.6 Multi-Protocol Label Switching Limitations .......................................................................... 41
5.6.1 MPLS LSPs Manual Creation ........................................................................................ 42
5.6.2 Large LSPs wont fit through little pipes ....................................................................... 42
5.6.3 Negatives of Auto Bandwidth ......................................................................................... 42
CHAPTER 6 BASIC MPLS NETWORK CONFIGURATION ....................................................... 43
CHAPTER 7 CONCLUSIONS ......................................................................................................... 50
BIBLIOGRAPHY ................................................................................................................................ 52
REFERENCES .................................................................................................................................. 55
TABLE OF FIGURES
Figure 1 MPLS (Roby, 2013) ............................................................................................................. 4
Figure 2 VPN (LogicalNet, n.d.) ....................................................................................................... 11
Figure 3 ATM (GL Communications Inc., 2014) ........................................................................... 13
Figure 4 OSI Model (Arisar, 2011) .................................................................................................. 21
Figure 5 Traffic Engineering (Steenbergen, n.d.) ......................................................................... 27
Figure 6 Traffic Engineering (Steenbergen, n.d.) ......................................................................... 28
Figure 7 Traffic Engineering (Steenbergen, n.d.) ......................................................................... 28
Figure 8 Traffic Engineering (Steenbergen, n.d.) ......................................................................... 29
Figure 9 MPLS No Protection (Steenbergen, n.d.) ....................................................................... 32
Figure 10 MPLS with Protection (Steenbergen, n.d.) ................................................................... 32
Figure 11 MPLS link and Node Protection (Steenbergen, n.d.) ................................................. 33
Figure 12 Working Auto Bandwidth (Steenbergen, n.d.) ............................................................. 34
Figure 13 Auto-Bandwidth not working (Steenbergen, n.d.) ....................................................... 35
CHAPTER 1 INTRODUCTION
1.1 Brief Introduction
IP over ATM The IP over ATM model was used as it complied with application
requirements by using Layer 3 functionality at the edges of the network, increasing network
efficiency with high speed, label-swapping ATM switches and permanent virtual circuits
(PVC) in the core. IP routing functionality was restricted to the edges of the network as the
IP over ATM model saw software-based routers as the main reason for an inefficient network
performance.
The rapid rise of internet service providers and availability of technologies and equipments
made the IP over ATM model inefficient due to its fundamental scalability problems. Some of
these problems include ATM segmentation and reassembly (SAR) interfaces bandwidth
limitations, 20% cell tax, the n-squared permanent virtual circuit problem, Interior Gateway
Protocol (IGP) stress and its inability to function over non-ATM infrastructures. The biggest
problem was the complications of operating a network using two dissimilar technologies that
were built separately and for different functions.
This led to the emergence of Multilayer Switching. This offered the performance and price of
an ATM switch and the control of an IP router without the complications experienced in the
IP over ATM model. With this apparent solution, there was still a common problem in that
they werent interoperable, they relied on dissimilar technologies to merge ATM switching
and IP routing into an integrated solution.
The problem with Multilayer Switching then led to the solution Multi-Layer Protocol Switching
(MPLS). Internet Engineering Task Force (IETF) created the MPLS group to build a unified
and a technology that can run over any link layer technology (Interoperability). The IP
functionality was untouched, but all of the ATM protocols were removed and replaced with
MPLS label swapping.
1.2 Aims
This project investigates and evaluates MPLS in comparison with other currently existing
technologies (ATM and Frame Relay). It describes in detail how it works, why MPLS is better
and the benefits it offers if implemented on networks.
How its better - Future networks will commonly carry packets, meaning time-division
multiplexing (TDM) is evolving, and new technologies improved to carry packets are being
defined, MPLS is thought of to be a leading connection-oriented packet transport networking
technology. It offers improved network performance because when data is split into smaller
categories such as real time traffic and low priority traffic, the carrier will carry out the
priorities across the network, which will provide quality of service on the network.
1.3 Objectives
To research and investigate the best method to transport data across Virtual Private
Network (VPNs)
Research and evaluate the currently competing technologies (Frame Relay and
ATM), and discuss the importance of network Traffic Engineering (TE).
Compare MPLS with the currently competing technologies (Frame Relay and ATM)
Discuss the future of MPLS in terms of compatibility and efficiency with evolving
network architecture
A Virtual Private Network is a rational network that involves a pair or more of different
physical networks, all of which are safely connected, usually via a public internetwork like the
Internet. There are 3 major types of VPNs:
Extranet This is basically a VPN where a network allows other networks to connect
to it, so data can be exchanged safely.
Individual Remote Access This allows a reliable network user to join the network
from a remote off-net-work site
Site-to-site This connects different sectors of the same network
These 3 types of VPN all share common features such as Scalability, Manageability,
Security and Handling of Private Addresses.
VPNs are split into two depending on where on the OSI level they fall, Layer 2 VPN and
Layer 3 VPN, some vendors even have Layer 4 VPNs, and these are focused on Layer 4
headers and are mostly used to secure tunnels for safe usage, e.g. web traffic and email.
Layer 2 VPN This uses link layer technologies and analyses header to make and execute
VPNs. It also encapsulates various protocols in IP.
Layer 3 VPN This is based on the network layer and implements VPNs and routing with
the network header. It encapsulates IP packets with IP. The most important feature of a
Layer 3 VPN is IP security (IPsec).
Before data travels over a public network, it is encapsulated in encrypted packets, and de-
encapsulated at the receiving end before being sent to the intended receiver.
Data is encapsulated using many different protocols like PPTP, L2TP and IPsec. But the one
thats focused on is the Internet Protocol security (IPsec).
IPsec This is fundamentally a tunnelling protocol used to safely transport IP over a public
network. It has quite a significant potential in the implementation of VPN as it provides a
complete security package, from authentication and encryption to protection against replay.
A great security feature of IPsec is that its connectionless and the tunnel end points doesnt
have to save any protocol state information (even though it has to regulate security data like
keys which may be automatically distributed or manually configured).
Tunnelling This encrypts the whole packet, (both the payload and header) and is
more secure than transport mode.
Transport Mode This encrypts only the payload (the messages in the packet).
The evolution of optical fibres, technological developments and the need for faster
interconnection meant efficient and equally capable WANs and technological tools had to be
developed such as ATMs, Frame Relays and MPLS.
Frame Relay uses a structured frame much the same as LAPD (Integrated services digital
network (ISDN) protocol), the only difference is the frame header is a 2-byte Frame Relay
header field. This carries the user specified DLCI (data link connection identifier) field, which
is the destination address of the frame.
(Philip Smith (1993). Frame Relay. Principles and Applications, Addison-Wesley. P1-
p93.)
MPLS is all about an efficient network performance, it assigns priorities to packets using
labels which in turn improves performance. It is particularly useful for applications that
require QoS (Quality of Service) such as real time applications, Video and Voice over IP
(VoIP), Oracle.
MPLS is provided in the cloud, its a private networking technology which can be comparable
to that of Frame Relay. The fundamental difference between the two technologies is that
QoS can be bought for your applications over your Wide Area Network (WAN). A discussion
with your carrier to conclude the importance of your applications and then this will be
arranged on your WAN.
The important applications are then assigned priority over other traffic when theres a high
load. It may not be the cheapest but is definitely worth it depending on how important the
applications are. For real time applications, MPLS drastically increases quality and efficiency
using its QoS features.
In comparison with VPN and Frame Relay, MPLS can do and will improve the application
uses with better quality and efficiency.
SCOPE
This dissertation intricately researches MPLS and how it could be help improve a networks
performance and efficiency if implemented. It was compared against rival technologies with
a concluding summary that shows it benefits as compared with the others. Then it goes in
extensive detail to show its features such as Virtual Private Network (VPN) and Quality of
Services (QoS).
A basic MPLS configuration was also included to show how its implemented on a network.
CHAPTER 3 METHODOLOGY
Primary Research This research method will be achieved through Cisco LAB simulations
using GNS3
Secondary Research - This research method will include library based research such as
studying books, journal articles, it will also include supervisor meetings.
Waterfall Model
The waterfall model was used in the planning of this project, this model follows a linear
sequential flow, meaning you move on to the next phase only after the previous or current
phase has been completed, theres no going back to make changes once youve moved on.
The following phases were used;
As shown in the table above, the Data Link layer (Layer 2) deals with protocols like Ethernet
and SONET, which carries IP packets only over point-to-point WANs (Wireless Area
Network) or LANs (Local Area Network).
Network Layer (Layer 3) deals with Internet addressing and routing with IP protocols.
In between these 2 layers comes MPLS, it provides extra features for transmitting data over
the network.
If exact matching is cheaper and easier to implement than CIDR, then whats the need for
MPLS?
MPLS is used to implement Traffic Engineering the process of controlling how and where
traffic is routed to on your network, it also helps avoid congestion, allocate priorities to
different services and manage bandwidth.
MPLS can increase network elasticity using MPLS fast reroute.
It can operate various service networks, so IP routing services and data transport services
can be run on the same packet-switched network organization.
MPLS traffic engineering works in conjunction with the IP layer to provide this functionality
and looks at future implementation technologies.
Traffic engineering is the process of efficiently managing the performance of a network by
continuously monitoring, predicting and controlling the operations of data transmission over
a network. Traffic engineers can be found in all types of networks, for example Local Area
Networks (LANs) and Wide Area Networks (WANs), Internet etc.
MPLS traffic engineering enables a quicker traffic flow over a network than other IP based
network. It helps fix network congestion where-by packets from a broken or congested path
are re-routed through a less congested path, to allow the flow of traffic without a disruption of
service. This is very useful, for example, during a flooding attack; the packets are re-routed
to a safer and less congested path.
VPN in conjunction with MPLS is very useful in terms of security, congestion reduction etc.,
because it uses MPLS on present VPN networks to route packets. MPLS allows for the
security of various threats like Denial of Services (DOS), data breaching and quick
recoveries from flooding attacks. It provides the multi-path routing feature with the layer 2
switching technique and add label with IP header to route the packets.
(Spraggs, S. 2000, "Traffic Engineering", BT Technology Journal, vol. 18, no. 3, pp. 137-
150.)
There are two ways Pseudowires is used to provide services to end users, these are Virtual
Private LAN service (VPLS) and Virtual Private Wire Service (VPWS). VPLS allows for
various sites to use an Ethernet broadcast domain using Pseudowires offering any-to-any
connectivity.
4.9.1 Layer 3 Virtual Private Network (L3VPN) - this is an IP only network, it creates virtual
routing domains (VRFs) on its edge routers. It puts end users in a VRF and exchange routes
with the provider router in a secure routing-instance, mostly Interior Gateway Protocol or
Border Gateway Protocol.
It supports intricate networks and connects many infrastructures together. Load-balancing
hash is easily implemented but it can place a considerable load to the Internet service
providers infrastructure, considering the potential edge device has to know the end users
routing table, taking on the sizes of the Routing Information Base (RIB) and Forwarding
Information Base (FIB).
4.9.2 Virtual Private LAN service (VPLS) A VPLS maintains the interconnection of various
networks in a single bridged domain on a controlled MPLS/IP network. VPLS helps with the
Local area network/Wide area network barrier for end users and service providers by giving
an Ethernet interface to end users, which allows for a really fast and flexible service
arrangement, as the bandwidth of the service is not attached to the physical interface. A
VPLS emulates the simple features of a layer 2 switch, such as Broadcasts, Unknown
unicast flooding and Mac learning.
4.11.1 One to one protection This single alternative path is wholly signalled over Resource
Reservation Protocol (RSVP) for every label switched path (LSP), everywhere security is
offered, such as nodes.
As the label depth stays at 1, a significant amount of reservations can occur allowing for a
weighty overhead.
4.11.2 Many to one protection 1 unused Label Switched Path (LSP) is built amongst 2
nodes to be secured, so when theres a failure, various label switched paths (LSPs) are then
re-sent through the unused LSP.
There are also various kinds of failures that can be prevented such as Link Protection and
Node Protection:
Link Protection An unused Label switched path (LSP) is built for any type of link failure
Node Protection An unused label switched path (LSP) is built for any type of router failure.
Figure 9 MPLS No Protection (Steenbergen, n.d.)
The threats against the networks can be divided into threats against the data plane and
threats against the control plane.
5.1.2 LSP Message Snooping An attacker can also snoop on traffic by listening to
information being transmitted by an MPLS signalling protocol like RSVP-TE or LDP, this can
be done by tapping a wire or capture wireless messages. He can then use this information to
find out which labels are being used for different purposes.
5.1.3 Control Plane Denial of Service MPLS control plane can be vulnerable to a lot of
Denial of Service (DoS) attack like CPU memory and cycles being used by the transmitting
RSVP-TE messages or starting LDP sessions. Worst cases can be using MPLS signalling
messages to starve the network of link bandwidth. This type of attack isnt unique to MPLS
but its very important to consider this when building the MPLS control plane protocols.
5.1.4 Cross-Connection of Users Since the use of Virtual Private Network (VPNs) in MPLS
is especially meant to segregate end users traffic, when an attack combines different
networks together, this can be very damaging. There are several ways this can happen, a lot
of them tend to be due to misconfiguration than premediated attacks, and some of the ways
this attack can happen are:
A point-to-point pseudo wire wrongly connecting two sites.
When a site is placed in the wrong Layer 2 Virtual Private Network or Layer 3 Virtual
Private Network (VPN).
Interconnecting two VPNs, could be Layer 2 or Layer 3, into one.
As MPLS data plane uses label swapping to forward packets, it is quite different from an IP
data plane. Because of this reason, it can be quite difficult as an attacker can direct a frame
to a specific target by using the chosen label. Label stacking makes it even more difficult as
a corrupt label can end up many hops away at the top of stack, a long way from where it was
put in the network.
5.3.1 Access Controls This can be used to prevent attacks, by implementing access lists
which allow or deny connection to network routers. So unknown or untrusted connections
can be denied.
5.3.2 Physical Security - This is the first step to take when considering security, this security
can prevent attacks such as wiretapping, and so secure cables can should be used on the
network. MPLS VPNs should also be secure because if the outer edge routers of the
providers network are very secure, then this makes it very difficult for an attacker to change
the physical interface on which his physical interface enter the network.
5.3.3 Control Plane Authentication This technique can be used to prevent or moderate
attacks. Control plane authentication is basically used to accept control plane messages or
connections only if the source can be confirmed. Authentication allows for a router to prevent
attacks such as the illegal creation of LSPs. It also allows for a router to prevent from
misconfiguration problems.
MPLS control plane protocols such as RSVP-TE, LDP etc, have different authentication
processes. LDP uses an MD5 signature scheme for TCP, this process works as following:
The MD5 Signature Option for Label Distribution Protocol Transmission Control
Protocol (LDPTCP) is a configurable Label Switch Router (LSR) option. Two LSRs
that are configured to use this option will agree to use MD5 signatures to guarantee
the validity of their LDP sessions.
An LSR that uses the MD5 signature option is configured with a password (shared
secret) for every potential LDP peer.
Each LSR applies the MD5 hash algorithm to compute the MD5 digest for a TSCP
segment to be sent to a peer. This computation determines the hash over the peer
password linked with the TCP segment.
When the LSR receives a TCP segment with an MD5 digest, it validates the segment
by calculating the expected MD5 digest (using its own record of the password) and
compares the computed digest with the received digest. If the comparison fails, the
segment is released without any response to the sender.
The LSR overlooks LDP Hellos from an LSR for which a password has not been
configured. This guarantees that the LSR establishes LDPTCP connections only with
LSRs for which a password has been configured.
(Davie, B.S. & Farrel, A. 2008, MPLS: next steps, Elsevier/Morgan Kaufmann Publishers,
Boston.)
This process makes sure that an LDP session can be only be controlled with an LSR using
the correct password. Any transmitted message thats been tampered with will be identified
as the MD5 hash is done over the whole TCP segment. Unless a device knows the shared
secret or it can give the right MD5 hash without knowing the shared secret, then a session
will not be established.
With RSVP-TE, authentication is done on RSVP-TE messages and not TCP sections as
RSVP-TE doesnt run through TCP.
There are two types of Router pre-emption, which are hard and soft:
Hard LSP is shredded immediately
Soft Much calmer than the hard option, the LSP is given time to reroute itself and get rid of
the previous.
Big LSPs will not go through small links as it cant fit, meaning any LSP thats bigger than the
size of the circuit its passing through will have serious problems going through it. An
example of this is a 3 Gbps LSP unable to pass through an OC48 circuit as its too big.
To get past this problem, a multi parallel LSPs can be made, for example you can have (9) 2
Gbps LSPs and not (3) 6 Gbps LSPs, but unfortunately this is still isnt a well-supported
method.
There are 5 key things that needs to done to get this network successfully running:
1. Implement MPLS on the provider backbone and ensure its enabled
2. Make VRFs and assign them to an interface on a router
3. Configure MP-BGP between the PE routers
4. Configure OSPF between the routers and their attached CE routers
5. Enable route redistribution between the customer sites and backbone
6. Test and Confirm connectivity
2. Then we make customer VRFs on the PE routers and assign them to the interfaces
facing the customers. Every VRF will then be assigned a route distinguisher (RD) to
distinctively recognize prefixes as belonging to that VRF and a couple of route
targets (RTs) to state how routes should be imported and exported from the VRF.
Then we need to assign a VRF to the correct interfaces and add their IP addresses again.
To see if the PE routers have formed adjacencies with the CE routers, show ip route vrf
Customer A
5. Finally, we have to combine all the sections together with route redistribution, so
enable route redistribution from the customers to OSPF to MP-BGP and do the same
for the PE routers.
To verify that the routes learned from the customers section are now in the BGP table, show
ip bgp vpn4 vrf Customer A
Now its time to the same thing, except this time its done the other way around, from the
BGP to the customer OSPF.
6. To test and confirm that the whole configuration was successful, showing that within
each VRF, a Customer router can connect to another, and they both have a full
routing table.
CHAPTER 7 CONCLUSIONS
Through extensive investigation and research, this dissertation has identified what MPLS is.
MPLS is a way of making sure that packets arrive at its intended target safely, through a
functional path and correctly assigns and executes priorities as configured.
Each packets are assigned a label or labels, and as they are carried across the network, the
labels are either added, replaced or removed. The network exchanges information so that
every switch understands what it should do if it comes across a label.
MPLS was then compared with competing technologies such as VPN, ATM and Frame
Relay, each technology were accurately explained and their features, advantages and
disadvantages pointed out. A conclusion was conducted after the comparison which
highlighted MPLS has the most beneficial of all due to its many benefits such as:
Increase in Uptime MPLS decreases this by sending packets over a substitute path
within 50 milliseconds.
Better user experience because MPLS prioritise traffic, applications such as VoIP
and video will run smoothly.
Bandwidth Utilisation Due to various types of traffic that runs on the links, high
priority traffic can borrow bandwidth capacity from lower priority streams and the
lower priority can borrow capacity aswel when it needs to surge past its usual
bandwidth capacity.
Scalable VPNS MPLS makes it very easy to add sites to VPN, you dont have to
configure a complex mesh of tunnels as should normally be done.
Decrease Congestion Because of MPLS traffic engineering features, traffic can be
transmitted over non-default paths, as the shortest path may be undesirable due to
congestion, this decreases latency, and also because it didnt send traffic through
some already busy links, it manages to avoid congestion also, leading to a very
efficient network.
Hidden network intricacy An MPLS connection between 2 sites can be configured
to behave like an Ethernet cable, so the hops are not seen (Virtual Private LAN
Service, VPLS).
Other than the benefits of MPLS and its implementation, Security, Traffic Engineering, MPLS
disadvantages were also researched
Security, detailing how to secure your network against threats and attacks, isolating into 2
types Data and Control plane, this makes it so much easier to tackle the problem or prevent
against the threat.
Traffic Engineering shows how to efficiently manage a network to improve performance
make it efficient.
MPLS negatives helps point out the features that could be improved, as no technology is
perfect or free from limitations, but even with these, this dissertation showed that the MPLS
benefits far outweigh these limitations.
And finally a basic MPLS network simulation was then configured to show MPLS in action,
and how to implement it in a network, it was tested and confirmed to be correct.
Overall this dissertation has shown that MPLS is a multi-use technology and a should have,
if not a must have for any network, as theres a considerable difference in network efficiency
and performance when using MPLS as compared to its rivals. Its scalability and extensibility
also shows that it can handle changes now and for future technologies.
BIBLIOGRAPHY
Davie, B.S. & Farrel, A. 2008, MPLS: next steps, Elsevier/Morgan Kaufmann
Publishers, Boston.
Cisco,. 'This Documentation Has Been Moved - Implementing Ipv6 Over MPLS
[Support]'. N.p., 2015. Web. 15 Apr. 2015.
Harnedy, Sean J. The MPLS Primer. Upper Saddle River, NJ: Prentice Hall PTR,
2002. Print.
Network Solution Experts,. 'MPLS Compared With Frame Relay And Internet VPN'.
N.p., 2012. Web. 11 Apr. 2015.
Cisco,. 'Virtual Private LAN Services (VPLS)'. N.p., 2015. Web. 5 Apr. 2015.
Garson, Steve. 'What Is A Pseudowire?'. Network Solution Experts. N.p., 2008. Web.
7 Apr. 2015.
Doyle, Jeff. 'Understanding MPLS Label Stacking'. Network World. N.p., 2015. Web.
7 Apr. 2015.
Smith, Philip. Frame Relay. Wokingham, England: Addison-Wesley Pub. Co., 1993.
Print.
Dictionary.com, "label switching," in The Free On-line Dictionary of Computing.
Source location: Denis Howe. http://dictionary.reference.com/browse/label switching.
Available: http://dictionary.reference.com. Accessed: November 09, 2014.
eHow UK, (2014). The disadvantages of atm protocol | eHow UK. [online] Available
at: http://www.ehow.co.uk/list_6119408_disadvantages-automatic-teller-
machines.html [Accessed 19 Nov. 2014].
Casey, J. (2014). The Advantages of MPLS | eHow. [online] eHow. Available at:
http://www.ehow.com/info_12097513_advantages-mpls.html [Accessed 19 Nov.
2014].
Searchtelecom.techtarget.com, (2014). What is traffic engineering? - Definition from
WhatIs.com. [online] Available at:
http://searchtelecom.techtarget.com/definition/traffic-engineering [Accessed 19 Nov.
2014].
Gl.com, (2014). OC-3 / STM-1 and OC-12 / STM-4 Analyzer for ATM Mode. [online]
Available at: http://www.gl.com/lightspeed1000-atm-analyzer.html [Accessed 19 Nov.
2014].
Singh, N. and Kumar, K. (2013). Layer Based M PLS V PN Security Under Flooding
Attack in Wireless Mesh Network. 3rd ed. [ebook] Firozpur Punjab: Department of
Computer Science & Engineering, pp.p1-p6. Available at:
http://www.ijarcsse.com/docs/papers/Volume_3/9_September2013/V3I9-0351.pdf
[Accessed 19 Nov. 2014].
Elfiq.com, (2014). MPLS (Multi Protocol Label Switching) Load Balancing | ELFIQ.
[online] Available at: http://www.elfiq.com/mpls [Accessed 4 Dec. 2014].
Cisco, (2014). Understanding MPLS-TP and Its Benefits [MPLS]. [online]
Available at: http://www.cisco.com/en/US/technologies/tk436/tk428/white_paper_c11-
562013.html [Accessed 4 Dec. 2014].
Gwi.net, (2014). Which is Best for Your Business: VPN, Metro Ethernet or MPLS in
Maine?. [online] Available at: http://www.gwi.net/policy/blog/which-is-best-for-your-
business-vpn-metro-ethernet-or-mpls-in-maine/ [Accessed 4 Dec. 2014].
REFERENCES
Gl.com, (2015). OC-3 / STM-1 and OC-12 / STM-4 Analyzer for ATM Mode.
[online] Available at: http://www.gl.com/lightspeed1000-atm-analyzer.html
[Accessed 2 Dec. 2014].