Alert Type

SRN - Software Release Notification
Low/NotificationSoftware Release Notification
Low/NotificationSoftware Release Notification

Product Affected

ACX PTX QFX running Junos Evolved Software

Alert Description

Junos Software Service Release version 21.4R3-S6-EVO is now available for download from the Junos software download site

Download Junos Software Service Release:

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

Solution

Junos Software service Release version 21.4R3-S6-EVO is now available.

21.4R3-S6-EVO - List of Fixed issues 

PR NumberSynopsisCategory: "agentd" software daemon
1702250The xmlproxyd process crash is observed in telemetry scenario
Product-Group=evo
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.
PR NumberSynopsisCategory: Bi Directional Forwarding Detection (BFD)
1698373A few BFD sessions might flap after FPC reload and stabilization
Product-Group=evo
On all Junos platforms and Junos Evolved with scaled BFD sessions, FPC reload/restart results in few BFD session flap.
PR NumberSynopsisCategory: Border Gateway Protocol
1712406IPv4 routes learnt over a link-local BGP session not advertised ahead to other BGP peers
Product-Group=evo
When rib (Routing Information Base) contains IPv4 routes with IPv6 next-hops, these routes do not get re-advertised by IPv4 EBGP sessions unless export policy is configured to change it to IPv4 next-hop.
1732087The rpd process will crash in a scaled BGP setup with traceoptions configured
Product-Group=evo
On all Junos and Junos Evolved platforms in a scaled Border Gateway Protocol (BGP) setup with different Hold timers and BGP trace options enabled, the rpd process will crash when multiple BGP sessions are enabled/disabled.
1754935BGP multipath route is not correctly applied after changing the IGP metric
Product-Group=evo
On all Junos and Junos Evolved platforms, multipath route is not correctly applied due to this Equal-cost multi-path (ECMP) will not be formed, when Border Gateway Protocol (BGP) multipath is configured and the Interior Gateway Protocol (IGP) metric of a network is modified and subsequently reverted.
1775548RPD core on cRPD acting as Route Reflector while running scaled test with 1000 peers with sharding and threading enabled
Product-Group=evo
RPD core on cRPD acting as Route Reflector while running scaled test with 1000 peers with sharding and threading enabled
PR NumberSynopsisCategory: EVO L3 routing for BCM XGS Platforms
1771661Traffic drop will be seen when the IRB interface is without explicit MTU configuration
Product-Group=evo
On QFX5220-32CD, QFX5220-128C & QFX5230 platforms, when the IRB (Integrated Routing and Bridging) interface is without explicit MTU (Maximum Transmission Unit) configuration and the underlying L2 interface has MTU greater than 1518, there will be a complete traffic drop.
PR NumberSynopsisCategory: PFE COS features on BT based platforms
1732461Traffic drop under strict-priority queue before low priority queue
Product-Group=evo
On Junos OS Evolved PTX10001-36MR, PTX10004, PTX10008, and PTX10016 platforms, when a strict-high priority queue without transmit-rate is configured on a 10Gig port, it will experience a packet drop before the low priority queue.
PR NumberSynopsisCategory: Express BT PFE L3 Features
1743034In P2MP-MPLS-LSP set-up traffic drop/traffic blackhaul/label swap/ttl being set to 0 seen due to ARP timeout
Product-Group=evo
On all Junos Evolved platforms, in point-to-multipoint (P2MP) MPLS (Multiprotocol Label Switching) LSP (label-switched path) scenario, multicast composite next-hop (CNH) is not getting updated on Address Resolution Protocol (ARP) expiry of one of the child member. As a result, it points to wrong replication address, and results in generating packets with wrong labels or packet drop or traffic blackhaul or ttl set to 0.
1764775Transit traffic loss during P2MP LSP change
Product-Group=evo
On all Junos Evolved PTX platforms, when Point-to-Multipoint (P2MP) sub-lsps are pruned/grafted, traffic will get dropped on different P2MP LSP(label-switched-path) tunnels.
PR NumberSynopsisCategory: ACX VxLAN Issue
1690815Junos OS Evolved: ACX7024, ACX7100-32C and ACX7100-48L: Traffic stops when a specific IPv4 UDP packet is received by the RE (CVE-2024-21602)
Product-Group=evo
A NULL Pointer Dereference vulnerability in Juniper Networks Junos OS Evolved on ACX7024, ACX7100-32C and ACX7100-48L allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). Please refer to https://supportportal.juniper.net/JSA75743 [juniper.net] for more information.
1766883Traffic impact is observed after device reboot or restart of picd on Junos Evolved ACX7100-48L
Product-Group=evo
On ACX7100-48L: EvoPfemand-main CPU may spike to over 100% after image installation.
PR NumberSynopsisCategory: JUNOS Dynamic Profile Configuration Infrastructure
1703380PDB may get corrupted on the backup RE
Product-Group=evo
PDB (dynamic profile database) may get corrupted on the backup RE (routing engine) as a result of race condition between ffp and bbe-smgd processes, most often during system boot up. New subscribers will not be able to connect if this RE becomes the master RE.
PR NumberSynopsisCategory: EVO Class of Services
1766873Duplicate code points through code-point-aliases under a classifier results in cosd crash
Product-Group=evo
On all Junos Evolved platforms, the class-of-service (COS) commit validation is missing for classifier when using code-point-aliases. Configuring duplicate code-point-aliases and using them in a classifier will result in the cosd crash. The system can be recovered by correcting the config and applying the "restart class-of-service" command.
PR NumberSynopsisCategory: EVO Netstack FIB Service Daemon
1696056The wrong source address will be used in egress packets
Product-Group=evo
The default address selection flag is not seen on a config modify the event, but it is seen where there is a reboot or if fibd is restarted.
1715760neighbor-interface-state not reaching adjacency state for routing protocols over tunneled interface
Product-Group=evo
FIBD operations of routing protocols involving fetching route tables associated with tunneled interfaces can fail, causing issues with traffic loss over tunneled interfaces.
PR NumberSynopsisCategory: Application controller related issues
1629823anomalies/leaks might be seen for some of the DDX objects upon switchover
Product-Group=evo
anomalies/leaks might be seen for some of the DDX objects upon switchover.
PR NumberSynopsisCategory: Issues related to EVO dependency layer including object graphs, incompletes, anomalies and nkdb
1722270Occasional FPC crash and traffic loss is observed with a scaled number of FIB routes
Product-Group=evo
When there are four thousand routes or more on the forwarding table of the PFE (Packet Forwarding Engine) and when interface adds and deletes are being executed it leads to FPC (Flexible PIC Concentrator) crash and traffic loss.
1777613[EVO] master-only IP address is missing on mgmt-0 interface after the master RE abnormal shutdown
Product-Group=evo
[EVO] master-only IP address is missing on mgmt-0 interface after the master Routing-Engineering abnormally shutdown, which causes the router is not accessible via mgmt-0.
PR NumberSynopsisCategory: management ethernet related issues - mgmt-ethd daemon
1672128Observing error "mgd: unable to execute /usr/sbin/arp: Bad file descriptor" intermittently during clear arp command
Product-Group=evo
On all Junos Evolved platforms, the error "mgd: unable to execute /usr/sbin/arp: Bad file descriptor" is intermittently observed during clear arp command.
PR NumberSynopsisCategory: software upgrade infra issues
1776669orchestratord core dump during JSU
Product-Group=evo
If the customer setup has more than 10 nodes (including REs and FPCs), then orchestratord core dump might be seen during JSU upgrade.
1779593[Junos OS Evolved] Committed configuration files are not preserved post software version rollback operation
Product-Group=evo
On all Junos OS Evolved platforms, committed configuration files are not preserved post software version rollback operation. The actual configuration is not affected.
PR NumberSynopsisCategory: Interface PRs defect & enhancement requests
1670362When donor interface is admin down, borrower can't be pinged from local/remote
Product-Group=evo
On all Junos Evolved platforms, in general, the network borrows addresses from lo0 which is not made admin down. When the interface has borrowed the address, need to note when it is down as the down borrowed interface will not receive packets.
1689391LLDP packet drop is seen when the physical interface (IFD) is configured with flexible-vlan-tagging
Product-Group=evo
On all Junos Evolved platforms, when the physical interface (IFD) is configured with flexible-vlan-tagging, LLDP packets are dropped as the outer vlan-id value is not properly set.
PR NumberSynopsisCategory: EVO Netstack Juniper Tunnel Driver Module
1718999TCP connection will be terminated when sent with incorrect MSS
Product-Group=evo
On all Junos Evolved platforms, Transmission Control Protocol (TCP) packets whose size is larger than its interface Maximum Transmission Unit (MTU) will be dropped impacting TCP connections.
PR NumberSynopsisCategory: EVO L2 Control Plane PRs
1749191Some of the MAC addresses are not learned in EVPN-VXLAN scenario
Product-Group=evo
On all Junos and Junos Evolved platforms configured with EVPN-VXLAN (Ethernet Virtual Private Network-Virtual Extensible Local Area Network) when network events such as interface flap/BFD (Bidirectional Forwarding Detection) flap etc. leads to overlay BGP (Border Gateway Protocol) / EVPN flap and results in VTEPs (VXLAN Tunnel Endpoint), IFLs (Logical Interface), IFFs (Interface Family) and IFBDs (Interface Family Bridge Domain) corresponding to remote MH (Multi Home) peers to be deleted and causes new ones to be recreated, it is observed that even though MAC address is received it is not being programmed which results in missing entries of MAC addresses in the MAC table.
1769086Data center interconnect config addition needs to be non-catastrophic.
Product-Group=evo
adding interconnect config can be catastrophic behavior which means bd (Bridge domain) and routing instance object will be deleted and added back.
PR NumberSynopsisCategory: EVO linux defects & enhancement requests
1745190Junos OS Evolved: IPython privilege escalation vulnerability (CVE-2022-21699)
Product-Group=evo
IPython, shipped with Juniper Networks Junos OS Evolved, is subject to an arbitrary code execution vulnerability achieved by not properly managing cross user temporary files. This vulnerability allows one user to run code as another on the same system. Please refer to https://supportportal.juniper.net/JSA75721 [juniper.net] for more information.
PR NumberSynopsisCategory: PRs related to tunnels like GRE, IPIP in EVO control plane
1717782Traffic loss is observed with FTI over IRB as underlay.
Product-Group=evo
In case of FTI (Flexible Tunnel Interface) over IRB (Integrated Routing and Bridging) over ethernet, underlay ifl (logical interface) was pointing to IRB instead of ethernet interface leading to packet loss.
PR NumberSynopsisCategory: mgd, ddl, odl infra issues
1752374Subsequent commits hang will be seen, when transfer-on-commit fails
Product-Group=evo
On all Junos Evolved platforms, When transfer-on-commit is configured and it fails as the destination is unreachable or invalid, commit lock taken by automatic rollback commit is not released. Due to this, subsequent commits result in a hung state.
PR NumberSynopsisCategory: SNMP, mib2d issues
1704878Neighbor device details not listed under snmp walk [ipNetToMediaPhysAddress]
Product-Group=evo
On Junos Evolved platforms, SNMP walk table (ipNetToMediaPhysAddress) is not updated when a neighbour entry is configured.
1737682The snmpd crash is observed after FPC restart
Product-Group=evo
On all Junos Evolved platforms, snmpd crash can be seen when snmpd query is running and simultaneously FPCs are restarted or system rebooted. There is no traffic impact due to this issue.
1760937snmpd-subagent cored
Product-Group=evo
, This issue is a seen very rarely when jnxCos related mibs are queried at a high rate and FPCs are down/unable to respond back to the query.
PR NumberSynopsisCategory: EVPN control plane issues
1673157The rpd crash would be observed when activating or deactivating the EVPN routing-instances
Product-Group=evo
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.
1718534L2ALD core at l2ald_vxlan_ifl_create_msg_build
Product-Group=evo
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.
1739686Evpn-vxlan comp nh is not installed in pfe after peer reboot
Product-Group=evo
Evpn-vxlan comp nh is not installed in pfe after reboot.
1747706Intermittent packet loss can be observed in evpn-vpws local switching scenario
Product-Group=evo
When evpn-vpws local switching is configured, RPD is setting the user flags on the ccc ucast next hop, which is being interpreted as MPLS_OAM_FILTER and leading to traffic dropThe packet loss is random, the pattern is still to be analyzedThe issue can be seen regardless of control word and vlan configuration on the instance and interfaces
PR NumberSynopsisCategory: EVPN Layer-2 Forwarding
1718165ARP learning issues are observed post-execution of the CLI command 'clear bridge mac-table' or 'clear ethernet-switching table' in the EVPN-MPLS over IRB environment
Product-Group=evo
On all Junos and Junos Evolved platforms, L3 (Layer 3) traffic will be impacted when ARP (Address Resolution Protocol) entries get deleted for the MAC (Media Access Control) address having a bad state post execution of the CLI 'clear bridge mac-table' or 'clear ethernet-switching table' command in the EVPN-MPLS (Ethernet VPN - Multiprotocol Label Switching) over IRB (Integrated routing and bridging) environment.
1734091Traffic drop is observed in EVPN-VXLAN CRB scenario
Product-Group=evo
On all Junos Evolved platforms, in EVPN-VXLAN (Ethernet VPN-Virtual Extensible LAN) CRB (centrally-routed bridging) scenario, post reboot of chassis or on clearing BGP (Border Gateway Protocol) neighbor on spine nodes ARP (Address Resolution Protocol) entries which are remotely learned when IRB (integrated routing and bridging) ifl is down and when it comes up, these entries are present in the ARP table but the corresponding destination routes are missing in the forwarding table. Due to which traffic drop is observed.
1743913IRB reachability issues may be observed in the EVPN-VXLAN environment when looped ARP comes on ESI-LAG
Product-Group=evo
On Junos and Junos OS Evolved platforms (except MX platforms) with EVPN-VXLAN (Ethernet VPN - Virtual Extensible LAN) configured, in case of traffic loop conditions, self-generated ARP packets (having physical-IRB MAC as SMAC) may come back to the same node where it originated. Such rare scenarios, when the MAC address of the IRB (Integrated Routing and Bridging) ages out and is cleared from the MAC table, also associated MAC-IP route (IRB route) might get cleaned. This may result in IRB reachability issues as the remote VTEPs (Virtual Tunnel End Point) won't have IRB information of the local VTEP and on the local VTEP, there won't be EVPN database entry and type-2 EVPN advertisements for local IRB towards the remote VTEPs.
1773734Traffic flooding is observed due to MAC-IP deletion by l2alm in the EVPN-VXLAN / EVPN-MPLS environment
Product-Group=evo
On Junos and Junos Evolved platforms, in the EVPN-VXLAN (Ethernet VPN-Virtual Extensible LAN) / EVPN-MPLS (Ethernet VPN-Multiprotocol Label Switching) environment when l2alm (Layer 2 Address Learning Manager) deletes the MAC-IP (Media Access Control - Internet Protocol Address) entry but doesn't re-add the MAC-IP entry right away leads to traffic flooding i.e. might result in congestion, packet looping, and packet drops.
PR NumberSynopsisCategory: ISIS routing protocol
1682778The rpd process will crash and generate core post graceful restart
Product-Group=evo
The rpd process crash is seen when a graceful rpd restart is initiated and ISIS auto-bandwidth is not configured in the system.
PR NumberSynopsisCategory: Interface PR for LC1202 LC
1768453PCS errors on Ethernet interface on certain PTX platforms running Junos Evolved
Product-Group=evo
On certain PTX10001-36MR and PTX10K4/8/16 with LC1201/LC1202 platforms running Junos Evolved 21.2R1-S1, 21.2R2, 21.3R1 or later releases, PCS (Physical Coding Sublayer) errors and framing errors would be seen on 10/100GE interfaces and the high rate of PCS error could lead to interface flap.
PR NumberSynopsisCategory: Issues related to Junos licensing infrastructure
1766515A warning message is seen while installing a license key with an unknown feature
Product-Group=evo
On all Junos platforms, a warning message is seen when installing the license key where features don't support the product.
PR NumberSynopsisCategory: Multiprotocol Label Switching
1701420The rpd core and traffic loss is observed on Junos and Junos Evolved platforms
Product-Group=evo
On Junos and Junos OS platforms, if an LSP (Label-Switched-Path) is configured and delegated to an external controller is disabled (not deleted from configuration), and then a rpd restart or RE (Routing Engine) switchover takes place, the rpd process crashes and generates core resulting in traffic loss.
PR NumberSynopsisCategory: For multicast snooping on MX
1649410"show multicast snooping route extensive instance evpn-vxlan-A" with vlan filter is not showing VE, AR mesh group route entries
Product-Group=evo
"show multicast snooping route extensive instance evpn-vxlan-A" with vlan filter will show all the mesh group routes present in the MCSNOOPD table.
PR NumberSynopsisCategory: Protocol Independant Multicast
1719596Junos OS and Junos OS Evolved: Receipt of a specific genuine PIM packet causes RPD crash (CVE-2023-44175)
Product-Group=evo
An Improper Handling of Exceptional Conditions vulnerability in Juniper Networks Junos OS and Junos OS Evolved allows an attacker to send specific genuine PIM packets to the device resulting in routing protocol daemon (rpd) to crash causing a Denial of Service (DoS). Please refer to https://supportportal.juniper.net/JSA73141 [juniper.net] for more information.
PR NumberSynopsisCategory: KRT Queue issues within RPD
1774975Features utilizing inactive routes will not work properly after the device reboot
Product-Group=evo
On all Junos and Junos OS Evolved platforms, due to some software issue, after the device reboot features utilizing inactive routes in the routing table will not work properly. This will cause issues like some inactive routes not being advertised when selected as the best path, features like advertise-inactive not working properly as it utilizes an inactive route flash, high Routing Protocol Daemon (rpd) Central Processing Unit (CPU) utilization, etc.
PR NumberSynopsisCategory: Issue related to mcnh routing infrastructure within RPD
1774334Synchronization issue between RIB and FIB tables leads to the P2MP LSP traffic outage
Product-Group=evo
On all Junos OS Evolved platforms, RIB (Routing Information Base) and FIB (Forwarding Information Base) tables are not synchronized properly, causing the P2MP (Point-to-Multipoint) LSP (label-switched-path) traffic outage when executing the CLI command "clear rsvp session".
PR NumberSynopsisCategory: Shard routing infrastructure within RPD
1716431Memory 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 NumberSynopsisCategory: RPD route tables, resolver, routing instances, static routes
1665094Route leaking might happen with auto-export configuration
Product-Group=evo
On all Junos and Junos evolved platforms, if auto-export is configured under VRF, unexpected leaking of the routes could be observed.
PR NumberSynopsisCategory: RPD API infrastructure
1710274Next Hop counts are not as expected
Product-Group=evo
Next Hop counts are not as expected
PR NumberSynopsisCategory: PTX10K platform specific fabric PRs
1751581PTX10K EVO - CMerror not raised post LAH(link auto-heal) fails during training failure
Product-Group=evo
On PTX EVO platforms, CMerror is not raised post LAH(link auto-heal) fails during training failure.
PR NumberSynopsisCategory: PTX10K specific platform PRs
1738854The FPC MEZZ board state becomes unknown with 'Too many open files' error messages due to file descriptor leak in picd process
Product-Group=evo
On PTX10K Junos OS Evolved platforms, the FPC MEZZ board state becomes unknown with 'Too many open files' error messages due to an FD (File Descriptor) leak in picd (Physical Interface Card Daemon) process.
1749781PTX10K4/8/16 EVO - Both SIB PWR/STAT LEDs become Unlit/OFF by RE switchover
Product-Group=evo
Both SIB PWR/STAT H/W LEDs become Unlit/OFF by RE switchover on PTX10K4/8/16 EVO platforms.
1758265PTX10K4/8/16 EVO - Mezz board status of all FPCs becomes "unknown" post RE switchover by "request node" CLI
Product-Group=evo
Mezz board status of all FPCs on PTX10K4/8/16 EVO platforms becomes "unknown" post RE switchover by "request node" CLI
PR NumberSynopsisCategory: SNMP Infrastructure (snmpd, mib2d)
1651774VTEP might report a high speed on the sub-interface, causing SNMP alarms
Product-Group=evo
When used on the VTEP sub-interface, the ifspeed OID may show a maximum value that is not zero.
PR NumberSynopsisCategory: Bug and Review Tracking for Segment routing traffic eng
1763406LDP traffic to destination route might be lost when TI-LFA is configured
Product-Group=evo
On all Junos and Junos OS Evolved platforms, when LDP tunnel over SR-TE route or over RSVP and LFA/rLFA/TI-LFA backup path for the same destination is configured, or if rLFA/LFA with L-ISIS as backup path is configured, the route to the destination is missing. LDP route for the destination is deleted because SR-TE LSP next hop is deleted by processing L-ISIS route with the backup path. Due to this LDP route gets deleted, LDP traffic to destination route is lost.
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1772201unexpected commit error - error: VLAN-ID must be specified on tagged ethernet interfaces
Product-Group=evo
unexpected commit error like 'error: VLAN-ID must be specified on tagged ethernet interfaces', due to 'commit check' reset internal flag incorrectly after load overide configuration in rare condition.
PR NumberSynopsisCategory: Virtual Private LAN Services
1729052The rpd process crash will be observed during VPLS to EVPN migration
Product-Group=evo
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 NumberSynopsisCategory: Express ZX PFE L3 Features
1768610FPC offline causes PTX10003-160C to reboot
Product-Group=evo
On PTX10003-160C platforms, an FPC (Flexible PIC Concentrator) offline via the command "request chassis fpc slot offline" triggers the evo-aftmand process crash as the FPC goes offline. This causes a system reboot. Services will be resumed normally after reboot.
 
 

21.4R3-S6-EVO - List of Known issues 

PR NumberSynopsisCategory: HW bugs for PTX10008/16 14.4 Tb Line Card, SIB-8 and SIB-16
1749793Scapa : EVO CB1, SIB0 and FPC0 (JNP10K-LC1201) went to fault after system power outage in lab.
Product-Group=evo
Scapa : EVO CB1, SIB0 and FPC0 (JNP10K-LC1201) went to fault after system power outage in lab.

Resolved In:
PR NumberSynopsisCategory: Alfa Romeo Chassis Category
1742510Tunnel interfaces are getting bounced causing a momentary impact on traffic
Product-Group=evo
On MX304 device and LC9600 line card, upon Routing Engine switchover chassisd on new master was not re-initializing the tunnel/inline services configuration data, hence all static tunnel interface (GRE, IP-IP, Multicast (MT), PIM, Logical tunnels and Virtual loopback tunneling (VT)) and inline interfaces will get bounced (deleted and re-created) after doing any CLI commit after an RE switchover. There will be momentary impact on traffic using these interfaces.

Resolved In: evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:21.4R3-S5-J6 junos:21.4R3-S6 junos:22.2R3-S3 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1 junos:23.4R1
PR NumberSynopsisCategory: Border Gateway Protocol
1663883Traffic loss will be seen due to delay in BGP convergence time
Product-Group=evo
On all Junos and Junos Evolved platforms, whenever there is high percentage of background CPU usage that causes the rpd process to run at an average CPU load, BGP convergence will be slow, which results in traffic loss.

Resolved In: evo:21.4X1-EVO evo:22.3R2-EVO evo:22.3R3-EVO evo:22.3X80-D33-EVO evo:22.4R1-EVO evo:23.4R1-EVO junos:18.2X75-D67 junos:20.3X75-D50 junos:22.3R2 junos:22.3R3 junos:22.4R1 junos:23.4R2
1689904BGP LU Advertisements fail with the message "BGP label allocation failure: Need a gateway"
Product-Group=evo
On all Junos and Junos Evolved platforms BGP-LU (Border Gateway Protocol Labeled-Unicast) Advertisements fail with the message "BGP label allocation failure: Need a gateway" based on timing conditions involving route resolution and installation.

Resolved In: evo:22.2R3-S3-EVO evo:22.3R3-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:21.4R3-S5 junos:22.1R3-S2 junos:22.2R3-S3 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R1 junos:23.2R1
1712527The PE advertises incorrect next-hop towards CE although BGP export policy configured with next-hop under policy-statement
Product-Group=evo
The show route advertising-protocol bgp reporting nexthop self rather than IP in the configured policy-statement for next-hop.

Resolved In: evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:21.2R3-S6 junos:21.3R3-S5 junos:22.2R3-S2-J2 junos:22.2R3-S3 junos:22.4R2-S1 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1 junos:23.4R1
1737679The rpd crash files are seen due to a use-after free of objects
Product-Group=evo
On all Junos and Junos Evolved platforms, due to a use-after free of objects that are being shared across threads for tracing that happened when some assumptions were broken in a recent fix. The crash files generated in rare conditions when the object is freed prior to when the trace is cut.

Resolved In: evo:22.3X50-EVO evo:22.4R3-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:22.2R3-S3 junos:22.3R3-S2 junos:22.4R3 junos:23.2R2 junos:23.3R1 junos:23.4R1
PR NumberSynopsisCategory: PTX10003 Interface related issues
1615000evo-aftmand process causing increase in memory utilization
Product-Group=evo
On some Junos and Junos Evolved platforms the evo-aftmand (Advanced Forwarding Toolkit manager) process might consume high memory over a period of time leading to an increase in the shared memory utilization.

Resolved In: evo:20.4R3-S10-EVO evo:21.2R3-EVO evo:21.3R3-EVO evo:21.4R1-S2-EVO evo:21.4R2-EVO evo:22.1R2-EVO evo:22.2R1-EVO junos:22.1R2 junos:22.2R1
PR NumberSynopsisCategory: EVO L3 routing for BCM XGS Platforms
PR NumberSynopsisCategory: DNX L2 related features
1756648The evo-pfemand process is observed to crash on Junos Evolved platforms with LACP configuration
Product-Group=evo
JDI_REG:EVO:ultron: evo-pfemand.re cored at futex_abstimed_wait_cancelable (private=0, abstime=0x7fd17582c870, clockid=0, expected=0, futex_word=0x7fd1479fb570) at ../sysdeps/unix/sysv/linux/futex-internal.h:208

Resolved In: evo:23.4R1-EVO evo:24.1R1-EVO
PR NumberSynopsisCategory: EVO Netstack FIB Service Daemon
1712705request routing-engine login other-routing-engine failure on EVO platforms
Product-Group=evo
Symptom request routing-engine login other-routing-engine failure Root Cause evo_ssh did not have an internal port defined Exposed versions: with fix of 1693858 evo:20.4R3-S6-EVO evo:21.2R3-S4-EVO evo:22.2R2-S1-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R1-EVO evo:22.4R2-EVO evo:23.1R1-EVO junos:22.3R2

Resolved In: evo:22.2R3-EVO
PR NumberSynopsisCategory: Multiprotocol Label Switching
1698889The rpd process will crash when rpd is restarted
Product-Group=evo
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.

Resolved In: evo:22.3R3-EVO evo:22.3X50-EVO evo:22.3X80-D38-EVO evo:22.4R3-EVO evo:23.1R1-EVO evo:23.1R2-EVO evo:23.2R1-EVO junos:20.3X75-D43 junos:21.2R3-S6 junos:21.3R3-S5 junos:21.4R3-S5 junos:22.1R3-S3 junos:22.2R3-S1 junos:22.3R3 junos:22.4R2-S2 junos:22.4R3 junos:23.1R1 junos:23.1R2 junos:23.2R1
1701800Memory leak issue in TED
Product-Group=evo
On all Junos and Junos Evolved platforms, a memory leak is observed in the traffic engineering database (TED) when the inet table is not cleaned up after routing instance deactivation.

Resolved In: evo:22.2R3-EVO evo:22.3R2-EVO evo:22.3R3-EVO evo:22.4R1-EVO evo:22.4R2-EVO evo:23.1R1-EVO junos:19.4R3-S11 junos:19.4R3-S3-J9 junos:20.2R3-S7 junos:20.3X75-D44 junos:20.3X75-D52 junos:20.4R3-S6 junos:21.1R3-S5 junos:21.2R3-S2-J6 junos:21.2R3-S3-J23 junos:21.2R3-S4 junos:21.3R3-S3 junos:21.4R3-S3 junos:22.1R3-S1 junos:22.2R3 junos:22.3R2 junos:22.3R3 junos:22.4R1 junos:22.4R2 junos:23.1R1
PR NumberSynopsisCategory: Path computation client daemon
1687885On Junos and Junos Evolved platforms delegated LSP control will not be returned to the PCC in a specific scenario
Product-Group=evo
On all Junos and Junos Evolved platforms where multiple PCEs (Path Computation Element) are provisioned and connected to Junos PCC (Path Computation Client) and when all the PCEP (Path Computation Element Protocol) sessions are down, LSP (Label Switched Path) control will not be returned to the PCC. As a result, if existing EROs (Explicit Route Object) becomes invalid, new ERO will not be computed by PCC and there will be traffic loss.

Resolved In: evo:21.4R3-S5-EVO evo:22.1R3-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R1-EVO evo:23.1R1-EVO junos:21.2R3-S3 junos:22.1R3 junos:22.2R2 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:23.1R1
PR NumberSynopsisCategory: QFX L2 PFE
1711860The dcpfe process will crash due to memory fragmentation
Product-Group=evo
On Junos and Junos OS Evolved platforms, the dcpfe (Dense Concentrator Packet Forwarding Engine) process crash will be observed due to memory fragmentation issue. This is a very rare case and would impact traffic as due to dcpfe failure the PFE restarts, so the interfaces will flap.

Resolved In: evo:23.4R1-EVO junos:23.4R1
PR NumberSynopsisCategory: RPD Next-hop issues including indirect, CNH, and MCNH
1716436Traffic loss due to incorrect route resolution and KRT queue getting stuck with 'EINVAL -- Bad parameter in request' error
Product-Group=evo
On all Junos and Junos OS Evolved platforms, due to a bug in route resolution over specific types of next hops, the route can resolve over itself and the nexthop chain keeps expanding. Due to this issue, the depth of recursion gets higher than supported and the KRT (Kernel Routing table) queue returns errors for nexthops. As a result, there will be incorrect route resolution, traffic loss and occasionally, the rpd (routing protocol deamon) crashes. The necessary configurations and conditions that will result in this issue are below 1. BGP (Border Gateway Protocol) Prefix-Independent Convergence (PIC) ("protect core") is configured and BGP receives same prefix from EBGP and IBGP neighbors 2. BGP LU (Labeled Unicast) with "protection" to create backup path to protect the active and BGP receives same prefix from EBGP and IBGP neighbors 3. Mutually recursive Route resolvability situations like Resolving using Default-route (not having proper resolution config)

Resolved In: evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO junos:22.2R3-S2 junos:22.3R3-S1 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
PR NumberSynopsisCategory: PTX10K Diagnostics related PRs
1725658Enabling Cell BIST Support for LC1201 and LC1202 new HBM components
Product-Group=evo
With the new HBM component, a software upgrade is needed to support the new hardware for the LC1201, LC1202. (See TSB71797 [juniper.net])

Resolved In: evo:22.1R3-S3-EVO evo:22.2R3-S1-EVO evo:22.3R3-EVO evo:22.3X50-EVO evo:22.3X80-D35-EVO evo:22.4R2-S1-EVO evo:22.4R3-EVO evo:23.1R1-S1-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR NumberSynopsisCategory: PTX10K specific platform PRs
1705225PTX10004/10008/10016 line card may be in the present state after the reboot
Product-Group=evo
When a PTX10004/10008/10016 running Junos Evolved software reboots, its line card may stay in the "present" state. The line card can be brought up online by using the cli command - "request chassis fpc slot 'slot number' restart force". There is no need to RMA or replace the line card.

Resolved In: evo:22.2R3-EVO evo:22.3R2-EVO evo:22.3R3-EVO evo:22.4R1-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:23.2R1
1766097PTX10008: When NSR Enabled and FMBB Knobs are configured and if SIB is Offline/Online casue resiliencyd core
Product-Group=evo
PTX10008: When NSR Enabled and FMBB Knobs are configured and if SIB is Offline/Online casue resiliencyd core

Resolved In:
PR NumberSynopsisCategory: Issues related to control plane security
1655537UEFI BIOS Key synchronization tool - efitools.service failed after optics diagnostics test
Product-Group=evo
The efitools.service failed since the EFI data structure is set to be immutable in the JUNOS WRL version 9.x

Resolved In: evo:21.4X1-EVO evo:22.1R3-EVO evo:22.2R2-EVO evo:22.3R3-S2-EVO evo:22.3X50-EVO evo:22.3X80-D39-EVO evo:22.3X80-D41-EVO evo:22.4R1-EVO junos:22.1R3 junos:22.2R1-S2 junos:22.2R2 junos:22.2R3 junos:22.3R1 junos:22.3R1-S1 junos:22.3R2 junos:22.3R3
PR NumberSynopsisCategory: Issues related to NETCONF
1585855< ok/> response is getting generated along with < rpc-error>
Product-Group=evo
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.

Resolved In: evo:22.2R3-S1-EVO evo:22.3R2-S2-EVO evo:22.4R3-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:20.3X75-D36 junos:22.2R3-S1 junos:22.3R2-S2 junos:22.3R3-S1 junos:22.4R2-S2 junos:22.4R3 junos:23.1R1 junos:23.2R1
PR NumberSynopsisCategory: Issues related to YANG Data Models
1725934ODL controller is throwing unavailable capabilities error for few of the Openconfig Yang modules
Product-Group=evo
ODL controller is throwing unavailable capabilities error for few of the Openconfig Yang modules

Resolved In: evo:22.4R3-EVO evo:23.2R1-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:21.4R3-S6

 

Modification History

First publication 2024-01-16