Page History
Add_workflow_for_techpubs | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
Internal_display_only | ||||||
---|---|---|---|---|---|---|
|
Panel | ||||
---|---|---|---|---|
In this section:
|
Upgrading the DSC 8000
Note | ||
---|---|---|
| ||
Screen captures, images, and code on this page are examples only and are the same between releases with the exception of the software version numbers. |
Note | ||
---|---|---|
| ||
Do not log onto the system using the shared IP addresses on the Management CPUs during the upgrade processes. These addresses are disabled as part of this process. |
Note | ||
---|---|---|
| ||
It is recommended that you perform the upgrade from a console port. A loss of connection while CPUs are being upgraded may require a rollback from the upgraded management CPU. |
Workflow
You must upgrade the DSC 8000 system cards in the following order: (1) CPUs, (2) MCH Ethernet Switches, and (3) IO cards.
Upgrade the Software on the CPUs
Start
Log onto the DSC 8000 Management CPU in slot 13 (p19p2.5, Control shelf) or slot 2 (p19p1.3).
Info title Note You must log onto the same CPU as the one you connected to upload the _upgrade.sh file.
Run command "upgrade" and press ENTER.
Code Block title Example ::::::::::::::::::::::::::::::: Ribbon DSC :::::::::::::::::::::::::::::::: +-------------------+ ¦DSC8000 CPU Upgrade¦ +-------------------+ _____________________________________________ Type "q" to quit from most prompts or CTRL-C. This process will prepare each CPU for upgrade before rebooting each CPU in order, isolating the reboots to avoid outages. -----------------------------Pre Upgrade Check------------------------------ Current pre-upgrade check lists errors. Type "yes" to re-execute this check (exiting otherwise):
Type "yes", and press ENTER.
Code Block title Example ======== 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:12 PASSED <Enter> to continue
Press ENTER.
Code Block title Example --------------------------------------------------- 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: 12 Packets dropped: 0% -Slot: 6 Packets dropped: 0% -Slot: 10 Packets dropped: 0% PASSED <Enter> to continue
One of the following will be displayed on the system depending on if SDA is deployed.
For a system doesn't deploy SDA:
Code Block --------------------------------------------------- Checking SDA configuration --------------------------------------------------- flex_slot.conf file doesn't exist ... This is expected if SDA is not configured on the system.
For a system that deploys SDA:
Code Block --------------------------------------------------- Checking SDA configuration --------------------------------------------------- Found DRBD 9.0 configuration on your system. PASSED
Press ENTER.
Code Block title Example collapse true --------------------------------------------------- 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-20201009 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-20201009 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-20201009 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-20201009 RPM database is not corrupt. Verifying RPM database. Cleaning up RPM database is valid. PASSED <Enter> to continue
Press ENTER.
Code Block title Example --------------------------------------------------- Free space check... --------------------------------------------------- -Available RAM space: 10500 MB -Available HDD (/var/log) space: 34159 MB -Available Compact Flash (/opt directory) space: 26564 MB PASSED <Enter> to continue
Press ENTER.
Code Block title Example Checking current Clock Settings... --------------------------------------------------- Current Clock Settings... --------------------------------------------------- TIMEZONE: CPU Slot 2: -05 (EST) CPU Slot 13: -05 (EST) CPU Slot 3: -05 (EST) CPU Slot 12: -05 (EST) IO Slot 6: -05 (EST) IO Slot 10: -05 (EST) HWCLOCK: CPU Slot 2: Fri 09 Oct 2020 04:19:26 AM EST -0.407717 seconds CPU Slot 13: Thu 08 Oct 2020 04:18:34 AM EST -0.485793 seconds CPU Slot 3: Thu 08 Oct 2020 04:18:48 AM EST -0.564361 seconds CPU Slot 12: Thu 08 Oct 2020 04:18:45 AM EST -0.798552 seconds IO Slot 6: IO Slot 10: WALL CLOCK: CPU Slot 2: Fri Oct 9 04:19:29 EST 2020 CPU Slot 13: Fri Oct 9 04:19:30 EST 2020 CPU Slot 3: Fri Oct 9 04:19:30 EST 2020 CPU Slot 12: Fri Oct 9 04:19:30 EST 2020 IO Slot 6: Fri Oct 9 04:19:31 EST 2020 IO Slot 10: Fri Oct 9 04:19:31 EST 2020 <Enter> to continue
Press ENTER.
Code Block title Example --------------------------------------------------- Validating NEW license keys... --------------------------------------------------- New load release: .. uses the same licensing as the current load release: .., so skipping this check. PASSED <Enter> to continue
Press ENTER.
Code Block title Example ---------------------------------------------------------------- Checking if firmware flashing is recommended... ---------------------------------------------------------------- -CPU Slot: 2 Firmware upgrade to 1.24 or greater recommended. Board Type: AMC124 Current Firmware version: 1.22 -CPU Slot: 13 Firmware upgrade to 1.24 or greater recommended. Board Type: AMC124 Current Firmware version: 1.22 -CPU Slot: 3 Firmware upgrade to 1.24 or greater recommended. Board Type: AMC124 Current Firmware version: 1.22 -CPU Slot: 12 Firmware upgrade to 1.24 or greater recommended. Board Type: AMC124 Current Firmware version: 1.22 -IO Slot: 6 Firmware up to date. Board Type: AMC348 Current Firmware version: 1.04 -IO Slot: 10 Firmware up to date. Board Type: AMC348 Current Firmware version: 1.00 -MCH Slot: 1 Firmware up to date. Board Type: AMC671 Current Firmware version: 1.26 -MCH Slot: 14 Firmware up to date. Board Type: AMC671 Current Firmware version: 1.26 -Chassis 1/cu1: Firmware up to date. Board Type: Cooling Unit Current Firmware version: 1.10 -Chassis 1/cu2: Firmware up to date. Board Type: Cooling Unit Current Firmware version: 1.10 -Chassis 1/pm1: Firmware up to date. Board Type: Power Module Current Firmware version: 1.24 -Chassis 1/pm2: Cannot get firmware version from Power Module. Check that component is inserted. -Chassis 1/pm4: Firmware up to date. Board Type: Power Module Current Firmware version: 1.24 **************************************************** *** FIRMWARE ON ONE OR MORE CARDS IS OUT OF DATE. *** *** IT IS RECOMMENDED THAT THE FIRMWARE BE UPDATED *** PER INSTRUCTIONS FOUND IN THE UPGRADE GUIDE *** AFTER THE UPGRADE IS COMPLETED. *** *** PLEASE CONTACT RIBBON CUSTOMER SUPPORT *** FOR MORE INFORMATION. *************************************************** WARNING <Enter> to continue
Press ENTER.
Code Block ---------------------------------------------------------------- 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: 12 FS volume labels set and verified PASSED <Enter> to continue
Press ENTER.
Code Block title Example ---------------------------------------------------------------- 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: 12 Unused SATA Channels are Disabled. Board Type: AMC124 PASSED <Enter> to continue
Press ENTER.
Code Block title Example --------------------------------------------------- Check Kernel and Mount Points. --------------------------------------------------- No tests to perform. <Enter> to continue
Press ENTER.
Code Block title Example collapse true --------------------------------------------------- Dumping slot status and watchdog processes... --------------------------------------------------- Dumping CPU status info... AVAILABLE SOFTWARE VERSIONS -------------------------------------------------------------------------------- CPU (new) dsc_8000_20_0_0_nb20201008 OS: Ribbon7.4.18 CPU (current) dsc_8000_18_1_0_nb20200612 OS: Ribbon7.4.18 (Servicepack) [none applied] CPU (previous) Not_Available OS: Ribbon7.4.18 (Servicepack) RUNNING SOFTWARE VERSIONS (*=update required, ?=update unknown) CARD BUILD SERVICE O/S -SLOT----TYPE----------RELEASE--VERSION----PACK---IMAGE-------CARD STATUS--- -------------------------------------------------------------------------------- Slot 2 MGMT * 18.1.0 (nb20200612) SP: OS: Ribbon7.4.18 17 procs running Slot 13 MGMT * 18.1.0 (nb20200612) SP: OS: Ribbon7.4.18 17 procs running Slot 3 ROUTING * 18.1.0 (nb20200612) SP: OS: Ribbon7.4.18 21 procs running Slot 12 ROUTING * 18.1.0 (nb20200612) SP: OS: Ribbon7.4.18 21 procs running (p=servicepack is partially applied) Dumping IO status info... AVAILABLE SOFTWARE VERSIONS -------------------------------------------------------------------------------- IO (new) 358/388 /upgrade/opt/dsc_8000_20_0_0_nb20201008 OS: Not_Available IO (new) 308A /upgrade/opt/dsc_8000_20_0_0_nb20201008 OS: Not_Available IO (new) PCE382 /upgrade/opt/dsc_8000_20_0_0_nb20201008 OS: Not_Available IO (current) AMC348 dsc_8000_18_1_0_nb20200612 OS: rel_12_00_p04.x511.img (Servicepack) [none applied] RUNNING SOFTWARE VERSIONS (*=update required, ?=update unknown) CARD BUILD SERVICE O/S -SLOT----TYPE----------RELEASE-VERSION------PACK-----IMAGE------- -------------------------------------------------------------------------------- Slot 6 IO AMC348 18.1.0 (nb20200612) SP: OS: rel_12_00_p04.x511.img Slot 10 IO AMC348 18.1.0 (nb20200612) SP: OS: rel_12_00_p04.x511.img (p=servicepack is partially applied) Dumping MCH status info... AVAILABLE SOFTWARE VERSIONS -------------------------------------------------------------------------------- MCH (new) dsc_8000_20_0_0_nb20201008 MCH (current) dsc_8000_18_1_0_nb20200612 (Servicepack) [none applied] RUNNING SOFTWARE VERSIONS (*=update required, ?=update unknown) CARD BUILD SERVICE O/S -SLOT----TYPE------RELEASE-VERSION----PACK-----IMAGE------------CARD STATUS----- -------------------------------------------------------------------------------- -- Chassis 1 -- Slot 1 MCH 18.1.0 (nb20200612) SP: Slot 14 MCH 18.1.0 (nb20200612) SP: (p=servicepack is partially applied) Dumping Watchdog process info for each CPU... Watchdog Process Details on MGMT - slot2_0. WID PID STA RPT RHT HTV HTT COM 1 10134 S+ 0 0 10 10 slotmon --platform X511 -s 2 -g 0 -p /opt... 2 15639 S+ 0 0 10 10 pxbr -p /opt/cpu_ss7gw/current/data --pla... 3 15666 S+ 0 0 10 10 upp -p /opt/cpu_ss7gw/current/data/ --pla... 4 15699 S+ 0 0 10 10 sca -p /opt/cpu_ss7gw/current/data/ 5 15718 S+ 0 0 10 10 sysmon.default -p /opt/cpu_ss7gw/current/... 6 15757 S+ 0 0 10 10 sysmon.cpucheck -p /opt/cpu_ss7gw/current... 7 15807 S+ 0 0 10 10 sysmon.diskmon -p /opt/cpu_ss7gw/current/... 8 15865 S+ 0 0 10 10 sysmon.logcpu -p /opt/cpu_ss7gw/current/s... 9 16015 S+ 0 0 10 10 sysmon.logmem -p /opt/cpu_ss7gw/current/s... 10 16353 S+ 0 0 10 10 sysmon.usbcheck -p /opt/cpu_ss7gw/current... 11 16471 S+ 0 0 10 10 sysmon.slotinventory -p /opt/cpu_ss7gw/cu... 12 16511 S+ 0 0 10 10 sysmon.configuremtu -p /opt/cpu_ss7gw/cur... 13 16555 S+ 0 0 10 10 switchmon -p /opt/cpu_ss7gw/current/data/... 14 16583 S+ 0 0 10 10 hwmon --platform X511 15 19622 S+ 0 0 10 10 licensed -r -f /opt/cpu_ss7gw/current/dat... 16 19732 S+ 0 0 10 10 snm --platform X511 -p /opt/cpu_ss7gw/cur... 17 19858 S+ 0 0 10 10 gws --platform X511 -p /opt/cpu_ss7gw/cur... Watchdog Process Details on MGMT - slot13_0. WID PID STA RPT RHT HTV HTT COM 1 9321 S+ 0 0 10 10 slotmon --platform X511 -s 13 -g 0 -p /op... 2 19011 S+ 0 0 10 10 pxbr -p /opt/cpu_ss7gw/current/data --pla... 3 19039 S+ 0 0 10 10 upp -p /opt/cpu_ss7gw/current/data/ --pla... 4 19069 S+ 0 0 10 10 sca -p /opt/cpu_ss7gw/current/data/ 5 19102 S+ 0 0 10 10 sysmon.default -p /opt/cpu_ss7gw/current/... 6 19201 S+ 0 0 10 10 sysmon.cpucheck -p /opt/cpu_ss7gw/current... 7 19301 S+ 0 0 10 10 sysmon.diskmon -p /opt/cpu_ss7gw/current/... 8 19359 S+ 0 0 10 10 sysmon.logcpu -p /opt/cpu_ss7gw/current/s... 9 19514 S+ 0 0 10 10 sysmon.logmem -p /opt/cpu_ss7gw/current/s... 10 19650 S+ 0 0 10 10 sysmon.usbcheck -p /opt/cpu_ss7gw/current... 11 19783 S+ 0 0 10 10 sysmon.slotinventory -p /opt/cpu_ss7gw/cu... 12 19827 S+ 0 0 10 10 sysmon.configuremtu -p /opt/cpu_ss7gw/cur... 13 19869 S+ 0 0 10 10 switchmon -p /opt/cpu_ss7gw/current/data/... 14 19897 S+ 0 0 10 10 hwmon --platform X511 15 25029 S+ 0 0 10 10 licensed -r -f /opt/cpu_ss7gw/current/dat... 16 25050 S+ 0 0 10 10 snm --platform X511 -p /opt/cpu_ss7gw/cur... 17 25157 S+ 0 0 10 10 gws --platform X511 -p /opt/cpu_ss7gw/cur... Watchdog Process Details on ROUTING - slot3_0. WID PID STA RPT RHT HTV HTT COM 22 10562 S+ 0 0 10 10 sysmon.default -p /opt/cpu_ss7gw/current/... 23 10644 S+ 0 0 10 10 sysmon.cpucheck -p /opt/cpu_ss7gw/current... 24 10702 S+ 0 0 10 10 sysmon.diskmon -p /opt/cpu_ss7gw/current/... 25 10772 S+ 0 0 10 10 sysmon.logcpu -p /opt/cpu_ss7gw/current/s... 26 10904 S+ 0 0 10 10 sysmon.logmem -p /opt/cpu_ss7gw/current/s... 27 11197 S+ 0 0 10 10 sysmon.usbcheck -p /opt/cpu_ss7gw/current... 28 11240 S+ 0 0 10 10 sysmon.slotinventory -p /opt/cpu_ss7gw/cu... 29 11283 S+ 0 0 10 10 sysmon.configuremtu -p /opt/cpu_ss7gw/cur... 30 12223 S+ 0 0 10 10 licensed -r -f /opt/cpu_ss7gw/current/dat... 31 12245 S+ 0 0 10 10 dsc.1 -p /opt/cpu_ss7gw/current/data/dsc.... 32 12356 S+ 0 0 10 10 dsc.2 -p /opt/cpu_ss7gw/current/data/dsc.... 33 12469 S+ 0 0 10 10 dsc.3 -p /opt/cpu_ss7gw/current/data/dsc.... 34 12581 S+ 0 0 10 10 dsc.4 -p /opt/cpu_ss7gw/current/data/dsc.... 35 12692 S+ 0 0 10 10 dsc.5 -p /opt/cpu_ss7gw/current/data/dsc.... 36 12803 S+ 0 0 10 10 dsc.6 -p /opt/cpu_ss7gw/current/data/dsc.... 37 12914 S+ 0 0 10 10 dsc.7 -p /opt/cpu_ss7gw/current/data/dsc.... 38 13025 S+ 0 0 10 10 dsc.8 -p /opt/cpu_ss7gw/current/data/dsc.... 39 13142 S+ 0 0 10 10 dsc.9 -p /opt/cpu_ss7gw/current/data/dsc.... 40 13253 S+ 0 0 10 10 dsc.10 -p /opt/cpu_ss7gw/current/data/dsc... 41 13357 S+ 0 0 10 10 dre --platform X511 -p /opt/cpu_ss7gw/cur... 42 13511 S+ 0 0 10 10 sccp --platform X511 -p /opt/cpu_ss7gw/cu... Watchdog Process Details on ROUTING - slot12_0. WID PID STA RPT RHT HTV HTT COM 22 15370 S+ 0 0 10 10 sysmon.default -p /opt/cpu_ss7gw/current/... 23 15437 S+ 0 0 10 10 sysmon.cpucheck -p /opt/cpu_ss7gw/current... 24 15495 S+ 0 0 10 10 sysmon.diskmon -p /opt/cpu_ss7gw/current/... 25 15565 S+ 0 0 10 10 sysmon.logcpu -p /opt/cpu_ss7gw/current/s... 26 15692 S+ 0 0 10 10 sysmon.logmem -p /opt/cpu_ss7gw/current/s... 27 15985 S+ 0 0 10 10 sysmon.usbcheck -p /opt/cpu_ss7gw/current... 28 16028 S+ 0 0 10 10 sysmon.slotinventory -p /opt/cpu_ss7gw/cu... 29 16072 S+ 0 0 10 10 sysmon.configuremtu -p /opt/cpu_ss7gw/cur... 30 17013 S+ 0 0 10 10 licensed -r -f /opt/cpu_ss7gw/current/dat... 31 17035 S+ 0 0 10 9 dsc.1 -p /opt/cpu_ss7gw/current/data/dsc.... 32 17151 S+ 0 0 10 9 dsc.2 -p /opt/cpu_ss7gw/current/data/dsc.... 33 17262 S+ 0 0 10 10 dsc.3 -p /opt/cpu_ss7gw/current/data/dsc.... 34 17373 S+ 0 0 10 10 dsc.4 -p /opt/cpu_ss7gw/current/data/dsc.... 35 17484 S+ 0 0 10 10 dsc.5 -p /opt/cpu_ss7gw/current/data/dsc.... 36 17595 S+ 0 0 10 10 dsc.6 -p /opt/cpu_ss7gw/current/data/dsc.... 37 17707 S+ 0 0 10 9 dsc.7 -p /opt/cpu_ss7gw/current/data/dsc.... 38 17823 S+ 0 0 10 10 dsc.8 -p /opt/cpu_ss7gw/current/data/dsc.... 39 17934 S+ 0 0 10 10 dsc.9 -p /opt/cpu_ss7gw/current/data/dsc.... 40 18045 S+ 0 0 10 10 dsc.10 -p /opt/cpu_ss7gw/current/data/dsc... 41 18149 S+ 0 0 10 10 dre --platform X511 -p /opt/cpu_ss7gw/cur... 42 18303 S+ 0 0 10 10 sccp --platform X511 -p /opt/cpu_ss7gw/cu... <Enter> to continue
Press ENTER.
Code Block title Example --------------------------------------------------- GWS Incoming Linkset check --------------------------------------------------- No GWS Incoming Linkset check needed for this X511 version <Enter> to continue
Press ENTER.
Code Block title Example ------------------------------------------------------------------------- Checking uniqueness of Linkset Point Codes per NA ------------------------------------------------------------------------- PASSED <Enter> to continue
Press ENTER.
Code Block title Example ------------------------------------------------------------------------- Checking if DB Definition of GTT NA and its LPC registration match ------------------------------------------------------------------------- PASSED <Enter> to continue
Press ENTER.
Code Block --------------------------------------------------- Ensure pcs files are in proper locations... --------------------------------------------------- PASSED <Enter> to continue
Press ENTER.
Code Block --------------------------------------------------- Ensure correct cluster password... --------------------------------------------------- PASSED <Enter> to continue
Press ENTER.
Code Block title Example --------------------------------------------------- Audit files check... --------------------------------------------------- Audit status: local copy of /opt/cpu_ss7gw/current/data/mtp.1.3.conf is different from 13, due to blank lines only 0 files were out of sync. Files: 83 Copied: 0 Deleted: 0 PASSED <Enter> to continue
Press ENTER.
Code Block title Example --------------------------------------------------- Test TIPC bearers... --------------------------------------------------- <Enter> to continue
Press ENTER.
Code Block title Example --------------------------------------------------- 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.
Code Block title Example ====== The results of the PRE upgrade check are stored in /var/log/cpu_ss7gw/upgrade_data/PRE_UPGRADE_DATA.dsc_8000_18_1_0_nb20200612.Fri_Oct__9_04_18_52_EST_2020 ====== Upgrade PRE checks completed. All checks PASSED. You may now proceed with the upgrade. ----------------------------Upgrade Information----------------------------- Using /shared/log/dsc_8000_20_0_0_nb20201008_upgrade.sh Upgrading to: 20_0_0_nb20201008 Requiring update: 2 3 12 13 Up to date: None I/O Cards: 10 6 Uncommissioned/Bad: None Confirmation to proceed with upgrade operations? (yes/no):
Type "yes" and press ENTER.
Code Block title Example collapse true -----------------------Upgrade Preparations (part 1)------------------------ Copying upgrade package and preparing each CPU. Preparing 13 Checking mounts.................Pass Checking available space........Pass Sending package.................Pass Preparing 3 Checking mounts.................Pass Checking available space........Pass Sending package.................Pass Preparing 12 Checking mounts.................Pass Checking available space........Pass Sending package.................Pass Setting up new OS files on 13: Started Setting up new OS files on 3: Started Setting up new OS files on 12: Started Waiting for OS setup to finish... 3: Pass 12: Pass 13: Pass -------------------------------System Backup-------------------------------- Generating new backup...Pass -----------------------Upgrade Preparations (part 2)------------------------ Preparing 13 fstab, restore id and keys......Pass Copying backup..................Pass Preparing 3 fstab, restore id and keys......Pass Copying backup..................Pass Preparing 12 fstab, restore id and keys......Pass Copying backup..................Pass Preparing 2 fstab, restore id and keys......Pass Copying backup..................NA Should user input (a y/n prompt) be required after each CPU is upgraded? (yes/no) [n]:
Type "yes" and press ENTER.
Code Block title Example Upgrade execution order [13, 3, 12, 2]. To continue, press the Enter key:
Press ENTER.
Code Block title Example -----------------------------Final upgrade step----------------------------- Upgrading peer 13 Backup stats files..............Pass Modify boot file................Pass Setting restore information.....Pass Rebooting.......................Pass Waiting to recover..............Pass Waiting for system processes....Pass Machine 13 is complete, type "yes" to continue.:
The script will upgrade remaining cards one a a time. Respond with "yes" when prompted to continue.
- Continue to upgrade all CPUs. After the software upgrade is completed on the CPUs, ensure that the upgrade was successful and the software was properly installed by continuing to the next section.
Verify the CPU Software has been Properly Installed
Note | ||
---|---|---|
| ||
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. |
Start
- At the Linux prompt, enter startmenu, and press ENTER.
- Select System, and press ENTER.
- Select Software Revisions, and press ENTER.
- Select CPU Versions, and press ENTER
Make sure that the software and OS have been upgraded, all cards are running the same software, and that there are no asterisks beside any of the cards.
Tip title Tip The output of the “CPU Versions” command 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” commands show the number of processes running on each CPU.
Code Block title Example AVAILABLE SOFTWARE VERSIONS -------------------------------------------------------------------------------- No new load detected on system. Upload and run load .sh file on /var/log before attempting upgrade. CPU (current) dsc_8000_20_0_0_nb20201008 OS: Ribbon7.4.18 (Servicepack) [none applied] CPU (previous) dsc_8000_18_1_0_nb20200612 OS: Ribbon7.4.18 (Servicepack) RUNNING SOFTWARE VERSIONS (*=update required, ?=update unknown) CARD BUILD SERVICE O/S -SLOT----TYPE----------RELEASE--VERSION----PACK---IMAGE-------CARD STATUS--- -------------------------------------------------------------------------------- Slot 2 MGMT 20.0.0 (nb20201008) SP: OS: Ribbon7.4.18 18 procs running Slot 13 MGMT 20.0.0 (nb20201008) SP: OS: Ribbon7.4.18 18 procs running Slot 3 ROUTING 20.0.0 (nb20201008) SP: OS: Ribbon7.4.18 21 procs running Slot 12 ROUTING 20.0.0 (nb20201008) SP: OS: Ribbon7.4.18 21 procs running (p=servicepack is partially applied) Select CPU slot number (9) to begin commissioning of individual card(s). Enter slot # or ENTER to cancel: No selection, exiting.
- Press ENTER to cancel.
- Pressing ENTER displays the Main Menu.
Upgrade the Software on the Ethernet (MCH) Cards
Start
- At the Linux prompt, enter startmenu, and press ENTER.
- Select System, and press ENTER.
- Select Software Revisions, and press ENTER.
Select Switch Versions, and press ENTER.
Code Block title Example AVAILABLE SOFTWARE VERSIONS -------------------------------------------------------------------------------- MCH (current) dsc_8000_20_0_0_nb20201008 (Servicepack) [none applied] MCH (previous) dsc_8000_18_1_0_nb20200612 (Servicepack) RUNNING SOFTWARE VERSIONS (*=update required, ?=update unknown) CARD BUILD SERVICE O/S -SLOT----TYPE------RELEASE-VERSION----PACK-----IMAGE------------CARD STATUS----- -------------------------------------------------------------------------------- -- Chassis 1 -- Slot 1 MCH * 18.1.0 (nb20200612) SP: Slot 14 MCH * 18.1.0 (nb20200612) SP: (p=servicepack is partially applied) Status legend: A - Active, S - Standby, ? - Unknown Select MCH slot number (1 14) to begin upgrade of ISM and SWITCH functions on that MCH. VERSION field modifiers (investigate & update): '***' - a mismatch between the two switches within the MCH. '*!!' - one of the two switches within the MCH is unreachable. Enter slot # or ENTER to cancel:
Type "14" and press ENTER.
Code Block title Example Note: flex_slot.conf file doesn't exist ... This is ok if the SDA is not configured on the system. Software Update for Switch Card in Slot #14 Determining running and current software version. Please wait... Running on SWITCH (slot14_0): -Load: dsc_8000_18_1_0_nb20200612 Current SWITCH version (on MGMT CPU): -Load: dsc_8000_20_0_0_nb20201008 -Servicepack: [none applied] 'u' - Update version (update slot14_0 to match the current load): -Load: dsc_8000_20_0_0_nb20201008 Select action to take, or any other key to cancel:
Type "u" and press ENTER.
Code Block title Example avail_switch_current_load is dsc_8000_20_0_0_nb20201008 avail_ism_current_load is Running SWITCH software is out-of-date! You have opted to update/reboot slot #14, thereby loading the current software: -Load: dsc_8000_20_0_0_nb20201008 -Servicepack: [none applied] MCH upgrade pre-step: disable TIPC bearer p19p2 for MCH 1. Updating/rebooting switch card in slot #14. Please wait... Note: The switch status may be unavailable for a few minutes while it performs its upgrade procedures. CPU local tftp is enabled. Running SWITCH slot 14 software is now up-to-date. MCH upgrade post-step: enable TIPC bearer p19p2 for MCH 1 Press <return> to continue.
Navigate to Software Revisions, and press ENTER.
Select Switch Versions, and press ENTER.
Code Block title Example AVAILABLE SOFTWARE VERSIONS MCH (current) dsc_8000_20_0_0_nb20201008 (Servicepack) [none applied] MCH (previous) dsc_8000_18_1_0_nb20200612 (Servicepack) RUNNING SOFTWARE VERSIONS (*=update required, ?=update unknown) CARD BUILD SERVICE O/S -SLOT----TYPE------RELEASE-VERSION----PACK-----IMAGE------------CARD STATUS----- -------------------------------------------------------------------------------- -- Chassis 1 -- Slot 1 MCH * 18.1.0 (nb20200612) SP: Slot 14 MCH 20.0.0 (nb20201008) SP: (p=servicepack is partially applied) Status legend: A - Active, S - Standby, ? - Unknown Select MCH slot number (1 14) to begin upgrade of ISM and SWITCH functions on that MCH. VERSION field modifiers (investigate & update): '***' - a mismatch between the two switches within the MCH. '*!!' - one of the two switches within the MCH is unreachable. Enter slot # or ENTER to cancel:
Type "1" and press ENTER.
Code Block title Example Determining running and current software version. Please wait... Running on SWITCH (slot1_0): -Load: dsc_8000_18_1_0_nb20200612 Current SWITCH version (on MGMT CPU): -Load: dsc_8000_20_0_0_nb20201008 -Servicepack: [none applied] 'u' - Update version (update slot1_0 to match the current load): -Load: dsc_8000_20_0_0_nb20201008 Select action to take, or any other key to cancel:
Type "u" and press ENTER.
Code Block title Example avail_switch_current_load is dsc_8000_20_0_0_nb20201008 avail_ism_current_load is Running SWITCH software is out-of-date! You have opted to update/reboot slot #1, thereby loading the current software: -Load: dsc_8000_20_0_0_nb20201008 -Servicepack: [none applied] MCH upgrade pre-step: disable TIPC bearer p19p1 for MCH 0. Updating/rebooting switch card in slot #1. Please wait... Note: The switch status may be unavailable for a few minutes while it performs its upgrade procedures. CPU local tftp is enabled. Connection closed by foreign host.
Execute steps 1 to 10 for each shelf (chassis) if you have a multi-shelf system.
Tip The slot numbers for the MCH cards in a multishelf configuration are as follows:
- Expansion Shelf 1 MCH slot numbers are 15 and 28
- Expansion Shelf 2 MCH slot numbers are 29 and 42
- Expansion Shelf 3 MCH slot numbers are 43 and 56
For more informaiton about the DSC 8000 hardware configuration, refer to DSC 8000 Hardware Description.
After the software upgrade is complete, make sure the upgrade was successful and the software was properly installed (see To verify the Ethernet Switch (MCH) software has been properly installed).
Verify the Ethernet Switch (MCH) Software has been Properly Installed
Note | ||
---|---|---|
| ||
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, is recommended that you contact Customer Support. |
Start
- To confirm the Ethernet Switch cards are also running the same software as the CPU cards, do the following:
- Navigate to the Software Revisions screen.
- Select Switch Versions, and press ENTER.
Make sure the software and OS have been upgraded, all cards are running the same software, and there is no asterisk beside any of the cards.
Code Block title Example AVAILABLE SOFTWARE VERSIONS -------------------------------------------------------------------------------- MCH (current) dsc_8000_20_0_0_nb20201008 (Servicepack) [none applied] MCH (previous) dsc_8000_18_1_0_nb20200612 (Servicepack) RUNNING SOFTWARE VERSIONS (*=update required, ?=update unknown) CARD BUILD SERVICE O/S -SLOT----TYPE------RELEASE-VERSION----PACK-----IMAGE------------CARD STATUS----- -------------------------------------------------------------------------------- -- Chassis 1 -- Slot 1 MCH 20.0.0 (nb20201008) SP: Slot 14 MCH 20.0.0 (nb20201008) SP: (p=servicepack is partially applied) Status legend: A - Active, S - Standby, ? - Unknown Select MCH slot number (1 14) to begin upgrade of ISM and SWITCH functions on that MCH. VERSION field modifiers (investigate & update): '***' - a mismatch between the two switches within the MCH. '*!!' - one of the two switches within the MCH is unreachable. Enter slot # or ENTER to cancel: No selection, exiting.
- Pressing ENTER twice displays the Main Menu.
Upgrade the Software on the IO Cards
Execute both of the following procedures in order to upgrade the software on the IO cards.
Verify the Health of the IO Configuration Files
Use this procedure if the system contains IO cards. This procedure executes a health check script that verifies the existence of the mp_mtp2.conf.slotX files on the IO card as well as its synchronization to the management CPU card (X is the IO slot number).
Start
- Log onto a Management CPU.
Enter "health_check_io.sh X" to execute the health check script.
Info title Note X is the IO number.
This command should be executed for each IO.
- The script produces a health check result, which is either PASS or ERROR.
- If the result is ERROR, proceed to step 4 and 5.
- If the result is PASS, proceed to step 6.
- If the result is ERROR, the issue is either missing or mismatched files on the IO card.
- When an issue is detected, the script allows the user to copy the necessary files from the management CPU card to the IO card. If all the files are retrieved successfully, then the result will be PASS.
If the health check result is PASS, proceed to the next section: To Upgrade the software on the IOs
Info | ||
---|---|---|
| ||
Only proceed to the upgrade IO card progress if the health check result is PASS. |
Upgrade the Software on the IO Cards
Prerequisites
- You are logged onto a Management CPU.
Start
- At the Linux prompt, enter startmenu, and press ENTER.
- Select System, and press ENTER.
- Select Software Revisions, and press ENTER.
Select IO Versions and press ENTER.
Code Block title Example AVAILABLE SOFTWARE VERSIONS -------------------------------------------------------------------------------- IO (current) AMC348 dsc_8000_20_0_0_nb20201008 OS: rel_12_00_p04.x511.img (Servicepack) [none applied] IO (prev) AMC348 dsc_8000_18_1_0_nb20200612 OS: rel_12_00_p04.x511.img (Servicepack) RUNNING SOFTWARE VERSIONS (*=update required, ?=update unknown) CARD BUILD SERVICE O/S -SLOT----TYPE----------RELEASE-VERSION------PACK-----IMAGE------- -------------------------------------------------------------------------------- Slot 6 IO AMC348 * 18.1.0 (nb20200612) SP: OS: rel_12_00_p04.x511.img Slot 10 IO AMC348 * 18.1.0 (nb20200612) SP: OS: rel_12_00_p04.x511.img (p=servicepack is partially applied) Select IO slot number (6 10) to begin upgrade or decommissioning of individual card(s). Enter slot # or ENTER to cancel:
Enter the slot number for the IO card as required (in this example, 6) and press ENTER.
Tip title Tip You may be prompted for a password from the IO card. To proceed with the upgrade, enter the root password.
Code Block title Example Note: flex_slot.conf file doesn't exist ... This is ok if the SDA is not configured on the system. Software Update for IO Card in Slot #6 Determining running and current software version. Please wait... Running on IO (slot6_0): -Load: dsc_8000_18_1_0_nb20200612 -OS: rel_12_00_p04.x511.img Current IO version (on MGMT CPU): -Load: dsc_8000_20_0_0_nb20201008 -OS: rel_12_00_p04.x511.img -Servicepack: [none applied] 'u' - Update version (update slot6_0 to match the current load): -Load: dsc_8000_20_0_0_nb20201008 -OS: rel_12_00_p04.x511.img 'd' - Decommission this IO card to prepare it for removal. Select action to take, or any other key to cancel:
Enter "u" and press ENTER.
Code Block title Example avail_switch_current_load is dsc_8000_20_0_0_nb20201008 avail_ism_current_load is Running IO software is out-of-date! You have opted to update/reboot slot #6, thereby loading the current software: -Load: dsc_8000_20_0_0_nb20201008 -OS: rel_12_00_p04.x511.img -Servicepack: [none applied] Pushing image to the IO card in slot #6 Executing verify_io_image.sh script on IO board in slot #6 DO NOT INTERRUPT!! THIS MAY TAKE A FEW MINUTES... Done: IO board was already up-to-date Rebooting IO card in slot #6. Press <return> to continue
Press ENTER and return to the main menu.
Repeat steps 1 to 7 for all other IO cards in the system as required.
- After the software upgrade is complete, make sure the upgrade was successful and the software was properly installed by continuing to the next section.
Verify the IO Software has been Properly Installed
Note | ||
---|---|---|
| ||
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, is recommended that you contact Customer Support. |
Start
- To confirm the IO cards are also running the same software as the CPU cards, do the following:
- Navigate to the Software Revisions screen.
- Select IO Versions, and press ENTER.
Make sure the software and OS have been upgraded, all cards are running the same software, and there is no asterisk beside any of the cards.
Tip title Tip You may be prompted to enter the appropriate password.
Code Block title Example AVAILABLE SOFTWARE VERSIONS -------------------------------------------------------------------------------- IO (current) AMC348 dsc_8000_20_0_0_nb20201008 OS: rel_12_00_p04.x511.img (Servicepack) [none applied] IO (prev) AMC348 dsc_8000_18_1_0_nb20200612 OS: rel_12_00_p04.x511.img (Servicepack) RUNNING SOFTWARE VERSIONS (*=update required, ?=update unknown) CARD BUILD SERVICE O/S -SLOT----TYPE----------RELEASE-VERSION------PACK-----IMAGE------- -------------------------------------------------------------------------------- Slot 10 IO AMC348 * 18.1.0 (nb20200612) SP: OS: rel_12_00_p04.x511.img (p=servicepack is partially applied) Select IO slot number (10) to begin upgrade or decommissioning of individual card(s). Enter slot # or ENTER to cancel:
- Pressing ENTER twice displays the Main Menu.
Upgrading the Software on Spare System Cards
The spare MCH and IO cards software can be updated when they are needed to replace a failed card. The cards are difficult to remove from the system, so do not attempt to remove the cards unless it is necessary. Contact Customer Support for assistance to upgrade the cards.
Info | ||
---|---|---|
| ||
Some of the system cards may be equipped with a yellow guard. You must remove these guards before inserting the respective card into the chassis’ slot. For more information, see the appropriate chapter in the DSC 8000 Hardware Installation Guide. |
Post Upgrade Processes
After the software upgrade is completed and considering any feature changes, validate the upgraded system.
Verify the system configuration and data recorded before the upgrade. See Collecting Common System Status Information. If there are discrepancies in the system prior to and after upgrade, contact Customer Support before considering a software rollback.
Info | ||
---|---|---|
| ||
A software rollback process only should be performed in case severe issues occur shortly after the software upgrade. Any provisioning or configuration changes that have been made after an upgrade are lost during a rollback process. |
Update MIBs Files on Trap Receivers
It is highly recommended that the new MIBS be downloaded from the upgraded system and compiled on the Trap Host. New features and parameters may exist in the new software that would not be contained in the older release MIBS. MIBS can be downloaded by logging into the WEB Interface and clicking on File Retrieval, and then clicking on the MIBS tab.
For information about obtaining the MIB files, refer to MIB Files.
Continuing Upgrade After Loss of Connection
Note | ||
---|---|---|
| ||
The DSC should never be left in a partially upgraded state. If the upgrade cannot be completed, a rollback should be performed. Changes should NEVER be made in the DSC while it is in a partially upgraded state. |
In the event the upgrade is performed via ssh to the DSC management CPU and a loss of connection is suffered while the CPU upgrade is in progress, you may continue the upgrade after reconnecting.
Restart the Upgrade
To restart an in progress upgrade after connection loss, reconnect to the direct IP of the management CPU the upgrade was initially started from and issue the 'upgrade' command again.
Info |
---|
Always select option A (Continue that upgrade process using the same backup) as seen in the example below. Never select option B unless directed to do so by Customer Support. |
When continuing a previous upgrade, some differences occur, as shown below:
Code Block |
---|
:::::::::::::::::::::::::::::::: Ribbon DSC :::::::::::::::::::::::::::::::: ┌───────────────────┐ │DSC8000 CPU Upgrade│ └───────────────────┘ _____________________________________________ Type "q" to quit from most prompts or CTRL-C. ┌────────────────────────Warning────────────────────────┐ │Found a previous upgrade in progress. You can: │ │ a) Continue that upgrade process using the same backup │ │or │ │ b) Restart using new backup. │ │Both options will skip any already upgraded peers. │ └────────────────────────────────────────────────────────┘ Please type 'continue' or 'restart' accordingly: |
The preupgrade check printout will change to:
Code Block |
---|
-----------------------------Pre Upgrade Check------------------------------ Recent preupgrade check found and all tests passed. Continuing with upgrade. |
And the backup printout will change to:
Code Block |
---|
-------------------------------System Backup-------------------------------- Generating new backup...Skipped - Using Lab230slot13-bak-29-09-20-151631-Complete-DSC8000.18.1.0.tar.gz |
Rolling Back a Partial Upgrade
If the loss of connection is not resolved with sufficient time left in the maintenance window to complete the upgrade, you will need to rollback from the newly upgraded management CPU.
Note | ||
---|---|---|
| ||
Rolling back from a partial upgrade must be completed as soon as connection can be restored to the DSC. No changes should be made on the DSC while in a partially upgraded state. |
One of the two management CPUs will ALWAYS be the first card upgraded. You will need to ssh to that CPU's direct IP and follow the rollback procedure for CPUs found here: Software Rollback Process - DSC 8000
If connection is lost during the upgrade of Switches or IO cards, if the software application verification fails, or the cards demonstrate issues, follow the rollback procedures found in the guide for the affected card(s).