request paragon cluster upgrade
Syntax
request paragon cluster upgrade local filename upgrade-filename (none|no-confirm)
request paragon cluster upgrade url web-url
request paragon cluster upgrade remote url web-url (none|no-confirm)
Description
Upgrade your Paragon Automation cluster.
When upgrading from an older version of release 2.3.0 to a later version of 2.3.0,
the upgrade command checks the health of the cluster before upgrading. If the
cluster health check returns a RED status, the cluster is not
upgraded. If the cluster health check returns an AMBER status, you
are prompted to choose to continue or stop the upgrade. You can also use the
no-confirm option to ignore the AMBER status
and continue with upgrade without being prompted. If the cluster health check
returns a GREEN status, the cluster is upgraded requiring no
further input.
Options
|
local filename upgrade-filename |
Upgrade the Paragon Automation cluster using a local file downloaded to the /root/epic/temp/ directory. Note:
When upgrading from release 2.2.0 to release 2.3.0, use the
|
|
url web-url |
Upgrade the cluster using a file on a remote site. Note:
Use this command when upgrading from release 2.2.0 to release
2.3.0. Use the |
|
local filename upgrade-filename no-confirm |
Upgrade the Paragon Automation cluster using a local file and
ignore the cluster heath-check Use this command if you are upgrading from an older version of release 2.3.0 to a newer version. |
|
remote url web-url |
Upgrade the cluster using a file on a remote site. Use this command if you are upgrading from an older version of release 2.3.0 to a newer version. |
|
remote url web-url no-confirm |
Upgrade the Paragon Automation cluster using a remote file and
ignore the cluster heath-check Use this command if you are upgrading from an older version of release 2.3.0 to a newer version. |
Required Privilege Level
configure
Output Fields
When you enter this command, you are provided feedback on the status of your request.
Sample Output
- request paragon cluster upgrade local filename upgrade-filename
- request paragon cluster upgrade local filename upgrade-filename
- request paragon cluster upgrade remote url web-url
- request paragon cluster upgrade remote url web-url no-confirm
request paragon cluster upgrade local filename upgrade-filename
root@node> request paragon cluster upgrade local filename upgrade_eop- release-2.3.0.6688.g63026f4af7.tgz Checking paragon cluster system health before proceeding with cluster upgrade. This will take a minute... ... <output snipped> ... ======================================================= Overall cluster status ======================================================= GREEN ======================================================= Paragon cluster is healthy. Proceed with Paragon cluster upgrade. Upgrade is in progress ... Updated to build: paragon-release-2.3.0.6688.g63026f4af7 Paragon Cluster upgrade is successful! Run 'request paragon health-check' command to check current system health with upgraded Paragon cluster. Please continue to primary host node to upgrade Paragon-shell and update OVA system files by: /root/epic/upgrade_paragon-shell_ova-system.sh
This is the sample output when you are upgrading from an older version of release 2.3.0 to a newer version.
request paragon cluster upgrade local filename upgrade-filename
root@node> request paragon cluster upgrade local filename upgrade_eop- release-2.3.0.6688.g63026f4af7.tgz Checking paragon cluster system health before proceeding with cluster upgrade. This will take a minute... ... <output snipped> ... ======================================================= Overall cluster status ======================================================= RED ======================================================= [Error] Paragon cluster is in bad state. Please fix it before trying to upgrade.
This is the sample output when you are upgrading from an older version of release 2.3.0 to a newer version.
request paragon cluster upgrade remote url web-url
root@node> request paragon cluster upgrade remote url https://10.2.3.4/eop-images/upgrade_eop-release-2.3.0.6688.g63026f4af7.tgz
Checking paragon cluster system health before proceeding with cluster upgrade. This will take a minute...
...
<output snipped>
...
=======================================================
Overall cluster status
=======================================================
AMBER
=======================================================
[Warning] Paragon cluster is unhealthy.
Do you want to proceed? (Y/N) y
Proceed with cluster upgrade.
Upgrading paragon cluster from https://10.2.3.4/eop-images/
Downloading tarball file upgrade_paragon-release-2.3.0.6688.g63026f4af7
Download file size: 28,831,677,064 bytes
Current disk Usage:
Total: 263,622,004,736 bytes
Used: 106,109,399,040 bytes
Available: 145,685,159,936 bytes
Please wait for current download to finish... (File is large. It may take a while.)
Upgrade tarball file is downloaded.
Upgrade is in progress ...
Updated to build: eop-release-2.3.0.6688.g63026f4af7
Paragon Cluster upgrade is successful!
Run 'request paragon health-check' command to check current system health with upgraded Paragoncluster.
Please continue to primary host node to upgrade Paragon-shell and update OVA system files by:
/root/epic/upgrade_paragon-shell_ova-system.shThis is the sample output when you are upgrading from an older version of release 2.3.0 to a newer version.
request paragon cluster upgrade remote url web-url no-confirm
root@node> request paragon cluster upgrade remote url https://10.2.3.4/eop-images/upgrade_eop-release-2.3.0.6688.g63026f4af7.tgz no-confirm
Checking paragon cluster system health before proceeding with cluster upgrade. This will take a minute...
...
<output snipped>
...
=======================================================
Overall cluster status
=======================================================
AMBER
=======================================================
[Warning] Paragon cluster is unhealthy.
Proceed with cluster upgrade with no-confirm flag being set.
Upgrading paragon cluster from https://10.2.3.4/eop-images/
Downloading tarball file upgrade_paragon-release-2.3.0.6688.g63026f4af7
Download file size: 28,831,677,064 bytes
Current disk Usage:
Total: 263,622,004,736 bytes
Used: 106,109,399,040 bytes
Available: 145,685,159,936 bytes
Please wait for current download to finish... (File is large. It may take a while.)
Upgrade tarball file is downloaded.
Upgrade is in progress ...
Updated to build: eop-release-2.3.0.6688.g63026f4af7
Paragon Cluster upgrade is successful!
Run 'request paragon health-check' command to check current system health with upgraded Paragon
cluster.
Please continue to primary host node to upgrade Paragon-shell and update OVA system files by:
/root/epic/upgrade_paragon-shell_ova-system.shThis is the sample output when you are upgrading from an older version of release 2.3.0 to a newer version.
Release Information
Command introduced in Juniper Paragon Automation Release 2.0.0.
remote url keyword introduced in Juniper Paragon Automation Release
2.3.0.
no-confirm option introduced in Juniper Paragon Automation Release
2.3.0.