Alert Type

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

Product Affected

ACX EX MX NFX PTX QFX SRX vSRX

Alert Description

Due to the article size limitation, we publish a list of known issue for Junos software version 21.2R3-S4 separately.

The original Junos 21.2R3-S4 can be found at - https://supportportal.juniper.net/s/article/21-2R3-S4-SRN?language=en_US 

Solution

21.2R3-S4 - List of Known issues 

PR NumberSynopsisCategory: EX2300/3400 platform
1704481EX2300 System may Reboot due to Console Port Noise under Rare Circumstances.
Product-Group=junos		EX2300 may hang and reboot due to the Console Port Noise under Rare Circumstances

Resolved In: 
PR NumberSynopsisCategory: EX-Series VC Infrastructure
1685067EX4600-VC - Master RE reboot and All-member reboot lead to PFE Manager hogging logs when SFP-T is plugged in
Product-Group=junos		On Junos EX4600 Virtual Chassis (VC), the master RE reboot and all-members reboot lead to the PFE Manager hogging logs when SFP-T pluggable is installed in. The PFE Manager hogging logs has no functionality impact (PR 1641556).

Resolved In: junos:20.2R3-S6 junos:21.4R3-S2
1700133One of the Virtual Chassis members on EX4600-VC might be disconnected during VC initialization
Product-Group=junos		On EX4600-VC, when "request system reboot all members" is executed, post-reboot one of the VC member/Flexible PIC Concentrator(FPC) might disconnect and join the VC back due to Packet Forwarding Engine (PFE) restart. Traffic loss is seen when FPC is disconnected.

Resolved In: junos:20.2R3-S7
PR NumberSynopsisCategory: Border Gateway Protocol
1671081The rpd can crash while route exchange using BGP and LDP in a rare scenario
Product-Group=junos		The rpd (routing protocol daemon) crash happens when a non-BGP (Border Gateway Protocol) route is exported via LDP (Label Distribution Protocol) and later on, if the same prefix advertised by BGP is received, we select that as the forwarded route rather than the already advertised route. This is due to the logic in the forwarding route to pick the BGP route for the BGP-owned routes rather than the active route. This is a rare case and the system recovers by itself until the next event.

Resolved In: evo:21.4R3-EVO evo:22.1R3-EVO evo:22.3R1-EVO evo:22.4R1-EVO junos:21.2R3-S2-J1 junos:21.3R3-S2 junos:21.4R3 junos:22.1R3 junos:22.3R1 junos:22.4R1
1679645Errors might be seen on ephemeral commit during ISSU
Product-Group=junos		Errors might be seen on ephemeral commit during ISSU.

Resolved In: evo:23.3R1-EVO
1689904BGP LU Advertisements fail with the message "BGP label allocation failure: Need a gateway"
Product-Group=junos		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 NumberSynopsisCategory: BBE Remote Access Server
1710145High CPU utilization is seen on Junos MX series platforms
Product-Group=junos		This issue is seen on Junos MX series platforms that support authd process. when authd traces are enabled in scale setup with 10k+ routing instances, authd will keep generating some logs. These logs consumes CPU cycles and makes authd process to utilize 100% CPU.

Resolved In: evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:21.2R3-S3-J17 junos:21.2R3-S4-J1 junos:21.2R3-S5 junos:21.3R3-S4 junos:21.4R3-S3 junos:22.1R3-S2 junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.2R1
PR NumberSynopsisCategory: Express BT PFE L3 Features
1651473The BFD session might flap in some scaled system with churn
Product-Group=junos		On all Junos and Junos Evolved AFT (Advanced Forwarding Toolkit) platforms, this is infrastructure enhancement which was done to avoid BFD session flapping during the system churn. Without this infra enhancement, BFD session flap would happen in some scaled system with churn.

Resolved In: evo:20.4R3-S5-EVO evo:21.3R3-EVO evo:21.4R1-S2-EVO evo:21.4R2-EVO evo:21.4R3-EVO evo:22.1R2-EVO evo:22.2R1-EVO evo:22.3R1-EVO junos:21.2R3-S4-J3 junos:21.3R3 junos:21.4R3 junos:22.1R2 junos:22.2R1 junos:22.3R1
PR NumberSynopsisCategory: Class of Service
1702836Control packets would be dropped when CoS configuration under AE wildcard IFLs gets applied to AE control IFLs as well
Product-Group=junos		On MX platforms, when Aggregated Ethernet (AE) working in hierarchical-scheduler or per-unit-scheduler mode and AE class of service (CoS) configuration having wildcard on AE Logical Interface (IFLs) is committed in a single commit with AE interface flap, then the wildcard configuration gets applied to AE control IFL also. Ideally, any wildcard CoS configuration should not get attached to control IFLs. Only explicit configurations should be attached to control IFLs. This can lead to unintentional behavior.

Resolved In: evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R2-EVO evo:23.2R1-EVO junos:20.4R3-S7 junos:21.1R3-S5 junos:21.2R3-S5 junos:21.3R3-S4 junos:21.4R3-S3 junos:22.1R3-S2 junos:22.2R3 junos:22.3R2-S1 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: CoS support on DNX
1706040On ACX710 platforms, any commit change with regard to class-of-services, particularly schedulers applied to an interface would cause sub-second forwarding pause hence the packet loss
Product-Group=junos		On ACX710 platforms, any commit change with regard to class-of-services, particularly schedulers applied to an interface would cause sub-second forwarding pause hence the packet loss. - CoS configuration changes to schedulers may affect traffic momentarily on the VOQs (Queues) used the interface, as the traffic need to be stopped, before updating the CoS scheduling parameters. - The Traffic is resumed after the COS scheduling parameters are applied. - Even if only one queue parameters are changed, all the VOQs traffic will be stopped, as per the design. - This is as per the recommendation of the forwarding chipset vendor to stop the relevant traffic before changing the CoS scheduler parameters. For some protocols using very short interval of keepalives, such as BFD, user can disable or enlarge the intervals before applying COS scheduler change.

Resolved In: 
PR NumberSynopsisCategory: Control Plane for Node Virtualization
1685453PICs on the GNF failed to come online after the chassisd restart
Product-Group=junos		On MX platforms supporting node-slicing (MX480, MX960, MX2010, MX2020 & MX2008) have an issue that when GNF (Guest Network Function) chassisd restarts, the FPC doesn't restart as expected which causes the PIC (Physical Interface Card) to be offline.

Resolved In: evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R2-EVO evo:23.1R1-EVO junos:19.3R2-S6-J1 junos:19.4R3-S10 junos:21.1R3-S5 junos:21.3R3-S3 junos:22.1R3 junos:22.2R2 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:22.4R2 junos:23.1R1
PR NumberSynopsisCategory: EVPN control plane issues
1701632A config change caused a rpd core dump for the EVPN migrated instance
Product-Group=junos		For a Juniper MX platform that has a routing instance migrated from VPLS to EVPN, a config change after a change in route distinguisher (RD) of such an instance, could result in the rpd core. The RD change could have been trigged via CLI or auto-RD feature.

Resolved In: evo:22.2R3-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 NumberSynopsisCategory: EVPN Layer-2 Forwarding
1665130CRB EVPN MPLS is not working with control-word enabled
Product-Group=junos		On MX platforms, ARP (Address Resolution Protocol) failure or traffic drops are seen in CRB (Centrally-Routed Bridging) EVPN-MPLS (Ethernet VPN - Multiprotocol Label Switching) mode when ARP requests with control-word enabled get flooded to the MX device as the remote PE (Provider Edge) does not support the ARP suppression feature and is unable to handle IRB (Integrated routing and bridging). The ARP reply from the MX device is not going out with the control word causing traffic to be dropped as the packet is malformed.

Resolved In: junos:21.4R3-S1 junos:22.1R3 junos:22.2R2 junos:22.3R2 junos:22.4R1
PR NumberSynopsisCategory: Control plane EVPN multicast
1672383EVPN-Vlan: The non-df is forwarding BUM traffic downstream when DF is elected per IFL on QFX5110
Product-Group=junos		QFX5k platforms can support DF only at port level granularity (In other words, for all evpn instances hosted on an ESI, only one of the Multihomed QFX5k nodes can be DF). Below config options are recommended Have df-granularity knob (with which QFX5k platforms seem to have been qualified). Here, few bytes from esi value itself, instead of vlan-id are used for MOD-based DF. Another approach would be to use preference based DF election, as updated by PFE team.

Resolved In: 
PR NumberSynopsisCategory: Express PFE including evpn, vxlan
1711889Traffic drop is observed in the EVPN-VXLAN scenario with Type-2 ESI Tunnel
Product-Group=junos		On Junos QFX10K platforms, in an Ethernet VPN-Virtual Extensible LAN (EVPN-VXLAN) scenario, if the route is learned over ECMP (Equal-Cost Multi-Path) and each child next hop of the ECMP group is learned over Type-2 Ethernet Segment Identifier (ESI) tunnel, the route doesn't get programmed correctly on the device, causing the complete traffic drop for the affected route.

Resolved In: junos:21.2R3-S3-J11 junos:21.2R3-S3-J12 junos:21.2R3-S3-J13 junos:21.2R3-S5 junos:21.4R3-S3 junos:22.2R2-S2 junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.2R1
PR NumberSynopsisCategory: Express PFE MPLS Features
1712076FPC memory leak will cause FPC crash
Product-Group=junos		On PTX and QFX10K platforms, enabling the collection of LSP (label-switched path) statistics for telemetry data using the CLI command 'set protocols mpls sensor-based-stats' will cause FPC (Flexible Physical Interface Cards (PIC) Concentrators) memory leak and a huge leak may result in FPC crash.

Resolved In: junos:19.4R3-S2-J10 junos:19.4R3-S2-J11 junos:20.4R3-S7 junos:21.1R3-S5 junos:21.2R3-S5 junos:21.3R3-S4 junos:21.4R3-S3 junos:22.1R3-S2 junos:22.2R3 junos:22.3R3 junos:22.4R1-S2 junos:22.4R2 junos:23.1R1 junos:23.2R1
PR NumberSynopsisCategory: Express ASIC platform
1683562On PTX5000 platforms when a command is issued to power off an FPC, it gets stuck in the 'Announce Offline' state
Product-Group=junos		When an FPC (Flexible PIC Concentrator) on PTX5000 platforms is shut down by issuing a request command (request chassis offline slot ) or by FPC power off configuration (set chassis fpc x power off), it gets stuck in the 'Announce Offline' state since the associated timer (fru_graceful_offline_timer) doesn't increment and expire as it is supposed to.

Resolved In: junos:19.2R3-S5-J2 junos:20.4R3-S2-J17 junos:20.4R3-S5-J3 junos:20.4R3-S6 junos:21.3R3-S4 junos:21.4R3-S2 junos:22.3R2 junos:22.4R1 junos:22.4R2 junos:23.1R1
PR NumberSynopsisCategory: SRX4100/SRX4200 platform software
1630981BGP down due to BFD expired; failover restored services
Product-Group=junos		All VPN traffic may internally drop during encryption / decryption processing in HW engine requiring PFE plane reset.

Resolved In: junos:20.4R3-S7 junos:21.4R3-S3 junos:23.2R1
PR NumberSynopsisCategory: idp flow creation, deletion, notification, session mgr intfce
1705491Network outage caused during change in IDP policy
Product-Group=junos		Junos SRX platforms experience traffic outage during change in IDP (Intrusion Detection and Prevention) policy.

Resolved In: junos:21.1R3-S5 junos:21.3R3-S4 junos:21.4R3-S3 junos:21.4R3-S4 junos:22.1R3-S1 junos:22.1R3-S2 junos:22.2R3 junos:22.3R2 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.2R1
PR NumberSynopsisCategory: Interface Information Display
1611623SRX1500: Traffic fail seen on irb interface for network control forwarding class when verifying dscp classification based on single and multiple code-points
Product-Group=junos		Traffic drop might be seen on irb interface on SRX1500 for network control forwarding class when verifying dscp classification based on single and multiple code-points.

Resolved In: junos:22.3R3 junos:22.4R2 junos:23.1R2 junos:23.2R1
1636668Management interface speed is incorrectly reported as 10G instead of 1G
Product-Group=junos		On VM Host platforms, the management interface speed may incorrectly be displayed as 10G instead of 1G - this is a cosmetic issue.

Resolved In: evo:22.1R3-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R1-EVO evo:22.4R2-EVO evo:23.1R1-EVO junos:21.4R3-S3 junos:22.1R3 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:22.4R2 junos:23.1R1
PR NumberSynopsisCategory: MX Inline Jflow
1713728Specifics of inline flow monitoring on Juniper routers for EoMPLS packets
Product-Group=junos		When a P or PE router is configured with inline active flow monitoring and MPLS template with tunnel-observation ipv4/ipv6 is used, there is a chance that some EoMPLS packets may be exported using mpls-ipv4 or mpls-ipv6 template instead of mpls template.

Resolved In: 
PR NumberSynopsisCategory: ISIS routing protocol
1667575When the SPF algorithm for IS-IS in Segment Routing use case is triggered frequently, CPU usage might increase
Product-Group=junos		On all Junos and Junos Evolved platforms, when the shortest-path-first (SPF) algorithm for IS-IS is triggered frequently, CPU usage might increase and impact the device performance and traffic.

Resolved In: evo:22.4R1-EVO junos:22.4R1
PR NumberSynopsisCategory: Firewall Network Address Translation
1706541ICMP based traceroute is not showing any hops after SRX when SRX is configured with NAT64
Product-Group=junos		For all SRX platforms, ICMP based traceroute does not show any hops after SRX when SRX is configured with NAT64.

Resolved In: junos:22.3R3 junos:22.4R2 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: Layer 2 VPN related issues
1654516Routes flapping when configuration changes are applied to custom routing instance
Product-Group=junos		Routes flapping when configuration changes are applied to a custom routing instance.

Resolved In: evo:22.2R3-EVO evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:21.1R3-S5 junos:21.3R3-S4 junos:22.2R3 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.2R1
PR NumberSynopsisCategory: MX Timing software
1696957In the rare scenario, huge PTP Time errors are introduced and propagated to the downstream devices after the chassis reboot
Product-Group=junos		On MX240, MX480, MX960, MX2010, and MX2020 platforms, the remote PTP (Precision Time Protocol) clock will recover the PTP clock with Time errors after a chassis reboot on the device running as Boundary Clock.

Resolved In: evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.2R1-EVO junos:20.4R3-S6 junos:21.3R3-S4 junos:21.4R3-S3 junos:22.2R3 junos:22.3R2 junos:22.3R3 junos:22.4R1-S1 junos:22.4R2 junos:23.1R1 junos:23.2R1
1704606A transit PTP packet is modified when passing through an MPC5E and MPC6G line card 100G ports part of PTP boundary/ordinary clock configuration
Product-Group=junos		On Junos MX240/MX480/MX960/MX2020/MX2008/MX2020 platforms with MPC5E/MPC6E line-cards at 100G ports, Precision Time Protocol over IPv4/6 (PTPoIPv4/6) and Precision Time Protocol over Ethernet (PTPoE) encapsulations are enabled by default when "phy-timestamping" is configured. Since both of these encapsulation types are enabled on the interface, the transit PTPoIPv4/6 packets passthrough to the through PTP configured interfaces get interpreted and timestamped incorrectly, leading to clock drift at the end of the PTPoIPv4/6 consumer side. In an ideal situation, the transit PTPoIPv4/6 packets should be sent forth as normal packets without being altered.

Resolved In: evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R2-EVO evo:23.2R1-EVO junos:22.3R3 junos:22.4R2 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: IPv6/ND/ICMPv6 issues
1703940RE will crash when static route duplicates with an interface IP address
Product-Group=junos		On all Junos platforms, RE (Routing-Engine) will crash when a static route is added that duplicates with an interface IP address. RE crash will lead complete traffic loss.

Resolved In: junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.2R1
PR NumberSynopsisCategory: Express Chip L3 software
1658317BFD session session-state is showing DOWN while checking Micro BFD Sessions with Authentication in Non-Distributed Mode
Product-Group=junos		BFD session session-state is showing DOWN when operating in centralized Mode. Packet loss may be seen.

Resolved In: junos:21.3R3-S4 junos:21.4R3 junos:22.1R3 junos:22.2R2 junos:22.3R1 junos:22.4R1
1660606MVPN traffic is getting dropped on PTX/QFX series platforms
Product-Group=junos		On all Junos PTX and QFX10k series platforms, MVPN (Multicast Virtual Private Network) traffic is getting dropped with a discarded error. This is because, the way LSI (Label Switched Interface) interface data is carried from ASIC (Application-Specific Integrated Circuit) to PFE (Packet Forwarding Engine) is changed, causing MVPN to break.

Resolved In: junos:19.3R3-S7 junos:19.4R3-S9 junos:20.3X75-D35 junos:20.3X75-D41 junos:20.3X75-D42 junos:20.3X75-D43 junos:20.4R3-S4 junos:21.1R3-S3 junos:21.2R3-S1 junos:21.2R3-S2 junos:21.3R3 junos:21.4R3 junos:22.1R2 junos:22.2R1 junos:22.2R2 junos:22.3R1
PR NumberSynopsisCategory: QFX L2 PFE
1699316"show system statistics | display json" will not show Bridge/VPLS statistics streamed by L2ald in all products.
Product-Group=junos		"show system statistics | display json" will not show Bridge/VPLS statistics streamed by L2ald in all products.

Resolved In: 
PR NumberSynopsisCategory: QFX L3 data-plane/forwarding
1666260Traffic loss might be seen when l2circuit configurations are deactivated and activated on QFX5110
Product-Group=junos		On QFX5110 platforms with more than one l2circuit configured, deactivating and activating the l2circuit configurations successively might cause traffic drop on one or more l2circuits.

Resolved In: 
PR NumberSynopsisCategory: RPD infrastructure issues related to NSR, GRES, switchover, 
1701146The rpd crash will be observed when any commit is performed
Product-Group=junos		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.

Resolved In: evo:21.3R3-S4-EVO evo:21.4R3-S3-EVO evo:22.2R3-EVO evo:22.3R2-EVO evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R1-EVO junos:20.2R3-S1-J8 junos:21.1R3-S5 junos:21.3R3-S4 junos:21.4R3-S3 junos:22.1R3-S1 junos:22.2R3 junos:22.3R2 junos:22.3R3 junos:22.4R2 junos:23.1R1
PR NumberSynopsisCategory: Resource Reservation Protocol
1694777Restarting FPC or router reboot might causes some CCC interfaces to go down due to a 'Remote CCC down'
Product-Group=junos		On all Junos and Junos OS Evolved platforms, if CCC (Circuit Cross-Connect) is configured to use a label-switched-path such as IGP routed, i.e., no-cspf and no strict ERO (Explicit Route Object) configuration, then restarting egress CCC node or restarting FPC on the egress CCC node containing remote-interface-switch configuration multiple times may cause CCC to remain stuck in remote-if-down state, resulting in loss of traffic. (The knob 'remote-interface-switch' is configured on the egress LER of the RSVP-TE LSP (Resource Reservation Protocol-Traffic Engineering label-switched-path) which binds the LSP terminating on the node to a local interface).

Resolved In: evo:22.4R2-EVO evo:23.1R1-EVO junos:20.4R3-J8 junos:22.4R2 junos:23.1R1
1703424Path Tear message is not forwarded by PLR to merge point when merge point supports enhanced frr while route reaching merge point is using shortcut route.
Product-Group=junos		PLR not sending pathtear when merge point supports enhanced frr while route reaching neighbor is using shortcut route.

Resolved In: 
PR NumberSynopsisCategory: SRX5XX platform
1634965[SRX] SRX550HM interfaces LED of ge-0/0/6-9 will auto turn off after device bootup some minutes
Product-Group=junos		SRX550HM interfaces LED of ge-0/0/6-9 will auto turn off after device bootup some minutes.

Resolved In: junos:20.4R3-S7 junos:21.2R3-S5
PR NumberSynopsisCategory: MX10003/MX204 Linux issues (including driver issues)
1281554The host root file system and the node boots with the previous vmhost software instead of the alternate disk.
Product-Group=junos		If a vmhost snapshot is taken on an alternate disk and there is no further vmhost software image upgrade, the expectation is that if the current vmhost image gets corrupted, the system boots with the alternate disk so the user can recover the primary disk to restore the state. However, the host root file system and the node boots with the previous vmhost software instead of the alternate disk.

Resolved In: 
PR NumberSynopsisCategory: SRX-1RU platfom related protocol, QoS, filtering features et
1683213SRX4600HA might not failover properly due to a hardware failure
Product-Group=junos		In SRX4600 platform, there is a possibility of raising alarm function might not work in FPGA failure. It might affect device availability.

Resolved In: junos:21.2R3-S4 junos:21.3R3-S4 junos:21.4R3-S3 junos:22.1R3-S1 junos:22.2R3 junos:22.3R2 junos:22.3R3 junos:22.4R2 junos:23.1R1 junos:23.2R1
PR NumberSynopsisCategory: Trio pfe stateless firewall software
1614480Filter related service will not work when the filter is deleted/re-added frequently for AE interface
Product-Group=junos		On MX platforms, during reboot, the AE ifls are first added, then deleted and again added, this flapping causes corner case where the filter attachment ipc has older AE ifl index on which the filter bind fails. Filter will not be attached to the interface, so any filter related service will not work.

Resolved In: junos:20.3X75-D35 junos:20.4R3-S4 junos:21.2R3-S5 junos:21.4R2-S1 junos:21.4R3-S1 junos:22.1R1 junos:22.1R3 junos:22.2R2 junos:22.3R1
PR NumberSynopsisCategory: Trio pfe l3 forwarding issues
1646799SR-stats : Per-Interface egress and per-sid Egress sensor stats do not take MPLS label length into account in the output octet calculations
Product-Group=junos		When per-interface egress and per-sid egress SR sensor stats are configured using the CLI commands below, the (pushed) MPLS label length does not get included in the output/Tx octets field that gets exported from the sensor. set protocols isis source-packet-routing sensor-based-stats per-interface-per-member-link egress set protocols isis source-packet-routing sensor-based-stats per-sid egress This is a day-1 behavior on all Trio ASIC based FPCs on the MX platform.

Resolved In: evo:22.3R3-EVO evo:22.4R2-EVO evo:23.1R1-EVO evo:23.1R2-EVO evo:23.2R1-EVO junos:22.3R3 junos:22.4R2 junos:23.1R2 junos:23.2R1
PR NumberSynopsisCategory: MX10K linecard
1688651JUNOS_REG:MX10008:Carrier transition count is more than expected at DUT(mx10008) after flapping the interface at peer non-DUT end.
Product-Group=junos		When laser off and on happens on the remote end, within an interval of less than 500 ms, the local interface undergoes additional flap, before the link comes up. There is no impact of the additional flap, as the link does come up eventually.

Resolved In: 
PR NumberSynopsisCategory: usf ams related issues
1521929The AMS bundle state toggles momentarily as up, down, and up after configuring commit for a scaled scenario.
Product-Group=junos		* When an AMS ifd is configured for the first time or any member of the AMS bundle is removed or added, the PICs on which the members of AMS bundle are present go for a reboot. * There is a timer running in the AMS kernel which is used as a delay for the PIC reboot to complete and once that timer expires AMS assumes that the PICs might have been rebooted and it moves into next step of AMS fsm. * In scaled scenarios, this rebooting of the PIC is delayed due to DCD. This is because when a PIC goes down, DCD is supposed to delete the IFDs on that PIC and then the PIC reboot happens. * But DCD is busy processing the scaled config and the IFD deletion is delayed. This delay is much greater than the timer running in AMS kernel. * When the above timer expires, the FSM in AMS kernel wrongly assumes the PIC reboot would be completed by then, but the reboot is still pending. * By the time DCD deletes this IFD the AMS bundles are already UP. Because of this, there is a momentary flap of the bundles.

Resolved In: 
 

Modification History

2023-03-29 Update the known issue table due to a software defect in the tool which shows a fix in previous releases as a known issue
2023-02-24 Companion article to Junos 21.2R3-S4 Software Release Notification