2-70
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 2
Shelf Management Commands
dspversion
dspversion
Display Version—display firmware versions on an individual card.
Show details for the versions of boot and runtime firmware residing on a card. Typically, you would use
dspversion in conjunction with the commands for changing a card’s firmware version. (See Related
Commands section.) For example, you can use dspversion to see if a particular firmware version is
currently running.
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
Using the example of axsm_002.000.000.001.fw, the version is 2.0(1.1). Similarly, if no patch were
present, the version number would be 2.0(1).
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)phase
For example, the significance of 2.0(14.8)P1 is shown below:
major-release minor-release (maintenance.patch) phase
2.
1.
(6.0)
P1