MPLS Traffic Engineering

Project Title

MPLS Traffic Engineering

Project Area of Specialization Cloud Infrastructure,Project Summary

Easy way of transporting layer 2 frames

2.point to point transport with QoS gaurantees service over a packet instracture

3.Easy migration toward network convergence

4.useful for re-routing traffic in congested environments

5. Buil innovative service like Virual MPLS FRR

6.MPLS puts IP routing functions on ATM
switches. This provides better IP and ATM
integration and better scaling.

7.On non-ATM equipment, MPLS simplifies the
forwarding operation and introduces
‘lightweight virtual circuits’. This allows
advanced features like MPLS Traffic
Engineering.

Project Objectives

Link not available
• Economics
• Size of pipes
• Failure scenarios
• Unanticipated growth
• Class of service routing

Resolution. MPLS TE works by learning about the topology and resources available in a network. It then maps the traffic flows to a particular path based on the resources that the traffic flow requires and the available resources.

Project Implementation Method

Abstract: One of the required characteristic of any network is the capacity to keep services running after node or network failure. This ability is known as network flexibility and an important for service providers. The flexible of networks recover from failure by fixing them automatically by transferable traffic from failed node of the network to another portion of the network. The traffic transferable process should be fastest to guarantee that the obstruction of service due to a network or link failure is either unnoticeable or as small as possible and kept the service running .in the proposed system MPLS TEfor use Fast Reroute mechanism to providing backup and redundancy tunnel that can be programmed in to the router. This way to recalculate the paths happens before the failure actually occurs. Fast Rerouting protects paths from link and node failures and networks by locally repairing the protected paths and re-routing them through backup tunnels at same the point of failure and allowing the data to flow continuously. In case of a network failure or node. Keywords: MPLS, IP, OSPF, VOIP, TE

The simulation environment provided in this paper is based on GNS3 Version 1.5.1. Router used in GNS3 -Cisco 7200 with IOS 15. The simulations were setup using a normal IP network using OSPF and MPLS network with Fast Reroute are implemented. The results from these simulations are used for comparative between the networks. Simulations are established on the same topology as shown in figure 5. The network depend of eight routers. Fast Ethernet link are connected between routers of network. Basic BGP (OSPF) is working in the network. MPLS domain is enabled in all routers except for R8 and R1 .R8 and R1 are Edge Routers .R7 and R2 are provider edge router that connect with customer to MPLS domain. The core network depend of four routers R4, R5, R6 and R3. R7 and R2 are called theEgress andIngress routers. The performance of network of with IP network implement without MPLS compared to MPLS FRR (fast Reroute) for link and node failure.The comparison done depend on Success rate, Packet loss and round trip time.

Benefits of the Project

Traffic engineering refers to the process of selecting the paths that traffic will transit through the network. Traffic engineering can be used to accomplish a number of goals. For example, a network organization could traffic engineer their network to ensure that none of the links or routers in the network are over or under utilized. Alternatively, a network organization could use traffic engineering to control the path taken by voice packets in order to ensure appropriate levels of delay, jitter, and packet loss.

MPLS supports traffic engineering thus allowing network organizations to associate a Label-Switched Path (LSP) with whatever physical path they choose. MPLS also supports constraint-based routing, which ensures that an LSP can meet specific performance requirements. In addition, tools that work on a per-LSP basis allow network organizations to identify usage levels and plan accordingly.

MPLS-based traffic engineering also supports the rerouting of traffic around a failed link or router quickly enough to not adversely affect the users of the network. To achieve this fast restoration time, a back-up LSP can be established at each node. The failover mechanisms are triggered by physical link or routing events that indicate that the link or node is down. The traffic can be switched immediately to this LSP once the failure has been detected.

Technical Details of Final Deliverable

1. An unlabeled IP packet is received, and is routed unlabeled to the
next hop.
2. An unlabeled IP packet is received, a label is inserted in the header,
and is switched to the next hop.
3. A labeled IP packet is received, the label is swapped, and is switched
to the next hop.
4. A labeled IP packet is received, the label is stripped off, and is routed
to the next hop or destination.
Frame-mode MPLS performs as follows:
1. An edge LSR receives a packet.
2. The edge LSR performs a routing table lookup to determine the next
hop (or exit interface).
3. If destined for the MPLS network, the edge router inserts the label
between the Layer-2 and Layer-3 headers.
4. The edge LSR forwards the labeled packet to the core LSR.
5. Core LSRs will route solely based on the label, and will not perform a
routing table lookup.

Final Deliverable of the Project HW/SW integrated systemType of Industry Telecommunication Technologies OthersSustainable Development Goals Partnerships to achieve the GoalRequired Resources