Cisco MPLS TE (Traffic Engineering) tunnels provide a way to optimize traffic routing within an MPLS network. However, there are certain constraints to be aware of:
QoS-aware tunneling: Unfortunately, Cisco MPLS TE tunnels do not inherently support Quality of Service (QoS) awareness. This means that the tunnels themselves do not directly consider QoS parameters when making routing decisions. QoS policies must be applied separately at the network level, and the TE tunnels do not inherently take QoS into account during path selection.
Tunnels spanning multiple OSPF areas: Contrary to option A, Cisco MPLS TE tunnels can indeed span multiple OSPF areas. The use of OSPF areas does not inherently restrict the creation of MPLS TE tunnels across area boundaries.
ISIS metrics: Option B is incorrect. When using ISIS (Intermediate System to Intermediate System) as the Interior Gateway Protocol (IGP), newer-style metrics (such as wide metrics) are supported. Older-style metrics are not the only option.
Tunnels over IP unnumbered links: Option C is also incorrect. Cisco MPLS TE tunnels can be configured over IP unnumbered links, allowing efficient use of IP addresses.
In summary, the primary constraint is the lack of built-in QoS awareness within MPLS TE tunnels.
References:
Implementing an MPLS VPN over TE Tunnels - Cisco Support
Configuring Basic MPLS TE - Cisco NX-OS
Contribute your Thoughts:
Chosen Answer:
This is a voting comment (?). You can switch to a simple comment. It is better to Upvote an existing comment if you don't have anything to add.
Submit