Skip to end of metadata
Go to start of metadata

Caution

EdgeView 16.2.0 includes significant changes to data storage. If any of your disks are currently more than 50% full, do not proceed with the installation; instead, add more disk space before proceeding. The script automatically performs data migration and backup of your existing data; however, this uses significant disk space.

If you have questions or concerns, contact Ribbon Support Portal before proceeding with your upgrade. It is highly recommended to review the section on storage configuration: Configuring Storage for EdgeView and Docker, as much of it changed from previous releases.

Note

For EdgeView versions 15.3.0 and higher, all current and future EdgeView and Docker data is copied/written to /var/lib/docker/

It is not possible to execute an in-place software downgrade from EdgeView 16.2.0 to any version before 15.3.0, due to storage infrastructure changes. Please take this into account when crafting your change management plan for the upgrade. Take a backup or snapshot prior to upgrading. 

In EdgeView versions 15.3.0 and higher, improvements impact the upgrade process, including:

  • Your system is automatically upgraded to recent, stable versions of Docker and Docker Compose to help improve the performance and reliability of EdgeView systems.
  • Your data directories are migrated from bind mounted volumes to Docker volumes to allow future improvements on EdgeView software.
  • If you were previously using the devicemapper Docker storage driver, your configuration is updated to use overlay2 since devicemapper is deprecated by Docker.

Perform the following installation steps when upgrading EdgeView:

  1. Take a backup or snapshot of your EdgeView system. 

    Note

    Test the restore procedure before continuing. Do not proceed unless this is successful.

  2. Download the three EdgeView artifacts install-ev.shev-fullpkg.tar.xz and MD5SUM.txt to the /opt directory of your system.                                    

    Note

    For these artifacts, log in to Salesforce and open an additional browser for the Ribbon Global Software Center (GSC). In the Downloads section, search for the name and version of the required software.
    To download a software package from the Ribbon Support Portal, see Ribbon Support Portal - Download Center.

  3. Enable read-write-execute permissions for the copied files using the commands given below:

    chmod +x install-ev.sh

  4. Execute the following command to start the installation process:

    ./install-ev.sh

    As the installation proceeds (upgrading Docker Compose, Docker and EdgeView), provide input, when prompted.
    The installation creates a log file of all actions for historical review/troubleshooting using the file format: $MM-DD-YYYY-ev-install.log
    When prompted, enter validation or update information related to your networking configuration environment.
    Once the installation completes, the directory scc-build is created, and the console screen displays the message “EdgeViewInstallation/Upgrade Completed”. 

  5. To check whether the containers started successfully, use the following command:

    docker ps --format "table
    {{.ID}}\t{{.Image}}\t{{.Status}}\t{{.Names}}"

    Tip

    Make sure that the STATUS is healthy. If unhealthy statuses exist, run the following command and check the Health section of the output:

    docker inspect $container_name

    For example:

    docker inspect scc
  6. Once the installation completes, optionally run a basic sanity check using the below command:

    cd /opt/scc-build ; ./ev_check.sh post-install

    Note

    Upgrade to EdgeView 16.2.0 requires the manual execution of the script to migrate existing MOS call records. For this, go to the scc-build directory and execute the following command:

    #docker exec -it services bash -c "./usr/local/bin/sip-callid-migration"