|
|
This chapter describes how to locate, download, and install firmware updates for the MGX 8850 switch. Because firmware updates are stored in the switch file system, this appendix starts with an introduction to browsing the file system.
The PXM45 hard disk stores log files, configuration files, and boot and runtime firmware. The switch operating system supports a set of UNIX-like commands that you can use to locate log files or manage software updates. Table A-1 lists commands that you can use to browse the file system.
 |
Note File and directory names in the switch file system are case sensitive. Also, some of the commands listed in Table A-1 are not available at all administrator access levels. |
| Command | Description |
|---|---|
Change directories. Access level required: ANYUSER or above. | |
Copies a file from one location to another. Syntax: copy <source file name> <destination file name> Access level required: GROUP1 or above. | |
Deletes a file. Syntax: del <file name> Access level required: GROUP1 or above. | |
List directory contents using long format, which includes the name, size, modification date, and modification time for each file. This command also displays the total disk space and free disk space. Syntax: ll Access level required: ANYUSER or above. | |
List directory contents using the short format, which displays filenames, total disk space, and free disk space. Syntax: ls Access level required: ANYUSER or above. | |
Display the present working directory. Syntax: pwd Access level required: ANYUSER or above. | |
Renames a file. Syntax: rename <old file name> <new file name> Access level required: GROUP1 or above. | |
Lists the login name for the current session. Syntax: whoami Access level required: ANYUSER or above. |
For information on locating software updates, refer to the Release Notes for the Cisco MGX 8850, Release 2.0.
This section describes how to copy firmware files to the MGX 8850 switch. The switch cards use boot firmware and runtime firmware. Each card uses the boot firmware to define communications between the card components and to enable cards to start up. The runtime firmware defines how the card operates after startup.
|
Note The boot and runtime firmware are installed on the switch at the factory. Before you copy new files to the switch, verify that you need to update them by following the procedure in "Verifying Card Firmware Version Levels," in "Preparing AXSM Cards and Lines for Communication." |
The MGX 8850 switch provides a File Transfer Protocol (FTP) service to support file transfers to the switch. If you have FTP client software and network connectivity to both the switch and the server where the firmware files are stored, you can FTP files directly from the server to the switch.
To copy the firmware files to the switch, use the following procedure.
Step 2 Using a workstation with FTP client software, transfer the files from the server to the switch directory C:/FW.
The procedure you use for transferring the files depends on the FTP client software you are using. When initiating the FTP connection, remember the following:
Step 3 To verify that the new files have been transferred to the switch, log into the switch and display the contents of the C:/FW directory.
For more information on browsing the switch file system, see "Browsing the File System," which appears earlier in this appendix.
The procedure you use for upgrading boot firmware is based on the configuration of your switch. This release of the Cisco MGX 8850 switch supports redundant PXM45 cards, which is the configuration recommended for production switches. When used for lab tests, the switch may be configured for a single PXM45 card.
The following sections describe the following:
PXM45 cards run two types of firmware: boot firmware and runtime firmware. Typically, boot firmware is updated less frequently than runtime firmware. When you upgrade PXM45 cards you might not need to upgrade the boot firmware. The Release Notes for the Cisco MGX 8850, Release 2.0 should indicate if a boot firmware upgrade is required.
When an upgrade requires both boot and runtime upgrades, you should upgrade the boot firmware first and the runtime firmware second. After you upgrade the runtime firmware, you have several options. You can revert to the previous runtime firmware version, maintain the option to revert back while using the newer version, or commit to the new version. The following sections describe how to complete these tasks.
When a boot firmware upgrade is required, the procedure for upgrading redundant PXM45 cards updates the standby card and then makes that card active. This method ensures a smooth transition to the new software and preserves all established calls. Any calls that are not established are lost.
Upgrading the boot firmware does the following:
1. Loads the new firmware on the standby PXM45 card
2. Makes the standby PXM45 card active
3. Loads the new firmware on the formerly active (now standby) PXM45 card
To upgrade the runtime firmware, use the following procedure.
Step 2 Establish a CLI session with the switch and determine which PXM45 card is in standby mode. To view the status of PXM45 card, use the cc command to switch to that card. The letter at the end of the prompt shows whether the card status is active (a) or standby (s).
The following example prompt shows a PXM45 card that is in standby mode:
mgx8850a.7.PXM.s >
Step 3 Establish a CLI session with the standby PXM45 card using the CP port on the UI-S3 back card and a user name with CISCO_GP privileges.
|
Note A CP port session is required because you will be resetting the node and entering commands in "Backup Boot mode," which is not accessible through other connection methods. |
Step 4 Upgrade the standby PXM45 boot code by using the following procedure:
a. At the switch prompt, enter the sh command to switch to the PXM45 shell mode.
mgx8850a.7.PXM.s > sh
pxm45>
b. At the shell prompt, enter the enter the sysBackupBoot command:
pxm45> sysBackupBoot
|
Note This command and all commands that you enter in shell mode are case sensitive. |
Press Return key stop auto-boot, d and Return for Diag... 4
c. When the auto-boot prompt appears, press Return to stop auto-boot and enter the PXM45 Backup Boot mode.
PPPPPPPPPPP XXX XXX M M 4444 555555555
PP PP XX XX MM MM 44 44 55
PP pp XX XX MMM MMM 44 44 55 555
PP pp XX XX MMMM MMMM 44 44 5555 55
PP PP XXXX MM MMMMM MM 44 44 55 55
PPPPPPPPP XX XX MM MMM MM 44444444444 55
PP XX XX MM MM 44 55 55
PP XX XX MM MM 44 55 55
PPPP XXX XXX MMMM MMMM 4444 5555
PXM45 BACKUP BOOT
To avoid reset from the Active card, use sysPxmRemove()
pxm45bkup>Use sysFWLoad() for FW download from active PXM.
d. When the PXM45 Backup Boot banner appears, press return to display the backup boot prompt:
pxm45bkup>
e. At the backup boot prompt, enter the sysPxm45Remove command:
pxm45bkup> sysPxm45Remove
f. To burn the boot firmware on the PXM45, enter the sysFlashBootBurn command as follows:
pxm45bkup> sysFlashBootBurn "filename"
pxm45bkup> sysFlashBootBurn "C:FW/pxm45_002.000.001.000_bt.fw"
g. When the switch prompts you to confirm this action, type y and press Return.
Flash download completed ... value = 0 = 0x0
h. When the boot code has been burned, reset the card with the reboot command. For example:
pxm45bkup> reboot
i. When the Login prompt appears, log in to the switch as you do at the beginning of a CLI session. The switch prompt should appear.
j. To confirm that the PXM45 card is now using the correct boot code, enter the dspcd command.
The Boot FW Rev row in the display should show the new revision as shown in the following example:
pop20one.7.PXM.a > dspcd
pop20one System Rev: 02.00 Aug. 08, 2000 07:56:06 PST
MGX8850 Node Alarm: CRITICAL
Slot Number 7 Redundant Slot: 8
Front Card Upper Card Lower Card
---------- ---------- ----------
Inserted Card: PXM45 UI Stratum3 PXM HardDiskDrive
Reserved Card: PXM45 UI Stratum3 PXM HardDiskDrive
State: Active Active Active
Serial Number: SAK0319004F SAK0332009K SAK0325007Q
Prim SW Rev: 2.0(10) --- ---
Sec SW Rev: 2.0(10) --- ---
Cur SW Rev: 2.0(10) --- ---
Boot FW Rev: 2.0(11) --- ---
800-level Rev: 04 04 03
Orderable Part#: 800-05306-01 800-05787-01 800-05052-02
CLEI Code:
Reset Reason: On Reset From Shell
Card Alarm: NONE
Failed Reason: None
Miscellaneous Information:
Type <CR> to continue, Q<CR> to stop:
After you confirm the upgrade to the first PXM45 card, the boot firmware upgrade for that card is complete. The upgraded card, which had been operating in standby mode, is now the active card. You must now upgrade the boot code on the other PXM45 card, which is operating in standby mode.
Step 5 To prepare for upgrading the other (non-upgraded) PXM45 card, establish a CLI session with that card using the CP port on its UI-S3 back card.
Step 6 Repeat Step 4 to upgrade the PXM45 card, and verify that the card has been properly upgraded.
Upgrading the runtime firmware does the following:
1. Loads the new firmware on the standby PXM45 card
2. Makes the standby PXM45 card active
3. Loads the new firmware on the formerly active (now standby) PXM45 card
To upgrade the runtime firmware, use the following procedure.
Step 2 Establish a configuration session using a user name with SERVICE_GP privileges or higher.
Step 3 Determine if there is an unfinished upgrade by doing the following:
a. If necessary, use the cc command to select the active PXM45 card.
b. Enter the dspcd command.
c. Check the dspcd command report to see if the same software revision is listed for the Primary Software Revision (Prim SW Rev), Secondary Software Revision (Sec SW Rev), and Current Software Revision (Curr SW Rev).
Step 4 If the primary and current software revisions are the same, and the secondary software revision is different, use the commitrev command to commit to the currently running firmware version.
For more information, see "Committing to a Runtime Firmware Upgrade," which appears later in this chapter.
Step 5 To load the new runtime firmware version on the standby PXM45 card, enter the following command:
mgx8850a.7.PXM.a > loadrev <slot> <revision>
Replace slot with the card slot number for the standby PXM45 card, and replace revision with the software version number for the update. You can find the software version number in the Release Notes for the Cisco MGX 8850, Release 2.0. You can also determine the version number from the runtime firmware filename as described in "Determining the Firmware Version Number from Filenames," which appears in "Switch Operating Procedures."
Step 6 When prompted to confirm the command, type y and press Return to continue.
Step 7 To start using the new runtime firmware version on the standby PXM45 card, enter the following command:
mgx8850a.7.PXM.a > runrev <slot> <revision>
Replace slot with the card slot number for the standby PXM45 card, and replace revision with the software version number specified with the loadrev command.
Step 8 When prompted to confirm the command, type y and press Return to continue.
Step 9 To verify that the standby PXM45 is running the new software version, use the cc command to select the standby PXM45 card, then enter the dspcd command to view the firmware version in use.
The following dspcd command report shows how the revision status changes after the loadrev command is entered:
pop20two.8.PXM.s > dspcd
pop20two System Rev: 02.00 Sep. 06, 2000 09:27:42 PST
MGX8850 Node Alarm: NONE
Slot Number 7 Redundant Slot: 8
Front Card Upper Card Lower Card
---------- ---------- ----------
Inserted Card: PXM45 UI Stratum3 PXM HardDiskDrive
Reserved Card: PXM45 UI Stratum3 PXM HardDiskDrive
State: Active Active Active
Serial Number: SAK033600AN SAK0332009P SAK0403005Q
Prim SW Rev: 2.0(10) --- ---
Sec SW Rev: 2.0(10) --- ---
Cur SW Rev: 2.0(11) --- ---
Boot FW Rev: 2.0(10) --- ---
800-level Rev: 12 04 06
Orderable Part#: 800-05983-01 800-05787-01 800-05052-03
CLEI Code: 0000000000 H 0000000000
Reset Reason: On Reset From Shell
Card Alarm: NONE
Failed Reason: None
Miscellaneous Information:
In the example above, the current software revision on the standby card changes to the new version specified with the loadrev command, 2.0(11). The active card is still running the 2.0(10) software and will continue to do so until the runrev command is entered.
The next example shows the dspcd command after the runrev command is entered:
pop20two.7.PXM.a > dspcd
pop20two System Rev: 02.00 Sep. 06, 2000 09:27:42 PST
MGX8850 Node Alarm: NONE
Slot Number 7 Redundant Slot: 8
Front Card Upper Card Lower Card
---------- ---------- ----------
Inserted Card: PXM45 UI Stratum3 PXM HardDiskDrive
Reserved Card: PXM45 UI Stratum3 PXM HardDiskDrive
State: Active Active Active
Serial Number: SAK033600AN SAK0332009P SAK0403005Q
Prim SW Rev: 2.0(11) --- ---
Sec SW Rev: 2.0(10) --- ---
Cur SW Rev: 2.0(11) --- ---
Boot FW Rev: 2.0(10) --- ---
800-level Rev: 12 04 06
Orderable Part#: 800-05983-01 800-05787-01 800-05052-03
CLEI Code: 0000000000 H 0000000000
Reset Reason: On Reset From Shell
Card Alarm: NONE
Failed Reason: None
Miscellaneous Information:
After the runrev command is entered, the switch starts running the new software revision loaded on the standby card. The switch is now running revision 2.0(11) on the former standby card, which became active when the runrev command was entered. The secondary software revision shows that a previous revision is still available. Whenever the secondary software revision is different from the primary and current software revisions, you can revert back to the secondary software revision as described in "Reverting Back from a Runtime Firmware Upgrade," which appears later in this chapter.
As with redundant card upgrades, when the Release Notes for the Cisco MGX 8850, Release 2.0 require boot and runtime firmware upgrades, you should upgrade the boot firmware first and then upgrade the runtime firmware second. The following sections describe how to complete these tasks.
When a boot firmware upgrade is required, the procedure for upgrading boot firmware on nonredundant PXM45 cards is simpler than for redundant cards, but it does not preserve established calls or calls in progress. If you have redundant PXM45 cards installed in the switch and want to maintain the established calls, see "Upgrading Boot Firmware on Redundant PXM45 Cards," which appears earlier in this appendix.
To upgrade the boot firmware, use the following procedure.
Step 2 Establish a CLI session with the PXM45 card using the CP port on the UI-S3 back card and a user name with CISCO_GP privileges.
|
Note A CP port session is required because you will be resetting the node and entering commands in "Backup Boot mode," which is not accessible through other connection methods. |
Step 3 At the switch prompt, enter the sh command to switch to the PXM45 shell mode.
mgx8850a.7.PXM.a > sh
The switch will display the following shell mode prompt:
pxm45>
Step 4 At the shell prompt, enter the enter the sysBackupBoot command:
pxm45> sysBackupBoot
|
Note This command and all commands that you enter in shell mode are case sensitive. |
 |
Tips If you are accessing the CP port through a terminal server, rebooting the PXM45 may disrupt your connection. Random characters may appear on the display or the display may appear to "hang." If this happens, use your terminal software command to reset the terminal connection. After a successful reset, switch status messages should start appearing on the display. |
The PXM45 card reboots after you enter this command. In the messages that appear, watch for the following prompt:
Press Return key stop auto-boot, d and Return for Diag... 4
Step 5 When the auto-boot prompt appears, press Return to stop auto-boot and enter the PXM45 Backup Boot mode.
Additional messages will appear, and then the following PXM45 Backup Boot banner appears:
PPPPPPPPPPP XXX XXX M M 4444 555555555
PP PP XX XX MM MM 44 44 55
PP pp XX XX MMM MMM 44 44 55 555
PP pp XX XX MMMM MMMM 44 44 5555 55
PP PP XXXX MM MMMMM MM 44 44 55 55
PPPPPPPPP XX XX MM MMM MM 44444444444 55
PP XX XX MM MM 44 55 55
PP XX XX MM MM 44 55 55
PPPP XXX XXX MMMM MMMM 4444 5555
PXM45 BACKUP BOOT
To avoid reset from the Active card, use sysPxmRemove()
pxm45bkup>Use sysFWLoad() for FW download from active PXM.
Step 6 When the PXM45 Backup Boot banner appears, press return to display the backup boot prompt:
pxm45bkup>
Step 7 To burn the boot firmware on the PXM45, enter the sysFlashBootBurn command as follows:
pxm45bkup> sysFlashBootBurn "filename"
|
Note This command and all commands that you enter in Backup Boot mode are case sensitive. |
Replace filename with the complete path to the boot file on the PXM45 hard drive. For example:
pxm45bkup> sysFlashBootBurn "C:FW/pxm45_002.000.010.000_bt.fw"
Step 8 When the switch prompts you to confirm this action, type y and press Return.
When the boot code burning process is complete, the switch displays a message similar to the following:
Flash download completed ... value = 0 = 0x0
Step 9 When the boot code has been burned, reset the card with the reboot command. For example:
pxm45bkup> reboot
Be patient and wait for Login prompt to appear.
Step 10 When the Login prompt appears, log in to the switch as you do at the beginning of a CLI session. The switch prompt should appear.
Step 11 To confirm that the PXM45 card is now using the correct boot code, enter the dspcd command.
The Boot FW Rev row in the display should show the new revision. For example, if you are upgrading from 2.0(1) to 2.0(10), this row would display as follows:
Boot FW Rev: 2.0(10)
After you confirm the upgrade to the PXM45 card, the boot firmware upgrade for that card is complete.
The procedure for upgrading nonredundant PXM45 cards is simpler than for redundant cards, but it does not preserve calls in progress. If you have redundant PXM45 cards installed in the switch and want to maintain the calls in progress, see "Upgrading Runtime Firmware on Redundant PXM45 Cards," which appears earlier in this appendix.
To upgrade the runtime firmware, use the following procedure.
Step 2 Establish a configuration session using a user name with SERVICE_GP privileges or higher.
Step 3 Determine if there is an unfinished upgrade by doing the following:
a. If necessary, use the cc command to select the active PXM45 card.
b. Enter the dspcd command.
c. Check the dspcd command report to see if the same software revision is listed for the Primary Software Revision (Prim SW Rev), Secondary Software Revision (Sec SW Rev), and Current Software Revision (Curr SW Rev).
Step 4 If the primary and current software revisions are the same, and the secondary software revision is different, use the commitrev command to commit to the currently running firmware version.
For more information, see "Committing to a Runtime Firmware Upgrade," which appears later in this chapter.
Step 5 To load the new runtime firmware version on the PXM45 card, enter the following command:
mgx8850a.7.PXM.a > loadrev <slot> <revision>
Replace slot with the card slot number for the PXM45 card, and replace revision with the software version number for the update. You can find the software version number in the Release Notes for the Cisco MGX 8850, Release 2.0. You can also determine the version number from the runtime firmware filename as described in "Determining the Firmware Version Number from Filenames," which appears in "Switch Operating Procedures."
Step 6 When prompted to confirm the command, type y and press Return to continue.
Step 7 To start using the new runtime firmware version on the active PXM45 card, enter the following command:
mgx8850a.7.PXM.a > runrev <slot> <revision>
Replace slot with the card slot number for the PXM45 card, and replace revision with the software version specified with the loadrev command.
Step 8 When prompted to confirm the command, type y and press Return to continue.
Step 9 To verify that the PXM45 card is running the new software version, use the dspcd <slot> command to view the firmware version in use.
The following dspcd command report shows how the revision status changes after the loadrev command is entered:
pop20two.7.PXM.a > dspcd
pop20two System Rev: 02.00 Sep. 06, 2000 09:27:42 PST
MGX8850 Node Alarm: NONE
Slot Number 7 Redundant Slot: 8
Front Card Upper Card Lower Card
---------- ---------- ----------
Inserted Card: PXM45 UI Stratum3 PXM HardDiskDrive
Reserved Card: PXM45 UI Stratum3 PXM HardDiskDrive
State: Active Active Active
Serial Number: SAK033600AN SAK0332009P SAK0403005Q
Prim SW Rev: 2.0(11) --- ---
Sec SW Rev: 2.0(10) --- ---
Cur SW Rev: 2.0(10) --- ---
Boot FW Rev: 2.0(10) --- ---
800-level Rev: 12 04 06
Orderable Part#: 800-05983-01 800-05787-01 800-05052-03
CLEI Code: 0000000000 H 0000000000
Reset Reason: On Reset From Shell
Card Alarm: NONE
Failed Reason: None
Miscellaneous Information:
In the example above, the primary software revision changes to the new version specified with the loadrev command, 2.0(11). The switch is still running the 2.0(10) software listed for the current software revision.
The next example shows the dspcd command after the runrev command is entered:
pop20two.7.PXM.a > dspcd
pop20two System Rev: 02.00 Sep. 06, 2000 09:27:42 PST
MGX8850 Node Alarm: NONE
Slot Number 7 Redundant Slot: 8
Front Card Upper Card Lower Card
---------- ---------- ----------
Inserted Card: PXM45 UI Stratum3 PXM HardDiskDrive
Reserved Card: PXM45 UI Stratum3 PXM HardDiskDrive
State: Active Active Active
Serial Number: SAK033600AN SAK0332009P SAK0403005Q
Prim SW Rev: 2.0(11) --- ---
Sec SW Rev: 2.0(10) --- ---
Cur SW Rev: 2.0(11) --- ---
Boot FW Rev: 2.0(10) --- ---
800-level Rev: 12 04 06
Orderable Part#: 800-05983-01 800-05787-01 800-05052-03
CLEI Code: 0000000000 H 0000000000
Reset Reason: On Reset From Shell
Card Alarm: NONE
Failed Reason: None
Miscellaneous Information:
After the runrev command is entered, the switch starts running the new primary revision software as shown in the example above. The switch is now running revision 2.0(11). The secondary software revision shows that a previous revision is still available. Whenever the secondary software revision is different from the primary and current software revisions, you can revert back to the secondary software revision as described in "Reverting Back from a Runtime Firmware Upgrade," which appears later in this chapter.
AXSM cards run two types of firmware: boot firmware and runtime firmware. Typically, boot firmware is updated less frequently than runtime firmware. When you upgrade AXSM cards, you might not need to upgrade the boot firmware. The Release Notes for the Cisco MGX 8850, Release 2.0 should indicate if a boot firmware upgrade is required.
When an upgrade requires both boot and runtime upgrades, you should upgrade the boot firmware first and the runtime firmware second. The MGX 8850 switch supports redundant and nonredundant AXSM cards. The following sections describe how to update the boot and runtime AXSM firmware for both configurations.
|
Note If you are upgrading runtime software on PXM45 and AXSM cards, upgrade the PXM45 cards first. If you upgrade the AXSM cards first, the switch may not correctly report the ASXM card status until the PXM45 cards have been upgraded. |
When you upgrade boot firmware on an AXSM card, you will terminate all established calls and all calls in progress. If you are upgrading redundant AXSM cards, upgrade the standby card, make the upgraded card active, and then upgrade the other card.
To upgrade the boot firmware, use the following procedure.
Step 2 Establish a CLI session with the switch using a user name with SERVICE_GP privileges or higher.
Step 3 To burn the new AXSM boot code, enter the burnboot command as follows:
pop20one.7.PXM.a > burnboot slot revision
Replace slot with the slot number of a standalone AXSM card or an AXSM card operating in standby mode. Replace revision with the software revision number to which you are upgrading. For example:
pop20one.7.PXM.a > burnboot 10 2.0(1)
Step 4 When prompted to confirm the upgrade, type y and press Return.
After you confirm the upgrade, the new boot code is burned into the AXSM card and the card is reset. Be patient, the card reset takes some time. You can use the dspcds command to display the status of the AXSM card. At first, the status may show that the card slot is empty or the card is rebooting. Reenter the command periodically to see the current status of the card. When the card status returns to active or standby, you are ready to continue.
Step 5 To confirm that the AXSM card is now using the correct boot code, use the following procedure:
a. Use the cc command to switch the prompt the to AXSM card you just upgraded.
b. Enter the dspcd command.
The Boot FW Rev row in the display should show the new revision as shown in the following example:
pop20one.10.AXSM.a > dspcd
Front Card Upper Card Lower Card
---------- ---------- ------------
Card Type: AXSM-4-622 SMFIR-2-622 SMFIR-2-622
State: Active Present Present
Serial Number: SAK0342003W SBK0406002N SAK0328000L
Boot FW Rev: 2.0(10) --- ---
SW Rev: 2.0(1) --- ---
800-level Rev: A0 14 10
Orderable Part#: 800-5774-6 800-5383-1 800-5383-1
PCA Part#: 73-4504-3 73-4125-1 73-4125-1
Reset Reason:On Power up
Card SCT Id: 0 !DefaultSCT used!
Type <CR> to continue, Q<CR> to stop: dspcd
After you confirm the upgrade to the AXSM card, the boot firmware upgrade for that card is complete.
Step 6 To upgrade the other card in a redundant AXSM pair, do the following:
a. Make the upgraded AXSM card the active AXSM card by entering the switchredcd command as described in "Switching Between Redundant AXSM Cards," in "Switch Operating Procedures."
b. Repeat Steps 3 through 5.
Upgrading the runtime firmware requires the following:
1. Load the new firmware on the standby AXSM card
2. Makes the standby AXSM card active
3. Loads the new firmware on the formerly active (now standby) AXSM card
To upgrade the runtime firmware, use the following procedure.
Step 2 Establish a configuration session using a user name with SERVICE_GP privileges or higher.
Step 3 Determine if there is an unfinished upgrade by doing the following:
a. Enter the dspcd <slot> command.
b. Check the dspcd command report to see if the same software revision is listed for the Primary Software Revision (Prim SW Rev), Secondary Software Revision (Sec SW Rev), and Current Software Revision (Curr SW Rev).
Step 4 If the primary and current software revisions are the same, and the secondary software revision is different, use the commitrev command to commit to the currently running firmware version.
For more information, see "Committing to a Runtime Firmware Upgrade," which appears later in this chapter.
Step 5 To load the new runtime firmware version on the standby AXSM card, enter the following command:
mgx8850a.7.PXM.a > loadrev <slot> <revision>
Replace slot with the card slot number for the standby AXSM card, and replace revision with the software version number for the update. You can find the software version number in the Release Notes for the Cisco MGX 8850, Release 2.0. You can also determine the version number from the runtime firmware filename as described in "Determining the Firmware Version Number from Filenames," which appears in "Switch Operating Procedures."
Step 6 When prompted to confirm the command, type y and press Return to continue.
Step 7 To start using the new runtime firmware version on the standby AXSM card, enter the following command:
mgx8850a.7.PXM.a > runrev <slot> <revision>
Replace slot with the card slot number for the standby AXSM card, and replace revision with the software version number specified with the loadrev command.
Step 8 When prompted to confirm the command, type y and press Return to continue.
Step 9 To verify that the standby AXSM is running the new software version, use the dspcd <slot> command to view the firmware version in use.
The following dspcd command report shows how the revision status changes after the loadrev command is entered:
pop20two.9.PXM.s > dspcd 1
pop20two System Rev: 02.00 Sep. 06, 2000 09:36:34 PST
MGX8850 Node Alarm: MAJOR
Slot Number: 1 Redundant Slot:
Front Card Upper Card Lower Card
---------- ---------- ----------
Inserted Card: AXSM_4OC12 SMFIR_2_OC12 SMFIR_2_OC12
Reserved Card: AXSM_4OC12 SMFIR_2_OC12 SMFIR_2_OC12
State: Active Active Active
Serial Number: SAK03500088 SBK0406002V SAK0346003F
Prim SW Rev: 2.0(10) --- ---
Sec SW Rev: 2.0(10) --- ---
Cur SW Rev: 2.0(11) --- ---
Boot FW Rev: 2.0(11) --- ---
800-level Rev:
Orderable Part#: 800-05774-05 800-05383-01 800-05383-01
CLEI Code: 1234567890 BAI9ADTAAA 0000000000
Reset Reason: UNKNOWN REASON (0x41)
Card Alarm: NONE
Failed Reason: None
Miscellaneous Information:
In the example above, the current software revision on the standby card changes to the new version specified with the loadrev command, 2.0(11). The active card is still running the 2.0(10) software and will continue to do so until the runrev command is entered.
The next example shows the dspcd command after the runrev command is entered:
pop20two.9.PXM.a > dspcd 1
pop20two System Rev: 02.00 Sep. 06, 2000 09:36:34 PST
MGX8850 Node Alarm: MAJOR
Slot Number: 1 Redundant Slot:
Front Card Upper Card Lower Card
---------- ---------- ----------
Inserted Card: AXSM_4OC12 SMFIR_2_OC12 SMFIR_2_OC12
Reserved Card: AXSM_4OC12 SMFIR_2_OC12 SMFIR_2_OC12
State: Active Active Active
Serial Number: SAK03500088 SBK0406002V SAK0346003F
Prim SW Rev: 2.0(11) --- ---
Sec SW Rev: 2.0(10) --- ---
Cur SW Rev: 2.0(11) --- ---
Boot FW Rev: 2.0(11) --- ---
800-level Rev:
Orderable Part#: 800-05774-05 800-05383-01 800-05383-01
CLEI Code: 1234567890 BAI9ADTAAA 0000000000
Reset Reason: UNKNOWN REASON (0x41)
Card Alarm: NONE
Failed Reason: None
Miscellaneous Information:
After the runrev command is entered, the switch starts running the new software revision loaded on the standby card. The switch is now running revision 2.0(11) on the former standby card, which became active when the runrev command was entered. The secondary software revision shows that a previous revision is still available. Whenever the secondary software revision is different from the primary and current software revisions, you can revert back to the secondary software revision as described in "Reverting Back from a Runtime Firmware Upgrade," which appears later in this chapter.
The procedure for upgrading nonredundant AXSM cards is simpler than for redundant cards, but it does not preserve calls in progress. If you have redundant AXSM cards installed in the switch and want to maintain the calls in progress, see "Upgrading Runtime Firmware on Redundant AXSM Cards," which appears earlier in this appendix.
To upgrade the runtime firmware, use the following procedure.
Step 2 Establish a configuration session using a user name with SERVICE_GP privileges or higher.
Step 3 Determine if there is an unfinished upgrade by doing the following:
c. Enter the dspcd <slot> command.
d. Check the dspcd command report to see if the same software revision is listed for the Primary Software Revision (Prim SW Rev), Secondary Software Revision (Sec SW Rev), and Current Software Revision (Curr SW Rev).
Step 4 If the primary and current software revisions are the same, and the secondary software revision is different, use the commitrev command to commit to the currently running firmware version.
For more information, see "Committing to a Runtime Firmware Upgrade," which appears later in this chapter.
Step 5 To load the new runtime firmware version on the AXSM card, enter the following command:
mgx8850a.7.PXM.a > loadrev <slot> <revision>
Replace slot with the card slot number for the AXSM card, and replace revision with the software version number for the update. You can find the software version number in the Release Notes for the Cisco MGX 8850, Release 2.0. You can also determine the version number from the runtime firmware filename as described in "Determining the Firmware Version Number from Filenames," which appears in "Switch Operating Procedures."
Step 6 When prompted to confirm the command, type y and press Return to continue.
Step 7 To start using the new runtime firmware version on the active AXSM card, enter the following command:
mgx8850a.7.PXM.a > runrev <slot> <revision>
Replace slot with the card slot number for the AXSM card, and replace revision with the software version specified with the loadrev command.
Step 8 When prompted to confirm the command, type y and press Return to continue.
Step 9 To verify that the AXSM card is running the new software version, use the dspcd <slot> command to view the firmware version in use.
The following dspcd command report shows how the revision status changes after the loadrev command is entered:
pop20two.9.PXM.a > dspcd 1
pop20two System Rev: 02.00 Sep. 06, 2000 09:36:34 PST
MGX8850 Node Alarm: MAJOR
Slot Number: 1 Redundant Slot:
Front Card Upper Card Lower Card
---------- ---------- ----------
Inserted Card: AXSM_4OC12 SMFIR_2_OC12 SMFIR_2_OC12
Reserved Card: AXSM_4OC12 SMFIR_2_OC12 SMFIR_2_OC12
State: Active Active Active
Serial Number: SAK03500088 SBK0406002V SAK0346003F
Prim SW Rev: 2.0(11) --- ---
Sec SW Rev: 2.0(10) --- ---
Cur SW Rev: 2.0(10) --- ---
Boot FW Rev: 2.0(11) --- ---
800-level Rev:
Orderable Part#: 800-05774-05 800-05383-01 800-05383-01
CLEI Code: 1234567890 BAI9ADTAAA 0000000000
Reset Reason: UNKNOWN REASON (0x41)
Card Alarm: NONE
Failed Reason: None
Miscellaneous Information:
In the example above, the primary software revision changes to the new version specified with the loadrev command, 2.0(11). The switch is still running the 2.0(10) software listed for the current software revision.
The next example shows the dspcd command after the runrev command is entered:
pop20two.9.PXM.a > dspcd 1
pop20two System Rev: 02.00 Sep. 06, 2000 09:36:34 PST
MGX8850 Node Alarm: MAJOR
Slot Number: 1 Redundant Slot:
Front Card Upper Card Lower Card
---------- ---------- ----------
Inserted Card: AXSM_4OC12 SMFIR_2_OC12 SMFIR_2_OC12
Reserved Card: AXSM_4OC12 SMFIR_2_OC12 SMFIR_2_OC12
State: Active Active Active
Serial Number: SAK03500088 SBK0406002V SAK0346003F
Prim SW Rev: 2.0(11) --- ---
Sec SW Rev: 2.0(10) --- ---
Cur SW Rev: 2.0(11) --- ---
Boot FW Rev: 2.0(11) --- ---
800-level Rev:
Orderable Part#: 800-05774-05 800-05383-01 800-05383-01
CLEI Code: 1234567890 BAI9ADTAAA 0000000000
Reset Reason: UNKNOWN REASON (0x41)
Card Alarm: NONE
Failed Reason: None
Miscellaneous Information:
After the runrev command is entered, the switch starts running the new primary revision software as shown in the example above. The switch is now running revision 2.0(11). The secondary software revision shows that a previous revision is still available. Whenever the secondary software revision is different from the primary and current software revisions, you can revert back to the secondary software revision as described in the next section.
After upgrading the runtime firmware, you can revert to the previously used version of firmware at any time, as long as you have not committed to the new firmware version with the commitrev command (which is described in the next section).
|
Note Reverting to the previously used version of runtime firmware terminates all calls in progress. |
To revert to the previously used runtime firmware version, use the following procedure.
Step 2 To display the software revisions known to the switch, enter the dspcd <slot> command.
Replace slot with the slot number of the active PXM45 or AXSM card. To complete the next step, you need to know the secondary software revision shown in the display.
|
Note If the primary and secondary software revisions are the same, there is no other revision level to revert back to. |
Step 3 To abort use of the primary software revision and revert back to the secondary software revision, enter the following command:
mgx8850a.7.PXM.a > abortrev <slot> <revision>
Replace slot with the card slot number for the active PXM45 or AXSM card, and replace revision with the software version number for the secondary software revision.
Step 4 To verify that the standby card is running the previously used software version, enter the dspcd <slot> command to view the firmware version in use.
Committing to an upgrade does the following:
Once you are sure that an upgrade is stable, you can use the commitrev command commit to that firmware version. This prevents other administrators from inadvertently reverting to the previous version. You must also commit to the current software version before you can upgrade to another software version.
To commit to the currently running runtime firmware version, use the following procedure.
Step 2 To commit to the firmware version, enter the following command:
mgx8850a.7.PXM.a > commitrev <slot> <revision>
Replace slot with the card slot number for the active PXM45 or AXSM card, and replace revision with the software version number for the currently used firmware version. To display the firmware version number, use the dspcd <slot> command to view the firmware version in use.
Posted: Thu Sep 14 18:53:31 PDT 2000
Copyright 1989-2000©Cisco Systems Inc.