Traffic engineering allows you to manage the direction that data packets take by bypassing the conventional routing architecture, which employs routing tables. Traffic engineering redirects traffic from congested links to alternative links that the automatically determined destination-based shortest path would not choose. Traffic engineering enables you to:
- Utilize pricey long-distance fibers more effectively.
- In the event of single or numerous failures, you can control how traffic is diverted.
- On a path-by-path basis, categories essential and normal traffic.
Building label-switched routes (LSPs) between routers is the foundation of the traffic engineering concept. An LSP is connection-oriented, like a virtual circuit in Frame Relay or ATM. LSPs are unreliable: Although preferential treatment is conceivable, packets entering an LSP do not have delivery guarantees. In that packets entering a network are contained in an envelope and switched across the full path without being affected by intermediary nodes, LSPs are comparable to unidirectional tunnels in this regard. LSPs give network administrators precise control over how packets are forwarded. An LSP may employ several primary and secondary channels to offer reliability.
LSPs can only be set up for BGP traffic (traffic whose destination is outside an autonomous system [AS]). In this instance, the presence of LSPs has no impact on traffic within the AS. LSPs can be set up to affect BGP and interior gateway protocol (IGP) traffic, which means they impact intra-AS and inter-AS traffic.
MPLS TE and multiple interfaces
I desire to use MPLS TE.
Two STM1 links connect my PE routers to my P routers.
When two POS interfaces are not included in the POS channel, and I wish to reserve 200 Mbps for my TE tunnel, RSVP will notice that there is not enough BW even if there are 300 Mbps available BE and 150 for each STM1 link.
Now that my OSR routers do not support pos-channel, Here is the solution.
From the source to the destination, the MPLS-TE tunnel can be set up to employ various path options, allowing it to select the path it requires in the order of preference. Using the data in the topology table and the specified constraints, paths can be explicitly configured or dynamically established. You can configure the path options by using the tunnel MPLS traffic-eng path-option command in the tunnel interface. Specify the path to be utilized by running the IP explicit-path command in global configuration mode if any explicit path configuration is involved.
What is the best Approach to MPLS Te With Multiple Interfaces Between Routers?
The best approach might be splitting the traffic between two tunnels, each having a 100Mbps reservation on both POS physical links.
You might need to experiment with each tunnel’s link option.
“As you indicated, OSR routers do not support POC-channel,”