Skip to main content
Skip table of contents

Upgrading Blue Cedar Connect Gateway

This section explains how to upgrade to the latest version of the Blue Cedar Connect Gateway. Choose one of these methods to upgrade the gateway:

Upgrading the Connect Gateway with internet connectivity

Prerequisites

  • The gateway must already have an existing and functional image.
  • The gateway must have network access.

Copy, activate, and execute the new image for the gateway

If using the Docker registry to retrieve the upgrade image, identify the available images with this command.

  • BASH
    > request list-images 
    message "Image list '
    Remote registry images:
    ==================
    
    bluecedar-connect-gateway:4.2.0
    bluecedar-connect-gateway:4.1.4
    bluecedar-connect-gateway:4.1.3
    
    Local registry images:
    ==================
    
    bluecedar-connect-gateway:4.1.4:[ACTIVE]
    '";

    By default, the gateway lists the most recent 5 images. If you don't see the image you're looking for, you can increase the limit with this command option:

    BASH
    > request list-images num-images 10 

Install the new image of the gateway using this template, which copies an image from the remote registry to the local registry.

  • BASH
    > request install-image image-name bluecedar-connect-gateway:4.1.4 
  • To check that the file was installed in the local registry, confirm with this list-images command:

    BASH
    > request list-images type local

Select and activate the new image.

  • Use this template to select the new image, using the name as it is listed in the local registry:
  • BASH
    > request select-image image-name bluecedar-connect-gateway:4.1.4 

Perform an upgrade-image to migrate your configuration and restart the new (active) image.

  • BASH
    > request upgrade-image
  • Note: This command restarts the CLI; you need to log in again to continue your CLI session.
  • Note: Although you can select any release, you cannot upgrade to an earlier release.

The upgrade is complete. You can resume configuring the gateway.

Upgrading the Connect Gateway offline

Prerequisites

Before you upgrade to the new image for the gateway, make sure the following prerequisites have been met:

  • The new image is downloaded to a device which supports scp (client).

    Note: In the instructions below, "scp" is used for the secure copy (scp) client on your computer. On Mac or Linux, the command is scp; it is installed by default. Free scp clients for Windows are available, such as pscp.
  • The gateway must already have an existing and functional image.
  • The gateway must have network access and connectivity to the device where the new image is located.
  • Make sure the gateway is configured to allow secure copy. By default, secure copy is enabled for the gateway. If secure copy has been disabled, then enter these CLI commands at the command prompt to enable secure copy:

    BASH
    > configure
    % set system ssh scp-enable true
    % commit

    You can now perform a secure copy on the gateway.

Copy, activate, and execute the new image for the gateway

Assuming you have an upgrade file from Blue Cedar, from the device with the downloaded file, perform a secure copy of the new image to the gateway using this template:

  • BASH
    > scp bluecedar-connect-gateway_x.x.x.tar admin@<VM-IP-or-hostname>:
  • Example:
  • BASH
    % scp bluecedar-connect-gateway_4.2.1.tar admin@192.168.3.76:
  • To check that the file was copied, on the gateway (in operational mode) enter “file list” to list the files that the gateway stores. You should see the name of the file that you uploaded.

Install the new image of the gateway using this template: 

  • BASH
    > request install-image file bluecedar-connect-gateway_4.1.4.tar
  • To check that the file was installed in the local registry, confirm with this list-images command:

    BASH
    > request list-images type local

Select and activate the new image.

  • Use this template to select the new image: 
  • BASH
    > request select-image image-name gatewayimage 

Perform an  upgrade-image  to migrate your configuration and restart the new (active) image.

  • BASH
    > request upgrade-image
  • Note: This command restarts the CLI; you need to log in again to continue your CLI session.
  • Note: Although you can select any release, you cannot upgrade to an earlier release.

The upgrade is complete. You can resume configuring the gateway.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.