Guest

Cisco MGX 8200 Series Edge Concentrators

Release Note

 Feedback

Table of Contents

Contents
System Requirements
New and Changed Information
Installation Notes
Caveats
Documentation Updates
Related Documentation
Obtaining Documentation
Obtaining Technical Assistance

June 2001

These release notes describe new features and caveats in system Software Release 1.2.3 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.3 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.3
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.03

01.02.02

MGX8260

System chassis

800-06541

-02 D2

-01 A0

N/A

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.03

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.03

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.03

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.03

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

N/A

OC3SMIBC-4

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

800-06396

-01 A0

-01 A0

N/A

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.03

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.03

01.02.02

SCC5FC-4OC32

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

800-06474

-01 A1

-01 A0

01.02.03

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.03

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

N/A

T1E1BC-50NR

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

800-06322

-01 D0

-01 D0

N/A

N/A

T1E1BC-RED

NSC back card providing 1:N redundancy support

800-06323

-01 C1

-01 B1

N/A

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

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


New and Changed Information

This section describes the new features in this release, and summarizes features from Release 1.2.2.

New Software Features in Release 1.2.3

This release contains the following new feature:

  • Fax Detection and Up-speed (T1 only)

Fax Detection and Up-speed (T1 only)

Fax signals can be distorted by some compression algorithms, such as G.729 and G.726. This problem is fixed (for T1 only) in Software Release 1.2.3. Now when the MGX 8260 detects a fax signal, it performs the following actions:

  • Turns off voice activity detection (VAD), and comfort noise generation (CNG).

  • Turns on echo cancellation (ECAN)

  • Initiates the "up-speed" of fax transmissions to G.711.

The default setting does not send an MGCP NTFY message to the call agent. You can request that a NTFY message be sent to the call agent by using chmpc command as follows:

chmpc * * * * * * * * * * 2 *

The following shows an example of the NTFY message received on fax up-speed:

	NTFY 1001 S1/DS1-10/15@mgx8260
	O: G/ft

New Software Features in Release 1.2.2

Release 1.2.2 introduced the following new features:

  • Mid-call DTMF Capture and Relay (T1 only)

  • Modem Detection and Up-speed (T1 only)

  • Multichassis E1 support

Release 1.2.2 also made changes to the following commands:

Command Description

chmpc

Use this command to configure default parameters for MGCP call control, including network types, bandwidth, service types, resource reservation, and voice encoding algorithms.

lsmpc

Use this command to list the default parameters set for MGCP call control.



For more information, see the "Documentation Updates" section.

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.3 software supports graceful upgrades from the following releases:

  • 1.2.2

  • 1.2.1

Security Key Requirements

A security key is required to transfer files to the MGX 8260 using 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 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 onto the workstation running the tftp server and locate the files to transfer.

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.03.img.[key]

tftp> put vxWorks_boot.scc.fw scc_r01.02.03.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.03.img.[key]

tftp> put vxWorks_boot.bsc.fw bsc_r01.02.03.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.03.img.[key]

tftp> put vxWorks_boot.nsc.fw nsc_r01.02.03.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 (e.g., some, but not all BSCs, or some, but not all NSCs) could cause unexpected behaviors in MGX 8260 system operation.


Note   This installation procedure describes only 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   Cisco Systems recommends that you undertake all upgrade procedures while simultaneous console connections are established to both the active and standby SCC.

Upgrading SCC Software

The upgrade process for redundant SCCs is graceful. It does not interrupt established calls, but 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 then have the option to 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 flash 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.03.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.03.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 will reset the standby SCC. Wait until the standby SCC reboots and its console session shows a standby state. The standby SCC will now be running the new release of boot flash and software images.

Step 4   You can now commit or cancel the upgrade.

upgdcmit 9

On redundant systems, the upgdcmit command will switch over the two SCCs. The previously standby SCC (with its newly upgraded database and software image) is placed into active state and the previously active SCC is reset 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 as follows:

swcd 9


Upgrading BSC Software

The upgrade process for redundant BSCs is graceful. It does not interrupt established calls, but 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 then have the option to commit or cancel the upgrade. When you commit the software, 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.03.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.03.fw

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

In redundant configurations, the upgd command will reset the secondary BSC matched with the primary BSC you specified in <logicalSlotNumber>. The secondary BSC will now be running the new release of boot flash and 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.

upgdcmit <logicalSlotNumber>

If you have redundant BSCs installed, the upgdcmit command will switch over the two BSCs. The previously secondary BSC (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 will occur.

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 as follows:

swcd <standbySlotNumber>

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

Step 8   Repeat Step 3 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 can interrupt calls in the process of being established. When you invoke the process, the MGX 8260 upgrades and restarts the standby NSC. You then have the option to commit or cancel the upgrade. When you commit the software, 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. Because of the shared nature of the redundant module, all NSC upgrades for MGX 8260 media gateways equipped with NSC redundancy must be performed sequentially in a particular order.

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.03.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, replacing the <logicalSlotNumber> with the appropriate number for your configuration.

upgd <logicalSlotNumber> nsc_r01.02.03.fw

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

In redundant configurations, the upgd command will reset the redundant NSC. The redundant NSC will 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.

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 will occur.

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

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

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 will return the NSC to No-Back-Card mode.


Configuration Database Information

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

Caveats

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

Open Caveats

The caveats in Table 2 are open in Release 1.2.3.

.


Table 2: Open Caveats
Identifiers Title Impact / Description Workaround

CSCdr03594

Telnet session suspended on active and Stby SCCs

In rare instances, debugging operations cause telnet sessions to become suspended.

N/A

CSCdr88819

Multiple tftp connections cause the tftp service to crash

Occurs only for scripts run on Microsoft Windows NT.

Run tftp only from a UNIX workstation. Do not run scripts on Microsoft Windows NT.

CSCdr89536

During connection, DS3 modification should not be allowed

During a connection, it is possible to modify DS3 parameters. This should not be possible, as it can affect calls in progress.

N/A

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.

N/A

CSCds70201

update user guide for new cli stopdisk

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

N/A

CSCds71682

typo in lsevt help message

If incorrect parameters are passed to the lsevt CLI command, the usage message describes the date as dd/mm/yyyy instead of mm/dd/yyyy.

When entering the lsevt CLI command, structure your command in the format mm/dd/yyyy.

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.

N/A

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.

N/A

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 the user continues operations with 2300 connections, the database will somehow become corrupted and will result in MGCP reporting 540 on CRCX and 400 on MDCX with the very first endpoint.

N/A

CSCdt00517

DTMF mid-signal duration not working properly

DTMF mid-signal duration is not working correctly. A DTMF signal may not be detected if the signal duration is borderline.

N/A

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

Upon occurrence of cell bus BIP-8 problems, the cell bus controller (Cubit) driver on the SCC and NSC does not accurately report the problem. Furthermore, upon this specific error condition, the SCC/NSC is not switched over. The occurrence of cell bus BIP-8 problem itself can be intermittent due to defective hardware. This problem is associated with the occurrence of BIP-8 cell bus problems.

N/A

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.

N/A

CSCdt21007

BSC Environmental Monitoring Module (EMM) Reports Failed

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

N/A

CSCdt27477

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

After changing the secondary clocking source, the Clock Source Card Type field displayed by lsclksrc shows the secondary clocking source rather than the current clocking source.

N/A

CSCdt31117

Misleading information on T1 lines in the documentation.

The MGX 8260 documentation for DS1/T1 lines states that the received direction is always set to robbed bit. This should be changed to state that the default signal mode for DS1/T1 lines in the receive direction is None, rather than robbed bit signaling.

N/A

CSCdt40426

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

IP addresses of the format xxx.xxx.xxx.0 are broadcast to IP addresses in that subnet. Unless this is intended, such as the manager IP address in the community string, then it is possible that the recipient host is not the intended target of the message. This problem is found in the email server IP configuration and the trap manager IP address configuration. These features are not intended for broadcast.

N/A

CSCdt56759

Tones not measured correctly with gain less than -38dBm in E1

N/A

N/A

CSCdt60334

E1MC: PSQM score is too high

E1 VoIP voice calls may have reduced quality. Workaround is to not use high compression codecs for voice calls.

Do not use high compression codecs for voice calls.

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.

None

CSCdt72583

DS1 Bert failure on repetitive patterns

During a Bert for DS1 on NSC, with repetitive patterns.
1) With error insertion, COMET sometimes will report error rate mismatch;
2) Without error insertion, COMET sometimes indicates that error bits are detected;
These cases are very likely to happen on patterns 3in24 and 1in16.

N/A

CSCdt75173

System Name is lost after resetnd or upgrade

N/A

N/A

CSCdt77965

clrndcnf may potentially lose trap mgr info if SCC switches over

When the node configuration is cleared, the trap Register RAM information is backed up in a temporary file. When the node rebuilds, this backup file is restored so that traps can be generated when the node is rebuilt. On normal operation, when the node configuration is cleared, when the Active card is reset, the same active card is assumed to still be the active one. However, in the SCC mastership arbitration, if the once ACTIVE card gives up mastership and the standby SCC takes over before the trap manager backup is restored, all trap manager information is gone. The Active SCC does not update the standby SCC trap register RAM information, which is the source of information for backing up the trap information.

Update the standby SCC's trap register RAM information. When clrndcnf is invoked, the standby SCC should also invoke the SnmpDbSave function so it can save its RAM information. If the SCC comes up as standby, it should not restore the backup. It should wait for updates from the Active card. If there is an ungraceful switchover and the standby SCC becomes active, it will restore the backup trap manager.

CSCdt83222

SCC switch over when adding inactive FastEthernet lines

When 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 two Fast Ethernet lines on the primary and secondary become active, the SCC also switches over.

N/A

CSCdt84087

TCG reports AAL1 add error

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

N/A

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 result from the MGX 8260 when transponder continuity testing is requested on a endpoint before the terminating call is setup.

N/A

CSCdt87073

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

While performing graceful shutdown of the BSC, when a call is active, one of the DS3 lines goes to a permanent blinking yellow state.

N/A

CSCdt89367

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

N/A

N/A

CSCdt89970

Standby NSC cannot be upgraded

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

N/A

CSCdt90496

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 currently 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.

N/A

CSCdt91753

System Date accepting invalid values

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

N/A

CSCdt94852

FAX call failed sometimes on data transmission stage

Fax calls sometimes fail during data transmission stage. This problem is different from what has been addressed in resolved issue CSCdt59149 where the failure happens during negotiation stage.

N/A

CSCdt96988

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

COT transponder tests may fail when the sctTimeout value in the COT tests is set to a small number, e.g. 100 ms.

N/A

CSCdu00119

D channels dropped during BSC switchover

N/A

N/A

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 modemup-speed is set to G.711. This processing of the MDCX message by TCG will cause multiple instances of modem tone to be detected. As a result, MPC will then report multiple MT NTFY messages to the call agent.

N/A

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.

Customers using release 1.2.2 or prior software should manually turn off the fax/modem reporting via the CLI command 'chmpc'. Customers using release 1.2.3 will have the fax/modem reporting configuration set to off as default.

CSCdu03115

All endpoints reset due to 1 unack message

Using G.726 32k codec selection, when a modem call with FaxModemDetect enabled, 2 MGCP NTFY messages are sent from the MGX 8260. One message is sent for modem tone detection and a second with voice band data detection. Eventually the repetition of this event results in all configured endpoints on the MGX 8260 to reset.

N/A

CSCdu04802

clrndinf dosent clear inband ip address

Clearing node config should clear inband ip, so the value would be at default again. This does not occur. When the clrndinf command is used, the inband ip address is not reset to the default.

N/A

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.

N/A

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.

N/A

CSCdu18974

SCC resetcd boots all cards and fails them

When you reset the SCC card with a redundant SCC card, all cards in the chassis reboot and later fail. You then need to use the resetnd command to return to the normal mode.

N/A

CSCdu22897

DTMFmid high pitch tones after switchover

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

N/A

CSCdu23980

NSC Standby responds badly to swcd command

When the redundant NSC module is in active state and the swcd command is issued to return this module to Standby state (and reactive the primary NSC), the standby card boots to Failed state.

N/A

CSCdu24995

lsreds command inconsistent when rdndnt NSC in slot 16

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

N/A

CSCdu26624

Received functions of lsmacsapstat command do not work.

The received fields of the lsmacsapstat command do not display any received statistics. These fields include Received Frames, Received Bytes, and Received Queued.

N/A

CSCdu26823

Dchan display reports Arbitration scheme as passive when active set

The Macsap profile has a parameter called "Link Arbitration Setup Scheme". This parameter is set to either "active" or "passive". When set to "active", it should be reported as active when viewing the details of a Dchan that is using the specific Macsap profile. Instead, the Dchan detail reports the arbitration scheme as passive.

N/A

CSCdu30720

AddChan and/or DelChan take 2 secs.

This problem is for PRI calls only. Some calls are taking up to 2 seconds for call setup request. The normal setup time is 0.2 seconds. This problem only occurs during high PRI call rates, such as 30 calls per second.

None

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.

N/A

CSCdu37541

Channel addition fails on TCG

N/A

N/A

CSCdu38083

Congestion is detected at 70 calls/sec VoIP traffic

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

N/A



Resolved Caveats

This release fixed the caveats listed in Table 3.

:


Table 3: Resolved Caveats
Identifiers Description

CSCds56950

Packet drops after adding more than 220 channels in E1 mode

CSCdt02274

lsacts command does not work

CSCdt22600

Cannot Delete Community String

CSCdt26200

clralmhist does not work

CSCdt29554

Need to support more channels per dsp for G.726

CSCdt32628

E1MC: Bearer path dropped on NSC s/o using snake config

CSCdt33122

Gateway Ip deleted when issue clrndcnf command

CSCdt33468

SCC Card Failure - No Failure Reason

CSCdt34657

dbrstr command can catastrophically fail

CSCdt34667

dbbkup can clobber existing backup file

CSCdt34675

Upon upgd standby SCCs files not updated.

CSCdt34694

Standby SCC should be forced to same revision as active SCC.

CSCdt34787

E1MC: All cards go to FAIL state when deleting bh session

CSCdt35761

chlpip command returns an error

CSCdt36019

SCC switched over after clrndcnf with error

CSCdt37063

dbrstr needs to check software version

CSCdt38399

dbbkup command does not store file to standby SCC.

CSCdt39098

end-of-DTMF is not sent

CSCdt39543

Standby SCC Card Went to Failed State after Resetting Entire Node

CSCdt40739

DSE does not receive packets from the network side

CSCdt41862

Idle Code byte set in wrong channel

CSCdt44307

1.2.e1 MDCX 502s to remove loopback with COT at 12% 40CPS

CSCdt47660

remove 2Mbyte limit on disk image size

CSCdt48207

mpc parms lost on upgrade due to DBM maxNum of table mishandling

CSCdt51323

Cannot telnet after overnight run

CSCdt53625

NTFY message was only sent out from one side

CSCdt55435

NTFY O: G/$sent to CA for Modem Up-Speed

CSCdt57005

BERT test does not contain same choices as previous release

CSCdt58544

clrndcnf causes tmmsShell0 task to crash

CSCdt61382

PB: RED NSC card doesn't report being removed

CSCdt62493

NSC Reboots during SCC SwOver

CSCdt62506

NTFY missing mandatory X: value

CSCdt62559

MDCX with NTFY request rejected by 8260

CSCdt64839

PB:re-insert SCC card caused OC3 lines go yellow

CSCdt65144

PB: re-insert SCC card caused NSC cards randomly reboot

CSCdt67011

PB: reinsert Stby SCC card could cause the card in failed state

CSCdt67821

PB: some DS0s get 502 return code after MDCX message

CSCdt68355

NSC upgrade commit causes d channel to drop

CSCdt69460

In a multinode system, inserting stby SCC causes rem NSC reset

CSCdt72591

Need SNMP support for dbbkup and dbrstr

CSCdt72631

CRM timer is not reset causing standby to reboot

CSCdt72642

Event log about Ack not received from tRudpAppl

CSCdt74138

CLI lsacps causes TLB Load Exception

CSCdt75199

Disk failure problem associated with standby reset

CSCdt75230

Diag failed OC3 loopback tests

CSCdt77394

upgd command confirmation not clear at all

CSCdt77876

SWCD 9 caused loss of chassis / telnet lost

CSCdt78183

Dejitter packet drops after BSC switchover

CSCdt78365

MRPC L3 statistics added to facilitate debugging

CSCdt79869

MRPC L2 RETX threshold (FATAL)

CSCdt81762

ISDN backhaul does not send REL_RSP in response to REL_REQ

CSCdt82754

New Congestion Check Mechanism for end point operations

CSCdt85167

Invoking MIB-related CLI commands before SNMP init may cause reset

CSCdt85475

NSC reset when receiving 5ms packet loading packets

CSCdt85737

MPC and RMG get out of synch during COT

CSCdt85940

SCC card goes to FAIL state with IPDC config in r01.02.f2 image

CSCdt86250

MGX 8260 doesn't report yellow alarm on DS-1 on a BSC DS-3 card

CSCdt87124

While doing SCC switchover, Fast Ethernet subnet mask changes to 0.0.0.0

CSCdt87134

If we add all 4 FE lines NSC switchover causes voice path broken in one dir

CSCdt87638

MPC crashes when running 30% COT and due to a line alarm

CSCdt89970

Standby NSC cannot be upgraded

CSCdt91005

Both SCCs are stuck in SLAVE_SYNCH

CSCdt91733

Modem Upspeed(V.90) call does not go through

CSCdt93549

TCG crashes in the middle of call deletion

CSCdt95503

During dbrstr, SCC switch over happened because of some major event

CSCdt95540

DLCX is rejected with 513 error code

CSCdt97110

NTFY G:vbd sent when there is a CODEC mismatch

CSCdt97179

PRI links go down when using FE for call control

CSCdu00576

IdeStop should check for interrupt context

CSCdu00633

NSC sometimes found in failed state due to lost heartbeat

CSCdu01067

Modem Call fails in NSC Redundancy Testing w/ E1 multichassis

CSCdu01097

Successful modem connection need multiple trials

CSCdu06360

TDM calls hung after resetcd BSC

CSCdu09692

No voice path 8260/5300 at 20 MS pktn

CSCdu12834

Memory corruption when running load test

CSCdu15446

MPC gets suspended while running 10cps

CSCdu15452

rtpport table overwrites memory

CSCdu23423

MGX stopped processing calls

CSCdu26667

upgd command for NSC should be disabled

CSCdu26760

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

CSCdu28168

Selection of LAPD Type via WebViewer provides incorrect LAPD type

CSCdu29048

Entering a period for any IP address field is accepted with no error msg

CSCdu37852

Duplicate transaction ID message is logged in event log by MGCP



Documentation Updates

This section describes the commands introduced or changed in Releases 1.2.2 and 1.2.3. These additions and changes apply to the Cisco MGX 8260 Command Line Interface Guide.

Commands Changed in Release 1.2.3

Release 1.2.3 changes the default for the DefReportFxMdmDet parameter in the chmpc command. The "chmpc" section shows this change.

There are no new commands introduced for this release.

Commands Changed in Release 1.2.2

Release 1.2.2 changed the chmpc and lsmpc commands. The chmpc command has two new parameters and the lmpc command lists these two new parameters.

chmpc

Configure default MPC parameters.

chmpc DefTypeNetwork DefPktnPeriod DefBandwidth DefEchoCancel DefSilenceSupp DefTypeOfService DefResourceRes DefCOTReceiveTone DefCOTTransmitTone DefEncodingType DefReportFxMdmDet DefModemUpspeed

Syntax Description

DefTypeNetwork

The type of network.

1 = voIp

2 = voAtm

3 = local

DefPktnPeriod

Packetization period in milliseconds. Value: fixed at 10

DefBandwidth

The network bandwidth in kbps. Values: 8 and 64 kbps

DefEchoCancel

Enables or disables echo cancellation.

1 = off

2 = on

DefSilenceSupp

Enables or disables silence suppression.

1 = off

2 = on

DefTypeOfService

The type of Service. Values: 1-256, where 1 indicates no service type

DefResourceRes

The resource reservation type.

1 = bestEffort

2 = guaranteed

3 = notUsed

4 = controlledLoad

DefCOTReceiveTone

The default receive tone. For transponder COT, when the media gateway controller does not supply the tones, the default tone the gateway receives is the default COT receive tone.

1 = co1 (2010 Hz)

2 = co2 (1780 Hz)

DefCOTTransmitTone

The default transmit tone. For transponder COT, when the media gateway controller does not supply the tones, the default tone the gateway transmits is the default COT transmit tone.

1 = co1

2 = co2

DefEncodingType

The type of voice encoding when not specified by the MGC:

1 = PCMA—A-law encoding

2 = PCMU—Mu-law encoding

3 = G729A

4 = G72632K

DefReportFxMdmDet

Enables or disables the fax and modem upspeed reporting to the call agent.

Values:

1 = Disable reporting

2 = Enable reporting

DefModemUpspeed

The modem up-speed encoding used when the line card detects modem tone on the active connection.

Values:

1 = clearChannel

2 = G.711 u-law for T1



Defaults

DefTypeNetwork: 3

DefPktnPeriod: 10

DefBandwidth: 64

DefEchoCancel: 1

DefSilenceSupp: 1

DefTypeOfService: 2

DefResourceRes: 1

DefCOTReceiveTone: 1

DefCOTTransmitTone: 2

DefEncodingType: 1

DefReportFxMdmDet: (Release 1.2.2): 2 (Release 1.2.3): 1

DefModemUpspeed: 1

Command Modes

Security level 2

Command History

Release Modification

1.2

This command was first introduced.

1.2.2

Added modem and up-speed parameters.

1.2.3

Changed the DefReportFxMdmDet default from 2 to 1.



Usage Guidelines

Use this command to configure default MPC parameters.

Examples

The following command changes the up-speed encoding to G.711.

chmpc * * * * * * * * * * * 2
Related Commands

Command Description

lsmpc

List MPC information.



lsmpc

List MPC parameters.

lsmpc

Syntax Description

The command has no arguments or keywords.

Defaults

No default behavior or values.

Command Modes

Security level 5

Command History

Release Modification

1.2

This command was first introduced.

1.2.2

Listing extended to include new parameters.



Usage Guidelines

Use this command to list the MPC parameters.

Examples

The following example displays MPC parameters.

lsmpc 
 
=========================================================================
MPC Parameters (lsmpc)
=========================================================================
 
Default Type of Network            : local
Packetization Period               : 10
Bandwidth                          : 64
Echo Cancellation                  : off
Silence Suppression                : off
Type of Service                    : 1
Resource Reservation               : bestEffort
Default COT Receive Tone           : co2
Default COT Transmit Tone          : co1
Default Encoding Type              : pcmu
Report Modem Upspeed Detection     : no
Modem Up-speed Option              : clearChannel 
 

The last two parameters indicate whether the Modem Detection feature is enabled, and the type of modem up-speed configured.

Related Commands

Command Description

chmpc

Change MPC information.



Related Documentation

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


Table 4: Related Software Documentation
Documentation Description

Cisco MGX 8260 Hardware Installation Guide

DOC-7810966=

Describes the procedures for hardware installation and initial software setup.

Cisco MGX 8260 Command Line Interface Guide

DOC-7810987=

Describes how to configure MGX 8260 Media Gateways from the command line interface.

Cisco WebViewer Guide

DOC-7811012=

Describes how to use the Cisco WebViewer tool.



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 as an annual subscription.

Ordering Documentation

Cisco documentation is available in the following ways:

  • Registered Cisco Direct Customers can order Cisco Product documentation from the Networking Products MarketPlace:

http://www.cisco.com/public/ordsum.html

  • Registered Cisco.com users can order the Documentation CD-ROM 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 corporate headquarters (California, USA) at 408 526-7208 or, in North America, by calling 800 553-NETS(6387).

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:

  • P3—Your network performance is degraded. Network functionality is noticeably impaired, but most business operations continue.

  • P4—You need information or assistance on Cisco product capabilities, product installation, or basic product configuration.

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:

  • P1—Your production network is down, causing a critical impact to business operations if service is not restored quickly. No workaround is available.

  • P2—Your production network is severely degraded, affecting significant aspects of your business operations. No workaround is available.

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

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