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

Junos Software Service Release version 23.2R1-S2 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 23.2R1-S2 is now available.

23.2R1-S2 - List of Fixed issues 

PR NumberSynopsisCategory: EX2300/3400 platform
PR NumberSynopsisCategory: CoS support on ACX
1765486On ACX710/5448 with a hierarchical-scheduler on CE interfaces EVPN ETREE Leaf to LEAF communication is allowed
Product-Group=junos
On ACX710/5448 with hierarchical-scheduler on CE(Customer edge) interfaces EVPN ETREE (Ethernet virtual private network Etree feature) leaf-to-leaf communication is allowed.
PR NumberSynopsisCategory: BBE network stack related issues
1751656ARP learning issue for dynamic ARP entry for the DVLAN stacked frame route not resolved
Product-Group=junos
On MX platforms with Subscriber Management and knob "ipoe-dynamic-arp-enable" configured, the L2 (MAC address) in the frame route will be incorrect due to which traffic flow for VLAN subscribers will get impacted as dynamic ARP entry for the DVLAN (Dynamic VLAN) stacked frame route won't get resolved resulting in ARP learning issue.
PR NumberSynopsisCategory: Border Gateway Protocol
1763095BGP link bandwidth community based load balancing is not working if BGP-PIC is enabled
Product-Group=junos
On all Junos and Junos Evolved T640, T1600, T4000, TX Matrix, TX Matrix Plus, MX5, MX10, MX40, MX80, MX150, MX204, MX240, MX304, MX480, MX960, MX2008, MX2010, MX2020, MX10003, MX10004, MX10008, MX10016, vMX, EX4500, EX9204, EX9208, EX9214, EX9251, EX9253 platforms, when Border Gateway Protocol Prefix-Independent Convergence (BGP-PIC) is enabled, the weighted Equal Cost Multipath (ECMP) does not work as expected.
PR NumberSynopsisCategory: Express Broadway PFE L3
1725716The error logs "fpc0 expr_hostbound_packet_handler: Receive pe 254?" would be generated
Product-Group=junosvae
On QFX10002-60C and PTX10k platforms, an error log can be generated repeatedly with the base configuration.
PR NumberSynopsisCategory: CoS support on DNX
1765478LACP packets are not forwarded after the reboot
Product-Group=junos
On ACX5448 and ACX710 platforms, due to a timing condition when the hierarchical-scheduler is configured on aggregated Ethernet (AE), then Link Aggregation Control Protocol (LACP) packets are not being sent after the chassis reboot.
PR NumberSynopsisCategory: ACX platform interface issues
1747140QSFP interfaces show additional flap during PFE bringup
Product-Group=junos
On Junos ACX5448 platform, the QSFP (Quad Small Form-factor Pluggable) interfaces can possibly see a momentary flap during device or pfe bring up.
PR NumberSynopsisCategory: VPWS, L2 CKT, EVPN-VPWS
PR NumberSynopsisCategory: DNX Multicast
1758659Multicast traffic drop observed when IGMP/MLD snooping is configured with IRB
Product-Group=junos
On all Junos and Junos Evolved platforms with IGMP (Internet Group Management Protocol)/MLD (Multicast Listener Discovery) snooping configured along with IRB, the mcsnoopd daemon crashes when addition, deletion and re-addition of snooping routes are performed rapidly. This impacts the learning of new IGMP/MLD groups by the multicast listeners disrupting multicast traffic.
PR NumberSynopsisCategory: Firewall related development
1743233On all Junos OS Evolved platforms support for a firewall policer rate needs to be increased
Product-Group=junos
On all Junos OS Evolved platforms, the firewall policer rate, Bandwidth limit, committed-information-rate, peak-information-rate, burst-size-limit are increased through this PR.
PR NumberSynopsisCategory: EVPN control plane issues
1739686Evpn-vxlan comp nh is not installed in pfe after peer reboot
Product-Group=junos
Evpn-vxlan comp nh is not installed in pfe after reboot.
1764126Color related LSPs for next-hop will disappear from EVPN routes on mpls.0 routing-table by changing 'fallback none' option in 'transport-class' config.
Product-Group=junos
Service mapping EVPN service gets effected with change in fallback none option at routing-options transport-class name <>. Due to this configuration change EVPN(Ethernet virtual private network) service starts resolving over best effort in route inet.3 instead of classful transport colored rib junos-rti-tc-.inet[6].3. Service mapping with classful transport support added for EVPN service from 23.1.
PR NumberSynopsisCategory: EVPN Layer-2 Forwarding
1743913IRB reachability issues may be observed in the EVPN-VXLAN environment when looped ARP comes on ESI-LAG
Product-Group=junos
On Junos and Junos OS Evolved platforms (except MX platforms) with EVPN-VXLAN (Ethernet VPN - Virtual Extensible LAN) configured, in case of traffic loop conditions, self-generated ARP packets (having physical-IRB MAC as SMAC) may come back to the same node where it originated. Such rare scenarios, when the MAC address of the IRB (Integrated Routing and Bridging) ages out and is cleared from the MAC table, also associated MAC-IP route (IRB route) might get cleaned. This may result in IRB reachability issues as the remote VTEPs (Virtual Tunnel End Point) won't have IRB information of the local VTEP and on the local VTEP, there won't be EVPN database entry and type-2 EVPN advertisements for local IRB towards the remote VTEPs.
PR NumberSynopsisCategory: Express PFE including evpn, vxlan
1750468L3VPN traffic destined for hosts learned over IRB/VXLAN will get dropped on QFX10K platforms
Product-Group=junos
On QFX10K platforms in the DCI (Data Center Interconnect) scenario with EVPN-VXLAN traffic flow traversing over L3VPN, some packet drops will be observed when packets received over L3VPN with VPN label and destined to host learned over IRB/VXLAN tunnel.
PR NumberSynopsisCategory: Express PFE L2 fwding Features
1739258The ksyncd process crash would be seen on backup RE
Product-Group=junos
On QFX10008 and QFX10016 platforms with IRB(Integrated Routing and Bridging), EVPN-VxLAN(Ethernet VPN-Virtual Extensible LAN) and enhanced-arp feature enabled, high availability will be impacted as backup RE(Routing Engine) will remain down due to ksyncd (kernel synchronization process) failure. In case of switchover, if backup become the new master, then traffic drop will happen.
1748500Traffic drop will be observed when Label MPLS traffic egressing out on the IRB interface as IPV4
Product-Group=junos
On QFX10K platforms, Label MPLS (Multiprotocol Label Switching) (labeled-unicast) traffic egressing out on IRB (Integrated routing and bridging) interface as IPV4 traffic can get dropped.
PR NumberSynopsisCategory: ISIS routing protocol
1738222RPD crashes when multiple ISIS processes are configured
Product-Group=junos
On all Junos and Junos Evolved platforms, RPD crash files are seen during the GRES (graceful restart) event as GRES functionlity is not supported in protocol isis-instance <>.
PR NumberSynopsisCategory: Flow Module
1758208Buffer leak when PMI sends out packet on egress interface with MTU smaller than the packet length
Product-Group=junos
On all SRX platforms, when the IPv4/IPv6 packet is larger than MTU of the interface, it leaks the memory buffer.
PR NumberSynopsisCategory: User Firewall related issues
1758332Junos OS: SRX Series and EX Series: Multiple vulnerabilities in J-Web can be combined to allow a preAuth Remote Code Execution
Product-Group=junos
A Missing Authentication for Critical Function vulnerability in Juniper Networks Junos OS on SRX Series and EX Series allows an unauthenticated, network-based attacker to cause limited impact to the file system integrity. Please refer to https://supportportal.juniper.net/JSA72300 [juniper.net] for more information.
PR NumberSynopsisCategory: Key Management Daemon
1728605Crash file is generated when local certificate keychain is missed repeatedly
Product-Group=junos
On all Junos platforms (M/MX series, ACX series, PTX series, SRX series, T series MX-VC) where kmd is set as control plane daemon which is responsible for IPSec (Internet Protocol Security)related operations, a core file is generated due to continuous failures for a certificate request.
PR NumberSynopsisCategory: Layer 2 Control Module
1763053LLDP neighborship will not be formed on all Junos devices
Product-Group=junos
On Junos and Junos OS Evolved platforms, LLDP (Link Layer Discovery protocol) neighborship will not come up on local device if the local device is using Junos version lower than 22.3 and remote device is using Junos version 21.4R3-S2 and its subsequent service releases or version higher than 22.3.
PR NumberSynopsisCategory: FreeBSD Kernel Infrastructure
1691036NTP time drift
Product-Group=junos
NTP time drift on the affected Junos releases. Earlier implementation of kvmclock with vDSO (virtual Dynamic Shared Object) which helps avoid the system call overhead for user space applications had problem of time drift, the latest set of changes takes care of initializing the clock after all auxiliary processors are launched so that the clock initialization is accurate.
1757668Unable to access VC member through console after performing request system halt
Product-Group=junos
On Junos EX4100 platform, Unable to access virtual-chassis(VC) member through console after performing request system halt and fpc goes to "NotPrsnt" state.
PR NumberSynopsisCategory: TCP/UDP transport layer
1761242TCP window scaling may be not applied to the first TCP packet sent to the client after the three-way handshake, leading to unnecessary segmentation.
Product-Group=junos
On all JUNOS platforms, the first TCP packet sent by Junos to the client after the three-way handshake may be unnecessarily segmented due to TCP window scaling option being not applied even if it was negotiated.
PR NumberSynopsisCategory: Protocol Independant Multicast
1720240RPD process crashes on all Junos and Junos OS Evolved platforms after adding static route to the VRF in some scenarios
Product-Group=junos
When static route is added to the VRF (Virtual Routing and Forwarding), and mc-ip (multicast-ip) and the PIM (Protocol Independent Multicast) instance get deleted in some scenarios, the RPD process crash is seen on all Junos and Junos OS Evolved platforms.
PR NumberSynopsisCategory: QFX L3 data-plane/forwarding
1724675Traffic loss will be observed with vlan tagging and/or vlan normalisation in a specific design (using a looped cable)
Product-Group=junos
Upon upgrade to Junos versions (junos:20.3R2, 20.3R3, 20.3X75-D20, 20.4R2, 21.1R1, 21.2R1), network connectivity is lost for traffic requiring vlan normalization and having DMAC one of the switch's MAC addresses. For example, incoming traffic has two vlans (S-vlan, C-vlan) ingressing on an interface and switch uses a looped link to provide routing via an IRB. --- (S-vlan|C-vlan) -- -> SW_X --- C-vlan -- -> SW_X_irb ARP and L2 learning occurs as expected but upon receiving the frame with DMAC of a local interface, switch takes a route lookup action instead of bridging and vlan normalization due to the frame having DMAC as the MAC of one of its interfaces. Hence, the traffic is not sent via looped cable to the L3 interface.
PR NumberSynopsisCategory: QFX EVPN / VxLAN
1738276High convergence time in the EVPN-VxLAN uplink failover scenario
Product-Group=junos
On Junos QFX5K platforms in the EVPN-VxLAN scenario, due to high convergence time, traffic loss is more than expected when the uplink to the spine disabled (CLI initiated uplink failover).
PR NumberSynopsisCategory: RPD Next-hop issues including indirect, CNH, and MCNH
1747992The memory consumption increases due to memory leak
Product-Group=junos
On all Junos and Junos OS Evolved platforms, a continuous memory leak is observed due to an allocated socket memory not being freed. This is a minor leak but can lead to significant memory usage on highly scaled setups leading to performance and functional impact including system crash beyond a certain point.
PR NumberSynopsisCategory: Bug and Review Tracking for Segment routing traffic eng
1737119The traffic blackhole will be observed when the SRTE shortcut is configured
Product-Group=junos
On Junos platforms, when the MPLS (Multiprotocol Label Switching) packet reaches the destination router, it will have a label that is unknown to the destination router due to a label POP operation miss at the ingress router resulting in the traffic black hole in the scenario SR-MPLS (Segment Routing With Multiprotocol Label Switching) + traffic engineering shortcut is configured.
PR NumberSynopsisCategory: SRX branch platforms
1661816fxp0 works under disable state in SRX300
Product-Group=junos
SRX300 runs in HA mode, fxp0 could be unexpectedly UP even though "disable" is configured.
PR NumberSynopsisCategory: SRX5XX platform
1514925Junos OS: An unauthenticated attacker with local access to the device can create a backdoor with root privileges (CVE-2023-44194)
Product-Group=junos
An Incorrect Default Permissions vulnerability in Juniper Networks Junos OS allows an unauthenticated attacker with local access to the device to create a backdoor with root privileges. Please refer to https://supportportal.juniper.net/JSA73158 [juniper.net] for more information.
PR NumberSynopsisCategory: SRX-1RU platfom datapath SW defects
1746567Packet drops observed in SRX4600 with burst traffic
Product-Group=junosvae
On SRX4600 platforms, around 25% traffic drop is observed with burst traffic (~20M pps ARP packets) till the node is restarted.
PR NumberSynopsisCategory: SRX-1RU platfom related protocol, QoS, filtering features et
1737721Junos OS installation using USB can fail on SRX4600
Product-Group=junosvae
On SRX4600 platforms, Junos OS installation using USB can fail due to slow USB detection.
PR NumberSynopsisCategory: Junos Automation, Commit/Op/Event and SLAX
1717425Junos platform device unable to commit configuration in recovery mode
Product-Group=junos
On all Junos platforms where snapshot is supported, when a device is rebooted from recovery mode it fails to commit configuration due to problems with slax import and device might go into amnesiac mode due commit fail.
PR NumberSynopsisCategory: Ephemeral Database
1751141Load replace via XML NetConf will not work
Product-Group=junos
On all Junos and Junos OS Evolved platforms, the load replace operation through XML NetConf will fail.
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1740289The 'load replace' operation might result in mustd and mgd crash
Product-Group=junos
On Junos and Junos Evolved platforms with 'apply-group' configured, the mustd and mgd processes might crash when the 'load replace' operation is performed. When this happens, 'apply-groups' will get deleted internally and the respective hierarchies will not be notified.
1741413The mgd process will crash due to stack overflow on high scale address configuration
Product-Group=junos
On all Junos and Junos OS Evolved platforms with high scaled addresses (360000 global address-book and above) configured over device, mgd (Management Daemon) crash is seen due to stack overflow when whole global address-book configuration is deleted and also while finding the entries of global address-book for a possible completion of CLI command.
1772201unexpected commit error - error: VLAN-ID must be specified on tagged ethernet interfaces
Product-Group=junos
unexpected commit error like 'error: VLAN-ID must be specified on tagged ethernet interfaces', due to 'commit check' reset internal flag incorrectly after load overide configuration in rare condition.
PR NumberSynopsisCategory: QFX RCB issues
1763588Warn if insufficient space to save unbundled packages during vm image upgrade
Product-Group=junos
If while preparing for replacement of a vm image, there is insufficient space to save copies of unbundled packages, issue a warning.
PR NumberSynopsisCategory: usf flow and datapath issue on SPC3
1750634Traffic transfer/receive is impacted for SPC3 CPU cores connected to the affected PCIe bus when the SPC3 card boots up
Product-Group=junos
On MX and SRX platforms with SPC3 card, SPC3 (Services Processing Card 3) CPU cores connected to the affected PCIe (Peripheral Component Interconnect) bus (7 CPU cores) getting into a bad state will not transfer any traffic i.e. traffic loss during SPC3 card bootup due to incorrect register settings.
 
 

23.2R1-S2 - List of Known issues 

PR NumberSynopsisCategory: EX2300/3400 PFE
1647209DHCP traffic might be dropped when DHCP-security and RTG are enabled
Product-Group=junos
On EX2300, EX2300-48MP, and EX3400 platforms, when DHCP-security and Redundant Trunk Group (RTG) are enabled clients connected over RTG might not get DHCP IP and DHCP traffic might be dropped.

Resolved In: junos:20.2R3-S6 junos:20.4R3-S4 junos:21.1R3-S4 junos:21.2R3-S3 junos:21.3R3-S2 junos:21.4R3 junos:21.4R3-S3 junos:22.1R3 junos:22.2R2 junos:22.2R3-S3 junos:22.3R1 junos:22.4R1
PR NumberSynopsisCategory: EX2300/3400 platform
1580560On EX2300, EX3400, :EX4300-48MP and EX4300 , Pause frames counters does not get incremented when pause frames are sent.
Product-Group=junos
On EX2300, EX3400, :EX4300-48MP and EX4300 , Pause frames counters does not get incremented when pause frames are sent.

Resolved In:
PR NumberSynopsisCategory: NFX Series Platform Software
1675919NFX350 :: JDI_REGRESSION:PLATFORM:SWITCHING:JDM:: Core "localhost.libvirtMib_suba.15909.1656455866.core.tgz" is seen on NFX-350 boxes
Product-Group=junos
NFX350 :: JDI_REGRESSION:PLATFORM:SWITCHING:JDM:: Core "localhost.libvirtMib_suba.15909.1656455866.core.tgz" is seen on NFX-350 boxes

Resolved In:
PR NumberSynopsisCategory: SRX Gen-3 RE, leveraged from Point Success Mt.Rainier
1774760RE switchover observed in SRX5K platforms when ethernet switchports failure scenario on SCB
Product-Group=junos
On SRX5K platforms when all ethernet switch ports on Switch Control Board(SCB) fail, it triggers the Routing Engine (RE) switch over and RE0 is stuck in "Disabled" state. As RE0 is disabled and RE1 does have the functionality to coordinate chassis. No PIC will turn up which were failed and triggered the failover and traffic impact will be there for those particular ports and the complete service impact will be there if RE1 had any issue when RE0 is in disable state. RE0 did not recover by its own from the disabled state until manual reboot is done.

Resolved In: junos:21.4R3-S6 junos:22.3R3-S2 junos:22.4R3-S1 junos:23.2R2 junos:23.4R1 junos:23.4R2
PR NumberSynopsisCategory: SPC3 HW and SW Issues
1749584SRX device will take time to come up in HA or device will go down in standalone setup
Product-Group=junos
For SRX Platforms with SPC3 cards in cluster configuration, One of the node in cluster will go down as FPC(Flexible PIC Concentrators) takes extra time to reset. In standalone setup, device will go down.

Resolved In: junos:21.4R3-S5 junos:22.1R3-S4 junos:22.2R3-S3 junos:22.3R3-S2 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1 junos:23.3R2 junos:23.4R1
PR NumberSynopsisCategory: ACX Services feature
1633395Delegated BFD sessions configured on routing-instance may fail to come up
Product-Group=junos
On ACX5448 and ACX710 platforms, all types of delegated BFD sessions configured on routing-instance other than the default routing-instance might not come up.

Resolved In: evo:22.4R3-EVO evo:23.1R1-EVO junos:21.4R3-S3 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R1 junos:23.1R2 junos:23.2R2 junos:23.3R1 junos:23.3R2 junos:23.4R1
PR NumberSynopsisCategory: a20a40 specific issue
1775880A flowd crash is observed if CP receives the packets due to some hardware memory issue
Product-Group=junos
On SRX5K platforms with SPC3 and SPC2 cards, flowd crash will be observed if CP (Central Point) receives the packets due to some hardware memory issue either on IOC (I/O card) or SPC (Services Processing Card) which requires session lookup.

Resolved In: junos:21.4R3-S6 junos:22.3R3-S2 junos:22.4R3-S1 junos:23.2R2 junos:23.4R1 junos:23.4R2
PR NumberSynopsisCategory: PFE issue for flowd on australia SPU
1727027The datapath-debug packet-dump feature is not capturing the transit traffic packets
Product-Group=junos
On SRX5000 platforms with IOC3 card (SRX5K-MPC3-100G10G and SRX5K-MPC3-40G10G), datapath-debug packet-dump will stop capturing the transit traffic packets when datapath-debug packet filters with packet-dump are targeting the traffic on the interface which is configured with firewall filters.

Resolved In: junos:20.4R3-S9 junos:21.2R3-S7 junos:22.2R3-S3 junos:22.3R3-S2 junos:23.2R2 junos:23.3R2 junos:23.4R1
PR NumberSynopsisCategory: MX304 interface specific 
17652001G single interface do not need setting of number-of-subport 1 on MX304
Product-Group=junos
Starting from 23.1, MX304 supports 1G interfaces. But when configuring a single unchannelized 1G interface, number-of-subports should not be specified. The interface will not come up if it is set.

Resolved In:
PR NumberSynopsisCategory: Platform PR for 1G/10G LC
1739595The FPC will core and crash in a race condition
Product-Group=junos
On all Junos and Junos Evolved platforms, in a rare scenario, the FPC will go down due to core.

Resolved In: evo:22.3R3-S1-EVO evo:22.4R3-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:21.4R3-S5 junos:22.2R3-S3 junos:22.3R3-S1 junos:22.4R3 junos:23.2R2 junos:23.3R1 junos:23.4R1
PR NumberSynopsisCategory: CoS support on DNX
1704589Traffic drops seen after making COS configuration change on ACX710
Product-Group=junos
On Junos ACX710 platforms, when CoS (Class-of-Service) scheduler changes are done for buffer usage and when traffic is flowing which involves bursty traffic, traffic drops are seen.

Resolved In: junos:21.2R3-S6 junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
1770491JUNOS_REG: ACX5448-M : While validating traffic convergence, traffic loss is more than expected.
Product-Group=junos
For FRR local repair functionality with unilist of unicast next hops( LSP with link protection) does not work when the link is recovered after a failover, there is a mismatch in the unilist next hop entry between Kernel and PFE.

Resolved In:
PR NumberSynopsisCategory: DNX Multicast
1758659Multicast traffic drop observed when IGMP/MLD snooping is configured with IRB
Product-Group=junos
On all Junos and Junos Evolved platforms with IGMP (Internet Group Management Protocol)/MLD (Multicast Listener Discovery) snooping configured along with IRB, the mcsnoopd daemon crashes when addition, deletion and re-addition of snooping routes are performed rapidly. This impacts the learning of new IGMP/MLD groups by the multicast listeners disrupting multicast traffic.

Resolved In: evo:22.4R3-EVO evo:23.2R1-S2-EVO evo:23.2R2-EVO evo:23.3R2-EVO evo:23.4R1-EVO evo:24.1R1-EVO junos:22.4R3 junos:22.4R3-S1 junos:23.2R2 junos:23.3R2 junos:23.4R1
PR NumberSynopsisCategory: Firewall related development
1743233On all Junos OS Evolved platforms support for a firewall policer rate needs to be increased
Product-Group=junos
On all Junos OS Evolved platforms, the firewall policer rate, Bandwidth limit, committed-information-rate, peak-information-rate, burst-size-limit are increased through this PR.

Resolved In: evo:23.2R1-S2-EVO evo:23.4R1-EVO junos:23.4R1
PR NumberSynopsisCategory: Express PFE L2 fwding Features
1746435QFX10002-60c port et-0/0/30 part of a lag is dropping peer ARP reply after configuring a GRE tunnel
Product-Group=junos
GRE IFL configuration was changing the physical port's igport attributes in IGP.

Resolved In: junos:21.2R3-S7 junos:21.4R3-S5 junos:22.1R3-S4 junos:22.2R3-S3 junos:22.3R3-S1 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1 junos:23.4R1
PR NumberSynopsisCategory: SRX4100/SRX4200 platform software
1761668False SNMP traps for power supply unit failure generated on SRX4100 and SRX4200 platforms
Product-Group=junosvae
On SRX4100/SRX4200 platforms, false SNMP traps for power supply unit failure generated as instability with the transmission in the hardware.

Resolved In: junos:21.2R3-S7 junos:21.4R3-S6 junos:22.1R3-S5 junos:22.2R3-S3 junos:22.3R3-S2 junos:22.4R3-S1 junos:23.2R2 junos:23.3R2 junos:23.4R1
PR NumberSynopsisCategory: High Availability/NSRP/VRRP
1736498In SRX MNHA cluster setup the RSI takes long time to generate
Product-Group=junos
In SRX MNHA cluster setup the RSI takes long time to generate on the MNHA backup node. The RSI includes the command "show security flow session session-state warm" which will collect all the sessions in warm state on the MNHA backup node - this output can be extensive and RSI is being generated an extended period of time, in known instances this was 1-2 hours.

Resolved In: junos:21.4R3-S5 junos:21.4R3-S6 junos:22.1R3-S4 junos:22.1R3-S5 junos:22.1R3-S6 junos:22.3R3 junos:22.3R3-S1 junos:22.3R3-S2 junos:22.3R3-S3 junos:22.4R2-S1 junos:22.4R3 junos:22.4R3-S1 junos:23.1R2 junos:23.2R2 junos:23.3R1 junos:23.4R1
PR NumberSynopsisCategory: SW PRs for MPC10E Chassisd
1775368An error will be observed while configuring HCOS resulting in COS not being applied to subscribers leading to traffic shaping not working
Product-Group=junos
On MX platforms with MPC10E, MPC11E, LC9600, and MX304-LMIC16 in the Subscriber-Management scenario, COS (Class-of-Service) will not be applied to subscribers leading to traffic shaping not working i.e. may result in slowness and packet drops due to the saturation of the link. The issue happens when configuring "set chassis fpc 3 pic 2 tunnel-services bandwidth 250g" and "hierarchical-scheduler" on the LT (Logical Trunnel) interface in separate commits.

Resolved In: evo:23.4R2-EVO evo:24.1R1-EVO junos:23.2R1-S1-J4 junos:23.2R2 junos:23.4R2
PR NumberSynopsisCategory: Multiprotocol Label Switching
1773796The LSP name and bandwidth values are displayed continuously in "show mpls lsp autobandwidth name X" command
Product-Group=junos
In "show mpls lsp autobandwidth name X" command when the name of the Link State Packet (LSP) is greater than 21 characters, the first column with LSP name and the second column with the Last bandwidth are merged.

Resolved In: evo:23.4R2-EVO evo:24.1R1-EVO junos:22.2R3-S3 junos:22.3R3-S2 junos:23.2R2 junos:23.4R2
PR NumberSynopsisCategory: QFX L2 PFE
1711860The dcpfe process will crash due to memory fragmentation
Product-Group=junos
On Junos and Junos OS Evolved platforms, the dcpfe (Dense Concentrator Packet Forwarding Engine) process crash will be observed due to memory fragmentation issue. This is a very rare case and would impact traffic as due to dcpfe failure the PFE restarts, so the interfaces will flap.

Resolved In: evo:23.4R1-EVO junos:23.4R1
PR NumberSynopsisCategory: PTX10K specific platform PRs
1735224Junos OS Evolved: PTX10001, PTX10004, PTX10008, PTX10016: MAC address validation bypass vulnerability (CVE-2023-44190)
Product-Group=junos
An Origin Validation vulnerability in MAC address validation of Juniper Networks Junos OS Evolved on PTX10001, PTX10004, PTX10008, and PTX10016 devices allows a network-adjacent attacker to bypass MAC address checking, allowing MAC addresses not intended to reach the adjacent LAN to be forwarded to the downstream network. Due to this issue, the router will start forwarding traffic if a valid route is present in forwarding-table, causing a loop and congestion in the downstream layer-2 domain connected to the device. Please refer to https://supportportal.juniper.net/JSA73154 [juniper.net] for more information.

Resolved In: evo:20.4X6-EVO evo:21.4R3-S5-EVO evo:22.1R3-S4-EVO evo:22.3R2-S2-EVO evo:22.3R3-S1-EVO evo:22.3X50-EVO evo:22.3X80-D35-EVO evo:22.3X80-D36-EVO evo:22.3X80-D37-EVO evo:22.4R2-S1-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-S1-EVO evo:23.2R2-EVO evo:23.3R1-EVO junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
PR NumberSynopsisCategory: SRX branch platforms
1658968The DNS information is getting lost when IPCP flaps
Product-Group=junos
On all SRX-branch series platforms working as a PPPoE (Point-to-Point Protocol over Ethernet) client and a DHCP (Dynamic Host Configuration Protocol) server, DNS (Domain Name System) information is getting lost, for which the DHCP client won't receive DHCP information and DNS packets will not get resolved to result in the packet drops. This issue happens when the IPCP (Internet Protocol Control Protocol) source address is not getting copied and IPCP is getting flapped due to the interface (DHCP interface) being flapped.

Resolved In: junos:20.4R3-S8 junos:21.2R3-S6 junos:21.3R3-S5 junos:21.4R3-S5 junos:22.1R3-S4 junos:22.2R3-S2 junos:22.3R3-S1 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1 junos:23.4R1
1714620High latency will be observed while pinging to peer device
Product-Group=junos
On Branch SRX Platforms, The delay will be observed while pinging to peer device due to high latency when VLAN(Virtual Local Area Network) tagged DHCP(Dynamic Host Configuration Protocol) packets arrive at IRB (Integrated Routing and Bridging) interface.

Resolved In: junos:21.2R3-S7 junos:21.3R3-S5 junos:21.4R3-S5 junos:22.1R3-S4 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1 junos:23.4R1
1715247Interface speed stays 100Mbps when removing speed and duplex command separately
Product-Group=junos
On SRX branch series, when the interface speed is set to 100Mbps and the link-mode is set to full-duplex, the interface speed remains at 100Mbps even the speed and duplex commands are removed separately.

Resolved In: junos:20.4R3-S8 junos:21.2R3-S6 junos:21.3R3-S5 junos:21.4R3-S6 junos:22.1R3-S4 junos:22.2R3-S2 junos:22.3R3-S1 junos:22.4R3 junos:23.2R2 junos:23.3R1 junos:23.4R1
1738271"Minor Autorecovery information needs to be saved" alarm is not displayed after zeroize
Product-Group=junos
On SRX Branch platform, "Minor Autorecovery information needs to be saved" alarm is not displayed after running zeroize command

Resolved In: junos:20.4R3-S8 junos:22.2R3-S3 junos:22.3R3-S2 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1 junos:23.4R1
1739520Random physical interfaces doesn't come up after a reboot
Product-Group=junos
On SRX345, some interface ports couldn't able to get correct medium (FIBRE or COPPER) sometimes after multiple reboot due to that SFP optics inserted may not come up after a reboot.

Resolved In: junos:21.2R3-S7 junos:21.4R3-S6 junos:22.1R3-S5 junos:22.2R3-S3 junos:22.3R3-S2 junos:22.4R3 junos:23.2R2 junos:23.4R1
1744108Commit panic reboot observed after implementing system processes watchdog timeout 180 on SRX hardware platforms
Product-Group=junos
On SRX hardware platforms, configuring set system processes watchdog related command causes commit panic reboot. Watchdog related commands are unsupported on SRX hardware platforms.

Resolved In: junos:22.1R3-S4 junos:22.2R3-S2 junos:22.3R3-S1 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1 junos:23.4R1
1746202Kernel CPU temperature becomes high and the flowd process crashes with dual VLAN tag configured
Product-Group=junos
On all SR3xx platforms having Q-in-Q tunnelling on VPLS (Virtual Private Local Area Network Service) over GRE (Generic Routing Encapsulation) tunnel, it is seen that due to dual VLAN (Virtual Local Area Network) tag configuration, the kernel CPU (Central Processing Unit) temperature becomes high along with the flowd process getting crashed.

Resolved In: junos:21.4R3-S6 junos:22.2R3-S3 junos:22.3R3-S2 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1 junos:23.4R1
1768050ARP resolution does not work if generated from the L3 Interface such as the IRB interface
Product-Group=junos
On SRX300 series platforms, ARP (Address Resolution Protocol) resolution does not work if it is generated internally from the L3 (Layer 3) interface such as the IRB (Integrated Routing and Bridging) interface. The routing protocol connections will not get established resulting in traffic impact.

Resolved In: junos:21.2R3-S7 junos:21.3R3-S5 junos:21.4R3-S6 junos:22.1R3-S5 junos:22.4R3 junos:23.2R2 junos:23.3R2 junos:23.4R1
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 junos:21.4R3-S5 junos:22.2R3-S3 junos:22.3R3-S2 junos:22.4R3 junos:23.2R2 junos:23.3R1
PR NumberSynopsisCategory: SRX-1RU platfom related protocol, QoS, filtering features et
1729284L2 channel error counter increases when unknown family packets received by interfaces
Product-Group=junos
On SRX4600 and SRX5K platforms, the L2 channel error counter will increase when some unknown family packets received by interfaces.

Resolved In: junos:21.2R3-S6 junos:21.3R3-S5 junos:21.4R3-S5 junos:22.1R3-S3 junos:22.2R3-S2 junos:22.3R3 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
1748971SRX4600 misleading Fan speed syslog output after removing or inserting one Fan tray unit
Product-Group=junos
On SRX4600, misleading Fan speed syslog is generated after removing or inserting one Fan tray unit.

Resolved In: junos:20.4R3-S9 junos:21.2R3-S7 junos:21.4R3-S6 junos:22.2R3-S3 junos:22.3R3-S2 junos:22.4R3-S1 junos:23.2R2 junos:23.3R2 junos:23.4R1
PR NumberSynopsisCategory: ZT/YT pfe infra issues
1697215Stoppage of statistics update on MPC10E
Product-Group=junos
We have seen the stoppage of statistics update on MPC10E cards running older releases. Please note that this issue affects only the statistics update with no impact on forwarding or connectivity. This issue is seen very rarely, and we don't know the exact trigger yet. A couple of occurrences seem to point at link flaps as trigger but not conclusive. We think this may be due to a data race condition and the changes in this PR address a potential issue.

Resolved In: evo:22.2R3-EVO evo:22.3R2-EVO evo:22.4R2-EVO evo:23.1R1-EVO junos:20.3X75-D46 junos:20.4R3-S8 junos:21.2R3-S4 junos:21.4R3-S2 junos:22.2R3 junos:22.3R2 junos:22.4R1 junos:22.4R2 junos:23.1R1
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1771991RSI is more than 3.7 GB
Product-Group=junos
The CLI command output of "show system processes extensive" should not have an 'srd' entry on PTX.

Resolved In: evo:23.4R2-EVO evo:24.1R1-EVO junos:22.2R3-S3 junos:22.3R3-S2 junos:22.4R3 junos:23.2R2 junos:23.4R2
PR NumberSynopsisCategory: VMHOST platforms software
1772127After device reboot Swap memory is not displayed in the CLI command output of "show system processes extensive"
Product-Group=junos
On the Junos PTX10008 and PTX10016 platforms, Swap memory is not getting displayed in the CLI command output of "show system processes extensive". The Swap partition is deleted for certain conditions on the Junos side and the external swap partition is not getting created during the boot-up, hence this issue is happening. The issue can be avoided temporarily using a workaround method until reboots. A permanent issue fix is provided for PTX10008 & PTX10016 in the latest release.

Resolved In: junos:22.2R3-S3 junos:22.3R3-S2 junos:22.4R3 junos:23.2R2 junos:23.4R2

Modification History

First Publication 2024-01-02