Cisco Cisco Packet Data Interworking Function (PDIF) Guía Para Resolver Problemas
MultiProtocol Label Switching (MPLS) Support
Overview ▀
Cisco ASR 5000 Series Enhanced Feature Configuration Guide ▄
OL-22983-01
There is a single MPLS-capable link between the CE and the PE. MP-BGP communicates across this link as a TCP
session over IP. Data packets are sent bidirectionally as MPLS encapsulated packets.
session over IP. Data packets are sent bidirectionally as MPLS encapsulated packets.
This solution does not use any MPLS routing protocols. The MPLS label corresponding to the immediate upstream
neighbor is statically configured on the downstream router, and similarly in the reverse direction.
neighbor is statically configured on the downstream router, and similarly in the reverse direction.
When forwarding subscriber packets in the upstream direction to the PE, the CE encapsulates packets with MPLS
headers that identify the upstream VRF (the label sent as an extended community with the NLRI) and the immediate
next hop. When the PE receives a packet it switches the label to an MPLS-labeled packet.
headers that identify the upstream VRF (the label sent as an extended community with the NLRI) and the immediate
next hop. When the PE receives a packet it switches the label to an MPLS-labeled packet.
The CE does not run any MPLS routing protocol (LDP or RSVP-TE).
When receiving data packets in the downstream direction from the PE, the label is checked to identify the destination
VRF. Then the packet is de-encapsulated into an IP packet and sent to the session subsystem for processing.
VRF. Then the packet is de-encapsulated into an IP packet and sent to the session subsystem for processing.
Important:
MPLS ping/trace route debugging facilities are not supported.
Chassis as MPLS-CE with ASBR
Figure 42. Chassis as MPLS-CE with ASBR