Table Of Contents
Release Notes for Cisco Voice Interworking Service Module Release 3.3.10
Table of Contents
About 3.3.10
About Release 3.3
Overview
New Features Introduced in Release 3.3
Changed Commands
Modified Command
Deleted Command
VISM Management Information Base
VISM Redundancy
VISM Call Rate
Compatibility
Limitations and Restrictions
Upgrade Procedures
Prerequisites
Check Domain Name Length
VISM/VISM-PR Upgrades with PXM1
VISM-PR Upgrades with PXM1E and PXM45
VISM/VISM-PR Downgrade Procedure
VISM to VISM-PR Hardware Upgrade
Caveats in Release 3.3.10
Resolved Caveats in Release 3.3.10
Open Caveats in Release 3.3.10
Caveats in Release 3.3
Resolved Caveats in Release 3.3
Open Caveats
Related Documentation
Obtaining Documentation
Cisco.com
Product Documentation DVD
Ordering Documentation
Documentation Feedback
Cisco Product Security Overview
Reporting Security Problems in Cisco Products
Obtaining Technical Assistance
Cisco Technical Support & Documentation Website
Submitting a Service Request
Definitions of Service Request Severity
Obtaining Additional Publications and Information
Release Notes for Cisco Voice Interworking Service Module Release 3.3.10
These release notes are Part Number OL-7098-01 Rev. C0, October 3, 2005.
The Voice Interworking Service Module (VISM) product is supported by MGX Voice Media Gateways. Refer to these release notes for Media Gateway and version level support guidelines.
The VISM/VISM-PR software release notes are supported by the Cisco Voice Interworking Services (VISM) Configuration Guide and Command Reference Release 3.3, which is available on cisco.com.
Table of Contents
About 3.3.10
The VISM/VISM-PR Release 3.3.10 is a maintenance release of Release 3.3 and contains no new features. For a list of the open and resolved caveats in this release, see "Caveats in Release 3.3.10" section.
About Release 3.3
The VISM/VISM-PR Release 3.3 is a new release. For a list of new features, see "New Features Introduced in Release 3.3" section. For a list of the open and resolved caveats this release, see "Caveats in Release 3.3" section.
Note 
The content of VISM Release 3.3 supersedes previous releases.
Overview
These release notes contain the following sections:
• "New Features Introduced in Release 3.3" section
• "VISM Management Information Base" section
• "VISM Redundancy" section
• "VISM Call Rate" section
• "Compatibility" section
• "Limitations and Restrictions" section
• "Upgrade Procedures" section
• "Caveats in Release 3.3.10" section
• "Caveats in Release 3.3" section
• "Related Documentation" section
• "Obtaining Documentation" section
• "Documentation Feedback" section
• "Cisco Product Security Overview" section
• "Obtaining Technical Assistance" section
• "Obtaining Additional Publications and Information" section
New Features Introduced in Release 3.3
VISM Release 3.3 is applicable to VISM and VISM-PR hardware. Table 1 summarizes the new features in VISM/VISM-PR Release 3.3.
Table 1 VISM/VISM-PR Release 3.3 Features
Feature
|
Summary
|
ATM Fax Relay
|
VISM-PR can transport fax over an ATM trunk using less bandwidth than fax pass through.
|
Filtering Traps
|
To reduce the load on CWM, you can filter the VISM-PR traps while the card is being configured.
|
VISM-PR Bulk Statistics Upload to CWM
|
You can upload history statistics data collected on a VISM-PR card to Cisco WAN Manager (CWM).
|
Display History Statistics
|
VISM and VISM-PR can collect history statistics.
|
Display All Static Configuration
|
On the VISM/VISM-PR card, you can use the dspall command to display static configurations, run-time statistics, and real-time dynamic data.
|
TDM Companding Law
|
VISM-PR supports non-standard law companding on the TDM interface.
|
G.729a Codec with 20 ms
|
VISM/VISM-PR cards contain a custom profile to support G.729a with 20 milliseconds (ms) packetization period.
|
Priority Bumping
|
On the VISM-PR card, you can set up high priority connections even if the available resources on the links are not enough to route the call.
|
Bearer IP Address Ping
|
On the VISM/VISM-PR card, you can ping both the controller traffic IP address and the bearer traffic IP address.
|
Call Throttling
|
VISM-PR card supports call throttling to maintain the stability of the card when the call rate exceeds the maximum allowable limit.
|
Changed Commands
This section contains the commands that have changed since Release 3.3.
Modified Command
The following command has been modified in Release 3.3.10:
dspcarddsp
The following example shows the new display parameters:
mgx-pxm45-24.1.6.VISM8.a > dspcarddsp
Adaptive Gain Control: off
Deleted Command
The following command has been deleted from Release 3.3.10:
cnfjtrinitdelay
To set the initial jitter delay for a specific codec, use the cnfcodecjtrdelay command.
VISM Management Information Base
VISM Release 3.3.10 uses Management Information Base (MIB) Version 53.
Load the MIBs available with MGX Release 1.3.11 located at the following URL: http://www.cisco.com/public/sw-center/wan/wan-planner.shtml
VISM MIBs are compatible with both PXM1-based and PXM1E/PXM45-based chassis.
Note The MIB version number was last updated in Release 3.3.0.
VISM Redundancy
Table 2 provides the support level for 1:N Service Module Redundancy (N = 1 through 11).
Table 2 Service Module Redundancy
Front Card Model Number
|
Redundancy Support
|
MGX-VISM-8T1
|
1:N redundancy (bulk mode support for T1 lines only).
|
MGX-VISM-8E1
|
1:N redundancy (bulk mode support for E1 lines only).
|
MGX-VISM-PR-8T1
|
1:N redundancy (bulk mode support for T1 lines only).
|
MGX-VISM-PR-8E1
|
1:N redundancy (bulk mode support for E1 lines only).
|
Note You can use a VISM-PR card as a redundant card for a VISM card, but a VISM card cannot be used as a redundant card for a VISM-PR card.
VISM/VISM-PR cards support bulk distribution using the SRM-3T3 and SRM-E (OC3) cards. In a redundancy configuration VISM/VISM-PR cards in bulk distribution mode do not require any back cards.
VISM Call Rate
Software Release 3.3.10 for VISM/VISM-PR handles 10 CAS, SS7, or PRI calls per second per VISM/VISM-PR card.
Compatibility
VISM/VISM-PR software interoperability with Cisco MGX 8230, Cisco MGX 8250, Cisco MGX 8830, and Cisco MGX 8850 (PXM1, PXM1E, PXM45) platform software is listed in Table 3.
Table 3 VISM/VISM-PR Software Interoperability
Product
|
Firmware
|
PXM1
|
1.3.11
1.2.23
1.2.13
|
PXM1E
|
5.0.20
5.0.10
4.0.17
3.0.25
|
PXM45
|
5.0.20
5.0.10
4.0.17
3.0.25
|
RPM-PR
|
12.3(7)T3
|
RPM-XF
|
12.3(7)T3
|
AXSM
|
5.0.20
5.0.10
|
Table 4 shows VISM and VISM-PR compatibility with the PXM controller cards.
Table 4 VISM/VISM-PR Compatibility with PXM Cards
| |
PXM1
|
PXM1E
|
PXM45 (A/B/C)
|
VISM
|
Yes
|
No
|
No
|
VISM-PR
|
Yes
|
Yes
|
Yes
|
Table 5 shows VISM and VISM-PR compatibility with the Cisco MGX chassis.
Table 5 VISM/VISM-PR Compatibility with Cisco MGX Chassis
| |
Cisco MGX 8230
|
Cisco MGX 8250
|
Cisco MGX 8830
|
Cisco MGX 8850 (PXM1)
|
Cisco MGX 8850
(PXM1E or PXM45)
|
Cisco MGX 8880 (PXM45)
|
VISM
|
Yes
|
Yes
|
No
|
Yes
|
No
|
No
|
VISM-PR
|
Yes
|
Yes
|
Yes
|
Yes
|
Yes
|
Yes
|
Table 6 describes the VISM/VISM-PR software interoperability with other Cisco products.
Table 6 VISM/VISM-PR Release 3.3.10 Interoperability with Other Cisco Products
Product
|
Latest Firmware
|
CWM
|
15.0 P3
|
BTS
|
4.4
4.2
3.5.4
|
PGW
|
9.5(2)
|
CISCO 2421
|
12.3(10a)
|
AS5400
|
12.3.9
|
AS5300
|
12.3.9 with vcware 11.32
|
Table 7 describes the software images available for Release 3.3.10 for VISM/VISM-PR.
Table 7 Software Images for VISM/VISM-PR Release 3.3.10
Product Name
|
Software Version
|
Firmware Image Name
|
Description
|
MGX-VISM-SW3310
|
003.003.010.200.FW
|
vism_8t1e1_003.003.010.200.fw
|
This image does not support the CALEA1 feature.
|
MGX-VISM-LISW3310
|
003.053.010.200.FW
|
vism_8t1e1_003.053.010.200.fw
|
This image supports the CALEA2 feature.
|
Table 8 describes the software boot code requirements for VISM/VISM-PR Release 3.3.10.
Table 8 VISM/VISM-PR Software 3.3.10 Boot Code Requirements
Board Pair
|
Boot Code Image Name
|
Boot Code Version
|
MGX-VISM-8T1
|
vism_8t1e1_VI8_BT_3.2.00.fw
|
VI8_BT_3.2.00
|
MGX-VISM-8E1
|
vism_8t1e1_VI8_BT_3.2.00.fw
|
VI8_BT_3.2.00
|
MGX-VISM-PR-8T1
|
vism_8t1e1_VI8_BT_3.2.00.fw
|
VI8_BT_3.2.00
|
MGX-VISM-PR-8E1
|
vism_8t1e1_VI8_BT_3.2.00.fw
|
VI8_BT_3.2.00
|
Note Loading this release of the backup boot code is required for existing VISM/VISM-PR cards not using this new release.
Limitations and Restrictions
The following limitations and restrictions are valid for software Release 3.3.10 for VISM/VISM-PR:
•If you are upgrading the VISM-PR image to Release 3.2.1x or later and the PXM1E or PXM45 image from Release 4.x or earlier to Release 5.x, first upgrade the VISM-PR cards. Then, upgrade the PXM1E or PXM45 cards in the same node.
Do not configure the new VISM features until you have fully upgraded the network. After you upgrade your network to PXM1E or PXM45 Release 5.x or later and VISM-PR to Release 3.2.1x or later, apply the standard upgrade process.
•Cisco recommends that you use the cnfcodecjtrdelay command to configure the fixed jitter-delay argument to 20 ms when using VISM 3.3.10.
•In a PNNI network, upspeeding SVC fax or modem calls requires an increase in bandwidth between the voice codec and the vbd codec. For fax calls to go through, you must disable policing.
•Switched AAL2 PVC mode is not recommended as this mode requires a meshed PVC network topology, which does not scale.
•The following commands are not supported:
–cnfmaxconfnum
–dspconferences
–dspmaxconfnum
•GR-303 is not supported for the LAPD commands.
•In AAL2 SVC mode, all active calls on the VISM cards are dropped upon PXM hard and soft switchover.
•For VISM-PR cards that are running on a PXM45 chassis, you can add connections to a maximum of 11 VISM-PR cards.
To add more cards and connections, you must enable the expanded memory option on the PXM45 card by using the cnfndparms (option 4) command.
•When configuring VoIP for modem or fax upspeed (passthrough), set the EventNegoPolicy parameter of the cnfvoiptransparams command to the value all.
This configuration is required for all related upspeed codecs to function correctly. An upspeed codec is defined as the codec that is switched to G.711a/u law, Clear Channel, or G.726.
•For a list of open issues and mitigations in VISM Release 3.3.10, see "Caveats in Release 3.3.10" section.
Upgrade Procedures
This section describes the following upgrade procedures:
• Prerequisites
• VISM/VISM-PR Upgrades with PXM1
• VISM-PR Upgrades with PXM1E and PXM45
• VISM/VISM-PR Downgrade Procedure
• VISM to VISM-PR Hardware Upgrade
VISM/VISM-PR Release 3.3.10 provides a procedure for the graceful upgrade (one in which the existing VISM/VISM-PR configuration is preserved throughout the upgrade procedure) from one of the following releases:
•From VISM 1.5(9) to VISM 3.3.10
•From VISM 2.1.1 to VISM 3.3.10
•From VISM 3.1(2) to VISM 3.3.10
•From VISM 3.1.3 to VISM 3.3.10
•From VISM 3.2.11 to VISM 3.3.10
•From VISM 3.3 to VISM 3.3.10
Prerequisites
To ensure that the VISM/VISM-PR configuration is preserved throughout the upgrade procedure, you must complete the prerequisites listed in this section.
Before starting the graceful upgrade procedure, complete the following prerequisites:
•Configure your MGX 8000 Series shelf with at least two VISM cards in a redundant configuration.
For more information on adding redundancy, refer to the add redundancy, addred, command in the Cisco MGX 8250, Cisco MGX 8230, and Cisco MGX 8850 PXM1-based Command Reference documentation and the Cisco MGX 8830 and Cisco MGX 8850 PXM1E/ PXM45-based Command Reference documentation.
•Ensure that the VISM cards are running at least Release 2.1, and the VISM-PR cards are running at least Release 3.0.
•Download software Release 3.3.10 for VISM/VISM-PR to the MGX 8000 Series shelf.
•If you are using the CALEA feature, ensure that you have the version of VISM/VISM-PR software that supports CALEA.
•Before you upgrade to 3.3.10, delete all domain names that are greater than 32 characters on the VISM/VISM-PR card. See the Check Domain Name Length section. After you complete the upgrade to 3.3.10, add the domain names that are greater than 32 characters.
Check Domain Name Length
Before you upgrade to 3.3.10, delete all domain names and domain name IPs that are greater than 32 characters on the VISM/VISM-PR card. After the upgrade, re-add the domain names and domain name IPs.
Complete the following steps.
Step 1 Log in to the VISM/VISM-PR card.
Step 2 Display the list of domain names by entering the dspdns command.
MGX1E.1.11.VISM8.a > dspdns
DomainNumber DomainName ResolutionType
------------ -------------- --------------
1 mga-SOLSYS1CA.234567890987654321234567890123456789.sol.cisco.com internalOnly
2 mga-SOLSYS1CA.234567890987654321234567890123456789.sol.cisco.dom internalOnly
3 mga-SOLSYS1CA.234567890987654321234567890123456789.sol.cisco.eom internalOnly
Step 3 For each domain number, count the number of characters in the DomainName field.
If the characters are greater than 32 for each domain number, go to Step 4.
Step 4 Check for the IP addresses associated with the domain names by entering the dspdnallips command.
MGX1E.1.11.VISM8.a > dspdnallips
ResolutionIndex DomainName IP State Pref
--------------- ------------ ------------ --------- -----
1 mga-SOLSYS1CA.234567890987654321234567890123456789.sol.cisco.com 10.1.3.25 Inactive 1
Step 5 If IP addresses are present, make a note of them in the order that they appear.
Step 6 Since you cannot delete the domain name or domain name IPs if MGCs exist, use the following commands to check for MGCs and delete them if they exist for each domain name:
a. Check for the MGC group protocols by entering the dspmgcgrpprotocols command.
MGX1E.1.11.VISM8.a > dspmgcgrpprotocols
MgcGrp Prot Qrntn Qrntn Sign Prov RspAck Disc Cancel
Num Num Persist Def OnOff Resp Attr Proc
Graceful
--------------------------------------------------------------------------------------
1 MGCP 1.0 Qrtn StepProcess DelNegEvt Send Send Enable Send
b. Check for MGC group entries by entering the dspmgcgrpparams command.
MGX1E.1.11.VISM8.a > dspmgcgrpparams
Mgc Grp Num Comm State State Chg Notification Priority
----------- ---------- ---------------------- --------
c. Check for MGC entries by entering the dspmgcs command.
MGX1E.1.11.VISM8.a > dspmgcs
1 mga-SOLSYS1CA.234567890987654321234567890123456789.sol.cisco.co
Step 7 If any entries exist for the domain name in Step 6 a. to Step 6 c., delete the MGC entries by entering the following commands as required:
•delmgcgrpprotocol
•delmggrpentry
•delmgc
Step 8 Delete the domain name IP address by entering the deldnip command.
Step 9 Delete the domain name by entering the deldn command.
Step 10 Perform the upgrade using the procedures in the "Upgrade VISM/VISM-PR Firmware with PXM1 Card" section or "Upgrade VISM-PR Firmware with PXM1E and PXM45 Cards" section.
Step 11 After you complete the upgrade, add the domain name entries, IP addresses, and MGCs as previously configured using the following commands:
•adddn
•adddnip
•addmgc
•addmgcgrpentry
•addmgcgrpprotocol
Step 12 To check that you added the entries successfully, use the display commands in Step 2 to Step 6.
VISM/VISM-PR Upgrades with PXM1
This section describes the procedures for upgrading VISM/VISM-PR software when the VISM/VISM-PR is used with a PXM1 card.
Download VISM/VISM-PR Boot Code and Firmware to PXM1
To download the VISM/VISM-PR boot code and firmware to the PXM1 card, use TFTP.
Step 1 Log in to your TFTP server.
Step 2 Download the bootcode and firmware images from the Cisco website.
Step 3 Download the selected revision of service module boot code into the service module.
a. tftp <node_name or IP address>
b. bin
c. put <backup boot> POPEYE@SM_1_0.BT
d. quit
Step 4 Download the selected firmware file.
a. tftp <node_name or IP address>
b. bin
c. To upgrade all VISM cards:
put <FW file> POPEYE@SM_1_0.FW
quit
d. To upgrade an individual VISM card:
put <FW file> POPEYE@SM_1_<slot number of card to upgrade>.FW
quit
Note Do not enter two put commands in the same TFTP session.
Step 5 Proceed to the "Upgrade VISM/VISM-PR Firmware with PXM1 Card" section to install the download.
Upgrade Boot Code with PXM1 Cards
Complete the following steps to upgrade the new backup boot code when you are using PXM1 cards in in a Cisco MGX 8230, Cisco MGX 8250, and Cisco MGX 8850 chassis:
Step 1 Log in to the active PXM1 card (slot 7 or 8 for Cisco MGX 8250 and Cisco MGX 8850 chassis; slot 1 or 2 for Cisco MGX 8230 and Cisco MGX 8830 chassis).
Note VISM/VISM-PR must be in the active state in order to update the VISM/VISM-PR boot code.
Step 2 Execute the PXM1 install command.
nodename.1.27.VISM8.a > install [bt] [sm <slot>] <version>
Caution Do not touch the VISM/VISM-PR card until the status comes back ('Sent xxx bytes in yyy seconds'). Failure to follow this recommendation corrupts the boot code, which cannot be recovered.
When the boot code is being written to PROM, you see comments displayed at the VISM/VISM-PR prompt. This behavior is normal and expected.
Step 3 Type the version command to verify the correct boot code.
Note Step 3 is optional.
Upgrade VISM/VISM-PR Firmware with PXM1 Card
Software Release 3.3.10 is for VISM and VISM-PR cards. Ensure that the VISM and VISM-PR cards have the minimum boot code version of vism_8t1e1_VI8_BT_3.2.00.fw.
The following versions of VISM software Release 3.3.10 are available:
•003.003.010.200.FW—without CALEA
•003.053.010.200.FW—with CALEA
In this procedure the following conditions apply:
•If two VISM or VISM-PR cards are part of a redundancy group, initially the primary card is in the active state, and the secondary card is in the standby state.
•Old-rev refers to the firmware, Release 3.2 and prior.
•New-rev refers to the firmware after the upgrade, Release 3.3.10.
Perform the firmware upgrade on the VISM or VISM-PR cards. Do not remove the VISM cards and replace them with VISM-PR cards at this time.
Step 1 Log in to the active PXM1 card (slot 7 or 8 for Cisco MGX 8250 and Cisco MGX 8850 chassis; slot 1 or 2 for Cisco MGX 8230 and Cisco MGX 8830 chassis).
Step 2 Save the existing configuration as a contingency plan by entering:
nodename.1.8.PXM.a > savesmcnf <SM slot#>
This command saves the existing configuration in the C:CNF directory. This file can be used during the downgrade procedure.
Step 3 To obtain the correct version of VISM/VISM-PR firmware, enter the dspfwrevs command.
nodename.1.8.PXM.a > dspfwrevs
Card Type Date Time Size Version File Name
----------- ------------------- -------- -------------------------------------
VISM-8T1E1 04/26/2004 20:06:04 248688 VI8_BT_3.2.00 sm150.bt
PXM1 01/04/2004 08:19:52 2602836 1.2.11 pxm_1.2.11.fw
PXM1 01/04/2004 11:03:02 2620132 1.2.21 pxm_1.2.21.fw
VISM-8T1E1 09/10/2004 16:22:32 4135208 003.003.000.200 sm150_12.fw
VISM-8T1E1 09/10/2004 15:37:52 4077560 003.002.010.200 sm150.fw
VISM-8T1E1 06/16/2004 13:29:38 3863768 003.051.002.000 sm150_11.fw
PXM1 01/04/2004 11:01:56 1346844 1.2.21 pxm_bkup_1.2.21.fw
VISM-8T1E1 03/08/2004 08:20:16 4037880 003.002.000.000 sm150_3.fw
VISM-8T1E1 03/08/2004 08:19:44 248688 VI8_BT_3.2.00 sm150_3.bt
PXM1 01/04/2004 07:58:44 1345328 1.2.11 pxm_bkup_1.2.11.fw
VISM-8T1E1 01/07/2004 23:33:02 3863768 003.051.002.000 sm150_2.fw
VISM-8T1E1 03/08/2004 08:21:12 248688 VI8_BT_3.2.00 sm150_4.bt
VISM-8T1E1 04/26/2004 19:59:52 4037880 003.002.000.000 sm150_1.fw
VISM-8T1E1 03/08/2004 08:20:58 4037880 003.002.000.000 sm150_4.fw
Step 4 Execute the PXM install command.
nodename.1.8.PXM.a > install sm <SM slot#> <new-rev>
Replace <SM slot#> with the slot number of the primary VISM or VISM-PR card.
Replace <new-rev > with the version of the new firmware (for example, 003.003.010.200.FW).
Caution Ensure that you perform
Step 4. If you do not perform
Step 4, the boot code is corrupted and not recoverable.
This command causes the secondary VISM or VISM-PR card to reset and come up in the standby state, running the new-rev firmware. The primary VISM or VISM-PR card is unaffected by this command.
Step 5 Execute the PXM newrev command.
nodename.1.8.PXM.a > newrev sm <SM slot#> <new-rev>
Replace <SM slot#> with the slot number of the primary VISM or VISM-PR card.
Replace <new-rev> with the version of the new firmware.
This command causes the primary VISM or VISM-PR card to reset. The secondary VISM or VISM-PR card becomes active and is running the new-rev firmware.
Step 6 Execute the PXM commit command.
nodename.1.8.PXM.a > commit sm <SM slot#> <new-rev>
Replace <SM slot#> with the slot number of the primary VISM or VISM-PR card.
Replace <new-rev> with the version of the new firmware.
The two VISM or VISM-PR cards are now back to their original condition except that both cards are now running the new-rev firmware.
Step 7 Log in to the active VISM or VISM-PR card and use the display commands (for example, dspendpts, dspcasvar, and so forth) to confirm that the configuration has been preserved through the upgrade process.
Note For more than one primary VISM or VISM-PR card in a redundancy group, ensure that the secondary card is in the standby state and repeat Step 5 and Step 6 for each VISM/VISM-PR card in the redundancy group.
Step 8 Perform the following verifications:
•Make minor modifications to the configuration.
•Check that the changes have been executed correctly.
•Change the configuration back again.
Note If the VISM or VISM-PR card is not part of a redundancy group, complete Step 1 to Step 4.
VISM-PR Upgrades with PXM1E and PXM45
This section describes the procedures for upgrading VISM-PR software when the VISM-PR is used with a PXM1E or PXM45 card.
If you are upgrading the VISM-PR image to Release 3.2.1x or later and the PXM1E or PXM45 image from Release 4.x or earlier to Release 5.x, first upgrade the VISM-PR cards. Then, upgrade the PXM1E or PXM45 cards in the same node.
Do not configure the new VISM features until you have fully upgraded the network. After you upgrade your network to PXM1E or PXM45 Release 5.x or later and VISM-PR to Release 3.2.1x or later, apply the standard upgrade process.
Download VISM-PR Boot Code and Firmware to PXM1E and PXM45
To download the VISM-PR boot code and firmware to the PXM1E or PXM45 card, use FTP.
Step 1 Access the images on the Cisco Web site.
Step 2 To download the images, enter the ftp command.
ftp node-ip
where node-ip is the IP address of the node to which you want to download the image.
Step 3 Enter your user name and password.
Step 4 Enter bin.
Step 5 Access the appropriate directory.
cd C:FW
Step 6 Download the images to your C:FW directory.
a. To download one file at a time, use the put image-version command.
b. To download multiple files at the same time, use the mput <image-version> <image-version> command.
where image-version is the downloaded image from Step 1.
Step 7 To exit the download procedure, enter bye.
Upgrade Boot Code with PXM1E and PXM45 Cards
Complete the following steps to upgrade the new backup boot code when you are using PXM1E or PXM45 cards in your MGX 8000 Series chassis:
Step 1 Complete the steps in Download VISM-PR Boot Code and Firmware to PXM1E and PXM45.
Step 2 Log in to the active PXM1E or PXM45 card.
Step 3 To upgrade the VISM-PR boot, enter the burnboot command.
nodename.1.7.PXM.a > burnboot <slot> <revision>
Replace <slot> with the number of the VISM-PR card that you want to upgrade.
Replace <revision> with the version of the bootcode you downloaded from Step 1.
The following example shows the burnboot.
nodename.1.7.PXM.a > burnboot 12 3.2(0.0)
The card in slot 12 will be reset.
burnboot:Do you want to proceed (Yes/No)? yes
For VISM-PR cards without redundancy, the card automatically resets and becomes active with the latest boot code image.
For VISM-PR cards with redundancy, the active card takes approximately 60 seconds to reset as standby. For the original standby card, complete Step 2- Step 3. This card now resets back to standby, and the standby card is now active.
Upgrade VISM-PR Firmware with PXM1E and PXM45 Cards
Ensure that the VISM-PR cards have the minimum boot code version of vism_8t1e1_VI8_BT_3.2.00.fw.
The following versions of VISM-PR software Release 3.3.10 are available:
•003.003.010.200.FW—without CALEA
•003.053.010.200.FW—with CALEA
Perform the firmware upgrade on the VISM-PR cards.
Step 1 Log in to the active PXM1E or PXM45 card.
Step 2 Ensure that the card is in the redundant mode, where the active card is the primary card.
Step 3 To save the existing configuration as a contingency plan, enter the saveallcnf command.
nodename.1.7.PXM.a > saveallcnf
Step 4 To load the new software, enter the loadrev command.
nodename.1.7.PXM.a > loadrev <sm-primary-slot-num> <new-rev>
Replace <sm-primary-slot-num> with the slot number of the VISM-PR card on which you want to install the new software.
Replace <new-rev> with the new firmware version number for the VISM-PR software.
Caution Temporary traffic loss occurs.
Step 5 Ensure that the redundant card is returned to the standby state by executing the dspcds command.
Note You must wait for the redundant card to return to the standby state. If you issue the runrev command too early, an error message is generated. The rev change does not occur.
Step 6 To execute the download, enter the runrev command.
nodename.1.7.PXM.a > runrev <sm-primary-slot-num> <new-rev>
Replace <sm-primary-slot-num> with the slot number of the VISM-PR card on which you want to install the new software.
Replace <new-rev> with the new firmware version number for the VISM-PR software.
Caution Temporary traffic loss occurs.
Step 7 Ensure that the primary slot completes booting and goes into the standby state by executing the dspcds command.
Note You must wait for the primary slot to finish booting and get to standby state. Issuing the commitrev command early might be accepted without an error. However, the active and standby cards might not be swapped back to their original state. For example, the original primary card might be left in standby, and the original redundant card might be left as active.
Step 8 To commit the new download to the VISM-PR card, enter the commitrev command.
nodename.1.7.PXM.a > commitrev <sm-primary-slot-num> <new-rev>
Replace <sm-primary-slot-num> with the slot number of the VISM-PR card on which you want to install the new software.
Replace <new-rev> with the new firmware version number for the VISM-PR software.
The commitrev command switches the primary card from a standby state to an active state and the redundant card from an active state back to a standby state.
Step 9 To verify the card states, execute the dspcds command.
VISM/VISM-PR Downgrade Procedure
Use this procedure to downgrade VISM/VISM-PR software from software Release 3.3.10 to an earlier VISM/VISM-PR release. By following the downgrade procedure described here, the configurations are retained after the downgrade.
Note The configurations that existed with old-rev firmware should have been saved earlier. You cannot downgrade from VISM-PR to VISM.
Complete the following steps to downgrade the VISM/VISM-PR software:
Step 1 If the VISM/VISM-PR card is in a redundancy group, remove the redundancy.
nodename.1.7.PXM.a > delred <SM slot#>
Step 2 Download the old-rev firmware onto the MGX shelf.
Step 3 Execute the PXM clrsmcnf command:
nodename.1.7.PXM.a > clrsmcnf <SM slot#>
Replace <SM slot#> with the slot number of the VISM/VISM-PR card to be downgraded.
Wait for the card to become active. The VISM/VISM-PR card resets after you execute this command.
Step 4 Execute the PXM restoresmcnf command:
Caution The
restoreallcnf command reconfigures all of the cards in the chassis.
nodename.1.7.PXM.a > restoresmcnf -f <filename> -s <SM slot#>
Replace <filename> with the name of the old configuration file that was saved while the old-rev firmware was running. The file can be found in the C:CNF directory on the MGX shelf.
Replace <SM slot#> with the slot number of the VISM/VISM-PR card to be downgraded.
The VISM/VISM-PR card resets again. The card becomes active, running the old-rev firmware with the old configuration.
Note For PXM1E/PXM45 cards, you cannot restore the configuration for an individual VISM-PR service module. You can save and restore the configuration of all cards in a chassis using the saveallcnf and restoreallcnf commands.
Step 5 Reconfigure the redundancy group, if required.
VISM to VISM-PR Hardware Upgrade
Complete the following steps to upgrade your system from VISM cards to VISM-PR cards.
Caution You must install the redundant (standby) VISM-PR card first. Failure to follow this recommendation results in traffic loss. In addition, do not remove an active VISM card from your chassis. Ensure that you configure an active VISM card to the standby state before you remove it and replace it with a VISM-PR card.
Step 1 Remove the redundant (standby) VISM card from your chassis.
Step 2 Install a VISM-PR card in the slot you removed the VISM card from in Step 1.
Step 3 Administratively configure the VISM-PR card you installed in Step 2 as primary (active).
Step 4 Remove the now redundant VISM card from your chassis.
Step 5 Install a VISM-PR card in the slot you removed the VISM card from in Step 4.
Step 6 Log in to the redundant (secondary) VISM-PR card and execute the dspcd command. Verify that the output from the dspcd command lists the card type under FunctionModuleType as a VISM-PR card. If the card type still indicates the VISM card, execute the resetcd slot-num command from the PXM and repeat the dspcd command to ensure that the correct card type is shown.
Step 7 Log in to the active VISM-PR card and execute the dspcd command. Verify that the output from the dspcd command lists the card type under FunctionModuleType as a VISM-PR card.
If the card type still indicates the VISM card, execute the resetcd slot-num command from the PXM. Repeat the dspcd command to ensure that the correct card type is shown.
Step 8 If you have no other VISM cards in your chassis, you have completed the hardware upgrade procedure; do not proceed to Step 9. If you have more VISM cards in your chassis, proceed to Step 9.
Step 9 Remove a standby VISM card from your chassis.
Step 10 Install a VISM-PR card in the slot you removed the VISM card from in Step 9.
Step 11 Repeat Step 9 and Step 10 to remove any remaining VISM cards in your chassis and replace them with VISM-PR cards.
Step 12 Repeat Step 6 and Step 7 on the remaining VISM-PR cards to insure the correct card type is shown.
Caveats in Release 3.3.10
This section describes the resolved and open caveats in VISM/VISM-PR Release 3.3.10. Caveats describe unexpected behavior or defects in VISM/VISM-PR software.
Resolved Caveats in Release 3.3.10
Table 9 describes the caveats that have been resolved in VISM/VISM-PR Release 3.3.10.
Table 9 Resolved Caveats in VISM/VISM-PR Release 3.3.10
DDTS Issue
|
Description
|
CSCed60487
|
CLI dspcids does not reflect correct state of the CID
|
CSCee03716
|
DTMF Relay: missing digits in VoIP switching mode
|
CSCee37537
|
VISM-PR responses to AUEP 502 failed to allocate tuple sometimes
|
CSCef03116
|
Fax passthrough fails with AAL2 Trunking, E1 PRI
|
CSCef03134
|
Low uplink rate on modem passthrough with AAL2 Trunking, E1-PRI
|
CSCef10041
|
VISM sending AIS twice upon detection from line side
|
CSCef26476
|
VISM CLI dsplnendptstatus does not reflect correct ECAN value
|
CSCef39465
|
HEC errors, invalid OSF cells on all VISM connections
|
CSCef54851
|
Connection parameter mismatch with cnfcon CLI command
|
CSCef61454
|
Display connection database discrepancy
|
CSCef69692
|
SNMP mibwalk stuck in loop when configuration has multiple PVCs
|
CSCef70885
|
Some client modems failed to upspeed to the configured VBD codec
|
CSCef80412
|
Timestamp discrepancy between PXM1 and VISM-PR
|
CSCef81423
|
BTS VoIP Switch T1 CAS 15 cps load causes card resets
|
CSCef82038
|
One way traffic on VISM-PR-8E1 for VoIP
|
CSCef97639
|
G.729 20 ms codec not supported in template 5 AAL2 Trunking
|
CSCeg01767
|
VISM prints debug messages after executing any gain/att CLI
|
CSCeg02863
|
Need to remove lossless codec from rtpcons—not supported
|
CSCeg06965
|
VISM should handle ICMP traffic gracefully
|
CSCeg09338
|
CLI output of dspcons command on VISM needs correcting
|
CSCeg12913
|
VISM rejects the a=sendrecv SDP when using image/t38 codec
|
CSCeg18984
|
VISM SCPU is crashed/frozen VoIP implementation
|
CSCeg24368
|
cnfjtrinitdelay can silently fail to set codec jitter delay
|
CSCeg27900
|
After FAX call, VISM sends voice packets when remote TDM alarm
|
CSCeg29149
|
printf should only be called when debug flag is set on VISM
|
CSCeg33271
|
Modem call failed to upspeed/downspeed
|
CSCeg33898
|
VISM card stuck in boot state after issuing ccTraceDump
|
CSCeg36000
|
VISM response 200 OK to CRCX but never really create a connection
|
CSCeg45224
|
PVC switchover broken in 3.2.11
|
CSCeg47932
|
64 character VISM domain name causes VISM card to hang
|
CSCeg49706
|
SGCP incorrect order crashes VISM
|
CSCeg55292
|
Setting timestamp ON w adaptive jtrmode resets jtrmode to fixed
|
CSCin79200
|
Fax Tx is successful using pt when Org-fxlco=pt and Trm-fxlco=gw
|
CSCin79878
|
VAD is not turned back to ON after a fax transmission in VISM
|
CSCin84813
|
VISM-PR card resets on bulk trap addition
|
CSCin87238
|
AAL2 fax passthrough fails for multiple fax calls
|
Open Caveats in Release 3.3.10
Table 10 describes the open caveats in VISM/VISM-PR Release 3.3.10 as of October 3, 2005.
Table 10 Open Caveats in VISM/VISM-PR Release 3.3.10
DDTS Issue
|
Description
|
CSCef12950
|
Symptom: VISM does not disable the ECAN when the codec used is Clear Channel.
Conditions: This symptom occurs when Clear Channel is set as the upspeed codec for fax/modem calls. In addition, this occurs when Clear Channel is used as a voice codec and if ECAN is enabled during call setup.
Workaround: Do not enable the ECAN through the MGCP, if the codec to be used is Clear Channel. VISM does not reject the MGCP command if ECAN is turned on and the preferred codec is Clear Channel.
|
CSCeg25307
|
Symptom: Increasing the jitter buffer has no effect in one-way delay.
Conditions: No significant change on one way delay was observed with fixed jitter buffer settings between 60 ms and 100 ms. The expected behavior is that increasing the jitter buffer would also increase the one-way delay value. Tests were performed in AAL2 Trunking mode.
Workaround: None.
|
CSCeg61617
|
Symptom: VISM crashes hours after running PRI backhaul load.
Conditions: While running PRI backhaul load on a fully loaded VISM-PR, the card would reset after running between 12-80 hours.
Workaround: The problem is fixed in VISM Patch Release 3.3.0.202. If you are running PRI backhaul load on VISM-PR, it is recommended that you upgrade to this patch release.
Contact Cisco TAC to obtain VISM Patch Release 3.3.0.202.
|
CSCeg82063
|
Symptom: VISM is not passing packets even if received at the ATM level as shown with the dspsarcnt command.
On the contrary dsprtpconnstat does not show any RTP packets received or rejected.
Conditions:
1. VISM should run 3.2(11.202) or above.
2. The CPE should use a different UDP port as source form the UDP, one used as destination. Code 3.2(11.202) introduced this check for security reasons.
Workaround: Revert back to 3.1.
|
CSCeg85887
|
Symptom: Card resets when running T.38 load in template 4.
Conditions: When configured to template 4, VISM DSPs crash if running T.38 GW mode load.
Workaround: Configure the VISM card to template 3, which supports T.38 fax relay.
|
CSCeg86053
|
Symptom: In 3.3.10 release, when using ATM fax relay feature, VISM checks for at least 200 cps to be available before it can upspeed the CID to fax relay mode.
However, VISM utilizes only 50 cps once in fax relay mode, which might cause the codecs on both sides to go into a mismatch and have voice quality issues.
Conditions: This affects fax calls on VISM when using template 3 in AAL2 trunking mode. The configured bandwidth is lesser than that used by fax passthrough.
Workaround:
1. Configure the PVC with extra bandwidth of 140 cps, which allows the fax calls on VISM to upspeed to fax relay mode.
2. Disable the ATM fax relay feature.
|
CSCeg86125
|
Symptom: When VISM is working with Arris MTAs through DTMF relay and the DTMF digits duration is no more than 50 ms, Arris MTA fails to outpulse the digits correctly. MTAs from other vendors work fine.
Conditions: This only happens to Arris MTAs when the DTMF digits are less than or equal to 50 ms. For digits longer than 50 ms, it works fine.
Workaround: None.
|
CSCeh35201
|
Symptom: VISM crash with E1 CCS load. ATMizier not responding.
Conditions: This reset happens in AAL2 Trunking mode with CCS channels that are configured with signaling PVCs.
Workaround: Do not configure CCS channels with signaling PVCs. Use Clear Channel codec with bearer PVCs to transport signaling.
|
CSCeh36322
|
Symptom: Six extra packets cause metallic voice.
When 6 out-of-order RTP packets are received, PSTN side hears robotized voice with the following configuration:
•dejitter buffer mode: fixed without timestamp
•initial delay: 20 ms
•codec: G.711A
•packetization period: 20 ms
Conditions: This problem happens in fixed without timestamp dejitter mode and the above specific configuration.
This issue does not happen when less than or more than 6 packets are received.
This issue is cleared by another extra packet being added or one packet being dropped.
Workaround: Use fixed with timestamp dejitter buffer mode.
|
CSCeh47379
|
Symptom: CCS AAL2 Trunking load of 200 V.110 calls cause reset.
VISM-E1/VISM-PR-E1 cards might intermittently reset. For a non-redundant configuration, the card resets and comes back active. If redundancy is configured, the card fails over to a redundant card. PXM log shows reset reason as "Watchdog Timeout".
Conditions: VISM-E1/VISM-PR-E1 might intermittently reset if all of the following conditions are met:
1. Card is configured for AAL2 Trunking mode.
2. Statistics upload feature for VISM-E1/VISM-PR-E1 is enabled, including CID statistics. By default, statistics upload feature is disabled.
3. VISM-E1/VISM-PR-E1 has 200 or more CIDS configured.
Workaround: One of the following workarounds can be applied, depending on the customer's requirements related to statistics upload to minimize an impact to their statistics upload capability.
1. Disable statistics upload feature all together for all narrow band service module (NBSM) cards.
2. Enable statistics upload feature only for other NBSMs only.
3. Enable statistics upload feature for VISM-E1/VISM-PR-E1, but only for PVC and/or line statistics (no CID statistics enabled).
|
CSCej16082
|
Symptom: Voice quality issue might be experienced on connections that are finished with a ATM fax relay call.
Conditions: This issue occurs with VISM software upgrades from older releases to 3.3.10 and with the codec template configured as 3 or 4.
Workaround: Disable ATM fax relay.
|
CSCej24398
|
Symptom: The dsplns command shows the configured line, but the dspln <line_number> command indicates that the line is not configured or does not exist.
Conditions: This issue is caused by a corrupted database.
Workaround: Delete the line and then add the line.
|
CSCej24487
|
Symptom: Accepted connection and rejected connection counters of a PVC cannot be cleared.
Conditions: None.
Workaround: None.
|
CSCej29886
|
Symptom: The pinglndsp command might cause the DSP to fail and cause dead air on a voice connection.
Conditions: Not applicable.
Workaround: Do not use pinglndsp command.
|
Caveats in Release 3.3
This section describes the resolved and open software caveats in VISM/VISM-PR Release 3.3.
Resolved Caveats in Release 3.3
Table 11 describes the caveats that have been resolved in VISM/VISM-PR Release 3.3.
Table 11 Resolved Caveats in VISM/VISM-PR Release 3.3
DDTS Issue
|
Description
|
CSCed10672
|
VISM supports 217 AAL2 SVC calls on VISM-PR-E1 only.
|
CSCed43103
|
VISM should not send any P2P messages in Alarm mode.
|
CSCed43668
|
Display of AIS delay time should display remaining time also.
|
CSCed66304
|
Video conference freezing under mixed traffic condition.
|
CSCed74024
|
T.38 CA controlled mode calls fail after successful initial run.
|
CSCed83124
|
CIDs oos while adding when the con is down even enough bandwidth is available.
|
CSCed84289
|
Wrong encoding of bits type in ABCD incoming and outgoing pattern.
|
CSCed85909
|
Proper error message should be thrown if Channel Modification not possible.
|
CSCed86492
|
VISM does not send busybearercode on random endpts with bulk ATM alarms.
|
CSCed86763
|
MIB gets set to none no matter which value is set.
|
CSCed87750
|
Line alarms with restoration of ATM trunks.
|
CSCed88798
|
During VISM line alarm VISM sends voice packets to network.
|
CSCed88838
|
Implement OAM CC cells transmission on VISM.
|
CSCed89176
|
Walk on rsvpIfRefreshInterval does not work.
|
CSCed89221
|
JitterInitialDelay cannot be SET to non-multiples of 5 for lossless.
|
CSCed91157
|
Wrong Transtbl is associated with DSX0 though returns failure.
|
CSCed92129
|
Adding CIDs on the second PVC puts all the CIDs oos.
|
CSCed92165
|
CID stays in fail state even after LOS got cleared.
|
CSCed95335
|
AAL2 Trunking - cnfcodectmpl does not check for CIDs codec types.
|
CSCee03210
|
T38 interop fails between VISM and 2421.
|
CSCee07416
|
No trap is sent when only BearerBusyC |
