Cisco Cisco Packet Data Interworking Function (PDIF) Documentation Roadmaps
New In This Release
▀ Common Features
▄ Cisco ASR 5000 Series Product Overview
OL-22937-01
Common Features
Dynamic MPLS Label Support
Benefits
This feature provides dynamic MPLS label support for ingress and egress traffic where system works as MPLS-
Customer Edge system and maintains VRF routes in various VRFs and exchanges route information with peer over MP-
eBGP session with an Autonomous System Border Router (ASBR).
Customer Edge system and maintains VRF routes in various VRFs and exchanges route information with peer over MP-
eBGP session with an Autonomous System Border Router (ASBR).
Description
In depolyment scenario the MPLS-CE system maintains VRF routes in various VRFs and exchanges route information
with peer over MP-eBGP session with peer. The peer in this scenario is not a PE router but an ASBR. The ASBR does
not need to maintain any VRF configuration. The PE routers use IBGP to redistribute labeled VPN-IPv4 routes either to
an Autonomous System Border Router (ASBR), or to a route reflector of which an ASBR is a client. The ASBR then
uses eBGP to redistribute those labeled VPN-IPv4 routes to MPLS-CE in another AS. Because of eBGP connection,
ASBR changes the next-hop and labels in the routes learnt from iBGP peers before advertising to MPLS-CE. MPLS-CE
is directly connected eBGP peering and uses only MP-eBGP to advertise and learn routes. MPLS-CE pushes/pops single
label to/from ASBR, which is learnt over MP-eBGP connection. This scenario uses dynamic MPLS lable and avoids
configuration of VRFs on PE, which are already configured on MPLS-CE.
with peer over MP-eBGP session with peer. The peer in this scenario is not a PE router but an ASBR. The ASBR does
not need to maintain any VRF configuration. The PE routers use IBGP to redistribute labeled VPN-IPv4 routes either to
an Autonomous System Border Router (ASBR), or to a route reflector of which an ASBR is a client. The ASBR then
uses eBGP to redistribute those labeled VPN-IPv4 routes to MPLS-CE in another AS. Because of eBGP connection,
ASBR changes the next-hop and labels in the routes learnt from iBGP peers before advertising to MPLS-CE. MPLS-CE
is directly connected eBGP peering and uses only MP-eBGP to advertise and learn routes. MPLS-CE pushes/pops single
label to/from ASBR, which is learnt over MP-eBGP connection. This scenario uses dynamic MPLS lable and avoids
configuration of VRFs on PE, which are already configured on MPLS-CE.
For more information on functioning and configuration of this interface, refer Multiple Protocol Lable Switching
chapter in System Enhanced Feature Configuration Guide.
chapter in System Enhanced Feature Configuration Guide.
License Keys
Requires separate license key.
PPC Card
The PPC features a quad-core x86 2.5Ghz CPU and 16GB of RAM. The processor runs a single copy of the operating
system. To check the CPU in the CLI, use the show cpu table command. The operating system running on the PPC
treats the dual-core processor as a 2-way multi-processor. You can see this in the output of the show cpu info verbose
command.
system. To check the CPU in the CLI, use the show cpu table command. The operating system running on the PPC
treats the dual-core processor as a 2-way multi-processor. You can see this in the output of the show cpu info verbose
command.