}
}
}
The statements at the
[edit interfaces
interface-name
unit
logical-unit-number
pppoe-underlying-options]
hierarchy level define the following PPPoE-specific
attributes for the underlying interface:
■
To provide an alternative access concentrator (AC) name in the AC-NAME
tag in a PPPoE control packet, include the
access-concentrator
statement.
■
To assign a previously configured dynamic profile to the underlying
interface, include the
dynamic-profile
statement. This is the only required
statement for configuring dynamic PPPoE interfaces at the
[edit interfaces
interface-name
unit
logical-unit-number
pppoe-underlying-options]
hierarchy
level.
■
To prevent the activation of another dynamic PPPoE logical interface
on the same underlying interface on which a dynamic PPPoE logical
interface is already active for the same client, include the
duplicate-protection
statement.
■
To configure the maximum number of dynamic PPPoE logical interfaces
(sessions) that the router can activate on the underlying interface, include
the
max-sessions
statement.
To display information about the dynamic PPPoE interface configuration, use
the
show pppoe underlying-interfaces
,
show pppoe statistics
, and
show pppoe
interfaces
operational commands. You can also use the
clear pppoe statistics
command to clear packet statistics on the underlying interface.
[
Subscriber Access
]
■
Support for PPPoE Layer 3 wholesale configuration in a subscriber access
network
—Enables you to configure PPPoE Layer 3 wholesaling within a
subscriber access network. Wholesale access is the process by which an access
network provider partitions the access network into separately manageable and
accountable subscriber segments for resale to other network providers. An access
network provider may elect to wholesale all or part of its network to one or more
service providers (retailers).
In a Juniper Networks subscriber access network, you accomplish Layer 3
partitioning through the use of logical systems (LSs) and routing instances. Logical
systems enable you to divide a physical router into separate, distinct, logical
administrative domains. This method of division enables multiple providers to
administer the router simultaneously and each have access to only the portions
of the configuration that are relevant to their specific logical system. The JUNOS
Software supports up to 15 named logical systems in addition to the default
logical system (inet.0).
Routing instances are typically used in Layer 3 VPN scenarios. A routing instance
does not have the same level of administrative separation as does a logical
system. The routing instance defines a distinct routing table, set of routing
policies, and set of interfaces, but it does not provide administrative isolation.
New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
■
33
New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
