Offline Upgrade Through Command Line Interface

To update HPE Aruba Networking Central On-Premises on offline mode through CLI Command-Line Interface. A console interface with a command line shell that allows users to execute text input as commands and convert these commands to appropriate functions. , complete the following steps:

Step 1: Enabling and Disabling Airgap via CLI

Step 2: Uploading the Checker File

Step 3: Uploading Signature Files and Upgrade Packages

Step 4: Selecting the Uploaded Files

Step 5: Verification and Extraction of the Files

Step 6: Triggering HPE Aruba Networking Central On-Premises Upgrade

Step 7: Retry Upgrade

Step 1: Enabling and Disabling Airgap via CLI

Airgap can be enabled and disabled through CLI option 4 System Configuration commands. Under option 4, you must use option 7, (4-7) for Airgap.

System Configuration Commands

Enter command option 4 from the main menu to view all the System Configuration commands.

1. System 2. File Operations 3. Show 4. System Configuration 5. Advanced 6. Security 7. Support 8. Temporary Root Shell 9. Authentication 10. Certificate configuration 11. Search commands ==================================== 0. exit Enter option [ 0 - 11 ]: 4

The supported System Configuration commands are displayed. These commands are used to configure system parameters like network setup, cluster setup, timezone setup. enable airgap mode, and also, upgrade the setup or perform a complete factory reset.

1. Upgrade 2. Network Setup 3. Proxy Setup 4. Setup Timezone 5. Setup NTP 6. Node Setup 7. Airgap 8. Datacenter Redundancy ==================================== b. back m. main menu 0. exit Enter option [ 0 - 8 ]:

Airgap

Enter command option 7 from the System Configuration menu to enable or disable Airgap mode for upgrade. Enabling Airgap allows you to upgrade the HPE Aruba Networking Central On-Premises setup offline without any internet access.

1. Upgrade 2. Network Setup 3. Proxy Setup 4. Setup Timezone 5. Setup NTP 6. Node Setup 7. Airgap 8. Datacenter Redundancy ==================================== b. back m. main menu 0. exit Enter option [ 0 - 8 ]: 7

1. Enable Airgap 2. Disable Airgap 3. Status ==================================== b. back m. main menu 0. exit Enter option [ 0 - 3 ]:

  • Enable Airgap—Enter command option 1 from the Airgap menu to enable the same.

    Enter option [ 0 - 3 ]: 1 Changing of Airgap mode requires restart of services and is recommended ONLY in maintenance window.Do you want to continue?(Y/N):

  • Disable Airgap—Enter command option 2 from the Airgap menu to disable the same.

    Enter option [ 0 - 3 ]: 2 Airgap is already disabled. Press [Enter] key to continue...

  • Status—Enter command option 3 from the Airgap menu to see the status.

    Enter option [ 0 - 3 ]: 3 Airgap is already disabled. Press [Enter] key to continue...

Step 2: Uploading the Checker File

Upgrading the Checker file is mandatory for every HPE Aruba Networking Central On-Premises release. The HPE Aruba Networking Central On-Premises checker file is uploaded on the HPE Networking Support Portal site in every 30 days. The purpose of the Checker file is to check regarding availability of any new release. Users receive a notification/ prompt in every 49 days in order to upload the Checker file to verify if there is any new HPE Aruba Networking Central On-Premises release available. The snooze period to upload the Checker file is 6 days. If a user doesn’t upload the checker file within the snooze period, the HPE Aruba Networking Central On-Premises user interface (UI User Interface. ) is completely blocked and cannot be accessed.

For any minor HPE Aruba Networking Central On-Premises release there is no time restriction to do the upgrade.

Upgrade Status

Based on the account login period, one of the following pages is displayed:

  1. Upgrade Available—This window is displayed when you log in to your HPE Aruba Networking Central On-Premises account within the deadline of the version upgrade (55 days from the date of version release). The upgrade available window provides the following information:
    • Current version—Current running version.
    • New versions—Next major available version.
    • Status—Provides the status and progress bar for the file transfer, verification, extract, and upgrade.
    • Deadline—Displays the number of days remaining for upgrade. The number of days varies depending on the version available date and the day of log in. For example, if the version was available on 8th of December and the user logs in on 10th of December, the remaining days gets changed to 53 days within which the account needs to be upgraded.
    • Remind in x days—Allows you to snooze the notification for some days. Notification can be snoozed for 7 days (55-20 remaining days), 5 days (20-10 remaining days), 3 days (10-5 remaining days), 2 days(5-3 remaining days), and 1 (for the rest remaining days). On snoozing the notification, you can use the account normally and the next notification comes after the set dates.

    The following example image displays the Upgrade available window.

    Figure 1  Upgrade Available

  1. Upgrade Check Required—This window is displayed when you log in to your HPE Aruba Networking Central On-Premises account after the deadline is missed. This window indicates that you have missed the upgrade check deadline and an immediate upgrade check is required. All the account GUI Graphical User Interface (GUI), is a type of UI enabling user interaction with electronic devices through symbols, graphical icons, and other visual metaphors instead of typed commands or text-based UIs. functionality is blocked till the upgrade availability is checked with the latest version of the update checker file. To check, follow the steps mentioned on the screen, and upload the update checker file. The upgrade check required window provides the following information:
    • Current Version—Current running version.
    • New Version—Next major available version.
    • Last Upgrade Check—Displays the date of last upgrade check.
    • Deadline—Displays the remaining days for mandatory upgrade check.
    • Upgrade Check Steps—Displays the steps to update the check file.

    To check the available version once notified, you can either drag and drop the update checker file from your local browser, or you can click the upload update checker file. Once the upgrade check is successful, you can use the account normally and the next notification comes after the set dates.

    Once the upgrade check is successful, the account comes to its normal functionality.

    The following example image displays the Upgrade check required window.

    Figure 2  Upgrade Check Required

  1. Upgrade Check Failed—This window is displayed when the user logs into HPE Aruba Networking Central On-Premises within the above mentioned periods. The upgrade check can fail because of the following reasons:
    • User uploaded an old version of upgrade file as compared to the latest available file

    Figure 3  Upgrade Version Check Required

    • User uploaded a lower version of upgrade check file as compared to the running version

    Figure 4  Upgrade Version Mismatch

Step 3: Uploading Signature Files and Upgrade Packages

After every HPE Aruba Networking Central On-Premises release, upgrade packages are uploaded to the HPE Networking Support Portal site. You should download it to your local file server and from there you can upload it to the COP server using CLI option.

System Configuration Commands

The System Configuration commands are used to configure system parameters like network setup, cluster setup, timezone setup and also, upgrade the setup or perform a complete factory reset.

Enter command option 4 from the main menu to view all the system configuration commands supported.

Enter option [ 0 - 11 ]: 4 1. Upgrade 2. Network Setup 3. Proxy Setup 4. Setup Timezone 5. Setup NTP 6. Node Setup 7. Airgap 8. Datacenter Redundancy ==================================== b. back m. main menu 0. exit Enter option [ 0 - 8 ]:

Upgrade

Enter command option 4-1 from the System Configuration commands menu to upgrade the system for either an online user or an offline user.

Enter option [ 0 - 8 ]: 1
1. Upload Package 2. Upgrade Status 3. Proceed With Upgrade ==================================== b. back m. main menu 0. exit Enter option [ 0 - 3 ]:

  • Upload Package

    Enter command option 4-1-1 from the Upgrade commands menu to view the options for uploading and selecting upgrade packages. The upgrade package includes the signature file and the installation file.

    Enter option [ 0 - 3 ]: 1 1. Select Signature and Installation File 2. Upload Signature and Installation via SCP 3. Upload Signature and Installation via SFTP ===================================== b. back m. main menu 0. exit Enter option [0 - 3]:

  • Upload Signature File and Installation File via SCP Secure Copy Protocol. SCP is a network protocol that supports file transfers between hosts on a network.

    Enter command option 4-1-1-2 from the Upload Package commands menu to upload the signature file and installation file through Secure Copy Protocol (SCP).

    For offline upgrade from HPE Aruba Networking Central On-Premises 2.5.7.6 onwards, use apps_pkg file instead of upgrade_pkg file. If you are on any older release than 2.5.7.6, you must continue using apps_upgrade_pkg file only.

    Uploading the Signature File

    Enter option [ 0 - 3 ]: 2 This will scp a sign file from the remote server to COP server Enter remote hostname and path (username@hostname:<filepath>): admin@10.xx.xx.xx:/build/2.5.7/454-20240206/apps_pkg -2.5.7-454-prod.sign Copying admin@10.xx.xx.xx:/build/2.5.7/454-20240206/apps_pkg_ -2.5.7-454-prod.sign COP server admin@10.xx.xx.xx's password: apps_pkg_-2.5.7-454-prod.sign Press [Enter] key to continue...

    After uploading the Signature file, press Enter and upload the Installation file.

    Uploading the Installation File

    Enter option [ 0 - 3 ]: 2 This will scp a sign file from the remote server to COP server Enter remote hostname and path (username@hostname:<filepath>): admin@10.xx.xx.xx:/build/2.5.7/454-24567891/apps_pkg -2.5.7-454-prod.tar.gz Copying admin@10.xx.xx.xx:/build/2.5.7/454-24567891/apps_pkg_ -2.5.7-454-prod.tar.gz to COP server admin@10.xx.xx.xx's password: apps_pkg-2.5.7-454-prod.tar.gz Press [Enter] key to continue...

  • Upload Signature File and Installation File via SFTP Secure File Transfer Protocol. SFTP is a network protocol that allows file access, file transfer, and file management functions over a secure connection.

    Enter command option 4-1-1-3 from the Upload Package commands menu to upload the signature file and installation file through Secure File Transfer Protocol (SFTP).

    For offline upgrade from HPE Aruba Networking Central On-Premises 2.5.7.6 onwards, use apps_pkg file instead of upgrade_pkg file. If you are on any older release than 2.5.7.6, you must continue using apps_upgrade_pkg file only.

    Uploading the Signature File

    Enter option [ 0 - 3 ]: 3 This will scp a sign file from the remote server to COP server Enter remote hostname and path (username@hostname:<filepath>): admin@10.xx.xx.xx:/build/2.5.7/454-20240206/apps_pkg -2.5.7-454-prod.sign Copying admin@10.xx.xx.xx:/build/2.5.7/454-20240206/apps_pkg_ -2.5.7-454-prod.sign to COP server administrator@10.xx.xx.xx's password: apps_pkg-2.5.7-454-prod.sign Press [Enter] key to continue...

    After uploading the Signature file, press Enter and upload the Installation file.

    Uploading the Installation File

    Enter option [ 0 - 3 ]: 3 This will scp a sign file from the remote server to COP server Enter remote hostname and path (username@hostname:<filepath>): admin@10.xx.xx.xx:/build/2.5.7/454-24567891/apps_pkg -2.5.7-454-prod.tar.gz Copying admin@10.xx.xx.xx:/build/2.5.7/454-24567891/apps_pkg_ -2.5.7-454-prod.tar.gz to COP server administrator@10.xx.xx.xx's password: apps_pkg-2.5.7-454-prod.tar.gz Press [Enter] key to continue...

Step 4: Selecting the Uploaded Files

After uploading the upgrade packages to HPE Aruba Networking Central On-Premises server, you must select the signature and installation files to initiate the offline upgrade.

Select Signature and Installation File

Enter command option 4-1-1-1 from the Upload Package commands menu to select the files.

Enter option [ 0 - 3 ]: 1 1. apps_pkg-2.5.7-369-dev_from_10.0.0-GA02.sign Choose a signature file [1 - 1]: 1 Selected file is :: apps_pkg-2.5.7-369-dev_from_10.0.0-GA02.sign 1. apps_pkg-2.5.7-369-dev_from_10.0.0-GA02.tar.gz Choose an installation file [1 - 1]:
1 Selected file is :: apps_pkg-2.5.7-369-dev_from_10.0.0-GA02.tar.gz
============Verification in progress=========== Press [Enter] key to continue...

For offline upgrade from HPE Aruba Networking Central On-Premises 2.5.7.6 onwards, use the apps_pkg file instead of the upgrade_pkg file. If you are on any older release than 2.5.7.6, you must continue using the apps_upgrade_pkg file only.

Step 5: Verification and Extraction of the Files

After selecting the uploaded files, validation of the files begin and after the validation is successful, file extraction is started. After the extraction is complete, you can manually trigger the upgrade through either the CLI or UI.

Upgrade Status

After selecting the file, to confirm regarding the extraction process you can monitor the status in the UI as well in the CLI. For more information on selecting files, see Step 4: Selecting the Uploaded Files.

To monitor the status through the CLI, enter command option 4-1-2 from the Upgrade commands menu.

Enter option [ 0 - 3 ]: 2
COP Server Status -------------------------------------------------------------------------------- Current Version : 2.5.7.0 Latest Version : 2.5.7.0 Online Customer : false Upgrade Status : EXTRACT_IN_PROGRESS Upgrade Available : true Sign File Transfer Completion Percentage : 100 Upg Pkg File Transfer Completion Percentage : 100 Pkg Sign Validate Completion Percentage : 100 Extract Completion Percentage : 100 Upgrade Stage Completion Percentage : 0 -------------------------------------------------------------------------------- - Last Sign File Transfer Status : SUCCESS Last Sign File Transfer Message : Last Sign File Transfer Time : 2023-07-26 06:10:50 Last Upg Pkg File Transfer Status : SUCCESS Last Upg Pkg File Transfer Message : Last Upg pkg File Transfer Time : 2023-07-26 06:10:54 Last Pkg Sign Validate Status : SUCCESS Last Pkg Sign Validate Message : Last Pkg Sign Validate Time : 2023-07-26 06:21:05 Last Extract Status : SUCCESS Last Extract Message : Last Extract Time : 2023-07-26 11:14:34 Last Upgrade Status : SUCCESS Last Upgrade Message : Last Upgrade Time : 2023-07-21 09:58:55 --------------------------------------------------------------------------------
Press [Enter] key to continue

Step 6: Triggering HPE Aruba Networking Central On-Premises Upgrade

Once extraction is completed, upgrade status will change to UPGRADE_NOT_STARTED. You can trigger the update through the CLI or GUI.

For CLI, enter option 4-1-3 Proceed With Upgrade:

Enter option [ 0 - 3 ]: 3 Please confirm to start the upgrade to 2.5.7.0 version (Y/N):

Step 7: Retry Upgrade

In case the upgrade fails, you can perform a retry through the CLI or GUI.

  • To retry upgrade through CLI, you have to use the same option 4-1-3 Proceed with Upgrade again.

    1. Upload Package 2. Upgrade Status 3. Proceed With Upgrade ==================================== b. back m. main menu 0. exit Enter option [ 0 - 3 ]: 3 Previous Upgrade was failed. Do you want to retry(Y/N):

After HPE Aruba Networking Central On-Premises is successfully upgraded, the following screen is displayed:

1. Upload Package 2. Upgrade Status

3. Proceed With Upgrade ========================= b. back m. main text 0. exit Enter option [ 0 - 3 ]: 2
COP Server Status -------------------------------------------------------------------------------- Current Version : 2.x.x.x Latest Version : 2.x.x.x Online Customer : false Upgrade Status : UP_TO_DATE Upgrade Available : false Sign File Transfer Completion Percentage : 100 Upg Pkg File Transfer Completion Percentage : 100 Pkg Sign Validate Completion Percentage : 100 Extract Completion Percentage : 100 Upgrade Readiness Check Completion Percentage : 100 Upgrade Stage Completion Percentage : 100 -------------------------------------------------------------------------------- - Last Sign File Transfer Status : SUCCESS Last Sign File Transfer Message : Last Sign File Transfer Time : 2025-07-26 06:10:50 Last Upg Pkg File Transfer Status : SUCCESS Last Upg Pkg File Transfer Message : Last Upg pkg File Transfer Time : 2025-07-26 06:10:54 Last Pkg Sign Validate Status : SUCCESS Last Pkg Sign Validate Message : Last Pkg Sign Validate Time : 2025-07-26 06:21:05 Last Extract Status : SUCCESS Last Extract Message : Last Extract Time : 2025-07-26 11:14:34 Last Upgrade Readiness Check Status : SUCCESS Last Upgrade Readiness Check Message : Last Upgrade Readiness Check Time : 2025-07-26 12:48:07 Last Upgrade Status : SUCCESS Last Upgrade Message : Last Upgrade Time : 2023-07-21 09:58:55 --------------------------------------------------------------------------------
Press [Enter] key to continue...