Limiting the Maximum Number of PPPoE Sessions on the Underlying Interface
You can limit the number of concurrent static or dynamic PPPoE logical interfaces (sessions) that the router can activate on the PPPoE underlying interface, or the number of active static or dynamic PPPoE sessions that the router can establish with a particular service entry in a PPPoE service name table.
To configure the PPPoE maximum session limit:
- Specify that you want to configure PPPoE-specific options
on the underlying interface:
For a PPPoE family in a dynamic profile for a VLAN demultiplexing (demux) logical interface:
[edit dynamic-profiles profile-name interfaces demux0 unit logical-unit-number] user@host# edit family pppoe
For a PPPoE family in a dynamic profile:
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number] user@host# edit family pppoe
For a PPPoE underlying interface in a dynamic profile:
[edit dynamic-profiles profile-name interfaces interface-name unit logical-unit-number] user@host# edit pppoe-underlying-options
For a PPPoE family on an underlying interface:
[edit interfaces interface-name unit logical-unit-number] user@host# edit family pppoe
For an underlying interface with PPPoE encapsulation:
[edit interfaces interface-name unit logical-unit-number] user@host# edit pppoe-underlying-options
For an underlying interface established with a particular service entry in a PPPoE service name table:
[edit protocols pppoe service-name-tables table-name] user@host# edit service service-name
- 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-sessionsstatement:[edit interfaces interface-name unit logical-unit-number pppoe-underlying-options] 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-sessionsstatement.
- (Optional) To restore the PPPoE maximum session value
on the underlying interface to the value configured in the CLI with
the
max-sessionsstatement, configure the router to ignore the value returned by RADIUS in the Max-Clients-Per-Interface VSA.[edit interfaces interface-name unit logical-unit-number pppoe-underlying-options] user@host# set max-sessions-vsa-ignore
Note:You can issue the
max-sessions-vsa-ignorestatement at the same hierarchy levels as themax-sessionsstatement, with the exception of the[edit protocols pppoe service-name-tables table-name service service-name]hierarchy level.