Specifications

[See ANCP Topology Discovery and Traffic Reporting Overview.]
Support for ANCP generic response messages and result codes (MX Series)—Starting
in Junos OS Release 13.3, the ANCP agent supports receipt of generic response
messages. Upon receipt, the router generates a system log, increments the generic
message counters, and increments the result code counters. Generic response messages
(GRMs) are typically sent instead of specific response messages when no information
needs to be sent other than a result of success or failure. When the message reports
a failure, it must include one of eight result codes to indicate the cause. A GRM can
also be sent independent of a request when the failure causes the adjacency to be
shut down.
[See ANCP Topology Discovery and Traffic Reporting Overview.]
Support for sending and receiving the ANCP Status-Info TLV (MX Series)—Starting
in Junos OS Release 13.3, the Status-Info TLV supplements the generic response
message result codes and provides information about a warning or error condition.
Although usually included in generic response messages, the TLV can also be included
in other ANCP message types. The Status-Info TLV must be included in generic response
messages when the result code indicates a port is down, a port does not exist, a
mandatory TLV is missing, or a TLV is invalid.
[See ANCP Topology Discovery and Traffic Reporting Overview.]
DNS address assignment in DHCPv6 IA_NA and IA_PD environments (MX
Series)—Starting in Junos OS Release 12.3R3 and Release 13.3 (but not in Releases
13.1 and 13.2), the DHCPv6 local server returns the DNS server address (DHCPv6
attribute 23) as a global DHCPv6 option, rather than as an IA_NA or IA_PD suboption.
DHCPv6 returns the DNS server address that is specified in the IA_PD or IA_NA pools—if
both address pools are requested, DHCPv6 returns the address specified in the IA_PD
pool only, and ignores any DNS address in the IA_NA pool.
In releases earlier than 12.3R3, and in Releases 13.1 and 13.2, DHCPv6 returns the DNS
server address as a suboption inside the respective DHCPv6 IA_NA or IA_PD header.
You can use the multi-address-embedded-option-response statement at the [edit
system services dhcp-local-server dhcpv6 overrides] hierarchy level to revert to the prior
behavior. However, returning the DNS server address as a suboption can create
interoperability issues for some CPE equipment that cannot recognize the suboption
information.
[See DHCPv6 Options in a DHCPv6 Multiple Address Environment.]
Support for filtering trace results by subscribers for AAA, L2TP, and PPP (MX
Series)—Starting in Junos OS Release 13.3, you can filter trace results for some
processes by subscriber. The reduced set of results simplifies troubleshooting in a
scaled environment. Specify the user user@domain option at the appropriate hierarchy
level:
AAA (authd)—[edit system processes general-authentication-service traceoptions
filter]
L2TP (jl2tpd)—[edit services l2tp traceoptions filter]
PPP (jpppd)—[edit protocols ppp-service traceoptions filter]
51Copyright © 2015, Juniper Networks, Inc.
New and Changed Features