22.2R2-S1: Software Release Notification for JUNOS Software

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.2R2-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.2R2-S1 is now available.

22.2R2-S1 - List of Fixed issues

PR Number	Synopsis	Category: Daily JUNOS build failures - automated builder use only
1691209	Use latest os-package when upgrading Product-Group=junos	Upgrade to 22.3R1 while using os-package published between July 2022 and November 2022 may incorrectly link os-libs package
PR Number	Synopsis	Category: EX2300/3400 platform
1680408	On Ex2300 and EX3400, "set system ports console log-out-on-disconnect" does not allow user to log in via console. Product-Group=junos	On certain units, with "set system ports console log-out-on-disconnect", when you login to the device via a console, the user will be kicked out to the login prompt and be asked to login again.
PR Number	Synopsis	Category: Border Gateway Protocol
1692255	The rpd crash is seen when using a BGP neighbor telemetry subscription in a sharding environment Product-Group=junos	On all Junos and Junos OS Evolved platforms, the rpd crash will be seen when the BGP (Border Gateway Protocol) neighbor telemetry subscription is used in the sharding environment leading to a layer-3 traffic drop.
PR Number	Synopsis	Category: MX304 Chassis specific platform
1675268	MX304:: Observed spmbpfe core on RE1 when installed image on both the REs Product-Group=junos	Sometimes cores are reported on backup RE during init after a reboot etc. When the backup RE initialization is being done and system is busy, some commands executed in context of spmbpfe are taking more time to complete due to the initial heavy lifting by the kernel, In this stage, if in case the commands from spmbpfe process do not complete for >2.5 seconds, then there are chances of spmbpfe cores. This is a temporary issue seen on backup RE during init time only. This may not be impacting because if in case spmbpfe process crashes due to this, it would restart by itself and continue to init and run once the initial high cpu condition has passed. It should not cause any functionality or performance impact; especially since it is reported only on backup RE.
PR Number	Synopsis	Category: MX304 Routing Engine issues
1647534	MX304 RCB: system does not got to shell prompt and hangs before rebooting after pressing N during PXE installation Product-Group=junos	pressing N during the PXE install and the reboot prompt is supposed to abort the installation, not reboot, and provide a debug shell. On MX304, the shell is not spawned and the system hangs for a while and then reboots.
PR Number	Synopsis	Category: QFX Access Control related
1693640	The dot1x reauthentication will not work for a port with VoIP VLAN Product-Group=junos	On Junos EX platforms, the dot1x clients will remain in connecting state after the 'clear dot1x interface' is done due to which the interface would not get authenticated to become a member of the configured access VLAN. When this happens, VLAN membership will not be formed.
PR Number	Synopsis	Category: dns-proxy feature
1688481	The chassis cluster will not respond to DNS queries when configured with DNS proxy service Product-Group=junos	On Junos SRX platforms with an operational DNS (Domain Name System) server, the chassis cluster will not respond to DNS queries when configured with DNS proxy service.
PR Number	Synopsis	Category: EVPN control plane issues
1680421	EVPN MPLS traffic drop can be observed in a multi-vendor PE CE setup with single-active LAG Product-Group=junos	On all Junos platforms running EVPN (Ethernet Virtual Private Network) MPLS (Multi-Protocol Labeled Switching) and a single active LAG (Link Aggregation), the traffic can get forwarded to the NDF (Non-Designed Forwarder) router which can lead to a traffic drop. This issue is seen in multi-vendor PE (Provider Edge) CE (Customer Edge) setup when there is a DF switchover i.e DF (Designated Forwarder) role changes and the backup router starts advertising the EVPN type 2 route, now there is another switchover and the old DF again becomes the DF and advertises EVPN type 1 route but the NDF does not withdraw its route consequently the traffic gets forwarded to the NDF.
PR Number	Synopsis	Category: EVPN Layer-2 Forwarding
1649234	The kernel crash would be observed in an EVPN multi-homed scenario Product-Group=junos	On QFX10002/QFX10008/QFX10016 (only QFX10K) platforms, when Assisted Replication (AR) feature as Replicator role is used in an Ethernet VPN (EVPN) multi-homed scenario, there would be out-of-bound memory access issue observed which could result in the kernel crash leading to the service impact.
PR Number	Synopsis	Category: EX4100 RE, Platform Infra, Drivers
1672731	The vmcore might be seen with the back-to-back reboot Product-Group=junos	On the EX4100 platform with VC setup, upon continuous back-to-back switch reboot, vmcore might be noticed when the switch boots back. The vmcore might lead to a kernel crash.
PR Number	Synopsis	Category: EX4400 PFE software
1694800	On a PVLAN with DAI ARP packets will be forwarded between isolated ports Product-Group=junos	On Junos based EX platforms, when Dynamic ARP (Address Resolution Protocol) Inspection (DAI) is configured on PVLAN (Private Virtual Local Area Network), ARP packets coming from the LAG (Link Aggregation Group) are forwarded to other isolated access ports.
PR Number	Synopsis	Category: EX4400 platform
1690674	On EX4100 and EX4400 platform, alarm 'PEM is not supported' might be seen. Product-Group=junos	On EX4100 and EX4400 platform, system alarm 'PEM is not supported' might be seen with a specific trigger and it keeps remain even after supplied power.
PR Number	Synopsis	Category: Express PFE including evpn, vxlan
1691029	Packet Loss seen on the EVPN-VXLAN spine router router Product-Group=junos	On all platforms supporting MAC_VRF in a scaled config when continous delete and rollback were performed the OSPF and BFD will go down leading to packet drop.
PR Number	Synopsis	Category: Express PFE L2 fwding Features
1693424	Traffic loss is observed when the ECMP path is IRB over AE (IPv4->MPLS) Product-Group=junos	On QFX10002 platforms, when the ECMP (Equal-cost multi-path) path is IRB (Integrated routing and bridging) over AE (Aggregated Ethernet) {IPv4->MPLS (Multiprotocol Label Switching)} results in packets getting discarded for which traffic loss is observed.
PR Number	Synopsis	Category: jdhcpd daemon
1666943	MX240:Verify VRRP stats is failed after Deactivate the Access interface Product-Group=junos	VRRP statistic may not be accurate with subscriber services
PR Number	Synopsis	Category: Category for JET(JUNOS Extension Toolkit) related issues
1653968	The connection might get closed by the collector when connecting to jsd Product-Group=junos	The collector connects to jsd and before acceptance can be called by gRPC, the connection might get closed by the collector.
PR Number	Synopsis	Category: Flow Module
1683334	Packet loss on GRE Tunnel due to improper route look-up for tunnel destination Product-Group=junos	On SRX platforms, due to improper route look-up for the tunnel destination if the GRE tunnel is configured in a virtual routing-instance for which packet loss is observed.
PR Number	Synopsis	Category: High Availability/NSRP/VRRP
1691071	Chassis cluster IP monitoring on the secondary node failed after the system reboot on the SRX platforms Product-Group=junos	On SRX platforms, IP monitoring on the secondary node failed when a Reth (redundant Ethernet) interface consists of two or more than two interfaces on each node. Reth member interface which has a higher port number cannot receive ICMP (Internet Control Message Protocol) packet used for IP monitoring, which will then put the system in an error state.
PR Number	Synopsis	Category: Port-based link layer security services and protocols that a
1693730	Traffic loss will be seen when MACSEC is configured Product-Group=junos	On all Junos platforms where MACSEC(Media Access Control Security) is configured with 60s SAK (secure association key) rollover, traffic loss will be observed during RE (Routing Engine) switchover.
PR Number	Synopsis	Category: MX Timing software
1671262	PTP server state stuck in acquiring state when configured on a port enabled with Ingress Queueing Feature Product-Group=junos	On MX and EX platforms, with Trio-based line cards, configuring ingress queuing on the interface where Precision Time Protocol (PTP) packets are received, Ingress Queueing duration was not accounted for in the PTP fields and results in a delay in processing.
PR Number	Synopsis	Category: FreeBSD Kernel Infrastructure
1681783	On Ex4400 upgrade failure happens when upgrading through a USB drive. Product-Group=junos	On EX4400 upgrade failure happens when upgrading through a USB drive.
PR Number	Synopsis	Category: TCP/UDP transport layer
1685113	Random BGP session flap with error "BGP_IO_ERROR_CLOSE_SESSION" Product-Group=junos	On all Junos and Junos Evolved platforms, a random BGP (Border Gateway Protocol) session flaps will be observed immediately after committing unrelated configuration changes with the error "BGP_IO_ERROR_CLOSE_SESSION" along with a connection reset. This issue is generic to any TCP (Transmission Control Protocol) connection that has MD5 (Message-Digest Algorithm) enabled on it.
PR Number	Synopsis	Category: OSPF routing protocol
1674802	BGP or OSPF neighbors will not come up in Junos OS Evolved platforms if IPSEC Security Associations are used to Authenticate the peer Product-Group=junos	The issue is seen when there is interoperability between Junos OS Evolved and other vendors or Junos, BGP (Border Gateway Protocol)/OSPF (Open Shortest Path First) neighbors will not come up if IPSEC (IP Security) Security Associations are used to authenticate the peer.
PR Number	Synopsis	Category: QFX L3 data-plane/forwarding
1695943	JUNOS_REG::QFX5110-32Q:VC:::After loading "20.4R3-S5.3" dcpfe core is observed and device is unstable Product-Group=junos	On QFX5K VCF platform, the PFE core will be seen due to invalid usage of snprintf (PR 1688206).
PR Number	Synopsis	Category: QFX EVPN / VxLAN
1687565	VxLAN configured on access port breaks L2 connectivity with "vxlan encapsulate-inner-vlan" knob Product-Group=junos	On all Junos QFX5k platforms, L2 connectivity fails when "vxlan encapsulate-inner-vlan" knob is configured on an access port. It impacts a forwarding plane and causes a traffic impact.
PR Number	Synopsis	Category: QFX5100 Interface related issues
1688023	The LLDP output packets are not transmitting on the em0 interface of Junos and Junos OS Evolved platforms Product-Group=junos	On Junos and Junos OS Evolved platforms, if a management Ethernet interface(em0) has an inet or inet6 family configured and "delete interfaces em0" is issued, the Link Layer Discovery Protocol (LLDP) output packets will stop transmitting, causing the LLDP neighborship to remain down in peer router.
PR Number	Synopsis	Category: Category for QFX5K EVO Platform Software PRs related to Chas
1696113	The BFD session might be stuck in "Init" state on certain QFX 5k platforms Product-Group=junos	On certain Junos QFX5k (QFX-5120-48Y/QFX-5120-32C/QFX-5120-48T) with multi-hop BFD (Bi-Directional Forwarding and Detection) enabled and multipath BGP (Border Gateway Protocol) is enabled, the BFD session can be stuck in "Init" state. This issue can be seen when there is a change in the routing path because of the interface flap for the BFD session. To recover from the issue, the BFD needs to be reconfigured.
PR Number	Synopsis	Category: Bug and Review Tracking for Segment routing traffic eng
1687287	The rpd process crash is seen when the BGP SR-TE tunnel is marked for deletion Product-Group=junos	On all Junos and Junos Evolved platforms, the crash is seen due to a sync failure between the Master and Backup RE when a BGP SR-TE tunnel is marked for deletion.
PR Number	Synopsis	Category: MX10003/MX204 Linux issues (including driver issues)
1660446	MX204 - SSH non-default port configuration causes FPC offline after upgrade to 21.4 Product-Group=junos	For MX204, MX10003, ACX5448 platform, if a non-default ssh port is configured for system login, after upgrade to 21.4 release, the FPC is stuck in offline. To avoid such issue please use default SSH port and use protect RE filter to only allow the access from the trusted source.
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.
PR Number	Synopsis	Category: ZT/YT pfe qos software issues
1688416	The COS queue burst size computation was incorrect when the explicit queue shaping rate was not configured, causing initial packet drops Product-Group=junos	On specific linecards MPC10/11/LC9600 and MX304 device, there was an issue with the COS (Class of Service) queue burst size calculation when the explicit queue shaping-rate was not configured, resulting in an initial packet drop and the COS queue burst size computation was incorrect which causes packets to drop initially.
PR Number	Synopsis	Category: ZT/YT pfe firewall software
1649499	The MPC/FPC might crash or the traffic may be silently dropped/discarded Product-Group=junos	The firewall filter might be incorrectly updated in the Packet Forwarding Engine (PFE) when large-scale filters, applied on any of the supported bind points, undergo repeated load and unload. It can result in a core and FPC will be restarted. It's a timing issue.
PR Number	Synopsis	Category: Trio LU, IX, QX, MQ chip drivers, ucode & related SW
1681533	The line card gets crashed during node/interface statistics reporting with resource monitoring Product-Group=junos	On MX platforms with specific line cards, the MPC may crash and generate core dumps in a corner case during node/interface statistics reporting scenario when resource monitoring is used.
PR Number	Synopsis	Category: Trio pfe bridging, learning, stp, oam, irb software
1696106	Packets received from type-5 tunnel are not sent out to local CE in EVPN-VxLAN scenario Product-Group=junos	IIn EVPN-VxLAN scenario, traffic drop can be seen for some local CEs which are multihomed to at least one MX Router as the packets
PR Number	Synopsis	Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1648744	JDI-RCT:M/Mx: While removing VRRP configs and adding them back, mgd process stuck at 100% and router hangs forever. Product-Group=junos	While removing VRRP configs and adding them back, the mgd process stuck at 100% and the router hangs forever.
PR Number	Synopsis	Category: Issues related to all UI tools (mgd-bsd/cli-bsd, XML and DMI
1681656	System uptime display is shown in minutes instead of seconds Product-Group=junos	On all Junos and Junos Evolved platforms, after the device reboot, show system uptime command is showing time in minutes instead of seconds for 24 hours.
PR Number	Synopsis	Category: VSRX platform software
1681042	ARP will not get learned if reth interface is configured with VLAN Product-Group=junos	On vSRX 3.0 platforms in High availability (HA) cluster environment, ARP (Address Resolution Protocol) will not get learned if VLAN is configured on the reth (redundant Ethernet) interface.
PR Number	Synopsis	Category: usf nat related issues
1692525	ALG child session will not be transported through the DS-Lite tunnel which might lead to traffic failures in absence of a direct route to the host Product-Group=junos	On Junos MX240/MX480/MX960 platform with MX-SPC3, a tunnel ID of the control session is not updated properly on the gate created for Session Initiation Protocol (SIP) Application Layer Gateway (ALG), which is leading to the gate hit session not mapping back to the Dual-Stack Lite (DS-Lite) tunnel. This might result in traffic failure if the client does not have a direct route to the host.

22.2R2-S1 - List of Known issues

PR Number	Synopsis	Category: CoS support on ACX
1689604	EVPN Packets may go to incorrect queues due to the wrong classification and may lead to packets drop during congestion Product-Group=junos	On Junos ACX5448 and ACX710 devices, in EVPN (Ethernet Virtual private network) with a multihoming scenario, if one link fails traffic will switch over to another link. When FPC is restarted and the dot1p classifier is changed, restore the failed link. Packets may not go to the correct queue due to the wrong classification when traffic switches back to the original link, and traffic drops may happen during congestion. Resolved In: junos:21.2R3-S4 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:22.4R2 junos:23.1R1
PR Number	Synopsis	Category: Track PRs in BGP BMP area & is part of BGP inside RPD.
1695320	BMP EOR is sent with wrong peer address causing BMP failure Product-Group=junos	On all Junos and Junos Evolved platforms, on removing and re-applying BMP (BGP Monitoring Protocol) configuration, the EOR (End-of-RIB) message sent by the router has the wrong peer address updated causing BMP collector failure. There is no traffic impact due to this issue. Resolved In: evo:22.1R3-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R2-EVO evo:23.1R1-EVO junos:21.2R3-S4 junos:21.3R3-S3 junos:21.4R3-S2 junos:22.1R3 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:22.4R2 junos:23.1R1
PR Number	Synopsis	Category: Issues related to Common BIOS on x86 based designs
1685206	MX304: After USB recovery of Primary bios flash there is an additional reboot of the system Product-Group=junos	If the USB recovery method to reflash the primary bios flash is used, the recovery is successfull. However after the successful recovery, there is an additional reboot to golden bios flash parition after which it boots from the recently recovered primary flash bios. There is no functional impact other than the delay due to the additional reboot. Resolved In:
PR Number	Synopsis	Category: MX304 interface specific
1697272	MX304 :: 25g link is not coming up after port speed change from 25G to 10G back to 25G Product-Group=junos	Normal 25G on bootup or first time config work. In a special seq When we move the speed from 25G to 10G on same link and back to 25G , the link doesnt come up in 25G. Due to transitioning between 10g to back 25G , there is some seq which leaves YT in bad state and it keeps reporting fault. Resolved In:
PR Number	Synopsis	Category: MX304 Routing Engine issues
1664592	RE - FPC physical link down event does not generate an alarm Product-Group=junos	If the physical link status of the ethernet link between the RE and FPC goes down, there are recovery attempts to bring up the link again. Log messages indicate the recovery attempts and the success/failure status of the attempt. However an alarm is not raised when this failure occurs Resolved In:
PR Number	Synopsis	Category: Device Configuration Daemon
1682271	Node Slicing: In a rare scenario, the FPC/SLC will get stuck in the ready state after a restart Product-Group=junos	On Junos MX platforms, in a rare scenario, FPC/SLC (Flexible PIC Concentrator/Sub Line Card) may get stuck in the ready state after restarting it and the error message of 'Device busy' will be observed in Syslog. Resolved In: junos:21.2R3-S2-J19 junos:21.2R3-S4 junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R1
PR Number	Synopsis	Category: EVPN control plane issues
1669585	Layer3 inter-subnet routing will fail if there is no reachability for the remote IP-host route Product-Group=junos	On all Junos and Junos Evolved platforms that support T-2(Type-2)IRB(Integrated Routing and Bridging) symmetric routing, EVPN VXLAN(Virtual Extensible LAN) symmetric type-2 route needs to be imported in L2 mac-vrf instance for IP host route to be added in Layer3(L3) vrf. Layer3 inter-subnet routing will fail if there is no reachability for the remote IP-host route. Resolved In: evo:22.2R3-EVO evo:22.4R1-EVO evo:23.1R1-EVO junos:22.4R1 junos:23.1R1
PR Number	Synopsis	Category: Interface Information Display
1636668	Pyrite_VC: em0 interface ppeed is reflecting as 10G instead of 1G Product-Group=junos	Management interface speed is displayed as 10G instead of 1G though there is no functionality impact. Resolved In: evo:22.1R3-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R1-EVO evo:22.4R2-EVO evo:23.1R1-EVO junos:21.4R3-S3 junos:22.1R3 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:22.4R2 junos:23.1R1
PR Number	Synopsis	Category: Platform infra to support jvision
1686766	MPC10E line card will reboot due to the sensord crash Product-Group=junos	On MX platforms with MPC10E line card, for sensor installed by health-mon causing sensord crash resulting in the MPC10E line card reboot. Resolved In: evo:21.3R3-S3-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R1-EVO junos:22.2R3 junos:22.3R2 junos:22.3R3 junos:22.4R1 junos:22.4R2 junos:23.1R1
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:22.2R3 junos:22.3R2 junos:22.4R1 junos:22.4R2
PR Number	Synopsis	Category: OSPF routing protocol
1674802	BGP or OSPF neighbors will not come up in Junos OS Evolved platforms if IPSEC Security Associations are used to Authenticate the peer Product-Group=junos	The issue is seen when there is interoperability between Junos OS Evolved and other vendors or Junos, BGP (Border Gateway Protocol)/OSPF (Open Shortest Path First) neighbors will not come up if IPSEC (IP Security) Security Associations are used to authenticate the peer. Resolved In: evo:22.2R2-S1-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R1-EVO evo:23.1R1-EVO junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:23.1R1
PR Number	Synopsis	Category: Resource Reservation Protocol
1681403	In the RSVP-TE scenario, with Entropy label capability is enabled during MBB issues handling Resv Messages Product-Group=junos	On all platforms with entropy-label configured, the issue shows up during Make-Before-Break (MBB) at a transit Juniper node when non-Juniper Egress constructs and sends a Resv message with multiple flow-descriptors (includes descriptors for both old and new instances). Juniper transit device has an issue handling such Resv Messages, the RRO object that is part of the flow-descriptor was getting dropped when the LSP_ATTRIBUTES object was also present within the flow-descriptor. Resolved In: evo:22.1R3-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R1-EVO evo:23.1R1-EVO junos:20.4R3-S5 junos:21.2R3-S4 junos:21.3R3-S3 junos:22.1R3 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:23.1R1
PR Number	Synopsis	Category: IPSEC functionality on M/MX/T ser
1641107	22.1R1:CGNATAMS:mspmand core is found while doing Tunnel distribution after Restart RPD daemon Product-Group=junos	mspmand daemon running on MS-MPC/MS-MIC cards can occasionally crash when the service card (fpc/pic) is turned offline and then online at regular intervals when the number of service-set configured is moderately high and when extensive hardware crypto operations are being performed. Exact issue is yet to be isolated. Resolved In:
PR Number	Synopsis	Category: Cover Logical System Infrastrcuture Development
1694449	The process srxpfd/ flowd will crash on SRX devices Product-Group=junos	On all SRX platforms (except branch SRX series) configured with chassis cluster redundancy group, when numerous logical interfaces or IFLs (> 1K) are deleted and traffic is running for those IFLs, or if the RG failover then the process srxpfed/ flowd will crash. Resolved In: junos:19.4R3-S11 junos:20.2R3-S7 junos:20.4R3-S6 junos:21.1R3-S5 junos:21.2R3-S4 junos:21.3R3-S3 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:22.4R2 junos:23.1R1
PR Number	Synopsis	Category: MPC7/8/9 Interface Issues
1682962	Auto-negotiation is not getting reflected on the MPC7E-10GE line card Product-Group=junos	On all MX platforms with MPC7E-10GE line card, auto-negotiation will not be set properly when changing the port speed from 10GE to 1G on a port with auto-negotiation configured. The port remains down until the commit is done separately for changing the port speed. Resolved In: evo:22.3R2-EVO evo:22.4R2-EVO evo:23.1R1-EVO junos:20.4R3-S6 junos:21.1R3-S4 junos:21.2R3-S3-J7 junos:21.2R3-S4 junos:21.3R3-S3 junos:21.4R3-S2 junos:22.1R3 junos:22.3R2 junos:22.4R2 junos:23.1R1
PR Number	Synopsis	Category: MX10003/MX204 Linux issues (including driver issues)
1660446	MX204 - SSH non-default port configuration causes FPC offline after upgrade to 21.4 Product-Group=junosvae	For MX204, MX10003, ACX5448 platform, if a non-default ssh port is configured for system login, after upgrade to 21.4 release, the FPC is stuck in offline. To avoid such issue please use default SSH port and use protect RE filter to only allow the access from the trusted source. Resolved In: junos:22.2R2-S1 junos:22.2R3 junos:22.3R2 junos:22.4R2 junos:23.1R1
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. Resolved In:
PR Number	Synopsis	Category: Configuration management, ffp, load action
1671112	Test Configuration might fail even though the config file is having valid configurations Product-Group=junos	Root cause; In test configuration flow we are calling mustd as "/usr/sbin/mustd -q /var/run/db/file.data /var/run/db/file.data+ -F -m" where we just copy the existing cog.db (generated out of committed config) as cdg.db+ , use it for testing the configuration passed, and remove it once the testing is done. This is creating the issue because the configuration is tested against the existing cdg.db. Fix would be to create the cdg.db fresh from the configuration to be tested and test the configuration against that. This new cdg.db should not replace the existing one in /var/run/db. Resolved In: evo:22.4R1-EVO evo:23.2R1-EVO junos:22.4R1 junos:23.1R1
PR Number	Synopsis	Category: MX10K linecard
1688651	JUNOS_REG:MX10008:Carrier transition count is more than expected at DUT(mx10008) after flapping the interface at peer non-DUT end. Product-Group=junos	When laser off and on happens on the remote end, within an interval of less than 500 ms, the local interface undergoes additional flap, before the link comes up. There is no impact of the additional flap, as the link does come up eventually. Resolved In:

Modification History

First publication 2023-01-05