Migrate a router Mist-managed #671
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MichaelBaj
requested changes
Feb 6, 2024
docs/wan_migration_to_mist.md
Outdated
|
|
||
| ## Prerequisites | ||
|
|
||
| - The conductor and router are running version x.x.x or newer of the Mist WAN Assurance plugin **I see no indication in the docs for the WA Plugin - Yikes!** |
There was a problem hiding this comment.
- Determine correct min version needed - if any.
docs/wan_migration_to_mist.md
Outdated
| - The router was previously onboarded and connected to the Mist cloud using the [ZTP Onboarding to a Conductor workflow](config_wan_assurance.md). | ||
| - For HA routers, each node should have a direct connection to the Mist cloud. | ||
| - The router must be online and connected to the cloud for the migration process to be initiated. | ||
| - The router is running a cloud-ready, image-based installation of SSR software, such as V6.0.0 or greater. Conductor-managed instances often are package-based installations. For upgrade instructions, please see [Image-Based Installation](intro_installation_image.md). |
There was a problem hiding this comment.
We have package-based 6.0.0 software, so this statement is misleading.
The router should be converted to image-based when it is migrated to the cloud, but need to double-check.
If not, then this guide needs to wait until IBU support is added to conductor.
docs/wan_migration_to_mist.md
Outdated
| - The router is running a cloud-ready, image-based installation of SSR software, such as V6.0.0 or greater. Conductor-managed instances often are package-based installations. For upgrade instructions, please see [Image-Based Installation](intro_installation_image.md). | ||
| - The router configuration must be re-created on the Mist cloud. | ||
| - The Mist cloud configuration should have the necessary components for establishing a successful cloud connection post migration. | ||
| - While still connected to the conductor, the system environment has to be prepared for migration to the Mist cloud. |
There was a problem hiding this comment.
I don't understand what this statement is asking of the reader. What does "preparing the system environment" mean?
docs/wan_migration_to_mist.md
Outdated
| - The router configuration must be re-created on the Mist cloud. | ||
| - The Mist cloud configuration should have the necessary components for establishing a successful cloud connection post migration. | ||
| - While still connected to the conductor, the system environment has to be prepared for migration to the Mist cloud. | ||
| - For a use case involving in-band management, the Mist config template must allow access to the conductor via SSH. This will ensure connectivity during the migration. |
There was a problem hiding this comment.
I don't understand how Mist will access the conductor via SSH, or why. I don't think this statement is correct.
docs/wan_migration_to_mist.md
Outdated
| ::: | ||
|
|
||
| :::note | ||
| - After upgrading to an image based software version, verify that the `mist-agent` is running. Use [Mist Agent Startup](add-link-here) to verify operation. |
docs/wan_migration_to_mist.md
Outdated
|
|
||
| While conductor-managed routers allow the user to configure the device-interface via PCI mapping, Mist management relies on name mapping instead. In order to create a compatible device map, use the following procedure. | ||
|
|
||
| **AdD StEPs HeRe** |
There was a problem hiding this comment.
- I'd really like for this section to not be necessary. For Juniper-branded devices, this shouldn't be necessary, however the ports they use may be different from the defaults in Mist.
docs/wan_migration_to_mist.md
Outdated
| ``` | ||
|
|
||
| 2. Remove the conductor from the global.init. | ||
|
|
| ``` | ||
| systemctl status reverse-ssh_conductor1_login | ||
| systemctl is-enabled reverse-ssh_conductor1_login | ||
| ``` |
There was a problem hiding this comment.
I thought engineering developed a migrate command that performed several of these steps outlined here.
@agrawalkaushik to confirm.
There was a problem hiding this comment.
We did. Spoke to Chris offline and the doc was created using the wrong source. Chris will be re-writing this.
… server exists any more - I did try the link and search several times for information.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.