Table Of Contents
Release Notes for Cisco Voice Interworking Service Module Release 1.5(9)
About the 1.5(9) Release
About the 1.5(8) Release
About the 1.5(7) Release
About the 1.5.05 Release
About the 1.5.04 Release
About the 1.5.03 Release
About the 1.5.02 Release
Contents
Features
Features Introduced in Release 1.5(9)
Features Introduced in Release 1.5(8)
Feature Introduced in Release 1.5(7)
Features Introduced in Release 1.5.05
Features Introduced in Release 1.5.04
Features Introduced in Release 1.5.03
Features Introduced in Release 1.5.02
Features Introduced in Release 1.5.01
Release 1.5(9) VISM Hardware
Redundancy
Features Not Supported in this Release
VISM MIB
Notes and Cautions
Notes and Cautions for Release 1.5(9)
Notes and Cautions for Release 1.5(8)
Notes and Cautions for Release 1.5(7)
Notes and Cautions for Release 1.5.05
Notes and Cautions for Release 1.5.04
Notes and Cautions for Release 1.5.03
Notes and Cautions For Release 1.5.02
Problems Fixed
Problem Fixed in Release 1.5(9)
Problems Fixed in Release 1.5(8)
Problems Fixed in Release 1.5(7)
Problems Fixed in Release 1.5.05
Problems Fixed in Release 1.5.04
Problems Fixed in Release 1.5.03
Problems Fixed in Release 1.5.02
Compatibility Notes
VISM Software Interoperability with MGX 8850 Platform Software
Special Installation and Upgrade Requirements
VISM Firmware Download Procedure
VISM Graceful Upgrade to 1.5(9)
VISM Upgrade from 1.5.01 and 1.5.02 to Later Releases
Standard Service Module Download Procedure
Known Anomalies for VISM
VISM 1.5(9) Anomalies
VISM 1.5(8) Anomaly
VISM 1.5(7) Anomaly
VISM 1.5.05 Anomalies
VISM 1.5.04 Anomalies
VISM 1.5.03 Anomalies
VISM 1.5.02 Anomalies
VISM 1.5.01 Anomalies
VISM 1.0 Anomalies
Obtaining Documentation
Cisco.com
Documentation CD-ROM
Ordering Documentation
Documentation Feedback
Obtaining Technical Assistance
Cisco.com
Technical Assistance Center
Cisco TAC Website
Cisco TAC Escalation Center
Obtaining Additional Publications and Information
Release Notes for Cisco Voice Interworking Service Module Release 1.5(9)
August 2003
About the 1.5(9) Release
The VISM 1.5(9) Release is a patch release and contains no new features. See the "Problem Fixed in Release 1.5(9)" section for information on the resolved caveat, CSCea42208.
About the 1.5(8) Release
The VISM 1.5(8) release is a patch release and contains no new features. This release consists of the following resolved DDTs issues:
•
CSCdv81919
•CSCdx71685
•CSCdx76786
See the "Resolved Caveats for VISM Release 1.5(8)" section for a description of the resolve issues.
About the 1.5(7) Release
The VISM 1.5(7) release consists of the new cnfallcids command line interface (CLI) command, resolved DDTs issues, and one open DDTs issue. See the "Feature Introduced in Release 1.5(7)" section for a complete description of cnfallcids. See the "Problems Fixed in Release 1.5(7)" section for a description of the following resolved DDTs issues:
•CSCdt56908
•CSCdv57222
•CSCdv77719
•CSCdv81693
•CSCdv84047
•CSCdw53331
See the "VISM 1.5(7) Anomaly" section for the open DDTs issue—CSCdv60608.
About the 1.5.05 Release
The 1.5.05 release is a maintenance upgrade of the VISM 1.5.04 release with some minor feature enhancements and a small number of corrected anomalies. This release is compatible with the Cisco MGX 8850 Release 1.1.24.
About the 1.5.04 Release
The 1.5.04 release is a maintenance upgrade of the VISM 1.5.03 release with a small number of corrected anomalies. There is also better support for E1 lines. This release is compatible with the MGX 8850 Release 1.1.23.
About the 1.5.03 Release
The 1.5.03 Release is a maintenance upgrade of the VISM 1.5.02 release with a small number of corrected anomalies. This release is compatible with the MGX 8850 release 1.1.23.
About the 1.5.02 Release
The previous release of VISM, known as Release 1.5.01, was part of the general MGX 8850 Release 1.1.22.
VISM releases have now been unbundled from the MGX 8850.
This VISM release, known as Release 1.5.02, is, therefore, an independent VISM software release that stands alone and is not part of a general MGX 8850 release. There are, however, compatibility issues regarding which release of VISM can operate with which release of the MGX 8850 and other Cisco products. See the "Compatibility Notes" section for details.
The update procedure included in these release notes should be noted to work around a clrsmcnf problem on slots with VISM cards.
Contents
These release notes contain the following sections:
•Features
•Release 1.5(9) VISM Hardware
•Redundancy
•Features Not Supported in this Release
•VISM MIB
•Notes and Cautions
•Problems Fixed
•Compatibility Notes
•Special Installation and Upgrade Requirements
•Known Anomalies for VISM
•Obtaining Documentation
•Obtaining Technical Assistance
•Obtaining Additional Publications and Information
Features
This section lists the features supported in each of the VISM 1.5.x releases.
Features Introduced in Release 1.5(9)
None.
Features Introduced in Release 1.5(8)
None.
Feature Introduced in Release 1.5(7)
The new cnfallcids command is added to VISM Release 1.5(7).
To configure all existing CIDs with idle channel suppression (ICS) and/or voice activity detection (VAD), use the cnfallcids command only in the AAL2 trunking operating mode.
cnfallcids idle-code-sup |vad-enable|
Syntax Description
idle-code-sup
|
Enables or disables idle channel suppression for all CIDs. It can be one of the following values:
1 = On
2 = Off
|
vad-enable
|
(Optional) Enables or disables voice activity detection for all CIDs. It can be one of the following values:
1 = On
2 = Off
|
Command Modes
AAL2 trunking
Usage Guidelines
The help string produced for this command lists default values. There are no default values associated for this command. Ignore the help string default value list for this command.
Note This command will not be available in any other release of VISM software.
Examples
The following example enables both ICS and VAD on all existing CIDs:
Related Commands
Command
|
Description
|
addcid
|
Adds an AAL2 channel identifier (CID) on a VISM card.
|
delcid
|
Deletes the association between an endpoint and an LCN/CID pair.
|
dspcid
|
Displays the argument values of an AAL2 CID on a VISM card.
|
dspcids
|
Displays all the AAL2 CIDs for a specified LCN on a VISM card.
|
Features Introduced in Release 1.5.05
Release 1.5.05 contains the following features:
•Idle channel suppression.
•Support for setting the IP precedence bit.
•Support for Q.50 CAS signaling variant.
•Negotiable packetization period.
Features Introduced in Release 1.5.04
Release 1.5.04 contains the following features:
•E1 backcard support in AAL2 trunking mode.
•AAL2 sub-cell multiplexing.
Features Introduced in Release 1.5.03
None.
Features Introduced in Release 1.5.02
VISM 1.5.02 includes all the features included with Release 1.5.01 and introduces the following new features:
•E1 backcard support (VoIP mode only).
•The following new CLI commands:
–dsploops—display line and endpoint loopbacks.
–pinglndsp—display the health of DSPs for a specified line.
–dsplnendptstatus—display endpoint status for a specified line.
•The addcon command has been modified to allow the user to specify the local VCI to be used for the connection.
Features Introduced in Release 1.5.01
Release 1.5.01 contains the following features:
•Provides 8 standard T1 interfaces with B8ZS, AMI and HDB3 line coding.
•Support for Voice over ATM using AAL2 cells (multiplexing only, no LLC/SNAP encapsulation).
•Voice over IP (VoIP) using AAL5 cells to RFC 1889.
•Support for both PCM a-law and mu-law.
•Programmable 24, 32, 48, 64, 80, 96, 112, 128 ms near end echo cancellation.
•Voice compression to G.711 and G.726-32K standards.
•Nx64 clear channel (N = 1 only) support.
•Voice activity detection (VAD) and comfort noise generation (CNG) using variable threshold energy (Cisco proprietary).
•Support for Call Agent Simple Gateway Control Protocol (SGCP) version 1.0, SGCP 1.1+, and Media Gateway Control Protocol (MGCP) 0.1.
•Support for CCS signaling transport across an AAL5 trunk.
•Support for fax and modem VoIP bearer transmissions.
•Support for dual (redundant) virtual circuits across the packet network.
•Support for full continuity testing (COT). Supports origination and terminating loopback and transponder COT towards the packet bearer and the TDM sides.
•Support for looptiming, payload, and line loopbacks.
•1:N cold redundancy using SRM-3T3 capabilities (bulk mode support for T1 lines only). Calls do not persist during switchover.
•Courtesy downing of ongoing voice calls when the VISM is taken out of service for maintenance or other reasons.
Release 1.5(9) VISM Hardware
Note This section contains the hardware that is supported for all of the VISM 1.5.x releases.
VISM hardware consists of two versions of a front card—one supporting T1 and one supporting E1.
The following versions of back card are supported by VISM Releases 1.5.x:
•An 8-port T1 version using RJ-48 connectors
•An 8-port E1 version using RJ-48 connectors
•An 8-port E1 version using SMB connectors
Each of the above back cards also has a redundant version.
The following table lists the VISM 1.5.x hardware front cards and back cards and their revisions:
Front Card Model #
|
Rev #
|
Back Card Model #
|
Rev #
|
AX-VISM-8T1
|
B1
|
AX-RJ48-8T1
|
A
|
AX-R-RJ48-8T1
|
A
|
AX-VISM-8E1
|
B1
|
AX-SMB-8/E1
|
A
|
AX-R-SMB-8E1
|
A
|
AX-RJ48-8/E1
|
A
|
AX-R-RJ48-8E1
|
A
|
Note The E1 versions of the above front and back cards are supported only when VISM is operating in VoIP mode.
Redundancy
Table 1 provides the support level for 1:N and 1:1 service module redundancy.
Table 1 1:N and 1:1 Service Module Redundancy
Front card model #
|
Redundancy supported
|
MGX-VISM-8T1
|
1:N redundancy (bulk mode support for T1 lines only)
|
MGX-VISM-8E1
|
1:N redundancy (bulk mode support for T1 lines only)
|
Bulk distribution is supported by using the SRM-3T3B card.
Features Not Supported in this Release
•T1/CAS Backhaul
•G.729a and G.729ab voice compression
•G729ab voice activity detection
•VBR Provisioning - Although the CLI allows the user to specify variable bit rate (VBR), VISM does not actually provision the card for VBR in this release.
•ABR/UBR Provisioning - These connections are not supported in this release and no connections are made when these parameters are specified by the user through the CLI.
•Support for 31 DS0s on E1 lines.
Note Code for the above features may be included in the VISM code image. However, no specific mechanism has been included to prevent the use of these unsupported features. If the user attempts to use these unsupported features, there is no guarantee that the features will operate correctly.
VISM MIB
The VISM MIB is available by request through your Cisco VISM product marketing representative.
Notes and Cautions
This section contains notes and cautions for the VISM 1.5.x releases.
Notes and Cautions for Release 1.5(9)
None.
Notes and Cautions for Release 1.5(8)
None.
Notes and Cautions for Release 1.5(7)
None.
Notes and Cautions for Release 1.5.05
Do not upgrade the VISM backup boot firmware as this may render the VISM card inoperable.
All other Notes and Cautions for Release 1.5.02 still apply (see below).
Notes and Cautions for Release 1.5.04
Do not upgrade the VISM backup boot firmware as this may render the VISM card inoperable.
All other Notes and Cautions for Release 1.5.02 still apply (see below).
Notes and Cautions for Release 1.5.03
Do not upgrade the VISM backup boot firmware as this may render the VISM card inoperable.
All other Notes and Cautions for Release 1.5.02 still apply (see below).
Notes and Cautions For Release 1.5.02
Do not upgrade the VISM backup boot firmware as this may render the VISM card inoperable.
The following CLI modification and changes apply to this release:
•The following new CLI commands:
–dsploops—Display line and endpoint loopbacks. This command has no parameters.
–pinglndsp <line #>—Display the health of DSPs for a specified line.
–dsplnendptstatus <line#>—Display the endpoint status for a specified line.
•The following CLI command is not supported in Release 1.5.02:
–cnfcasxgcp—Configure CAS xGCP.
•The dspxgcpstat and dspxgcpstats commands have been renamed to dspxgcpcnt and dspxgcpcnts respectively.
•Both codec templates, 1 and 2, now include clear channel.
•The addcon command has been changed to include a new "localVCI" parameter. Also the permissible ranges for the addcon PCR parameter have been changed.
The format of the addcon command is now:
addcon <localVCI><preference><pvcType><application><PCR><mastership>[<remoteConnId>]
Where:
localVCI
|
Local VCI to be used for the connection. Range is 131-510. The value entered is also used as the LCN value.
|
preference
|
Specifies the use of a primary or secondary channel: 1 for primary, 2 for secondary.
|
pvcType
|
Specifies the AAL type of the connection. 1 for AAL5, 2 for AAL2
|
application
|
Application of the connection. 1 = control, 2 = bearer, 3 = signaling. If the connection is used for bearer and signaling, specify 2 for bearer.
|
PCR
|
Peak cell rate in cells per second. Ranges are: 1 - 75600 for VoIP bearer,
1 - 24400 for VoIP control, 1 - 50000 for AAL2 T1, 1- 60000 for AAL2 E1,
1 - 400 for AAL2 signaling (trunking).
|
mastership
|
Specifies the connection as master or slave. 1 = master, 2 = slave (default).
|
remoteConnId
|
Remote connection identifier. This parameter has the format "nodename.slot.port.vpi.vci". (This parameter is used only when mastership is set to 1).
|
•There is now a new way of configuring CAS. The command sequence is:
addln "1" (Assuming line# 1)
cnflnsig "1 1" (Configuring line#1 for CAS signaling type 1)
The addcasvar command can now be executed in any order.
–For wink-start application, use filename as wink-did-dod.o
–For immediate-start application, use filename as immed-did-dod.o
–For ground-start application, use filename as basic-pbx.o
–For wink-start, MF application, use filename as wink-did-dod-mf.o
For example, to add wink-start MF variant, enter the following:
addcasvar winkmf wink-did-dod-mf.o
This can be done at any time, irrespective of whether you had configured the other CAS variants or not.
If a valid filename is not entered, the command displays an error saying that filename has to be one of the above.
Problems Fixed
This section lists the problems that are resolved in the 1.5.x releases.
Problem Fixed in Release 1.5(9)
Table 2 lists the caveat that is resolved in Release 1.5(9).
Table 2 Resolved Caveat for VISM Release 1.5(9)
Bug ID
|
Description
|
CSCea42208
|
VISM stuck in boot aft switchcc; standby did not take over.
|
Problems Fixed in Release 1.5(8)
Table 3 lists the caveats that are resolved in Release 1.5(8).
Table 3 Resolved Caveats for VISM Release 1.5(8)
Bug ID
|
Description
|
CSCdv81919
|
Idle channel suppression (ICS) is not working in the VoIP trunking operating mode.
|
CSCdx71685
|
Idle channel suppression (ICS) one way voice path problem.
|
CSCdx76786
|
When Idle channel suppression (ICS) is disabled using the cnfallcids command, keepalive messages are no longer sent.
|
Problems Fixed in Release 1.5(7)
Table 4 lists the caveats that are resolved in Release 1.5(7).
Table 4 Resolved Caveats for VISM Release 1.5(7)
Bug ID
|
Description
|
CSCdt56908
|
Idle channel suppression fails for AAL2 trunks. Workaround is to use VAD on trunk connection rather than idle channel suppression.
|
CSCdv57222
|
Idle channel suppression is enabled on a CID both voice packets and signaling packets are suppressed; only voice packets should be suppressed.
|
CSCdv77719
|
Idle channel suppression does not engage after a modem call terminates and the codec downspeeds to G.729.
|
CSCdv81693
|
Idle channel suppression does not engage after PBX line alarm conditions clear.
|
CSCdv84047
|
VISM needs to provide a new CLI to configure the ICS and VAD values for all the CIDs in a CID table.
|
CSCdw53331
|
VISM one way voice path problem. VAD frame count incrementing is performed without checking the overflow condition, which causes VAD frames to be classified as unknown. Additionally, VAD considers the unknown classified VAD frames as noise and suppresses them, which silences the voice path for an extended length of time.
|
Problems Fixed in Release 1.5.05
Table 5 and Table 6 list the caveats that are resolved in Release 1.5.05.
.
Table 5 Resolved AAL2 Operating Mode Caveats for VISM Release 1.5.05
Bug ID
|
Description
|
CSCdr22479
|
Headline: PSQM high scores with VAC on.
Description: The PSQM threshold was set to be at 2.5, however, the resulting scores were in the 6.5 range. Post analysis showed that leading edge and trailing edge were missing.
|
CSCdr26132
|
Headline: CAC was enabled even when the connection bandwidth was in excess of the allowed bandwidth.
Description: Added connections (PVC) with a specific PCR, and added CIDS without CAC enabled. Re-enabling CAC should fail to enable the CAC on the card because the current bandwidth was in excess of the allowed bandwidth. Instead of failing to enable CAC, CAC is enabled.
|
CSCdr26900
|
Headline: Upspeeded CID is not down speeded when FAX call made
Description: When the FAX call was made with both the end of the connections were in MASTER mode of CAC, one end of CID upspeeded but the other end did not. After the FAX call was disconnected, the upspeeded end of the CID did not return to the original codec type. Subsequent calls were not able to be made.
Workaround: Configure connection CAC to Slave before making any calls.
|
Table 6 Resolved VoIP Operating Mode Caveats for VISM Release 1.5.05
Bug ID
|
Description
|
CSCdr08976
|
Headline: E1 VISM allows calls with depleted bandwidth.
Description: After 60 call completions, VISM begins to borrow or deplete bandwidth from stable calls to be used in newly setup calls. This results in tone verification failure and calls getting torn down. Once PVC bandwidth has been depleted with active calls, VISM should reject any new incoming calls. Currently it does not.
|
CSCdr13493
|
Headline: VISM E1: ECAN/VAD not disabled during modem call detection
Description: Make a modem call from the PC to the NAS via the DMS/VSC/VISM. The VISM-E1 does not dynamically disable ECAN during the detection of the modem call. After entering the VISM shellconn/CLI to disable ECAN/VAD and ignore ECAN/VAD, and changing jitter = 20 ms, the modem call is established with V.90 mode.
|
Problems Fixed in Release 1.5.04
Table 7 and Table 8 list the caveats that are resolved in Release 1.5.04.
Table 7 Resolved AAL2 Operating Mode Caveats for VISM Release 1.5.04
Bug ID
|
Description
|
CSCdp49340
VoAAL2
|
Headline: cnfcon does not change the PCR
Description: When the value of the PCR parameter is changed through the cnfcon command, VISM does not change the value in the MIB.
|
CSCdp72954
VoAAL2
|
Headline: LOS does not cause VISM to switch clock if VISM is clocking the shelf
Description: When the VISM line is used to clock the MGX shelf, if the VISM gets a loss of signal on the T1 line, or, if the line from which clock is derived is deleted, the PXM does not switch to the secondary clock source as expected. Loss of clock is recognized at the PXM only when the VISM port is down (when a card is reset or if a port is deleted).
|
CSCdr16013
VoAAL2
|
Headline: VISM and 3810 Tx ones (seizures) on last 6 ds0s to pbx.
Description: VISM and 3810 Tx ones (seizures) on last 6 ds0s to pbx. On test bed (pbx loop - ie no 4ESS connection), both 3810 & VISM are transmitting ones on ds0s 19 to 24.
|
Table 8 Resolved VoIP Operating Mode Caveats for VISM Release 1.5.04
Bug ID
|
Description
|
CSCdr17034
VoIP
|
Headline: Unable to detect co2 in transponder mode.
Description: The NTFY message is not forwarded to the CA and COT fails.
|
Problems Fixed in Release 1.5.03
Table 9 lists the caveats that are resolved in Release 1.5.03.
Table 9 Resolved AAL2 Operating Mode Caveats for VISM Release 1.5.03
Bug ID
|
Description
|
CSCdr16005
VoAAL2
|
Headline: Manual call upspeeds by itself after static pops
Description: While testing CCS INC to Frame with 20 Hammer calls up, one modem call up and one manual call, the manual call would have a static pop and then upspeed and downspeed. Testing with CNN on one end of the call, this was happening about every second. With two people talking, it happened much less often but still happened.
|
CSCdr16020
VoAAL2
|
Headline: VISM sending packets to Cisco 3810 when no voice call is active.
Description: VISM sending packets to 3810 w/ no voice call active.
|
CSCdr12039
VoAAL2
|
Headline: VISM bulk stress test call failure.
Description: During test using the VCO4K some degradation in tone shaping was detected. the VCO4k flag these calls as failed. No call drops resulted from this condition.
|
Problems Fixed in Release 1.5.02
Table 10 lists the caveats that are resolved in Release 1.5.02.
Table 10 Resolved Caveat for VISM Release 1.5.02
Bug ID
|
Description
|
CSCdp69061
|
Headline: VISM cards reset during 15 cps test
Description: During a 15 cps test, all VISM cards reset unexpectedly stopping all traffic. Cause is being investigated.
Workaround: None
|
CSCdp68582
|
Headline: Loss of voice quality on PXM to PXM calls
Description: Some voice dropout and clipping experienced during testing on PXM to PXM calls. Cause is being investigated.
Workaround: None.
|
CSCdp66621
|
Headline: Slower data rates when modem calls pass through VISM cards
Description: When modem calls were passed through VISM, the achieved data rates were lower than expected.
Workaround: Modem support is limited to V.34 in this release.
|
Compatibility Notes
This section lists the compatibility matrixes and the bootcode and firmware requirements for the 1.5.x releases.
VISM Software Interoperability with MGX 8850 Platform Software
Table 11 Image Configuration Matrix
Product
|
Boot Image
|
Firmware image
|
PXM1
|
pxm_bkup_1.1.34.fw
|
pxm_1.1.34.fw
|
PXM1-2-T3E3
|
pxm_bkup_1.1.34.fw
|
pxm_1.1.34.fw
|
PXM1-4-155
|
pxm_bkup_1.1.34.fw
|
pxm_1.1.34.fw
|
PXM1-1-622
|
pxm_bkup_1.1.34.fw
|
pxm_1.1.34.fw
|
AX-CESM-8E1
|
cesm_8t1e1_CE8_BT_1.0.02.fw
|
cesm_8t1e1_10.0.11.fw
|
AX-CESM-8T1
|
cesm_8t1e1_CE8_BT_1.0.02.fw
|
cesm_8t1e1_10.0.11.fw
|
MGX-AUSM-8E1/B
|
ausm_8t1e1_AU8_BT_1.0.02.fw
|
ausm_8t1e1_10.0.11.fw
|
MGX-AUSM-8T1/B
|
ausm_8t1e1_AU8_BT_1.0.02.fw
|
ausm_8t1e1_10.0.11.fw
|
MGX-CESM-T3
|
cesm_t3e3_CE8_BT_1.0.02.fw
|
cesm_t3e3_10.0.11.fw
|
MGX-CESM-E3
|
cesm_t3e3_CE8_BT_1.0.02.fw
|
cesm_t3e3_10.0.11.fw
|
AX-FRSM-8E1
|
frsm_8t1e1_FR8_BT_1.0.02.fw
|
frsm_8t1e1_10.0.11.fw
|
AX-FRSM-8E1-C
|
frsm_8t1e1_FR8_BT_1.0.02.fw
|
frsm_8t1e1_10.0.11.fw
|
AX-FRSM-8T1
|
frsm_8t1e1_FR8_BT_1.0.02.fw
|
frsm_8t1e1_10.0.11.fw
|
AX-FRSM-8T1-C
|
frsm_8t1e1_FR8_BT_1.0.02.fw
|
frsm_8t1e1_10.0.11.fw
|
MGX-FRSM-HS2
|
frsm_vhs_VHS_BT_1.0.02.fw
|
frsm_vhs_10.0.11.fw
|
MGX-FRSM-2CT3
|
frsm_vhs_VHS_BT_1.0.02.fw
|
frsm_vhs_10.0.11.fw
|
MGX-FRSM-2T3E3
|
frsm_vhs_VHS_BT_1.0.02.fw
|
frsm_vhs_10.0.11.fw
|
MGX-FRSM-HS1/B
|
frsm_hs1_HS1_BT_1.0.02.fw
|
frsm_hs1_10.0.11.fw
|
MGX-VISM-8T1
|
vism_8t1e1_VI8_BT_1.0.02.fw
|
vism_8t1e1_1.5.09.fw
|
MGX-VISM-8E1
|
vism_8t1e1_VI8_BT_1.0.02.fw
|
vism_8t1e1_1.5.09.fw
|
MGX-RPM-128M/B
|
rpm-boot-mz.121-1.T1
|
rpm-js-mz.121-1.T
|
Table 12 VISM 1.5.x Software Interoperability with other Cisco Products
Product
|
Component
|
Cisco 3810
|
MC3810_A2JSV5_MZ.121_1.XA2
|
Network Management Software:
|
CWM 9.2.08 .SOL.Patch6.tar
|
|
CiscoView
|
CV 4.2 WAN CV 2.09
|
Virtual Switch Controller Software
|
VSC 7.4(6)
|
Table 13 through Table 20 list the software boot and runtime firmware requirements for the 1.5.x releases.
Table 13 VISM 1.5(9) Software Boot and Runtime Firmware Requirements
Board Pair
|
Latest Boot Code Version
|
Minimum Boot Code Version
|
Firmware
|
Latest Firmware Version
|
Minimum Firmware Version
|
MGX-VISM-8T1
|
vism_8t1e_VI8_BT_1.0.02.fw
|
1.0.02
|
vism_8t1e1_1.5.09.fw
|
1.5.09
|
1.5.09
|
MGX-VISM-8E1
|
vism_8t1e_VI8_BT_1.0.02.fw
|
1.0.02
|
vism_8t1e1_1.5.09.fw
|
1.5.09
|
1.5.09
|
Table 14 VISM 1.5(8) Software Boot and Runtime Firmware Requirements
Board Pair
|
Latest Boot Code Version
|
Minimum Boot Code Version
|
Firmware
|
Latest Firmware Version
|
Minimum Firmware Version
|
MGX-VISM-8T1
|
vism_8t1e_VI8_BT_1.0.02.fw
|
1.0.02
|
vism_8t1e1_1.5.0_8.fw
|
1.5.08
|
1.5.08
|
MGX-VISM-8E1
|
vism_8t1e_VI8_BT_1.0.02.fw
|
1.0.02
|
vism_8t1e1_1.5.0_8.fw
|
1.5.08
|
1.5.08
|
Table 15 VISM 1.5(7) Software Boot and Runtime Firmware Requirements
Board Pair
|
Latest Boot Code Version
|
Minimum Boot Code Version
|
Firmware
|
Latest Firmware Version
|
Minimum Firmware Version
|
MGX-VISM-8T1
|
vism_8t1e_VI8_BT_1.0.02.fw
|
1.0.02
|
vism_8t1e1_1.5.0_7.fw
|
1.5.07
|
1.5.07
|
MGX-VISM-8E1
|
vism_8t1e_VI8_BT_1.0.02.fw
|
1.0.02
|
vism_8t1e1_1.5.0_7.fw
|
1.5.07
|
1.5.07
|
Table 16 VISM 1.5.05 Software Boot and Runtime Firmware Requirements
Board Pair
|
Latest Boot Code Version
|
Minimum Boot Code Version
|
Firmware
|
Latest Firmware Version
|
Minimum Firmware Version
|
MGX-VISM-8T1
|
vism_8t1e_VI8_BT_1.0.02.fw
|
1.0.02
|
vism_8t1e1_1.5.0_5.fw
|
1.5.05
|
1.5.05
|
MGX-VISM-8E1
|
vism_8t1e_VI8_BT_1.0.02.fw
|
1.0.02
|
vism_8t1e1_1.5.0_5.fw
|
1.5.05
|
1.5.05
|
Table 17 VISM 1.5.04 Software Boot and Runtime Firmware Requirements
Board Pair
|
Latest Boot Code Version
|
Minimum Boot Code Version
|
Firmware
|
Latest Firmware Version
|
Minimum Firmware Version
|
MGX-VISM-8T1
|
vism_8t1e_VI8_BT_1.0.02.fw
|
1.0.02
|
vism_8t1e1_1.5.0_4.fw
|
1.5.04
|
1.5.04
|
MGX-VISM-8E1
|
vism_8t1e_VI8_BT_1.0.02.fw
|
1.0.02
|
vism_8t1e1_1.5.0_4.fw
|
1.5.04
|
1.5.04
|
Table 18 VISM 1.5.03 Software Boot and Runtime Firmware Requirements
Board Pair
|
Latest Boot Code Version
|
Minimum Boot Code Version
|
Firmware
|
Latest Firmware Version
|
Minimum Firmware Version
|
MGX-VISM-8T1
|
vism_8t1e_VI8_BT_1.0.02.fw
|
1.0.02
|
vism_8t1e1_1.5.0_3.fw
|
1.5.03
|
1.5.03
|
MGX-VISM-8E1
|
vism_8t1e_VI8_BT_1.0.02.fw
|
1.0.02
|
vism_8t1e1_1.5.0_3.fw
|
1.5.03
|
1.5.03
|
Table 19 VISM 1.5.02 Software Boot and Runtime Firmware Requirements
Board Pair
|
Latest Boot Code Version
|
Minimum Boot Code Version
|
Firmware
|
Latest Firmware Version
|
Minimum Firmware Version
|
MGX-VISM-8T1
|
vism_8t1e_VI8_BT_1.0.02.fw
|
1.0.02
|
vism_8t1e1_1.5.0_2.fw
|
1.5.02
|
1.5.02
|
MGX-VISM-8E1
|
vism_8t1e_VI8_BT_1.0.02.fw
|
1.0.02
|
vism_8t1e1_1.5.0_2.fw
|
1.5.02
|
1.5.02
|
Table 20 VISM 1.5.01 Software Boot and Runtime Firmware Requirements
Board Pair
|
Latest Boot Code Version
|
Minimum Boot Code Version
|
Firmware
|
Latest Firmware Version
|
Minimum Firmware Version
|
MGX-VISM-8T1
|
vism_8t1e_VI8_BT_1.0.02.fw
|
1.0.01
|
vism_8t1e1_VI8_1.5_01fw
|
1.5.01
|
1.5.01
|
MGX-VISM-8E1
|
vism_8t1e_VI8_BT_1.0.02.fw
|
1.0.01
|
vism_8t1e1_VI8_15_01.fw
|
1.5.01
|
1.5.01
|
Special Installation and Upgrade Requirements
This section describes how to upgrade the VISM card.
VISM Firmware Download Procedure
To download the VISM firmware, complete the following steps:
Step 1 Download the selected revision of service module firmware into the service module in the selected slot.
a. tftp <node_name or IP address>
b. bin
c. put <backup boot> POPEYE@SM_1_<slot#>.BOOT
d. quit
Step 2 Download the selected firmware files.
To upgrade all VISM cards, proceed to Step 2c. To upgrade an individual card, proceed to Step 2d.
a. tftp <node_name or IP address>
b. bin
c. put <FW file> POPEYE@SM_1_0.FW
quit
d. put <FW file> POPEYE@SM_1_<slot number of card to upgrade>.FW
quit
Note You cannot enter two put commands in the same TFTP session.
Step 3 Proceed to the "VISM Graceful Upgrade to 1.5(9)" section to install the download.
VISM Graceful Upgrade to 1.5(9)
VISM 1.5(9) provides a procedure for the graceful upgrade (one in which the existing VISM configuration is preserved throughout the upgrade procedure) from Releases 1.5.03 through 1.5(8).
Initial Conditions
The following initial conditions are required before the graceful upgrade procedure can be started:
•The MGX 8850 must be configured with at least two VISM cards in a redundant configuration (see the addred command in the MGX 8850 command references for details).
•The VISM cards must be running Release 1.5.03 or higher and configured to the desired configuration.
•The VISM 1.5(9) firmware must have been downloaded to the MGX 8850 (see "VISM Firmware Download Procedure" above for details).
Upgrade Procedure
In this procedure the following conditions apply:
•Two VISM card are involved, one initially active and one initially standby. In the procedure description, the initially active VISM is identified as VISM 1 and the initially standby VISM as VISM 2.
•Old-rev refers to the firmware before the upgrade, 1.5(8) and prior.
•New-rev refers to the 1.5(9) firmware.
Step 1 Log in to the active PXM card (slot 7 or 8).
Step 2 Execute the PXM install command:
install sm <SM slot#> <new-rev>
where:
SM slot# is the slot number of the VISM 1 card (the initially active card) and new-rev is the file name of the 1.5(9) firmware.
Note Use the PXM dspfwrevs command to obtain the new-rev number for Step 2.
This command causes the standby VISM 2 to reset and come up in the "hold" state, running the new-rev firmware. The active VISM 1 is unaffected by this command. At this point the primary firmware is still the old-rev and the secondary firmware is new-rev.
Step 3 Execute the PXM newrev command:
newrev sm <SM slot#> <new-rev>
where:
SM slot# is the slot number of the VISM 1 and new-rev is the filename of the 1.5(9) firmware.
This command causes the VISM 2 to become the active VISM running the new-rev firmware. The previously active VISM 1 changes to a "hold" state and is still running the old-rev firmware. The primary and secondary firmware switches, with the new-rev becoming the primary firmware.
Step 4 Execute the PXM commit command:
commit sm <SM slot#> <new-rev>
where:
SM slot# is the slot number of the standby VISM 1 and new-rev is the filename of the 1.5(9) firmware.
This command causes both VISM cards to run the new-rev firmware. At first, VISM 2 is the active VISM with VISM 1 remaining in the hold state. After a short time, the cards switch automatically with
VISM 1 becoming the active card and VISM 2 the standby card.
The two VISM cards are now back to their original condition except that both cards are now running the new-rev firmware, Release 1.5(9).
Step 5 Log in to the active VISM card and use the display commands (dspendpts, dspcasvar, and so forth) to confirm that the configuration has been preserved through the upgrade process.
It is also recommended that you perform further verifications by making some minor modifications to the configuration, checking that the changes have been executed correctly, and then changing the configuration back again.
VISM Upgrade from 1.5.01 and 1.5.02 to Later Releases
VISM Releases 1.5.01 and 1.5.02 do not provide for graceful upgrades. Upgrading from these releases requires the old configuration to be cleared.
•The resetsys command does not clear the configuration.
•The clrsmcnf command is not supported on VISM cards that have ports and connections.
Follow these steps to successfully load the new VISM configuration:
Step 1 With old PXM and VISM images still loaded, delete all of the following from the VISM cards:
•CIDs
•CCS (in case of a CCS config)
•connections
•endpoints
•lines
•resource partitions
•ports
Step 2 Remove VISM cards from the shelf.
Note THIS STEP IS VERY IMPORTANT.
Step 3 Execute the clrsmcnf command on all VISM cards.
Step 4 Upgrade boot code on PXM using the normal procedure.
Step 5 TFTP the new PXM firmware image and new VISM firmware image. See "Standard Service Module Download Procedure" below for this step.
Step 6 Use the resetsys command to reset the shelf.
Step 7 Insert VISM cards back into the shelf.
The proper databases with the new images are automatically rebuilt.
Standard Service Module Download Procedure
Follow this procedure for service module upgrades. Service module firmware images cannot be downloaded as specific versions in MGX 8850 Release 1.1.22 because only one image can be present on the disk at one instance. Hence the user cannot revert back during the installation process.
Step 1 Download the service module firmware to the shelf:
a. unix-prompt> tftp shelf.ip.address
b. tftp> bin
c. tftp> put vism_8t1e1_1.5.09.fw POPEYE@SM_1_0.FW
Sent 1982672 bytes in 18.3 seconds
Step 2 Make sure that the transfer is successful, by looking at the message displayed on the PXM console after the transfer:
Calculated checksum = 0xd9779bc6 stored checksum = 0xd9779bc6
Step 3 Repeat the above steps for each service module type and for each slot independent firmware.
Note There is no abort command for service module upgrade.
Known Anomalies for VISM
This section contains the known caveats for VISM Release 1.5.x. A brief description of the problem is included with each anomaly ID. A more in-depth discussion is available in the release note enclosure of the problem record in Bug Navigator.
VISM 1.5(9) Anomalies
None.
VISM 1.5(8) Anomaly
Table 21 describes the known anomaly in Release 1.5(8).
Table 21 Anomaly in VISM Release 1.5(8)
Bug ID
|
Description
|
CSCea42208
|
Headline: VISM stuck in boot aft switchcc; standby did not take over.
Problem: Moderately loaded shelf, light traffic.
Workaround: Reset card stuck in boot, which makes the standby take over. Then softswitch to make primary card active.
|
VISM 1.5(7) Anomaly
Table 22 describes the known anomaly in the VISM service module, Release 1.5(7).
Table 22 AAL2 Operating Mode Anomaly for VISM Release 1.5(7)
Bug ID
|
Description
|
CSCdv60608
|
Headline: DTMF Digits failure during the call.
Problem: When a call originates at VISM A and VISM B tests the speech path using digits transmitted from the terminating end (VISM B), a failure rate of 0.1% is observed for Digit ON time less than 80 ms (OFF time fixed at 60 ms). Failure rate increases as ON time is decreased.
The failure rate is observed to be independent of DTMF digit relay being turned ON or turned OFF.
Workaround: Use a digit ON time greater than 120 ms.
|
VISM 1.5.05 Anomalies
Table 23 and Table 24 list the known anomalies in the VISM service module, Release 1.5.05 delivery.
Table 23 VoIP Operating Mode Anomalies for VISM Release 1.5.05
Bug ID
|
Description
|
CSCdr58602
|
Headline: DTMF is not supported for G729 in VoIP.
For VoIP application, DTMF digit relay fails for G.729a and G.729ab codecs. The failure is determined to be due to the digit being leaked out over bearer while simultaneously being relayed as NSE packet.
Workaround: None. Do not use G.729a, G.729ab for VoIP application.
|
Table 24 AAL2 Operating Mode Anomalies for VISM Release 1.5.05
Bug ID
|
Description
|
CSCdr63059
|
Headline: DTMF Digits failure during the call
Problem: When a call originates at VISM A and VISM B tests the speech path using digits transmitted from the terminating end (VISM B), a failure rate of 0.1% is observed for Digit ON time less than 80 ms (OFF time fixed at 60 ms). Failure rate increases as ON time is decreased.
The failure rate is observed to be independent of DTMF digit relay being turned ON or turned OFF.
Workaround: Use a digit ON time greater than 120 ms.
|
VISM 1.5.04 Anomalies
Table 25 and Table 26 list the known anomalies in the VISM service module, Release 1.5.04 delivery.
Table 25 AAL2 Operating Mode Anomalies for VISM Release 1.5.04
Bug ID
|
Description
|
CSCdr22479
|
Headline: PSQM high scores with VAC on.
Description: The PSQM threshold was set to be at 2.5, however, the resulting scores were in the 6.5 range. Post analysis showed that leading edge and trailing edge were missing.
|
CSCdr26132
|
Headline: CAC was enabled even when the connection bandwidth was in excess of the allowed bandwidth.
Description: Added connections (PVC) with a specific PCR, and added CIDS without CAC enabled. Re-enabling CAC should fail to enable the CAC on the card because the current bandwidth was in excess of the allowed bandwidth. Instead of failing to enable CAC, CAC is enabled.
|
CSCdr26900
|
Headline: Upspeeded CID is not down speeded when FAX call made
Description: When the FAX call was made with both the end of the connections were in MASTER mode of CAC, one end of CID upspeeded but the other end did not. After the FAX call was disconnected, the upspeeded end of the CID did not return to the original codec type. Subsequent calls were not able to be made.
Workaround: Configure connection CAC to Slave before making any calls.
|
Table 26 VoIP Operating Mode Anomalies for VISM Release 1.5.04
Bug ID
|
Description
|
CSCdr08976
|
Headline: E1 VISM allows calls with depleted bandwidth.
Description: After 60 call completions, VISM begins to borrow or deplete bandwidth from stable calls to be used in newly setup calls. This results in tone verification failure and calls getting torn down. Once PVC bandwidth has been depleted with active calls, VISM should reject any new incoming calls. Currently it does not.
|
CSCdr13493
|
Headline: VISM E1: ECAN/VAD not disabled during modem call detection
Description: Make a modem call from the PC to the NAS via the DMS/VSC/VISM. The VISM-E1 does not dynamically disable ECAN during the detection of the modem call. After entering the VISM shellconn/CLI to disable ECAN/VAD and ignore ECAN/VAD, and changing jitter=20ms, the modem call is established with V.90 mode.
|
VISM 1.5.03 Anomalies
Table 27 and Table 28 list the known anomalies in the VISM service module, Release 1.5.03 delivery.
Table 27 AAL2 Operating Mode Anomalies for VISM Release 1.5.03
Bug ID
|
Description
|
CSCdp49340
|
Headline: cnfcon does not change the PCR
Description: When the value of the PCR parameter is changed through the cnfcon command, VISM does not change the value in the MIB.
|
CSCdp72954
|
Headline: LOS does not cause Vism to switch clock if VISM clocking the shelf
Description: When the VISM line is used to clock the MGX shelf, if the VISM gets a loss of signal on the T1 line or if the line from which clock is derived is deleted, the PXM does not switch to the secondary clock source as expected. Loss of clock is recognized at the PXM only when the VISM port is down (when a card is reset or if a port is deleted).
|
CSCdr16013
|
Headline: VISM and 3810 Tx ones (seizures) on last 6 ds0s to pbx.
Description: VISM and 3810 Tx ones (seizures) on last 6 ds0s to pbx. On test bed (pbx loop - ie no 4ESS connection), both 3810 and VISM are transmitting ones on ds0s 19 to 24.
|
Table 28 VoIP Operating Mode Anomalies for VISM Release 1.5.03
Bug ID
|
Description
|
CSCdr08976
|
Headline: E1 VISM allows calls with depleted bandwidth.
Description: After 60 call completions, VISM begins to borrow or deplete bandwidth from stable calls to be used in newly setup calls. This results in tone verification failure and calls getting torn down. Once PVC bandwidth has been depleted with active calls, VISM should reject any new incoming calls. Currently it does not.
|
CSCdr13493
|
Headline: VISM E1: ECAN/VAD not disabled during modem call detection
Description: Make a modem call from the PC to the NAS via the DMS/VSC/VISM. The VISM-E1 does not dynamically disable ECAN during the detection of the modem call. After entering the VISM shellconn/CLI to disable ECAN/VAD and ignore ECAN/VAD, and changing jitter=20ms, the modem call is established with V.90 mode.
|
CSCdr17034
|
Headline: Unable to detect co2 in transponder mode.
Description: The NTFY message is not forwarded to the CA and COT fails.
|
VISM 1.5.02 Anomalies
Table 29 and Table 30 list the known anomalies in the VISM service module, Release 1.5.02 delivery.
Table 29 AAL2 Operating Mode Anomalies for VISM 1.5.02
Bug ID
|
Description
|
CSCdp49340
|
Headline: cnfcon does not change the PCR.
Description: When the value of the PCR parameter is changed through the cnfcon command, VISM does not change the value in the MIB.
|
CSCdp72954
|
Headline: LOS does not cause VISM to switch clock if VISM clocking the shelf.
Description: When the VISM line is used to clock the MGX shelf, if the VISM gets a loss of signal on the T1 line or if the line from which clock is derived is deleted, the PXM does not switch to the secondary clock source as expected. Loss of clock is recognized at the PXM only when the VISM port is down (when a card is reset or if a port is deleted).
|
CSCdr12039
|
Headline: VISM bulk stress test call failure
Description: During test using the VCO4K, some degradation in tone shaping was detected. The VCO4K flags these calls as failed. No call drops resulted from this condition.
|
CSCdr16013
|
Headline: VISM and 3810 Tx ones (seizures) on last 6 ds0s to pbx.
Description: VISM and 3810 Tx ones (seizures) on last 6 ds0s to pbx. On test bed (pbx loop - ie no 4ESS connection), both 3810 and VISM are transmitting ones on ds0s 19 to 24.
|
CSCdr16005
|
Headline: Manual call upspeeds by itself after static pops
Description: While testing CCS INC to Frame with 20 Hammer calls up, one modem call up and one manual call, the manual call would have a static pop and then upspeed and downspeed. Testing with CNN on one end of the call this was happening about every second. With two people talking, it happened much less often but still happened.
|
CSCdr16020
|
Headline: VISM sending packets to Cisco 3810 when no voice call is active.
Description: VISM sending packets to 3810 with no voice call active.
|
Table 30 VoIP Operating Mode Anomalies for VISM Release 1.5.02
Bug ID
|
Description
|
CSCdr08976
|
Headline: E1 VISM allows calls with depleted bandwidth.
Description: After 60 call completions, VISM begins to borrow or deplete bandwidth from stable calls to be used in newly setup calls. This results in tone verification failure and calls getting torn down. Once PVC bandwidth has been depleted with active calls, VISM should reject any new incoming calls. Currently it does not.
|
CSCdr13493
|
Headline: VISM E1: ECAN/VAD not disabled during modem call detection
Description: Make a modem call from the PC to the NAS via the DMS/VSC/VISM. The VISM-E1 does not dynamically disable ECAN during the detection of the modem call. After entering the VISM shellconn/CLI to disable ECAN/VAD and ignore ECAN/VAD, and changing jitter=20ms, the modem call is established with V.90 mode.
|
CSCdr17034
|
Headline: Unable to detect co2 in transponder mode.
Description: The NTFY message is not forwarded to the CA and COT fails.
|
VISM 1.5.01 Anomalies
Table 31 lists the known anomalies in the VISM service module, Release 1.5.01 delivery.
Table 31 VISM Release 1.5.01 Anomalies
Bug ID
|
Description
|
CSCdp69061
|
Headline: VISM cards reset during 15 cps test
Description: During a 15 cps test, all VISM cards reset unexpectedly, stopping all traffic. Cause is being investigated.
Workaround: None
|
CSCdp68582
|
Headline: Loss of voice quality on PXM to PXM calls.
Description: Some voice dropout and clipping experienced during testing on PXM to PXM calls. Cause is being investigated.
Workaround: None.
|
CSCdp66621
|
Headline: Slower data rates when modem calls pass through VISM cards.
Description: When modem calls were passed through VISM, the achieved data rates were lower than expected.
Workaround: Modem support is limited to V.34 in this release.
|
VISM 1.0 Anomalies
Table 32 lists the known anomalies in the MGX 8850 VISM service module, Release 1.0 delivery.
Table 32 VISM Release 1.0 Anomalies
Bug ID
|
Description
|
CSCdp20174
|
Symptom: VISM does not recognize LOS
Description: If T1 cables are disconnected from the VISM card, or the connected channel bank is powered off, the VISM card does not detect LOS. The card still acts like the line is connected. Reported by ATT Piscataway, MR:000233, Jan Sussman.
|
|
|
|
CSCdp21467
|
Symptom: VISM ignores echo setting
Description: When sending SGCP messages that tell the VISM to turn on echo cancellation, the actual endpoints setup do not have ECAN turned on.
Workaround: The work around for this issue in VISM 1.0 is to use the shellcon command ccIgnoreLcoEcan. Note that this change via the use of this command is not persistent. This command needs to be re-executed every time VISM is reset/rebooted.
|
|
|
|
|
|
CSCdp32764
|
Symptom: Undeleted Connections existed on VISM after overnight calls
Description: We have set up the VISM to originate and terminate on same T1 line. We ran the overnight calls and we observed that each endpoint had connection associated with it. VSC was sending DLCX message but VISM was responding with 510 NACK message and reason code was - CALL/Endpoint Unknown.
|
|
|
|
Obtaining Documentation
Cisco provides several ways to obtain documentation, 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 on the World Wide Web at this URL:
http://www.cisco.com/univercd/home/home.htm
You can access the Cisco website at this URL:
http://www.cisco.com
International Cisco web sites can be accessed from this URL:
http://www.cisco.com/public/countries_languages.shtml
Documentation CD-ROM
Cisco documentation and additional literature are available in a Cisco Documentation CD-ROM package, which may have shipped with your product. The Documentation CD-ROM is updated monthly and may be more current than printed documentation. The CD-ROM package is available as a single unit or through an annual subscription.
Registered Cisco.com users can order the Documentation CD-ROM (product number DOC-CONDOCCD=) through the online Subscription Store:
http://www.cisco.com/go/subscription
Ordering Documentation
You can find instructions for ordering documentation at this URL:
http://www.cisco.com/univercd/cc/td/doc/es_inpck/pdi.htm
You can order Cisco documentation in these ways:
•Registered Cisco.com users (Cisco direct customers) can order Cisco product documentation from the Networking Products MarketPlace:
http://www.cisco.com/en/US/partner/ordering/index.shtml
•Registered Cisco.com users can order the Documentation CD-ROM (Customer Order Number DOC-CONDOCCD=) through the online Subscription Store:
http://www.cisco.com/go/subscription
•Nonregistered Cisco.com users can order documentation through a local account representative by calling Cisco Systems Corporate Headquarters (California, U.S.A.) at 408 526-7208 or, elsewhere in North America, by calling 800 553-NETS (6387).
Documentation Feedback
You can submit comments electronically on Cisco.com. On the Cisco Documentation home page, click Feedback at the top of the page.
You can e-mail your comments to bug-doc@cisco.com.
You can submit your comments by mail by using the response card 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.
Obtaining Technical Assistance
Cisco provides Cisco.com, which includes the Cisco Technical Assistance Center (TAC) Website, as a starting point for all technical assistance. Customers and partners can obtain online documentation, troubleshooting tips, and sample configurations from the Cisco TAC website. Cisco.com registered users have complete access to the technical support resources on the Cisco TAC website, including TAC tools and utilities.
Cisco.com
Cisco.com offers a suite of interactive, networked services that let you access Cisco information, networking solutions, services, programs, and resources at any time, from anywhere in the world.
Cisco.com provides a broad range of features and services to help you with these tasks:
•Streamline business processes and improve productivity
•Resolve technical issues with online support
•Download and test software packages
•Order Cisco learning materials and merchandise
•Register for online skill assessment, training, and certification programs
To obtain customized information and service, you can self-register on Cisco.com at this URL:
http://www.cisco.com
Technical Assistance Center
The Cisco TAC is available to all customers who need technical assistance with a Cisco product, technology, or solution. Two levels of support are available: the Cisco TAC website and the Cisco TAC Escalation Center. The avenue of support that you choose depends on the priority of the problem and the conditions stated in service contracts, when applicable.
We categorize Cisco TAC inquiries according to urgency:
•Priority level 4 (P4)—You need information or assistance concerning Cisco product capabilities, product installation, or basic product configuration.
•Priority level 3 (P3)—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.
•Priority level 2 (P2)—Your production network is severely degraded, affecting significant aspects of business operations. No workaround is available.
•Priority level 1 (P1)—Your production network is down, and a critical impact to business operations will occur if service is not restored quickly. No workaround is available.
Cisco TAC Website
You can use the Cisco TAC website to resolve P3 and P4 issues yourself, saving both cost and time. The site provides around-the-clock access to online tools, knowledge bases, and software. To access the Cisco TAC website, go to this URL:
http://www.cisco.com/tac
All customers, partners, and resellers who have a valid Cisco service contract have complete access to the technical support resources on the Cisco TAC website. Some services on the Cisco TAC website require a Cisco.com login ID and password. If you have a valid service contract but do not have a login ID or password, go to this URL to register:
http://tools.cisco.com/RPF/register/register.do
If you are a Cisco.com registered user, and you cannot resolve your technical issues by using the Cisco TAC website, you can open a case online at this URL:
http://www.cisco.com/en/US/support/index.html
If you have Internet access, we recommend that you open P3 and P4 cases through the Cisco TAC website so that you can describe the situation in your own words and attach any necessary files.
Cisco TAC Escalation Center
The Cisco TAC Escalation Center addresses priority level 1 or priority level 2 issues. These classifications are assigned when severe network degradation significantly impacts business operations. When you contact the TAC Escalation Center with a P1 or P2 problem, a Cisco TAC engineer automatically opens a case.
To obtain a directory of toll-free Cisco TAC telephone numbers for your country, go to this URL:
http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml
Before calling, please check with your network operations center to determine the level of Cisco support services to which your company is entitled: for example, SMARTnet, SMARTnet Onsite, or Network Supported Accounts (NSA). When you call the center, please have available your service agreement number and your product serial number.
Obtaining Additional Publications and Information
Information about Cisco products, technologies, and network solutions is available from various online and printed sources.
•The Cisco Product Catalog describes the networking products offered by Cisco Systems as well as ordering and customer support services. Access the Cisco Product Catalog at this URL:
http://www.cisco.com/en/US/products/products_catalog_links_launch.html
•Cisco Press publishes a wide range of networking publications. Cisco suggests these titles for new and experienced users: Internetworking Terms and Acronyms Dictionary, Internetworking Technology Handbook, Internetworking Troubleshooting Guide, and the Internetworking Design Guide. For current Cisco Press titles and other information, go to Cisco Press online at this URL:
http://www.ciscopress.com
•Packet magazine is the Cisco monthly periodical that provides industry professionals with the latest information about the field of networking. You can access Packet magazine at this URL:
http://www.cisco.com/en/US/about/ac123/ac114/about_cisco_packet_magazine.html
•iQ Magazine is the Cisco monthly periodical that provides business leaders and decision makers with the latest information about the networking industry. You can access iQ Magazine at this URL:
http://business.cisco.com/prod/tree.taf%3fasset_id=44699&public_view=true&kbns=1.html
•Internet Protocol Journal is a quarterly journal published by Cisco Systems for engineering professionals involved in the design, development, and operation of public and private internets and intranets. You can access the Internet Protocol Journal at this URL:
http://www.cisco.com/en/US/about/ac123/ac147/about_cisco_the_internet_protocol_journal.html
•Training—Cisco offers world-class networking training, with current offerings in network training listed at this URL:
http://www.cisco.com/en/US/learning/le31/learning_recommended_training_list.html
CCIP, CCSP, the Cisco Arrow logo, the Cisco Powered Network mark, the Cisco Systems Verified logo, Cisco Unity, Follow Me Browsing, FormShare, iQ Net Readiness Scorecard, Networking Academy, and ScriptShare are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, The Fastest Way to Increase Your Internet Quotient, and iQuick Study are service marks of Cisco Systems, Inc.; and Aironet, ASIST, BPX, Catalyst, CCDA, CCDP, CCIE, CCNA, CCNP, Cisco, the Cisco Certified Internetwork Expert logo, Cisco IOS, the Cisco IOS logo, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Empowering the Internet Generation, Enterprise/Solver, EtherChannel, EtherSwitch, Fast Step, GigaStack, Internet Quotient, IOS, IP/TV, iQ Expertise, the iQ logo, LightStream, MGX, MICA, the Networkers logo, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, SlideCast, SMARTnet, StrataView Plus, Stratm, SwitchProbe, TeleRouter, TransPath, and VCO are registered trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and certain other countries.
All other trademarks mentioned in this document or Web site 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. (0303R)
Copyright © 2003, Cisco Systems, Inc.
All rights reserved.
