Juniper JUNOS OS 10.4 - RELEASE NOTES REV 5 Release Note page 48

JUNOS OS 10.4 Release Notes
48
configuration. Failure to include the
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
[edit interfaces pp0 unit logical-unit-number]
logical-systems logical-system-name interfaces pp0 unit logical-unit-number]
level. At a minimum, the
pppoe-options
PPPoE underlying interface and the
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
interfaces pp0 unit "$junos-interface-unit"]
subhierarchy must include the name of the underlying Ethernet interface,
pppoe-options
represented by the
$junos-underlying-interface
server statement. For example:
[edit]
dynamic-profiles {
pppoe-profile {
interfaces {
pp0 {
unit "$junos-interface-unit" {
pppoe-options {
underlying-interface "$junos-underlying-interface";
server;
}
...
}
}
}
}
subhierarchy causes the commit
pppoe-options
pppoe-options
hierarchy level or at the
subhierarchy must include the name of the
statement, which configures the router to
server
subhierarchy at the
[edit dynamic-profiles profile-name
hierarchy level. At a minimum, the
predefined dynamic variable, and the
Copyright © 2011, Juniper Networks, Inc.
subhierarchy at the
[edit
hierarchy