Skip to content

Conversation

@Chr1st0ph3rTurn3r
Copy link
Contributor

@Chr1st0ph3rTurn3r Chr1st0ph3rTurn3r commented Jan 2, 2026

No description provided.

… to at least v6.3.5 before upgrading to v7.0.1 and higher.
@Chr1st0ph3rTurn3r Chr1st0ph3rTurn3r changed the title clarification that both the conductor AND the router must be upgraded… clarification for conductor and router upgrade Jan 2, 2026
MichaelBaj
MichaelBaj previously approved these changes Jan 5, 2026

:::important
The minimum starting version for a conductor upgrade to 7.0.1 is 6.3.5. If the conductor is not currently running at least 6.3.5, first upgrade to this version and wait for all managed routers to reach the synchronized state prior to upgrading to 7.0.1. There are new keying requirements enforced by the conductor in 7.0.1, and if the routers do not reach the synchronized state before upgrading to 7.0.1, those routers will not be able to communicate with the conductor.
**The minimum starting version for upgrading a conductor or a router to 7.0.1 is 6.3.5.** If the conductor is not currently running at least 6.3.5, first upgrade to this version. Then upgrade each router to 6.3.5, and wait for all managed routers to reach the synchronized state prior to upgrading to 7.0.1. There are new keying requirements enforced by the conductor in 7.0.1, and if the routers do not reach the synchronized state before upgrading to 7.0.1, those routers will not be able to communicate with the conductor.
Copy link
Contributor

@migolnikov migolnikov Jan 5, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Then upgrade each router to 6.3.5, " This is not right. Customer does not need to upgrade the routers to 6.3.5. Here is how this works:
To connect ANY pre 6.3.5 Router to a 7.x Conductor, they first MUST connect those routers to a 6.3.5+ Conductor (6.3.6, 6.3.7, etc). Once that happens, the 6.3.x Conductor will update the Router with info necessary to connect to a 7.x Conductor. The Router itself does NOT need to be upgraded.

MichaelBaj
MichaelBaj previously approved these changes Jan 5, 2026

**7.0.1 Conductor Upgrades**

If you are upgrading a conductor that is currently installed with version 6.3.4 or lower, and you wish to upgrade to version 7.0.1, you must first upgrade the conductor to version 6.3.5.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

or 6.3.6 or 6.3.7, etc


1. Upgrade the conductor to 6.3.5+ (but not higher than the latest version of 6.3.x).
2. Upon completion of the install, allow all managed routers to connect and reach the **Synchronized** state.
The new keying requirements that are part of 6.3.5+ are loaded onto the routers during synchronization. These are required for routers to communicate with a 7.0.1+ conductor. If the routers do not reach the synchronized state before upgrading to 7.0.1, those routers will not be able to communicate with the conductor.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"will not be able to communicate with the conductor." ==> will not be able to communicate with the 7.0+ conductor.

migolnikov
migolnikov previously approved these changes Jan 5, 2026
Copy link
Contributor

@migolnikov migolnikov left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added 2 comments which are more of suggestions.

migolnikov
migolnikov previously approved these changes Jan 6, 2026
@MichaelBaj MichaelBaj self-requested a review January 6, 2026 18:03

Routers running SSR software versions earlier than 6.3.5 cannot connect to conductors running SSR software version 7.0.1 and higher. A transitional step is required to enable routers running versions earlier than 6.3.5 (6.0.x, 6.1.x, 6.2.x, 6.3.4 and lower) to communicate with a conductor running 7.0.1+.

1. Upgrade the conductor to 6.3.5+ (but not higher than the latest version of 6.3.x).
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't understand this statement of not higher than the latest version of 6.3.x. Is it always going to be true, or is it only true right now for 6.3.6? Why is this the case?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because the keying requirements are only in 6.3.5+. The only way they can get a router to communicate with a 7.x conductor, is by getting the keying requirements that are only in the 6.3 branch starting with 6.3.5. The issue is that if the conductor goes from 6.3.3 or 6.2.6 to 7.0.1 or 7.1.x, the router won't be able to communicate with it. The router has to sync with 6.3.5, 6.3.6, 6.3.7 to be able to talk to 7.0.1/7.1.x.

The new keying requirements that are part of 6.3.5+ are loaded onto the routers during synchronization. These are required for routers to communicate with a 7.0.1+ conductor. If the routers do not reach the synchronized state before upgrading to 7.0.1, those routers will not be able to communicate with the conductor.

Routers running SSR software versions earlier than 6.3.5 cannot connect to conductors running SSR software version 7.0.1 and higher. A transitional step is required to enable routers running versions earlier than 6.3.5 (6.0.x, 6.1.x, 6.2.x, 6.3.4 and lower) to communicate with a conductor running 7.0.1+.

1. Upgrade the conductor to any version of the 6.3.x software, including and higher than 6.3.5.
2. Upon completion of the install, allow all managed routers to connect and reach the **Synchronized** state.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: " Upon completion of the install" ==> " Upon completion of the upgrade"


1. Upgrade the conductor to any version of the 6.3.x software, including and higher than 6.3.5.
2. Upon completion of the install, allow all managed routers to connect and reach the **Synchronized** state.
The new keying requirements that are part of 6.3.5+ are loaded onto the routers during synchronization. These are required for routers to communicate with a 7.0.1+ conductor. If the routers do not reach the synchronized state, those routers will not be able to communicate with the 7.0.1+ conductor.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: "These are required" ==> "These will be required"

1. Upgrade the conductor to any version of the 6.3.x software, including and higher than 6.3.5.
2. Upon completion of the install, allow all managed routers to connect and reach the **Synchronized** state.
The new keying requirements that are part of 6.3.5+ are loaded onto the routers during synchronization. These are required for routers to communicate with a 7.0.1+ conductor. If the routers do not reach the synchronized state, those routers will not be able to communicate with the 7.0.1+ conductor.
3. Once the routers are synchronized, you may upgrade the conductor to 7.0.1. All synchronized routers, regardless of version, will be able to communicate with the upgraded conductor. The routers are not required to upgrade to 7.0.1 or to 6.3.5.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: "The routers are not required to upgrade to 7.0.1 or to 6.3.5." ==> "Note: The routers themselves do not need to be upgraded"

@Chr1st0ph3rTurn3r Chr1st0ph3rTurn3r merged commit 8ac1451 into master Jan 7, 2026
1 check passed
@Chr1st0ph3rTurn3r Chr1st0ph3rTurn3r deleted the I95-63539-upgrade-edit branch January 7, 2026 14:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants