Cisco MGX 8800 Series Switches

CSCdp39955

Symptom

Deleted channels on FRSM reappearing after the card is reset.

Condition:

When delchan was issued on the FRSM , FRSM did not send a disk update message to the PXM. this seems to be a FRSM-related issue.

CSCdp35989

Symptom:

A flood of invalid LMI frames overruns the LMI queue causing random LMI failures on other ports.

Condition:

Flooding LMI frames on one port.

Workaround:

Stop the flood of invalid LMI messages.

CSCdk63920

Symptom

Adding connection on PXM interface with VPI value larger than 255 will be successful, but the data will not flow.

Condition

On PXM BBIF (broadband interface), HW supports VPI range of 0-4095. However, there is a FW restriction which limits the VPI range to 0-255. The result of this further limit that a feeder connection originated from a service module (SM) can have a VPI value no larger than 255 on the feeder trunk; and a connection between a SM and PXM UNI can have a VPI value on the PXM UNI interface of no more than 255.

Example 1:

SM - PXM feeder trunk - bpx - bpx - PXM feeder trunk - SM

VPI value [0-255] [0-255] [0-255] [0-255]

Example 2:

SM --- PXM UNI

VPI range [0-255] [0-255]

For all other DAX conns this is not an issue, since SMs only support VPI up to 255.

Workaround:

Use VPI 0 - 255 when adding connections.

CSCdm00200

Symptom:

PCI errors cause VISM to reboot without displaying/logging error source!

CSCdm14439

Symptom:

Cannot stop an UPLOAD data capture session once it begins.

CSCdm21316

Symptom:

Can not do clrsmcnf for a VISM card

CSCdm33635

Conditions:

During switchback, dspcds shows neither card as active.

Symptoms:

During switchback processing for a 1:1 redundant FRSM-2CT3, neither card is shown active; there is also no redundancy indication:

Initially, the redundancy information is displayed as follows:

taggmt42.1.7.PXM.a > dspcds

     Slot  CardState    CardType     CardAlarm  Redundancy

     ----  -----------  --------     ---------  -----------

     1.1   Standby      FRSM-2CT3    Clear     Covered by slot 2

     1.2   Active       FRSM-2CT3    Major     Covering slot 1

 taggmt42.1.7.PXM.a > switchback 2 1

 Do you want to proceed (Yes/No)? Yes

 taggmt42.1.7.PXM.a > dsplog

 04/25/1999-08:01:52 07 tTnCmdTsk02 RED-7-AC_INFO_ERR

  Error Event switchBack() successful

 04/25/1999-08:01:52 07 tTnCmdTsk02 PMM-7-RST_REQ

  Reset request: SM Reset, 2

 04/25/1999-08:01:52 07 tTnCmdTsk02 RED-7-SMM_INFO

System Information : switchback:

 slot 2 (cardInx 3) is present, insertion msg from 7

taggmt42.1.7.PXM.a > dspcds

     Slot  CardState    CardType     CardAlarm  Redundancy

     ----  -----------  --------     ---------  -----------

     1.1   Standby      FRSM-2CT3    Clear

     1.2   Boot         FRSM-2CT3    Clear

 taggmt42.1.7.PXM.a > dspcds

     Slot  CardState    CardType     CardAlarm  Redundancy

     ----  -----------  --------     ---------  -----------

     1.1   Standby      FRSM-2CT3    Clear

     1.2   Reserved     FRSM-2CT3    Clear

 slot 2 (cardInx 3) is present, insertion msg from 7

 taggmt42.1.7.PXM.a > dspcds

     Slot  CardState    CardType     CardAlarm  Redundancy

     ----  -----------  --------     ---------  -----------

     1.1   Standby      FRSM-2CT3    Clear

     1.2   CardInit                  Clear

     Slot  CardState    CardType     CardAlarm  Redundancy

     ----  -----------  --------     ---------  -----------

     1.1   Active       FRSM-2CT3    Major

     1.2   Standby      FRSM-2CT3    Clear

Workaround:

There is currently no work around for this.

CSCdm33996

Symptom:

Error log shows an invalid SSI_MQID of 0xFFFFFFFF has been passed as an argument to SSI calls by the "tSmterd" task.

Conditions:

This may occur if the user tries to "cc" to a standby PXM immediately after it becomes "standby".

Workaround:

The "cc" session with the above error will fail. The user can try again in 30 seconds after the CPU is free from the busy-burst right after the board turns "standby".

CSCdm35462

Symptom:

Unable to add SRM lines from PXM in slot 8

Fix:

The Line and alarm related commands are modified to allow Slots 8, 16 and 32 as valid arguments if PXM at slot 8 is active. The following commands are affected by this:

* addln

* delln

* cnfln

* dspln

* dsplns

* addlnloop

* dellnloop

* cnfsrmclksrc

* dspsrmclksrc

* dspalm

* dspalms

* dspalmcnt

* clralmcnt

* clralm

* dspalmcnf

CSCdm38278

Symptom:

CiscoView enables SRM line automatically if other parameters are altered.

Conditions:

Do a Line....config on any T3 line on an active SRM card.

Verify if the line is disabled

Try altering any of the parameters in the "Physical Line Config(dsx3)" menu. For example, change the line loopback from dsx3NoLoop to dsx3remotelineloop.

The "Line Enable" parameter also automatically gets toggled and the line gets enabled.

CSCdm40113

Symptom:

It takes over 20 minutes for the FRSM-2CT3 cards to go active after a clrallcnf command has been issued.

Conditions:

Occurs when there are several FRSM-2CT3s in the shelf along with other service modules.

Workaround:

None. Wait for cards to go active.

Further Problem Description:

Creation of default service module config takes a long time and is processed one service module at a time. Subsequently, all the other SM wait to go active until the default config upload for all the service modules are done.

CSCdm45217

Symptom:

SM shows misleading Reset reason

CSCdm45565

Symptom:

Cannot add ATM-ATM connection due to wrong UPC values

CSCdm49847

Symptom:

dsplns returns undefined symbol dsplns on FRSM-VHS2E3

CSCdm57910

Symptom:

An Address load Exception occurred on the ACTIVE PXM.

CSCdm60448

Symptom:

SRM-3T3 X-bits not in compliance with standards

CScdm61211,CSCdm61376

Symptom:

dsptrkload does not show any information about trunk load.

CSCdm63240

Symptom:

IMA ports on AUSM cards connected back to back via bulk distribution through SRM are disabled for 15 seconds on switchcc.

CSCdm64109

Symptom:

AUSM does not report an LOS when link is deleted from SRM

CSCdm66841

Symptom:

0 Slot ID sent from Atmizer to CB Slave

CSCdm68837

Symptom:

Softswitch on the FRSM-2CT3 cards takes 2 minutes per 100 connections to execute.

CSCdm68952

Symptom:

runslftstno 5 run on AUSM shows Disk Data Corruption even though test passes

CSCdm73833

Symptom:

Dspchancnt on AUSM should show current ingress queue length

CSCdm73841

Symptom:

Missing IMA link counters in AUSM CLI.

CSCdm74358

Symptom:

k_chanCntGrp has not been implemented in VISM 1.0

CSCdm75342

Symptom:

After resetcd, all configuration for HS2 card is lost

CSCdm76573

Symptom:

dsx3LineLength setting is not working for FRSM-2T3/E3

CSCdm77618

Symptom:

PXM Core Redundancy is lost if the right/bottom latch is opened and closed

CSCdm78193

Symptom:

Traffic generation functionality does not work in FRSM 8E1

CSCdm78448

Symptom:

FRSM-2CT3 card displays 'temporarily out of buffers' when scrolling through a dspcons display.

CSCdm80527

Symptom:

Cannot set dsx3PlcpPayloadScramble from SNMP.

CSCdm80773

Symptom:

clralm/clralms command does not provide help syntax

CSCdm81358

Symptom:

Softswitch on AUSM causes remote end to go in and out of alarm.

Condition

When a softswitch is done, the DS1 lines are through the distribution bus (SRM) and the SRM now has to send the data to a different card (Redundant card), this causes a glitch (errors) in the DS1 lines. The AIM Group goes into failed state because of these errors. When the AIM Group goes into failed state the channels go into alarm and so the remote end of the channel also goes into alarm. When the AIM Group recovers, the channels come out of alarm.

Workaround:

Do not report the port alarm immediately to the connection manager. Integrate the port alarm for 't' seconds. If the alarm persists even after time 't', inform connection manager. Else, connection manager need not know about alarm at all. The main disadvantage of connections going into alarm at all. The main disadvantage of connections going into alarm, is that recovery time is in seconds. So delay in data transfer is going to be more. This is avoided by masking the port alarm to connection manager.

CSCdm81375

Symptom:

Phantom channels on cards that don't have lines or ports enabled

CSCdm84845, CSCdm84850

Symptom:

Card Information field (Card Reset Reason) is not consistent with the CLI.

CSCdm86362

Symptom:

Comfort Noise is not turned ON when VAD is turn ON.

CSCdm88721

Symptom:

In a shelf with core card redundancy, both PXMs got reset while executing switchcc.

CSCdm90248

Symptom:

All the channels do not come out of alarm after a hot standby switchback

Description:

The active card and the standby card can have different configurations if the line is in clear state, because no line clear trap would be sent after the active trap.

Resolution:

The system now clears the port state after receiving functionModuleActive trap.

CSCdm90295

Symptom:

Remote loops put up are not displayed by dspln command

CSCdm91925

Symptom:

Some commands execute after entering only one letter.

Description:

The 3 commands actually correspond to:

f = format

s = saveallcnf

b = bootChange

The first one "f" is the most harmful. this could format the PXM hard-disk.

the next two are not harmful though. It appears that these three commands appear first among all the commands that begin with these letters. This is also found to be true on the Popeye shelf. This is not found with all letters.

The CLI Command Parser searches for the closest match if it cannot find the exact match.Sometimes there is only one command beginning with certain characters;like there is only one command beginning with "f" i.e. formatdisk.Hence that command is executed when only one alphabet is typed.In this case to let the user know what command is executed,the executed command name is displayed.

CSCdm92288

Symptom:

On removal of the active back-card, redundancy switchover fails in hot-stdby

Condition:

Resetting the standby card while it is being configured to be a hot standby. In this case, Primary (17) is active and Secondary(19) is in HotStandby. The backcard of 17 was removed and NOT reinserted. This causes switchover to 19, which becomes active. The PXM now tries to make 17 to be a Hot Standby and to do so downloads the PRI file to 17. While the PRI download is in progress, the backcard of 17 is reinserted, causing 17 to reset and the PRI download to fail.

WorkAround:

Remember that both inserting and removal of backcards cause VHS cards to reset.

Allow standby cards to become hotstandby by waiting for a few minutes before resetting them. You can find out if the card is in hot standby by executing the "dsphotstandby" command on the PXM.

CSCdm92305

Symptom:

dspcds, dspred & dsphotstandby commands display inconsistent card states

CSCdm93789

Symptom:

Memory leak causes SM to mismatch after running resetcd.

CSCdm93970

Symptom:

Image mismatch when downloading firmware to standby PXM in backup boot.

CSCdm94630

Symptom:

Multiple traps generated due to reset of standby PXM.

CSCdp00721

Symptom:

Redundant active CT3 card comes up in mismatch & standby doesn't take over

CSCdp00894

Symptom:

tftp put command creates the wrong file name when option

POPEYE@PXM.FW used

CSCdp00909

Symptom:

Customer needs a way to identify node via CLI as SES

CSCdp00911

Symptom:

APS lost track of which PXM is active and won't allow commands on active PXM

CSCdp02813

Symptom:

FRSM-VHS - tstcon/tstdelay to UXM UNI port cons fail nearly every time

CSCdp04258

Symptom:

PXM drops incremental updates while SM goes to HotStandby

CSCdp04475

Symptom:

Rounding off errors occur when CWM and the CLI are used together to configure a ForeSight connection.

Conditions:

Refer to Eng-Note for the details.

Workaround:

Since the CLI takes any value greater than the CIR converted to CPS (with rounding off errors. e.g 1333cps for a 512k connection), to avoid the problem user should do the rounding off manually and give it in the CLI.

CSCdp05115

Symptom:

Cell-loss on CESM-feeder connections after new-rev command execution

CSCdp07010, CSCdm57910

Symptom:

Could not configure i/f as trunk initially until background check failed

CSCdp08034

Symptom:

Timezone gets reset back to GMT after PXM FW upgrade.

CSCdp08186

Symptom:
PXM went into a constant reboot state after a resetsys was issued.
Conditions:
The contents of the hard disk is corrupted on two rpm connections: vpi/vci 0/97 and vpi/vci 0/320. 0/97 has illegal port number 96. 0/320 has illegal port number 319. Both of these cause exception when trying to access the port block structure, thus result in reset.
The prevention to skip the access to illegal port block is already in 1.1.12. However the root cause of the corruption is still under investigation.

Workaround:
Due to the corruption in the hard disk, when the PXM is going through a reset, it will be trapped in this reset loop. In some occasion, with redundant PXMs, the reset loop stops after 3-5 iterations. If it does not breakout of the loop by itself, the following command must be entered at the shellConn prompt after VxWorks banner appears:

dbmClrAllCnf

<ctrl> <x> (to reset the card)

The system will come up with empty database, except nodename and ip address. The configuration has to be added.

Since the saved configuration has the corrupted contents from the hard disk, performing "restoreallcnf -f filename.zip" will encounter this exception again during the channel mib parsing. This result in reset loop.

CSCdp11717

Symptom:

Security risk with hard coded community strings for SNMP access

Workaround:

There is currently no work around for this.

CSCdp11982

Symptom:

OC3 jitter higher than the normal standards specs

CSCdp12285

Symptom:

FRSM-2CT3 card failed during data transfer

CSCdp12705

Symptom:

Standby VHS card not taking over when the ACTIVE VHS

card is reset.

CSCdp14439

Symptom:

clrallcnf fixed so that it does not default the netmask.

CSCdp15333, CSCdp15346

Symptom:

EIR MIB Implementation for 0 CIR connections

CSCdp15490

Symptom:

dspcd got wrong backcard NVRAM info

CSCdp16649

Symptom:

System reset caused during upgrade to 1.1.11Jd

Conditions:

Upgrade was being performed from 1.1.11Ja to 1.1.11Jd.

The install 1.1.11Jd command was executed on slot 8; slot 7 came up in hold state The newrev 1.1.11Jd command was executed on slot 8, at which point the shelf reset. After the reset, Slot 7 (1.1.11Jd) came up active, slot 8 was in hold (1.1.11Ja). When the dsplog command was executed, it could not read the last file. This file was manually transferred over, its contents are as follows:

dsplog

  ^M10/08/1999-12:02:19 08 tTnCmdTsk01INST-7-COMMAND1             
install

 1.1.11jD

 ^M10/08/1999-12:02:25 08 tTnCmdTsk01INST-7-COMMAND1             install

 1.1.11Jd

 ^M10/08/1999-12:02:27 07 tPMM        PMM-7-RST_REQ              Reset

 request: , 1

 ^

Workaround:

There is currently no work around for this.

CSCdp17156

Symptom:

Removal of active PXM backcard, caused APS switch as expected, but clocking reverted to internal oscillator

Conditions:

XM=1.1.11Jd

System is configured for APS.

Primary clock source is set to derive from uplink trunk.

When the line module backcard was removed from the active PXM, APS switch took place to the protection line as expected. However the clock source (as viewed from dspcurclk) reverted to the internal oscillator, instead of continuing to derive from the protection line. It stayed on the internal oscillator until the backcard was re-installed on the active PXM - the aps line continued to stay on protection because aps was configured as non-revertive.

Workaround:

Do not remove back card.

CSCdp17292

Symptom:

FRSM-2CT3 card fails after multiple softswitch

CSCdp18806

Symptom:

Disk cache not updated when boot fails

CSCdp26382

Symptom:

Protection APS line, when active, does not go into Sig_fail state when threshold is reached, and goes into P_B state when working line is made to go into Signal_Degrade.

CSCdp26521

Symptom:

Secondary card went into FAILED state while upgrading from

1.1.12Kh to Kj.

CSCdp27483

Symptom:

SPM null pointer fixes

CSCdp28741

Symptom:

dsptrkload does not show any information about trunk load

CSCdp29095

Symptom:

PXM1-OC12 config upload file incorrect

CSCdp29275

Symptom:

System error msgs 21205, 21202, 20617 & 20420

Condition:

The delay is due to the creation time of the FRSM-VHS database on the disk. This delay is only introduced the first time the card is inserted or after clrallcnf.

Workaround:

Wait for card to go active. The Hot Standby Feature has been introduced for VHS to mitigate this problem. With a hot standby the switchover happens in less than one second.

CSCdp29597

Symptom:

Software Exception:Vector 2 EPC:0x8003580c ADR:0x0e1d2ea0

CSCdp29775

Symptom:

Several FRSM-8T1 &VHS Service Modules were in failed/stdby after upgrade and resetsys

Condition:

The upgrade procedure went through fine but after executing the resetsys command the FRSM-8T1 & VHS service modules which had redundancy came up in failed state.

Workaround:

None.

CSCdp35045

Symptom:

All the connections declared failed after switchcc

Condition:

After switchcc, channels are in alarm. PAR declares "local interface failure" for all connections even though some cards still have data continuity. From PXM the connections indicate "failed".

CSCdp41514

Symptom:

Some conns goes to FAILED (with error Local I/F failure) even though I/F is UP

Workaround:

When the connection state is seen to be incorrect immediately after provisioning as described in this bug report (e.g. FAILED when it should have been OK), following is a workaround to rectify the status:

1 Delete Master End and Slave End

2 Provision Slave End and Master End

3 Check that connection Status is OK (assuming there are no other genuine reasons for the connection status to be failed - like interface failure, alarm due to AIS).

CSCdm83469, CSCdp08711

Symptom:

Lines on FRSM get disabled

CSCdk72991

Symptom:

FRSM-VHS takes several minutes to go active when inserted the first time or after clrallcnf.

Condition:

The delay is due to the creation time of the FRSM-VHS database on the disk. This delay is only introduced the first time the card is inserted or after clrallcnf.

Workaround:

Wait for card to go active. The Hot Standby Feature has been introduced for VHS to mitigate this problem. With a hot standby the switchover happens in less than one second.

CSCdm89192

Symptom:

Oscillation of APS lines on switchcc.

CSCdm46620

Symptom:

PXM and SRM do not display the Fab # via dspcd command like other SMs

CSCdm49706

Symptom:

PXM gives unwanted Error Messages after switchcc

CSCdp16642

Symptom:

dspln -ds3 command does not work for SRMs in 1.1.11Jd

Conditions:

When the PXM firmware is of a version later than 1.1.11Ja and the PXM back card is not a T3 back card.

Workaround:

Issue the command dsplns -ds3 <slotno> to get the required information.

Further Problem Description:

The problem occurs because of an invalid conditional checking during the display.

CSCdm45533

Symptom:

Round trip delay test results do not change on changing CDVT for CE-CE connection

Conditions:

1 While adding a connection, the aal1driver added the connection with default CDVT of 1000us. After adding the connection, the CDVT was configured. This effect of CDVT change was felt only after a channel failure

2 When modifying CDVT with cnfcon too, the same problem was found, because of the CBR traffic, the buffer size cannot be changed dynamically without dropping data, hence it was not possible to see the effect of change in CDVT immediately.

Workaround:

1 The first problem can be overcome by using CWM or the xcnfchan command to add a connection with value of CDVT different from the default

2 For dynamic changes in round trip as a result of CDVT changes, a shellConn command is introduced to synchronize the SAR queues. This command would, however, cause a momentary traffic disruption for CDVT to take effect

NODENAME.1.4.CESM.a > dspcons

  Line    ConnId            ChanNum Status  CDVT  MaxBufSize  CLIP    
CBRservice

  ---- -------------------- ------- ------ ----- ---------- ------ 
------------

  1    NODENAME.4.1.0       32      Mod    10000 5120       2500   
unstructured

  2    NODENAME.4.2.0       33      Mod    10000 5120       2500   
unstructured

  ChanNumNextAvailable: 35

NODENAME.1.4.CESM.a > shellConn

NODENAME.1.4.CESM.a > SyncChan 32

SyncChan 32

value = 0 = 0x0

The command reports an error if it is unsuccessful. It takes channel number (not connection number) as an argument and does range checking for valid channels.

CSCdm54264

Symptom:

RPM DAX connection is not rejected when conflict

CSCdm59885

Symptom:

Connections with mismatched endpoints should be rejected

CSCdm61180

Symptom:

Able to change passwords without knowing password

Synopsis:

When a user wants to change the password, the CLI interface does not ask the user for the old password. Hence lack of security.

Description:

Irrespective of user GROUP ACCESS, he/she can change their password without knowing the old password.

Workaround:

This problem is fixed in release 1.1.12. Users belonging to SUPER USER GROUP are not prompted for the old password; while users belonging to other GROUPS are prompted for old password before they are allowed to change their current password.

CSCdm45141

Symptom:

Switchcc displays ssiFrameXmt failed and VSI master: invalid sw clock info pg

Condition:

The ssiXmtFrame failure was caused by SCM transmitting on GLCN=0, which is reserved. This is due to scmSwitch including slot 31 and slot 32 which are not mapped in SCM master.

switchcc on PXM displays the following message in the PXM log:

 1. ssiFrameXmt failed, error status -1 - 31 dropped

 2. Vsi master: invalid sw clock info pg

 ; 2, 3, -2104681808 - 1 dropped

 05/27/1999-06:16:13 07 PAR:Vsi     PAR-7-VSIM_DEBUG           

  Vsi master: invalid sw clock info pg

 ; 2, 3, -2104681808 - 1 dropped

 05/27/1999-06:16:10 07 PAR:Vsi     PAR-7-VSIM_DEBUG           

  Vsi master: invalid sw clock info pg

 ; 2, 3, -2104681808

Workaround:

No workaround

CSCdm61405

Symptom:

The bootChange information does not get propagated to a newly installed card

CSCdm69913

Symptom:

Checksum blocks not sync between controller and slave

CSCdm83431

Symptom:

Cannot telnet into an MGX 8850 shelf, but shows alive on ping

CSCdm86705

Symptom:

PLCP payload scrambling enable/disable needs to be supported

CSCdm91291

Symptom:

CWM flooded with APS trap 50606

Conditions:

Under Signal Degrade conditions, the MGX 8850 floods CWM with APS trap 50606

CSCdm59422

Symptom:

PXM declares RPM as Failed when CPU reaches high utilization.

Conditions:

The RPM is a NPE-150 based router card capable to sustain traffic up-to 150,000pps. The RPM limits it to 62,000pps because of its single switch interface design. Under heavy load (data or controlled traffic) the CPU utilization increases which breaks the IPC communication channel between the PXM and RPM card, due to which PXM declares RPM as Failed. Under such condition the provisioning commands will time-out as the PXM assumes that the RPM card is not available, whereas the RPM will continue to pass traffic.

WorkAround:

It is recommended for OSPF configurations to limit the number of networks to 20 or less and the MPLS configuration to limit the interface to 100 or less. Doing so will guarantee a sustainable traffic with a low CPU utilization and hence the CPU will be able to service IPC channel traffic.

CSCdp02058

Symptom:

Memory leak observed when master connection deleted

CSCdp02415

Symptom:

Bulk overflow system errors for conn addition beyond half of max-con limit

CSCdm94636

Symptom:

APS switch causes Db plfm: aps disk update failed in ssiDb Update in log

CSCdp04474

Symptom:

An LOS condition was cleared on an APS line, and neither a trap or an entry in the switch log was generated

CSCdp06288

Symptom:

All FRSM-VHS cards get into mismatch on downgrading to 1.1.11

CSCdp06386

Symptom:

APS - doing addapsln with OC12 interface causes both PXMs to reboot constantly

CSCdp07688

Symptom:

PAR ERROR - SYSTEM ERROR 20418 when deleting connection

CSCdp08594

Symptom:

Every 55 minutes MGX 8850 sends out 18 fan traps.

CSCdp09205

Symptom:

Not able to add 12K complete connections in MGX 8850 shelf

CSCdp10299

Symptom:

Standby PXM got reset during switchcc

CSCdp07383

Symptom:

APS alarm status is not provided in the MGX 8850 node, this must be provided

CSCdp04380

Symptom:

A switchcc caused by software error on node with 12000 connections

CSCdk87710

Symptom:

Decrease in number of CLP set cells.

Problem :

In a feeder environment, with connections between frsm-vhs at both ends, it was observed that the total cells sent, and received on other end did tally, but there was a decrease observed in the number of clp1 cell count.

CSCdm35110

Symptom:

Traffic dropped in Adaptive mode in CESM 8t1 card

CSCdm65796, CSCdm94176

Symptom:

Remote loops put up on FRSM-2CT3 are not detected by the dspln command

CSCdm69833

Symptom:

AUSM default connection parameter values severely impact data

CSCdm72334

Symptom:

FRSM-2CT3 DS3 line loopback not available

CSCdm72343

Symptom:

FRSM-2CT3 M-frame seq for OOF not evaluated

CSCdm75968

Symptom:

Universal(12in1) backcard must support X.21

CSCdm77348

Symptom:

CESM front card does not reset when backcard is re-inserted

CSCdm81340

Symptom:

AUSM slot 7 on axis shelf mysteriously switched to slot 14 <CSCdm10441>

CSCdm81362

Symptom:

singleBitErrCorrection missing from the tftp table <CSCdm44566>

CSCdm81363

Symptom:

Huge traps 50900/50901 sent on line errors. <CSCdm54102>

CSCdm81366

Symptom:

AUSM card with Bad PRI which pass checksum test ... <CSCdm60447>

CSCdm82908

Symptom:

Clock synchronization is required in loop timing

CSCdm83655

Symptom:

Bit and Framing errors were detected using the on-board T1/E1 service module BERT feature, and also with an external BERT test when the T1s were distributed from an SRM connected to an M13.

Further Problem Description:

When the T1 framer is configured in line loopback, there is no dejittering involved in the path. This causes bit errors for traffic from distribution bus , which is more susceptible to noise.

To eliminate these jitter induced errors, now the framer is configured for payload loopback in response to a loopup request. The jitter tolerance is improved with framer in payload loopback mode.

CSCdm83787

Symptom:

runslftstno 5 gets Disk Data Corruption message (similar to bug CSCdm68952)

CSCdm84900

Symptom:

After adding some connections, HS2 card goes into constant failed state

Problem & Reason:

When one of the feeder cable was bad and it was causing a lot of LCV's, HEC errors and also going on and off the MAJOR alarm state, some of the OAM cells from the far end connection were received as data and this triggered the card failing problem.

Workaround:

None if the bad cable cannot be replaced with a good one.

CSCdm49144

Symptom:

CLI support required with Port.dlci as Connection Index

CSCdm92558

Symptom:

The dspcd <slot_no> command display shows unexpected output

CSCdp03564

Symptom:

Getting large amounts of aborted frames on FRSM-HS2 card

CSCdp05125

Symptom:

Connections which terminate on FRSM-2CT3 ports which span multiple DS0s experience intermittant data problems. Counters and statistics on the FRSM and PXM do not indicate any problems. The CPE equipment will show FRAME abort conditions.

Conditions:

The condition will manifest itself after a number of low speed ports have been configured on the card. Data will run fine on the first few low speed ports configured, but after a point, the creation of one more low speed port will cause data on all ports to exhibit the problem symptoms.

Workaround:

No known workaround.

Further Problem Description:

The problem can be identified as follows --

Send data from the CPE (in this case a 3620 router). Notice that 3 of the 5 pings went through. We also see 2 abort frames (input errors on the interface). These directly correspond to the 2 missing icmp datagrams.

CSCdm75434

Symptom:

FRSM-2T3 is in failed state after xcnfchan -chn ? -cntp 2 for slave

CSCdm80762

Symptom:

N393 counter can be set to less than or equal to N392 counter

CSCdp05620

Symptom:

DLCI and Delete bit fields of an async. status message don't carry correct values

Scenario:

1. Configure a port with PVC Asynchronous Status Report enable.

2. Add a PVC.

3. Delete the PVC.

Problem:

1. The ASYNCH STATUS message contains DLCI = 0 instead of the DLCI of the

deleted PVC.

2. The "Delete bit" in the PVC IE is not turned on.

Workaround: none

CSCdp09346

Symptom:

CESM-8T1/E1 - New dsptotals command only shows max of 124 ports for both cards.

CSCdm30544

Symptom:

The major card integrated alarm due to inconsistent databases on the PXM and the SM does not get cleared.

Symptom :

Under rare situations, a configuration change on an SM will fail to make the necessary changes on the PXM. The SM will try to back-off the changes and this might fail also. This failure to undo the changes will result in the inconsistent databases card integrated alarm (which can be seen using the "dspcd" command).

Workaround :

There is no workaround to prevent this alarm condition from happening. However it is extremely rare that it will occur.

This alarm indication does not disappear at all. There is no CLI command to clear the alarm indication either. The only way to get rid of the alarm indication is to reset the card.

CSCdm49120

Symptom:

CLI support required using Port.dlci as Connection Index

CSCdm79642

Symptom:

PXM-CESM connections declared failed even though data continuity is fine

CSCdm84330

Symptom:

Random bit errors observed on DAX - T3 connections

CSCdm90305

Symptom:

Remote loops put up are not displayed by dspln command <VHS:CSCdm65796>

Remote Loopback invoked on an FRSM-2CT3 via cnfbert was not displayed via the dspln or any other command.

CSCdm93572

Symptom:

Cannot set AUSM IMA PortQueues on Popeye AUSM card, however this works on the AXIS shelf.

CSCdp06586

Symptom:

Unable to reverse LMI i.e. N393<N392 on FRSM-2CT3 ports

CSCdp06562

Symptom:

Provisioning of large numbers of PVCs using SNMP causes card to fail

Conditions:

FRSM card resets when attempting to provision up to 4000 connections. The lines and ports are deleted.

Workaround:

There is currently no work around for this.

CSCdm34026

Symptom:

Following switchcc duplicate IP address reported

CSCdm56223

Symptom:

SRM responds to FEAC for T3 resulting in local loop.

Conditions:

Happens when FEAC codes are sent to T3 of SRM.

Workaround:

Investigating.

CSCdm56229

Symptom:

SRM responds to FEAC to loop the T1s.

Conditions:

Happens when FEAC codes to loop the T1s are sent to the SRM card.

Workaround:

Investigating.

CSCdm64880

Symptom:

Switchcc caused telnet loss for two minutes and sequence mismatch messages

CSCdm67158

Symptom:

Control X issued at the console login prompt caused reset

CSCdm72320

Symptom:

Communication between PXM and service module drops in case of a switchover. Conditions caused by loss of messages between SM and PXM (e.g. updates about SM failover while PXM switchover is occuring) during PXM switchover are not corrected after new PXM has become active.

CSCdm94687

Symptom:

LOS on an APS line not in compliance with standards

CSCdm81375

Symptom:

Phantom channels on cards that don't have lines or ports enabled

CScdm87663

Symptom:

Performing switchcc on a system configured for APS results in error message

CSCdp08385

Symptom:

Possible memory leak after weekend of add/del slave end connections to PXM-UNI

CSCdp11201

Symptom:

FRSM-8T1E1 ports disappear after reset of card

CSCdp11885

Symptom:

FRSM-2E3: after deletion of the only channel on the card, the card still indicates channel alarm

CSCdm45045

Symptom:

APS: no differentiation between Model A and B backcards

CSCdm56779

Symptom:

Removing the back card from the active PXM causes the APS line to fail

CSCdk63920

Symptom:

VPI value supported on PXM broadband interface BBIF is 255

CSCdm32833

Symptom:

APS: switchapsln service options are not working

CSCdm36155

Symptom:

IP+ATM - Saved PVC configurations will not come up after pulling the RPM

CSCdm42355

Symptom:

Feature enhancement: real time VBR support on PXM UNI

CSCdm47536

Symptom:

FRSM front card should remain Active when line card is removed

CSCdm62176

Symptom:

Executing cc to redundant-active SMs CESM, FRSM, AUSM always fails after switchcc

CSCdm65505

Symptom:

APS and PMM pipc call forward functions leak pipc buf descriptor memory

CSCdm46613

dsptotals functionality not implemented on PXM

CSCdm57515

Removal of FRSM-2CT3 backcard did not cause redundancy switchover

CSCdm60455

Unable to configure SRM alarm intervals

CSCdm67669

Not able to configure Cellbus for double clock speed

CSCdm55225

Saveallcnf does not work while provisioning

CSCdm69780

Support of PXM core dump subsystem feature.

CSCdm35781

IP+ATM A PXM that is up does not detect PVCs going down at the far end

CSCdm40790

Expected dspred to show BLOCKED when redundant back card is unplugged.

CSCdm58432

Line cnf cleared on mmf-smf transition, mismatch not shown for mmf-smf combine

CSCdm60455

Unable to configure SRM alarm intervals

CSCdm61275

No APS switch on SDBER threshold exceeded

CSCdm63233

Saveallcnf does not include RPM configs

CSCdm71506

ssiMemPartShow output is broken caller, time and user data is garbage

CSCdm59316, CSCdm51290

Design rule for core card redundancy needs to be changed - Standby SRM does not take over when active SRM fails

CSCdm35781

IP+ATM A PXM that is up does not detect PVCs going down at the far end

CSCdm40790

Expected dspred to show BLOCKED when redundant back card is unplugged

CSCdm61199

cnftrapip reqd to specify source add. for traps-cnfifip address not sufficient

CSCdm74699

dspfwrevs hangs if ComMat.dat file is in C:/FW directory

CSCdm75102

If background memory check finds an error, the chunk pool may become unusable

CSCdm72701

Modified the red state machine to handle, SM_NOT_RESPONDING state from PMM in addition to SM_FAILED

CSCdm81167

Memory corruption in cliPlugin call

CSCdm81213

pool header status field has an invalid value

CSCdm80527

Cannot set dsx3PlcpPayloadScramble from SNMP

CSCdm00200

PCI errors cause VISM to reboot without displaying/logging error source

CSCdm23426

FRSM VHS 2CT3 delete rsc part config change50600 trap has incorrect status

CSCdm36668

Symptom:

On switchcc, CESM-8T1 & FRSM-VHS in slot 1 & 17 fails, incr unknown ScmTypeCnt

CSCdm44993

FRSM-V.35: Frame traffic loss on local DAX connection with internal loopback

CSCdm46266

FRSM-V.35: Unnecessary traps upon port addition and deletion

CSCdm47536

FRSM front card should remain Active when line card is removed

CSCdm49847

dsplns returns undefined symbol: dsplns on FRSM-VHS2E3

CSCdm50397

FRSM-V.35: UNI Timeout counts increment with NNI signalling configured

CSCdm51406

dspchancnt on remote end does not show receiving AIS

CSCdm51635

FRSM-8T1 does not show backcard serial number in dspcd

CSCdm54744

FRSM-V.35: Tagging should not occur with DE tagging disabled

CSCdm56090

FRSM-V.35: Port alarm should occur with Rcv clk rate out-of-bounds line alarm

CSCdm56264

CESM continuously rebooting

CSCdm57914

dspimainfo command to follow AXIS 5 implementation

CSCdm63207

MGX fails to send yellow upon receipt of AIS

CSCdm63250

FRSM-2CT3 does not generate yellow alarm

CSCdm63851

FRSM-V.35: FRSM Cards should not be identified as AXIS cards

CSCdm65343

FRSM V.35: Commands should include help text for V.35 interface not only X.21

CSCdm65939

SRM DS3 momentary error causes permanent DS1 LOF

CSCdm65940

SRM DS3 momentary error causes permanent DS1 LOF

CSCdm68952

runslftstno 5 run on AUSM shows Disk Data Corruption even though test passes

CSCdm69071

Automatic relearning of IMA ID required

CSCdm69713

FRSM-V.35: FRSM Cards should not be identified as AXIS cards

CSCdm69714

FRSM-V.35: FRSM Cards should not be identified as AXIS cards

CSCdm70125

Removal of FRSM-2CT3 backcard did not cause redundancy switchover

CSCdm56202

dsploads on AUSM

CSCdm83075

Redundant SM cards unavailable on pxm switchover caused by SRM failure

CSCdm83995

pxm - LMI port disabled on upgrade and resetsys, trunk unusable

CSCdm75342

After resetcd, all configuration for HS2 card is lost

CSCdm80086

FRSM-CT3 went into failed state during con provisioning

CSCdm29907

The cardMajorAlarmBitmap MIB variable is not found in the AXIPOP.my file. Currently, this information is available only on CLI. Some backward compatibility issues need to be resolved before this is available through SNMP

CSCdm38440

Wrong GMT offset when daylight savings time change

CSCdm47203

FRSM-2CT3 dsplns returns undefined symbol

CSCdm51406

dspchancnt on remote end does not show receiving AIS

CSCdm54605

delifip 37 results in system reset

CSCdk36727

Trap managers are not aged. If a trap manager is added, it has to be explicitly deleted.

CSCdk56888

Unexpected RAI alarms while configure DSX1 line in SF mode

CSCdm09225

The customer would like to have the ability to measure the processor consumption by process on the MGX 8850, the same way they can on the BPX.

CSCdm21269

When the ATM uplink is under congested condition ATM cloud, it is observed that the receiving FRSM is not receiving frames with FECN bit set and the sending FRSM is not receiving frames with BECN bit set as expected, if the FR-ATM interworking mode is set to service interworking transparent mode on the FRSMs.

CSCdm33419

The Connection GUI misreports connection modification in the following scenario: 1. Add a 3-segment connection with PXM UNI endpoints. 2. Modify the SCR on the PXM UNI side to a big number, big enough to exceed the available bandwidth on the feeder trunk side. Also turn on CAC override. 3. Execute the modification. CWM will display a successful result, even though the modification is actually rejected because oversubscription is not allowed on the feeder trunk side.

CSCdm36595

Sometimes the channels start sending AIS cells on to the port. As a result some channels on service modules are consistently in alarm state. Also as a result feeder connections disappear on the MGX 8850 after executing the resetsys command.

CSCdm29249

Some AUSM cards get stuck in cardInit state after executing the resetsys command.

CSCdm42493

CardIntegratedAlarm is not displayed when CLI command "dspcd" is executed on MGX 8850 service modules.

CSCdm50194

FRSM-2CT3 gives temporarily out of buffers message after addds3loop

CSCdm57808

Pulling out an active PXM causes multiple problems

CSCdm55429

APS line switch not indicated in switchlog & incorrect in CWM trap

CSCdm29177

FRSM-2CT3 can go into mismatch due to configuration mismatch between PXM cards

CSCdm33972

Error log shows: A process that is not the owner is attempting to free resources

CSCdm46905

Boot code from an invalid card type could be loaded to a different SM

CSdm47917

PXM log flooded with resync messages

CSCdm07070

MemShow, dspclksrc and dsptrkload bad responses

CSCdm23786

Unable to configure RS232 port speeds

CSCdk84622

Dsplmi & dspsarcnt available on AXIS or on PXM

CSCdm29177

FRSM-2CT3 cards go into mismatch due to config mismatch

CSCdm32736

Par-VSI task gets suspended unable to add/delete connections

CSCdm33972

Error log for slot 7 shows a process that is not the owner

CSCdm34001

Error log for slot 8 shows Db plfm:PmmRamDb update when card is not active

CSCdm34011

Error log for slot 8 shows no updated to Db plfm:sm14-v20 found to commit

CSCdm37450

Dspcons display breaks a connection into two lines

CSCdm39478

Restoreallcnf fails, with PXMs locking up and connections not restored

CSCdm39767

PSW firmware needs to reset PXM when a task fails to spawn successfully

CSCdm42463

On switchcc can lose RPM files that exist on the active PXM

CSCdm42849

When lmitrace on, keep doing dlmi hangs the system

CSCdm33996

Error log for slot 8 shows an invalid ssi-mqid of 0xffffffff

CSCdm38372

Addcon for a dax connection with ABR gives SNMP set error 6

CScdm33570

FRSM-2CT3 does not pause its display totals

CSCdm47909

PXM logs error for manually invoked switchcc

CSCdm53583

RPM config file not mirrored from active to standby PXM card

CSCdm50771

Copy of file to RPM can result in overwriting RPM directory entry

CSCdm23426

Config change trap carries the port resource partition row status as ADD while deleting the resource partition.