Cisco Cisco MGX 8230 and 8250 Modules Guida Alla Risoluzione Dei Problemi
Service Module to the Standby
PXM / Secondary Service
Module.
PXM / Secondary Service
Module.
commit
second loadrev
to new version
to new version
Completes the upgrade to the
new firmware version. Graceful
downgrade to original firmware
version is lost.
new firmware version. Graceful
downgrade to original firmware
version is lost.
abort
loadrev to old
version
version
Restores the PXM to the original
firmware version. Must be issued
prior to the commit command.
Not supported for Service
Module firmware.
firmware version. Must be issued
prior to the commit command.
Not supported for Service
Module firmware.
The MGX 8850 firmware provides redundancy by providing support for hot insertion and removal of the
PXM module, as well as 1:1 hot standby redundancy for high availability of the MGX 8850. The active and
standby PXM have exactly the same database in the local memory at any given time. The active PXM is
responsible for updating the standby PXM whenever the database is changed. When the active PXM fails, the
standby PXM will switchover in 100 milliseconds (msec). The switchover is transparent to the RPM and
service modules.
PXM module, as well as 1:1 hot standby redundancy for high availability of the MGX 8850. The active and
standby PXM have exactly the same database in the local memory at any given time. The active PXM is
responsible for updating the standby PXM whenever the database is changed. When the active PXM fails, the
standby PXM will switchover in 100 milliseconds (msec). The switchover is transparent to the RPM and
service modules.
In some cases, older firmware versions are incompatible with newer versions due to incompatible database
structures or incompatible MIB structures, and the MGX 8850 Boot Code and Firmware Upgrade Script for
Non−Redundant Switches script should be used. To determine compatibility, please refer to the Release Notes
for the desired firmware.
structures or incompatible MIB structures, and the MGX 8850 Boot Code and Firmware Upgrade Script for
Non−Redundant Switches script should be used. To determine compatibility, please refer to the Release Notes
for the desired firmware.
The tasks listed in this document are recommended for redundant MGX 8850 firmware upgrades using two
PXMs. The tasks were verified in the order shown in a laboratory test of a redundant MGX 8850 upgrade
from release 1.1.21 to release 1.1.24. To maintain database integrity an interim PXM runtime firmware
upgrade to release 1.1.23 was required. The path of the graceful upgrade was:
PXMs. The tasks were verified in the order shown in a laboratory test of a redundant MGX 8850 upgrade
from release 1.1.21 to release 1.1.24. To maintain database integrity an interim PXM runtime firmware
upgrade to release 1.1.23 was required. The path of the graceful upgrade was:
1.1.21 −> 1.1.23 −> 1.1.24.
•
This document lists the minimum required steps, and then addresses each step in some detail. The MGX 8850
is based on the same platform as the MGX 8220, and it is recommended that the MGX 8220 Upgrade and
Downgrade Matrices, Concepts and Definitions be reviewed to familiarize the reader with general upgrade
concepts. The screen displays used to illustrate the tasks were taken from laboratory equipment and are in no
way intended to specify Internet Protocol (IP) addressing or naming schemes.
is based on the same platform as the MGX 8220, and it is recommended that the MGX 8220 Upgrade and
Downgrade Matrices, Concepts and Definitions be reviewed to familiarize the reader with general upgrade
concepts. The screen displays used to illustrate the tasks were taken from laboratory equipment and are in no
way intended to specify Internet Protocol (IP) addressing or naming schemes.
Caution:
Only one image must be loaded onto the PXM per Trivial File Transfer Protocol (TFTP) session.
•
Multiple TFTP sessions are required to load boot code and firmware images onto a PXM.
•
If multiple firmware images are loaded in one TFTP session, all files copied after the initial image
will be corrupted.
will be corrupted.
•
This document is intended to be used as an aid for conducting successful firmware upgrades, but is
not a substitute for proper planning with your Cisco Sales Engineer, Systems Engineer, or Account
Manager.
not a substitute for proper planning with your Cisco Sales Engineer, Systems Engineer, or Account
Manager.
•
Components Used
The information in this document is based on the software and hardware versions below.