Alert Type

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

Product Affected

ACX PTX QFX platforms running Junos Evolved software

Alert Description

Junos Software Service Release version 22.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

NOTE: Starting on August 30th, 2024, we include PR's severity with each entry. See KB86335 [juniper.net] for the definition of PR's Severity

 

Solution

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

22.4R3-S6-EVO - List of Fixed issues 

PR NumberSynopsisCategory: Bi Directional Forwarding Detection (BFD)
1846448
Major		The S-BFD responder session cannot be distributed to PFE and failing S-BFD session to establish
Product-Group=evo
Severity=Major		On al MX and PTX platforms, If S-BFD(Seamless-Bidirectional Forwarding Detection) responder is configured without the "lo0.0" on device and with any other "lo0.x " then this S-BFD responder session cannot be distributed to PFE(Packet Forwarding Engine) and fails to come up in distributed mode. Hence BFD service will be impacted.
PR NumberSynopsisCategory: Border Gateway Protocol
1817834
Major		The rpd crashes when stale label entry keeps increasing when knob stale-labels-holddown-period is configured
Product-Group=evo
Severity=Major		On all Junos and Junos Evolved platforms configured with the "stale-labels-holddown-period" setting and extensive label configurations (such as Multiprotocol Label Switching labels), the Routing Protocol Daemon (RPD) may crash if stale labels are not cleared periodically and keep accumulating. Due this, temporary traffic impact will be seen until the rpd process restarts.
PR NumberSynopsisCategory: PFE L2 forwarding features on BT based platforms
1795953
Major		VRF leaking does not work due to incorrect VRF info passed to Control Plane on all Junos OS Evolved PTX series platforms
Product-Group=evo
Severity=Major		On all Junos OS Evolved PTX series platforms, when VRF (Virtual Routing and Forwarding) Leaking is configured, packets received over IRB (Integrated Routing and Bridging) interface on a particular VRF and destined for a local IP (for example, destined for loopback interface) on a different VRF will get dropped
PR NumberSynopsisCategory: Express BT PFE L3 Features
1841145
Major		The evo-aftmand-bt/evo-aftmand-bx crash observed with SCU/DCU feature on IPv6 Prefixes
Product-Group=evo
Severity=Major		On Junos Evolved PTX10001-36MR, PTX10004, PTX10008, PTX10016, PTX10002-36QDD platforms, the evo-aftmand-bt/evo-aftmand-bx process may crash at high scale when source-class-usage (SCU) /destination-class-usage (DCU) features are configured on IPv6 prefixes (25 to 88 bits) due to hardware lookup entry updates from 20 to 40 bytes for additional action information.
PR NumberSynopsisCategory: Class of Service
1836528
Minor		FC id goes out of sync between the RE and PFE impacting all CoS features using FC id
Product-Group=evo
Severity=Minor		On all Junos and Junos Evolved Platform, forwarding-class (FC) identifier (id) goes out of sync between the Routing Engine (RE) and Packet Forwarding Engine (PFE) when software upgrade is performed. When In Service Software Upgrade (ISSU) is performed, FC id goes out of sync between the RE and PFE impacting all class-of-service (CoS) features using FC id. When manual software upgrade is performed (without using ISSU) , this issue will be seen as a cosmetic display issue where the order in which the FC configurations are displayed will differ.
PR NumberSynopsisCategory: Device Configuration Daemon
1848768
Major		MTU configuration is not applied from the configuration group after commit and "warning" is seen
Product-Group=evo
Severity=Major		When configuring MTU on interfaces through a configuration-group and commit the changes, those are not saved on the configuration file.
PR NumberSynopsisCategory: FIB telemetry, fibtd, libocaft repositories
1781544
Major		The fibtd process crash is seen on all Junos Evolved platforms
Product-Group=evo
Severity=Major		On all Junos Evolved platforms configured with fib-streaming, fibtd process crash can be seen due to interface flapping which caused traffic impact until the process self-recovers.
PR NumberSynopsisCategory: EVO L2 Control Plane PRs
1844623
Major		Stale MAC-IP entries are not cleared in an EVPN-VXLAN scenario when encapsulate-inner-vlan or decapsulate-accept-inner-vlan or both knobs are present
Product-Group=evo
Severity=Major		On all Junos and Junos OS Evolved platforms, when decapsulate-accept-inner-vlan or encapsulate-inner-vlan or both knobs are configured for a VXLAN (Virtual Extensible Local Area Network) and when any action corresponding to MAC-IP entries cleanup takes place, the MAC-IP entries will not be cleaned up from kernel. This will result in anomalies in device and could also lead to a core crash.
PR NumberSynopsisCategory: Express PFE MPLS for EVO platforms
1829924
Major		PTX devices acting as transit nodes display incorrect MPLS traceroute or TTL
Product-Group=evo
Severity=Major		On Junos Evolved PTX10K platforms, when there is an ECMP to destination, PTX devices in a transit MPLS path do not decrement the TTL value properly, leading to ICMP tunneling failure and incorrect traceroute behavior.
1847169
Major		Traffic going over LDP or LDPoRSVP route matching the CBF is getting impacted when PTX EVO platform working as PHP router with CBF configuration
Product-Group=evo
Severity=Major		Traffic hitting Penultimate Hop Popping router and matching the class based forwarding (CBF) is affected when Junos OS Evolved PTX platform acting as PHP router with CBF configuration. This will impact traffic going over affected LDP or LDPoRSVP route. Also, it will cause ping and trace route failure.
PR NumberSynopsisCategory: event/op/commit scripts, SLAX, netconf issues
1836806
Major		Rest API service will not launch on EVO devices when the server address is configured as any interface IP (excluding management interface IP).
Product-Group=evo
Severity=Major		Rest API service will not launch on EVO devices when the server address is configured as any interface IP (excluding management interface IP).
PR NumberSynopsisCategory: EVPN control plane issues
1806416
Major		The MAC pinning functionality is not working on QFX platforms
Product-Group=evo
Severity=Major		On Junos and Junos Evolved QFX platforms with EVPN-VXLAN (Ethernet Virtual Private Network- Virtual Extensible LAN) configuration, the MAC pinning functionality is not working as expected, causing traffic forwarding issues.
PR NumberSynopsisCategory: QFX5700 RCB software.
1762909
Critical		The CLI output string for DPLL firmware mismatch has changed on QFX5700
Product-Group=evo
Severity=Critical		The CLI output string for DPLL firmware mismatch has changes as follows: Minor RE 0 RE DPLL minimum supported firmware version mismatch Minor RE 1 RE DPLL minimum supported firmware version mismatch Minor FPC 0 FPC DPLL minimum supported firmware version mismatch Minor FPC 1 FPC DPLL minimum supported firmware version mismatch
PR NumberSynopsisCategory: Interface Information Display
1631200
Major		The packets for IPv6 'Local statistics'(host-inbound/outbound) are counted against the 'IPv6 transit statistics' in IFL.
Product-Group=evo
Severity=Major		IFL counter has a counter named "IPv6 transit statistics". It can be confirmed on "show interfaces extensive" command output. However, this counter is originally for IPv6 total statistics(transit + local) and the counter name was wrong from the first. On older releases like 19.1R1, as the support for IPv6 local stats was not available the local stats was always zero. So, the meaning of the counter name was the same to the counting content coincidentally. In latest releases support for IPv6 local stats has been added but the counter name was not changed. As the local stats will not be zero the difference between the meaning of the counter name and the counting content started being visible.
PR NumberSynopsisCategory: ISIS routing protocol
1841108
Major		Traffic drop is seen after GRES on ISIS peer
Product-Group=evo
Severity=Major		On all Junos and Junos OS Evolved platforms, in an ISIS(Intermediate System-Intermediate System) graceful restart scenario, helper node sends and programs its locally configured hold-time (180 secs) instead of the "Restart-duration" received as hold-time from DUT (210 secs), due to this incorrect update, the hold timer expires at the helper node before the GR (Graceful Restart) is complete on DUT and it causes a flap of ISIS adjacency on peer/helper Node.
PR NumberSynopsisCategory: jdhcpd daemon
1779273
Major		DHCPv6 Information-request packets will be dropped when it has server identifier option
Product-Group=evo
Severity=Major		On all Junos and Junos OS Evolved platforms acting as Dynamic Host Control protocol (DHCP) relay agent or DHCP server, DHCPv6 information-request packets are dropped when it has server identifier option. There will be no traffic impact however, the requested configuration parameters by client will not be shared by servers.
1825998
Major		DHCP ALQ process crashes to recover from memory leak.
Product-Group=evo
Severity=Major		On all Junos OS and Junos OS Evolved platforms , In a rare scenario when memory leak happens the Dynamic Host Configuration Protocol (DHCP) active-leasequery (ALQ) process crashes automatically.
PR NumberSynopsisCategory: lacp protocol
1773702
Major		MC-LAG will not work as expected on all platforms
Product-Group=evo
Severity=Major		On all Junos and Junos OS Evolved platforms, due to mis-wiring or unexpected design in MC-LAG topology, when all the Multi-Chassis Link Aggregation (MC-LAG) nodes including Customer Edge (CE) devices are rebooted at once, MC-LAG will not work as expected.
PR NumberSynopsisCategory: lldp sw on MX platform
1811545
Major		The LLDP neighborship does not recover on AE interfaces
Product-Group=evo
Severity=Major		When LLDP is configured on interface all and there are AE interfaces configured, to disable LLDP on one of the AE "set protocols lldp interface is done". To enable it back when rollback is done for reverting disable config, AE is not participating in LLDP neighborship and this happening because PFE stopped sending packets to control plane because on rollback L2CPD did not sent LLDP ENABLE for its child interface to PFE and LLDP on child interface was still set to disabled for PFE.
PR NumberSynopsisCategory: Protocol Independant Multicast
1767314
Major		RPD may restart unexpectedly when MSDP peers were reset or closed
Product-Group=evo
Severity=Major		When an MSDP peer is terminated, the peer's information may not be cleaned up properly. Causing the RPD process to restart unexpectedly.
PR NumberSynopsisCategory: ZT/YT pfe qos software issues
1793375
Critical		CMErrors are observed on MX platforms running MPC10/MPC11 causing the PFE to be disabled
Product-Group=evo
Severity=Critical		On all MX platforms having MPC10 or MPC11 having class-of-service configured, it is observed that in a scaled scenario (1500 IFLs (Interface Logical)), when queues are oversubscribed and the output interface starts to get congested, "CMERROR 0x230063 " or "XQSS_CMERROR_SCHED_QL4_INT_REG_DQU_QSUM_UDR" error message is seen. These cm errors would result in PFE (Packet Forwarding Engine) disable or the action configured in the device.
PR NumberSynopsisCategory: Virtual Router Redundancy Protocol
1760534
Major		VRRP Status displayed incorrectly in CLI command
Product-Group=evo
Severity=Major		On Junos and Junios OS Evolved platforms with dual RE, when GRES and NSR are enabled. VRRP status is wrongly displayed in standby RE when VRRP is configured although it is in the correct state. There is no impact with services. its a display issue.

 

 

22.4R3-S6-EVO - List of Known issues 

PR NumberSynopsisCategory: Bowmore specific platform defects tracking
1782498
Major		[Junos OS Evolved] PTX10004/8/16 - !Minor alarm LED on FPM(Front Panel Module) is glowing Yellow, although there is no active alarms/errors on the system
Product-Group=evo		On PTX10004/8/16 EVO platforms, !Minor alarm LED on FPM(Front Panel Module) is glowing Yellow, although there is no active alarms/errors shown by "show system alarms" CLI.

Resolved In: evo:22.4R3-S2-J1-EVO evo:23.4R2-S4-EVO evo:24.2R2-EVO evo:24.4R1-EVO evo:25.1R1-EVO junos:24.2R2 junos:24.4R1 junos:25.1R1
PR NumberSynopsisCategory: Layer 3 forwarding, both v4+v6
1841071
Major		Incorrect routing seen for VRF traffic after changing packet-forwarding options from hw-db-profile to balanced-exem
Product-Group=evo		On all ACX Evolved platforms the packet-forwarding options hw-db-profiles "balanced-exem" and "l3-xl" causes routing issues for traffic coming in a VRF (Virtual routing and forwarding) and forwarded using the default route leading to traffic impact.

Resolved In: evo:23.2R2-S3-EVO
PR NumberSynopsisCategory: eventd, syslog infra issues
1815238
Major		PTX10004 - Host-name is not updated in picd logs
Product-Group=evo		On Junos OS Evolved platforms, host-name was not appended to PICD logs.

Resolved In: evo:24.2R2-EVO evo:24.4R1-EVO evo:25.1R1-EVO evo:25.2R1-EVO junos:24.4R1 junos:25.1R1
PR NumberSynopsisCategory: PTX10K specific platform PRs
1766099
Major		PTX10016 - Power budget allocation is missing one fantray power
Product-Group=evo		Before this software fix, the power budget for PTX10016 running Junos Evolved software used only half of the fan power requirement. The incorrect FAN power requirement was 2530 Watts. The new fan power budget is corrected to be 5060 Watts.

Resolved In: evo:22.3X80-D45-EVO evo:22.3X80-D46-EVO evo:23.4R2-EVO evo:24.1R1-EVO junos:23.4R2 junos:24.1R1

 

Modification History

First publication 2025-01-14