8
C H A P T E R
Upgrading VXSM Code Images from a Previous
Version
The chapter describes the procedure for setting up the image on a VXSM for the first time and for
upgrading VXSM cards from an earlier image.
Initial Considerations
1.
In order to upgrade the image on a VXSM card while preserving the call processing service, the
VXSM card must be one of a redundant pair of VXSM cards (in adjacent slots).
2.
Only one pair of VXSM cards can be upgraded at a time.
3.
Once the upgrade procedure is started, there must be no configuration changes until after the
upgrade is complete.
4.
VXSM downgrades are not supported.
5.
Only those upgrade paths (marked with X) shown in Table 8-1 are allowed. Note that only like to
like images are allowed. This table applies to both single card upgrades and redundant card pairs
upgrades.
Table 8-1
Allowable VXSM Image Upgrades
To Version
Non-CALEA,
H.248
Non-CALEA,
H.248
From
Version
Non-CALEA,
TGCP
Non-CALEA,
MGCP
CALEA,
TGCP
Non-CALEA,
TGCP
Non-CALEA,
MGCP
CALEA,
TGCP
X
X
X
X
Cisco Voice Switch Services (VXSM) Configuration Guide and Command Reference for MGX Switches and Media Gateways, Release 5
Part Number OL-4625-01 Rev. E0, April 14, 2005
8-1
Chapter 8
Upgrading VXSM Code Images from a Previous Version
Initial Considerations
6.
The new VXSM image must reside on the hard disk of the PXM cards before the upgrade procedure
can start. The VXSM disk can be browsed to ascertain whether or not the image exists. At the PXM
prompt, the PXM card will respond to Unix like commands (for example, cd for change directory,
ls for list short format, etc.) to allow the user to inspect the contents of the disk.
If the image doesn’t exist, it must be downloaded from a workstation using the FTP protocol (refer
to the PXM-45 Configuration Guide for more detailed information).
Check the release notes to see if the VXSM upgrade also requires an upgrade of the boot code image
in addition to the runtime image. If it does, the boot code image must also reside on the PXM’s hard
disk.
Warning
READ ALL OF THIS WARNING BEFORE PERFORMING THE PROCEDURES DESCRIBED IN THIS
CHAPTER!!!
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 to the extent that it must be returned
to the factory for repair.
THE REAPPEARANCE OF THE COMMAND PROMPT AFTER A COMMAND IS ENTERED DOES NOT
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.
ONLY WHEN THE CARD IS DISPLAYED TO BE IN ONE OF THESE STATES IS IT SAFE TO GO TO THE NEXT
STEP.
Loading a VXSM Image for the First Time
The procedure for loading images onto a VXSM card the first time the card is as follows.
Note
All the commands in the following procedure are performed on the gateway’s active PXM card.
Check the command prompt to verify that you are logged into the PXM card.
Step 1
Telnet to the media gateway. Check that you have the PXM card prompt. If necessary, check the location
of the VXSM cards by using the dspcds command.
Step 2
Check the release notes to see if the VXSM boot code image needs upgrading. If it does, use the
burnboot command to burn the boot code onto the desired VXSM card (otherwise, skip to step 4).
burnboot <slot> <revision>
For revision, use the revision number of the boot code image to be loaded (see later in this chapter for
information on revision numbers).
Step 3
8-2
Periodically check that the burnboot process has ended. To do this, use the dspcds or dsprev command
on the PXM. When the state of the VXSM card is displayed as either Active, Standby, or Failed, proceed
to the next step.
Cisco Voice Switch Services (VXSM) Configuration Guide and Command Reference for MGX Switches and Media Gateways, Release 5
Part Number OL-4625-01 Rev. E0, April 14, 2005
Chapter 8
Upgrading VXSM Code Images from a Previous Version
Initial Considerations
Step 4
Use the clrsmcnf command to the clear the VXSM card’s configuration. The format of this command is:
clrsmcnf <slot-id> [all]
Step 5
Periodically check that the clrsmcnf process has ended. To do this use the dspcds or dsprev command
on the PXM. When the state of the VXSM card is displayed as either Active, Standby, or Failed, proceed
to the next step.
Note
Step 6
If the -all parameter is used in the clrsmcnf command, the VXSM card will come up in the failed
state. This is normal and is expected.
Use the setrev command. This command loads the VXSM image with the specified call control protocol.
The format of this command is:
setrev <slot> <primary revision> [-ccp <CallControlProtocol>]
Specify the gateway control protocol as either H.248, TGCP, or MGCP as appropriate.
Step 7
Periodically check that the setrev process has ended. To do this use the dspcds or dsprev command on
the PXM. When the state of the VXSM card is displayed as either Active, Standby, or Failed, proceed to
the next step.
Step 8
Repeat steps 2 and 7 for any other VXSM cards that need to be brought up for the first time.
Step 9
Use the addred command to set up VXSM redundant pairs. The format of this command is:
addred <redprimaryslotnum><redstandbyslotnum><redtype>
Step 10
Switch to the VXSM cards and use their commands to configure the cards as necessary and bring them
into service.
Upgrade Procedure
To upgrade the VXSM cards, use the following steps. This procedure is for VXSM cards that are in
service and provides a graceful upgrade in which call processing continues during the upgrade. This
procedure can also be performed on a single VXSM card but the service will not be preserved during the
upgrade.
Telnet to the media gateway.
Note
All the commands in the following upgrade procedure are performed on the gateway’s active
PXM card. Check the command prompt to verify that you are logged into the PXM card.
Step 1
Determine which set of redundant VXSM cards is to be upgraded. Use the dspcds command if necessary
to locate the slot numbers of the VXSM cards. Determine which VXSM card slot in the set is primary
(active) and which is secondary (standby).
Step 2
Check the release notes to see if the VXSM boot code image needs upgrading. If it does, perform the
following substeps a, b, c, and d; otherwise skip these steps and go to step 3.
a.
use the burnboot command to burn the boot code onto the standby card.
burnboot <slot> <revision>
Cisco Voice Switch Services (VXSM) Configuration Guide and Command Reference for MGX Switches and Media Gateways, Release 5
Part Number OL-4625-01 Rev. E0, April 14, 2005
8-3
Chapter 8
Upgrading VXSM Code Images from a Previous Version
Initial Considerations
Note
Make sure that the slot number in the burnboot command is that of the standby VXSM card.
For revision, use the revision number of the bootcode image to be loaded (see later in this chapter
for information on revision numbers).
b.
Periodically check that the burnboot process has ended.To do this use the dspcds or dsprev
command on the PXM. When the state of the VXSM card is displayed as either Active, Standby, or
Failed, proceed to the next step.
c.
Use the switchredcd command to switch the states of the active and standby VXSM cards. The
format of this command is:
switchredcd <fromslot><toslot>
The fromslot parameter is the slot number of the active card in the VXSM redundant pair.The toslot
parameter is the slot number of the standby card in the VXSM redundant pair.
When this command is executed, the active card becomes the standby card and vice versa.
d.
Note
Use the burnboot command again to burn the boot code onto the new standby card.
Make sure that the slot number in the burnboot command is that of the new standby VXSM card.
e.
Periodically check that the burnboot process has ended. To do this use the dspcds or dsprev
command on the PXM. When the state of the VXSM card is displayed as either Active, Standby, or
Failed, proceed to the next step.
f.
Use the switchredcd command again to return the VXSM cards to their original states (active and
standby).
After this command has been executed, the originally active VXSM card is once again active and
the originally standby card is once again in standby. Both VXSM cards in the redundant pair have
upgraded boot code but with their original runtime code.
Step 3
Use the loadrev command to load the new runtime image onto the standby VXSM card. The format of
this command is:
loadrev <slot> <revision>
For slot, the user can enter either the slot number of the active or standby VXSM. PXM automatically
selects the standby to load the new image. For revision, use the revision number of the image to be loaded
(see later in this chapter for information on revision numbers).
Step 4
Periodically check that the loadrev process has ended. To do this use the dspcds or dsprev command on
the PXM. When the state of the VXSM card is displayed as either Active, Standby, or Failed, proceed to
the next step.
Step 5
Use the runrev command. This command causes the active card and the standby card to switch roles.
This results is the new runtime image becoming the active image. The new image is also loaded onto the
(now) standby card so that both cards have been upgraded. The format of the runrev command is:
runrev <slot> <revision>
Step 6
Both VXSM cards in the redundant set now have upgraded boot code images (if required) and runtime
images. Use the commitrev command to finalize the upgrade procedure. This command removes the old
images from the cards. The format of this command is:
commitrev <slot> <revision>
8-4
Cisco Voice Switch Services (VXSM) Configuration Guide and Command Reference for MGX Switches and Media Gateways, Release 5
Part Number OL-4625-01 Rev. E0, April 14, 2005
Chapter 8
Upgrading VXSM Code Images from a Previous Version
Initial Considerations
Note
If you suspect that some error has or is occurring during the upgrade process, use to abortrev command
to restore the images to their state before the upgrade was started.
Image Filenames and Revision Numbers
Images have both a filename and a revision number.
Filenames
Filenames are used to download the image to the PXM hard disk and when browsing the disc to examine
its contents. Filenames have the following formats.
cardtype_version-element{_platform}.fw
where version-element is composed of:
major-release.minor-release.maintenance.patch-phase
An example of a filename for VXSM 5.0.02 boot code is:
vxsm_005.000.002.200_bt.fw
An example of a filename for VXSM 5.0.02 runtime code is:
vxsm_005.000.002.202.fw
Revision Numbers
Revision numbers are used to identify images in the burnboot, loadrev, runrev, commitrev, and
abortrev commands. Revision numbers are derived from the filenames by:
•
Using only the version-element portion of the filename (cardtype, platform, and the.fw extension
are not used).
•
Removing the leading zeroes from the major/minor/maintenance/patch numbers.
•
Enclosing the maintenance.patch number in parentheses.
•
Adding a phase identifier to the end.
Thus, revision numbers have the general format:
major-release.minor-release(maintenance.patch)phase
Using this process, the filename vxsm_005.000.002.202.fw converts to the version number of
5.0(2.202)
Note
In this example the phase identifier is omitted because the image has been released. Phase identifiers are
used only for images that are still under development.
Note
A more detailed explanation of upgrading images, filenames, and revision numbers can be found in the
document entitled “Cisco MGX (PXM45/PXME1). MGX 9850, MGX 8830, and MGX 8880 Command
Reference” under the loadrev description.
Cisco Voice Switch Services (VXSM) Configuration Guide and Command Reference for MGX Switches and Media Gateways, Release 5
Part Number OL-4625-01 Rev. E0, April 14, 2005
8-5
Chapter 8
Upgrading VXSM Code Images from a Previous Version
Initial Considerations
CALEA and Non-CALEA Image Numbering
There is a special numbering relationship between a VXSM CALEA image and its corresponding
non-CALEA image. This relationship applies to both filenames and version numbers.
The relationship is as follows:
The value of the minor-release field for a non-CALEA release has the number “50” added to it to signify
the corresponding CALEA release.
For example, if the filename and revision number for a non-CALEA VXSM release ARE:
filename = vxsm_005.000.002.202.fw
revision number = 5.0(2.202)
The filename and revision number for the corresponding CALEA release would be:
filename = vxsm_005.050.002.202.fw
revision number = 5.50(2.202)
8-6
Cisco Voice Switch Services (VXSM) Configuration Guide and Command Reference for MGX Switches and Media Gateways, Release 5
Part Number OL-4625-01 Rev. E0, April 14, 2005