6.3.0 install updates #696

Chr1st0ph3rTurn3r · 2024-03-26T18:31:54Z

No description provided.

…e docs.

… make it more usable.

…adding network interface info.

…ld issue.

…added the \ delimiter.

…" Merge branch '6.3.0-traffic-engineering' into 6.3.0-install-updates

… '6.3.0-traffic-engineering' into 6.3.0-release-documentation

tcarroll25

One thing I think we should add is the software access channel is now part of the datamodel. Apologies if I forgot to mention this earlier. Previously, in order to enable different repos like alpha, the customer would have to drop to the Linux shell and execute commands with install128t. Now this behavior is integrated into the product. There is an authority level configuration object:

config
    authority
        software-access
            channel <prealpha|alpha|beta|release>
            username <username>
            token <token>
        exit
    exit
exit

Its important to note that upon upgrading the conductor to 6.3, the existing credentials on disk will be automatically added to the configuration and default to the release channel so the user will not have to take any action. If the user wishes to change the channel for the authority they can simply change it in the datamodel and the new channel will be enabled for all routers in the authority. There is also a router level override if the user wishes to enable a different channel for a single router. The user is able to use the same credentials as the authority object or override them as well:

config
    authority
        router
            system
                software-access
                    channel <prealpha|alpha|beta|release>
                    use-authority-credentials true
                exit
            exit
        exit
    exit
exit

Override authority credentials (probably a very uncommon use case):

config
    authority
        router
            system
                software-access
                    channel <prealpha|alpha|beta|release>
                    use-authority-credentials false
                    router-credentials
                        username <username>
                        token <token>
                    exit
                exit
            exit
        exit
    exit
exit

tcarroll25 · 2024-04-29T19:13:23Z

docs/intro_rollback.md

@@ -7,6 +7,10 @@ Occasionally you may want or need to revert to a previously running version of S

 ## Rollback Considerations

+With an upgrade or installation of SSR v6.3.0, conductor rollbacks are performed using the `request system software revert` command from the conductor's PCLI. On routers, it is recommended that upgrades and rollbacks are performed from the conductor's GUI. 


On routers, it is recommended that upgrades and rollbacks are performed from the conductor's GUI.

This is correct however, the GUI only supports upgrades. The PCLI supports upgrades and reverts.

tcarroll25 · 2024-04-29T19:15:33Z

docs/intro_rollback.md

@@ -7,6 +7,10 @@ Occasionally you may want or need to revert to a previously running version of S

 ## Rollback Considerations

+With an upgrade or installation of SSR v6.3.0, conductor rollbacks are performed using the `request system software revert` command from the conductor's PCLI. On routers, it is recommended that upgrades and rollbacks are performed from the conductor's GUI. 
+
+Rolling back earlier versions of the SSR software (conductor peer or router) with the interactive installer `install128t`, that is managed by a conductor may result in the system becoming unresponsive. It is highly recommended that rollbacks be performed through the conductor UI. Manual upgrades and rollbacks may not be resilient to failures.


Can we say that for 6.3 that using the interactive installer is no longer supported? The user should always use either the GUI or PCLI. Especially now that the PCLI supports self upgrades and rollbacks even when 128T is not running.

tcarroll25 · 2024-04-29T19:16:32Z

docs/intro_upgrade_considerations.md


 ### Rollback Considerations
-Upgrading or rolling back a system (conductor peer or router) with the interactive installer `install128t`, that is managed by a conductor may result in the system becoming unresponsive. It is highly recommended that upgrades be performed through the conductor UI. Manual upgrades and rollbacks may not be resilient to failures. See [Rolling Back Software](intro_rollback.md) for more information on these operations.
+With an upgrade or installation of SSR v6.3.0, conductor rollbacks are performed using the `request system software revert` command from the conductor's pcli. On routers, it is recommended that upgrades and rollbacks are performed from the conductor's GUI. 


Same comment as above. Only the PCLI supports upgrades and reverts, the GUI only supports upgrades.

tcarroll25 · 2024-04-29T19:17:18Z

docs/intro_upgrade_considerations.md

-Upgrading or rolling back a system (conductor peer or router) with the interactive installer `install128t`, that is managed by a conductor may result in the system becoming unresponsive. It is highly recommended that upgrades be performed through the conductor UI. Manual upgrades and rollbacks may not be resilient to failures. See [Rolling Back Software](intro_rollback.md) for more information on these operations.
+With an upgrade or installation of SSR v6.3.0, conductor rollbacks are performed using the `request system software revert` command from the conductor's pcli. On routers, it is recommended that upgrades and rollbacks are performed from the conductor's GUI. 
+
+Upgrading or rolling back earlier versions of the SSR software (conductor peer or router) with the interactive installer `install128t`, that is managed by a conductor may result in the system becoming unresponsive. It is highly recommended that upgrades be performed through the conductor UI. Manual upgrades and rollbacks may not be resilient to failures. See [Rolling Back Software](intro_rollback.md) for more information on these operations.


Same comment as above, can we say its not supported any longer?

tcarroll25 · 2024-04-29T19:21:36Z

docs/upgrade_ibu_conductor.md

+
+### Upgrading Using the CLI
+
+Use the `request system software upgrade` command and the associated arguments to perform upgrades. All of the upgrade features are available from the command line as well as the GUI. 


We may want to mention that the PCLI is now capable of doing an HA sequenced self upgrade. So if the user is logged into an HA conductor and executes request system software upgrade router <conductor-router-name> then the default behavior is to perform a sequenced self upgrade of the conductor, one node at a time automatically. If the user prefers to manually upgrade each conductor node one at a time then they can target each node directly with request system software upgrade router <conductor-router-name> node <conductor-node-name> and wait for the first node to finish before moving onto the second.

tcarroll25 · 2024-04-29T19:24:58Z

docs/upgrade_ibu_conductor.md

+
+* If an HA pair is discovered to have a mismatched software state (image-based and package-based) an Alarm is reported. The software state must be the same for both nodes.
+* Failure of a router to complete the conversion generates a user visible event and records the reasons for the failure on the conductor.
+* Router conversion success generates an event recording the transition on the conductor.


Router conversion success generates an event recording the transition on the conductor.

I don't think this is true

I confirmed that this is not true. There will be an event on the router itself but not the conductor.

tcarroll25 · 2024-04-29T19:26:16Z

docs/upgrade_ibu_conductor.md

+* If an HA pair is discovered to have a mismatched software state (image-based and package-based) an Alarm is reported. The software state must be the same for both nodes.
+* Failure of a router to complete the conversion generates a user visible event and records the reasons for the failure on the conductor.
+* Router conversion success generates an event recording the transition on the conductor.
+* The image-based and package-based status is visible in the `asset-status` in the GUI, and in the PCLI using `show assets`.


This is not true, the image-based vs package-based status is visible with show system version which can be targeted to routers from the conductor

@Chr1st0ph3rTurn3r I decided to add this in, show assets will now show if the system is PBU or IBU

tcarroll25 · 2024-04-29T19:28:08Z

docs/upgrade_router.md

+
+1. Use the command `show assets` to list the devices managed by this conductor, and the software revision each asset is currently running.
+
+2. For a given asset, use the command `show asset [asset ID]` or `show asset software router [router name]`  to view the available software upgrades for that asset. The list will be in the section labeled "Available for Download" at the end of the output.


This is no longer true, none of the show assets commands show available or downloaded software. The user must use show system software available router <router> node <node> or show system software download router <router> node <node>

tcarroll25 · 2024-04-29T19:29:07Z

docs/upgrade_router.md

+
+2. For a given asset, use the command `show asset [asset ID]` or `show asset software router [router name]`  to view the available software upgrades for that asset. The list will be in the section labeled "Available for Download" at the end of the output.
+   :::note
+   If there are software releases absent from the list that you are confident should appear, use the command `send command yum-cache-refresh router [router name]` to refresh the software list.


The command send command yum-cache-refresh router [router name] is not longer relevant since the available and downloaded software is no longer cached on the conductor. The latest info is always retrieved on demand when show system software available router <router> node <node> or show system software download router <router> node <node> are executed.

tcarroll25 · 2024-04-29T19:31:36Z

docs/upgrade_router.md

+
+4. Once the download is complete, use the command `request system software upgrade router <rtr> node <node> version <image-version>` to initiate the upgrade process. View upgrade progress using `show system software upgrade router <rtr> node <node>`
+
+In a high availability deployment, the conductor upgrades each router node sequentially to minimize/avoid downtime. For manual upgrades, intiating an upgrade on one HA node or router will automatically upgrade the second node/router. However, it is still recommended to perform upgrade activity during periods of low traffic or maintenance windows.


To clarify this a bit more, we give the user a little more flexibility now. If the user targets a router with the upgrade command request system software upgrade router <name> then both nodes will be upgraded sequentially. However, we also allow the user to target an individual node request system software upgrade router <name> node <name> which will only upgrade that node. The same behavior occurs if the conductor is targeting itself or a remote router. Its also the same behavior for reverts as well as upgrades.

tcarroll25 · 2024-04-29T19:49:46Z

docs/upgrade_restricted_access.md

+            exit
+        exit
+    exit
+exit


The repository does not have a nameandtruecan go on the same line asoffline-mode`:

config authority router system software-update repository offline-mode true exit exit exit exit exit exit

tcarroll25 · 2024-04-29T20:03:16Z

docs/upgrade_restricted_access.md

+
+The `import iso` command is used to import packages contained within an SSR ISO onto a local repository, allowing the SSR to be upgraded without connecting to Juniper servers. When upgrading a conductor or when `offline-mode` is defined for a router, the ISO must be imported to the target conductor to perform the upgrade. 
+
+Use the [import iso](cli_reference.md#import-iso) command to specify the exact `filepath` to the ISO, or to specify `hunt` which searches the disk for a file that matches the pattern `128T*.iso` (except in the following directories `/boot`, `/dev`, `/proc`, and `/sys`).


The hunt command now imports anything matching the patterns 128T*.iso, SSR*.iso or SSR*.tar and any corresponding checksum and signature files.

Another thing that may be worth documenting is, when importing an SSR ISO we added some additional security and validation mechanisms where the ISO also needs to be imported with the checksum and signature files for the tarball contained within the ISO. This probably sounds confusing and we have a (hopefully) very obvious error message when the checksum and signature files are missing that the user needs to go download them as well. What is means is, if I was a user and I wanted to import this file:

SSR-6.3.0-58.r1.el7.x86_64.ibu-v1.iso

I would get an import error if I did not also download these two files to go with it and place them in the same directory (note the .tar and not .iso)

SSR-6.3.0-58.r1.el7.x86_64.ibu-v1.tar.sha256sum SSR-6.3.0-58.r1.el7.x86_64.ibu-v1.tar.sha256sum.asc

This is unfortunate and actually a current limitation of our release pipeline that we hope to fix in the future so it wont be necessary to download these extra files and they will be included within the .iso file.

…entation' into 6.3.0-install-updates

tcarroll25 · 2024-05-02T14:03:56Z

One other thing I thought of is there is now a PCLI command for IBU systems to change the boot volume. The user can view the current boot volume with show system version:

admin@conductor-node-1.Conductor# show system version router RTR_WEST_COMBO node combo-west-1 detail
Thu 2024-05-02 14:03:28 UTC
Retrieving system version...

=================================================================
 Node: combo-west-1.RTR_WEST_COMBO
=================================================================
 Version:               6.3.0
 Status:                r1
 Build Date:            2024-05-01T21:25:38Z
 Build Machine:         releaseslave3.openstacklocal
 Build User:            jenkins
 Build Directory:       /i95code
 Hash:                  1d892d709c45409369048d129840b02e435b4e21
 Package:               128T-6.3.0-60.r1.el7
 SSR-IMG-release:       SSR-6.3.0-60.r1.el7.x86_64.ibu-v1
 Volume ID:             b
 Selected Boot Volume:  b
 Idle Volume:
   Version:               5.4.11
   Status:                unavailable
   Build Date:            2022-12-21T03:10:13Z
   Build Machine:         releaseslave4.openstacklocal
   Build User:
   Build Directory:
   Hash:
   Package:               128T-5.4.11-4.el7
   Volume ID:             a

Completed in 5.53 seconds
admin@conductor-node-1.Conductor#

Then they can change the selected boot volume with:

set system software router <name> node <name> boot-volume {a|b}

To reboot into the other volume they can use the new reboot PCLI command which I added for this purpose in 6.3:

send command reboot router <name> node <name>

Chr1st0ph3rTurn3r and others added 27 commits February 20, 2024 17:34

adding DNAT

5729103

adding Dynamic Source NAT info and reorganizing the NAT section of th…

c532baf

…e docs.

updating CLI reference docs, and linking to them from NAT docs.

7c8c84a

fixing broken links

e711c1c

Merge branch 'master' into 6.3.0-release-documentation

4c4adc6

updates per review

040f663

adding net interf traffic engineering info, breaking out all of TE to…

6f47217

… make it more usable.

adding content for Traffic engineering - improving existing content, …

ab545ac

…adding network interface info.

forgot the graphic that will need to be updated anyway.

d38bde1

Merge branch 'master' into 6.3.0-release-documentation

d4196e3

Merge branch 'master' into 6.3.0-traffic-engineering

ab8e876

links and new screenshots

fabab2f

Merge branch 'master' into 6.3.0-traffic-engineering

7039d52

updates

259dca4

updates per scotts review - not complete yet - and attempt to fix bui…

8d5efbe

…ld issue.

Merge branch 'master' into 6.3.0-traffic-engineering

996e889

escaping the curly braces.

c9d9e84

Merge branch 'master' into 6.3.0-traffic-engineering

9b80ac9

adding TE output, some of it anyway.

b308df3

adding TE show stats output, and fixing the files that I incorrectly …

6c1a072

…added the \ delimiter.

Merge branch 'master' into 6.3.0-traffic-engineering

bf73d22

Merge branch 'master' into 6.3.0-traffic-engineering

13dd313

Merge branch 'master' into 6.3.0-release-documentation

330ab5e

escaping curly braces

81adfd8

escaping curly braces

7784635

Merge branch 'master' into 6.3.0-traffic-engineering

d1d2fc4

adding new doc for install steps and new graphics.

cd713fc

Chr1st0ph3rTurn3r requested a review from MichaelBaj as a code owner March 26, 2024 18:31

Chr1st0ph3rTurn3r added 2 commits March 26, 2024 15:09

merging other 6.3 docs in to collect updates and enable local builds…

0cf60d9

…" Merge branch '6.3.0-traffic-engineering' into 6.3.0-install-updates

adding u-iso install topic.

17d36b5

Chr1st0ph3rTurn3r and others added 11 commits April 4, 2024 11:28

adding traffic engineering info to the main docs branch Merge branch…

c465a5c

… '6.3.0-traffic-engineering' into 6.3.0-release-documentation

adding release notes and some other edits.

6e38852

adding new feature info to the release notes.

1f44728

minor text edits

00394a6

adding some upgrade text

cc038e0

Merge branch 'master' into 6.3.0-install-updates

1de439f

Merge branch 'master' into 6.3.0-release-documentation

7c932e7

Merge branch 'master' into 6.3.0-release-documentation

94101cf

revising and updaing upgrade procdess for 6.3

f451fe5

added some info about ha upgrades.

47e97cc

clarifying rollback info for 6.3

af12f77

Chr1st0ph3rTurn3r requested a review from tcarroll25 April 24, 2024 18:56

Chr1st0ph3rTurn3r and others added 5 commits April 24, 2024 18:02

fixing broken links

a5929e8

Merge branch 'master' into 6.3.0-install-updates

5c77750

Merge branch 'master' into 6.3.0-release-documentation

0c502ac

Merge branch 'master' into 6.3.0-release-documentation

9bc9fbb

Merge branch 'master' into 6.3.0-install-updates

779d2e3

tcarroll25 reviewed Apr 29, 2024

View reviewed changes

Chr1st0ph3rTurn3r added 5 commits April 30, 2024 16:45

updating new features list, adding force-up for LACP

d40a746

disabling link checker for slow wireguard links

ccf3664

updates to the new feature list and documentation.

6d5203a

updating with the release notes docMerge branch '6.3.0-release-docum…

d6e1a19

…entation' into 6.3.0-install-updates

beginning of tylers edits

dab3ad6

tcarroll25 self-assigned this May 2, 2024

Chr1st0ph3rTurn3r and others added 3 commits May 3, 2024 10:53

intrim commit

f562265

upgrade process edits

0f3504b

Merge branch 'master' into 6.3.0-install-updates

15c5c8e

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

6.3.0 install updates #696

6.3.0 install updates #696

Chr1st0ph3rTurn3r commented Mar 26, 2024

tcarroll25 left a comment

tcarroll25 Apr 29, 2024

tcarroll25 Apr 29, 2024

tcarroll25 Apr 29, 2024

tcarroll25 Apr 29, 2024

tcarroll25 Apr 29, 2024

tcarroll25 Apr 29, 2024

tcarroll25 May 2, 2024

tcarroll25 Apr 29, 2024

tcarroll25 May 2, 2024

tcarroll25 Apr 29, 2024

tcarroll25 Apr 29, 2024

tcarroll25 Apr 29, 2024

tcarroll25 Apr 29, 2024

tcarroll25 Apr 29, 2024

tcarroll25 commented May 2, 2024

		@@ -7,6 +7,10 @@ Occasionally you may want or need to revert to a previously running version of S

		## Rollback Considerations

		With an upgrade or installation of SSR v6.3.0, conductor rollbacks are performed using the `request system software revert` command from the conductor's PCLI. On routers, it is recommended that upgrades and rollbacks are performed from the conductor's GUI.


		### Upgrading Using the CLI

		Use the `request system software upgrade` command and the associated arguments to perform upgrades. All of the upgrade features are available from the command line as well as the GUI.


		1. Use the command `show assets` to list the devices managed by this conductor, and the software revision each asset is currently running.

		2. For a given asset, use the command `show asset [asset ID]` or `show asset software router [router name]` to view the available software upgrades for that asset. The list will be in the section labeled "Available for Download" at the end of the output.


		4. Once the download is complete, use the command `request system software upgrade router <rtr> node <node> version <image-version>` to initiate the upgrade process. View upgrade progress using `show system software upgrade router <rtr> node <node>`

		In a high availability deployment, the conductor upgrades each router node sequentially to minimize/avoid downtime. For manual upgrades, intiating an upgrade on one HA node or router will automatically upgrade the second node/router. However, it is still recommended to perform upgrade activity during periods of low traffic or maintenance windows.


		The `import iso` command is used to import packages contained within an SSR ISO onto a local repository, allowing the SSR to be upgraded without connecting to Juniper servers. When upgrading a conductor or when `offline-mode` is defined for a router, the ISO must be imported to the target conductor to perform the upgrade.

		Use the [import iso](cli_reference.md#import-iso) command to specify the exact `filepath` to the ISO, or to specify `hunt` which searches the disk for a file that matches the pattern `128T*.iso` (except in the following directories `/boot`, `/dev`, `/proc`, and `/sys`).

6.3.0 install updates #696

Are you sure you want to change the base?

6.3.0 install updates #696

Conversation

Chr1st0ph3rTurn3r commented Mar 26, 2024

tcarroll25 left a 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

Choose a reason for hiding this comment

Choose a reason for hiding this comment

tcarroll25 commented May 2, 2024