Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation

Supported Platforms

Configuring an Underlying Interface for Dynamic PPPoE Subscriber Interfaces

After you configure a dynamic profile to define the attributes of a dynamic PPPoE subscriber interface, you must attach the dynamic profile to a statically created underlying Ethernet interface configured with PPPoE (ppp-over-ether) encapsulation. You configure the underlying interface at the [edit interfaces interface-name unit logical-unit-number pppoe-underlying-options] hierarchy level.

In addition to attaching the dynamic profile to the interface by using the required dynamic-profile statement, you can also configure the underlying interface with one or more of the following optional PPPoE-specific attributes:

  • Prevention of another dynamic PPPoE logical interface from being activated on the underlying interface when a PPPoE logical interface for a client with the same MAC address is already active on that interface (duplicate-protection)
  • Maximum number of dynamic PPPoE logical interfaces (sessions) that the router can activate on the underlying interface on a per-interface basis (using the max-sessions statement) or on a per-subscriber basis (using the Max-Clients-Per-Interface Juniper Networks VSA [26-143])
  • Lockout of failed or short-lived (also known as short-cycle) PPPoE subscriber sessions to prevent reconnection to the router for a default or configurable period of time (short-cycle-protection)
  • An alternative access concentrator name in the AC-NAME tag in a PPPoE control packet (access-concentrator)

Before you begin:

  1. Configure the static underlying Ethernet interface on which you want the router to dynamically create the PPPoE logical interface.

    For information about configuring static Ethernet interfaces, see the Junos® OS Network Interfaces.

  2. Configure a PPPoE dynamic profile in either of the following ways:

To configure an underlying Ethernet interface for a dynamic PPPoE subscriber interface:

  1. Specify the name and logical unit number of the static underlying Ethernet interface to which you want to attach the PPPoE dynamic profile.
    [edit]user@host# edit interfaces ge-1/0/1 unit 0
  2. Configure PPPoE encapsulation on the underlying interface.
    [edit interfaces ge-1/0/1 unit 0]user@host# set encapsulation ppp-over-ether
  3. Specify that you want to configure PPPoE-specific options on the underlying interface.
    [edit interfaces ge-1/0/1 unit 0] user@host# edit pppoe-underlying-options
  4. Attach a previously configured PPPoE dynamic profile to the underlying interface.

    The specified PPPoE dynamic profile must already be configured on the router. In addition, you cannot attach a PPPoE dynamic profile to an underlying Ethernet interface that is already associated with static PPPoE logical interfaces. Conversely, you cannot associate static PPPoE logical interfaces with an underlying Ethernet interface that already has a PPPoE dynamic profile attached.

    [edit interfaces ge-1/0/1 unit 0 pppoe-underlying-options] user@host# set dynamic-profile basic-pppoe-profile
  5. (Optional) Enable duplicate protection to prevent activation of another dynamic PPPoE logical interface for the same client on the underlying interface.
    [edit interfaces ge-1/0/1 unit 0 pppoe-underlying-options] user@host# set duplicate-protection
  6. (Optional) Configure the maximum number of concurrent PPPoE sessions that the router can activate on the underlying interface in either of the following ways:
    • To configure the maximum number of concurrent PPPoE sessions on a per-interface basis, from 1 to the platform-specific default for your router, use the max-sessions statement:
      [edit interfaces ge-1/0/1 unit 0 pppoe-underlying-options] user@host# set max-sessions 20
    • To configure the maximum number of concurrent PPPoE sessions on a per-subscriber basis, use the value returned by RADIUS in the Max-Clients-Per-Interface Juniper Networks vendor-specific attribute (VSA) [26-143]. By default, the PPPoE maximum session value returned by RADIUS in the Max-Clients-Per-Interface VSA takes precedence over the PPPoE maximum session value configured with the max-sessions statement.
  7. (Optional) Configure the router to ignore the value returned by RADIUS in the Max-Clients-Per-Interface VSA and restore the PPPoE maximum session value on the underlying interface to the value configured in the CLI with the max-sessions statement.
    [edit interfaces ge-1/0/1 unit 0 pppoe-underlying-options] user@host# set max-sessions-vsa-ignore
  8. (Optional) Enable PPPoE subscriber session lockout on the PPPoE underlying interface in either of the following ways:

    • To configure PPPoE subscriber session lockout with the default lockout period:
      [edit interfaces interface-name unit logical-unit-number pppoe-underlying-options] user@host# set short-cycle-protection
    • To configure PPPoE subscriber session lockout with a nondefault lockout period:
      [edit interfaces interface-name unit logical-unit-number pppoe-underlying-options] user@host# set short-cycle-protection lockout-time-min minimum-seconds lockout-time-max maximum-seconds

    Best Practice: When you configure PPPoE subscriber session lockout, we recommend that you also enable duplicate protection to ensure that the MAC source address for each PPPoE session is unique on the underlying interface.

  9. (Optional) Specify the alternative name for the access concentrator, also known as the PPPoE server.
    [edit interfaces ge-1/0/1 unit 0 pppoe-underlying-options] user@host# set access-concentrator server-east

Published: 2013-02-11

Supported Platforms

Published: 2013-02-11