Specifications

NOTE: The header-integrity-check option that is supported on MS-MICs
and MS-MPCs to verify the packet header for anomalies in IP, TCP, UDP,
and ICMP information and flag such anomalies and errors has a functionality
that is opposite to the functionality caused by passive mode tunneling. If
you configure both the header-integrity-check statement and the
passive-mode tunneling statement on MS-MICs and MS-MPCs, and attempt
to commit such a configuration, an error is displayed during commit.
The passive mode tunneling functionality (by including the
passive-mode-tunneling statement at the [edit services service-set
service-set-name ipsec-vpn-options] hierarchy level) is a superset of the
capability to disable IPsec tunnel endpoint in the traceroute output (by
including no-ipsec-tunnel-in-traceroute statement at the [edit services
ipsec-vpn] hierarchy level). Passive mode tunneling also bypasses the
active IP checks and tunnel MTU check in addition to not treating an IPsec
tunnel as a next-hop as configured by the no-ipsec-tunnel-in-traceroute
statement.
•
Interoperation of ingress sampling and PIC-based flow monitoring (MX
Series)—Starting in Junos OS Release 13.3R6, If PIC-based flow monitoring is enabled
on an ms- logical interface, a commit check error occurs when you attempt to configure
ingress traffic sampling on that particular ms- logical interface. This error occurs
because a combination of ingress sampling and PIC-based flow monitoring operations
on an ms- logical interface causes undesired flow monitoring behavior and might result
in repeated sampling of a single packet. You must not configure ingress traffic sampling
on ms- logical interfaces on which PIC-based flow monitoring is enabled.
•
Generation of mspmand core file for flow control (MX Series with MS-MICs and
MS-MPCs)—Starting with Junos OS Release 13.3R6, instead of an eJunos kernel core
file, the multiservices PIC management daemon core file is generated when a prolonged
flow control occurs and when you configure the setting to generate a core file during
prolonged flow control (by using the dump-on-flow-control option). The watchdog
functionality continues to generate a kernel core file in such scenarios.
•
Change in support for service options configuration on service PICs at the MS and
AMS interface levels (MX Series)—Starting in Junos OS Release 13.3R6, when a
multiservices PIC (ms- interface) is a member interface of an AMS bundle, you can
configure the service options to be applied on the interface only at the ms- interface
level or the AMS bundle level by including the services-options statement at the [edit
interfaces interface-name] hierarchy level at a point in time. You cannot define service
options for a service PIC at both the AMS bundle level and at the ms- interface level
simultaneously. When you define the service options at the MS level or the AMS bundle
level, the service options are applied to all the service-sets on the ms- interface or AMS
interface defined at ms-fpc/pic/port.logical-unit or amsN respectively.
•
Changes in the format of session open and close system log messages (MX Series
with MS-MICs and MS-MPCs)—Starting with Junos OS Release 13.3R7, with the Junos
OS Extension-Provider packages installed and configured on the device for MS-MPCs
and MS-MICs, the formats of the MSVCS_LOG_SESSION_OPEN and
Copyright © 2015, Juniper Networks, Inc.62
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series