In this case, each subscriber connection consumes two logical interfaces: one
for the VLAN logical interface and one for the pp0 logical interface.
The M120, M320, and MX Series routers support a maximum of 2000 different
dynamic profiles per chassis. [
Subscriber Access
]
■
Support for dynamic CoS for subscriber interfaces on Trio MPC/MIC interfaces
(MX Series routers)
—Enables you to configure dynamic CoS for subscriber
interfaces on Trio MPC/MIC interfaces that are now available on MX Series routers.
In earlier releases, dynamic CoS was supported on EQ DPCs only.
To configure dynamic CoS on Trio MPC/MIC interfaces, you must enable the
hierarchical scheduler for an interface at the
[edit interfaces]
hierarchy level. You
can then configure dynamic CoS parameters at the
[edit dynamic-profiles
profile-name
class-of-service]
hierarchy level. The CoS parameters are dynamically
applied to subscriber’s services when they log in or change services.
Trio MPC/MIC interfaces support CoS for the following interface types: static
VLAN, demux, static and dynamic PPPoE, and aggregated Ethernet subscriber
interfaces.
In this release, hierarchical CoS for aggregated Ethernet interfaces is supported
on the Trio MPC/MIC product when a static VLAN configured over the aggregated
Ethernet interface. It is not supported for static or dynamic demux subscriber
interfaces configured over aggregated Ethernet.
[
Subscriber Access
]
■
Support for CoS on dynamic PPPoE subscriber interfaces (MX Series
routers)
—Enables you to configure CoS for dynamic PPPoE subscriber interfaces
on Trio MPC/MIC interfaces available on MX Series routers and the Intelligent
Queuing 2 (IQ2) PIC on M120 and M320 Series routers.
In earlier releases, only static CoS was supported for static PPPoE subscriber
interfaces configured on IQ2 PICs on M120 and M320 Series routers.
To configure CoS for a dynamic PPPoE interface, configure the shaping and
scheduling parameters at the
[edit dynamic-profiles
profile-name
class-of-service]
hierarchy level. You then attach the traffic control profile to the dynamic PPPoE
interface by including the
output-traffic-control-profile
profile-name
statement at
the
[edit dynamic-profiles
profile-name
class-of-service interfaces
$junos-interface-ifd-name unit $junos-underlying-interface-unit]
hierarchy level.
When the subscriber logs in, PPP supplies
pp0
as the
$junos-interface-ifd-name
variable, and supplies the PPPoE logical interface number for the
$junos-underlying-interface-unit
variable.
[
Subscriber Access
]
■
Support for IPv6 for dynamic subscriber services (MX Series routers)
—Enables
you to configure IPv6 addressing and prefixes for dynamic subscriber services.
In earlier releases, dynamic subscriber services supported IPv4 addressing only.
You can now configure both IPv4 and IPv6 addressing in the same dynamic
profile to grant access and services to IPv4 and IPv6 subscribers.
In this release, IPv6 addressing is supported for static and dynamic VLAN
subscriber interfaces and dynamic demux subscriber interfaces.
New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
■
29
New Features in JUNOS Release 10.1 for M Series, MX Series, and T Series Routers
