Cisco Cisco MGX 8880 Media Gateway Notas de publicación
5
Release Notes for Cisco Voice Switch Service Module (VXSM) Release 5.6.10
OL-23364-03
Upgrading from an Earlier VXSM Release
The CALEA image supports LI based on SII architecture for H.248, TGCP and MGCP protocols. The
PktCable CALEA is supported only with MGCP and TGCP protocols.
PktCable CALEA is supported only with MGCP and TGCP protocols.
VXSM supports four different Codec templates; Tandem Gateway (TGW), Tandem Gateway 2, Fixed
Mobile Convergence (FMC), and Cable. The Cable template can be used only in conjunction with TGCP.
Mobile Convergence (FMC), and Cable. The Cable template can be used only in conjunction with TGCP.
Upgrading from an Earlier VXSM Release
VXSM can be gracefully upgraded (configuration is preserved) from VXSM Release 5.5.00 or later.
Note
VXSM supports upgrade of non-CALEA to CALEA firmware. But upgrade from CALEA to
non-CALEA is not supported.
non-CALEA is not supported.
When loading or upgrading a boot or runtime image to a VXSM card, users must observe the following
caution:
caution:
Caution
If an H.248 association is active with SrvChgProfile (used in service change message) as BT_TGW in
5.3.x.x release, after graceful upgrade to 5.6.10, the association will continue to use BT_TGW, but new
association(s) cannot be added with SrvChgProfile as BT_TGW.
5.3.x.x release, after graceful upgrade to 5.6.10, the association will continue to use BT_TGW, but new
association(s) cannot be added with SrvChgProfile as BT_TGW.
From the 5.4.00 release onward, the BT_TGW SrvChgProfile is no longer available. All new
associations must be added using either etsi_tgw or CISCO_TGW.
associations must be added using either etsi_tgw or CISCO_TGW.
Prior to upgrade, user should confirm that additional termtypes (other than the defaults) have not been
configured for VXSM in H.248.
configured for VXSM in H.248.
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 particular:
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.