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 22.3R3-S2-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 22.3R3-S2-EVO is now available.

22.3R3-S2-EVO - List of Fixed issues 

PR NumberSynopsisCategory: OAM support on ACX
1746304Node-segment reachability will be lost in Multitopology based IS-IS
Product-Group=evo		On all Junos and Junos OS Evolved platforms, in a Segment Routing MPLS(Multi Protocol Label Switching) environment using IS-IS and an alternate IPv6 unicast topology is configured in addition to the normal IPv4 unicast topology, the node-segment reachability might be lost resulting in traffic loss. This will only happen when the 'family inet6' is configured on the interface without configuring the IPv6 address.
PR NumberSynopsisCategory: "agentd" software daemon
1732763The xmlproxyd crash might be observed when there are multiple collectors
Product-Group=evo		The Xmlproxyd crash could be seen if there are multiple collectors subscribing for Xmlproxyd sensors and some or all of the collectors are flapping frequently at the rate of 90 seconds or so.The occurrence of this issue is rare.The telemetry streaming of Xmlproxyd sensors will be absent during the time Xmlproxyd crashes and restarts on its own. This time could be within 30 seconds or so.Once Xmlproxyd comes up, the telemetry streaming of Xmlproxyd sensors will be resumed automatically.
PR NumberSynopsisCategory: BBE network stack related issues
1729913DHCP 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 NumberSynopsisCategory: Border Gateway Protocol
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.
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: Track PRs in BGP programmability area using JET APIs.
1699356The rpd core will be seen when the route monitor stream times out
Product-Group=evo		On all Junos and Junos Evolved platforms supporting prpd (programmable routing protocol process), when the route monitor stream times out because of any reason, rpd (routing protocol daemon) core will be seen.
PR NumberSynopsisCategory: Track PRs in BGP BMP area & is part of BGP inside RPD.
1764911High RPD CPU due to BMP station config
Product-Group=evo		RPD runs at high CPU when configure BGP BMP configurtion.
PR NumberSynopsisCategory: EVO L3 routing for BCM XGS Platforms
1771209PFE crash seen on Junos OS Evolved platforms due to upstream interface change
Product-Group=evo		On all Junos OS Evolved platforms, PFE (Packet Forwarding Engine) process crashes when the upstream interface for a multicast route changes from L3 (Layer 3) interface to another L3 interface or from L3 to an IRB (Integrated Routing and Bridging) interface. This can happen when the RPF (Reverse Path Forwarding) to the source changed due to an interface going down in the upstream path. A complete loss of traffic is observed till the PFE process restarts post the crash.
PR NumberSynopsisCategory: PFE L2 forwarding features on BT based platforms
1716767Protocol hello and keep-alive messages will not work on the mac accounting interface
Product-Group=evo		On PTX10003, PTX10008, PTX10016 and PTX10001-36MR Junos OS Evolved Platforms , when mac accounting is enabled under any interface and that same interface is also used to exchange hello/keep-alive protocol messages, then those multicast-based hello and keep-alive messages will not function on the mac accounting interface and any dynamic routing protocol which uses multicast for exchanging hello and keep-alive packets got affected by this PR when mac accounting is enabled in the communication path.
1745528Untagged control traffic on L3 interface will be dropped on Junos OS Evolved based PTX platforms
Product-Group=evo		On all Junos OS Evolved based PTX platforms with physical interface/LAG (Link Aggregation Group) interface in L3 mode, the untagged control traffic on L3 interface gets dropped if lport value of L3 interface matches with lport value of L2 aggregated ethernet (AE) interface in trunk mode.
PR NumberSynopsisCategory: PMB (AMD) PR for 1G/10G LC
1722823The FPC crash is observed on Junos MX10008 platform when connected to non-Juniper SFP
Product-Group=evo		On Junos MX10008 platform, the FPC (Flexible PIC Concentrator) crash will be observed when connected to non-Juniper SFP (Small Form-factor Pluggable) and it will lead to traffic loss.
PR NumberSynopsisCategory: DNX platform MPLS FRR features
1768729Unknown unicast IPv4 Traffic received with UDP destination port 8503 will be flooded back to Source PE
Product-Group=evo		On the Junos Evolved ACX7K platform, the split horizon rule is broken when an IPv4 packet with destination UDP port 8503 is received on the system over the Ethernet VPN (EVPN) /Layer-2 network. This will result in the traffic being sent /flooded to the source PE router. The below filter can be seen incrementing during the issue. pfe> show evo-pfemand filter counters filter-name __BfdLspMplsSelfPingTrap_unit0__ Counter-Name Packets BytesBfdLspMplsSelfPingTrap_unit0-rule 125016 99578126
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: Issues related to EVO dependency layer including object graphs, incompletes, anomalies and nkdb
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: software upgrade infra issues
1755616automatic software synchronization mechanism doesn't function as expected
Product-Group=evo		On all Junos Evolved platforms, the auto-sw-sync mechanism doesn't function as expected. When Routing Engine is out of cluster and attempts to rejoin the cluster, synchronization fails to occur. Consequently, the current version from the master does not sync to the backup Routing Engine, resulting in new Routing Engine continuous reboot that denies access to break the cycle.
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.
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.
1749745The MAC learning process is impacted and l2ald gets stuck when scaled L2 services and telemetry are configured
Product-Group=evo		On all Junos Evolved platforms having scaled L2 (Layer 2) services and telemetry is enabled, under a rare scenario, it is seen that the l2 daemon is getting stuck due to which the show commands served by l2ald are not working and MAC (Media Access Control) addresses are not getting learned which leads to traffic drop.
PR NumberSynopsisCategory: EVO Netstack Socket Intercept and NetIO libraries
1766212DNS resolution is not working for default instance when name server is reachable through mgmt_junos VRF
Product-Group=evo		DNS resolution is not working for default instance when name server is reachable through mgmt_junos VRF
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: EVPN control plane issues
1722102L2alm sends IPv6 NS with IRB link local address even though target IP is global address
Product-Group=evo		On Junos and Junos Evolved platforms configured with EVPN-VXLAN, EVPN-MPLS, it is observed that L2alm sends IPv6 NS(Neighbor Solicitation) with link local address even through target IP is global address.
1761852The rpd can crash on all Junos platforms in Seamless DCI scenario
Product-Group=evo		On all Junos platforms, a crash can be seen for the rpd (routing process daemon) in EVPN (Ethernet Virtual Private Network) seamless DCI (Data Center Interconnect) scenario when the 'evpn interconnect' and the BD (Bridge Domain) configuration are deleted in the same commit. There will be traffic loss when the rpd crashes but the system will self-recover.
PR NumberSynopsisCategory: EVPN Layer-2 Forwarding
1751386Re-ARP is not sent before MAC entry expires in EVPN environment on Junos MX platforms
Product-Group=evo		On Junos MX240, MX304, MX480, MX960, MX2010, MX2020, MX10004, MX10008 platforms with MPC10/MPC11/LC9600 line cards, Re-Address Resolution Protocol (Re-ARP) is not sent before Media Access Control (MAC) entry expires. It causes a service impact in Ethernet Virtual Private Network- Virtual eXtensible Local-Area Network (EVPN-VxLAN) scenario with IRB (Integrated Routing and Bridging) and BD (Bridge Domain) configured.
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: Libjtask for RPD tasks, scheduler, timers, memory, and slip
1692738On all Junos lsys systems RPD process crashes due to JET client invoking rpc handled by RPD daemon
Product-Group=evo		RPD process crash might be seen when the gRPC stack expects a 8 byte aligned memory but gets a 4 byte aligned memory instead.
PR NumberSynopsisCategory: ISIS routing protocol
1753003The rpd crashes on all Junos and Junos Evolved platforms with IS-IS, segment routing and flex algo configured
Product-Group=evo		On all Junos and Junos Evolved platforms, with IS-IS, segment routing and flex algorithm enabled, when the route from ribgroup is deleted due to interface flap, it leads to crash of the infra module as route entry table does not match with the rtbit table (which is passed from IS-IS).
PR NumberSynopsisCategory: Layer2 forwarding on EX/NTF/PTX/QFX
1707878Mac entry not ageout in RTG in EX4600-VC after VCP port reconnect
Product-Group=evo		EX4600 with Redundant Trunk Group (RTG) configured, after VCP port between members of EX4600 disconnect and connect again. Mac address entry created in RTG cannot ageout.
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
1759618License-service crash is seen on Junos OS Evolved platforms
Product-Group=evo		On Junos OS Evolved platforms, when license with unknown feature ID/platform reserved feature ID is added via configuration set system license keys key and then if License-service is restarted or system is rebooted or software upgrade is done then license service crashes and crash files are seen. This is a non service impacting issue.
PR NumberSynopsisCategory: Multicast Routing
1769782The rpd crash is observed when mvpn-mode is configured as "rpt-spt" and multicast snooping is enabled
Product-Group=evo		On Junos OS Evolved platforms, when mvpn-mode (Multicast Virtual Private Network) is configured as "rpt-spt" (Rendezvous-point tree - Shortest-path tree) and multicast snooping is enabled, the rpd crash is observed. The issue happens when the routing process tries to obtain the source address on processing the multicast <*, g> route.
1777774The rpd core is observed when MVPN PE receives PIM join messages from the remote peers
Product-Group=evo		On all Junos Evolved platforms, when MVPN configured device receives PIM join or IGMP report from the remote peer installs route in next-hop and not in multicast composite next-hop, causing rpd to core.
PR NumberSynopsisCategory: Multicast for L3VPNs
1709175MVPN sender site not working with IR tunnels configured
Product-Group=evo		On all Junos and Junos Evolved platforms, MVPN (Multicast Virtual Private Network) sender site having IR (Ingress Replication) tunnel configured, due to software issue, type 1 route is not being sent and egress node is observed to not accept traffic from unknown neighbor.
PR NumberSynopsisCategory: qfx-sw-mclag
1742613Race condition where FLOOD ROUTE DEL event can cause l2ald crash.
Product-Group=evo		When system comes up with BULK L2 config, a subsequent CONFIG delete in a way that L2ALD is still not finished processing the config create, could lead to a race condition where FLOOD ROUTE DEL event can cause l2ald crash.
PR NumberSynopsisCategory: QFX EVPN / VxLAN
1727119The 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 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: RPD API infrastructure
1710274Next Hop counts are not as expected
Product-Group=evo		Next Hop counts are not as expected
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
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: Stout card (MPC7) fabric issues
1764457Traffic drop observed at the source pfe when the destination line card has fabric link error
Product-Group=evo		On all Junos and Junos Evolved platforms, when data traffic is sourced from line cards like MPC1-9 and there is a link error at the destination PFE (Packet Forwarding Engine) end, traffic is dropped at the source PFE end.
PR NumberSynopsisCategory: Stout cards (MPC8, MPC9) fabric issues
1747893MX2k Platform: frequent fabric plane Check state reported due to remote destination timeouts
Product-Group=evo		Upon some crc errors on fabric links, fabric destination timeouts are reported more frequent. Once there is a fabric request timeout, the system will attempt auto recovery. Since the periodic detection logic ran twice for 500msec period and 60msec period, it reported fabric destination timeout too aggressive. The additional 60msec period is targeted to detect a condition if user removed SFB board ungracefully. This exposure is specific to MX2K Platforms only
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.
 
 

22.3R3-S2-EVO - List of Known issues 

PR NumberSynopsisCategory: ACX L3 IPv4, IPv6 support
1751135ARP and ND packets are not getting resolved in vlan-based EVPN service on Junos OS Evolved ACX platforms
Product-Group=evo		On Junos OS Evolved ACX platforms configured with EVPN-MPLS (Ethernet VPN-Multiprotocol Label Switching) vlan-based EVPN service or EVPN-VXLAN(Ethernet VPN-Virtual Extensible LAN), device is responding to ARP/ND (Address Resolution Protocol/Neighbor Discovery) without any vlan-id tag. Due to this, the ARP/ND response packet will get dropped in LAN network and the local host will not be able to resolve the ARP.

Resolved In: evo:22.2R3-S3-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-S2-EVO evo:23.2R2-EVO junos:23.1R2 junos:23.2R2
PR NumberSynopsisCategory: EVO interface software
1716518Interface on PTX1001-36MR router remains down with QSFP-100GBASE-SR4 optics
Product-Group=evo		On Junos Evolved PTX10001-36MR platform, when the third party QSFP-100GBASE-SR4 is being used, rewriting the value of rx-out-amplitude (receiver side signal integrity parameter) with default value(0X3), causes the link to remain down.

Resolved In: evo:20.4R3-S7-EVO evo:21.4R3-S4-EVO evo:22.2R3-S3-EVO evo:22.3R3-EVO evo:22.3X50-EVO evo:22.3X80-D36-EVO evo:22.3X80-D37-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO
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.

Resolved In: evo:20.4R3-S10-EVO evo:21.4R3-S6-EVO evo:22.1R3-S5-EVO evo:22.4R3-EVO junos:20.3X75-D44 junos:20.4R3-S10 junos:21.4R3-S6 junos:22.1R3-S5 junos:22.2R3-S3 junos:22.3R3-S2 junos:22.4R3 junos:23.2R1 junos:23.4R2
PR NumberSynopsisCategory: EVO Layer-2 switching for BCM XGS Platforms
1741712Traffic 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.2R3-S3-EVO 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 NumberSynopsisCategory: EVO L3 routing for BCM XGS Platforms
1715871Traffic gets dropped on Junos Evolved QFX platforms when app routing is restarted
Product-Group=evo		On Junos Evolved QFX platforms, when the app (application) routing is restarted from the CLI and having L3VPN (Layer 3 Virtual Private Network) over MPLS (Multiprotocol Label Switching) configured, traffic is observed to get dropped.

Resolved In: evo:22.2R3-S3-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO
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.

Resolved In: evo:21.4R3-S6-EVO evo:22.2R3-S3-EVO evo:22.2R3-S4-EVO evo:22.3R3-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO
PR NumberSynopsisCategory: VPWS, L2 CKT, EVPN-VPWS
1775809In the scaled L2circuit configured with L2circuit redundancy configuration traffic drops may be observed
Product-Group=evo		On Junos OS Evolved ACX platforms, in the scaled L2circuit (Layer 2 Circuit) configured (200+ L2circuits) with L2circuit redundancy configuration traffic drops may be observed on a few instances only when deactivating/activating IGP (Interior Gateway Protocol) protocol or restart routing.

Resolved In: evo:22.4R3-EVO evo:22.4R3-S1-EVO evo:23.2R2-EVO evo:23.4R1-S1-EVO evo:23.4R2-EVO evo:24.1R1-EVO
PR NumberSynopsisCategory: software upgrade infra issues
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.

Resolved In: evo:21.4R3-S6-EVO evo:22.1R3-S5-EVO evo:22.4R3-S1-EVO evo:23.2R2-EVO evo:23.4R1-S1-EVO evo:23.4R2-EVO evo:24.1R1-EVO junos:23.4R2
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.

Resolved In: evo:21.2R3-S7-EVO evo:21.4R3-S6-EVO evo:22.4R3-EVO evo:23.2R1-S1-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.3R2-EVO evo:23.4R1-EVO junos:20.4R3-S10 junos:21.2X32-D20 junos:21.4R3-S6 junos:22.1R3-S5 junos:22.2R3-S3 junos:22.3R3-S2 junos:22.4R3 junos:23.2R1 junos:23.2R1-S1 junos:23.2R2 junos:23.3R1 junos:23.3R2 junos:23.4R1
PR NumberSynopsisCategory: SNMP, mib2d issues
175950622.2R2-S2.6-EVO : Incorrect IF-MIB:: ifLastChange Value Polled
Product-Group=evo		Fix - ifLastChange - This takes the system uptime value (show system uptime command output) meaning it takes the time when the interface came up and became operational. Earlier due to the bug - Initially during ifLastChange polling, it was incorrectly reading system up time. Now after fix it will read correct sysUpTime (show system uptime) whenever there is a change in the interface state. This issue was corrected post code changes and now after interface comes up it will populate proper values for ifLastChange.

Resolved In: evo:22.2R3-S3-EVO evo:22.2X100-EVO evo:22.3X80-D36-EVO evo:22.3X80-D42-EVO evo:22.4R3-EVO evo:23.2R2-EVO evo:23.4R2-EVO
PR NumberSynopsisCategory: SW PRs for MPC10E PMB
1731258MPC10 and MPC11 line cards experiencing unexpected reboots
Product-Group=evo		Line cards such as MPC10 and MPC11 experience unexpected reboots because of CPU C-states which are enabled by default thus impacting the customer production traffic.

Resolved In: evo:24.1R1-EVO junos:22.4R3 junos:22.4R3-S1
PR NumberSynopsisCategory: For multicast snooping on MX
1710565In a scaled setup mcsnoopd is taking high CPU causing traffic drop
Product-Group=evo		On all Junos and Junos Evolved platforms, whenever a commit is done, that involves mcsnoopd daemon config parsing such as (VLAN creation/deletion, interface add/delete to VLAN, interface enable/disable, IGMP (Internet Group Management Protocol) snooping/MLD (Multicast Listener Discovery) snooping related config commands) mcsnoopd will consume CPU. In less scaled setup (few IGMP snooping enabled VLANs and few hundred IGMP snooping memberships), the CPU time taken is less. In a more scaled setup (many IGMP snooping-enabled VLANs and a few thousand IGMP snooping memberships), the CPU may reach >90%. Since mcsnoopd is taking high CPU, it may affect other daemons like rpd. It may affect all the protocols if the CPU is not available to the protocols/daemons. This can impact route entries expiring and cause traffic drop.

Resolved In: evo:24.1R1-EVO junos:22.2R3-S3
PR NumberSynopsisCategory: Periodic Packet Management Daemon
1490918The ppmd process generates a core file after MS-MPC restarts.
Product-Group=evo		On MX Series routers, the ppmd process might crash after the FPC restarts.

Resolved In: evo:20.1R3-EVO evo:20.2R3-EVO evo:20.3R2-EVO evo:20.4R1-EVO junos:19.4R3-S2 junos:20.1R2 junos:20.2R3 junos:20.3R2 junos:20.3X75-D40 junos:20.4R1
PR NumberSynopsisCategory: KRT Queue issues within RPD
1761667On Junos and Junos Evolved platforms the rpd crashed abnormally and later chassisd crashed as well
Product-Group=evo		On Junos and Junos Evolved platforms configuring BGP causes the rpd to crash abnormally and later chassisd crashes too.

Resolved In: evo:22.2R3-S3-EVO evo:22.3R3-S3-EVO evo:22.3X50-EVO evo:22.4R3-S1-EVO evo:23.2R2-EVO evo:23.4R1-EVO evo:23.4R2-EVO evo:24.1R1-EVO junos:22.2R3-S3 junos:22.4R3-S1 junos:23.2R2 junos:23.4R1 junos:23.4R2
PR NumberSynopsisCategory: Bug and Review Tracking for Segment routing traffic eng
1720031The rpd process crash will be observed while creating/updating the PCEP tunnel
Product-Group=evo		On Junos and Junos OS Evolved platforms, when SR (Segment Routing) PCEP (Path Computation Element Protocol) provisional tunnel is configured along with the template but the template has delegation configured, then the PCEP update message received for creating/updating tunnels is causing the rpd process crash and tunnel creation/update will fail for PCEP provisional tunnel.

Resolved In: evo:22.2R3-S3-EVO evo:22.3R3-EVO evo:22.3X80-D38-EVO evo:22.3X80-D39-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.2R2-EVO evo:23.3R1-EVO junos:21.2R3-S5 junos:21.3R3-S5 junos:21.4R3-S4 junos:22.1R3-S4 junos:22.2R3-S3 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R1-S1 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1
PR NumberSynopsisCategory: ZT/YT pfe l3 forwarding issues
1774127Memory leak for deactivation/activation of SCU
Product-Group=evo		On MX platforms with MPC10, MPC11, LC9600, and MX304-LMIC16, the heap memory leaks every time the SCU (source-class-usage) policy is removed i.e. removed and re-applied resulting in restart of the line card. Heap leak is proportional to the number of source classes or indices being removed by related policy.

Resolved In: evo:23.4R2-EVO evo:24.1R1-EVO junos:20.4R3-S10 junos:21.4R3-S6 junos:22.1R3-S5 junos:22.2R3-J9 junos:22.2R3-S3 junos:22.3R3-S2 junos:22.4R3 junos:23.2R2 junos:23.4R1 junos:23.4R2
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1718063After deleting commit scripts with transient changes, the changes do not take effect
Product-Group=evo		On Junos OS Evolved ACX7100-32C / ACX7100-48L / ACX7509 / PTX10001-36MR / PTX10003 / PTX10004 / PTX10008 / PTX10016 platforms, when a commit script with transient configurations is deleted, daemon does not see the change after commit.

Resolved In: evo:23.2R1-EVO evo:23.3R1-EVO junos:22.1R3-S5 junos:22.2R3-S3 junos:23.2R1 junos:23.3R1

Modification History

First publication 2024-01-18