Table Of Contents
Release Notes for Cisco Voice Switch Service Module (VXSM) Release 5.4.20
Contents
About This Release
New Feature in Release 5.4.20.201
New Feature in Release 5.4.20.200
New Feature in Release 5.4.00.201
DTMF Squelching
For H.248
For XGCP
New Features in Release 5.4.00.200
Call Rate Performance Support
SNMPv3
V.110 Support for AAL2 Trunking Applications
Unique Virtual Gateway Domain Name for H.248
ptime Support for H.248
Firmware Images
Upgrading from an Earlier VXSM Release
Interrupted Procedure Recovery
Feature Clarifications
Online Diagnostics Feature as Applied to VXSM
DSP Resources Under Mixed Codec Conditions
VXSM Management Information Base
Service Module Support by Platform
Compatibility
Caveats for VXSM Release 5.4.00
Open Caveats in Release 5.4.20.201
Open Caveats in Release 5.4.20.200
Open Caveats in Release 5.4.00.201
Open Caveats in Release 5.4.00.200
Resolved Caveats in Release 5.4.20.201
Resolved Caveats in Release 5.4.20.200
Resolved Caveats in Release 5.4.00.201
Removed Caveats in Release 5.4.00.200
Resolved Caveats in Release 5.4.00.200
Related Documentation
Obtaining Documentation, Obtaining Support, and Security Guidelines
Release Notes for Cisco Voice Switch Service Module (VXSM) Release 5.4.20
Revised: August 20, 2010, OL-16164-01
Contents
The content of this document is arranged into the following major sections:
About This Release
New Feature in Release 5.4.20.201
New Feature in Release 5.4.20.200
New Feature in Release 5.4.00.201
DTMF Squelching
New Features in Release 5.4.00.200
Call Rate Performance Support
SNMPv3
V.110 Support for AAL2 Trunking Applications
Unique Virtual Gateway Domain Name for H.248
ptime Support for H.248
Firmware Images
Upgrading from an Earlier VXSM Release
Interrupted Procedure Recovery
Feature Clarifications
Online Diagnostics Feature as Applied to VXSM
DSP Resources Under Mixed Codec Conditions
VXSM Management Information Base
Service Module Support by Platform
Compatibility
Caveats for VXSM Release 5.4.00
Related Documentation
Obtaining Documentation, Obtaining Support, and Security Guidelines
About This Release
Version .201 of Release 5.4.20 is a patch release for VXSM and introduces no new features. The resolved caveats for Versions .201 are listed in Table 7.
The VXSM Release 5.4.20 follows VXSM Release 5.4.00. The resolved caveats for Release 5.4.20 are listed in Table 8.
Version .201 of Release 5.4.00 is a patch release for VXSM that introduces a new feature (see DTMF Squelching). The resolved caveats for Versions .201 are listed in Table 9.
The VXSM Release 5.4.00 follows VXSM Release 5.3.10. The resolved caveats for VXSM Release 5.4.00 are listed in Table 9.
The Voice Switch Service Module (VXSM) product is supported by the MGX 8880 Media Gateway and the MGX 8850 Multiservice Switch. Refer to their respective release notes for platform and version level support guidelines.
Note 
To verify that you have the latest version of Cisco IOS required to support the new features included in this release, please check Cisco IOS availability status at Cisco.com.
The VXSM software release notes are supported by Cisco Voice Switch Services (VXSM) Configuration Guide, Release 5.4 and Cisco Voice Switch Services (VXSM) Command Reference, Release 5.4, both of which are available on cisco.com.
New Feature in Release 5.4.20.201
This release has no new VXSM features.
New Feature in Release 5.4.20.200
This release has no new VXSM features.
New Feature in Release 5.4.00.201
DTMF Squelching
This release contains the enhancements to completely squelch DTMF digits. This feature can be provisioned using the CLI commands shown below.
Note These CLI commands are not new for this release. They already exist in the product.
For H.248
Syntax Description
cnfh248profdtmf <Index> <DigitOnDuration> <DtmfPauseDuration> <DetectLongDigitDuration> <SuppressBearerDigit>
Option SuppressBearerDigit should be set to 1 to enable DTMF squelching.
For XGCP
Syntax Description
cnfxgcpprofdtmf <ProfileIndex> <SuppressBearerDigit>
Option SuppressBearerDigit should be set to 1 to enable DTMF squelching.
New Features in Release 5.4.00.200
Release 5.4.00 is a significant release with several major new software features over Release 5.3.10.
This release has no new VXSM hardware features.
The new software features include:
•Call Rate Performance Support
•SNMPv3
•V.110 Support for AAL2 Trunking Applications
•Unique Virtual Gateway Domain Name for H.248
•ptime Support for H.248
Call Rate Performance Support
VXSM OC3 Card supports the following call rates:
•In MGCP, the maximum CPS supported is 60 (without signaling). If signaling (M3UA/IUA/RUDP) is configured, then the maximum supported CPS is 35.
•In H.248, the maximum CPS supported is 85 (without signaling). If signaling (M3UA/IUA) is configured, then the maximum supported CPS is 35.
SNMPv3
Simple Network Management Protocol Version 3 (SNMPv3) is an standards-based protocol for network management. SNMPv3 provides secure access to devices using a combination of authentication and encryption of packets over the network. This assures that data can be collected securely from SNMP devices and that configuration messages cannot be viewed or altered.
The security features provided in SNMPv3 are:
•Message integrity—Ensuring that a packet has not been tampered with in-transit.
•Authentication—Determining that the message is from a valid source.
•Encryption—Scrambling the contents of a packet to prevent it from being seen by an unauthorized source.
V.110 Support for AAL2 Trunking Applications
VXSM supports the detection and handling of V.110 traffic used for modem and fax devices on mobile networks. This feature is used in conjunction with the AAL2 Trunking function. Upon detection of a V.110 bit pattern, VXSM provides a Clear Channel circuit for the duration of the V.110 (data) session.
The V.110 feature adds the following commands:
cnfeventmapping -v110 Configure V.110 events mapping
dspeventmapping -v110 Display V.110 events mapping
addccdprof Add clear channel data profile
cnfccdprof Configure clear channel data profile
delccdprof Delete clear channel data profile
dspccdprof Display clear channel data profile
dspccdprofs Display clear channel data profiles
Unique Virtual Gateway Domain Name for H.248
For H.248 applications, a VXSM card has the capability of being partitioned into a number of virtual media gateways (VMGs); where each VMG is a logical entity residing within a physical VXSM card. This feature permits each virtual gateway to be assigned its own unique domain name.
The Unique Virtual Gateway Domain Name feature modifies the following commands:
addh248assoc Add H.248 association
cnfh248mg Configure H.248 media gateway
dsph248assoc List configuration of H.248 Association
dsph248mg List configuration of H.248 Gateway
ptime Support for H.248
The ptime (packet period) attribute is defined in RFC 2327 as "the length of time in milliseconds represented by the media in a packet." ptime specifies the packet period for a codec, and maxptime specifies the maximum packet period.
The ptime and maxptime attributes are optional SDP attributes that can be sent down by the MGC in the local or remote descriptor SDP.
In release earlier than 5.4.00, the values of ptime and maxptime were ignored and the values configured on the platform were used.
Firmware Images
For each VXSM card type (OC-3/STM-1, T1/E1, or T3), two firmware images are available, namely, Non-CALEA and CALEA. When placing an order, the user must specify whether a Non-CALEA or CALEA image is required.
The Non-CALEA image supports three Media Gateway Control protocols, namely, H.248, MGCP, and TGCP. However, VXSM supports only one protocol at a time. The user must choose between the H.248, MGCP, and TGCP protocols when the image is first loaded from the PXM using the setrev command.
The CALEA image supports TGCP and MGCP only. The protocol must be explicitly selected when the image is loaded from the PXM using the setrev command.
VXSM supports two different codec templates; "TGW/wireline" and "Cable." The Cable template can be used only in conjunction with TGCP.
Upgrading from an Earlier VXSM Release
VXSM can be gracefully upgraded (configuration is preserved) from VXSM Release 5.2.10 or later so long as the original and the upgraded images are both either CALEA or Non-CALEA.
Note Upgrading from CALEA to Non-CALEA, or Non-CALEA to CALEA, is NOT supported.
When loading or upgrading a boot or runtime image to a VXSM card, users must observe the following caution:
Caution If an H.248 association is active with SrvChgProfile (used in service change message) as BT_TGW in 5.3.x.x release, after graceful upgrade to 5.4.00, the association will continue to use BT_TGW, but new association(s) cannot be added with SrvChgProfile as BT_TGW.
From the 5.4.00 release onward, the BT_TGW SrvChgProfile is no longer available. All new associations must be added using either etsi_tgw or CISCO_TGW.
Warning Many of the commands involved in loading or upgrading boot and runtime images can take several minutes to execute completely. If the user resets or otherwise disturbs the VXSM card during a loading or upgrading process, the card can easily be damaged even to the extent that it must be returned to the factory for repair.
In particular:
Do not reset VXSM or PXM cards manually or through commands such as resetcd or resetsys
Do not save all MGX configurations with commands such as saveallcnfs.
Do not toggle primary/secondary cards through commands such as switchredcd, delred
Do not change the name of software image before or during the upgrade
Do not change any configuration of active primary card during the upgrade
THE REAPPEARANCE OF THE COMMAND PROMPT AFTER A COMMAND IS ENTERED DOES NOT INDICATE THAT THE IMAGE LOAD OR UPGRADE HAS BEEN COMPLETED.
After the execution of the burnboot, clrsmcnf, loadrev, or setrev commands, the user must execute either a dspcds or dsprev command periodically to verify that the state of the VXSM card being loaded or upgraded is either Active, Standby, or Failed.
ONLY WHEN THE CARD IS DISPLAYED TO BE IN ONE OF THESE STATES IS IT SAFE TO GO TO THE NEXT STEP.
If the upgrade procedure is interrupted for reasons outside the control of the user (for example, a power outage), see "Interrupted Procedure Recovery" below for instructions.
Interrupted Procedure Recovery
In the event that a VXSM software upgrade procedure is interrupted (for example, power outage), and both Primary and Secondary are stuck in 'Failed-U' state, perform the following procedure
Step 1 Execute the abortrev command:
abortrev <PrimarySlot> <NewImageRevision>
Step 2 If the primary VXSM becomes "Failed/Active" (out of Failed-U/Active"), then execute the resetcd command
resetcd <PrimarySlot>
Step 3 If the secondary VXSM becomes "Failed/Active" (out of Failed-U/Active"), then execute the resetcd command:
resetcd <SecondarySlot>
Step 4 Both primary and secondary VXSM cards should now have their original SW image and original DB
Feature Clarifications
Online Diagnostics Feature as Applied to VXSM
The online diagnostics feature as implemented on the PXM45 card is supported on VXSM. When enabled, using the PXM45 cnfdiag command, this feature performs non-intrusive diagnostics tests that use four of the VXSM G711 DSP resources.
If the user executes the VXSM dspdspcodecpools command, the resulting display shows the four G711 DSP resources being used (for diagnostics) and subtracts them from the remaining available codecs (see example below).
mgx.3.VXSM.a > dspdspcodecpools
=====================================================================
=====================================================================
Codec pool Current utilized Current available
capacity (#DSP chans) capacity (#DSP chans)
========== ===================== =====================
G711 family/HDLC 179 7885
G729/G726/T.38 family 0 3919
In this example, 175 G711 calls have been established along with four G711 resources used for diagnostics.
The online diagnostics feature does not reduce the maximum number of 8064 G711 DSP resources available for calls on the VXSM card. If the number of call requests on the VXSM is sufficiently high, the online diagnostic feature is disabled automatically and the four codecs are made available for active calls.
DSP Resources Under Mixed Codec Conditions
When the same codec is used to setup calls on the gateway the available DSP resources will be fully utilized. However when different codecs are used to setup calls the amount of utilizable DSP resources may be limited in certain cases due to resource fragmentation.
Fragmentation is said to have occurred when the available capacities on two different DSP resources have enough available capacity to support a call of a particular codec type but cannot support that codec type individually.
Consider two DSP resources whose available capacity is 1 unit each making the total available capacity 2 units. However a codec that requires 2 units cannot be supported in the system because the available capacities have been fragmented across the individual DSP resources.
The DSP allocation algorithm on VXSM does make an attempt to smooth the effects of fragmentation. Fragmentation can happen because the pattern of future calls cannot be predicted beforehand.
VXSM Management Information Base
The VXSM Management Information Base (MIB) Version 5.4 is available to users with CCO accounts who can access the MIB and VXSM software on-line at: http://www.cisco.com/public/sw-center/sw-wan.shtml
Step 1 Log on to http://www.cisco.com/public/sw-center/sw-wan.shtml
Step 2 Locate the VXSM platform (either VXSM 8880 or VXSM 8850) and click the down arrow to expand the "Select Release Level" drop down menu.
Step 3 Select the desired MIB release level (for example, Release 5400) to display a list of downloadable files.
Step 4 Click on the desired file (for example, mgx8850-fw-5400.tar).
Step 5 Read the license agreement and, if approved, click Accept.
Step 6 In the Software Download dialog box, click on Download: filename (where filename is the name of the file selected for download). This step starts the download procedure.
Step 7 Follow the normal file download procedure for your computer.
Step 8 When the file has been downloaded, untar or unzip the downloaded file. The MIB file is included in the downloaded file and is listed as a tar file (for example mgx8850rel5400mib.tar).
Step 9 Untar the MIB file to display its contents.
Service Module Support by Platform
Service Module
|
MGX8880
|
MGX8850
|
PXM45/C
|
PXM1
|
PXM45/B
|
PXM45/C
|
PXM1E
|
MGX-RPM-XF-512
|
Yes
|
|
Yes
|
Yes
|
No
|
MGX-RPM-PR-512
|
Yes
|
|
Yes
|
Yes
|
Yes
|
VISM-PR-8T1
|
Yes
|
Yes
|
Yes
|
Yes
|
Yes
|
VISM-PR-8E1
|
Yes
|
Yes
|
Yes
|
Yes
|
Yes
|
AXSM-1-2488/B
|
Yes
|
|
Yes
|
Yes
|
|
AXSM-16-T3/E3/B
|
Yes
|
|
Yes
|
Yes
|
|
AXSM-16-155-XG
|
Yes
|
|
Yes
|
Yes
|
|
AXSM-8-622-XG
|
Yes
|
|
Yes
|
Yes
|
|
MGX-VXSM-155
|
Yes
|
|
No
|
Yes
|
|
MGX-VXSM-T1E1
|
Yes
|
|
No
|
Yes
|
|
MGX-VXSM-T3
|
Yes
|
|
No
|
Yes
|
|
MPSM-T3E3-155
|
No
|
|
Yes
|
Yes
|
Yes
|
MPSM-16-T1E1
|
Yes
|
|
Yes
|
Yes
|
Yes
|
RCON-1TO5-8850
|
Yes
|
|
|
Yes
|
|
Compatibility
Note VXSM Release 5.4.20 is supported only with PXM-45/C.
VXSM software interoperability with the MGX 8880 Media Gateway or the Cisco MGX 8850 (PXM45) Multiservice Switch platform software is listed in Table 1.
Table 1 VXSM 5.4.20.201 Software Interoperability
Product
|
Latest Firmware
|
Min. Firmware
|
PXM45
|
5.4.30.200
|
5.4.00.202
|
MGX-RPM-XF-512
|
12.4(15)T1
|
12.4(6)T1
|
CWM
|
15.4.00
|
15.4.00
|
CTM
|
8.5
|
8.0
|
VISM-PR
|
3.3.30
|
3.3.30
|
AXSM-16-T3/E3/B
|
5.4.30.200
|
5.4.00
|
AXSM-16-155-XG
|
5.4.30.200
|
5.4.00
|
AXSM-8-622-XG
|
5.4.30.200
|
5.4.00
|
MPSM-16-T1E1
|
5.4.30.200
|
5.4.00
|
MPSM-T3E3-155 (8850 only)
|
5.4.30.200
|
5.4.00
|
BTS
|
5.0(1)V05
|
4.4
|
PGW
|
9.7.3
|
9.5.2
|
Cisco 2600 Series Routers
|
c2600-ipvoice-mz.123-9.13.T
|
c2600-ipvoice-mz.123-9.13.T
|
Cisco 2600 for use as an
IP Transfer Point
|
c2600-itp-mz.122-21.SW bin
|
c2600-itp-mz.122-21.SW bin
|
Cisco 3700 Series Routers
|
c3725-ipvoice-mz,123-9.13.T
|
c3725-ipvoice-mz,123-9.13.T
|
Cisco ATA 188
|
3.2.0 for SIP/MGCP/H323
|
3.2.0 for SIP/MGCP/H323
|
Linksys PAP2 Phone Adapter
|
Version 2.0.6 (LS)
|
Version 2.0.6 (LS)
|
Linksys RT31 Router
|
Version 1.27.01
|
Version 1.27.01
|
Sipura 2100 ATA
|
Version 3.2.3
|
Version 3.2.3
|
Table 2 describes the software images available for Release 5.4.20.201 for VXSM.
Table 2 Software Images for Release 5.4.20.201 for VXSM
Board Pair
|
Latest Boot Code Version
|
Minimum Boot Code Version
|
Firmware
|
MGX-VXSM-155, CALEA
|
vxsm_005.004.020.201_bt.fw
|
vxsm_005.004.020.200_bt.fw
|
vxsm_005.054.020.201.fw
|
MGX-VXSM-155, Non-CALEA
|
vxsm_005.004.020.201_bt.fw
|
vxsm_005.004.020.200_bt.fw
|
vxsm_005.004.020.201.fw
|
MGX-VXSM-T1E1, CALEA
|
vxsm_005.004.020.201_bt.fw
|
vxsm_005.004.020.200_bt.fw
|
vxsm_005.054.020.201.fw
|
MGX-VXSM-T1E1, Non-CALEA
|
vxsm_005.004.020.201_bt.fw
|
vxsm_005.004.020.200_bt.fw
|
vxsm_005.004.020.201.fw
|
MGX-VXSM-T3, CALEA
|
vxsm_005.004.020.201_bt.fw
|
vxsm_005.004.020.200_bt.fw
|
vxsm_005.054.020.201.fw
|
MGX-VXSM-T3, Non-CALEA
|
vxsm_005.004.020.201_bt.fw
|
vxsm_005.004.020.200_bt.fw
|
vxsm_005.004.020.201.fw
|
Caveats for VXSM Release 5.4.00
This section describes software caveats for the various versions of Release 5.4.00.
Open Caveats in Release 5.4.20.201
Table 3 Open Software Caveats in VXSM Release 5.4.20.201
DDTS Issue
|
Description
|
CSCsq83555
|
Headline: XGCP: VXSM card crashes after switchover in load with COT enabled.
Symptom: VXSM Card goes into Failed State after switchover.
Conditions: The VXSM card goes into failed state when:
•Configure the VXSM card with cable codec template.
•Enable COT on BTS for each call.
•Start load (approximately1500 calls at 15 cps).
•Perform switchover.
Workaround: None.
|
CSCsq83631
|
Headline: Echo-cancellation is disabled after mid call codec change from CCD to any other codec.
Symptom: Echo-cancellation is disabled after mid call codec change from CCD to any other codec.
Conditions: Midcall codec change from CCD to any other codec with echo cancellation enabled.
Workaround: None.
|
Open Caveats in Release 5.4.20.200
Table 4 Open Software Caveats in VXSM Release 5.4.20.200
DDTS Issue
|
Description
|
CSCsm52388
|
Headline: VXSM resets: DC heartbeat fail fatal along with BCDRV error message.
Symptom: VXSM resets with the message, DC heartbeat fail Fatal and BCDRV Error.
Conditions: None.
Workaround: None.
|
CSCsm66311
|
Headline: Notify entity remain 0.0.0.0 even after configuring MGC (cnfxgcpmgcgrp)
Symptom: Wrong Notify entity even after configuring MGC
Conditions: The wrong notify entity symptom is observed in the following scenario:
•Configure single MGC IP using the command cnfxgcpmgc <ip address>
•Delete the single MGC IP configuration setting using the command cnfxgcpmgc 0.0.0.0
•Add MGC group configuration using the commands addmgcdn, addmgcip and addmgcgrpmgc
•Configure the active MGC group using the command cnfxgcpmgcgrp
Send a CRCX followed by RQNT for some event. Check the notify entity in the output of dspxgcpendptcon <end pt> 2. It will display 0.0.0.0 instead of notify entity of the MGC group configuration.
Workaround: This is a display issue without any impact on the notification process of the gateway. As a workaround, bring the gateway out of service using the command cnfgwoos 3 and then in service using cnfgwis. This will update the notify entity with the latest entries present in MGC group configuration.
|
CSCsj41671
|
Headline: MGCP VoIP: TTY upspeed occurs with wrong encoding type
Symptom: When bringing up a TTY call, the upspeed occurs but the codec being used for the upspeed is incorrect. It uses G711u in E1 mode while it should use G711A, thus impacting the quality of the call.
Conditions: Not Known. This issue is seen intermittently.
Workaround: Configure the upspeed codec to some other upspeed codec say G.726. Again configure the upspeed codec as G711a. Subsequent upspeed will work fine.
|
CSCsk94294
|
Headline: IUA-SLT: Fax failure when T.38 traffic is high - around 10% of total VXSM call capacity.
Symptom: T.38 Fax failures with channel exceptions.
Conditions: The failure is only seen under high ratio (>10%) of T.38 calls.
Workaround: None.
|
CSCsl41112
|
Headline: TGCP-CALEA: Wrong counters increment for CALEA calls after switchover.
Symptom: In dspxgcpcaleacalls number of CALEA call counter does not increment properly when a VXSM switchover is performed after an upspeed.
Conditions: CALEA calls with switchover.
Workaround: None.
|
CSCsk58269
|
Headline: Active card reset due to memory leak in MGCP application.
Symptom: Active card resets due to memory leak.
Conditions: The issue occurs on nodes running T.38 calls. Nodes running Fax pass through are working fine.
Workaround: None.
|
CSCso17343
|
Headline: RTCP control messages in T.38 mode leads to DSP crash.
Symptom: VXSM reset due to DSP Crash.
Conditions: DSP receives RTCP control message when ENCAP_NONE(used for T38 mode).
Workaround: None.
|
CSCso14820
|
Headline: XGCP: Standby fails on switchover with 8K subscriber and mid-call modify.
Symptom: Standby fails on switchover with 8K calls at 40 cps and mid-call codec change.
Conditions: Standby fails on switchover with > 6K calls at 40 cps and mid-call codec change on 40 calls at 1 cps.
Workaround: None.
|
Open Caveats in Release 5.4.00.201
Table 5 Open Software Caveats in VXSM Release 5.4.00.201
DDTS Issue
|
Description
|
CSCek54023
|
Headline: DSP exception while running the mix codec codecs with COT enabled
Symptom: Call setup or call modification failure is seen on calls that are affected by this non-fatal error. This error also results in associated PXM logs indicating a DSP Channel EXCEPTION.
Conditions: This issue was seen twice in an overnight run with a single codec of G.711. There is no permanent damage at the card level due to this error. The error only affects single calls. Subsequent calls on the same TDM endpoint will be unaffected by the previous occurrence of this error.
Workaround: None.
|
CSCek65811
|
Headline: cnfgwis gives error message when the GW is in forced OOSstate already
Symptoms: cnfgwis command fails to bring VXSM Gateway state back to in-service.
Conditions: cnfgwis command fails after cnfgwoos command execution with error "Out of service operation is going on, wait for a while."
Workaround: VXSM card reset.
|
CSCek69535
|
Headline: hung calls in midcall codec chng when no bearer channel available
Symptoms: When near to maximum capacity call is made and codec is modified to a different codec family, few modify failures happen.
Conditions: When channel capacity required for new codec is more than the previous one and the DSP core, where the channel was allocated is full then modify doesn't happen successfully. This happens even if some channels in other DSP core are free.
Workaround: None.
|
.
Open Caveats in Release 5.4.00.200
Table 6 Open Software Caveats in VXSM Release 5.4.00.200
DDTS Issue
|
Description
|
CSCek69535
|
Headline: hung calls in midcall codec change when no bearer channel is available.
Symptom: When channel capacity required for new codec is more than the previous one and the dsp core, where the channel was allocated is full then modify doesn't happen successfully. This happens even if some channels in other DSP core are free.
Condition: When near to maximum capacity call is made and codec is modified to a different codec family, few modify failures happen.
Workaround: None.
|
CSCek65811
|
Headline: cnfgwis gives error message when the GW is already in forced OOSstate.
Symptom: cnfgwis command fails after cnfgwoos command execution with error "Out of service operation is going on, wait for a while."
Condition: cnfgwis command fails to bring VXSM Gateway state back to in-service.
Workaround: VXSM card reset.
|
CSCek54023
|
Headline: DSP exception while running the mix codec codecs with COT enabled.
Symptom: Call setup or call modification failure is seen on calls that are affected by this non-fatal error. This error also results in associated PXM logs indicating a DSP Channel EXCEPTION.
Condition: This issue was seen twice in an overnight run with a single codec of G.711. There is no permanent damage at the card level due to this error. The error only affects single calls. Subsequent calls on the same TDM endpoint will be unaffected by the previous occurrence of this error.
Workaround: There is no workaround for this problem at this time. It has not been completely ascertained whether the issue does not occur with COT disabled or with single codecs.
|
.
Resolved Caveats in Release 5.4.20.201
Table 7 Resolved Anomalies in Release 5.4.20.201
Anomaly ID
|
Description
|
CSCsq86483
|
506 observed when signal "SG { ct/rsp }" is applied on TDM termination.
|
CSCsk94294
|
IUA-SLT: Fax failure at high T.38 traffic around 10% of total VXSM cap.
|
CSCek61396
|
VXSM Crashes with audit on RTP in Null Context
|
CSCsq50340
|
Race condition in Modify and SSRC collision resulted in Nacking of Modify
|
CSCsm07555
|
When inact timer sets to 0 then call returns to voice for HS modulation.
|
CSCsq50528
|
CRML-1-REDM_DELCON_FAI are logged on PXM quite frequently
|
CSCsq52529
|
MGCP:Inconsistent VAD in Primary and Secondary on Mid call codec change.
|
CSCsq72893
|
Modify to T38 with remote empty leads to "Unsupported media type"
|
CSCsq67724
|
FTimer in cnfl2as command is not functional after configuration.
|
CSCsq58032
|
Data bound exception: on standby, when different 'c' lines are sent.
|
CSCsq62940
|
Modify to IPIP call leads to 422 {"syntax error in Action"}.
|
CSCsq02397
|
Modified RTP term name (Lower Case) in response of Add.
|
CSCsj41671
|
MGCP VoIP: TTY upspeed occurs with wrong encoding type.
|
CSCsm52388
|
VXSM resets with DC heartbeat fail Fatal along with BCDRV Error message.
|
CSCso14820
|
XGCP:Standby fails on switchover with 8K subscriber and mid-call modify
|
CSCso89555
|
VXSM returns 500 Error when RTP stats requested in T.38 mode.
|
CSCso37667
|
CACing is not proper after VXSM downspeed in CA controlled T38.
|
CSCso71748
|
Bearer channel contention between LAPD and BLV channel during INIT time.
|
CSCso92744
|
MGCP: Tones should be programmed at DSP based on eventmapping configuration.
|
CSCso47028
|
LAPD: The parameter name of a stat is wrong in CLI.
|
CSCso64336
|
FAX/MODEM upspeed fails on midcall codec change followed by VXSM switchover.
|
CSCso46707
|
Cannot delete VIF when ss7link is configured on 1st DS0 and VIF on 2nd.
|
CSCso40195
|
VAD mismatch after VXSM downspeeds in a CA T38 call- remote port change
|
CSCso85969
|
cnfpathoos is not logged in PXM log and the endpoints are in forcedOOS but the call is through.
|
CSCsq45547
|
VXSM core dumps when reaching 780 contexts using SCTP.
|
CSCsl02645
|
DSP crash due to wrong value of VIF size(pkt period) for G.729 and G.711.
|
CSCsq33740
|
DSP Image Checkin 11.2.10.16
|
CSCso89302
|
IUA-SLT:"MEGA-1-INNSUFT_RESOURC" PXM logs observed during VXSM switch
|
CSCsl41112
|
TGCP-CALEA:Wrong Counters increment for calea calls after switchover.
|
CSCsm66311
|
Notify entity remain 0.0.0.0 even after configuring MGC (cnfxgcpmgcgrp)
|
CSCso57402
|
RSIP-restart is not received after small duration line alarm clears on E1
|
CSCso59549
|
IUA-MGCP SLT: IUA chunks failures observed in voice+fax+modem load.
|
CSCso53222
|
High Call Failures with 1AESS Signaling enabled on trunks and COT sent.
|
CSCso57777
|
During VXSM upgrade from 5.4(0.201) to 5.4(20.200), domain name is lost.
|
CSCso34779
|
500 observed when the remote contains rtpmap for the static payload type
|
CSCso80286
|
Setting Initial Aggressiveness Value to -32K instead of default value 0.
|
CSCso39934
|
mgcDirectOOS association goes to inservice state after switchover
|
CSCsm96820
|
H.248: Incorrect CAC utilization for ClearChannel codec on sending FAX
|
CSCso69123
|
Multiple Transition in single request cmd leads to no response from VXSM
|
CSCso83202
|
Fax pass through is not working due to early detection of CNG tone.
|
CSCsq06487
|
Illegal VIF Size sent to DSP API for G.729a/G.729ab codecs
|
CSCsk58269
|
The active card resets due to memory leak in MGCP application
|
CSCso52286
|
[H.248]VXSM fails to notify ANS on detecting CED after 1300 Hz tone
|
CSCsq09409
|
Checkin DSP image 11.2.10.15
|
CSCso94679
|
xGCP: Remote descriptor does not return AUCX response after switchover
|
Resolved Caveats in Release 5.4.20.200
Table 8 Resolved Anomalies in Release 5.4.20.200
Anomaly ID
|
Description
|
CSCsk51808
|
VXSM card cannot sync with CWM due to usage of memory by VIFs that is allocated for config file upload.
|
CSCsk42708
|
Memory leak found in VXSM Standby card
|
CSCsk63526
|
DSM buffers exhausted due to repeated close channel requests by CRML
|
CSCsk46107
|
Hung RTP ccb due to toolkit journaling errors in 5.2 to 5.3/5.4 upgrade
|
CSCsj17905
|
VXSM fails to accept codec after placing a call with announcement
|
CSCsk13959
|
Tone detection is disabled when a midcall codec changes from PCMU to G729a
|
CSCek62859
|
Hung CCB in spite of setting the GW to OOS and resetting it back to IS
|
CSCsj48979
|
SS7 link can be created on ds0 if a VIF already exists
|
CSCsk86272
|
In a MGCP voice call, the CRCX response does not contain ptime.
|
CSCsk80578
|
DPVC goes into failed state and fails to recover even though a tstcon is passed
|
CSCsk35142
|
Standby VXSM reboots due to MOD recreate errors in CRML module
|
CSCsj36223
|
MGCP VoIP: Improper fax behavior after VXSM switchover
|
CSCsk88716
|
VIDEO Media type not interpreted in SDP with multiple m-lines in xGCP
|
CSCsk32055
|
XGCP: FAX passthrough not working (FAX going to T38 mode)
|
CSCsj45240
|
Ringback tone of AU for H.248 is incorrect.
|
CSCsk96122
|
ES and CSS counters increment on E1 path because of clock slips
|
CSCsk68173
|
Accepting ECAN and VAD on VXSM for ClearChannel call
|
CSCsk43119
|
T.38 capabilities are not returned in Add response.
|
CSCsi65236
|
IP-IP call without Back card
|
CSCsk22938
|
Context Audit on Emergency for emergency call is not working correctly
|
CSCsl16245
|
cnfxgcpcalea command does not enable/disable calea functionality
|
CSCsl43171
|
cnfpathis fails when any of the ds0 is in invalid state
|
CSCsl16242
|
CALEA calls result in one way audio
|
CSCsl39190
|
Hung ccb connections observed when signal is applied to the CALEA end point.
|
CSCsj50804
|
H248 - GW fax is not sent after mid-call codec change.
|
CSCsk80171
|
VXSM replies with 500 Internal Gateway Errors to ADD command
|
CSCsj50743
|
H.248-MG does not send ptime if MGC does not send ptime in Local
|
CSCsl42706
|
Incorrect Error Code when Payload is different in Local and Remote
|
CSCsl38892
|
TGCP- CALEA: Hung CALEA Call after fax call termination.
|
CSCsl02645
|
DSP crash due to wrong value of vif size(pkt period) for G.729 & G.711
|
CSCsk59547
|
VoIP: XGCP -VAD is disabled after VXSM switchover.
|
CSCsl76488
|
M3UA-MGCP: Card went into FAILED state after inhibiting SS7links and reset.
|
CSCsl74176
|
IUA-MGCP-SLT: Invalid chunk data ptr error observed under mix load.
|
CSCsk17339
|
deleventmapping command does not delete the VoIP eventmapping
|
CSCsl37094
|
Standby card goes into the failed state during mid-call codec change with ecan ON.
|
CSCsl54242
|
Standby card goes into the failed state with tDspApi Instruction Bound Exception
|
CSCsk44560
|
After switchover the bearer call is successful even in an isolate topology.
|
CSCsk94545
|
IUA-MGCP SLT: VXSM goes into the failed state during an upspeed codec change.
|
CSCsk26823
|
Card crashes on cnfvifterm when different ds0 groups are configured
|
CSCsk36122
|
CRML is not able to create VXSM logs directory
|
CSCsl49576
|
H248-SLT: Standby card goes into the failed state after issuing Loadrev.
|
CSCsl55325
|
Error: Exceed maximum PVC! occurs when add connection IP for the 4th Co
|
CSCsl53978
|
TGCP-CALEA: updates wrong call type in dspxgcpcaleacalls
|
CSCsj60070
|
Incorrect ttycodec selected for E1 mode when adding new tty profile
|
CSCsm02358
|
Integrating DSP image 11.2 to branch 5.4 (r3.0)
|
CSCsk04438
|
H.248: Failed to modify H.248 association during forced OOS
|
CSCsj96896
|
Calls not replicated on standby card during Bulk Sync
|
CSCsk00126
|
IUA-SLT-H.248: Card failed after issuing cnfh248oos.
|
CSCsm02358
|
Integrating DSP image 11.2 to branch 5.4 (r3.0)
|
CSCsj40853
|
H.248 call made with a codec and RV=ON, is dropped after a switchover.
|
CSCsj68164
|
dspcodeccnt counter clears after VXSM switchover
|
CSCsl49437
|
Wrong packetization period while processing MDCX after T.38 fallback
|
CSCsl56709
|
435 observed when a switchover and switchback is performed with RV= ON
|
CSCsi58210
|
Upspeed fails in AAL2 after changing vbd codec using the command cnfcid
|
CSCsj97117
|
H.248: Incorrect vbd codec selected for E1 mode on adding new vbd profile
|
CSCsk98413
|
GW fails to notify MGC with observed event {ctyp/dtone{dtt=CNG}}
|
CSCsi46857
|
DS3 Alarms are not logged in PXM log when payload of OC3 line is ds3
|
CSCsk76180
|
Incorrect display of dspcodeccnts for EFR after the VXSM switchover
|
CSCsk43122
|
Even after SC (restart) rejection the association with SBC is UP
|
CSCsl89676
|
M3UA: Unable to add links in linkset during load conditions
|
CSCsm14555
|
DSPAPI Related PXM logs cleanup
|
CSCsj82169
|
H.248 -Mid-Call Codec change fails(515 error) when RV= ON
|
CSCsl85558
|
Wrong packetization period in tty call when ppcntrl is disabled for G.729a voice calls
|
CSCsm07681
|
H.248 MG gives unsupported media type for IP-IP call with G.729A and RV=OFF
|
CSCsj03370
|
VXSM card resets when call waiting is enabled
|
CSCsm23277
|
MEGACO Related PXM logs cleanup - Trace Enhancement
|
CSCsm00642
|
CALEA not disabled by MDCX
|
CSCsl87869
|
Wrong Codec and VAD returned for annexb missing in SDP for G.729 and G.729A
|
CSCsm04072
|
When CA ack with ver=3, MG remains in OOS state even after a switchover
|
CSCsk21076
|
During a transcoding call when relay is set to false, the remote descriptor on first leg of transcoding GW is lost.
|
CSCsl11377
|
MEGACO MCC exception observed when ECAN is modified in hairpin call.
|
CSCsl39311
|
DCAP exception fails to capture SRR registers
|
CSCsm09963
|
Addition of ss7 link generates an error
|
CSCsl87603
|
AnnexB: CodecSelectionFailure for annexB line missing in SDP in MGCP VoIP
|
CSCsm04542
|
Wrong PVC state replication after VXSM switchover when DPVC timer= 12000
|
CSCsm04560
|
DPVC debug shellconns: DPVC PXM logs correction and enhancements
|
CSCsm07555
|
When inact timer is set to 0 then call returns to voice for HS modulation.
|
CSCsm04380
|
Error213 is not received due to delayed command execution and CALEA enabled in MDCX
|
CSCsl87977
|
AnnexAB: VAD is OFF even when AnnexB is implicit in G.729 name string
|
CSCsm25925
|
H.248: SC with reason 901 should be sent on redirection before registration
|
CSCsk94945
|
E1 status bounces between OUT to IN to OUT, when path is down at ONS
|
CSCsl11653
|
MEGACO PPC observed on applying events after switchover on TranscodingGW
|
CSCsj93041
|
H.248-VAD mismatch at both the endpoints in the attached call flow
|
CSCsm36793
|
AAL2: Upgrade failed from N-1 to N in AAL2-Trunking Application.
|
CSCsm34288
|
Setting prof value to 0 for command addss7linkset leads to VXSM crash
|
CSCsj48391
|
H.248 - MG gives 515 error for iLBC when RV = OFF
|
CSCsl51931
|
XGCP: Wrong call mode display during fax transmission after VXSM switchover
|
CSCsm31117
|
VAD is not updated during a midcall codec change
|
CSCsm04364
|
Error message 210 is not received when CALEA call is sent on nonCALEA image
|
CSCsl87344
|
AnnexB: VAD parameter different at two endpoints of same call with G.729codec
|
CSCsl87097
|
AnnexAB: VAD incorrect in dumpCcb for G729/G723 calls due to s:<on/off>
|
CSCsm04420
|
Error 211 not received for CALEA low bandwidth calls
|
CSCsm04483
|
No error message received if es-cci/es-ccd/port is missing
|
CSCsm23206
|
H248: Hung RTP termination exists on standby card.
|
CSCsk17259
|
Transcoding: Data Bound Exception when new EventBuffer descriptor is sent
|
CSCsm07005
|
MGCP: CNG Tone should be linked to CED and V21Tone
|
CSCsm02440
|
VXSM crashes on sending s:off in MDCX after switchover in TGCP VoIP call
|
CSCsm12464
|
One-way Voice Path when CLEARCHANNEL is used as mid-call codec
|
CSCsm52792
|
Command dspxgcpendpts displays T1 line as in use even though the VIFs are deleted
|
CSCsl93607
|
Task tDspApi gives an exception while playing announcement with RV=ON
|
CSCsm07737
|
AnnexA for G.723: Call is not established according to codec in SDP
|
CSCsm04236
|
irm database is corrupted when dncon and upcon commands are run and dpvc timer is set to -1
|
CSCsl58624
|
Resource deallocation observed when CA controlled Fax is sent with RV= ON
|
CSCsm30992
|
Wrong Media Type for call on sending MDCX after T.38 fallback
|
CSCsm50246
|
VXSM does not accept silenceSupp:off when event descriptor is applied.
|
CSCsm55027
|
Delay is observed as 1 in 902 SVC on VXSM switchover for ETSI profile
|
CSCsm57394
|
VXSM remains in OOS state when GW receives unauthorized messages
|
CSCsm68945
|
MEGACO PPC exception on sending Modify with different payloadtype in local and remote
|
CSCsm19414
|
Standby card reboots as DSP crashes in IUA load
|
CSCsm45885
|
AUCX does not publish CALEA parameters
|
CSCsm45644
|
MG does not upspeed after VXSM switchover for CA controlled T.38
|
CSCsj96729
|
Transcoding: Event buffer functionality is not working
|
CSCsm12337
|
IUA-H248: Standby card fails while adding redundancy with mix load
|
CSCsk96065
|
DCAP Software Exception: Vector 768 EPC: 0x00010890 ADDR: 0x00e04cc0.
|
CSCsm87178
|
500 Internal Gateway error returned if ptime is not present in Local
|
CSCsm84537
|
Problem in SIP call establishment with BTS due to non support 0 = line
|
CSCsm82335
|
VXSM card reset due to VTSP crash
|
CSCsk84152
|
H248: Tones should be programmed at DSP based on eventmapping configuration
|
CSCsm12135
|
H248SLT: Standby goes to Failed state when redundancy is added on an existing call.
|
CSCsm91688
|
VXSM crashes during VoIP call: Task: 0x87f27590 MEGACO PPC
|
CSCsm96582
|
VXSM crashes while executing COT: Task: 0x87ef72a0 MEGACO MCC
|
CSCso17523
|
CAS digit power levels are incorrect
|
CSCso17254
|
Improper initialization of channel_state in API modify channel.
|
CSCsm82730
|
M3UA-SLT:StandBy goes into Failed state if reset issued in Init state.
|
CSCsm97012
|
VXSM loses MG Domain Name when a switchover is performed after upgrade
|
CSCsm27343
|
XGCP: Multiple Modify over 60 cps resulting standby card to failure
|
CSCso04391
|
Standby VXSM card goes into failed state after mid-call codec change
|
Resolved Caveats in Release 5.4.00.201
Table 9 Resolved Anomalies in Release 5.4.00.201
Anomaly ID
|
Description
|
CSCek55569
|
Standby card recreate failed by NULL ldibptr
|
CSCsj73803
|
VXSM is rejecting the MDCX containing SDP with the following attributes
|
CSCsj47252
|
VXSM crashes on Load for PCMU calls in MGCP
|
CSCek62958
|
IUA-SLT: Dsperrs observed stating invalid chunk data ptr.
|
CSCsj83896
|
malformed REL_CON in response to REL_REQ in IUA
|
CSCsj65154
|
Standby reboots after failure in Mod operation (without an Add operation)
|
CSCsj58344
|
Fine Tune Lower and upper limits for callsetupResouce
|
CSCsj47830
|
Connection Id not cleaned up on standby after call gets deleted
|
CSCsj37922
|
GW controlled fax in H248 with OGW set to VBD and TGW set to fax fails
|
CSCsj23389
|
Memory Leaks in VXSM during M3UA load
|
CSCek66089
|
M3UA-SLT: Observed invalid chunk data ptr in dsperrs.
|
CSCsj02353
|
G.729 calls fails on enabling AnnexABsdp
|
CSCsi73479
|
Successful Graceful OOS followed by Forced OOS hangs H.248 Assoc
|
CSCsj21826
|
Subtract cmd with RTP/* results in Internal Gateway Error (500)
|
CSCsi96344
|
DSP crash due to misconfiguration with 40 ms pkt size forG711u CSCsj10767
|
CSCsj02348
|
Standby Failure during the incremental sync
|
CSCsi68488
|
MGCP: 1% call failures during 8cps with codec change from g729ab to g711u
|
CSCek70423
|
Unable to add lapd on 1 T1(Rest all 335 lapds are added)
|
CSCsi86301
|
VXSM does not send DLCX on RTCP timeout if some evt/sig exists on endpoint
|
CSCsi98033
|
TTY tone should be programmed on DSP depending on the event mapping
|
CSCsi58250
|
VXSM is not changing remote end port on getting T.38 modify msg in H248
|
CSCsi96310
|
CRML-1-REDM_DELCON_FAIL Memory Full
|
CSCsi75071
|
Hung SCN termination due to Exception in dil_open_channel
|
CSCek70228
|
H.248:Hung RTP terminations due to res dealloc failures in CRML
|
CSCsi55192
|
rtpmap not supported for Static payload types
|
CSCek72659
|
Low priority RUDP session remains In service
|
CSCsi34955
|
Rudp Sessions Grp Status is in the NONE state
|
CSCek72659
|
Low priority RUDP session remains In service
|
CSCek70227
|
H.248:Megaco PPC task suspended when stuck in a for loop.
|
CSCek70226
|
H.248:Out of resource error due to CDB leak.
|
CSCsi51255
|
Tones detection not getting enabled in TDM hairpin call.
|
CSCek70118
|
VXSM H.248 returns Pending transactions
|
CSCek70116
|
VXSM sends incorrect H.248 error code 500 when no termination matches
|
CSCsi49015
|
Allow 1st character as digit in domain name configuration
|
CSCek73769
|
Ringback Tone for US is not working.
|
CSCek73413
|
No endpoints registered... prints on console periodically.
|
CSCek70797
|
Fax fails on T.38 devices when call starts at G729
|
CSCek70878
|
VXSM mgcgwdn mismatch results in COT failure
|
CSCek67800
|
H.248:Restart SC shud be sent on redirection before registration
|
Removed Caveats in Release 5.4.00.200
Table 10 lists caveats that were listed as open in Release 5.3.10 but have been removed because they are unreproducible or otherwise invalid.
Table 10 Caveats Removed in Release 5.4.00.200
DDTS Issue
|
Description
|
CSCek40572
|
Fax upspeed fails after modifying H248 call to a new codec.
|
CSCek33012
|
VQM RFC 3611 Dup pkts (1 in 100) cause incorrect loss rate 99.6%.
|
CSCek50487
|
T.38 call doesn't downspeed if midcall mdcx is sent.
|
CSCek53995
|
DB missing dsp info after upgrade from 2.5 to 2.5mr.
|
.
Resolved Caveats in Release 5.4.00.200
Table 11 describes the caveats that were open following in Release 5.3.10 but are now resolved in VXSM Release 5.4.00.200.
Table 11 Software Caveats Resolved in VXSM Release 5.4.00.200
DDTS Issue
|
Description
|
CSCek38528
|
Enable card switch-over if IOS tasks crash
|
CSCek52027
|
semGive error in PXM log, VXSM resets after 2-3 days
|
CSCek52788
|
Inconsistent severity and huge amount of H248 log messages
|
CSCek52935
|
VXSM intermittently uses G723 resources instead of specified G711
|
CSCek53543
|
Dual PVC failure will not recover if failure threshold is 2
|
CSCek53969
|
DSM rejects some DSP responses with no pending requests error
|
CSCek54015
|
Memory leak in DSPAPI buffers on the daughtercard
|
CSCek54040
|
Mix codec calls with COT enabled on BTS caused vxsm VTSP crash
|
CSCek54219
|
Double open in standby VXSM
|
CSCek54902
|
CCAPI memory leak when handling disconnect timeout
|
CSCek54911
|
Standby card crashes with DSP channel exception
|
CSCek55602
|
Mem Leak in MGCP app
|
CSCek55865
|
Time duration too long (~48hrs) for audit on NULL context
|
CSCek56159
|
RTP terms left hanging on standby even after deleting the call
|
CSCek56325
|
VXSM should ignore unsupported codec
|
CSCek56719
|
RQNT followed by mid-call codec change and subsequent call fails
|
CSCek57181
|
increase TM_MM_BUFF_NT_ADDR buffer from 2 to 20 bytes
|
CSCek57550
|
cnfgwoos failed to clean up dangling call legs
|
CSCek55569
|
Standby card recreate failed by NULL ldibptr
|
CSCek58229
|
154 bytes of a-X-cluster causes PPC exception
|
CSCek58493
|
Compare strings failed because of null string pointers
|
CSCek65232
|
Cisco MGX did not recover from call server sequential restart
|
CSCek60744
|
Calls not cleared in MG while H248 Midcall Codec Chg call rate test
|
CSCek65479
|
failure in response to resource allocation request, SCN termination
|
CSCek65910
|
Standby Card resets frequently
|
CSCuk61635
|
VXSM replies with Internal Gw error to a Modify in a T38 Call
|
CSCek63961
|
T.38 with fallback to G.711
|
CSCuk61637
|
VXSM stays in service after an Unauthorized message from CA
|
CSCek64524
|
VXSM gives err-442 when Term-desc is not at first pos in Media desc
|
CSCek64573
|
VXSM cli stops working after adding 1st session grp when 2nd exists
|
CSCek66095
|
Modify command failure from CRML is returned as success to MGC
|
CSCek65372
|
VXSM OC-3 TGCP could not handle RQNT with cot
|
CSCek68159
|
Default PLC config does not take effect during call-setup
|
CSCek68160
|
DSP Knob cnfdsp -ec does not work
|
CSCek68398
|
H248:CED not re-enabled on 1300Hz detection (during V.90 ups)
|
CSCek68407
|
cant cnfgwdn or adddnsdn after upgrade to 5.3(10.200)
|
CSCek69459
|
MGCP T.38:Upspeed fails when remote port changesduring T.38 switch
|
Related Documentation
The following documents contains information that may be useful to software Release 5.4 for VXSM:
•Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Hardware Installation Guide, Releases 2 Through 5.3
•Cisco ATM Services (AXSM) Configuration Guide and Command Reference for MGX Switches, Release 5.2
•Cisco MGX Route Processor Module (RPM-XF) Installation and Configuration Guide, Release 4
•Cisco MGX 8880 Media Gateway, Release 5.4: A Guide to User Documentation.
•Release Notes for Cisco MGX 8850 (PXM1E/PXM45), Cisco MGX 8950, and Cisco MGX 8830 Switches, Release 5.4
Obtaining Documentation, Obtaining Support, and Security Guidelines
For information on obtaining documentation, obtaining support, providing documentation feedback, security guidelines, and also recommended aliases and general Cisco documents, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:
http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html
Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned 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. (1005R)
Any Internet Protocol (IP) addresses used in this document are not intended to be actual addresses. Any examples, command display output, and figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses in illustrative content is unintentional and coincidental.
© 2008 Cisco Systems, Inc. All rights reserved.
Feedback
