Professional Documents
Culture Documents
CMTS1500 - ErrorCodes - v43
CMTS1500 - ErrorCodes - v43
Cornerstone
CMTS 1500 v 4.3 Error Codes Guide
Release 4.3 Standard 1.0 ARSVD00757 September 2003
Cornerstone
CMTS 1500 v 4.3 Error Codes Guide
Document number: ARSVD00757 Document release: Release 4.3 Standard 1.0 Date: September 2003
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
iii
Publication history
September 2003 Release 4.3 Standard 1.0 version of this document.
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
iv Publication history
September 2003
Contents v
Contents
Audience x CMTS 1500 documents x Related documents x Getting help xi About the CMTS 1500 xi Upgrading the CMTS 1000 xi
1-1
2-1 3-1 4-1 5-1 6-1 7-1 8-1 9-1 10-1 11-1 12-1 13-1 14-1 15-1
September 2003
vi Contents
16-1 17-1 18-1 19-1 20-1 21-1 22-1 23-1 24-1 25-1 26-1 27-1 28-1 29-1 30-1 31-1 32-1 33-1 34-1
Galileo Events
Galileo event module 19-1
QP Event Codes
QP event module 32-1
Contents vii
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
viii Contents
September 2003
ix
The DOCSIS 1.1 and CMTS event code sections contain the following: event IDvalue that identies the event contained in the event log event text messagemessage displayed on the screen describing the event event text denitionclear denition of the text message prioritylevel of priority
The levels of priority for an event ID are: emergencyfatal error, cannot recover alerta condition that should be corrected immediately criticalcritical condition such as NVRAM is full errornon-fatal error, may or may not require action warningwarning message noticecondition that is not error connected but may require special handling informationinformation message, no action required debuginternal debug information
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
The event text messages (messages that describe the event displayed on the screen) contain specic format conventions for the % symbol. They are: %xRefers to the hexadecimal number %dRefers to the decimal number %sRefers to the ASCII string
Audience
This document is for technicians and systems administrators who work with the Cornerstone Cable Modem Termination System (CMTS) 1500, Version 4.2 software.
September 2003
Cornerstone Cable Provisioning System 2000 v 1.1.1 Release Notes, 309929-A Rev 01
Getting help Documentation, customer service, and support are available from your account representative.
Upgrading the CMTS 1000 The CMTS 1000 can be upgraded to a CMTS 1100, which is functionally equivalent to a CMTS 1500. The upgraded CMTS 1100 will support version 4.x software. Information about upgrading is available from your account representative. When this document refers to CMTS 1500, the information applies to the CMTS 1100 (with upgraded hardware and software) as well.
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
September 2003
1-1
1-
Table 1-1 lists the error codes that may appear on the CMTS front panel while running power-on self tests. This indicates a hardware problem in the CMTS; only the upstream receiver cards are eld-replaceable.
Table 1-1 Power-up diagnostic codes Error code 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 Failed hardware Flash Process DRAM PCI DEC21143 PLX BCM3210 BCM3033 BCM3137 FPGA LCD Upstream receiver card QoS accelerator card) Downstream processor Card Processor upgrade card
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
Event logs
The CMTS supports a primary Event Log server and up to two secondary Event Log servers. The IP addresses for these event log servers are dened via the CLI, SNMP Manager, or a provisioning server. The event logs are used to track events occurring via the CMTS and cable modems. As an option, the events can be displayed as part of the CLI output. Event logs can be checked to see if certain events such as ARP spoong by subscriber CPE equipment occurs. Furthermore, the event logs show if CMTS resets occur due to specic events, or if the resets are triggered by the watchdog timer or normal power-off.
September 2003
2-1
2-
*Priority
Missing BP configuration setting TLV type. Notice Refer to Baseline Privacy Plus Interface Specification SP-BPI+-I07-010829 Appendix A.1.1.1 Invalid BP Configuration Setting Value Refer to Baseline Privacy Plus Interface Specification SP-BPI+-I07-010829 Appendix A.1.1.1 Auth Reject - No Information Refer to OSS-N-00108 Specification Appendix F Notice
66010200
Invalid BP Configuration Setting Value: %d for Type: %d, Auth Reject - No Information, -MAC addr: %s
66030102
Error
66030103
Auth Reject - Unauthorized CM Auth Reject - Unauthorized CM -MAC addr: %s Refer to OSS-N-00108 Specification Appendix F Auth Reject Unauthorized_said, -MAC addr: %s Auth Reject - Permanent Authorization Failure -MAC addr: %s Auth Reject - Time of Day not acquired -MAC addr: %s CM Certificate Error -MAC addr: %s Auth Reject - Unauthorized SAID Refer to OSS-N-00108 Specification Appendix F Auth Reject - Permanent Authorization Failure Refer to OSS-N-00108 Specification Appendix F Auth Reject - Time of Day not acquired Refer to OSS-N-00108 Specification Appendix F CM Certificate Error Refer to OSS-N-00108 Specification Appendix F
Error
66030104
Error
66030108
Error
66030109
Error
66030111
Error
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
2-2 DOCSIS 1.1 Standard BPI Events Table 2-1 (continued) DOCSIS standard BPI events Event ID 66030202 Event Text Message Auth Invalid - No Information -MAC addr: %s Event Definition Auth Invalid - No Information Refer to OSS-N-00108 Specification Appendix F *Priority Error
66030203
Auth Invalid - Unauthorized CM Auth Invalid - Unauthorized CM -MAC addr: %s Refer to OSS-N-00108 Specification Appendix F Auth Invalid - Unsolicited -MAC Auth Invalid - Unsolicited addr: %s Refer to OSS-N-00108 Specification Appendix F Auth Invalid - Invalid Key Auth Invalid - Invalid Key Sequence Sequence Number -MAC addr: Number %s Refer to OSS-N-00108 Specification Appendix F Auth Invalid - Message (Key Request) Authentication Failure -MAC addr: %s Unsupported Crypto Suite -MAC addr: %s Key Reject - No Information -MAC addr: %s Key Reject - Unauthorized SAID -MAC addr: %s TEK Invalid - No Information -MAC addr: %s Auth Invalid - Message (Key Request) Authentication Failure Refer to OSS-N-00108 Specification Appendix F Unsupported Crypto Suite Refer to OSS-N-00108 Specification Appendix F Key Reject - No Information Refer to OSS-N-00108 Specification Appendix F Key Reject - Unauthorized SAID Refer to OSS-N-00108 Specification Appendix F TEK Invalid - No Information Refer to OSS-N-00108 Specification Appendix F
Error
66030205
Error
66030206
Error
66030207
Error
66030300
Error
66050102
Error
66050103
Error
66050203
Error
66050206
TEK Invalid - Invalid Key TEK Invalid - Invalid Key Sequence Sequence Number -MAC addr: Number %s Refer to OSS-N-00108 Specification Appendix F
Error
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
September 2003
3-1
3-
*Priority Error
Map Reject - Not Authorized for Map Reject - Not Authorized for Requested Error Requested Downstream Traffic Downstream Traffic Flow (EC=7) Flow (EC=7) -MAC addr: %s Map Reject - Downstream Traffic Flow Not Error Map Reject - Downstream Traffic Flow Not Mapped to Mapped to BPI= SAID (EC=8) BPI= SAID (EC=8) -MAC addr: %s Mapped to Existing SAID -MAC Mapped to Existing SAID addr: %s Mapped to New SAID -MAC addr: %s Mapped to New SAID Error Error
66060510
66060600 66060700
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
September 2003
4-1
4-
Table 4-1 lists and describes the DOCSIS 1.1 standard registration events.
Table 4-1 DOCSIS 1.1 standard registration events Event ID 73000400 73000401 Event Text Message Service unavailable - Other -MAC addr: %s. Service unavailable Unrecognized configuration setting -MAC addr: %s. Event Definition Service unavailable - Other Service unavailable - Unrecognized configuration setting *Priority Warning Warning
73000402
Service unavailable - Temporarily Service unavailable Temporarily unavailable -MAC unavailable addr: %s. Service unavailable -Permanent -MAC addr: %s. Registration rejected authentication failure: CMTS MIC invalid -MAC addr: %s. REG REQ has Invalid MAC header -MAC addr: %s. REG REQ has Invalid SID or not in use -MAC addr: %s. REG REQ missed Required TLVs -MAC addr: %s. Service unavailable - Permanent
Warning
73000403 73000500
Warning
Registration rejected authentication failure: Warning CMTS MIC invalid REG REQ has Invalid MAC header REG REQ has Invalid SID or not in use REG REQ missed Required TLVs Warning Warning Warning Warning Warning Warning Warning
Bad DS FREQ - Format Invalid Bad DS FREQ - Format Invalid -MAC addr: %s. Bad DS FREQ - Not in use -MAC addr: %s. Bad DS FREQ - Not in use
Bad DS FREQ - Not Multiple of Bad DS FREQ - Not Multiple of 62500 Hz 62500 Hz -MAC addr: %s. Bad US CH - Invalid or Unassigned -MAC addr: %s. Bad US CH - Invalid or Unassigned
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
4-2 DOCSIS 1.1 Standard Registration Events Table 4-1 (continued) DOCSIS 1.1 standard registration events Event ID 73010601 Event Text Message Event Definition *Priority Warning Bad US CH - Change followed Bad US CH - Change followed with (RE-) with (RE-) Registration REQ Registration REQ -MAC addr: %s. Bad US CH - Overload -MAC addr: %s. Network Access has Invalid Parameter -MAC addr: %s. Bad Class of Service - Invalid Configuration -MAC addr: %s. Bad US CH - Overload Network Access has Invalid Parameter Bad Class of Service - Invalid Configuration
Bad Class of Service - Unsupported class Warning Bad Class of Service Unsupported class -MAC addr: %s. Bad Class of Service - Invalid class ID or out of range -MAC addr: %s. Bad Max DS Bit Rate - Invalid Format -MAC addr: %s. Bad Max DS Bit Rate Unsupported Setting -MAC addr: %s. Bad Max Us Bit Rate - Invalid Format -MAC addr: %s. Bad Max US Bit Rate Unsupported Setting -MAC addr: %s. Bad Class of Service - Invalid class ID or out of range Bad Max DS Bit Rate - Invalid Format Warning
73011100
73011200 73011201
Warning
73011300 73011301
Warning
73011400 73011401
Bad US Priority Configuration - Bad US Priority Configuration - Invalid Invalid Format -MAC addr: %s. Format
Warning
Bad US Priority Configuration - Bad US Priority Configuration - Setting out Warning Setting out of Range -MAC of Range addr: %s. Bad Guaranteed Min US CH Bit Bad Guaranteed Min US CH Bit Rate Rate Configuration setting Configuration setting - Invalid Format Invalid Format -MAC addr: %s. Warning
73011500
73011501
Bad Guaranteed Min US CH Bit Bad Guaranteed Min US CH Bit rate Warning rate Configuration setting Configuration setting - Exceed Max US Bit Exceed Max US Bit Rate -MAC Rate addr: %s. Bad Guaranteed Min US CH Bit Bad Guaranteed Min US CH Bit rate rate Configuration setting - Out Configuration setting - Out of Range of Range -MAC addr: %s. Warning
73011502
September 2003
DOCSIS 1.1 Standard Registration Events 4-3 Table 4-1 (continued) DOCSIS 1.1 standard registration events Event ID 73011600 Event Text Message Event Definition *Priority Warning Bad Max US CH Transmit Burst Bad Max US CH Transmit Burst configuration setting - Invalid configuration setting - Invalid Format Format -MAC addr: %s. Bad Max US CH Transmit Burst Bad Max US CH Transmit Burst configuration setting - Out of configuration setting - Out of Range Range -MAC addr: %s. Invalid Modem Capabilities configuration setting -MAC addr: %s. Configuration file contains parameter with the value outside of the range -MAC addr: %s. Invalid Modem Capabilities configuration setting
73011601
Warning
73011700
Warning
73011800
Configuration file contains parameter with Warning the value outside of the range
73020100
REG REQ rejected REG REQ rejected - Unspecified reason Unspecified reason -MAC addr: %s. REG REQ rejected Unrecognized configuration setting -MAC addr: %s. REG REQ rejected - Unrecognized configuration setting
Warning
73020101
Warning
73020102 73020103
REG REQ rejected - temporary REG REQ rejected - temporary no no resource -MAC addr: %s. resource REG REQ rejected Permanent administrative -MAC addr: %s. REG REQ rejected - Permanent administrative
Warning Warning
73020104
REG REQ rejected - Required REG REQ rejected - Required parameter parameter not present %d not present -MAC addr: %s. REG REQ rejected - Header suppression setting not supported -MAC addr: %s. REG REQ rejected - Multiple errors -MAC addr: %s. REG REQ rejected - duplicate reference-ID or index in message -MAC addr: %s. REG REQ rejected - Header suppression setting not supported REG REQ rejected - Multiple errors REG REQ rejected - duplicate reference-ID or index in message
Warning
73020105
Warning
73020106 73020107
Warning Warning
73020108
REG REQ rejected - parameter REG REQ rejected - parameter invalid for Warning invalid for context %d -MAC context addr: %s. REG REQ rejected Authorization failure -MAC addr: %s. REG REQ rejected - Authorization failure Warning
73020109
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
4-4 DOCSIS 1.1 Standard Registration Events Table 4-1 (continued) DOCSIS 1.1 standard registration events Event ID 73020110 Event Text Message REG REQ rejected - Major service flow error %d -MAC addr: %s. Event Definition REG REQ rejected - Major service flow error *Priority Warning
73020111
REG REQ rejected - Major REG REQ rejected - Major classifier error classifier error %d -MAC addr: %s.
Warning
73020112
REG REQ rejected - Major REG REQ rejected - Major PHS rule error Warning PHS rule error %d -MAC addr: %s. REG REQ rejected - Multiple major errors -MAC addr: %s. REG REQ rejected - Multiple major errors Warning
73020113 73020114
REG REQ rejected - Message REG REQ rejected - Message syntax error Warning syntax error %s -MAC addr: %s. REG REQ rejected - Primary service flow error %d -MAC addr: %s. REG REQ rejected - Primary service flow error Warning
73020115
REG REQ rejected - Message REG REQ rejected - Message too big too big %d -MAC addr: %s. REG aborted no REG-ACK -MAC addr: %s. REG aborted no REG-ACK
REG ACK rejected unspecified REG ACK rejected unspecified reason reason -MAC addr: %s. REG ACK rejected message syntax error -MAC addr: %s. REG ACK rejected message syntax error
No Ranging Requests received The CMTS polled a CM but did not receive Warning from POLLED CM (CMTS a Ranging Request. generated polls) %.12llx. Retries exhausted for polled CM %.12llx The CM has not been responding to polls. Warning
Unable to Successfully Range The CM was not able to range successfully Warning %.12llx CM Retries Exhausted in the alloted number of attempts. Failed to Receive Periodic RNG-REQ from modem (SID %d), timing-out SID The CM did not send a ranging request within the alloted time. Warning
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
September 2003
5-1
5-
*Priority Warning
83000101
Warning
83000102
Warning
83000103
Warning
83000104
Warning
83000105
DSA service add rejected DSA service add rejected header header suppression setting not suppression setting not supported. supported, -MAC addr: %s. DSA service add rejected DSA service add rejected service flow service flow exists, -MAC addr: exists. %s. DSA service add rejected DSA service add rejected HMAC auth HMAC auth failure, -MAC addr: failure. %s. DSA service add rejected, add DSA service add rejected, add aborted. aborted, -MAC addr: %s.
Warning
83000106
Warning
83000107
Warning
83000108
Warning
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
5-2 DOCSIS 1.1 Dynamic Service Events and Traps Table 5-1 (continued) DOCSIS 1.1 dynamic service events, traps, and syslog Event ID 83000109 83000110 Event Text Message Event Definition *Priority Warning Warning DSA service add rejected DSA service add rejected multiple errors. multiple errors, -MAC addr: %s. DSA service add rejected DSA service add rejected classifier not classifier not found, -MAC addr: found. %s. DSA service add rejected classifier exists, -MAC addr: %s.
83000111
DSA service add rejected PHS DSA service add rejected PHS rule not rule not found, -MAC addr: %s. found.
Warning
DSA service add rejected PHS DSA service add rejected PHS rule exists. Warning rule exists, -MAC addr: %s. DSA service add rejected DSA service add rejected duplicate duplicate reference ID or index, reference ID or index. -MAC addr: %s. DSA service add rejected multiple upstream flow, -MAC addr: %s. DSA service add rejected multiple downstream flow, -MAC addr: %s. DSA service add rejected classifier for another flow, -MAC addr: %s. DSA service add rejected multiple upstream flow. DSA service add rejected multiple downstream flow. DSA service add rejected classifier for another flow. Warning
83000115
Warning
83000116
Warning
83000117
Warning
83000118
DSA service add rejected PHS DSA service add rejected PHS rule for rule for another flow, -MAC another flow. addr: %s. DSA service add rejected parameter invalid for context, -MAC addr: %s. DSA service add rejected authorization failure, -MAC addr: %s. DSA service add rejected parameter invalid for context. DSA service add rejected authorization failure.
Warning
83000119
Warning
83000120
Warning
83000121
DSA service add rejected DSA service add rejected major service major service flow error, -MAC flow error. addr: %s. DSA service add rejected major classifier error, -MAC addr: %s. DSA service add rejected major PHS rule error, -MAC addr: %s. DSA service add rejected major classifier error. DSA service add rejected major PHS rule error.
Warning
83000122
Warning
83000123
Warning
September 2003
DOCSIS 1.1 Dynamic Service Events and Traps 5-3 Table 5-1 (continued) DOCSIS 1.1 dynamic service events, traps, and syslog Event ID 83000124 Event Text Message DSA service add rejected multiple major errors, -MAC addr: %s. DSA service add rejected message syntax error, -MAC addr: %s. DSA service add rejected message too big, -MAC addr: %s. DSA service add rejected temporary DCC, -MAC addr: %s. DSC service change rejected unspecified reason, -MAC addr: %s. DSC service change rejected unrecognized configuration setting, -MAC addr: %s. DSC service change rejected temporary no resource, -MAC addr: %s. DSC service change rejected permanent administrative, -MAC addr: %s. Event Definition DSA service add rejected multiple major errors. *Priority Warning
83000125
DSA service add rejected message syntax Warning error. DSA service add rejected message too big. Warning
83000126
83000127
83000200
DSC service change rejected unspecified reason. DSC service change rejected unrecognized configuration.
Warning
83000201
Warning
83000202
DSC service change rejected temporary no Warning resource. DSC service change rejected permanent administrative. Warning
83000203
83000204
DSC service change rejected DSC service change rejected requestor not Warning requestor not owner of service owner of service flow. flow, -MAC addr: %s. DSC service change rejected service flow not found, -MAC addr: %s. DSC service change rejected required parameter not present, -MAC addr: %s. DSC service change rejected service flow Warning not found. DSC service change rejected required parameter not present. Warning
83000205
83000206
83000207
DSC service change rejected DSC service change rejected header header suppression setting not suppression setting not supported. supported, -MAC addr: %s.
Warning
83000208
DSC service change rejected DSC service change rejected HMAC auth Warning HMAC auth failure, -MAC addr: failure. %s. DSC service change rejected DSC service change rejected multiple multiple errors, -MAC addr: %s. errors. Warning
83000209
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
5-4 DOCSIS 1.1 Dynamic Service Events and Traps Table 5-1 (continued) DOCSIS 1.1 dynamic service events, traps, and syslog Event ID 83000210 Event Text Message Event Definition *Priority DSC service change rejected DSC service change rejected classifier not Warning classifier not found, -MAC addr: found. %s. DSC service change rejected classifier exists, -MAC addr: %s. DSC service change rejected classifier exists. Warning
83000211
83000212
DSC service change rejected DSC service change rejected PHS rule not Warning PHS rule not found, -MAC addr: found. %s. DSC service change rejected PHS rule exists, -MAC addr: %s. DSC service change rejected duplicated reference ID or index, -MAC addr: %s. DSC service change rejected PHS rule exists. DSC service change rejected duplicated reference ID or index. Warning
83000213
83000214
Warning
83000215
DSC service change rejected DSC service change rejected multiple multiple upstream flows, -MAC upstream flows. addr: %s. DSC service change rejected multiple downstream flows, -MAC addr: %s. DSC service change rejected classifier for another flow, -MAC addr: %s. DSC service change rejected PHS rule for another flow, -MAC addr: %s. DSC service change rejected invalid parameter for context, -MAC addr: %s. DSC service change rejected authorization failure, -MAC addr: %s. DSC service change rejected multiple downstream flows.
Warning
83000216
Warning
83000217
DSC service change rejected classifier for Warning another flow. DSC service change rejected PHS rule for Warning another flow. DSC service change rejected invalid parameter for context. Warning
83000218
83000219
83000220
83000221
DSC service change rejected DSC service change rejected major major service flow error, -MAC service flow error. addr: %s. DSC service change rejected major classifier error, -MAC addr: %s. DSC service change rejected major PHS error, -MAC addr: %s. DSC service change rejected major classifier error. DSC service change rejected major PHS error.
83000222
Warning
83000223
Warning
September 2003
DOCSIS 1.1 Dynamic Service Events and Traps 5-5 Table 5-1 (continued) DOCSIS 1.1 dynamic service events, traps, and syslog Event ID 83000224 Event Text Message DSC service change rejected multiple major errors, -MAC addr: %s. DSC service change rejected message syntax error, -MAC addr: %s. DSC service change rejected message too big, -MAC addr: %s. DSC service change rejected temporary DCC, -MAC addr: %s. DSD service delete rejected unspecified reason, -MAC addr: %s. Event Definition DSC service change rejected multiple major errors. DSC service change rejected message syntax error. *Priority Warning
83000225
Warning
83000226
DSC service change rejected message too Warning big. DSC service change rejected temporary DCC. DSD service delete rejected unspecified reason. Warning
83000227
83000300
Warning
83000301
DSD service delete rejected DSD service delete rejected requestor not Warning requestor not owner of service owner of service flow. flow, -MAC addr: %s. DSD service delete rejected service flow not found, -MAC addr: %s. DSD service delete rejected service flow not found. Warning
83000302
83000303
DSD service delete rejected DSD service delete rejected HMAC auth HMAC auth failure, -MAC addr: failure. %s. DSD service delete rejected message syntax error, -MAC addr: %s. DSD service delete rejected message syntax error.
Warning
8300304
Warning
83010100
DSA-RSP service add DSA-RSP service add response rejected response rejected invalid invalid transaction ID. transaction ID, -MAC addr: %s. DSA-RSP service add aborted DSA-RSP service add aborted no RSP. no RSP, -MAC addr: %s. DSA-RSP service add DSA-RSP service add response rejected response rejected HMAC auth HMAC auth failure. failure, -MAC addr: %s. DSA-RSP service add response rejected message syntax error, -MAC addr: %s. DSA-RSP service add response rejected unspecified reason, -MAC addr: %s. DSA-RSP service add response rejected message syntax error. DSA-RSP service add response rejected unspecified reason.
Warning
83010101 83010102
Warning Warning
83010103
Warning
83010104
Warning
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
5-6 DOCSIS 1.1 Dynamic Service Events and Traps Table 5-1 (continued) DOCSIS 1.1 dynamic service events, traps, and syslog Event ID 83010105 Event Text Message DSA-RSP service add response rejected unrecognized configuration setting, -MAC addr: %s. DSA-RSP service add response rejected required parameter not present, -MAC addr: %s. Event Definition DSA-RSP service add response rejected unrecognized configuration setting. *Priority Warning
83010106
Warning
83010107
DSA-RSP service add response rejected DSA-RSP service add response rejected service flow service flow exists. exists, -MAC addr: %s. DSA-RSP service add response rejected multiple errors, -MAC addr: %s. DSA-RSP service add response rejected classifier exists, -MAC addr: %s. DSA-RSP service add response rejected PHS rule exists, -MAC addr: %s. DSA-RSP service add response rejected duplicate reference ID or index in message, -MAC addr: %s. DSA-RSP service add response rejected multiple errors. DSA-RSP service add response rejected classifier exists. DSA-RSP service add response rejected PHS rule exists. DSA-RSP service add response rejected duplicate reference ID or index in message.
Warning
83010108
Warning
83010109
Warning
83010110
Warning
83010111
Warning
83010112
DSA-RSP service add DSA-RSP service add response rejected response rejected classifier for classifier for another flow. another flow, -MAC addr: %s. DSA-RSP service add DSA-RSP service add response rejected response rejected parameter parameter invalid for context. invalid for context, -MAC addr: %s. DSA-RSP service add response rejected major service flow error, -MAC addr: %s. DSA-RSP service add response rejected major service flow error.
Warning
83010113
Warning
83010114
Warning
83010115
DSA-RSP service add DSA-RSP service add response rejected response rejected major major classifier error. classifier error, -MAC addr: %s. DSA-RSP service add response rejected major PHS rule error, -MAC addr: %s. DSA-RSP service add response rejected major PHS rule error.
Warning
83010116
Warning
September 2003
DOCSIS 1.1 Dynamic Service Events and Traps 5-7 Table 5-1 (continued) DOCSIS 1.1 dynamic service events, traps, and syslog Event ID 83010117 Event Text Message DSA-RSP service add response rejected multiple major errors, -MAC addr: %s. Event Definition DSA-RSP service add response rejected multiple major errors. *Priority Warning
83010118
DSA-RSP service add DSA-RSP service add response rejected response rejected message too message too big. big, -MAC addr: %s. DSC-RSP service change DSC-RSP service change response response rejected invalid rejected invalid transaction ID. transaction ID, -MAC addr: %s. DSC-RSP service change aborted no RSP, -MAC addr: %s. DSC-RSP service change aborted no RSP.
Warning
83010200
Warning
83010201
Warning
83010202
DSC-RSP service change DSC-RSP service change response response rejected HMAC auth rejected HMAC auth failure. failure, -MAC addr: %s. DSC-RSP service change response rejected unspecified reason, -MAC addr: %s. DSC-RSP service change response rejected message syntax error, -MAC addr: %s. DSC-RSP service change response rejected unrecognized configuration setting, -MAC addr: %s. DSC-RSP service change response rejected required parameter not present, -MAC addr: %s. DSC-RSP service change response rejected multiple errors, -MAC addr: %s. DSC-RSP service change response rejected classifier exists, -MAC addr: %s. DSC-RSP service change response rejected PHS rule exists, -MAC addr: %s. DSC-RSP service change response rejected duplicated reference ID or index, -MAC addr: %s. DSC-RSP service change response rejected unspecified reason. DSC-RSP service change response rejected message syntax error. DSC-RSP service change response rejected unrecognized configuration setting. DSC-RSP service change response rejected required parameter not present.
Warning
83010204
Warning
83010203
Warning
83010205
Warning
83010206
Warning
83010207
DSC-RSP service change response rejected multiple errors. DSC-RSP service change response rejected classifier exists. DSC-RSP service change response rejected PHS rule exists. DSC-RSP service change response rejected duplicated reference ID or index.
Warning
83010208
Warning
83010209
Warning
83010210
Warning
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
5-8 DOCSIS 1.1 Dynamic Service Events and Traps Table 5-1 (continued) DOCSIS 1.1 dynamic service events, traps, and syslog Event ID 83010211 Event Text Message DSC-RSP service change response rejected invalid parameter for context, -MAC addr: %s. Event Definition DSC-RSP service change response rejected invalid parameter for context. *Priority Warning
83010212
DSC-RSP service change DSC-RSP service change response response rejected major rejected major classifier error. classifier error, -MAC addr: %s. DSC-RSP service change response rejected major PHS rule error, -MAC addr: %s. DSC-RSP service change response rejected multiple major errors, -MAC addr; %s. DSC-RSP service change response rejected major PHS rule error. DSC-RSP service change response rejected multiple major errors.
Warning
83010213
Warning
83010214
Warning
83010215
DSC-RSP service change DSC-RSP service change response response rejected message too rejected message too big. big, -MAC addr: %s. DSC-RSP service delete DSC-RSP service delete response response rejected invalid rejected invalid transaction ID. transaction ID, -MAC addr: %s. DSA-RSP service add DSA-RSP service add response ACK response ACK rejected invalid rejected invalid transaction ID. transaction ID, -MAC addr: %s. DSA service add abort no ACK, DSA service add abort no ACK. -MAC addr: %s.
Warning
83010300
Warning
83020100
Warning
83020101 83020102
Warning
DSA service add ACK rejected DSA service add ACK rejected HMAC auth Warning HMAC auth failure, -MAC addr: failure. %s. DSA service add ACK rejected DSA service add ACK rejected message message syntax error, -MAC syntax error. addr: %s. Warning
83020103
83020200
DSC service change ACK DSC service change ACK rejected invalid Warning rejected invalid transaction ID, transaction ID. -MAC addr: %s. DSC service change aborted no ACK, -MAC addr: %s. DSC service change ACK rejected HMAC auth failure, -MAC addr: %s. DSC service change aborted no ACK. Warning
83020201 83020202
DSC service change ACK rejected HMAC Warning auth failure. Warning
83020203
DSC service change ACK DSC service change ACK rejected rejected message syntax error, message syntax error. -MAC addr: %s.
September 2003
DOCSIS 1.1 Dynamic Service Events and Traps 5-9 Table 5-1 (continued) DOCSIS 1.1 dynamic service events, traps, and syslog Event ID Event Text Message Event Definition *Priority
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
September 2003
6-1
6-
Table 6-1 lists and describes the event codes for the kernel system module generated by the CMTS 1500.
Table 6-1 Kernel system event codes Event ID 100 Event Text Message System tasking failure, TID=0x%x, status=%d, extra=%.8x Event Definition * Priority Unexpected failure of Kernel services. Emergency If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Debug
101
Error sending Intertask message System resources are back logged, CMTS is overburdened. (QID=0x%x, TID=0x%x, status=0x%x) will retry. Internal kernel failure; E_CODE 0x%0.8x: %s.
102
Unexpected failure of Kernel services. Emergency If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Debug
103
Error sending Intertask message System resources are back logged, to QID %s from TID %s. CMTS is overburdened.
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
September 2003
7-1
7-
Table 7-1 lists and describes the error codes for the event handler generated by the CMTS 1500.
Table 7-1 Event handler event codes Event ID 200 Event Text Message Unknown error. Event Definition *Priority Software error. Error If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
201
Emergency System error, EPC: %.8x, CR: System error, some sort of exception. Displayed are the EPC, cause, BadVaddr, %.8x, BadVaddr: %.8x, SR: %.8x. and status registers. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. System error, EPC: %.8x, CR: Software error. Debug %.8x, BadVaddr: %.8x, SR: If priority is emergency, or if priority is error %.8x. and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Assertion failed, file %s, line %d. Software error. Emergency If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Operator initiated actions. Operator initiated actions. Information Information
202
203
204 205
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
7-2 Event Handler Event Codes Table 7-1 (continued) Event handler event codes Event ID 206 207 Event Text Message Event reporting set to default values. Event Definition Operator initiated actions. *Priority Information
System error, ErrorEPC: %.8x, System error, some sort of exception, Emergency CacheErrReg: %.8x. further details for the 4700 processor, specifically the ErrorEPC and CacheError registers. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Reset due to watchdog timeout. Error The system was reset because the watchdog timer fired. This means the software was not operating normally. The watchdog timer should be periodically cleared to prevent this reset from occurring. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Information about a system error: calling Alert stack display, helpful for problem analysis. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Info about a system error: calling stack Alert display reached the top and further info is displayed as to whether this was a normal or unexpected termination. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
208
209
210
211
Stack frame %d, arg1: %08x, Info about a system error: called routine Alert arg2: %08x, arg3: %08x, arg4: arguments display, helpful for problem %08x. analysis. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
September 2003
Event Handler Event Codes 7-3 Table 7-1 (continued) Event handler event codes Event ID 212 214 215 Event Text Message Event Definition *Priority Event %08x, arg1: %08x, arg2: Debug information for Software Engineering Information %08x, arg3: %08x. use. Null Debug information for Software Engineering Information use.
Index %08x, 1: %08x %08x, 2: Software error. Error %08x, %08x. Debug information for Software Engineering use. 3: %08x %08x, 4: %08x %08x 5: %08x %08x. 6: %08x %08x, 7: %08x %08x 8: %08x %08x. Software error. Error Debug information for Software Engineering use. Software error. Error Debug information for Software Engineering use.
216
217
218
Index %08x, 1: %08x %08x, 2: Software error. Error %08x %08x. Debug information for Software Engineering use. 3: %08x %08x, 4: %08x %08x 5: %08x %08x. Last system reset was due to %s. Cause\t%#010x\tException # %#x [%s]. 1. AT\t%#010x\t 2. V0\t%#010x\t 3. V1\t%#010x. Software error. Error Debug information for Software Engineering use. Software error. Error Debug information for Software Engineering use. Software error. Error Debug information for Software Engineering use. Software error. Error Debug information for Software Engineering use.
219
220
221
222
223
4. A0\t%010x\t 5. A1\t%#010x\t Software error. Error 6. A2\t%#010x. Debug information for Software Engineering use. 7. A3\t%#010x\t 8. T0\t%#010x\t 9. T1\t%#010x. 10. T2\t%#010x\t11. T3\t%#010x\t12. T4\t%#010x. 13. T5\t%#010x\t14. T6\t%#010x\t15. T7\t%#010x. Software error. Error Debug information for Software Engineering use. Software error. Error Debug information for Software Engineering use. Software error. Error Debug information for Software Engineering use.
224
225
226
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
7-4 Event Handler Event Codes Table 7-1 (continued) Event handler event codes Event ID 227 Event Text Message 16. S0\t%#010x\t17. S1\t%#010x\t18. S2\t%#010x. 19. S3\t%#010x\t20. S4\t%#010x\t21. S5\t%#010x. 22. S6\t%#010x\t23. S7\t$#010x\t24. T8\t%#010x. 25. T9\t%#010x\t26. K0\t%#010x\t27. K1\t%#010x. Event Definition *Priority Software error. Error Debug information for Software Engineering use. Software error. Error Debug information for Software Engineering use. Software error. Error Debug information for Software Engineering use. Software error. Error Debug information for Software Engineering use.
228
229
230
231
28. GP\t%#010x\t29. Software error. Error SP\t%#010x\t30. FP\t%#010x. Debug information for Software Engineering use. 31. RA\t%#010x\t HI\t%#010x\t Software error. Error LO\t%#010x. Debug information for Software Engineering use. SR\t%#010x\t EPC\t%#010x. Software error. Error Debug information for Software Engineering use.
232
233
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
September 2003
8-1
8-
Table 8-1 lists and describes the error codes for the registrar module generated by the CMTS 1500.
Table 8-1 Registrar module event codes Event ID 300 Event Text Message Unable to allocate %d, file %s line %d, avail %d. Event Definition *Priority Unable to allocate memory for initial Error ranging. Software error. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Re-starting registration for modem. Debug
301 302
Error Unable to allocate initial service Unable to allocate initial service ID for ID for modem %.1211x. modem. Software error. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Ranging retries exceeded for modem %.1211x. Invalid ranging request received from modem %.1211x. Ranging timed out for modem %.1211x. Invalid registration request received from modem %.1211x. Ranging entries exceeded for modem. Invalid ranging request received from modem. Ranging timed out for modem. Invalid registration request received from modem. Debug Debug
303 304
305 306
Debug Debug
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
8-2 Registrar Module Event Codes Table 8-1 (continued) Registrar module event codes Event ID 307 Event Text Message Registration request from modem %.1211x did not have IP TLV 12. Registration request from modem %.1211x did not have IP TLV 12 or 20. Unable to unpack registration TLV data from modem %.1211x. Modem %.1211x already registered as SID 0x%0x. Registration request from modem %.1211x failed validation. Unable to allocate SID for modem %.1211x. Event Definition Registration request from modem did not have modem IP address TLV (12). *Priority Information
308
Registration request from modem did not Warning have modem IP address TLV (12) or TFTP server provisioned modem address (20) so IP address 0.0.0.0 was assigned. Unable to unpack the TLV data in the Debug registration request received from modem. Modem is already registered as another SID. Registration request data in error, failed validation test. Warning Warning
309
310 311
312
Registration request failed because no SID Error was available. Software error. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Invalid or inconsistent registration request TLVs received from modem. Registration reports failure to register a modem. Registration timed out for modem. Registration reports information. Warning Warning Warning Warning Warning
Invalid registration TLV data from modem %.1211x. Registration error, modem %.1211x: %s. Registration timed out for modem %.1211x. Registration error: %s.
REG-NACK received from Registration reports modem sent modem %.1211x, confirmation REG-NACK. code: 0d%d. Registration info: %s. Registration info: %s. Registration rejected authentication failure: TFTP server timestamp invalid %.1211x. Initial available memory %d. Registration reports information. Registration reports information.
Information Debug
321
Debug
September 2003
Registrar Module Event Codes 8-3 Table 8-1 (continued) Registrar module event codes Event ID 322 Event Text Message Registration rejected authentication failure: TFTP Server Timestamp invalid %.12llx Event Definition *Priority Registration rejected authentication failure: warning TFTP Server Timestamp invalid
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
September 2003
9-1
9-
Table 9-1 lists and describes the error codes for the spanning tree module generated by the CMTS 1500.
Table 9-1 Spanning tree event codes Event ID 500 Event Text Message Unexpected spanning tree packet format received. Event Definition External event to CMTS illegal. *Priority Warning
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
September 2003
10-1
10-
*Priority
Internal inconsistency in upstream Emergency scheduler due to CMTS malfunction. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Downstream transmitter hang reported by Emergency scheduler. CMTS is reset to clear transmitter problem. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Invalid nominal grant/polling interval. Warning
601
603
Invalid nominal grant/polling interval %d received from SID %d IUC = %d. Maximum CBR flows exhausted on channel %d (channel flows = %d, system flows = %d).
604
Warning
605 606
No resources to reserve No resources to reserve maintenance IUC. Warning maintenance IUC from SID %d. Reserved event being canceled with invalid %s (0x%x) for SID %d. Reserved event being canceled with invalid Warning control information.
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
10-2 Allocator Event Codes Table 10-1 (continued) Allocator event codes Event ID 607 Event Text Message Scheduled event being canceled with invalid %s (0x%x) for SID %d. Event Definition *Priority Reserved event being canceled with invalid Warning control information. Warning
608
Disabling SID %d that was not Disabling SID that was not admitted or admitted or active (schedule = active. %d state = %d). Disabling SID %d with schedule = %d not supported
609 610
Disabling SID %d that was not Disabling SID that was not admitted or admitted or active (schedule = active. %d state = %d). Enabling SID %d with schedule Enabling SID with schedule not supported. not supported = %d not supported. Memory resource error while admitting service flow on channel %d. Service flow SID = %d (0x%x) on channel %d could not be realigned Admit flow (sid = %d) denied %s. Memory resource error while admitting service flow. Service flow could not be realigned.
611
Warning
612
Warning
613
Warning
Activate flow (sid = Td) denied Activate service flow denied. %s. %s is not supported. Corruption in allocators %s (sid = %d) found. Requested action is not supported.
Memory corruption found by allocator. Emergency If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Allocator destroyed service flow due to upstream channel change. Information
618
619
Allocator could not send Allocator could not send message to message to CMTS manager to cmtsmgr to destroy sid. destroy sid %d.
Information
September 2003
Allocator Event Codes 10-3 Table 10-1 (continued) Allocator event codes Event ID 620 Event Text Message Tried to build MAP with too many elements - %s. Event Definition *Priority Too many information elements were Error scheduled for a MAP. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Debug information for Software Engineering Debug use. Debug information for Software Engineering Debug use.
621
Al debug1:sid = %d, iuc = %d, event_class = %d, channel_id = %d. Al debug2: desired_slot=%d, next_slot_occurrence=0x%x, next_map_is_effective_at=0x %x\n. Al debug3:am->starts_at = 0x%x requested-start = 0x%x\n. Al debug4:channel %d mapped_slots = %d\n. Al debug5:am->duration (0x%x) < requested (0x%x) starts_at=0x%x, requested=0x%x\n.
622
623
Debug information for Software Engineering Debug use. Debug information for Software Engineering Debug use. Debug information for Software Engineering Debug use.
624 625
626
Al debug6:SF Ehdr with active Debug information for Software Engineering Debug grants (%d) when UGS flow use. (%d) inactive \n. Al debug7:Sid = %d (0x%x), Debug information for Software Engineering Debug channel = %d, active grants = use. %d, active.grants_per_interval = %d. Al debug8: ch = %d, reqd = Debug information for Software Engineering Debug %d, iuc = %d, sid = %d (0x%x), use. frag = %d, remaining = %d\n. Al debug9: invalid req/xmit Debug information for Software Engineering Debug policy : sid = %d (0x%x), R/T = use. 0x%x\n. Al debug10:next_slot_abs = 0x%x, next_map_is_effective_at = 0x%x\n. Change admitted flow (sid = %d) denied %s. Debug information for Software Engineering Debug use.
627
628
629
630
631
Information
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
10-4 Allocator Event Codes Table 10-1 (continued) Allocator event codes Event ID 633 634 Event Text Message Change active flow (sid = %d) denied %s. Service flow rejected, cannot block conflicting bandwidth_id = %d sid = %d)\n. Event Definition *Priority Service flow rejected because bandwidth is Information fragmented. Service flow rejected because conflicting bandwidth cannot be blocked. Information
635
Al debug generic:%s (sid = %d, Allocator generic debug message. A = %d, B = %d)\n.
Information
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
September 2003
11-1
CMTS Headend Data Path Event Codes11CMTS headend data path module
Table 11-1 lists and describes the error codes for the CMTS headend data path module generated by the CMTS 1500.
Table 11-1 CMTS headend data path event codes Event ID 700 Event Text Message %.20s Initialization Mismatched Buffer Counts : Rx DES COUNT = %d, DP buffer count = %d. Event Definition *Priority Initialization mismatched buffer counts. Error If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
701 702
IP %d.%d.%d.%d, moved from IP address moved from MAC address ... to Warning MAC %A to MAC %A. MAC address ... MAC %A moved from port %d and said %d to port %d and said %d. %.3s address hash table resource exhausted. %.3s address hash table lookup failed. MAC address moved from port and said to Warning port and said. Address hash table resource exhausted. Debug
703 704
Error Address hash table lookup failed. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Data path received an invalid MAC header. External event to CMTS illegal. Warning
705
Data Path received invalid %s in MAC Header = %.2x %.2x %.2x %.2x.
706
Data Path received Extended Data path received extended header that Header (%.2x %.2x %.2x %.2x) is not supported. not supported. External event to CMTS illegal. Data Path received invalid or Data path received invalid extended not supported EHDR (mac hdr header. = %.8x). External event to CMTS illegal.
Warning
707
Warning
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
11-2 CMTS Headend Data Path Event Codes Table 11-1 (continued) CMTS headend data path event codes Event ID 708 Event Text Message MAC Address, %A, was not found when DP was informed of CM's %s. DP MTD found null buffer address in %s tx_desc_get = 0x%x, tx_desc_put = 0x%x, tx_desc_start = 0x%x\n. Ehdr hdr = %.8x %.8x %.8x %.8x %.8x %.8x %.8x. Ehdr hdr + 28 = %.8x %.8x %.8x %.8x %.8x %.8x %.8x. Ehdr hdr + 56 = %.8x %.8x %.8x %.8x %.8x %.8x %.8x. Ehdr hdr + 84 = %.8x %.8x %.8x %.8x %.8x %.8x %.8x. Event Definition *Priority MAC address was not found when DP was Warning informed of CMs registration/inoperability. DP MTD found null buffer address in enet_tx_desc_get or mac_tx_desc_get. Debug
709
710
Data path received invalid extended header. External event to CMTS illegal. Data path received invalid extended header. External event to CMTS illegal. Data path received invalid extended header. External event to CMTS illegal. Data path received invalid extended header. External event to CMTS illegal.
Warning
711
Warning
712
Warning
713
Warning
DP MTD occurred on %s DP MTD occurred debug message. interface tx_desc_get = 0x%x. DP MTD tx_desc_put = 0x%x, tx_desc_start = 0x%x. DP MTD occurred debug message#2.
DP MTD status = 0x%x, Debug information for Software max_tick = %d, hit_count = %d. Engineering use. DP DHCP Trace encountered error: invalid ethernet length = 0x%x. DP DHCP Trace encountered error: invalid ethernet length. External event to CMTS illegal.
718
%s Rx descriptor received with CATV/Ethernet Rx descriptor received FIRST + LAST not set (status = with FIRST + LAST not set. 0x%x). RX buffer written beyond buffer CATV/Ethernet Rx descriptor received (status = 0x%x). with FIRST + LAST not set. (%.8x %.8x %.8x %.8x %.8x %.8x %.8x %.8x). (%.8x %.8x %.8x %.8x %.8x %.8x %.8x %.8x). DP ENET MTD caused by %s error. %d packets stranded. Dump data. Dump data. DP MTD occurred debug message#4
Debug
DP MTD status = 0x%x, DP MTD occurred debug message#5 max_tick = %d, hit_count = %d.
September 2003
CMTS Headend Data Path Event Codes 11-3 Table 11-1 (continued) CMTS headend data path event codes Event ID 724 Event Text Message DP CATV concatenation header packet with no prepended data. DP CATV packet with bad prepended data. Event Definition DP CATV concatenation packet received with no prepended data. External event to CMTS illegal. DP CATV packet received with bad prepended data. External event to CMTS illegal. *Priority Warning
725
Warning
726
Data path resources Data path resources exhausted; cannot Error exhausted, cannot link CPEs to link CPEs to CM. CM. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. DP FDB corruption avoided %s. DP received packet from channel %d. CATV concatenated packet with no concatenated header. CATV concatenated packet with no prepended data. DP DHCP trace encountered error %d. DP null buffer freed by 0x%x. DP forwarding database corruption avoided at specified location. DP CATV channel number of received packet was bad. CATV: concatenation header packet without concat bit in MAC header. External event to CMTS illegal. CATV: concatenation header packet without prepended data. External event to CMTS illegal. DP DHCP trace encountered error: bad DHCP packet. Debug Error Error
730
Error
731 732
Debug
DP null buffer freeing encountered. Error If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
733
DP buffer freed twice by 0x%x. DP buffer freed twice encountered. Error If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
11-4 CMTS Headend Data Path Event Codes Table 11-1 (continued) CMTS headend data path event codes Event ID 734 Event Text Message DP FDB time-to-live list: no such %s. Event Definition *Priority DP forwarding database ttl list has no such Error entry. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Address hash table resource exhausted for CMs. Address hash table resource exhausted for non-CMs. ARP spoofing IP address stolen ARP spoofing IP address stolen ARP spoofing IP address stolen DP reassembled packet exceeds allocated buffer. Debug Debug
735 736
%.3s address hash table resource exhausted for CMs. %.3s address hash table resource exhausted for non-Cms. ARP spoof prevented %A %d.%d.%d.%d -> %d.%d.%d.%d. ARP spoof occurred %A %d.%d.%d.%d -> %d.%d.%d.%d. IP %d.%d.%d.%d, not moved from %A to %A. DP reassembled packet exceeds allocated buffer %d bytes (sid=%d).
737
Warning
738
Warning
739 750
Warning Information
751 752
DP reassembled buffer too big DP reassembled buffer too big. %d bytes (sid=%d).
Warning
DP embedded deconcatenated DP embedded deconcatenated packet too Warning packet too big %d bytes big. (sid=%d). DP total defragmented packet too small %d bytes (sid=%d). DP defragmented deconcatenated packet error (sid=%d). DP total defragmented packet too small. Warning
753 754
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
September 2003
12-1
12-
Table 12-1 lists and describes the error codes for the system manager module generated by the CMTS 1500.
Table 12-1 System manager event codes Event ID 800 Event Text Message System Manager reports fatal error: %s. Contact Customer Support. Event Definition *Priority System Manager fatal error is reported. Emergency If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. System Manager debug information is reported. Debug
801 802
Error SM_malloc () failure, size = %x, System Manager reports: SM_alloc() status = %d. memory allocation failed. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. SM_free () failure, address = %x. System Manager reports: SM_free() Error memory release failed. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Information Warning
803
804 805
Restart, system software build System Manager reports: Restart. time: %d. Device temperature exceeded threshold of %d degrees celsius. Device Temperature Exceeded Specified Temperature Threshold.
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
12-2 System Manager Events Table 12-1 (continued) System manager event codes Event ID 806 807 808 809 810 811 Event Text Message CPU speed detected to be: %d\n. Time server not specified in DHCP offer. Event Definition CPU speed detected to be: (speed in Hz). Time server not specified in DHCP offer. *Priority Information Warning Information Information Warning
Time server specified in DHCP Time server specified in DHCP offer. offer. Time server contacted. Time server not contacted. Bad trap type (%d). Time server contacted. Time server not contacted.
Error A trap was requested specifying an unknown trap type. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Error Error creating trap packet for a particular trap type. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. System Manager reports: Error processing a provisioned SNMP object Information
812
813 814
SNMP provisioning error, object OID = %s. DHCP offer from %d.%d.%d.%d ignored; missing yiaddr, siaddr, or filename.
A DHCP offer was received which is Warning unacceptable because it lacks either yiaddr, siaddr, or filename. The filename is always needed at the CM; it appears at the CMTS only if TFTP provisioning is required. Warning
815
DHCP offer from A DHCP offer was received which is %d.%d.%d.%d ignored; unacceptable because it lacks an option missing required field tag = %d. required by the device. The tag is from RFC2132. DHCP offer from A DHCP offer was received which lacks a %d.%d.%d.%d missing default gateway address. gateway.
816
Warning
817
ICMP error received on time An ICMP message (probably destination Warning server query to %d.%d.%d.%d. unreachable) was received when attempting to query the time server.
September 2003
System Manager Events 12-3 Table 12-1 (continued) System manager event codes Event ID 819 Event Text Message SNMP provisioning error: %s. Event Definition *Priority System Manager reports: Error processing Error a provisioned SNMP object. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. System Manager reports information. Information
820 821
TFTP provisioning file %s is too TFTP get of Provisioning file failed because Error large. the file size received exceeds the receive buffer size. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. DHCP: NAK from server %d.%d.%d.%d. DHCP: Incomplete offer from %d.%d.%d.%d ignored. DHCP received a NAK from the server and Information the offer is rejected. Information The DHCP offer from the specified server does not have all required fields and is being ignored. A previous log entry will have the specific error describing which entry was missing.
822 823
824 825
DHCP: No valid offer received. DHCP discover received no offers or offers Warning that were silently ignored. DHCP: Declined offer from %d.%d.%d.%d, duplicate IP. No IP address, BOOTP Relay cannot work. IP address assigned, BOOTP Relay functional. Old time = %04d/%02d/%02d %02d:%02d, new time = %04d/%02d/%02d %02d:%02d:%02d. Error (%d) adding route entry for provisioned gateway %a. This %d.%d.%d.%d has no SNMP access to this CMTS. DHCP offer declined because it contained an IP address that is in use by another station. Information
826
No IP address is assigned so BOOTP Relay Warning functionality cannot work. This means that CMs behind this CMTS will not register. IP address is assigned so BOOTP Relay functionality can now work. Time server contacted for sync. Warning Information
827 828
829 830
Error adding route entry for provisioned gateway. Not an authorized NM IP address for the CMTS.
Warning Information
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
12-4 System Manager Events Table 12-1 (continued) System manager event codes Event ID 831 832 833 834 835 Event Text Message Event Definition *Priority This %d.%d.%d.%d community No matching community NM read access for Information <%s> has no read access. this CMTS. This %d.%d.%d.%d community No matching community NM write access <%s> has no write access. for this CMTS. This %d.%d.%d.%d has no read access to the CMTS. This %d.%d.%d.%d has no write access to the CMTS. No authorized NM read access for the CMTS. No authorized NM write access for the CMTS. Information Information Information Information
This %d.%d.%d.%d has no No authorized ethernet interface NM read ethernet interface read access access to this CMTS. to this CMTS. This %d.%d.%d.%d has no cable interface read access to this CMTS. No authorized cable interface NM read access to this CMTS.
836
Information
837
This %d.%d.%d.%d has no No authorized ethernet interface NM write ethernet interface write access access to this CMTS. to this CMTS. This %d.%d.%d.%d has no No authorized cable interface NM write cable interface write access to access to this CMTS. this CMTS.
Information
838
Information
839
DHCP provisioned DNS server DHCP provisioning contained a DNS server Warning list was invalid or list that was invalid or due to a bad list corrupt--ignoring bad list length; the invalid list will be ignored. List was %d. DHCP provisioned DNS default DHCP provisioning contained a DNS default Warning domain name was invalid or domain name that was invalid or corrupt due corrupt--ignoring bad name to a bad string length; the invalid name will be ignored. Name length was %d. System memory %xh below minimum %xh. DHCP (callback) handler received an illegal, default event Event code was %d. System Manager reports supplemental debug information: %s: %d, %s: 0x%08x, %s: %a, %s. Cannot allocate memory for coex. tables during the initialization. System memory below minimum. The DHCP callback handler received an illegal event. Warning Warning
840
841 850
851
Debug
852
Error
September 2003
System Manager Events 12-5 Table 12-1 (continued) System manager event codes Event ID Event Text Message Event Definition *Priority
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
September 2003
13-1
13-
Table 13-1 lists and describes the error codes for the PHY operations module generated by the CMTS 1500.
Table 13-1 PHY operations event codes Event ID 1100 1101 1102 1103 1104 1105 Event Text Message PHY module reports %s. PHY module: Main PHY connection operational at %s. PHY module: Aux PHY connection operational at %s. PHY module: Main PHY connection link lost. PHY module: Aux PHY connection link lost. Event Definition PHY module reports debug information. *Priority Debug
PHY module reports Main PHY connection Information operational. PHY module reports Aux PHY connection Information operational. PHY module reports Main PHY link lost. PHY module reports Aux PHY link lost. Information Information Information
PHY module: Main PHY ping PHY module reports Main ping polling polling of %s failed, switching to failed. Aux. PHY module: Aux PHY ping PHY module reports Aux ping polling polling of %s failed, switching to failed. Main. PHY module: Main PHY PHY module reports Main PHY administrator state changed to administrator state changed. %s. PHY module: Aux PHY PHY module reports Aux PHY administrator state changed to administrator state changed. %s. PHY module: Main PHY sending Topology Change Notice (TCN)> PHY module reports Main PHY sending topology change notice.
1106
Information
1107
Information
1108
Information
1109
Information
1110
PHY module: Aux PHY sending PHY module reports Aux PHY sending Topology Change Notice topology change notice. (TCN).
Information
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
13-2 PHY Operations Events Table 13-1 (continued) PHY operations event codes Event ID 1111 1112 Event Text Message Event Definition *Priority Information Information PHY module: DHCP failure on PHY module reports Main PHY Main PHY connection. connection. PHY module: DHCP failure on PHY module reports Aux PHY DHCP Aux PHY connection. failure.
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
September 2003
14-1
14-
Table 14-1 lists and describes the error codes for the lter module generated by the CMTS 1500.
Table 14-1 Filter event codes Event ID 1200 Event Text Message Filter module reports %s. Event Definition *Priority Filter module reports debug information. Debug If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Filter module reports an invalid flash value Error was read. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Error attempting to remove IP table entry Error which is not active. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
1201
1202
1203
Error attempting to remove LLC Error attempting to remove LLC table entry Error table entry which is not active. which is not active. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
14-2 Filter Module Events Table 14-1 (continued) Filter event codes Event ID 1204 Event Text Message Filter module reports %s. Event Definition *Priority Filter module reports information. Information If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. IGMP reports multicast filter table full. Error If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
1205
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
September 2003
15-1
15-
Table 15-1 lists and describes the error codes for the system upgrade event module generated by the CMTS 1500.
Table 15-1 System upgrade event codes Event ID 1300 1301 Event Text Message Software upgrade reports %s. Software upgrade failed %s. Event Definition Software upgrade reports information. *Priority Information
Software upgrade failure notice. Error If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Software upgrade failure occurred Emergency resulting in a reset. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Software upgrade succeeded. Software upgrade was canceled. Information Information
1302
Software upgrade canceled by Software upgrade was canceled by a new Information new request. request. Software upgrade flash programming failure, %s. Software upgrade flash programming Error failure. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
15-2 System Upgrade Events Table 15-1 (continued) System upgrade event codes Event ID 1307 Event Text Message Software upgrade flash programming failure, %s. Event Definition *Priority Software upgrade flash programming Emergency failure resulting in a reset. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Software upgrade flash erase failure. Error
1308 1309
Software upgrade flash erase failure, %s. Software upgrade flash erase failure resulting in a reset.
Software upgrade flash erase failure Emergency resulting in a reset. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Emergency Software upgrade; unknown flash. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
1310
1311
Software upgrade: Invalid flash Software upgrade; invalid flash runtime Error runtime info block. info block. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Software upgrade failed, TFTP Software upgrade failed, tftp error reset. error = %d, packet_count = %d, abort upgrade. Software upgrade failed, TFTP Software upgrade failed due to a TFTP error = %d, packet_count = %d, error, system is reset to retry. reset to retry. Software upgrade NU_Alloc_Memory failure, error = %d. Information
1312
1313
Information
1314
Software upgrade NU_Alloc_Memory Error failure. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
September 2003
System Upgrade Events 15-3 Table 15-1 (continued) System upgrade event codes Event ID 1315 Event Text Message Software upgrade error: %s. Event Definition *Priority Software upgrade error reported. Error If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. The product code in the software upgrade Error file is not correct for the system being upgraded. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Error There was a TFTP error during the software upgrade. Possible errors are that the upgrade file does not exist, the docsDevSwServer address is not correct, or the transfer failed in the middle of the transfer. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
1316
1317
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
September 2003
16-1
Console interface command: %s. User %s on console set MIB item: %s.
User %s from remote session Remote session interface user snmp set. %s set MIB item: %s.
Error NU_Allocate_Memory failure in Software error. MIB search, status = %d. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. NU_Deallocate_Memory failure in MIB search, status = %d. Error Software error. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Console interface user logged in. Remote session 1 user is logged in. Information Information
1509
1510 1511
Console interface user %s logged in from %s. Remote session 1 user %s logged in from %s.
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
16-2 Command Line Interface (CLI) Events Table 16-1 (continued) CLI event codes Event ID 1512 1513 1514 1515 1516 1520 1521 1522 1523 1524 1525 1526 1530 1531 1532 1533 1534 1535 1540 1541 Event Text Message Remote session 2 user %s logged in from %s . Remote session 3 user %s logged in from %s. Remote session 4 user %s logged in from %s. Remote session 5 user %s logged in from %s. SSH session %d user %s logged in from %s Console interface user %s from %s logged out. Remote session 1 user %s from %s logged out. Remote session 2 user %s from %s logged out. Remote session 3 user %s from %s logged out. Remote session 4 user %s from %s logged out. Remote session 5 user %s from %s logged out. SSH session %d user %s logged out from %s Console interface user %s login failed from %s . Remote session 1 user %s login failed from %s . Remote session 2 user %s login failed from %s . Remote session 3 user %s login failed from %s. Remote session 4 user %s login failed from %s . Remote session 5 user %s login failed from %s . Console Interface user %s timed out. Remote session 1 user %s timed out. Event Definition Remote session 2 user is logged in. Remote session 3 user is logged in. Remote session 4 user is logged in. Remote session 5 user is logged in. SSH session is logged in. Console interface user logged out. Remote session 1 user logged out. Remote session 2 user logged out. Remote session 3 user logged out. Remote session 4 user logged out. Remote session 5 user logged out. SSH session is logged out. Console interface user login fail. Remote session 1 user login fail. Remote session 2 login fail. Remote session 3 login fail. Remote session 4 login fail. Remote session 5 login fail. Console interface user timed out. Remote session 1 user timed out. *Priority Information Information Information Information Information Information Information Information Information Information Information Information Information Information Information Information Information Information Information Information
September 2003
Command Line Interface (CLI) Events 16-3 Table 16-1 (continued) CLI event codes Event ID 1542 1543 1544 1545 1550 1551 1552 1553 1554 1555 Event Text Message Remote session 2 user %s timed out. Remote session 3 user %s timed out. Remote session 4 user %s timed out. Remote session 5 user %s timed out. Console interface timed out while login attempt as %s . Remote session 1 timed out while login attempt as %s . Remote session 2 timed out while login attempt as %s . Remote session 3 timed out while login attempt as %s . Remote session 4 timed out while login attempt as %s . Remote session 5 timed out while login attempt as %s . Event Definition Remote session 2 user timed out. Remote session 3 user timed out. Remote session 4 user timed out. Remote session 5 user timed out. *Priority Information Information Information Information
Console interface login attempt timed out. Information Remote session 1 login attempt timed out. Information Remote session 2 login attempt timed out. Information Remote session 3 login attempt timed out. Information Remote session 4 login attempt timed out. Information Remote session 5 login attempt timed out. Information
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
September 2003
17-1
17-
Table 17-1 lists and describes the error codes for the broadcom driver module generated by the CMTS 1500.
Table 17-1 Broadcom driver event codes Event ID 1600 Event Text Message Could not initialize network interface parts. Event Definition *Priority Could not initialize network interface parts. Error If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. The receiver has an improper hardware Error revision. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
1602
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
September 2003
18-1
18-
Table 18-1 lists and describes the error codes for the SNMP initiated reset event module using the docsDevResetNow MIB variable generated by the CMTS 1500.
Table 18-1 SNMP initiated reset event codes Event ID 1800 Event Text Message System reset by docsDevResetNow MIB var. Event Definition The system has been reset by the docsDevResetNow MIB variable. *Priority Warning
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
September 2003
19-1
Galileo Events
Galileo event module
19-
Table 19-1 lists and describes the error codes for the Galileo event module generated by the CMTS 1500.
Table 19-1 Galileo event codes Event ID 1900 Event Text Message PCI parity error detected, cause register 0x%x. Event Definition *Priority PCI parity error detected. Emergency If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
September 2003
20-1
2101
2102
2103
2104
BPKM SA MAC does not match The source MAC address of a BP Key Error CM MAC (SA=%s CM management message is not equivalent to MAC=%s) the MAC address passed in the messages CM identification field. New public key in BPKM Auth Req (SA=%s CM MAC=%s) A CM has made a BP Authorization request Warning but a CM with the same MAC address, and different public key, is already authorized.
2105
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
20-2 CMTS Baseline Privacy Event Codes Table 20-1 (continued) CMTS baseline privacy event codes Event ID Event Text Message Event Definition *Priority
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
September 2003
21-1
21-
Table 21-1 lists and describes the error codes for the CMTS Cruiser driver module generated by the CMTS 1500.
Table 21-1 CMTS cruiser driver event codes Event ID 2200 Event Text Message Event Definition *Priority CMTS hardware initialization The CMTS hardware could not be Error failure: FPGA not programmed initialized due to an FPGA programming failure. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
September 2003
22-1
22-
Table 22-1 lists and describes the error codes for the CMTS manufacturing module generated by the CMTS 1500.
Table 22-1 Manufacturing event codes Event ID 2300 Event Text Message MFG flash module: error reading TLV type 0x%x from flash Event Definition *Priority Error reading TLV from flash. Debug If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
September 2003
23-1
23-
*Priority
CMTS hardware initialization The CMTS hardware could not be Error failure: up-converter inoperable initialized because the up-converter was not detected. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. CMTS hardware initialization failure: up-converter not calibrated Error The CMTS hardware could not be initialized because the up-converter calibration data could not be found. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. The CMTS hardware could not lock onto Error the downstream frequency. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
2401
2402
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
23-2 UC (Sunset Up-Converter) Event Codes Table 23-1 (continued) UC (Sunset Up-Converter) event codes Event ID 2403 Event Text Message CMTS hardware failure: up-converter %s V power supply failed Event Definition *Priority The CMTS up-converter power supply Error failed. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. The CMTS downstream output power could Error not reach the desired level. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
2404
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
September 2003
24-1
24-
Table 24-1 lists and describes the error codes for the CMTS Pacer module generated by the CMTS 1500.
Table 24-1 CMTS Pacer event codes Event ID 2500 Event Text Message The downstream channel configuration is incompatible with the CMTS hardware; the downstream channel is disabled The upstream channel configuration for channel %d is incompatible with the CMTS hardware; the upstream channel is disabled The Downstream Center Frequency has been changed to %d Event Definition *Priority If priority is emergency, or if priority is error Error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. If priority is emergency, or if priority is error Error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. If priority is emergency, or if priority is error Information and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. If priority is emergency, or if priority is error Information and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. If priority is emergency, or if priority is error Information and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
2501
2502
2503
2504
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
24-2 CMTS Pacer Event Codes Table 24-1 (continued) CMTS Pacer event codes Event ID 2505 Event Text Message The Downstream Interleave has been changed to index %d Event Definition *Priority If priority is emergency, or if priority is error Information and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
2506
The Downstream Channel Power If priority is emergency, or if priority is error Information has been changed to %d and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. The Downstream FEC Annex type If priority is emergency, or if priority is error Information has been changed to %s and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. The Frequency Split has been changed to %s If priority is emergency, or if priority is error Information and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
2507
2508
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
September 2003
25-1
25-
Table 25-1 lists and describes the error codes for the Testing module generated by the CMTS 1500.
Table 25-1 Testing event codes Event ID 2600 Event Text Message Test being run - MAC Header Event Definition Test ID = %s, MAC Header = 0x%02x 0x%02x 0x%02x 0x%02x. Debug information for Software Engineering use. *Priority Debug
2601
Test being run - Extended header EHDR = 0x%02x 0x%02x 0x%02x 0x%02x Debug 0x%02x 0x%02x 0x%02x 0x%02x 0x%02x 0x%02x 0x%02x 0x%02x 0x%02x 0x%02x 0x%02x 0x%02x 0x%02x 0x%02x 0x%02x 0x%02x. Debug information for Software Engineering use.
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
September 2003
26-1
26-
Table 26-1 lists and describes the error codes for the Ingress Avoidance module generated by the CMTS 1500.
Table 26-1 Ingress Avoidance event codes Event ID 2700 Event Text Message Ingress avoidance feature has automatically changed frequency, modulation profile and bandwidth Event Definition Ingress Avoidance change Upstream %d, Freq %d Hz, Mod Profile %d, BW %d Hz *Priority Information
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
September 2003
27-1
27-
Table 27-1 lists and describes the error codes for the CMTS fans module generated by the CMTS 1500.
Table 27-1 CMTS fans event codes Event ID 2800 2801 2802 2803 2804 2805 Event Text Message Front fan is off Front fan is on Middle fan is off Middle fan is on Back fan is off Back fan is on Event Definition Front fan is not functioning properly or is powered down Front fan is now functioning properly Middle fan is not functioning properly or is powered down Middle fan is now functioning properly Back fan is not functioning properly or is powered down Back fan is now functioning properly *Priority Warning Warning Warning Warning Warning Warning
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
September 2003
28-1
28-
Table 28-1 lists and describes the error codes for the CMTS multi-session module generated by the CMTS 1500.
Table 28-1 CMTS multi-session event codes Event ID 3000 Event Text Message Event Definition *Priority Telnet reports: TELNET_malloc() TELNET_malloc() failure, size _ %x, status Error memory allocation failed = %d. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Telnet reports: TELNET_free() memory release failed TELNET_free() failure, address - %x. Error If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. TELNET_Init() failure, tcb_create() failed. Error If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. TELNET_Init() failure, tn_create_listener () Error failed. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
3001
3002
3003
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
28-2 CMTS Multi-Session Event Codes Table 28-1 (continued) CMTS multi-session event codes Event ID 3004 Event Text Message Telnet reports: TELNET_Init() tcp_start () failed Event Definition *Priority TELNET_Init() failure, tcp_start () failed Error with error code = %d. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
September 2003
29-1
29-
Table 29-1 lists and describes the error codes for the QoS module generated by the CMTS 1500.
Table 29-1 QoS event codes Event ID 3100 3101 Event Text Message Qos driver dropping packet - no descriptors available QoS driver not running due to lack of system memory Event Definition *Priority QoS driver dropping packet - no descriptors Warning available. QoS driver not running due to lack of Error system memory. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. QoS driver dropping packet due to invalid Emergency HFID or state. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Warning QoS hardware missing. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. The QoS timer failed to initialize correctly. Emergency If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
3102
3103
3104
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
29-2 QoS Event Codes Table 29-1 (continued) QoS event codes Event ID 3105 Event Text Message Event Definition *Priority Haulback reset due to excessive The Haulback queue overflowed. Error queue backup. QD_pktCnt = %d Capture the event log and console output, and contact Customer Service.
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
September 2003
30-1
Service Flow Mgr error, %s %d, station_id Information = %A. Service Flow Mgr error, %s, station_id= %A. Service Flow Manager error, %s, %d, reason = 0x%x. Service Flow Mgr: %s, station_id= %A. Service Flow Manager, %s, %d. Warning Warning Information Warning
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
30-2 Service Flow Manager Task Event Codes Table 30-1 (continued) Service flow manager task event codes Event ID Event Text Message Event Definition Priority
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
September 2003
31-1
31-
Table 31-1 lists and describes the error codes for the domain name service event module generated by the CMTS 1500.
Table 31-1 Domain name service event codes Event ID 3300 Event Text Message DNS_malloc failed to allocate a %d byte buffer Error code was: 0x%08X Event Definition *Priority The DNS_malloc function failed to allocate Error a buffer. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. The DNS_free function failed to de-allocate Error a buffer. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
3301
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
September 2003
32-1
QP Event Codes
QP event module
Table 32-1 lists and describes the error codes for the QP event module generated by the CMTS 1500.
Table 32-1 QP event codes Event ID 3400 3401 3402 Event Text Message QP module error, %s QP module error, modem % .1211x: %s QP module reports %s Event Definition QP module reports failure. QP module reports failure.
32-
Error QP module reports. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Error QP Module reports: QP_alloc() memory allocation failed. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
3403
3404
QP_compare ID %d Params %d QP Module reports: QP_compare failed. Error %d %d %d %d %d If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
September 2003
33-1
3501
Information
3502
Alarms LOC, threshold exceeded Alarms Loss of Comm to CM exceeded threshold, set major alarm on upstream channel %d, SET major alarm Alarms LOC, on upstream Alarms Loss of Comm to CM fails below channel %d, CLEAR major alarm threshold, clear major alarm Alarms LOC, unable to auto-provision device %A Alarms unable to auto-provision Loss of Comm to CM
Information
3503 3504
Information Information
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
September 2003
34-1
34-
Table 34-1 lists and describes the error codes for the soft watchdog timer event module generated by the CMTS 1500.
Table 34-1 Soft watchdog timer event codes Event ID 3600 Event Text Message Event Definition *Priority Information Soft watchdog: back trace of Soft watchdog: back trace of interrupted interrupted task: TID = %d: PC = task. 0x%X Debug information for Software Engineering use. Soft watchdog: System going down Soft watchdog: System going down. Debug information for Software Engineering use.
3601
Information
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
September 2003
35-1
35-
Table 35-1 lists and describes the error codes for the multi-usage upstream event module generated by the CMTS 1500.
Table 35-1 Multi-usage upstream event codes Event ID 3700 Event Text Message Multi Usage Upstream Admin Changed - %s Multi Usage Upstream Oper Status has changed. Upstream %d has failed over. Event Definition The multi-usage upstream admin has changed. The Nth upstream is no longer being used as standard upstream. The multi-usage upstream admin has changed. The Nth upstream is no longer being used as standard upstream. Priority Information
3701
Information
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
September 2003
36-1
36-
Table 36-1 lists and describes the error codes for the secure shell V1 (SSH1) event module generated by the CMTS 1500.
Table 36-1 Secure shell V1 (SSH1) event codes Event ID 4100 Event Text Message Event Definition * Priority Error The ssh_malloc function failed to ssh_malloc failed to allocate a %d byte allocate a buffer buffer Error code was: 0x%08X. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. 4101 The ssh_free function failed to de-allocate a buffer ssh_free failed to recycle the buffer @ 0x%08X. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. 4102 SSH1 reports: SSH1_Server_Init SSH1 reports: SSH1_Server_Init () () tcb_create() failed tcb_creat() failed. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. 4103 SSH1 reports: SSH1_Server_Init() ssh1_create_listener() failed SSH1 reports: SSH1_Server_Init() ssh1_create_listener() failed. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. September 2003 Error Error Error
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
36-2 Secure Shell V1 (SSH1) Event Codes Table 36-1 (continued) Secure shell V1 (SSH1) event codes Event ID 4104 Event Text Message SSH1reports: SSH1_Server_Init() tcp_start() failed Event Definition * Priority SSH1reports: SSH1_Server_Init() Error tcp_start() failed with error code =%d. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. NET_Task() failure, queue full sending srvr Error init to SM, queue status was %d. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
4105
4110 4111
SSH1reports: buffer_bet_string() Received packet with bad string length %d. Warning got bad string length SSH reports: buffer_get() operation overflows buffer limits buffer_get() trying to get more bytes (%d) Error than buffer describes (%d - %d). If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
4112
SSH1 reports: buffer_consume() buffer_consume() trying to consume more Error operation overflows buffer limits bytes (%d) than buffer describes (%d - %d). If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. SSH1 reports: buffer consume_end() operation overflows buffer limits buffer_consume_end(s) trying to consume Error more bytes (%d) than buffer describes (%d - %d). If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
4113
September 2003
Secure Shell V1 (SSH1) Event Codes 36-3 Table 36-1 (continued) Secure shell V1 (SSH1) event codes Event ID 4115 Event Text Message SSH1 reports: cipher_name(): bad cipher number Event Definition * Priority cipher_name(): bad cipher number: %d. Error If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. cipher_number(): Arcfour cipher disabled, Information using blowfish cipher instead. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Error cipher_set_key() : Key length %d is insufficient for IDEA. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
4116
4117
SSH1 reports: SSH1 reports: cipher_set_key() : Key length insufficient for IDEA
4118
Error SSH1 reports: cipher_set_key(): cipher_set_key(): Key length %d is Key length insufficient for DES insufficient for DES. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. SSH1 reports: cipher_set_key(): cipher_set_key(): Key length insufficient Error Key length insufficient for 3DES for3 DES. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. SSH1 reports: cipher_set_key(): cipher_set_key(): Key length insufficient for Error Key length insufficient for blowfish. blowfish If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
4119
4120
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
36-4 Secure Shell V1 (SSH1) Event Codes Table 36-1 (continued) Secure shell V1 (SSH1) event codes Event ID 4121 Event Text Message SSH1 reports: Unknown cipher type Event Definition * Priority Unknown cipher type %d. Error If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. SSH1 Packet Too Large, size - %d. Error If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
4125
4130
SSH1 reports: ssh1_bsafe_init() : SSH1 BSAFE Init error: BSAFE error #%d Error Error initializing BSAFE and calling %s. random number data If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. SSH1 reports: ssh1_decrypt_data(): Error decrypting RSA-encoded data Error SSH1 RSA data decryption error: BSAF error #%d calling %s. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. SSH! Create Check Bytes error: BSAFE Error error #%d calling %s. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. SSH! RSA Key Generation error: BSAFE Error error #%d calling %s. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
4131
4132
4133
September 2003
Secure Shell V1 (SSH1) Event Codes 36-5 Table 36-1 (continued) Secure shell V1 (SSH1) event codes Event ID 4134 Event Text Message SSH1 reports: get_rsa_key_data() : Error getting RSA key data Event Definition * Priority SSH! Get RSA Key Data error : BSAFE Error error #%d calling %s. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. SSH1 Check Emulation error: Unexpected Error return value from check_emulation. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Error SSH1 Receive Session Key error: Unexpected message type, code %d. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. SSH1 Receive Session Key error: IP Error Spoofing check bytes do not match. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. SSH1 Receive Session Key error: Session Error key has invalid length. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
4135
4146
4147
4148
4149
SSH1 reports: SSH1 Receive Session Key error: Encoded Error ssh1_recv_sesskey(s): Encoded Session key is %d bytes larger than local Session key is too big largest private key. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
36-6 Secure Shell V1 (SSH1) Event Codes Table 36-1 (continued) Secure shell V1 (SSH1) event codes Event ID 4150 Event Text Message Event Definition * Priority SSH1 reports: SSH! Receive Session Key error: Could not Error ssh1_recv_sesskey(): Could not allocate Encoded copy buffer. allocate Encoded copy buffer If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. SSH1 reports: SSH1 Parse Packet Prefix error: Packet Error parse_packet_prefix(): Packet length greater than parsing buffer! %u. length greater than parsing buffer If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. SSH1 reports:SSH1 reports: parse_packet_prefix() : Bad packet length Error SSH1 Parse Packet Prefix error: Bad packet length %u. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. SSH1 Parse Packet Prefix error: Corrupted Error check bytes on input. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. SSH1 Parse Packet Prefix msg: Client disconnected: %.900s\n. SSH1 Parse Packet Prefix msg: Debug message from Remote: %.900s\n Information
4152
4153
4154
4155
SSH1 reports: parse_packet_prefix(): Client disconnected with reason text SSH1 reports: parse_packet_prefix(): Debug message from Remote SSH1 reports: ssh1_recv_username(): Unexpected message type
4156
Information
4158
SSH1 Recv Username: Unexpected Error message type, code %d. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
September 2003
Secure Shell V1 (SSH1) Event Codes 36-7 Table 36-1 (continued) Secure shell V1 (SSH1) event codes Event ID 4159 Event Text Message SSH1 reports: ssh1_recv_encrypted_msg(): Unexpected message type Event Definition * Priority SSH1 Recv Encrypted Msg: Unexpected Error message type, code %d. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
4162
SSH1 SSH1 Server_Closed Upcall: TCB = Error reports:ssh1_srvr_closed_upcall 0X%08x, REASON = %d. (): TCB closed If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. SSH1 reports: ssh1_open_upcall(): Could not allocate connection struct for TCB SSH1 Open Upcall: Could not allocate Error connection struct for TCB = 0X%08x. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. SSH1 Open Upcall: Could not setup Error connection for TCB = 0X%08x, CNX = 0X%08x. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. SSH1 Receive UPcall: Illegal Connection Error State: %d - - Aborting connection. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. SSH1 Receive Upcall: Illegal Connection Error State Action: %d - - Aborting connection. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
4164
4165
4166
4167
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
36-8 Secure Shell V1 (SSH1) Event Codes Table 36-1 (continued) Secure shell V1 (SSH1) event codes Event ID 4168 Event Text Message SSH1 reports: ssh1_receive_upcall(): ssh1_send_buffer() failed Event Definition * Priority SSH1 Receive Upcall: ssh1_send_buffer() Error failed. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
4170
SSH1 reports: SSH1 Opened Upcall: ssh1_send_buffer() Error ssh1_tcp_opened():ssh1_send_ failed. buffer() failed If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. Error SSH1 reports: SSH1 Send Buffer: Error %d calling ssh1_send_buffer(): Error calling ssh1_tcp_alloc. ssh1_tcp_alloc() If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. SSH1 reports: SSH1 Send Buffer: Error %d calling Error ssh1_send_buffer(): Error calling ssh1_tcp_write. ssh1_tcp_write() If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service.
4172
4173
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
September 2003
37-1
37-
Table 37-1 lists and describes the error codes for the dynamic service event module generated by the CMTS 1500.
Table 37-1 Dynamic service event codes Event ID 4300 Event Text Message SF Error SREF%d%d SFID %d%d param %d code %d, %s Event Definition Service Flow Error Encodings Refer to RFI Specification SP-RFIV1.1-107-010829 and DOCSIS Specification c.2.2.4. Classifier Error Encodings Refer to RFI Specification SP-RFIV1.1-107-010829 and DOCSIS Specification c.2.1.4. Service Flow Error Encodings Refer to RFI Specification SP-RFIV1.1-107-010829 and DOCSIS Specification c.2.2.4. Payload Header Suppression Error Encodings Refer to RFI Specification SP-RFIV1.1-107-010829 and DOCSIS Specification c.2.2.9. 4303 SF Error SFID %d SREF %d param %d code %d, %s External event to CMTS illegal. Service Flow Error Encodings Refer to RFI Specification SP-RFIV1.1-107-010829 and DOCSIS Specification c.2.2.4. External event to CMTS illegal. Classifier Error Encodings Refer to RFI Specification SP-RFIV1.1-107-010829 and DOCSIS Specification c.2.1.4. Debug * Priority Debug
4301
Class Err CREF %d/%d CID %d/%d SREF %d/%d SFID %d/%d param0 %d param1 %d PHS error CREF %d/%d CID %d/%d SREF %d/%d SFID %d/%d param %d code %d
Debug
4302
Debug
4304
Debug
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
37-2 Dynamic Service Event Codes Table 37-1 (continued) Dynamic service event codes Event ID 4305 Event Text Message PHS Error SFID %d SREF %d CID %d CREF %d param %d code %d, %s Event Definition External event to CMTS illegal. Payload Header Suppression Error Encodings Refer to RFI Specification SP-RFIV1.1-107-010829 and DOCSIS Specification c.2.2.9. * Priority Debug
4308
Received bad DSC-RSP from Received bad DSC-RSP MAC addr %A confirmation code %d Transmit errored DSC-ACK confirmation code %d to MAC addr %A Received bad DSC-REQ from MAC addr %A Transmit errored DSC-RSP confirmation code %d to MAC addr %A Transmit errored DSC-ACK
Debug
4309
Debug
4310 4311
Debug Debug
4312
Received not OK DSC-ACK from Received bad DSC-ACK. MAC addr %A confirmation code %D. Received transaction ID is unknown and msg is not a req msg %D. Received invalid transaction ID value for dsx message %d. Received unknown transaction ID. External event to CMTS illegal. Received invalid transaction ID value. External event to CMTS illegal.
Debug
4313
Error
4314 4315
Error Error
Received dsx message too small Received dsx message too small to hold to hold transaction ID. transaction ID. External event to CMTS illegal.
4316
DS assertion debug info, file %s, DS assertion debug information. Debug line %d. Software error. If priority is emergency, or if priority is error and occurs repeatedly, then record steps to recreate the event, capture the event log and console output, and contact Customer Service. DS hit default %d file %s line %d. DS hit default. Debug information for Software Engineering use. Delete request specified primary Delete request specified primary flow. flow MAC addr %A, must Debug information for Software deregister. Engineering use. Emergency
4317
4318
Error
September 2003
Dynamic Service Event Codes 37-3 Table 37-1 (continued) Dynamic service event codes Event ID 4319 Event Text Message Deadmit or deactivate primary flow, deregister modem %A. Event Definition Deadmit or deactivate primary flow, deregister modem. Debug information for Software Engineering use. * Priority Error
4320
DSx req specified sfids from two DSx req specified sfids from two different sf Error diff sf groups, MAC addr %A. groups. External event to CMTS illegal. DSA RSP was too big, fail the DSA for MAC addr %A. DSC RSP was too big, fail the DSC for MAC addr %A. DSC ACK was OKAY but DSC-RSP was not, out of sync MAC addr %A. DSA rsp too big. External event to CMTS illegal. DSC rsp too big. External event to CMTS illegal. DSC out of sync. External event to CMTS illegal. Error Error Error
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
September 2003
37-1
37-
Table 37-1 lists and describes ash memory-related error codes for the system manager module generated by the CMTS 1500.
Table 37-1 Flash event codes Event ID 4400 Event Text Message FH: Non-volatile memory is FULL, config changes will no longer be saved Event Definition * Priority Flash memory is FULL, config updates will Critical not be saved
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
CMTS 1500 v 4.3 Error Codes Guide Release 4.3 Standard 1.0
September 2003
RFC AUTHENTICATION Authentication failure FAILURE invalid_name:'%s' nameLength:%d src_ip_addr"%x failure reason:%d interface:%d RFC topology change RFC new root Topology change New root
4505 4506
Information Information
* emergencyfatal error, cannot recover; alerta condition that should be corrected immediately; criticalcritical condition such as NVRAM is full; errornon-fatal error, may or may not require action; warningwarning message; noticecondition that is not error connected but may require special handling; informationinformation message, no action required; debug internal debug information
September 2003