L2TP Services Configuration Overview

The statements for configuring L2TP services are found at the following hierarchy levels:

• [edit services l2tp tunnel-group group-name]

  The L2TP tunnel-group statement identifies an L2TP instance or L2TP server. Associated statements specify the local gateway address on which incoming tunnels and sessions are accepted, the Adaptive Services (AS) Physical Interface Card (PIC) that processes data for the sessions in this tunnel group, references to L2TP and PPP access profiles, and other attributes for configuring window sizes and timer values.

• [edit interfaces sp-fpc/pic/port unit logical-unit-number dial-options]

  The dial-options statement includes configuration for the l2tp-interface-id statement and the shared/dedicated flag. The interface identifier associates a user session with a logical interface. Sessions can use either shared or dedicated logical interfaces. To run routing protocols, a session must use a dedicated logical interface.

• [edit access profile profile-name client name l2tp]

  Tunnel profiles are defined at the [edit access] hierarchy level. Tunnel clients are defined with authentication, multilink negotiation and fragmentation, and other L2TP attributes in these profiles.

• [edit access profile profile-name client name ppp]

  User profiles are defined at the [edit access] hierarchy level. User clients are defined with authentication and other PPP attributes in these profiles. These client profiles are used when local authentication is specified.

• [edit access radius-server address]

  When you configure authentication-order radius at the [edit access profile profile-name] hierarchy level, you must configure a RADIUS service at the [edit access radius-server] hierarchy level.

Note: For more information about configuring properties at the [edit access] hierarchy level, see the Junos System Basics Configuration Guide.