Setrev - Cisco MGX 8850 Command Reference Manual

Chapter 2 Shelf Management Commands

setrev

Set Revision
Force-load and run a firmware version for a card. You must execute setrev from the CLI of the active
PXM45 whether the target is a service module or the PXM45.
Note For the first-time power-up of the node, you should execute the burnboot command to burn in the
bootcode. For details, refer to the Cisco MGX 8850 Routing Switch Software Configuration Guide,
Release 2.
From a high-level perspective, the setrev command has two effects. It causes the PXM45 to load a
firmware image from the hard drive to a card, then it causes the receiving card to run that image. The
impact is a non-graceful revision change. (A graceful revision path is available through the sequence of
loadrev, runrev, and commitrev. A revision is an upgrade if the new firmware version has a higher
numerical value or a downgrade if the new version has a lower value.)
At the time you initially bring up a node or after executing clrallcnf, the service modules have no
runtime firmware image, so you must execute setrev for each service module in the switch. For the
PXM45, Cisco ships the product with firmware installed, so executing setrev is not necessary until you
need to change firmware version or after you execute clrallcnf.
Version Numbering Conventions
This section describes how to interpret the version number of a firmware image. Commands such as
loadrev and setrev require a version number rather than a filename. Similarly, dspversion shows the
firmware version number rather than the firmware filename. Although the version number derives from
the firmware filename, they are distinctly different.
Firmware Filenames
The FW directory on the hard drive contains firmware files of possibly many revisions. (Each firmware
file has the fw file extension.) The format of a firmware filename is:
cardtype_version-element[_platform].fw
Note that platform is an optional field because it applies to only the PXM45. For example, a firmware
file may have the name "axsm_002.000.000.001.fw." Within this filename, the version-portion is
002.000.000.001. (Note the absence of "mgx.") This version-portion has the following format:
major-release.minor-release.maintenance.patch
The range for each release, maintenance, and patch is 0–255. Note that, as you read left-to-right, each
element is a superset of the element on the right, and the number on the right resets to 0 or 1 when the
element on its left is incremented. For example, if the minor-release number 010 rolls to 011, the
maintenance on its right is reset to 1, so the new version in the example is 002.011.000.000. (Note the
anomaly here is that the maintenance number resets to 1 rather than 0 because of the IOS convention of
starting maintenance numbers at 1.)
Version Numbers
To derive the firmware version number, the firmware filename is altered by removing insignificant
zeroes and being reformatted to include parentheses. The format of a version number is:
major-release.minor-release(maintenance.patch)
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Cisco MGX 8850 Routing Switch Command Reference
setrev
2-91