Specifications

underlying interfaces. In earlier Junos OS releases, PPPoE subscriber session lockout
identified and filtered subscriber sessions only by their unique MAC source address.
ACI-based or MAC-based PPPoE subscriber session lockout prevents a failed or
short-lived PPPoE subscriber session from reconnecting to the router for a default or
configurable time period. ACI-based PPPoE subscriber session lockout is useful for
configurations such as PPPoE interworking in which MAC source addresses are not
unique on the PPPoE underlying interface.
To configure ACI-based PPPoE subscriber session lockout, use the short-cycle-protection
statement with the filter aci option. To clear an ACI-based lockout condition, issue the
clear pppoe lockout command with the aci option.
[See PPPoE Subscriber Session Lockout Overview.]
•
Subscriber management and services feature parity (MX80)—Starting in Junos OS
Release 13.3, the MX80 supports all subscriber management and services features
that are supported by the MX240, MX480, and MX960 routers. Previously, the MX80
router matched feature support for these routers as of Junos OS Release 11.4.
[See Protocols and Applications Supported by MX5, MX10, MX40, and MX80 Routers.]
•
Subscriber management and services feature and scaling parity (MX2010 and
MX2020)—Starting in Junos OS Release 13.3, the MX2010 and the MX2020 support
all subscriber management and services features that are supported by the MX240,
MX480, and MX960 routers. In addition, the scaling and performance values for the
MX2010 and the MX2020 match those of MX960 routers.
[See Protocols and Applications Supported by MX240, MX480, MX960, MX2010, and
MX2020 MPCs, Protocols and Applications Supported by MX240, MX480, MX960, MX2010,
and MX2020 Enhanced MPCs (MPCEs), Protocols and Applications Supported by the
MX240, MX480, MX960, MX2010, and MX2020 MPC3E, and Protocols and Applications
Supported by the MX240, MX480, MX960, MX2010, and MX2020 MPC4Es.]
•
Per-subscriber support for multiple instances of the same service with different
parameters (MX Series routers with MPCs or MICs)—Starting In Junos OS Release
13.3, a subscriber can have multiple instances of the same service, provided that each
service instance has a different set of parameters. In earlier Junos OS releases, each
subscriber was limited to only a single instance of each service.
You can configure a specific service instance for a particular subscriber by specifying
a service name and unique service parameters for that instance. Each service instance
is uniquely identified by the combination of its service name and service parameters.
Use the request network-access aaa subscriber delete command to deactivate all
instances of a subscriber service by specifying only the service name, or to deactivate
a specific instance of a service by specifying both the service name and its parameters.
In earlier Junos OS releases, you deactivated a service by specifying only its service
name, but not its service parameters.
[See Subscriber Services with Multiple Instances Overview.]
•
RADIUS accounting messages for dual-stack subscribers (MX Series)—Starting in
Junos OS Release 13.3, when an IPv6 address is assigned using DHCPv6, the RADIUS
interim accounting message includes the assigned IPv6 address. If the delegated prefix
49Copyright © 2015, Juniper Networks, Inc.
New and Changed Features