Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

request paragon cluster upgrade

Syntax

Description

Upgrade your Paragon Automation cluster. You can upgrade the cluster by downloading the upgrade file locally to your cluster node or by using the upgrade file directly from a remote server.

Options

local filename upgrade-filename

Upgrade the Paragon Automation cluster using a local upgrade file downloaded to the /root/epic/temp/ directory.

   

local filename upgrade-filename no-confirm

Upgrade the Paragon Automation cluster using a local file and ignore the cluster heath-check AMBER status and continue with upgrade. You are not prompted to confirm or stop or continue with the upgrade.

local filename upgrade-filename detach-process

The upgrade process runs in the background and frees up the CLI screen for any other tasks. The command runs the initial health checks and then proceeds with the upgrade. Once the upgrade process starts, the process is detached and moved into the background and you are returned to the command prompt. The upgrade output is logged in the /epic/temp/upgrade.log file. To monitor the status of the upgrade process and print the output onscreen, use the monitor start /epic/temp/upgrade.log command. When the upgrade process completes, a success message similar to the following is displayed on all the cluster nodes:

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

If you get disconnected from the VM during the upgrade process, you can periodically check the upgrade log file for status on the upgrade.

local filename upgrade-filename input input-string

Use the input input-string options to pass additional Ansible input parameters to the upgrade command. For example, to enable verbose logging:

local filename upgrade-filename input "-v"

local filename upgrade-filename patch

Apply a patch file to upgrade the Paragon Automation cluster to the patch version. The patch process is shorter than the upgrade process and patch files are smaller in size.

Note: Do not use the patch option to upgrade the cluster using a regular upgrade.tgz file.

remote url web-url

Upgrade the cluster using an upgrade file located on a remote site.

remote url web-url no-confirm

Upgrade the Paragon Automation cluster using a remote file and ignore the cluster heath-check AMBER status and continue with upgrade. You are not prompted to confirm or stop or continue with the upgrade.

remote url web-url detach-process

The upgrade process runs in the background and frees up the CLI screen for any other tasks. The command runs the initial health checks and then proceeds with the upgrade. Once the upgrade process starts, the process is detached and moved into the background and you are returned to the command prompt. The upgrade output is logged in the /epic/temp/upgrade.log file. To monitor the status of the upgrade process and print the output onscreen, use the monitor start /epic/temp/upgrade.log command. When the upgrade process completes, a success message similar to the following is displayed on all the cluster nodes:

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

If you get disconnected from the VM during the upgrade process, you can periodically check the upgrade log file for status on the upgrade.

remote url web-url disk-saving

Delete the upgrade.tgz file as soon as it is unzipped. The upgrade command extracts the contents of the upgrade.tgz file at the beginning of the upgrade process. This option deletes the zipped file as soon as it is unzipped to free up space on the primary node.

The advantage of using this option is that you need lesser free space for the upgrade process. The default minimum free space required is 15% of the total disk space + three times the upgrade file size. With this option you need a minimum free space of 15% of the total disk space + two times the upgrade file size.

The disadvantage of using this command is that if upgrade fails or is uninterrupted, you need to re-download the upgrade.tgz file again.

remote url web-url input input-string

Use the input input-string options to pass additional Ansible input parameters to the upgrade command. For example, to enable verbose logging:

remote url web-url input "-v"

remote url web-url patch

Apply a patch file to upgrade the Paragon Automation cluster to the patch version. The patch process is shorter than the upgrade process and patch files are smaller in size.

Note: Do not use the patch option to upgrade the cluster using a regular upgrade.tgz file.

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 local filename upgrade-filename detach-process

request paragon cluster upgrade remote url web-url

request paragon cluster upgrade remote url web-url no-confirm

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.

detach-process, disk-saving, input, and patch options introduced in Juniper Paragon Automation Release 2.4.0 .