6.3.5 release notes #858

Chr1st0ph3rTurn3r · 2025-06-18T14:43:08Z

No description provided.

MichaelBaj · 2025-06-18T15:05:48Z

docs/release_notes_128t_6.3.md

@@ -36,6 +36,99 @@ An issue has been identified that may be observed in conductor deployments runni

 We have identified an issue when onboarding SSR routers installed with older versions of software (such as 5.4.4) to Conductors running 6.3.x, when running in offline-mode. In some cases, certain software packages are not available to be installed during onboarding. To work around this issue, import the **package-based** (the "128T" prefixed) ISO for the current conductor version onto the conductor. This provides the necessary software packages to complete the onboarding process. This issue will be resolved in a future release. 

+## Release 6.3.5-27r2


You will need to update the about release pages to update the latest 6.3 release - and ensure that the support timeframes are correct.

Also, shouldn't 6.3.5 be labeled STS?

Also, per Max's comments, we need to ensure that min-version for 6.3.5 for conductor is clearly called out since this is the version that will be shipped from factory.

MichaelBaj · 2025-06-18T15:15:28Z

docs/release_notes_128t_6.3.md

+------
+- **I95-57265 Highway crash when generating TSI on Azure instance:** An Azure instance can crash while accessing an uninitialized RX queue. This invalid access has been prevented and the issue resolved.
+-------
+- **I95-57508 Traffic from node1 LAN to node1 WAN does not show on graph:** When an HA interface becomes non-redundant (reconfigured as non-HA), state updates were not showing on the active-interface path. This led to the icmp-probe-manager not running. This issue has been resolved.


What graph? Is this for conductor or Mist? In either case, please be specific.

MichaelBaj · 2025-06-18T15:16:36Z

docs/release_notes_128t_6.3.md

+-------
+- **I95-57508 Traffic from node1 LAN to node1 WAN does not show on graph:** When an HA interface becomes non-redundant (reconfigured as non-HA), state updates were not showing on the active-interface path. This led to the icmp-probe-manager not running. This issue has been resolved.
+------
+- **I95-58017 FIB entries on `show fib` not available for all headends:** Resolved an issue with `show fib` stalling and not returning complete data. 


I believe it would be more accurate to say that the show fib output is incomplete on any router (not just head-ends) where the fib is large. It would be good if this could be quantified.

MichaelBaj · 2025-06-18T15:18:13Z

docs/release_notes_128t_6.3.md

+------
+- **I95-58017 FIB entries on `show fib` not available for all headends:** Resolved an issue with `show fib` stalling and not returning complete data. 
+------
+- **I95-58999 CPU usage for Packet Processing CPU always reads 100%:** Resolved an issue where the size of the packet transmit burst was reported, rather than the actual number transmitted when `transmit-on-standby` fails. The correct information is now provided.


transmit-on-standby is an internal detail that buries the lead on the problem statement.
packet processing CPU reads 100% when interface is operationally down. (please confirm).

waiting on input from Dennis

MichaelBaj · 2025-06-18T15:29:12Z

docs/release_notes_128t_6.3.md

+------
+- **I95-60282 Disk space usage growing to more than 90%:** DNF logs were increasing in size and not being rotated, causing a significant increase in size. A `log rotate` configuration file for DNF has been added to limit the size of DNF log files to prevent them from filling the hard drive. When this fix is installed on the conductor, it is automatically propogated to all managed routers. 
+------
+- **I95-60287 Add option to disable Kernel Metric SLA Calculation:** In rare cases on a heavily loaded system, the kernel metric calculation process can sometimes hang for a period of time, causing an internal watchdog to fire. This results in a system restart. Setting the `service-metric-use-lsa` (under the `routing default-instance`) to `false` will prevent the kernel flap that causes this issue. See [`service-metric-use-lsa`](config_command_guide.md#configure-authority-router-routing-service-metric-use-sla) for addtional information.


would it be cleaner to state:

Setting routing default-instance > service-metric-use-lsa > false will prevent the kernel flap that causes this issue.

MichaelBaj · 2025-06-18T15:56:06Z

docs/release_notes_128t_6.3.md

+------
+- **I95-60424 Anti-Virus whitelist not implemented:** Resolved an issue where a configuration error in the cSRX generated an error that was being ignored. The error is now handled correctly and the whitelist is implemented.
+------
+- **I95-60438 Max filesize setting not honoring the custom profile setting:** Resolved an issue where the max filesize setting would override to 10000 any time the configured value was less than 10000. 


Where is this max filesize configured? Can you provide the full configuration path?

MichaelBaj · 2025-06-18T15:56:48Z

docs/release_notes_128t_6.3.md

+------
+- **I95-60438 Max filesize setting not honoring the custom profile setting:** Resolved an issue where the max filesize setting would override to 10000 any time the configured value was less than 10000. 
+------
+- **I95-60465 Warning added when routers running V5.4.0 or less are detected:** Routers running V5.4.0 or less are not compatible with software versions 6.3.5 and higher. A warning has been added, noting that routers must be upgraded to avoid configuration issues.


We don't use V5.4.0 syntax for versions. It should be SSR-5.4.0 or lower.

MichaelBaj · 2025-06-18T17:15:40Z

docs/release_notes_128t_6.3.md

+------
+- **I95-60593, I95-60686 Unable to onboard 6.2.3 routers to 6.3.3:** Resolved an issue where assets would transition to `Reinitializing` and get stuck there because the asset was unable to succesfully complete highstate. Validations have been added to ensure the asset completes highstate successfully before transitioning to `Reinitializing`.
+------
+- **I95-60651 vSSR upgrade from 6.3.0 to 6.3.3 reboots back to 6.3.0:** Resolved an issue where the Conductor was unable to upgrade router packages to the latest version even though the packages were available on the Conductor. A `dnf refresh` now runs to ensure package accessibility. 


vSSR is called out here. Is it true that this is issue is specific to the SSR running as a VM only?

migolnikov · 2025-06-23T04:51:46Z

docs/conductor_upgrade.md

-The conductor `major.minor` version must be greater than or equal to the router version. The router version can not exceed the conductors `major.minor` version, but it can have a greater patch version. All [versions currently under support](about_support_policy.md) can be run on a router and managed by the conductor, provided that the conductor version is greater. Versions of software not under support *may* work, but are not guaranteed to do so.  
+**SSR-6.3.5 Software and Version Compatibility** 
+
+Beginning with SSR-6.3.5, conductor-managed **routers** running SSR-6.3.5 must be managed by conductors running SSR-6.3.5 or higher software. Internal updates to the software prevent successful management from a lower patch version on the conductor when 6.3.5 is installed on the router. For example:


This rule has always been in place, so I would not say "Beginning with SSR-6.3.5".

Max, this is not true. Please read the original statement. With the salt fix for 6.3.5, the router MUST be the same version or greater than the conductor. This is in fact new behavior.

So to clarify this - I reached out to Lane to determine what the field has experienced regarding conductor managed routers and versions. The documentation has said, for as long as I have been here, that a conductor patch version lower than the router patch version is supported as long as the major.minor versions are the same. However, both Max and Lane agreed that while this was requested and documented as such, if you tried to upgrade a router from a conductor to a patch version higher than the conductor, it would not work. If you bypassed the conductor and manually upgraded the router to a higher patch version, it "would probably work". So it has "not really" been supported.

Despite this reality, the documentation has stated for at least 5 years that it has been supported, which means that it is now, with 6.3.5, new behavior. Hence the documentation change.

migolnikov · 2025-06-23T04:53:33Z

docs/intro_installation.md

-The conductor `major.minor` version must be greater than or equal to the router version. The router version can not exceed the conductors `major.minor` version, but it can have a greater patch version. All [versions currently under support](about_support_policy.md) can be run on a router and managed by the conductor, provided that the conductor version is greater. Versions of software not under support *may* work, but are not guaranteed to do so.  
+**SSR-6.3.5 Software and Version Compatibility** 
+
+Beginning with SSR-6.3.5, conductor-managed **routers** running SSR-6.3.5 must be managed by conductors running SSR-6.3.5 or higher software. Internal updates to the software prevent successful management from a lower patch version on the conductor when 6.3.5 is installed on the router. For example:


same comment as above. "Beginning with SSR-6.3.5:"

migolnikov · 2025-06-23T04:54:09Z

docs/intro_installation_legacy.md

-The conductor `major.minor` version must be greater than or equal to the router version. The router version can not exceed the conductors `major.minor` version, but it can have a greater patch version. All [versions currently under support](about_support_policy.md) can be run on a router and managed by the conductor, provided that the conductor version is greater. Versions of software not under support *may* work, but are not guaranteed to do so.  
+**SSR-6.3.5 Software and Version Compatibility** 
+
+Beginning with SSR-6.3.5, conductor-managed **routers** running SSR-6.3.5 must be managed by conductors running SSR-6.3.5 or higher software. Internal updates to the software prevent successful management from a lower patch version on the conductor when 6.3.5 is installed on the router. For example:


Same comment as above "Beginning with SSR-6.3.5"

migolnikov · 2025-06-23T04:54:32Z

docs/intro_upgrading.md

-The conductor `major.minor` version must be greater than or equal to the router version. The router version can not exceed the conductors `major.minor` version, but it can have a greater patch version. All [versions currently under support](about_support_policy.md) can be run on a router and managed by the conductor, provided that the conductor version is greater. Versions of software not under support *may* work, but are not guaranteed to do so.  
+**SSR-6.3.5 Software and Version Compatibility** 
+
+Beginning with SSR-6.3.5, conductor-managed **routers** running SSR-6.3.5 must be managed by conductors running SSR-6.3.5 or higher software. Internal updates to the software prevent successful management from a lower patch version on the conductor when 6.3.5 is installed on the router. For example:


Same comment as above "Beginning with SSR-6.3.5"

migolnikov · 2025-06-23T04:55:05Z

docs/release_notes_128t_6.3.md

@@ -36,6 +36,111 @@ An issue has been identified that may be observed in conductor deployments runni

 We have identified an issue when onboarding SSR routers installed with older versions of software (such as 5.4.4) to Conductors running 6.3.x, when running in offline-mode. In some cases, certain software packages are not available to be installed during onboarding. To work around this issue, import the **package-based** (the "128T" prefixed) ISO for the current conductor version onto the conductor. This provides the necessary software packages to complete the onboarding process. This issue will be resolved in a future release. 

+**SSR-6.3.5 Software and Version Compatibility** 
+
+Beginning with SSR-6.3.5, conductor-managed **routers** running SSR-6.3.5 must be managed by conductors running SSR-6.3.5 or higher software. Internal updates to the software prevent successful management from a lower patch version on the conductor when 6.3.5 is installed on the router. For example:


Same as above "Beginning with SSR-6.3.5"

migolnikov · 2025-06-23T04:55:50Z

docs/upgrade_legacy.md

-The conductor `major.minor` version must be greater than or equal to the router version. The router version can not exceed the conductors `major.minor` version, but it can have a greater patch version. All [versions currently under support](about_support_policy.md) can be run on a router and managed by the conductor, provided that the conductor version is greater. Versions of software not under support *may* work, but are not guaranteed to do so.  
+**SSR-6.3.5 Software and Version Compatibility** 
+
+Beginning with SSR-6.3.5, conductor-managed **routers** running SSR-6.3.5 must be managed by conductors running SSR-6.3.5 or higher software. Internal updates to the software prevent successful management from a lower patch version on the conductor when 6.3.5 is installed on the router. For example:


same as above "Beginning with SSR-6.3.5"

MichaelBaj · 2025-06-23T12:34:53Z

docs/about_releases.md

@@ -35,7 +35,7 @@ However, issues resolved in `4.3.12`, which was released on 3/12/2021 are not ad

 | Version | Initial GA Version | First Release Shipping Date | Latest GA Version | End of Engineering support | End of Support |
 | -- | -- | -- | -- | -- | -- |
-| Release 6.3 | [6.3.0](release_notes_128t_6.3.md#release-630-107r1) | September 30, 2024 | [6.3.4-r2](release_notes_128t_6.3.md#release-634-7r2) | March 26, 2026 | September 26, 2026 |
+| Release 6.3 | [6.3.0](release_notes_128t_6.3.md#release-630-107r1) | September 30, 2024 | [6.3.5-27-sts](release_notes_128t_6.3.md#release-635-27-sts) | April 10, 2026 | October 10, 2026 |


If 6.3.5-sts is to be released on June 26, its EoE support date should be 9 months later and EoS date 6 months after that.
Release date: 6-26-2025
EoE: 3-26-2026
EoS: 9-26-2026

I believe the original dates were correct.

Ryan told me that the date had been pushed out to July 10, so I was using that date.

MichaelBaj · 2025-06-23T12:36:54Z

docs/conductor_upgrade.md

-The conductor `major.minor` version must be greater than or equal to the router version. The router version can not exceed the conductors `major.minor` version, but it can have a greater patch version. All [versions currently under support](about_support_policy.md) can be run on a router and managed by the conductor, provided that the conductor version is greater. Versions of software not under support *may* work, but are not guaranteed to do so.  
+**SSR-6.3.5 Software and Version Compatibility** 
+
+Beginning with SSR-6.3.5, conductor-managed **routers** running SSR-6.3.5 must be managed by conductors running SSR-6.3.5 or higher software. Internal updates to the software prevent successful management from a lower patch version on the conductor when 6.3.5 is installed on the router. For example:


Max, this is not true. Please read the original statement. With the salt fix for 6.3.5, the router MUST be the same version or greater than the conductor. This is in fact new behavior.

Chr1st0ph3rTurn3r added 2 commits June 18, 2025 08:56

new graphics, release notes updates.

04b7162

release notes for 6.3.5

b3d4460

Chr1st0ph3rTurn3r requested review from migolnikov and jeffmart-jnpr June 18, 2025 14:43

Chr1st0ph3rTurn3r requested a review from MichaelBaj as a code owner June 18, 2025 14:43

MichaelBaj requested changes Jun 18, 2025

View reviewed changes

updates per review, adding 6.3.5 version reqs.

8ec0422

migolnikov reviewed Jun 23, 2025

View reviewed changes

MichaelBaj self-requested a review June 23, 2025 12:20

MichaelBaj previously approved these changes Jun 23, 2025

View reviewed changes

Chr1st0ph3rTurn3r and others added 2 commits June 23, 2025 09:44

Merge branch 'master' into 6.3.5-release-notes

c9fdb13

added clarification on 58999 from Dennis. Updated date to 7/10.

442f543

Chr1st0ph3rTurn3r dismissed MichaelBaj’s stale review via 442f543 June 24, 2025 12:58

Chr1st0ph3rTurn3r and others added 3 commits July 15, 2025 15:18

Merge branch 'master' into 6.3.5-release-notes

367134a

date and release number changes

1969dc6

date changes

675fe02

		@@ -36,6 +36,99 @@ An issue has been identified that may be observed in conductor deployments runni

		We have identified an issue when onboarding SSR routers installed with older versions of software (such as 5.4.4) to Conductors running 6.3.x, when running in offline-mode. In some cases, certain software packages are not available to be installed during onboarding. To work around this issue, import the package-based (the "128T" prefixed) ISO for the current conductor version onto the conductor. This provides the necessary software packages to complete the onboarding process. This issue will be resolved in a future release.

		## Release 6.3.5-27r2

6.3.5 release notes #858

Are you sure you want to change the base?

6.3.5 release notes #858

Uh oh!

Conversation

Chr1st0ph3rTurn3r commented Jun 18, 2025

Uh oh!

MichaelBaj Jun 18, 2025 • edited by Chr1st0ph3rTurn3r Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

MichaelBaj Jun 18, 2025 •

edited by Chr1st0ph3rTurn3r

Loading