22.1R3-S2: Software Release Notification for JUNOS Software Version 22.1R3-S2

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.1R3-S2 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.1R3-S2 is now available.

22.1R3-S2 - List of Fixed issues

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.
1706845	Layer 3 forwarding issues for IRB Product-Group=junos	On EX2300, EX3400, EX4400, EX4100 and EX4300-MP platforms, when master FPC with mac-persistence-timer configured on a virtual chassis switch is halted, it leads to layer 3 (l3) forwarding issues for the integrated routing and bridging (IRB).
PR Number	Synopsis	Category: EX2300/3400 platform
1695057	The l2cpd telemetry crash would be observed when the LLDP Netconf notification from external controllers along with Netconf services configuration is present on the device Product-Group=junos	On all Junos and Junos Evolved platforms, configuring Link Layer Discovery Protocol (LLDP) with "system services netconf notification" enabled will trigger the l2cpd crash. This crash causes the CPU to spike.
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: JUNOS kernel/ukernel changes for ACX
1713699	The member interface will not be added to the AE bundle if the link-speed of the AE interface doesn't match that of the member Product-Group=junos	On Junos ACX5048 and ACX5096 platforms, if the link-speed is configured under the aggregated-ether-options hierarchy of the Aggregated Ethernet (AE) interface and the link-speed value does not match with the member link-speed, the member interface will not be added to the AE bundle.
PR Number	Synopsis	Category: MPC Fusion SW
1716766	A 10G port on a MPC2E or MPC3E 4x10G MIC can randomly flap constantly every few seconds Product-Group=junos	On Junos MX platforms, the interface flaps in every few seconds on the 10G port on 4x10G MIC on MPC2E-NG or MPC3E-NG card whatever cause the interface to go down.
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
1689904	BGP LU Advertisements fail with the message "BGP label allocation failure: Need a gateway" Product-Group=junos	On all Junos and Junos Evolved platforms BGP-LU (Border Gateway Protocol Labeled-Unicast) Advertisements fail with the message "BGP label allocation failure: Need a gateway" based on timing conditions involving route resolution and installation.
1695062	Traffic blackholing is observed when removing the BGP routes take a long time to get removed from RIB Product-Group=junos	On Junos platforms, if a BGP (Border Gateway Protocol) peer is going down and stays down and the system might take an extremely long time to complete removing the BGP routes. The issue observed when a BGP peer sends many routes, only a small amount of routes are selected as the active routes in the RIB (Routing Information Base), and if the BGP delete job gets only a small part of the CPU time as other work in the routing process utilize the CPU.
1712406	IPv4 routes learnt over a link-local BGP session not advertised ahead to other BGP peers Product-Group=junos	When rib (Routing Information Base) contains IPv4 routes with IPv6 next-hops, these routes do not get re-advertised by IPv4 EBGP sessions unless export policy is configured to change it to IPv4 next-hop.
PR Number	Synopsis	Category: BBE Remote Access Server
1695956	The interim-rate under radius-options feature is not working post implementing BBE statistics performance and scale improvements Product-Group=junos	On all Junos platforms interim-rate under radius-options feature missing in Broadband Edge (BBE) scenario on the 18.4 release onwards which could cause more than the configured interim-rate per second at the radius server.
1710145	High CPU utilization is seen on Junos MX series platforms Product-Group=junos	This issue is seen on Junos MX series platforms that support authd process. when authd traces are enabled in scale setup with 10k+ routing instances, authd will keep generating some logs. These logs consumes CPU cycles and makes authd process to utilize 100% CPU.
1715490	IPv4 and IPv6 address allocation will be impacted due to changes in address pool configuration Product-Group=junos	On all Junos platforms with address assignment pools configured, after changing, deleting, adding the IP address pools and moving the prefix ranges among the pools in a single commit would impact the IP address allocation process. This happens because of the overlapping of address prefixes in the pools.
PR Number	Synopsis	Category: Virtual-chassis platform/chassisd infrastructure PRs for MX
1706268	FPC offline can be seen on MX-VC during the sequential upgrade Product-Group=junos	On Junos MX-VC (Virtual Chassis), CCL (Chassis Control Link), and CRC (Cyclic Redundancy Check) errors can be seen after FPC (Flexible PIC Concentrator) detach during the sequential OS (Operating System) upgrade of MX-VC system. The CCL and CRC errors are expected after the FPC detaches and eventually, the FPC is marked offline by the MX-VC and there is an unexpected chassisd process restart. The chassisd restarted because of the connection failure between LCC (Linecard Chassis Control) chassisd and SCC (Switch Chassis Control) chassisd which is triggered by the sequence of messages exchanged between the LCC and SCC after the FPC detach event. There will be a traffic impact as the FPC will be offline, and the system recovers to a working state by itself.
1713502	The firmware upgradation will fail for MPC7E line card in MX-VC scenario Product-Group=junos	On MX-VC platforms, the MPC7E firmware upgrade cannot be completed due to the TFTP (Trivial File Transfer Protocol) timeout error due to which the firmware image can't be put into FPC and the upgrade will not get succeed.
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: QFX Access Control related
1705490	EAP authentication might not be successful with 802.1X server-fail configuration Product-Group=junos	On all Junos and Junos OS Evolved platforms, in the case of server-fail scenarios for Extensible Authentication Protocol (EAP) based authentication, the supplicant will be shown as authenticated but the supplicant failed to get authenticated. This will impact the users not being authenticated even if the server-fail fallback option is configured as permit.
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: QFX Control Plane VXLAN
1712805	The generation of the VXLAN table appears to be lost after loading configuration Product-Group=junos	On all Junos and Juos OS Evolved platforms that have EVPN-VXLAN enabled, the generation of the VXLAN table and the message during the setup of the EVPN/VXLAN connection seems to get lost because of a timing issue between the layer2 address learning daemon(l2ald) and routing protocol daemon( rpd ) connections.
PR Number	Synopsis	Category: Layer 3 forwarding, both v4+v6
1712564	Transit traffic drop is observed for the BGP-LU route prefixes with ECMP forwarding path on Junos ACX5448/ACX710 platforms Product-Group=junos	On Junos ACX5448/ACX710 platforms, if the BGP-LU route prefixes points towards the ECMP forwarding path, the transit traffic drop is observed for the BGP-LU routes, due to the incorrect programming for the routes.
PR Number	Synopsis	Category: ACX LAG infrastructure
1714111	The traffic through the AE member link will be dropped Product-Group=junos	On ACX5448 and ACX710 platforms, when the Aggregate Ethernet (AE) interface is configured with tagging-mode (e.g flexible-vlan-tagging) but without any encapsulation and the member port is added to the AE interface after service creation, then the ingress traffic through the member port will be dropped as it was not yet part of the AE interface.
PR Number	Synopsis	Category: ACX IFL, IFF creation
1691004	The PFE process crashes on ACX5448 Product-Group=junos	On Junos ACX5448 platforms, the PFE (Packet Forwarding Engine) process will crash after continuous IFD (Interface Device) flaps. As a result, all traffic will be lost until the process recovers on its own.
PR Number	Synopsis	Category: Gnats category for dynamic rendering infrastructure
1698192	EVO jkey path changed under protocol/isis. "isis/levels" is missing Product-Group=junos	When using the proprietary subscribe RPC for telemetry, the "isis/levels" keyword is missing from the jkey output for leaf lists.
1706708	evo-aftmand-zx not responding, ping, arp not working after unsubscribing some telemetry sensors. Product-Group=junos	After unsubscribing certain telemetry sensors, evo-aftmand-zx becomes unresponsive due to a deadlock problem.
1714120	PICD core is seen on LC120x line cards after starting the Jvision decoder Product-Group=junos	PICD and EVOAFTMAND will crash just by unsubscribing /component or /interface sensor which uses AFT telemetry infra.
PR Number	Synopsis	Category: PRs related to software Agentd daemon on EVO
1697986	The agentd process crash might crash in a telemetry scenario Product-Group=junos	On all Junos Evolved platforms, the agentd process will crash when the telemetry sensor name is greater than 64 characters. The crash will only impact RPD related telemetry services.
PR Number	Synopsis	Category: jdhcpd daemon refactored for evo
1707690	[dhcp] [DHCP_RELAY] ACX7100-48L :: Getting commit error for the dhcp config commit and then it is coring with the bt jtimer_start_oneshot Product-Group=junos	During commit of configuration related to active-leasquery requires initialization of timers. However, in Junos Evolved system, the timers were not initialized correctly. This caused commit check error.
PR Number	Synopsis	Category: EVO L2 Control Plane PRs
1703226	The l2ld process will crash when an IFL is changed to trunk mode and a new VLAN is added Product-Group=junos	On all Junos Evolved platforms, the Layer 2 address learning daemon (l2ald) process will crash when there is a scaled configuration to commit and a Logical Interface (IFL) mode is changed from access to the trunk and a new Virtual Local Area Network (VLAN) is added to the IFL in a single commit. This issue will impact new MAC learning until the l2ald process recovers.
1713640	On PTX10001-36MR the VXLAN tunnel termination functionality impacted with global configuration not enabled Product-Group=junos	On Junos Evolved PTX10001-36MR platform, the VXLAN(Virtual Extensible LAN) tunnel termination functionality will be impacted when configuration is not enabled for tunnel termination. As the tunnel will not get terminated this will impact the packet forwarding process.
PR Number	Synopsis	Category: EVPN Layer-2 Forwarding
1712259	The Anycast Gateway stretched across 2 DCs over the seamless MPLS stitching DCI does not have Anycast Gateway MAC information coming from the remote DC when VLAN and VNI ids are different Product-Group=junos	On all Junos and Junos OS Evolved platforms, the AnyCast Gateway stretched across 2 Data Centres (DC) over the Data Centre Interconnect (DCI) using seamless Multiprotocol Label Switching (MPLS) stitching through Interconnect knob and having different VLAN and Virtual Network Identifier (VNI) ids (e.g., VLAN ID 101 <-- -> VNI 1101), then upon deactivating the Integrated Routing and Bridging (IRB) interface on all the gateways within DC, the AnyCast Gateway MAC information coming from Interconnect-Ethernet Segment Identifier (I-ESI) will not be available in the bridge mac-table and thus, the Inter VLAN/VNI routing will be impacted.
PR Number	Synopsis	Category: EX4400 PFE software
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.
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: Express PFE MPLS Features
1712076	FPC memory leak will cause FPC crash Product-Group=junos	On PTX and QFX10K platforms, enabling the collection of LSP (label-switched path) statistics for telemetry data using the CLI command 'set protocols mpls sensor-based-stats' will cause FPC (Flexible Physical Interface Cards (PIC) Concentrators) memory leak and a huge leak may result in FPC crash.
PR Number	Synopsis	Category: MX Inline Jflow
1708485	The Inline Flow Monitoring is not working on Junos MX-VC platforms Product-Group=junos	In a Virtual-chassis (VC) scenario on Junos MX platforms installed with MPC7E Flexible PIC Concentrators (FPC), if the inline-jflow Sampling is enabled, the Inline Flow Monitoring will not work as data is not getting exported to the collector.
PR Number	Synopsis	Category: jdhcpd daemon
1693124	phone-home and SZTP may fail if phone-home daemon restarts Product-Group=junos	Onboarding device with Phone-home or SZTP fails in rare cases where phone-home daemon restarts.
1713619	A jdhcpd process crash is observed on all Junos platforms Product-Group=junos	On all Junos platforms with DHCP (Dynamic Host Configuration Protocol) relay/server/client configured, a jdhcpd process crash is observed when FPC (Flexible PIC Concentrator) is restarted or rebooted and the DHCP functionality could be impacted.
1714260	The DHCPv4 relay will send two option-82 to the server and the DHCP session will not be established Product-Group=junos	On all Junos and Junos OS Evolved platforms, when Dynamic Host Configuration Protocol (DHCPv4) Relay is configured with forward-only mode along with "trust-option-82", DHCP-relay should not add another option 82 to the packet sent to the DHCP server. The DHCP server upon receiving the packet with two option-82 will respond only with 1st header of option-82 which might get dropped by the relay, thus the packet is not forwarded to the DHCP client and the DHCP session won't get established.
PR Number	Synopsis	Category: Adresses ALG issues found in JSF
1688986	H.323 traffic failure caused by RAS packet drops when incorrect route lookup performed Product-Group=junos	On SRX platforms, due to incorrect route lookup performed for default routing-instance instead of ingress routing-instance results in RAS (Registration, Admission, and Status) packet drops for which H.323 traffic failure is observed.
PR Number	Synopsis	Category: High Availability/NSRP/VRRP
1686648	Policy configured with condition route-active-on import is not working properly after RG0 failover Product-Group=junos	In a specific scenario, condition route-active-on import is not working properly after RG0 failover.
PR Number	Synopsis	Category: all logging related bugs on srx platforms
1708777	Setting the security log profile without a category or stream will lead to srxpfe process crash Product-Group=junos	On all Junos SRX platforms, when security log profile is added without a category or stream can cause the srxpfe to crash. Due to this there will be complete traffic loss.
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
1696102	IPsec VPNs will disconnect after ISSU Product-Group=junos	On SRX platforms except SRX5K, & vSRX2.0/vSRX3.0, traffic will not pass over IPsec (Internet Protocol Security) VPN tunnels after ISSU (In-service software upgrade).
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: Security platform jweb support
1712454	[Jweb] "address-book attach zone" is unexpectedly removed when address-book entry is added or removed by Jweb Product-Group=junos	On SRX platform series, when address-book entry is added or removed by Jweb, "address-book attach zone" might be unexpectedly removed at configuration commit.
PR Number	Synopsis	Category: Layer2 forwarding on EX/NTF/PTX/QFX
1716270	mac-move-limit : MMAS flag not getting reset after interface recovers due to l2-learning restart Product-Group=junos	MMAS Flag will not be displayed for interface after it recovers due to l2-learning process restart
1716881	"set forwarding-options evpn-vxlan shared-tunnels" command will not be available for EX92XX and MX series platforms Product-Group=junos	Presence of "set forwarding-options evpn-vxlan shared-tunnels" configuration is causing mpc cores in EX92XX and MX series platforms
PR Number	Synopsis	Category: Issues related to Junos licensing infrastructure
1686654	Subscribers are not able to connect to the device after the device reboot Product-Group=junos	Due to a rare timing issue all subscribers may fail to connect and get suck in init state after reboot of MX broadband network gateway (BNG).
PR Number	Synopsis	Category: Port-based link layer security services and protocols that a
1711422	A dot1xd crash is seen on Junos EX2300 platforms Product-Group=junos	On Junos EX2300, if the Master Session Key (MSK) parameters are received from RADIUS (Remote Authentication Dial-In User Service) as part of authentication, a dot1xd crash could be observed which will impact the authentication on the dot1x enabled ports.
PR Number	Synopsis	Category: Application specific PRs (cos/snmp/time-sync/routing/BRAS)
1712790	The traffic is dropped while passing through VCP link on MX Virtual Chassis with MPC10 line card Product-Group=junos	The packets are being dropped when they come from the VC (Virtual Chassis) link into member in the MX Virtual Chassis with MPC10 line card.
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.
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: QFX access control list
1710704	FPC is down on QFX5k after committing an IPv6 filter Product-Group=junos	On Junos QFX5k series platforms, traffic is getting dropped as FPC (Flexible PIC Concentrators) is not up. The issue is seen when a 'flexible-match-range' is configured in an IPv6 firewall filter term and that filter is applied to any IPv6 interface. FPC goes down after committing the filter.
1710776	The message "fpc0 list_get_head, list has bad magic (0x0)" maybe output after the commit operation is complete Product-Group=junos	When a VACL filter is added or deleted, the message "fpc0 list_get_head, list has bad magic (0x0)" maybe output.
PR Number	Synopsis	Category: QFX L2 PFE
1706515	DCPFE crashes which leads to FPC restart Product-Group=junos	On Junos QFX and EX platforms, the DCPFE (Dense Concentrator Packet Forwarding Engine) crashed continuously after configuring the unsupported telemetry sensor '/junos/system/linecard/npu/utilization/' leading to the restarting of FPC. Once FPC is restarted, traffic is impacted.
PR Number	Synopsis	Category: QFX L3 data-plane/forwarding
1695847	Traffic forwarding fails when deleting all L2 related configurations Product-Group=junos	On QFX and EX series platforms, traffic loss will be observed for deleting all Layer2 related configurations when both L2 and Layer3 configurations are present.
PR Number	Synopsis	Category: QFX EVPN / VxLAN
1712405	VXLAN traffic gets dropped after new L3 VLANs are created Product-Group=junos	Traffic black-holing in EVPN (Ethernet VPN) fabric when performing configuration of new VLANs, it is found that L3 VLANs are having IPV4 bits disabled.
PR Number	Synopsis	Category: QFX5200/5110/5120/5210 Platfom issues
1696119	Traffic drop is observed for the VCP ports when there is traffic congestion in the egress queues Product-Group=junos	On QFX5110 with Virtual Chassis configured, if any of the egress queues 3 or 4 is congested it causes buffer stuck error messages and traffic drop on the VCP (Virtual Chassis port) ports.
1709938	VC members are split when removing and inserting em0 cable Product-Group=junosvae	On QFX5120-48YM, QFX5120-48Y-8C, QFX5120-32C and EX4650-48Y platforms, when the management em0 cable is removed and reinserted in the Virtual Chassis (VC) environment, the VC members will split into separate VCs. The VC members will remain in the split state for approximately 5 mins.
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
PR Number	Synopsis	Category: Shard routing infrastructure within RPD
1710829	AIGP not distinguished with BGP-LU when rib-sharding is enabled Product-Group=junos	On all Junos platforms, BGP LU (Border Gateway Protocol Labeled Unicast) routes with AIGP (Accumulated Interior Gateway Protocol) metrics are not used when sharding is enabled, causing the incorrect route (having a high metric) to be selected as active.
PR Number	Synopsis	Category: Resource Reservation Protocol
1713392	PathErr with RoutingProblem error code generated unexpectedly during dual failure local repair Product-Group=junos	When an LSR acts as a Point of Local Repair (PLR) as well as a Merge Point (MP) for an LSP during a double failure scenario, the LSR incorrectly originates one or two PathErr messages with RoutingProblem (code=24/2) instead of originating PathErr with NotifyError (code/subcode=25/3). This will not cause any service impact if the ingress LER would not react adversely to RoutingProblem error (code=24/2).
PR Number	Synopsis	Category: SFW, CGNAT on MS-MIC/MS-MPC (XLP)
1701305	On Junos platforms with MS-MPC cards the IKE ALG inactivity timeout value stays fixed Product-Group=junos	On Junos platforms having MS-MPC (Multi-Service Modular PIC Concentrator), the value for the inactivity timeout for IKE (Internet Key Exchange) ALG (Application Level gateway) is automatically set to 14400 seconds even though a custom timeout value is configured by the customer. This issue is seen only in the case of IKEv1 having SFW (Stateful Firewall) without any NAT (Network Address Translation) configuration. When this issue is seen IKE transit tunnel sessions remain in the session table longer than expected, not honoring the configured timeout value. This issue is self-recoverable.
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: SRX branch platforms
1713759	Continuous vmcores observed on the secondary node when committing the "set system management-instance" command Product-Group=junos	On Junos SRX3xx series platforms, when the "set system management-instance" command is committed on the secondary node, continuous vmcores are observed on primary and secondary nodes. No recovery action is needed for the primary node and the secondary node of the cluster reboots automatically to recover from the error. The cluster redundancy is not restored until the management-instance knob is removed using the "delete system management-instance".
PR Number	Synopsis	Category: SSL Proxy functionality on JUNOS
1709386	The ECDSA certificate based websites are not accessible when the SSL proxy is enabled from 22.1R1 onwards Product-Group=junos	Webservers that have ECDSA (Elliptic Curve Digital Signature Algorithm) certificates will not be accessible when SSL (Secure Sockets Layer) proxy is enabled with P-384/P-521 ECDSA root certificates as they are not supported at the moment, SRX currently supports only P-256 ECDSA root certificates.
PR Number	Synopsis	Category: SRX-1RU platfom chassisd SW defects
1711467	SRX4600 doesn't support ae interfaces Product-Group=junos	On Junos SRX4600 platforms, ae interfaces doesn't come up or not work properly when configured in HA (High Availability) cluster mode.
PR Number	Synopsis	Category: SRX-1RU platfom related protocol, QoS, filtering features et
1712727	Continuous vmcores observed on the secondary node when committing set system management-instance command Product-Group=junos	On Junos SRX4600 device, when the "set system management-instance" command is synced to the secondary node, continuous VMcores are observed on primary and secondary nodes. 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: ZT/YT pfe qos software issues
1704129	Traffic is blocked on a queue when enhanced priority mode is configured Product-Group=junos	On MPC1-9, JNP10K-LC2101, JNP10003-LC2103, JNP10K-LC480 line cards, with scheduler map configuration change in enhanced priority mode, traffic is blocked on a queue.
PR Number	Synopsis	Category: Issues related to broadband edge apps (PPP, DHCP) on Trio ch
1706446	No network reachability when enabling the routing-service knob for PPPoE subscribers over AE Product-Group=junos	On all Junos platforms configured with PPPoE subscribers, when the PPPoE (Point-to-Point Protocol over Ethernet) subscriber is configured on the AE (Aggregated Ethernet) interface while enabling the routing-service knob, the service will not get enabled and the subscriber traffic gets impacted.
PR Number	Synopsis	Category: Junos Automation, Commit/Op/Event and SLAX
1689567	Translation scripts from new image not being used for validation during upgrade Product-Group=junos	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
1708321	MX960 :: CST:RE goes to amnesiac state, when rebooting the DUT -mgd: error: translation script failure Product-Group=junos	When a toggle attribute with variable is committed under dynamic-profiles hierarchy, upon reboot system will go to amnesiac mode
PR Number	Synopsis	Category: PTX/QFX100002/8/16 interface software
1712007	The interface does not come up or keeps flapping Product-Group=junos	On Junos PTX10008/PTX100016 devices with LC1101/LC1102 line cards, any event that causes an interface state change can lead to interface flapping or the interface may not come back at all. This leads to traffic impact on that interface.
PR Number	Synopsis	Category: Track Windriver Linux issues
1689100	Integration of RCP binary into the LTS19 code for Vmhost Platforms Product-Group=junos	With RCP, the system no longer depends on ssh root-login configuration when upgrading software. See https://kb.juniper.net/TSB18224 [juniper.net] and PR1660446
PR Number	Synopsis	Category: Xellent Platform issues
1709817	Ports with QSA adapter are down Product-Group=junos	On Junos PTX1000 and PTX10002-60C/QFX10002-60C platforms, ports which use the QSA (QSFP-to-SFP Adapter) may not come up when running software version containing the fix for PR 1620527.

22.1R3-S2 - List of Known issues

PR Number	Synopsis	Category: EX4300 Platform implementation
1668414	On EX4300-48MP, NSSU abort is seen with "error: rebooting VC". VC instability and dc-pfe core is observed after reboot. Product-Group=junos	On EX4300-48MP, NSSU abort is seen with "error: rebooting VC". VC instability and dc-pfe core is observed after reboot. Resolved In:
PR Number	Synopsis	Category: EX2300/3400 PFE
1685938	MAC address learning might not happen on specific EX/QFX platforms Product-Group=junos	On specific EX/QFX platforms (EX2300/EX3400/EX4300-MP/EX4100/EX4400/QFX5K), MAC learning is not happening in any of the interfaces of the particular VLAN (contains both LAG (Link Aggregation Group) and non-LAG interfaces) when VSTP (VLAN Spanning Tree Protocol) is enabled on LAG interface with no child interface and VSTP is disabled for non-LAG interfaces. It causes a traffic impact as mac address learning does not happen for all interfaces on the VLAN. Resolved In: junos:20.4R3-S5 junos:21.1R3-S4 junos:21.2R3-S3 junos:21.3R3-S3 junos:21.4R3-S3 junos:21.4R3-S4 junos:22.1R3 junos:22.2R2 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:23.1R1
PR Number	Synopsis	Category: EX2300/3400 platform
1580560	On EX2300, EX3400, :EX4300-48MP and EX4300 , Pause frames counters does not get incremented when pause frames are sent. Product-Group=junos	On EX2300, EX3400, :EX4300-48MP and EX4300 , Pause frames counters does not get incremented when pause frames are sent. Resolved In:
1695057	The l2cpd telemetry crash would be observed when the LLDP Netconf notification from external controllers along with Netconf services configuration is present on the device Product-Group=junos	On all Junos and Junos Evolved platforms, configuring Link Layer Discovery Protocol (LLDP) with "system services netconf notification" enabled will trigger the l2cpd crash. This crash causes the CPU to spike. Resolved In: evo:21.4R3-S4-EVO evo:22.1R3-S2-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.3R3-EVO evo:22.4R1-S2-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:21.2R3-S5 junos:21.4R3-S4 junos:22.3R2 junos:22.3R3 junos:22.4R1-S2 junos:22.4R2 junos:23.1R1 junos:23.2R1
PR Number	Synopsis	Category: Anything related to Multicast
1461339	Mcast traffic drops is observed with the following error message: brcm_rt_ip_mc_ipmc_install. Product-Group=junos	Following two Failure messages seen brcm_rt_ip_mc_ipmc_install:2455 Failed (Invalid parameter:-4) This message is due to IPMC Group being used is not created, when RE tried to add this check indicates there is a parameter mis-match. brcm_rt_ip_mc_ipmc_install:2455 Failed (Internal error:-1) This message is due to Failure to read IPMC Table or any memory/register Resolved In:
PR Number	Synopsis	Category: BBE dynamic profile related issues
1714778	PPPoE subscriber connection on dynamic VLAN can fail on Junos MX platforms Product-Group=junos	On Junos MX platforms supporting subscriber services, cleanup of a dynamic VLAN (Virtual Local Area Network) session may fail if SDB (Subscriber Database) becomes briefly unavailable. The dynamic VLANs will stay in an active state, but all PPPoE (Point to Point Over Ethernet) subscriber connection attempts over this VLAN will fail. Resolved In: evo:22.3R3-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:20.2R3-S4-J9 junos:21.2R3-S5 junos:21.4R3-S2-J9 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: the SMGD redundancy plugin in SMGD
1718342	In a DHCP ALQ subscriber scenario delete-binding-on-renegotiation knob does not work as expected due to a synchronization error between the primary and the backup routers Product-Group=junos	On Junos platforms, active lease query (ALQ) synchronization between peers is not happening properly. Traffic forwarding impact would be observed if there was a switchover from the Primary to the Backup. The primary router will correctly delete-binding-on-renegotiation and create a new session, but the backup router keeps the old session and old MAC address. (DHCP overrides have delete-binding-on-renegotiation configured and work as expected on the primary router whereas no notification is sent to the backup to delete the session) Resolved In: evo:22.3R3-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO 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: BBE Remote Access Server
1709574	Externally assigned IP address subscriber sessions logout after GRES Product-Group=junos	externally assigned IP address subscriber sessions might get terminated if: 1 - The knob "address-protection" is not enabled under the access profile configuration 2 - GRES (Graceful Routing Engine Switchover) occurred GRES termination code: aaa shutdown-administrative-reset Note:The issue is not seen if the user uses a local pool for address assignment. Resolved In: evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R2-EVO evo:23.2R1-EVO junos:21.2R3-S4-J12 junos:21.2R3-S4-J13 junos:21.2R3-S5 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.1R2 junos:23.2R1
PR Number	Synopsis	Category: Device Configuration Daemon
1692404	Incompatible/unsupported configuration is not getting validated correctly during ISSU/normal upgrade causing the traffic loss Product-Group=junos	On all Junos platforms, while performing the Junos upgrade from the release before 20.4 to a higher version having an incorrect configuration may fail. This issue may lead to traffic loss or network outages. Resolved In: junos:20.4R3-S7 junos:21.2R3-S5 junos:22.2R3-S1 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.2R1
1712800	After each commit, some evpn interfaces are deleted and added back from lag, Logs "LAG: Deleting cifl" and "lag_add_cifl_to_pifl" Product-Group=junos	In case of evpn routing-instance, there will be an implicit bridge-domain created for VPLS route table.This BD index will be used by daemon DCD in successive commits. When igmp-snooping is enabled, mcsnoopd daemon publishes update on INET route table with BD index value 0, which is mismatching with the DCD. As a result, this might cause to flap ifls which are part of this routing-instance on successive commits. Resolved In: junos:21.4R3-S4 junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R1
PR Number	Synopsis	Category: DNX Multicast
1722277	The multicast packets could hit the CPU/RE on ACX5448 and ACX710 platforms Product-Group=junos	On Junos ACX5448 and ACX710 platforms, multicast packets could hit the CPU/RE when IGMP (Internet Group Management Protocol) snooping is enabled with v4 multicast data traffic running in a VLAN. 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
PR Number	Synopsis	Category: Firewall related development
1720389	Commit error will not be seen after deactivating routing-instance applied under firewall filter Product-Group=junos	On Junos OS Evolved platforms with enabled firewall filter, deactivating routing-instance which is already applied under the firewall filter, will not show any commit error after commit is issued. This can be seen occasionally and might impact control plane traffic. Resolved In: evo:21.4R3-S4-EVO evo:22.1R3-S3-EVO evo:22.2R3-S1-EVO evo:22.3R3-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R1-S1-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO 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: EX4400 platform
1696444	A serial number of SFP is not shown in "show chassis hardware" on EX4400. Product-Group=junos	When a sfp is unplugged or plugged in, it may not be recognized. Resolved In: junos:21.4R3-S4 junos:22.2R3-S1 junos:22.3R2-S1 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1
PR Number	Synopsis	Category: SRX4100/SRX4200 platform software
1630981	BGP down due to BFD expired; failover restored services Product-Group=junosvae	All VPN traffic may internally drop during encryption / decryption processing in HW engine requiring PFE plane reset. Resolved In: junos:20.4R3-S7 junos:21.4R3-S3 junos:23.2R1
PR Number	Synopsis	Category: jdhcpd daemon
1689005	DHCP packets might not be sent to the clients when 'forward-only' is reconfigured under the routing instance Product-Group=junos	On all Junos platforms, reconfiguring 'forward-only' in any routing instance is leading to deactivate of [default:default] jdhcpd filter. Dynamic Host Configuration Protocol (DHCP) packets might not be sent to the clients. Resolved In: evo:20.4R3-S7-EVO evo:21.2R3-S5-EVO evo:21.4R3-S4-EVO evo:22.2R3-S1-EVO evo:22.3R2-EVO evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:20.4R3-S7 junos:21.2R3-S5 junos:21.4R3-S4 junos:22.2R3-S1 junos:22.3R2 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.2R1
PR Number	Synopsis	Category: Layer 2 Control Module
1717267	Traffic loop is seen due to incorrect root bridge ID Product-Group=junos	On all Junos and Junos Evolved platforms, in VSTP (Virtual Spanning-Tree Protocol) topology, whenever a new vlan is added in between previously configured vlan group followed by configuring the system-identifier, the bridge priority will change for existing vlans which might give incorrect system ID or bridge ID creating a traffic loop. Resolved In: evo:21.2R3-S5-EVO evo:21.3R3-S4-EVO evo:21.4R3-S4-EVO evo:22.2R3-S1-EVO 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:20.4R3-S7 junos:21.2R3-S5 junos:21.3R3-S4 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: Microkernel for neo mpc
1670137	Multibit ECC error causes the whole MX platform chassis to go down Product-Group=junos	Faulty FPC (Flexible PIC Concentrator) on the MX platform chassis exhibiting multibit ECC (Error Checking and Correction) error (L2 cache error) will trigger this issue. The whole chassis goes down until the faulty FPC is removed from the chassis. Resolved In: junos:21.2R3-S4 junos:21.4R3-S3 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:22.4R2
PR Number	Synopsis	Category: Express Chip L3 software
1658317	BFD session session-state is showing DOWN while checking Micro BFD Sessions with Authentication in Non-Distributed Mode Product-Group=junos	BFD session session-state is showing DOWN when operating in centralized Mode. Packet loss may be seen. Resolved In: junos:21.2R3-S5 junos:21.3R3-S4 junos:21.4R3 junos:22.1R3 junos:22.2R2 junos:22.3R1 junos:22.4R1
PR Number	Synopsis	Category: PPPoE functional plugin for bbe-smgd
1701739	Some PPPoE subscriber connection lost during RE switchover Product-Group=junos	On all Junos platforms, when rpd is busy on standby RE in deleting routes from previous subscriber termination, and followed by new subscriber login in master RE and switchover performed. Some PPPoE subscriber won't come up on new master RE. Resolved In: evo:22.3R3-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:21.2R3-S5 junos:21.4R3-S4 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1
PR Number	Synopsis	Category: QFX PFE Class of Services
1688455	The FPC crash would be observed when the same CoS configuration is applied with wildcard for all the physical interfaces and AE Product-Group=junos	On all Junos platforms, in a scaled scenario when some of the ge/xe/et interfaces are members of Aggregated Ethernet (AE) and the Class of Service (CoS) forwarding-class-set configuration is applied with a wildcard for all the physical interfaces and AE, it would trigger a Flexible PIC Concentrators (FPC) crash which leads to traffic loss. Resolved In: junos:20.2R3-S6 junos:21.2R3-S5 junos:21.4R3-S1 junos:22.3R3 junos:22.4R2 junos:23.1R1
PR Number	Synopsis	Category: QFX EVPN / VxLAN
1688323	Traffic loss is observed in IP fabric when there is a change in the underlay network Product-Group=junos	On Junos QFX5K series platforms, configuration-change/protocol flapping/port flapping in Ethernet Virtual private network (EVPN) Virtual Extensible LAN (VXLAN) can cause traffic loss (changes related to the underlay network). Resolved In: junos:20.4R3-S7 junos:21.2R3-S5 junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R1
PR Number	Synopsis	Category: RPD route tables, resolver, routing instances, static routes
1716153	Multipath route is not getting compute and skip the multipath eligibility check Product-Group=junos	On all Junos platforms, multipath route will not be formed correctly when a BGP route is received from RR (Route Reflector) and preference decided based on cluster list length. Resolved In: evo:22.2R3-S1-EVO evo:22.3R3-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R1-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:21.4R3-S4 junos:22.2R3-S1 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R1 junos:23.1R2 junos:23.2R1
PR Number	Synopsis	Category: Secure Web Proxy functionality on Junos
1719703	The flowd process crash is observed when the web proxy packet reinjection fails Product-Group=junos	On SRX-branch series, SRX4100, SRX4200, and vSRX platforms, packet reinjection fails if the load on the system is high and the web proxy tries to reinject the packet. Resolved In: junos:20.4R3-S7 junos:21.2R3-S5 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1
PR Number	Synopsis	Category: MX10003/MX204 MPC defects tracking
1689644	A 1G port on a QSFPP-4x10G transceiver will be down sometimes after the FPC restart Product-Group=junos	On MX204 device, a QSFPP-4x10G transceiver configured at 1G speed sometimes stays down after a FPC restart. Traffic will not pass through the port. Resolved In: junos:21.2R3-S5 junos:21.4R3-S4 junos:22.1R3 junos:22.2R2-S1 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:22.4R2 junos:23.1R1
PR Number	Synopsis	Category: VMHOST platforms software
1686825	The pre-installed optional packages and JSUs will be lost after a VMHost rollback Product-Group=junos	On VMHost based platforms, the pre-installed optional packages and Junos Selective Update (JSU) packages will be lost when a VMHost reboot is performed after VMHost rollback. Resolved In: junos:21.2R3-S5 junos:21.3R3-S4 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: VSRX platform software
1711440	VLAN tagging does not work for vSRX3.0 on HyperV Windows Server 2019 Datacenter Product-Group=junos	VLAN tagging for vSRX3.0 on HyperV Windows Server 2019 Datacenter is not working. Resolved In: junos:21.2R3-S5 junos:21.4R3-S4 junos:22.2R3 junos:22.2R3-S1 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.1R2 junos:23.2R1
PR Number	Synopsis	Category: usf nat related issues
1718840	The PPTP connection itself won't work when trying to establish PPTP connection along with DSLITE Product-Group=junos	On Junos MX and SRX platforms with SPC3 cards, Point-to-Point Tunneling Protocol (PPTP) connection between client and server always failed along with Dual-Stack Lite (DSLITE) scenario. PPTP failure occurred due to Generic Routing Encapsulation tunnel (GRE) wrong call-id swapping that taken place by Address Family Transition Router (AFTR). Traffic will not pass through the tunnel at all as the tunnel does not establish. Resolved In: junos:20.4R3-S7 junos:21.2R3-S5 junos:22.2R3-S1 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1

Modification History

First Publication 2023-04-12