Cisco Cisco Packet Data Gateway (PDG) Fehlerbehebungsanleitung
L2TP Network Server
▀ LNS Service Operation
▄ Cisco ASR 5000 Series Enhanced Feature Configuration Guide
OL-22983-01
In this configuration, the LNS service in the source context terminates L2TP tunnels from peer LACs and routes the
subscriber session data through the destination context to and from a packet data network such as the Internet or a home
network.
subscriber session data through the destination context to and from a packet data network such as the Internet or a home
network.
Information Required
Prior to configuring the system as shown in figure above, a minimum amount of information is required. The following
sections describe the information required to configure the source and destination contexts.
sections describe the information required to configure the source and destination contexts.
Source Context Configuration
The following table lists the information that is required to configure the source context.
Table 28. Required Information for Source Context Configuration
Required Information
Description
Source context name
This is an identification string between 1 and 79 characters (alpha and/or numeric) by which the source
context will be recognized by the system.
context will be recognized by the system.
PDN Interface Configuration
PDN interface name
This is an identification string between 1 and 79 characters (alpha and/or numeric) by which the
interface will be recognized by the system.
Multiple names are needed if multiple interfaces will be configured.
These PDN interfaces facilitates the L2TP tunnels/sessions from the LAC and are configured in the
source context.
interface will be recognized by the system.
Multiple names are needed if multiple interfaces will be configured.
These PDN interfaces facilitates the L2TP tunnels/sessions from the LAC and are configured in the
source context.
IP address and subnet
These will be assigned to the PDN interface.
Multiple addresses and/or subnets are needed if multiple interfaces will be configured.
Multiple addresses and/or subnets are needed if multiple interfaces will be configured.
Physical port number
This specifies the physical port to which the interface will be bound. Ports are identified by the chassis
slot number where the line card resides in, followed by the number of the physical connector on the line
card. For example, port 17/1 identifies connector number 1 on the card in slot 17.
A single physical port can facilitate multiple interfaces.
slot number where the line card resides in, followed by the number of the physical connector on the line
card. For example, port 17/1 identifies connector number 1 on the card in slot 17.
A single physical port can facilitate multiple interfaces.
Physical port
description
description
This is an identification string between 1 and 79 characters (alpha and/or numeric) by which the physical
port will be recognized by the system.
Multiple descriptions are needed if multiple ports will be used.
Physical ports are configured within the source context and are used to bind logical PDN interfaces.
port will be recognized by the system.
Multiple descriptions are needed if multiple ports will be used.
Physical ports are configured within the source context and are used to bind logical PDN interfaces.
Gateway IP address
Used when configuring static routes from the PDN interface(s) to a specific network.
LNS service Configuration
LNS service name
This is an identification string between 1 and 63 characters (alpha and/or numeric) by which the LNS
service will be recognized by the system.
Multiple names are needed if multiple LNS services will be used.
LNS services are configured in the source context.
service will be recognized by the system.
Multiple names are needed if multiple LNS services will be used.
LNS services are configured in the source context.