ACX, EX, T, TX, PTX, MX, QFX5100, VMX, VRR, Network Agent

Junos Software Service Release version 16.1R7-S7 is now available for download from the Junos software download site
Download Junos Software Service Release:

1. Go to Junos Platforms - Download Software page
2. Input your product in the "Find a Product" search box
3. From the Type/OS drop-down menu, select Junos SR
4. From the Version drop-down menu, select your version
5. Click the Software tab
6. Select the Install Package as need and follow the prompts

NOTE

PR1463859 introduces a software defect that causes a 10GE interface to flap continuously when configured with the WAN-PHY framing with the default "hold-down" timer (0). Once you upgrade a router to an affected software release, the interface may flap continuously. This is not applicable to an interface with the default framing - LAN-PHY. [TSB17782]

16.1R7-S7 - List of Fixed issues

PR Number	Synopsis	Category: EX2300/3400 CP
1192363	On Ex3400 and EX2300 switches, when client is authenticated in Dynamic/Server-fail/Server-reject/Guest vlan multiple supplicant mode, ping failure can be seen between client and switch.	On Ex3400 and EX2300 switches,when client is authenticated in Dynamic/Server-fail/Server-reject/Guest vlan multiple supplicant mode, ping failure can be seen between client and switch.
PR Number	Synopsis	Category: Accounting Profile
1452363	The pfed might crash and not be able to come up on the PTX or TVP platforms	The flow label statistics are retrieved periodically by pfed for PTX or TVP platforms, if the statistics reply becomes very big number, the pfed might crash hence affecting traffic.
1458008	MX: syslog errors @ pfed: rtslib: ERROR received async message with no handler: 28	An MX router configured for Subscriber Management, and "chassis network-services enhanced-ip", may see log messages similar to Jan 1 01:00:00 MXrouter_RE0 pfed: rtslib: ERROR received async message with no handler: 28
1458143	PFED fails to retrieve statistics from PFE for (ESSM) subscribers. Error message: libstats_error: interim-or-baseline-stats-not-found	In some occasions upon FPC reboot, the pfed database might not get updated with the correct location_id for some physical interfaces (IFDs). This results in an error when the timeout for a ESSM subscriber connected to such an interface reaches it's limit and the pfed daemon tries to collect the statistics for the subscriber in PFE based on this wrong location_id. The error "essmd[xxxx]: is_stats_error_retryable: ifl name: ge-x/x/x.xxx, libstats_error: interim-or-baseline-stats-not-found" will be logged in the messages log.
PR Number	Synopsis	Category: MPC Fusion SW
1463859	The MPC2E-NG/MPC3E-NG card with specific MIC might crash after a high rate of interface flaps	If any MIC of MIC-3D-2XGE-XFP / MIC-3D-4XGE-XFP / MIC-3D-20GE-SFP-E / MIC-3D-20GE-SFP-EH / MIC-MACSEC-20GE is installed in MPC2E-NG/MPC3E-NG card, the Microkernel (uKern) might hog for CPU on Packet Forwarding Engine (PFE) when there is a high rate of interface flaps (~30/40 flaps per second). This will eventually trigger the MPC2E-NG/MPC3E-NG card crash with an NGMPC core file. Normally the excessive interface flapping won't happen frequently in real world and it may be caused due to external environment. This fix will reduce the impact and prevent the uKern hog when having such conditions.
PR Number	Synopsis	Category: Border Gateway Protocol
1366823	Ukern memory leak and core crash in BGP environment	Ukern memory leak and fpc core crash might be happened when device configured link-node protection with labeled-bgp.
1389379	FPC might crash when BGP multipath is configured with protection	When running with Border Gateway Protocol (BGP) multipath with protection configured, it is possible to encounter a situation where nexthops references are not properly decremented, thus causing the system to hold onto nexthops when they should be freed. This leads to a memory hog situation which eventually results in a Flexible PIC Concentrator (FPC) crash.
1454198	The rpd scheduler slip for BGP GR might be up to 120s after the peer goes down	In BGP GR (graceful-restart) scenario (graceful-restart is configured for BGP or GR-helper mode is enabled by default), when high-scale routes get learnt from one peer, the rpd scheduler slip might be up to 120s after that BGP peer flaps.
1454951	The rpd process might crash when multipath is in use	If multipath is enabled, in some certain conditions, The rpd process might crash while secondary route resolution is running.
1487691	RPD's bgpio thread goes into high CPU utilization when the outgoing BGP updates queue is full	RPD goes into high CPU utilization causing slow BGP network convergence on a large scale setup. The high CPU utilization of the BGP IO thread (bgpio) happens when the outgoing BGP update queue is full. The typical situation is a BGP Route-Reflector (RR) sending a large number of BGP updates (900K routes) to a large number of slow peers (more than 200 peers). This issue is the side-effect of PR1351639. (See also https://kb.juniper.net/TSB17725)
PR Number	Synopsis	Category: MX Platform SW - System Buses
1299594	CHASSISD_I2CS_READBACK_ERROR: Readback error from I2C slave for FPC 0 ([0x10, 0x3a] -> 0x0)	Chassisd may report readback error for MPC 3D 16x10G FPCs when it?s trying to access 0x3a register. However, it?s an invalid register for this type of FPC so error got reported.The log itself is non-impacting and can be safely ignored.
PR Number	Synopsis	Category: dhcpd daemon
1457949	Show subscriber extensive incorrectly displays DNS (domain-name-server) address provided to DHCP clients	Show subscriber extensive incorrectly displays DNS (domain-name-server) address provided to DHCP clients
PR Number	Synopsis	Category: JUNOS Dynamic Profile Configuration Infrastructure
1379482	The subinfo process might crash with core file if flapping all the subscribers	On MX platforms with large scaled number of subscribers login, if flapping all the subscribers and executing the command "show subscriber summary port", the subinfo process might crash.
PR Number	Synopsis	Category: dynamic dcd prs
1470622	Executing commit might hang up due to stuck dcd process	When dynamic DHCP sessions are existing in the device, if multiple commits in parallel are performed, the commit might hang up.
PR Number	Synopsis	Category: Ethernet OAM (LFM)
1253542	In a VPLS multihoming scenario, the CFM packets can be forwarded over backup, standby, non-designated, or CCC-down link, which might cause the traffic to be endlessly looped	In a VPLS multihoming scenario, the CFM packets are forwarded over the standby PE device link, resulting in duplicate packets or a loop between the active and standby link.
PR Number	Synopsis	Category: Express PFE L2 fwding Features
1399369	CPU hog may be observed on PTX/QFX10000 Series platform	On PTX/QFX10000 series platform, CPU hog on PFC may be observed if the adaptive feature is enabled to load-balance for an AE interface.
PR Number	Synopsis	Category: Express PFE L3 Multicast
1389569	BFD flaps are seen on PTX or QFX10K platforms with inline BFD	With inline-BFD configured on the PTX or QFX10000 platforms, BFD sessions might flap continuously.
PR Number	Synopsis	Category: Kernel software for AE/AS/Container
1440033	Traffic loss is observed on newly added interfaces in AE on "MX and EX platforms"	On MX and EX series devices that support the "enhanced-ip" feature and when the new interface is added to aggregated ethernet (ae), output traffic is observed as 0 on the existing member links. This is being observed due to software issues as wrong weights are being set for existing child interfaces in the AE bundle.
PR Number	Synopsis	Category: Label Distribution Protocol
1460292	High CPU usage and rpd coredump might be observed if "ldp track-igp-metric" is configured and IGP metric is changed	If "protocols ldp track-igp-metric" is configured, metric change of IGP route might cause high CPU usage and rpd coredump on the device.
PR Number	Synopsis	Category: MQTT protocol, Mosquitto Broker and Client API
1140087	Mosquitto log file management enhancement	Before 16.2R1, Mosquitto daemon (3rd party s/w) does not have log management features. It will write logs named with "mqtt_" under /var/log/ until the disk is full which is a problem. After 16.2R1, Junos adds the log management features to the Mosquitto logs. The log size can be maximum 4.0 Mbytes and it keeps 10 archives. From 18.4 onwards, Junos will not use such daemon so these logs won't be generated at all.
PR Number	Synopsis	Category: FreeBSD Kernel Infrastructure
1146891	EX4300-48MP: 'set system ports console log-out-on-disconnect' does not work	'set system ports console log-out-on-disconnect' does not work
PR Number	Synopsis	Category: "ifstate" infrastructure
1404507	The VMCore might be seen when there is an interface deletion	In a very rare situation, The VMCore might be seen when there is an interface deletion/addition.
PR Number	Synopsis	Category: PTX Broadway based PFE MPLS-LSPs RSVP VPNs tcc ccc software
1484255	FPC might crash when dealing with invalid next-hops	On PTX3000/PTX5000 platform with some specific FPCs, if the weights of links are set to an invalid value on an AE bundle interface or unilist (an unilist next-hop composed of several unicast next-hops), the FPC crash might be observed. It is a rare issue and the FPC will try to reload to resolve this problem. Traffic loss might be seen before the FPC completes the reload period.
PR Number	Synopsis	Category: RPD policy options
1357802	Configuration commit operation after policy change causes rpd crash	The rpd might crash during policy configuration changes.
PR Number	Synopsis	Category: SNMP Infrastructure (snmpd, mib2d)
1350826	SNMP Traps not being sent by the new master RE after RE mastership switchover	Sometimes, the trap-source-address bind is getting delayed because the platform does not attach the respective IP to any of the interfaces on the router. But since trap is generated at the start before any configured trap source-address is not yet bound properly, this trap is not added into the throttle/destination trap queues.
1392616	The snmpd process might crash and cause a core dump	The snmpd process leaks memory in the SNMPv3 query path and crashes. The issue is caused by a memory leak when the request PDU is dropped by SNMP when the snmp filter-duplicates configuration is enabled. Each request PDU has a structure pointer for the SNMPv3 security details. This is allocated when the PDU is created or cloned. But while dropping the duplicate requests, the corresponding structure is not freed, which causes the memory leak.
1413352	The SNMP query might not get data in scaled Layer 2 circuits environment.	When a large-scale AE interfaces are configured with a large-scale l2circuits, if executing snmpwalk on interface OID's, the query may time out and the data could not be retrieved. When the issue occurs, below error could be observed. user@router> show snmp mib walk 1.3.6.1.2.1.2.2 ... ifInOctets.70781 = 75155380 Request failed: General error user@router> show snmp mib walk ifHCInOctets ifHCInOctets.831 = 340482960268874 Request failed: General error It is to be noted that all general errors are not an issue. If there are interface flaps and churns in the system during which snmp query happens on the same interface which is flapping, then general error is the way to report it because stats cannot be fetched during the churn/flap duration.
PR Number	Synopsis	Category: MPC7/8/9 Interface Issues
1463015	An interface might get stuck in down state on certain MX platforms	The interfaces on certain MX platforms might get stuck in a down state, if the remote interface sends invalid code to the local interface. Link might not come up even after the remote peer has begun sending a good signal.
PR Number	Synopsis	Category: Stout PF fabric (SFB2)
1461356	Traffic might be impacted because the fabric hardening is stuck	Fabric hardening (FH) is the process of controlling bandwidth degradation to prevent traffic black hole. When FH is processing, if SFB/SCB get failure, FH process will be stuck, which will get traffic lost.
PR Number	Synopsis	Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1415042	The user might not enter configure mode due to mgd is in lockf status	If "commit confirmed " is executed, then issuing another "commit" or "commit confirmed " after around the minutes, in race condition, a rollback might be hit. At last, it may cause the mgd process to enter and to stay in lockf status. Thus, the user might not enter configure mode anymore.

Updated 2020-05-08 to include a notice about TSB17782
First publication date 2020-02-20