2-91
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter2 Shelf Management Commands setrev
setrev
Set Revision
Force-load and run a firmware version fo r a ca rd. You must execute setrev from the CLI of the active
PXM45 whether the target is a s er vi ce mod u le or t he PX M 45 .
Note For the first-time power-up of the node, you should execute the burnboot command to burn in the
bootcode. For detai ls, re fe r 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 P X M 45 t o lo ad a
firmware image from the hard drive to a c ard, then it causes the receiving c ar d to r un t hat i mag e. The
impact is a non-graceful revi sion change. (A graceful revision path is available through the seque nce of
loadrev, runrev, and commitrev. A revision is an upgrade if the new firmware vers io n ha s 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 th e
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 h ow to in te rp r et 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 d is ti n ctl y di fferent.
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 for m at o f a firmw ar e filen am e 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-po r tio n is
002.000.000.001. (Note the absence of “mgx.”) This version-portion has the following format:
major-release.minor-release.mainte nance.patch
The range for each releas e, maintenance, and patch is 0–255. Note that, as you read left-to-right, each
element is a superset of the ele m en t o n th e ri gh t , an d th e nu m b er o n the right resets to 0 or 1 when th e
element on its left is incremented. For example, if the m inor-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 b ecause 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(main tenance.patch)