Conductor deployment guide #591

Chr1st0ph3rTurn3r · 2023-07-28T17:57:37Z

I suggest that you build the docs to see the changes, additions, and removals.

MichaelBaj · 2023-08-01T16:33:49Z

docs/install_conductor_overview.md

 - [Import Configurations to the Conductor](single_conductor_config.md)
 - [Conductor Software Upgrades](conductor_upgrade.md)
- [Conversion of an SSR Router to a Conductor](conductor_conversion.md)
+<!-- markdown-link-check-disable-next-line -->
+- [Conversion of an SSR Router to a Conductor](single_conductor_install#conductor-conversion)


Why did you have to disable the link check for this hyperlink? it should be single_conductor_install.mdx#conductor-conversion

MichaelBaj · 2023-08-03T15:01:11Z

docs/_install_interactiveoverview.md

This snippet needs modification for use in the conductor guide as the sentence above reads:

"The steps in this section describe the interactive conductor installation from the packaged-based ISO. The section Initialize the SSR describes..."

"Initialize the SSR" should be initialize the conductor

MichaelBaj · 2023-08-03T16:29:56Z

docs/_install_interactiveoverview.md

To the last sentence "... can be used to install more complex router configurations."
While this is true, we should be more binary regarding the use of the OTP workflow. It is intended for whitebox and air-gapped, conductor-only networks.

MichaelBaj · 2023-08-03T16:37:28Z

docs/_conductor_conversion.md

@@ -0,0 +1,5 @@
+<!---Conductor Conversion---->
+
+An SSR device (SSR1xx or SSR1xxx) shipped with SSR 5.4.x Routing software may be reinitialized as a conductor for use in an existing network. **The conductor can be used with or without Cloud Telemetry for devices running pre 6.0.x SSR software.**


"The conductor can be used with Mist Cloud Telemetry for SSR routers running software version 5.5 or greater."

MichaelBaj · 2023-08-03T16:41:17Z

docs/ha_conductor_install.mdx

+### Configure the Network Interface 
+<ConductorIP/>
+
+### Initialize the SSR Node


This heading should be "Initialized the Conductor Node"

MichaelBaj · 2023-08-03T16:57:19Z

docs/single_conductor_install.mdx

+
+ ![Authority Settings](/img/conductor_authority_name.png)
+
+3. Under Basic Information, enter the new Authority name.


Add the sentence:
A good name for the Authority would be the name of the business, e.g., Acme Corp.

MichaelBaj · 2023-08-03T16:59:19Z

docs/single_conductor_install.mdx

+
+### Set the Conductor IP Address
+
+1. Under Conductor Addresses, select ADD.


This section is incomplete. The steps during initialization setup the management IP. This conductor IP address will be its public IP address for which the manage routers will connect. This needs to be associated with a network-interface. Those configuration steps are missing from this guide.

MichaelBaj · 2023-08-03T17:53:16Z

docs/ha_conductor_install.mdx

@@ -0,0 +1,200 @@
+---
+title: High Availability Conductor Installation


All of my comments on single_conductor_install.mdx are applicable to this file as well.

MichaelBaj · 2023-08-03T17:56:36Z

docs/ha_conductor_install.mdx

+- Conductor High Availability
+- [Conductor High Availability for Cloud Deployments](intro_initialize_HA_conductor.md)
+
+## Install the First Conductor HA Node 


It would be beneficial to have a digram of SSR 1300s (acting as conductors) indicating how physical ports should be configured. Since this section discusses management ports, and HA sync ports and reachability, it would be better to provide a blueprint for customers to follow.

Still working on this diagram. Will include in the next edits/push.

Added. Am reaching out to Adam for review - sending him a pdf.

MichaelBaj · 2023-08-03T17:58:49Z

docs/ha_conductor_install.mdx

+
+  ![2nd HA Peer IP](/img/initializer_Serial4dHANode.png)
+
+3. Enter the **HA Peer Credentials**. This is a one time operation for the initialization of the second HA Node with the first HA Peer. The `t128` user can be used for this operation.


The t128 user can be used for this operation.
What other user can be used for this operation? We should be explicit in this step for which user account to use.
Additionally, it should be added as a note that this one time operation has no impact on future changes to users and their passwords. Once HA is established between conductor nodes, security keys are exchanged for secure communication and not passwords.

…ing info from Adam.

MichaelBaj · 2023-08-17T13:57:34Z

docs/_install_verify_conductor_install.md


-2. Execute the command:
+1. Login using the Admin credentials.


recommend changing "Admin" to "admin" because that is how you would enter it on the command line.

MichaelBaj · 2023-08-17T13:58:39Z

docs/_install_verify_conductor_install.md

-  sudo systemctl status 128T
-  ```
+```
+CentOS Linux 7 (Core)


Not sure why these two lines with "CentOS and Kernel" are here

Chr1st0ph3rTurn3r added 6 commits July 17, 2023 16:32

rearragne FIPS

f662c00

in progress

bea25cf

revising conductor install process

f364971

adding graphics and text edits

760ee66

updating HA process with new steps and single source docs.

70acd29

final additions to draft version.

b30d450

Chr1st0ph3rTurn3r requested review from laneshields and reidstidolph-JNPR July 28, 2023 17:57

Chr1st0ph3rTurn3r requested a review from MichaelBaj as a code owner July 28, 2023 17:57

Chr1st0ph3rTurn3r and others added 6 commits July 28, 2023 15:41

fix broken link

a68c0a9

testing for resolving broken link - please ignore this commit

ca8f885

trying to resolve broken link

c0772ef

disable link check on not-broken link

d41d47b

typos

be0f394

Merge branch 'master' into conductor-deployment-guide

50743aa

MichaelBaj requested changes Aug 3, 2023

View reviewed changes

Chr1st0ph3rTurn3r and others added 5 commits August 7, 2023 11:19

Merge branch 'master' into conductor-deployment-guide

c9670b9

some but not all of Mike's review comments. Still working and collect…

032c221

…ing info from Adam.

almost all edits included, still working on diagram.

da22827

Merge branch 'master' into conductor-deployment-guide

5775da8

adding graphic for review and other text updates.

7b82b83

Chr1st0ph3rTurn3r requested a review from MichaelBaj August 10, 2023 20:54

MichaelBaj previously approved these changes Aug 11, 2023

View reviewed changes

updates from independent review

a6e5163

Chr1st0ph3rTurn3r dismissed MichaelBaj’s stale review via a6e5163 August 16, 2023 18:36

Chr1st0ph3rTurn3r requested a review from MichaelBaj August 17, 2023 12:33

MichaelBaj requested changes Aug 17, 2023

View reviewed changes

case change for admin, and removed unnecessary lines

77824bd

MichaelBaj self-requested a review August 18, 2023 19:03

MichaelBaj approved these changes Aug 18, 2023

View reviewed changes

Chr1st0ph3rTurn3r merged commit 310d2d7 into master Aug 18, 2023
1 check passed

Chr1st0ph3rTurn3r deleted the conductor-deployment-guide branch August 18, 2023 19:31

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Conductor deployment guide #591

Conductor deployment guide #591

Chr1st0ph3rTurn3r commented Jul 28, 2023 •

edited

Loading

MichaelBaj Aug 1, 2023

MichaelBaj Aug 3, 2023

MichaelBaj Aug 3, 2023

MichaelBaj Aug 3, 2023

MichaelBaj Aug 3, 2023

MichaelBaj Aug 3, 2023

MichaelBaj Aug 3, 2023

MichaelBaj Aug 3, 2023

MichaelBaj Aug 3, 2023

Chr1st0ph3rTurn3r Aug 8, 2023

Chr1st0ph3rTurn3r Aug 10, 2023

MichaelBaj Aug 3, 2023

MichaelBaj Aug 17, 2023

MichaelBaj Aug 17, 2023

		@@ -0,0 +1,5 @@
		<!---Conductor Conversion---->

		An SSR device (SSR1xx or SSR1xxx) shipped with SSR 5.4.x Routing software may be reinitialized as a conductor for use in an existing network. The conductor can be used with or without Cloud Telemetry for devices running pre 6.0.x SSR software.


		![Authority Settings](/img/conductor_authority_name.png)

		3. Under Basic Information, enter the new Authority name.


		### Set the Conductor IP Address

		1. Under Conductor Addresses, select ADD.

		@@ -0,0 +1,200 @@
		---
		title: High Availability Conductor Installation


		![2nd HA Peer IP](/img/initializer_Serial4dHANode.png)

		3. Enter the HA Peer Credentials. This is a one time operation for the initialization of the second HA Node with the first HA Peer. The `t128` user can be used for this operation.


		2. Execute the command:
		1. Login using the Admin credentials.

Conductor deployment guide #591

Conductor deployment guide #591

Conversation

Chr1st0ph3rTurn3r commented Jul 28, 2023 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Chr1st0ph3rTurn3r commented Jul 28, 2023 •

edited

Loading