Configuring an L2TP LNS with Inline Service Interfaces
In addition to performing the specific LNS configuration procedure that follows, you must also configure a RADIUS server and optionally configure an address pool on the local routing instance to be used by RADIUS to assign addresses to PPP subscribers at login.
The L2TP LNS feature license must be installed before you begin the configuration. Else, a warning message is displayed when the configuration is committed.
To configure an L2TP LNS with inline service interfaces:
- (Optional) Configure a user group profile that defines
the PPP configuration for tunnel subscribers.
See Applying PPP Attributes to L2TP LNS Subscribers with a User Group Profile.
- (Optional) Configure PPP attributes for subscribers on
inline service interfaces.
See Applying PPP Attributes to L2TP LNS Subscribers Per Inline Service Interface.
- Configure an L2TP access profile that defines the L2TP parameters for each LNS client (LAC).
- (Optional) Configure a AAA access profile to override the access profile configured under the routing instance.
- Configure a pool of addresses to be dynamically assigned
to tunneled PPP subscribers.
See Configuring an Address-Assignment Pool for L2TP LNS with Inline Services.
- Configure the peer interface to terminate the tunnel and the PPP server-side IPCP address.
- Enable inline service interfaces on an MPC.
- Configure a service interface.
- Configure options for each inline service logical interface.
See Configuring Options for the LNS Inline Services Logical Interface.
- Configure the L2TP tunnel group.
See Configuring an L2TP Tunnel Group for LNS Sessions with Inline Services Interfaces.
- (Optional) Configure a dynamic profile that dynamically creates L2TP logical interfaces.
- (Optional) Configure a service interface pool for dynamic
LNS sessions.
See Configuring a Pool of Inline Services Interfaces for Dynamic LNS Sessions.
- (Optional) Specify how many times L2TP retransmits unacknowledged
control messages.
See Configuring the Number of L2TP Control Message Retransmissions.
- (Optional) Specify how long a tunnel can remain idle before being torn down.
- (Optional) Specify how long the L2TP retains information about terminated dynamic tunnels, sessions, and destinations.
- (Optional) Configure trace options for troubleshooting the configuration.
You also need to configure CoS for LNS sessions. For more information, see Configuring Dynamic CoS for an L2TP LNS Inline Service.
