Specifications

•
The error message 'unlink(): failed to delete .perm file: No such file or directory' was
logged when disconnecting from a Telnet session to the router. PR876508
•
When the instance have vlan-id all and adding interface unit with "vlan-tags outer X
inner Y" to this instance, traffic from ALL instance VLANs is leaking over that unit tagged
with outer tag X and each VLANs own inner tag A,B.C,..... Fix: When the instance have
vlan-id all, for dual tagged ifl the inner vlan check will be done. PR883760
•
On MX Series based line card, for interfaces tagged with VLAN ID same as the
native-vlan-id configured on the interface, FPC adds Native VLAN ID to the packets
received on the interface and destined to the host. This is irrespective of the packet
content. This results in the packets getting doubly tagged when receiving packets
which are already tagged with VLAN ID matching the Native VLAN ID, and thus cause
ARP resolution failure on Native VLAN. For example, the ARP packets to IRB (on VLAN
101) are tagged with VLAN ID 101 (which is also the native VLAN ID) and are getting
additional tagged. Hence they are dropped by the IRB and this can cause the ARP
request packet not getting resolved on Native VLAN. PR917576
•
When the transit traffic is hitting the router and the destination is a local segment IP
which requires ARP resolution, it's mis-classified by the DDOS filter and an incorrect
policer is applied. This leads to host queue congestion. PR924807
•
Starting with Junos 13.3 and later, the range of cli screen-with is 40 through 1024 (in
earlier Junos OS releases, the range is 0 through 1024). This PR restores the option of
setting screen-width to 0 resulting in unlimited screen width. PR936460
•
The Routing Engine and FPCs are connected with an internal Ethernet switch. In some
rare case, the FPCs might receive a malformed packet from the Routing Engine (e.g.
packet gets corrupted somewhere on its way from Routing Engine to FPC). Then the
toxic traffic might crash the FPC. PR938578
•
MPC Type 2 3D may crash with CPU hog due to excessive link flaps causing the
interrupts to go high. PR938956
•
On a router which does a MPLS label POP operation (penultimate hop router for
example) if the resulting packet (IPv4 or IPv6) is corrupted then it will be dropped.
PR943382
•
If a PE router is both egress and trazit node for a p2mp lsp, the Packet Forwarding
Engine may report errors and install a discard state for the fib entry representing the
p2mp lsp label with bottom of stack bit set to 0 . This problem does not have any
impact since there is no application using the s=0 entry of a p2mp lsp. PR950575
•
* MX2020 FanTray power specification. - zone#1:FT#3 - gets power from zone#1 only
- zone#1:FT#2 - gets power from zone#0 in case of no-power in zone#1 - zone#0:FT#1
- gets power from zone#0 only - zone#0:FT#0 - gets power from zone#1 in case of
no-power in zone#0 - Critical(Minimum) number for MX2020 operation is 3 If one of
zone has no PSM, then it means FAN single-fault in the chassis's point of view. For
example, if zone#1 has no PSM, then the FT#3 doesn't get power as it is local-powered
FT. Hence, in this case, the FT#3-LED should show ORANGE to notify the single-fault
to user, while FT#2 can shows GREEN if it gets enough power from zone#0. In addition,
CRAFT-LED for FT#3 should be turned off. * Due to HW-limit(bicolor), it could not
show ORANGE color. In current implementation, both CRAFT-LED, FT#3-LED show
Copyright © 2015, Juniper Networks, Inc.120
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series