Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

18.1R3-S8 - Software Release Notification for JUNOS Software Version 18.1R3-S8

0

0

Article ID: TSB17687 TECHNICAL_BULLETINS Last Updated: 22 Nov 2019Version: 1.0
Alert Type:
SRN - Software Release Notification
Product Affected:
ACX, EX, MX, PTX, QFX, SRX, NFX, VMX, VRR, Network Agent
Alert Description:
Junos Software Service Release version 18.1R3-S78 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
Solution:

Junos Software service Release version 18.1R3-S8 is now available.

18.1R3-S8 - List of Open issues

PR Number Synopsis Category:QFX L3 data-plane/forwarding
1437943 The IPv4 fragmented packets might be broken if PTP transparent clock is configured
 
When Precision Time Protocol (PTP) transparent clock is enabled, PTP adds the residence time to the Correction Field of the PTP packets as they pass through the device. On QFX5K platforms with PTP transparent clock enabled, the IPv4 fragmented packets of UDP datagram might be broken by PTP in some rare scenario, and the corrupted packets will be discarded by system. This issue has traffic impact.
PR Number Synopsis Category:EX Chassis Interface Handling
1441035 The ports of the EX device might stay in up state even if the EX46XX/QFX51XX series device is rebooted
 
With DAC cable used between EX46XX/QFX51XX series device and EX device, during rebooting the EX46XX/QFX51XX series device, the ports on EX device might still stay up.
PR Number Synopsis Category:QFX L3 data-plane/forwarding
1406242 QFX5200/5100 might not be able to send out control plane traffic to the peering device
 
On all QFX5200/5100 platforms, the router might not be able to send out control plane traffic to the peering device along with "Failed to allocate 16384 DMA memory" messages. All the routing protocols running over the affected interfaces will be down due to this issue, and therefore it impacts the service.
1406242 QFX5200/5100 might not be able to send out control plane traffic to the peering device
 
On all QFX5200/5100 platforms, the router might not be able to send out control plane traffic to the peering device along with "Failed to allocate 16384 DMA memory" messages. All the routing protocols running over the affected interfaces will be down due to this issue, and therefore it impacts the service.

18.1R3-S8 - List of Fixed issues

PR Number Synopsis Category:EX platform-side analytics
1436223 i40e NVM upgrade support for EX9200 platform
 
Added support for i40e NVM upgrade in EX9208.
PR Number Synopsis Category:L2NG RTG feature
1440574 MAC addresses learned on RTG may not be aged out after a VC member rebooted.
 
There is a IPC sequence issue when VC member rebooted in aggregated interface. After reboot VC member, RE kernel inject mac entry to fpc. Because of IPC sequence issue, RE added mac entry, originally source mac entry, is added to fpc as remote mac entry. And entry is never be aged out because it is remote entry.
PR Number Synopsis Category:EX4300 Platform
1383356 EX4300 device chooses wrong bridge-id as RSTP bridge-id
 
Under RSTP scenario, EX4300 chooses wrong bridge-id as RSTP bridge-id. It might cause loops in the networks.
PR Number Synopsis Category:EX4300 Virtual Chassis
1449206 Current MAC address might change when deleting one of the multiple L3 interfaces
 
Current MAC address might change when deleting one of the multiple L3 interfaces and it has traffic impact when this issue occurs.
PR Number Synopsis Category:Marvell based EX PFE L2
1404664 The dot1x could not work when dot1x is configured with isolated VLAN on one interface
 
On EX2300/EX3400/EX4300/EX4600 platforms, when one interface is configured as a member of an isolated VLAN and dot1x is enabled on that interface, the dot1x might not be able to work due to the EAPOL (Extensible Authentication Protocol over LAN) packets not transmitted from PFE.
PR Number Synopsis Category:EX2300 & EX3400 PFE
1355111 Transit OSPF traffic over Q-in-Q tunneling might be dropped if a firewall filter applied to Lo0 interface
 
On EX2300 as CE/PE device, transit OSPF traffic over Q-in-Q tunneling might be dropped if a firewall filter applied to Lo0 interface.
1423310 IPv6 multicast traffic received on one VC member might be dropped when egressing on other VC member if MLD snooping is enabled
 
With MLD snooping enabled, IPv6 multicast traffic might be dropped on Virtual Chassis (VC) if ingress and egress interfaces are on different VC members.
1446844 The traffic might be dropped when a firewall filter rule uses 'then vlan' as the action in a VC scenario
 
If a firewall filter is configured with the action 'then vlan' in a VC scenario on some specific platforms (e.g., EX2300/EX3400/EX4600/QFX5100...), some of the traffic which matches that filter might be dropped.
1448071 Unicast arp requests are not replied with no-arp-trap option.
 
When unicast arp request is received by EX3400/QFX5100 switch and it is configured with "set switch-options no-arp-trap option", the arp request may not be replied. This has been fixed and unicast ARP request will be replied even with "set switch-options no-arp-trap option" configuration.
PR Number Synopsis Category:EX2300 & EX3400 platform
1378710 MACSEC session might fail to re-establish after interface flap
 
After the MACsec session is deleted, the corresponding interfaces might lose their MACsec function if LACP is enabled on them and the statement exclude lacp is configured under the [edit security macsec] hierarchy.
1438252 LED turn on even after power-off the VC members
 
Front panel LED keeps on even after request system power-off on ex platform VC setup
1442134 EX3400 FAN alarm (Fan X not spinning) appears and disappears repeatedly after removed the fantray (Absent).
 
EX3400 FAN alarm (Fan X not spinning) appears and disappears repeatedly after removed the fantray (Absent).
PR Number Synopsis Category:EX2300 & EX3400 VC
1422507 The interface on failed member FPC of EX2300/EX3400 virtual-chassis may stay up 120 seconds
 
On EX2300/EX3400 virtual-chassis setup, the interface on failed member FPC retains as up state for 120 seconds. This issue will cause traffic loss of about 120 seconds.
1447853 EX3400-VC may go into hang state when a disk error occurs on EX3400
 
On EX3400 platform, because "on-disk-failure" CLI is not supported, when a disk error occurs, the device may go into hang state. For EX3400 virtual chassis (VC), this issue may cause other devices in the VC to stop working.
PR Number Synopsis Category:JSF SSL Service Module
1411110 SRX5000 Series: Denial of Service vulnerability in SSL-Proxy feature. (CVE-2019-0051)
 
SSL-Proxy feature on SRX devices fails to handle a hardware resource limitation which can be exploited by remote SSL/TLS servers to crash the flowd daemon.
PR Number Synopsis Category:QFX LLDP Control Plane related
1426753 QFX5210: Received LLDP frames on em0 not displaying in LLDP neighbor output
 
LLDP frames received on a QFX5210 management em0 port may not show in show lldp operational queries. Other non-em0 interfaces will display statistics
PR Number Synopsis Category:QFX Access control list
1441444 QFX5210: Firewall Filter DSCP Action Modifier does not work when Firewall Filter is mapped to IRB
 
When applying a firewall filter, which has a modifier to change the DSCP value of a packet, to an IRB interface, the action modifier has no effect.
PR Number Synopsis Category:QFX PFE CoS
1449645 Qfx10008: FPC0 cored after running the pfe command "show cos sched-usage"
 
Without this fix, the PFE cli "show cos sched-usage" will restart QFX10008's forwarding plane
1452013 "show cos scheds-per-pfe" and "show cos pfe-scheduler-ifds" pfe commands will restart forwarding planes on QFX10008 switches
 
Without this fix, "show cos scheds-per-pfe" and "show cos pfe-scheduler-ifds" PFE cli will cause the forwarding plan to restart on QFX10008 switches. See also PR1449645
PR Number Synopsis Category:QFX PFE L2
1354889 Storm control configuration may be disabled for the interface
 
When QFX5100 is initialized, in rare condition, if storm control is configured on the interface, it might not work as expected. The traffic levels will not be monitored and the unknown unicast packets will not be dropped.
1421672 Packet loss might be seen when one of the Spine switch fails or reboots
 
On QFX5K/AS7816 series switches, a brief packet loss might be seen when one of the spine switch fails or reboots in a VxLAN setup as it takes time to update all the VTEPs to new next-hop towards the other Spine switch. This happens due to the Fast Reroute capability not being present for VxLAN technology.
1453430 In VC scenario traffic drop might be seen when one VC member reboots and rejoins the VC
 
On QFX5K or EX4600 VC (Virtual-Chassis) scenario, when VSTP is enabled and one AE interface is used, if one member reboots and rejoins the VC, some packets drop might be seen.
1455161 Unequal LAG hashing might happen on QFX devices
 
On QFX5100/QFX5110/QFX5120/QFX5200/QFX5210 Series platforms with load-balance configuration, the uneven traffic distribution might be seen on the link aggregation group (LAG) interfaces.
PR Number Synopsis Category:QFX L3 data-plane/forwarding
1432023 On QFX5100/EX4600 switches, fxpc core might be seen during the reboot of device
 
On QFX5100/EX4600 switches due to Bad Chip ID, an fxpc core can be seen during the device reboot. This is due to a transient error related to BCM chip where vendor tries to get the chip ID and it results in improper info.
1441402 Traffic might be dropped after the QinQ enabled interface is flapped or a change is made to the vlan-id-list
 
On QFX5K/EX4600 with SP (Service Provider) style VLAN configuration (in this method, each VLAN-ID is locally significant to a physical interface), if interface-mac-limit/mac-table-size is configured (i.e. software MAC learning is enabled) and the scale of MAC addresses on the box is more than 2000, traffic might be dropped after QinQ enabled interface is flapped or a change is made to the vlan-id-list.
1449410 Loopback address exported into other VRF instance might not work on EX/QFX/ACX platforms
 
On EX/QFX/ACX platforms, the loopback address exported into other VRF instance might not work.
1451217 MPLS LDP may still use stale MAC of the neighbor even the LDP neighbor's MAC changes
 
On EX/QFX/ACX platforms, when there is MAC change for LDP neighbor and IP remains the same, ARP update is proper but MPLS LDP may still use the stale MAC of the neighbor. If there is any application/service such as MP-BGP using LDP as next-hop, all transit traffic pointing to the stale MAC will be dropped.
1457725 The IGMP snooping on QFX5110/QFX5129 leaf devices might cause multicast packets to be looped in case of multihomed scenario
 
In an EVPN/VXLAN multihomed environment with QFX5110/QFX5120 acting as leaf devices, if the IGMP snooping is used, IGMP snooping might override the local bias filters on Designated Forwarder (DF) and Non-Designated Forwarder (NDF) devices, and forwards the packets causing multicast packets loops.
1460688 The egress interface in PFE for some end-hosts may not be correct on the layer 3 gateway switch after it is rebooted
 
On edge-routed bridging (ERB) EVPN-VXLAN multihoming designs with QFX5110 and QFX5120 switches work as Layer 3 gateways, in some rare condition, when one of the switches acting as L3 gateway comes up after reboot, the egress interface in PFE for some end-host may not be updated to the correct next-hop interface in the hardware on that gateway. This issue cause traffic disruption for the affected end host
PR Number Synopsis Category:QFX PFE MPLS
1435504 The l2circuit traffic might be black-holed at EVPN SPINE/MPLS LSP TRANSIT device if VXLAN access interface flaps on remote PE node(QFX5110)
 
When there is a L2circuit connection between 2 QFX5110 established through an EVPN SPINE/MPLS LSP TRANSIT device. If the VXLAN access interface flap at one QFX5110, it will cause corruption for l2circuit at the other QFX5110. So the l2circuit traffic is blackholed at MPLS transit node.
PR Number Synopsis Category:QFX Analyzer, sflow
1460122 Storm control profile might not be applied on QFX5k/EX4600 platforms
 
On QFX5k/EX4600 platforms, storm control profile might not be applied hence there might be CPU high usage or packets loss issues on the device if there is large amount of broadcast or unknown unicast packets arriving the device.
PR Number Synopsis Category:accounting profile bugs
1446762 [MX204] Input/Output counters of AE bundle/member links configured on non-default logical systems are not updated
 
On MX204, Input/Output counters of AE bundle and its member links defined in non-default logical systems are not updated.
PR Number Synopsis Category:"agentd" software daemon
1401817 The na-grpcd log file is not rotated and keeps growing until RE is out of disk space
 
In JET/Telemetry scenario, the Telemetry log file is not rotated and keep growing until Routing Engine (RE) is out of disk space, this might cause unexpected impact of RE, and eventually lead to RE crash. The fix has now been provided to set max allowable size to 50M and once the file reaches its max size, it will get rotated and compressed.
PR Number Synopsis Category:MPC Fusion SW
1427305 ENTITY MIB has incorrect containedIn values for some fixed MPCs with builtin PICs
 
On some fixed MPCs with builtin PICs, the ENTITY MIB has incorrect containedIn values for PICs when doing snmp mib walk for oid .1.3.6.1.2.1.47
PR Number Synopsis Category:A20/A40 IOC card
1414460 HA packets might be dropped on SRX5000 line of devices with IOC3 or IOC2 cards
 
On SRX5K platform with IOC3 or IOC2 card installed, the HA packets (HA data plane RTOs and Z mode revenue) might be dropped by SPU and hence, HA fablink might get down.
PR Number Synopsis Category:Junos Fusion Infrastructure
1447873 Reachability issue of the host connected to the SD might be affected in Junos Fusion Enterprise environment with EX9200 series devices as AD
 
In a Junos Fusion Enterprise environment, when traffic originates from a peer device connected to the aggregation device and the ICL is a LAG, there might be a reachability issue if the cascade port is disabled and traffic has to flow through the ICL LAG to reach the satellite device. As a workaround, use single interface as the ICL instead of a LAG.
PR Number Synopsis Category:BBE Autoconfigured DVLAN related issues
1461340 bbe-smgd coredump when all radius servers are unreachable
 
The bbe-smgd might crash when all the RADIUS servers are unreachable
PR Number Synopsis Category:BBE database related issues
1396470 The subscriber bindings might not be successful on QFX/EX platforms
 
On QFX/EX platforms, when bringing up clients (most likely in DHCP/PPP subscriber scenario), the subscribers might fail to bind. The reason is that when installing new software images, it might cause shared memory (created by previously running image) not to be cleared out. The issue will persist until the previous values in shared memory are removed and the daemons affected by the data in shared memory may continue core/crash and thus they will not be able to function properly.
PR Number Synopsis Category:Subscriber Management routing
1458369 The subscriber routes are not cleared from backup RE when session is aborted
 
On MX platforms with enhanced subscriber enabled, the subscriber routes might not be cleared from backup RE when session is aborted. The bbe-smgd memory leak might be seen on the backup RE and subscribers could not login after switchover.
PR Number Synopsis Category:Border Gateway Protocol
1351639 The rpd crashes in JunOS 16.1 or higher during BGP convergence
 
In JunOS 16.1 or higher, during BGP convergence, the input/output thread constructing the outgoing BGP PDU and manipulating the path attributes before hand-off the data to the socket. If this PDU length is zero, it will trigger an assertion and routing-protocol demon is restarting.
1423647 Route churn might be seen after changing maximum-prefixes configuration from value A to vlaue B
 
In BGP setup configured with VPN families (inet-vpn, inet6-vpn, l2vpn, evpn or mvpn), route churn might be seen after changing maximum-prefixes configuration from value A to value B, it causes rpd CPU usage to be hogged for about an hour.
PR Number Synopsis Category:Issues regarding Capella related OTN/Software.
1419204 RX alarms are not set as according to the threshold value configured for the DCO Tunable Optics.
 
MDIO (Management data input/output) is a serial management interface for handling read/write access of the registers on the OTN CFP2. Due to a regression issue, MDIO returns command error for the write operation on the registers for the received optical power threshold. Hence the values for the received optical power threshold are not set correctly and the contents of the registers for received optical power thresholds are left to zero. Below syslog error messages are observed from the FPC ac200_dcfp2_cfp_write: MDIO command error, err status 8000, err addr b03c <<< ac200_dcfp2_cfp_write: MDIO command error, err status 8000, err addr b03d <<<
PR Number Synopsis Category:MX Platform SW - FRU Management
1442138 The chassisd is unable to power off a faulty FPC after RE switchover which leading to chassisd restart loop
 
In the MX router with a faulty (e.g. hardware error) FPC (Flexible PIC Concentrator) installed, performing RE (Routing Engine) switchover or restarting chassisd which may cause chassisd restart loop. This issue will cause traffic lose completely.
PR Number Synopsis Category:L2NG Access Security feature
1451688 DHCP Snooping static binding not take effect after deleting and re-adding the entries
 
From Junos OS release 14.1X53-D15/15.1R1 and above, due to a software defect, DHCP Snooping static binding may not take effect after deleting and re-adding the entries with commit. As a workaround, we can use "commit full" after the configuration changes.
PR Number Synopsis Category:QFX Control Plane VXLAN
1441047 The specific source-ports of UDP packet are dropped on EVPN/VXLAN setup
 
On QFX5120 EVPN/VXLAN scenario, in a rare condition, the specific source-ports of UDP packets (41070 or 52870) are wrongly hitting wrong internal VXLAN implicit filter (system level and unable to configure), causing these two kinds of UDP packet loss/service degradation on UDP service.
1441047 The specific source-ports of UDP packet are dropped on EVPN/VXLAN setup
 
On QFX5120 EVPN/VXLAN scenario, in a rare condition, the specific source-ports of UDP packets (41070 or 52870) are wrongly hitting wrong internal VXLAN implicit filter (system level and unable to configure), causing these two kinds of UDP packet loss/service degradation on UDP service.
1453865 JDI-RCT: EVPN-VXLAN NON-COLLAPSED:ARP will get resolved on QFX5100 for Vxlan having vlan-id of 2
 
When there is a vxlan with vlan -id of 2 on a QFX5100, ARP will not get resolved.
PR Number Synopsis Category:QFX xSTP Control Plane related
1453505 Config change in VLAN all option might affect the per-VLAN configuration
 
The VLAN specific parameters might not be used if configuring VLAN all option and VLAN specific config.
PR Number Synopsis Category:OpenSSH and related subsystems
1440476 Removing SSH Protocol version 1 from configuration
 
You can no longer configure "set system services ssh protocol-version v1" on this JUNOS software.
PR Number Synopsis Category:Device Configuration Daemon
1409535 Unrelated AE interfaces might go down if committing configuration changes
 
On all Junos platforms, if VRRP is running upon AE interfaces while committing any configuration changes related to AE interfaces, unrelated AE interfaces might go down.
PR Number Synopsis Category:EVPN control plane issues
1399726 EVPN Type 2 MAC+IP route is stuck when the route Advertisement has 2 MPLS labels and Withdrawal has 1 label
 
In EVPN (Ethernet VPN) scenario, if the router receives a Type 2 MAC+IP route Advertisement having 2 MPLS labels, and then Withdrawal of the same route with only 1 label, the Withdrawal will not be processed and that route will be stuck.
1461677 In EVPN scenario memory Leak might be observed when proxy-macip-advertisement is configured
 
In EVPN scenario if "proxy-macip-advertisement" knob is configured, it might cause memory leak. Traffic would be impacted in case the memory leak is not stopped.
PR Number Synopsis Category:EVPN Layer-2 Forwarding
1441565 Restarting l2-learning might cause some remote MAC addresses to move into forwarding 'dead' state
 
When restarting l2-learning (l2ald) process on MX in an EVPN/MPLS scenario, some mac-addresses might be pointed to dead next-hop in the forwarding-table. All further MAC-addresses learned using the same indirect next-hop or from the same remote PE will get rejected by the kernel too and will not be installed in the PFE anymore. This is only applicable if the routing-instance type is evpn. If the EVPN instances type is virtual-switch there is no exposure.
1442319 Traffic drop might be seen at EVPN Layer3 Gateway scenario
 
In EVPN-VXLAN Layer3 Gateway scenario, when some events occur (such as, IP/VM move, VRRP switchover and so on), the GARP (Gratuitous Address Resolution Protocol) packet is received with source Ether MAC different with inner ARP MAC, then it would move IP Route/NH (Next-Hop) into discard state in the forwarding-table. This causes traffic drop. The reason is that normally (as per design) MAC+IP is allowed to be learned after MAC is learned. But in this scenario the GARP is received before the inner MAC is learned. So it might result in reverse process and would move the ARP NH into the discard state. The fix is to drop ARP (or GARP) packets till the host/Server Mac is learned. This could avoid ARP entry moving into discard NH.
1443933 The localhost address is missing from the EVPN database and mac-ip-table
 
In the EVPN scenario, the localhost address is missing from the EVPN database and mac-ip-table when the vlan-id is removed and re-added in EVPN routing-instance. This issue will impact traffic/host reachability.
1455973 Instance type is changed from VPLS to EVPN and this results in packet loss
 
In VPLS to EVPN migration scenario, when the routing-instance type is changed from VPLS to EVPN, short-lived loss of traffic is seen.
1459830 ARP request/NS might be sent back to the local segment by DF router
 
Under EVPN multihoming mode, if ARP Request or Neighbor Solicitation (NS) message encapsulated in Dual Tagged VLAN arrives at the DF(designated forwarder) which may send it back to the local segment as it was, that might cause a loop and at last, overwhelms the device. Note: It will not happen with normal broadcast traffic. BDF(backup designated forwarder)does not have this behavior.
PR Number Synopsis Category:EX Chassis chassism/chassisd
1446363 Major alarm log messages for temperature conditions for EX4600 at 56 degrees Celsius
 
EX4600 will generate a major alarm once any sensor temperature is hit at 56 degrees celsius. This is incorrect behavior and can be resolved by upgrading version of code. **Note: Even though incorrect alarms are triggered, the chassis will still shut down gracefully when "fire shutdown" threshold is hit as seen in operational mode > show chassis temperature-thresholds.
PR Number Synopsis Category:Express PFE L2 fwding Features
1405786 Ping over loopback might not work over TYPE 5 tunnel on QFX10000 platforms
 
On QFX10000 platforms, in EVPN-VXLAN scenarios, ping between Spine to Spine loopback over TYPE 5 tunnel might not work.
PR Number Synopsis Category:Express pfe Mclag
1445939 On QFX10008 traffic impact might be seen when the JSRV interface is used
 
The JSRV is Juniper services interface and it is only used either for dot1x or captive portal scenario in QFX10008 platform. As the JSRV IFD (pysical interface) shares same port type with IRB interface, IRB IFD`s SMAC (source MAC) might be overwritten by JSRV IFD`s SMAC, then the QFX might discard the traffic. As a workaround, if disable dot1x, the JSRV interface won`t come up in the switch and then the traffic would recover.
PR Number Synopsis Category:SRX1500 platform software
1428657 Junos OS: SRX1500: Denial of service due to crash of srxpfe process under heavy traffic conditions. (CVE-2019-0050)
 
Under certain heavy traffic conditions srxpfe process can crash and result in a denial of service condition for the SRX1500 device. Repeated crashes of the srxpfe can result in an extended denial of service condition. The SRX device may fail to forward traffic when this condition occurs.
PR Number Synopsis Category:Kernel software for AE/AS/Container
1429917 The AE interface does not come up after rebooting the FPC/device though the physical member link is up
 
When a single FPC carries minimum 10 member links which belong to the same or different AE (Aggregate Ethernet) bundle, if one of the static AE bundle (LACP is not enabled) has disabled member link, this static AE interface does not come up after rebooting the FPC/device though it has physical member link with UP state.
1459692 In MC-LAG scenario traffic destined to VRRP virtual MAC gets dropped
 
When VRRP (virtual router redundancy protocol) is configured on MC-LAG (multichassis link aggregation groups), traffic destined to VRRP virtual MAC address might get dropped because the virtual MAC is not correctly programmed in PFE (packet forwarding engine).
PR Number Synopsis Category:ISIS routing protocol
1455994 Prefix SID conflict might be observed in ISIS
 
In an ISIS segment routing scenario, prefix SID(Segment Identifier) might conflict for internal prefixes. When ISIS L2 to L1 route leaking policy is used after NSR(Nonstop active Routing), it is observed that the L1/L2 router appears to be leaking some prefixes twice, second time setting SID and all flags to 0 due to which all the SIDs have conflicting values as '0' which might cause traffic loss.
PR Number Synopsis Category:jdhcpd daemon
1447323 The dhcp-relay knob might not work on MX10008/MX10016 platforms
 
On MX10008/MX10016 platforms, if the dhcp-relay knob is enabled under the forwarding-option hierachy, either in default or non-default routing-instance, the Dynamic Host Configuration Protocol (DHCP) relay feature might not work as expected. Due to this issue, all the DHCP discovery packets couldn't be relayed.
1453464 PPPoE holding DHCPv6 prefix causes DHCPv6 binding failure due to duplicate prefix
 
In subscriber management scenario deployed with DHCPv6 over PPPoE, if the DHCPv6 handshake process of one subscriber does not complete and fails, the prefix assigned will be freed back to the address-assignment pool and assigned to the next subscriber. But that prefix is incorrectly retained in the first subscriber's PPPoE session. Then if the first subscriber solicits DHCPv6 prefix again, the original prefix which is already assigned to the second subscriber will be requested, resulting in DHCPv6 bind failure due to duplicate prefix.
PR Number Synopsis Category:JFlow bug tracker for SRX platforms
1446996 The jflow version 5 stops working after changing input rate value.
 
The jflow version 5 stops working after changing "input rate" value. No sampling packet will be generated when this issue occurs. The issue will restore after system reboot.
PR Number Synopsis Category:Adresses ALG issues found in JSF
1387895 The SUN-RPC data traffic might be dropped after interface related configuration is changed.
 
On all SRX platforms, after interface related configuration is changed, for example, changing MTU on an interface, SUN-RPC data traffic for previously established Application Layer Gateway (ALG) sessions may be dropped because it matches the gate which contains old interface information.
PR Number Synopsis Category:Flow Module
1397744 Junos OS: SRX Series: Denial of Service vulnerability in srxpfe related to PIM (CVE-2019-0075)
 
A vulnerability in the srxpfe process on Protocol Independent Multicast (PIM) enabled SRX series devices may lead to crash of the srxpfe process and an FPC reboot while processing (PIM) messages.
PR Number Synopsis Category:Firewall Policy
1419983 The NSD process might stop due to a memory corruption issue
 
The NSD process might stop due to a memory corruption issue. As a result, security-related configurations cannot be committed on SRX Series device and core files are generated.
PR Number Synopsis Category:Security platform jweb support
1410401 Junos OS: Session fixation vulnerability in J-Web (CVE-2019-0062)
 
A session fixation vulnerability in J-Web on Junos OS may allow an attacker to use social engineering techniques to fix and hijack a J-Web administrators web session and potentially gain administrative access to the device. Please refer to https://kb.juniper.net/JSA10961 for more information.
PR Number Synopsis Category:Layer 2 Control Module
1450832 VLAN config change with l2ald restart might cause Kernel sync issues and impact forwarding
 
On all Junos platforms including MX, EX, QFX and SRX devices, VLAN config change with l2ald restart might cause Kernel sync issues and impact forwarding. The "show route forwarding table" may show dead BDs, MACs and the "show vlans extensive" may show the state as destroyed.
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:Multiprotocol Label Switching
1435014 The P2MP LSP branch traffic might be dropped for a while when the Sender PE is doing switchover
 
On a system with NSR enabled, if the RSVP P2MP LSP with multiple branches is used (NGMVPN is one of the typical scenarios), when bringing down one of the branches (for eg, bringing one of the receivers down -- one of the receivers withdraws interest), and then if doing switchover on ingress PE, some unexpected traffic drop might be seen for a while. The reason is that the withdraw P2MP branch will be deleted but backup RE could not update properly and the LSP is down on the backup RE. After switchover is done, there is no loss seen.
1445024 The rpd memory leak might be seen when the inter-domain RSVP LSP is in down state
 
In inter-domain RSVP (Resource Reservation Protocol) LSP (Label-switched Path) scenario, the rpd memory leak might be seen when the CSPF (Constrained Shortest Path First) tries to recompute the path for the "down" LSP which is due to no route or ERO is incorrectly configured. The issue might lead to rpd crash when the rpd is out of memory and results in traffic loss.
PR Number Synopsis Category:Multicast Routing
1457228 Few seconds of traffic drop might be seen on the existing receivers when another receiver joins/leaves
 
With "protocol igmp-snooping" configured, if some receiver joins/leaves a group, few seconds of traffic drop might be seen on the existing receivers.
PR Number Synopsis Category:Fabric Manager for MX
1451958 [MX] Error dropped packets seen on MQ/XM based MPC cards though there is no traffic flowing through the system
 
After fixing PR 1338647, Error dropped packets are seen on MQ/XM based MPC cards, though there is no traffic flowing through the system.
PR Number Synopsis Category:MX104 Software - PFE Microcode
1356657 The packets might be dropped when they go through MX104 built-in interface
 
If the packets are destined to specific MAC address (for example, if the last two octets are 0x1101, 0x1102, 0x1103, 0x1104, 0x1106, 0x1108, 0x1109, 0x110a and so on), they might be dropped on the remote-end device when going through the built-in 10-Gigabit Ethernet (xe-) ports on the MX104 device.
PR Number Synopsis Category:Track Mt Rainier RE platform software issues
1343680 i40e NVM upgrade support for PTX platforms
 
Adding support for i40e NVM upgrade in PTX3000 platforms
PR Number Synopsis Category:FreeBSD Kernel Infrastructure
1456668 Certain EX-series platforms might generate vmcore by panic and reboot
 
Certain EX-series platforms might generate vmcore by panic and gets reset. This is a rare case since it occurs only when JFE (Junos FreeBSD Extension) statistic- too_long_complete is incremented. user@host> show system core-dumps no-forwarding -rw-r--r-- 1 root wheel 283194368 DDMMYYY /var/crash/vmcore.direct
PR Number Synopsis Category:"ifstate" infrastructure
1437762 The CPU utilization on a daemon might keep around 100% or backup RE might crash in race conditions
 
The CPU utilization on a daemon might keep around 100% or backup RE might crash in race conditions (it may get hit or triggered at times by some churn in the system, no specific trigger).
PR Number Synopsis Category:IPv6/ND/ICMPv6 issues
1439887 Improve serviceability of error message "PFESVCS: Input IFL not found"
 
This is a minor modification and has no functionality change as the change is done to add more description to PFESVCS log message.
PR Number Synopsis Category:PFE Peer Infra
1448858 Interface attributes might cause high CPU usage of dcd
 
When the interface attributes are configured, this configuration might cause an error in the IRSD (IRSD syncing errors) and lead the CPU usage of dcd spike up. The convergence time of this interface will be impacted.
PR Number Synopsis Category:TCP/UDP transport layer
1449664 FPC might reboot with vmcore due to memory leak
 
On all Junos platforms, if the device is up for a long period (e.g. several weeks or months), there might be a slow memory leak happening in some error scenarios where an application tries to send some data on a stale TCP socket (e.g. short-lived TCP connections used by the mgd process), and this issue might lead to FPC reboot with vmcore files.
PR Number Synopsis Category:OSPF routing protocol
1432615 Per-Prefix LFA might not work as expected where the last hop needs to be protected on the penultimate node
 
On all Junos platforms working as the source node (e.g. node S) where Per-Prefix Loop Free Alternate (PP-LFA) is configured for Open Shortest Path First (OSPF) routing protocol, if the destination prefix is learned from two originator nodes (e.g. node E and node F) with different costs, and both originator nodes E and F are directly connected with the source node S, PP-LFA might not work as expected in such scenario where the last hop needs to be protected on the penultimate hop. Due to this issue, an improper backup nexthop might be selected which couldn't handle node failure case and micro-loop might be seen.
1459080 The rpd might crash when OSPF router-id gets changed for NSSA with area-range configured
 
The rpd crash might be observed due to modification of router-id in OSPF NSSA with area-range configured.
PR Number Synopsis Category:Used for tracking OVSDB software issues and features
1452149 Vgd core might happen when tunnel getting deleted twice
 
If OVSDB is enabled on the device, in a rare case, vgd (VTEP gateway daemon) core might be seen when a tunnel is getting deleted twice. It may cause OVSDB to not work properly.
PR Number Synopsis Category:Provider Backbone (PBB) EVPN PFE functionality on MX
1453203 The bridge mac-table age timer does not expire for rbeb interfaces
 
On MX-Series platforms with PBB-EVPN environment, the bridge mac-table age timer might not expire for rbeb interfaces when the MAC table reaches its aging time.
PR Number Synopsis Category:Issues related to PKI daemon
1419515 Junos OS: PKI key pairs are exported with insecure file permissions (CVE-2019-0073)
 
The PKI keys exported using the command "run request security pki key-pair export" on Junos OS may have insecure file permissions. This may allow another user on the Junos OS device with shell access to read them.
PR Number Synopsis Category:Chassis mgmt for all QFX systems - chassis MIB, alarms, CLI
1426737 The dcpfe/PFE might not start on AS7816-64X and QFX5K TVP platform devices
 
The dcpfe/PFE might not start on AS7816-64X and QFX5K TVP platform devices which results in all the interfaces going down.
1453821 "show chassis led" shows wrong status
 
"show chassis led" status outputs may not proper along with some port status
PR Number Synopsis Category:QFX Control Plane Kernel related
1423928 On QFX5K/QFX10K switches, packet drops might be seen for the traffic that has to go over type-5 overlay tunnel
 
On QFX10K/QFX5K switches, packet drops can occur for the traffic that has to use an EVPN type-5 overlay tunnel if the first FPC(FPC0) is down on the other end of the tunnel. In this case, the destination switch which has the FPC0 down receives the packet and drops it.
PR Number Synopsis Category:QFX Platform related (SYSLOG/ALARMS/miscellaneous)
1419536 libvirtMib_suba core seen during installation
 
libvirtMib_suba core might be observed during installation of images. There is no functional impact due to this core, since this core happens in the libvirtMib_subagent.
1457456 Over temperature SNMP trap messages are shown up after update even though the temperature are within the system thresholds
 
EX2300 and QFX series switches generate SNMP trap for high temperature after upgrading to any of the affected Junos software. This is due to a temperature threshold value being set incorrectly in the software, SNMP false trap related to temperature gets generated and results in "over temperature" logs.
PR Number Synopsis Category:QFX platform optics related issues
1337340 On QFX5100 platforms, LR4 QSFP can take up to 15 min to come up after VC reboot
 
On QFX5100 platforms, LR4 QSFPs might take take longer to come up than others (up to 15 minutes). This is a intermittent occurrence.
1402127 QSFP-100GBASE-SR4/LR4 might take a long time to come up after disabling interface or reboot
 
On QFX5110 platform with QSFP-100GBASE-SR4/LR4 port used, after disabling an 100G port and then enable the port again, or reboot the device, there is a long time delay (5-15 minutes) before the ports come up.
PR Number Synopsis Category:QFX PFE Class of Services
1445960 CoS classifier might not work as expected
 
On QFX5000 Series platforms(except for the QFX5100) in the VxLAN scenario, the traffic is not classified properly on the UNI interface which has multiple VLANs configured.
1453512 The classifier configuration doesn't get applied to the interface in an EVPN/VXLAN environment
 
On QFX5100/QFX5110/QFX5120/QFX5200/QFX5210 Series platforms with an EVPN/VXLAN scenario, the classifier might not be applied to the interface successfully and all traffic flows in the best-effort queue.
PR Number Synopsis Category:DHCP related Issues
1436436 DHCP discover packets sent to IP addresses in the same subnet as irb interface cause the QFX5110 to send bogus traffic out of dhcp-snooping enabled interfaces
 
When the DHCP discover packets are received with destination mac address of the device's irb interface, the packets are supposed to be dropped when dhcp snooping is enabled and DHCP relay and DHCP server are not configured.
PR Number Synopsis Category:Filters
1434941 L3 filters applied to PVLAN IRB interface may not work after ISSU
 
On QFX5K platform, when there are more than 15 L3 filters are configured and ISSU is performed, the filter applied to PVLAN (Primary VLAN) IRB interfaces might not work unless the filter is deleted and re-added.
PR Number Synopsis Category:QFX L2 PFE
1437295 The FPC might crash if both the AE boundle flapping on local device and the configuration change on peer device occur at the same time
 
On QFX platforms, the FPC might crash if both the AE (Aggregate Ethernet) boundle flapping on local device and the configuration change on peer device which can cause the interface down occur at the same time.
1439268 LACP MUX state struck in "Attached" after disabling peer active members when link protection is enabled on local along with force-up.
 
When lacp is configured with link protection and force-up on local, and peer is configured with link protection, disabling the active member on peer device causes LACP MUX state to be stuck in attached state. Issue is not seen if link protection is not configured on the peer device. The feature where link protection and force-up is configured on local and link protection is configured on peer is not qualified. It is mention in release note, so that it can be documented.
PR Number Synopsis Category:QFX L3 data-plane/forwarding
1386440 MLD snooping as MLD membership info will be overritten to only latest one in case of stream group is same with different source MLD version2
 
With MLD-snooping enabled and when we have two receivers in the same VLAN interested in the same group address but from a different source, traffic will be received on only one receiver which sent the lastest MLD report. This is because we do not install S, G routes in H/w when MLD snooping is enabled.
PR Number Synopsis Category:QFX EVPN / VxLAN
1432703 Outer VLAN tag may not be pushed in the egress VXLAN traffic towards the host for QinQ scenario
 
In EVPN-VXLAN with QinQ scenario, if the "encapsulate-inner-vlan" knob is configured on some VXLANs but not configured on some other VXLANs, and after an interface flap OR a configuration change, the switch may stop pushing the outer VLAN tag towards host for QinQ scenario.
1441690 The L3 communication might break on an interface which is configured with flexible-ethernet-services
 
On QFX5100/5200 switches when an interface is configured for both L2 and L3 units with flexible-ethernet-services encapsulation, L3 communication breaks and ARP resolution is affected if the hardware token used by L3 unit is same as a VLAN allowed over VxLAN on the L2 unit. This hardware token is randomly generated.
PR Number Synopsis Category:RPD Interfaces related issues
1460181 The "forwarding" option is missed in routing-instance type
 
On PTX10008/PTX10016/QFX10008/QFX10016 Series platforms, the "forwarding" option for routing-instance type configuration is missed, it might impact the function related to this configuration. For example, FBF won't work because of the missing configuration.
1460181 The "forwarding" option is missed in routing-instance type
 
On PTX10008/PTX10016/QFX10008/QFX10016 Series platforms, the "forwarding" option for routing-instance type configuration is missed, it might impact the function related to this configuration. For example, FBF won't work because of the missing configuration.
PR Number Synopsis Category:RPD Next-hop issues including indirect, CNH, and MCNH
1406070 The rpd might crash or duplicated routes might be seen if doing configuration change with BGP multipath and flapping routes
 
On all platforms, if doing configuration change (with BGP multipath) and flapping the IGP/LDP/RSVP routes simultaneously, the rpd crash or duplicated routes might be seen.
1424819 The rpd keeps crashing after changing configuration
 
In the ECMP (Equal-Cost Multipath) environment with existing more than 8 multipath for a given route, changing configuration (e.g. delete routing protocol IGP or LSP) is trying to delete a software structure which was already corrupted sometime earlier due to memory corruption, and this may cause the rpd to keep crashing. This issue applies to all types of nexthops with multipath.
PR Number Synopsis Category:RPD route tables, resolver, routing instances, static routes
1442952 The rpd might crash with SRTE configuration change
 
In BGP segment routing traffic engineering (SRTE) scenario, process rpd might crash when knob "extended-nexthop-color" is added or removed from the BGP configuration.
PR Number Synopsis Category:Generic platform and infra issues for MS-MIC and MS-MPC(XLP)
1405917 The FPC crash might be observed in MS-MPC HA environment
 
On MX-series platform with MS-MPC card used, in race condition, if the MS-MPC is used on HA (High Availability) scenario ( the 'set interfaces ms-x/x/x redundancy-options redundancy-peer/redundancy-local' knob and GRES is configured), the FPC might crash due to the bus error (segmentation fault). The reason is that when two CPUs simultaneously access the same session-extension memory in the session structure, one for writing, the other for reading. A reading CPU gets a wrong value and uses that as the memory address. This causes the bus error (segmentation fault).
PR Number Synopsis Category:SFW, CGNAT on MS-MIC/MS-MPC (XLP)
1446931 NAT service-set in certain scale might fail to get programmed
 
In NAT/stateful-firewall scenario using service PIC on MX platforms, the service-set might fail to get programmed after configuration commit if the configuration scale is in particular range hitting the issue.
1460027 The PPTP doesn't work with destination NAT
 
On the MX platform, if the PPTP control connection is established with destination NAT (network address translation), it will be failed. This issue will cause the PPTP traffic loss.
PR Number Synopsis Category:SRX Argon module bugs
1460619 The aamwd process exceeds 85% RLIMIT_DATA limitation due to memory leak
 
The aamwd process may exceed 85% RLIMIT_DATA limitation due to memory leak when there is a connection issue with the Sky ATP server. Below log indicates a connect error occurred which might result in a memory leak. aamwd[13569]: AAMWD_NETWORK_CONNECT_FAILED: <2> Access host srxapi.us-west-2.sky.junipersecurity.net on ip port 443 error
PR Number Synopsis Category:platform related PRs on SRX branch platforms
1449728 Junos OS upgrade fails when partition option is used.
 
Branch SRX device fails to upgrade Junos image when partition option is used.
1451860 The rpd process might crash and restart with an rpd core file created when committing the configuration
 
On SRX300/320/340/345 Series platforms, when the protocol (BGP/ISIS/OSPF) authentication-Key, Master system-password, and TPM password is configured, the rpd process might crash during committing the configuration on the device.
PR Number Synopsis Category:Issues related to broadband edge apps (PPP, DHCP) on Trio ch
1442527 In "enhanced-ip" or "enhanced-ethernet" mode with DCU (destination-class-usage) accounting enabled, MS-DPC may drop all traffic that should egress via ae interface
 
On MX platform with "enhanced-ip" or "enhanced-ethernet" mode enabled, if the ae interface is configured with DCU accounting, MS-DPC might drop all traffic that should go out via the interface.
PR Number Synopsis Category:Trio pfe stateless firewall software
1409879 FPC crash may be observed with scaled subscribers login attempts
 
In a subscriber management environment with scaled subscribers login such as 200k PPPoE subscribers, FPC crash may be observed.
PR Number Synopsis Category:Trio pfe bridging, learning, stp, oam, irb software
1434933 Traffic from the same physical interface can not be forwarded
 
In EVPN-MPLS scenario, if EVPN works at a logical interface while the ESI configured under the physical interface which the logical interface belongs, and if there are some other Layer 3 services (non-EVPN) using logical interfaces under the physical interface, then the traffic from any of these logical interfaces may not reach each other. Due to the ESI's split-horizon covers all logical interfaces of the physical interface, regardless whether the logical interface is used for EVPN.
1451559 In EVPN VXLAN scenario, sometimes host generated packets are getting dropped as hitting "reject route" in PFE
 
In EVPN VXLAN scenario, sometimes host generated packets are getting dropped as hitting "reject route" in PFE. For example, when you initiate the ICMP request sourced from EVPN instance's L3 GW irb address, the ICMP packet may not get out successfully in below scenario 1. control plane generated packet with overlay destination address (irb) belonging to one particular routing instance and the underlay (vtep) is on a different routing instance, This packet is inserted from control plane on the underlay's routing instance lookup which will fail leading to this control plane generated packet not go out. 2. When MPLS traffic engineering is enabled. The underlay vtep route in inet.0 will be labeled mpls route.
PR Number Synopsis Category:Trio pfe l3 forwarding issues
1354225 Trinity JNH memory leak when adding and removing unicast NH
 
Junos MPC memory leak when adding and removing unicast Next-hops
1381580 The unicast traffic from IRB interface towards LSI might be dropped due to PFE mismatching at egress processing
 
On all Junos with Trio platforms, the unicast traffic might get dropped when it is passed from an Integrated Routing and Bridging (IRB) interface towards label switch interface (LSI) if the Aggregation Ethernet (AE) load balancing adaptive or per-packet is configured.
PR Number Synopsis Category:Junos Automation, Commit/Op/Event and SLAX
1442248 SRX device fails to download dynamic-address feed from security director
 
If SRX device is configured to download dynamic-address feed from HTTPs server that configured by security director, the download processing will be failed. This issue causes the IP address contained in the list not be sent from SD to SRX device. If SRX device has policy referencing the IP address, they will not match passing-through traffic.
1445917 Python op scripts executed as user "nobody" if started from NETCONF session, not as logged in user, resulting in failing PyEZ connection to the device.
 
When executed over Junos CLI, Python op script is started as a separate process with the same user as the user which started the script.However, when the python op script is started from NETCONF session, the script started as a process from user "nobody". If the script is using PyEZ session to connect to the device and execute RPC commands, it will return the following error from Pyez: ConnectError(host: None, msg: user "nobody" does not have access privileges.). This is fixed by executing with the python op script with the same user as the user from the NETCONF session which invoked op script. This means that the behavior from CLI and NETCONF sessions are the same.
PR Number Synopsis Category:Configuration management, ffp, load action
1407848 The "show configuration" and "rollback compare" commands causing high CPU
 
If scaled config of interfaces and filters are configured, the CPU usage hits 100% for a few seconds while running "show configuration" or "show system rollback compare " commands.
PR Number Synopsis Category:UI Infrastructure - mgd, DAX API, DDL/ODL
1431198 Error might be observed when using a script to load-configuration
 
Multiple delete of a non existing config statements produces errors via rpc load-configuration.
Modification History:
First publication date 2019-11-22
Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search