-
Notifications
You must be signed in to change notification settings - Fork 14
clarification for conductor and router upgrade #907
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
… to at least v6.3.5 before upgrading to v7.0.1 and higher.
docs/release_notes_128t_7.0.md
Outdated
|
|
||
| :::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. |
There was a problem hiding this comment.
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.
docs/release_notes_128t_7.0.md
Outdated
|
|
||
| **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. |
There was a problem hiding this comment.
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
docs/release_notes_128t_7.0.md
Outdated
|
|
||
| 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. |
There was a problem hiding this comment.
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
left a comment
There was a problem hiding this 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.
docs/release_notes_128t_7.0.md
Outdated
|
|
||
| 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). |
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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"
No description provided.