Specifications

You can filter on the user, the domain, or both. You can use a wildcard (*) at the
beginning or end of each term, as in the following examples: [e-mail], tom*,
*tom, *ample.com, tom@ex*, tom*@*example.com.
You cannot filter results using a wildcard in the middle of the user or domain, as in the
following examples: tom*[e-mail], tom125@ex*.com.
Traces that have insufficient information to determine the subscriber username are
automatically excluded from the results.
•
Overriding the preferred source address as the source address of Neighbor
Solicitation/Neighbor Advertisement (NS/NA) on unnumbered interfaces (MX
Series)—By default, if a preferred source address is configured on an unnumbered
interface, that preferred address is used as the source address of NS/NA. If no preferred
source address is configured, the router uses a suitable address based on the destination
address scope. Starting in Junos OS Release 13.3, you can configure the router to
override the default configuration of using the preferred source address for NS/NA.
The router ignores the preferred source address and uses an appropriate address based
on the destination address scope.
•
DHCPv6 local server and relay agent username and option 37 (MX Series)—Starting
in Junos OS Releases 12.3R7, 13.2R4, and 13.3R2, the router supports the generation of
an ASCII version of the authentication username. When you configure DHCPv6 local
server or relay agent to concatenate the authentication username with the Agent
Remote-ID option 37, the router uses only the remote-id portion of option 37 and ignores
the enterprise number.
The router no longer supports the enterprise-id and remote-id options for the
relay-agent–remote-id statement.
•
Subscriber management and services feature and scaling parity (MX104)—Starting
in Junos OS Release 13.3R3, the MX104 router supports all subscriber management
and services features that are supported by the MX80 router. In addition, the scaling
and performance values for the MX104 router match those of the MX80 router.
[See Protocols and Applications Supported by MX5, MX10, MX40, and MX80 Routers.]
•
DHCP relay agent for clients in different VRF than DHCP server (MX Series)—Starting
in Junos OS Release 13.3R3, subscriber management provides enhanced security when
exchanging DHCP messages between a DHCP server and DHCP clients that reside in
different virtual routing instances (VRFs). The DHCP cross-VRF message exchange
uses the DHCP relay agent to ensure that there is no direct routing between the client
VRF and the DHCP server VRF.
To exchange DHCP messages between the two VRFs, you configure both the server
side and the client side of the DHCP relay to permit traffic based on the Agent Circuit
ID (DHCP option 82 suboption 1) in DHCPv4 packets and the Relay Agent Interface-ID
(DHCPv6 option 18) in DHCPv6 packets.
•
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.
Copyright © 2015, Juniper Networks, Inc.52
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series