Table of Contents
Advertisement
Chapter
Table 8-5
Error Number
5016
5017
5018
5019
5020
5021
5022
5023
5024
5025
5026
5027
5028
5029
5030
5031
5032
5033
5034
5035
5036
5037
5038
5039
Release 5.0, Part Number 78-6430-03 Rev. D0, November 2003
SRM Log Codes (continued)
Display Log String
Invalid PIO Number
Invalid PIO PORT Number
Line interface is not ready
Too many XFEAC requests
The FE Lpbk line number is
invalid
E3 is not supported
Line is in alarm
Unknown current state
Configured from BRAM
Configured with default
value
Line configuration is
incorrect
Unable to initialize HW
Enter into a dead end state
Unknown core card state
message from SMM
Access BRAM failed
Fail to access the remote
BRAM
Clear configuration
Unable to break a T1
connection inside I-Cube
Unable to make a T1
Connection inside I-Cube
Invalid SM slot number
Invalid DS3 configuration
pointer
Line in alarm state
Loss of clock
Receive a FEAC from a far
end
Detail Description
Invalid device I/O port specified to read from a
device.
Invalid PIO port specified to read from a device.
Not used.
Too many far-end loopback requests have been
received.
Invalid far-end loopback line number encountered
while processing the loopback requests.
Card type E3 is not supported.
Not used.
Current state of the SRM card is unknown.
Loading SRM configuration from the BRAM.
SRM card configuration in the BRAM is invalid.
Using default SRM configuration.
Invalid line configuration. Switching to the standby
state.
Hardware initialization failed. Fail LED is turned on.
SRM task has entered a dead end state.
Core card state message received from the SMM task
through the message queue is invalid.
Access to BRAM failed. Additional information
regarding the address, size, and offset of the
read/write operation is displayed.
Access to a remote BRAM failed.
SRM card configuration in the BRAM is cleared.
BRAM configuration is no longer valid.
Unable to break a T1 connection inside the I-Cube.
Unable to make a T1 connection inside the I-Cube.
Invalid service module slot number encountered.
DS3 configuration pointer is invalid, possibly null.
Line major/minor/clear alarm trap generated and sent
to the manager.
Loss of line interface clock.
Received a FEAC from a far end. The line number
through which it is received is displayed.
Cisco MGX 8220 Installation and Configuration
Log Codes
8-15
Advertisement
Table of Contents
Troubleshooting
