Alert Type

PSN - Product Support Notification
Low/NotificationSoftware Release Notification
Low/NotificationSoftware Release Notification

Product Affected

ACX EX MX NFX PTX QFX SRX vSRX

Alert Description

Junos Software Service Release version 22.3R1-S1 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 22.3R1-S1 is now available.

22.3R1-S1 - List of Fixed issues

PR NumberSynopsisCategory: BBE Remote Access Server
1687998The authd process crashes during GRES recovery phase
Product-Group=junos
On MX platforms, during recovery phase of Graceful Routing Engine Switchover (GRES), authd process crashes.
PR NumberSynopsisCategory: Express Broadway PFE L3
1680757BFD sessions will remain down in the EVPN-VxLAN scenario
Product-Group=junos
On QFX 10008 and QFX10016 platforms, in a distributed mode Bidirectional Forwarding Detection(BFD) session might remain down if the anchor FPC and the FPC where BFD packets are received over Virtual Tunnel Endpoint (VTEP) are different.
PR NumberSynopsisCategory: EX4100 Interface, Optics, MacSec, POE
1682633EX4100-24mp/48mp/48p/48t/24p/24t: Activity LED is lit on some ports if 1G optic is inserted without link being present or up.
Product-Group=junos
If 1G optic is inserted on uplink ports of EX4100-24mp/24mp/48p/48t/24p/24t SKUs, then the activity LED is lit irrespective of link present/up status.
PR NumberSynopsisCategory: EX4100 PFE
1681478Multicast traffic loss is seen with 'igmp-snooping' running on EX4100
Product-Group=junos
On Junos EX4100 platforms, multicast traffic drop happens if IGMP (Internet Group Management Protocol) snooping is configured without an IRB (Integrated Routing and Bridging) interface association.
PR NumberSynopsisCategory: EX4100 RE, Platform Infra, Drivers
1672731The vmcore might be seen with the back-to-back reboot
Product-Group=junos
On the EX4100 platform with VC setup, upon continuous back-to-back switch reboot, vmcore might be noticed when the switch boots back. The vmcore might lead to a kernel crash.
1684032EX4100 & EX4100-F series: The secondary console (USB-C type) does not show the boot logs
Product-Group=junos
EX4100 & EX4100-F series: The secondary console (USB-C type) does not show the boot logs. User will get the login prompt once the device boots up with the Junos.
PR NumberSynopsisCategory: SRX4100/SRX4200 platform software
1650112Packet loss might be seen on SRX4100 and SRX4200 devices from 20.2R2
Product-Group=junosvae
Packet loss might be seen on SRX4100 and SRX4200 devices from 20.2R2
PR NumberSynopsisCategory: Layer 2 Control Module
1686097The l2ald core seen after zeroize
Product-Group=junos
One time l2ald (Layer 2 Address Learning Daemon) core will be seen once the box comes up after zeroize. There will be no service impact due to this.
PR NumberSynopsisCategory: Layer2 forwarding on EX/NTF/PTX/QFX
1689127[Blocker:Test] ULTIMAT[QFX10008]: While verifying "show ethernet-switching global-mac-count | display xml" command "global-mac-count" is not as expected.
Product-Group=junos
With family ccc configartion present, vlan tag getting removed, leading to Mac table entries not resolving
PR NumberSynopsisCategory: JDHCP is a daemon for EVO platform to handle DHCP protocol
1658327ACX7100-48L : jdhcpd core seen on boot
Product-Group=junos
core is seen when any invalid range of interfaces in committed in any group under dhcpv6 dhcp-local-server system services and the box is booted. For eg :- set system services dhcp-local-server group g1 interface ge-0/0/1.3 upto ge-0/0/1.1
PR NumberSynopsisCategory: Category for tracking Olympus-MX issues
1671649Traffic loss seen due to SPC3's packets getting stuck
Product-Group=junos
On Junos MX960, MX480 platforms, Flowd restart or PIC offline/online( Physical Interface Cards) causes SPC3's sending of packets to get stuck.
PR NumberSynopsisCategory: FreeBSD Kernel Infrastructure
1681783On Ex4400 upgrade failure happens when upgrading through a USB drive.
Product-Group=junos
On EX4400 upgrade failure happens when upgrading through a USB drive.
PR NumberSynopsisCategory: RPD route tables, resolver, routing instances, static routes
1677749High CPU is seen on the platforms running IPv6
Product-Group=junos
On all Junos platforms, high CPU is seen due to ipv6 router-advertisement.
PR NumberSynopsisCategory: Issues related to control plane security
1655537UEFI BIOS Key synchronization tool - efitools.service failed after optics diagnostics test
Product-Group=junos
The efitools.service failed since the EFI data structure is set to be immutable in the JUNOS WRL version 9.x
PR NumberSynopsisCategory: SRX branch platforms
1594014During reboot, "warning: requires 'idp-sig' license" can be seen on the screen even when the device has valid license
Product-Group=junos
If a device is rebooted manually or reboots for any other reason, The following messages can be seen on the boot up screen even when the device has valid license and proper configuration to use the features like IDP/UTM
PR NumberSynopsisCategory: VSRX platform software
1680874vSRX instance in GCP gets stuck in halt state randomly when trying to reboot multiple times
Product-Group=junos
vSRX instance in GCP (Google Cloud Platform) freezes during restart and does not shutdown. This issue is very difficult to hit in production as it is seen very rarely after several reboots.
PR NumberSynopsisCategory: Unified Services Framework
1664517SPC3: Receive [Rx] queue of direct memory access might be stuck which may cause issues in packet processing
Product-Group=junos
SPC3:Receive [Rx] queue of direct memory access might be stuck which may cause issues in packet processing
 
 

22.3R1-S1 - List of Known issues

PR NumberSynopsisCategory: EX4100 VC
1686671In rare situations, internal communication timeouts can result in restart of internal PFE process.
Product-Group=junos
In rare situations, internal communication timeouts can result in restart of internal PFE process.

Resolved In: junos:22.3R1 junos:22.3R1-S1 junos:22.3R2
PR NumberSynopsisCategory: Express PFE MPLS Features
1590387ISIS adjacency is not coming up through TCC l2circuit
Product-Group=junos
On ACX/PTX/QFX platforms(PTX10002/10003/10008/10016/QFX10002/10003/10008/10016/ACX6360) if protocols l2circuit and channel tcc is enabled for providing layer 2 transaction, ISIS connection through the layer 2 domain might get failed and traffic loss might be seen.

Resolved In: junos:19.4R3-S8 junos:20.3R3-S4 junos:21.1R3-S1 junos:21.2R3 junos:21.2R3-S3 junos:21.3R2 junos:21.3R3-S3 junos:21.4R2 junos:21.4R3-S1 junos:22.1R1 junos:22.1R3 junos:22.2R1-S2 junos:22.2R2 junos:22.2R3 junos:22.3R2 junos:22.4R1
PR NumberSynopsisCategory: jdhcpd daemon
1666943MX240:Verify VRRP stats is failed after Deactivate the Access interface
Product-Group=junos
VRRP statistic may not be accurate with subscriber services

Resolved In: evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R2-EVO evo:23.1R1-EVO junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:22.4R2 junos:23.1R1
1688272IPv4 ALQ not working with authentication
Product-Group=junos
IPv4 ALQ not working with authentication. The below error would be seen on the backup router: "Message failed sanity test - the access-profile info is invalid. length:0 "

Resolved In: evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R2-EVO evo:23.1R1-EVO junos:22.2R3 junos:22.3R2 junos:22.4R2 junos:23.1R1
PR NumberSynopsisCategory: Layer 2 Control Module
1686596If MVRP is enabled on an MSTP enabled interface, the interface will be made part of all the existing instances on the switch
Product-Group=junos
, If MVRP is enabled on an MSTP enabled interface, the interface will be made part of all the existing instances on the switch, So, if there are two interfaces between R1 and R2 as below: R1(et-0/0/1 & et-0/0/2)======(et-0/0/1 & et-0/0/2)R2 And one interface is MVRP enabled (say et-0/0/1), and et-0/0/2 is not MVRP enabled. By configuration et-0/0/1 is part of MSTI-1 and et-0/0/2 is part of MSTI-2. MSTI-1 is running on vlan-100 and MSTI-2 is running on Vlan-200. R2 in this case, is advertising only vlan-100. The MVRP enabled interface will become part of all the MSTIs(MSTI-1 and MSTI-2 both) configured on the device and it will take part in the FSM of all the MSTIs. Although et-0/0/1 is not member interface of vlan-200(correspnding to MSTI-2). This potentially can cause a problem where et-0/0/1 although not a vlan-200 member, will go into FWD state and et-0/0/2, genuine member of vlan-200 goes into BLK state for MSTI-2. So, when traffic is received in vlan-200 it will be sent out of et-0/0/1, an it will be dropped.

Resolved In: evo:22.4R1-EVO
PR NumberSynopsisCategory: TCP/UDP transport layer
1685113Random BGP session flap with error "BGP_IO_ERROR_CLOSE_SESSION"
Product-Group=junos
On all Junos and Junos Evolved platforms, a random BGP (Border Gateway Protocol) session flaps will be observed immediately after committing unrelated configuration changes with the error "BGP_IO_ERROR_CLOSE_SESSION" along with a connection reset. This issue is generic to any TCP (Transmission Control Protocol) connection that has MD5 (Message-Digest Algorithm) enabled on it.

Resolved In: junos:20.4R3-S6 junos:21.2R3-S4 junos:21.4R3-S3 junos:22.2R2-S1 junos:22.2R3 junos:22.3R2 junos:22.3R3 junos:22.4R2 junos:23.1R1
PR NumberSynopsisCategory: Protocol Independant Multicast
1675212KRT queue shows deferred operation while creating IFL after FPC offline/online event
Product-Group=junos
Dynamic IFL add request is waiting to be processed in KRT queue during that if chassid down event occurs. To handle the chassid down event RPD Infra sends notification to protocol(producer of Dynamic IFL add request) and it is producer jobs to DELETE the dynamic ifls request which were there in the KRT queue. PIM code is not clearing those Dyanamic IFLs ADD request during chassis fpc down event. Hence getting error 'ENOENT -- Item not found' when chassis comes back up.

Resolved In: evo:22.3R1-S2-EVO evo:22.3R2-EVO evo:22.4R1-EVO evo:23.1R1-EVO junos:21.4R3-S2 junos:22.3R2 junos:22.4R1 junos:23.1R1
PR NumberSynopsisCategory: PPPoE functional plugin for bbe-smgd
1685070Multiple bbe-smgd cores might be observed resulting in subscribers being lost or failing to login in the Enhanced subscriber scenario
Product-Group=junos
On MX platforms, multiple bbe-smgd cores might be observed due to out-of-bound memory access in the Enhanced subscriber scenario when bringing up PPPoE (Point-to-Point Protocol over Ethernet) subscribers and ACI (agent circuit identifier)/ARI (agent remote identifier) are part of the payload.

Resolved In: evo:22.1R3-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R1-EVO evo:23.1R1-EVO junos:19.4R3-S10 junos:19.4R3-S5-J1 junos:20.2R3-S4-J9 junos:20.2R3-S6 junos:20.3R3-S6 junos:20.4R3-S5 junos:21.1R3-S4 junos:21.2R3-S3 junos:21.3R3-S3 junos:21.4R3-S1 junos:22.1R3 junos:22.2R2 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:23.1R1
PR NumberSynopsisCategory: QFX L2 PFE
1632565QFX5110-32Q : Traffic loss seen after renumbering master in VC
Product-Group=junos
QFX5110-32Q : Traffic loss seen after renumbering master in VC

Resolved In:
PR NumberSynopsisCategory: QFX L3 data-plane/forwarding
1695943QFX5110-32Q:VC::: After loading "20.4R3-S5.3" dcpfe core is observed and device is unstable
Product-Group=junos
On QFX5K VCF platform, the PFE core will be seen due to invalid usage of snprintf (PR 1688206).

Resolved In: junos:20.2R3-S6 junos:20.4R3-S5 junos:21.1R3-S4 junos:21.2R3-S4 junos:21.3R3-S3 junos:21.4R3-S2 junos:22.1R3 junos:22.2R2-S1 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:22.4R2
PR NumberSynopsisCategory: SRX Argon module
164666121.3R2:SRX_RIAD:srx1500,srx4200:SKYATP:IMAP/IMAPS Email permitted counter is not incremented in AAMW email statistics while testing whole email block.
Product-Group=junos
The SKYATP:IMAP/IMAPS Email permitted counter may have incorrect value under certain conditions.

Resolved In: junos:22.3R2 junos:23.1R1
PR NumberSynopsisCategory: MX10K linecard
1688651JUNOS_REG:MX10008:Carrier transition count is more than expected at DUT(mx10008) after flapping the interface at peer non-DUT end.
Product-Group=junos
When laser off and on happens on the remote end, within an interval of less than 500 ms, the local interface undergoes additional flap, before the link comes up. There is no impact of the additional flap, as the link does come up eventually.

Resolved In:

Modification History

First publication 2022-12-27