In this section:
Related articles:
Before you upgrade the software on your system, it is recommended that you execute the pre-upgrade check procedure provided in this section. This procedure requires about fifteen minutes to complete depending on your system configuration.
Note
The pre-upgrade process can be executed multiple times (if required).
The screen captures in this page are examples only and are the same between releases with the exception of the software version numbers in these screen captures.
It is assumed that you are logged onto the Ribbon DSC 8000.
The following procedure provides the instructions if you have to obtain the software load version number to execute the pre-upgrade check.
New License Key Entries Message
When upgrading to Release 24.0.0, a new license key is required. The file for the new license key is named license.dat.new and should have been provided with the purchase of the license key. Place the file on the management slot where the upgrade is being run (slot2 or slot13) in /opt/cpu_ss7gw/current/data. If the file is missing, the pre-upgrade check will fail. The license is checked at the end of the pre-upgrade check.
If you purchased a new application which requires that you enter the license key, perform this task using the procedures described in Configuring the System Licensing.
Obtain the Software Load Version Number
Make sure that all CPUs have the same software load version; otherwise, the pre-upgrade check may fail. The following procedure provides the instructions to obtain the software load version number.
Start- From the Main Menu, click Product Information.
- Using the Product Information on drop-down list, select the required CPU.
Click Update.
TipThe software load is listed as Internal Build.
Repeat this procedure for all other CPUs by selecting the required slot in the Product Information on drop-down list that is populated with a CPU.
All system cards should have the same Internal Build number. Otherwise, the pre-upgrade check may not be successful.
Perform the Pre-upgrade Check
Follow the instructions in this section in the order presented to perform a pre-upgrade check.
Note
The following illustration is an example of the various functions that are automatically done by the system for the pre-upgrade check.
It is assumed that you are logged onto the Ribbon DSC Platform [either Management CPU in slot 2 (p19p1.3) or slot 13 (p19p.2.5)] and have a terminal window open.
- Log onto one of the DSC 8000 Management CPUs (for information about logging onto the system, refer to Accessing the DSC Platforms.
- At the Linux prompt, enter startmenu, and press ENTER.
- From the Main Menu, select System, and press ENTER.
Select Software Revisions, and press ENTER.
Select Pre Upgrade Check, and press ENTER.
===== Performing upgrade PRE-checks... ====== -------------------------------------------- USB device check ... -------------------------------------------- Check USB device status on all the CPU or VM slots reported by cardlist/slotmon SLOT: 2 SLOT: 13 SLOT: 3 SLOT: 4 SLOT: 5 SLOT: 10 SLOT: 11 SLOT: 12 PASSED <Enter> to continue
Press ENTER.
--------------------------------------------------- Ping connectivity check... --------------------------------------------------- Ping all slots which are CPUS or IOs in /opt/cpu_ss7gw/current/data/slot.conf to check card availability Ping all the slots reported by cardlist/slotmon to check packet loss -Slot: 2 Packets dropped: 0% -Slot: 13 Packets dropped: 0% -Slot: 3 Packets dropped: 0% -Slot: 4 Packets dropped: 0% -Slot: 5 Packets dropped: 0% -Slot: 10 Packets dropped: 0% -Slot: 11 Packets dropped: 0% -Slot: 12 Packets dropped: 0% -Slot: 7 Packets dropped: 0% -Slot: 8 Packets dropped: 0% PASSED <Enter> to continue
Press ENTER.
--------------------------------------------------- ish connectivity check... --------------------------------------------------- Perform ish test between all CPUS in /opt/cpu_ss7gw/current/data/slot.conf to check slots interactive communication availability ish test from slot 2 to all slots in system... ish test from slot 2 to slot 2 passed. ish test from slot 2 to slot 3 passed. ish test from slot 2 to slot 4 passed. ish test from slot 2 to slot 5 passed. ish test from slot 2 to slot 10 passed. ish test from slot 2 to slot 11 passed. ish test from slot 2 to slot 12 passed. ish test from slot 2 to slot 13 passed. ish test from slot 3 to all slots in system... ish test from slot 3 to slot 2 passed. ish test from slot 3 to slot 3 passed. ish test from slot 3 to slot 4 passed. ish test from slot 3 to slot 5 passed. ish test from slot 3 to slot 10 passed. ish test from slot 3 to slot 11 passed. ish test from slot 3 to slot 12 passed. ish test from slot 3 to slot 13 passed. ish test from slot 4 to all slots in system... ish test from slot 4 to slot 2 passed. ish test from slot 4 to slot 3 passed. ish test from slot 4 to slot 4 passed. ish test from slot 4 to slot 5 passed. ish test from slot 4 to slot 10 passed. ish test from slot 4 to slot 11 passed. ish test from slot 4 to slot 12 passed. ish test from slot 4 to slot 13 passed. ish test from slot 5 to all slots in system... ish test from slot 5 to slot 2 passed. ish test from slot 5 to slot 3 passed. ish test from slot 5 to slot 4 passed. ish test from slot 5 to slot 5 passed. ish test from slot 5 to slot 10 passed. ish test from slot 5 to slot 11 passed. ish test from slot 5 to slot 12 passed. ish test from slot 5 to slot 13 passed. ish test from slot 10 to all slots in system... ish test from slot 10 to slot 2 passed. ish test from slot 10 to slot 3 passed. ish test from slot 10 to slot 4 passed. ish test from slot 10 to slot 5 passed. ish test from slot 10 to slot 10 passed. ish test from slot 10 to slot 11 passed. ish test from slot 10 to slot 12 passed. ish test from slot 10 to slot 13 passed. ish test from slot 11 to all slots in system... ish test from slot 11 to slot 2 passed. ish test from slot 11 to slot 3 passed. ish test from slot 11 to slot 4 passed. ish test from slot 11 to slot 5 passed. ish test from slot 11 to slot 10 passed. ish test from slot 11 to slot 11 passed. ish test from slot 11 to slot 12 passed. ish test from slot 11 to slot 13 passed. ish test from slot 12 to all slots in system... ish test from slot 12 to slot 2 passed. ish test from slot 12 to slot 3 passed. ish test from slot 12 to slot 4 passed. ish test from slot 12 to slot 5 passed. ish test from slot 12 to slot 10 passed. ish test from slot 12 to slot 11 passed. ish test from slot 12 to slot 12 passed. ish test from slot 12 to slot 13 passed. ish test from slot 13 to all slots in system... ish test from slot 13 to slot 2 passed. ish test from slot 13 to slot 3 passed. ish test from slot 13 to slot 4 passed. ish test from slot 13 to slot 5 passed. ish test from slot 13 to slot 10 passed. ish test from slot 13 to slot 11 passed. ish test from slot 13 to slot 12 passed. ish test from slot 13 to slot 13 passed. PASSED <Enter> to continue
Press ENTER to check SDA configuration.
NoteThe SDA configuration check will pass if:
- SDA is not configured on the system
- DRBD version 9.0 is found on the system (SDA version 19.0.0 R07 contains the updated DRDB)
The SDA configuration check will fail if:
- An older version than DRBD 9.0 configuration is found on the system
Press ENTER.
--------------------------------------------------- RPM database check... --------------------------------------------------- Check RPM database status on all the CPU or VM slots reported by cardlist/slotmon SLOT: 2 RPM database files backed up to /var/lib/rpm/backup-20240228 RPM database is not corrupt. Verifying RPM database. Cleaning up RPM database is valid. SLOT: 13 RPM database files backed up to /var/lib/rpm/backup-20240228 RPM database is not corrupt. Verifying RPM database. Cleaning up RPM database is valid. SLOT: 3 RPM database files backed up to /var/lib/rpm/backup-20240228 RPM database is not corrupt. Verifying RPM database. Cleaning up RPM database is valid. SLOT: 4 RPM database files backed up to /var/lib/rpm/backup-20240228 RPM database is not corrupt. Verifying RPM database. Cleaning up RPM database is valid. SLOT: 5 RPM database files backed up to /var/lib/rpm/backup-20240228 RPM database is not corrupt. Verifying RPM database. Cleaning up RPM database is valid. SLOT: 10 RPM database files backed up to /var/lib/rpm/backup-20240228 RPM database is not corrupt. Verifying RPM database. Cleaning up RPM database is valid. SLOT: 11 RPM database files backed up to /var/lib/rpm/backup-20240228 RPM database is not corrupt. Verifying RPM database. Cleaning up RPM database is valid. SLOT: 12 RPM database files backed up to /var/lib/rpm/backup-20240228 RPM database is not corrupt. Verifying RPM database. Cleaning up RPM database is valid. PASSED <Enter> to continue
Press ENTER.
--------------------------------------------------- Free space check... --------------------------------------------------- -Available RAM space: 10602 MB -Available HDD (/var/log) space: 211502 MB -Available Compact Flash (/opt directory) space: 26435 MB PASSED <Enter> to continue
Press ENTER.
Press ENTER.
Press ENTER.
---------------------------------------------------------------- Pre-setting and verifying new FS volume labels... ---------------------------------------------------------------- -CPU Slot: 2 FS volume labels set and verified -CPU Slot: 13 FS volume labels set and verified -CPU Slot: 3 FS volume labels set and verified -CPU Slot: 4 FS volume labels set and verified -CPU Slot: 5 FS volume labels set and verified -CPU Slot: 10 FS volume labels set and verified -CPU Slot: 11 FS volume labels set and verified -CPU Slot: 12 FS volume labels set and verified PASSED <Enter> to continue
Press ENTER.
---------------------------------------------------------------- Checking if CPU Unused SATA Channels are Disabled... ---------------------------------------------------------------- -CPU Slot: 2 Unused SATA Channels are Disabled. Board Type: AMC124 -CPU Slot: 13 Unused SATA Channels are Disabled. Board Type: AMC124 -CPU Slot: 3 Unused SATA Channels are Disabled. Board Type: AMC124 -CPU Slot: 4 Unused SATA Channels are Disabled. Board Type: AMC124 -CPU Slot: 5 Unused SATA Channels are Disabled. Board Type: AMC124 -CPU Slot: 10 Unused SATA Channels are Disabled. Board Type: AMC124 -CPU Slot: 11 Unused SATA Channels are Disabled. Board Type: AMC124 -CPU Slot: 12 Unused SATA Channels are Disabled. Board Type: AMC124 PASSED <Enter> to continue
Press ENTER.
--------------------------------------------------- Check Kernel and Mount Points. --------------------------------------------------- No tests to perform. <Enter> to continue
Press ENTER.
Press ENTER.
--------------------------------------------------- GWS Incoming Linkset check --------------------------------------------------- No GWS Incoming Linkset check needed for this X511 version <Enter> to continue
Press ENTER.
------------------------------------------------------------------------- Checking uniqueness of Linkset Point Codes per NA ------------------------------------------------------------------------- PASSED <Enter> to continue
Press ENTER.
------------------------------------------------------------------------- Checking if DB Definition of GTT NA and its LPC registration match ------------------------------------------------------------------------- PASSED <Enter> to continue
If the GTT NA has a Local Point Code (LPC) registered, it is recommended that you conduct a pre-upgrade check to verify that the GTT NA Database Definition matches the Database Definition of the LPC registration. The PC registration for the LPC of the GTT NA may need to be reset to the GTT NA Database Definition. The following is a pre-upgrade check failure scenario example:
Compare DB definitions of GTT NA and LPC registration Mismatch for GTT NA 8: NA DB Def is INAPGWITU, but LPC 2.003.4 has TEST1 Mismatch for GTT NA 9: NA DB Def is INAPGWITU, but LPC 3.004.5 has TEST2 Mismatch for GTT NA 7: NA DB Def is INAPGWANSI, but LPC 008.009.010 has TEST3
For information about reseting the PC registration of the LPC, refer to Resetting the PC registration of the LPC.Press Enter.
--------------------------------------------------- Ensure correct cluster password... --------------------------------------------------- PASSED <Enter> to continue
Press Enter.
--------------------------------------------------- Audit files check... --------------------------------------------------- 0 files were out of sync. Files: 94 Copied: 0 Deleted: 0 PASSED <Enter> to continue
Press ENTER.
--------------------------------------------------- Test TIPC bearers... --------------------------------------------------- <Enter> to continue
Press Enter. DSC 24.0 requires a new license key. If the new license file has not been uploaded to the system, this will be the failure (see example below).
---------------------------------------------------------------- Checking if license keys need to be changed ---------------------------------------------------------------- New license file not found Please put the new license keys in /opt/cpu_ss7gw/current/data/license.new.dat ERROR: (MAJOR) License check failed ***************************************************************************** *** LICENSE KEYS NEED TO BE UPDATED *** PRIOR TO ATTEMPTING THE UPGRADE. *** PLEASE CONTACT RIBBON SUPPORT FOR MORE INFORMATION. ***************************************************************************** FAILED <Enter> to continue
Otherwise, the license check will pass (see below).---------------------------------------------------------------- Checking if license keys need to be changed ---------------------------------------------------------------- PASSED <Enter> to continue
It is recommended that at this step you perform a backup. For information about performing a backup, refer to the appropriate page in the Back Up Systems.
--------------------------------------------------- Reminder to take a backup... --------------------------------------------------- -It is highly recommended to take a backup of the system prior to starting the upgrade. Label and keep the backup in a safe place. <Enter> to continue
Press ENTER. If the pre-upgrade check was successfully executed, the following information appears on your screen.
====== The results of the PRE upgrade check are stored in /var/log/cpu_ss7gw/upgrade_data/PRE_UPGRADE_DATA.dsc_8000_16_1_0_nb20180111.Wed_Aug_28_01_36_52_EDT_2019 ====== Upgrade PRE checks completed. All checks PASSED. You may now proceed with the upgrade.
Press ENTER.
- If you have at least one issue that has to be resolved before you can start the software upgrade, find a resolution to each failed pre-upgrade check in the order these checks were presented in the given file. It is recommended that you execute this procedure (from step 1) after resolving each issue until you have resolved all issues.
When all pre-upgrade checks are successfully completed, it is highly recommended that you perform a Complete System Backup using a USB key (refer to Complete System Backup Configuration for the DSC 8000).
If this is performed, remove the USB key once the backup is complete from the USB port and keep this key in a safe place.NoteThe results of the pre-upgrade check are stored in /var/log/cpu_ss7gw/upgrade_data.
Overview
Content Tools