cc/td/doc/product/wanbu/mgx8260/rel1_2
hometocprevnextglossaryfeedbacksearchhelp
PDF

Table of Contents

Release Notes for Cisco MGX 8260 Media Gateway, Release 1.2.5
 Contents
 System Requirements
 New and Changed Information
 Installation Notes
 Caveats
 Documentation Updates
Related Documentation
 Obtaining Documentation
 Obtaining Technical Assistance

Release Notes for Cisco MGX 8260 Media Gateway, Release 1.2.5

January 2002

These release notes describe new features and caveats in system Software Release 1.2.5 for the Cisco MGX 8260 Media Gateway. Use these release notes in conjunction with the documentation listed in the "Related Documentation" section.

Contents

These release notes contain the following sections:

System Requirements

Table 1 provides a list of hardware, software, and firmware requirements for running MGX 8260 Release 1.2.5 system software. All software runs on the MGX 8260 using the Wind River Systems VxWorks operating system, Version 5.3.1. Contact Cisco Systems Technical Assistance Center (TAC) for any additional information.

:

Table 1   System Requirements for MGX 8260 System Software Release 1.2.5

Customer Orderable Part Number Description Part Number Hardware Version Firmware Version
Current  Minimum  Current  Minimum 

BSCFC-6T3

Front card for Broadband Service Card (BSC); provides TDM switching for 6 channelized DS3 lines.

800-06397

-02 D0

-02 C0

01.02.05

01.02.02

MGX8260

System chassis.

800-06541

-02 D2

-01 A0

—

N/A

NSCFC-8DSP

Front card for Narrowband Service Card (NSC); provides DSP processing for up to 8 channelized T1/E1 lines, including voice, G.711, echo, VAD, and CNG functions.

800-06406

-03 C0

-02 A0

01.02.05

01.02.02

NSCFC-16DSP

NSC front card providing DSP processing for up to 16 channelized T1/E1 lines, including voice, G.711, echo, VAD, and CNG functions.

800-06405

-03 C0

-02 A0

01.02.05

01.02.02

NSCFC-8TDM

NSC front card providing TDM switching for up to 8 channelized T1/E1 lines.

800-06407

-03 C0

-02 A0

01.02.05

01.02.02

NSCFC-16TDM

NSC front card providing TDM switching for up to 16 channelized T1/E1 lines

800-06408

-03 C0

-02 A0

01.02.05

01.02.02

OC3MMBC-4

SCC back card providing 4 OC-3 Multi-Mode Fiber (MMF) interfaces.

800-06393

-01 A0

-01 A0

—

N/A

OC3SMIBC-4

SCC back card providing 4 OC-3 Single-Mode Fiber Interface (SMFI)

800-06396

-01 A0

-01 A0

—

N/A

SCC5FC-4FE1

5-Gbps front card for System Control Card (SCC). Supports 4 FE ports.

800-06392

-01 F1

-01 F0

01.02.05

01.01.03

SCC5FC-4FE/B

5-Gbps, 256-MB SCC front card. Supports 4 FE ports.

800-15982

-01 D0

-01 A0

01.02.05

01.02.02

SCC5FC-4OC32

5-Gbps SCC front card. Supports 4 OC-3 ports.

800-06474

-01 A1

-01 A0

01.02.05

01.02.00

SCC5FC-4OC3/B

5-Gbps, 256-MB SCC front card. Supports 4 OC-3 ports.

800-16007

-01 D0

-01 A0

01.02.05

01.02.02

SCCBC-4FE

SCC back card providing NMS ports and four 100BASE-T network interface ports.

800-06325

-01 C0

-01 C0

—

N/A

T1E1BC-50NR

NSC back card providing 50-pin, 100-ohm, T1/E1 interfaces.

800-06322

-01 D0

-01 D0

—

N/A

T1E1BC-RED

NSC back card providing 1:N redundancy support.

800-06323

-01 C1

-01 B1

—

N/A

T1E1BC-RJ48

NSC back card providing 16 E1 120-ohm RJ-48 interfaces

800-06463

-01 B0

-01 A0

N/A

N/A

T3E3BC-6DSX

BSC back card providing 6 Tx and Rx coaxial T3 interfaces

800-06324

-01 D0

-01 D0

N/A

N/A

1 SCC5FC-4FE is no longer available for ordering and has been replaced by SCC5FC-4FE/B.

2 SCC5FC-4OC3 is no longer available for ordering and has been replaced by SCC5FC-4OC3/B.

New and Changed Information

There are no new software features introduced for software Release 1.2.5. There were no new software features introduced for software Release 1.2.4.

Installation Notes

This section describes the software upgrade paths, security key requirements, installation procedures, and database configurations needed for software upgrade.

System Software Upgrade Paths

Release 1.2.5 software supports graceful upgrades from the following releases:

Security Key Requirements

A security key is required for the transfer of files to the MGX 8260 through use of the UNIX tftp function. To determine the appropriate MGX 8260 security key code, use the lskey command from the command line interface.

Installation Procedures

The following sections describe the process you use to download MGX 8260 software from the Cisco web or ftp sites, transfer the files to the MGX 8260, and download the files to each card.

Downloading Software from CCO

To download MGX 8260 software images, refer to the Cisco software center on Cisco Connection Online (CCO), located at the following URL:

For instructions on how to download software, refer to the link for "Using the Software Center".

MGX 8260 software includes the following files:

vxWorks_dnld.scc.fw
vxWorks_boot.scc.fw
vxWorks_dnld.nsc.fw
vxWorks_boot.nsc.fw
vxWorks_dnld.bsc.fw
vxWorks_boot.bsc.fw

To upgrade the MGX 8260, download the new system software from CCO to a management server on your network that supports the UNIX tftp function.

Transferring Files to the MGX 8260

Using tftp, transfer the files to the MGX 8260 using the following procedure:

Step 1   Log on to the workstation running the tftp server and locate the files you downloaded in the "Downloading Software from CCO" section.

Step 2   Initiate a tftp session with the target MGX 8260 Media Gateway using the tftp command.

tftp <IP Address>

Specify the IP address of the MGX 8260 management port in standard IP dot notation.

Step 3   Set the transfer mode to binary with the following command:

mode binary

Step 4   Use the following tftp commands to transfer SCC software to the MGX 8260:

tftp> put vxWorks_dnld.scc.fw scc_r01.02.05.img.[key]

tftp> put vxWorks_boot.scc.fw scc_r01.02.05.fls.[key]

For information about the security key [key], refer to the "Security Key Requirements" section.

Step 5   Use the following tftp commands to transfer BSC software to the MGX 8260:

tftp> put vxWorks_dnld.bsc.fw bsc_r01.02.05.img.[key]

tftp> put vxWorks_boot.bsc.fw bsc_r01.02.05.fls.[key]

Step 6   Use the following tftp commands to transfer NSC software to the MGX 8260:

tftp> put vxWorks_dnld.nsc.fw nsc_r01.02.05.img.[key]

tftp> put vxWorks_boot.nsc.fw nsc_r01.02.05.fls.[key]

Step 7   Close your tftp session.


Upgrading Card Software

Before performing an upgrade, make sure you have a current backup of the configuration database. Back up the database using the dbbkup command from the command line interface.

Caution   All modules must be upgraded to the new release of software during the upgrade process. Performing a partial upgrade (For example, some, but not all BSCs, or some, but not all NSCs) could cause unexpected behavior in MGX 8260 system operation.
Note   The installation procedure described here is for a graceful upgrade process from the software release indicated in the "System Software Upgrade Paths" section to the current release.

The general process to upgrade software on all cards is as follows:

1. Initiate a Telnet session with the target MGX 8260 Media Gateway, specifying the IP address of the MGX 8260 management port in standard IP dot notation.

2. Log in as superuser or a user with level 1 privileges.

3. Follow the upgrade procedures for each card type.

4. Log out of your Telnet session.

Note   We recommend that you use the upgrade procedures while simultaneous console connections are established to both the active and the standby SCC.

Upgrading SCC Software

The upgrade process for redundant SCCs is graceful. It does not interrupt established calls, but it can interrupt calls in the process of being established. When you invoke the upgrade process, the MGX 8260 upgrades and restarts the standby SCC. You can then commit or cancel the upgrade. When you commit the software, the MGX 8260 switches to the standby SCC and then upgrades the other SCC.

Warning Upgrading nonredundant cards interrupts service. Perform nonredundant upgrades during light traffic periods or during a prearranged maintenance window.

To upgrade SCC and software images, perform the following steps:

Step 1   Upgrade the boot Flash software on each SCC using the following command. Issue the command for each SCC, replacing the <physicalSlotNumber> with the appropriate number for your configuration.

updatefls <physicalSlotNumber> IMAGE/SCC/scc_r01.02.05.fls

Step 2   Ensure that the standby SCC is in the standby state.

Step 3   Upgrade the software image on the active SCC using the following command:

upgd 9 scc_r01.02.05.fw

Note    Enter a 9 even if card 10 is active. This parameter refers to logical card 9. The active SCC is always logical card 9 regardless of its physical slot location.

In redundant configurations, the upgd command resets the standby SCC. Wait until the standby SCC reboots and its console session shows a standby state. At that point, the standby SCC will be running the new release of boot Flash and software images.

Step 4   You can now commit or cancel the upgrade.

    a. For redundant SCCs, if you wish to cancel the upgrade, enter the upgdcancel command. Use this command only if you have not entered the upgdcmit command. You cannot cancel an upgrade for nonredundant cards.

Note    Before you cancel an upgrade with the upgdcancel command, you need to to reset the previous software on the flash card using the updatefls command.

    b. To commit the new software, enter the following command:

upgdcmit 9

On redundant systems, the upgdcmit command switches over the two SCCs. The SCC that was standby is placed into active state with its newly upgraded database and software image, and the previously active SCC resets and boots up to standby state.

Warning You must execute either the upgdcmit command in Step 4b. or the upgdcancel command in Step 4a. If you do not execute one of these commands, database corruption will occur.

Step 5   Ensure that the previously active SCC has completed booting and is in standby state.

Step 6   On redundant systems, force a switchback to the primary card using the swcd command:

swcd 9


Upgrading BSC Software

The upgrade process for redundant BSCs is graceful. It does not interrupt established calls, but it can interrupt calls in the process of being established. When you invoke the upgrade process, the MGX 8260 upgrades and restarts the standby BSC. You can then commit or cancel the upgrade. When you commit the upgrade, the MGX 8260 switches to the standby BSC and then upgrades the other BSC.

Warning Upgrading nonredundant cards interrupts service. Perform nonredundant upgrades during light traffic periods or during a prearranged maintenance window.

If your MGX 8260 includes BSCs, perform the following steps to upgrade BSC Flash and software images:

Step 1   Upgrade the boot Flash software on each BSC using the following command. Issue the command for each BSC, replacing the <physicalSlotNumber> with the appropriate number for your configuration.

updatefls <physicalSlotNumber> IMAGE/BSC/bsc_r01.02.05.fls

Step 2   Ensure that the standby BSC is in the standby state.

Step 3   Upgrade the BSC software image using the following command. Issue the command for the first primary BSC in your system, replacing the <logicalSlotNumber> with the appropriate number for your configuration.

upgd <logicalSlotNumber> bsc_r01.02.05.fw

Answer Y to the "Are you sure?" warning message.

In redundant configurations, the upgd command resets the secondary BSC matched with the primary BSC you specified in <logicalSlotNumber>. The secondary is now running the new release of boot Flash and the software images.

Step 4   Ensure that the standby BSC has finished booting and is in the standby state.

Step 5   You can now commit or cancel the upgrade.

    a. For redundant BSCs, if you wish to cancel the upgrade, enter the upgdcancel command. This command can be used only if you have not entered the upgdcmit command. You cannot cancel an upgrade for nonredundant cards.

Note    Before you cancel an upgrade with the upgdcancel command, you need to to reset the previous software on the flash card using the updatefls command.

    b. To commit the new software, use the following command. Issue the command for the first primary BSC in your system, replacing the <logicalSlotNumber> with the appropriate number for your configuration.

upgdcmit <logicalSlotNumber>

If you have redundant BSCs installed, the upgdcmit command switches over the two BSCs. The BSC that was secondary (with its newly upgraded database and software image) becomes the primary BSC, and the previously primary BSC becomes the secondary BSC.

Warning You must execute either the upgdcmit command in Step 5b. or the upgdcancel command in
Step 5a. If you do not execute one of these commands, database corruption occurs.

Step 6   Ensure that the previously primary BSC has finished booting and is in the standby state.

Step 7   On redundant systems, force a switchback to the original primary BSC using the swcd command:

swcd <standbySlotNumber>

Where <standbySlotNumber> is the number of the original secondary BSC (the BSC that is currently in active state).

Step 8   Repeat Step 2 through Step 7 for additional BSC pairs in your system.


Upgrading NSC Software

The upgrade process for redundant NSCs is graceful. It does not interrupt established calls, but it can interrupt calls in the process of being established. When you invoke the process, the MGX 8260 upgrades and restarts the standby NSC. You can then commit or cancel the upgrade. When you commit the upgrade, the MGX 8260 switches to the standby NSC and then upgrades the other NSC.

Warning Upgrading nonredundant cards interrupts service. Perform nonredundant upgrades during light traffic periods or during a prearranged maintenance window.

NSC redundancy follows an N:1 design, with one NSC providing redundancy for all remaining NSCs.

If your MGX 8260 includes NSCs, perform the following steps to upgrade NSC Flash and software images:

Step 1   Upgrade the boot Flash software on each NSC using the following command. Issue the command for each NSC, replacing the <physicalSlotNumber> with the appropriate number for your configuration.

updatefls <physicalSlotNumber> IMAGE/NSC/nsc_r01.02.05.fls

Step 2   If your system includes NSC redundancy, identify the slot number of the NSC providing redundancy.

Step 3   Enter the following command for the first NSC in your system (excluding the redundant NSC identified in Step 2). Replace the <logicalSlotNumber> with the appropriate number for your configuration.

upgd <logicalSlotNumber> nsc_r01.02.05.fw

Answer Y to the "Are you sure?" warning message.

In redundant configurations, the upgd command resets the redundant NSC. The redundant NSC should now be running the new release of boot Flash and software images.

Step 4   Ensure that the standby/redundant NSC has finished rebooting and is in the standby state.

Step 5   You can now commit or cancel the upgrade.

    a. If your MGX 8260 is configured for NSC redundancy, and you wish to cancel the upgrade, enter the upgdcancel command. You can use this command only if you have not entered the upgdcmit command. You cannot cancel an upgrade for nonredundant cards.

Note    Before you cancel an upgrade with the upgdcancel command, you need to to reset the previous software on the flash card using the updatefls command.

    b. To commit the new software, use the following command. Issue the command for the first NSC as indicated in Step 3. Replace the <logicalSlotNumber> with the appropriate number for your configuration.

upgdcmit <logicalSlotNumber>

Warning You must execute either the upgdcmit command in Step 5b. or the upgdcancel command in Step 5a. If you do not execute one of these commands, database corruption occurs.

Step 6   Ensure that the previously standby NSC is now active and that the NSC in <logicalSlotNumber> is now in standby state.

Step 7   For an MGX 8260 configured for NSC redundancy, force a switchback to the NSC indicated in Step 3. Use the swcd command:

swcd <standbySlotNumber>

Where <standbySlotNumber> is the number of the standby/redundant NSC (currently in active state).

Step 8   Repeat Step 3 through Step 7 for all NSCs in your system.

Note   If the NSC does not have a back card, it may reboot in MISMATCH state. Fix this by entering the command chcdif <logicalSlotNumber> 3. This returns the NSC to No-Back-Card mode.


Database Configuration Information

You do not need to clear the configuration database when performing a graceful upgrade from Release 1.2.2, 1.2.3, or 1.2.4 to Release 1.2.5. Nongraceful upgrades require a database reconfiguration.

Caveats

This section lists the open and closed caveats for Release 1.2.5.

Open Caveats

Caveats in Table 2 are new issues observed during lab/EFT testing of Release 1.2.5.

.

Table 2   New Caveats Observed During Lab/EFT Testing of Release 1.2.5

Identifier  Title  Description 

CSCdv79034

Minor Alarms observed during IMT-IMT load test of BSC card.

With a call load of approximately 40 cps (SS7 calls), the following two alarms repeatedly appear:

RMG-RM_EVT_ERR_LOG*-MINOR
MPC-MSG_EVENT******-MINOR

CSCdw07597

WebViewer does not convert .img extension to .fw after downloading.

Cisco WebViewer does not convert the .img filename extension to .fw after downloading the NSC, BSC, or SCC image files. This causes the upgd command to fail.

CSCdw12617

Standby SCC reports Firmware mismatch after upgradecancel.

After you run the upgdcancel command, the MGX 8260 reloads the SCC with the software release prior to your current upgrade process. After resetting itself, the standby SCC reports a mismatched state due to firmware mismatch because the boot code is a different release version than the firmware.

Caveats in Table 3 were open for Release 1.2.4 and are also open in Release 1.2.5.

.

Table 3   Open Caveats in Release 1.2.4 and 1.2.5

Identifier  Title  Description 

CSCds67779

Documentation change to have ECAN and VAD default to off.

ECAN and VAD default have been changed to OFF but the user documentation does not include this change as of Release 1.2.

CSCds70201

Update user guide for new cli stopdisk.

As of Release 1.2.1, a new CLI command, stopdisk, is available. You can use this command to shut off hard disk access. This command is not yet included in the Cisco MGX 8260 Command Line Interface Guide.

CSCds79125

CLI - adddlsp; dlsapTEIAssign does not default to 2.

According to the Cisco MGX 8260 Command Line Interface Guide, the default value for the addlsp dlsapTEIAssign parameter is 2. This is incorrect. The current default is 1.

CSCds79162

CLI - adddlsp; min for dlsap203Timer should be 20.

According to the Cisco MGX 8260 Command Line Interface Guide, the minimum value for the addlsp dlsap203Timer parameter is 20. This is incorrect. Currently, this value can be as low as 10.

CSCdt00032

Cells are being dropped when there are 2300 connections.

Cells are being dropped slowly when there are 2300 connections with 4 Ethernet lines active. dspatm2stat shows ErrCrc increasing slowing. Also, if you continue operations with 2300 connections, the database becomes corrupted. As a result, MGCP reports 540 on CRCX and 400 on MDCX with the very first endpoint.

CSCdt04637

Datapath distorts original tone from HPT1 tester.

When a 404-Hz tone is sent through the bearer path, and switched over to Slot 6, the 404-Hz tone is replaced with a much higher frequency tone.

This problem is caused by bad NSC hardware. Contact the Cisco TAC for assistance.

CSCdt10260

BIP-8 bit does not report cell crash error in CbtPrintStatus function.

If there is a cell bus BIP-8 problem, the cell bus controller (Cubit) driver on the SCC and NSC does not accurately report the problem and the SCC/NSC is not switched over.

CSCdt13497

MRPC errors in event log and 502 responses to MGCP.

Some MGCP events in the event log are not explained in the user documentation.

CSCdt21007

BSC Environmental Monitoring Module (EMM) Reports Failed.

The environmental monitoring module (EMM) reports created before and after the resetting of the BSC cards are different.

 

CSCdt31117

Misleading information on T1 lines in the documentation.

The MGX 8260 documentation for DS1/T1 lines states that the default for received direction is robbed bit. This should be changed to state that the default for received direction is none.

CSCdt62577

Need CLI to shut off RSIP generation.

When the call agent does not generate traffic, the
MGX 8260 eventually brings down the MGCP link and starts sending RSIPs.

CSCdt72583

DS1 Bert failure on repetitive patterns.

During a BERT for DS1 on NSC, with error insertion, COMET sometimes reports error rate mismatch. Without error insertion, COMET sometimes indicates that error bits are detected. These cases are likely to happen on patterns 3in24 and 1in16.

CSCdt75173

System Name is lost after resetnd or upgrade.

—

CSCdt83222

SCC switch over when adding inactive FastEthernet lines

When you are adding 4 new Fast Ethernet lines to the primary SCC, the SCC switches over. This should not occur when the Fast Ethernet lines on the secondary SCC are also down. In addition, when the 2 Fast Ethernet lines on the primary and secondary become active, the SCC also switches over.

CSCdt84087

TCG reports AAL1 add error.

After a few switchovers, calls start failing due to Add Channel failure from RMG (possibly due to TCG failure).

CSCdt84298

Call Agent times out while waiting for COT notify from the MGX 8260.

The call agent times out while waiting for a notification of continuity test results from the MGX 8260. This occurs when transponder continuity testing is requested on an endpoint before the terminating call is set up.

CSCdt89367

Cannot add an ethernet line when OSPF and loopback ip are enabled.

—

CSCdt89970

Standby NSC cannot be upgraded.

When you are using the upgrade functions (upgd, upgdcmit), NSC modules in standby state but not set up as part of a redundant pair cannot be upgraded. Also, the nsc.fw file is not updated when the last NSC module is upgraded. This causes any new NSC modules that are introduced into the system or previously upgraded NSC modules that are clear configured (clrcdcnf) to boot up on the pre-upgrade software version.

CSCdt89970

A unique/special tftp key should be added for sensitive files.

Currently it is possible to tftp the pswd file out of the MGX 8260. This is a high security risk because any user can do this. A unique/secret tftp key (separate from that for normal files) needs to be added and applied against all sensitive/security related files on the system.

CSCdt91753

System Date accepting invalid values.

The MGX 8260 allows invalid settings for system date and time. For example, February 31 is allowed.

CSCdt96988

COT transponder tests on each channel of BSC DS1 times out.

The COT transponder tests might result in failure if the sctTimeout value is set to a small number, for example 100 ms.

CSCdu00119

D channels dropped during BSC switchover.

—

CSCdu02910

Multiple NTFY sent by the MGX 8260.

The NSC reports multiple instances of modem tone upon receipt of each MDCX message. This occurs when modem up-speed is set to G.711. This processing of the MDCX message by TCG causes multiple instances of modem tone to be detected. As a result, MPC reports multiple MT NTFY messages to the call agent.

CSCdu03079

Unrequested NFTY G/vbd sent by 8260.

This problem occurs when the
MGX 8260 is configured to send fax/modem NTFY messages.When a modem call is made with FaxModemDetect enabled, 2 NTFY messages are sent from the MGX 8260, one with modem tone detection and a second with voice band detection.

If you use Release 1.2.2 or earlier software, you should manually turn off the fax/modem reporting through use of the chmpc command. If you use Release 1.2.3, the fax/modem reporting configuration is automatically set to off as default.

CSCdu03115

All endpoints reset due to 1 unack message.

If you are using G.726 32K codec selection, when a modem call occurs with FaxModemDetect enabled, 2 MGCP NTFY messages are sent from the MGX 8260 to the call agent. One message is sent for modem tone detection and a second for voice band detection. Eventually the repetition of this event causes all configured endpoints on the MGX 8260 to reset.

CSCdu04944

updatefls CLI command should not require path for flashfile.

The CLI updatefls command returns an error if the flashfile path is not also included in the command syntax.

CSCdu13426

Adding and deleting DS1 lines causes COT test instability.

Continually adding and deleting DS1 lines can cause COT tests to become unstable.

CSCdu16859

Event log entry needed for system clock events.

An event log entry should be made whenever there is a status change to either the primary or secondary clock. Currently clock failures/recoveries are not recorded in the event log.

CSCdu20559

BSC reset when SCC s/o due to mastership HW signal delay.

When initiating an SCC switchover, the BSC sometimes resets. This is a hardware-related problem.

CSCdu22897

DTMF mid high pitch tones after switchover.

When switchover is performed, sometimes tones are discontinued and a high-pitched tone is heard while the call connection is still active. If tones are re-sent, the high-pitched tones stop, and the correct tones are received.

CSCdu24995

lsreds command inconsistent when rdndnt NSC in slot 16.

The MGX 8260 does not display redundancy correctly in response to the lsreds command when the redundant card is in the upper slots (11 to 16) and there is BSC redundancy as well as NSC redundancy.

CSCdu30720

AddChan and/or DelChan take 2 secs.

This problem is for PRI calls only. Some calls are taking up to 2 seconds for a call setup request. The normal setup time is 0.2 second. This problem occurs only during times of high PRI call rates (for example, 30 calls per second).

CSCdu36092

Many performance alarm traps in event log but there is no alarm.

During normal traffic load tests, many performance alarm traps fill up the event log, but there is no alarm.

CSCdu38083

Congestion is detected at 70 calls/sec VoIP traffic.

At 50 VoIP calls per second, MGX 8260 call processing becomes congested.

CSCdu54353

ALBM Channel Addition fails on BSC card after SCC switchover w/red.

At 30 cps TDM with BSC redundancy, after SCC switchover, channel additions continuously fail for some of the ports on BSC cards. The event log indicates ALBM channel addition failures. Detailed analysis of the event log indicates that ALBM has the port already in connected/used state, but TCG has the same port in idle state.

CSCdu67763

add checking for CLI input parameters.

No error checking is performed on some CLI input parameters.

CSCdu74830

Speech Tone Failure with ISUP-PRI VoIP call using Hammer.

In testing ISUP to PRI and PRI to ISUP VoIP mode calls with 20/50 cps, approximately 75 percent of calls failed. ISUP to ISUP or PRI to PRI calls did not experience problems.

CSCdw03012

Cellbus congestion observed at 1000 VoIP-IMT calls.

When running VoIP calls (SS7-VoIP-SS7 setup) between two MGX 8260s, at a rate of 2 calls per second, with 1000 long-duration calls in progress, an alarm occurs. Workaround: Do not run more than 1000 VoIP-IMT calls on the MGX 8260.

Resolved Caveats

This release fixed the caveats listed in Table 4.

:

Table 4   Caveats Resolved in Release 1.2.5

Identifiers  Description 

CSCdr89536

During connection, DS3 modification should not be allowed.

CSCdt27477

Incorrect clock source card type displayed after entering the chsclksrc command.

CSCdt40426

NMS-IP addr of format xxx.xxx.xxx.0 broadcast to that subnet.

CSCdt87073

BSC s/o causes one of the ds3ln to remain in blinking yellow state.

CSCdu19148

AAL1 problem: RxDropCell counter increasing.

CSCdu28263

Non-existent NSC appears as failed card.

CSCdu37541

COT+VoIP causes AddChan Fail due to duplicate local RTP ports.

CSCdu37852

Duplicate transaction ID message is logged in event log by MGCP.

CSCdu46029

Nsc switchover causes the Nsc to failed state permanently.

CSCdu47381

~2k G.726/G.729 connections cause system to behave abnormally.

CSCdu54067

DS1 lines change to SOLID RED after resetnd and bootup.

CSCdu54837

COT terminating side need to stop once the originating side stops.

CSCdu57481

To minimize transient call drops after SCC switchover.

CSCdu58060

Standby BSC fails to boot up while high calls in progress.

CSCdu58584

Get Clock Source Card Type from Current System Clock.

CSCdu62039

H/W mphy overrun in SCC when adding ~1200 G.726 VoIP.

CSCdu66753

E1 switchover sees yellow alarm.

CSCdu66949

CLI does not allow sonetmedium type to be set to sdh.

CSCdu67935

Unable to login with Webviewer and RUDP session stopped working.

CSCdu68300

Node name missing after swcd during upgrade process.

CSCdu73430

DTMF digits not detected by 8260.

CSCdu73466

NSC FPGA drop cell when bursty cell traffic arrive cause buffer full.

CSCdu73788

Active NSC Reboots with 1 cps of PRI Calls.

CSCdu84838

After upgdcmit on SCC no further calls can be made.

CSCdv06477

OnLine Diags will cause SCC/BSC to FAIL wrongfully.

CSCdv27663

Enhancemnet on card-removal detection causes some bad side-effect.

CSCdv31969

NSC unable to recover after Add Chan Failed - Resource stuck.

CSCdv35423

Memory leak (buffer queued up) caused by fax/modem calls.

CSCdv41293

TaskMonitor crashes in malloc routine.

CSCdv48475

Service Card swover cardRemoved trap deletes Backhaul d-chans.

CSCdv60224

TEI Assign field in Dlsap Profile and D-Chan Config are incorrect.

CSCdv80244

Cell bus congestion control.

CSCdv89102

RM has to resync with NSC when there is no backcard on NSC.

CSCdw03048

BIM-SAR failure followed by SCC switchover and SCC failed to come up

CSCdw04742

SCC switchover/failed at 45cps Voip load.

Documentation Updates

Significant changes were made to the Cisco MGX 8260 Hardware Installation Guide for the 1.2.x software releases. Important updates were made to power drawings and installation procedures. For more information, please refer to this document on the web at http://www.cisco.com/univercd/cc/td/doc/product/wanbu/mgx8260/rel1_2/setup/index.htm.

There are no changes to MGX 8260 documentation for Release 1.2.5.

Related Documentation

The following Cisco publications contain additional information related to the operation of the Cisco MGX 8260 Media Gateway:

Cisco MGX 8260 Hardware Installation Guide

Cisco MGX 8260 Command Line Interface Guide

Cisco WebViewer Guide

Cisco MGX 8260 Maintenance Guide

Obtaining Documentation

The following sections provide sources for obtaining documentation from Cisco Systems.

World Wide Web

You can access the most current Cisco documentation on the World Wide Web at the following sites:

Documentation CD-ROM

Cisco documentation and additional literature are available in a CD-ROM package, which ships 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.

Ordering Documentation

Cisco documentation is available in the following ways:

http://www.cisco.com/cgi-bin/order/order_root.pl

http://www.cisco.com/go/subscription

Documentation Feedback

If you are reading Cisco product documentation on the World Wide Web, you can submit technical comments electronically. Click Feedback in the toolbar and select Documentation. After you complete the form, click Submit to send it to Cisco.

You can e-mail your comments to bug-doc@cisco.com.

To submit your comments by mail, use the response card behind the front cover of your document, or write to the following address:

Attn Document Resource Connection
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-9883

Obtaining Technical Assistance

Cisco provides Cisco.com as a starting point for all technical assistance. Customers and partners can obtain documentation, troubleshooting tips, and sample configurations from online tools. For Cisco.com registered users, additional troubleshooting tools are available from the TAC website.

Cisco.com

Cisco.com is the foundation of a suite of interactive, networked services that provides immediate, open access to Cisco information and resources at anytime, from anywhere in the world. This highly integrated Internet application is a powerful, easy-to-use tool for doing business with Cisco.

Cisco.com provides a broad range of features and services to help customers and partners streamline business processes and improve productivity. Through Cisco.com, you can find information about Cisco and our networking solutions, services, and programs. In addition, you can resolve technical issues with online technical support, download and test software packages, and order Cisco learning materials and merchandise. Valuable online skill assessment, training, and certification programs are also available.

Customers and partners can self-register on Cisco.com to obtain additional personalized information and services. Registered users can order products, check on the status of an order, access technical support, and view benefits specific to their relationships with Cisco.

To access Cisco.com, go to the following website:

http://www.cisco.com

Technical Assistance Center

The Cisco TAC website is available to all customers who need technical assistance with a Cisco product or technology that is under warranty or covered by a maintenance contract.

Contacting TAC by Using the Cisco TAC Website

If you have a priority level 3 (P3) or priority level 4 (P4) problem, contact TAC by going to the TAC website:

http://www.cisco.com/tac

P3 and P4 level problems are defined as follows:

In each of the above cases, use the Cisco TAC website to quickly find answers to your questions.

To register for Cisco.com, go to the following website:

http://www.cisco.com/register/

If you cannot resolve your technical issue by using the TAC online resources, Cisco.com registered users can open a case online by using the TAC Case Open tool at the following website:

http://www.cisco.com/tac/caseopen

Contacting TAC by Telephone

If you have a priority level 1 (P1) or priority level 2 (P2) problem, contact TAC by telephone and immediately open a case. To obtain a directory of toll-free numbers for your country, go to the following website:

http://www.cisco.com/warp/public/687/Directory/DirTAC.shtml

P1 and P2 level problems are defined as follows:

AccessPath, AtmDirector, Browse with Me, CCIP, CCSI, CD-PAC, CiscoLink, the Cisco Powered Network logo, Cisco Systems Networking Academy, the Cisco Systems Networking Academy logo, Cisco Unity, Fast Step, Follow Me Browsing, FormShare, FrameShare, IGX, Internet Quotient, IP/VC, iQ Breakthrough, iQ Expertise, iQ FastTrack, the iQ Logo, iQ Net Readiness Scorecard, MGX, the Networkers logo, ScriptBuilder, ScriptShare, SMARTnet, TransPath, Voice LAN, Wavelength Router, and WebViewer are trademarks of Cisco Systems, Inc.; Changing the Way We Work, Live, Play, and Learn, and Discover All That's Possible 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, FastHub, FastSwitch, GigaStack, IOS, IP/TV, LightStream, MICA, Network Registrar, Packet, PIX, Post-Routing, Pre-Routing, RateMUX, Registrar, SlideCast, StrataView Plus, Stratm, SwitchProbe, TeleRouter, 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. (0110R)

Copyright © 2001, Cisco Systems, Inc.
All rights reserved.


hometocprevnextglossaryfeedbacksearchhelp
Posted: Wed Nov 5 22:03:31 PST 2003
All contents are Copyright © 1992--2003 Cisco Systems, Inc. All rights reserved.
Important Notices and Privacy Statement.