Specifications

•
The dynamic flow control process (dfcd) might core dump when Dynamic Tasking
Control Protocol (DTCP) trigger request is same for both the VLAN and DHCP
subscriber. PR962810
•
Message type for if_msg_ifl_channel_delete should be lower severity and not an error.
PR965298
•
In the context of DS-Lite softwire scenario, where the Address Family Transition Router
(AFTR) node performs NAT with Endpoint Independent Filtering (EIF) and Endpoint
Independent Mapping (EIM) enabled, the simultaneous arrival of two packets from
opposite sides of the NAT will trigger the creation of the same flow, which in a race
condition results in the Service-PIC restart. PR966255
•
During the Junos OS enhancement of the Port Control Protocol a few issues were
identified regarding NAT flows creation, clearing of the mappings, releasing the
addresses in use, etc. PR967971
•
In the L2TP scenario with dual Routing Engines. After subscriber management
infrastructure daemon (smid) being restarted, because the delete notification to backup
Routing Engine might be lost, the subscriber database (SDB) information does not
synchronize between master Routing Engine and standby Routing Engine. After Routing
Engine switchover is executed, the Layer 2 Tunneling Protocol daemon (jl2tpd) might
crash, and new L2TP subscribers are unable to dial. PR968947
•
When transferring large FTP file, the server might send packets with incorrect layer 4
checksum. If inline NAT service is enabled on the router, it might transit the packets to
client instead of dropping it, which eventually causes the client FTP time out. PR972402
•
If a PPPoE/PPP user disconnects in the access network without the LAC/LNS noticing
it to tear down the connection (also the PPP keepalive hasn't detected yet), and a
second PPP request comes from the same subscriber on the L2TP tunnel (same or
different LAC/tunnel), then a second route is added to the table having the next hop
"service to unknown". PR981488
•
The cflow export would cease due to memory exhaustion when flow-monitoring is
enabled using Adaptive Services II PIC due to memory leak condition. While in this
condition, user would see increments in "Packet dropped (no memory)" as below:
user@node> show services accounting errors Service Accounting interface: sp-3/0/0,
Local interface index: 320 Service name: (default sampling) Interface state: Accounting
Error information Packets dropped (no memory): 315805425, Packets dropped (not
IP): 0. PR982160
•
In H323 ALG with CGNAT scenario, the MS-PIC might crash when the ALG is deleting
an H323 conversation due to the deleting port is outside of allocated NAT port-block
range. PR982780
•
On M/MX/T Series routers (platforms) with Services PIC with dynamic-nat44
translation-type configured, when the flows are cleared the IP addresses in use are
never freed. This issue is present in JunOS 11.4R7 and all more recent releases without
this fix. PR986974
•
In large scale L2TP LNS environment. When the SNMP MIB JNX-L2TP-MIB is walked
continuously, the memory of the L2TP daemon (jl2tpd) increases due to memory leak.
PR987678
Copyright © 2015, Juniper Networks, Inc.124
Release Notes: Junos OS Release 13.3R6 for the EX Series, M Series, MX Series, PTX Series, and T Series