Alert Type
SRN - Software Release Notification
Risk
Risk Description
Low/Notification
Software Release Notification
Impact
Impact Description
Low/Notification
Software Release Notification
Product Affected
ACX, EX, MX, PTX, QFX, NFX, QFX, VMX, SRX, and VSRX platforms
Alert Description
Junos Software Service Release version 22.4R2-S1 is now available for download from the Junos software download site
Download Junos Software Service Release:
Go to
Junos Platforms - Download Software page
Input your product in the "Find a Product" search box
From the Type/OS drop-down menu, select
Junos SR
From the Version drop-down menu, select your version
Click the Software tab
Select the Install Package as need and follow the prompts
Solution
Junos Software service Release version 22.4R2-S1 is now available.
22.4R2-S1 - List of Fixed issues
PR Number
Synopsis
Category: Border Gateway Protocol
1705938
The BGP sessions will flap after the RE switchover
Product-Group=junos
On all Junos and Junos OS Evolved platforms with dual RE (Routing Engine) or VC (Virtual Chassis) with NSR enabled scenarios, in some rare BGP scaled scenarios upon RE switchover the new Master RE will send out a route refresh message to all the peers, which is not expected. This will eventually lead to the BGP session flap.
1712527
The PE advertises incorrect next-hop towards CE although BGP export policy configured with next-hop under policy-statement
Product-Group=junos
The show route advertising-protocol bgp reporting nexthop self rather than IP in the configured policy-statement for next-hop.
1739919
Junos OS and Junos OS Evolved: A BGP session will flap upon receipt of a specific, optional transitive attribute (CVE-2023-0026)
Product-Group=junos
An Improper Input Validation vulnerability in the Routing Protocol Daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an unauthenticated, network-based attacker to cause a Denial of Service (DoS). Please refer to https://supportportal.juniper.net/
JSA71542
[juniper.net]
for more details.
PR Number
Synopsis
Category: L2NG Access Security feature
1724933
On certain Junos EX and QFX platforms the static ARP entries for DHCP-security are not present
Product-Group=junos
On certain Junos EX series switches, the static MAC (Media Access Control) bindings are not present in certain conditions. This issue will be seen when the static DHCP (Dynamic Host Configuration Protocol)-security ARP(Address Resolution Protocol) bindings are moved from an interface having a higher interface number to an interface with a lower interface number. Due to the binding not happening, there will be impact on the traffic. The workaround when such a binding change is done is to restart the DHCP services after the configuration is committed.
PR Number
Synopsis
Category: Device Configuration Daemon
1742124
DCD crash can be seen sometimes while pushing config using API
Product-Group=junos
DCD crash can be seen when interface config is added using API and some Junos application (such as vrrpd, jdhcpd etc) add config for the same interface using Overlay files. This is because, in DCD the internal data structures are not updated correctly when config source is changed from API to Overlay which eventually leads to corruption.
PR Number
Synopsis
Category: EX4100 RE, Platform Infra, Drivers
1722674
EX4100-24MP does not set invalid "Power Class" value in Power Via MDI
Product-Group=junos
EX4100-24MP does not set invalid "Power Class" value in Power Via MDI
PR Number
Synopsis
Category: EX4400 PFE software
1682960
fxpc daemon core is observed on Junos EX4400 platforms in a Virtual chassis setup with HGoE mode
Product-Group=junos
On Junos EX4400 platforms with a Virtual Chassis(VC) setup and operating in a HiGig over Ethernet (HGoE) mode, Packet Forwarding Engine manager (fxpc) daemon core is observed when there is CPU-generated burst traffic. Due to this core, the Packet Forwarding Engine(PFE) will be restarted and traffic through it will be impacted.
1716902
IGMP/MLD queries may get dropped if received on a port on the backup VC member when IGMP/MLD snooping is enabled
Product-Group=junos
On Junos QFX and EX in the VC (Virtual Chassis) scenario, when the switch is acting as pure L2 (Layer 2), and forwarding IGMP (Internet Group Management Protocol)/MLD (Multicast Listener Discovery) query as transit traffic, if IGMP/MLD snooping is enabled then IGMP/MLD queries may get dropped if received on a port on the backup VC member resulting in IGMP/MLD groups to expire.
1718316
The fxpc daemon crash is observed on Junos EX4400 platforms in a Virtual chassis setup with HGoE mode
Product-Group=junos
On Junos EX4400 platforms with a Virtual Chassis(VC) setup and operating in a HiGig over Ethernet (HGoE) mode, the Packet Forwarding Engine manager (fxpc) daemon crash is observed when reload of switch or switchover happens. Due to this crash, the Packet Forwarding Engine(PFE) will be restarted and traffic through it will be impacted.
1731522
The traffic drop will be observed after changing the VSTP VLAN configuration
Product-Group=junos
On Junos EX4400, EX4100, EX2300, EX3400, and QFX5K platforms, traffic drop would happen on RSTP (Rapid Spanning Tree Protocol) enabled port attached to a VLAN (Virtual Local Area Network) when the same VLAN has VSTP (VLAN Spanning Tree Protocol) enabled on a different port and there is a configuration change done on VSTP for that VLAN.
1731548
The fxpc process crashes when the next hop information is not properly maintained in the PFE table
Product-Group=junos
On Junos EX series deployed as a virtual chassis, post switchover/GRES (Graceful Routing Engine Switchover), next hop information for Type 5 route fluctuates which leads to invalid entries in the PFE (Packet Forward Engine) table and causes the fxpc (Packet Forwarding Engine Manager) process to crash.
1732271
Filter term dropping VRRP traffic when "then log" is configured
Product-Group=junos
On all Junos platforms, VRRP (Virtual Router Redundancy Protocol) packet goes to a wrong CPU queue when filter is added to match VRRP packet with "then log" action, resulting in VRRP functionality impact.
1733365
Error logs are seen with a non-vxlan dot1x enabled port
Product-Group=junos
In a heaviliy loaded system in a specific scenario (Dot1x in multiple supplicant mode & dynamic vlan from radius server & non vxlan access port) following log message may be captured in the syslog - {brcm_as_dot1x_vxlan_set_mac_learning_mode:1168 dot1x bd_get failed for bd index 0}. This log is not impacting any funtionality.
1738384
The 'input-vlan-map push' operation will not work on double-tagged frames
Product-Group=junos
On EX4400 platforms, when 'input-vlan-map push' is configured to push an outer VLAN (Virtual Local Area Network) tag on to a double-tagged frame, the egressing frame will be tagged incorrectly. Instead of a push operation, the outer VLAN tag of the ingressing double-tagged frame will be swapped and sent out. This results in unexpected behaviour or traffic loss as the Ethernet frames will not have the expected VLAN tag information.
PR Number
Synopsis
Category: EX4400 platform
1700309
EX4400: pps counter does not show correct values for jubmo frames
Product-Group=junos
When packets of size bigger than 1518 Bytes are received/transmitted, pps counter value does not show correct value.
1710793
The link does not come up after PIC offline and online operation
Product-Group=junos
On EX4400 platforms running Junos OS, the link does not come up after PIC (Physical Interface Card) offline and online operation is performed, either through CLI or after physical PIC removal and insertion , when 1G optics is used on a 4x10G PIC module.
1719509
RSTP default configuration is missing when zeroize is performed
Product-Group=junos
On Junos EX4400 device, if more than one EX4400 uplink port is connected to another EX4400 uplink port, then with the default factory config there will be a switching loop. This could impact the Zero Touch Provisioning (ZTP) of the device over uplink ports due to a risk of encountering Mac-learning race conditions or loops. If multiple such devices (that are zeroized) are in a VLAN, that could cause unpredictable results for traffic being forwarded.
1720074
Port will be down when "no-auto-negotiation" is configured on EX4400-48F platform
Product-Group=junos
On EX4400-48F platform with Small Form Factor Pluggable 100Base-FX Fast Ethernet Optics, when "no-auto-negotiation" is configured on the interface this results in the interface not coming back online even after deleting "no-auto-negotiation" in interface.
1720257
EX4400 shows incorrect interface et-0/0/0
Product-Group=junos
On EX4400-48MP/EX4400-24MP pic 0 port 0 ifd ( Interface device) would be incorrect due to set chassis fpc <> pic <> port <> speed <> configuration.
1728725
EX4400 VC: During upgrade/reboot , fxpc core may be seen in a very rare race condition
Product-Group=junos
issues aren't always seen. test cases are pre-provisioned and pfe planned restart conditions are randomly seen due to race conditions. System will auto recover after dcpfe core.
1731345
EX4400: Some log messages may get flooded in heavily loaded system.
Product-Group=junos
In rare scenarios in a heavily loaded system when syslog level is set to all, following log messages may get flooded - { ifinfo[72742]: PVIDB: Attribute 'ifinfo.pad_to_minimum_frame_size' not present in Db}. Recommendation is not to set syslog level to all.
1747128
EX4400: PoE stops working after the reboot
Product-Group=junos
The switch might intermittently stop delivering power on the POE enabled ports after a reboot.
PR Number
Synopsis
Category: PFE EVPN / VxLAN related issues on EX platforms
1727112
Programming of native-vlan-id on the interface fails and MAC is not learned
Product-Group=junos
On all EX4400 and EX4100 devices in virtual-chassis (VC) deployed, in EVPN-VXLAN (Ethernet Virtual Private Network - Virtual Extensible LAN) scenario, with native-vlan-id configured on the interface, MAC (Media Access Control) address is not learned.
PR Number
Synopsis
Category: EX POE
1713545
The LLDP negotiation response is not sent back to PD when perpetual Power over Ethernet (PoE) is enabled on EX4400
Product-Group=junos
On the EX4400 platform, perpetual Power over Ethernet (PoE) is enabled, and when a device is connected to more than 10 Link Layer Discovery Protocol (LLDP) Power Devices (PD) and PD restarted while perpetual PoE is enabled, the LLDP negotiation response is not sent back to PD.
1716261
EX4100MP (PSE) does not allocate a power value requested in LLDP by the PD
Product-Group=junos
EX4100MP may allocate a power 0.1w less than the one PD requested. For example, when PD requests the power 19.4W in LLDP, EX4100 will allocate 19.3W to PD.
1743547
EX Series: Removal of notice about the availability of new POE firmware and the prompt to upgrade the same
Product-Group=junos
When there is newer POE firmware version available in the Junos Software, "show poe controller" command output displays the availability details to upgrade
1744343
Enhancement of PoE Controller Firmware upgrade procedure
Product-Group=junos
PoE firmware upgrade gets stuck in an incompatible controller scenario leading to POE not working.
1745088
Enhancement of PoE controller firmware files into Junos Software
Product-Group=junos
Junos Software version package does not have sufficient PoE firmware files, leading to incompatible firmware version upgrade
PR Number
Synopsis
Category: ISIS routing protocol
1725686
Unnecessary SPF calculation is causing high CPU utilization
Product-Group=junos
On all Junos and Junos Evolved platforms, very frequent SPF (Shortest Path First) calculation, being caused by leaking multiple prefixes across the IS-IS areas, is causing high CPU utilization.
PR Number
Synopsis
Category: jdhcpd daemon
1742696
Address allocation for DHCP client will fail if 'force-discover' configuration is enabled on client
Product-Group=junos
Junos based platforms operating as DHCP-client with 'force-discover' knob enabled, will get stuck in requesting state when DHCP-Server is not responding. Client will face login failure and thus traffic would be impacted.
PR Number
Synopsis
Category: High Availability/NSRP/VRRP
1736498
In 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.
PR Number
Synopsis
Category: FreeBSD Kernel Infrastructure
1712855
Unicast packets are received on the management interface even though the destination MAC is not local
Product-Group=junos
On all platforms supporting em driver for their ethernet interface, promiscuous mode is enabled by default and hence traffic storm is noticed on the management interface.
PR Number
Synopsis
Category: OSPF routing protocol
1737978
EX4100 : OSPFv3 irb's are not coming up in both aggregation device with metro config
Product-Group=junos
OSPFv3 may not form adjacencies on IRB interfaces with VRRP configuration.
PR Number
Synopsis
Category: Phone-Home-Client Infrastructure
1687926
Unable to onboard the VC members after performing ZTP due to the phone-home process sending a blank in the device serial number field while connecting to the redirect server
Product-Group=junos
When EX4100/EX4400 devices are first powered on, the Zero Touch Provisioning (ZTP) by phone home will provision the devices. In rare situations where the powered devices are already connected with Virtual Chassis Port (VCP) cables to form a Virtual Chassis (VC), the ZTP using the phone home will keep retrying to connect the redirect server and unable to onboard VC because of the blank serial number sent by the phone home due to the memory corruption.
1736982
Phone-Home redirect config missing for EX4650 after zeroize
Product-Group=junosvae
Phone-Home redirect config missing for EX4650 after zeroize
PR Number
Synopsis
Category: QFX L3 data-plane/forwarding
1704489
High CPU utilization causes a latency/slowness issue on QFX platforms
Product-Group=junos
On QFX5110 and QFX5120 platforms, latency or slowness issue is observed when the traffic is passing through a layer 3 interface configured with just family inet/family inet6 due to unwarranted MAC lookup. This could lead to traffic loss on that interface.
PR Number
Synopsis
Category: QFX EVPN / VxLAN
1688323
Traffic loss is observed in IP fabric when there is a change in the underlay network
Product-Group=junos
On Junos QFX5K series, EX4400 platforms, configuration-change/protocol flapping/port flapping in Ethernet Virtual private network (EVPN) Virtual Extensible LAN (VXLAN) can cause traffic loss (changes related to the underlay network).
PR Number
Synopsis
Category: KRT Queue issues within RPD
1721032
Local route is not added in the secondary FIB on all Junos SRX platforms and routes will be permanently stuck in KRT queue
Product-Group=junos
On all Junos SRX platforms when ST (Secure-Tunnel) interface with P2MP (Point-to-Multipoint) is configured and interface routes are leaked via RIB-group (Routing Information Base), local route of the ST interface will not be leaked into forwarding-table of the secondary-RIB and it will be stuck in the KRT (Kernel Routing Table) queue.
PR Number
Synopsis
Category: RPD API infrastructure
1715907
After the device reboots with lpm(longest prefix match) profile configured, the default route entry is getting created on ipv4 and ipv6 (pfe hw lpm) due to gRIBI routing instance and same route is removed after the interface flap.
Product-Group=junos
The multi topology table:gribi.inet6.0 is always created when rib service is being instantiated. Since this is a dynamic table, if we do a config commit and the rpd infra module sees that the table is not being used, the dynamic table will be reclaimed (deleted) by the infra module. To prevent the rpd infra module from reclaiming the table, create a dummy route entry in :gribi.inet6.0.
PR Number
Synopsis
Category: SNMP Infrastructure (snmpd, mib2d)
1734549
Syslog messages modification for SNMPv3 authentication failure
Product-Group=junos
On all Junos and Junos Evolved platforms, a cosmetic change was made to an existing syslog message to print more information. The syslog error message that is logged when a user with wrong auth/privacy password sends a SNMP v3 request to router has been changed to add more information. From: LIBJSNMP_NS_LOG_WARNING: WARNING: Authentication failed for To: LIBJSNMP_NS_LOG_WARNING: WARNING: Authentication failed for , SNMPv3 query from to
PR Number
Synopsis
Category: Trio pfe qos software
1736890
The CoS rewrite rules will not be working in the EVPN with IRB scenario
Product-Group=junos
On Junos platforms, the Class of Service(CoS) rewrite rules are not working in Ethernet Virtual Private Network(EVPN) with integrated routing and bridging (IRB) scenarios. The packets will not be overwritten as per the rewrite rules and traffic forwarding through an IRB interface will not be working as expected.
PR Number
Synopsis
Category: Trio pfe l3 forwarding issues
1700203
DHCP offer requests are dropped while routed towards different VRFs of transit router
Product-Group=junos
On all Junos platforms with route leaking and no-snoop configuration, DHCP (Dynamic Host Configuration Protocol) offer requests could be dropped while traversed to different VRFs (Virtual Routing and Forwarding) from default RI (Routing Instance).
PR Number
Synopsis
Category: UI Infrastructure - mgd, DAX API, DDL/ODL
1730336
The rpd crashes and the commit operation fails while pushing a large configuration with the "extend-size" knob enabled
Product-Group=junos
On all Junos platforms, when the 'extend-size' knob is configured and a scaled configuration is committed, the rpd daemon crash is seen and the commit operation fails.
22.4R2-S1 - List of Known issues
PR Number
Synopsis
Category: MX Platform SW - FRU Management
1739922
FPC crashes and remains offline after the upgrade of RE BIOS to 0.15.1 version
Product-Group=junos
On MX204 and EX9251 platforms running Junos 21.4 or later, the Flexible PIC Concentrator (FPC) crashes and will remain offline after upgrading the RE (Routing Engine) BIOS to 0.15.1 version without power cycling the chassis. This will result in total traffic loss.
Resolved In:
junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
PR Number
Synopsis
Category: Firewall related development
1720389
Commit error will not be seen after deactivating routing-instance applied under firewall filter
Product-Group=junos
On Junos OS Evolved platforms with enabled firewall filter, deactivating routing-instance which is already applied under the firewall filter, will not show any commit error after commit is issued. This can be seen occasionally and might impact control plane traffic.
Resolved In:
evo:21.4R3-S4-EVO evo:22.1R3-S3-EVO evo:22.2R3-S1-EVO evo:22.3R3-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R1-S1-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.3R1-EVO junos:21.4R3-S4 junos:22.2R3-S1 junos:22.3R3 junos:22.4R2 junos:22.4R3 junos:23.1R1-S1 junos:23.1R2 junos:23.2R1 junos:23.3R1
PR Number
Synopsis
Category: Kernel software for AE/AS/Container
1724298
PS interface remains up while LT or RLT interface is down
Product-Group=junos
On all Junos MX platforms , PS (Pseudowire Subscriber) interface remains up while LT (Logical Interface) or RLT (Redundant Logical Tunnel) interface is brought down by disabling PFE (Packet Forwarding Engine) which will cause traffic black-holing.
Resolved In:
evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO evo:23.4R1-EVO junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
PR Number
Synopsis
Category: ISIS routing protocol
1725686
Unnecessary SPF calculation is causing high CPU utilization
Product-Group=junos
On all Junos and Junos Evolved platforms, very frequent SPF (Shortest Path First) calculation, being caused by leaking multiple prefixes across the IS-IS areas, is causing high CPU utilization.
Resolved In:
evo:21.2R3-S6-EVO evo:21.4R3-S4-EVO evo:22.1R3-S4-EVO evo:22.2R3-S2-EVO evo:22.4R2-S1-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R1-EVO evo:23.2R2-EVO evo:23.3R1-EVO junos:20.4R3-S7-J2 junos:20.4R3-S8 junos:21.2R3-S6 junos:22.1R3-S4 junos:22.2R3-S2 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1
PR Number
Synopsis
Category: jdhcpd daemon
1743611
DNS received through DHCP is lost after a commit and not able to ping internet
Product-Group=junos
If name-server information is changed via CLI after the DHCP subscribers are up, DNS obtained from DHCP server is overwritten by local config. This may result in DNS look up failures in some cases.
Resolved In:
PR Number
Synopsis
Category: Security platform jweb support
1698386
Junos OS: J-Web: Multiple Vulnerabilities in PHP software
Product-Group=junos
PHP software included with Junos OS J-Web has been updated from 7.4.30 to 8.2.0 to resolve multiple vulnerabilities. Please refer to https://supportportal.juniper.net/
JSA71653
[juniper.net]
for more information.
Resolved In:
evo:23.2R1-EVO evo:23.3R1-EVO junos:23.2R1 junos:23.3R1
PR Number
Synopsis
Category: Multiprotocol Label Switching
1698889
The rpd process will crash when rpd is restarted
Product-Group=junos
On all Junos and Junos OS Evolved platforms, when MPLS (Multiprotocol Label Switching) statistics is configured without LSP (Label-Switched Path) configuration, the rpd process will crash and impact the routing protocols. This leads to traffic disruption due to the loss of routing information.
Resolved In:
evo:22.3R3-EVO evo:22.4R3-EVO evo:23.1R1-EVO evo:23.1R2-EVO evo:23.2R1-EVO junos:21.2R3-S6 junos:22.1R3-S3 junos:22.2R3-S1 junos:22.3R3 junos:22.4R3 junos:23.1R1 junos:23.1R2 junos:23.2R1
PR Number
Synopsis
Category: FreeBSD Kernel Infrastructure
1718048
junos-ike optional package failed to install on 22.4R1-S1
Product-Group=junos
IKED is failing to install on NFX250 devices when using request vmhost software add optional junos-ike.tgz
Resolved In:
PR Number
Synopsis
Category: "ifstate" infrastructure
1735685
Control plane flap, data drop, unexpected behavior of PFE or device is observed when file storage is impacted in a continuous ksyncd process crash scenario
Product-Group=junos
On all Junos platforms configured with GRES (Graceful Routing Engine Switchover), file storage in the system will get affected when the ksyncd process crashes continuously and result in control plane flap, data drop or unexpected behavior of PFE (Packet Forwarding Engine) or device.
Resolved In:
junos:22.1R3-S4 junos:22.2R3-S2 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
PR Number
Synopsis
Category: QFX L2 PFE
1730076
Packets received on a port that is in "LACP Detached" state is getting forwarded
Product-Group=junos
On all Junos EX46xx/QFX5k (except QFX5100) platforms, child links that are in LACP (Link Aggregation Control Protocol) detached state are up and accepting incoming traffic, expecting it to drop.
Resolved In:
junos:21.2R3-S6 junos:22.1R3-S4 junos:22.2R3-S2 junos:22.3R2-S2 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
PR Number
Synopsis
Category: QFX10008/16 QFX10002 Ultimat/Elit platform related issues -
1734734
Online SIBs will go down due to a faulty SIB that triggers spmbpfe crash
Product-Group=junos
On all Junos QFX10K and PTX platforms, due to initialization failure of a faulty Switch Interface Board (SIB) in the device, the Switch Processor Mezzanine Board status (SPMB) process will crash and online SIBs will go down.
Resolved In:
junos:20.3X75-D36 junos:22.1R3-S4 junos:22.2R3-S2 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1
1742186
SPMB process will crash and PICS will not come online
Product-Group=junos
On Junos QFX10K platforms, if any bad SFBs (Switch Fabric Board) are present in the system. Any faulty SIB can cause all PIC to go down due to the Switch Processor Mezzanine Board (SPMB) core. The SPMB process will crash and PICS will not come online. Traffic cannot flow through line card.
Resolved In:
junos:20.3X75-D36 junos:22.1R3-S4 junos:22.2R3-S2 junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1
PR Number
Synopsis
Category: RPD Next-hop issues including indirect, CNH, and MCNH
1699773
MFT: RPD may restart during Multi-Feature-Test with BGP-MP, L3VPN/L2VPN, over RSVP/LDP transport, as well as colored SRTE, and SRv6 tunnel transport along with BGP CT.
Product-Group=junos
During BGP MP route 9.0.0.2 re-resolution window, a corner case was hit, such that rpd will assert and restart. This error case is observed during Multi-Feature-Test with BGP-MP, L3VPN/L2VPN, over RSVP/LDP transport, as well as colored SRTE, and SRv6 tunnel transport along with BGP CT. This issue will get resolved in next 22.4R1 services releases.
Resolved In:
PR Number
Synopsis
Category: Resource Reservation Protocol
1723229
The rpd process crash is observed when RSVP LSP at Juniper transit/ingress router receives RESV message with RESVCONF object in multi vendor deployment
Product-Group=junos
On all Junos and Junos OS Evolved platforms (For QFX5100, only in Virtual Chassis-VC setup) with RSVP (Resource Reservation Protocol) LSP (Label-Switched Path) configured in multi vendor deployment and Juniper router is acting as a transit/ingress router and RESV (Reservation Request) message is received with RESVCONF object from other vendors, rpd process crash will be observed.
Resolved In:
evo:22.1R3-S4-EVO evo:22.2R3-S2-EVO evo:22.3R3-S1-EVO evo:22.4R2-EVO evo:22.4R3-EVO evo:23.1R2-EVO evo:23.2R2-EVO evo:23.3R1-EVO junos:22.1R3-S4 junos:22.2R3-S2 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
PR Number
Synopsis
Category: RPD API infrastructure
1715907
After the device reboots with lpm(longest prefix match) profile configured, the default route entry is getting created on ipv4 and ipv6 (pfe hw lpm) due to gRIBI routing instance and same route is removed after the interface flap.
Product-Group=junos
The multi topology table:gribi.inet6.0 is always created when rib service is being instantiated. Since this is a dynamic table, if we do a config commit and the rpd infra module sees that the table is not being used, the dynamic table will be reclaimed (deleted) by the infra module. To prevent the rpd infra module from reclaiming the table, create a dummy route entry in :gribi.inet6.0.
Resolved In:
evo:22.4R2-S1-EVO junos:22.4R3 junos:23.1R2 junos:23.2R1 junos:23.2R2 junos:23.3R1
PR Number
Synopsis
Category: ZT/YT pfe firewall software
1718893
There are some BGP peers that remain down due to a firewall filter attached to the interface lo0
Product-Group=junos
On specific line cards and devices, fast-lookup-filter is not working on the router's loopback interface. Some BGP peers remain down with a firewall filter attached to the lo0 interface.
Resolved In:
PR Number
Synopsis
Category: Issues related to broadband edge apps (PPP, DHCP) on Trio ch
1722945
PADT response will not be sent for an incoming PPPoE/PPP data Packet from an unknown session ID
Product-Group=junos
On all MX platforms with line cards before MPC10, when Broadband Network Gateway (BNG) switchover occurs, the new master does not send PPPoE Active Discovery Termination (PADT) packet for an unknown session if the incoming packet is PPPoE/PPP data packet and thus the existing subscribers does not come up on this router.
Resolved In:
junos:21.3R3-S5 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
PR Number
Synopsis
Category: Issues related to YANG Data Models
1725934
ODL controller is throwing unavailable capabilities error for few of the Openconfig Yang modules
Product-Group=junos
ODL controller is throwing unavailable capabilities error for few of the Openconfig Yang modules
Resolved In:
evo:23.2R1-EVO evo:23.3R1-EVO junos:23.3R1
PR Number
Synopsis
Category: VMHOST platforms software
1726621
Root user is unable to login using public key authentication after reboot or upgrade
Product-Group=junos
On all EX92XX series platforms with NG-RE running Junos OS 21.4R1 or higher releases, the root user is unable to login using public key authentication (RSA Keys) after reboot or upgrade and prompts for a password even when password less authentication is configured.
Resolved In:
junos:22.1R3-S4 junos:22.4R3 junos:23.1R2 junos:23.2R2 junos:23.3R1
Modification History
First publication 2023-07-28
22.4R2-S1: Software Release Notification for JUNOS Software