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
preferred-source-address
option for the
unnumbered-address
statement when it is configured. To avoid confusion,
we recommend that you do not configure the
preferred-source-address
option
for the
unnumbered-address
statement when configuring an unnumbered
interface. However, the system will function appropriately, regardless of
whether or not you have configured the
preferred-source-address
option.
To configure PPPoE Layer 3 wholesale for a subscriber access network:
■
Include the
routing-instances
statement along with the
$junos-routing-instance
dynamic variable at the
[edit dynamic-profiles
profile-name
]
hierarchy level.
■
Include the
interface
statement along with the
$junos-interface-name
dynamic
variable at the
[edit dynamic-profiles
profile-name
routing-instances
“$junos-routing-instance”]
hierarchy level.
■
Include the
unnumbered-address
statement along with
$junos-loopback-interface
dynamic variable at the
[edit dynamic-profiles
profile-name
interfaces pp0 unit
“$junos-interface-unit” family inet]
hierarchy level.
To view the logical system and routing instance for each subscriber, use the
show
subscriber
operational command.
[
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
statement in the configuration, the router functions
as the authenticator for remote clients. If you include the
passive
statement,
the router is authenticated by the remote client. Also, when you specify the
passive
statement for static interfaces, you must specify other attributes, as
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
[edit dynamic-profiles]
hierarchy
34
■
New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
JUNOS 10.1 Software Release Notes
