Juniper JUNOS 10.1 - RELEASE NOTES REV 4 - Page 32

interfaces pp0 {
unit $junos-interface-unit {
keepalives interval seconds;
no-keepalives;
pppoe-options {
underlying-interface "$junos-underlying-interface";
server;
}
ppp-options {
chap;
pap;
}
family inet {
unnumbered-address interface-name;
address address;
service {
input {
service-set service-set-name <service-filter filter-name>;
}
output {
service-set service-set-name <service-filter filter-name>;
}
}
filter {
input filter-name;
output filter-name;
}
}
}
}
}
}
You can use most of these same statements to configure statically created
PPPoE interfaces, with the following important differences. When you
configure a profile to dynamically create a PPPoE interface, you must specify
the $junos-interface-unit predefined dynamic variable instead of the actual
logical unit number for the unit statement, and the $junos-underlying-interface
predefined dynamic variable instead of the actual name of the underlying
interface for the underlying-interface statement.
2. Assign the dynamic profile to the underlying interface on which the router
creates the dynamic PPPoE interface. To do so, include the
pppoe-underlying-options statement at the [edit interfaces interface-name unit
logical-unit-number] hierarchy level, as follows:
interfaces {
interface-name {
unit logical-unit-number {
encapsulation ppp-over-ethernet;
pppoe-underlying-options {
access-concentrator name;
dynamic-profile profile-name;
duplicate-protection;
max-sessions number;
}
32 ■ New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
JUNOS 10.1 Software Release Notes