Traffic Engineering in MPLS Networks
The first step in a traffic engineering study is to determine whether or not traffic engineering is required for a given network. You can make this determination by doing an IGP analysis of the network. If the IGP analysis shows that one or more links are highly utilized while others are virtually unused, the network can benefit from traffic engineering. In this case, the next step is to create LSPs in the network that will direct traffic from the over-utilized links towards the less utilized links.
After you have determined that a traffic engineering analysis is needed and configured the LSPs to direct traffic to less congested links, you can do the analysis by running a discrete event simulation or a flow analysis.
Note: Flow analysis studies with MPLS require SteelCentral NetPlanner and a Carrier Planner license.
Traffic Engineering Without DiffServ
You can create LSPs in the network topology by using one of the methods described in Configuring Dynamic LSPs, or you can create LSPs based on the traffic flows configured in the network. This operation (Protocols > MPLS > Configure LSPs from Demands) creates an LSP with the same source and destination as each traffic flow in the network.
By setting up constraints on the LSPs, such as requiring that links possess a fixed amount of available bandwidth, you can ensure that traffic will flow over some of the less utilized links in the network. After configuring LSPs, you can do another IGP analysis to make sure that traffic is flowing over the less-utilized links.
Traffic Engineering With DiffServ
Traffic Engineering with DiffServ (DS-TE) lets you control LSP routing on a service class basis. The main difference between traffic engineering with and without DiffServ is that DiffServ lets you associate an LSP with a specific class of service. Generally, there is only one class of service for each DS-TE LSP, however, you can assign more than one class of service (CoS) to an LSP. Cisco supports a maximum of two CoS, Juniper supports up to eight.
Procedure 86: Using DiffServ in Traffic Engineering Studies
-
Create one LSP for each class of service supported between a source and destination. Cisco implementation permits two or fewer classes per LSP, Juniper permits eight or fewer.
-
Configure policy routing on the interface to map the CoS to the appropriate LSP.
2.1 Define a route map in the IP > IP Routing Parameters > Route Map Configuration attribute that sets the next hop to the intended outgoing LSP.
2.2 Assign the route map to the appropriate interface in the IP Routing Parameters > Interface Information > Policy Routing attribute.
-
Size the LSPs.
3.1 Run the size LSPs design action to get the amount of traffic flowing through these LSPs.
3.2 Partition the DS-TE interfaces according to the aggregate BW for each class type.
-
Run the DS-TE design algorithm to get the optimal path setup for the LSPs of different class types.
End of Procedure 86