Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Configuring L2TP Client Access to Support MLPPP for Dynamic Subscribers

 

To enable support for MLPPP over LT2P network server (LNS) you configure the family mlppp statement in the dynamic profile name, which indicates that MLPPP is supported for dynamic subscribers from a particular L2TP client (LAC).

Note

The multilink statement used to enable MLPPP for static LNS subscribers is ignored for dynamic LNS subscribers if it is configured.

You can configure a dynamic profile name for the LAC using access profile from the l2tp statement. If you specify a dynamic profile name in the L2TP client access profile, it overrides the dynamic-profile name specified in the tunnel-group used to create the dynamic subscriber interface. If you do not configure a dynamic profile name in the L2TP client access profile, then the dynamic-profile name specified in the tunnel-group is used.

The following example shows an L2TP access profile configuration with a dynamic profile name for dynamic LNS subscribers.

To configure an L2TP access profile configuration with a dynamic profile name for dynamic LNS subscribers:

  1. Create the access profile.
  2. Configure characteristics for one or more clients (LACs).
  3. Associate a group profile containing PPP attributes to apply for the PPP sessions being tunneled from this LAC client.
  4. Configure the maximum number of sessions allowed in a tunnel from the client (LAC).
  5. Configure the tunnel password used to authenticate the client (LAC).
  6. (Optional) Specify a local access profile that overrides the global access profile and the tunnel group AAA access profile to configure RADIUS server settings for the client.
  7. Specify the dynamic profile name for the dynamic LNS subscriber.

If the family mlppp statement is configured in dynamic-profile, MLPPP is negotiated first; otherwise, only PPP is negotiated. The following shows sample output for an L2TP access profile configuration with a dynamic profile name for dynamic LNS subscribers: