Cisco Cisco Packet Data Gateway (PDG) Documentation Roadmaps
New In This 8.0 Release
▀ Common Features
▄ Cisco ASR 5000 Series Product Overview
OL-22937-01
Common Features
Configurable Transmit Timing Source
It is now possible to configure the transmit clock source, as either Building Integrated Timing Supply (BITS) or line-
timing, for application services using SDH or SONET over the Optical line card or the Channelized line card.
timing, for application services using SDH or SONET over the Optical line card or the Channelized line card.
BITS-timing provides the transmit timing source, using Stratum 3 compliant BITS modules resident on either the SPIO
with a BITS BNC interface or the SPIO with a BITS 3-pin interface. Line-timing recovers the receive timing from an
external clock source via a port on an Optical or Channelized line card. It is possible to configure both clock sources, so
that one timing source backs up the other.
with a BITS BNC interface or the SPIO with a BITS 3-pin interface. Line-timing recovers the receive timing from an
external clock source via a port on an Optical or Channelized line card. It is possible to configure both clock sources, so
that one timing source backs up the other.
Configuration of this clock source is explained in Configuring Transmit Timing Source in the System Administration
Guide.
Guide.
Domain-based L2TP Tunnel Support
Benefits
This feature enables initiation of new L2TP create tunnel request to same LNS address based on the value of attribute
―Tunnel-Server-Auth-ID‖ in Access-Accept message received from AAA server. This value is treated as a key to
identify tunnel. Thus, effectively, this result in multiple L2TP tunnels based on the value of attribute received from
AAA server by a LAC. This value of attribute is treated as a key to identify tunnel.
―Tunnel-Server-Auth-ID‖ in Access-Accept message received from AAA server. This value is treated as a key to
identify tunnel. Thus, effectively, this result in multiple L2TP tunnels based on the value of attribute received from
AAA server by a LAC. This value of attribute is treated as a key to identify tunnel.
Description
In earlier implementation, LAC chooses to create a new tunnel between LAC and LNS pair only when existing tunnel
has reached its full capacity of allowed L2TP sessions per tunnel. There was no provision to the further segregation of
the traffic between LAC and LNS.
has reached its full capacity of allowed L2TP sessions per tunnel. There was no provision to the further segregation of
the traffic between LAC and LNS.
New CLI command
is added in LAC
service configuration mode to support this feature. This command will provide facility to create new tunnel on the basis
of domain name irrespective of the current capacity of existing tunnels established for different domains.
of domain name irrespective of the current capacity of existing tunnels established for different domains.
The domain name (key to tunnel) is taken from the ―Tunnel-Server-Auth-ID‖ attribute received from AAA server and
when the LAC service needs to establish a new L2TP session, it will first check, if there is already an existing L2TP
tunnel with the peer LNS based on the value of key ―Tunnel-Server-Auth-ID‖ attribute value. If no such tunnel exists
when the LAC service needs to establish a new L2TP session, it will first check, if there is already an existing L2TP
tunnel with the peer LNS based on the value of key ―Tunnel-Server-Auth-ID‖ attribute value. If no such tunnel exists