Table Of Contents

LCCOREDUMP Messages

LC_CT3 Messages

LC_CX3 Messages

LC_DMLP Messages

LCDS3 Messages

LDP Messages

LCE3 Messages

LCFE Messages

LCGE Messages

LCINFO Messages

LCCOREDUMP Messages

The following are GRP line card core dump subsystem messages.

Error Message    

%LCCOREDUMP-3-BADCLOSE : Can't close slave core socket for slot [dec]

Explanation    The system just finished dumping a core file. It tried to close this file on the remote system and failed.

Recommended Action    Debug network connections and user privileges.

Error Message    

%LCCOREDUMP-3-ILLEGALREQ : Cannot process coredump request for slot [dec]

Explanation    A line cannot not directly send a core dump request.

Recommended Action    Gather information about the state of the card. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     

%LCCOREDUMP-3-ILLPAK : Coredump packet received from slot [dec] (not in dump state)
[hex] [hex] [hex] [hex]\n[hex] [hex] [hex] [hex]\n[hex] [hex] [hex] [hex]
[hex] [hex] [hex] [hex]

Explanation    A core dump packet from a card that should not be dumping a core dump packet has arrived at the RP.

Recommended Action    Gather information about the state of all cards, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the information you have gathered.

Error Message     

%LCCOREDUMP-3-ILLTD : Testdump not allowed on primary GRP

Explanation    The user has attempted to run a line card core dump test for a primary GRP. This action is not allowed.

Recommended Action    Do not run a line card core dump test for a primary GRP.

Error Message     

%LCCOREDUMP-3-NOMCP : Cannot malloc memory for mbus core dump message to slot [dec]

Explanation    The system is trying to write a core dump file to a remote system. It could not allocate memory to create the message to send to start the dump on the card.

Recommended Action    Add memory.

Error Message    

%LCCOREDUMP-4-NOMEM : Could not allocate memory for [chars]

Explanation    Memory allocation for a core dump parameter has failed.

Recommended Action    Gather information about memory usage. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     

%LCCOREDUMP-3-NOPAK : No packet on queue ([hex] [dec])

Explanation    A core dump packet from a card that should not be dumping core arrived at the RP.

Recommended Action    Gather information about the state of all cards and file a bug.

Error Message     

%LCCOREDUMP-3-NOQUEUE : Cannot create queue to receive dump packets for slot [dec]

Explanation    The system is trying to write a core dump file to a remote system. It could not create a queue to hold dump data coming from the card.

Recommended Action    Add memory.

Error Message     

%LCCOREDUMP-4-TIMEOUT : [chars] ([hex] [dec])

Explanation    The system is trying to write a core dump file, but the RP timed out waiting for data from the card.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

LC_CT3 Messages

The following are line card error messages for the Channelized T3 controller.

Error Message    

%LC_CT3-1-INITBERT : BERT port [dec] init failed ([chars])

Explanation    A T1 BERT initialization failure has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs. data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, contact your Cisco technical support representative, and provide the representative with the information you have gathered.

Error Message     

%LC_CT3-1-INITFAIL : CT3 linecard init ([chars])

Explanation    The CT3 could not be initialized.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LC_CT3-1-INITFAILP : [dec] init failed at [chars]

Explanation    The CT3 port could not be initialized.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LC_CT3-3-NOTFOUND : [chars] not found for port [dec].

Explanation    A software or hardware error has occurred. The specified object was not found.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LC_CT3-3-UNEXPECTEDCASE : Unexpected case ([dec])

Explanation    An unexpected case has occurred in the CT3 line card software switch statement.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

LC_CX3 Messages

The following are error messages for the CX3 line card.

Error Message    

%LC_CX3-3-BMA_ERR : Packet with length 0 received by FrFab BMA:
[chars]

Explanation    The FrFab BMA has encountered a packet with length of zero, and forwarded it to the PLIM so that it could be logged.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LC_CX3-1-INITFAIL : CX3 linecard init ([chars])

Explanation    An attempt to initialize the CX3 has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LC_CX3-4-INVCALL : Invalid call ([chars]: [dec])

Explanation    A software error was detected.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LC_CX3-2-KEEPALIVE_FAILURE : PLIM Keepalive failed (freedm [int]) - plim reset

Explanation    A PLIM keepalive failure was detected.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LC_CX3-3-MBOXACCESS : Mailbox[[dec]] in use by process [chars], timeout by process [chars]

Explanation    A process could not obtain access to the PLIM mailbox on an Internet router CX3 line card because the PLIM mailbox was locked by another process.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Enter the following commands to gather data that may provide information to determine the nature of the error: exec slot slot-number show controllers tofab mailbox, exec slot slot-number show controllers frfab mailbox, exec slot slot-number show plim tofab mailbox, exec slot slot-number show plim frfab mailbox, with slot-number being the slot number of the CX3 line card. Call your Cisco technical support representative. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LC_CX3-3-NOBUFFERS : Message dropped from [chars]: No buffers available

Explanation    There are not enough buffers available for messages coming from the PLIM on an Internet router CX3 line card.

Recommended Action    Try shutting down debugs on the PLIM CPU or reloading the card. If the problem persists, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative, and provide the representative with the information you have gathered.

Error Message    

%LC_CX3-3-PLIMCON : Message dropped from [chars]: No buffers available

Explanation    There are too many messages coming from the PLIM on an Internet router CX3 line card. There are no more buffers on the line card to handle these messages.

Recommended Action    Try shutting down debugs on the PLIM CPU or reloading the card. If the problem persists, copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may help identify the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support command output, contact your Cisco technical support representative, and provide the representative with the information you have gathered.

Error Message    

%LC_CX3-2-PLIM_CPU_CRASHED : PLIM CPU [chars] - plim reset

Explanation    PLIM CPU software did not respond to a heartbeat message.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LC_CX3-1-PLIM_CPU_ERR : [chars]: [chars]

Explanation    The PLIM CPU reported a system message.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LC_CX3-4-THROTTLE : Packet throttling activated due to congestion

Explanation    Packet throttling has been started in the PLIM due to excessive buffer overruns. Throttling eliminates overruns, which allows high priority packets such as link control and keepalives to be preserved and to pass through. This mechanism prevents interfaces from toggling up and down.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LC_CX3-4-UNEXPECTEDCASE : Unexpected case ([dec])

Explanation    An unexpected case was encountered in the line card software switch statement.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LC_CX3-4-UNEXPECTEDCOND : Unexpected condition [chars] [dec]

Explanation    An unexpected condition was encountered in the line card software.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

LC_DMLP Messages

The following are line card DMLP messages.

Error Message     

%LC_DMLP-4-BUNDLENULL : Unexpected null bundle in [chars], searching for [chars]

Explanation    A software error has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LC_DMLP-1-IDBCREATEFAIL : Could not create bundle hwidb in [chars]

Explanation    The system is out of resources.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LC_DMLP-4-IDBNULL : Unexpected null hwidb in [chars]

Explanation    A software error has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LC_DMLP-4-IDBWRONG : The requested hwidb is null or wrong type in [chars], vc [dec]

Explanation    A software error has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LC_DMLP-4-NLINKS : The bundle had an unexpected number of links in [chars], nlinks [dec]

Explanation    A software error has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

LCDS3 Messages

The following are error messages for the DS3 line card.

Error Message     

%LCDS3-1-ALLOCFAIL : [dec]/[dec][chars] allocation failure

Explanation    Memory could not be allocated for the DS3.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LCDS3-0-BADPORT : [chars] [dec]

Explanation    A very high rate of bad packets was received on the specified port. This situation can happen because of port misconfiguration, especially for mismatched DSU subrates (most common with Kentrox). The port is shut down for this reason so that the line card is not overwhelmed with these bad packets.

Recommended Action    Verify that the configuration is correct and matching on both ends of the connection. These include the clock source (one end line, the other internal), DSU (mode and subrate), and encapsulation. Also verify the physical condition on the line (run BERT or other tests), signal strength, and cable length.

Error Message     

%LCDS3-3-BMAENG : [chars] HDLC, [chars] [chars][chars]. (src=[hex], det1=[hex], det2=[hex])

Explanation    Hardware errors have occurred in the HDLC BMA engine.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Run diagnostics on the line card in slot x. If diagnostics pass, contact your Cisco technical support representative, and provide the representative with the information you have gathered.

Error Message     

%LCDS3-3-BMAPAR : [chars] HDLC, [chars]. BMA_DATA[3:0]=[hex]. (src=[hex], det1=[hex], det2=[hex])

Explanation    A parity error has occurred on the HDLC ASIC BMA engine.

Recommended Action    Run diagnostics on the line card in the specified slot. Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     

%LCDS3-3-HDLCENG : [chars] HDLC, [chars]. [chars], port [dec]. (src=[hex], det1=[hex], det2=[hex])

Explanation    HDLC engine hardware errors have occurred.

Recommended Action    Run diagnostics on the line card in the specified slot. Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     

%LCDS3-0-INITFAIL : initialization failure for slot [dec]

Explanation    The DS3 line card could not be initialized.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    .

%LCDS3-2-LOWSIG : low DS3 signal in port [dec]

Explanation    A low signal condition was detected in the specified DS3 port.

Recommended Action    Verify the DS3 line conditions.

Error Message     

%LCDS3-3-NOHWIDB : [dec]/[dec][chars] hardware IDB is missing

Explanation    DS3 port hardware IDB is missing.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LCDS3-3-SRAMPAR : [chars] HDLC, [chars]. [chars]=[hex][chars]. (src=[hex], det1=[hex], det2=[hex])

Explanation    A parity error has occurred on the HDLC ASIC SRAM.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LCDS3-4-UNKNOWNPARAM : [dec]/[dec][chars] parameter value is unknown

Explanation    An IPC command parameter is unknown.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

LDP Messages

The following are Label Distribution Protocol (LDP) messages.

Error Message    

%LDP-4-ADV : Label advertisement mode (DU/DoD) mismatch with peer [chars], resolved to [chars].

Explanation    A disagreement regarding the label distribution mode to be used with an LDP peer has been resolved according to the LDP protocol specification. For LCATM links when there is a disagreement the protocol specification requires that the session use Downstream on Demand mode; for frame-based links when there is disagreement the protocol requires that the session use Downstream Unsolicited mode.

Recommended Action    This is an informational message. The system will recover from this situation by terminating the TDP session and attempting to establish a new session with the peer. If this message occurs repeatedly, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LDP-5-GR : [chars]

Explanation    An informational LDP notice was generated for a "graceful restart" event.

Recommended Action    No action is required.

Error Message     

%LDP-3-MALFORMED_MSG : peer [chars]; format error for msg type [hex]

Explanation    A malformed LDP message has been received from an LDP peer.

Recommended Action    This is an informational message. The system will recover from this situation by terminating the TDP session and attempting to establish a new session with the peer. If this message occurs repeatedly, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the information you have gathered.

Error Message    

%LDP-5-NBRCHG : [chars] Neighbor [chars] is [chars]

Explanation    An LDP neighbor has either come up or gone down. The error message text describes the change for it.

Recommended Action    This informational message normally appears as routers and LDP neighbors go up or down. However, unexpected neighbor loss might indicate high error rates or high packet loss in the network and should be investigated.

Error Message     

%LDP-4-PTCL : peer [chars], [chars]

Explanation    A violation of the LDP protocol by an LDP peer has been detected.

Recommended Action    This is an informational message. The system will recover from this situation by terminating the TDP session and attempting to establish a new session with the peer. If this message occurs repeatedly, copy the error message exactly as it appears on the console or in the system log, contact your Cisco technical support representative, and provide the representative with the information you have gathered.

Error Message    

%LDP-3-UNKNOWN_MPLS_APP : [chars] [chars] message from [chars]; [chars];

Explanation    An LDP message with an unknown label type or address family has been received from a peer. The message has been dropped.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

LCE3 Messages

The following are line card E3 messages.

Error Message     

%LCE3-1-ALLOCFAIL : [dec]/[dec][chars] allocation failure

Explanation    Memory could not be allocated for the E3 port.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LCE3-0-BADPORT : [chars] [dec]

Explanation    A very high rate of bad packets was received on the specified port. This situation can happen because of port misconfiguration (most common with Kentrox). The port is shut down for this reason so that the line card is not overwhelmed with these bad packets.

Recommended Action    Verify that the configuration is correct and matching on both ends of the connection. These include the clock source (one end line, the other internal), DSU mode, and encapsulation. Also verify the physical condition on the line (run BERT or other tests), signal strength, and cable length.

Error Message     

%LCE3-3-BMAENG : [chars] HDLC, [chars] [chars][chars]. (src=[hex], det1=[hex], det2=[hex])

Explanation    Hardware errors have occurred on the HDLC BMA engine.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LCE3-3-BMAPAR : [chars] HDLC, [chars]. BMA_DATA[3:0]=[hex]. (src=[hex], det1=[hex], det2=[hex])

Explanation    A parity error has occurred on the HDLC ASIC BMA engine.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LCE3-3-HDLCENG : [chars] HDLC, [chars]. [chars], port [dec]. (src=[hex], det1=[hex], det2=[hex])

Explanation    Hardware errors have occurred on the HDLC engine.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LCE3-0-INITFAIL : initialization failure for slot [dec]

Explanation    The E3 line card could not be initialized.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LCE3-2-LOWSIG : low E3 signal in port [dec]

Explanation    A low signal condition was detected in the specified E3 port.

Recommended Action    Verify the E3 line conditions.

Error Message     

%LCE3-3-NOHWIDB : [dec]/[dec][chars] hardware IDB is missing

Explanation    The E3 port hardware IDB is missing.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LCE3-3-SRAMPAR : [chars] HDLC, [chars]. [chars]=[hex][chars]. (src=[hex], det1=[hex], det2=[hex])

Explanation    A parity error has occurred on the HDLC ASIC SRAM.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LCE3-4-UNKNOWNPARAM : [dec]/[dec][chars] parameter value is unknown

Explanation    An IPC command parameter is unknown.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

LCFE Messages

The following are Fast Ethernet line card messages.

Error Message     

%LCFE-6-CAM_ADD : Failed to add address [enet] to CAM

Explanation    An entry could not be added to the CAM MAC address filter.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LCFE-4-CAM_DONE_ITER : CAM [chars]: wait for DONE exceeded [dec] iterations

Explanation    An LC Fast Ethernet Rx Translator CAM DONE bit was not reset to 1 on a write or read within the given number of iterations.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LCFE-4-CAM_DONE_TIME : CAM [chars]: wait for DONE exceeded timeout ([dec] ms)

Explanation    An LC Fast Ethernet Rx Translator CAM DONE bit was not reset to 1 on a write or read within the given timeout period.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LCFE-6-CAM_EXCEEDED : [dec] entries to add > [dec] entries available

Explanation    An entry could not be added to the CAM MAC address filter.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LCFE-6-CAM_INIT : HW MAC address filter (CAM) init failed: CAM disabled

Explanation    The CAM hardware containing the MAC address filter has failed.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LCFE-6-CAM_REMOVE : Failed to remove address [enet] from CAM

Explanation    The system has failed to remove an entry from the CAM MAC address filter.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LCFE-3-FE_MAC_INTR : MAC has detected unexpected interrupt

Explanation    The LC Fast Ethernet MAC has detected an unexpected error interrupt.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LCFE-3-FE_RX_MICE : MICE not initialized

Explanation    The LC Fast Ethernet Mice FPGA could not be loaded.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LCFE-1-INITFAIL : LCFE([dec]/[dec]), initialization timeout failure

Explanation    The LC Fast Ethernet hardware could not be initialized.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LCFE-6-LINE_STATE : Line state [chars]

Explanation    A line state error was detected or fixed as specified in the message.

Recommended Action    Check the cable connections. A local Rx cable must be connected to the remote Tx cable and vice versa.

Error Message     

%LCFE-4-OP : error: [chars]

Explanation    A line card Fast Ethernet driver general operation error has occurred.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LCFE-4-RPCMD : [chars] command error: [chars]

Explanation    The line card Fast Ethernet driver has encountered RP command errors.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LCFE-6-RX_LOS : [chars] RX Loss of Signal

Explanation    An Rx loss of signal error was detected or fixed as specified in the message.

Recommended Action    Check the cable connections. A local Rx cable must be connected to the remote Tx cable and vice versa.

Error Message     

%LCFE-3-RX_TRANS_INTR : RX FPGA has detected SRAM Parity Error

Explanation    The LC Fast Ethernet Rx Translator FPGA has detected an SRAM parity error.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LCFE-3-RX_TX_TRANS : RX/TX FPGA not initialized

Explanation    The LC Fast Ethernet Rx/Tx Translator FPGA could not be loaded.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message    

%LCFE-3-SOP : [chars]. Source=[hex] [chars], halt_minor0=[hex] [chars]

Explanation    The LC Fast Ethernet SOP has encountered hardware errors.

Recommended Action    Copy the message exactly as it ap