Juniper JUNOS 10.1 - RELEASE NOTES REV 4 Release Note page 34

JUNOS 10.1 Software Release Notes
34
New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
When configuring PPPoE Layer 3 wholesale for a subscriber access network,
keep the following in mind:
PPPoE Layer 3 wholesaling supports the use of only the default logical system
using multiple routing instances.
Each routing instance must contain a loopback with one or more addresses
to be used for the unnumbered interface. However, unlike configuring Layer
3 wholesale for DHCP, the loopback interface address does not have to be
within the same subnetwork as the client IP address.
The system ignores the
statement when it is configured. To avoid confusion,
unnumbered-address
we recommend that you do not configure the
for the
unnumbered-address
interface. However, the system will function appropriately, regardless of
whether or not you have configured the
To configure PPPoE Layer 3 wholesale for a subscriber access network:
Include the
routing-instances
dynamic variable at the
Include the statement along with the
interface
variable at the [edit dynamic-profiles profile-name routing-instances
"$junos-routing-instance"]
Include the unnumbered-address
dynamic variable at the
"$junos-interface-unit" family inet]
To view the logical system and routing instance for each subscriber, use the
operational command.
subscriber
[Subscriber Access, Broadband Subscriber Management]
PPP PAP and CHAP enhancements for subscriber management (M120 and
M320 routers) Subscriber management supports both bidirectional and
unidirectional PPP PAP and CHAP authentication.
In subscriber management, the router's PPP interface typically authenticates the
remote client (the subscriber). Bidirectional authentication is not usually used in
a subscriber management environment, even though it is supported for static
interfaces. Also, subscriber management uses AAA to authenticate subscribers,
which removes the need to specify an access profile or a default password for
PAP or CHAP authentication.
For static interfaces, the router supports bidirectional authentication. If you
do not include the
passive
as the authenticator for remote clients. If you include the
the router is authenticated by the remote client. Also, when you specify the
statement for static interfaces, you must specify other attributes, as
passive
described in the JUNOS Network Interfaces Guide.
For dynamic interfaces, the router supports unidirectional authentication
only the router always functions as the authenticator. When you configure
PPP authentication in a dynamic profile (at the
preferred-source-address option for the
preferred-source-address
statement when configuring an unnumbered
preferred-source-address
statement along with the
[edit dynamic-profiles profile-name]
$junos-interface-name
hierarchy level.
statement along with
[edit dynamic-profiles profile-name interfaces pp0 unit
hierarchy level.
statement in the configuration, the router functions
[edit dynamic-profiles]
option
option.
$junos-routing-instance
hierarchy level.
dynamic
$junos-loopback-interface
show
passive statement,
hierarchy