Alert Type

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

Product Affected

ACX EX MX NFX PTX QFX SRX vSRX platforms running Junos software

Alert Description

Junos Software Service Release version 22.4R3-S5 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

NOTE: Starting on August 30th, 2024, we include PR's severity with each entry. See KB86335 [juniper.net] for the definition of PR's Severity

Solution

Junos Software service Release version 22.4R3-S5 is now available.

22.4R3-S5 - List of Fixed issues

PR NumberSynopsisCategory: EX4100 Hardware
1822363Intermittent alarms related to fan overspeed value can be observed on EX4100 platform
Product-Group=junos
Severity=Major		On Junos EX4100 platform, intermittent alarms can occur regarding fan overspeed on the FPCs if they exceed the predefined fan speed threshold. These alarms are regularly activated and deactivated whenever the fan speed crosses the threshold and subsequently falls back below it. There is no service impact due to this
PR NumberSynopsisCategory: "agentd" software daemon
1817267The latest GNMI specification decrements the streaming of float_val types. Instead double_val type should be streamed.
Product-Group=junos
Severity=Major		GNMI telemetry streaming of Decimal64 data types should stream double_val types instead of float_val types. GNMI has decremented the use of float_val and Decimal64 types in favor of double_val types for floating point data.
PR NumberSynopsisCategory: Border Gateway Protocol
1756603RPD process crash is seen on high scale peering scenario where the sessions are un-configured/shutdown abruptly
Product-Group=junos
Severity=Minor		The RPD process crashes on all Junos and Junos OS Evolved platforms in a highly scaled scenario of more than 2000 BGP peers if the BGP sessions are un-configured/brought down abruptly. This leads to loss of routing information and will lead to loss of protocol traffic.
1778879Junos OS and Junos OS Evolved: Receipt of malformed BGP path attributes leads to a memory leak (CVE-2024-39549)
Product-Group=junos
Severity=Critical		A Missing Release of Memory after Effective Lifetime vulnerability in the routing process daemon (rpd) of Juniper Networks Junos OS and Junos OS Evolved allows an attacker to send a malformed BGP Path attribute update which allocates memory used to log the bad path attribute. This memory is not properly freed in all circumstances, leading to a Denial of Service (DoS). Please refer to https://supportportal.juniper.net/JSA83011 [juniper.net] for more information.
1807504BGP multipath selects wrong interface with "Multiple Single-Hop EBGP sessions on different links using the same IPv6 Link-Local Address"
Product-Group=junos
Severity=Major		On Junos and Junos Evolved Platforms having BGP (Border Gateway Protocol) Multipath when "Multiple Single-Hop EBGP Sessions on different links using the same IPv6 (Internet Protocol Version 6) Link-Local Address" as over multiple links and one of those links is down, the next-hop information which has the smallest IFL (Logical Interface) index interface will get deleted. Since RIB (Routing Information Base) and FIB (Forwarding Information Base) are not correct network traffic will be lost when one of the peer device is down.
1811862Improper maximum value for limit-bandwidth of policy-statement
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms limit-bandwidth of policy-statement can only be configured to maximum value 4.2G (4294967295) which is not large enough based on actual maximum capacity. user@router# set policy-options policy-statement test then limit-bandwidth ? Possible completions: Limit advertised aggregate outbound link bandwidth (0...4294967295)
1826686Traffic impact due to BGP route stuck in hidden state
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms, with BMP (BGP Monitoring Protocol) 'exclude-non-eligible' configured, the BGP route gets stuck in a hidden state with the next hop state as 'Next hop type unusable' leading to traffic drop.
PR NumberSynopsisCategory: Track PRs in BGP BMP area & is part of BGP inside RPD.
1776453BMP does not come up after switchover when configured with sharding and NSR
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved Dual RE platforms, After switchover, BMP does not come up when configured with sharding and NSR enabled.
1807892A route stuck inA route can get stuck in
PR NumberSynopsisCategory: QFX Access Control related
1826621After "deactivating protocol dot1x" and activating it again, the dot1x authentication will not work for ports in single/single-secure supplicant mode
Product-Group=junos
Severity=Major		On all Junos and Junos OS Evolved platforms configured with a dot1x authentication in single/single-secure supplicant mode, client authentication fails when the dot1x protocol is deactivated and activated back while having active authenticated sessions with Dynamic VLAN and VOIP (Voice Over IP).
1830067The dot1x client does not get authenticated and gets stuck in the connecting state when a new dot1x profile is assigned along with a newly created VLAN
Product-Group=junos
Severity=Major		On all Junos and Junos OS Evolved platforms configured with a dot1x authentication, when a dot1x client is authenticated in single/single-secure supplicant mode with dynamic VLAN and later if a new dot1x profile is assigned along with a newly created VLAN, the dot1x client does not get authenticated and gets stuck in the connecting state. The users will be stuck in a connecting state and will not be able to authenticate hence losing access to the network.
PR NumberSynopsisCategory: EVPN Layer-2 Forwarding
1807084The VXLAN traffic drop could be seen after modifying control-word in an EVPN instance
Product-Group=junos
Severity=Major		On MX, QFX and PTX10K line of routers running Junos and Junos OS Evolved with static Virtual Extensible LAN (VXLAN), the Virtual Tunnel Endpoint (VTEP) connections may not work properly after enabling or disabling control-word in the EVPN instance. This could disrupt the connectivity provided by the static VXLAN setup and affect data traffic.
PR NumberSynopsisCategory: Issues related to EX MACsec
1830395Commit error on using more than 31 characters authentication-key-chain-name
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms, when authentication-key-chain-name is configured with more than 31 characters, commit error is seen due to which MACSEC will not work with the configuration.
PR NumberSynopsisCategory: Express PFE FW Features
1819643The Flowspec filters with packet length>2 length ranges showing installed with errors
Product-Group=junos
Severity=Major		On configuring the Flow-spec filters with packet length greater than two, should be throwing an error as unsupported configuration. Instead it showing an installation error logs.
PR NumberSynopsisCategory: Express PFE including evpn, vxlan
1814387The traffic loss is observed if both L3 unicast and VTEP next hop are used to reach same destination
Product-Group=junos
Severity=Major		In the EVPN-VXLAN (Ethernet VPN-Virtual Extensible LAN) scenario on Junos QFX10K platforms, if the Layer 3 unicast and VTEP (VXLAN Tunnel Endpoint) next hops are both enabled for the same destination, traffic drop will be observed.
PR NumberSynopsisCategory: Category for Gamora interfaces software (ACX7332 & ACX7348)
1742772IFD does not not come up whenever optics is removed and inserted on all Junos OS Evolved platforms
Product-Group=junos
Severity=Major		On all Junos OS Evolved platforms and on MX304 platform whenever jack-out/Jack-in of optics is performed , it is observed that the link/ Interface Device (IFD) goes down disturbing traffic on the network.
PR NumberSynopsisCategory: MX Inline Jflow
1798466With scaled routes and flex-flow-sizing configured memory exhaustion will lead to an FPC crash
Product-Group=junos
Severity=Major		On all Junos MX platforms with LC(Linecard) MPC (Modular Port Concentrator)4-9 installed, the Linecard crash can be seen in the corner case. This issue will be seen when Jflow is configured with the inline-services flex-flow-sizing enabled and 'flow-table-size' near the total capacity is configured. There will be a traffic impact due to the crash.
PR NumberSynopsisCategory: IoT data filtering/streaming
1830246The PFE crash is observed on SRX platforms on dynamic-filter configuration
Product-Group=junos
Severity=Major		On SRX platforms when the dynamic filter is configured, the packet forwarding engine (PFE) crashes, impacting traffic.
PR NumberSynopsisCategory: ISIS routing protocol
1777702The rpd process crashes after multiple iterations of disable/enable ISIS protocol
Product-Group=junos
Severity=Minor		On all Junos and Junos Evolved platforms, the rpd process crashes after disabling/enabling the ISIS (Intermediate System-to-Intermediate System) protocol using the set command. The issue is seen after 2-3 hours of continuous disabling, and enabling the ISIS process with a 90-sec interval.
PR NumberSynopsisCategory: IPSEC/IKE VPN
1818197The srxpfe process will crash due to memory buffer corruption if the outgoing interface of the IPsec VPN peer goes down and the default route points to st0
Product-Group=junos
Severity=Major		On SRX platforms, if the outgoing interface of the Internet Protocol Security (IPsec) Virtual Private Network (VPN) peer goes down when the peer device operates in the Network Address Translation-Traversal (NAT-T) environment and the default route points to the secure tunnel interface (st0), there are chances of an internal routing loop which will lead a srxpfe process crash caused by the Memory Buffer (mbuf) corruption.
PR NumberSynopsisCategory: Security platform jweb support
1766378J-Web UI cannot be launched
Product-Group=junos
Severity=Major		On all SRX platforms, while displaying the configured login message from Command Line Interface (CLI), the newline characters will be added which results in parsing error. Hence J-Web UI cannot be launched.
PR NumberSynopsisCategory: Key Management Daemon
1781993Memory leak is observed on MX series platforms that run kmd process
Product-Group=junos
Severity=Major		On all MX series platforms that support MS-MPC/MS-MIC cards, memory leak is observed on kmd (Key Management Deamon) process when IPSec VPN is configured with DiffieHellman group24. The issue is not seen on platforms that support iked process. Memory leak causes incorrect outputs for CLI ipsec/ike show commands and over time kmd might crash when reach its maximum memory, creating a core-dump and resulting in ipsec/vpn going down.
PR NumberSynopsisCategory: Layer 2 VPN related issues
1807853ISIS packets over 1500 bytes sent to L2VPN over MPLS are not being processed
Product-Group=junos
Severity=Major		On SRX-branch series platforms, due to incorrect mbuf (Memory Buffer) allocation, the ISIS (Intermediate System-to-Intermediate System) packets transiting over L2VPN (Layer 2 Virtual Private Network) over MPLS (Multiprotocol Label Switching) are dropped if is more than 1500 bytes. The issue happens when jumbo frames is enabled or the MTU is configured above 1514.
PR NumberSynopsisCategory: Layer2 forwarding on EX/NTF/PTX/QFX
1822911Aggregated ethernet interface flaps can be seen when IRB interface is activated or deactivated
Product-Group=junos
Severity=Major		On all Junos platforms configured in EVPN (Ethernet Virtual Private Network) scenario with AE (Aggregated Ethernet) interface and esi "auto-derive type-3-system-mac" knob, if an IRB (Integrated Routing and Bridging) interface is activated or deactivated the link aggregation interfaces ( IFL) will get flapped due to which interface traffic gets impacted.
1824739The traffic is getting duplicated when VPLS to EVPN transition is performed
Product-Group=junos
Severity=Major		On platforms with MPC10, MPC11, LC9600 and MX304-LMIC line cards, during a transition from VPLS (Virtual Private LAN Services) to EVPN (Ethernet Virtual Private Network) or when the MAC (Media Access Control Address) addresses move from a local to a remote state, control MAC addresses are incorrectly programmed in the hardware, leading to traffic duplication and unresolved destination errors.
PR NumberSynopsisCategory: Label Distribution Protocol
1817712MPLS LDP sessions are not established when container-lsp is configured with an already existing lsp-template
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms Label Distribution Protocol (LDP) sessions are not formed due to the configuration of "container-lsp" with an already existing configured lsp-template which has "ldp-tunneling" knob enabled.
PR NumberSynopsisCategory: Issues related to Junos licensing infrastructure
1737035BGP sessions flap due to license updates
Product-Group=junos
Severity=Minor		On all Junos platforms, a BGP flap is observed when a license key is upgraded or a new license is added resulting in traffic loss.
PR NumberSynopsisCategory: Port-based link layer security services and protocols that a
1757100Memory leak observed in AFTd-Trio daemon in PFE with IFL based MACSEC enabled on MX platforms with MPC11/LC2301/LC9600 line cards and MX304-LMIC16
Product-Group=junos
Severity=Major		On all Junos MX platforms with MPC11/LC2301/LC9600 line cards and MX304-LMIC16, the statistics for MACSEC (MAC Security) are not displayed properly and lead to memory not getting freed. In a scaled environment of IFLs with MACSEC configured, eventually leads to AFTd-Trio daemon crash due to memory exhaustion.
PR NumberSynopsisCategory: Multiprotocol Label Switching
1744584Traffic loss will be observed whenever a soft preemption reroute request arrives
Product-Group=junos
Severity=Major		On all Junos and Junos OS Evolved platforms, whenever a soft preemption reroute request arrives in the middle of the ongoing make-before-break, traffic loss would be observed which is still referring to the old instance.
1814358LSP keep retrying over the transit router marked as "overload" resulting in traffic drops or using the suboptimal path for the LSP
Product-Group=junos
Severity=Major		On Junos and Junos Evolved platforms with RSVP-TE (Reservation Protocol-Traffic Engineering) configured, when IGP (Interior Gateway Protocol) "overload" is configured on the transit router, the traffic should move away from the transit router. But in the issue scenario, the LSP (Label Switched Path) continues to stay across the transit router which has been marked as overload and traffic continues across the transit router resulting in traffic drops or using the suboptimal path for the LSP. The issue happens when Patherr is received for the re-optimized path and CSPF (Constrained Shortest Path First) computation is triggered before the backoff timer.
PR NumberSynopsisCategory: Track Mt Rainier RE platform software issues
1778324The FPC connection times out and reboots post mastership switchover
Product-Group=junos
Severity=Major		On Junos MX and PTX with VMHost MT-RE (NG-RE), when the RE<->CB link down triggers the Routing Engine (RE) switchover, the switchover will be successful but Flexible PIC Concentrators (FPC) will not reconnect to the new master RE. The FPCs reboot and then connect to the new master RE automatically.
PR NumberSynopsisCategory: "ifstate" infrastructure
1780149EX4100 - JUNOS High CPU due to L2ALD
Product-Group=junos
Severity=Major		Under unusual circumstances L2ALD process may get stuck in an infinite loop leading to high CPU, this is not a timing issue.
PR NumberSynopsisCategory: Express Chip L3 software
1827286PTX10008, PTX10002-60C, or QFX10002-60C platforms might not send back icmpv4/v6 reply packets with icmp ddos configuration.
Product-Group=junos
Severity=Major		PTX10008, PTX10002-60C, or QFX10002-60C platforms might not send back ICMPv4/v6 reply packets properly due to defects leading to misprogramming of hardware. Ping with v4/v6 from other device to the PTX10008, PTX10002-60C, or QFX10002-60C platform may fail.
PR NumberSynopsisCategory: Express Paradise PFE Sflow
1803542PTX10008 - Recurring logs -ppcfpc-multi-svcs.elf: FDB :: Ipv4 route operation 2 failed. Rt_index 1801
Product-Group=junos
Severity=Major		Recurring logs -ppcfpc-multi-svcs.elf: FDB :: Ipv4 route operation 2 failed. Rt_index are seen in PTX10008 after upgrade
PR NumberSynopsisCategory: Phone-Home-Client Infrastructure
1828735EX4400-48MP ping rapid count with high values stops when phone-home is configured
Product-Group=junos
Severity=Major		As PHC is expected to be run before onboarding, it is assumed, no user would run "ping" in CLI. So as a cleanup mechanism, the PHC script which is part of the factory default configuration kills all ping processes before it can check connectivity with its gateway.
PR NumberSynopsisCategory: QFX MPLS PFE
1830828Junos QFX5K configured with l2circuit stops forwarding traffic on IFD with vlan-ccc encapsulation subunit when deleting or adding one of the IFLs
Product-Group=junos
Severity=Major		On Junos QFX5K platforms with l2circuit configuration, forwarding traffic on all IFD (Physical Interface) with vlan-ccc encapsulation subunit is stopped when deleting or adding one of the IFLs (Logical Interfaces).
PR NumberSynopsisCategory: QFX5K JUNOS Interface, MACSec, Optics, SDK, PHY
1757704JUNOS_REG: QFX5110-48S : "mge" interface is going down after performing soft OIR
Product-Group=junos
Severity=Major		this is an issue with SOFT OIR, which is used for internal debugging purposes.
PR NumberSynopsisCategory: KRT Queue issues within RPD
1805427The rpd process crashes during rpd restart on Junos and Junos Evolved platforms
Product-Group=junos
Severity=Major		On all Junos platforms, due to timing issue during the restart of the rpd process may cause it to crash. This can temporarily impacts traffic until the process recovers.
1810622The rpd process crash is seen when a malformed AS PATH is received related to changes in BGP.
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms, the Routing Protocol Daemon (rpd) process crashes resulting in a core dump when a malformed AS PATH is received related to changes in Border Gateway Protocol (BGP). The problem was triggered by issue related to memory allocation.
PR NumberSynopsisCategory: RPD Next-hop issues including indirect, CNH, and MCNH
1808463CPU utilization of the rpd process stays high on all Junos and Junos OS Evolved platforms
Product-Group=junos
Severity=Major		On all Junos and Junos OS Evolved platforms in a corner case, the Routing Protocol Daemon (rpd) CPU utilization will be seen high in scenarios where recursive route resolution is involved. The rpd process will be continuously spinning in the re-resolution job which could impact scheduling of other jobs and re-resolution of other routes impacting traffic.
PR NumberSynopsisCategory: RPD policy options
1795263Performance degrades when learning BGP routes with communities
Product-Group=junos
Severity=Major		On all Junos and Junos OS Evolved platforms, degraded performance occurs when BGP routes with communities are learned.
PR NumberSynopsisCategory: RPD route tables, resolver, routing instances, static routes
1812124The rpd process crash is observed when the label received exceeds the configured maximum-labels 16
Product-Group=junos
Severity=Major		On Junos and Junos Evolved platforms, the rpd process crash is observed on both REs (Routing Engines) and RE switchover was triggered when maximum-labels under MPLS(Multi Protocol Label System) address family is configured as 16 and an extra label is received.
PR NumberSynopsisCategory: show route table commands, tracing, and syslog facilities
1812009The rpd process crash is observed when there are catastrophic changes under the particular routing instance configuration
Product-Group=junos
Severity=Major		On all Junos and Junos OS Evolved platforms, when there is any catastrophic changes made in the configuration without deactivating a particular routing instance will lead to the rpd process crash.
PR NumberSynopsisCategory: Resource Reservation Protocol
1819948LSP re-optimization issue has been observed
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms, the LSP (Label Switched Path) re-optimization issue has been observed. LSP bandwidth change is unsuccessful due to bandwidth unavailable RSVP (Resource Reservation Protocol) PathErr.
PR NumberSynopsisCategory: Bug and Review Tracking for Segment routing traffic eng
1820791Per-Segment-list telemetry for colored tunnel doesn't work
Product-Group=junos
Severity=Major		Per-Segment-list telemetry for colored tunnel doesn't work on PTX-Series platform with Junos OS Evolved such as PTX10004, PTX10003, PTX10001, but it works on PTX10008 and PTX10016.
PR NumberSynopsisCategory: SRX branch platforms
1811858Monitored-Status keeps Up after CTL link down in branch model SRX HA
Product-Group=junos
Severity=Major		After CTL link down, Monitored-Status in "show chassis cluster interfaces" keeps showing "Up" state.
PR NumberSynopsisCategory: MX10003/MX204 Platform SW - Chassisd s/w defects
1818517Fan Tray Outer Fan running at over speed alarm is reporting after upgrade
Product-Group=junosvae
Severity=Major		For MX10003 fan min and max threshold were -40 and +20 set. If fan RPM goes below/beyond those RPM, s/w start raising alarms. Similarly for MX204 fan min and max threshold were -20 and +20 set. On log analyzing, its seen FAN RPM was running +34% , that was beyond ma threshold. After discussing with h/w team, min & max threshold values are now decided -40 and +40. Due to this FAN RPM will be in bandwidth and no alarm will be seen.
PR NumberSynopsisCategory: SRX-1RU platfom related protocol, QoS, filtering features et
1819376The 1G interface might be down after upgradation on SRX4600 platform
Product-Group=junos
Severity=Major		On SRX4600 platform, upgrading from any earlier release to Junos 23.2R2 or later whether via ISSU (in-service software upgrade) or a standard upgrade process can cause the 1G interfaces to go down when the speed is changed from 10G to 1G. As a result, the port fails to activate properly at 1G, remaining down and unable to transmit any traffic.
PR NumberSynopsisCategory: Issues related to broadband edge apps (PPP, DHCP) on ZT/YT
1814341The aftd process crash is seen on certain MX platforms with subscriber management enabled
Product-Group=junos
Severity=Major		On MX platforms with MPC10/11/LC9600 and MX304 platforms with subscriber management enabled, the aftd process crash is seen. The line card reboots due to crash and subscribers will be logged off.
1827261Memory leak is observed in aftd-trio process with PPPoE subscriber login/logout activity
Product-Group=junos
Severity=Major		Memory leak is observed in aftd-trio process with PPPoE subscriber login/logout activity
PR NumberSynopsisCategory: Authentication, Authorization, Accounting, PAM (RADIUS/tacplus)
1802329Multiple Products: RADIUS protocol susceptible to forgery attacks (Blast-RADIUS) (CVE-2024-3596)
Product-Group=junos
Severity=Major		An Authentication Bypass by Spoofing vulnerability in the RADIUS protocol of Juniper Networks Junos OS and Junos OS Evolved platforms allows an on-path attacker between a RADIUS server and a RADIUS client to bypass authentication when RADIUS authentication is in use. Please refer to https://supportportal.juniper.net/JSA88210 [juniper.net] for more information.
PR NumberSynopsisCategory: Configuration mgmt, ffp, load-action, commit processing
1818692Configuration commit fails due to mustd process crash
Product-Group=junos
Severity=Major		Core dumps in mustd seen commiting a change to a large prefix-list used by BGP
PR NumberSynopsisCategory: UI Infrastructure - mgd, DAX API, DDL/ODL
1825728The mgd process crashes while using an FQDN in conjunction with the ephemeral configuration database
Product-Group=junos
Severity=Critical		On all Junos and Junos Evolved platforms, the mgd process crashes when device has an ephemeral configuration database instance and an FQDN (Fully Qualified Domain Name) is used for NTP (Network Time Protocol), radius-server, tacplus-server, etc. in either the main static configuration or the ephemeral configuration database.
PR NumberSynopsisCategory: Issues related to NETCONF
1800859Configuration push to device using RPC resulted in incorrect policy order
Product-Group=junos
Severity=Major		On all Junos and Junos OS Evolved platforms, RPC command with default-operation replace uses load update instead of load override from Junos 21.1 onwards. Policies could get incorrectly reordered impacting traffic, because load update does not honor the replace: tag present in configuration file loaded.
1819656In all Junos and Junos OS Evolved platforms, with Multinode High Availability configured, node configuration on primary might differ from backup due to configuration synchronization failure at the time of commit
Product-Group=junos
Severity=Major		In all Junos and Junos OS Evolved platforms with MNHA (Multinode High Availability) supported and "set system commit peers-synchronize" is configured in a local primary node of the HA, when the "commit" command is issued, a synchronization warning message is displayed informing that session to peer (backup) has failed and configuration is committed only in the local primary device. Under the same configuration, if the command "commit peers-synchronize" is used instead of "commit", then the synchronization error will cause the configuration to not be committed on any of the high availability nodes. This issue does not affect network services. The synchronization error is caused by a TACACS authentication failure when primary node attempts to access the secondary backup node.
PR NumberSynopsisCategory: Issues related to YANG Data Models
1826630Annotations are improperly structured in NETCONF after enabling YANG compliance
Product-Group=junos
Severity=Major		When the YANG(Yet Another Next Generation)-compliant knob is configured, annotations containing non-alphanumeric characters are written as-is, instead of being escaped into their corresponding formats.
PR NumberSynopsisCategory: video monitoring feature
1822738The PFE becomes inactive or disabled when running multicast in a video monitoring setup
Product-Group=junos
Severity=Major		On all Junos MX platforms with MPC2E, MPC3E, MPC4, MPC5 and MPC6 line cards and video monitoring configuration enabled, the Packet Forwarding Engine(PFE) goes in to disabled state when multicast traffic with more than 10 downstream interfaces. This leads to traffic loss.
PR NumberSynopsisCategory: Virtual Router Redundancy Protocol
1822867After RE switchover the VRRP master and backup router will start functioning as master routers
Product-Group=junos
Severity=Major		On all Junos and Junos Evolved platforms configured with VRRP (Virtual Router Redundancy Protocol) and NSR (Non-Stop Routing), after RE switchover or GRES (Graceful Routing Engine Switchover) the master router would starts sending VRRP advertisements with a different priority value. As a result, both the master and backup VRRP routers will begin operating as the master which results in inconsistent traffic routing or packet loss as the system fails to establish a single master node.

 

Modification History

First publication 2024-11-01