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 running Junos Evolved Software
Alert Description
Junos Software Service Release version 21.4R3-S3-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-S3-EVO is now available.
21.4R3-S3-EVO - List of Fixed issues
PR Number
Synopsis
Category: Border Gateway Protocol
1659441
Routing Process Daemon (rpd) crashes and restarts when a specific timing condition is hit with BGP configuration
Product-Group=evo
On all Junos platforms and all Junos Evolved platforms, Routing Process Daemon (rpd) crashes and restarts when BGP (Border Gateway Protocol) is configured and a specific timing condition is hit for secondary route. This issue might cause a traffic impact.
1679646
The AGGREGATOR attribute will not be set correctly when the independent-domain is configured
Product-Group=evo
On all Junos and Junos OS Evolved platforms, in BGP(Border Gateway Protocol) deployments with the "independent-domain" and aggregate routes configured under routing-instance, the AGGREGATOR attribute encapsulated within the ATTR_SET will not be populated correctly. This can result in unintended behavior or service impact because the BGP neighbors receiving this update may discard it as it is not RFC complaint.
PR Number
Synopsis
Category: PTX10003 Platform related issues
1679346
On Junos Evolved PTX10003, when FPC3 or PFE0 on FPC3 is restarted, the wedge is detected on other FPCs
Product-Group=evo
On Junos Evolved PTX10003-160C and PTX10003-80C, when "FPC3" or "PFE0 on FPC3"(Flexible PIC Concentrator 3/Packet Forwarding Engine 0) is restarted/rebooted wedge is detected on other FPCs, and traffic on the wedge detected FPCs will be dropped.
PR Number
Synopsis
Category: ACX VxLAN Issue
1687842
Traffic failure when pinging from ACX leaf to it's directly attached host
Product-Group=evo
On all ACX Evolved platforms, if there is a no IRB Interfaces attached to the first BD (Bridge Domain) in the list and VLAN member configuration on interface in particular sequence will lead traffic failure from ACX Evolved leaf to it's directly attached host.
1688773
Unable to appropriately failover the incoming traffic with multiple links
Product-Group=evo
All Junos OS Evolved ACX based platforms are unable to appropriately failover the incoming traffic during link failure with multiple links under Aggregated-Ethernet (ae) interface.
PR Number
Synopsis
Category: EVO Class of Services
1692542
The host outbound traffic drop is seen on all Junos OS Evolved platforms due to a race condition between class-of-service host-outbound-traffic and forwarding-class configuration update
Product-Group=evo
Host outbound forwarding-class/queue mapping does not take effect as expected per configurations on all Junos OS Evolved platforms. Host outbound queue is not getting correctly programmed and caused a traffic drop.
PR Number
Synopsis
Category: EVO Netstack FIB Service Daemon
1703955
SYN-ACK and subsequent TCP session packets generated by RE will have incorrect DSCP value
Product-Group=evo
On all Junos OS Evolved platforms, TCP SYN-ACK packet generated by the Routing Engine(RE) in response to a TCP SYN and subsequent packets of the session will have an erroneous Differentiated Services code point (DSCP) value when "set class-of-service host-outbound-traffic dscp-code-point " is configured.
PR Number
Synopsis
Category: Firewall related development
1676850
Commit failure is observed while committing configuration with firewall inet6 filter attached in forwarding-options hierarchy
Product-Group=evo
While committing firewall inet6 filter attached in forwarding-options hierarchy, commit fails with "argument of type 'NoneType' is not iterable" error on all Junos OS Evolved platforms.
PR Number
Synopsis
Category: management ethernet related issues - mgmt-ethd daemon
1648174
PTX10004/8/16 EVO : Unable to clear learned IPV6 address in ipv6 neighbor table on mgmt interface
Product-Group=evo
PTX10004/8/16 EVO : Clear functions for Ipv4 and Ipv6 are missing.
1705245
PTX10004/8/16 EVO : GARP is not sent from new master RE's mgmt interface upon RE switchover
Product-Group=evo
GARP(Gratuitous ARP) is not sent from new master RE's mgmt interface upon RE switchover on PTX10004/8/16 EVO. The ARP table of the network devices located in the same segment is not updated.
1714546
PTX10004/8/16 EVO : MAC address is cleared on ARP table on mgmt interface, but "Address" and "Interface" for cleared MAC remain on ARP table
Product-Group=evo
On PTX10004/8/16 EVO platforms, MAC address is cleared on ARP table on mgmt interface, but "Address" and "Interface" for cleared MAC remain on ARP table.
PR Number
Synopsis
Category: software upgrade infra issues
1680266
Commit failure on Junos OS Evolved platforms post device upgrade
Product-Group=evo
Commit failure can be observed on all Junos OS Evolved platforms after an image upgrade, leading to possible traffic issues and packet drops.
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, and PTX10016, 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: Interface PRs defect & enhancement requests
1695502
The link-local address is not generated for loopback interface
Product-Group=evo
The link-local address is not assigned for the loopback interface after the upgrade or the device reboot on all Junos OS Evolved platforms. The impact depends on how the loopback interface is used in the configuration. It can cause a connectivity issue and traffic impact when it is used for the routing process.
PR Number
Synopsis
Category: EVO L2 Control Plane PRs
1703226
The l2ld process will crash when an IFL is changed to trunk mode and a new VLAN is added
Product-Group=evo
On all Junos Evolved platforms, the Layer 2 address learning daemon (l2ald) process will crash when there is a scaled configuration to commit and a Logical Interface (IFL) mode is changed from access to the trunk and a new Virtual Local Area Network (VLAN) is added to the IFL in a single commit. This issue will impact new MAC learning until the l2ald process recovers.
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: EVO Netstack Socket Intercept and NetIO libraries
1703823
When a syslog is generated and transported to a log collector over an IPv6 connection, processes like eventd might crash.
Product-Group=evo
This rare issue is seen on all Junos Evolved platforms. When a descriptor is erroneously assigned to two or more different processes/libraries, the processes might crash.
PR Number
Synopsis
Category: cmdd, crd issues
1655441
FPC ungracefully restarts when cda-bt process crashes
Product-Group=evo
On all Junos OS Evolved in a very rare scenario, when evo-cda-bt is killed, the agentd and other processes would crash due to an ungraceful FPC (Flexible PIC Concentrator) restart. This issue is not seen in a normal working scenario and is seen only upon ungraceful FPC restarts. The issue is seen when an important application is brought down and due to which FPC also goes down. Since FPC goes down there will be traffic loss.
PR Number
Synopsis
Category: Configd, ffp issues
1698347
The BFD fails to come up when RE filter is configured with apply-path
Product-Group=evo
On Junos OS Evolved platforms, the Bidirectional Forwarding Detection (BFD) protocol will fail to come up. This happens when the Routing Engine (RE) filter is applied with the filter term having source-prefix-list derived from apply-path configured with - "interfaces <*> aggregated-ether-options bfd-liveness-detection neighbor". The issue occured in the commit handling after correcting the apply-path string.
PR Number
Synopsis
Category: EVPN Layer-2 Forwarding
1662954
In EVPN-MPLS Mutihoming scenario DF election will get stuck in the Preference based state
Product-Group=evo
On all Junos and Junos Evolved platforms supporting preference-based DF (Designated Forwarder) election in EVPN-MPLS Multihoming scenario, the DF election will be stuck in the Preference based state if there will be a change in the df-election on the fly.
1709007
In EVPN scenario, proxy-arp on IRB interfaces do not work as expected
Product-Group=evo
On all Junos and Junos Evolved platforms with EVPN(Ethernet Virtual Private Network) scenario, IRB(Integrated Routing and Bridging) interfaces send proxy-arp for IPs that are already present in the network, which triggers a duplicate IP error on the end device/host.
PR Number
Synopsis
Category: Control plane EVPN multicast
1670435
EVPN multicast traffic may get impacted because of routes getting stuck in the kernel routing table (krt) queue
Product-Group=evo
On all Junos and Junos Evolved platforms with Ethernet Virtual Private Network(EVPN) enabled, in the presence of certain triggers like rpd restart, rollback of configuration etc., EVPN multicast routes might get stuck in the kernel routing table (krt) queue due to which the corresponding routes in the forwarding table may point to 'fictitious' next hops, resulting in traffic disruption.
PR Number
Synopsis
Category: ISIS routing protocol
1696598
Wrong SRTE Secondary path weight makes the secondary path active in forwarding table
Product-Group=evo
On all Junos and Junos Evolved platforms, SRTE (Segment Routing Traffic Engineering) Secondary LSP (Label Switched Path) should be only on standby in the forwarding table however it is also active and forwarding traffic due to the wrong metric calculation.
PR Number
Synopsis
Category: lacp protocol
1686546
The ethernet switching tables are not in sync between two PEs
Product-Group=evo
MAC entries are not synced between the two PE (Provider Edge) devices as seen from the output of the 'show ethernet-switching table'. This is a rare timing issue which happens after GRES (Graceful Routing Engine Switchover) where the AE (Aggregate Ethernet) interface flaps leading to traffic loss.
PR Number
Synopsis
Category: Label Distribution Protocol
1666506
LDP session stuck in non-existent state when router has multiple addresses configured on loopback interface
Product-Group=evo
When statically configured LDP neighbour and sessions transport address exists between two routers that is having multiple loopback addresses may cause LDP stuck in non-existent state. Deactivating and activating the LDP neighbour configuration can cause LDP session to remain stuck in the non-existent state.
PR Number
Synopsis
Category: Issues related to Junos licensing infrastructure
1658869
The license might get out of sync between master and backup RE
Product-Group=evo
On all Junos OS Evolved platforms, the license might get out of sync between master and backup RE after the addition/deletion of licenses.
1694935
license-check warning reported on backup RE by commit or commit check
Product-Group=evo
On Junos Evolved 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: MPC11 ULC interface software related issues.
1698135
XQSS_CMERROR_DSTAT_INT_REG_DROP0_QDEPTH_UNDRN alarm is seen on MX2K platforms with MPC11E line cards upon aggregate interface down/flap event
Product-Group=evo
On MX2010 or MX2020 platforms with MPC11E line cards, if a member link of an aggregate interface goes down or flaps, it might trigger "XQSS_CMERROR_DSTAT_INT_REG_DROP0_QDEPTH_UNDRN" alarm and disable-pfe action is executed. The affected PFE (Packet Forwarding Engine) will be disabled and no traffic will pass through it.
PR Number
Synopsis
Category: Multiprotocol Label Switching
1694648
The rpd crash will be observed during the MPLS label block allocation
Product-Group=evo
On all Junos and Junos Evolved platforms in the Multiprotocol Label Switching (MPLS) scenario, the rpd crash will happen in rare conditions during MPLS label block allocation.
PR Number
Synopsis
Category: OSPF routing protocol
1682506
Traffic loss is seen when the router in helper mode deletes the route for the router undergoing graceful restart
Product-Group=evo
On all Junos OS and Junos OS Evolved devices, traffic loss is seen when the router in helper mode to support an OSPF graceful restart deletes the route for the router undergoing graceful restart. The device deletes the route due to the topology change.
1705975
OSPF routes are not getting installed after the interface is flapped
Product-Group=evo
On all Junos and Junos Evolved platforms, the OSPF (Open Shortest Path First) routes are not getting installed when the interface is flapped multiple times. A deadlock is created when the OSPF routers wait for an LSA (Link State Advertisement) with a P2P (Point-to-Point) link to be advertised from its neighbouring router to add it to its router LSA and at the same time the neighbouring router also waits for an LSA with a P2P link to be advertised to add it to its router LSA. Both the OSPF routers advertise their router LSA without a P2P link and as a result, routes are not getting installed.
PR Number
Synopsis
Category: RPD infrastructure issues related to NSR, GRES, switchover,
1701146
The rpd crash will be observed when any commit is performed
Product-Group=evo
On all Junos and Evolved platforms with RSVP auto-mesh dynamic tunnel configuration, whenever a commit is done the rpd (Routing Process Daemon) crash will be seen. This happens due to null pointer access in the memory.
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.
PR Number
Synopsis
Category: Issue related to mcnh routing infrastructure within RPD
1658425
The next-hop does not be updated and errors observed when aggregated interface goes down
Product-Group=evo
On all Junos OS Evolved platforms, dependency errors after interface flap are observed due to uncleared multicast composite next hop from RPD(routing protocol process daemon).
1708299
The rpd process crash is seen with scaled multicast next-hops
Product-Group=evo
On all Junos OS Evolved platforms, due to timing issues in scaled setup with multicast next-hops, the rpd process might crash when the corresponding multicast next-hops Aggregated Ethernet (AE) interface flaps continuously. This will result in traffic loss.
PR Number
Synopsis
Category: RPD Next-hop issues including indirect, CNH, and MCNH
1652387
The rpd process might crash with back-to-back rpd restarts
Product-Group=evo
On all Junos and Junos Evolved platforms, the rpd process might crash if the rpd process restarts back-to-back before the rpd process comes up.
PR Number
Synopsis
Category: Shard routing infrastructure within RPD
1699557
The rpd crash is observed when rib-sharding configured
Product-Group=evo
On all Junos and Junos OS Evolved platforms, rpd crash observed while configuring BGP rib-sharding as route re-resolve happens due to another best match route. Traffic drop can be seen during rpd process recovery.
PR Number
Synopsis
Category: Resource Reservation Protocol
1621771
RSVP refcount leak and the rpd crash observed post LSP churn
Product-Group=evo
On all Junos and Junos Evolved platforms, rpd crash was observed due to RSVP refcount leak.
1661526
The rpd crash would be observed in a RSVP scenario
Product-Group=evo
On all Junos and Junos Evolved platforms with RSVP enabled, the rpd (routing protocol daemon) crash will be observed while updating the RSVP path information with a new metric. When this happens, the core files are generated and some traffic loss will be seen.
PR Number
Synopsis
Category: RPM and TWAMP
1703104
The TWAMP test session packets are dropped when the payload is less than 52 bytes
Product-Group=evo
On all Junos OS Evolved platform and Junos platform is using MPC10E/MPC11E/JNP10K-LC9600 linecards, If a Two-Way Active Management Protocol (TWAMP) client from a different vendor is transmitting a packet that is smaller than the 52 bytes then (the minimum allowed by RFC5357 is 41), the TWAMP reflector will be unable to function. Any packets from the TWAMP client will therefore be ignored. Similar to this, juniper boxes will also block any answers that are less than 52 bytes long, causing TWAMP test sessions to report a packet loss.
PR Number
Synopsis
Category: PTX10K platform specific fabric PRs
1669435
The process fabspoked-pfe crash might be observed while executing CLI commands for fabric statistics
Product-Group=evo
On all Junos OS Evolved platforms, the process fabspoked-pfe crash might be observed while executing CLI commands for fabric statistics. Executing CLI commands specific to the status related to FBC and SIBs will hit this issue.
PR Number
Synopsis
Category: PTX10K specific platform PRs
1669323
PTX10K : PSM fault state not recoverable
Product-Group=evo
On PTX10K platforms, Fault state is latched on PSM although all input and output is OK with no chassis alarm.
1697503
PTX10004/8/16 EVO : LED on "Status Panel" is Unlit OFF
Product-Group=evo
On PTX10004/8/16 EVO platforms, Status Panel LED(POWER SUPPLIES, FANS, SIBS, LINE CARDS, CONTROL BOARDS) might be Unlit OFF after system boot.
1698209
PTX10008 EVO : FTC FPGA minimum supported firmware version mismatch alarm gets generated upon re-seating FTC
Product-Group=evo
On PTX10008 EVO, FTC (Fan Tray Controller) FPGA minimum supported firmware version mismatch alarm gets generated upon re-seating FTC because the current firmware version becomes null value after re-insertion.
1701983
PTX10004/8/16 EVO : SNMP mib jnxOperatingState not working for runningAtFullSpeed
Product-Group=evo
SNMP mib jnxOperatingState does not work for runningAtFullSpeed on PTX10004/8/16 EVO platforms
1706601
PTX10004/8/16 EVO : When offlined FPC is removed from chassis, "show chassis craft-interface" CLI shows "Fail" for removed FPC
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
1708892
PTX10008 EVO : When PSM (JNP10K-PWR-AC2) is switched off and "OK LED" is unlit off, but jnxLEDState mib shows green(2)
Product-Group=evo
On PTX10008 EVO, when PSM (JNP10K-PWR-AC2) is switched off and "OK LED" is unlit off, but jnxLEDState mib shows green(2).
1713462
PTX10004/8/16 EVO : SNMP trap jnxFruOnline is raised when JNP10K-PWR-DC2 PSM(single power input) is powered off by button press
Product-Group=evo
On PTX10004/8/16 EVO platforms, SNMP trap jnxFruOnline is raised when JNP10K-PWR-DC2 PSM(single power input) is powered off by button press
PR Number
Synopsis
Category: PTX10K Timing/Sync-E issues tracking
1695952
The line cards will remain in PRESENT state post reboot
Product-Group=evo
On Junos Evolved PTX10008 and PTX10016, due to the timing of the boot-up events, a few line cards will fail to come online. The Flexible PIC Concentrator (FPC) remains in the PRESENT state as if the FPC is inserted after the system boot-up.
PR Number
Synopsis
Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1708321
MX960 :: CST:RE goes to amnesiac state, when rebooting the DUT -mgd: error: translation script failure
Product-Group=evo
When a toggle attribute with variable is committed under dynamic-profiles hierarchy, upon reboot system will go to amnesiac mode
PR Number
Synopsis
Category: Issues related to Logging/Tracing, errmsg, eventd infrastruc
1689661
source-address on syslog at custom routing-instance not applied right after rebooting
Product-Group=evo
syslog may not be sent out via configured source address when target host exists on a custom routing-instance
PR Number
Synopsis
Category: Virtual Router Redundancy Protocol
1680178
VRRP master-master condition might occur when there are more than two devices in the VRRP group
Product-Group=evo
When more than two devices are part of the VRRP group and a lower priority master sends a keepalive as master, low priority backup may transition to master state and get stuck.
1697394
VRRP Master session on AE ifl having child links on Satellite Device stops transmission post GRES
Product-Group=evo
On Junos Fusion Aggregation Device platforms, when the VRRP (Virtual Router Redundancy Protocol) interface is configured on IRB (Integrated Routing and Bridging) with underlying L2 interface on Satellite Device post GRES (graceful Routing Engine switchover) VRRP Master stops transmission of VRRP PDU (Protocol Data Unit) resulting in VRRP Master/Master state.
PR Number
Synopsis
Category: EVO Services Sflow PRs for defect & enhancement requests
1696413
The VLAN-id mapping is incorrect in sflow scenario on PTX Junos OS Evolved platforms
Product-Group=evo
On PTX Junos OS Evolved platforms, the VLAN-id (Virtual Local Area Network) and priority values are not reset and are getting used for the next packet that was processed by sflow (Sampled Flow) process.
21.4R3-S3-EVO - List of Known issues
PR Number
Synopsis
Category: Border Gateway Protocol
1689904
BGP 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.3R3-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:22.1R3-S2 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R1 junos:23.2R1
PR Number
Synopsis
Category: PFE L2 forwarding features on BT based platforms
1672631
The traffic loop would be observed when ESI is configured on IFD
Product-Group=evo
On PTX Junos Evolved platforms when Ethernet Segment Identifier (ESI) for multihomed Ethernet Virtual Private Network-Multiprotocol Label Switching (EVPN-MPLS) scenario is configured on the physical interface (IFD), and multiple logical interfaces (IFLs) within the same IFD are associated with Bridge Domains/VLANs within the same MAC-VRF routing instance for service-type VLAN-Aware, then the traffic loop will be observed between Multihomed Customer Edge and Provider Edge devices for the Broadcast, Unknown unicast, and Multicast (BUM) traffic.
Resolved In:
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.3R3 junos:22.4R2 junos:23.1R1
PR Number
Synopsis
Category: Gnats category for dynamic rendering infrastructure
1695523
The routing protocol daemon may core dump when streaming telemetry data
Product-Group=evo
There are edge cases where the routing protocol daemon may core dump when streaming the telemetry data for paths under the protocol container. For example: "/network-instances/network-instance[name='DEFAULT']/protocols/protocol/isis"
Resolved In:
evo:22.2R2-S1-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.3R3-EVO evo:22.3X80-D30-EVO evo:22.3X80-D31-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:21.2R3-S4 junos:21.2X32-D20 junos:21.4R3-S3 junos:23.1R1 junos:23.2R1
1706708
evo-aftmand-zx not responding, ping, arp not working after unsubscribing some telemetry sensors.
Product-Group=evo
After unsubscribing certain telemetry sensors, evo-aftmand-zx becomes unresponsive due to a deadlock problem.
Resolved In:
evo:22.2R3-EVO evo:22.3R2-EVO evo:22.3X80-D32-EVO evo:22.4R2-EVO evo:23.1R2-EVO evo:23.2R1-EVO junos:22.1R3-S2 junos:22.3R3 junos:23.2R1
1714120
PICD core is seen on LC120x line cards after starting the Jvision decoder.
Product-Group=evo
PICD and EVOAFTMAND will crash just by unsubscribing /component or /interface sensor which uses AFT telemetry infra.
Resolved In:
evo:22.2R3-EVO evo:22.3R3-EVO evo:22.3X50-EVO evo:22.3X80-D32-EVO evo:22.3X80-D33-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO junos:22.1R3-S2 junos:22.4R3 junos:23.1R1 junos:23.2R1
PR Number
Synopsis
Category: EVO cfmd RE related PRs
1695518
[Error] CTRL:CFM:: PpmCtrlProtoCfm:: getSessionKey: Unknown Cfm transmit session type params0x0 ( ) can be seen when router is rebooted with CFM config
Product-Group=evo
When CFM configurations are present on the router, and the router is rebooted, below error logs may be seen. [Error] CTRL:CFM:: PpmCtrlProtoCfm:: getSessionKey: Unknown Cfm transmit session type params0x0 ( ) There is no feature impact when this error log is seen. CFM sessions will be unaffected. The error log is not emitted consistently, and may be seen only sometimes.
Resolved In:
evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO junos:22.4R3 junos:23.1R2 junos:23.2R1
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:
junos:23.2R1
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.
Resolved In:
evo:20.4R3-S5-EVO evo:22.1R1-EVO junos:20.4R3-S5 junos:20.4R3-S6 junos:21.4R3-S3 junos:22.1R1
PR Number
Synopsis
Category: mgd, ddl, odl infra issues
1674890
Seen configd-streamer core in 22.3R1EVO evf_walk_and_diff cfg_print_reorder
Product-Group=evo
Configd-streamer cores during commit of wild-carded groups related config. The core is only seen with the wild-carded config which is used in the reported fusion test case.
Resolved In:
evo:23.2R1-EVO
PR Number
Synopsis
Category: EVPN control plane issues
1646722
IFLs aren't created post Graceful RE switchover on guardian platform with EVPN services
Product-Group=evo
On performing Graceful RE swithchover on guardian platform with EVPN services, some IFLs are missing. IFLs come up post reboot.
Resolved In:
evo:22.4R1-EVO
1673157
The 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.
Resolved In:
evo:22.4R1-EVO junos:22.4R1
PR Number
Synopsis
Category: Port-based link layer security services and protocols that a
1693301
MACSec session will not come up on the new fallback key during the primary key transition
Product-Group=evo
On all Junos and Evolved platforms, during the primary key transition on the MACSec session, when a new fallback key is updated on the MACSec peers the session will not come up due to the primary key remaining live on the same interface. When this happens, there will be a traffic drop on the MACSec interface. This is a rare issue and only occurs when a certain sequence of steps is performed.
Resolved In:
evo:22.2R3-EVO junos:22.2R3
PR Number
Synopsis
Category: Resource Reservation Protocol
1713392
PathErr with RoutingProblem error code generated unexpectedly during dual failure local repair
Product-Group=evo
When an LSR acts as a Point of Local Repair (PLR) as well as a Merge Point (MP) for an LSP during a double failure scenario, the LSR incorrectly originates one or two PathErr messages with RoutingProblem (code=24/2) instead of originating PathErr with NotifyError (code/subcode=25/3). This will not cause any service impact if the ingress LER would not react adversely to RoutingProblem error (code=24/2).
Resolved In:
evo:22.3R3-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:22.1R3-S2 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R2 junos:23.2R1
PR Number
Synopsis
Category: PTX10K specific platform PRs
1682659
FPC going to fault state with Major alarm - Power Failure on upgrading
Product-Group=evo
FPC going to fault state with Major alarm - Power Failure on upgrading
Resolved In:
evo:22.3R2-S1-EVO evo:22.3R3-EVO evo:22.3X50-EVO evo:22.4R1-EVO evo:22.4R2-EVO evo:23.1R1-EVO junos:22.3R3 junos:22.4R2 junos:23.1R1
PR Number
Synopsis
Category: Ephemeral Database
1610713
The rpd crash will be observed post ephemeral database configuration commit sync
Product-Group=evo
On Junos and Junos Evolved platforms, post ephemeral database configuration commit sync leads to a state mismatch between master and backup.
Resolved In:
evo:21.2R3-S2-EVO evo:22.3R1-EVO evo:22.4R1-EVO junos:21.2R3-S1 junos:21.2R3-S2 junos:21.2X32-D10 junos:21.2X32-D20 junos:21.4R3-S2 junos:22.3R1 junos:22.4R1
PR Number
Synopsis
Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1679413
Configuration filtering doesn't work when the logical system is present
Product-Group=evo
On SRX platforms, configuration filtering doesn't work when the logical system is present.
Resolved In:
evo:22.2R2-S2-EVO evo:22.2R3-EVO evo:22.3R1-S2-EVO evo:22.3R2-EVO evo:22.3R3-EVO evo:22.4R2-EVO junos:21.4R3-S3 junos:22.1R3-S1 junos:22.2R2-S2 junos:22.2R3 junos:22.3R1-S2 junos:22.3R2 junos:22.3R3 junos:22.4R1-S1 junos:22.4R2 junos:23.1R1
1699245
The mgd process might crash during commit synchronize
Product-Group=evo
On all Junos and Junos Evolved platforms with dual Routing Engines, during commit script synchronize, the backup Routing Engine mgd get process crashes once the memory leak reaches 65K. When this happens, commit configurations from the primary Routing Engine fail.
Resolved In:
evo:22.2R2-S2-EVO evo:22.2R3-EVO evo:22.3R1-S2-EVO evo:22.3R2-EVO evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:20.3X75-D35 junos:20.3X75-D50 junos:21.1R3-S5 junos:21.2R3-S4 junos:21.2X32-D20 junos:21.3R3-S4 junos:21.4R3-S3 junos:22.1R3-S1 junos:22.2R2-S2 junos:22.2R3 junos:22.3R1-S2 junos:22.3R2 junos:22.3R3 junos:22.4R1-S1 junos:22.4R2 junos:23.1R1 junos:23.2R1
Modification History
First publication 2023-03-17
21.4R3-S3-EVO: Software Release Notification for JUNOS Evolved Software