Specifications

IPv6
•
On PTX Series platform, when receiving high rate ipv4/ipv6/mpls packets with TTL
equals 1, the ICMP TTL expired messages are sent back to the sender not according
with the ICMP rate limit settings. PR893129
•
PTX Series drops packets containing same source and destination IP due to LAND
attack check. PR934364
MPLS
•
In rare scenarios, the routing protocol process can fail to read the mesh-group
information from the kernel, which might result in the VPLS connections for that
routing-instance to stay in MI (Mesh-Group ID not available) state. The workaround is
to deactivate/activate the routing-instance. PR892593
•
MPLS traceroute does not work with logical router. PR965883
•
When issue "traceroute mpls rsvp lsp-name" from the MPLS LSP ingress node, if there
are PTX Series routers on the LSP path, PTX Series would not list correct downstream
router's IP in the TLV of the response packet. PR966986
Routing Policy and Firewall Filters
•
On PTX Series platform, when a firewall filter has many terms, all the terms might not
work correctly due to incorrect order of terms due to mis-programming. PR973545
VLAN Infrastructure
•
Commits less than 3 minutes apart with per-vlan-queuing configuration should be
avoided, as this might lead to interrupts or undesirable side-effects. PR897601
Resolved Issues: Release 13.3R2
Chassis Cluster
•
When only one end of an AE link sees LACP timeouts or there is intermittent LACP loss
on the AE link, it does not result in AE flap. PR908059
Dynamic Host Configuration Protocol (DHCP)
•
DHCP relay feature doesn't work on PTX3000. PR864601
General Routing
•
On PTX Series Packet Transport Routers, we support only 48k longest prefix match
(LPM) routes. If the limit of 48,000 longest prefix match (LPM) routes is exceeded,
the kernel routing table (KRT) queue can be stuck with the error "Longest Prefix
Match(LPM) route limit is exceeded." PR801271
•
RPD on the backup Routing Engine might crash when it receives a malformed message
from the master. This can occur at high scale with nonstop active routing enabled
when a large flood of updates are being sent to the backup. There is no workaround
181Copyright © 2015, Juniper Networks, Inc.
Resolved Issues