Add_workflow_for_techpubs |
---|
AUTH1 | UserResourceIdentifier{userKey=8a00a0c86ca23f8a016cd6ed6fe90013, userName='null'} |
---|
REV5 | UserResourceIdentifier{userKey=8a00a0c85b2726c2015b58aa779d0003, userName='null'} |
---|
REV6 | UserResourceIdentifier{userKey=8a00a0c866dc3dee0166ea60b86f0014, userName='null'} |
---|
REV3 | UserResourceIdentifier{userKey=8a00a0c866dc3dee0166f54435370023, userName='null'} |
---|
REV1 | UserResourceIdentifier{userKey=8a00a0c866dc3dee0166e4fafc100006, userName='null'} |
---|
|
Note |
---|
|
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. |
...
It is not possible to execute an in-place software downgrade from
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.
You must take Take a backup
/or snapshot prior to upgrading.
...
Take a backup or snapshot of your
system. Info |
---|
|
Test the restore procedure before continuing. Do not proceed unless this is successful. |
Download the
artifacts install-ev.sh and ev-fullpkg.tar.xz to the /opt directory of your system (reach out to Ribbon Support for the URLs for these artifacts):. Info |
---|
|
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. Reach out to Ribbon Support for more information. |
Code Block |
---|
cd /opt/ |
Enable read-write-execute permissions for the copied files using the commands given below:
Code Block |
---|
chmod +x install-ev.sh |
Execute the following command to start the installation process:
Code Block |
---|
./install-ev.sh |
As the installation proceeds (upgrading Docker Compose, Docker and ), 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 “Installation/Upgrade Completed”.
To check whether the containers started successfully, use the following command:
Code Block |
---|
docker ps --format "table
{{.ID}}\t{{.Image}}\t{{.Status}}\t{{.Names}}" |
![docker ps_code8.png](/plugins/servlet/confluence/placeholder/unknown-attachment?locale=en_GB&version=2)
Tip |
---|
|
Make sure that the STATUS is healthy. If unhealthy statuses exist, run the following command and check the Health section of the output: Code Block |
---|
docker inspect $container_name |
For example:
Code Block |
---|
docker inspect scc |
|
Once the installation completes, optionally run a basic sanity check using the below command:
Code Block |
---|
cd /opt/scc-build ; ./ev_check.sh post-install |
Info |
---|
|
Upgrade to 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: Code Block |
---|
#docker exec -it services bash -c "./usr/local/bin/sip-callid-migration" |
|
...