Software Rollback - EMS/System

IMG 2020

Note: Since release 2.3.0 SP2 (Build 2.3.0.76), the IMG 2020 EMS host installer package uses RPM instead of the InstallAnywhere tool.

This page covers both type of installations. make sure to use the proper method.

The procedure below describes the steps needed to downgrade or rollback the individual node software as well as rollback the EMS software running on the Virtual Machine. Once the EMS software has been rolled back on the Virtual Machine, each of the individual nodes communicating with the EMS software must then also be rolled back. The EMS software version and the system software version running on the individual nodes must both match. The procedure assumes that the EMS and node software had previously been upgraded and all previous software files are accessible. Follow the steps below to downgrade/roll-back both the EMS and node software.

Note: When rolling back software from an upgraded point release such as 2.3 to an older release such as 2.2, the current license file will need to be removed and replaced with the license file that was archived during the upgrade process. Failure to load the older release license file could result in the IMG 2020 not configuring after the rollback has completed.

EMS and System Software Files

During the initial Software Upgrade procedure, two software files were upgraded. They are as follows:

The downgrade procedure will downgrade these same two files. Verify that the older version of the webuid-2.3.0-xxx-Linux.rpm or bdn2020_host_ver230xxx.bin is still located in the /home/dialogic/ftpBuilds directory of the Virtual Machine EMS installation. Also, verify that the older version of the bdn2020_ver230xxx.bin file is still located in the directory of the ftp server or SD card set up to load the software from. If either of these files are needed, contact the support team and they can supply you with the proper files.

Note: The procedures below describe the rollback process. If during the rollback process, the copying and modifying of files is done using an SD Reader, the steps below will be the same except the modifications will be achieved through the SD Reader/Writer.

Modify Software Download Site

During the upgrade process, the node software, bdn2020_ver230xxx.bin (xxx=build number), was upgraded by modifying the information at the download location site (FTP Server or SD Card). To downgrade the node software, the information must be modified back to its original state. To configure this site to be able to load the original/previous software, two pieces of information must be modified.

• The original/previous software is still located at the download site. If not, the software must be transferred to that site. -and-

• The System Software Filename line in the bootup.cfg file must point to the original/previous software.

Before proceeding, verify that the download site has been modified to be able to load the original/previous software. Refer to the Software Install Overview topic for the different download locations and procedures.

Clear Previously Saved Node Configuration and Install Node Software

Once the download site information has been updated, the existing configuration on each IMG 2020 node must be cleared as well as the node software must be re-loaded into each node. These two tasks can be accomplished through the Web UI. Follow the steps below to load the original/previous software into each individual IMG 2020 node.

1. At this point, if not currently logged into the Web UI, log into the Web UI. The table below displays the default login credentials.

2. In the Web UI select the New icon from the File menu tab. (File > New).  Select Yes to the Confirm dialog box that appears informing the user that the "System will reboot, start a new configuration?".

3. Select OK to the second dialog box displaying "System has finished generating a new configuration. Press OK to reload browser."

4. The Web UI will automatically close and bring user back to a Login Screen. Any nodes connected to the Web UI interface will reboot and load the updated software. The loading of software can take anywhere from 30 seconds to 3 minutes depending on where the IMG 2020 is getting load from (SD Card or FTP Server).

5. Verify each node has the correct software. Using SSH, connect to each node and login using the credentials displayed above. Once connected, enter the "b" command and verify the S/W Version: displayed is correct.

6. After software has been verified, log back into the Web UI. At this point, the file that tells the EMS application what configuration file to load and what build to use has been wiped out. This will force the user to a screen in the Web UI that has no configuration in it.

Install Original/Previous Host Software

The software in each of the individual nodes has now been downgraded to the software build that was loaded on them prior to the initial upgrade. Now the EMS software on the VM needs to be downgraded. Follow instruction below to downgrade the EMS software.

1. Using SSH, connect to /home/dialogic/ftpBuilds directory on the VM. Become a superuser by entering the following commands:
   [dialogic@localhost ~]$ su
   Password: Dial0gic (Capital D, zero for o)
   
   If the previous version uses the new RPM package format, go to step 3 immediately.

2. Install the original/previous version of the EMS Software using the commands below. The Web UI interface will automatically log out during the installation process.
   [root@localhost /]# ./bdn2020_host_ver230xxx.bin (xxx = build number prior to upgrade)

3. Search installed rpm by running following command
   [root@localhost ftpBuilds]# rpm –qa | grep webuid
   webuid-2.3.0-76.i686

4. Now uninstall RPM Package using following command
   [root@localhost ftpBuilds]$ rpm -e webuid-2.3.0-76.i686

Replace .dat Configuration File

Because of the issues that may have occurred during the upgrade procedure, the configuration file in the /opt/dialogic/export directory may be corrupt with the newer build information. The procedure is to delete the existing configuration file and replace with a second configuration file that was created during the upgrade process. Follow the procedure below to rename the existing file.

1. SSH to the VM. Delete the existing configuration file. In this example the existing configuration file is labeled myconfiguration.dat.
   [dialogic@localhost export]$rm myconfiguration.dat

2. Rename the existing file created during the upgrade process to myconfiguration.dat
   [dialogic@localhost export]$cp myconfiguration.dat.orig.v2.3.0-xxx myconfiguration.dat   (xxx = build number)

At this point there is a myconfiguration.dat file and a myconfiguration.dat.orig.v2.3.0-xxx. The file myconfiguration.dat will be used going forward.

Open Configuration File

1. Log back into the Web UI using the Login credentials displayed above. The Web UI will again open without any configuration in it.

2. Select File > Open from the menu bar in the Web UI. In the Open File dialog box, select the configuration file that was previously modified. In this example, the file was renamed myconfiguration.dat. Click on Open button.

3. A Confirm Dialog Box will appear informing the user that the "System will reboot, load myconfiguration.dat configuration?" Select Yes. System will now load the myconfiguration.dat file. Web UI will disconnect again.

4. The Login Dialog box will reappear. Log back into the Web UI.

5. The file myconfiguration.dat file will now be displayed in the Configuration tree.

6. Verify the EMS software being utilized has been downgraded by going to the /opt/dialogic/bin directory and executing the following command.
   [dialogic@localhost export]$ ./DBSyncEntity -v

7. Click on each of the Node objects in the configuration tree of the Web UI and verify the following:

• The Connection State field is displayed as Connected and the Version of EMS Software and node software are the same.

• The Serial Number field is populated with the correct serial number.

• The Security ID field is populated with the correct Security ID. Refer to screen capture below.
  
  
  

  Open

  

8. Verify all spans that were in service prior to the upgrade and then rollback are still in service.

9. Verify calls are being processed to all trunk groups.

10. Software rollback/downgrade is complete.