eaa3adb96c
Some substitutions also added to accomodate StX vs partner file naming.
Add 750.006 alarm to performing-an-orchestrated-upgrade
Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: I33588f3c1b22cd0dbc96133cf8eb056c8c2e5162
Signed-off-by: Ron Stone <ronald.stone@windriver.com>
(cherry picked from commit 0012d76f09)
40 lines
1.4 KiB
ReStructuredText
40 lines
1.4 KiB
ReStructuredText
|
|
.. mzg1592854560344
|
|
.. _manual-upgrade-overview:
|
|
|
|
=======================
|
|
Manual Upgrade Overview
|
|
=======================
|
|
|
|
|prod-long| enables you to upgrade the software across your Simplex, Duplex,
|
|
Standard, |prod-dc|, and subcloud deployments.
|
|
|
|
.. note::
|
|
Upgrading |prod-dc| is distinct from upgrading other |prod| configurations.
|
|
|
|
.. xbooklink For information on updating |prod-dc|, see |distcloud-doc|: :ref:`Upgrade
|
|
Management <upgrade-management-overview>`.
|
|
|
|
An upgrade can be performed manually or by the Upgrade Orchestrator which
|
|
automates a rolling install of an update across all of the |prod-long| hosts.
|
|
This section describes the manual upgrade procedures.
|
|
|
|
.. xbooklink For the orchestrated
|
|
procedure, see |distcloud-doc|: :ref:`Orchestration Upgrade Overview
|
|
<orchestration-upgrade-overview>`.
|
|
|
|
Before starting the upgrades process, the system must be “patch current,” there
|
|
must be no management-affecting alarms present on the system, the new software
|
|
load must be imported, and a valid license file for the upgrade must be
|
|
installed.
|
|
|
|
The upgrade procedure is different for the All-in-One Simplex configuration
|
|
versus the All-in-One Duplex, and Standard configurations. For more
|
|
information, see:
|
|
|
|
.. _manual-upgrade-overview-ul-bcp-ght-cmb:
|
|
|
|
- :ref:`Upgrading All-in-One Simplex <upgrading-all-in-one-simplex>`
|
|
|
|
- :ref:`Upgrading All-in-One Duplex / Standard <upgrading-all-in-one-duplex-or-standard>`
|