Table of Contents
Advertisement
Log Codes
Table 8-3
Error Number
1108
1109
1110
1111
1112
1113
1114
1115
1200
1201
1202
1203
1204
1205
1206
1207
1208
1209
1210
1211
1212
Cisco MGX 8220 Installation and Configuration
8-6
ASC Log Codes (continued)
Display Log String
Msg queue rcv/send
Unknown card
Invalid alarm type
Creating semId fail
Tx mgmbuf ret twice
Tx mgmbuf alloc twice
All self test results are
cleared
Self test failed; card is
reset
Bad shelf slot num
Unknown aum msg
Unknown scm msg
Array out of bounds
General error
Standby BRAM
download err
Slave failed ack
Slave ack timeout
Aum arbit err
Malloc err
msg data err
err from msg rcv call
no response
Detail Description
Failed to receive/send message from/to the message
queue.
Invalid card slot number conveyed by the slave.
Information describing the specific instance is also
displayed.
Not used.
Error occurred while creating a semaphore.
Same management transmit buffer returned twice as a
free buffer.
Same buffer allocated twice from the management-free
buffers pool.
All self-test counters and results have been cleared.
Self-test failed on the card and the card has been reset.
Invalid shelf slot number encountered. Information
regarding the specific instance is also displayed.
Unknown message type received while processing the
messages from BNM.
Unknown message type from SCM. Information
regarding the type, source, and destination of the
message is also displayed.
Not used.
Some general error occurred, for example invalid slot
number, ASC disk read/write error, checksum failure,
bad unexpected response, malloc errors, or send/receive
failures. Information describing the specific instance is
also displayed.
Failed to download the firmware to the card.
No ACK received from the slave.
Error occurred while sending messages through message
queues to other tasks. No response to the messages sent.
Not used.
Failed to allocate memory. Running out of memory
space.
Invalid message received or message missing some
information.
Invalid message received from another task.
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.
Release 5.0, Part Number 78-6430-03 Rev. D0, November 2003
Chapter
Advertisement
Table of Contents
Troubleshooting
