22.3R2-S1: Software Release Notification for JUNOS Software Version 22.3R2-S1

Alert Type

SRN - Software Release Notification

RiskRisk Description

Low/Notification

Software Release Notification

ImpactImpact Description

Low/Notification

Software Release Notification

Product Affected

ACX EX MX NFX PTX QFX SRX vSRX

Alert Description

Junos Software Service Release version 22.3R2-S1 is now available for download from the Junos software download site

Download Junos Software Service Release:

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

Solution

22.3R2-S1: Software Release Notification for JUNOS Software Version 22.3R2-S1

Alert Description

Junos Software Service Release version 22.3R2-S1 is now available for download from the Junos software download site

Download Junos Software Service Release:

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

Solution

Junos Software service Release version 22.3R2-S1 is now available.

22.3R2-S1 - List of Fixed issues

PR Number	Synopsis	Category: EX4300 PFE
1698833	The DHCP offer packet failed to send back to the client leaf from the server leaf Product-Group=junos	On EX4100, EX4400 and QFX5k platforms, when inter-vrf DHCP relay scenario is configured, the server leaf fails to send the DHCP offer response packet to the client leaf. Due to this DHCP client will not be able to bind.
PR Number	Synopsis	Category: EX2300/3400 PFE
1695771	Traffic loss is seen when a MAC moves from dot1x port to non-dot1x port Product-Group=junos	On all Junos and Junos OS Evolved platforms is having dot1x enabled interface. When two or more MAC addresses are learnt on a dot1x port, and if one of them is shifted to a non-dot1x port, the MAC address that was moved is still seen as a MAC-based VLAN entry on the Layer2 Address Learning Manager (l2alm). This could lead to network traffic being lost.
PR Number	Synopsis	Category: Accounting Profile
1706085	Firewall filter counters are not written to accounting file when interface-specific knob is used Product-Group=junos	On all Junos platforms, when firewall filters are configured with 'interface-specific' knob to log packet counters on the accounting file using 'accounting-options', firewall filter counters are not written to this file. This causes problem in fetching the filter counters.
PR Number	Synopsis	Category: ChassisD changes specific for ACX series
1717105	SNMP MIB OID output showing wrong temperature value if device running under negative temperature Product-Group=junos	On all Junos platforms, devices may display wrong temperature values when executing commands. The temperature value is processed as positive integers but not negative integers. Hence, the negative temperature value is showing the wrong value.
PR Number	Synopsis	Category: australia related kernel issue
1714002	vmcores can be seen on SRX5k platforms when the fxp0 interface is configured under management-instance Product-Group=junos	On Junos SRX5K series platforms, when the 'set system management-instance' command is committed on the secondary node, continuous VMcores are observed on the secondary node leading to the kernel crash. The secondary node of the cluster reboots automatically to recover from the error. The cluster redundancy is not restored until management-instance knob is removed using "delete system management-instance".
PR Number	Synopsis	Category: BBE interface related issues
1715410	The bbe-smgd process is seen to crash if a large scale PWHT configuration is present Product-Group=junos	On all MX platforms in a subscriber scenario, the bbe-smgd process is seen to crash immediately after a configuration change is committed and if a large scale PWHT (Pseudowire Headend Termination) configuration is present.
PR Number	Synopsis	Category: Border Gateway Protocol
1695062	Traffic null routes are observed when it takes a long time to remove the BGP routes from RIB Product-Group=junos	On Junos platforms, if a BGP peer goes down and stays down, the system might take an extremely long time to finish removing the BGP routes. This issue is observed when a BGP peer sends many routes, the system only selects only a small number of routes are as the active routes in the routing information base (RIB), and the BGP delete job gets only a small portion of the CPU time because other work in the routing process is utilizing the CPU.
PR Number	Synopsis	Category: Issues related to Common BIOS on x86 based designs
1715258	On EX4400 and EX4400-24X platforms, BIOS upgrade is not getting successful via CLI. Product-Group=junos	On EX4400 and EX4400-24X platforms, BIOS upgrade is not getting successful via CLI when the system is booted with secondary partition [HDD00.6].
PR Number	Synopsis	Category: MX304 Chassis specific platform
1675268	MX304:: Observed spmbpfe core on RE1 when installed image on both the REs Product-Group=junos	Sometimes cores are reported on backup RE during init after a reboot etc. When the backup RE initialization is being done and system is busy, some commands executed in context of spmbpfe are taking more time to complete due to the initial heavy lifting by the kernel, In this stage, if in case the commands from spmbpfe process do not complete for >2.5 seconds, then there are chances of spmbpfe cores. This is a temporary issue seen on backup RE during init time only. This may not be impacting because if in case spmbpfe process crashes due to this, it would restart by itself and continue to init and run once the initial high cpu condition has passed. It should not cause any functionality or performance impact; especially since it is reported only on backup RE.
PR Number	Synopsis	Category: MX304 Routing Engine issues
1686577	New CLI commands addition to support RE and Chassis power-cycle Product-Group=junos	New CLI commands addition to support RE and Chassis power-cycle under request vmhost hierarchy. These are the "request vmhost power-cycle-re", and "request vmhost power-cycle-cb".
PR Number	Synopsis	Category: Class of Service
1702836	Control packets would be dropped when CoS configuration under AE wildcard IFLs gets applied to AE control IFLs as well Product-Group=junos	On MX platforms, when Aggregated Ethernet (AE) working in hierarchical-scheduler or per-unit-scheduler mode and AE class of service (CoS) configuration having wildcard on AE Logical Interface (IFLs) is committed in a single commit with AE interface flap, then the wildcard configuration gets applied to AE control IFL also. Ideally, any wildcard CoS configuration should not get attached to control IFLs. Only explicit configurations should be attached to control IFLs. This can lead to unintentional behavior.
PR Number	Synopsis	Category: L2NG RTG feature
1715518	Traffic loss is seen on RTG bound interface Product-Group=junos	On all Junos and Junos OS Evolved platforms, configuring mac-move with action shutdown can disable the RTG (Redundant Trunk Groups) interface leading to traffic loss bound to that interface.
PR Number	Synopsis	Category: DNX L2 related features
1722919	Intermittent MAC move is observed in VPLS environment when ACX5448 or ACX710 is acting as a PE device Product-Group=junos	On Junos ACX5448 and ACX710 platforms acting as a PE (Provider Edge) device in a VPLS (Virtual Private LAN Services) environment and multiple CE (Customer Edge) interfaces are bound to a single routing instance, intermittent MAC move is observed. This is a corner case scenario and the MAC move can be triggered due to various reasons and not limiting to mac address time out, l2 loop on the extended network or a congested backbone link connecting the PE devices. The split horizon rule in VPLS fails and the traffic received from VPLS LSI (Label-Switched Interface) is forwarded back towards the MPLS core through the LSI.
PR Number	Synopsis	Category: Gnats category for dynamic rendering infrastructure
1681777	Invalid XML output for get RPC response Product-Group=junos	If the configured data has special characters in it, then rpc get output will not escape these special characters and display the data as it is. For example, if we have configured qos class as , then ---- > the response should have default as response value .
1714120	The picd and evoaftmand process crash is seen in telemetry scenario Product-Group=junos	The picd and evoaftmand process will crash by unsubscribing /component or /interface sensor on certain platforms which uses telemetry infra.
PR Number	Synopsis	Category: EX4100 RE, Platform Infra, Drivers
1681673	EX4100 & EX4100-F Virtual chassis: Non-existing PIC ports are seen in jvision queries Product-Group=junos	EX4100 & EX4100-F Virtual chassis: Non-existing PIC ports (e.g. PIC0:PORT100, PIC2:PORT102) while running the jvision query.
1686364	EX4100 and EX4100-F series: On configuring console "logout-on-disconnect", password configuration via console does not work Product-Group=junos	EX4100 and EX4100-F series: On configuring "console logout-on-disconnect", password configuration via console does not work
PR Number	Synopsis	Category: EX4400 PFE software
1682960	fxpc daemon core is observed on Junos EX4400 platforms in a Virtual chassis setup with HGoE mode Product-Group=junos	On Junos EX4400 platforms with a Virtual Chassis(VC) setup and operating in a HiGig over Ethernet (HGoE) mode, Packet Forwarding Engine manager (fxpc) daemon core is observed when there is CPU-generated burst traffic. Due to this core, the Packet Forwarding Engine(PFE) will be restarted and traffic through it will be impacted.
1701546	The BFD session will remain in init/down state in the Virtual Chassis scenario Product-Group=junos	On Junos EX and QFX Virtual Chassis platforms configured with Bidirectional Forwarding Detection (BFD) over the Aggregate Ethernet (AE) interface, when the BFD control plane traffic is received on the lag member port which is present as non-anchor FPC of the BFD session, the BFD session will be stuck in the Init/down state. Only single-hop BFD sessions will be impacted.
1718316	EX4400-24X: fxpc core seen on backup RE with collapsed config on aggregation 3 member device in HGoE mode Product-Group=junos	The number of DCBs per DV in sdk config is reduced from 256 to 128 for HGoE mode to accommodate increase in memory requirements.
PR Number	Synopsis	Category: EX4400 platform
1696444	Transceiver not detected after it's unplugged and plugged in again Product-Group=junos	On EX4400 and EX4300MP platforms, after JOJI (jack out/jack in), transceiver is not detected in "show chassis hardware".
1706952	The PoE firmware upgrade fails on EX4400 platforms Product-Group=junos	On Junos EX4400 platforms, the Power over Ethernet (PoE) firmware (FW) upgrade fails and gets stuck in "POE_SW_ERASE" state.
1710793	The link does not come up after PIC offline and online operation Product-Group=junos	On EX4400 platforms running Junos OS, the link does not come up after PIC (Physical Interface Card) offline and online operation is performed, either through CLI or after physical PIC removal and insertion , when 1G optics is used on a 4x10G PIC module.
1714116	EX4400 Link/Activity LED is not lit when it transits to the factory default configuration by pressing the Factory Reset/Mode button Product-Group=junos	Press the Factory Reset/Mode button on the far right side of the front panel for 10 seconds. EX4400 transitions into factory-default configuration and the Link/Activity LEDs on the network ports and the QSFP28 ports should be lit steadily in green color but were off.
1715680	The interface phy of PIC 0 comes up causing traffic loss while the device boots/reboots Product-Group=junos	On EX4400-48P/T and EX4400-24P/T platforms, traffic loss is observed when the interface phy comes up of PIC 0 for which the remote end link powers up while the device boots/reboots.
1719509	factory default config does not have rstp enabled for uplink ports. Product-Group=junos	An EX4400 device running release 22.4R1 will not have spanning tree enabled for uplink ports in the factory default config. This could impact Zero Touch Provisioning of the device over uplink ports due to a risk of encountering Mac-learning race condition or loops. If multiple such devices (that are zeroized) are in a vlan, that could cause unpredictable results for traffic being forwarded.
PR Number	Synopsis	Category: PFE EVPN / VxLAN related issues on EX platforms
1693967	DHCP binding fails after dot1x authentication in EVPN-VXLAN network Product-Group=junos	On Junos EX4100, EX4400 and EX4650 platforms, in the VXLAN (Virtual Extensible LAN) network, DHCP (Dynamic Host Configuration Protocol), ARP (Address Resolution Protocol) and PING services will get impacted as the DHCP binding fails due to the DHCP offer packet being tagged while egressing out of the DHCP relay agent when Dot1x is authenticated on a port.
PR Number	Synopsis	Category: EX POE
1716261	EX4100MP (PSE) does not allocate a power value requested in LLDP by Mist AP devices like AP12, AP32, AP33 and AP43 (PD). Product-Group=junos	EX4100MP may allocate a power 0.1w less than the one PD requested. For example, when PD requests the power 19.4W in LLDP, EX4100 will allocate 19.3W to PD.
PR Number	Synopsis	Category: Express PFE CoS Features
1719956	Convergence delay is seen when FPC is offlined under heavy traffic and scaled scenario Product-Group=junos	On certain Junos PTX platforms (PTX3000/PTX5000/PTX10008/PTX10016) when the FPC (Flexible PIC Concentrators) is offlined with scale configuration and heavy traffic, a delay in convergence (into tens of minutes) is seen on all the live FPCs in the chassis other than the offlined one, leading to traffic impact.
PR Number	Synopsis	Category: Firewall Policy
1698508	Security policies go out of sync during ISSU Product-Group=junos	On all Junos platforms, policies go out of sync between RE (Routing Engine) and PFE (Packet Forwarding Engine) after performing ISSU (In-service software upgrade) leading to the wrong policy lookup.
PR Number	Synopsis	Category: IPSEC/IKE VPN
1716092	The iked process will crash when VPN tunnels parameters are not matching Product-Group=junos	On all SRX platforms and MX platforms with SPC3, the iked process crash will be seen continuously when parameters do not match for the same VPN tunnel. For example, in the site-to-site tunnel if iked-id configured in the IKE config does not match with the remote site and the IPSEC proposal does not match between the sites.
PR Number	Synopsis	Category: PFE infra to support jvision
1711779	gNMI line card (PFE) sensor /junos/system/linecard/packet/usage/ may have packet drops (gNMI translator lookup failures) Product-Group=junos	When subscribing to sensor paths "/junos/system/linecard/packet/usage/" in gNMI subscription mode, packet drops ((gNMI translator lookup failures)) may be seen in the CLI command "show network-agent statistics gnmi detail" output for empty dummy packets (packets which do not have a prefix or key-value data). The collector output may also contain missing sequence numbers. For example, the sequence number output may be 0, 3, 6, 9, 12, etc. instead of 0, 1, 2, 3, 4, etc.
PR Number	Synopsis	Category: Issues related to Junos licensing infrastructure
1708794	License expire error will be observed after upgrade Product-Group=junos	On all Junos and Junos OS Evolved platforms, license expire error will be observed after the upgrade.
PR Number	Synopsis	Category: FreeBSD Kernel Infrastructure
1704032	VM process crashes if a file is shared between the host operating system and the guest operating system using virtFS Product-Group=junos	On Virtual Machines (VM) based platforms running Junos images, files are not shared between the host operating system and guest operating system via Virtual Filesystem (virtFS). When this issue happens, the device will be restarted.
1712855	ICMP packets are received on the management interface even though the destination MAC is not local Product-Group=junos	On all platforms supporting em driver for their ethernet interface, promiscuous mode is enabled by default and hence traffic storm is noticed on the management interface.
1717710	Unable to take recovery snapshots after USB upgrade is performed on ACX710 Product-Group=junos	On ACX710 platform, the OAM (Operations, Administration and Maintenance) volume seems unpopulated when an upgrade is performed with USB (Universal Serial Bus) drive or zeroize media. This leads to failure in taking recovery snapshots.
PR Number	Synopsis	Category: TCP/UDP transport layer
1694463	The vmcore crash observed in low memory conditions Product-Group=junos	On all Junos platforms, when there are low memory conditions vmcore crash is observed which impacts the traffic.
PR Number	Synopsis	Category: JRR - VRR running on SRX4200
1677503	Junos OS: JRR200: Kernel crash upon receipt of a specific packet (CVE-2023-28970) Product-Group=junos	An Improper Check or Handling of Exceptional Conditions vulnerability in packet processing on the network interfaces of Juniper Networks Junos OS on JRR200 route reflector appliances allows an adjacent, network-based attacker sending a specific packet to the device to cause a kernel crash, resulting in a Denial of Service (DoS). Continued receipt and processing of this packet will create a sustained Denial of Service (DoS) condition. Please refer to https://supportportal.juniper.net/JSA70594 [juniper.net] for more information.
PR Number	Synopsis	Category: QFX EVPN / VxLAN
1721322	The dcpfe process crash will be observed in the EVPN-VXLAN multihoming scenario Product-Group=junosvae	On Junos QFX and EX platforms that are deployed in Ethernet Virtual Private Network Virtual Extensible LAN (EVPN-VXLAN) with multihoming scenario, a memory leak will be observed by the creation of the Shared VxLAN overlay Load balancing Next-Hop (SVLBNH) in the Packet Forwarding Engine (PFE). As a result, the dcpfe process will crash leading to service disruption. Refer to https://kb.juniper.net/TSB70548 [juniper.net] for more information.
PR Number	Synopsis	Category: QFX5200/5110/5120/5210 Platfom issues
1711407	When a 100G transceiver is used as a VC port or network port, the VC port or network port will either not come up or come up as 40G Product-Group=junos	On Junos QFX5110 and QFX5120 platforms, when a 100G transceiver is used as a Virtual Chassis (VC) Port or network port, the VC port or network port will either not come up or come up as 40G.
PR Number	Synopsis	Category: SFW, CGNAT on MS-MIC/MS-MPC (XLP)
1713725	IPv6 Fragmentation is not working on MS-MPC/MS-MIC in DS-Lite scenario Product-Group=junos	On all Junos MX platforms with MS-MPC/MS-MIC cards in DS-Lite(Dual-stack Lite) scenario , Address Family Transition Router (AFTR) always failed to fragment newly generated IPV6 packet that has packet size larger than mtu-v6 value. packet will be dropped and will not reach to the softwire initiator (B4)
PR Number	Synopsis	Category: SSL Proxy functionality on JUNOS
1716893	The SSL session drops because of the wrong SNI value Product-Group=junos	On Junos SRX platforms supporting SSL proxy, Server Name Indication (SNI) value changes in session resumption and if some residual info from other sessions is present in reused pool memory then it causes a comparison failure and eventual session drop.
PR Number	Synopsis	Category: Junos Automation, Commit/Op/Event and SLAX
1642991	BNG Controller: L2TP LAC functionality is not working in this release Product-Group=junos	L2TP LAC functionality is not working in this release
1689567	Translation scripts from new image not being used for validation during upgrade Product-Group=junos	On all Junos platforms, when performing software add/validation, configuration validation may fail because during validation translation scripts from the old(current) image is used instead of the translation scripts from the new image.
PR Number	Synopsis	Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1638847	The mustd process crash might be observed with persist-group-inheritance Product-Group=junos	On all Junos and Junos Evolved platforms configured with persist-group-inheritance, which is enabled by default from 19.4R3 onwards, might lead to mustd process crash in highly scaled configuration.
PR Number	Synopsis	Category: Issues related to NETCONF
1709056	Unable to upgrade Junos using NetConf or Junos script Product-Group=junos	On all Junos and Junos OS Evolved platforms, if RPC get-configuration is invoked before RPC request-package-add in the same session of the NETCONF or Junos script, RPC request-package-add will not work.
PR Number	Synopsis	Category: Issues related to all UI tools (mgd-bsd/cli-bsd, XML and DMI
1681656	System uptime display is shown in minutes instead of seconds Product-Group=junos	On all Junos and Junos Evolved platforms, after the device reboot, show system uptime command is showing time in minutes instead of seconds for 24 hours.
PR Number	Synopsis	Category: usf nat related issues
1646822	NAT session reverse traffic fails due to NAT routes getting deleted from routing instance. Product-Group=junos	With overlapping NAT pool configured with different NAT rules under different service sets, when service outside interface is moved between different routing instances (EX: from vr1 to default, and from default to vr1), NAT routes corresponding to the service-set in default routing instance are getting deleted, resulting in reverse path traffic failure for NAT sessions.

22.3R2-S1 - List of Known issues

PR Number	Synopsis	Category: JUNOS bugs found in UAC integration
1692398	Connection fails are observed on Junos despite a valid auth entry Product-Group=junos	On Junos platforms, authentication failures and connection drops are observed for a few users when UAC (Unified Access Control) modules fail to look up the roles. Resolved In: junos:20.4R3-S7 junos:21.2R3-S5 junos:21.4R3-S4 junos:22.2R3-S1 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1
PR Number	Synopsis	Category: EX4300 Platform implementation
1701444	EX4300-48MP: :Interface operational states shows up even when interface as made down administratively. Product-Group=junos	When a port is disabled, the operation state will be shown as Up. This is only a display issue and has no funtionality impact as the port is actually down. Resolved In: junos:21.4R3-S4 junos:22.2R3-S1 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1
1708123	QSFPs are displayed as UKNOWN after the upgrade Product-Group=junos	On EX4300 & EX4300MP platforms, QSFPs are displayed as UKNOWN after the upgrade. Resolved In: junos:21.4R3-S3 junos:22.2R3 junos:22.3R2 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.2R1
PR Number	Synopsis	Category: EX4400 PFE software
1731522	The traffic drop will be observed after changing the VSTP vlan configuration Product-Group=junos	On EX4400, EX4100, EX2300, EX3400, and QFX5K platforms, a traffic drop would happen on an RSTP (Rapid Spanning Tree Protocol) enabled port attached to a vlan when the same vlan has VSTP (VLAN Spanning Tree Protocol) enabled and there is a configuration change done on VSTP for that vlan. Resolved In: junos:21.4R3-S4 junos:22.2R3-S1 junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2
1733365	EX4400: Syslog 'dot1xbd_get failed' are captured during MAC-Move in a heavily loaded device. Product-Group=junos	In a heaviliy loaded system in a specific scenario (Dot1x in multiple supplicant mode & dynamic vlan from radius server & non vxlan access port) following log message may be captured in the syslog - {brcm_as_dot1x_vxlan_set_mac_learning_mode:1168 dot1x bd_get failed for bd index 0}. This log is not impacting any funtionality. Resolved In:
PR Number	Synopsis	Category: EX4400 platform
1697678	EX4400: Output of 'show chassis led' does not reflect accurately for port beacon configuration Product-Group=junos	When the beacon LED for a port is configured as OFF, output of 'shot chassis led' incorrectly shows it as GREEN instead of OFF. When the beacon LED for a port is configured as ON, output of 'shot chassis led' incorrectly shows it as GREEN instead of 'GREEN Blinking'. Physical LED behavior reflects correctly as per beacon configuration Resolved In:
1700309	EX4400: pps counter does not show correct values for jubmo frames Product-Group=junos	When packets of size bigger than 1518 Bytes are received/transmitted, pps counter value does not show correct value. Resolved In:
1724188	EX4400: Flow control shows as disabled at pfe, even after enabling it Product-Group=junos	Flow control state does not show updated value in pfe cli when flow-control for a port is enabled or disabled. This is a display issue with PFE level flow control status, with no functional impact. Need to hard reboot the device or the dcpfe process restart to show correctly updated value Resolved In: junos:22.2R3-S1 junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R1
1725406	'Reboot all-members at now' does not work for all members of a VC Product-Group=junos	Cli "request system reboot all-member at now" may not work for all members of a VC. "Reboot AT now" is not recommended to be used. Recommendation is to use reboot command for each member. Resolved In:
1725683	EX4400: After BIOS upgrade device mode gets changed from hgoe to higig mode Product-Group=junos	After BIOS upgrade of EX4400-VC, device mode will be changed to HiGig mode if they are operating in HGoE mode earlier. Resolved In: junos:22.2R3-S1 junos:22.4R3 junos:23.1R2 junos:23.2R2
1726148	EX4400: In rare scenarios, PoE related error message might be logged in a very heavily loaded system. Product-Group=junos	Below error Messages may be observed randomly when a system is heavily loaded. {PoE poe_read_response: Wait for i2c module of PoE MCU to reset! CMQFX_BT_POE_PERIODIC_STATUS_ERR: poe_msemi_bt_stop_transaction: PoE controller transactions are being stopped!} There is no functional impact dut to such error messages Resolved In: junos:22.4R3
1726532	EX4400: FPC temperature value is exported incorrectly as 0 in Telemtery server Product-Group=junos	When data is streamed through telemetry with subscription to path /components/component, there is no data present for FPC temperature hence exporting as value 0. There is no functionality impact due to this issue. There is no a workaround for this issue. Resolved In: junos:21.4R3-S4 junos:22.2R3-S1 junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R2
1727609	EX4400: Firmware upgrade failed and device got stuck during upgrade Product-Group=junos	Once BIOS upgrade is triggered and it is interrupted by any operation which causes power loss to the system then the BIOS upgrade will fail, and system will land in unusable state. Resolved In:
1728725	EX4400 VC: During upgrade/reboot , fxpc core may be seen in a very rare race condition Product-Group=junos	issues aren't always seen. test cases are pre-provisioned and pfe planned restart conditions are randomly seen due to race conditions. System will auto recover after dcpfe core. Resolved In: junos:22.2R3-S1 junos:22.3R3 junos:23.2R1
1729464	EX4400: While exporting telemetry data, transceiver data is also streamed when there is no transceiver in device itself. Product-Group=junos	When data is streamed through telemetry, transceiver data is also streamed, even when there is no transceiver in device itself. There is no functional impact. There is no workaround for this issue. Resolved In:
1731345	EX4400: Some log messages may get flooded in heavily loaded system. Product-Group=junos	In rare scenarios in a heavily loaded system when syslog level is set to all, following log messages may get flooded - { ifinfo[72742]: PVIDB: Attribute 'ifinfo.pad_to_minimum_frame_size' not present in Db}. Recommendation is not to set syslog level to all. Resolved In: junos:22.2R3-S1 junos:22.3R3 junos:23.2R1 junos:23.2R2
1733920	EX4400: When SFPP-10G-T optics insterted in EX4400, IFD doesnt get created Product-Group=junos	When SFPP-10G-T transceiver is inserted in PIC0 ports of EX4400-48F, IFD will not be created. Resolved In: junos:21.4R3-S4 junos:22.2R3-S1 junos:22.4R3
PR Number	Synopsis	Category: EX POE
1713545	EX4400: Booting the device having LLDP PDs connected with perpetual PoE configuration may take longer time to update the LLDP negotiated value in CLI output of 'show poe interface'. Product-Group=junos	Booting the device having LLDP PDs connected with perpetual PoE configuration enabled will take time to update the negotiated value in CLI (show poe interface). Resolved In:
PR Number	Synopsis	Category: ISIS routing protocol
1667575	When the SPF algorithm for IS-IS in Segment Routing use case is triggered frequently, CPU usage might increase Product-Group=junos	On all Junos and Junos Evolved platforms, when the shortest-path-first (SPF) algorithm for IS-IS is triggered frequently, CPU usage might increase and impact the device performance and traffic. Resolved In: evo:22.4R1-EVO junos:22.4R1
1719033	The rpd process crashes when TI-LFA is enabled Product-Group=junos	On all Junos and Junos Evolved platforms, the rpd is seen to crash when TI-LFA (Topology-Independent Loop-Free Alternate) is enabled and there are ECMP (Equal-Cost Multipath) routes present. Resolved In: evo:22.3R3-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R1-S1 junos:23.1R2 junos:23.2R1
PR Number	Synopsis	Category: JFlow bug tracker for SRX platforms
1716707	J-flow sends wrong IP in sampling records when NAT is configured for traffic along with input sampling Product-Group=junos	When NAT (Network Address Translation) is configured on interfaces along with sampling, the J-flow record will contain NAT'ed IP as opposed to the original IP. Resolved In: junos:20.4R3-S7 junos:22.4R2
PR Number	Synopsis	Category: PFE infra to support jvision
1703418	gNMI line card (PFE) sensor paths may have packet drops Product-Group=junos	When subscribing to sensor paths "/junos/system/linecard/packet/usage/", "/junos/services/label-switched-path/usage/" or other line card (PFE) sensor paths in gNMI subscription mode, packet drops may be seen in the CLI command "show network-agent statistics gnmi detail" output. The collector output may also contain missing sequence numbers. For example, the sequence number output may be 0, 3, 6, 9, 12, etc. instead of 0, 1, 2, 3, 4, etc. Resolved In:
PR Number	Synopsis	Category: QFX5200/5110/5120/5210 Platfom issues
1710855	The FPC will be offline after upgrading the system Product-Group=junosvae	On the Junos QFX5100 platform, after upgrading the system to the affected TVP/5e releases the PFE (Packet forwarding Engine) will crash continuously and Flexible PIC Concentrators (FPC) will remain down. TVP/5e Junos only needed if mixed VC of QFX5100 & QFX5110 need to form. Resolved In: junos:20.2R3-S7 junos:20.4R3-S7 junos:21.1R3-S5 junos:21.3R3-S4 junos:21.4R3-S3 junos:22.1R3-S2 junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.1R2 junos:23.2R1
PR Number	Synopsis	Category: Remote Access VPN issues on SRX
1715297	The nsd process may report an error msg Product-Group=junos	On SRX platforms, nsd process may report an error msg during the commit. Resolved In: junos:21.4R3-S4 junos:22.2R3-S1 junos:22.4R3 junos:23.1R2 junos:23.2R1
PR Number	Synopsis	Category: Issues related to YANG Data Models
1726505	EX4400:Device schema Datatype validation fails for JTI. Product-Group=junos	Device schema leaf may not populate the appropriate values through jvision/telemetry Resolved In:

Modification History

2023-05-17 Update to include late identified Open Issues
First publication 2023-05-12