Specifications

•
filter-action protocol group—The following packet types are available for unclassified
firewall filter action packets, which are sent to the host because of reject terms in
firewall filters:
•
aggregate—Aggregate of all unclassified filter action packets.
•
filter-v4—Unclassified IPv4 filter action packets.
•
filter-v6—Unclassified IPv6 filter action packets.
•
other—All other unclassified filter action packets that are not IPv4 or IPv6.
The resolve-v4 and resolve-v6 packet types have been removed from the unclassified
protocol group. They are replaced by the new mcast-v4, mcast-v6, ucast-v4, and
ucast-v6 packet types in the new resolve protocol group.
•
resolve protocol group—The following packet types are available for unclassified
resolve packets, which are sent to the host because of a traffic request resolve action:
•
aggregate—Aggregate of all unclassified resolve packets.
•
mcast-v4—Unclassified IPv4 multicast resolve packets.
•
mcast-v6—Unclassified IPv6 multicast resolve packets.
•
other—All other unclassified resolve packets.
•
ucast-v4—Unclassified IPv4 unicast resolve packets.
•
ucast-v6—Unclassified IPv6 unicast resolve packets.
•
Deleting PTP clock client (MX104)—Starting with Junos OS Release 13.2, on MX104
routers, when you toggle from a secure slave to an automatic slave or vice versa in the
configuration of a Precision Timing Protocol (PTP) boundary clock, you must first
delete the existing PTP clock client or slave clock settings and then commit the
configuration. You can delete the existing PTP clock client or slave clock settings by
using the delete clock-client ip-address local-ip-address local-ip-address statement at
the [edit protocols ptp master interface interface-name unicast-mode] hierarchy level.
You can then add new clock client configuration by using the set clock-client ip-address
local-ip-address local-ip-address statement at the [edit protocols ptp master interface
interface-name unicast-mode] hierarchy level and committing the configuration.
However, if you attempt to delete the existing PTP clock client and add the new clock
client before committing the configuration, the PTP slave clock remains in the free-run
state and does not operate in the auto-select state (to select the best clock source).
This behavior is expected when PTP client or slave settings are modified.
•
Preventing the filtering of packets by ARP policers (MX Series routers)—Beginning
in Junos OS Release 13.3R3, you can configure the router to disable the processing of
the specified ARP policers on the received ARP packets. Disabling ARP policers can
cause denial-of-service (DoS) attacks on the system. Due to this possibility, we
recommend that you exercise caution while disabling ARP policers. To prevent the
processing of ARP policers on the arriving ARP packets, include the disable-arp-policer
statement at the [edit interfaces interface-name unit logical-unit-number family inet
policer] or the [edit logical-systems logical-system-name interfaces interface-name unit
logical-unit-number familyinet policer] hierarchy level. You can configure this statement
Copyright © 2015, Juniper Networks, Inc.56
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series