Alert Type
SRN - Software Release 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 22.2R3-S1-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 22.2R3-S1-EVO is now available.
22.2R3-S1-EVO - List of Fixed issues
PR Number
Synopsis
Category: AFT l2lam
1721704
Sending GARP reply packet on a VTEP interface causes flooding in network on QFX5130 and QFX5700 platforms
Product-Group=evo
On Junos OS Evolved QFX5130 and QFX5700 platforms, Gratuitous Address Resolution Protocol (GARP) flooding occurs in the network when it receives a GARP reply packet on a Virtual Tunnel End Point (VTEP) interface.
PR Number
Synopsis
Category: "agentd" software daemon
1702250
The 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.
1726205
Delete notifications for sub-interfaces missed in gRPC telemetry
Product-Group=evo
On Junos platforms, delete notifications for deleted interfaces are not reported through gRPC(Remote Procedure Call) in Telemetry. There is no service impact however notifications on deleted interface are not received.
PR Number
Synopsis
Category: MX YT-ZF Linecards Interface Software Category
1706517
Delay in an interface on LC9600 to come up due to repeated flaps
Product-Group=evo
There is a delay in an interface on LC9600 to come up sometimes due to SerDes re-initing triggered by repeating flaps. Each plane is made of one or several Fabric ASICs (Application-Specific Integrated Circuits). The Fabric ASIC is connected to all the PFE (Packet Forwarding Engine) with dedicated links called SerDes. The issue caused a delay in turning up the link from 30 seconds to 80 seconds depending on if the link partner undergoes the same delay. Traffic will not pass on the port until the link is up again.
PR Number
Synopsis
Category: EVO interface software
1725763
EVO: 400GZR: Not able to tune 400G ZR optics to 1554.54nm
Product-Group=evo
Can't set wavelength 1554.54 nm for 400G ZR and ZR-M optics
PR Number
Synopsis
Category: Bi Directional Forwarding Detection (BFD)
1725971
Multiple flaps of the interface will cause the BFD session to be down
Product-Group=evo
On all Junos and Junos Evolved platforms, the IPv4 static route BFD (Bidirectional Forwarding Detection) session may stay down if the corresponding interface flaps multiple times.
PR Number
Synopsis
Category: Border Gateway Protocol
1691299
The BGP neighbor receives the parent authentication regardless of the authentication setup under the neighbor
Product-Group=evo
On all Junos and Junos OS Evolved platforms, when a BGP neighbor authentication algorithm is configured differently from its parent group. the authentication set up in the parent group is applied to the neighbor instead of using the neighbor's specific algorithm. This causes an authentication error with the neighbor and prevents the connection from being established.
PR Number
Synopsis
Category: PTX10003 Platform related issues
1705725
Few applications fail to start after image upgrade on PTX10003 platforms
Product-Group=evo
On Junos OS Evolved PTX10003, when 'set chassis fpc pfe power (off|on)' is configured and an image upgrade is performed, certain applications like rpd-sa-agent, rptmd, dot1xd, etc might fail to start post upgrade is completed. Related features and functionalities associated with these applications will not work.
PR Number
Synopsis
Category: EVO L3 routing for BCM XGS Platforms
1718113
Unequal traffic distribution on the fabric links
Product-Group=evo
On QFX5130/QFX5700 Junos OS Evolved platforms functioning as Edge Routed Bridging (ERB) leaf, in EVPN-VXLAN (Ethernet VPN-Virtual Extensible LAN) scenario, the traffic distribution from the leaf device to the spine device over the core links will be unequal.
PR Number
Synopsis
Category: EVO VXLAN PFE for BCM XGS Platforms
1713599
LAG doesn't load balance as expected when it is configured as a VXLAN gateway
Product-Group=evo
On QFX5130/QFX5700 Junos OS Evolved platforms, in Ethernet VPN-Virtual Extensible LAN (EVPN-VXLAN) scenario, traffic is not load balanced on one of the egress member links after VXLAN tunnel termination over the LAG (Link Aggregation Group)/ECMP (Equal Cost Multipath).
1720399
The ECMP routing table does not get updated when underlay L3 interface link flaps in EVPN-VXLAN scenario
Product-Group=evo
On all Junos Evolved QFX5130/QFX5700 switches, in an EVPN-VXLAN (Ethernet Virtual Private LAN - Virtual Extensible LAN) deployment, Type-2 Overlay ECMP (Equal Cost Multi Path) routing does not happen when the underlay Layer 3 interface is flapped.
PR Number
Synopsis
Category: Express BT PFE L3 Features
1723808
Unstable interface statistic (ingress) going up and down
Product-Group=evo
The PPS reported for the interface may fluctuate for a few seconds and show either higher or lower value. The chance of this happening is very rare
PR Number
Synopsis
Category: EVO Netstack FIB Service Daemon
1698611
The route leaking does not work between different routing instances by using rib-groups on all Junos OS Evolved platforms
Product-Group=evo
On all Junos OS Evolved platforms, if the rib-groups is used to import/export routes into the default routing instance from another routing instance, then connectivity fails between those routing instances.
PR Number
Synopsis
Category: Firewall related development
1720389
Commit error will not be seen after deactivating routing-instance applied under firewall filter
Product-Group=evo
On Junos OS Evolved platforms with enabled firewall filter, deactivating routing-instance which is already applied under the firewall filter, will not show any commit error after commit is issued. This can be seen occasionally and might impact control plane traffic.
PR Number
Synopsis
Category: EVO L2 Control Plane PRs
1713640
On PTX10001-36MR the VXLAN tunnel termination functionality impacted with global configuration not enabled
Product-Group=evo
On Junos Evolved PTX10001-36MR platform, the VXLAN (Virtual Extensible LAN) tunnel termination functionality will be impacted when configuration is not enabled for tunnel termination. As the tunnel will not get terminated this will impact the packet forwarding process.
PR Number
Synopsis
Category: EVPN control plane issues
1713508
A high CPU consumption of mcsnoopd process is seen under IGMP-snooping configured scenario leading to its crash
Product-Group=evo
On all Junos and Junos OS Evolved platforms with IGMP-snooping (Internet Group Management Protocol) enabled under instance type EVPN (Ethernet Virtual Private Network) with vlan-id=none or unspecified vlan-id there will be a spike in the mcsnoopd process CPU utilization. This will lead to the mcsnoopd process crash and there will be disruptions in the traffic.
1718534
L2ALD 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.
1723832
The rpd core is seen in the long-running devices with EVPN enabled
Product-Group=evo
On Junos and Junos Evolved platforms, BGP (Border Gateway Protocol) community object reference count is not handled properly during the process of remote BGP peer routes update event. The community reference count is increasing during the increment function. However, decrement functions are not called in one of the places after processing the routes update. This will lead to a disturbance of the continuity reference count, which will cause an rpd crash.
PR Number
Synopsis
Category: ISIS routing protocol
1718734
Unexpected behavior of bandwidth based metric for IS-IS protocol
Product-Group=evo
On all Junos and Junos OS Evolved platforms unexpected behavior of bandwidth based metric in IS-IS is seen since actual bandwidth is falling back to 0 bps when one of the member interface of AE (Aggregated Ethernet) bundle (interface-group) goes down.
PR Number
Synopsis
Category: jdhcpd daemon
1689005
DHCP packets might not be sent to the clients when 'forward-only' is reconfigured under the routing instance
Product-Group=evo
On all Junos platforms, reconfiguring 'forward-only' in any routing instance is leading to deactivate of [default:default] jdhcpd filter. Dynamic Host Configuration Protocol (DHCP) packets might not be sent to the clients.
1714260
The DHCPv4 relay will send two option-82 to the server and the DHCP session will not be established
Product-Group=evo
On all Junos and Junos OS Evolved platforms, when Dynamic Host Configuration Protocol (DHCPv4) Relay is configured with forward-only mode along with "trust-option-82", DHCP-relay should not add another option 82 to the packet sent to the DHCP server. The DHCP server upon receiving the packet with two option-82 will respond only with 1st header of option-82 which might get dropped by the relay, thus the packet is not forwarded to the DHCP client and the DHCP session won't get established.
PR Number
Synopsis
Category: Layer 2 Control Module
1717267
Traffic loop is seen due to incorrect root bridge ID
Product-Group=evo
On all Junos and Junos Evolved platforms, in VSTP (Virtual Spanning-Tree Protocol) topology, whenever a new vlan is added in between previously configured vlan group followed by configuring the system-identifier, the bridge priority will change for existing vlans which might give incorrect system ID or bridge ID creating a traffic loop.
PR Number
Synopsis
Category: Layer2 forwarding on EX/NTF/PTX/QFX
1716270
mac-move-limit : MMAS flag not getting reset after interface recovers due to l2-learning restart
Product-Group=evo
MMAS Flag will not be displayed for interface after it recovers due to l2-learning process restart
PR Number
Synopsis
Category: Multicast for L3VPNs
1710323
MVPN tunnel is not synced to backup router
Product-Group=evo
On all Junos and Junos Evolved platforms, when OSPF inter-area is configured with segmented provider-tunnel and master undergoes MBB(make-before-break), the multicast route entry on backup router will not have the tunnel name synced with master.
PR Number
Synopsis
Category: Protocol Independant Multicast
1675212
High CPU utilization is seen when chassisd is down during dynamic IFL creation
Product-Group=evo
On all Junos platforms, in a very rare cases, while creating the specific dynamic IFls (PE-PIM (Protocol Independent Multicast) Encapsulation or PD-PIM Decapsulation), if the chassisd is down, the stuck entries in the Kernel Routing table (KRT) queue results in a high CPU utilization. The high CPU might hamper the rpd process functionality in rare cases and also device responsiveness will be slow.
PR Number
Synopsis
Category: Periodic Packet Management Daemon
1660299
JDI-RCT : PPMD crashed at ppm_destroy_distrib_proto_stats_group_entry ( )
Product-Group=evo
When l2cpd (in the context of xSTP) clears the entries that it has programmed on ppmd, ie when you delete xSTP configs from the box, there can be a possibility of ppmd core. If ppmd is in distributed mode then there will be no service impact, else there can be service impact as packet transmission for various protocols will happen via if ppmd is in centralized mode.
PR Number
Synopsis
Category: RPD Interfaces related issues
1722809
Router Send RA with Router lifetime 0 when the upstream interface is shut
Product-Group=evo
Issue: 1. This is a Day-1 issue with virtual RA. For virtual interfaces used in EVPN-VXLAN with multihoming scenario and VRRP, we will have two IPv6 link local addresses, one is the interface's link local address and another one is the virtual-gateway-address(VGA). There are two redundant gateways in this case which will have common VGA and in event of a failure of any given gateway, ND/RA re-resolution is not required. 2. Whenever interface is enabled or disabled, we get two link local IFA notifications for the same IFL. Only one link local IFA will be stored in the IPv6 interface at a time. 3. When second notification is received for the interface's link local address, it is treated as a link local address change and hence RA with 0 lifetime is sent for this IFA, but the source address is derived from virtual interface which is the VGA. 4. After receiving RA packet with lifetime zero, host VM deletes the default route to the VGA address and hence traffic loss is observed. 5. In this case, RA with 0 lifetime must not be sent as the VGA link local address is common and it is not changed by RPD clients (L2ALD for EVPN-VXLAN and VRRPD for VRRP). Fix: 1. As link local address will keep changing for virtual interface from virtual gateway address to configured link local address with every IFA notification, we don't need to send RA with lifetime 0 for virtual interface as the link local address for virtual interface can be changed only by RPD clients. Hence removed this part from the code for virtual interface only. 2. We need to send RA with lifetime 0 when RPD client sends an RA add request with different link local VGA. Hence added support to send RA with lifetime 0 if received VGA from RPD client is different from stored link local address in the virtual interface.
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: RPD route tables, resolver, routing instances, static routes
1716153
Multipath route is not getting compute and skip the multipath eligibility check
Product-Group=evo
On all Junos platforms, multipath route will not be formed correctly when a BGP route is received from RR (Route Reflector) and preference decided based on cluster list length.
PR Number
Synopsis
Category: PTX10K specific platform PRs
1682659
The FPC can go to a fault state on certain Junos Evolved PTX platforms after system reboot
Product-Group=evo
On certain Junos Evolved PTX platforms FPC (Flexible PIC concentrator) goes to a fault state after a system reboots with a Major alarm - Power Failure. This issue is a rare issue and the FPC in a fault state will impact the data traffic. To recover from this issue the impacted FPCs need to be rebooted.
PR Number
Synopsis
Category: ZT/YTpfe bridging, learning, stp, oam, irb software
1700321
VLAN tags are imposed incorrectly when traffic is routed over IRB going out of the access interface
Product-Group=evo
On MX platforms, traffic egressing on the IRB (Integrated Routing and Bridging) interface with the underlying L2 (layer2) access port has VLAN tags imposed incorrectly.
PR Number
Synopsis
Category: Configuration mgmt, ffp, load-action, commit processing
1663590
Commit failure might be observed on reactivation of jflow related configurations
Product-Group=evo
On all Junos and Junos Evolved platforms, reactivation of jflow (v9/ipfix) related configurations cannot be committed on backup RE.
PR Number
Synopsis
Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1730336
The rpd crashes and the commit operation fails while pushing a large configuration with the "extend-size" knob enabled
Product-Group=evo
On all Junos platforms, when the 'extend-size' knob is configured and a scaled configuration is committed, the rpd daemon crash is seen and the commit operation fails. root@device> show configuration | match configuration-database | display set set system configuration-database extend-size root@device# load update /var/tmp/New_config.txt load complete root@device# commit error: Check-out pass for Routing protocols process (/usr/sbin/rpd) dumped core (0x86) error: configuration check-out failed
PR Number
Synopsis
Category: 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.
22.2R3-S1-EVO - List of Known Issues
PR Number
Category: EVO L3 routing for BCM XGS Platforms
1709859
On Junos Evolved QFX series platforms, all BGP (Border Gateway Protocol) flapped (due to many physical interfaces flapping) and evo application crashed (evo-pfemand) when Jvision IFL (Interface Logical) sensor is periodically streamed and the IFL is deleted.
Resolved In:
evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO
PR Number
Category: PFE COS features on BT based platforms
1732461
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:22.3R3-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO
PR Number
Category: Gnats category for dynamic rendering infrastructure
1681777
If the configured data has special characters in it, then rpc get output will not escape these special characters and display the data as it is. For example, if we have configured qos class as , then ---- > the response should have default as response value .
Resolved In:
evo:21.4R3-S4-EVO evo:22.2R2-J6-EVO evo:22.2R2-S2-J2-EVO evo:22.3R2-S1-EVO evo:22.3R3-EVO evo:22.3X50-EVO evo:22.4R1-EVO evo:23.1R1-EVO junos:21.2R3-S5 junos:21.4R3-S4 junos:22.2R3-S1 junos:22.3R2-S1 junos:22.3R3 junos:22.4R1 junos:23.1R1
PR Number
Category: Firewall related development
1674893
On all Junos evolved PTX platforms, when firewall filter with family inet6 is configured with source-port/destination-port and has next-header and no payload-protocol, error messages are observed causing the filter fail to install.
Resolved In:
evo:21.4R3-S4-EVO evo:22.3R2-EVO evo:22.4R1-EVO evo:23.1R1-EVO junos:22.3R2 junos:22.4R1 junos:23.1R1
PR Number
Category: EVO Netstack Juniper Tunnel Driver Module
1703708
In EVO, lo0 statistics wont be updating. it shows always 0. Not like JUNOS.
Resolved In:
PR Number
Category: SNMP, mib2d issues
1704878
On Junos Evolved platforms, SNMP walk table (ipNetToMediaPhysAddress) is not updated when a neighbour entry is configured.
Resolved In:
evo:23.1R2-EVO evo:23.2R1-EVO
PR Number
Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1638847
On all Junos and Junos Evolved platforms configured with persist-group-inheritance, which is enabled by default from 19.4R3 onwards, might lead to mustd process crash in highly scaled configuration.
Resolved In:
evo:22.3X50-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO junos:21.2R3-S6 junos:21.3R3-S5 junos:21.4R3-S4 junos:22.1R3-S3 junos:22.2R3-S1 junos:22.3R2-S1 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R1-S1 junos:23.1R2 junos:23.2R1
PR Number
Category: Issues related to NETCONF
1709056
On all Junos and Junos OS Evolved platforms, if RPC get-configuration is invoked before RPC request-package-add in the same session of the NETCONF or Junos script, RPC request-package-add will not work.
Resolved In:
evo:22.2R2-S2-J2-EVO evo:22.3R2-S1-EVO evo:22.3R3-EVO evo:22.3X50-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:21.4R3-S4 junos:22.1R3-S3 junos:22.2R3-S1 junos:22.3R2-S1 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R1-S1 junos:23.1R2 junos:23.2R1 junos:23.3R1
Modification History
First publication 2023-06-20
22.2R3-S1-EVO: Software Release Notification for JUNOS Evolved Software