In this section:
Note
Note that all screen captures, outputs, or images on this page are examples only and are the same between releases with the exception of the software version numbers.
Caution
Do not log onto the system using the shared IP address on the Routing and Management VMs during the upgrade procedures provided in this section. This address is disabled as part of the upgrade process.
Caution
All VMs must be upgraded to the same software version. VMs can run different versions for short periods of time but this state will restrict certain provisioning operations. Make sure to upgrade and verify all VMs before closing the maintenance window.
Upgrade the VMs
Prerequisites- You have completed the tasks in Before you Begin the DSC SWe - vSP2000 Software Upgrade.
- Upload the dsc_swe_xx_x_x_xxx_upgrade.sh file to the system on slot1. (/var/log/ on a Routing and Management VM).
- Log onto the Routing and Management VM as root that contains the dsc_swe_xx_x_x_xxx_upgrade.sh file.
- cd to the /var/log directory.
Enter the following at the command line, and press ENTER.
./dsc_swe_xx_x_x_nbxxxxxxxx_upgrade.sh
Example[root@dscLab218-slot1 log]# ./dsc_swe_xx_x_x_nbxxxxxxxx_upgrade.sh DSC Self-Extraction Utility xx_x_x_nbxxxxxxxxx ----------------------------------------------------- Verify archive integrity... Executing install script... Software Upgrade Preparation ---------------------------- root: UpgradeInstaller Executed upgrade installer xx_x_x_nbxxxxxxxx ---------------------------------------- Executed upgrade installer xx_x_x_nbxxxxxxxx Verify /upgrade ... Partition for /upgrade has 4.8 GB Verify execution point... Verify system state... Verify requisite files in the archive... Is it OK to proceed with preparation of the /upgrade directory? (y/n):
Enter y.
ExamplePreparing /upgrade directory... Expand OS image from archive... Place SW load file... Redirect pre-upgrade-check and upgrade... Place new pre-upgrade-check and upgrade... ---------------------------------------------------------------- To complete the process run the upgrade command. (May optionally run pre-upgrade-check independently beforehand). ---------------------------------------------------------------- complete. [root@lab81TMAslot1 log]#
Enter the following at the command line:
upgrade
The upgrade is automatically executed on the system. During this process, the VMs initialize, discover, and install the software load and perform the upgrade/restore using the backup file.
Release 23.1.0 Example[root@lababc-slot1 log]# upgrade :::::::::::::::::::::::::::::::: Ribbon DSC :::::::::::::::::::::::::::::::: ┌──────────────┐ │DSC VM Upgrade│ └──────────────┘ _____________________________________________ Type "q" to quit from most prompts or CTRL-C. This process will prepare each VM for upgrade before rebooting each VM in order, isolating the reboots to avoid outages. etting software versions...Done ------------------------------Check IO OS: N/A------------------------------- ------------------------------Pre Upgrade Check------------------------------ Please run a new pre-upgrade check. Type "yes" to execute this check (exiting otherwise): yes Calling pre-upgrade check... :::::::::::::::::::::::::::::::: Ribbon DSC :::::::::::::::::::::::::::::::: Pre-Upgrade Check ____________________________________________ Type "q" to quit from most prompts or CTRL-C. Notice: replacing previous pre-upgrade checkRunning in-container upgrade tests. User root..............................................: Pass Current VMs Exist......................................: Pass Previous Upgrade.......................................: Pass Script Run-From Point..................................: Pass VM Replacements Exist..................................: Pass VM MGT Interfaces......................................: Pass VM Interface Compare...................................: Pass File Audit (Current MGMT)..............................: Pass APC Uniqueness.........................................: Pass Compare DB definitions of GTT NA and LPC registration..: Pass Check grub file for proper data........................: Pass Ensure VMUUID in pticonfig.............................: Pass Ensure SCTP NAT is not configured......................: Pass Persistent Session Management Enabled license Exists...: Pass Check time zone for all slots..........................: Pass Check license for upgrading to RedHat..................: Pass ----------------------------------------------------------------- Overall pre-upgrade check result is PASS. ----------------------------------------------------------------- Recent preupgrade check found and all tests passed. Continuing with upgrade. ----------------------------Upgrade Information----------------------------- Using /shared/log/dsc_swe_24_0_0_nb20240216_upgrade.sh Upgrading to: 24_0_0_nb20240216 Requiring update: 1 2 3 4 Up to date: None I/O Cards: None detected Switch Cards: Uncommissioned/Bad: None Confirmation to proceed with upgrade operations? (yes/no):Enter "yes" and press ENTER.
Example-----------------------Upgrade Preparations (part 1)------------------------ Copying upgrade package and preparing each VM. Preparing 2 Checking mounts.................Pass Checking available space........Pass Sending package.................Pass Setting up new OS files on 2: Started Waiting for OS setup to finish... 2: Pass -------------------------------System Backup-------------------------------- Generating new backup...Pass -----------------------Upgrade Preparations (part 2)------------------------ Preparing 2 fstab, restore id and keys......Pass Copying backup..................Pass Preparing 1 fstab, restore id and keys......Pass Copying backup..................NA Should user input (a y/n prompt) be required after each VM is upgraded? (yes/no) [n]:
Enter yes.
Upgrade execution order [2, 1]. To continue, press the Enter key:
Press Enter to start upgrade processing.
-----------------------------Final upgrade step----------------------------- Upgrading peer 2 Backup stats files..............Pass Modify boot file................Pass Setting restore information.....Pass Rebooting.......................Pass Waiting to recover..............Pass Waiting for system processes....Pass
Log into the Web UI and navigate to System > Processes > Watchdog Processes. Select the CPU that was just upgraded and ensure that processes are running without issues.
When the upgrade process of the first CPU has been completed, tests can be performed to ensure stability and functionality of the new load.
Ensuring That Test Calls are Processed by the New Software
To ensure that all test calls are processed by the newly upgraded CPU, you must stop the SS7 or Routing software on the Slot not yet upgraded.Log into the WEB UI on the CPU that has not been upgraded and navigate to the System Start/Stop Commands Under System > Processes.
Choose the CPU Slot that has not been upgraded and check Stop SS7 Software Applications and click ‘Continue’.
Proceed with test calls.
If testing is unfavorable after the first CPU upgrade AND a rollback is required, apply the following steps BEFORE proceeding with the Rollback. This will minimize the outage on the M3UA ASPs to the CORE.
If testing was successful, continue with the upgrade by entering "yes" and pressing ENTER.Machine 2 is complete, type "yes" to continue.: yes Upgrading peer 1 Backup stats files..............NA Modify boot file................Pass Setting restore information.....Pass Rebooting.......................
- For upgrades to DSC 24.0 only: Log into the Web UI and navigate to IP Networking > Firewall. Click Restart Firewall.
- After the software upgrade is completed, make sure that the upgrade was successful and the software was properly installed (see Verify that the Software has been Properly Installed on the CPUs ).
Steps to Follow if Rollback is Needed After the First CPU Upgrade is Completed
Before the software can be rolled back, the software must be restarted on the CPU that has NOT been upgraded.
Start- Log into the WEB UI on the CPU that has NOT been upgraded and navigate to System > Processes > System Start/Stop Commands.
- Choose the CPU Slot that has NOT been upgraded and check Restart SS7 Software Applications and click ‘Continue’
- Confirm that all software has restarted by viewing the Watchdog processes for the affected slot and ensure that any MTP3 links have returned to service. The Signaling Gateway M3UA links will not return to service at this point. To view the Watchdog running processes, perform the following steps.
- Go to System > Processes > Watchdog Processes.
- Choose the CPU that has NOT been upgraded and ensure that the applications are running. This would have started the following applications: licensed, snm, gws, dre, dinamo and pt_route_refreshd.
- You can now proceed with the Rollback as documented in the DSC SWe Rollback to a Previous Software Version.
Verify that the Software has been Properly Installed on the CPUs
Caution
If an asterisk appears beside any of the system cards during the verification process, the upgrade for the respective card was unsuccessful. In this case, it is recommended that you contact Customer Support.
- At the Linux prompt, enter startmenu and press ENTER.
- Select System and press ENTER.
- Navigate to the Software Revisions screen.
- Select CPU Versions and press ENTER.
Make sure that the SS7 software and Linux software has been upgraded, all cards are running the same software, and that there is no asterisk beside any of the cards.
TipThe output of the CPU Versions shows that the CPU card has “UPGRADED” status if this is the first time the command is issued after an upgrade. All subsequent CPU Versions selections show the number of processes running on each CPU.
Press ENTER.
Overview
Content Tools