• On branch SRX Series platforms, performing a configuration commit via SSH or the console port takes significantly longer than expected following a software upgrade.
• Under normal conditions on legacy releases, a commit completes in approximately 40 seconds to 1 minute. After upgrading, the execution time degrades to between 2 and 4 minutes, even when committing minimal configuration changes.

Trigger Conditions:

This issue will occur if all the following conditions are met:

• Affected Platforms: All branch SRX series platforms (SRX300, SRX320, SRX340, SRX345, and SRX380).

• Affected Software: Any Junos OS or EVO release post-24.4 that runs on the FreeBSD 12 base kernel (e.g., initial 24.4R1 base software).

• Running a configuration change via commit or commit confirmed hangs on specific internal execution reveals massive time gaps.

• High CPU utilization attributed to configuration management daemons when checked via the CLI command "show system processes extensive"

Workaround:

• There are no temporary system configurations or restoration steps required to stabilize services, as data and transit operations are unaffected. If an upgrade cannot be scheduled immediately, the only workaround is to wait for the commit operation to safely finish processing.
• Disabling web-management Or shifting primary node roles within a chassis cluster will not reduce the delay.

Resolved In:

• To permanently resolve the commit degradation, upgrade the operating system to a release containing the official performance optimization fix:
  • Junos OS: 24.4R2-S4, 24.4X3, 25.2R2-S1, 25.4R2, 26.2R1
  • Junos EVO: 25.4R2-EVO, 26.2R1-EVO, 26.3R1-EVO