Cisco Cisco Packet Data Gateway (PDG) Manual De Manutenção
Generally Available 06-30-2010
Common Features in Release 9.0
1-3
Common Features in Release 9.0
This section provides information on new features that are common to products in Release
9.0.
9.0.
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).
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).
Description
In deployment 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 label and avoids configuration of VRFs on
PE, which are already configured on MPLS-CE.
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 label 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.
Protocol Lable Switching chapter in System Enhanced Feature Configuration Guide.
License Keys
Requires separate license key.
Side-by-side Redundancy for the 10 Gig Line Card (XGLC)
Starent chassis provides the redundancy scheme for using top and bottom line card slots for
one-to-one redundancy for line cards with top and bottom line card slot for one-to-one
redundancy.
one-to-one redundancy for line cards with top and bottom line card slot for one-to-one
redundancy.
The XGLC is a full-height card that requires both top and bottom line card slots for a single
10-gigabit port. This means that the scheme for using top and bottom line card slots for
one-to-one redundancy is not workable for XGLCs. To achieve one-to-one line card
redundancy, user must install two XGLCs in adjacent slots. Otherwise, user can configure
port and card redundancy for the XGLCs in the same way as other line cards. There are no
restrictions that prevent the side-to-side 1:1 XGLC redundant arrangement from functioning
with other Ethernet line card types.
10-gigabit port. This means that the scheme for using top and bottom line card slots for
one-to-one redundancy is not workable for XGLCs. To achieve one-to-one line card
redundancy, user must install two XGLCs in adjacent slots. Otherwise, user can configure
port and card redundancy for the XGLCs in the same way as other line cards. There are no
restrictions that prevent the side-to-side 1:1 XGLC redundant arrangement from functioning
with other Ethernet line card types.
Each PSC or PSC2 is mated to a single XGLC. Monitoring functions occur in a distributed
fashion. Select the line cards that act as a redundant pair via the CLI. Configure the
fashion. Select the line cards that act as a redundant pair via the CLI. Configure the