Restrictions For Mpls-Te Automatic Bandwidth; Point-To-Multipoint Traffic-Engineering; Point-To-Multipoint Traffic-Engineering Overview - Cisco ASR 9000 Series Configuration Manual

Point-to-Multipoint Traffic-Engineering

Restrictions for MPLS-TE Automatic Bandwidth

When the automatic bandwidth cannot update the tunnel bandwidth, the following restrictions are listed:
• Tunnel is in a fast reroute (FRR) backup, active, or path protect active state. This occurs because of the
• Reoptimization fails to occur during a lockdown. In this case, the automatic bandwidth does not update
Point-to-Multipoint Traffic-Engineering

Point-to-Multipoint Traffic-Engineering Overview

The Point-to-Multipoint (P2MP) Resource Reservation Protocol-Traffic Engineering (RSVP-TE) solution
allows service providers to implement IP multicast applications, such as IPTV and real-time video, broadcast
over the MPLS label switch network. The RSVP-TE protocol is extended to signal point-to-point (P2P) and
P2MP label switched paths (LSPs) across the MPLS networks.
By using RSVP-TE extensions as defined in RFC 4875, multiple subLSPs are signaled for a given TE source.
The P2MP tunnel is considered as a set of Source-to-Leaf (S2L) subLSPs that connect the TE source to
multiple leaf Provider Edge (PE) nodes.
At the TE source, the ingress point of the P2MP-TE tunnel, IP multicast traffic is encapsulated with a unique
MPLS label, which is associated with the P2MP-TE tunnel. The traffic continues to be label-switched in the
P2MP tree. If needed, the labeled packet is replicated at branch nodes along the P2MP tree. When the labeled
packet reaches the egress leaf (PE) node, the MPLS label is removed and forwarded onto the IP multicast tree
across the PE-CE link.
To enable end-to-end IP multicast connectivity, RSVP is used in the MPLS-core for P2MP-TE signaling and
PIM is used for PE-CE link signaling.
• All edge routers are running PIM-SSM or Source-Specific Multicast (SSM) to exchange multicast routing
• In the MPLS network, RSVP P2MP-TE replaces PIM as the tree building mechanism, RSVP-TE grafts
These are the definitions for Point-to-Multipoint (P2MP) tunnels:
Source
Mid-point
Cisco ASR 9000 Series Aggregation Services Router MPLS Configuration Guide, Release 4.3.x
140
assumption that protection is a temporary state, and there is no need to reserve the bandwidth on a backup
tunnel. You should prevent taking away the bandwidth from other primary or backup tunnels.
the bandwidth unless the bandwidth application is manually triggered by using the mpls traffic-eng
auto-bw apply command in EXEC mode.
information with the directly-connected Customer Edge (CE) routers.
or prunes a given P2MP tree when the end-points are added or removed in the TE source configuration
(explicit user operation).
Configures the node in which Label Switched Path (LSP) signaling is initiated.
Specifies the transit node in which LSP signaling is processed (for example, not a source or receiver).
Implementing MPLS Traffic Engineering
OL-28381-02