6.3.0 install updates #696
Conversation
… make it more usable.
…adding network interface info.
…added the \ delimiter.
…" Merge branch '6.3.0-traffic-engineering' into 6.3.0-install-updates
Merge branch '6.3.0-install-updates' of github.com:128technology/docs into 6.3.0-install-updates
docs/intro_upgrade_considerations.md
Outdated
|
|
||
| ### Upgrade Installer | ||
| Before **upgrading to, or installing** version 5.4, update the Installer to the latest version. Failing to upgrade the installer may result in a rollback failure, should a rollback be necessary at any time. | ||
| Before **upgrading or installing**, update the Installer to the latest version. Failing to upgrade the installer may result in a rollback failure, should a rollback be necessary at any time. |
There was a problem hiding this comment.
Upgrading the installer manually is only required if the user is performing a rollback with the interactive installer. The next section correctly says that rollbacks are performed using request system software revert. There is no need to upgrade the installer manually when using the PCLI command.
|
|
||
| ### 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 are performed from the conductor's GUI. Router rollbacks must be performed from the PCLI. |
There was a problem hiding this comment.
this section is called intro_upgrade_consideration, is this supposed to discuss rollback as well? Or should this be Upgrade Consideration?
docs/upgrade_ibu_conductor.md
Outdated
| * 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`. |
There was a problem hiding this comment.
To follow up, this is added to the PCLI but not the GUI with a new Install Type section:
Image based:
[email protected]# show assets
Mon 2024-09-09 18:14:18 UTC
Retrieving assets...
=========== =========== ===================== ============= ============== ================ ================ ========
Router Node Asset Id SSR Version Install Type Status Time in Status Errors
=========== =========== ===================== ============= ============== ================ ================ ========
Conductor t106-dut1 t106-dut1.novalocal 7.0.0-1.el9 Image Synchronized 34m 44s 0
t106-dut2 t106-dut2.novalocal 7.0.0-1.el9 Image Synchronized 21m 19s 0
Package based:
[email protected]_EAST_CONDUCTOR# show assets
Mon 2024-09-09 18:15:20 UTC
✔ Retrieving assets...
==================== ================== ===================== ====================== ============== ============== ================ ========
Router Node Asset Id SSR Version Install Type Status Time in Status Errors
==================== ================== ===================== ====================== ============== ============== ================ ========
RTR_EAST_COMBO combo-east-1 t212-dut3.novalocal 6.3.0-1.r1.debug.el7 Package Synchronized 3d 23h 18m 58s 0
combo-east-2 t212-dut4.novalocal 6.3.0-1.r1.debug.el7 Package Synchronized 4d 2h 40m 27s 0
RTR_EAST_CONDUCTOR conductor-east-1 t212-dut1.novalocal 6.3.0-1.r1.debug.el7 Package Synchronized 4d 2h 42m 57s 0
conductor-east-2 t212-dut2.novalocal 6.3.0-1.r1.debug.el7 Package Synchronized 4d 2h 43m 14s 0
Completed in 0.04 seconds
docs/upgrade_restricted_access.md
Outdated
|
|
||
| - `SSR-6.3.0-xx.r1.el7.x86_64.ibu-v1.iso` | ||
| - `SSR-6.3.0-xx.r1.el7.x86_64.ibu-v1.tar.sha256sum` | ||
| - `SSR-6.3.0-xx.r1.el7.x86_64.ibu-v1.tar.sha256sum.asc` |
There was a problem hiding this comment.
We already spoke this but I'll leave a comment as well. Recent SSR images (6.2.6+ and 6.3.0+) will include the checksum and signature files in the ISO so there will be no need to download them separately. This section could be reworded to say the user may need to download the checksum and signature files for older images if an error is returned during the import process
docs/upgrade_router.md
Outdated
|
|
||
| 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 system software available router <router> node <node>` to show the versions available for upgrade, or the `show system software download router <router> node <node>` to show the versions available for download. |
There was a problem hiding this comment.
Just FYI it may be worth mentioning that a user can execute all these commands a the router level as well if they want to view available software, download and view the status of the download from both nodes in an HA router (or conductor) at once:
View available software for both nodes in an HA router:
show system software available router <router>
Download a version to both nodes in an HA router at once :
request system software download router <rtr> version <image-version>
Viewing download status:
show system software download router <rtr>
docs/upgrade_router.md
Outdated
|
|
||
| 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 system software available router <router> node <node>` to show the versions available for upgrade, or the `show system software download router <router> node <node>` to show the versions available for download. |
There was a problem hiding this comment.
The command show system software available actually shows the versions of software available to download (not upgrade to) and the command show system software download shows a few things, in progress download, completed downloads and failed downloads. Completed downloads are versions which are available to upgrade to.
docs/upgrade_router.md
Outdated
|
|
||
| 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. | ||
|
|
||
| If you perform an upgrade from the CLI using the `request system software upgrade router <conductor-router-name>` from an HA conductor, it launches a sequenced self upgrade, one node at a time. In a situation where you prefer to upgrade each node manually, you can target each node directly using `request system software upgrade router <conductor-router-name> node <conductor-node-name>`. When the upgrade is complete on the first node, you may run the command on the second node. |
There was a problem hiding this comment.
There is also a show system software upgrade command to view the status of an in progress upgrade.
docs/intro_rollback.md
Outdated
|
|
||
| ## Rollback Considerations | ||
|
|
||
| Rollbacks are not supported if configuration changes are made after the conductor or router are updated to the target version. For example, if the conductor and/or router has been upgraded to version 5.4, and a new feature such as Traffic Engineering is configured on the target conductor or router, rolling back to an earlier version of software may result in loss of configuration or router functionality. | ||
| 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 are performed from the conductor's GUI. Router rollbacks must be performed from the PCLI. |
There was a problem hiding this comment.
There is also a show system software revert command to show the progress of a revert operation
No description provided.