2-6
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 2
Shelf Management Commands
abortrev
abortrev
Abort Revision—return to the previous firmware version.
The abortrev command causes the target card to use the previous operational firmware image. It
provides a way out of a graceful upgrade that has shown signs of unacceptable performance. (For
example, a new feature may not perform as expected.) The commands for changing firmware versions
commands run on the PXM45, but they can target either a service module or the PXM45 itself.
You can execute the abortrev command after you have executed either loadrev or runrev but before
commitrev. (After commitrev, the only way to restore the previous version is to force-load it by
executing setrev or restoreallcnf.) The following list outlines the sequence for a graceful upgrade. For
a state-by-state view that elaborates on this subject, see
Table 2-5
and
Table 2-6
.
1.
loadrev loads a firmware version from the hard disk to a card’s memory. In a non-redundant card
setup, loadrev does not cause the system to reset the card.
2.
runrev causes the primary card to start running the new version. For a redundant pair of cards, the
standby becomes the active card then starts running the new version.
3.
If an unacceptable problem occurs, the optional abortrev command restores the previous version of
firmware as well as the previous database contents.
4.
commitrev declares the new primary version to be acceptable and removes the old primary from
main memory (but not the hard disk).
A graceful upgrade takes a single card or a redundant card pair through different states. In addition, the
stage at which you execute abortrev on a redundant pair determines whether the system resets one or
both cards in the pair. The reset depends on whether you execute abortrev before or after runrev. The
stages of a graceful upgrade and the reset actions appear in
Table 2-5
and
Table 2-6
. For a single-card
upgrade, see
Table 2-5
. For a redundant-pair upgrade, see
Table 2-6
.
The tables start by showing that, initially, the primary and secondary versions of firmware are 2.x, so
the only possible operational version is 2.x. The loadrev command loads a generic version called 2.y,
and the upgrade sequence progressively changes the primary and secondary firmware versions.
Table 2-5
Single-Card Upgrade From 2.x to 2.y
Firmware
Status
Initial Version
After loadrev
After runrev
After
commitrev
Primary
2.x
2.x
2.y
2.y
Secondary
2.x
2.y
2.x
2.y
Operational
2.x
2.x
2.y
2.y
After runrev,
the card resets.
