Article Detail

Alert Type

PSN - Product Support 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.2R3-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.2R3-S1 is now available.

22.2R3-S1 - List of Fixed 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.
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 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: EX4300 Platform
1720335	On EX4300-48MP I/O accesses to disk will fail Product-Group=junosvae	On EX4300-48MP due to a disk cache mode that is less resilient, in rare conditions, all the I/O (Input Output) accesses to the disk will fail including any configuration commands. The device might also go into an inaccessible state.
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.
1712785	EX4300-48MP CPLD firmware fails to upgrade from 2.2 to 2.5 with 22.4R1.10 image Product-Group=junosvae	EX4300-48MP CPLD firmware fails to upgrade from 2.2 to 2.5 with 22.4R1.10 image
1714056	On EX4650, jnxOperatingDescr.1.1.0.0 is populated with blank Product-Group=junosvae	On EX4650, jnxOperatingDescr.1.1.0.0 is populated with blank
PR Number	Synopsis	Category: EX2300/3400 platform
1716703	The link remains down on connecting the transceiver 10GBASE-T with the serial number starting with "2P1" Product-Group=junos	On all Junos EX platforms, the link does not come up when SFPP-10GE-T transceiver is plugged into the device with serial number starting with "2P1".
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: AFT l2lam
1721704	Sending GARP reply packet on a VTEP interface causes flooding in network on QFX5130 and QFX5700 platforms Product-Group=junos	On Junos OS Evolved QFX5130 and QFX5700 platforms, Gratuitous Address Resolution Protocol (GARP) flooding occurs in the network when it receives a GARP reply packet on a Virtual Tunnel End Point (VTEP) interface.
PR Number	Synopsis	Category: "agentd" software daemon
1702250	The xmlproxyd process crash is observed in telemetry scenario Product-Group=junos	On all Junos and Junos OS Evolved platforms, when telemetry services are enabled and the interleaving of telemetry streaming of more than one xmlproxyd sensors can lead to xmlproxyd process crash.
1712409	PCT : Show Ephemeral-Configuration Instance Junos-Analytics is not giving expected output while verifying the commit operation with new config hierarchy openconfig-telemetry:telemetry-system Product-Group=junos	Release note needed
1726205	Delete notifications for sub-interfaces missed in gRPC telemetry Product-Group=junos	On Junos platforms, delete notifications for deleted interfaces are not reported through gRPC(Remote Procedure Call) in Telemetry. There is no service impact however notifications on deleted interface are not received.
PR Number	Synopsis	Category: MX YT-ZF Linecards Interface Software Category
1706517	Delay in an interface on LC9600 to come up due to repeated flaps Product-Group=junos	There is a delay in an interface on LC9600 to come up sometimes due to SerDes re-initing triggered by repeating flaps. Each plane is made of one or several Fabric ASICs (Application-Specific Integrated Circuits). The Fabric ASIC is connected to all the PFE (Packet Forwarding Engine) with dedicated links called SerDes. The issue caused a delay in turning up the link from 30 seconds to 80 seconds depending on if the link partner undergoes the same delay. Traffic will not pass on the port until the link is up again.
PR Number	Synopsis	Category: MX Layer 2 Forwarding Module
1700073	The device is using the MAC address of the IRB interface even after configuring static MAC for a default gateway Product-Group=junos	On all Junos platforms supporting evpn-vxlan, on configuring static MAC (Media Access Control) address explicitly for a default gateway, the outer ethernet header of the packets are including the MAC address of the IRB (Integrated Routing and Bridging) interface instead of the configured virtual gateway MAC address.
PR Number	Synopsis	Category: a20a40 specific issue
1645817	Line cards fail to come online state when the device is powered on with multiple cards Product-Group=junos	On SRX5k and MX240/MX480/MX960 platforms, when device is powered on with multiple line cards, power might not be sufficient and few line cards fail to come into online state.
PR Number	Synopsis	Category: srx5k service offloading related PR
1702138	TCP packet drops are seen when services-offload is enabled Product-Group=junos	On Junos SRX5400, SRX5600, SRX5800 and SRX4600 Platforms, packet drops may be observed while services-offload is enabled.
PR Number	Synopsis	Category: BBE dynamic profile related issues
1714778	PPPoE and DHCP 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) and DHCP (Dynamic Host Configuration Protocol) subscriber connection attempts over this VLAN will fail.
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: BBE packet trigger access model issues
1726136	PTSP subscribers are stuck in 'configured' state Product-Group=junos	On MX platforms supporting packet-triggered subscribers and policy control (PTSP) feature, a high percentage of packet triggered subscribers are getting stuck in 'Configured' state due to an authentication failure.
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)
PR Number	Synopsis	Category: Bi Directional Forwarding Detection (BFD)
1725971	Multiple flaps of the interface will cause the BFD session to be down Product-Group=junos	On all Junos and Junos Evolved platforms, the IPv4 static route BFD (Bidirectional Forwarding Detection) session may stay down if the corresponding interface flaps multiple times.
PR Number	Synopsis	Category: Border Gateway Protocol
1691299	The BGP neighbor receives the parent authentication regardless of the authentication setup under the neighbor Product-Group=junos	On all Junos and Junos OS Evolved platforms, when a BGP neighbor authentication algorithm is configured differently from its parent group. the authentication set up in the parent group is applied to the neighbor instead of using the neighbor's specific algorithm. This causes an authentication error with the neighbor and prevents the connection from being established.
1705938	The BGP sessions will flap after the RE switchover Product-Group=junos	On all Junos and Junos OS Evolved platforms with dual RE (Routing Engine) or VC (Virtual Chassis) with NSR enabled scenarios, in some rare BGP scaled scenarios upon RE switchover the new Master RE will send out a route refresh message to all the peers, which is not expected. This will eventually lead to the BGP session flap.
PR Number	Synopsis	Category: Issues related to Common BIOS on x86 based designs
1687790	CPU will not reset automatically and will not work as expected when CAT Error is observed Product-Group=junosvae	Unexpected behavior will be seen on the QFX5120-48Y/QFX5120-48T platforms when any CAT (Catastrophic) error (PCIE/ memory driver issue, defective memory, any PCIE (Peripheral Component Interconnect Express) events like malfunctioning PCIE devices etc) is seen. The switch can also go in the hung state as the CPU is unable to execute the instructions.
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 a secondary partition.
PR Number	Synopsis	Category: BBE Remote Access Server
1709574	The subscriber sessions will be logged out when assigned IP addresses from Radius or AAA via framed-IP Product-Group=junos	On the MX platforms, when the subscriber sessions are not assigned addresses from locally configured pools and the knob "address-protection" is not enabled under the access profile configuration, then those subscriber sessions will be logged out after GRES with termination code: "aaa shutdown-administrative-reset".
1715490	IPv4 and IPv6 address allocation will be impacted due to changes in address pool configuration Product-Group=junos	On Junos platforms supporting address assignment pools, 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: MX304 line card platform software
1734132	The MX304 stops forwarding traffic on channelized 1*N G ports after the GRES is performed Product-Group=junos	On MX304 platforms with dual Routing-Engine(RE), if the ports are channelized into 1*N Gigabitethernet(G) mode, where N can be 1/10/25 G and the Graceful Routing Engine switchover (GRES) is performed, the ports go into the down state and traffic through these ports will be impacted.
PR Number	Synopsis	Category: MX304 Routing Engine issues
1726252	Enabling disk smart-check utility on the routing-engine with Innodisk SSD raises a false positive smart error. Product-Group=junos	On Junos MX304 device , Enabling disk smart-check utility on the routing-engine with Innodisk SSD raises a false positive smart error, which is visible in 'show chassis alarms'
PR Number	Synopsis	Category: Virtual-chassis platform/chassisd infrastructure PRs for MX
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
1722939	Cos Scheduling hierarchy on PS interface is destroyed when the TCP is modified Product-Group=junos	When a TCP attached on a service IFL is modified, cosd is supposed to destroy the hierarchy and send gencfg messages with new TCP information. LT IFD :: level1 PS transport IFL :: level2 - -> TCP attached here is modified. PS service IFL :: level3 After destroying the hierarchy of level2 and level3 mentioned above, instead of sending the add message which will rebuild the hierarchy, it sends a change message, thus the new hierarchy is not built up while old hierarchy is destroyed. As the PS interface hierachy is destroyed because of the events mentioned above, eventhough TCP is present for the service/transport IFL, LT IFD queues would be used for sending the PS traffic.
1725769	The cosd could crash due to upgrade to 21.2R3-S4 with AE specific wildcard and explicit configuration Product-Group=junos	On all Junos platforms, the cosd crash could be observed due to upgrade to 21.2R3-S4 with AE specific wildcard and explicit configuration.
PR Number	Synopsis	Category: Enhanced Broadband Edge support for cos
1713968	Subscribers connectivity is lost due to multiple MIC restart on all Junos MX platforms with MPC5E and BBE configuration Product-Group=junos	On all Junos MX platforms with MPC5E and BBE (Broadband Edge) configuration, subscribers connectivity will be lost due to multiple MIC (Modular Interface Card) restart.
PR Number	Synopsis	Category: L2NG Access Security feature
1724933	On certain Junos EX and QFX platforms the static ARP entries for DHCP-security are not present Product-Group=junos	On certain Junos EX series switches, the static MAC (Media Access Control) bindings are not present in certain conditions. This issue will be seen when the static DHCP (Dynamic Host Configuration Protocol)-security ARP(Address Resolution Protocol) bindings are moved from an interface having a higher interface number to an interface with a lower interface number. Due to the binding not happening, there will be impact on the traffic. The workaround when such a binding change is done is to restart the DHCP services after the configuration is committed.
PR Number	Synopsis	Category: QFX Control Plane VXLAN
1723968	Traffic loss is seen as Type 2 routes are not pushed even after withdrawing Type 5 routes Product-Group=junos	On all Junos and Junos Evolved platforms with the EVPN (Ethernet VPN) Type 2 and Type 5 Coexistence and when the host route changes from EVPN Type 5 route to non EVPN route in the rpd, traffic loss is observed as Type 2 routes are not getting pushed even after withdrawing Type 5 routes.
PR Number	Synopsis	Category: Device Configuration Daemon
1650676	The dcd core may be seen on the backup RE after GRES is disabled if targeted distributed configuration is used Product-Group=junos	The device control daemon (dcd) on the backup RE might crash immediately after GRES and NSR are disabled if AE logical interfaces are configured with targeted distribution.
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.
1726073	PFE table is not updated when new VLANs are added in an EA bundle with MPC10 when ESI is enabled Product-Group=junos	IFF Change message is not propagated to PFE when AE bundle has ESI configuration.
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: VPWS, L2 CKT, EVPN-VPWS
1723624	Traffic is getting discarded in PFE when forwarding-table is changed Product-Group=junos	On Junos ACX series platforms, traffic will be discarded and PFE (Packet Forwarding Engine) has error logs when EVPN-VPWS (Ethernet VPN Virtual Private Wire Service) over unilist towards NNI (network-to-network) side is configured and PFE is restarted. It is a timing issue and is dependent on the order of events received from the control plane.
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: 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.
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 .
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.
PR Number	Synopsis	Category: EVO L2 Control Plane PRs
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 control plane issues
1673157	The rpd crash would be observed when activating or deactivating the EVPN routing-instances Product-Group=junos	On all Junos Evolved platforms with Ethernet VPN (EVPN) enabled, when EVPN or other routing-instances are activated or deactivated, the rpd crash will be triggered. It will impact the traffic and it is a very rare case.
1713508	A high CPU consumption of mcsnoopd process is seen under IGMP-snooping configured scenario leading to its crash Product-Group=junos	On all Junos and Junos OS Evolved platforms with IGMP-snooping (Internet Group Management Protocol) enabled under instance type EVPN (Ethernet Virtual Private Network) with vlan-id=none or unspecified vlan-id there will be a spike in the mcsnoopd process CPU utilization. This will lead to the mcsnoopd process crash and there will be disruptions in the traffic.
1718534	L2ALD core at l2ald_vxlan_ifl_create_msg_build Product-Group=junos	During network churn(or during provision- when RVTEP are being discovered/created, network events), it is possible to l2ald cores @ l2ald_vxlan_ifl_create_msg_build.
1723832	The rpd core is seen in the long-running devices with EVPN enabled Product-Group=junos	On Junos and Junos Evolved platforms, BGP (Border Gateway Protocol) community object reference count is not handled properly during the process of remote BGP peer routes update event. The community reference count is increasing during the increment function. However, decrement functions are not called in one of the places after processing the routes update. This will lead to a disturbance of the continuity reference count, which will cause an rpd crash.
PR Number	Synopsis	Category: EX4100 PFE
1699216	Traffic impact is observed when OSPF adjacency gets stuck in exstart or exchange state Product-Group=junos	On Junos EX4100 platform the OSPF (Open Shortest Path First) adjacency establishment will take longer time with more than 90 VRRPv6 (Virtual Router Redundancy Protocol for IPv6) sessions causing traffic disruption.
PR Number	Synopsis	Category: EX4400 PFE software
1718286	DHCP services are impacted as DHCP binding will not work as expected Product-Group=junos	On all Junos and Junos Evolved platforms, all the DHCP (Dynamic Host Configuration Protocol) security services will be impacted as the DHCP-security binding will not work if the DHCP server-facing interface is a VTEP (VXLAN tunnel endpoint) interface.
1718316	The fxpc daemon crash 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, the Packet Forwarding Engine manager (fxpc) daemon crash is observed when reload of switch or switchover happens. Due to this crash, the Packet Forwarding Engine(PFE) will be restarted and traffic through it will be impacted.
1731522	The traffic drop will be observed after changing the VSTP VLAN configuration Product-Group=junos	On Junos EX4400, EX4100, EX2300, EX3400, and QFX5K platforms, traffic drop would happen on RSTP (Rapid Spanning Tree Protocol) enabled port attached to a VLAN (Virtual Local Area Network) when the same VLAN has VSTP (VLAN Spanning Tree Protocol) enabled on a different port and there is a configuration change done on VSTP for that VLAN.
1731548	The fxpc process crashes when the next hop information is not properly maintained in the PFE table Product-Group=junos	On Junos EX series deployed as a virtual chassis, post switchover/GRES (Graceful Routing Engine Switchover), next hop information for Type 5 route fluctuates which leads to invalid entries in the PFE (Packet Forward Engine) table and causes the fxpc (Packet Forwarding Engine Manager) process to crash.
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.
PR Number	Synopsis	Category: EX4400 platform
1680952	40G VC ports might not come up after changing VC mode from HGoE to HiGig on EX4400 VC Product-Group=junos	On Junos EX4400 VC (Virtual Chassis) platforms the 40G VCP (Virtual Chassis Port) ports do not come up after changing the VC PHY (Physical Layer) mode from HGoE (Higig over Ethernet) to HiGig. This is a rare issue that will be difficult to encounter, there will impact on traffic because the ports do not come up. To recover from the issue, the mode needs to be changed back to HGoE and a reboot needs to be performed.
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".
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.
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.
1718825	[EX4400]Alarm PEM is not supported/powered might be seen Product-Group=junos	On EX4400 platform, system alarm 'PEM is not supported/powered' might be seen after removing a power cable from PEM.
1719509	There is a missing default config of RSTP which is missing when zeroize is done Product-Group=junos	On Junos EX4400 device running will not have a Rapid Spanning Tree (RSTP) enabled for uplink ports in the factory default config. This could impact the Zero Touch Provisioning (ZTP) of the device over uplink ports due to a risk of encountering Mac-learning race conditions or loops. If multiple such devices (that are zeroized) are in a VLAN, that could cause unpredictable results for traffic being forwarded.
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
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.
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.
1726908	EX SNMP: FRU insertion trap is not generated Product-Group=junos	On EX platforms, insertion SNMP trap is not generated properly while inserting fan tray.
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.
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.
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.
1738535	25G DAC in 4x25G plugged in PIC2 does not come up when used as VC ports Product-Group=junos	On EX4400: 25G (Gigabits) DAC (Direct Attach Copper) in 4x25G in PIC2 (Physical Interface Cards) when used as VC (Virtual Chassis) ports, link is not coming up and complete traffic block is observed. On EX4100: 25G DAC with 4x25G in PIC 1, link is coming up with 10G but only with partial traffic.
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.
1727112	Programming of native-vlan-id on the interface fails and MAC is not learned Product-Group=junos	On all EX4400 and EX4100 devices in virtual-chassis (VC) deployed, in EVPN-VXLAN (Ethernet Virtual Private Network - Virtual Extensible LAN) scenario, with native-vlan-id configured on the interface, MAC (Media Access Control) address is not learned.
PR Number	Synopsis	Category: EX POE
1713545	The LLDP negotiation response is not sent back to PD when perpetual Power over Ethernet (PoE) is enabled on EX4400 Product-Group=junos	On the EX4400 platform, perpetual Power over Ethernet (PoE) is enabled, and when a device is connected to more than 10 Link Layer Discovery Protocol (LLDP) Power Devices (PD) and PD restarted while perpetual PoE is enabled, the LLDP negotiation response is not sent back to PD.
1716261	EX4100MP (PSE) does not allocate a power value requested in LLDP by the 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 Junos PTX3000, PTX5000, PTX10008, and PTX10016 routers, when the Flexible PIC Concentrator (FPC) 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. This impacts traffic.
PR Number	Synopsis	Category: Express PFE FW Features
1727067	FPC crashes when the firewall filter is configured with above 65k prefixes in a single filter Product-Group=junos	On the below PTX platforms ( PTX1000, PTX3000 (NextGen), PTX5000, PTX10008, PTX10016), when prefixes above 65K are configured in a single firewall filter, FPC (Flexible PIC Concentrator) crash would be observed.
PR Number	Synopsis	Category: Express PFE including evpn, vxlan
1718528	Traffic egressing over the EVPN-VXLAN tunnel will drop which has AE interface as underlay Product-Group=junos	On all QFX10K platforms with EVPN-VXLAN (Ethernet Virtual Private Network - Virtual Extensible LAN) configured with AE (aggregate-ethernet) as underlay, complete packet drop is observed in certain scenarios like chassis/FPC reboot or BGP (Border Gateway Protocol) flap which causes the tunnel to be rebuilt along with AE churn.
PR Number	Synopsis	Category: Express PFE L2 fwding Features
1723545	ECMP traffic is not being forwarded on all QFX10002 platforms after software upgrade Product-Group=junos	ECMP traffic is not being forwarded to L3 interface on all QFX10002 platforms after upgrading to 20.3R1 and later releases when ECMP (Equal-cost multipath) is configured with L3 interface and VTEP (Virtual Tunnel End Point) interface.
PR Number	Synopsis	Category: Express PFE L3 Multicast
1715429	Known multicast traffic is not forwarded when MLD snooping is enabled Product-Group=junos	On Junos QFX10002-60C platforms, complete traffic loss is seen when MLD (Multicast Listener Discovery) snooping is enabled.
PR Number	Synopsis	Category: Express ASIC interface
1712920	When a 4x10GE channelized interface is set to disable from config, the channel 0 also goes down Product-Group=junos	With a software changed introduced via PR1630006, when a 40G Ethernet interface is configure to be channelized interface as 4x10G interface, if an interface is disabled, or detecting an error, the interface channel 0 will also go down.
PR Number	Synopsis	Category: Express ASIC platform
1683562	On PTX5000 platforms when a command is issued to power off an FPC, it gets stuck in the 'Announce Offline' state Product-Group=junos	When an FPC (Flexible PIC Concentrator) on PTX5000 platforms is shut down by issuing a request command (request chassis offline slot ) or by FPC power off configuration (set chassis fpc x power off), it gets stuck in the 'Announce Offline' state since the associated timer (fru_graceful_offline_timer) doesn't increment and expire as it is supposed to.
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: ISIS routing protocol
1718734	Unexpected behavior of bandwidth based metric for IS-IS protocol Product-Group=junos	On all Junos and Junos OS Evolved platforms unexpected behavior of bandwidth based metric in IS-IS is seen since actual bandwidth is falling back to 0 bps when one of the member interface of AE (Aggregated Ethernet) bundle (interface-group) goes down.
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.
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
1715315	The traffic will be dropped in the DS-Lite+ALG scenario Product-Group=junos	On all Junos MX platforms with MS-MPC/MS-MIC cards in DS-Lite (Dual-stack Lite)+ ALG scenario, the connection between the client and server is not stable and is lost. The failure occurred due TCP keepalive mechanism that is always broken due to wrong data in the generated tcp-tickle packet.
1715918	The first FTPS session will not work on SRX5K platforms leading to a traffic drop Product-Group=junos	FTPS connection to the server will not be successful until the first attempt is aborted and a new connection to the server is made.
1722877	Device crashed while processing H323 traffic in SRX and MX Product-Group=junos	The SRX Device and MX with MS-MPC and MX-SPC3 service cards, crashes due to a timing issue, while processing H323 traffic.
1728638	SIP ALG not working and traffic is dropped Product-Group=junos	On all MX and SRX platforms, SIP ALG not working as SIP packets with MIME header causes traffic to be dropped
PR Number	Synopsis	Category: Flow Module
1692885	Packet loss is observed for IPSec sessions when PMI is enabled Product-Group=junos	On SRX4k series, and vSRX platforms with PMI (Power-mode) enabled, when using IPSec tunnels, IPSec packets sent out by SRX which contain a small IP packet (less than 64 bytes) may be dropped by a non-Juniper IPSec VPN peer. Power-mode is enabled by default in Junos 21.3R1 and higher.
1720570	The IPv6 Neighbor Discovery fails on VLAN tagged reth interfaces Product-Group=junos	On SRX5k and SRX4600 platforms, the IPv6 Neighbor Discovery(ND) fails if the IPv6 address is configured on two or more Virtual local area network(VLAN) tagged redundant Ethernet(reth) interfaces. This will impact the IPv6 connectivity on affected interfaces.
1733819	The inet6 packet mode drops traffic significantly Product-Group=junos	On the SRX branch series, inet6 packet mode (packet-based) throughput drops significantly. Traffic will be fine until the CPU reaches 100% and random traffic will be dropped.
PR Number	Synopsis	Category: Firewall Network Address Translation
1712738	Some sessions will not be deleted when the NAT rule is deleted from the system Product-Group=junos	On all SRX platforms with NAT (Network Address Translation) configured, upon deleting a NAT rule the session associated with deleted rule continues to exist in the system, until the connection close initiated by the session. This is a rare timing issue.
PR Number	Synopsis	Category: Firewall Policy
1713576	The flowd process crash is observed with the security policy updated with changing IP address related to the FQDN Product-Group=junos	On all SRX platforms, the policy gets updated frequently due to changes in FQDN (Fully Qualified Domain Name) resolution. At the same time, any VOIP (Voice over IP) ALGs like SIP (Session Initiation Protocol) were created with old policy data, thus Parallel security policy updation and sip data packet handling led to the core.
1725567	Traffic impact is observed when the security policy is configured with a huge number of addresses and on addition/deletion of these policies Product-Group=junos	On SRX platforms configured with security policies, having a huge number (approx. 15K) of addresses and performing addition/deletion of such policies in short intervals of time might result in srxpfe process crash and hence, data path traffic gets impacted.
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.
1722122	ISSU is aborted and flowd process crash is observed Product-Group=junos	On SRX1500, SRX4100, SRX4200 and SRX4600 an ISSU (In-Service Software Upgrade) to Junos releases 21.4R3-S3 or 22.2R3 may abort after upgrading one node and flowd coredumps may occur on that node.
PR Number	Synopsis	Category: Security platform jweb support
1735314	[Jweb] "Exclude selected" is unexpectedly enabled in security policy configuration Product-Group=junos	On SRX platform, when you cancel editing source/destination address in security policy using Jweb, "Exclude selected" is unexpectedly enabled
PR Number	Synopsis	Category: Junos Selective Update infrastructure
1732878	The Junos Selective Upgrade (JSU) version is not removed post a major Junos upgrade/downgrade Product-Group=junos	There is no functional impact but the previously installed JSU will show up even though it is deleted during major upgrade. This PR will fix that issue. Workaround is to remove /packages/sets/active/junos-version file.
PR Number	Synopsis	Category: Key Management Daemon
1719216	A stale nat-long-route entry is present in the device causing incoming packets to be dropped Product-Group=junos	On all MX platforms with MS-MPC cards, When there is an active NAT (Network Address Translation) enabled IPSec (IP security) tunnel already present for a particular service-set, any change in the outside logical interface (IFL) becomes a stale entry in the forwarding table causing IKE (Internet Key Exchange) control and data traffic to drop.
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.
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
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: Port-based link layer security services and protocols that a
1711561	MACsec dynamic CAK not working due to interoperability issue Product-Group=junos	On all Junos EX (except EX2300 and 3400) and QFX5120 platforms which support MACSEC (Media Access Control Security), due to interoperability issue between Juniper and non-Juniper devices when dynamic-CAK (connectivity association key name) is configured, traffic for ports with dynamic-CAK configured will be impacted.
1726264	JSU installation fails when MACsec is configured Product-Group=junos	On Junos and Junos Evolved platforms with PPC based image (Example MX104), JSU (Junos Selective Update) package might not pass configuration validation when the MACsec (Media Access Control Security) configuration is present.
PR Number	Synopsis	Category: Multiprotocol Label Switching
1698889	The rpd process will crash when rpd is restarted Product-Group=junos	On all Junos and Junos OS Evolved platforms, when MPLS (Multiprotocol Label Switching) statistics is configured without LSP (Label-Switched Path) configuration, the rpd process will crash and impact the routing protocols. This leads to traffic disruption due to the loss of routing information.
PR Number	Synopsis	Category: Multicast for L3VPNs
1710323	MVPN tunnel is not synced to backup router Product-Group=junos	On all Junos and Junos Evolved platforms, when OSPF inter-area is configured with segmented provider-tunnel and master undergoes MBB(make-before-break), the multicast route entry on backup router will not have the tunnel name synced with master.
PR Number	Synopsis	Category: MX Timing software
1724254	On certain Junos MX platforms with SCB3 SyncE fails after enabling PTP Product-Group=junos	On Junos MX platforms having SCB3 (Switch Control Board), the SyncE (Synchronous Ethernet) can be stuck in "Clock_Aborted" state. This issue is seen in release 20.4R3 onwards when PTP (Precision Time Protocol) is operated in hybrid mode, the SyncE failure will hinder the operation of applications like G.8275.1 deployment will fail. There is a fix in 20.4R3-S4 with JSU (Juniper Selective Upgrade) J10.2. Below are the important notes to consider regarding the verification of the fix. - -> JSU upgrade can be performed to replace the clksyncd with fix to address this issue. - -> However, if the system is already in a problem state before the JSU upgrade, a one-time deactivate and activate of "protocols PTP" and "chassis synchronization" configuration is needed to recover from the current problem state after the JSU upgrade of clksyncd is performed.
PR Number	Synopsis	Category: Track Mt Rainier RE platform software issues
1655935	Images older than 22.2R1S2 can be installed on RE-S-X6-128G-K. This will result in system booting to Linux prompt Product-Group=junos	Currently User can install images older that the minimum supported image on RE-S-X6-128G-K. System comes up in Linux prompt in such cases.
PR Number	Synopsis	Category: Kernel Composite Next Hop (composite / l3vpn) Infrastructure
1677512	The next-hops entries are not cleared in some error-handling scenarios Product-Group=junos	On all Junos platforms, the reference counts are not cleared which in turn is blocking the deletion of the route tables when routing protocols (OSPF/BGP, etc) are enabled on em0.
PR Number	Synopsis	Category: FreeBSD Kernel Infrastructure
1690892	After the VC are upgraded with NSSU and rebooted again, the VCPs constantly flap. Product-Group=junos	Upgraded using NSSU, and then after power cycling the VC, the VC gets unstable and the CPU usage of new master might get too high.
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.
PR Number	Synopsis	Category: Kernel MPLS / Tag / P2MP Infrastructure
1723145	Routing engine initiated PING failed over MPLS interface Product-Group=junos	The packets that have MTU size greater than the inet MTU size get dropped.
PR Number	Synopsis	Category: IPv6/ND/ICMPv6 issues
1703940	RE will crash when static route duplicates with an interface IP address Product-Group=junos	On all Junos platforms, RE (Routing-Engine) will crash when a static route is added that duplicates with an interface IP address. RE crash will lead complete traffic loss.
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: Protocol Independant Multicast
1675212	High CPU utilization is seen when chassisd is down during dynamic IFL creation Product-Group=junos	On all Junos platforms, in a very rare cases, while creating the specific dynamic IFls (PE-PIM (Protocol Independent Multicast) Encapsulation or PD-PIM Decapsulation), if the chassisd is down, the stuck entries in the Kernel Routing table (KRT) queue results in a high CPU utilization. The high CPU might hamper the rpd process functionality in rare cases and also device responsiveness will be slow.
1720708	Slow convergence of PIM joins causes temporary traffic loss with scaled downstream interfaces Product-Group=junos	On all Junos and Junos Evolved platforms with PIM (Protocol Independent Multicast), MVPN (Multicast Virtual Private Network) configured and when the number of downstream interfaces is more than three thousand, slow convergence of PIM joins is seen to take up more of the time and CPU, causing traffic loss for some time.
PR Number	Synopsis	Category: Periodic Packet Management Daemon
1660299	JDI-RCT : PPMD crashed at ppm_destroy_distrib_proto_stats_group_entry ( ) Product-Group=junos	When l2cpd (in the context of xSTP) clears the entries that it has programmed on ppmd, ie when you delete xSTP configs from the box, there can be a possibility of ppmd core. If ppmd is in distributed mode then there will be no service impact, else there can be service impact as packet transmission for various protocols will happen via if ppmd is in centralized mode.
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.
PR Number	Synopsis	Category: QFX PFE Class of Services
1641572	Traffic failure with error message 'Buffers are stuck on queue' after removing and attaching 100G QSFP Product-Group=junos	On QFX5110, traffic failure may be observed after removing and attaching 100G QSFP.
PR Number	Synopsis	Category: QFX5K hostpath
1721318	Error message "%PFE-3: fpc0 Failed to get ifl for ifl index = XXX" is generated when receives DHCP packet via remote vtep. Product-Group=junos	You may see the following error message in VXLAN environment. This can happen when the device receives DHCP packet via a remote vtep and L3 interface (IRB) is not assiged on the egress interface. Even though there is no DHCP configuration, the packet injection happens and it fails to get IFL index as there is no IRB interface on the egress interface. Oct 7 16:31:51.137 2022 d16-25 : %PFE-3: fpc0 Failed to get ifl for ifl index = 640
1723465	PFE crash is seen on Junos when file-logging is disabled Product-Group=junos	On Junos QFX5K platforms, when file-logging is enabled for ukern_trace handle and the logs are written continuously to the corresponding buffer due to a network issue, disabling file-logging for that handle will cause a PFE crash and will lead to a complete traffic loss.
PR Number	Synopsis	Category: QFX L2 PFE
1696428	Adding more than 256 VLANs as name tags on the same interface results in dcd crash Product-Group=junos	On all Junos platforms, the dcd (device control daemon) process crash is observed when more than 256 VLANs as name tags are added on the same interface.
1715477	Untagged packets get dropped while adding a layer 3 logical unit to an interface with native vlan configured Product-Group=junos	On all Junos platforms, adding a logical layer3 unit to an interface with native vlan configured causes the untagged packets to get dropped.
1725916	On QFX5K platforms, the status of 'ECMP Resilient Hashing' will not be displayed in output of CLI command 'show forwarding-options enhanced-hash-key' Product-Group=junos	On Junos QFX5K platforms, the output of CLI command 'show forwarding-options enhanced-hash-key' does not indicate weather the 'ECMP Resilient Hashing' is enabled or disabled. This is just a display issue with no functional impact.
PR Number	Synopsis	Category: QFX L3 data-plane/forwarding
1686539	The dcpfe process crashes on QFX5k and certain EX platforms Product-Group=junos	On QFX5k, EX4100, EX4300, EX4400, and EX4650 platforms, the dcpfe process crash will be seen when EVPN-VXLAN (Ethernet VPN-Virtual Extensible LAN) is configured.
1713133	The dcpfe crashes after restarting l2-learning process on QFX and EX series Junos platforms Product-Group=junos	The dcpfe process crash is observed on EX and QFX Junos platforms after restarting the l2-learning process when flex-hash is configured. It will be recovered automatically after the dcpfe restart
1714701	Traffic blackhole after reboot Product-Group=junos	On all Junos platforms, traffic drops observed when RH (Resilient-Hashing) is configured on a LAG (Link Aggregation Group) interface.
1724675	Traffic loss will be observed with vlan tagging and/or vlan normalisation in a specific design (using a looped cable) Product-Group=junos	Upon upgrade to Junos versions (junos:20.3R2, 20.3R3, 20.3X75-D20, 20.4R2, 21.1R1, 21.2R1), network connectivity is lost for traffic requiring vlan normalization and having DMAC one of the switch's MAC addresses. For example, incoming traffic has two vlans (S-vlan, C-vlan) ingressing on an interface and switch uses a looped link to provide routing via an IRB. --- (S-vlan\|C-vlan) -- -> SW_X --- C-vlan -- -> SW_X_irb ARP and L2 learning occurs as expected but upon receiving the frame with DMAC of a local interface, switch takes a route lookup action instead of bridging and vlan normalization due to the frame having DMAC as the MAC of one of its interfaces. Hence, the traffic is not sent via looped cable to the L3 interface.
1732708	SNMP polling Timeout due to OID 1.3.6.1.2.1.31.1.1.1.10.514 ( ifInOctets.514 ) Product-Group=junos	When trying to poll information via SNMP, the device stops reponding causing a SNMP timeout, the issue is due to sxe-0/0/0 private interface that is marked as public interfaces which causes it to query kernel for statistics.
PR Number	Synopsis	Category: QFX EVPN / VxLAN
1697244	Assigning VNI to VLAN will cause a small number of packets lost on other VLANs on the same interface Product-Group=junos	On Junos QFX5110 and QFX5120 devices, a small number of packets are lost when assigned VNI (VXLAN Network Identifier) to the VLAN (Virtual Local Area Network). There is a packet loss on incoming packets, but no packet loss on outgoing packets.
1712175	The dcpfe process crash is seen on QFX5k platforms due to stale vtep entry Product-Group=junos	On all QFX5000 platforms, with VXLAN (Virtual Extensible LAN) configured and due to a stale next hop entry of vtep (vxlan tunnel end point) interface, dcpfe (Dense Concentrator Packet Forwarding Engine) process crash was observed.
1730771	Traffic is impacted due to high CPU and dcpfe/fxpc crash (in some cases) in EVPN-VXLAN scenario Product-Group=junos	On Junos QFX5k and EX platforms, a high CPU and dcpfe/fxpc crash (in some cases) is seen in the EVPN-VXLAN (Ethernet VPN-Virtual Extensible LAN) scenario.
1731583	Traffic drops when VXLAN VLAN is deleted Product-Group=junos	On all Junos platforms whenever any of the VXLAN (Virtual Extensible LAN) VLAN (Virtual Local Area Network) is removed the VXLAN traffic is seen to get dropped.
1733022	QFX5120 reboots without dcpfe core due to deletion of EP style interface with native vlan configured Product-Group=junos	QFX5120 will reboot without causing a dcpfe crash upon the deletion of EP style(trunk) interface with multiple IFLs and native vlan configured.
PR Number	Synopsis	Category: QFX10008/16 QFX10002 Ultimat/Elit platform related issues -
1695183	PTX1000 resources exhaustion causing host loopback wedge Product-Group=junosvae	Junos PTX1000 platforms will experience resource exhaustion 64 days after the reboot. Due to this the device will drop all the control plane traffic resulting in complete service impact. see https://kb.juniper.net/TSB71154 [juniper.net]
PR Number	Synopsis	Category: QFX5100 Interface related issues
1665800	Ports with SFP-T 1G plugged in may go to hung state on QFX5100 platforms Product-Group=junos	When the remote end server/system reboots, QFX5100 platform ports with SFP-T 1G inserted may go into a hung state and remain in that state even after the reboot is complete. This may affect traffic after the remote end system comes online and resumes traffic transmission.
PR Number	Synopsis	Category: QFX5100 Platfom related issues. CPLD, FPGA, FRU, Host, RE
1611354	The ports might remain in downstate on QFX5K platforms Product-Group=junosvae	In a rare scenario, if the upgrade is being performed or ports are continuously flapped on QFX5K platforms, then interfaces might remain in downstate and need to reset in order to restore it.
PR Number	Synopsis	Category: QFX5200/5110/5120/5210 Platfom issues
1710952	No alarm is raised when PSU is inserted with different airflow directions Product-Group=junosvae	On QFX5100/QFX5110/QFX5120/QFX5200 platforms, no alarm would be raised even though inserted PSU module which has a different airflow.
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.
1725116	The 100G interface will remain down post rebooting the device Product-Group=junosvae	On the Junos QFX5200 platform, sometimes upon restarting the device the 100G link will not come up and will remain down, impacting the traffic flowing through it.
PR Number	Synopsis	Category: RPD Interfaces related issues
1722809	Router Send RA with Router lifetime 0 when the upstream interface is shut Product-Group=junos	Issue: 1. This is a Day-1 issue with virtual RA. For virtual interfaces used in EVPN-VXLAN with multihoming scenario and VRRP, we will have two IPv6 link local addresses, one is the interface's link local address and another one is the virtual-gateway-address(VGA). There are two redundant gateways in this case which will have common VGA and in event of a failure of any given gateway, ND/RA re-resolution is not required. 2. Whenever interface is enabled or disabled, we get two link local IFA notifications for the same IFL. Only one link local IFA will be stored in the IPv6 interface at a time. 3. When second notification is received for the interface's link local address, it is treated as a link local address change and hence RA with 0 lifetime is sent for this IFA, but the source address is derived from virtual interface which is the VGA. 4. After receiving RA packet with lifetime zero, host VM deletes the default route to the VGA address and hence traffic loss is observed. 5. In this case, RA with 0 lifetime must not be sent as the VGA link local address is common and it is not changed by RPD clients (L2ALD for EVPN-VXLAN and VRRPD for VRRP). Fix: 1. As link local address will keep changing for virtual interface from virtual gateway address to configured link local address with every IFA notification, we don't need to send RA with lifetime 0 for virtual interface as the link local address for virtual interface can be changed only by RPD clients. Hence removed this part from the code for virtual interface only. 2. We need to send RA with lifetime 0 when RPD client sends an RA add request with different link local VGA. Hence added support to send RA with lifetime 0 if received VGA from RPD client is different from stored link local address in the virtual interface.
PR Number	Synopsis	Category: RPD Next-hop issues including indirect, CNH, and MCNH
1652387	The rpd process might crash with back-to-back rpd restarts Product-Group=junos	On all Junos and Junos Evolved platforms, the rpd process might crash if the rpd process restarts back-to-back before the rpd process comes up.
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.
PR Number	Synopsis	Category: RPM and TWAMP
1722232	In TWAMP server/reflector, test traffic classified by ingress filter is re-classified by host-outbound-traffic statement Product-Group=junos	Irrespective of ingress forwarding class configured and marked, all the TWAMP reflected packets are sent over the Q3(Network control).
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: 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 harmless an error msg during the commit.
PR Number	Synopsis	Category: SRX branch platforms
1646943	No system or chassis alarm will be seen when device booting from backup partition Product-Group=junos	On Junos SRX branch platforms, when the device boots up from the backup partition, the alert message will not be notified in "show system alarm". This issue has been seen from Junos 19.4R2 release.
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: Stout cards (MPC7, MPC8, MPC9) microkernel issues
1727427	FPC crash observed when the ASIC usage is high Product-Group=junos	On platforms with MS-MPC/MPC1/2/3/4/5/6/7/8/9 line cards and EX9200/EX9204/EX9208/EX9214/EX9251/EX9253 series devices, route churn (add or deletes) when the ASIC usage crosses a threshold (ASIC usage is high) which leads to a FPC crash.
PR Number	Synopsis	Category: MX10002 Platform SW - Platform s/w defects
1721714	BFD session failed when configured on the loopback sub interface Product-Group=junos	On the MX10003 and MX304 platforms, BFD (Bidirectional Forward Detection) session failed to come up when configured on the loopback sub interface.
PR Number	Synopsis	Category: ZT/YT pfe qos software issues
1715149	DSCP field in IPv4 header is incorrectly re-written Product-Group=junos	On Junos platforms that support MPC10/MPC11/LC9600 line cards, whenever there is a rewrite rule configured to rewrite the DSCP bits on transit router in core network, packet loss are observed in the destination due to incorrectly re-written DSCP field in IPv4 header.
1729747	Egress CoS rewrites won't work and that may lead to QoS specific issues downstream Product-Group=junos	On Junos platforms, when the Preserve Next Hop routing knob is enabled, MPLS (Multiprotocol Label Switching) EXP rewrites on the transit router do not work. CoS (Class of Service) behaviour seen for the packets downstream of this node may not be on expected lines . There could be drops where it is not expected.
PR Number	Synopsis	Category: ZT/YT pfe firewall software
1726733	Traffic drops with percent policer attached using list Product-Group=junos	On Junos EX92xx, MX304 and MX series platforms with MPC10, MPC11 and LC9600, traffic drop will happen with the attachment of family filter configured with percent policer (bandwidth-percent) via input-list/output-list.
PR Number	Synopsis	Category: ZT/YTpfe bridging, learning, stp, oam, irb software
1664694	Not all MAC addresses are learnt for some VPLS instances Product-Group=junos	On MX platforms with specific line cards(MPC10, MPC11 & LC9600), when the CLI "clear vpls mac-table" is executed, all the MAC addresses are not learned for some VPLS instances. This will lead to traffic loss due to MAC table not having all the MAC addresses.
1700321	VLAN tags are imposed incorrectly when traffic is routed over IRB going out of the access interface Product-Group=junos	On MX platforms, traffic egressing on the IRB (Integrated Routing and Bridging) interface with the underlying L2 (layer2) access port has VLAN tags imposed incorrectly.
1713523	When VPLS is enabled on the LT interface, unknown unicast traffic is forwarded rather than discarded Product-Group=junos	On MX platforms with MPC10/MPC11/LC9600 line cards, when the Logical Tunnel (LT) interface is configured with family Virtual Private LAN Service (VPLS) and VLAN, unknown unicast traffic on this line card forwards the traffic instead of discarding it. Hence the services configured on the LT interface which will use unicast traffic are affected.
PR Number	Synopsis	Category: ZT/YT pfe l3 forwarding issues
1658017	AFT sensor UDP output not decodable using Junos Proto file. Product-Group=junos	UDP Telemetry output fields may misalign on AFT-based line cards such as MPC10/11 or Junos Evolved platform.
PR Number	Synopsis	Category: Trio LU, IX, QX, MQ chip drivers, ucode & related SW
1720591	In a rare case FPC crashes and reboots generating a core Product-Group=junos	On all Junos platforms, in a rare scenario, GRES (Graceful Routing Engine switchover) may result in LACP (Link Aggregation Control Protocol) on the new master being down which may cause an FPC crash.
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: Trio pfe qos software
1706494	Severity reclassification of queuing ASIC XQSS and memory parity error auto recovery Product-Group=junos	On Junos with MX platform using specific MPC7E/MPC8E/MPC9E/JNP10K-LC2101/JNP10003-LC2103/JNP10K-LC480 line cards in the event of a transient memory hardware issue, parity errors are generated which cannot be rectified by the ASIC. When the Flexible PIC Concentrators(FPC) encounters such an error, it will automatically deactivate the Packet Forwarding Engine(PFE) which leads to traffic impact.
1714429	The DEI bit will not be copied in the inner VLAN tag although the incoming traffic has the DEI bit set Product-Group=junos	On all Junos platforms, there might be a service impact if the DEI (Drop eligible indicator) bit is used to decide if the packet needs to be dropped or not as the DEI bit will not be copied in the inner VLAN tag although the incoming traffic has the DEI bit set. The issue will happen when the dot1p (IEEE 802.1p) rewrite is bound to the egress interface with inner and outer tag options in the P2P (Point-to-Point) L2VPN (Layer 2 Virtual Private Network) environment.
PR Number	Synopsis	Category: Trio pfe bridging, learning, stp, oam, irb software
1636758	JDI-RCT:M/Mx: FPC core @ jnh_call_read_index , trinity_nh_ucast_uninstall_hw Product-Group=junos	With given multi dimensional scale, if configuration is removed and restored continuously for more than 24 times, MX Trio based FPC may crash and restart. During the reboot, there can be traffic impact if backup paths are not configured.
1720772	VLAN rewrite will not work for traffic egressing on IRB over L2 AE IFL Product-Group=junos	On Junos MX and EX92XX with specific line cards, VLAN rewrites will not happen for traffic egressing from IRB(Integrated Routing and Bridging) interface over an L2 AE (Aggregated Ethernet) IFL (Interface Logical), if the L2 AE IFL is configured to perform VLAN rewrites on the frames. This happens when the IRB is configured as a routing-interface on EVPN (Ethernet Virtual Private LAN) or VXLAN (Virtual Extensible LAN) routing instances and the traffic has to egress on IRB over an L2 AE IFL. As a result, the frames are forwarded with incorrect VLAN tag information.
1727049	Multiple CFM sessions are down when vlan rewrite feature is configured on AE interfaces Product-Group=junos	On MX platforms, in Aggregate Ethernet (AE) hybrid case (having child links in MPC1 to MPC9 line cards) a new Virtual Local Area Network (VLAN) rewrite feature is added before punting the CCMs (cross-connect continuity check messages) packets. This feature is derived from the AE member interfaces where the PFE instance of the member is wrongly updated causing the CFM sessions down.
PR Number	Synopsis	Category: Trio pfe l3 forwarding issues
1646799	SR-stats : Per-Interface egress and per-sid Egress sensor stats do not take MPLS label length into account in the output octet calculations Product-Group=junos	When per-interface egress and per-sid egress SR sensor stats are configured using the CLI commands below, the (pushed) MPLS label length does not get included in the output/Tx octets field that gets exported from the sensor. set protocols isis source-packet-routing sensor-based-stats per-interface-per-member-link egress set protocols isis source-packet-routing sensor-based-stats per-sid egress This is a day-1 behavior on all Trio ASIC based FPCs on the MX platform.
1714656	Incorrect Destination MAC and Source MAC addresses while processing transit packets over LT IFL Product-Group=junos	On MX platforms with MPC10, MPC11, LC9600, and MX304-LMIC16, while processing transit packets over LT IFL (logical interface) incorrect Destination MAC and Source MAC addresses are observed when the Ethernet encapsulation type is configured on the LT interface.
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
1717425	Junos platform device unable to commit configuration in recovery mode Product-Group=junos	On all Junos platforms where snapshot is supported, when a device is rebooted from recovery mode it fails to commit configuration due to problems with slax import and device might go into amnesiac mode due commit fail.
PR Number	Synopsis	Category: Configuration mgmt, ffp, load-action, commit processing
1663590	Commit failure might be observed on reactivation of jflow related configurations Product-Group=junos	On all Junos and Junos Evolved platforms, reactivation of jflow (v9/ipfix) related configurations cannot be committed on backup RE.
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.
1730336	The rpd crashes and the commit operation fails while pushing a large configuration with the "extend-size" knob enabled Product-Group=junos	On all Junos platforms, when the 'extend-size' knob is configured and a scaled configuration is committed, the rpd daemon crash is seen and the commit operation fails. root@device> show configuration \| match configuration-database \| display set set system configuration-database extend-size root@device# load update /var/tmp/New_config.txt load complete root@device# commit error: Check-out pass for Routing protocols process (/usr/sbin/rpd) dumped core (0x86) error: configuration check-out failed
PR Number	Synopsis	Category: Issues related to NETCONF
1585855	< ok/> response is getting generated along with < rpc-error> Product-Group=junos	When maximum-password-length is configured and the user tries to configure password whose length exceeds configured maximum-password-length, there is an error and the '' tag is emitted. (Ideally '' tag should not be emitted in an error scenario.) The configuration does not get committed.
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: web filterig issues
1715260	utmd core has seen at commit when . or ..* is configured at url-pattern Product-Group=junos	When url-pattern contains '.' or '..*', utmd core is generated and commit fails .
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.
1726775	Upgrading the i40e NVM Firmware on Routing Engines with VM Host Support Product-Group=junos	Steps for Upgrading the i40e NVM Firmware on Routing Engines with VM Host Support is described in https://www.juniper.net/documentation/us/en/software/junos/junos-install-upgrade/topics/task/vmhost-nvm-upgrade.html i40e NVM version 6.01 is the prerequisite to install a LTS19 based image, else image installation will fail. This prerequisite is not needed now.
PR Number	Synopsis	Category: Virtual Private LAN Services
1729052	The rpd process crash will be observed during VPLS to EVPN migration Product-Group=junos	On all Junos platforms during VPLS (Virtual Private LAN Service) to EVPN (Ethernet Virtual Private Network) migration, when the EVPN and VPLS are configured under the same routing instance and "instance-type evpn" is enabled, then upon deactivate/delete "protocols vpls" and changing the IFL configuration associated with VPLS will lead to rpd process crash.
PR Number	Synopsis	Category: Virtual Router Redundancy Protocol
1720943	Issue in VRRP inline adjacency whenever a master router uplink goes down on MX platforms Product-Group=junos	On all Junos MX platforms, when "set protocols vrrp delegate-processing" knob is enabled in Virtual Router Redundancy Protocol (VRRP) protocol and VRRP track is also enabled for uplink interfaces in that scenario if the master router uplink fails and the master priority remains higher than the backup router even after the master router uplink failure, this results in an issue with VRRP inline adjacency.
PR Number	Synopsis	Category: Track Windriver Linux issues
1631579	WRL9 based line card will be stuck in the present state and later go offline after it is rebooted Product-Group=junos	A system equipped with Wind River Linux 9 (WRL9) based line cards will be stuck in the present state and later go offline after the line card or router is rebooted.
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.
1729801	Traffic drop might be observed on MX Platform configured with PCP mapping with NAT Product-Group=junos	On all MX platforms with SPC3 cards and PCP (Port Control Protocol) with NAT (Network Address Translation) configured, the PCP client should renew the mapping before its expiry time to keep the PCP mapping always active. the issue is seen if the traffic from outside the network (public network) toward B4 (softwire initiator) was suspended for sometime. When traffic started again toward B4 from outside the network, it will be dropped and service will be impacted.
PR Number	Synopsis	Category: usf service set related issues
1728510	SNMP walk timeout for NMS Product-Group=junos	On Junos MX platform with SPC3 card, NMS (Network Management System) times out when polling any data from jnxSpSvcSetIfTable OID.

22.2R3-S1 - List of Known Issues

See TSB71464 [juniper.net] for a list of KNOWN Issues

Modification History

First Publication 2023-05-15