Alert Type

SRN - Software Release Notification
Low/NotificationSRN
Low/NotificationSRN

Product Affected

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

Alert Description

Junos Software Service Release version 19.2R3-S5 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 19.2R3-S5 is now available.

19.2R3-S5 - List of Fixed issues

PR NumberSynopsisCategory: EX4300 PFE
1630616The ARP resolution may get failed on VRRP enabled interface
Product-Group=junos
On EX4300, ARP resolution against virtual IP on VRRP enabled interface may get fail with "no-arp-trap" is configured due to which service may get affected.
1630935Application of firewall filters might break connectivity towards the hosts on EX4300
Product-Group=junos
On EX4300 platforms except EX4300-MP/EX4300-48MP, once input/output firewall filters are applied to the interfaces under family ethernet-switching, it might result in disrupting the connectivity towards few hosts connected to the device and thus impacts the related traffic.
PR NumberSynopsisCategory: EX4300 Layer 2 implementation
1600029On EX4300 platform MAC addresses aging issue is seen
Product-Group=junos
On EX4300 platforms, some of the MAC addresses might not aged out specific to virtual chassis. When a LAG (aggregate interface) is configured and if any of the FPC member of virtual chassis has no interface part of LAG, then MACs learnt on the LAG interface may not aged out.
PR NumberSynopsisCategory: EX2300/3400 PFE
1564941The DHCP client might not obtain IP address when dhcp-security is configured
Product-Group=junos
On EX2300 platforms, if enterprise Style (EP) and service provider (SP) style configurations are mixed on a trunk interface, the DHCP client under SP style configuration might not obtain IP address when dhcp-security is enabled on one of the trunk VLANs.
1616646PFE might crash due to deletion of storm control configuration for IFL in CLI which may lead to traffic loss
Product-Group=junos
On Junos EX and QFX platforms with storm control IFL entry, when deleting the storm control configuration in CLI PFE reboot might occur due to access of storm control IFL entry memory that was freed during deletion which might lead to traffic loss.
1627857Packet drop might be observed when L2PT is configured on transit device
Product-Group=junos
On ACX/EX/QFX Junos platforms with Q-in-Q setup in SP(Service Provider) style configuration, when L2PT (Layer2 Protocol Tunneling) is enabled on a transit switch, mac rewritten packets might get dropped on the transit device due to which protocol (for example, STP) convergence fails between the end nodes and thus L2PT breakage could be observed for service-VLANs included in the environment.
1632643Unicast ARP packets with the first four bytes of its destination MAC matching to system macs of a transit system gets trapped by the system
Product-Group=junos
On EX2300 platforms as transit switches, when no-arp-trap is enabled, if the ARP packets are unicast of which the destination MAC has upper four bytes matching to the system MAC, the ARP packets are not forwarded but trapped.
1633115Traffic loss for 20 sec on VC with AE link-protection when rebooting backup FPC
Product-Group=junos
On EX/QFX series Virtual Chassis (VC) with Aggregated Ethernet (AE) link-protection configured, traffic loss could be seen for around 20 sec when the traffic is passing through backup link and backup FPC is rebooted.
PR NumberSynopsisCategory: EX2300/3400 platform
1627673System time may not be updated after reboot on EX2300 platform
Product-Group=junos
System time may not be updated after reboot. Symptoms seen are: 1) After USB image installation, CLI is not working fine. 2) When DHCP persistence is configured with DHCP security and device reboots, the lease time values may show a high lease value post reboot.
PR NumberSynopsisCategory: QFX PFE CoS
1633827Unable to configure policer with "bandwidth-limit" more than 50G
Product-Group=junos
On EX4650 and on all QFX5k (except QFX5220 and QFX5770) platforms, a policer with a "bandwidth-limit" of more than 50G may not be configured for a 100G port.
PR NumberSynopsisCategory: ACX GE, 10GE, PoE, IDT framers
1633226Speed 10m configuration error on ACX5048 and ACX5096 platforms
Product-Group=junos
On ACX5048 and ACX5096 platforms interface speed 10m is not supported on 1G interface. This issue was introduced due to a bug fix and it has been resolved with this PR.
PR NumberSynopsisCategory: Bi Directional Forwarding Detection (BFD)
1599431Some BFD sessions stuck in Init state after FPC restart
Product-Group=junos
After a reboot or chassis restart, everything goes Up and is stable. However, after restarting FPC 3 a good number of BGP sessions never recover. The reason is BFD (see the piece of log below) show bfd session | except up Detect Transmit Address State Interface Time Interval Multiplier XX.XX.XX.XX Init ae-x/x/x 6.000 2.000 3 XX:XX Init xe-x/x/x 256.000 2.000 3 After restarting fpc(Flexible PIC Concentrators ), there is a delay of 12-15sec delay to receive the PIPE close message. Few sessions which are using AE interface may stuck in init state forever. Which may impact traffic.
PR NumberSynopsisCategory: Border Gateway Protocol
1626367Time delay to export prefixes to BGP neighbors might occur post applying peer-specific BGP export policies
Product-Group=junos
On all Junos and EVO Platforms, when BGP export policies were changed from deny all to the peer-specific export policies, it might take several hours for the RPD/BGP to finish the export evaluation.
PR NumberSynopsisCategory: BBE Remote Access Server
1625858Radius CoA (Change of Authorization) NAK may not be sent with the configured Source Address in a virtual-router environment
Product-Group=junos
On all Junos, when running a radius server in multiple routing instances, the CoA NAK messages uses the interface address instead of the configured source address for non-existent sessions. This issue happens when the Radius server is configured in different virtual routers with different settings.
PR NumberSynopsisCategory: MX Platform SW - FRU Management
1634164Slow chassis memory leak may occur when chassisd related configuration change is committed
Product-Group=junos
On MX platforms, every commit routine may leak some memory in chassisd process. Over a long period of time if the total process heap memory usage goes above 3 GB approximately, chassisd may core and restart.
PR NumberSynopsisCategory: Covers Application classification workflows apart from custo
1574056srxpfed/flowd might crash when deactivating and activating application-identification based policies /application-services configurations on SRX platforms
Product-Group=junos
On SRX platforms, memory is exhausting when the device is processing heavy traffic load or any configuration changes. Due to this, srxpfed/flowd might crash while deactivating and activating application-identification based policies/application-services configurations. This crash might cause temporary traffic loss.
1625364Coredumps might be reported on installing IDP security package
Product-Group=junos
On SRX platforms, when installing IDP sigpack, it might impact SRXPFE core file generation. It is a memory corruption issue.
PR NumberSynopsisCategory: eventd, syslog infra issues
1611885Master-eventd process might go down when syslog configuration is misconfigured
Product-Group=junos
On all Junos Operating System Evolved(EVO) based platforms with misconfigured syslog, master-eventd process might go down.
PR NumberSynopsisCategory: Express PFE FW Features
1637328Filters with Unsupported match/action by kernel filters, will not be learnt by firewall MIB daemon.
Product-Group=junosvae
Filters with Unsupported match/action by kernel filters, will not be learnt by firewall MIB daemon.
PR NumberSynopsisCategory: Enhanced Broadband Edge support for firewall
1626091The bbe-smgd might crash on backup RE after ISSU/GRES
Product-Group=junos
On all Junos platforms with BNG enabled, after performing GRES or ISSU if a family is bouncing in a dual-stack scenario, then bbe-smgd might crash on backup RE and the traffic might get impacted if any switchover takes place.
PR NumberSynopsisCategory: Flow-tap software
1647179DTCP radius-flow-tap fails to program PFE when trigger X-NAS-Port-Id exceeds 48 character length.
Product-Group=junos
DTCP radius-flow-tap fails to program PFE when trigger X-NAS-Port-Id exceeds 48 character length.
PR NumberSynopsisCategory: Fast Ethernet interfaces
1613430Static route might not work on vSRX
Product-Group=junos
On vSRX instance instantiated in Google Cloud, static route might not work.
PR NumberSynopsisCategory: Kernel software for AE/AS/Container
1577799Kernel crash may be observed on the backup RE after GRES
Product-Group=junos
If a child member interface is deleted from an AE interface after NSSU/ISSU, then performing GRES may cause the kernel crash on the new backup device/RE in a rare case.
1641988The VMcore might be observed on EX platforms in rare scenario
Product-Group=junos
On EX platforms, the Routing Engine (RE) might get crashed and result in VMcore, if the kernel sends a request to PFE for fetching the statistics of an Aggregated Ethernet (AE) with more than one member link. This issue appears when the member link gets lost for certain reasons in background and at the same time the kernel's request arrives. Since AE member link has lost, PFE might not send statistics response to kernel within 10 seconds(default time) and error might be returned. This invalid memory access might result in RE crash by generating VMcore. This could be a rare case scenario.
PR NumberSynopsisCategory: Integrated Routing & Bridging (IRB) module
1623262Host generated IPv4 traffic sent over IPv6 next-hop with IRB interface might get dropped
Product-Group=junos
On all Junos platforms that support IRB(Integrated routing and bridging), when host originated IPv4 traffic is sent over IPv6 next-hop with IRB interface, the traffic might get dropped because of ether-type mismatch. This is because the ether-type field in L2 header is set to IPv6 (instead of IPv4) always due to the IPv6 next hop.
PR NumberSynopsisCategory: ISIS routing protocol
1538696IS-IS adjacency might flap after committing configuration change on protocol MTU for IS-IS interface
Product-Group=junos
With IS-IS configured, committing configuration change on protocol MTU for IS-IS interface will trigger a sequence of events in Junos. The following specific sequence of events might cause IS-IS hello PDU to convey incorrect IP address in IS-IS TLV #132 (IP interface address field) which would result in the IS-IS adjacency flapping. This is a timing issue. == The following sequence of events trigger this issue when changing protocol MTU for IS-IS interface == 1. IP interface address is deleted. 2. IS-IS hello PDU is sent out. 3. MTU is changed to new value. 4. IP interface address is added back. When the IP interface address (IFA) is deleted due to protocol MTU (like inet MTU) being changed, if IS-IS hello PDU is sending out during this time, the current implementation will encode the router-id in IS-IS TLV #132 (IP interface address field). So, in this special case, the IS-IS hello PDU received by IS-IS neighbor will be marked as invalid because of address mismatch and the IS-IS adjacency will be down. In the fix of this PR, by default, Junos does not encode the router-id in IS-IS hello PDU when IFA is not present on interface. However, a hidden knob is given for the backward compatibility, and when this knob is configured, the router-id will be encoded in IS-IS hello PDU if IFA is not present on interface.
PR NumberSynopsisCategory: jdhcpd daemon
1588813Delegated prefix ipv6 address is missing in accounting stop messages
Product-Group=junos
DP (Delegated prefix) is cleared when underlying session (dhcpv6 over ppp) ifl is deconfigured. DP is not seen in Radius accounting stop messages.
PR NumberSynopsisCategory: jl2tpd daemon
1629104L2TP tunnels may go down and not able to re-establish after restarting the bbe-smgd process
Product-Group=junos
On MX configured as L2TP access concentrator (LAC), if the bbe-smgd process is restarted when L2TP tunnels are getting down (e.g., L2TP tunnel will get down due to retransmission timed out caused by loss of IP connection between LAC and LNS) and later on the same tunnels are selected to tunnel new subscriber sessions, these L2TP tunnels may be stuck in down state and not be able to re-establish. The issue could cause the subscriber to lose connectivity. This is a timing issue.
PR NumberSynopsisCategory: User Firewall related issues
1637548Unable to connect to domain controller on installing Microsoft KB update
Product-Group=junos
On all SRX platforms, when the User Identification feature is used with Active Directory, after the Domain Controller server installs updates related to Microsoft's KB article KB5004442 [juniper.net], SRX is no longer able to connect to it.
PR NumberSynopsisCategory: Security platform jweb support
1629978skip to jweb not working for srx300
Product-Group=junos
The J-Web setup wizard may not function correctly on SRX300 and SRX320 devices. The work around is to perform initial configuration manually.
PR NumberSynopsisCategory: Layer 2 Circuit issues
1626219The rpd process might crash during ISSU if the auto-sensing knob is enabled for l2circuit
Product-Group=junos
On all platforms which support the In-Service Software Upgrade (ISSU) feature, if the auto-sensing knob is enabled for l2circuit, the routing protocol daemon (rpd) might crash while performing ISSU. Traffic loss might be seen when the rpd is down and service can recover after rpd comes back up.
PR NumberSynopsisCategory: MX104 Software - Chassis Daemon
1626486The chassisd might crash on MX104
Product-Group=junos
On the MX104 platform, when 'Invalid Chassis Model' occurs in the chassisd daemon, the chassisd might crash which might lead to interfaces down and automatic recovery. The fix is to solve avoid this chassisd core during 'Invalid Chassis Model' scenario.
PR NumberSynopsisCategory: FreeBSD Kernel Infrastructure
1570148A false error related to insufficient space might appear while installing a Junos image that is corrupted
Product-Group=junos
On all Junos platforms, the upgrade might fail with a false error related to insufficient space when trying to install Junos from a corrupted package.
1601904The process rpd may slip due to a FreeBSD defect
Product-Group=junos
The process rpd may slip due to a FreeBSD defect. See [FreeBSD id=227689](https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=227689) for more information.
1639991Recovery snapshot might fail if OAM volume is already mounted
Product-Group=junos
Recovery snapshot might fail with the error "The OAM volume is too small to store a snapshot" if OAM volume is already mounted.
PR NumberSynopsisCategory: Kernel Multicast Infrastructure
1608311Intermittent p2mp traffic drop might be seen in MVPN scenario
Product-Group=junos
On MX platforms that support enhanced IP, intermittent p2mp traffic drop might be seen in the case of MVPN with p2mp. When the multicast composite NH involves unicast NH pointing to pseudo interfaces like interface vt-, irb or lsi and the other unicast next-hop is spread across multiple line cards/PFEs, if a new member joins or an existing member leaves the multicast stream traffic drop might be seen.
PR NumberSynopsisCategory: OSPF routing protocol
1636028RPD memory leak on OSPF SR routers when deploy in a network with mixed OSPF SR/Non-SR router
Product-Group=junos
When mixing OSPF Segment Routing (SR) routers with non-SR routers, you may see memory leak on the SR routers.
PR NumberSynopsisCategory: vMX Data Plane Issues
1641119IPv4 and v6 packet header corruption could happen with some sampling scenario
Product-Group=junos
On vMX/MX150/NFX150 platforms, when sampling is enabled on input WAN interfaces and the sampled packet go out through a GRE tunnel, IPv4/6 header corruption may happen. Due to IP header corruption, remote router reports L3 incompletes at receiving interface.
PR NumberSynopsisCategory: VRR (Virtual Route Reflector) for MX
1635950vRR VM might establish its identity as "Olive" after a CLI s/w upgrade
Product-Group=junos
vRR VM might come up as Olive after a CLI sw upgrade using junos-install-mx* package if the XML used to spawn the VM didn't have SMBIOS entry "VRR".
PR NumberSynopsisCategory: QFX L2 PFE
1633452The FBF filtered VLAN traffic will not be passed properly to the forwarding routing instances over AE interfaces on QFX5K/EX4600/EX4650 platforms
Product-Group=junos
On QFX5K/EX4600/EX4650 platforms with IPv4 Filter-based forwarding (FBF) scenario, when IPv4 FBF is used with 802.1Q VLAN tag enabled layer-3 AE interfaces, the VLAN filtered configuration enabled by FBF filter will be stored in the VLAN filter processor (VFP) ternary content addressable memory (TCAM). But, in some cases of adding/deleting the configuration of the routing instances (then routing-instance) in FBF filter, the stale allocated entries in VFP TCAM might not be deleted from the system, the memory slices of VFP TCAM will be exhausted until it is run out. Finally, there are not enough memory slices left to store the VLAN filtered information for the forwarding routing instances, then the FBF filtered VLAN traffic will not be forwarded correctly since the FBF filters might not be programmed/processed on the system.
1637249Configuring L2PT on a transit switch in a Q-in-Q environment breaks L2PT for other S-VLANs
Product-Group=junos
When L2PT (Layer2 Protocol Tunneling) is enabled on a transit switch using SP style configuration, protocol convergence between end nodes might fail.
1638619Targeted broadcast or WOL feature may not work on QFX 5k platforms
Product-Group=junos
On QFX platforms, Wake On LAN(WOL) feature stops working as the affected platforms erroneously process such packets. This might cause a blackhole in the network for such traffic.
PR NumberSynopsisCategory: QFX L3 data-plane/forwarding
1608610FPC might crash post firewall filter configuration changes in QFX platforms
Product-Group=junos
On QFX5110/5120 platforms with VXLAN routing scenarios, FPC might crash when there is a change in firewall filter configuration which is applied on IRB. This issue might not affect the 20.3R1 version.
PR NumberSynopsisCategory: QFX VCCP
1559172The VCF might become not stable
Product-Group=junos
When adding a new leaf to VCF of 12 members without setting its VC mode to 'fabric' on QFX5100 platforms, it might cause the VCF to become not stable.
1628447802.1p BA classification might not work on mixed VC when interface has a DSCP and 802.1p classifier
Product-Group=junos
In a mixed (QFX5K and EX4300) VC (Virtual-Chassis) scenario, when traffic enters the VC on an EX4300, the classification for IP traffic (DSCP classifier) is working fine, but MPLS traffic is not correctly classified (802.1p classifier is NOT working and all traffic is classified as Best Effort) that might lead to incorrect QoS treatment for MPLS traffic.
PR NumberSynopsisCategory: QFX5100 Virtual Chassis
1601557Removing and adding VC ports might cause the FPC to reboot
Product-Group=junos
On QFX5100-24Q/QFX5100-48S/QFX5100-48T/QFX5100-96S Virtual Chassis (VC) setup, when the 10G VCP port is removed and added (logically/physically), the remaining 10G VCP ports are getting flap, causing the FPC to restart and the VC to lose the connection between members and rejoins to VC after sometime. Logically by using the commands "request virtual-chassis vc-port delete pic-slot port member " and "request virtual-chassis vc-port set pic-slot port member " to remove and add respectively. Physically by plugging and unplugging the optics corresponding to the VC port.
PR NumberSynopsisCategory: RPD route tables, resolver, routing instances, static routes
1635009Multipath route getting formed for a VPN prefix due to incorrect BGP route selection logic
Product-Group=junos
On all Junos OS and Junos OS Evolved platforms running BGP, when a specific route is received from multiple places under a VRF, multipath route is getting formed even though the BGP route selection algorithm has the active route with higher local preference. Once multipath is formed, the traffic forwarding is happening based on that, and it may result in some traffic going to an unwanted path. Please refer to KB37775 [juniper.net] for more details.
PR NumberSynopsisCategory: IPSEC functionality on M/MX/T ser
1631443The kmd might crash since the pkid requested memory leak happens on M/MX platforms
Product-Group=junos
In IPsec running M/MX platforms, in some rare cases (e.g., after rebooting router/upgrading MPC/SCB), the kmd (Key Manager Daemon) will crash due to pkid (handling Public Key Infrastructure function) requested memory leak. Then IPSec key negotiation service might be impacted and IPSec traffic loss might follow.
PR NumberSynopsisCategory: SRX5XX platform
1575231The fxp0 interface of an SRX550 in cluster might become unreachable from an external network
Product-Group=junos
On SRX550 configured with chassis cluster, fxp0 interfaces might not be reachable from external management interface when the fxp0 and redundant Ethernet(reth) interfaces are in separate routing instances. This is because there is no ARP entry for the reth interface in fxp0 ARP table. As a result of this, SRX cluster cannot be accessed from an external management network.
PR NumberSynopsisCategory: Stout cards (MPC8, MPC9) fabric issues
1617469MPC8E in 1.6T bandwidth mode may not work correctly
Product-Group=junos
If MPC8E is set in 1.6T bandwidth mode, it may not work correctly and the end result is that the MPC8E will not be able to see 1.6T throughput (as configured) and will see fabric drops at higher traffic rates. The 1.6T bandwidth fabric parameters are not getting applied to SFBs. https://kb.juniper.net/TSB18180 [juniper.net]
PR NumberSynopsisCategory: SRX-1RU platfom related protocol, QoS, filtering features et
1541668SRX4600 PEM code has a bug which might raise false fan failure alarm
Product-Group=junosvae
SRX4600 PEM code has a bug which might raise false fan failure alarm when other status is wrong.
PR NumberSynopsisCategory: Issues related to all UI tools (mgd-bsd/cli-bsd, XML and DMI
1630167Zeroize RPC returns no positive reply
Product-Group=junos
Zeroize RPC returns no positive reply
PR NumberSynopsisCategory: PTX/QFX100002/8/16 interface software
1600768CRC errors increase continuously after interface flap
Product-Group=junos
On PTX10008 and PTX10016 routers with LC1101, LC1102, or LC1103 line cards, interface flapping might cause the interface CRC errors to increase continuously. Then traffic loss might be seen. This is a rare timing issue.
PR NumberSynopsisCategory: VMHOST platforms software
1547669WR Linux 6 platforms and WR Linux 9 platforms might be stuck after upgrading or downgrading image version and restarting the device
Product-Group=junos
On Wind River Linux 6 (WR Linux 6) platforms and WR Linux 9 platforms using VMHOST based routing engine (RE), device might be stuck after upgrading image or downgrading image and reload the device. There is service impact if this issue happens.
 
 

19.2R3-S5 - List of Known issues

PR NumberSynopsisCategory: BBE Remote Access Server
1624066Class attribute is corrupted for Radius accounting messages since ISSU to 19.1 or higher release on MX series platforms
Product-Group=junos
When performing ISSU from earlier releases to certain releases (refer to External Description) on MX series platforms, accounting messages for new service on existing subscribers will have corrupted class attribute value which might be rejected by Radius Server. As a result, new service on existing subscribers might not get created.
PR NumberSynopsisCategory: Firewall Filter
1471310Firewall filter monitoring using SNMP might not provide accurate results
Product-Group=junos
On all Junos except MX platforms, the firewall filter monitoring using SNMP OID 1.3.6.1.4.1.2636.3.5.2.1.6 might not provide the entire output of configured filters. The following actions are not supported - "then policy map", "clear-policy-map", and "then encapsulate/decapsulate". The following matching expressions are not supported - "payload-protocol", "gre-key", flex-offset range/prefix", and "policy-map".
PR NumberSynopsisCategory: Express PFE FW Features
1420560The firewall counter for lo0 interface might not increase
Product-Group=junos
The firewall counter for lo0 does not increase on PTX if lo0 filter family any is configured.
PR NumberSynopsisCategory: Express PFE MPLS Features
1628196EAPol packets over Layer 2 circuit may get dropped at the tunnel start
Product-Group=junos
On all PTX Series routers in the Layer 2 circuit scenario, when the "l2circuit-control-passthrough" option is enabled, Extensible Authentication Protocol over LAN (EAPoL) packets might not go over the Layer 2 circuit as expected.
PR NumberSynopsisCategory: Layer 2 Control Module
1629011Traffic drop might be reported on the interface after reboot or power cycle
Product-Group=junos
On Junos and EVO platforms, after reboot or power cycle, aggregated ethernet (AE) interfaces will have spanning tree protocol (STP) state discarding after the box comes up. It might cause traffic drop on the interface.
PR NumberSynopsisCategory: Multicast for L3VPNs
1579963The rpd might crash in the NG-MVPN scenario on all Junos/Evo platforms
Product-Group=junos
The routing process (rpd) might crash and generate core-dumps in Next Generation Multicast Virtual Private Network (NG-MVPN) environment configured with 'convert-sa-to-msdp' knob which converts source active from MVPN routes to MSDP SA. The crash might be triggered under rare circumstances when a delete is requested for locally originated MSDP source active (SA) but the SA is already deleted.
PR NumberSynopsisCategory: Track Mt Rainier RE platform software issues
1568038The chassisd might crash on MX/PTX/EX92xx platforms with NG-RE
Product-Group=junos
On MX/PTX/EX92xx platforms with NG-RE, when message length is less than the message header length, which is received in chassisd from the host, the chassisd might crash.
PR NumberSynopsisCategory: Track Mt Rainier SPMB platform software issues
1637950SPMB might crash immediately after a switchover
Product-Group=junos
On dual RE PTX5K platforms equipped with SPMB type- PTX5K CB PMB, immediately after a switchover, if the new master SPMB (Switch Processor Mezzanine Board) finds any CB-to-SIB PCI (Control Board - Switch Interface Board Peripheral Component Interconnect) link down error, then the new master SPMB might crash causing a traffic blackhole for about 2-3 minutes while the SIBs (Switch Interface Board) are re-initialized.
PR NumberSynopsisCategory: IPv6/ND/ICMPv6 issues
1631607ipv6 host route prefix match disappear from 'forwarding-table' after a ping test, ping continues to work, forwarding table entry is not shown. No impact in traffic.
Product-Group=junos
IPv6 route resolutions for ipv6 hosts is missing from the 'route forwarding-table' after pinging hosts within the ip prefix.
PR NumberSynopsisCategory: QFX5K hostpath
1630201LACP timeout might be observed during high CPU utilization
Product-Group=junos
On QFX5100 switches, when the CPU utilization (Routing Engine and FPC) is 85 percentage or more and there are multiple Network Configuration Protocol (NETCONF) sessions running or SNMP polling is happening over multiple sessions simultaneously, the LACP session configured in fast mode might timeout.
PR NumberSynopsisCategory: Trio pfe bridging, learning, stp, oam, irb software
1594146Incorrect Encapsulation/Decapsulation VNI pairs might get created and destroyed for type-5 tunnel in EVPN deployment
Product-Group=junos
On MX240/MX480/MX960/MX2008/MX2010/MX2020/EX9200 series configured with EVPN deployment and VXLAN Type-5 configuration with route leaking is enabled on remote PE VRF then VXLAN decapsulation may have issues leading to packet drops in PFE.
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1452136The mgd might crash when you use the replace pattern command.
Product-Group=junos
When you use the "replace pattern" command to replace the name in the apply-group, the mgd crashes.

Modification History

First publication 2022-04-11