Specifications

chassisd) tried to connect using the TNP socket. SNMPD does not accept these
connections. As a fix, in an MX-VC, we made sure that chassisd connects to all processes
which run on the protocol master using internal socket while the chassisd process on
the protocol backup and protocol lincecard connect connect using TNP socket.
PR986009
•
In 6PE scenario, when PE router is sending IPv6 TCP traffic to MPLS core, in rare
occasions, the kernel might crash and reboot with a vmcore file dumped. PR988418
•
OpenFlow v1.0 running on an MX Series router does not respond reliably to interface
up or down events within a specified time interval. Per a fix implemented in Junos OS
Release 13.3R3.6, OpenFlow v1.0 running on an MX Series router responds reliably to
interface up or down events if the echo interval timeout is set to 11 seconds or more.
PR989308
•
On M7i/M10i with enchanced CFEB, M320 with E3-FPC, M120 and MX with DPC. If
"no-local-switching" is present in the bridge domain, then the IGMP-snooping is not
functioning and client cannot see the multicast traffic. PR989755
•
During large scale MVPN routes churn events, some core-facing IGP protocols (like
OSPF or LDP) might flap or experience a long convergence time. PR989787
•
Commit error needs to be reported when using unsupported NAPT44 nat-options
max-sessions-per-subscriber configuration with MS-MIC/MS-MPC. PR993320
•
On T4000 router with type5 FPC. After FPC rebooting, if chassisd process does not
get FPC ready/FPC online ACK message from FPC in 360 seconds, the FPC might reset
again. PR998075
•
On M/MX/T Series routers (platforms) with Network Address Port Translation (NAPT)
configuration. When the router receives the packet whose value of protocol field in the
IPv4 header is 61, the router erroneously does NAPT44 translation. In the correct
situation, the packet should not be translated and forwarded. PR999265
•
The PIC memory gauge counters show up as 0 after a GRES switchover in the "show
chassis pic fpc-slot X pic-slot Y" output. PR1000111
•
On MX240/MX480/MX960 routers running as precision time protocol (PTP) master
when interconnect with MX104 routers running as slave, the PTP clocking state might
get stuck in "INITIALIZING" for the first created PTP port and not be aligned to clocking
state. Another issue is that when issue command "show ptp clock", wrong "slot"
number might be seen on MX104 slave. PR1001282
•
"Syslog generated for session-open will have nat port information only if it is different
from the original source port". PR1001912
•
If issue the command "show services nat mappings endpoint-independent" or "show
services nat mappings address-pooling-paired" or "show services sessions" and kill it
immediately when using EIM/APP feature with too many EIM/APP entries present in
the system, lots of ipc message reply failure messages may be seen in the syslog.
PR1002683
•
Multi-Services PIC could crash and restart on receiving a stray SIGQUIT signal due to
it not handling the signal. PR1004195
Copyright © 2015, Juniper Networks, Inc.104
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series