MPLS-TE Features - Details
The following figure illustrates PBTS Network Topology:
Figure 11: Policy-Based Tunnel Selection Implementation
• Tunnels are created between Ingress and Egress nodes through LSR 1-2 and LSR 1-3-4-2 paths.
• High priority traffic takes the path: Ingress->LSR1->LSR2->Egress.
• Low priority traffic takes the path: Ingress->LSR1->LSR3->LSR4->LSR2->Egress
PBTS Function Details
The following PBTS functions are supported on the Cisco NCS 5500 Series Routers:
• Classify the Ingress traffic into different classes by creating rules using PBR configuration.
• Classify packets using DSCP/IP precedence for both IPv4 and IPv6 traffic.
• After classification, set the desired forward-class to each type of Ingress traffic.
• Define one or many MPLS-TE tunnels in the destination using Tunnel configuration.
• Associate the MPLS-TE tunnels to a specific forward-class under Tunnel configuration.
• Enable PBTS on the Ingress interface by applying the service policy that uses the configured classification
rules.
The following list gives PBTS support information:
• PBTS is supported only on Ipv4/Ipv6 incoming traffic only.
• A maximum of eight forward-classes per destination prefix is supported.
• A maximum of 64 TE-tunnels within each forward class is supported.
• A maximum of 64 TE-tunnels can be configured on a given destination.
• Incoming labeled traffic is not supported.
• PBTS with L2VPN/L3VPN traffic is not supported.
MPLS Configuration Guide for Cisco NCS 5500 Series Routers, IOS XR Release 6.2.x
56
Implementing MPLS Traffic Engineering