Cisco Cisco Packet Data Gateway (PDG) Guia De Resolução De Problemas
MultiProtocol Label Switching (MPLS) Support
▀ Overview
▄ Cisco ASR 5000 Series Enhanced Feature Configuration Guide
OL-22982-01
Overview
As seen in the following scenario, the chassis can be deployed as a router while supporting MPLS in a network.
Chassis as MPLS-Customer Edge (MPLS-CE) with Provider Edge (PE)
Chassis as MPLS-CE with PE
Figure 41. Chassis as MPLS-CE with PE
The system in this scenario uses static MPLS labels for ingress and egress traffic. For configuration information on
static label, refer to the
static label, refer to the
The system is in a separate autonomous system (AS) from the Provider Edge (PE). It communicates with the PE and
routes for all VPNs supported on the PE that are exchanged with the system. Routes belonging to different VPNs are
logically separated, using separate virtual route forwarding tables (VRFs).
routes for all VPNs supported on the PE that are exchanged with the system. Routes belonging to different VPNs are
logically separated, using separate virtual route forwarding tables (VRFs).
Routes for each VPN are advertised as VPN-IPv4 routes, where route distinguishers are prepended to regular IPv4
routes to allow them to be unique within the routing table. Route targets added to the BGP extended community
attributes identify different VPN address spaces. The particular upstream BGP peer routing domain (VPN), from which
a route is to be imported by the downstream peer into an appropriate VRF, is identified with an extended community in
the advertised NLRI, which is in fact an MPLS label.
routes to allow them to be unique within the routing table. Route targets added to the BGP extended community
attributes identify different VPN address spaces. The particular upstream BGP peer routing domain (VPN), from which
a route is to be imported by the downstream peer into an appropriate VRF, is identified with an extended community in
the advertised NLRI, which is in fact an MPLS label.
The Customer Edge (CE) also advertises routes to the PE using NLRIs that include route distinguishers to differentiate
VPNs, and extended community MPLS labels to identify VRFs.
VPNs, and extended community MPLS labels to identify VRFs.