Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Configuring the PPPoE Family for an Underlying Interface

You can configure the PPPoE family on an underlying interface as an alternative to configuring PPPoE encapsulation on that interface. You cannot configure both on the same interface. You can configure the same attributes for the PPPoE family as you can for an interface configured with pppoe-underlying-options.

Before you begin, configure the underlying interface. When you want to configure PPPoE on an aggregated Ethernet bundle, you must configure the PPPoE family over a VLAN demux interface as an intermediate underlying option. The VLAN demux interface can be static or dynamic.

• Configuring a Subscriber Interface with a Static VLAN Interface
• Configuring Static Subscriber Interfaces Using VLAN Demux Interfaces
• Configuring Dynamic Subscriber Interfaces Using VLAN Demux Interfaces in Dynamic Profiles

1. Specify the PPPoE family.
   [edit interfaces demux0 unit logical-unit-number]user@host# set family pppoe
2. (Optional) Configure an alternative access concentrator name to be used instead of the system name in PPPoE control packets for the dynamic PPPoE subscriber interface.
   [edit interfaces demux0 unit logical-unit-number family pppoe]user@host# set access-concentrator name
3. (Optional) Configure duplicate protection to prevent the activation of another dynamic PPPoE logical interface on the same underlying interface when a dynamic PPPoE logical interface for a client with the same MAC address is already active on that interface.
   [edit interfaces demux0 unit logical-unit-number family pppoe]user@host# set duplicate-protection
4. (Optional) Attach a dynamic profile to determine the properties of the dynamic PPPoE logical interface when it is created.
   [edit interfaces demux0 unit logical-unit-number family pppoe]user@host# set dynamic-profile profile-name
5. (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 through the platform-specific default for your router, use the max-sessions statement:
     [edit interfaces demux0 unit logical-unit-number family pppoe]user@host# set max-sessions number
   • 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.
6. (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 demux0 unit logical-unit-number family pppoe]user@host# set max-sessions-vsa-ignore

7. (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.

8. (Optional) Specify the service name table assigned to the underlying interface.
   [edit interfaces demux0 unit logical-unit-number family pppoe]user@host# set service-name-table table-name