Repair and Replacement

Preventive Maintenance

Troubleshooting the MGX 8220 Shelf

General Troubleshooting Procedures

Procedure for all errors

Displayed Log Message Format

Log Codes

Replacing Parts

Replacing a Front Card

Replacing a Line Module

Replacing a DC Power Entry Module

Replacing the Cooling, Booster, Plenum, and AC Power Assemblies

Repair and Replacement

This chapter describes periodic maintenance procedures, troubleshooting procedures, and the replacement of major parts for the Release 4.0 MGX 8220.

Caution For protection against shock hazard, verify both power cords are disconnected before servicing unit.

Caution Vergewissern sie sich, däss beide Netzkäbel vom Gerät getrennt sind, bevor Sie mit den Wärtungsärbeiten beginnen.

Caution Pour iviten tout danger, dibrancher les deux cordons d'alimentation avant toute intervention de maintenance sur cet equipement.

Preventive Maintenance

Most monitoring and maintenance of the MGX 8220 shelf is done via the operating system software. Preventive maintenance of the MGX 8220 shelf hardware is minimal and requires the following:

1. Periodically check the node supply voltage and internal cabinet temperature. The temperature should not exceed 50º C.

2. Periodically check the event log with the dsplog command.

3. Periodically check the network alarm status with the dspalms command.

4. Ensure that the cooling unit intake grills and the exhaust plenum are clear.

Troubleshooting the MGX 8220 Shelf

This section describes basic troubleshooting steps to be taken for some of the more obvious node failures. (Refer to Table 8-1.) This is not an exhaustive set of procedures, and does not take into account any of the diagnostic or network tools available to troubleshoot the MGX 8220 shelf. Refer to Chapter 5, "Service Configuration", for information on commands and command usage.

General Troubleshooting Procedures

The MGX 8220 shelf run self tests continuously to ensure proper function. When the unit finds an error condition that affects its operation, it downs the card or line that is affected. If it is caused by a card failure and there is a redundant card, the failed card is downed and the standby card becomes the active card.

The FAIL lights on the cards indicate that the system has found these cards defective in some mode, and now considers them as failed cards. Refer to Table 8-1 to find the cause and obtain information on replacing the failed component.

Symptom	Probable Cause	Remedy
No front panel LEDs are lighted.	Circuit breakers on the MGX 8220 shelf Power Entry Module(s) switched off.	Press in the black button on power entry modules to switch on circuit breakers. If problem persists, pull all cards and power supplies out to see if a shorted card or supply exists.
	The MGX 8220 shelf power cord plug disconnected from AC supply.	Reconnect power cord.
Card front panel fail LED lit	Card failed self-test.	Check status of card at control console using dspcds screen. If alarm is confirmed, try card reset (resetcd command). Finally, remove and replace the card.
Card stby LED on.	Card is off-line.	Not a problem as long as a primary card is active.
BNM major or minor LED on.	Service-affecting (major) or non-service affecting (minor) system fault.	Check event log to identify problem reported.
	Network trunk failed.	Observe Port LEDs on each BNM. Use control console dspln to locate failure.
	Internal temperature is higher than normal resulting from blocked air flow or defective fan.	Check front of cooling assembly for freedom of air flow. Replace the assembly that may have failed or slowed. Check free air flow in plenum chamber, remove blockage if necessary.
ASM hist LED lit.	If no other alarm indications, a fault occurred in the past but has been cleared.	Press ASM history clear button. Check NMS event log to determine cause.
BNM Port LED is red.	Trunk is in local or remote alarm.	Use short BNM loopback cable line module connector for local test of trunk. Loop trunk at DSX-3 crossconnect to check cable.
ASC fail LED flashing	Downloading system software or configuration data.	Wait for download to complete.

Table 8-1: Troubleshooting the MGX 8220 Shelf Node

Symptom Probable Cause Remedy

No front panel LEDs are lighted.

Circuit breakers on the MGX 8220 shelf Power Entry Module(s) switched off.

Press in the black button on power entry modules to switch on circuit breakers. If problem persists, pull all cards and power supplies out to see if a shorted card or supply exists.

The MGX 8220 shelf power cord plug disconnected from AC supply.

Reconnect power cord.

Card front panel fail LED lit

Card failed self-test.

Check status of card at control console using dspcds screen. If alarm is confirmed, try card reset (resetcd command). Finally, remove and replace the card.

Card stby LED on.

Card is off-line.

Not a problem as long as a primary card is active.

BNM major or minor LED on.

Service-affecting (major) or non-service affecting (minor) system fault.

Check event log to identify problem reported.

Network trunk failed.

Observe Port LEDs on each BNM.
Use control console dspln to locate failure.

Internal temperature is higher than normal resulting from blocked air flow or defective fan.

Check front of cooling assembly for freedom of air flow. Replace the assembly that may have failed or slowed. Check free air flow in plenum chamber, remove blockage if necessary.

ASM hist LED lit.

If no other alarm indications, a fault occurred in the past but has been cleared.

Press ASM history clear button. Check NMS event log to determine cause.

BNM Port LED is red.

Trunk is in local or remote alarm.

Use short BNM loopback cable line module connector for local test of trunk. Loop trunk at DSX-3 crossconnect to check cable.

ASC fail LED flashing

Downloading system software or configuration data.

Wait for download to complete.

Procedure for all errors

The first action to take for all failures seen on an MGX 8220 is to collect data from the following commands:

dspcds

  Slot  CardState    CardType     CardAlarm  Redundancy
  ----  -----------  --------     ---------  -------------------- 
  1.1   Unknown      ?                                            
  1.2   Active       BNM-T3        Minor                          
  1.3   Empty                                                     
  1.4   Active       ASC                                          
  1.5   Active       FRSM-4E1                                     
  1.6   Active       FRSM-4E1     Major                           
  1.7   Active       FRSM-4T1                                     
  1.8   Active       AUSM-4T1                                     
  1.9   Empty                                                     
  1.10  Empty                                                     
  1.11  Empty                                                     
  1.12  Active       FRSM-HS1                                     
  1.13  Empty                                                     
  1.14  Empty                                                     
  1.15  Unknown                                                   
  1.16  Empty

Column `Slot' indicates `shelf'.'slot'

Column `CardState' indicates the status of the card in the card in that slot.

`Active' indicates when a card has become active.
`Empty' indicates that the active ASC does not recognized that a card is installed in that slot.
`Standby' indicates that a card is in standby.
`Mismatch' indicates that there is some condition that does not allow the active ASC to complete the initialization of the card in the slot.
`Failed' indicates that the card has failed the initialization and configuration.
`Unknown' indicates that the active ASC was not able to identify the card installed in the slot.

Column `CardType' indicates the type of card that is installed in that slot.

Column `CardAlarm' indicates if any Major or Minor alarms exist for that slot.

Column ` Redundancy' indicates if when redundancy state has changed.

The output from the dspcds command is a two screen display; the first screen displays the card status; the second screen displays the backplane and node information.

   NodeName:             axis_sh1
    Date:                 01/15/1998
    Time:                 14:14:40
    TimeZone:             PST
    TimeZoneGMTOff:       -8
    StatsMasterIpAddress: 0.0.0.0
    shelfIntegratedAlarm: Minor
    BkplnSerialNum:       135797
    BkplnType:            1
    BkplnFabNumber:       218412-00
    BkplnHwRev:           bb
 
   Syntax : dspcds

The AXIS Shelf Controller(ASC) maintains a set of log files, which contain the messages logged by the ASC and the individual Service Modules. The logs are stored on the ASC hard disk. There are five logs, each log contains one days worth of events. The logs are rotated daily, therefore there should always be five days worth of events. Each log file contains information about configuration changes and errors that occurred in the shelf on a particular day. The commands used by the user to change the configuration are also logged in these log files.

Note Each file has a maximum size of 1.4 MB. When a day's log exceeds 1.4MB, the last entry in the log is overwritten, each time it logs a new message. This process is repeated until a new file is created the next day.

The log file can be displayed only from the Command Line Interface (CLI). The CLI command used to display the log is dsplog.

dsplog (slot# )|(<slot# > <day offset>)

The day offset means offset from today.

Examples: dsplog 7 1 would display the events for slot 7 that occurred yesterday.

dsplog 12 3 would display the events for slot 12, 3 days ago.

dsplog 5 would display the events for slot 5 today.

dsplog displays all the logs starting from the most current and proceeding backwards.

Each line of the log display is one log entry in the following fixed format:

01/21/1998-08:34:36   5      cmm                    4024   FRSM going active

Displayed Log Message Format

The messages logged are displayed in the following syntax

<Date>-<Time> <Slot Number> <Task Name/User Id> <Log Code> <Log String> : <Log Specific information>

Date	The date on which this message was logged
Time	The time at which this message was logged
Slot Number	The slot number of the card which logged the message
Task Name/User Id	The name of the task which logged this message or if it is command log then specifies the user id
Log Code	A numeric value which specifies the log code
Log String	The log string associated with the log code
Log Specific Information	Addtional information on the specific instance of this log. e.g. If a line is in LOS the line number is displayed

Some sample log messages:

Searching ..done
 
04/09/1998-13:57:46 7 clt        6050   Channel in alarm     : LCN #21
04/09/1998-15:33:26 7  SuperUser    0   addln 4 
04/09/1998-14:29:22 8  talarm    4057   Line Rx LOF alarm on : line: 8
  
Type <CR> to continue, Q<CR> to stop:

Log Codes

The log codes used in the log messages are broadly classified as shown in Table 8-2.

Log Code Range	Module Logging Messages
1000 - 1999	ASC
2000 - 2999	BNM
3000 - 3999	Not Used
4000 - 4999	FRSM
5000 - 5999	SRM
6000 - 6999	AUSM
7000 - 7999	AUSM8/IMATM
8000 - 8999	CESM

Table 8-2: Log Code Ranges for Various Cards

Log Code Range Module Logging Messages

1000 - 1999

ASC

2000 - 2999

BNM

3000 - 3999

Not Used

4000 - 4999

FRSM

5000 - 5999

SRM

6000 - 6999

AUSM

7000 - 7999

AUSM8/IMATM

8000 - 8999

CESM

ASC Log Codes

Error Number	Display Log String	Detail Description
1100	Out of Heap Space	SCM task is running out of Heap space, malloc failed.
1101	Sar Operation Failed	Failed to enable, disable or send data on an LCN. Additional information describing the specific instance of failure and the LCN number are displayed.
1102	Switch Over Failed	Not Used
1103	Queue Error	Encountered Data Queue overflow error while queueing data. The particular card index is also displayed.
1104	Unknown number	Error occurred while sending a Frame. Unrecognizable Frame type.
1105	Seq_num not match	Not Used
1107	Out of xmt buffer	Error occurred due to shortage of transmit buffers in the SCM. Information describing the specific instance is also displayed.
1108	Msg queue rcv/send	Failed to receive/send message from/to the message Queue.
1109	Unknown card	Invalid card slot number conveyed by the slave Information describing the specific instance is also displayed.
1110	Invalid alarm type	Not Used
1111	Creating semId fail	Error occurred while creating a semaphore.
1112	Tx mgmbuf ret twice	Same management transmit buffer returned twice as a free buffer.
1113	Tx mgmbuf alloc twice	Same buffer allocated twice from the management free buffers pool.
1114	All selftest results are cleared	All selftest counters and results have been cleared.
1115	Selftest Failed; Card is reset	Self test failed on the card and the card has been reset.
1200	bad shelf slot num	Invalid shelf slot number encountered. Information regarding the specific instance is also displayed.
1201	unknown aum msg	Unknown message type received while processing the messages from BNM.
1202	unknown scm msg	Unknown message type from SCM. Information regarding the type, source and destination of the message is also displayed
1203	array out of bounds	Not Used
1204	general error	Some general error occurred, like invalid slot number, ASC disk read/write error, checksum failure, bad unexpected response, malloc errors, send/receive failures, etc. Information describing the specific instance is also displayed.
1205	standby BRAM download err	Failed to download the firmware to the card.
1206	slave failed ack	No ACK received from the slave.
1207	slave ack timeout	Error occurred while sending messages through message Queues to other tasks. No response to the messages sent.
1208	aum arbit err	Not Used.
1209	malloc err	Failed to allocate memory. Running out of memory space.
1210	msg data err	Invalid message received or message missing some information.
1211	err from msg rcv call	Invalid message received from another task.
1212	no response	Failed to receive response from another task in a particular amount of time. Especially while trying to propagate the change in the card state to other tasks.
1213	NULL	Standby card's Firmware update, as active Card Firmware revision is higher than the Standby revision.
1214	NULL	Standby Firmware update when Active is native to shelf and standby is non native
1215	switch reason	The Standby Card has been allowed to gain mastership as the Firmware revision in the Standby Card is higher than the Active Firmware.
1216	switch reason	The Standby Card has been allowed mastership because the Active was not native to shelf and the standby was native to shelf.
1217	switch reason	Not Used
1218	NULL	Overrides to do not change standby if standby firmware revision is Release 2 or 3.
1219	switch reason	The Standby Card has been allowed mastership because Standby Firmware version is higher than Active.
1220	informational	SMM related Information regarding the card state and other information useful for debugging and administration has been logged.
1221	communication up, slot	A message received, which states that an SM card is responding while polling. Additional Information about the slot number and the card state is also displayed.
1222	communication down, slot	A message received, which states that an SM card is not responding while polling.
1223	card inserted, slot	An SM Card Insertion detected while monitoring the slot states of the shelf.
1224	card removed, slot	An SM Card Removal detected while monitoring the slot states of the shelf.
1225	SM card state change	A message received, which reports the change in card state. Information about the present card state is also displayed.
1226	Both Mastership Asserted, cardState	Both the cards have been asserted Mastership state.
1227	Major Alarm: Connections exist on removed SM	Connections exist on the removed SM card and a Major Alarm has been logged.
1228	Clear Alarm: Connections exist on removed SM	Clear the Alarm caused by the switch over of a card with existing connections by a new card.
1229	card ready de asserted, slot n	An SM Card Failure detected. Additional Information about the slot number is displayed.
1230	standby F/W update failed	Error occurred while updating the Firmware version in the Standby card. Operation Incomplete.
1231	BERT informational	Error occurred in a BERT related Module. Additional Information describing the specific instance of error is displayed.
1232	Unable to spawn ascSrmDetectedTask	Error occurred while spawning the SRM DETECTED task.
1233	Error in srm common task message	Invalid message received from the SRM task. Additional information describing the specific instance of the error is displayed.
1234	SRM peer mismatch detected	Type mismatch between the Active and the Redundant service module card types.
1235	SRM config. mismatch detected	Type mismatch between the Active and the Redundant Card configurations.
1236	SRM card failed	SRM Card failure detected. Additional Information about the Card is also displayed.
1237	switchcc reason	Standby ASC Card has been allowed mastership, as the Active ASC doesn't have an SRM Card. Additional information describing the specific instance is displayed.
1280	Q not present	Error occurred while accessing the ATM message Queue. Failed to get the number of messages in the Queue.
1281	atmRx task spawn fail	Failed to Spawn the ATM receiver task.
1282	error in recv msg Q	Error occurred while receiving message from the ATM message Queue.
1283	PDU received bigger than 2032	The length of the PDU received through the ATM receive queue exceeds the maximum value.
1301	snmp pdu auth parse err	Authentication in SNMP PDU failed while parsing.
1302	snmp varbind parse err	Failed trying to parse varbinds in SNMP PDU.
1303	mgmt buffer shortage	Not Used
1304	SR agent gen err	SNMP PDU to be forwarded to the Agent failed Authentication.
1305	destination of PDU unknown	Not Used
1306	err making varbind for trap PDU	Not Used
1307	unable to open SNMP-161 port	Error occurred while Opening the SNMP UDP port 161.
1308	unable to bind SNMP-161 port	Error occurred while Binding the SNMP UDP port 161.
1309	message recv call generated error	General NMIM error occurred like malloc failure, message Queue send/receive failure, etc. Additional information describing the specific instance is displayed.
1310	sendto - call err, or did not xmt all data	Failed to transmit the IP data packet. System call error or failed to transmit all the data.
1311	executing STANDBY card code, wrong thread	Executing wrong thread. STANBY card code has been executed.
1312	local IP address not programmed	No Interface has been configured with a Local IP address.
1313	receive size error	Failed to receive the SNMP PDU. System call error.
1314	tx data size error	Invalid packet data length. Packet cannot be sent.
1315	error number =	General NMIM error occurred like Queue send failure, bad source address, authentication failure, etc.
1316	general error	Not Used
1400	msg send error	Failed to send a message to another task through a message Queue.
1401	LCN out of range	Not Used
1402	xmt buffer not available	Failed to send an OAM cell. Transmit buffers not available.
1403	xmt failure	Error occurred while transmitting the OAM cell. SAR transmit Queue is full.
1404	cell type error	Invalid OAM cell type.
1405	msg rcv error	Error occurred while receiving a message from another task through a message queue.
1406	rcv failure	Error occurred while receiving an OAM cell from the SAR module.
1407	VC table full	The OAM VC Table if full. Cannot accept one more entry.
1408	VC entry not found	Not Used
1409	VC state error	OAM VC table is not in the expected state to execute the particular Command from another task.
1410	unknown command	Unknown OAM Command received from another task.
1411	AUM LCN list ptr is 0	OAM cell missing the list of LCNs.
1412	AUM req send AIS again	BNM (AUM) has sent the command to send the AIS cells for the same VC, again.
1500	Receive Queue Error	LMI task Failed to receive a message sent by another task through a message queue.
1501	Transmit Queue Error	LMI task Failed to transmit a message to another task through a message queue.
1502	Bad Source ID	A message received from an unknown source through a message queue. Bad source ID.
1503	Bad Destination ID	Message not meant for LMI task has been received through a message queue. Bad destination ID.
1504	Bad Slot number	Message received from another task refers to an Invalid Slot number.
1505	Invalid message	Invalid message received from another task.
1506	Received PDU too long	Size of the PDU received from the SCM message queue exceeds the maximum length.
1507	No tx buffers available	Error occurred while sending LMI PDUs to SCM. Transmit buffers not available.
1508	Bad LCN	Invalid LCN number. LCN exceeds the maximum value or it is below zero.
1509	Minor Alarm: LMI failure	LMI module failure triggered a minor alarm.
1510	Clear Alarm: LMI failure	Cleared the minor alarm caused by LMI failure. LMI port is up, now.
1511	Conn Status Req failure	Failed to get the connection status of the SM cards.
1512	Bad Prefix Port Received	Received an invalid address prefix registration message.
1513	Bad Prefix (preexisting) received	Not Used
1514	Bad ATM address received	ATM address received for registering/deregistering/clearing the port prefix is Invalid.
1515	No system memory available	Insufficient system memory. Failed to malloc.
1516	Bad maximum LCN number	Invalid maximum LCN number encountered while processing SCM messages.
1517	Bad LCN counter	Invalid LCN number encountered.
1518	Bad VPI counter	Invalid VPI number encountered while processing SCM messages.
1519	Bad start and more bits	Invalid start and more bits.
1520	Failed to malloc	Malloc failed. LMI task running out of memory.
1600	ACRED: Could not send MSG to SM	Failed to send a message to SM. Additional information describing the particular instance is displayed.
1601	ACRED: General ERROR	General ACRED error. Additional information describing the specific instance is displayed.
1602	ACRED: Informational	Information useful for debugging and maintenance which describes the critical control flow, has been logged.
1603	ACRED: Memory corruption in system	Memory corruption occurred in the system.
1604	ACRED: State Time out	Timed out in a particular state after several retries. Moved to FAILED state.
1605	ACRED: Wrong msg rcvd	Invalid message received from another task. Additional information describing the specific instance is displayed.
1606	ACRED: Download BRAM Failed	Failed to download BRAM from ASC to SM.
1607	ACRED: Upload BRAM Failed	Error occurred while uploading the SM configuration file to the ASC disk.

Table 8-3: ASC Log Codes

Error Number Display Log String Detail Description

1100

Out of Heap Space

SCM task is running out of Heap space, malloc failed.

1101

Sar Operation Failed

Failed to enable, disable or send data on an LCN. Additional information describing the specific instance of failure and the LCN number are displayed.

1102

Switch Over Failed

Not Used

1103

Queue Error

Encountered Data Queue overflow error while queueing data. The particular card index is also displayed.

1104

Unknown number

Error occurred while sending a Frame. Unrecognizable Frame type.

1105

Seq_num not match

Not Used

1107

Out of xmt buffer

Error occurred due to shortage of transmit buffers in the SCM. Information describing the specific instance is also

displayed.

1108

Msg queue rcv/send

Failed to receive/send message from/to the message Queue.

1109

Unknown card

Invalid card slot number conveyed by the slave Information describing the specific instance is also displayed.

1110

Invalid alarm type

Not Used

1111

Creating semId fail

Error occurred while creating a semaphore.

1112

Tx mgmbuf ret twice

Same management transmit buffer returned twice as a free buffer.

1113

Tx mgmbuf alloc twice

Same buffer allocated twice from the management free buffers pool.

1114

All selftest results are cleared

All selftest counters and results have been cleared.

1115

Selftest Failed; Card is reset

Self test failed on the card and the card has been reset.

1200

bad shelf slot num

Invalid shelf slot number encountered. Information regarding the specific instance is also displayed.

1201

unknown aum msg

Unknown message type received while processing the messages from BNM.

1202

unknown scm msg

Unknown message type from SCM. Information regarding the type, source and destination of the message is also displayed

1203

array out of bounds

Not Used

1204

general error

Some general error occurred, like invalid slot number, ASC disk read/write error, checksum failure, bad unexpected response, malloc errors, send/receive failures, etc. Information describing the specific instance is also displayed.

1205

standby BRAM download err

Failed to download the firmware to the card.

1206

slave failed ack

No ACK received from the slave.

1207

slave ack timeout

Error occurred while sending messages through message Queues to other tasks. No response to the messages sent.

1208

aum arbit err

Not Used.

1209

malloc err

Failed to allocate memory. Running out of memory space.

1210

msg data err

Invalid message received or message missing some information.

1211

err from msg rcv call

Invalid message received from another task.

1212

no response

Failed to receive response from another task in a particular amount of time. Especially while trying to propagate the change in the card state to other tasks.

1213

NULL

Standby card's Firmware update, as active Card Firmware revision is higher than the Standby revision.

1214

NULL

Standby Firmware update when Active is native to shelf and standby is non native

1215

switch reason

The Standby Card has been allowed to gain mastership as the Firmware revision in the Standby Card is higher than the Active Firmware.

1216

switch reason

The Standby Card has been allowed mastership because the Active was not native to shelf and the standby was native to shelf.

1217

switch reason

Not Used

1218

NULL

Overrides to do not change standby if standby firmware revision is Release 2 or 3.

1219

switch reason

The Standby Card has been allowed mastership because Standby Firmware version is higher than Active.

1220

informational

SMM related Information regarding the card state and other information useful for debugging and administration has been logged.

1221

communication up, slot

A message received, which states that an SM card is responding while polling. Additional Information about the slot number and the card state is also displayed.

1222

communication down,

slot

A message received, which states that an SM card is not responding while polling.

1223

card inserted, slot

An SM Card Insertion detected while monitoring the slot states of the shelf.

1224

card removed, slot

An SM Card Removal detected while monitoring the slot states of the shelf.

1225

SM card state change

A message received, which reports the change in card state. Information about the present card state is also

displayed.

1226

Both Mastership Asserted, cardState

Both the cards have been asserted Mastership state.

1227

Major Alarm: Connections exist on removed SM

Connections exist on the removed SM card and a Major Alarm has been logged.

1228

Clear Alarm: Connections exist on removed SM

Clear the Alarm caused by the switch over of a card with existing connections by a new card.

1229

card ready de asserted, slot n

An SM Card Failure detected. Additional Information about the slot number is displayed.

1230

standby F/W update failed

Error occurred while updating the Firmware version in the Standby card. Operation Incomplete.

1231

BERT informational

Error occurred in a BERT related Module. Additional Information describing the specific instance of error is displayed.

1232

Unable to spawn

ascSrmDetectedTask

Error occurred while spawning the SRM DETECTED task.

1233

Error in srm common task message

Invalid message received from the SRM task. Additional information describing the specific instance of the error is displayed.

1234

SRM peer mismatch detected

Type mismatch between the Active and the Redundant

service module card types.

1235

SRM config. mismatch detected

Type mismatch between the Active and the Redundant Card configurations.

1236

SRM card failed

SRM Card failure detected. Additional Information about the Card is also displayed.

1237

switchcc reason

Standby ASC Card has been allowed mastership, as the Active ASC doesn't have an SRM Card. Additional information describing the specific instance is displayed.

1280

Q not present

Error occurred while accessing the ATM message Queue. Failed to get the number of messages in the Queue.

1281

atmRx task spawn fail

Failed to Spawn the ATM receiver task.

1282

error in recv msg Q

Error occurred while receiving message from the ATM message Queue.

1283

PDU received bigger than 2032

The length of the PDU received through the ATM receive queue exceeds the maximum value.

1301

snmp pdu auth parse err

Authentication in SNMP PDU failed while parsing.

1302

snmp varbind parse err

Failed trying to parse varbinds in SNMP PDU.

1303

mgmt buffer shortage

Not Used

1304

SR agent gen err

SNMP PDU to be forwarded to the Agent failed Authentication.

1305

destination of PDU unknown

Not Used

1306

err making varbind for trap PDU

Not Used

1307

unable to open SNMP-161 port

Error occurred while Opening the SNMP UDP port 161.

1308

unable to bind SNMP-161 port

Error occurred while Binding the SNMP UDP port 161.

1309

message recv call

generated error

General NMIM error occurred like malloc failure, message Queue send/receive failure, etc. Additional information describing the specific instance is displayed.

1310

sendto - call err, or did not xmt all data

Failed to transmit the IP data packet. System call error or failed to transmit all the data.

1311

executing STANDBY card code, wrong thread

Executing wrong thread. STANBY card code has been executed.

1312

local IP address not programmed

No Interface has been configured with a Local IP address.

1313

receive size error

Failed to receive the SNMP PDU. System call error.

1314

tx data size error

Invalid packet data length. Packet cannot be sent.

1315

error number =

General NMIM error occurred like Queue send failure, bad source address, authentication failure, etc.

1316

general error

Not Used

1400

msg send error

Failed to send a message to another task through a message Queue.

1401

LCN out of range

Not Used

1402

xmt buffer not available

Failed to send an OAM cell. Transmit buffers not available.

1403

xmt failure

Error occurred while transmitting the OAM cell. SAR transmit Queue is full.

1404

cell type error

Invalid OAM cell type.

1405

msg rcv error

Error occurred while receiving a message from another task through a message queue.

1406

rcv failure

Error occurred while receiving an OAM cell from the SAR module.

1407

VC table full

The OAM VC Table if full. Cannot accept one more entry.

1408

VC entry not found

Not Used

1409

VC state error

OAM VC table is not in the expected state to execute the particular Command from another task.

1410

unknown command

Unknown OAM Command received from another task.

1411

AUM LCN list ptr is 0

OAM cell missing the list of LCNs.

1412

AUM req send AIS again

BNM (AUM) has sent the command to send the AIS cells for the same VC, again.

1500

Receive Queue Error

LMI task Failed to receive a message sent by another task through a message queue.

1501

Transmit Queue Error

LMI task Failed to transmit a message to another task through a message queue.

1502

Bad Source ID

A message received from an unknown source through a message queue. Bad source ID.

1503

Bad Destination ID

Message not meant for LMI task has been received through a message queue. Bad

destination ID.

1504

Bad Slot number

Message received from another task refers to an Invalid Slot number.

1505

Invalid message

Invalid message received from another task.

1506

Received PDU too long

Size of the PDU received from the SCM message queue exceeds the maximum length.

1507

No tx buffers available

Error occurred while sending LMI PDUs to SCM. Transmit buffers not available.

1508

Bad LCN

Invalid LCN number. LCN exceeds the maximum value or it is below zero.

1509

Minor Alarm: LMI

failure

LMI module failure triggered a minor alarm.

1510

Clear Alarm: LMI

failure

Cleared the minor alarm caused by LMI failure. LMI port is up, now.

1511

Conn Status Req failure

Failed to get the connection status of the SM cards.

1512

Bad Prefix Port Received

Received an invalid address prefix registration message.

1513

Bad Prefix

(preexisting) received

Not Used

1514

Bad ATM address received

ATM address received for registering/deregistering/clearing the port prefix is Invalid.

1515

No system memory available

Insufficient system memory. Failed to malloc.

1516

Bad maximum LCN number

Invalid maximum LCN

number encountered while processing SCM messages.

1517

Bad LCN counter

Invalid LCN number encountered.

1518

Bad VPI counter

Invalid VPI number encountered while processing SCM messages.

1519

Bad start and more bits

Invalid start and more bits.

1520

Failed to malloc

Malloc failed. LMI task running out of memory.

1600

ACRED: Could not send MSG to SM

Failed to send a message to SM. Additional information describing the particular instance is displayed.

1601

ACRED: General ERROR

General ACRED error. Additional information describing the specific instance is displayed.

1602

ACRED: Informational

Information useful for debugging and maintenance which describes the critical control flow, has been logged.

1603

ACRED: Memory

corruption in system

Memory corruption occurred in the system.

1604

ACRED: State Time out

Timed out in a particular state after several retries. Moved to FAILED state.

1605

ACRED: Wrong msg rcvd

Invalid message received from another task. Additional information describing the specific instance is displayed.

1606

ACRED: Download BRAM Failed

Failed to download BRAM from ASC to SM.

1607

ACRED: Upload BRAM Failed

Error occurred while uploading the SM configuration file to the ASC disk.

BNM Log Codes

Error Number	Display Log String	Detail Description
2016	Received message length not correct for message type	Length of the message received from another task is invalid for the message type.
2017	Unknown message type from SMM task	Received a message of unknown type from the SMM task.
2018	Unknown message type from SCM task	Received a message of unknown type from the SCM task.
2019	Unexpected message from a task	Received a message from an unknown source. Source ID is Invalid.
2020	Misdirected message in AUM message queue	Received a message not destined for the BNM task.
2021	Failure while trying to transmit message to VxWorks message queue	BNM task failed to send a message to another task through a VxWorks message queue.
2022	Failure while trying to receive message from VxWorks message queue	BNM task failed to receive a message from another task through a VxWorks message queue.
2023	Specified slot number is out of recognized range	Invalid Slot number specified.
2024	Specified shelf number is out of recognized range	Not Used
2025	Specified LCN is out of range	Not Used
2026	Invalid Core card state specified	The Core Card State information specified by a message from another task is Invalid.
2027	Invalid Slot state specified	The Slot Reset State information specified by a message from another task is invalid.
2028	Invalid signal name specified	Invalid signal name specified by the message from the SMM task.
2029	Invalid signal state specified	Invalid signal state specified by the message from the SMM task.
2032	Error in aumAddConn while rebuilding from BRAM	Error occurred while rebuilding connections from the BRAM. Additional information regarding the specific instance is displayed.
2048	Internal FW Error. Access to unrecognized pio port	Invalid PIO port specified to read from a device.
2049	Internal FW Error. Access to unknown i/o port	Invalid device I/O port specified to read from a device.
2050	Internal FW Error. Connection database corrupted	Not Used
2051	Internal FW Error. LCN linked list corrupted	Error occurred while building the LCN list for OAM cells. Additional information regarding the specific instance is displayed.
2052	Internal FW Error. Unrecognized AUM port	Invalid BNM (AUM) port.
2053	Internal FW Error. Unrecognized clock source	Invalid MUX Clock Source encountered while configuring Clock MUX.
2054	Internal FW Error. Unrecognized clock mux	Invalid Clock MUX.
2055	Internal FW Error. Unrecognized port number	Invalid Port number encountered while enabling/disabling the line transmission function.
2056	Internal FW Error. Unrecognized counter	Invalid Counter number encountered.
2057	Internal FW Error. ADC timeout	ADC error occurred. Additional information regarding the specific instance is displayed.
2058	Internal FW Error. Unrecognized fan tray	Invalid Fan Tray number encountered.
2064	HW Error. XILINX fails to respond to INIT signal	Not Used
2065	HW Error. XILINX fails to respond with DONE signal	Error occurred while downloading Xilinx image. Additional information regarding the specific instance is displayed.
2066	HW Error. XILINX Init pin went low during download	Error occurred while downloading Xilinx image. Xilinx Init pin went low.
2067	HW Error. PLL failure (E3 port)	Not Used
2068	HW Error. Invalid Front Card Type	Invalid Front Card Type. BNM cannot stay in the Active state.
2069	HW Error. ADC Zero Calibration Error	ADC Zero Calibration error occurred.
2070	HW Error. ADC Mid-range Calibration Error	ADC Mid-range voltage Calibration error occurred.
2071	HW Error. BNM Card NOVRAM Checksum Error	BNM Front Card NOVRAM checksum error occurred.
2072	HW Error. Backplane NOVRAM Checksum Error	BNM Backplane NOVRAM checksum error occurred.
2080	Cannot allocate memory:	Failed to Allocate memory. BNM task running out of memory space.
2081	Line clock update	Line clock updated.
2082	Line clock changed to=	Line clock changed. Additional information regarding the specific instance is displayed.
2096	Line alarm	Line Alarm trap generated as the line alarm state bits changed.
2097	Line statistical alarm	Line statistics alarm trap generated.
2098	PLCP alarm	PLCP Alarm trap generated as the PLCP alarm state bits changed.
2099	PLCP statistical alarm	PLCP statistics alarm trap generated.
2100	Function module alarm	Function module major alarm trap generated.
2101	Line module alarm	Line module major alarm trap generated. Back card not present.
2102	ASM alarm	Shelf Major alarm trap generated.
2112	BRAM Conn Update error in	Error occurred while updating BNM connection information on the BRAM.
2113	BNM mastership change	Change in BNM card mastership state.
2114	Mesg from ASC to set FWREADY =	Received a message from the SMM task to set the BNM Firmware ready.
2115	Line configuration does not match with BNM card	Line Configuration mismatch occurred with the BNM card.
2116	BNM cardType of the other card set does not match	Card type of the standby BNM card does not match with the active card type.
2117	BNM cardType =	Information about the BNM card type.
2118	BNM Initialization error,	Error occurred while initializing BNM. Additional information regarding the specific instance is displayed.
2119	BNM incompatible module,	BNM incompatibility error.
2120	BNM FPGA Download Error,	Error occurred while downloading image from FPGA. Additional information regarding the specific instance is displayed.
2121	BNM Init Info:	Information useful for debugging/administration purposes.

Table 8-4: BNM Log Codes

Error Number Display Log String Detail Description

2016

Received message length not correct for message type

Length of the message received from another task is invalid for the message type.

2017

Unknown message type from SMM task

Received a message of unknown type from the SMM task.

2018

Unknown message type from SCM task

Received a message of unknown type from the SCM task.

2019

Unexpected message from a task

Received a message from an unknown source. Source ID is Invalid.

2020

Misdirected message in AUM message queue

Received a message not destined for the BNM task.

2021

Failure while trying to transmit message to VxWorks message queue

BNM task failed to send a message to another task through a VxWorks message queue.

2022

Failure while trying to receive message from VxWorks message queue

BNM task failed to receive a message from another task through a VxWorks message queue.

2023

Specified slot number is out of recognized range

Invalid Slot number specified.

2024

Specified shelf number is out of recognized range

Not Used

2025

Specified LCN is out of range

Not Used

2026

Invalid Core card state specified

The Core Card State information specified by a message from another task is Invalid.

2027

Invalid Slot state

specified

The Slot Reset State information specified by a message from another task is invalid.

2028

Invalid signal name specified

Invalid signal name specified by the message from the SMM task.

2029

Invalid signal state specified

Invalid signal state specified by the message from the SMM task.

2032

Error in aumAddConn while rebuilding from BRAM

Error occurred while rebuilding connections from the BRAM. Additional information regarding the specific instance is displayed.

2048

Internal FW Error. Access to unrecognized pio port

Invalid PIO port specified to read from a device.

2049

Internal FW Error. Access to unknown i/o port

Invalid device I/O port

specified to read from a device.

2050

Internal FW Error. Connection database corrupted

Not Used

2051

Internal FW Error. LCN linked list

corrupted

Error occurred while building the LCN list for OAM cells. Additional information regarding the specific instance is displayed.

2052

Internal FW Error. Unrecognized AUM port

Invalid BNM (AUM) port.

2053

Internal FW Error. Unrecognized clock source

Invalid MUX Clock Source encountered while configuring Clock MUX.

2054

Internal FW Error. Unrecognized clock mux

Invalid Clock MUX.

2055

Internal FW Error. Unrecognized port number

Invalid Port number encountered while enabling/disabling the line transmission function.

2056

Internal FW Error. Unrecognized counter

Invalid Counter number encountered.

2057

Internal FW Error. ADC timeout

ADC error occurred. Additional information regarding the specific instance is displayed.

2058

Internal FW Error. Unrecognized fan tray

Invalid Fan Tray number encountered.

2064

HW Error. XILINX fails to respond to INIT signal

Not Used

2065

HW Error. XILINX fails to respond with DONE signal

Error occurred while downloading Xilinx image. Additional information regarding the specific instance is displayed.

2066

HW Error. XILINX Init pin went low during download

Error occurred while downloading Xilinx image. Xilinx Init pin went low.

2067

HW Error. PLL failure (E3 port)

Not Used

2068

HW Error. Invalid Front Card Type

Invalid Front Card Type. BNM cannot stay in the Active state.

2069

HW Error. ADC Zero Calibration Error

ADC Zero Calibration error occurred.

2070

HW Error. ADC Mid-range Calibration Error

ADC Mid-range voltage Calibration error occurred.

2071

HW Error. BNM Card NOVRAM Checksum Error

BNM Front Card NOVRAM checksum error occurred.

2072

HW Error. Backplane NOVRAM Checksum Error

BNM Backplane NOVRAM checksum error occurred.

2080

Cannot allocate

memory:

Failed to Allocate memory. BNM task running out of memory space.

2081

Line clock update

Line clock updated.

2082

Line clock changed to=

Line clock changed. Additional information regarding the specific instance is displayed.

2096

Line alarm

Line Alarm trap generated as the line alarm state bits changed.

2097

Line statistical alarm

Line statistics alarm trap generated.

2098

PLCP alarm

PLCP Alarm trap generated as the PLCP alarm state bits changed.

2099

PLCP statistical alarm

PLCP statistics alarm trap

generated.

2100

Function module alarm

Function module major alarm trap generated.

2101

Line module alarm

Line module major alarm trap generated. Back card not present.

2102

ASM alarm

Shelf Major alarm trap

generated.

2112

BRAM Conn Update error in

Error occurred while updating BNM connection information on the BRAM.

2113

BNM mastership change

Change in BNM card mastership state.

2114

Mesg from ASC to set FWREADY =

Received a message from the SMM task to set the BNM Firmware ready.

2115

Line configuration does not match with BNM card

Line Configuration mismatch occurred with the BNM card.

2116

BNM cardType of the other card set does not match

Card type of the standby BNM card does not match with the active card type.

2117

BNM cardType =

Information about the BNM card type.

2118

BNM Initialization error,

Error occurred while initializing BNM. Additional information regarding the specific instance is displayed.

2119

BNM incompatible module,

BNM incompatibility error.

2120

BNM FPGA Download Error,

Error occurred while downloading image from FPGA. Additional information regarding the specific instance is displayed.

2121

BNM Init Info:

Information useful for debugging/administration purposes.

SRM Log Codes

Error Number	Display Log String	Detail Description
5000	Fail to allocate a semaphore ID	Failed to create a VxWorks semaphore while initializing SRM control structures.
5001	Line Configuration Failure	Failed to configure a Line. The particular port number is also displayed.
5002	Unable to get a message from the message queue	Error occurred while receiving a message by another task through the message queue.
5003	Misdirected message in SRMT message queue	Message not intended for the SRM task has been received through the message queue.
5004	Received message length not correct for message type	Length of the message received through the message queue is invalid for the particular message type.
5005	Invalid Core card state specified	Not Used
5006	Unexpected message from a task	Received a message from unknown source. Source ID is invalid.
5007	Unknown message type from SMM task	Received a message of unknown type from the SMM task.
5008	Cannot allocate memory:	Failed to allocate memory. SRM task running out of memory space.
5009	Fail to load ENCODER 0	Failed to load SRM FPGA encoder 0.
5010	Fail to load ENCODER 1	Failed to load SRM FPGA encoder 1.
5011	Fail to load ENCODER 2	Failed to load SRM FPGA encoder 2.
5012	Fail to load DECODER 0	Failed to load SRM FPGA decoder 0.
5013	Fail to load DECODER 1	Failed to load SRM FPGA decoder 1.
5014	Fail to load CLOCK	Failed to load SRM FPGA clock control.
5015	Fail to load FPGA	Failed to load FPGA image.
5016	Invalid PIO Number	Invalid device I/O port specified to read from a device.
5017	Invalid PIO PORT Number	Invalid PIO port specified to read from a device.
5018	Line interface is not ready	Not Used
5019	Too many XFEAC requests	Too many Far End Loopback requests have been received.
5020	The FE Lpbk line number is invalid	Invalid Far End Loopback line number encountered while processing the Loopback requests.
5021	E3 is not supported	Card type E3 is not supported.
5022	Line is in alarm	Not Used
5023	Unknown current state	Current state of the SRM card is unknown.
5024	Configured from BRAM	Loading SRM configuration from the BRAM.
5025	Configured with default value	SRM card configuration in the BRAM is Invalid. Using default SRM configuration.
5026	Line configuration is incorrect	Invalid Line configuration. Switching to the Standby state.
5027	Unable to initialize HW	Hardware initialization failed. Fail LED is turned ON.
5028	Enter into a dead end state	SRM task has entered a Dead end state.
5029	Unknown core card state message from SMM	The core card state message received from the SMM task through the message queue is Invalid.
5030	Access BRAM failed	Access to BRAM failed. Additional information regarding the address, size and offset of the read/write operation is displayed.
5031	Fail to access the remote BRAM	Access to a remote BRAM failed.
5032	Clear configuration	SRM card configuration in the BRAM is cleared. BRAM configuration is no more valid.
5033	Unable to break a T1 connection inside I-Cube	Unable to break a T1 connection inside the I-Cube.
5034	Unable to make a T1 Connection inside I-Cube	Unable to make a T1 connection inside the I-Cube.
5035	Invalid SM slot number	Invalid Service Module slot number encountered.
5036	Invalid DS3 configuration pointer	The DS3 configuration pointer is invalid, possibly NULL.
5037	Line in alarm state	Line major/minor/clear alarm trap generated and sent to the manager.
5038	Loss of clock	Loss of Line interface clock.
5039	Receive a FEAC from a far-end	Received a FEAC from a Far end. The line number through which it is received is displayed.
5040	Fail to get an SRM Image from GRAM	Failed to download the SRM image from the GRAM.
5041	Fail to download I-Cube Image	Failed to download the I-Cube image.

Table 8-5: SRM Log Codes

Error Number Display Log String Detail Description

5000

Fail to allocate a semaphore ID

Failed to create a VxWorks semaphore while initializing SRM control structures.

5001

Line Configuration Failure

Failed to configure a Line. The particular port number is also displayed.

5002

Unable to get a message from the message queue

Error occurred while receiving a message by another task through the message queue.

5003

Misdirected message in SRMT message queue

Message not intended for the SRM task has been received through the message queue.

5004

Received message length not correct for message type

Length of the message received through the message queue is invalid for the

particular message type.

5005

Invalid Core card state specified

Not Used

5006

Unexpected message from a task

Received a message from unknown source. Source ID is invalid.

5007

Unknown message type from SMM task

Received a message of unknown type from the SMM task.

5008

Cannot allocate memory:

Failed to allocate memory. SRM task running out of memory space.

5009

Fail to load ENCODER 0

Failed to load SRM FPGA encoder 0.

5010

Fail to load ENCODER 1

Failed to load SRM FPGA encoder 1.

5011

Fail to load ENCODER 2

Failed to load SRM FPGA encoder 2.

5012

Fail to load DECODER 0

Failed to load SRM FPGA decoder 0.

5013

Fail to load DECODER 1

Failed to load SRM FPGA decoder 1.

5014

Fail to load CLOCK

Failed to load SRM FPGA clock control.

5015

Fail to load FPGA

Failed to load FPGA image.

5016

Invalid PIO Number

Invalid device I/O port specified to read from a device.

5017

Invalid PIO PORT Number

Invalid PIO port specified to read from a device.

5018

Line interface is not ready

Not Used

5019

Too many XFEAC requests

Too many Far End Loopback requests have been received.

5020

The FE Lpbk line

number is invalid

Invalid Far End Loopback line number encountered while processing the Loopback requests.

5021

E3 is not supported

Card type E3 is not supported.

5022

Line is in alarm

Not Used

5023

Unknown current state

Current state of the SRM card is unknown.

5024

Configured from BRAM

Loading SRM configuration from the BRAM.

5025

Configured with default value

SRM card configuration in the BRAM is Invalid. Using default SRM configuration.

5026

Line configuration is incorrect

Invalid Line configuration. Switching to the Standby state.

5027

Unable to initialize HW

Hardware initialization failed. Fail LED is turned ON.

5028

Enter into a dead end state

SRM task has entered a Dead end state.

5029

Unknown core card state message from SMM

The core card state message received from the SMM task through the message queue is Invalid.

5030

Access BRAM failed

Access to BRAM failed. Additional information regarding the address, size and offset of the read/write operation is displayed.

5031

Fail to access the remote BRAM

Access to a remote BRAM failed.

5032

Clear configuration

SRM card configuration in the BRAM is cleared. BRAM configuration is no more valid.

5033

Unable to break a T1 connection inside I-Cube

Unable to break a T1 connection inside the I-Cube.

5034

Unable to make a T1 Connection inside I-Cube

Unable to make a T1 connection inside the I-Cube.

5035

Invalid SM slot number

Invalid Service Module slot number encountered.

5036

Invalid DS3 configuration pointer

The DS3 configuration pointer is invalid, possibly NULL.

5037

Line in alarm state

Line major/minor/clear alarm trap generated and sent to the manager.

5038

Loss of clock

Loss of Line interface clock.

5039

Receive a FEAC from a far-end

Received a FEAC from a Far end. The line number through which it is received is displayed.

5040

Fail to get an SRM Image from GRAM

Failed to download the SRM image from the GRAM.

5041

Fail to download I-Cube Image

Failed to download the I-Cube image.

AUSM Log Codes

Error Number	Display Log String	Detail Description
6001	Hardware Error	Hardware errors that were encountered by the card.
6002	Message Rx Error	The message sent by the ASC to the SM is not a data frame. SM is expecting an Auto Card Request.
6003	Message Tx Error	Error while trying to respond to ASC Auto Card request
6004	Other OS Error	Error when OS calls fail. Specific area of failure is displayed.
6005	Unknown Message Received	The Card Manager received an unknown message. The message which is expected is displayed.
6019	Error in Getting Semaphore	Error while trying to get semaphore. The semaphore details are displayed.
6021	Backcard Missing	Backcard was missing when the card came up.
6022	Unknown Backcard Type	AUSM is unable to recognize backcard
6023	Mismatch Backcard	This is not the correct backcard for this AUSM card
6024	AUSM going active	AUSM card becoming active
6025	AUSM going to standby	AUSM card going to standby
6026	Backcard is removed	The backcard was removed
6027	Backcard is inserted (causing a reset)	A backcard was inserted or already present
6050	Channel in alarm	The channel has gone into alarm The channel number is displayed.
6051	Channel out of alarm	The channel has come out off alarm The channel number is displayed.
6052	Port out of alarm	The port has come out off alarm The port number is displayed.
6053	Port in alarm	The port has gone into alarm The port number is displayed.
6054	Line alarm off	The line has come out off alarm The line number is displayed.
6055	Line Rx LOS alarm on	The line number displayed is in receive LOS alarm.
6056	Line Rx AIS alarm on	The line number displayed is in receive AIS alarm
6057	Line Rx LOF alarm on	The line number displayed is in receive LOF alarm
6058	Line Rx RAI alarm on	The line number displayed is in receive RAI alarm
6061	Invalid ILMI Community String Received	The snmp community string received through the ILMI interface is invalid. The received community string is also displayed.
6062	ILMI ASN1 Parse Error	Error while trying to parse the SNMP PDU received.
6063	ILMI Invalid PDU Type	SNMP PDU received is unknown. PDU other than GET,SET,GET-NEXT and TRAP.
6064	Bad SNMP version number	SNMP Version in the PDU received is bad
6065	ILMI - Authentication parse error	Unable to parse authentication received in SNMP PDU.
6066	ILMI - Error Build/Send Get Request Packet	Error while trying to build SNMP GET/SET PDU
6067	ILMI - Error receiving msg	Unable to receive ILMI message.
6068	ILMI - Error Build/Send Trap Packet	Error trying to build ILMI TRAP PDU.
6069	ILMI - Trap Message Queue is full	ILMI Task message queue is full.
6070	ILMI - Egress Queue enque failed	Error while trying to enque ILMI SNMP Packet in Egress ILMI queue.
6071	ILMI - Cannot Create message queues	Unable to create message queue for ILMI task.
6081	Failed to add a line	Failed to add line either due to invalid parameter or line already enabled. Addtional information describing the specific instance of failure is displayed.
6082	Failed to delete a line	The line trying to delete does not exist.
6083	Failed to modify a line	Line trying to modify does not exist or modification of the parameter is not allowed.
6102	Failed to add a port	Failed trying to add port. Additional information describing the specific instance of failure is displayed.
6103	Failed to add a channel	Failed trying to add channel. Additional information describing the specific instance of failure is displayed.
6104	Failed to delete a port	Failed trying to delete port. Additional information describing the specific instance of failure is displayed.
6105	Failed to delete a channel	Failed trying to delete channel. Additional information describing the specific instance of failure is displayed.
6106	Failed to modify a port	Failed to modify port. Additional information describing the specific instance of failure is displayed.
6107	Failed to modify a channel	Failed to modify channel. Additional information describing the specific instance of failure is displayed.
6121	Command to SAR failed	Command issued to SAR failed.
6141	Updating ASC mib failed	Failed trying to update ASC MIB. Additional information describing the reason for ASC mib is displayed.
6142	Undoing channel config. failed	Failed while trying to undo channel configuration,. Undoing channel configuration because of ASC Mib updated failure.
6143	Undoing delete with add chan failed	Failed while trying to undo delete chan (by adding the channel back). Trying to undo because of ASC Mib update failure.
6144	Undoing add with delete chan failed	Failed while trying to undo add chan (by deleting the channel). Trying to undo because of ASC Mib update failure.
6145	Undoing modify with modify chan failed	Failed while trying to undo modify channel. Trying to undo because of ASC Mib update failure.
6146	Added line	The line number added is displayed along with the log string.
6147	Deleted line	The line number deleted is displayed along with the log string.
6148	Modified line	The line number modified displayed along with the log string.
6149	Added port	The port number added is displayed along with the log string.
6150	Deleted port	The port number deleted is displayed along with the log string.
6151	Modified port	The port number modified displayed along with the log string.
6152	Added channel	The channel number added is displayed along with the log string.
6153	Deleted channel	The channel number deleted is displayed along with the log string.
6154	Modified channel	The channel number modified displayed along with the log string.
6155	Rate Control feature changed to	The rate control feature is changed. Whether it is turned on or off is displayed.
6157	AUSM got time from ASC	AUSM received date and time from the ASC.
6165	ASC request to go to default	AUSM received message from ASC to use default values for configuration.
6166	AUSM using the default Config.	AUSM card is using default values for configuration parameters.
6167	ASC sent slot number to SM	AUSM received slot information from ASC. Displays the slot number after validation.
6170	Added Egress Queue	A new egress queue has been added. Egress queue number is displayed.
6171	Deleted Egress Queue	An egress queue is deleted, queue number is displayed.
6172	Modified Egress Queue	Egress queue is modified, queue number is displayed.
6201	CSE decision not read	CellDMA has not read the service decision for Egress queue servicing.
6202	CSE Enable Failed	Cell Service Engine enable failed.
6221	Invalid Connection Request	Connection Request from CDMA is neither for VCC or VPC connection.
6222	PLPP write FIFO full	Failed while trying to write to PLPP FIFO.
6223	CDMA Exception	A CDMA exception has occurred.
6224	Duplicate Connection Open	Found a duplicate entry while trying add to Address Translation Table.
6225	Unknown connection close	Did not find entry in Address Translation Table for closing.
6226	IBS queue full	Found IBS Queue full while trying to enqueue cell.
6227	ABR queue full	Found ABR Queue full while trying to enqueue cell.
6228	No free ingress data buffers	Could not find free buffer from ingress free data pool
6229	No free ingress ILMI buffers	Could not find free buffer from ingress ilmi free pool.
6230	No free ingress OAM buffers	Could not find free buffer from ingress oam free pool
6231	cellDmaEnablePort Failed	Failed trying to enable CDMA for a port. Port number is displayed.
6241	CDMA Ping Error	CellDMA module is not responding.
6242	Error from CDMA	CellDMA reports error. Addtional information on the specific instance is displayed.
6224	Cannot Load CDMA firmware	Unable able to load CDMA firmware.
6225	CellDMA Enable Failed	Failed to enabled cellDMA.
6261	Foresight Enable Failed	Failed to start foresight interrupt service routine.
6271	PLPP FIFO Overrun	PLPP FIFO overflow has occurred.
6281	Failed to Add Egress Q	Failed to add egress queue to specified port.
6282	Failed to modify Egress Q	Failed to modify egress queue parameters.
6283	Failed to delete Egress Q	Deletion of egress queue failed
6284	bert error	Error in bert. Details on the specific instance of BERT failure is displayed.
6285	AUSM out of xmt buffer	AUSM Card is out of buffers, malloc failed.
6286	Invalid value	Invalid value for parameters. Additional information on the specific parameter is displayed.
6288	Undoing delete with add line failed	Failed while trying to undo delete line (by adding the line back). Trying to undo because of ASC Mib update failure.
6289	Undoing add with delete line failed	Failed while trying to undo add line (by deleting the line). Trying to undo because of ASC Mib update failure.
6290	Undoing modify with modify line failed	Failed while trying to undo modify line. Trying to undo because of ASC Mib update failure.
6292	Undoing delete with add port failed	Failed while trying to undo delete port (by adding the port back). Trying to undo because of ASC Mib update failure.
6293	Undoing add with delete port failed	Failed while trying to undo add port (by deleting the port). Trying to undo because of ASC Mib update failure.
6294	Undoing modify with modify port failed	Failed while trying to undo modify port. Trying to undo because of ASC Mib update failure.
6295	Updating BNM failed	Failed to update BNM. Addtional information describing the specific instance of failure is displayed.

Table 8-6: AUSM Log Codes

Error Number Display Log String Detail Description

6001

Hardware Error

Hardware errors that were encountered by the card.

6002

Message Rx Error

The message sent by the ASC to the SM is not a data frame. SM is expecting an Auto Card Request.

6003

Message Tx Error

Error while trying to respond to ASC Auto Card request

6004

Other OS Error

Error when OS calls fail. Specific area of failure is displayed.

6005

Unknown Message Received

The Card Manager received an unknown message. The message which is expected is displayed.

6019

Error in Getting Semaphore

Error while trying to get semaphore. The semaphore details are displayed.

6021

Backcard Missing

Backcard was missing when the card came up.

6022

Unknown Backcard Type

AUSM is unable to recognize backcard

6023

Mismatch Backcard

This is not the correct backcard for this AUSM card

6024

AUSM going active

AUSM card becoming active

6025

AUSM going to standby

AUSM card going to standby

6026

Backcard is removed

The backcard was removed

6027

Backcard is inserted (causing a reset)

A backcard was inserted or already present

6050

Channel in alarm

The channel has gone into alarm The channel number is displayed.

6051

Channel out of alarm

The channel has come out off alarm The channel number is displayed.

6052

Port out of alarm

The port has come out off alarm The port number is displayed.

6053

Port in alarm

The port has gone into alarm The port number is displayed.

6054

Line alarm off

The line has come out off alarm The line number is displayed.

6055

Line Rx LOS alarm on

The line number displayed is in receive LOS alarm.

6056

Line Rx AIS alarm on

The line number displayed is in receive AIS alarm

6057

Line Rx LOF alarm on

The line number displayed is in receive LOF alarm

6058

Line Rx RAI alarm on

The line number displayed is in receive RAI alarm

6061

Invalid ILMI Community String Received

The snmp community string received through the ILMI interface is invalid. The received community string is also displayed.

6062

ILMI ASN1 Parse Error

Error while trying to parse the SNMP PDU received.

6063

ILMI Invalid PDU Type

SNMP PDU received is unknown. PDU other than GET,SET,GET-NEXT and TRAP.

6064

Bad SNMP version number

SNMP Version in the PDU received is bad

6065

ILMI - Authentication parse error

Unable to parse authentication received in SNMP PDU.

6066

ILMI - Error Build/Send Get Request Packet

Error while trying to build SNMP GET/SET PDU

6067

ILMI - Error receiving msg

Unable to receive ILMI message.

6068

ILMI - Error Build/Send Trap Packet

Error trying to build ILMI TRAP PDU.

6069

ILMI - Trap Message Queue is full

ILMI Task message queue is full.

6070

ILMI - Egress Queue enque failed

Error while trying to enque ILMI SNMP Packet in Egress ILMI queue.

6071

ILMI - Cannot Create message queues

Unable to create message queue for ILMI task.

6081

Failed to add a line

Failed to add line either due to invalid parameter or line already enabled. Addtional information describing the specific instance of failure is displayed.

6082

Failed to delete a line

The line trying to delete does not exist.

6083

Failed to modify a line

Line trying to modify does not exist or modification of the parameter is not allowed.

6102

Failed to add a port

Failed trying to add port. Additional information describing the specific instance of failure is displayed.

6103

Failed to add a channel

Failed trying to add channel. Additional information describing the specific instance of failure is displayed.

6104

Failed to delete a port

Failed trying to delete port. Additional information describing the specific instance of failure is displayed.

6105

Failed to delete a channel

Failed trying to delete channel. Additional information describing the specific instance of failure is displayed.

6106

Failed to modify a port

Failed to modify port. Additional information describing the specific instance of failure is displayed.

6107

Failed to modify a channel

Failed to modify channel. Additional information describing the specific instance of failure is displayed.

6121

Command to SAR failed

Command issued to SAR failed.

6141

Updating ASC mib failed

Failed trying to update ASC MIB. Additional information describing the reason for ASC mib is displayed.

6142

Undoing channel config. failed

Failed while trying to undo channel configuration,. Undoing channel configuration because of ASC Mib updated failure.

6143

Undoing delete with add chan failed

Failed while trying to undo delete chan (by adding the channel back). Trying to undo because of ASC Mib update failure.

6144

Undoing add with delete chan failed

Failed while trying to undo add chan (by deleting the channel). Trying to undo because of ASC Mib update
failure.

6145

Undoing modify with modify chan failed

Failed while trying to undo modify channel. Trying to undo because of ASC Mib update failure.

6146

Added line

The line number added is displayed along with the log string.

6147

Deleted line

The line number deleted is displayed along with the log
string.

6148

Modified line

The line number modified displayed along with the log
string.

6149

Added port

The port number added is displayed along with the log string.

6150

Deleted port

The port number deleted is displayed along with the log
string.

6151

Modified port

The port number modified displayed along with the log
string.

6152

Added channel

The channel number added is displayed along with the log string.

6153

Deleted channel

The channel number deleted is displayed along with the log
string.

6154

Modified channel

The channel number modified displayed along with the log
string.

6155

Rate Control feature changed to

The rate control feature is changed. Whether it is turned on or off is displayed.

6157

AUSM got time from ASC

AUSM received date and time from the ASC.

6165

ASC request to go to default

AUSM received message from ASC to use default values for configuration.

6166

AUSM using the default Config.

AUSM card is using default values for configuration parameters.

6167

ASC sent slot number to SM

AUSM received slot information from ASC. Displays the slot number after validation.

6170

Added Egress Queue

A new egress queue has been added. Egress queue number is displayed.

6171

Deleted Egress Queue

An egress queue is deleted, queue number is displayed.

6172

Modified Egress Queue

Egress queue is modified, queue number is displayed.

6201

CSE decision not read

CellDMA has not read the service decision for Egress queue servicing.

6202

CSE Enable Failed

Cell Service Engine enable failed.

6221

Invalid Connection Request

Connection Request from CDMA is neither for VCC or VPC connection.

6222

PLPP write FIFO full

Failed while trying to write to PLPP FIFO.

6223

CDMA Exception

A CDMA exception has occurred.

6224

Duplicate Connection Open

Found a duplicate entry while trying add to Address Translation Table.

6225

Unknown connection close

Did not find entry in Address Translation Table for closing.

6226

IBS queue full

Found IBS Queue full while trying to enqueue cell.

6227

ABR queue full

Found ABR Queue full while trying to enqueue cell.

6228

No free ingress data buffers

Could not find free buffer from ingress free data pool

6229

No free ingress ILMI buffers

Could not find free buffer from ingress ilmi free pool.

6230

No free ingress OAM buffers

Could not find free buffer from ingress oam free pool

6231

cellDmaEnablePort Failed

Failed trying to enable CDMA for a port. Port number is displayed.

6241

CDMA Ping Error

CellDMA module is not responding.

6242

Error from CDMA

CellDMA reports error. Addtional information on the specific instance is displayed.

6224

Cannot Load CDMA firmware

Unable able to load CDMA firmware.

6225

CellDMA Enable Failed

Failed to enabled cellDMA.

6261

Foresight Enable Failed

Failed to start foresight interrupt service routine.

6271

PLPP FIFO Overrun

PLPP FIFO overflow has occurred.

6281

Failed to Add Egress Q

Failed to add egress queue to specified port.

6282

Failed to modify Egress Q

Failed to modify egress queue parameters.

6283

Failed to delete Egress Q

Deletion of egress queue failed

6284

bert error

Error in bert. Details on the specific instance of BERT failure is displayed.

6285

AUSM out of xmt buffer

AUSM Card is out of buffers, malloc failed.

6286

Invalid value

Invalid value for parameters. Additional information on the specific parameter is displayed.

6288

Undoing delete with add line failed

Failed while trying to undo delete line (by adding the line back). Trying to undo because of ASC Mib update failure.

6289

Undoing add with delete line failed

Failed while trying to undo add line (by deleting the line). Trying to undo because of ASC Mib update
failure.

6290

Undoing modify with modify line failed

Failed while trying to undo modify line. Trying to undo because of ASC Mib update failure.

6292

Undoing delete with add port failed

Failed while trying to undo delete port (by adding the port back). Trying to undo because of ASC Mib update failure.

6293

Undoing add with delete port failed

Failed while trying to undo add port (by deleting the port). Trying to undo because of ASC Mib update
failure.

6294

Undoing modify with modify port failed

Failed while trying to undo modify port. Trying to undo because of ASC Mib update failure.

6295

Updating BNM failed

Failed to update BNM. Addtional information describing the specific instance of failure is displayed.

Replacing Parts

After an alarm occurs, use the MGX 8220 shelf software to isolate the problem. If an MGX 8220 shelf part has failed, it must be replaced.

Caution Only authorized personnel should remove and replace parts on the MGX 8220 system.

Parts should be replaced personnel who have taken Cisco training courses or have been trained by a qualified system manager. For assistance in diagnosing or replacing a failed part, call a Cisco representative.

Save the electrostatic bag, foam, and carton. These packaging materials are needed to return the failed part to Cisco.

Replacing a Front Card

This section describes how to replace an MGX 8220 front card.

The MGX 8220 shelf front cards are:

MGX 8220 Shelf Controller (ASC)
Broadband Network Module (BNM)
Service Redundancy Module (SRM)
Service Modules
ATM Inverse Multiplexer Network Module (IMATM)

Caution Ground yourself before handling the MGX 8220 shelf cards by placing a wrist strap on your wrist and clipping the wrist strap lead to the cabinet.

When a card has failed, the red FAIL light for that card turns on. Before replacing it, check to see if the card needs to be reseated and check that the appropriate back card is correctly installed. After reseating the card, wait for it to run its self-tests to see if the ACTIVE light comes on. If the card is seated correctly, but the FAIL light is still on, replace the card.

When replacing a card that has no redundant equivalent, the service provided by that card will be disrupted. Replacing a non-redundant ASC or BNM card will bring down the entire shelf. Replacing a FRSM card will bring down the channels that are serviced by that card.

To remove a front card:

Step 1 Insert a small flat head screwdriver into the slot in the retaining tab and press until the latch springs open.

Step 2 Gently pull the card out of the card cage.

To install a front card:

Step 1 Position the card guides over the appropriate slot at the top and bottom of the card cage.

Step 2 Gently slide the card all the way into the slot and press the retaining tab until it snaps into the vertical position.

Replacing a Line Module

Back cards are retained through two screws: one at the top of the faceplate and one at the bottom of the faceplate. Back cards contain very few active components (if any) and rarely need replacing.

To remove a back card:

Step 1 Remove any cables connected to the back card.

Step 2 Use a flat screwdriver to undo the two retaining screws in the back card's faceplate.

Step 3 Pull the two extraction levers into the horizontal position. This will start the card extraction.

Step 4 Gently pull the card out of the card cage.

To install a back card:

Step 1 Position the extraction levers so they lie flush with the card's faceplate.

Step 2 Position the rear card guides over the appropriate slot at the top and bottom of the card cage.

Step 3 Gently slide the card all the way into the slot and tighten the two captive screws on the back card's faceplate. Tighten the upper and lower screws alternately to prevent misalignment of the card. Tighten the screws to secure the card. Do not overtighten.

Warning Cards must be inserted in the correct slot positions. This is particularly true with back cards. If service module back cards are inserted into slots intended only for ASC and/or BNM back cards (slots 1, 2, 3, and 4) damage to the card and backplane can result. If you accidentally attempt to insert a service module back card into slots 1, 2, 3, or 4 and have difficulty in operating the shelf, examine the backplane pins and the connector on the wrongly inserted back card to see if they have been bent or damaged.

Replacing a DC Power Entry Module

DC Power Entry Modules (PEM) contain few active components so they should rarely need replacement. Access is from the back of the shelf. To remove a PEM, proceed as follows:

Step 1 Press the red button on the power entry module you need to replace. This removes power from the module.

Step 2 Disconnect the 48VDC power cable from the module.

Step 3 Pull out the power entry module from its slot.

Step 4 Slide in the replacement module until its connector seats in its socket.

Step 5 Replace the 48VDC power cable.

Step 6 Press the black button on the power entry module until it latches in the IN position.

Replacing the Cooling, Booster, Plenum, and AC Power Assemblies

To replace the assembly:

Step 1 Remove any cables at the rear of the assembly that connect to the shelf or other modules.

Step 2 Remove the screws attaching the assembly to the rack.

Step 3 Pull the assembly out of the rack.

Step 4 Slide the new assembly into the rack.

Step 5 Use the screws to attach the assembly to the rack.

Step 6 Reconnect the cables from the shelf or other modules to the new assembly.

Warning f you replace the cooling assembly with power applied to the shelf, you must work quickly to prevent heat buildup in the shelf which could damage the cards.

Table of Contents

Repair and Replacement