Alert Type

SRN - Software Release Notification
Low/NotificationSoftware Release Notification
Low/NotificationSoftware Release Notification

Product Affected

ACX, EX, MX, PTX, QFX, NFX, SRX, VRR, vMX, vSRX

Alert Description

Junos Software Service Release version 18.2R3-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

Solution

Junos Software service Release version 18.2R3-S7 is now available.

18.2R3-S7 - List of Fixed issues

PR NumberSynopsisCategory: EX4300 PFE
1538401LLDP neighborship might not come up on EX4300 non-aggregated Ethernet interfaces.
Product-Group=junos		On EX4300 platform, LLDP might not work on non-AE (Aggregated Ethernet) interfaces. However, it works fine for AE interfaces.
1548858The targeted-broadcast feature may not work after a reboot
Product-Group=junos		On EX4300 Series platforms, the targeted-broadcast feature may not work after a reboot. It can be seen that no target-broadcast packets are received on the targeted-broadcast interface.
PR NumberSynopsisCategory: EX2300/3400 PFE
1472350CoS 802.1p bits rewrite might not happen in Q-in-Q mode
Product-Group=junos		In EX2300/EX3400 platform with CoS rewrite scenario, if an 802.1p bits (single VLAN) rewrite is used for an SVLAN (outer VLAN) of Q-in-Q, the rewrite will do nothing. Due to the PFE can not parse the firewall rule for given filter match conditions. Therefore, some traffic processing does not work as customer's expectation. Note: EX4300 has no this issue.
1556198Traffic might be dropped when a firewall filter rule uses 'then vlan' as the action
Product-Group=junos		If a firewall filter is configured with the action 'then vlan' on EX and QFX platforms, some of the traffic that matches the firewall filter might be dropped.
PR NumberSynopsisCategory: EX2300/3400 platform
1536408On the EX2300 device, the following PoE message is observed: poe_get_dev_class: Failed to get PD class info.
Product-Group=junos		Moved POE messages to informational level: "poe_get_dev_class: Failed to get PD class info"
PR NumberSynopsisCategory: QFX L3 data-plane/forwarding
1463092When deleting IRB on the layer 3 gateway, IRB does not get removed from PFE and will blackhole traffic to IRB mac address
Product-Group=junos		On QFX5110/5120 platform as the layer 3 gateway, after deleting the configuration of interfaces irb, The IRB might not get removed from PFE and will blackhole traffic to the MAC address of the deleted IRB.
1486632On the QFX 5100-48T-6Q Virtual Chassis or Virtual Chassis fan, the following error message is observed while copying the image to the Virtual Chassis fan member and trying to downgrade the image: rcp for member 14, failed.
Product-Group=junos		On QFX 5100-48T-6Q VC/VCF, RCP error might be seen while upgrading the system using "request system software add  no-validate" and system upgrade/ installation could fail. This issue happens if DCPFE cpu utilization is very high.
PR NumberSynopsisCategory: CoS support on ACX
1522941The show class-of-service interface command does not show classifier information.
Product-Group=junos		This is a display issue. Due to misread in PFE registers, classifier is not shown in "show class-of-service interface" output
PR NumberSynopsisCategory: JUNOS kernel/ukernel changes for ACX
1481151Memory utilization enhancement is needed.
Product-Group=junos		RPD memory chunk size is optimized for the ACX platform to reduce the memory footprint.
PR NumberSynopsisCategory: ACX GE, 10GE, PoE, IDT framers
1523418Interface does not come up with the auto-negotiation setting between the ACX1100 router and the other ACX Series routers, MX Series routers and QFX Series switches as the other end.
Product-Group=junosvae		When QFX5100/5110 is connected to other devices with 1G/10G ports, both sides configuring auto-negotiation and the remote interface might stay down.
PR NumberSynopsisCategory: BBE interface related issues
1447493bbe-smgd core file on backup Routing Engine in bbe_ifd_add_vlan (ifd=0x8c3e835, ifl=0xcaf59f18) at ../../../../../../src/junos/usr.sbin/bbe-svcs/smd/infra/bbe_ifd.c:6374.
Product-Group=junos		When a logical interface with vlan is deleted from the master Routing Engine (master RE), the backup RE does not process the removal correctly. When a new vlan logical interface is added after the removal, the bbe-smgd process on the backup RE may panic.
PR NumberSynopsisCategory: BBE Layer-2 Bitstream Access
1551207The PPPoE subscribers might fail to login.
Product-Group=junos		In Broadband Network Gateway (BNG) scenario where Layer-2 Bitstream Access (L2BSA) and PPPoE subscribers are working on the same interface/VLAN, PPPoE subscribers login may get stuck in a pending state, if the IN-FLIGHT flag of L2BSA is not cleared after its Port-Up packet is rejected by RADIUS, and during this process, another Port-Up for the same access-loop arrives.
PR NumberSynopsisCategory: MIBs related to BBE
1535754Snmp mib walk for jnxSubscriber OIDs returns General error
Product-Group=junos		Snmp mib walk for jnxSubscriber OIDs returns General error
PR NumberSynopsisCategory: Border Gateway Protocol
1431536Unsupported configuration (EPE with dynamic-next-hop GRE tunnels) continuously rpd to generat core files.
Product-Group=junos		If the knob "egress-te" is configured under the EBGP (External Border Gateway Protocol) VRF (Virtual Routing and Forwarding) routing-instance, the rpd process might crash continuously during the EBGP peer establishing. The routing protocols might be impacted and traffic disruption might be seen during the rpd crash and restart.
1466709BGP peers might flap if the parameter of hold-time is set small.
Product-Group=junos		On all Junos platforms with BGP enabled, the hold timer is still running when the session is to processing BGP updates to peers, but the keepalive messages which BGP peer sends might be skipped. If the BGP updates in handling cannot be completed within the hold timer (e.g., manually sets the hold-time to 3s), the BGP peer flaps might be observed.
1482209The BGP multipathed traffic might not fully load-balance for a while after adding a new path for load sharing.
Product-Group=junos		On all Junos platforms with the BGP-ECMP (Equal Cost Multi-Path) scenario, if adding a new path for load sharing, the traffic might not fully load-balanced for a while. The worst-case scenario is much traffic moving to the new path and lead to a link oversubscription.
1487486The rpd might crash with BGP RPKI enabled in a race condition
Product-Group=junos		On all Junos platforms with BGP PRKI (Resource Public Key Infrastructure) scenario, if NSR is enabled and scale routes and ROAs exist, in a very rare case, the ROA (route origin authorization) might be withdrawn before replicating to the backup RE when ROA changes happen, which results in the rpd crash.
1517498The rpd might crash after deleting and re-adding a BGP neighbor.
Product-Group=junos		In BGP scenario on all Junos platforms, after deleting and re-adding a BGP neighbor, the rpd might crash due to a rare timing issue.
1518056Tag matching in the VRF policy does not work properly when the independent-domain option is configured.
Product-Group=junos		On all platforms and in an L3VPN environment, when the tag is configured in the policy and applied to the VRF instance, configuring 'independent domain' for the autonomous system under the routing-options will cause the inet-vpn routes stop getting advertised between VRF instances.
1532414Transit labels for Layer 3 VPN routes are pushed momentarily to the MPLS.0 table.
Product-Group=junos		In L3VPN scenario with in-line RR (Route Reflector) which has an export policy with next-hop self to advertise all transit L3VPN routes to its clients and also uses route-target family, the undesired L3VPN routes may be pushed to FIB (Forwarding Information Base) after enabling/disabling route-target family on the RR or a new BGP peer joins a group with 'next-hop self'.
1538491Configuring then next hop and then reject on a route policy for the same route might cause the rpd process to crash.
Product-Group=junos		On all Junos platforms with BGP enabled, if a policy is setting 'then next-hop' and 'then reject' at the same time for the same prefix, rpd crash might be seen. Like the following: set policy-options policy-statement xxx term 1 from route-filter xxx set policy-options policy-statement xxx term 1 then next-hop ... set policy-options policy-statement xxx term 2 then reject
PR NumberSynopsisCategory: Track PRs in BGP Flow Spec area & is part of BGP inside RPD.
1539109Junos OS and Junos OS Evolved: Upon receipt of a specific BGP FlowSpec message network traffic may be disrupted. (CVE-2021-0211)
Product-Group=junos		Upon receipt of a specific BGP FlowSpec message network traffic may be disrupted. Please refer to https://kb.juniper.net/JSA11101 [juniper.net] for more information.
PR NumberSynopsisCategory: BBE Remote Access Server
1474180Some address relevant fields are missing when executing "test aaa ppp" command.
Product-Group=junos		After upgrade software 18.4R2,"test aaa ppp" command output can't see "Client IP Address" field.
PR NumberSynopsisCategory: PTX Chassis Manager
1441256On the PTX1000 or PTX10002 devices, the PIC and interfaces might not come up after FPC reboot.
Product-Group=junos		On PTX1000/PTX10002 platforms, PIC and interfaces might not come up after FPC reboot even FPC is in online status.
PR NumberSynopsisCategory: MX Platform SW - UI management
1537194The chassisd memory leak might cause traffic loss.
Product-Group=junos		On MX/PTX platforms with 18.1 or higher release, chassisd memory leak may be caused by configuration commit. When chassisd consumes ~3.4GB of memory it may crash, chassisd crash may cause GRES or/and FPC restart. If GRES is enabled, commits are being synchronized between REs, so backup RE chassisd may suffer from memory leak too.
PR NumberSynopsisCategory: Device Configuration Daemon
1544257Subscribers might logout then login after loopback address is changed
Product-Group=junos		On MX platform, under subscriber environment and unnumbered IP address borrowed from the loopback interface configured on Demux interface and Aggregated Ethernet (AE) interface, subscriber session might flap if IP address of the loopback interface IP is changed. Please refer to workaround provided when this issue hit.
PR NumberSynopsisCategory: This is for all defects raised against dns-proxy feature
1512212Junos OS: SRX Series: ISC Security Advisory: BIND does not sufficiently limit the number of fetches performed when processing referrals (CVE-2020-8616)
Product-Group=junos		On Juniper Networks Junos OS SRX Series devices an uncontrolled resource consumption vulnerability in BIND may allow an attacker to cause a Denial of Service (DoS) condition. When these devices are configured to use DNS Proxy, these devices do not sufficiently limit the number of fetches performed when processing referrals. In order for a server performing recursion to locate records in the DNS graph it must be capable of processing referrals, such as those received when it attempts to query an authoritative server for a record which is delegated elsewhere. In its original design BIND (as well as other nameservers) does not sufficiently limit the number of fetches which may be performed while processing a referral response. A malicious actor who intentionally exploits this lack of effective limitation on the number of fetches performed when processing referrals can, through the use of specially crafted referrals, cause a recursing server to issue a very large number of fetches in an attempt to process the referral. Refer to https://kb.juniper.net/JSA11090 [juniper.net] for more information.
PR NumberSynopsisCategory: Covers Application classification workflows apart from custo
1455465The traffic loss might occur when application service is configured
Product-Group=junosvae		On vSRX3.0 platforms, traffic loss might occur when application service is configured.
PR NumberSynopsisCategory: Ethernet OAM (LFM)
1500048The fpc process might crash in the inline mode with CFM configured.
Product-Group=junos		On the Junos platforms with inline mode CFM (Connectivity Fault Management) configured, if there are several CFM adjacencies flapping, due to the flaw in the CFM module to process the error-adjacencies messages, the FPC may crash alongside with NPC core-dump file generated. All services/traffic configured on the FPC will see outage till FPC recovers from an automatic reboot.
PR NumberSynopsisCategory: EVPN control plane issues
1547275VLAN ID information is missed while installing the EVPN route from the BGP Type 2 Route after modifying a routing-instance from instance-type EVPN to instance-type virtual-switch.
Product-Group=junos		VLAN ID information might be missing while installing the EVPN route from the BGP Type 2 Route after modifying a routing-instance from "instance-type evpn" to "instance-type virtual-switch". As a result, the data traffic sent via these EVPN routes doesn't push vlan-id in the inner Ethernet Header. This might result in traffic getting discarded on the remote PE.
PR NumberSynopsisCategory: EVPN Layer-2 Forwarding
1535515All the ARP reply packets toward some address are flooded across the entire fabric.
Product-Group=junos		In the EVPN-VXLAN scenario, if the spine has irb and the leaves don't have irb, and the leaves have multi-home interfaces, the ARP reply packets flooding across the entire fabric might be seen.
PR NumberSynopsisCategory: Integrated Routing & Bridging (IRB) module
1484721ARP entry might not be created in the EVPN-MPLS environment.
Product-Group=junos		In the EVPN-MPLS environment, if a VLAN is created without having it in "protocols evpn extended-vlan-list", then adding it, the ARP entry may not be created on the device even it receives the ARP packets through the newly added VLAN.
PR NumberSynopsisCategory: ISIS routing protocol
1463650IS-IS IPv6 multi-topology routes might flap every time when there is an unrelated commit under protocol stanza.
Product-Group=junos		With multi-topology enabled in ISIS globally hierarchy level, if some ISIS interfaces don't have IPv6 address, all ISIS IPv6 routes flap when committing any change under protocol stanza (e.g. 'protocol pim traceoption').
1482983The output of the show isis interface detail command might be incorrect if wide-metrics-only is enabled for IS-IS and the ASCII representation of the metric in decimal is more than 6 characters long.
Product-Group=junos		If 'wide-metrics-only' is enabled for any IS-IS level and a metric configured on the IS-IS enabled interface for that level has ASCII representation in decimal more than 6 characters long, this interface's metric for that level will be merged with 'priority' field value in the output of 'show isis interface detail'.
1526447The IS-IS LSP database synchronization issue might be seen while using the flood-group feature.
Product-Group=junos		On all Junos platform, when flood-group is configured on interface under isis, if isis LSPs time out and then come up, the device sends only self-generated LSPs and doesn't increment the LSP updates received from neighbor which flapped. This is causing LSP database out of synchronization issue.
PR NumberSynopsisCategory: jdhcpd daemon
1429456The DHCP DECLINE packets are not forwarded to the DHCP server when forward-only is set within dhcp-reply.
Product-Group=junos		If forward-only is set within dhcp-reply in a Juniper Networks device as a DHCP relay agent, the DHCP DECLINE packets that are broadcasted from the DHCP client are dropped and not forwarded to the DHCP server.
1453464PPPoE holding DHCPv6 prefix causes DHCPv6 binding failure due to duplicate prefix.
Product-Group=junos		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 NumberSynopsisCategory: Firewall Policy
1482200Request security policies check output shows policies out of syn command.
Product-Group=junos		This issue affects an SRX system with large security policies (reproduced with 8000 policies). The result of the "request security policies check" cli command may display policies in the "out-of-sync" instead of "in-sync" state.
1544554The flowd or srxpfe process might crash when an SRX Series or NFX Series device running Junos OS Release 18.2R1 or later supports the unified policy feature.
Product-Group=junos		On SRX Series device running on Junos OS 18.2R1 or above, or NFX Series device running on NextGen Junos OS, the unified policy feature is supported, the flowd/srxpfe might crash.
PR NumberSynopsisCategory: lacp protocol
1277144LACP is not sending IFF_DOWN reason with destroy session request
Product-Group=junos		In current scenario when interface is going down then LACPD is not sending reason for destroy session request i.e IFF_DOWN(interface down). So the LACP session may not be destoried immediately until the LACP session times out.
1366825The RG1 interface failover occurs when RG0 failover is triggered.
Product-Group=junos		RG1+ which is configured for interface-monitor, might fail over to the other node if RG0 failover is triggered.
PR NumberSynopsisCategory: Label Distribution Protocol
1527197LDP routes might be deleted from MPLS routing table after RE switchover
Product-Group=junos		On all Junos platforms with NSR and segment routing for ISIS configured, LDP routes might be deleted on new master RE's MPLS routing table after RE switchover.
1538124The rpd process might crash when the LDP route with indirect next hop is deleted on the aggregated Ethernet interface.
Product-Group=junos		If the Label Distribution Protocol (LDP) route with indirect next-hop exists (e.g. LDP egress-policy is used to advertise BGP route into LDP), the rpd might crash when the LDP route is deleted from the AE interface.
PR NumberSynopsisCategory: lldp sw on MX platform
1538482DUT did not receive the LLDP packet from phone.
Product-Group=junos		On EX4300 platforms, the LLDP (Link Layer Discovery Protocol) neighborship with the VoIP (Voice over Internet Protocol) phones can't be established when LLDP is configured on the PoE (Power over Ethernet) enabled port on EX4300 and connects to the VoIP Phone.
PR NumberSynopsisCategory: PTX1000 platform
1460406PTX1000 and PTX10002 routers might get drop or discarded after transient SIB or FPC voltage alarms.
Product-Group=junosvae		On PTX1000 and PTX10002 platforms, if transient voltage fluctuations on a SIB or an FPC are seen, it might trigger the fabric healing process (FHP) and FPC/SIB restart. Later, the SIB might not restart but the FPC still goes online, so the device might experience silent dropping of packets, which affects the service.
PR NumberSynopsisCategory: Multicast Routing
1555518Sending multicast traffic to downstream receiver on Trio based Virtual Chassis platforms might fail.
Product-Group=junos		On Trio based Virtual Chassis (VC) platform, when there are multicast tunneled packets being received, which come into the Virtual Chassis Ports (VCP) and then pop out of the tunnel, if the VCP ports and the interfaces where multicast packets enter/leave the router are located on the same Packet Forwarding Engine (PFE), it might fail in sending multicast traffic to downstream receiver due to this issue.
PR NumberSynopsisCategory: OS IPv4/ARP/ICMPv4
1496429Routing Engine crash might be seen when a large number of next hops are quickly deleted and readded in large ARP/ND scale scenario.
Product-Group=junos		On all Junos platforms with large ARP/ND scale scenario, if a large number of nexthops are deleted and re-added very quickly (such as a result of link flap), the memory corruption might occur and eventually cause RE crash.
1511833The kernel might crash causing the router or the Routing Engine to reboot when performing virtual IP related change.
Product-Group=junos		On all Junos platforms with VRRP enabled, if delete and add any configuration which involves the virtual IP in the same commit, the kernel might crash. When this happens, the system or the RE will reboot.
1544398ARP expired timer on backup RE is not same with master RE if aging-timer is configured
Product-Group=junos		If aging-timer is configured on master RE for an IRB interface, the ARP timer configuration is not synced properly to backup RE for the IRB interface. It might cause ARP storm after RE switchover.
PR NumberSynopsisCategory: "ifstate" infrastructure
1545463Continuous rpd errors might be seen and new routes will fail to be programmed by rpd
Product-Group=junos		In case of high route churn in the network, all kuackmem (Kernel ACK mechanism) entries may be exhausted as a result of a rare timing issue and any new routes will fail to get programmed by rpd.
PR NumberSynopsisCategory: OSPF routing protocol
1525870The OSPFv3 adjacency should not be established when IPsec authentication is enabled.
Product-Group=junos		On EX4300 platforms, the OSPFv3 configured with IPsec authentication after device reboots, the OSPFv3 adjacency should not be established, while do the same configuration before device reboots, the adjacency should be established.
PR NumberSynopsisCategory: vMX Platform Infrastructure related issue tracking
1548422Traffic with jumbo frame may be discarded on the vMX platforms
Product-Group=junos		On the VMX platforms which are installed on ESXI 6.7 with vmxnet3 driver, traffic with jumbo frame (Packets with MTU more than 1500) may be discarded upon receiving.
PR NumberSynopsisCategory: Interface related issues. Port up/down, stats, CMLC , serdes
1538340Interfaces are not created after channel-speed 10g is applied across ports 48 to 53 on QFX5100-48T
Product-Group=junos		After channelizing port 48 through 53 and channel speed, the interfaces are down on QFX5100-48T platform. This issue causes interfaces are deleted and traffic might be dropped.
PR NumberSynopsisCategory: QFX Platform related (SYSLOG/ALARMS/miscellaneous)
1520956QFX5100: cprod timeout triggers high CPU (100%)
Product-Group=junos		In QFX5100, you might get into a high CPU (CPU running at 100%) situation when a "cprod" command timed out.
PR NumberSynopsisCategory: QFX L3 data-plane/forwarding
1484440IRB MAC will not be programmed in hardware when MAC persistence timer expires
Product-Group=junos		On QFX5XXX/EX46XX virtual chassis platforms with GRES, if an IRB interface is configured with members across master and backup REs, and when mac-persistence-timer expires, the new MAC address of the IRB interface might not be programmed in hardware, which might result in failure on protocols and traffic.
1512712Display issue, Virtual Chassis environment, Configured num-65-127-prefix value is shown incorrect for the command O/P "show chassis forwarding-options"
Product-Group=junos		Display issue, In a Virtual Chassis environment, Configured num-65-127-prefix value is shown incorrect for the command O/P "show chassis forwarding-options" for the FPC which is not local (Backup and line card members of the VC)
PR NumberSynopsisCategory: QFX VC Infrastructure
1548079Backup RE clears the reporting alarm for a PEM failure intermittently for a missing power source on a QFX5100 VC
Product-Group=junos		The PEM failure alarm for a missing power source on a QFX5100 VC is incorrectly being toggled on the Backup RE
PR NumberSynopsisCategory: RPD Next-hop issues including indirect, CNH, and MCNH
1242589In a BGP or MPLS scenario, changing events about the next hop interface MPLS family might cause the route to be in the Dead state
Product-Group=junos		In a BGP or MPLS scenario, if the next-hop type of label route is indirect, then the following changing events about the next-hop interface MPLS family might cause the route to be in the Dead state, and the route remains in that state even when the family MPLS is again activated: Deactivating and activating the interface family mpls. Deleting and adding back the interface family mpls. Changing maximum labels for the interface. When a labeled route is resolved over an interface, that interface must have family mpls configured for the route to be successfully resolved. Otherwise, the route does not get resolved.
1458595The rpd crash might be seen if BGP route is resolved over the same prefix protocol next-hop in inet.3 table that has both RSVP and LDP routes.
Product-Group=junos		In race condition, if a BGP route is resolved over the same prefix protocol next hop in a routing table that has routes of the prefix from different routing protocols, when the routes are flapping (firstly these routes are down and then up), the BGP route will be re-resolved, and then the rpd crash might be seen.
1534455Some routes might get incorrectly programmed in the forwarding table in the kernel which is no longer present in rpd.
Product-Group=junos		In a scaled routes scenario, if there is any route change operation when the system is under memory pressure, the rpd might change a route entry but the same is not conveyed to the kernel. This causes a mismatch between routes in rpd and kernel leading to traffic blackhole for the mismatched route entries that are incorrectly programmed in the kernel.
PR NumberSynopsisCategory: RPD policy options
1523891The policy configuration might be mismatched between the rpd and mgd process when deactivate policy-options prefix-list is involved in the configuration sequence.
Product-Group=junos		If "deactivate policy-options prefix-list" is involved in configuration sequence along with other policy configurations, the mgd process might not notify the rpd process about the policy configuration changes after committing the configuration. This can cause the policy configuration to be out-of-synchronization between policy database used by rpd and configuration database used by mgd. Due to the missing policy entries in policy database, later the rpd might crash when accessing these entries via CLI command like "show policy".
PR NumberSynopsisCategory: RPM and TWAMP
1541808The rmopd process memory leak might be seen if TWAMP client is configured
Product-Group=junos		If TWAMP (Two-Way Active Measurement Protocol) client is configured, memory leak in rmopd process may be observed after executing "request services rpm twamp start client" command.
PR NumberSynopsisCategory: jflow/monitoring services
1517646The srrd process might crash in a high route churns scenario or if the process flaps.
Product-Group=junos		On all Junos OS platforms with inline Jflow enabled, the sampled route reflector process (srrd) might crash in a scenario where there are high route churns or flaps in the system. This is a rare timing issue and because of the crash, the Jflow export might report older route information for sometime.
PR NumberSynopsisCategory: MPC7/8/9 Interface Issues
1490531The MPC might crash due to the PHY interface driver issue of MIC in MX2K or MX10003 platform
Product-Group=junos		In MACSEC TIC (TerABIT INTERFACE CARD) with MX2K or 10003 scenarios, if the IFD is detached or attached when interface flaps, the PHY interface driver issue might happen in some corner cases. Then these flapped IFD might cause PFEMAN thread crash on PFE and the MPC where it is located might crash soon afterward.
PR NumberSynopsisCategory: MX10003/MX204 Linux issues (including driver issues)
1492121The MX10003 router might shut itself down automatically after the system upgrades or downgrades.
Product-Group=junosvae		On the MX10003 platform, if we upgrade or downgrade Junos software from a set of original releases to a set of target releases, the system might detect incorrect temperature values and shutdown. The set of the original releases are: Junos 18.2R3, 18.3R3, 18.4R2, 19.1R2, 19.2R1, 19.3R1. The set of the target releases are: Junos pre-18.2R3, pre-18.3R3, pre-18.4R2, pre-19.1R2, pre-19.2R1, and pre-19.3R1 releases
PR NumberSynopsisCategory: Trio LU, IX, QX, MQ chip drivers, ucode & related SW
1388998Reclassify the severity of XM wicpq free pointer SRMA (0x07032C) from major to minor
Product-Group=junos		A parity error for wicpq free pointer SRAM (0x07032c) on XM chipsets based FPC is set to a major CM ALARM and invokes disable-pfe(packet forwarding engine) action. Actually WI CPQ Free Pointer SRAM Protect alone does not cause operational impact. So creating a new CMERROR XMCHIP_CMERROR_WI_WICPQ_FREEPTR_SRAM_PAR_PROTECT_FSET_REG_DETECTED_WICPQ_FREEPTR_SRAM with severity minor is a better solution.
PR NumberSynopsisCategory: Trio pfe bridging, learning, stp, oam, irb software
1502867Traffic originated from another subnet is sent out with 0x8100 instead of 0x88a8.
Product-Group=junos		On the MX platforms with MPC7/8/9 installed, when an interface configured with vlan-tags outer tpid (tag protocol ID) 0x88a8 on these line cards, traffic originated from another subnet will be sent out with 0x8100. It will cause traffic to get dropped at the remote site.
1533767PPE errors/traps might be observed in L2 flooding scenarios
Product-Group=junos		On Junos platforms with MPC1~4/MPC-3D-16XGE/T4000-FPC5/ EX9200-4QS/EX9200-2C-8XS/EX9200-MPC/EX9200-32XS/ SRX5K-SPC-4-15-320/SRX5K-MPC, when broadcast/multicast packets from access as transit traffic flooding in a bridge-domain (for example: multicast OSPF packets entering EVPN instance, these OSPF packets are being handled as transient packets), all packets except IPv6 NS (Neighbor Solicitation) might be dropped because of traps.
1533857The fpc process might crash when the next hop memory of ASIC is exhausted in the EVPN-MPLS scenario.
Product-Group=junos		On all MX/EX92xx platforms with EVPN-MPLS configured, NH (Next-Hop) memory leak in Trio ASIC happens whenever there is a route churn for remote MAC-IP entries learned bound to the IRB interface in EVPN-MPLS routing-instance. When the ASIC's NH memory partition exhausted (free% NH memory is close to 20% or below), which will result in the line card to reboot.
1542211Trio-based FPC might crash when the underlying Layer 2 interface for ARP over IRB interface is changed from the physical interface to the LSI interface.
Product-Group=junos		This issue applies to a Trio-based FPC using the integrated routing and bridging (IRB) interface with a VPLS instance using the label-switched interface (LSI) to provide VPLS functionality. The FPC may restart unexpectedly. The restart is triggered when the underlying layer-2 interface for ARP over IRB interface changes from the physical interface to the LSI interface.
PR NumberSynopsisCategory: Trio pfe l3 forwarding issues
1478279FPC memory leak might happen after executing show pfe route.
Product-Group=junos		On all Junos OS platforms, if the command "show pfe route " is executed to dump the Packet Forwarding Engine (PFE) routes, and then the routes get deleted by some events (for example, Virtual Routing and Forwarding (VRF) configuration removal or Border Gateway Protocol (BGP) flap), the FPC memory leak might happen due to this issue. In large scaled scenario, the memory leak will increase by a large amount, which might be easier to cause FPC crash.
PR NumberSynopsisCategory: Issues related to port-mirroring functionality on JUNOS
1542500Port mirroring with maximum-packet-length configuration does not work over the GRE interface
Product-Group=junos		Port mirroring with maximum-packet-length configuration does not work over GRE interface on MX204. While constructing GRE header, the clipping aspect of inner packet was not accounted earlier. If the inner packet is truncated, the outer GRE header packet size must use the new size (clipped size) to calculate the total length of outer header.
PR NumberSynopsisCategory: Trio pfe microcode software
1396311Non impacting errors@clear_app_mem_active(XXXX): Clr Memory-0x02 at 0xXXXXXX. owned by 0xXX
Product-Group=junos		Below non-impacting errors are seen while freeing BNG related memory. There would not be any memory leak due to this. Customer can safely ignore these errors.
PR NumberSynopsisCategory: Authentication, Authorization, Accounting, PAM (RADIUS/tacplus)
1478959SSH login might hang and the TACAS + server closes the connection without sending any authentication failure response.
Product-Group=junos		On all Junos OS platforms, the SSH login session might hang if the Junos OS device is sending an authentication request to the TACACS+ server with an incorrect secret and the TACACS+ server closes the connection without sending any authentication response.
PR NumberSynopsisCategory: Issues related to Logging/Tracing, errmsg, eventd infrastruc
1380777event-policy generated traps are sent with UTC, even though timezone defined under system hierarchy
Product-Group=junos		event-policy generated traps are sent with UTC, even though timezone defined under system hierarchy
PR NumberSynopsisCategory: Virtual Router Redundancy Protocol
1526851When SRX Series devices receive proxy ARP requests on VRRP interfaces, SRX Series devices send ARP replies with the underlying interface MAC address.
Product-Group=junos		On SRX Series devices with VRRP scenario, the proxy ARP reply uses interface MAC address instead of VRRP MAC address if the VRRP is configured on some IFL and the proxy-arp is configured on same IFL, traffic loss may occur.
 

18.2R3-S7 - List of Known issues

PR NumberSynopsisCategory: EX2300 Hardware
1369924EX2300 - Watchdog reset is shown as Swizzle
Product-Group=junos		On EX2300, when watchdog is induced, the last reboot reason is shown as Swizzle Reboot.
PR NumberSynopsisCategory: SFI Infra-structure
1485038The following error message is observed continuously in AD with base configurations: IFDE: Null uint32 set vector, ifd and IFFPC: 'IFD Ether uint32 set' (opcode 151) failed.
Product-Group=junos		EX 9251 Summit-B54 : "IFDE: Null uint32 set vector, ifd and IFFPC: 'IFD Ether uint32 set' (opcode 151) error message is observed continuously in AD with base configurations.
PR NumberSynopsisCategory: Marvell based EX PFE ACL
1434927The FPC crashes with pfem generating core file might be seen if large-scale number of firewall filters are configured.
Product-Group=junos		On EX Series switches, If you are configuring a large-scale number of firewall filters on some interfaces, the FPC might crash and generate core files.
PR NumberSynopsisCategory: Marvell based EX PFE MISC
1232403HSRPv2 IPv6 packets might get dropped if IGMP-snooping is enabled.
Product-Group=junos		On EX Series switches except EX4300/EX4600/EX9200, an interface is configured for single vlan or multiple vlans, if all these vlans of this interface have igmp-snooping enabled, then this interface will drop HSRPv2 (Hot Standby Router Protocol for IPv6) packets. But if some vlans do not have igmp-snooping enabled, then this interface is working fine.
PR NumberSynopsisCategory: EX2300/3400 VC
1444595A FPC may not be shown in the output by "show chassis routing-engine" in EX3400-VC
Product-Group=junos		A FPC may not be shown in the output by "show chassis routing-engine" and also SNMP OID "jnxOperatingCPU" in EX3400-VC. Some "show commands" like "show chassis hardware detail", "show chassis fpc" indicate fpc0 as expected. In this example, the Virtual Chassis configuration has two ex3400 switches and fpc0 is a master role. root@ex3400VC> show chassis routing-engine | no-more ------------<<<<<<<< FPC 0 missed Routing Engine status: Slot 1: Current state Backup Temperature 34 degrees C / 93 degrees F CPU temperature 34 degrees C / 93 degrees F DRAM 1950 MB Memory utilization 14 percent 5 sec CPU utilization: User 5 percent Background 0 percent Kernel 3 percent Interrupt 0 percent Idle 92 percent Model RE-EX3400-24T Serial ID BUILTIN Start time 2019-03-26 17:22:44 CST Uptime 84 days, 22 hours, 1 minute, 59 seconds Last reboot reason 0x1:power cycle/failure Load averages: 1 minute 5 minute 15 minute 0.15 0.18 0.16 {master:0} root@ex3400VC> root@ex3400VC> show snmp mib get .1.3.6.1.4.1.2636.3.1.13.1.8.9.1.0.0 jnxOperatingCPU.9.1.0.0 No such instance <<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<< {master:0} root@ex3400VC>
PR NumberSynopsisCategory: Cassis XQ related issues
1464297On the MX960 router, the following error message might be observed: SCHED L4NP[0] Parity errors.
Product-Group=junos		This PR along with an earlier PR1232952 address the issue completely, so JUNOS version in question should have fix for these two PRs to address this issue completely.
PR NumberSynopsisCategory: NFX Series Platform Software
1462556Junos OS: NFX350: Password hashes stored in world-readable format (CVE-2020-1669)
Product-Group=junos		The Juniper Device Manager (JDM) container, used by the disaggregated Junos OS architecture on Juniper Networks NFX350 Series devices, stores password hashes in the world-readable file /etc/passwd. This is not a security best current practice as it can allow an attacker with access to the local filesystem the ability to brute-force decrypt password hashes stored on the system. Refer to https://kb.juniper.net/JSA11066 [juniper.net] for more information.
PR NumberSynopsisCategory: Bi Directional Forwarding Detection (BFD)
1518106The BFD sessions might flap continuously after disruptive switchover followed by GRES.
Product-Group=junos		Disruptive switchover (no GRES or NSR configured) can lead to stale PPM entries programmed on the new master Routing Engine. If both GRES and NSR are activated after disruptive switchover and then a GRES switchover is performed, BFD sessions might flap continuously.
PR NumberSynopsisCategory: Border Gateway Protocol
1446383The BGP route prefixes are not being advertised to the peer.
Product-Group=junos		In the graceful-restart and delay-route-advertisements are configured scenario, when a BGP router is waiting for the End-Of-Rib message from the upstream BGP peer, the received corresponding set of NLRI (network layer reachability information) might be held in the Rib-Out and not being sent to the downstream BGP peers. This issue will cause the route update failure.
1523075The BGP session with VRRP virtual address might not come up after a flap.
Product-Group=junos		When VRRP virtual address is configured and used to set up a BGP session with the remote side, under rare timing conditions, BGP peer establishment may get rejected repetitively.
PR NumberSynopsisCategory: BBE Remote Access Server
1402653The subscriber might need to take retry for login
Product-Group=junos		On all Junos platforms running in subscriber scenario with address pool configured, if the address pool has high usage so that only few addresses are free to allocate, when there are subscribers logout and login, the released address by one subscriber might get re-used and allocated to the other subscriber very soon. Due to this issue, syslog error messages might be seen, and the affected subscriber might need to take retry for login.
PR NumberSynopsisCategory: MPC5/6E pfe microcode software
1453575The FPC might crash due to the memory corruption in JNH pool
Product-Group=junos		On all Trio-based platforms, after the restart of the fabric plane, the FPC might crash due to memory corruption in the JNH pool.
PR NumberSynopsisCategory: PRs related to channelized E1/T1 mic
1442820JDI MMX REGRESSIONS: ALTIUS:T1 mode interfaces link protocol is not coming up with cisco-hdlc encapsulation
Product-Group=junos		mode interfaces link protocol is not coming up with cisco-hdlc encapsulation
PR NumberSynopsisCategory: Class of Service
1329141CoS is incorrectly applied on the Packet Forwarding Engine, leading to egress traffic drop.
Product-Group=junos		On ACX5K/EX4600/QFX5100 series platforms, in some cases, CoS configuration is not applied appropriately in the Packet Forwarding Engine, leading to unexpected egress traffic drop on some interfaces.
PR NumberSynopsisCategory: EVPN control plane issues
1439537The rpd process may crash after committing changes in the EVPN environment
Product-Group=junos		On all Junos platforms with EVPN configured, the rpd process may crash after committing any configuration changes if there is an existing MAC entry received from multiple sources and trying to update the latest source. Traffic loss may be observed due to the rpd crash.
PR NumberSynopsisCategory: Enhanced Broadband Edge support for firewall
1531580New subscribers might fail to connect due to "Filter index space exhausted" error
Product-Group=junos		In Junos OS Enhanced Subscriber Management software architecture, there is a code to manage list of freed filter indices. The current code only releases the freed filter indices when a subscriber logs out. However, if only address family bounces (like activating/deactivating family) or service activation/deactivation occurs but the subscriber does not log out, the filter allocation/deletion will happen, but the freed filter indices will not be released. This is more likely happen in a dual-stack subscriber scenario. This filter index leak issue could eventually result in filter index space being exhausted, thereby affecting the new subscriber session establishment. There are 4 million filter indices in the system, so the system can still work even with so many indices in pending state.
PR NumberSynopsisCategory: Libjtask for RPD tasks, scheduler, timers, memory, and slip
1401396The rpd generates the following core files: cmgr_if_route_exists_condition_init, ctx_handle_node, task_reconfigure_complete.
Product-Group=junos		The rpd might crash and restart when condition-manager policy is configured for routing table and the same routing table is repeatedly deleted then re-added. The issue is not fixed in 19.2R1, and it is fixed in 17.4R2-S8-J1 17.4R2-S9 18.2X75-D33 19.2R2 19.2R2-EVO 19.3R1 19.3R1-EVO 19.4R1.
PR NumberSynopsisCategory: jl2tpd daemon
1493289L2TP LNS: Subscriber that sends IRCQ that includes RFC5515 AVPs may fail to establish session
Product-Group=junos		In release 17.4 and forward, subscriber sessions on the LNS that send an ICRQ that includes RFC5515 AVPs may fail to establish a session. The client will receive a CDN error "receive-icrq-avp-missing-random-vector" in response.
PR NumberSynopsisCategory: Firewall Policy
1454907Traffic might be dropped when policies are changed in SRX Series devices
Product-Group=junos		If a huge number of policies are configured on SRX Series devices and some policies are changed, the traffic that matches the changed policies might be dropped.
PR NumberSynopsisCategory: PTX1000 platform
1460406PTX1000 and PTX10002 routers might get drop or discarded after transient SIB or FPC voltage alarms.
Product-Group=junos		On PTX1000 and PTX10002 platforms, if transient voltage fluctuations on a SIB or an FPC are seen, it might trigger the fabric healing process (FHP) and FPC/SIB restart. Later, the SIB might not restart but the FPC still goes online, so the device might experience silent dropping of packets, which affects the service.
PR NumberSynopsisCategory: Multicast for L3VPNs
1536903The PIM (S,G) join state might stay forever when there are no MC receivers and source is inactive.
Product-Group=junos		The problem can be seen in MVPN ASM scenario on a PE which has local MC source and receivers and RP is remote. If all receivers stop joining the group and MC source stops transmitting, corresponding PIM (S,G) state may remain indefinitely despite that. Due to the problem a router will maintain extra PIM state. Service is not impacted.
1546739MVPN multicast route entry might not be properly updated with the actual downstream interfaces list.
Product-Group=junos		In multicast VPN RPT-SPT mode with both locally and remotely connected receivers, the multicast forwarding entry related to the actual downstream interfaces may not be properly updated. The issue may happen when multicast forwarding entry is created by locally connected PIM receiver, followed by remote receiver and after local receiver decides to prune its membership in that multicast group.
PR NumberSynopsisCategory: TCP/UDP transport layer
1552603The BGP session replication might fail to start after the session crashes on a backup Routing Engine
Product-Group=junos		On certain Junos platforms with Dual-REs (platforms capable of installing Junos packages with name format as "junos*install"), BGP replication may fail to start under GRES/NSR setup after a crash on backup Routing Engine. NSR starts un-replicating the socket since backup Routing Engine is no longer present. Massive unreplicated request leads to memory buffer getting full with multiple BGP sessions (e.g., 20 BGP peers). Hence BGP unreplicated request returned with an error. Besides, the kernel is left with stale data. It does not allow the JSR (Juniper Socket Replication, BGP in this case) when backup RE comes up due to the stale data. BGP-NSR (Nonstop Routing) is broke under the conditions. Traffic outage will be observed after performing GRES.
PR NumberSynopsisCategory: PE based L3 software
1500798BFD sessions flap after deactivating or activating the aggregated Ethernet interface or executing GRES.
Product-Group=junos		On QFX10008 platforms, if the BFD is configured over an AE interface (member link across multiple FPCs), deactivating/activating the AE interface or executing GRES will cause the BFD sessions to flap.
PR NumberSynopsisCategory: Protocol Independant Multicast
1487636The rpd might crash when perform GRES with MSDP configured
Product-Group=junos		On all Junos platforms, when execute Graceful Routing Engine Switchover (GRES) with Multicast Source Discovery Protocol (MSDP) enabled, rpd might crash on new master Routing Engine (RE). The issue could be automatically recovered after rpd successful self-restart. This is a timing and regression issue.
1500125Some PIM join or prune packets might not be processed in the first attempt in the scale scenario where the PIM routers establish neighborship and immediately join the multicast group.
Product-Group=junos		On all Junos platforms with scaling MVPN scenario, some PIM Join/Prune messages may not be processed for the first attempt. For instance, a dedicated PIM router receives more than 2500 PIM hello packets from the new neighbors, followed by PIM Join packets for the same multicast group in a very short period of time.
PR NumberSynopsisCategory: vMX Platform Infrastructure related issue tracking
1538252Traffic drop might be seen when executing "request system reboot"
Product-Group=junos		When issuing the command "request system reboot" on MX150 platform, the interfaces are still in the UP state during the reboot process which is not the same behavior as other platforms.
PR NumberSynopsisCategory: Interface related issues. Port up/down, stats, CMLC , serdes
1475851FPC major error is observed after system boots up or FPC restarts.
Product-Group=junos		FPC is reporting Major Error because of SHUTDOWN ERI failure during BIST with repair on HMC having FW version >= 0x9c. BIST with repair is incorporated during boot up, so this Major Error will be reported during boot up having FW>=0x9c on HMC. During debugging, its found that this ERI is getting issued even before the HMC was brought up which is resulting into this Error. So added bringup steps for HMC before the BIST procedure starts as done for vale-ptx.
PR NumberSynopsisCategory: QFX L3 data-plane/forwarding
1406242QFX5200/5100 might not be able to send out control plane traffic to the peering device
Product-Group=junos		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.
PR NumberSynopsisCategory: show route table commands, tracing, and syslog facilities
1555866Configuring HFRR i.e. link-protection on an interface may cause rpd to crash
Product-Group=junos		On MX/VMX/T/TX series platforms, if Host fast reroute (HFRR) is enabled on an interface, the ARP and FRR (BGP backup routes) routes will be added to RIB. Then changing this interface address and adding new ARP route within 10 seconds will cause the rpd to crash.
PR NumberSynopsisCategory: Resource Reservation Protocol
1242558Stale LSPs might exist if the primary LSP goes down immediately after bypass LSP
Product-Group=junos		If the primary link goes down immediately after bypass (for example, FPC containing both primary and bypass, or both primary and bypass FPCs go down simultaneously) such that primary link goes down even before the PLR sends out any path message after bypass down, then the nodes downstream of the PLR along the LSP path will be left with stale LSP state until refresh timeout. This condition will not result in any traffic loss.
1516657The rpd scheduler might slip after the link flaps.
Product-Group=junos		On all Junos platforms with RSVP-TE configured, when a transit router carries a large number of LSP's (for example, 60k and higher) and all those LSPs undergo FRR (for example, when link carrying large number of LSP's flap) then, the rpd scheduler might slip and LDP session tear down might be observed after the link flap.
1546447Amnesiac Mode after D65 to D521 Downgrade
Product-Group=junos		As the update-threshold config changes from an attribute to an object between D65 and D521 the user will need to delete the update-threshold stanza and re-configure it after downgrade.
PR NumberSynopsisCategory: platform related PRs on SRX branch platforms
1465366MAC limiting on Layer 3 routing interfaces does not work.
Product-Group=junos		In SRX platform, if MAC Limiting feature ("source-address-filter" or "accept-source-mac" ) is configured on a Layer 3 Routing interface, the Commit check might fail or the features does not work.
PR NumberSynopsisCategory: MPC7/8/9 Interface Issues
1441816Egress stream flush failure and traffic black hole might occur.
Product-Group=junos		Egress stream flush failure and silent dropping of traffic could occur in a rare occasion for a repeatedly flapping link on MPC7E, MPC8E, MPC9E cards, MX204 and MX10003.
1473280The following error message might appear: Failed to complete DFE tuning. This error message has no functional impact and can be ignored.
Product-Group=junos		Even with the fix for PR 1463015, the "Failed to complete DFE tuning" syslog may appear. This message has no functional impact and can be ignored.
PR NumberSynopsisCategory: Trio pfe qos software
1382288One single port with Dual stack subscribers pppoe/dhcpv6 drop all the connections and no subscribers seen now.
Product-Group=junos		One single port with dual stack subscribers pppoe/dhcpv6 drop all the connections and no subscribers are seen.
PR NumberSynopsisCategory: Trio pfe bridging, learning, stp, oam, irb software
1542537In EVPN-MPLS scenario, BUM traffic is dropped during configuration changes.
Product-Group=junos		In evpn-mpls scenario, BUM(Broadcast, unknown-unicast and multicast) traffic would be dropped due to flood nexthop deletion during configuration changes on any of the PE node.
PR NumberSynopsisCategory: Trio pfe microcode software
1463718On MX204 platform, Packet Forwarding Engine errors might occur when incoming GRE tunnel fragments (1) get sampled and (2) undergo inline reassembly.
Product-Group=junos		On MX204 platform, Packet Forwarding Engine (PFE) error messages might be seen when sampling, GRE tunnel termination and inline reassembly are all configured. The errors could cause packet buffer memory leak. Eventually, once packet buffer memory is exhausted, traffic will starting getting lost.
PR NumberSynopsisCategory: Authentication, Authorization, Accounting, PAM (RADIUS/tacplus)
1099700High CPU usage and high latency are observed with mgd going high while executing commands by a user which has allow-configuration configured
Product-Group=junos		Complex regular expression like below in class configuration cause delay and high cpu with some show commands device> show configuration system login class test allow-configuration "(interfaces lo0 unit 0 .+)|(protocols isis .+)|(protocols ldp .+)|(protocols bgp .+)|(protocols mpls .+)" deny-configuration "(interfaces$|protocols$|protocols isis$|protocols ldp$|interfaces lo0$|interfaces lo0 unit 0$|interfaces lo0 disable$|protocols bgp$|protocols mpls$)" When user configuration has allow-configuration, we build auth tree at runtime. If the configuration is huge enough then building auth tree will take time, and hence the delay. Below is one show command example that was causing this issue "show configuration | display set | match 'pattern'"
PR NumberSynopsisCategory: Virtual Router Redundancy Protocol
1558560Junos device might send VRRP advertisement packets in VRRP init or idle state before startup-silent-period timer expiry after performing GRES on VRRP master device with NSR disabled
Product-Group=junos		If VRRP master device has dual Routing Engines (REs) and GRES enabled but nonstop-routing (NSR) disabled, after performing GRES, both REs will move to VRRP init then idle state and the new master RE will send VRRP advertisement packets in this stage before startup-silent-period timer expiry. Since the VRRP backup device can still receive the VRRP advertisement packets with higher priority, it will not transition to VRRP master state and hence cause the longer traffic downtime until the VRRP master device re-take the VRRP mastership after startup-silent-period timer expiry.
 

Modification History

First publication 2021-02-05

01/04/2022: Non-technical changes; formatting modified