2-39
Cisco MGX 8850 Routing Switch Command Reference
Release 2.0, Part Number 78-10467-04 Rev C0, October 2001
Chapter 2
Shelf Management Commands
commitrev
commitrev
Commit Revision
Completes a graceful upgrade by committing to the operating firmware image as the primary version.
The commitrev command is the necessary conclusion to a graceful upgrade. See the loadrev description
for more details about graceful firmware changes.
The impact of commitrev is:
•
It signifies that the primary firmware image activated through the runrev command is accepted.
•
The previous image is removed from the card’s main memory (but continues to reside on disk).
•
Starting another graceful revision change becomes possible. If you attempt loadrev on the same
card before you execute commitrev, the system blocks loadrev and states that a revision change is
in progress.
•
You cannot use abortrev to revert to the previous image. To bring a previous image into memory
and run it, you must use setrev to force-load the image (a non-graceful revision change) or execute
restoreallcnf.
The order of commands in a graceful upgrade, including the option of aborting the revision change,
appears in the following list. For clarification of where firmware resides after each stage of the upgrade,
refer to
Table 2-7
for a single card and
Table 2-8
for a redundant card pair.
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).
The stages of a graceful upgrade and the reset actions appear in
Table 2-7
and
Table 2-8
. For a
single-card upgrade, see
Table 2-7
. For a redundant-pair upgrade, see
Table 2-8
. 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. If you execute abortrev
before commitrev, one or two cards (redundant pair only) are reset, as the tables show.
Table 2-7
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
Current
2.x
2.x
2.y
2.y
After abortrev,
the card is reset.
