EasyManua.ls Logo

Juniper JUNOS OS 10.4 - RELEASE NOTES - Page 45

Juniper JUNOS OS 10.4 - RELEASE NOTES
197 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Subscriber management supports DSL Forum VSAs in pass-through mode. In
pass-through mode, the router does not process DSL values, but rather passes the
values received from the subscriber to the RADIUS server, without performing any
parsing or manipulation.
[Subscriber Access]
Required pppoe-options subhierarchy for configuring static and dynamic PPPoE
interfaces (M120, M320, MX Series routers)When you configure a static or dynamic
pp0 (PPPoE) logical interface, you must include the pppoe-options subhierarchy in the
configuration. Failure to include the pppoe-options subhierarchy causes the commit
operation to fail.
This requirement is in effect for configuration of static PPPoE logical interfaces as of
Junos OS Release 10.2 and later, and has always been in effect for configuration of
dynamic PPPoE subscriber interfaces in a PPPoE dynamic profile. For example, the
following configuration now causes the commit operation to fail for both static and
dynamic PPPoE logical interfaces:
pp0 {
unit 0 {
}
To configure a static PPPoE logical interface in Junos OS Release 10.2 and
higher-numbered releases, you must include the pppoe-options subhierarchy at the
[edit interfaces pp0 unit logical-unit-number] hierarchy level or at the [edit
logical-systems logical-system-name interfaces pp0 unit logical-unit-number] hierarchy
level. At a minimum, the pppoe-options subhierarchy must include the name of the
PPPoE underlying interface and the server statement, which configures the router to
act as a PPPoE server. For example:
[edit interfaces]
...
pp0 {
unit 0 {
pppoe-options {
underlying-interface ge-1/0/0.0;
server;
}
...
}
}
To configure a dynamic PPPoE subscriber interface in a PPPoE dynamic profile, you
must include the pppoe-options subhierarchy at the [edit dynamic-profiles profile-name
interfaces pp0 unit “$junos-interface-unit”] hierarchy level. At a minimum, the
pppoe-options subhierarchy must include the name of the underlying Ethernet interface,
represented by the $junos-underlying-interface predefined dynamic variable, and the
server statement. For example:
[edit]
dynamic-profiles {
pppoe-profile {
interfaces {
pp0 {
45Copyright © 2010, Juniper Networks, Inc.
Changes in Default Behavior and Syntax in Junos OS Release 10.4 for M Series, MX Series, and T Series Routers

Table of Contents

Related product manuals