Alert Type
PSN - Product Support 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 21.4R3-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 21.4R3-S2-EVO is now available.
21.4R3-S2-EVO - List of Fixed issues
PR Number
Synopsis
Category: Express BT PFE L3 Features
1693710
PTX 10004/8/16 EVO : Generic CM Alarm is added for triggering PFE chip init failure
Product-Group=evo
On PTX10004/8/16 EVO, chip init failure will eventually result in PFE going into fault state, but there is no alarm triggered. Generic CM Error is added to result in an alarm when the chip init fails for any reason.
PR Number
Synopsis
Category: Ztp related issues
1683964
PTX EVO : Major alarm "Application ztp fail on node Re0" appears about one day later post system zeroize
Product-Group=evo
On PTX EVO, application ztp fails on node Re0 about one day later post system zeroize.
PR Number
Synopsis
Category: SNMP, mib2d issues
1690850
Interface physical ip address is assigned to SNMP Trap source address after chassis restart although source-address lo0 is configured under trap-options
Product-Group=evo
Interface physical ip address is assigned to SNMP Trap source address after chassis restart although source-address lo0 is configured under trap-options
PR Number
Synopsis
Category: Multiprotocol Label Switching
1655031
The rpd core is seen due to IGP database and BGP LS database out of sync
Product-Group=evo
On all Junos and Junos OS Evolved platforms, rpd core is hit when the events for deleting prefixes, sids, links and nodes come in out of order which occasionally leads to IGP database and BGP LS database out of sync.
1690458
On a controller based MPLS setup with container LSPs, rpd daemon crashes after LSP deletion occurs
Product-Group=evo
On all Junos-based platforms, in a scenario where an external controller is provisioned, rpd crashes when an externally controlled container LSP (Label Switched Path) is deleted and the software tries to update its status.
PR Number
Synopsis
Category: Path computation client daemon
1675816
In a rare case, 'pccd' will crash when the PCEP connection is down
Product-Group=evo
On all Junos and Junos Evolved platforms, on the intermediate device when connection towards Path Computation Element (PCE) is down, Path Computation Element Protocol (PCEP) session will be down resulting in pccd crash. Routing protocols are not impacted but pccd crashes.
PR Number
Synopsis
Category: Periodic Packet Management Daemon
1687395
On single PFE with Fusion satellite, LACP is not sending PDUs
Product-Group=evo
On platforms supporting Fusion technology, LACP (Link Aggregation Control Protocol) is not up on the aggregate ethernet interfaces when a satellite device is connected to an aggregate device with a single PFE (Packet Forwarding Engine) and is upgraded to a software version 19.4 and above.
PR Number
Synopsis
Category: KRT Queue issues within RPD
1639252
High CPU utilization for rpd process might be seen
Product-Group=evo
On all Junos OS and Junos OS Evolved devices, the rpd process might utilize a large amount of the CPU during commit. This might only be seen in a scaled static route setup with virtual routing and forwarding (VRF) and Bidirectional Forwarding Detection (BFD) configured. The reason for the CPU spike is that kernel routing table (KRT) might get stuck and keep running for a long time. The high CPU might hamper the rpd process functionality in rare cases. However, the system recovers by itself when it encounters this issue.
1686211
The rpd crash would be observed when two separate next-hops in rpd map to the same next-hop-index in the kernel
Product-Group=evo
On all Junos and Junos Evolved platforms, when a route is getting installed to the forwarding table, associated next-hops also get installed in the forwarding table. As part of this installation process, the Junos kernel allocates the next-hop-index for the next-hop. The rpd sets this next-hop-index in its database when two separate next-hops for instance NH1 and NH2 in the rpd map to the same next-hop NH in the kernel. In such case, NH1 and NH2 next-hops in rpd will have the same next-hop-index leading to the rpd crash.
PR Number
Synopsis
Category: PTX10K Line Card specific interface PRs
1696795
PTX10004/8/16 EVO syslog flooding of "picd: PICD_XCVR_LANE_ALARM: xcvr-x/x/x chan 0 RX LOS alarm set"
Product-Group=evo
PTX10004/8/16 EVO continuous syslog flooding of "picd: PICD_XCVR_LANE_ALARM: xcvr-x/x/x chan 0 RX LOS alarm set"
PR Number
Synopsis
Category: PTX10K specific platform PRs
1693511
CM Major Errors alarm not raised for pre_init_pll_programming failure with faulty PFE on PTX10004/8/16 EVO platforms
Product-Group=evo
On PTX10004/8/16 EVO Scapa, when PFE initialization fails in programming PLL settings at pre_init state, "pll_init_error" is not detected, and the CM Major Errors alarm is not raised.
1696500
PTX10004/8/16 EVO : LC Status LED MIB jnxLEDDescr.3.7.x.0.0 returns undefined 0 value due to read error
Product-Group=evo
On PTX10004/8/16 EVO, Line Card Status LED MIB jnxLEDDescr.3.7.x.0.0 returns undefined 0 value due to read error.
1698919
PTX10004/8/16 EVO : SNMP jnxLEDState mib returns 4(red) value even when BITS LED is unlit/off
Product-Group=evo
On PTX10004/8/16 EVO platforms, SNMP jnxLEDState mib returns 4(red) value even when BITS LED is unlit/off. After fix, it returns 7(off) value correctly for unlit/off BITS LED.
PR Number
Synopsis
Category: PTX10K RE EVO Issues
1681609
LED status on backup RCB never turns on after reboot
Product-Group=evo
On PTX10008 EVO, STS(Status) LED on backup RCB (Routing Engine and Control Board) goes off and never turns on when backup RE (Routing Engine) is rebooted.
21.4R3-S2-EVO - List of Known issues
PR Number
Synopsis
Category: EVO Layer-2 switching for BCM XGS Platforms
1687475
QFX EVO: vlan tag of transit IGMP report will be removed when igmp-snooping is enabled.
Product-Group=evo
On QFX series switch running on EVO, vlan tag of transit IGMP report will be removed when igmp-snooping is enabled.
PR Number
Synopsis
Category: EVO Netstack Juniper Tunnel Driver Module
1693330
iBGP peer or eBGP peer with multihop without local-address defined, does not move into established mode
Product-Group=evo
If the EVO system is operating 21.4R2-EVO, 21.4R2-S1-EVO or 21.4R2-S2-EVO, and the remote BGP side uses one of those versions too, the iBGP session will stay in Active state forever. The same condition does also apply to eBGP multihop session. This is only applicable if the local-address for the iBGP peer is not defined and default-address-selection is used. The BGP socket is getting closed immediately and no tcp sync is sent to the neighbor. Software version 20.4R3-EVO and higher is not exposed
PR Number
Synopsis
Category: AAA, auditd issues
1622936
Idle/inactive netconf user sessions not terminated as per the config set under class
Product-Group=evo
Session idle time was not supported for netconf session in EVO, as part of the current PR extending this feature support. This might result in dangling sessions.
PR Number
Synopsis
Category: Issues related to Junos licensing infrastructure
1694935
PTX EVO : license-check warning reported on backup RE by commit or commit check
Product-Group=evo
On Junos EVO platforms, license-check warning is reported on backup RE by "commit" or "commit check" operation, because license-check is not running in backup RE.
PR Number
Synopsis
Category: Issues related to krt-async routing infrastructure
1656251
Backup rpd core after routing process restart
Product-Group=evo
In some rare case, backup RPD may core during master RPD restart or if some quick route churn occurs. We need to update to new version of software (22.3R1) for the fix.
PR Number
Synopsis
Category: SRX branch platforms
1594014
During reboot, "warning: requires 'idp-sig' license" can be seen on the screen even when the device has valid license
Product-Group=evo
If a device is rebooted manually or reboots for any other reason, The following messages can be seen on the boot up screen even when the device has valid license and proper configuration to use the features like IDP/UTM
Modification History
First publication 2022-12-08
21.4R3-S2-EVO: Software Release Notification for JUNOS Evolved Software