Specifications

5-413
Cisco ATM Services (AXSM) Configuration Guide and Command Reference for MGX Switches
Release 5.2, Part Number OL-6484-01 Rev. C0, September 2005
Chapter 5
dspversion
dspversion
Display Version—AXSM, AXSM-E, AXSM-32-T1E1-E, AXSM-XG
The dspversion command displays details for the versions of boot and runtime firmware images residing
on a card. Typically, you use the dspversion command in conjunction with the commands for changing
a card’s firmware version. (See “Related Commands” section below.) For example, you can enter the
dspversion command 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, the dspversion command
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 for possibly many revisions. Each firmware
file has the fw file extension. The format of a firmware filename follows:
cardtype_version-element[_platform].fw
Note that platform is an optional field because it applies only to the PXM45 card. For example, a
firmware file may have the name “axsm_003.000.001.001.fw.” Within this filename, the version-portion
of the filename is 003.000.001.001. (Note the absence of “mgx” in the filename.) The version-portion of
the filename has the following format:
major-release.minor-release.maintenance.patch
Using the example “axsm_003.000.001.001.fw,” the version portion is 3.0(1.1). Similarly, if no patch is
present in the firmware image, the version number would be 3.0(1).
The range for each release, maintenance, and patch is 0–255. Note, as you read left-to-right, that 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 “003.010.001.000.” (Note the
anomaly here is that the maintenance number resets to 1 rather than 0, due to 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 reformatting the filename to include parentheses. The format of a version number follows:
major-release.minor-release(maintenance.patch)phase
For example, the significance of 3.0(60.8)P1 is shown below:
major-release minor-release (maintenance.patch) phase
3. 0. (60.8) P1