Alert Type
SRN - Software Release Notification
Risk
Risk Description
Low/Notification
Software Release Notification
Impact
Impact Description
Low/Notification
Software Release Notification
Product Affected
ACX PTX QFX platforms running Junos Evolved software
Alert Description
Junos Software Service Release version 22.2R3-S2-EVO 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-S2-EVO is now available.
22.2R3-S2-EVO - List of Fixed issues
PR Number
Synopsis
Category: EVO platform software
1725823
Random link flap is observed on the ports connected to re-timer
Product-Group=evo
On Junos OS Evolved QFX5220-32CD/QFX5220-128C/PTX10001-36MR/JNP10K-LC1202/PTX10K-LC1202 platforms and Junos MPC11 linecards, if SNR (Signal to Noise) is high on the re-timer ports then a random link flap on the ports connected to re-timer will be observed.
PR Number
Synopsis
Category: MX Layer 2 Forwarding Module
1743032
FPC cards restart unexpectedly
Product-Group=evo
On Junos based MX platforms with MPC7E, FPC(Flexible PIC Concentrator) crashes and core would be observed causing traffic loss. This is a rare issue.
PR Number
Synopsis
Category: BBE network stack related issues
1729913
DHCP subscribers are stuck in DHCP-Renew state when 'overrides always-write-giaddr' is enabled
Product-Group=evo
On all Junos platforms supporting DHCP (Dynamic Host Configuration Protocol), when 'overrides always-write-giaddr' option is enabled on the DHCP relay, checksum is not computed properly causing the DHCP renew to fail and subscribers getting stuck in 'Requesting' state.
PR Number
Synopsis
Category: Border Gateway Protocol
1728604
Traffic impact is seen when there is a single peer in the proxy BGP group connected to the BGP route reflector
Product-Group=evo
On all Junos and Junos OS Evolved platforms, if the proxy BGP (Border Gateway Protocol) route reflector is connected to the only peer present in the BGP group then it stops advertising the routes coming from the remote cluster and that leads to proxy route-target routes not getting added which causes traffic disruption.
1738074
BFD session for BGP remains down in a specific scenario
Product-Group=evo
On all Junos and Junos Evolved platforms supporting BFD (Bi-directional Forwarding and Detection) for BGP (Border Gateway Protocol) multi-hop BFD sessions can remain in a down state. This issue is seen when the multi-hop BFD session endpoints are in the same subnet but the interface addresses on which the BFD is configured are not directly connected.
1739335
The rpd process crash will be observed when the prefix-limit exceeds on the backup RE
Product-Group=evo
On all Junos and Junos OS Evolved platforms configured with BGP (Border Gateway Protocol), NSR (Nonstop Active Routing), and prefix-limit with idle-timeout, when the prefix-limit exceeds on the backup RE (Routing Engine) and switchover is performed the rpd process crash will be observed on the new backup RE.
1739919
Junos OS and Junos OS Evolved: A BGP session will flap upon receipt of a specific, optional transitive attribute (CVE-2023-0026)
Product-Group=evo
An Improper Input Validation vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). Please refer to https://supportportal.juniper.net/
JSA71542
[juniper.net]
for more details.
1742222
Partial application of BGP import policy with BMP configuration and after back-to-back commits changes BGP import policy
Product-Group=evo
When BMP is configured and sessions are established, if a back-to-back commit is made that alters a BGP peers import policy, then the import evaluation job is not re-run after the 2nd commit. This can lead to partial application of the desired policy, resulting in missing values that need to take effect with second policy (eg: missing communities).
1745073
CPU in rpd spikes and scheduler slips will be observed when the duplicate community is added
Product-Group=evo
On all Junos and Junos Evolved platforms, when Border Gateway Protocol (BGP) is configured with the existing community member added via another community that is called in import policy and the intermediate router does not support large/extended communities based on scale (route). Due to this, the rpd Central Processing Unit (CPU) stays high and protocols level choking will be seen in adjacent nodes. Scheduler slips are also observed due to the same.
PR Number
Synopsis
Category: EVO L3 routing for BCM XGS Platforms
1738709
The traffic for the same flow with the same tuple will be sent through different tunnels if the TTL value in IPv4 or the payload length in IPv6 is different
Product-Group=evo
On Junos OS Evolved QFX5130/QFX5700 platforms configured with EVPN-VXLAN (Ethernet VPN-Virtual Extensible LAN), when the packets of a flow have the same tuples but have different TTL (time-to-live) values or payload length, the packets will be sent through multiple VXLAN tunnels, which would lead to a jitter.
PR Number
Synopsis
Category: EVO VXLAN PFE for BCM XGS Platforms
1722109
The VRF route leaking will not happen for the routes learned on the AE interface in the EVPN-VXLAN MAC-VRF routing-instance
Product-Group=evo
On QFX5130 and QFX5700 Junos OS Evolved platforms, configured with Ethernet Virtual Private Network Virtual Extensible LAN (EVPN-VXLAN) with routing-instance MAC-VRF and Aggregate Ethernet (AE) interface is a member of it, the routes learned on the AE interface will not leak to other routing instances even if configured to do so. Thus, the layer 3 traffic across the VRF will be impacted for the routes that are learned on the AE interface.
PR Number
Synopsis
Category: Express BT PFE L3 Features
1671799
Junos OS Evolved: PTX10001-36MR, and PTX10004, PTX10008, PTX10016 with LC1201/1202: The aftman-bt process will crash in a MoFRR scenario after multiple link flaps (CVE-2023-36833)
Product-Group=evo
A Use After Free vulnerability in the packet forwarding engine (PFE) of Juniper Networks Junos OS Evolved on PTX10001-36MR, and PTX10004, PTX10008, PTX10016 with LC1201/1202 allows an adjacent, unauthenticated attacker to cause a Denial of Service (DoS).Please refer to https://supportportal.juniper.net/
JSA71640
[juniper.net]
for more information
PR Number
Synopsis
Category: DNX platform MPLS FRR features
1739112
[Error] BrcmPlusNhMpls: Tunnel create failed for NH: *. BrcmPlusNhMplsTunDataShrPtr BrcmPlusNhMplsTunnel:: mplsHwCreate()
Product-Group=evo
Due a the SW bug, the local LIF which is responsible for HW resource allocation was not getting freed properly, causing resource exhaustion and leading to Tunnel creation failure. Below logs may appear : [Error] BrcmPlusNhMpls: Tunnel create failed for NH: *. BrcmPlusNhMplsTunDataShrPtr BrcmPlusNhMplsTunnel:: mplsHwCreate()
PR Number
Synopsis
Category: software upgrade infra issues
1731877
Auto-sw-sync doesn't trigger upgrade/restart of routing engine
Product-Group=evo
On Junos Evolved PTX10008 and PTX10016 platforms, on releases after 21.2R1-EVO, on enabling auto-sw-sync with no user groups configuration, routing engine 1 (RE1) after joining the cluster, can not sync the versions present in master RE0.
PR Number
Synopsis
Category: System Management High availability
1716059
The Zookeeper session fails on master RE and reboots RE twice
Product-Group=evo
On the Junos OS Evolved PTX10004, PTX10008, PTX10016, QFX5700, and ACX7509 platforms when the Zookeeper retries fail the master Routing Engine (RE0) will reboot and the backup RE becomes the new master RE (RE1). If the mastership switchover didn't happen within 5 sec then the Zookeeper server on the new master RE (RE1) will shut down. Thus, the Zookeeper connection will not get established and the new master RE (RE1) will reboot.
PR Number
Synopsis
Category: PRs related to software Agentd daemon on EVO
1715345
SSD failure resulting in File System errors does not perform mastership switch in timely manner and results in an operational outage
Product-Group=evo
On all Junos Evolved platforms with dual RE (Routing Engine), the current filesystem (FS) error handling will remount the filesystem into read-only mode for protection when disk failure happens. This software change performs a kernel panic upon FS error and will recover the system. If the primary SSD (Solid-State Drive) is not in 'running' state, the system will reboot from the backup SSD. A kernel panic will trigger a mastership switch on dual Routing Engine systems. A delay in the mastership switchover leads to operational outage.
PR Number
Synopsis
Category: Configd, ffp issues
1743038
Commit confirm and commit race condition crashes the firewall functionality
Product-Group=evo
On dual-RE (Routing Engine) Junos Evolved platforms, when the commit is executed during the commit confirm timeout window, it causes the firewalld to stop working.
PR Number
Synopsis
Category: EVPN Layer-2 Forwarding
1715343
Ping overlay vxlan replies Overlay-segment present even the bridge-domain has been deactivated
Product-Group=evo
The vxlan ping overlay request is recevied for a certain VNI on MX and the bridge-domain associcated with the VNI has been deactivated. However the MX still responses with "Overlay-segment present" sub-code in the reply message.
PR Number
Synopsis
Category: ISIS routing protocol
1699076
The rpd process might crash when SPF is recalculated
Product-Group=evo
On all Junos and Junos Evolved platforms, the rpd (Routing Protocol Daemon) process can crash due to periodic SPF (Shortest Path first) recalculation when ISIS (Intermediate System to Intermediate System) connected or direct routes get deleted.
1725686
Unnecessary SPF calculation is causing high CPU utilization
Product-Group=evo
On all Junos and Junos Evolved platforms, very frequent SPF (Shortest Path First) calculation, being caused by leaking multiple prefixes across the IS-IS areas, is causing high CPU utilization.
PR Number
Synopsis
Category: jdhcpd daemon
1722082
DHCP binding is not happening in EVPN VXLAN topology with DHCP stateless relay (forward-only)
Product-Group=evo
In EVPN VXLAN topology with DHCP stateless relay (forward-only) configured at layer 3 gateways, Jdhcpd broadcasts snooped unicast offer packets. That leads to the offer getting dropped on its way to the client and then the IP negotiation fails.
PR Number
Synopsis
Category: Layer 2 Control Module
1739975
Layer 2 traffic will be dropped on VSTP disabled interface
Product-Group=evo
On Junos platforms, Whenever an interface is disabled under VSTP (VLAN Spanning Tre Protocol) configuration, the issue will be seen in the following cases. 1. When interface, IFBD (Interface Family Bridge Domain) and VSTP, configured via single commit. (In case of new configuration) 2. When VSTP configurations are present and chassisd restarts/device reboots, then issue will be seen. (During ifd delete and add, issue will be seen)
PR Number
Synopsis
Category: Layer2 forwarding on EX/NTF/PTX/QFX
1727954
On all Junos and Junos Evolved platforms the l2ald process memory usage is seen to increase over time
Product-Group=evo
On all Junos and Junos Evolved platforms service impact is seen due to a consistent increase in l2ald (Layer 2 Address Learning Daemon) memory usage.
1743282
The l2ald crashes when there is recursive deletion of IFBD or when BGP neighborship is cleared in EVPN-VXLAN multi-homed configuration
Product-Group=evo
On all Junos and Junos OS Evolved platforms, in a rare scenario, due to timing issue, the l2ald (Layer 2 Address Learning Daemon) crashes and traffic is being blackholed due to recursive deletion of IFBD (Interface Family Bridge Domain) or when BGP (Border Gateway Protocol) neighborship is cleared when EVPN (Ethernet Virtual Private Network) - VXLAN (Virtual Extensible Local Area Network) with multi-homed is configured.
PR Number
Synopsis
Category: Multiprotocol Label Switching
1740226
LSP with auto bandwidth enabled is not updating its Max AvgBW value, preventing the LSP from being resized
Product-Group=evo
On all Junos and Junos OS Evolved platforms, when there is no underflow limit configured under auto-bandwidth for an RSVP (Resource Reservation Protocol) LSP (Label Switched Paths), and if the traffic across the LSP is reduced and there is an underflow, the LSPs continue to be signaled with a higher bandwidth without being adjusted even after multiple adjustment intervals. The issue is observed only when there is a secondary standby path present. The MaxAvgBw (Maximum Average Bandwidth) value continues to stay at a higher value and is not being set based on the underflow Max Avg. This will eventually lead to bandwidth starvation for other LSPs.
PR Number
Synopsis
Category: OSPF routing protocol
1741480
The rpd crashes when repeated routing-instance and interface is flapped
Product-Group=evo
The rpd is seen to crash when OSPF (Open Shortest Path First) is configured and repeated routing-instance and interface is flapped. The rpd crash leads to traffic impact.
PR Number
Synopsis
Category: Protocol Independant Multicast
1720240
RPD process crashes on all Junos and Junos OS Evolved platforms after adding static route to the VRF in some scenarios
Product-Group=evo
When static route is added to the VRF (Virtual Routing and Forwarding), and mc-ip (multicast-ip) and the PIM (Protocol Independent Multicast) instance get deleted in some scenarios, the RPD process crash is seen on all Junos and Junos OS Evolved platforms.
PR Number
Synopsis
Category: QFX EVPN / VxLAN
1727119
The EVPN-VXLAN proxy-arp will respond with the wrong MAC when no-mac-learning is configured
Product-Group=evo
On all Junos and Junos OS Evolved platforms in the EVPN-VXLAN (Ethernet VPN-Virtual Extensible LAN) scenario, when the knob "switch-options no-mac-learning" is configured, the mac-ip entry will still be learned even though the MAC learning is disabled due to which the proxy ARP (Address Resolution Protocol) will not work properly on the leaf device and it will respond with a wrong MAC address for the ARP request.
PR Number
Synopsis
Category: Issues related to dynamic-tunnels routing infrastructure
1695236
The rpd process crash is observed when dynamic tunnel deletes composite next-hop
Product-Group=evo
On all Junos OS Evolved platforms, the rpd process crash is observed when dynamic tunnel deletes composite next-hop.
PR Number
Synopsis
Category: Indirect nexthop routing infrastructure
1692776
The rpd crash will be observed when there is a temporary recursion loop and routes are flapping
Product-Group=evo
On all Junos and Junos Evolved platforms, the rpd process crashes when a temporary recursive loop forms. This happens when a BGP route flaps and while the options 'multipath-resolve' and 'preserve-nexthop-hierarchy' are configured.
PR Number
Synopsis
Category: RPD policy options
1706143
Issue in committing more than 23, 4-byte AS on Junos and Junos Evolved platforms
Product-Group=evo
On all Junos and Junos Evolved platforms, when a 4 byte autonomous system (AS) number is committed with more than 23 as-path in as-path-prepend policy it gives "rpd string" error and the configuration commit fails.
1744449
Policy change to a rib-group import-policy configured with global routing-options interface-routes causes the rpd issue on all platforms with EVPN-VXLAN configuration
Product-Group=evo
When a user configures "set routing-options interface-routes rib-group " along with an import policy for that particular rib-group, it will result in an unexpected behavior. It could disrupt the rpd or result in the rpd running at 100%. This issue is only related the "interface-routes" being configured in the global routing-options hierarchy with EVPN-VXLAN configuration. This issue won't be seen when routing-options configurations can have "interface-routes" enabled under specific routing instance.
PR Number
Synopsis
Category: Shard routing infrastructure within RPD
1716431
Memory leak will be observed in rpd after performing restart routing
Product-Group=evo
On all Junos OS and Junos OS Evolved platforms with rib-sharding enabled, memory leak will be observed in rpd when restart routing is performed. If system is up from long time and restart routing performed multiple times can exhaust system memory that causes to process crash or configuration are not effective/applied because of lack of memory then it is possible that it will impact traffic.
PR Number
Synopsis
Category: RPD route tables, resolver, routing instances, static routes
1742147
Memory leak observed when reconfiguring the flow routes
Product-Group=evo
On all Junos and Junos OS Evolved platforms, if the nexthop of a flow route is the same as it was before when reconfiguring flow routes, memory leak occurs. High memory use of routing process daemon(rpd) is seen as a result of this leak. A kernel out of memory message is observed which results BGP flap.
PR Number
Synopsis
Category: Resource Reservation Protocol
1723229
The rpd process crash is observed when RSVP LSP at Juniper transit/ingress router receives RESV message with RESVCONF object in multi vendor deployment
Product-Group=evo
On all Junos and Junos OS Evolved platforms (For QFX5100, only in Virtual Chassis-VC setup) with RSVP (Resource Reservation Protocol) LSP (Label-Switched Path) configured in multi vendor deployment and Juniper router is acting as a transit/ingress router and RESV (Reservation Request) message is received with RESVCONF object from other vendors, rpd process crash will be observed.
PR Number
Synopsis
Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1693630
In JUNOS EVO "show | display inheritance" does not work correctly for LSPs with whitespace in the name
Product-Group=evo
An LSP with whitespace in the name does not display correctly when viewing the configuration using 'show | display inheritance'
1745565
The mgd process crash is observed when 'show' is executed from the configuration mode
Product-Group=evo
On all Junos platforms, when 'show' is executed from the configuration mode, a mgd process crash is observed which has no functionality impact.
PR Number
Synopsis
Category: Express ZX PFE L3 Features
1720264
Unnecessary "resiliencyd" messages appear for trap codes
Product-Group=evo
Unnecessary "resiliencyd" messages appear for trap codes. We do have "cda trapstats" which count these.
22.2R3-S2-EVO - List of Known issues
PR Number
Synopsis
Category: Border Gateway Protocol
1709837
Junos OS and Junos OS Evolved: A crafted BGP UPDATE message allows a remote attacker to de-peer (reset) BGP sessions (CVE-2023-4481)
Product-Group=evo
An Improper Input Validation vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). Please refer to https://supportportal.juniper.net/
JSA72510
[juniper.net]
for more information.
Resolved In:
evo:22.1R3-S4-EVO evo:23.1R2-EVO evo:23.2R1-S1-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.3R2-EVO evo:23.4R1-EVO junos:23.1R2 junos:23.2R1-S1 junos:23.2R2 junos:23.3R1 junos:23.3R2 junos:23.4R1
PR Number
Synopsis
Category: EVO Layer-2 switching for BCM XGS Platforms
1741712
Traffic loss would be seen for host generated traffic from QFX5130 and QFX5700 platforms
Product-Group=evo
On QFX5130 and QFX5700 platforms on LAG(Link Aggregation Group) interfaces with flexible-vlan-tagging enabled and extended-vlan-bridge and native-vlan-id configuration, traffic towards host would be sent out untagged to both native VLAN and non-native VLAN.
Resolved In:
evo:22.4R2-S2-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-S1-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO
PR Number
Synopsis
Category: ACX VxLAN Issue
1720541
ACX7100-32C EVO: Router Does not reply to RS message with VXLAN.
Product-Group=evo
ACX7100-32C EVO: Router Does not reply to RS message with VXLAN
Resolved In:
evo:22.3R3-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO
PR Number
Synopsis
Category: Gnats category for dynamic rendering infrastructure
1681777
Invalid XML output can be seen for RPC get response
Product-Group=evo
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 .
Resolved In:
evo:21.4R3-S4-EVO evo:22.2R2-J6-EVO evo:22.2R2-S2-J2-EVO evo:22.3R2-S1-EVO evo:22.3R3-EVO evo:22.3X50-EVO evo:22.4R1-EVO evo:23.1R1-EVO junos:21.2R3-S5 junos:21.2X32-D20 junos:21.4R3-S4 junos:22.2R3-S1 junos:22.3R2-S1 junos:22.3R3 junos:22.4R1 junos:23.1R1
PR Number
Synopsis
Category: software upgrade infra issues
1699699
The commit changes will not take effect post software upgrade once the system is rebooted on Junos OS Evolved platforms
Product-Group=evo
On Junos OS Evolved Platforms, any UI (user interface) set (configuration, script, license) changes done post software addition were being lost after the subsequent reboot.
Resolved In:
evo:23.3R1-EVO junos:23.2R1 junos:23.3R1
PR Number
Synopsis
Category: Interface PRs defect & enhancement requests
1743461
Changing speed and adding to AE in the same commit fails
Product-Group=evo
On all Junos OS Evolved platforms, If the changing of the speed and the creation of the ae interfaces is in the same commit, the commit fails with "Interface aeX with child links of mixed speed but link-speed mixed is not configured".
Resolved In:
evo:21.4R3-S5-EVO evo:22.3X50-EVO evo:22.3X80-D38-EVO evo:22.3X80-D39-EVO evo:22.4R2-S1-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1 junos:23.4R1
PR Number
Synopsis
Category: EVO L2 Control Plane PRs
1705712
Traffic loss would be seen as prefix gets stuck in Hold state
Product-Group=evo
On Junos OS Evolved platforms with EVPN-VXLAN (Ethernet VPN Virtual Extensible LANs) feature, traffic loss would be observed as host prefix gets stuck in Hold state due to any network event which causes the route to delete and add in a quick succession.
Resolved In:
evo:22.4R2-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:22.2R3-S2 junos:22.3R3-S1 junos:22.4R2 junos:23.1R1 junos:23.2R1
1740561
Traffic loss is seen due to anomalies after the recreation of IFLs
Product-Group=evo
On all Junos Evolved Platforms, in the EVPN-VXLAN DCI (Data center Interconnect) scenario, traffic loss is seen due to anomalies when any catastrophic interface change is done which results in the IFL (logical interface) deletion and recreation by the system.
Resolved In:
evo:22.3R3-S1-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.2R1-S1-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:22.3R3-S1 junos:22.4R3 junos:23.1R2 junos:23.2R1-S1 junos:23.2R2 junos:23.3R1 junos:23.4R1
PR Number
Synopsis
Category: mgd, ddl, odl infra issues
1703745
The system won't come up in a working state post reboot for upgrade validation fails to detect invalid host-name
Product-Group=evo
On all Junos Evolved platforms, running with Junos Evolved OS image prior to 22.1R1-EVO and if it is having the system host-name configured with an underscore then when upgrading the system to a Junos Evolved OS image 22.1R1-EVO or higher, config validation does not detect the invalid host-name with an underscore and validation will pass, but post reboot service mgd-init-service will fail to come up, due to which upgrade will fail and as a result system won't come up in a working state.
Resolved In:
evo:22.3X50-EVO evo:22.3X80-D38-EVO evo:22.3X80-D39-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:22.4R3 junos:23.1R1 junos:23.2R1
PR Number
Synopsis
Category: Periodic Packet Management Daemon
1702687
The ppmd process crash will be seen after GRES
Product-Group=evo
On all Junos and Junos OS Evolved platforms with dual-RE, after back to back Graceful Routing Engine switchover (GRES) is performed, the periodic packet management process (ppmd) crash will be seen.
Resolved In:
evo:23.1R2-EVO evo:23.2R1-EVO junos:23.1R2 junos:23.2R1
PR Number
Synopsis
Category: Category for QFX5K EVO Platform Software PRs related to Chas
1741772
CLI start shell puts the system in 'csh'
Product-Group=evo
Please refer to
TSB69736
[juniper.net]
Resolved In:
PR Number
Synopsis
Category: Issues related to dynamic-tunnels routing infrastructure
1728305
The tunnel remains down and traffic is impacted due to no validation of the tunnel forwarding route
Product-Group=evo
Traffic drop is observed when the tunnel route resolves over a route, which the next hop was set to discard. This occurs as there is no check if the nexthop is of type discard, reject or black hole.
Resolved In:
evo:22.2R3-S1-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.2R2-EVO evo:23.3R1-EVO junos:20.3X75-D43 junos:21.4R3-S5 junos:22.2R3-S1 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1
PR Number
Synopsis
Category: RPD Interfaces related issues
1722809
Router Send RA with Router lifetime 0 when the upstream interface is shut
Product-Group=evo
For virtual interfaces used in EVPN-VXLAN (Ethernet VPN-Virtual Extensible LAN) with multihoming scenario and VRRP (Virtual Router Redundancy Protocol), after receiving RA (Router Advertisement) packet with lifetime zero, host VM deletes the default route to the VGA (Virtual Gateway address) address and hence traffic loss is observed.
Resolved In:
evo:22.2R3-S1-EVO evo:22.3R3-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:22.2R3-S1 junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR Number
Synopsis
Category: KRT Queue issues within RPD
1674310
The rpd crash may be encountered on Junos Evolved platforms
Product-Group=evo
On Junos Evolved dual RE (Routing Engine) platforms, the rpd (routing protocol daemon) may crash if the NSR (Non-Stop Routing) switchover is performed before even the backup rpd is NSR ready. If the issue is encountered, the rpd may get stuck and not install routes. The workaround to avoid this is to perform the switchover when backup RE is fully synced.
Resolved In:
evo:21.4R3-EVO evo:21.4R3-S3-EVO evo:22.1R3-EVO evo:22.2R2-EVO evo:22.3R2-EVO evo:22.4R1-EVO junos:22.1R3 junos:22.2R2 junos:22.3R2 junos:22.4R1
PR Number
Synopsis
Category: PTX10K specific platform PRs
1706601
CLI "show chassis craft-interface" shows "Fail" with the removed FPC after offlined FPC is removed from chassis
Product-Group=evo
On PTX10004/8/16 EVO, when offlined FPC is removed from chassis, "show chassis craft-interface" CLI shows "Fail" for removed FPC.
Resolved In:
evo:21.4R3-S3-EVO evo:22.3R3-EVO evo:22.3X50-EVO evo:22.3X80-D38-EVO evo:22.3X80-D39-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.1R2-EVO evo:23.2R1-EVO junos:22.3R3 junos:22.4R2 junos:23.1R2 junos:23.2R1
1716276
PTX10004/8/16 EVO "LINE CARDS" LED on Status Panel is Lit ON in Green right after FPC is inserted although FPC is Present state
Product-Group=evo
On PTX10K running Junos Evolved software platforms, the "LINE CARDS" LED on Status Panel is Lit ON in Green right after FPC is inserted although FPC is Present state.
Resolved In:
evo:21.4R3-S4-EVO evo:22.3R3-EVO evo:22.3X50-EVO evo:22.3X80-D38-EVO evo:22.3X80-D39-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR Number
Synopsis
Category: Configuration mgmt, ffp, load-action, commit processing
1663590
Commit failure might be observed on reactivation or commit of specific configurations after the upgrade of the device
Product-Group=evo
On all Junos and Junos Evolved platforms, reactivation or commit of specific configurations fails after the upgrade of the device.
Resolved In:
evo:21.2R1-J3-EVO evo:21.2R3-S1-EVO evo:22.2R3-S1-EVO evo:22.3R1-EVO junos:21.2R3-S1 junos:21.2R3-S5 junos:21.2X32-D10 junos:21.2X32-D20 junos:22.2R3-S1 junos:22.3R1
PR Number
Synopsis
Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1730336
The rpd crashes and the commit operation fails while pushing a large configuration with the "extend-size" knob enabled
Product-Group=evo
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.
Resolved In:
evo:22.2R3-S1-EVO evo:22.3R2-S2-EVO evo:22.3X50-EVO evo:22.4R3-EVO evo:23.1R1-S1-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.2R2-EVO evo:23.3R1-EVO junos:20.3X75-D52 junos:21.2R3-S6 junos:21.2X32-D20 junos:21.4R3-S4 junos:22.1R3-S4 junos:22.2R3-S1 junos:22.2R3-S2 junos:22.3R2-S1 junos:22.3R2-S2 junos:22.3R3-S1 junos:22.4R2-S1 junos:22.4R3 junos:23.1R1-S1 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1
Modification History
First publication 2023-09-07
22.2R3-S2-EVO: Software Release Notification for JUNOS Evolved Software