* Traffic engineering selects the path that traffic will transit
In previous newsletters, we discussed the emergence of private Multi-protocol Label Switching networks. This newsletter will discuss the ability of those networks to support traffic engineering.
In previous newsletters, we discussed the emergence of private Multi-protocol Label Switching networks. This newsletter will discuss the ability of those networks to support traffic engineering.
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.
