Cisco Cisco MGX 8880 Media Gateway Notas de publicación
3
Release Notes for Cisco Voice Switch Service Module (VXSM) Release 5.2.10.201
Part Number OL-9215-01 Rev. A0, February 15, 2006
Upgrading from an Earlier VXSM Release
Upgrading from an Earlier VXSM Release
VXSM can be gracefully upgraded (configuration is preserved) from VXSM Release 5.0.70, Release
5.2.0 and Release 5.2.10.200 so long as the original and the upgraded images are of the same version
(for example Non-CALEA, TGCP to Non-CALEA, TGCP). When loading or upgrading a boot or
runtime image to a VXSM card, users must observe the following caution.
5.2.0 and Release 5.2.10.200 so long as the original and the upgraded images are of the same version
(for example Non-CALEA, TGCP to Non-CALEA, TGCP). When loading or upgrading a boot or
runtime image to a VXSM card, users must observe the following caution.
Warning
Many of the commands involved in loading or upgrading boot and runtime images can take several
minutes to execute completely. If the user resets or otherwise disturbs the VXSM card during a
loading or upgrading process, the card can easily be damaged even to the extent that it must be
returned to the factory for repair.
minutes to execute completely. If the user resets or otherwise disturbs the VXSM card during a
loading or upgrading process, the card can easily be damaged even to the extent that it must be
returned to the factory for repair.
In paricular:
Do not reset VXSM or PXM cards manually or through commands such as resetcd or resetsys
Do not save all MGX configurations with commands such as saveallcnfs.
Do not toggle primary/secondary cards through commands such as switchredcd, delred
Do not change the name of software image before or during the upgrade
Do not change any configuration of active primary card during the upgrade
Do not reset VXSM or PXM cards manually or through commands such as resetcd or resetsys
Do not save all MGX configurations with commands such as saveallcnfs.
Do not toggle primary/secondary cards through commands such as switchredcd, delred
Do not change the name of software image before or during the upgrade
Do not change any configuration of active primary card during the upgrade
THE REAPPEARANCE OF THE COMMAND PROMPT AFTER A COMMAND IS ENTERED DOES NOT
INDICATE THAT THE IMAGE LOAD OR UPGRADE HAS BEEN COMPLETED.
INDICATE THAT THE IMAGE LOAD OR UPGRADE HAS BEEN COMPLETED.
After the execution of the burnboot, clrsmcnf, loadrev, or setrev commands, the user must execute
either a dspcds or dsprev command periodically to verify that the state of the VXSM card being loaded
or upgraded is either Active, Standby, or Failed.
either a dspcds or dsprev command periodically to verify that the state of the VXSM card being loaded
or upgraded is either Active, Standby, or Failed.
ONLY WHEN THE CARD IS DISPLAYED TO BE IN ONE OF THESE STATES IS IT SAFE TO GO TO THE NEXT
STEP.
STEP.
If the upgrade procedure is interrupted for reasons outside the control of the user (for example, a
power outage), see “Interrupted Procedure Recovery” below for instructions.
power outage), see “Interrupted Procedure Recovery” below for instructions.
Interrupted Procedure Recovery
In the event that a VXSM software upgrade procedure is interrupted (for example, power outage), and
both Primary and Secondary are stuck in 'Failed-U' state, perform the following procedure
both Primary and Secondary are stuck in 'Failed-U' state, perform the following procedure
Step 1
Execute the abortrev command:
abortrev <PrimarySlot> <NewImageRevision>
Step 2
If the primary VXSM becomes "Failed/Active" (out of Failed-U/Active"), then execute the resetcd
command
command
resetcd <PrimarySlot> (
Step 3
If the secondary VXSM becomes "Failed/Active" (out of Failed-U/Active"), then execute the resetcd
command:
command:
resetcd <SecondarySlot>
Step 4
Both primary and secondary VXSM cards should now have their original SW image and original DB