Alert Type

PSN - Product Support Notification
Low/NotificationSRN
Low/NotificationSRN

Product Affected

ACX. EX, MX, NFX, PTX, QFX, SRX, vSRX

Alert Description

Junos Software Service Release version 21.1R3-S3 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 21.1R3-S3 is now available.

21.1R3-S3 - List of Fixed issues

PR NumberSynopsisCategory: Mojito PFE
1661332On EX4300 platform, High CPU is seen with generation of log message "/kernel: %KERN-3: i802_3_slow_recv_input:oam/esmc PDU dropped"
Product-Group=junos
High CPU is observed on EX4300 platform as packet is marked as unknown wrongly punting to CPU and spiking up the Periodic Packet Management Daemon (PPMD) and Link Fault Management Daemon (LFMD) usage. MAC address is also not learnt from the source of this packet.
1671304Commit fails on EX4300 as EX4600 and EX4300 mixed virtual-chassis is not able to create more than 1024 IFLs
Product-Group=junos
Commit check fails on EX4300 when mixed mode virtual-chassis is configured between EX4600 and EX4300 and IFL (logical interface) is created on an aggregate interface having more than 1024 IFLs. Commit failure will be seen.
PR NumberSynopsisCategory: Mojito Platform
1655530The dc-pfe might crash due to the VCCP flap
Product-Group=junos
On all Junos EX and QFX platforms configured with Virtual Chassis (VC), with the Virtual Chassis Control Protocol (VCCP) flaps or any configuration change which causes VCCP to flap, might lead to the process dc-pfe crash.
PR NumberSynopsisCategory: Bug category for Mojito Royale Layer 2 implementation
1663172MAC address learning failure and traffic loss might be observed on VXLAN enabled ports having native-VLAN configured
Product-Group=junos
On EX4300 platforms with Virtual Chassis (VC) scenario, VXLAN (Virtual Extensible LAN protocol) enabled ports may not learn MAC address when having native-VLAN (virtual LAN) configured due to FPC reboot.
PR NumberSynopsisCategory: Bug category for Mojito Royale routing implementation
1655654Few EX platforms does not generate ICMPv6 too big messages
Product-Group=junos
Few EX platforms may not generate ICMPv6 too long messages which could cause the path MTU (maximum transmission unit) discovery to fail. As a result, IPv6 session establishment may fail.
PR NumberSynopsisCategory: Category for all the Sazerac & Macallan PFE PRs
1633883The EX2300 may unexpectedly drop VOIP VLAN traffic after reboot
Product-Group=junos
On the EX2300 platform, the traffic drop may be observed on VOIP VLAN after the device reboot. Voice VLAN on EX2300 may not forward traffic correctly out of the interface when the device is either power-cycled / halted / power off or power on, and may not communicate with the default gateway.
1653260L2PT may not work for AE interfaces in Q-in-Q environment.
Product-Group=junos
This issue Affects all EX-2300,EX-3400,EX-4300MP,EX4600,EX4600-40F. L2PT may not work for AE interfaces in Q-in-Q environment.
PR NumberSynopsisCategory: All issues related to QFX PFE CoS
1650051The fixed classifier may not work in MPLS and VXLAN scenario
Product-Group=junos
On QFX5100 platforms, traffic may not get classified based on a fixed classifier in MPLS as well as the VXLAN scenario.
PR NumberSynopsisCategory: All the issues related to PFE MPLS
1627002Traffic towards MPLS-Core is not rerouted to alternate port on QFX5k platforms
Product-Group=junos
On QFX5k platforms after active egress port is down, traffic is not rerouted to alternate port towards Multiprotocol Label Switching (MPLS)-Core.
PR NumberSynopsisCategory: agentd software daemon
1656313The Configuration of invalid forwarding-class in analytics export profile goes through may lead to traffic drop
Product-Group=junos
In Telemetry scenario, the configuration of invalid forwarding-class in analytics export profile goes through inspite of the forwarding-class containing an invalid value. Due to this, FPC might crash and could cause traffic loss.
PR NumberSynopsisCategory: Atlas Layer 2 Forwarding Module
1663717Traffic loss is observed in the VPLS scenario after the upgrade
Product-Group=junos
On all Junos platforms with VPLS configuration, traffic loss is observed due to failure in ARP resolution. The ping fails for devices configured on VPLS after the upgrade.
PR NumberSynopsisCategory: Control Plane and Infrastructire for the B-54 program
1577977There might be memory leak observed in Junos Fusion satellite device for cpd process
Product-Group=junosvae
On Junos Fusion Enterprise setup, the cpd daemon running on SD (Satellite Device) attempts to establish connection with scpd (which is not present). This results in cpd memory utilization piling up on the SD node. Since the memory leak appears to be small, the impact of leak is noticed only on prolonged run.
PR NumberSynopsisCategory: BBE Layer-2 Bitstream Access
1652337The L2BSA subscribers may not be able to browse due to incorrect entries in the VPLS mac-table
Product-Group=junos
On All Junos platforms, a few L2BSA(Layer 2 Bit Stream Access) subscribers with specific S-VLAN (stacked VLAN) allocated from a specified VLAN range may face issues with traffic forwarding due to incorrect/duplicate entries which might block the genuine subscribers. When this happens, subscriber traffic could be dropped.
PR NumberSynopsisCategory: Border Gateway Protocol
1653356BGP PIC Protection is not working in virtual router
Product-Group=junos
BGP PIC Protection is not working in virtual router.
1664168The v4 prefixes might not be advertised over the BGPv6 sessions
Product-Group=junos
On all MX platforms with BGP rib-sharding and update-threading configured, the v4 prefixes might not be advertised over the BGPv6 sessions.
PR NumberSynopsisCategory: QFX Control Plane VXLAN related
1625475Some local ARP/ND entries might be lost on all Junos and Junos Evolved platforms
Product-Group=junos
Some local ARP/ND entries might be lost on all Junos and Junos Evolved platforms configured with EVPN-VxLAN or EVPN-MPLS with type 2 and type 5 NLRI resulting in impacting the routing protocols and the traffic.
PR NumberSynopsisCategory: Device Configuration Daemon
1633339The Syslog messages and the dcd crash might be seen in Junos
Product-Group=junos
On all Junos platforms, "duplicate VLAN-ID on untagged interface gr-x/x/x.xxx: conflicts with unit 1" syslog message might be seen and dcd process might be crashed if the same VLAN is configured on the GRE-tunnel interfaces.
PR NumberSynopsisCategory: Firewall Filter
1622585The FPC might crash when interface participating in "next-interface" filter action flaps
Product-Group=junos
On MX platforms, when FBF(Filter-based Forwarding) is configured with "next-interface" action and if the interface participating in the filter gets flapped due to any reasons, notification to update the filter action is initiated. It might result in FPC crash with core dump. The same could be a rare timing issue.
PR NumberSynopsisCategory: dhcpd daemon
1649638The jdhcpd daemon might crash after Junos upgrade
Product-Group=junos
On all MX platforms, jdhcpd core dumps might observed when using legacy DHCP feature with pseudowire interface after the Junos upgrade.
PR NumberSynopsisCategory: IFL, IFF creation
1612026Traffic might be dropped on ACX5448 and ACX710
Product-Group=junos
On ACX5448 and ACX710 platforms, if ECMP is configured, while removing the config, the unicast NHs will be deleted first followed by the unilist NH. Since unilist NH in turn refers to this unicast NH, first the unicast elements in unilist will be set to discard. This replace action (unicast to discard) will take place only if the weights of unilist NH and unicast NHs are same. But while updating the last unicast member in unilist, the weights are different because unilist weight is not updated properly when all the unilist elements are pointing to discard NH. Due to which, ecmp egress object creation fails for that unilist and it remains stale in BCM. The max entry for ECMP is 4096, if all this is used up due to this stale entries, new ECMP entries can not be created thus traffic drop will be seen.
PR NumberSynopsisCategory: Covers Application classification workflows apart from custo
1642383Flowd crash when back to back sigpack is updated at the time of stress traffic
Product-Group=junos
The flowd might crash when back to back sigpack is updated when heavy traffic is going on.
PR NumberSynopsisCategory: PRs related to Juniper's Ethernet OAM (LFM) implementation.
1636226FPC might crash if the continuity-check interval under CFM is modified
Product-Group=junos
On Junos platforms in an ethernet OAM (Operation Administration and Maintenance) environment, configured with CFM (Connectivity Fault Management) and PM (Performance Monitoring) when continuity-check interval is changed and then the OAM configuration is deactivated, FPC's that are associated with the CFM sessions might crash.
1643855Traffic might be impacted due to the RCP session number reaching the maximum limit
Product-Group=junos
If there are communication issues between the primary RE and the backup RE, the RCP process may spawn database sync sessions that exceed 75 sessions on dual RE platforms. This can impact services such as performing a configuration commit may fail.
PR NumberSynopsisCategory: bug tracker for evo
1667404The default code-point aliases and respective CoS value Bit patterns are inconsistent with Junos in Evo
Product-Group=junos
On Junos Evolved PTX platforms, class-of-service (CoS) values associated with default code-point aliases are inconsistent with Junos. Due to this, incoming packets may get associated with incorrect CoS servicing level (forwarding class and packet loss priority (PLP)).
PR NumberSynopsisCategory: EVPN control plane issues
1659786The process rpd might crash when protocol EVPN is deactivated
Product-Group=junos
On all Junos and Junos OS Evolved platforms, with multiple activating/deactivating Ethernet Virtual Private Network (EVPN) or deactivating the Virtual Routing and Forwarding (VRF) instance with protocols EVPN for type 5 route, the process rpd might crash.
PR NumberSynopsisCategory: EVPN Layer-2 Forwarding
1576943The BUM traffic might be dropped after changing any configuration on the device without router-id configured.
Product-Group=junos
In EVPN-MPLS scenario, if router-id is not configured on the device, BUM (Broadcast, Unknown Unicast, and Multicast) traffic might be dropped after any configuration is changed.
PR NumberSynopsisCategory: PRs for Lagavulin PFE tracking
1656117Filter-Based Forwarding filter might not work as expected
Product-Group=junos
On EX4400 platforms with high number of FBF (Filter-Based Forwarding) filters configured in IRB (Integrated Routing and Bridging) interfaces or FBF filter configured for multiple IRB interfaces, the filter might not work as expected due to high TCAM (Ternary Content Addressable Memory) entries.
1662508The fxpc crash might be observed with the RPF check enabled
Product-Group=junosvae
On the EX4400 and EX4400-Multigigabit platforms with Reverse Path Forwarding (RPF) check enabled, the fxpc crash might be observed with the IPv6 routes.
1663126SSH traffic might be affected when filter log action is used
Product-Group=junos
On EX4400 and EX4100 platforms, when a filter is configured with log action, Secure Shell (SSH) packet might hit queue 15 where it will be discarded after logging causing SSH to fail.
PR NumberSynopsisCategory: Express PFE including evpn, vxlan related issues on QFX10K
1627876Traffic loss might be observed due to Address Resolution Protocol (ARP) getting programmed as indirect next-hop by control plane for external routes distributed over IRB on QFX10k Junos platforms
Product-Group=junos
On QFX10k Junos platforms Address Resolution Protocol (ARP) host might get programmed as indirect next-hop by control plane for routes reachable via IRB host.
PR NumberSynopsisCategory: Express PFE L2 fwding Features
1648078The CLNP traffic tunneled through EVPN-VXLAN fabric might get dropped
Product-Group=junos
On QFX10k platforms with EVPN-VXLAN (Ethernet Virtual Private Network Virtual Extensible LAN) is deployed, differences in the unicast and multicast packets between IS-IS (Intermediate System - Intermediate System) hello packets and CLNP (Connectionless Network Protocol) ping packets might be observed. The packet might get egressed out, but the LLC (Logical Link Control) header data is missed. A header needs to be added for all LLC packets, so the peer node can not recognize these packets without the header, and it simply discards the CLNP packet.
PR NumberSynopsisCategory: Express pfe Mclag
1666399Static MACs are not programmed after reboot, resulting in floods of unicast traffic
Product-Group=junos
After rebooting, we see that the link does not have a static MAC address. This results in unicast traffic flooding and sometimes traffic drops for this static MAC.
PR NumberSynopsisCategory: FIB telemetry daemon
1653942When fib-streaming is enabled and two or more collectors are involved, fibtd core may be observed due to a timing sync issue
Product-Group=junos
On all junos and EVO platforms, when two or more collectors have subscribed to gAFT sensors on the device, fibtd daemon(forwarding information base processing daemon) observes a core and initial sync with the collectors are lost. This will cause the device to stop streaming telemetry data.
PR NumberSynopsisCategory: PRs for forge platform software issue
1656738The fxp0 interface might remain 'UP' when the cable is disconnected
Product-Group=junosvae
On SRX1500 and SRX4K platforms, the fxp0 interface might remain up even when the cable is disconnected.
PR NumberSynopsisCategory: ACX500/1000/2000/4000 timing software
1610305ACX2100/2200 with G.8275.1 configuring 'e2e-transparent' might be stuck at PTP ACQUIRING
Product-Group=junos
On ACX2100/2200 platforms, after feb/chassis-control reboot, the downstream node will give PTP announce message to upstream with unexpected values of priority and clock class, etc. to force upstream elect the downstream as master. Also for the case when the upstream's slave port swing back and forth, the PHY_OP and PHY_TYPE for correction fields updating are not managed properly. This leads to the downstream node being stuck at PTP ACQUIRING status. To recover the issue, bounce the 'e2e-transparent' knob on the upstream to deactivate the phy-timestamping functionality for short while and enable it back.
PR NumberSynopsisCategory: IDP policy
1657056The flowd core might be observed when IDP policy rulebase changes
Product-Group=junos
A change in IDP lsys policy configuration while the system is processing traffic may cause a flowd coredump in rare cases.
PR NumberSynopsisCategory: Atlas Integrated Routing & Bridging (IRB) module
1651273VMcore is triggered when control packets go over IRB and GRE
Product-Group=junos
On all Junos platforms, when IGP (OSPF/RIP) protocols are configured with GRE and IRB, the control packets from them pass over GRE and IRB which leads to VMcore.
PR NumberSynopsisCategory: Flow Module
1630124TCP-MSS override for GREoIPSec does not work
Product-Group=junos
On SRX-Series devices, Generic routing encapsulation over internet protocol security (GREoIPSec) may not work when TCP-MSS overrides.
1651836The traffic might get lost when using dedicated HA fabric link
Product-Group=junos
When dedicated fabric High Availability (HA) link is configured, there might be random device crash causing traffic loss. However, this can be avoided by configuring revenue port as fabric link.
1668898vSRX not processing fragmented packets
Product-Group=junos
When the system memory is running low (Yellow/Orange zone) due to extensive L7 inspection of traffic, fragmented packets may not be able to be reassembled and may be dropped.
PR NumberSynopsisCategory: Issues related to Firewall Authentication on SRX platforms
165112922.1R1:AUTH:unable to get the "firewall-authentication users" details on node 1
Product-Group=junos
Functionality Impact - Authentication entries will not be synced to secondary node in the HA setup and when switchover happens, already established authentication sessions will be lost and clients will have to login again with authentication credentials.
PR NumberSynopsisCategory: all logging related bugs on srx platforms
1655808The crash files may be seen on SRX platforms
Product-Group=junos
On Junos vSRX and cSRX platforms crash files may be seen for pfe(packet forwarding engine) and llmd(local log manager daemon). The system may see momentary service impact due to the pfe crash but recovers to normal functioning without manual intervention.
PR NumberSynopsisCategory: Firewall Network Address Translation
1645039Datapath daemon might crash resulting in total traffic and service failure
Product-Group=junos
On all SRX-Series devices, when policy configuration is modified and committed multiple times while the device is handling MS-RPC traffic with more than 1000 RPC port map entries present in the device, it may result in datapath daemon crash.
PR NumberSynopsisCategory: IPSEC/IKE VPN
162796321.4Th :SPC3-Config payload :Tunnel bringing up failed from strongswan when changing the configuration IKE in VR and observed the " NO_PROPOSAL_CHOSEN notify error" message
Product-Group=junos
Half open timer for IKE negotiation is set to 60s i.e. DUT keeps an entry of an IKE INIT request packet for its response in a temporary database for a maximum time period of 60 seconds. Upon timer expiry, the entry will get deleted from its database. Also the below two cases are supported: Case1: DUT sends IKE response if the peer retransmits IKE-INIT negotiation packet: Peer sends the first packet DUT replies with second packet The second packet is lost in the network Peer retransmits first packet DUT replies again with second packet Case2: If peer initiates a new negotiation instead of retransmitting the earlier packet, then the DUT will send NO_PROPOSAL_CHOSEN: Peer sends first packet DUT replies with the second packet Second packet is lost in the network Peer starts a new negotiation with first packet DUT then sends NO_PROPOSAL_CHOSEN
1655140The Juniper secure connect VPN users may face login issues intermittently
Product-Group=junos
On SRX Series devices, when using the Juniper Secure Connect VPN client with Radius authentication for login requests, users may get the PAP (password authentication protocol) and CHAP (Challenge Handshake Authentication Protocol) authentication failure error message. When this happens, VPN connections might not be established all the time even though the number of IPs in the address pool is greater than supported remote-access users.
PR NumberSynopsisCategory: prs for lacp protocol
1635935Traffic loss may be seen on QFX10K due to congestion
Product-Group=junos
During congestion PPMAN(Periodic packet management) run short of resource leading to PDUs (Protocol Data Units) getting failed to be sent. Due to PPMAN queue starvation across TX/RX path, LACP sessions may not get a chance to transmit PDUs which can further lead to peer lacp timeout, aggregated ethernet interface flap and traffic loss.
1640240Aggregated Ethernet interface remains up instead of down after deleting loopback and ae interface ip on neighbor while verifying BFD sessions on router
Product-Group=junos
Aggregated Ethernet child interfaces with LACP configurations are not timing out even if peer is gone and not sending any bridge protocol data unit (BPDU).
PR NumberSynopsisCategory: Label Distribution Protocol
1611338IPv4 Prefixes might be associated into both IPv4 and IPv6 LDP database after RE switchover
Product-Group=junos
On all Junos and Evolved platforms with NSR enabled and dual-transport knob configured under protocols ldp, if RE switchover, IPv4 prefixes might get advertised to IPv6 session as well if there are separate LDP sessions existed for IPv4 and IPv6.
PR NumberSynopsisCategory: SW PRs for MPC10E Interfaces
1638410PFE might get stuck after 100G/400G interface flaps
Product-Group=junos
On Junos platforms equipped with MPC10E/MPC11E/LC2301/MX10K-LC9600 line cards, when any 100G/400G interface with high priority class-of-service scheduler configuration flaps, it might result in series of error messages during high traffic flow. Eventually this would result in PFE-disable action, impacting the related traffic. However, the issue could be recovered after FPC reboot.
PR NumberSynopsisCategory: Multiprotocol Label Switching
1655177The "rpd" process may get crash when container Label Switch Path (LSP) is configured with "default-template"
Product-Group=junos
On all Junos and Junos Evolved platforms, if container LSP is configured in non-master instance with "default-template" and if normalization gets triggered then "rpd" may crash .
1664670Dynamic label space usage crossed the threshold limit of 90 percent
Product-Group=junos
On all Junos and EVO platforms, in warm standby mode, when the MPLS route is learnt on the standby, a label was allocated. As protocols are not running it will not be automatically synced/mirrored. But in case the route is deleted, this was not deallocated back and will result in traffic loss.
PR NumberSynopsisCategory: next gen multicast for L3VPNs
1640487Type 7 routes might be lost in MVPN+PIM SSM scenario
Product-Group=junos
On all Junos platforms with Multicast Virtual Private Network (MVPN) implemented, few Type 7 routes might get disappeared from the egress provider-edge (PE) router on a failover scenario. This issue might be observed if the PIM-SSM (Protocol Independent Multicast - Source Specific Multicast) mode is used. Hence, egress PE might not receive multicast traffic and end to end communication might not be successful. This could be a rare issue. Please consider not to use PIM-SSM mode in order to avoid hitting with this issue.
PR NumberSynopsisCategory: MX Timing software
1657132The transit traffic might be impacted in the PTP scenario
Product-Group=junos
On all Junos platforms, traffic issues might be observed with downstream devices when Precision Time Protocol(PTP) is configured (G.8275.1 PTP profile) along with PHY timestamping and Multiprotocol Label Switching (MPLS) terminated on the 10G interface. The transit PTP ipv4 packets are updated with the wrong Correction Factor(CF). This issue could be restored by disabling PHY stamping. However, disabling might impact the PTP performance.
1660844Transit PTP over IP packet drop might be observed on an AE interface
Product-Group=junos
On Junos MX/EX/SRX platforms with specific line cards e.g. MPC2E-NG, 3E-NG, 5E,6E,7E,8E,9E, LC2101, when Precision Time Protocol (PTP) over IP encapsulation is configured, there might be transit PTP packet drop when reconfiguring child interfaces of an Aggregate-Ethernet (AE) bundle from one FPC to the other. This issue might be restored by deactivating and activating PTP stream.
PR NumberSynopsisCategory: This PR category is for tracking only IPv4/ARP/ICMPv4 is
1644616GARP reply doesn't update ARP entry though gratuitous-arp-reply option is configured.
Product-Group=junos
Receiving GARP reply doesn't help update ARP entry though gratuitous-arp-reply option is configured. As a result, traffic loss might be seen depending on the timing.
PR NumberSynopsisCategory: Kernel Multicast Infrastructure
1653920Traffic blackhole might be seen due to next-hop install failure on Junos PTX platforms
Product-Group=junos
On Junos PTX platforms there might be a traffic blackhole which happens because of next-hop installation failure for multicast RSVP(Resource Reservation Protocol) P2MP(Point to Multipoint) traffic. This issue might only be encountered in a scaled RSVP P2MP environment after a network event which might cause reconvergence.
PR NumberSynopsisCategory: This PR category is for tracking only TCP/UDPtransport layer
1626400Configuration commit may fail while configuring the knob 'authentication-key-chains' under groups
Product-Group=junos
On all Junos and Evo platforms, if 'no-persist-groups-inheritance' is not configured, configuration commit issues may be seen while configuring the knob 'authentication-key-chains' under groups. Expanded view of the database is not fetched when configured via groups security and hence commit check error may be seen. The TCP-keychain functionality may not work as expected if this issue occurs.
PR NumberSynopsisCategory: OSPF routing protocol
1659366The memory leak and process rpd crash might be observed when the peer interface flaps continuously in the Segment Routing
Product-Group=junos
On all Junos and Junos OS Evolved platforms configured with Segment Routing, when the peer interface flaps continuously, the memory leak might be observed which might lead to the process rpd crash.
PR NumberSynopsisCategory: MPLS Point-to-Multipoint TE
1652439P2MP LSP flaps after the MVPN CE facing interface goes down
Product-Group=junos
On all Junos and EVO platforms, P2MP (Point-to-Multipoint) LSP (Label-Switched Paths) which is configured as a static provider tunnel for (S,G) in an MVPN (Multicast Virtual Private Network) instance may flap when the MVPN CE (Customer Edge) facing interface goes down and intermittent traffic loss might be observed.
PR NumberSynopsisCategory: Express Paradise PFE L3 Features
1663881ALB stats not showing in CLI
Product-Group=junos
Adaptive [Load Balancing] Statistics are not updated under 'show interfaces aeX extensive' on the QFX10k platform.
PR NumberSynopsisCategory: Issues related to PKI daemon
1624613PKID could crash and generate a core-file when there was limited memory available on the routing-engine
Product-Group=junos
In rare circumstances, PKID could crash and generate a core-file when there was limited memory available on the routing-engine
PR NumberSynopsisCategory: vMX Platform Infrastructure related issue tracking
1634908LACP interface might go down when a sub-interface configuration is added and committed to the AE interface
Product-Group=junos
On all MX150 platforms, when an Aggregate Ethernet (AE) interface is configured with LACP and adding a sub-interface configuration under the AE interface causes the LACP down leads to traffic loss.
PR NumberSynopsisCategory: Chassis mgmt for all QFX systems - chassis MIB, alarms, CLI
1603588Chassisd generates "Cannot read hw.chassis.startup_time value: m" every 5 seconds on qfx10008 and qfx10016
Product-Group=junos
The "Cannot read hw.chassis.startup_time value:m" error log is generated every 5 seconds in the output by "show log chassisd" on qfx10008 and qfx10016. This is a cosmetic message. There is no impact to the system.
PR NumberSynopsisCategory: Category to track the issues related to QFX5K hostpath
1630201LACP timeout might be observed during high CPU utilization
Product-Group=junos
On QFX5100 switches, when the CPU utilization (Routing Engine and FPC) is 85 percentage or more and there are multiple Network Configuration Protocol (NETCONF) sessions running or SNMP polling is happening over multiple sessions simultaneously, the LACP session configured in fast mode might timeout.
PR NumberSynopsisCategory: PFE L2
1649637The local-minimum-links feature not working as expected on QFX5100 VC platforms
Product-Group=junos
On the QFX5100 VC(Virtual-Chassis) platform, the AE(Aggregated Ethernet) interface might not go down on a single interface flap in the bundle even though the knob "local-minimum-links" is configured on the device.
1650416L2PT configuration on a transit switch in a Q-in-Q environment breaks L2PT
Product-Group=junos
L2PT on a transit switchs like Ex4600 and QFX in a Q-in-Q environment breaks L2PT for other S-VLANs if uplink is AE (Aggregated Ethernet) interface.
1660787CoS might not get applied on VC ports
Product-Group=junosvae
CoS configs are not getting applied on vcp port in QFX5100 VC.
PR NumberSynopsisCategory: All issues related to L3 data-plane/forwarding
1650335Traffic Loss will be observed with Virtual-Router
Product-Group=junos
In EX4K and QFX5K platforms, traffic loss will be observed with virtual-router function.
PR NumberSynopsisCategory: All the issues related to PFE MPLS
1666760BGP-LU traffic might be dropped when "CCNH ingress labeled-bgp inet" is configured
Product-Group=junos
On Junos PTX platforms, the native inet packet might not be forwarded correctly when "Chained Composite Next-Hop (CCNH) ingress labeled-bgp inet" is configured. PFE wrongly adds Label 3 to the incoming inet packet and sent the MPLS frame to the edge device where it fails.
PR NumberSynopsisCategory: PRs for PFE EVPN / VxLAN related issues on QFX5K
1645929An interface might be detached from LACP when configuring VLAN tagging in the EVPN-VXLAN scenario on Junos QFX5K platforms
Product-Group=junos
On Junos QFX5K platforms, the LACP packet might get intercepted and the interface detached from LACP when configuring VLAN tagging in the EVPN-VXLAN scenario.
PR NumberSynopsisCategory: QFX5100 Virtual Chassis related issues
1667952QFX5100VC SNMP : jnxPowerSupplyFailure and jnxPowerSupplyOK are not getting generated for Backup FPC
Product-Group=junos
On QFX5100VC, jnxPowerSupplyFailure and jnxPowerSupplyOK are not getting generated for Backup FPC.
PR NumberSynopsisCategory: QFX5200/5110/5120/5210 Interface related issues. Port up/do
1618891One-time interface flap might be seen on the QFX5120 platform
Product-Group=junos
On QFX5120 platforms, the flap might be observed on the interface when applying the configuration unrelated to the respective interfaces.
PR NumberSynopsisCategory: QFX5200/5110/5120/5210 Platform optics related issues
1653723Port might be down after inserting specific SFP
Product-Group=junosvae
On QFX5100-48S platforms with QFX-5e img and 10G interface, insertion of transceivers- SFP-SX or SFP-LX10 into a 1G port might make other neighbour 10G ports down, affecting the related traffic.
PR NumberSynopsisCategory: QFX5200/5110/5120/5210 Platfom issues
1634495Traffic loss might be observed on EX4650-48Y and QFX5120-48Y switches when there is a link flap
Product-Group=junos
On EX4650-48Y and QFX5120-48Y switches when there is a link flap, the link/interface might take more than expected time to come up resulting in increased traffic loss.
1646894Restarting one of the FPCs may cause traffic loss in QFX VC scenario
Product-Group=junosvae
On QFX with the Virtual Chassis (VC) scenario, when traffic coming into master FPC and going out from the backup FPC, reboot the backup FPC, the master FPC still thinks the backup link is present, and "show lacp interface" also continues showing the backup link as collecting / distributing. Therefore, master FPC continues sending the echo reply through the backup link which fails since the backup is powered off, which might lead to a traffic drop.
1658568QFX5120: "request system power-off" doesn't work and vmcore is generated
Product-Group=junosvae
On QFX5120 platform, "request system power-off" doesn't work and system will be rebooted. At that time, vmcore is generated.
1659453The slave PTP device will not lock its clock with the master PTP device
Product-Group=junos
On all Junos platforms, when a slave Precision Time Protocol (PTP) member that used one IPV6 address went for a reboot and came back with another IP address via Dynamic Host Configuration Protocol (DHCP), which can end up in multiple entries for the same source port.
PR NumberSynopsisCategory: Related to sw defects for K2-RE
1662913The watchdog timeout is encountered and the system reboots after the 'request system halt' command executed
Product-Group=junos
On all platforms with RE-1800 & RE-2000, after the 'request system halt' command is executed, the watchdog timeout is encountered and causes the routing engine (RE) to fail to boot.
PR NumberSynopsisCategory: Issue related to mcnh routing infrastructure within RPD
1663568The forwarding plane is not updated properly in scaled MVPN scenario after receiving PIM leave messages
Product-Group=junos
On all Junos and Junos Evolved platforms, when IFLs from non-default routing instances are being added with the OIF scaling of more than 2000 there will be a spillover of IFLNHs into different next hops due to this the outgoing interfaces (OIFs) will not be deleted from multicast next-hop.
PR NumberSynopsisCategory: RPD Next-hop issues including indirect, CNH, and MCNH
1645296Traffic drop with EBGP multipath and EBGP paths equal to the maximum-ecmp limit
Product-Group=junos
On all Junos and Junos OS Evolved platforms configured with EBGP multipath and bgp-protect-core under the routing instance, if the number of external paths along with the BGP Prefix-Independent Convergence (PIC) backup paths reaches the maximum ECMP limit, then all the traffic towards the destination is dropped on PFE with the exception of "sw error".
PR NumberSynopsisCategory: Issues related route resolution routing infrastructure
1658277Some L3VPN prefixes are not active because nexthop is not usable
Product-Group=junos
If preserve-nexthop-hierarchy knob was deconfigured and if no-propagate-ttl config within VRF is opposite to global config,some routes can be inactive. Secondary nexthops may not be resolved and active, hence L3VPN routes are not active.
1658678The rpd crash might be triggered when the BGP route resolves over another BGP route
Product-Group=junos
On all Junos and EVO platforms, when the BGP route resolves over another BGP default route such that the default route is an EIBGP load-balanced route, then the resolution loop may go into infinite recursion leading to stack corruption and rpd core.
PR NumberSynopsisCategory: Resource Reservation Protocol
1638145LSP over broadcast segment stays down when RSVP setup protection is enabled
Product-Group=junos
When RSVP setup protection is enabled, the LSP over a broadcast segment might stay down, due to a missing function of nexthop check for broadcast segment in code.
PR NumberSynopsisCategory: SW PRs for SCBE3 fabric
1606296Fabric error might be seen when MPC10E to MPC2/MPC3/MPC4/MPC5/MPC6 based FPC fabric traffic is congested
Product-Group=junos
On the MX240/480/960 system with both MPC10E and MPC2/MPC3/MPC4/MPC5/MPC6 based FPCs are installed, when MPC10E sends high traffic to MPC4E or other mentioned cards as the destination, the destination line card will not be able to cope up with MPC10E traffic flow.
1612957The PFE/SIB/SCBE/FPCs might reboot due to the unexpected fabric errors shown up on MX240/480/960 platforms
Product-Group=junos
In MX240/480/960 platforms with SCBE3-MX and Enhanced midplane scenario, in some rare cases, if flooding huge traffic from MPC7/MPC8/MPC9 to MPC2E/MPC3E/MPC4E/MPC5E and flapping the interface on MPC2E/MPC3E/MPC4E/MPC5E, it will cause the unexpected request time errors on MPC7/MPC8/MPC9 since the MPC2E/MPC3E/MPC4E/MPC5E might not be able to handle such high volume of requests, it will cause PFE destinations to become unreachable even when the fabrics are online. Then PFE/SIB/SCBE/FPCs might reboot automatically while these accumulated fabric errors hit the fabric connectivity restoration conditions of the Fabric Healing process (FHP).
1657378The low priority stream may get stuck and all traffic might be dropped
Product-Group=junos
On MX-Series devices, the low priority stream might be marked as a destination error and as a result, the low priority stream is stuck and all traffic might get dropped.
1658206The CPU usage SPMB can hit 100% for a short while
Product-Group=junos
This issue is seen on the MX20XX platform the CPU usage SPMB can hit 100% for 10 or 20 seconds.
PR NumberSynopsisCategory: Generic platform and infra issues for MS-MIC and MS-MPC(XLP)
1645585The eBGP session might not be established on MX platforms with MS-MPC and MX-SPC3 cards
Product-Group=junos
On MX platforms with Multiservices Modular PIC Concentrator(MS-MPC) or Service Processing card(MX-SPC3), enabled with the service-set for NAT and stateful firewall configuration, the eBGP session might not be established on the interface when the multiservices (ms-) logical interface service-set is applied to the same physical interface.
PR NumberSynopsisCategory: SRX RTCOM module bugs
1588593Updates were made to RTCOM to reduce its overall memory usage, improving holistic scale of Layer-7 services
Product-Group=junos
Updates were made to RTCOM to reduce its overall memory usage, improving holistic scale of Layer-7 services
PR NumberSynopsisCategory: security-intelligence feature on SRX
1638923Kernel panic might be seen during boot
Product-Group=junos
On Junos platforms kernel panic might be seen during the boot sequence.
PR NumberSynopsisCategory: SRX-1RU platfom related protocol, QoS, filtering features et
1654838The control link may not come up during the reboot
Product-Group=junos
On SRX4600 platforms, during reboot when the port signal is unstable, it may cause a control link down.
PR NumberSynopsisCategory: ZT/YT pfe firewall software
1627986FPC might restart with syslog filter action configured
Product-Group=junos
On EVO-based PTX platforms and all MX series platforms with MPC10+, configuring syslog as a filter action may cause the FPC to restart.
PR NumberSynopsisCategory: ZT/YTpfe bridging, learning, stp, oam, irb software
1650854The IPv4 traffic drop might be observed in EVPN scenario
Product-Group=junos
On specific Junos platforms with line cards MPC10 and above, EVPN (Ethernet Virtual Private Network) configured with MPLS, IPv4 packet drops might be observed, when transit IPv4 traffic passing through EVPN data plane. This issue is observed due to a bug during ARP snoop processing.
PR NumberSynopsisCategory: Trinity LU, IX, QX, MQ chip drivers, ucode & related SW
1645505FPC crash might occur during ISSU upgrade
Product-Group=junos
On MX/EX/SRX platforms, FPC crash might be observed during ISSU (In-Service Software Upgrade)upgrade in specific line cards (eg MPC9/8/7).
PR NumberSynopsisCategory: Issues related to broadband edge apps (PPP, DHCP) on Trio ch
1668976Traffic loss might be observed for the multicast traffic
Product-Group=junos
On all MX platforms where BBE subscriber services are configured, multicast traffic loss might be observed for subscribers if the multicast group id is larger than 255.
PR NumberSynopsisCategory: Issues related to mgd, DAX API, DDL/ODL infrastructure, Juno
1590099The ISSU might abort due to unsuccessful image validation on all SRX platforms
Product-Group=junos
On all SRX platforms, the image validation will fail when ISSU from an image earlier than 21.2R1 (with stable11 freebsd) to an image later than 21.2R1 (with stable12 freebsd) which will cause the ISSU will abort. This is due to incompatible BSD releases. This PR has enabled the no-validate option so that this validation can be skipped for future releases.
1624562The core files may not get deleted using CLI "file delete /var/core/*/vmcore*"
Product-Group=junos
File delete with regex may fail, if using filename without regex it works.
1627323Junos Fusion Satellite EX4300 upgrade fails from Aggregate Device MX104
Product-Group=junos
Junos Fusion Satellite Device (SD) EX4300 upgrade fails from Aggregate Device (AD) MX104 with dual-RE.
PR NumberSynopsisCategory: Vale platform related issues.
1583839File permissions are changed for /var/db/scripts files after reboot on PTX/QFX platforms
Product-Group=junosvae
On PTX10K and QFX10K platforms running Junos, file permissions might be changed for /var/db/scripts files after rebooting the device. This issue might have an impact on the scripts running on the box.
PR NumberSynopsisCategory: Virtual Router Redundancy Protocol
1668280The VRRP track might go down upon GRES
Product-Group=junos
On all Junos platforms, when Graceful Routing Engine Switchover (GRES) is performed on the Virtual Router Redundancy Protocol (VRRP) master, the VRRP track on the master may go down and might be stuck in the down state. This might trigger VRRP Master switchover and temporary traffic loss if the track route cost changes the priority.
PR NumberSynopsisCategory: Windsurf interfaces software
1664978The link-degrade recovery will not work for a specific interface speed
Product-Group=junos
On all Junos platforms link-degrade functionality needs to be supported and manually configured. Link degrade is manually configured to monitor for link error/issues. Once the error is observed, the link goes down.
PR NumberSynopsisCategory: usf nat related issues
1610977Traffic might not be processed when mams-members are replaced in the AMS bundle
Product-Group=junos
On all MX platforms with SPC3 card having MAMs interface configured in AMS bundle, traffic/data packet loss might be seen. Packets might be seen discarded as "NAT allocation failures".
 
 

21.1R3-S3 - List of Known issues

PR NumberSynopsisCategory: NFX Layer 3 Features Software
163427021.1R3:NFX350_S2:Observing packet drop between two nfx350-S2 boxes
Product-Group=junos
The BCM FPC port's STP states are going disabled state because of timing issue between bring up of couple of processes.
PR NumberSynopsisCategory: This is for Hw & Sw issues which are special for SPC3 car
1641793Traffic might be dropped due to the RX queue being full
Product-Group=junos
Incoming packets might be sent to RX queues of core0 or core14 mistakenly, might result in the queue buffer full and the packets getting dropped.
PR NumberSynopsisCategory: Bi Directional Forwarding Detection
1675921Micro BFD session state in RE remain UP even peer side session is down.
Product-Group=junos
Any platforms with Micro BFD configured on member links of the LAG/ae interface, BFD Session state in RE remains as UP always even though PEER device has ceased.
PR NumberSynopsisCategory: Border Gateway Protocol
1669930BGP inactive routes may not be advertised to peers in BGP-LU scenario
Product-Group=junos
If BGP-LU(labeled-unicast) is configured using "rib inet.3/inet6.3" address family, BGP inactive routes are not re-distributed to BGP-LU peers, leading to improper traffic patterns.
PR NumberSynopsisCategory: VPWS, L2 CKT, EVPN-VPWS
1661802The l2circuit backup might not get reverted to primary in rare condition
Product-Group=junos
On ACX710/ACX5448 platforms in the layer2 circuit scenario, if the primary path is down due to any reason, the backup circuit takes the mastership and ideally, once the primary path is up, mastership is to be reverted. But, in rare cases, the mastership gets reverted but the label might get lost from PFE and results in traffic loss for the l2circuit connection. However, deactivating and activating the affected l2circuit configuration could help in restoring the services.
PR NumberSynopsisCategory: SNMP, mib2d issues
1669510The snmpd core might be observed with filter-duplicates configuration
Product-Group=junos
On all Junos and EVO platforms configured with filter-duplicates, the snmpd core might be observed if the SNMP query is made simultaneously from NMS (Network Management System) as well from the CLI.
PR NumberSynopsisCategory: EVPN Layer-2 Forwarding
1669811BUM traffic might be blackholed for ESI configured CE interface flap
Product-Group=junos
On Junos MX/QFX5K/QFX10K platforms and Junos Evolved ACX/MX platforms, on interface up/down event loop prevention might not work resulting in BUM traffic being blackholed.
PR NumberSynopsisCategory: EX Diagnostics Software
1598805The interface on SFP-T or SFP-SX might stop forwarding traffic on EX4600
Product-Group=junos
On EX4600, the interfaces on SFP-T or SFP-SX might stop forwarding traffic when MACSec and auto-negotiation is enabled on the ports. The interfaces would still show as up and the transmit and receive counters will increase. However, the transmit counters on the port will not increase.
PR NumberSynopsisCategory: PR for Lagavuling platform
1613702FPC might crash after device restart in EVPN-VXLAN scenario
Product-Group=junos
On EX or QFX platforms with Ethernet VPN (EVPN) and Virtual Extensible LAN (VxLAN) enabled, FPC(Flexible PIC Concentrator) might crash after the device is restarted. Traffic loss is observed until the FPC is restarted and services are restored.
1653499Additional debug logs may be printed onto device console, when device is booted from a bootable USB
Product-Group=junos
When EX4400 device is booted from a USB image with 22.1R1.8 software, additional debug log messages may be printed onto the console of the EX4400 device.
PR NumberSynopsisCategory: SRX4100/SRX4200 Great Wall
1626562A major alarm DPDK (data plane development kit) Tx stuck issue of SRX4100/4200
Product-Group=junos
On the SRX4100 and SRX4200 platforms, it can detect DPDK (data plane development kit) Tx stuck issue and trigger a major chassis alarm goes which might trigger RG1 failover to the healthy node. A DPDK reset will be triggered only to the stuck port and if the reset resolves the tx stuck issue, the major chassis alarm will go off.
PR NumberSynopsisCategory: Inline Jflow PRs for defect & enhancement requests
1652901The syslog errors and PPE traps might be observed
Product-Group=junos
On MS-MPC/MPC-3D/MPC1/MPC1E/EX9200-40T/EX9200-40F/SRX5K-SPC-4-15-320/SRX5K-MPC/SRX5K-MPC3-100G10G/SRX5K-MPC3-40G10 linecards, syslog errors and PPE(Packet Forwarding Engine) traps might be observed due to exhaustion of NH partition of memory.
PR NumberSynopsisCategory: ISIS routing protocol
1664152The rpd crash might be seen on MX platforms
Product-Group=junos
On Junos platforms supporting SRv6 (Segment Routing), the rpd (routing processor daemon) crash may be observed when there is an update in the LSP (Link State PDU) for IS-IS (Intermediate System-Intermediate System). There might be a service impact because of the rpd crash, however, the system will self-recover to a functional state before the next occurrence.
PR NumberSynopsisCategory: IPSEC/IKE VPN
1665332IPSec tunnels may flap on SRX platforms
Product-Group=junos
On all SRX platforms running the Junos-ike (Internet Key Exchange) package, when the flow trace options are committed, the ikemd process may restart and IPSec tunnels may flap.
PR NumberSynopsisCategory: l2 forwarding on non atlas platforms
1664955MAC addresses learned on the RTG interface are not aging out
Product-Group=junos
On Junos EX/NFX/QFX platforms, stale MAC addresses entry not getting removed for RTG (Redundant trunk groups) interfaces.
PR NumberSynopsisCategory: Issues related to Junos licensing infrastructure
1658913Valid software licenses might not be in sync between members in the Virtual chassis.
Product-Group=junos
Software licenses will now be synced to all members of Virtual chassis. - Warnings and alarm to be seen only on global master member in VC. - show system license. command will be executed only on global master member. - Issue is specific to all MX VC setup for all Junos. For all other members it will display the following message: root@> show system license error: This command can only be used on the master routing engine.
PR NumberSynopsisCategory: lldp sw on MX platform
1669677LLDP neighborship might fail if the chassis-id format of the LLDP packet is xx:xx:xx:88:8e:xx
Product-Group=junos
On all Junos platforms, Link Layer Discovery Protocol (LLDP) neighborship fails if the chassis-id format of the LLDP packet is xx:xx:xx:88:8e:xx.
PR NumberSynopsisCategory: Port-based link layer security services and protocols that a
1660070MACsec session configured over IFD might be down when an IFL configured on IFD is disabled/deactivated
Product-Group=junos
On EX and QFX platforms, in vlan-tagging/flexible-vlan-tagging scenario, when multiple Logical Interfaces (IFLs)(SP-style) are configured on a single Physical Interface (IFD) and MACsec is configured on the same IFD, and when one of the IFL is diabled/deactivated MACsec session will be down.
PR NumberSynopsisCategory: SW PRs for MPC10E Interfaces
1601049Interface flap might trigger major alarm causing disble-pfe action when high priority scheduler is configured
Product-Group=junos
On all Junos platforms with MPC10E line-cards, repeated 100GE interface link flaps may result in loss of traffic going out of the interface. Each 100GE interface down event might not flush the stream and triggers a major alarm causing disable-pfe action. This is specific to interfaces configured with high priority scheduler. MPC11E card is not exposed.
PR NumberSynopsisCategory: Multi Protocol Label Switch Operations, Admin & Maintenance
1634632VCCV BFD session keeps flapping between MX and peer device if ultimate-hop popping is enabled
Product-Group=junos
In Layer 2 circuit/Layer 2 VPN/VPLS environment with ultimate-hop popping enabled for LSP, Bidirectional Forwarding Detection (BFD) for the Pseudowire Virtual Circuit Connectivity Verification (VCCV) session between MX and peer device might flap periodically, due to the MPLS LSP ping sent from peer to MX getting failed.
PR NumberSynopsisCategory: PFE L2
1632565JUNOS:JDI_REGRESSION:PLATFORM:SWITCHING:VC:QFX5110-32Q : Traffic loss seen after renumbering master in VC
Product-Group=junos
Required release note.
PR NumberSynopsisCategory: PRs for PFE EVPN / VxLAN related issues on QFX5K
1665306On QFX5K series platforms, duplicate packets might be seen in the multihomed scenario in an EVPN-VxLAN fabric when unicast ARP packets are received
Product-Group=junos
On QFX5K series platforms, when unicast ARP (Address Resolution Protocol) is received for a MAC address that is already learned in an EVPN-VxLAN (Ethernet VPN-Virtual Extensible LAN) environment, the ARP request is flooded and duplicate packets might be seen on leaf devices. We might see some service impact where split-horizon might not work or continuous mac-move might be seen. This issue is rare and very unlikely to occur in a production environment due to presence of intermediate switches which might resolve the unicast ARP query.
PR NumberSynopsisCategory: QFX5200/5110/5120/5210 Interface related issues. Port up/do
1605037The carrier transition counter might not get incremented upon link flap after the reboot
Product-Group=junos
On all QFX Series switches supporting auto-channelization, after reboot the carrier transition counter does not increment upon link flap.
PR NumberSynopsisCategory: Related to sw defects for K2-RE
1497592Backup Routing Engine reboots because of power cycle or failure when the offline and online operations are performed on CB1
Product-Group=junos
After backup Routing Engine halt, CB1 goes offline and comes back online; this leads to the backup Routing Engine booting up, and it shows the reboot reason as "0x1:power cycle/failure." This issue is only for the RE reboot reason, and there is no other functional impact of this.
PR NumberSynopsisCategory: KRT Queue issues within RPD stuck queue, retries due to erro
1664527The routing process on the device might crash when the IP address of local interface is changed to the IP address of BGP peer
Product-Group=junos
On all Junos and Junos Evolved platforms, the rpd process might crash when the IP address of local interfaces is changed to BGP peer's IP address. When the IP address is changed, Router NH is created. When this route is leaked to another routing instance, flag is set on the same Router NH instead of creating a new one. This leads to rpd crash. Core files are generated and some traffic impact might be seen.
PR NumberSynopsisCategory: MX10003/MX204 MPC defects tracking
1609988MX204: Interface flaps might be observed on certain ports
Product-Group=junos
On MX204 platforms, when QSA(QSFP-to-SFP) adapter is used with any SFP/SFP+(small form-factor pluggable) optics and if interface at PIC0 is configured with 1G speed, the corresponding interface might flaps with the "Ethernet PCS Block Not Locked/Locked Delta Event" error messages leading to traffic fluctuation passing through it.
PR NumberSynopsisCategory: ZT/YT pfe firewall software
1662606Heap memory issues may lead to crash of MPC10/MPC11 line cards on MX platforms
Product-Group=junos
Heap memory leaks may occur on MPC10/MPC11 line cards when processing firewall filter terms. Accumulation of heap memory over time might lead to the crash of the card(s) affected.
PR NumberSynopsisCategory: Trinity LU, IX, QX, MQ chip drivers, ucode & related SW
1631313The packet drop might be seen on FPC on Trio based platforms
Product-Group=junos
On Trio based platforms, when scaled firewall config is frequently changed/added/deleted, traffic drop might be seen on PFE due to incomplete handling of freeing read-only memory.
1651407CCL-DT-BNG: show interface and monitoring interface (ifd level) counters are tripled.
Product-Group=junos
In a subscriber management scenario requiring four subscriber accurate accounting statistics per packet, three stats are handled correctly while the fourth one - ifd stat - is not handled correctly due to this PR. The net effect is only the ifd byte statistic may not be accurate while the ifd packet count is still accurate. Also there is no service or traffic impact due to this issue.
PR NumberSynopsisCategory: Issues related to broadband edge apps (PPP, DHCP) on Trio ch
1647214DHCP Subscriber traffic might get dropped due to the rpf-check filter
Product-Group=junos
On all Junos platforms running BroadBand Edge(BBE) subscribers, when the rpf-check CLI knob is present in the configuration but the Reverse Path Forwarding (RPF) feature is not getting applied to certain subscribers which leads to DHCP subscriber traffic drop.
PR NumberSynopsisCategory: trinity 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.
PR NumberSynopsisCategory: trinity pfe bridging, learning, stp, oam, irb software
1522896Egress traffic loss might happen because of PFE MTU feature problem
Product-Group=junos
On MX and EX9200 serial platforms, under Ethernet VPN (EVPN) environment, packets routed using IRB interface could not be fragmented due to media maximum transmission unit (MTU) problem.
PR NumberSynopsisCategory: Issues related to mgd, DAX API, DDL/ODL infrastructure, Juno
1636085MTU configuration on an interface is not set as expected
Product-Group=junos
On all Junos with persist-groups disabled ( on Junos persist-groups feature is enabled by default 19.4 onwards) and on EVO platforms where persist groups can be disabled (21.4R1 onwards persist-groups cannot be disabled on EVO) this issue can be seen. This issue occurs when grafting happens during configuration expansion (when persist-groups is disabled) and a configuration such as a customer configuration is applied( for example, a configuration in which MTU is inherited from a groups configuration).
PR NumberSynopsisCategory: SW PRs related to Vale development
1599183False fan failure alarm flaps (set and cleared) frequently
Product-Group=junosvae
Fan Trays (FT) on PTX10008/10016 EVO system has implemented dampening with the zero speed failures. The same will be implemented in Junos.
PR NumberSynopsisCategory: PRs related to vmhost platforms
1646339The alarm might not be generated for EDAC errors until the FPC is rebooted
Product-Group=junos
On all MX and PTX platforms, EDAC errors are triggered but alarms are not observed until the FPC gets rebooted due to the data corruption in hardware.
PR NumberSynopsisCategory: Virtual Private LAN Services
1655858The Pseudo Wires might go down in VPLS scenario
Product-Group=junos
On all Junos/Junos Evolved platforms with VPLS (virtual private LAN service) deployed, deactivating and activating the neighbour under the default mesh-group might lead Pseudo Wires(PW) to go down. This happens when there is a change in default mesh-group and that might not be updating the PW status. This can be recovered by deactivating and activating the complete routing instance under the mesh-group.

Modification History

First publication 2022-08-12