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 Static Subscribers

To enable MLPPP over LT2P network server (LNS) support for MX Series, you must indicate whether MLPPP is supported for static subscribers from a particular L2TP client (LAC) by configuring the multilink statement currently supported in access profile. Access profiles define how to validate Layer 2 Tunneling Protocol (L2TP) connections and session requests. Within each L2TP access profile, you configure one or more clients (LACs). You can configure multiple access profiles and multiple clients within each profile.

With mixed mode support, the multilink statement enables MLPPP but does not set it. However, if you do not configure the multilink statement, MLPPP is not supported for static LAC subscribers.

The following two examples show L2TP access profile configurations for an MLPPP-capable static L2TP client and non-multilink (single link) static L2TP client.

To configure an L2TP access profile for MLPPP-capable static L2TP clients:

  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 LNS to renegotiate the link control protocol (LCP) with the PPP client.
  5. Configure the maximum number of sessions allowed in a tunnel from the client (LAC).
  6. Configure the tunnel password used to authenticate the client (LAC).
  7. (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.
  8. Specify that the L2TP client is MLPPP-capable for static subscribers.

MLPPP is first negotiated with static subscribers coming from the LAC peer group profile, ce-lac-1-gp, but then switches to PPP if the subscriber rejects MLPPP. The following shows sample output for MLPPP-capable static L2TP client:

To configure an L2TP access profile for non-MLPPP, or single link static L2TP clients, repeat Step 1 through Step 7 for configuring an L2TP access profile for multilink-capable static L2TP clients. Do not set l2tp multilink.

Only PPP is negotiated with static subscribers from the LAC peer group profile, ce-lac-2-gp, and an LCP configuration request from the customer premises equipment (CPE) with maximum received reconstructed unit (MRRU) option is rejected. The following shows sample output for single link static L2TP client: