Table Of Contents
Release Notes for Cisco Voice Interworking Service Module Release 3.3.25
Table of Contents
About Release 3.3.25
About Release 3.3.20
About Release 3.3.10
About Release 3.3
Overview
New Features Introduced in Release 3.3.25
SPVC Capacity Expansion
VISM-PR Alarm Events Reported in the MGX Log File
Configurable Loopback Cell Priority
History Statistics Enhancement
VISM Management Information Base
VISM Redundancy
VISM Call Rate
Compatibility
Limitations and Restrictions
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
Caveats in Release 3.3.25
Resolved Caveats in Release 3.3.25
Open Caveats in Release 3.3.25
Caveats in Release 3.3.20
Resolved Caveats in Release 3.3.20
Open Caveats in Release 3.3.20
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.25
These release notes are Part Number OL-8428-01 Rev. A0, November 21, 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 Release 3.3.25
VISM/VISM-PR Release 3.3.25 is a maintenance release of Release 3.3.20 and contains new features for VISM-PR. For a description of these features, see the "New Features Introduced in Release 3.3.25" section.
For a list of the resolved caveats in this release, see the "Resolved Caveats in Release 3.3.25" section.
About Release 3.3.20
VISM/VISM-PR Release 3.3.20 is a maintenance release of Release 3.3 and contains the following new features:
•
1560/980 Hz modem tones
•VQT statistics
•V.110
Note For a description of these features, refer to the Cisco Voice Interworking Services (VISM) Configuration Guide and Command Reference, Release 3.3.
For a list of the open and resolved caveats in this release, see the "Caveats in Release 3.3.20" section.
About Release 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
VISM/VISM-PR Release 3.3 is a new release. Table 1 summarizes the new features in VISM/VISM-PR Release 3.3.
Note For a description of these features, refer to the Cisco Voice Interworking Services (VISM) Configuration Guide and Command Reference, 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.
|
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.25" 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.25" section
• "Caveats in Release 3.3.20" 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.25
This section contains the description of the following new features:
• "SPVC Capacity Expansion" section
• "VISM-PR Alarm Events Reported in the MGX Log File" section
• "Configurable Loopback Cell Priority" section
• "History Statistics Enhancement" section
SPVC Capacity Expansion
In this release, you can now configure a maximum of 248 PVCs on a VISM-PR-8E1 card and a maximum of 192 PVCs on a VISM-PR-8T1 card. The cards must be running in the AAL2 trunking mode.
Prior to Release 3.3.25, you could configure a maximum of 64 PVCs on a VISM-PR card.
With the increase in SPVC capacity now supported, you have the option of assigning each DS0 to a separate PVC.
VISM-PR Alarm Events Reported in the MGX Log File
Prior to Release 3.3.25, VISM-PR reported the Receive Line alarms to the PXM log file.
In Release 3.3.25, in addition to the Receive Line alarms, VISM-PR reports the following alarms in the PXM log file:
•Transmitted Line alarms
•Transmitted and Received PVC alarms
•Transmitted and Received Ds0 alarms
The reporting of these alarms is applicable to all of the VISM-PR modes.
The following new commands support this feature:
• cnflnalmlog
• cnfpvcalmlog
• cnfallalmlog
• dspalmlog
By default, the alarm log is disabled on all the lines, and the timer is set to 0.
cnflnalmlog
To enable or disable the reporting of VISM-PR line alarms to the PXM log file, use the cnflnalmlog command.
nodename.1.27.VISM8.a > cnflnalmlog <line_number> <logEnab> |LogTimer|
Replace the above arguments with the values listed in Table 2.
Table 2 Parameters for cnflnalmlog Command
Parameter
|
Description
|
line_number
|
Line number for which you want to enable or disable the DS0 alarm reporting.
|
logEnab
|
Value you can use to enable or disable the logging of VISM-PR line alarms to the PXM alarm log.
•1 = Enable
•2 = Disable
|
|LogTimer|
|
(Optional) Number of minutes for which you want the line alarms to be reported to the PXM log file. The maximum time is 7200 minutes (5 days).
|
In the following example, DS0-based alarm logging is enabled on line 1 for 1440 minutes (1 day):
nodename.1.27.VISM8.a > cnflnalmlog 1 1 1440
nodename.1.27.VISM8.a >
cnfpvcalmlog
To enable or disable the reporting of the alarms for all of the PVCs on a VISM-PR card to the PXM log file, use the cnfpvcalmlog command.
nodename.1.27.VISM8.a > cnfpvcalmlog <logEnab> <LogTimer>
Replace the above arguments with the values listed in Table 3.
Table 3 Parameters for cnfpvcalmlog Command
Parameter
|
Description
|
logEnab
|
Value you can use to enable or disable the alarm reporting for all of the PVCs on a VISM-PR card.
•1 = Enable
•2 = Disable
|
|LogTimer|
|
(Optional) Number of minutes for which you want the PVC alarms to be reported to the PXM log file. The maximum time is 7200 minutes (5 days).
|
In the following example, alarm logging for all PVCs is enabled on line 1440 minutes (1 day):
nodename.1.27.VISM8.a > cnfpvcalmlog 1 1440
nodename.1.27.VISM8.a >
cnfallalmlog
To enable or disable the reporting of alarms on all of the lines and PVCs to the PXM log file, use the cnfallalmlog command. The default reporting time is 7200 minutes (5 days).
nodename.1.27.VISM8.a > cnfallalmlog <logEnab>
Replace the <logEnab> argument with one of the following values to enable or disable the alarm reporting for all of the lines and PVCs on the VISM-PR card:
•1 = Enable
•2 = Disable
In the following example, alarm logging for all of the lines and PVCs on a VISM-PR card is enabled.
nodename.1.27.VISM8.a > cnfallalmlog 1
nodename.1.27.VISM8.a >
This command is valid when all of the lines on the card are enabled.
dspalmlog
To display the current settings for reporting VISM-PR line and PVC alarms to the PXM log file, use the dspalmlog command.
nodename.1.27.VISM8.a > dspalmlog
In the following example, the line and PVC alarm reporting settings are displayed:
8850.1.1.VISM8.a > dspalmlog
Detailed PVC Alarms to Log: Enabled
-----------------------------------
Alarm Time Configured(minutes) Alarm Time Left(minutes)
============================== ================================
7200 7200
Detailed Line Alarms to Log
-----------------------------
Line Number Timer Configured(minutes) Time Left(minutes)
========== =============================== ========================
1 1440 1440
2 7200 7198
3 Disabled
4 Disabled
5 Disabled
6 Disabled
7 Disabled
8 Disabled
Configurable Loopback Cell Priority
The ATM OAM loopback cell is used to monitor the end to end connectivity of the PVC in an ATM network.The cell loss priority (CLP) bit in the ATM header is used to set the priority of the cell. A cell with CLP set to 0 has higher priority compared to a cell with CLP set to 1. During traffic congestion events, the lower priority cells are eligible first for discard.
The ATM OAM loopback cells in the VISM-PR card have the cell loss priority (CLP) bit set to 1 by default. These cells can be discarded during traffic congestion even though the class of service is configured to be constant bit rate (CBR). This discard can cause the SPVCs to go into alarm as a result of an OAM loopback timeout, which could result in the dropping of all calls on the SPVCs.
In Release 3.3.25, you can set the CLP bit of an OAM loopback cell to 0 on a VISM-PR card. This setting is propagated across the network to preserve the calls during traffic congestion.
CLP bit configuration is applicable to the OAM loopback cells in all configured PVCs of a VISM-PR card.
To configure the loopback cell priority, complete the following steps:
Step 1 Ensure you are logged in to a VISM-PR card and are operating in the VoIP switching/trunking or AAL2 trunking mode.
Step 2 To set the CLP bit in the OAM cell, enter the cnfoamloopbkclp command.
nodename.1.27.VISM8.a > cnfoamloopbkclp <ClpSetFlag>
Replace the <ClpSetFlag> argument with one of the following values:
•1 = Enable (default). The CLP bit of the OAM cell is set to 1.
•2 = Disable. The CLP bit of the OAM cell is set to 0.
Step 3 To display the CLP bit settings for the OAM loopback cell, enter the dspvismparam command.
The following example shows the CLP bit of the OAM cell is set to 0.
nodename.1.27.VISM8.a > dspvismparam
VISM mode: voipSwitching/voipTrunking
VISM features Bit Map: 0x5bc
FunctionModuleType: VISM-PR-8T1
CAC flag: enable
DS0s available: 192
Template number: 2
Percent of functional DSPs: 100
IP address: 20.25.14.99
Subnet mask: 255.255.255.0
Bearer IP address: 0.0.0.0
Bearer Subnet mask: 0.0.0.0
Bearer IP ping: disable
RTCP report interval: 5000 msec
RTCP receive multiplier: 3
RTP receive timer: disable
ControlPrecedence/Tos: 0x60
BearerPrecedence/Tos: 0xa0
Aal2 muxing status: disable
Tftp Server Dn TFTPDOMAIN
Aggregate Clipping enable
Type <CR> to continue, Q<CR> to stop:
Aggregate Svc Bandwidth 0
Codec negotiation option 1
Profile negotiation option 1
VAD Duty Cycle 61
VAD Tolerance 100
VISM Initiated NW COT Off
VISM CO4 Timer 1000 msec
CALEA flag disable
Oam Loopback CLP Bit 0
Continuity Check Cell 1
SupportdModuleType: VISM-PR-8T1.
VismNSAP: 3838353000000000000000000000000001000100
History Statistics Enhancement
In Release 3.3.25, the VISM-PR card can collect the following new statistics:
•OAM Loopback Timeout counts
•New OAM Loopback Timeout duration
•Active OAM Loopback Timeout Duration
•OAM Loopback Timeout Threshold
When all of the statistics are enabled, VISM-PR performance is not affected. All of the statistics are enabled by default except for the statistics upload file, which is enabled through CWM.
The following two commands are modified to include these new statistics:
•dsphistorystats
•dspconcnt
You can collect history statistics on PVCs 1-64. PVCs above the 64th PVC are not tracked in history statistics and cannot be displayed with the dsphistorystats command.
For more information about collecting history statistics and the commands, refer to the Cisco Voice Interworking Services (VISM) Configuration Guide & Command Reference, Release 3.3 located at the following URL on Cisco.com:
http://www.cisco.com/en/US/products/hw/switches/ps1938/products_configuration_guide_book09186a0080301d30.html
To view the new OAM history statistics, use the dsphistorystats command.
nodename.1.5.VISM8.a > dsphistorystats <StatsType> <Interval> <InterfaceIndex>
|InterfaceIndex2|
Replace the above arguments with the values listed in Table 4.
Table 4 Parameters for dsphistorystats Command
Parameter
|
Description
|
StatsType
|
Type of history statistics. Value is 1 for PVC.
|
Interval
|
Interval. Range is 0-96.
A value of 0 displays the 24-hr total of all of the intervals. Values 1-96 are 15-minute time intervals for the previous 24 hrs.
|
InterfaceIndex
|
If StatsType is set to 1 (PVC) or 2 (CID), this value is in the range 131-510 for the logical channel number (LCN).
|
|InterfaceIndex2|
|
Not applicable for displaying the new OAM statistics.
|
In the following example the new OAM statistics are shown in bold.
pxm45-24.1.13.VISM8.a > dsphistorystats 1 80 132
PVC History Statistics: interval = 80, LCN = 132
--------------------------------------------
Valid Flag = VALID
Last Reset Uptime Ticks = 0
Total ATM Xmt Cells = 33157
Total ATM Rcv Cells = 31380
Avg Per Sec ATM Xmt Cells = 36
Avg Per Sec ATM Rcv Cells = 34
Peak Per Sec ATM Xmt Cells = 49
Peak Per Sec ATM Rcv Cells = 40
Total OAM Xmt End-to-End Lpbk Req Cells = 874
Total OAM Rcv End-to-End Lpbk Rsp Cells = 874
Total OAM Xmt Segment Lpbk Cells = 0
Total OAM Rcv Segment Lpbk Cells = 0
Total OAM End-to-End Lpbk Lost Cells = 0
Total Discarded Rcv OAM Cells = 0
Total OAM Lpbk Timeout Cnts = 0
Total New OAM Lpbk Timeout Duration = 0
Total Active OAM Lpbk Timeout Duration = 0
OAM Lpbk Timeout Threshold = 5
Total AIS Suppress Cnts = 0
Total Xmt AIS Cnts = 0
Total Rcv AIS Cnts = 0
Total Xmt FERF Cnts = 0
Total Rcv FERF Cnts = 0
Total Xmt AIS Cells = 0
Total Rcv AIS Cells = 0
Total Xmt FERF Cells = 0
Total Rcv FERF Cells = 0
Total AAL2 CPS Sent Pkts = 196985
Total AAL2 CPS Rcvd Pkts = 223126
Total AAL2 HEC Errors = 0
Total AAL2 CRC Errors = 0
Total AAL2 Invalid OSF Cells = 0
Total AAL2 Invalid Parity Cells = 0
Total AAL2 Invalid Cid Pkts = 12997
Total AAL2 Invalid UUI Pkts = 0
Total AAL2 Invalid Length Pkts = 0
Total AAL5 PDU Sent Pkts = 0
Total AAL5 PDU Rcvd Pkts = 0
Total AAL5 Invalid CPI PDUs = 0
Total AAL5 Oversized SDU Rcvd PDUs = 0
Total AAL5 Invalid Length PDUs = 0
Total AAL5 CRC32 Errored PDUs = 0
Total AAL5 Reassembly Timer Expiry PDUs = 0
Last Completed Interval Number is 81
To display the real-time count and duration of OAM Loopback Timeouts, use the dspconcnt command.
nodename.1.5.VISM8.a > dspconcnt <LCN>
Replace <LCN> with the number of the logical channel for which OAM loopback timeout information is to be displayed. Range is 131-510.
The following example shows the OAM Loopback Timer count and duration in bold.
pxm45-24.1.13.VISM8.a > dspconcnt 132
ChanNum: 132
Chan State: okay
Chan XMT ATM State: Normal
Chan RCV ATM State: Normal
Chan Status Bit Map: 0x0
OAM Lpb Lost Cells: 0
AAL2 HEC Errors: 0
AAL2 CRC Errors: 0
AAL2 Invalid OSF Cells: 0
AAL2 Invalid Parity Cells: 0
AAL2 CPS Packet Xmt: 3619340
AAL2 CPS Packet Rcv: 3745789
AAL2 Invalid CID CPS: 220398
AAL2 Invalid UUI CPS: 0
AAL2 Invalid Len. CPS: 0
Chan 24Hr Peak Xmt Cell Rate (CPS): 192
Chan Current Xmt Cell Rate (CPS): 38
Chan 24Hr Peak Rcv Cell Rate (CPS): 160
Chan Current Rcv Cell Rate (CPS): 36
AAL5 PDU Packet Xmt: 0
AAL5 PDU Packet Rcv: 0
AAL5 Invalid CPI: 0
AAL5 oversized SDU PDU: 0
AAL5 Invalid Len. PDU: 0
AAL5 PDU CRC32 Errors: 0
AAL5 Reassembly Timer expired PDU: 0
AIS Successful Suppression Count: 0
AIS Alarm Transmitted Count: 0
AIS Alarm Received Count: 0
FERF Alarm Transmitted Count: 0
FERF Alarm Received Count: 1
OAM Loopback Timeout Count 0
OAM Loopback Timeout Duration(secs):0
VISM Management Information Base
VISM Release 3.3.25 uses Management Information Base (MIB) Version 76. VISM MIBs are compatible with both PXM1-based and PXM1E/PXM45-based chassis.
To access the MIBs, complete the following steps:
Step 1 Load the MIBs available with MGX Release 1.3.11 located at the following URL: http://www.cisco.com/kobayashi/sw-center/wan/wan-planner.shtml
Step 2 Copy the modified MIBs that are contained in the MIBS.zip file, which is available at the same location as the firmware files for this release.
Note The MIB version number was last updated in Release 3.3.25.
VISM Redundancy
Table 5 provides the support level for 1:N Service Module Redundancy (N = 1 through 11).
Table 5 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.25 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, Cisco MGX 8850 (PXM1, PXM1E, PXM45), and Cisco MGX 8880 platform software is listed in Table 6.
Table 6 VISM/VISM-PR Software Interoperability
Product
|
Firmware
|
PXM1
|
1.3.12
1.2.23
1.2.13
|
PXM1E
|
5.002.000.200
5.000.020.201
4.000.017.202
3.000.025.200
|
PXM45
|
5.002.000.200
5.000.020.201
4.000.017.202
3.000.025.200
|
RPM-PR
|
12.3(7)T3
12.2(8)T1
|
RPM-XF
|
12.3(7)T3
12.2(15)T5
|
AXSM
|
5.002.000.200
5.000.020.201
4.000.017.202
3.000.025.200
|
MPSM
|
5.002.000.200
|
VXSM
|
5.002.000.200
|
Table 7 shows VISM and VISM-PR compatibility with the PXM controller cards.
Table 7 VISM/VISM-PR Compatibility with PXM Cards
| |
PXM1
|
PXM1E
|
PXM45 (A/B/C)
|
VISM
|
Yes
|
No
|
No
|
VISM-PR
|
Yes
|
Yes
|
Yes
|
Table 8 shows VISM and VISM-PR compatibility with the Cisco MGX chassis.
Table 8 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 9 describes the VISM/VISM-PR software interoperability with other Cisco products.
Table 9 VISM/VISM-PR Release 3.3.25 Interoperability with Other Cisco Products
Product
|
Latest Firmware
|
CWM
|
15.1.50 P1 and P2
|
BTS
|
4.5
4.4
4.2
3.5.4
|
PGW
|
9.5(2)
9.3(2)
|
CISCO 2421
|
12.3(10a)
|
AS5400
|
12.3.9
|
AS5300
|
12.3.9 with vcware 11.32
|
Table 10 describes the software images available for Release 3.3.25 for VISM/VISM-PR.
Table 10 Software Images for VISM/VISM-PR Release 3.3.25
Product Name
|
Software Version
|
Firmware Image Name
|
Description
|
MGX-VISM-SW3325
|
003.003.025.201.FW
|
vism_8t1e1_003.003.025.201.fw
|
This image does not support the CALEA1 feature.
|
MGX-VISM-LISW3325
|
003.053.025.201.FW
|
vism_8t1e1_003.053.025.201.fw
|
This image supports the CALEA2 feature.
|
Table 11 describes the software boot code requirements for VISM/VISM-PR Release 3.3.25.
Table 11 VISM/VISM-PR Software 3.3.25 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-PR cards not using this new release.
Limitations and Restrictions
The following limitations and restrictions are valid for software Release 3.3.25 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-PR 3.3.25.
•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.25, see "Caveats in Release 3.3.25" 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.25 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 3.2.11 to VISM 3.3.25
•From VISM 3.3 to VISM 3.3.25
•From VISM 3.3.20 to VISM 3.3.25
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.25 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.
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.25 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.25 are available:
•003.003.025.201.FW—without CALEA
•003.053.025.201.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.25.
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 05/10/2005 19:59:52 4037880 003.003.020.000 sm150.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.025.201.FW).
The install sm 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.
Caution Ensure that you perform
Step 4. If you do not perform
Step 4, the boot code is corrupted and not recoverable.
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.
The newrev command causes the primary VISM or VISM-PR card to reset. The secondary VISM or VISM-PR card becomes active and runs 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 only
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 boot code and firmware images on Cisco.com.
Step 2 To download the images, enter the ftp command.
ftp node-ip
The node-ip argument 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 Change to the C:FW 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.
The image-version argument is the image that you accessed in 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 the "Download VISM-PR Boot Code and Firmware to PXM1E and PXM45" section.
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 sample results from the burnboot command.
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 and becomes the standby again, and the standby card is now active.
Upgrade VISM-PR Firmware with PXM1E and PXM45 Cards
Complete the steps in this section to upgrade the VISM-PR firmware. 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.25 are available:
•003.003.025.201.FW—Without CALEA
•003.053.025.201.FW—With CALEA
Caution If you plan to upgrade PXM cards and VISM-PR modules, upgrade the PXM cards first. Wait until the PXM cards are operating in active and standby modes with the correct software before upgrading the VISM-PR modules. Failing to upgrade the node in the correct order can fail VISM connections, causing significant service disruption.
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, 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 card completes booting up and goes into the standby state by executing the dspcds command.
Note You must wait for the primary card to finish booting up 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 states. 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.25 to an earlier VISM/VISM-PR release. If you use the downgrade procedure described here, you can retain the configurations 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.
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.
Caution The
restoreallcnf command reconfigures all of the cards in the chassis.
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 For this procedure, 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 change 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 its slot in your chassis.
Step 2 Install a VISM-PR card in the same slot.
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 from which you removed the VISM card 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 its slot in your chassis.
Step 10 Install a VISM-PR card in the same slot.
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 ensure that the correct card type is shown for each.
Caveats in Release 3.3.25
This section describes the resolved and open caveats in VISM/VISM-PR Release 3.3.20.
Resolved Caveats in Release 3.3.25
Table 12 describes the caveats that have been resolved in Release 3.3.25 as of November 4, 2005.
Table 12 Resolved Caveats in Release 3.3.25
DDTS Issue
|
Description
|
CSCee41976
|
VISM cards are failing due to incorrect card id field on MB/DC
|
CSCee92429
|
Performance degradation since 3.1.3 results in additional AAL2 errors
|
CSCeh49678
|
dspxgcpendpt shows wrong information
|
CSCeh64800
|
Fax passthrough fails when excessive jitter is experienced
|
CSCeh72843
|
False statistics displayed by dspconcnt after deleting and adding AAL2 CIDs
|
CSCei20746
|
Profile 1, 7 (ITU 7) AAL2 indicates generic SID which is incorrect
|
CSCei54326
|
VISM stops sending RTCP packets after cnfgwoos forceful
|
CSCei54618
|
Discrepancy in the VISM statistical information
|
CSCei69138
|
NLP gets stuck in VoIP switching mode
|
CSCei85965
|
Insufficient bandwidth causes CIDs to be put OOS after card reset
|
CSCei87559
|
Configurable continuity check cell
|
CSCei93468
|
Voice path exists when CID is out of service
|
CSCej16082
|
Bad voice quality after upgrade from 3.1 to 3.3
|
CSCej24398
|
VISM line DB corruption
|
CSCej24487
|
Cannot clear dspconcac counter when card is reset
|
CSCej54263
|
VISM statistics upload key field for PVC statistics is incorrect
|
CSCin90085
|
In RSVP, GUI shows new element created although the LCN does not exist
|
CSCin95193
|
Modifying the session type for the RUDP session should throw error
|
Open Caveats in Release 3.3.25
Table 13 describes the open caveats in VISM/VISM-PR Release 3.3.25 as of November 17, 2005.
Table 13 Open Caveats in VISM/VISM-PR Release 3.3.25
DDTS Issue
|
Description
|
CSCei29995
|
Symptom: VISM-PR reports latency of zero when it interoperates with platforms: 2421, 3745, and 5400.
Conditions: This issue is seen intermittently in VISM-PR interop testing with 2421, 3745, and 5400.
Workaround: None.
|
CSCei51973
|
Symptom: Fax retrains to a lower data rate in case of VISM <-> IOS interop.
Conditions: With a T38 Fax Relay call between VISM-T1/VISM-PR-T1 (Template 3; G711u) and 5300, 2421, and 3745 IOS platforms, the fax transmission retrains from 14400 bps to 12000 bps. The fax transmission is successful but only at the lower data rate.
This conditions occurs when the IOS (5300, 2421, and 3745) platforms originate fax calls. The fax calls run successfully when VISM/VISM-PR originates the call.
With VISM interoperating with 5400 and 3810 platforms, this problem is not observed.
Workaround: None.
|
CSCej06477
|
Symptom: When 248 PVCs are configured and CIDs with G711a and VAD off are added per PVC, some PVCs go into failed state.
Conditions: The problem occurs if all 248 PVCs are added and each PVC has one CID on it.
Workaround: None.
|
CSCej12076
|
Symptom: VISM stops transporting DTMF after BW change.
Conditions: CIDS are in alarm state and are not able to transmit DTMF digits.
Workaround: None.
|
CSCej45540
|
Symptom: The UDP port used by the static RTP stream is used later by a dynamic RTP stream, which causes the datamover to send all the data from the C7 signaling stream to the wrong DSP channel.
Conditions: This issue occurs because after 1 to 2 hours, more than 248 dynamic RTP connections are set up. The 249 dynamic RTP connections use UDP port 49684, which is used by slot 2, C7 signaling channel. If the call rate is less, the time it takes to the dynamic RTP connection is more.
Workaround: Delete the RTP connections for the C7 signal, and add them back with a local UDP port greater than 49748.
|
CSCej61968
|
Symptom: Even after successfully recovering from DSP failure, VISM sends a 900 "DSP Failure" message in response to AUEP message CA.
Conditions: This issue occurs with a DSP failure.
Workaround: None.
|
Caveats in Release 3.3.20
This section describes the resolved and open caveats in VISM/VISM-PR Release 3.3.20.
Resolved Caveats in Release 3.3.20
Table 14 describes the caveats that have been resolved in Release 3.3.20 as of August 9, 2005.
Table 14 Resolved Caveats in Release 3.3.20
DDTS Issue
|
Description
|
CSCec68687
|
Simultaneous ISDN call drops not clearing all the endpoints on VISM
|
CSCef12950
|
VISM processes calls with Clr Chan Codec and ECAN On
|
CSCef32606
|
DSP fails to re-download when DSP failed
|
CSCef55005
|
High failure rate for fax passthrough calls on VISM
|
CSCef55425
|
Path confirmation failures-G729a codec, adaptive Jtr Delay
|
CSCef72611
|
Path confirmation failures with CCD calls and VISM 3.1(3.x)
|
CSCef80145
|
No speech with 0 fixed JB, timestamp on and 20 ms codec packet period
|
CSCeg25307
|
Increasing the jitter buffer has no effect in one-way delay
|
CSCeg61617
|
VISM crashes hours after running PRI backhaul load
|
CSCeg82063
|
RTP ports check on RTP stream
|
CSCeg86053
|
PVC bandwidth not freed up correctly after FAX relay call
|
CSCeg86125
|
VISM-PR DTMF not working for tones of 50 ms or less with Arris E-MTA
|
CSCeg90314
|
Wrong values for E1 dsplndsx0s default idle and seize CAS code
|
CSCeh02598
|
VISM displays novram via PXM1E incorrectly
|
CSCeh06598
|
VISM should return 540 errors instead of 501
|
CSCeh07389
|
T38 failed if dtmf-relay low-bit-rate configured on IAD side
|
CSCeh18123
|
After failing DSPs, dsplncidcps shows negative values
|
CSCeh35201
|
VISM crashes with E1 CCS load-ATMizier not responding
|
CSCeh36322
|
Six extra packets cause metallic voice
|
CSCeh39265
|
VISM-PR crashes when CP tone SIT is played out
|
CSCeh46707
|
Interop with SIP fails as VISM does not accept different codec strings
|
CSCeh47379
|
CCS AAL2 Trunking load of 200 V.110 calls cause reset
|
CSCeh51733
|
VISM dspcidcps does not show correct display
|
CSCeh54188
|
VISM is reset when interop with VXSM
|
CSCeh58782
|
32740 byte ping to vism host IP causes card to reset
|
CSCeh72843
|
False statistics displayed by dspconcnt after deleting/adding AAL2 CIDs
|
CSCeh77215
|
Softswitch on VISM causes burst of audible noise
|
CSCeh78724
|
Calls fail when adding cas variant endpoints in AAL2 trunking mode
|
CSCeh89668
|
Remote loopback on VISM does not appear to be working
|
CSCeh91020
|
E911 call drops when BTS sends piggybacked mgcp messages
|
CSCei26177
|
Call failures in benchmark load tests due to call throttling
|
CSCei26288
|
Restore the UUI codepoint range of custom profile 210
|
CSCin82554
|
VISM-PR sec.card allows SNMP set for trap filtering but not from CLI
|
CSCin87735
|
Wrong codec status displayed when fax mode changed to relay/passthru
|
CSCin89464
|
D_vismChanState_oid 1.3.6.1.4.1.351.110.5.5.3.2.1.1.2 missing in CF
|
Open Caveats in Release 3.3.20
Table 15 describes the open caveats in VISM/VISM-PR Release 3.3.20 as of July 19, 2005.
Table 15 Open Caveats in VISM/VISM-PR Release 3.3.20
DDTS Issue
|
Description
|
CSCeh72843
|
Symptom: CLI dspconcnt shows false AAL5 statistics when AAL2 CIDs have been deleted and re-added.
Conditions: This symptom occurs with the following conditions:
•AAL2 trunking
•CIDs added, deleted and re-added
•Releases 3.3.10 and earlier
Workaround: Do not delete and re-add CIDs.
Issue the clrsmcnf command and reconfigure the card if CIDs are changed and statistics are needed.
|
CSCei25172
|
Symptom: VISM lines are stuck in AIS.
Conditions: VISM-PR-8T1 is configured for AAL2 trunking and has CID. When the DS3 links go down and come back up, the VISM line remains stuck in AIS alarm.
Workaround: Disconnect and then reconnect the VISM cable.
|
CSCei30249
|
Symptom: VISM resets itself upon receiving RTP packets with different SSRCs on each RTP packet.
Conditions: The symptom happens only when VISM receives RTP packets with different SSRCs on each RTP packet.
This condition occurred with 12.3.4T6 on one of its IAD 2431 to create the problem.
Workaround: Fix the issue on the other side of the RTP session so that the correct SSRCs are used.
|
CSCei54326
|
Symptom: VISM stops sending RTCP packets after cnfgwoos forceful.
Conditions: RTCP packets are not sent from VISM for any of the calls when the VISM meets the following conditions:
1. One hundred or more active calls exist.
2. The gateway is forcefully taken out of service: cnfgwoos 2
3. The gateway is put back in service: cnfgwis
Workaround: Take the gateway gracefully out of service: cnfgwoos 3
|
CSCei54618
|
Symptom: Discrepancy in the VISM statistical information.
Conditions: The issue was observed with the CTM /MGM 5.0 Element Management on the MGX 8850 with VISM-PR-8T1/E1 Release 3.3.10.
Workaround: Use SNMP to get the current real-time and last 15 minute statistics for unavailable seconds (UAS) statistics.
Further Problem Description: The incorrect report value is of the UAS that is calculated by the VISM-PR.
|
CSCei61996
|
Symptom: VQT Stats: Latency is different between each direction of a call. During the early stage of a call, the A-->B and B-->A directions of a call report different values of latency.
Conditions: This symptom occurs with the following conditions:
•VAD ON
•Fixed jitter buffer
•Timestamp disabled
•VoIP switching mode
Workaround: Use one of the following workarounds:
1. Fixed jitter buffer mode with timestamp enabled
2. Adaptive jitter buffer mode
3. VAD disabled
|
CSCei85965
|
Symptom: CIDs are put in OOS as a result of insufficient bandwidth.
Conditions: Subsequent CIDs will be put in OOS after a card reset.
Workaround: Increase the bandwidth on the PVC.
|
Caveats in Release 3.3.10
This section describes the resolved and open caveats in VISM/VISM-PR Release 3.3.10.
Resolved Caveats in Release 3.3.10
Table 16 describes the caveats that have been resolved in VISM/VISM-PR Release 3.3.10.
Table 16 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 17 describes the open caveats in VISM/VISM-PR Release 3.3.10 as of March 11, 2005.
Table 17 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, it utilizes only 50 cps once in Fax Relay mode.
Conditions: This affects fax calls on VISM when using a template in AAL2 trunking mode. The configured bandwidth is lesser than that used by fax passthrough.
Workaround: Configure the PVC with extra bandwidth of 140 cps, which allows the fax calls on VISM to upspeed to Fax Relay mode.
|
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).
|
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 18 describes the caveats that have been resolved in VISM/VISM-PR Release 3.3.
Table 18 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 BearerBusyCode is change through SNMP set.
|
CSCee07440
|
Switch agent should reject SET on BearereBusyCode, if TrunkCond disable.
|
CSCee09073
|
VISM 3.2.1-vism_cid table is not updated when changed admin state.
|
CSCee13138
|
VISM-PR unreachable from IP cloud.
|
CSCee20389
|
tstdelay measurement reported as us instead of ms.
|
CSCee21753
|
CAS template allowed to create with out-of-range index 21 by SNMP.
|
CSCee22756
|
Media Start package-Packet detector work only on first DSP channel.
|
CSCee29268
|
REG5+: VISM MSG #9059 missing from legacy/vismGlobals.c.
|
CSCee31685
|
VISM sends extra concealment when init delay is 20 ms and 3 packet lost.
|
CSCee32065
|
911 Operator Ringback Fails on VISM.
|
CSCee35515
|
CAS signaling channel not programmed during DSP redownload.
|
CSCee37609
|
Adding multiple endpoints succeeds but failure reported.
|
CSCee54848
|
Spurious upspeed on VISM 3.2.10.
|
CSCee61267
|
Increase of PVC bandwidth should be allowed when CIDs are active.
|
CSCee66023
|
DSPs failed when running calls on Clear Channel with timestamp enable.
|
CSCee68257
|
Support 64 character domain name on VISM.
|
CSCef23824
|
VISM card resets when multiple DSPs fail.
|
CSCef26389
|
Clock slips on VISM while running load.
|
CSCin69879
|
VISM resets on giving addcon with MBS = 0.
|
Open Caveats
Table 19 describes the open caveats in VISM/VISM-PR Release 3.3 as of September 27, 2004.
Table 19 Open Caveats for VISM/VISM-PR Release 3.3
DDTS Issue
|
Description
|
CSCec54765
|
Symptom: VISM regenerates incorrect DTMF on-times in VoIP Trunking mode.
Conditions: When DTMF digits with on-times of less than 50 ms are detected on the near-end VISM, the digits are regenerated with inconsistent on/off times on the far end VISM.
Workaround: Ensure the DTMF digits that are detected have an on-time value greater than 50-60 ms (preferably greater than 60 ms).
|
CSCed59217
|
Symptom: VISM-PR keeps sending DTMF digits when no digit is pressed.
Conditions: By random press of the digits on both on-net and off-net phone or the combination of various digits at the same time, the VISM-PR card sends out the DTMF payload type 101 packets every 50 ms (like retransmission) even when digit is entered from the TDM side.
Workaround: Press another digit in the normal fashion to clear the problem.
|
CSCed83268
|
Symptom: Lower than expected throughput on V.90 modem calls over AAL2. Some modem calls speed shift to V.34 speeds and/or retrain.
Conditions: This symptom occurs with VISM to VISM calls as well as VISM to VXSM calls.
Workaround: None.
|
CSCee92429
|
Symptom: Voice quality issue due to AAL2 packet drops.
Conditions: Configure 248 CIDS with G.711a 5 ms with VAD off and subcell muxing enabled from one VISM-PR-E1 to another VISM-PR-E1.
Delete some CIDS on one VISM-PR and re-add. The following errors are seen on other side thus causing voice quality issue:
•AAL2 HEC errors
•AAL2 invalid OSF cells
•AAL2 invalid length
Workaround:
1. Turn subcell muxing off and/or turn VAD on.
2. Use G.729 or other 10 ms/20 ms codecs.
|
CSCef02022
|
Symptom: VISM advertising the NTE capability with DTMF relay disabled.
Conditions: When DTMF Relay is disabled on the VISM, the NTE capability is still advertised by the VISM.
Specifically, when the VISM is configured for DTMF relay off (cnfvoiptransparams 2 1 1 1), VISM response to the call agent still advertises the VISM bearer capability to use NTE for digits 0-15.
Workaround: None.
|
CSCef32606
|
Symptom: DSPs stop responding to ping after re-download is initiated when DSPs failed.
Conditions: This condition is random. Some DSPs might or might not re-download. This symptom happens when you have connections that are associated with the DSPs prior to the failure. DSP status is not in active state.
Workaround: Reset the card.
|
CSCef39465
|
Symptom: When the cell rate on one of the VISM connection exceeds its PCR value, HEC Errors and Invalid OSF cell counters starts incrementing on all of the connections on the VISM card.
Conditions: This problem happens only in AAL2 trunking mode and with subcell multiplexing on.
Workaround: Having a sufficient PCR value on all the VISM connections so that the cell rate on any of the connections exceeds the PCR value is the only solution.
|
CSCef55005
|
Symptom: When running high traffic load scenarios with eight fully loaded E1 spans in VoIP switching mode, traffic might include upspeed to G.711, clear channel, or nailed up G.711 voice connections.
Packet loss might be encountered on occasion.
Conditions: This symptom occurs when concurrent traffic load of G.711 or clear channel with VAD off is sustained on lines with greater than 220 DS0s.
Workaround: For G.711 use VAD on because this issue does not occur with VAD on. Currently for clear channel the recommendation is not to load more than seven spans when utilizing 3.3 release.
|
CSCef55425
|
Symptom: Path confirmation failures—G.729a codec, adaptive jitter delay.
Conditions: At 11 calls per second, 3% of the voice calls fail with path confirmation errors (subsequent).
VISM configuration is ISDN-G729a with template 1. Jitter buffer is adaptive with initial delay set at 60 ms.
Workaround: Configure fixed jitter buffer delay of any value should resolve this problem for G.729a codec.
|
CSCef69692
|
Symptom: Mibwalk stuck in loop on catsAal2PvcHistoryTable.
Conditions: Multiple PVCs with multiple bucket interval updates for statistics causes this symptom to occur.
Workaround: No workarounds exist for the mibwalk. Except, run the mibwalks right after a card reset.
Note SNMP gets for objects within the table work correctly.
|
CSCef72611
|
Symptom: Path confirmation failures with CCD calls and VISM 3.1(3.x).
Conditions: Voice quality degrades (hiss) when running Clear Channel codec when the originating and terminating VISM cards are running different images, for example 3.1.3.x and 3.2.x.x.
This problem is not seen with any other codec or when running the Clear Channel codec on both VISM cards that are running the same version.
Workaround: Configure VISM to utilize a different codec during upgrades. And/or upgrade both VISM cards to the same version before running Clear Channel voice traffic.
|
CSCef81423
|
Symptom: BTS VoIP Switch T1 CAS 15 CPS load causes card resets.
Conditions: This problem exists only during CAS call load. VISM supports call rates up to a maximum call load of 10 cps.
Workaround: Ensure the call rate for a fully loaded VISM card that is configured for CAS voice traffic does not exceed the supported rate of 10 cps.
|
CSCeg47932
|
Symptom: 64 character VISM domain name causes VISM card to hang.
Conditions: After adding a 64 character VISM domain name using the cnfvismdn command, the card resets. When the card becomes active and you execute the dspvismdn command, the response shows (null) instead of the vism domain name.
If you try to execute the cnfvismdn command again, the prompt hangs indefinitely.
This problem is similar to caveat CSCee68257, regarding the call agent domain names instead of the VISM domain name.
This symptom occurs on VISM cards with Release 3.3 and a 64 character VISM domain name.
Workaround: Clear the configuration and enter only vism domain names with a maximum length of 63 characters.
|
Related Documentation
The following documents contain information that may be useful to software Release 3.3.25 for VISM/VISM-PR:
•Cisco Voice Interworking Services (VISM) Configuration Guide and Command Reference, Release 3.3
•Cisco MGX 8830, MGX 8850 (PXM45 and PXM1E), and MGX 8950 Command Reference, Release 5
•Cisco MGX 8850 (PXM45 and PXM1E) Hardware Installation Guide, Release 5
•Cisco MGX 8850 (PXM45) and MGX 8950 Software Configuration Guide, Release 5
Obtaining Documentation
Cisco documentation and additional literature are available on Cisco.com. Cisco also provides several ways to obtain technical assistance and other technical resources. These sections explain how to obtain technical information from Cisco Systems.
Cisco.com
You can access the most current Cisco documentation at this URL:
http://www.cisco.com/techsupport
You can access the Cisco website at this URL:
http://www.cisco.com
You can access international Cisco websites at this URL:
http://www.cisco.com/public/countries_languages.shtml
Product Documentation DVD
Cisco documentation and additional literature are available in the Product Documentation DVD package, which may have shipped with your product. The Product Documentation DVD is updated regularly and may be more current than printed documentation.
The Product Documentation DVD is a comprehensive library of technical product documentation on portable media. The DVD enables you to access multiple versions of hardware and software installation, configuration, and command guides for Cisco products and to view technical documentation in HTML. With the DVD, you have access to the same documentation that is found on the Cisco website without being connected to the Internet. Certain products also have .pdf versions of the documentation available.
The Product Documentation DVD is available as a single unit or as a subscription. Registered Cisco.com users (Cisco direct customers) can order a Product Documentation DVD (product number DOC-DOCDVD=) from Cisco Marketplace at this URL:
http://www.cisco.com/go/marketplace/
Ordering Documentation
Beginning June 30, 2005, registered Cisco.com users may order Cisco documentation at the Product Documentation Store in the Cisco Marketplace at this URL:
http://www.cisco.com/go/marketplace/
Nonregistered Cisco.com users can order technical documentation from 8:00 a.m. to 5:00 p.m. (0800 to 1700) PDT by calling 1 866 463-3487 in the United States and Canada, or elsewhere by calling 011 408 519-5055. You can also order documentation by e-mail at tech-doc-store-mkpl@external.cisco.com or by fax at 1 408 519-5001 in the United States and Canada, or elsewhere at 011 408 519-5001.
Documentation Feedback
You can rate and provide feedback about Cisco technical documents by completing the online feedback form that appears with the technical documents on Cisco.com.
You can send comments about Cisco documentation to bug-doc@cisco.com.
You can submit comments by using the response card (if present) behind the front cover of your document or by writing to the following address:
Cisco Systems
Attn: Customer Document Ordering
170 West Tasman Drive
San Jose, CA 95134-9883
We appreciate your comments.
Cisco Product Security Overview
Cisco provides a free online Security Vulnerability Policy portal at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
From this site, you can perform these tasks:
•Report security vulnerabilities in Cisco products.
•Obtain assistance with security incidents that involve Cisco products.
•Register to receive security information from Cisco.
A current list of security advisories and notices for Cisco products is available at this URL:
http://www.cisco.com/go/psirt
If you prefer to see advisories and notices as they are updated in real time, you can access a Product Security Incident Response Team Really Simple Syndication (PSIRT RSS) feed from this URL:
http://www.cisco.com/en/US/products/products_psirt_rss_feed.html
Reporting Security Problems in Cisco Products
Cisco is committed to delivering secure products. We test our products internally before we release them, and we strive to correct all vulnerabilities quickly. If you think that you might have identified a vulnerability in a Cisco product, contact PSIRT:
•Emergencies — security-alert@cisco.com
An emergency is either a condition in which a system is under active attack or a condition for which a severe and urgent security vulnerability should be reported. All other conditions are considered nonemergencies.
•Nonemergencies — psirt@cisco.com
In an emergency, you can also reach PSIRT by telephone:
•1 877 228-7302
•1 408 525-6532
Tip We encourage you to use Pretty Good Privacy (PGP) or a compatible product to encrypt any sensitive information that you send to Cisco. PSIRT can work from encrypted information that is compatible with PGP versions 2.x through 8.x.
Never use a revoked or an expired encryption key. The correct public key to use in your correspondence with PSIRT is the one linked in the Contact Summary section of the Security Vulnerability Policy page at this URL:
http://www.cisco.com/en/US/products/products_security_vulnerability_policy.html
The link on this page has the current PGP key ID in use.
Obtaining Technical Assistance
Cisco Technical Support provides 24-hour-a-day award-winning technical assistance. The Cisco Technical Support & Documentation website on Cisco.com features extensive online support resources. In addition, if you have a valid Cisco service contract, Cisco Technical Assistance Center (TAC) engineers provide telephone support. If you do not have a valid Cisco service contract, contact your reseller.
Cisco Technical Support & Documentation Website
The Cisco Technical Support & Documentation website provides online documents and tools for troubleshooting and resolving technical issues with Cisco products and technologies. The website is available 24 hours a day, at this URL:
http://www.cisco.com/techsupport
Access to all tools on the Cisco Technical Support & Documentation website requires a Cisco.com user ID and password. If you have a valid service contract but do not have a user ID or password, you can register at this URL:
http://tools.cisco.com/RPF/register/register.do
Note Use the Cisco Product Identification (CPI) tool to locate your product serial number before submitting a web or phone request for service. You can access the CPI tool from the Cisco Technical Support & Documentation website by clicking the Tools & Resources link under Documentation & Tools. Choose Cisco Product Identification Tool from the Alphabetical Index drop-down list, or click the Cisco Product Identification Tool link under Alerts & RMAs. The CPI tool offers three search options: by product ID or model name; by tree view; or for certain products, by copying and pasting show command output. Search results show an illustration of your product with the serial number label location highlighted. Locate the serial number label on your product and record the information before placing a service call.
Submitting a Service Request
Using the online TAC Service Request Tool is the fastest way to open S3 and S4 service requests. (S3 and S4 service requests are those in which your network is minimally impaired or for which you require product information.) After you describe your situation, the TAC Service Request Tool provides recommended solutions. If your issue is not resolved using the recommended resources, your service request is assigned to a Cisco engineer. The TAC Service Request Tool is located at this URL:
http://www.cisco.com/techsupport/servicerequest
For S1 or S2 service requests or if you do not have Internet access, contact the Cisco TAC by telephone. (S1 or S2 service requests are those in which your production network is down or severely degraded.) Cisco engineers are assigned immediately to S1 and S2 service requests to help keep your business operations running smoothly.
To open a service request by telephone, use one of the following numbers:
Asia-Pacific: +61 2 8446 7411 (Australia: 1 800 805 227)
EMEA: +32 2 704 55 55
USA: 1 800 553-2447
For a complete list of Cisco TAC contacts, go to this URL:
http://www.cisco.com/techsupport/contacts
Definitions of Service Request Severity
To ensure that all service requests are reported in a standard format, Cisco has established severity definitions.
Severity 1 (S1)—Your network is "down," or there is a critical impact to your business operations. You and Cisco will commit all necessary resources around the clock to resolve the situation.
Severity 2 (S2)—Operation of an existing network is severely degraded, or significant aspects of your business operation are negatively affected by inadequate performance of Cisco products. You and Cisco will commit full-time resources during normal business hours to resolve the situation.
Severity 3 (S3)—Operational performance of your network is impaired, but most business operations remain functional. You and Cisco will commit resources during normal business hours to restore service to satisfactory levels.
Severity 4 (S4)—You require information or assistance with Cisco product capabilities, installation, or configuration. There is little or no effect on your business operations.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•Cisco Marketplace provides a variety of Cisco books, reference guides, documentation, and logo merchandise. Visit Cisco Marketplace, the company store, at this URL:
http://www.cisco.com/go/marketplace/
•Cisco Press publishes a wide range of general networking, training and certification titles. Both new and experienced users will benefit from these publications. For current Cisco Press titles and other information, go to Cisco Press at this URL:
http://www.ciscopress.com
•Packet magazine is the Cisco Systems technical user magazine for maximizing Internet and networking investments. Each quarter, Packet delivers coverage of the latest industry trends, technology breakthroughs, and Cisco products and solutions, as well as network deployment and troubleshooting tips, configuration examples, customer case studies, certification and training information, and links to scores of in-depth online resources. You can access Packet magazine at this URL:
http://www.cisco.com/packet
•iQ Magazine is the quarterly publication from Cisco Systems designed to help growing companies learn how they can use technology to increase revenue, streamline their business, and expand services. The publication identifies the challenges facing these companies and the technologies to help solve them, using real-world case studies and business strategies to help readers make sound technology investment decisions. You can access iQ Magazine at this URL:
http://www.cisco.com/go/iqmagazine
or view the digital edition at this URL:
http://ciscoiq.texterity.com/ciscoiq/sample/
•Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in designing, developing, and operating public and private internets and intranets. You can access the Internet Protocol Journal at this URL:
http://www.cisco.com/ipj
•Networking products offered by Cisco Systems, as well as customer support services, can be obtained at this URL:
http://www.cisco.com/en/US/products/index.html
•Networking Professionals Connection is an interactive website for networking professionals to share questions, suggestions, and information about networking products and technologies with Cisco experts and other networking professionals. Join a discussion at this URL:
http://www.cisco.com/discuss/networking
•World-class networking training is available from Cisco. You can view current offerings at this URL:
http://www.cisco.com/en/US/learning/index.html
CCSP, CCVP, the Cisco Square Bridge logo, Follow Me Browsing, and StackWise are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and iQuick Study are service marks of Cisco Systems, Inc.; and Access Registrar, Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCIP, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unity, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherFast, EtherSwitch, Fast Step, FormShare, GigaDrive, GigaStack, HomeLink, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, iQ Net Readiness Scorecard, LightStream, Linksys, MeetingPlace, MGX, the Networkers logo, Networking Academy, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, ProConnect, RateMUX, ScriptShare, SlideCast, SMARTnet, StrataView Plus, TeleRouter, The Fastest Way to Increase Your Internet Quotient, and TransPath are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the United States and certain other countries.
All other trademarks mentioned in this document or Website are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (0502R)
© 2005 Cisco Systems, Inc. All rights reserved.
