-
12.3 T System Message Guide
-
System Message Overview
-
AAA through BSTUN messages
-
C10K through CALL_CONTROL messages
-
CALLRECORD through CPOS messages
-
CRYPTO through DMA messages
-
DNET through ENVM messages
-
ENVMON through FDM_HA messages
-
FECPM through GT96K_TDM messages
-
GTP through HEALTH_MONITOR messages
-
HHM through IPSECV6 messages
-
IPV6 through MICA messages
-
MIPC through NP_VPD messages
-
NRP through PIF messages
-
PIM through PVDM2 messages
-
PXF through RPM_BULK messages
-
RPM_CONN_MGMT through SEC_LOGIN messages
-
SENSOR through SWITCH_IF messages
-
SWITCHOVER through Y88E8K messages
-
Glossary of Acronyms
-
Table Of Contents
IP_VFR Messages
The following are IP Virtual Fragment Reassembly (VFR) subsystem messages.
Error Message%IP_VFR-4-FRAG_TABLE_OVERFLOW : [chars]: the fragment table has reached its maximum threshold [dec]
Explanation The number of datagrams being reassembled at any one time has reached it maximum limit.
Recommended Action Increase the maximum number of datagrams that can be reassembled by entering the ip virtual-reassembly max-reassemblies number command, with number being the maximum number of datagrams that can be reassembled at any one time.
Error Message%IP_VFR-3-INVALID_FRAG_LENGTH : [chars]: fragment length invalid - received from [IP_address], destined to [IP_address]
Explanation The router has encountered a "ping-of-death" type of attack
Recommended Action It is highly recommended to configure an ACL to drop any traffic from the sender of this attack.
Error Message%IP_VFR-3-OVERLAP_FRAGMENTS : [chars]: from the host [IP_address] destined to [IP_address]
Explanation The router has encountered overlap fragments. "Overlap fragment" means that the offset of one fragment overlaps the offset of another fragment. For example, if the offset of the first fragment is 0 and its length is 800, the offset of the second fragments offset must be 800. If the offset of the second fragment is less than 800, the second fragment overlaps the first fragment. This condition might indicate a hostile attack.
Recommended Action Configure a static ACL to prevent further overlap fragments from the sender.
Error Message%IP_VFR-3-SYSTEM_ERROR : [chars]: IP VFR System failure - [chars]
Explanation Miscellaneous errors have occurred in the VFR subsystem.
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%IP_VFR-4-TINY_FRAGMENTS : [chars]: from the host [IP_address] destined to [IP_address]
Explanation The router is receiving tiny fragments (the initial fragment does not have a complete layer 4 header).
Recommended Action This is an informational message only. No action is required.
Error Message%IP_VFR-4-TOO_MANY_FRAGMENTS : [chars]: Too many fragments per datagram (more than [dec]) - sent by [IP_address], destined to [IP_address]
Explanation The datagram that is being reassembled has received more fragments than its threshold value.
Recommended Action Check to see if the fragments that are being received are from a genuine source. If the fragments are coming from a genuine source, enter the ip virtual-reassembly max-fragments number command, with number being the maximum number of fragments that are allowed, to increase the fragment value.
IP_VRF Messages
The following are VPN routing and forwarding messages.
Error Message%IP_VRF-4-VRF_DELETE_WAIT : The VRF [chars] is getting deleted after a wait
Explanation There are routes remaining in the routing table of a deleted VRF, even after the system has waited for the deletion to complete. To ensure reusability of the same VRF, the routes in the VRF routing table are forcibly being cleared to complete the VRF deletion operation.
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.
IPV6 Messages
The following are IP version 6 (IPv6) messages.
Error Message%IPV6-3-INTERNAL : Internal error, [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet 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 gathered information.
Error Message%IPV6-3-MIN_MTU : The link MTU of [chars] is below the [int]-byte minimum IPv6 link MTU. IPv6 may not work correctly on this interface.
Explanation IPv6 requires that every link have an MTU of at least 1280 as specified in the IPV6 standard. Because the MTU for this link is less than 1280, IPv6 has been disabled on this interface.
Recommended Action No action is required.
Error Message%IPV6-4-MULTICAST : Application does not support multicast destination address [ipv6_addr], packet dropped.
Explanation An internal software error has occurred. A multicast destination address was used in a local application that does not yet handle IPv6 multicast.
Recommended Action Use a unicast address in commands on the router. If the problem persists, or you feel that the command should support multicast, then contact the TAC with the failing command line.
Error Message%IPV6-3-UNFRAGMENTABLE : Cannot fragment packet: unfragmentable part length [dec], MTU of [dec]
Explanation An internal software error has occurred. A single packet that was originated by this system could not be fragmented and has been dropped. Normal system operation will continue.
Recommended Action This is a transient error; however, this condition indicates other errors in the software that will require further examination by your Cisco technical support representative. 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.
IPV6_FW Messages
The following are IPv6 Inspection subsystem messages.
Error Message%IPV6_FW-4-ALERT_OFF : [chars], count ([dec]/[dec]) current 1-min rate: [dec]
Explanation Either the number of half-open connections have dropped below the low threshold, or the new connection initiation rate has dropped below the low threshold. This message may indicate that an attack has stopped.
Recommended Action No action is required.
Error Message%IPV6_FW-4-ALERT_ON : [chars], count ([dec]/[dec]) current 1-min rate: [dec]
Explanation Either the high threshold of half-open connections has been exceeded, or the new connection initiation rate has been exceeded. This message indicates that an unusually high rate of new connections is coming through the firewall, and a DOS attack may be in progress. This message is for informational purposes only, but may indicate a security problem.
Recommended Action If an attack is suspected, perform actions to block the security attack.
Error Message%IPV6_FW-2-BLOCK_HOST : Blocking new TCP connections to host[p] for [dec] minute[chars] (half-open count [dec] exceeded).
Explanation The threshold of half-open TCP connections has been exceeded, and the blocking option will now block any subsequent new connections. The blocking will be removed when the configured block-time expires. This message is for informational purposes only, but may indicate that a SYN flood attack was attempted.
Recommended Action If a SYN attack is suspected, perform actions to block a SYN attack.
Error Message%IPV6_FW-3-FTP_NON_MATCHING_IP_ADDR : Non-matching address[p] used in [chars] -- FTP client[p] FTP server[p]
Explanation An FTP client attempted to use a port command, or the FTP server attempted to use a response to a PASV command to trick the firewall into opening access to a third-party host that is different from the two hosts that are engaged in the FTP connection. This message indicates that a suspicious violation was detected while an attempt to modify the security policy was being made in the firewall. The command is rejected and the connection is reset by the firewall. This message is for informational purposes only, but may indicate that an attempt was made to grant or open access to unauthorized hosts.
Recommended Action If this is an expected message, no action is required. If this message is unexpected, or you determine that this condition is the result of a malicious attempt to breach the firewall, perform actions to correct the problem.
Error Message%IPV6_FW-3-FTP_PRIV_PORT : Privileged port [dec] used in [chars] -- FTP client[p] FTP server[p]
Explanation An FTP client attempted to use a port command, or the FTP server attempted to use a response to a PASV command to trick the firewall into opening access to a privileged port. This message indicates that a suspicious violation was detected from the FTP client or server that was attempting to modify the security policy in the firewall. The command is rejected and the connection is reset by the firewall. This message is for informational purposes only, but may indicate that an attempt was made to gain access to privileged ports.
Recommended Action If this is an expected message, no action is required. If this message is unexpected, or you determine that this condition is the result of a malicious attempt to breach the firewall, perform actions to correct the problem.
Error Message%IPV6_FW-3-FTP_SESSION_NOT_AUTHENTICATED : Command issued before the session is authenticated -- FTP client[p] FTP server[p]
Explanation An FTP client attempted to use the port command or an FTP server attempted to use the response to a PASV command to open a data channel in the firewall before the client could be successfully authenticated with the server. This condition is a suspicious attempt by the client or server to trick the firewall into opening a hole so that outside attackers can take advantage of the firewall opening. This message indicates that a suspicious violation was detected, and the port or PASV command or response has been rejected by the firewall. The data channel in the firewall will not be opened until the authentication is performed successfully. This message is for informational purposes only, but may indicate that an illegal attempt was made to modify the firewall security policy.
Recommended Action If this is an expected message, no action is required. If this message is unexpected, or you determine that this condition is the result of a malicious attempt to breach the firewall, perform actions to correct the problem.
Error Message%IPV6_FW-4-HOST_TCP_ALERT_ON : Max tcp half-open connections ([dec]) exceeded for host[p].
Explanation The maximum limit of half-open TCP connections has been exceeded. A high number of half-open connections is being received by the protected server. This condition may indicate that a SYN flood attack is in progress and is targeted to the specified server host. This message is for informational purposes only, but may indicate that a SYN flood attack was attempted.
Recommended Action If this alert is issued frequently and identified to be mostly false alarms, then the max-incomplete host threshold value is probably set too low, and there is a lot of legitimate traffic coming in to that server. In this case, set the max-incomplete host parameter to a higher number to avoid false alarms.
Error Message%IPV6_FW-3-NOTFOUND : Session context for Unrecognized format `(%P':[dec]) => Unrecognized format `(%P':[dec]) not found.
Explanation The CBAC code was searching its database for information for a particular inspection session, but this information was not found.
Recommended Action If this message recurs, 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%IPV6_FW-6-SESS_AUDIT_TRAIL : [chars] session initiator Unrecognized format `(%P':[dec]) sent [int] bytes -- responder Unrecognized format `(%P':[dec]) sent [int] bytes
Explanation This message documents the per-session transaction log of network activities. The message is issued at the end of each inspected session and it records the source and destination addresses and ports, as well as the number of bytes transmitted by the client and server. This message is for informational purposes only, and can be used to collect basic accounting information for inspected sessions.
Recommended Action No action is required.
Error Message%IPV6_FW-4-UNBLOCK_HOST : New TCP connections to host[p] no longer blocked
Explanation New TCP connection attempts to the specified host are no longer blocked. This message indicates that the blocking of new TCP attempts to the specified host has been lifted. This message is for informational purposes only, but may indicate that a SYN flood attack was previously attempted to the host.
Recommended Action No action is required.
IPV6_VFR Messages
The following are IPv6 virtual fragment reassembly subsystem messages.
Error Message%IPV6_VFR-4-FRAG_TABLE_OVERFLOW : the fragment table has reached its maximum threshold [dec]
Explanation The number of datagrams being reassembled has reached its maximum limit.
Recommended Action , increase the maximum datagram value by entering the ip virtual-reassembly max-datagram number, with number being the maximum number of datagrams that can be assembled.
Error Message%IPV6_VFR-3-INVALID_FRAG_LENGTH : fragment length invalid - received from[p], destined to[p]
Explanation The router has encountered activity that indicates that a "ping-of-death" attack is being initiated.
Recommended Action To prevent further attacks, we strongly recommend that you configure an ACL to drop any traffic from the sender of this attack.
Error Message%IPV6_VFR-3-OVERLAP_FRAGMENTS : from the host[p] destined to[p]
Explanation The router has encountered overlapping fragments. An offset of one fragment has overlapped the offset of another fragment. For example, if the offset of the first fragment is 0 and its length is 800, the offset of the second fragment must be 800. If the offset of the second fragment is smaller than 800, that means that the second fragment overlaps the first fragment. This condition could possibly indicate a hostile attack.
Recommended Action Configure a static ACL to prevent further overlapping fragments from the sender.
Error Message%IPV6_VFR-3-SYSTEM_ERROR : IP VFR System failure - [chars]
Explanation Miscellaneous errors have occurred in the VFR subsystem.
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%IPV6_VFR-4-TINY_FRAGMENTS : from the host[p] destined to[p]
Explanation The router is receiving tiny fragments. The initial fragment does not have a complete layer 4 header.
Recommended Action No action is required.
Error Message%IPV6_VFR-4-TOO_MANY_FRAGMENTS : Too many fragments per datagram (more than [dec]) - sent by[p], destined to[p]
Explanation The datagram being reassembled has received more fragments than its threshold value allows.
Recommended Action Check to see if the fragments that have been received are from a genuine source. If the received fragments are from a genuine source, increase the value of maximum fragments per datagram by entering the virtual-reassembly fragments-per-datagram number command, with number being the number of maximum fragments allowed per datagram.
IPX Messages
The following are Novell Internetwork Packet Exchange Protocol (IPX) messages.
Error Message%IPX-3-NOVNOSTART : IPX Failed to Start due to insufficient memory
Explanation The Novell IPX routing subsystem failed to initialize properly because of memory allocation errors. This condition is usually caused by an insufficient amount of available memory.
Recommended Action Reduce other system activity to ease memory demands, look for a possible memory leak, or upgrade to a larger memory configuration.
ISDN Messages
The following are Integrated Services Digital Network (ISDN) messages.
Error Message%ISDN-1-NOMEMORY : no memory for [chars]
Explanation The requested operation could not be completed because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
IVR Messages
The following are Interactive Voice Response (IVR) messages.
Error Message%IVR-3-BADSCRIPT : Could not parse malformed IVR script: [chars]\n
Explanation The system could not parse a malformed IVR script. This message is most likely generated by a syntax error.
Recommended Action Check the script and fix the syntax error.
IVR_NOSIGNALING Messages
The following are Interactive Voice Response (IVR) system messages not related to call signaling.
Error Message%IVR_NOSIGNALING-3-LOW_CPU_RESOURCE : IVR: System experiencing high cpu utilization ([dec]/100). Application cannot be instantiated.\n
Explanation The system does not have enough CPU capacity to spawn a new instance of the IVR application.
Recommended Action Ensure that the call setup rate is within the supported capacity of this gateway.
Error Message%IVR_NOSIGNALING-3-LOW_MEMORY_RESOURCE : IVR: System running low on memory ([dec]/100 in use). Application cannot be instantiated.\n
Explanation The system does not have enough free memory to spawn a new instance of the IVR application.
Recommended Action Ensure that the gateway has the recommended amount of memory for this Cisco IOS software feature set and version.
IXP1200_CP Messages
The following are one-port Fast Ethernet with coprocessor assist messages.
Error Message%IXP1200_CP-1-CMDERR : [chars]: Command [hex] failed with status [hex]
Explanation A command was sent to the Encryption AIM, and it responded that the command contained an error. The details of the failure depend upon the circumstances, but in all likelihood the Encryption AIM is faulty and should be replaced.
Recommended Action The one-port Fast Ethernet coprocessor will most likely need to be replaced. 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%IXP1200_CP-3-DEACTIVATED : bay [[dec]] deactivated
Explanation The port adapter is being deactivated because it failed to successfully complete its initialization. Other messages in the log specify the exact cause of the failure.
Recommended Action If possible, correct any errors that were indicated by the other messages that were received at the same time that this message was received. Verify that the port adapter is properly seated in the bay.
Error Message%IXP1200_CP-1-FUTIL : Flash Utilities were downloaded instead of the RAM Application
Explanation Flash utilities (FlashUtil) were downloaded onto the one-port Fast Ethernet coprocessor instead of the RAM application (RAMApp). The flash memory can be updated on the coprocessor, but no traffic can be run.
Recommended Action Remove any "ixp1200_cp_firmware" binary files that exist in the flash memory and remove the card. If this does not fix the problem, load a version of the Cisco IOS software that has RAMApp bundled instead of FlashUtil.
Error Message%IXP1200_CP-3-HB_FAILURE : 1FE-CP HeartBeat Lost from slot [dec]
Explanation The IXP1200 is no longer receiving heartbeat messages from the line card in the slot indicated in the message.
Recommended Action If the one-port Fast Ethernet coprocessor backcard was removed, no action is required. If other heartbeat error messages are seen, 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%IXP1200_CP-1-HB_STOP : [chars] Heartbeats stopped due to IXP crash
Explanation The IXP1200 complex has failed.
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%IXP1200_CP-1-HPRX_CTX_MEM_POOL : Out of resources for [chars]. Requested [dec] compression-connections, obtained [dec]
Explanation Insufficient memory is available to allocate all the contexts to the cRTP interfaces. More contexts were allocated by entering the ip rtp compression-connection command than the one-port Fast Ethernet coprocessor memory resources can accommodate.
Recommended Action Reduce the number of compression connections on some of the interfaces so that the sum for all interfaces does not exceed 6000.
Error Message%IXP1200_CP-1-HPRXERR : Unexpected error received from CP, status [hex]
Explanation An unexpected error occurred during packet processing.
Recommended Action This message can occur occasionally during normal operation of the system. However, if it happens frequently, or is associated with traffic disruption, this condition indicates that the one-port Fast Ethernet coprocessor will most likely require replacement. 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%IXP1200_CP-1-INITFAIL : CP: Initialization failed at [chars]
Explanation The one-port Fast Ethernet coprocessor would not reset properly. This condition indicates a hardware failure.
Recommended Action The one-port Fast Ethernet coprocessor will require replacement. 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%IXP1200_CP-3-IXP1200_CP_DRIVERKILL : Unexpected request to terminate: 1FE-CP driver process ([chars])
Explanation The driver process for the one-port Fast Ethernet coprocessor was terminated unexpectedly.
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%IXP1200_CP-1-IXP_CRASH : [chars] IXP crashed due to [chars]
Explanation The IXP1200 complex has failed.
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%IXP1200_CP-3-IXP_CRASHINFO_FAIL : Failed to write IXP debug information.
Explanation IXP debugging information could not be written. The device on which the write operation was attempted is likely out of free space, or the write has encountered some other error.
Recommended Action Free up some memory on the device on which the write operation was attempted. If you require further assistance, 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%IXP1200_CP-1-ME_FAIL : [chars] MicroEngines lost heart beat
Explanation The micro engines have failed.
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%IXP1200_CP-6-MULTDEV : Cannot support more than one 1 FE/Co-Processor
Explanation A second one-port Fast Ethernet coprocessor was discovered present in the system. The one-port Fast Ethernet coprocessor software supports only a single one-port Fast Ethernet coprocessor. All other one-port Fast Ethernet coprocessor that are installed will be ignored.
Recommended Action Remove one of the one-port Fast Ethernet coprocessors that is installed in your system.
Error Message%IXP1200_CP-1-NOHW : One Port Fast Ethernet With Co-processor Assist not present in system
Explanation A user-entered command was issued that involves a one-port Fast Ethernet coprocessor back card, but none is present in the system.
Recommended Action The one-port Fast Ethernet coprocessor will most likely require replacement. 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%IXP1200_CP-6-OUT_OF_RESOURCES : [chars] cannot utilize Co-Processor. Co-Processor limited to [dec] interfaces.
Explanation The one-port Fast Ethernet coprocessor can perform a hardware assist function only on the number of interfaces that is displayed in the error message.
Recommended Action Limit the hardware assist functions to the number of interfaces that is displayed in the error message.
Error Message%IXP1200_CP-1-POSTFAIL : [chars]: Power On Self Test failed, alert status [hex]
Explanation The power-on self-test for the one-port Fast Ethernet coprocessor has failed.
Recommended Action The one-port Fast Ethernet coprocessor will require replacement. 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%IXP1200_CP-1-SA_FAIL : [chars] StrongArm lost heart beat
Explanation The strongarm processor has failed.
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%IXP1200_CP-6-STARTUP : [chars]: starting up
Explanation The specified one-port Fast Ethernet coprocessor has initialized successfully.
Recommended Action This message occurs during normal system operation. No action is required.
Error Message%IXP1200_CP-1-UNEXPCMD : [chars]: Invalid command reply: expected [hex] received 0x[chars]
Explanation A command was sent to the Encryption AIM, and the reply to that command contained an unexpected reply code. The details of the failure depend upon the circumstances, but in all likelihood the Encryption AIM is faulty and should be replaced.
Recommended Action The one-port Fast Ethernet coprocessor will most likely require replacement. 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%IXP1200_CP-1-UNEXPECTEDEVENT : Process received unknown event [hex]
Explanation A process specific to the IXP1200 process has received an event that it could not process.
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.
JAGGER Messages
The following are WAN line card messages.
Error Message%JAGGER-2-ASIC_INIT : Failed to initialize [chars] ASIC
Explanation This is probably a hardware problem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet 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 gathered information.
Error Message%JAGGER-2-BADPABAY : Out of range PCI Port Adaptor bay [dec]
Explanation The software has specified an out-of-range port adapter bay.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet 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 gathered information.
Error Message%JAGGER-4-BUSSTALL : Constellation BUS Stall detected
Explanation A stall was detected on the Constellation Bus probably due to some OIR activity on the Bus.
Recommended Action No action is required.
Error Message%JAGGER-3-ERROR : [chars]
Explanation Informational.
Recommended Action No action is required.
Error Message%JAGGER-4-FABRICCRCERRORS : [dec] Fabric crc error events in 100ms period
Explanation The fabric interface encountered more CRC errors than the Supervisor CRC error threshold allows.
Recommended Action The line card has notified the Supervisor and the fabric interface will be re-synchronized. No action is required.
Error Message%JAGGER-4-FABRICSYNCERRS : [dec] Fabric sync error events in 100ms period
Explanation The fabric interface encountered more sync error events than the Supervisor sync error threshold allows.
Recommended Action The line card has notified the Supervisor and the fabric interface will be re-synchronized. No action is required.
Error Message%JAGGER-3-IMAGESSAME : The rommon images are the same. No rommon upgrade is required.
Explanation A ROMmon upgrade was not carried out because the ROMmon images are the same.
Recommended Action No action is required.
Error Message%JAGGER-6-INFO : [chars]
Explanation Informational.
Recommended Action No action is required.
Error Message%JAGGER-3-IPCALLOCFAIL : Failed to allocate IPC buffer [chars]
Explanation The line card failed to allocate a buffer for communication with the Route Processor.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%JAGGER-3-IPCPORTFAIL : Failed to open IPC port '[chars]' [chars]
Explanation The line card failed to open a port for communication with the Route Processor.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%JAGGER-3-IPCSENDFAIL : Failed to send IPC message [chars]
Explanation The line card failed to send a message to the Route Processor.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%JAGGER-4-LOGMSGTOOBIG : Logger message length exceeds max, [int] bytes
Explanation The line card attempted to send a large message to the Route Processor.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter https://www.cisco.com/cgi-bin/Support/OutputInterpreter/home.pl. Also perform a search of the Bug Toolkit http://www.cisco.com/pcgi-bin/Support/Bugtool/home.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 gathered information.
Error Message%JAGGER-3-LONGSTALL : Long bus stall ([int] ms), check for improperly seated cards
Explanation This message indicates that a stall was detected, but the backplane stall was longer than expected.
Recommended Action Make sure that all cards are firmly seated. If the problem recurs, it may indicate a hardware failure.
Error Message%JAGGER-4-LYRAPATCH : Lyra Patch reset sequence invoked.
Explanation The Lyra patch reset sequence is being invoked.
Recommended Action No action is required.if traffic recovers. Otherwise contact technical support representative.
Error Message%JAGGER-4-LYRASEQERR : Lyra Sequence Error. Resetting port ASICS.
Explanation The Lyra ASIC detected a sequence error.
Recommended Action No action is required if traffic recovers. Otherwise, contact your technical support representative.
Error Message%JAGGER-3-MEDUSAFATAL : Medusa Fatal Error. Resetting ASIC.
Explanation The Medusa ASIC received a fatal error.
Recommended Action No action is required if traffic recovers. Otherwise contact technical support representative.
Error Message%JAGGER-5-MEDUSAMODECHANGE : MEDUSA Mode changed to [chars]
Explanation The Medusa device has changed the switching bus mode.
Recommended Action The Supervisor has changed the line card Medusa mode. No action is required.
Error Message%JAGGER-3-MEMORYALLOCERR : unable to allocate memory
Explanation The memory allocation for the .srec file has failed.
Recommended Action Ensure that there is enough memory available.
Error Message%JAGGER-3-NOFABRICPROCESS : No fabric process created
Explanation The fabric interface does not have a link process running; the system failed to create this process. This module will not support the fabric interface
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%JAGGER-3-OPENFILEERR : Unable to open file
Explanation The ROMmon upgrade file has failed to open.
Recommended Action Ensure that the approporiate .srec file is present in boot flash memory.
Error Message%JAGGER-2-PCIERROR : Fatal PCI Error [chars] seen on PCI Bus [dec]
Explanation A Fatal PCI Error was detected on the PCI bus. Most likely it is a hardware problem.
Recommended Action If this message recurs, 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 that 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%JAGGER-3-READFILEERR : Unable to read file
Explanation The read operation of the file has failed.
Recommended Action Ensure that the appropriate .srec file is present in boot flash memory.
Error Message%JAGGER-3-SRECDECODEERR : unable to decode SREC file
Explanation The decode from the .srec file to the bin file has failed.
Recommended Action Ensure that the appropriate SREC file is present in boot flash memory.
Error Message%JAGGER-4-UPGRADECOMPLETE : rommon upgrade completed. Please ensure that a host
image is present in bootflash: and power cycle the CMM.Explanation The ROMmon upgrade has been completed.
Recommended Action Power cycle the CMM.
Error Message%JAGGER-3-UPGRADEFAILERR : Rommon upgrade failed.
Explanation The ROMmon upgrade has failed.
Recommended Action If this message recurs, 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 that 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.
JETFIRE_SM Messages
The following are NAM Sensor network module messages.
Error Message%JETFIRE_SM-1-INITFAIL : NM slot [dec]: PCI device [dec] initialization failed
Explanation The initialization of the NAM Sensor network module has failed.
Recommended Action Power down, reseat the interface card, and reboot the system. If this message recurs, 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%JETFIRE_SM-1-MULTIPLEREGISTRATION : NM slot [dec]: PCI device [dec] multiple NAM service modules not allowed
Explanation another NAM sensor service module has already been installed.
Recommended Action Power down, reseat the interface card, and reboot the system. If this message recurs, 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.
KEYMAN Messages
The following are key string encryption messages.
Error Message%KEYMAN-4-KEYSTR_BAD_CRYPTO : Bad encrypted keystring for key id [dec].
Explanation The system could not successfully decrypt an encrypted key string. The key string may have been corrupted during system configuration.
Recommended Action Reenter the key-string command, and reconfigure the key string.
Error Message%KEYMAN-4-KEYSTR_CRYPTO_TYPE : Type [dec] encryption unknown. Interpreting keystring as literal
Explanation The format type was not recognized by the system. A key string format type value of 0 (unencrypted key string) or 7 (hidden key string), followed by a space, can precede the actual key string to indicate its format. An unknown type value will be accepted, but the system will consider the key string as being unencrypted.
Recommended Action Use the correct format for the value type, or remove the space following the value type.
L2HW_CM Messages
The following are Layer 2 hardware connection manager messages.
Error Message%L2HW_CM-3-CM_ERROR : Connection Manager Error - [chars].
Explanation An error occurred in the connection manager.
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%L2HW_CM-3-CM_INVALID_HANDLE : Connection Manager Error - Invalid [chars] handle - [dec].
Explanation An error in the connection manager occurred because of an invalid handle.
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%L2HW_CM-3-CM_INVALID_SEGMENT : Connection Manager Error - Invalid segment - [chars].
Explanation An error in the connection manager occurred because of an invalid segment.
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%L2HW_CM-3-SM_ERROR : Segment Manager Error - [chars].
Explanation An error occurred in the segment manager.
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.
LC Messages
The following are line card messages.
Error Message%LC-2-BADIDB : LC interface idb incorrect, [hex]
Explanation The line card control block data structure has indicated an IDB value of zero.
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-2-BADINTERFACE : Out of range Line Card interface, [dec] on bay [dec]
Explanation The software has specified an out-of-range line card interface.
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-2-BADLCCB : LC interface lccb incorrect, [hex]
Explanation The line card control block data structure was incorrectly set in the command data structure.
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-2-BADLCSLOT : Out of range Line Card slot [dec]
Explanation The software specified a line card slot that is not within the allowed range.
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-2-BADSUBSLOT : Out of range Line Card slot [dec] Sub Module slot [dec]
Explanation The software specified a sub-module slot that is not within the allowed range.
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-3-BRINGUPFAIL : line card in slot [[dec]] failed to reset.
Explanation An attempt to reset and initialize the line card has timed out. The line card could not be reset.
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-3-CIMUXERROR : CI-MUX: Serial Link [hex], Status [hex], [chars]
Explanation The cluster interconnect multiplexer FPGA on the RP has detected an error at the specified line card serial link. This error could be the result of line card FPGA logical errors, or the result of incorrect initialization of a line card serial link by the line card software driver. The line card has automatically been deactivated, and a recovery attempt will be made. If line card recovery attempts fail five times within an hour, the line card will be deactivated without further attempts at recovery.
Recommended Action Reactivate the line card by entering the hw-module slot slot-number start command, with slot-number being the slot number of the affected card. If this command fails to reactivate the line card, copy the message exactly as it appears on the console or in the system log. Enter the show diag slot-number command, with slot-number being the slot number of the affected card. Remove the line card and place it in a different slot. If the line card fails to initialize in the new slot, 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, show tech-support and show diag slot-number commands, with slot-number being the slot number of the affected card, and your pertinent troubleshooting logs.
Error Message%LC-3-CLFPGAERROR : Line card common logic fpga (slot [dec]) error: [chars]
Explanation The line card common logic FPGA in the specified slot encountered an error. This error could be result of either a problem with the line card FPGA or an incorrect line card reset sequence by the line card software driver. Because of the severity of the error, the line card has automatically been deactivated and a recovery attempt will be made. If line card recovery attempts fail five times within an hour, the line card will be deactivated without further attempts at recovery.
Recommended Action Reactivate the line card by entering the hw-module slot slot-number start command, with slot-number being the slot number of the affected card. If this command fails to reactivate the line card, copy the message exactly as it appears on the console or in the system log. Enter the show diag slot-number command, with slot-number being the slot number of the affected card. Remove the line card and place it in a different slot. If the line card fails to initialize in the new slot, 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, show tech-support and show diag slot-number commands, with slot-number being the slot number of the affected card, and your pertinent troubleshooting logs.
Error Message%LC-3-CONFIG : Recommended line card configuration exceeded
Explanation The aggregate throughput of the line cards exceeds the rated capacity of this system.
Recommended Action Refer to the configuration guidelines for the maximum allowed aggregate throughput of the line cards for the system.
Error Message%LC-3-DEACTIVATED : line card in slot [[dec]] deactivated.
Explanation The line card is being deactivated.
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-3-EMPTYSLOT : No line card in slot [[dec]].
Explanation There is no line card in the slot.
Recommended Action Insert a line card in the slot or attempt to reseat the line card into the slot. If there is already a line card in the slot and it is not being detected, 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-3-EXCESSERRORS : Errors seen on the line card (slot [dec]) exceeds the error threshold
Explanation The software is attempting to recover the line card from certain fatal errors such as the following:
–
A line card serial link error
–
–
–
–
–
The line card will automatically reinitialize after this error, unless the error occurs five times in one hour. If a line card encounters five such errors in one hour, the line card will be deactivated without further attempts at recovery.
Recommended Action Reactivate the line card by entering the hw-module slot slot-number start command, with slot-number being the slot number of the affected card, or by removing and reinserting the line card. Before manually removing and reinserting the line card, copy the message exactly as it appears on the console or in the system log and enter the show diag slot-number command, with slot-number being the slot number of the affected card. If this message recurs, 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, show tech-support and show diag slot-number commands, with slot-number being the slot number of the affected card, and your pertinent troubleshooting logs.
Error Message%LC-3-FPGAREVNOTMATCH : [chars]([dec]) Line card fpga requires min h/w revision of ([dec].[dec])
Explanation A newer hardware revision of the line card is required in order for the current FPGA to function properly on this chassis.
Recommended Action Upgrade the hardware revision of the line card, or downgrade the version of the FPGA.
Error Message%LC-3-FPGAREVNOTSUPPORTED : [chars]([dec]) Line card requires fpga revision of ([dec]).Current fpga revision is ([dec])
Explanation The specified line card has a downlevel FPGA revision. A newer FPGA revision of the line card is required for functional operation on this chassis.
Recommended Action Upgrade the FPGA revision of the line card.
Error Message%LC-3-IOTIMEOUT : RP CI-MUX FPGA read timeout (Slot [dec], Serial Channel [dec])
Explanation The cluster interconnect multiplexer FPGA on the RP could not complete a line card I/O read transaction. This error could be the result of a timing error inside the line card FPGA or the result of an incorrect line card I/O access attempt by the line card software driver. The line card has automatically been deactivated and a recovery attempt will be made. If line card recovery attempts fail five times within an hour, the line card will be deactivated without further attempts at recovery.
Recommended Action Reactivate the line card by entering the hw-module slot slot-number start command, with slot-number being the slot number of the affected card. If this command fails to reactivate the line card, copy the message exactly as it appears on the console or in the system log. Enter the show diag slot-number command, with slot-number being the slot number of the affected card. Remove the line card and place it in a different slot. If the line card fails to initialize in the new slot, 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, show tech-support and show diag slot-number commands, with slot-number being the slot number of the affected card, and your pertinent troubleshooting logs.
Error Message%LC-3-LCCREATE : Unable to create driver for Line Card type [dec] in slot [dec]
Explanation A possible memory shortage or line card hardware error has occurred.
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-3-LCI2C_ERROR : [chars] Linecard I2C bus access failed at slot [dec], status = [hex]
Explanation The line card in the specified slot has experienced an I2C access failure. This problem often occurs when the I2C has failed to gracefully terminate the previous transaction and could be the result of a hardware or software error. The line card is automatically deactivated.
Recommended Action Reactivate the line card by entering the hw-module slot slot-number start command, with slot-number being the slot number of the affected card. If this command fails to reactivate the line card, copy the message exactly as it appears on the console or in the system log. Enter the show diag slot-number command, with slot-number being the slot number of the affected card. Remove the line card and place it in a different slot. If the line card fails to initialize in the new slot, 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, show tech-support and show diag slot-number commands, with slot-number being the slot number of the affected card, and your pertinent troubleshooting logs.
Error Message%LC-2-LCRECUR : Recursive loop while getting the daughtercard info for LC type [dec]
Explanation While obtaining the daughter card information for the chassis MIB, the platform SNMP code has gone into an infinite loop.
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-2-LCSYNC : Line Card type [dec] in slot [dec] serial link sync failed.
Explanation A serial link synchronization in the specified slot has failed.
Recommended Action Check that the card is seated properly in the slot. 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-2-LCWEDGED : Line Card type [dec] in slot [dec] wedged.
Explanation The line card in the specified slot could not be initialized.
Recommended Action Check that the card is seated properly in the slot. 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-3-NOTSUPPORTED : LC in slot[dec] ([chars]) is not supported on this [chars]
Explanation This line card is not supported on this chassis or CPU card.
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-3-RECOVERY : Line card (slot [dec]) recovery in progress
Explanation A line card is recovering from a fatal error. This error could caused by one of the following conditions:
–
–
–
–
–
–
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show diag slot-number command, with slot-number being the slot number of the affected card, 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-3-REVNOTSUPPORTED : LC in slot[dec] with hw version ([dec].[dec]) is old. Requires base h/w \n revision of ([dec].[dec]) for this line card
Explanation The line card has a downlevel hardware revision. A newer hardware revision is required for this line card to work properly with the current Cisco IOS software image.
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-3-SANTAANA : Santa Ana Asic: [chars] [dec], Serial Channel [char] (slot [dec]), Error Status [hex] [chars][chars][chars]
Explanation The Santa Ana ASIC on the RP or the indicated line card has detected an error at the associated serial link. This error could be caused by the line card FPGA timing errors or by an incorrect line card serial link bring up by the line card software driver. The line card has been deactivated automatically and a recovery attempt will be made. If line card recovery attempts fail five times within an hour, the line card will be deactivated without further attempts at recovery.
Recommended Action Reactivate the line card by entering the hw-module slot slot-number start command, with slot-number being the slot number of the affected card. If this command fails to reactivate the line card, copy the message exactly as it appears on the console or in the system log. Enter the show diag slot-number command, with slot-number being the slot number of the affected card. Remove the line card and place it in a different slot. If the line card fails to initialize in the new slot, 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, show tech-support and show diag slot-number commands, with slot-number being the slot number of the affected card, and your pertinent troubleshooting logs.
Error Message%LC-2-UNDEFLC : Undefined Line Card type [dec] in slot [dec]
Explanation The software does not have a driver for the line card type in the specified slot.
Recommended Action Ensure that the image you are running is supposed to support this card. Check that the card is properly seated. If this message recurs, 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.
LDP Messages
The following are Label Distribution Protocol messages.
Error Message%LDP-3-AUTOCFG : Interface [chars] is in an unexpected autoconfig state [hex], [chars] request.
Explanation An interface is in an unexpected LDP auto config state. This could impact the LDP session running on this interface
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Error Message%LDP-5-CLEAR_NBRS : Clear LDP neighbors ([chars]) by [chars]
Explanation One or more LDP neighbor sessions has been reset
Recommended Action No action is required.
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-ISYNC : [chars]
Explanation An unexpected error happened in LDP-IGP Synchronization operation.
Recommended Action Copy the message exactly as it appears and report it to your technical service representative.
Error Message%LDP-5-SP : [chars]
Explanation An informational LDP notice was generated for a Session Protection event.
Recommended Action No action is required.
LNM Messages
The following are link noise monitor for the E1T1 module messages.
Error Message%LNM-3-LNM_NULLPTR : Controller [chars], driver_data not initialized
Explanation Noise monitoring could not be properly set up for this controller.
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%LNM-2-REMEXCEED : Interface [chars], noise exceeded removal LCV threshold [dec] / PCV threshold [dec], duration [dec]
Explanation The noise level on the E1 or T1 link has exceeded the maximum threshold that would require removal of the link. However, the link was not removed because it is the last link on a multilink bundle. This message indicates that the quality of the link is very poor.
Recommended Action Contact the service provider for the T1/E1 link to remedy the situation immediately.
Error Message%LNM-2-REMFAILED : Interface [chars], Link is not an active MLP member link.
Explanation The noise level on the E1 or T1 link has exceeded the maximum threshold that would require removal of the link. However, the link was not removed because it is not an active MLP member link. This message indicates that the quality of the link is very poor.
Recommended Action Contact the service provider for the T1/E1 link to remedy the situation immediately.
Error Message%LNM-2-REMIMPROVE : Interface [chars], noise improved below LCV removal threshold [dec] / PCV threshold [dec], duration [dec]
Explanation The noise level on the E1 or T1 link has improved and has gone below the maximum threshold that would require removal of the link.
Recommended Action No action is required.
Error Message%LNM-2-REMOVE : Interface [chars] removed, noise exceeded LCV threshold [dec] / PCV threshold [dec], duration [dec]
Explanation The noise level on the E1 or T1 link has exceeded the maximum threshold that requires removal of the link.
Recommended Action Contact the service provider for the T1/E1 link to remedy the situation immediately.
Error Message%LNM-2-RESTORE : Interface [chars] restored, noise improved below LCV removal threshold [dec] / PCV threshold [dec], duration [dec]
Explanation The noise level on the E1 or T1 link has improved and has gone below the maximum noise threshold that would require removal of the link.
Recommended Action No action is required.
Error Message%LNM-2-RESTOREFAILED : Interface [chars], Failed to restore link
Explanation An error was detected while a serial link was being restored whose noise level had gone below the maximum noise threshold that would require removal of the link.
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%LNM-4-WARNEXCEED : Controller [chars], noise exceeded LCV warning threshold [dec] / PCV threshold [dec], duration [dec]
Explanation The noise level on the E1 or T1 link has exceeded the maximum threshold that would require removal of the link. This message indicates that the quality of the link is very poor.
Recommended Action Contact the service provider for the T1/E1 link to remedy the situation.
Error Message%LNM-4-WARNIMPROVE : Controller [chars], noise improved below LCV threshold [dec] / PCV threshold [dec], duration [dec]
Explanation The noise level on the E1 or T1 link has improved and has gone below the maximum noise threshold that would require removal of the link.
Recommended Action No action is required.
MARS_NETCLK Messages
The following are Network clock system messages.
Error Message%MARS_NETCLK-3-CLK_SWITCH : [chars] of Controller [chars] Clock during Clock Switching has failed
Explanation An error occurred while the system was switching from one clock to another.
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%MARS_NETCLK-3-CLKRATE_NET : Configure clock rate network before network-clock-select on [chars]
Explanation The clock rate network defines the clock to be derived from the DTE or to be generated by the DCE
Recommended Action Configure the clock rate network.
Error Message%MARS_NETCLK-3-HOLDOVER : [chars] Holdover for Controller [chars]
Explanation The current clock source signal is not within the configured range.
Recommended Action Ensure that a valid clock has been provided to the controller. If this message recurs, 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%MARS_NETCLK-3-HOLDOVER_TRANS : Holdover timer exceeded for Controller [chars]
Explanation The current clock source signal is not within the configured range, and the system has transferred to another clock source.
Recommended Action Ensure that a valid clock has been provided to the controller. If this message recurs, 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.
MARVEL_HM Messages
The following are platform-dependent health monitor rules messages.
Error Message%MARVEL_HM-3-HM_RULES_RELOAD : Health Monitor causing a reload due to [chars]
Explanation The health monitor rules are causing a reload.
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%MARVEL_HM-3-INFORM_ACTIVE_AND_RELOAD_ERR : Attempt to inform Active and reload this unit failed
Explanation An attempt to inform the active unit and then perform a reload of the standby unit has failed.
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.
MASTER_LED Messages
The following are master LED messages.
Error Message%MASTER_LED-3-(-1) : Failed to create the '[chars]' process to turn on the Master LED
Explanation An internal error has occurred. A Cisco IOS process cannot be created to light the active LED on the front panel of the RSC. The active LED is not lit when the RSC becomes a active controller.
Recommended Action If possible, reload the RSC to recover from the error. If this message recurs, 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.
MBUS Messages
The following are CMCC maintenance bus (MBus) messages.
Error Message%MBUS-3-INCORRECT_CONT_ID : The programmed MBUS CONTROLLER ID [hex] does notmatch the gmac version [chars].
Explanation The MBus controller ID should match the GMAC version.
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%MBUS-3-MSGTOOBIG : Message type [int] to [int] has length [int] (exceeds [int])
Explanation A received MBus message exceeds the maximum size of 254 bytes. This error indicates a software defect.
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.
MCAST Messages
The following are Layer 2 multicast messages.
Error Message%MCAST-6-GC_LIMIT_EXCEEDED : IGMP snooping was trying to allocate more Layer 2 entries than what allowed ([dec])
Explanation The allocation of Layer 2 entries is bounded to prevent IGMP snooping from hogging the system resources.
Recommended Action Fewer IP groups need to be sent, because even the groups that go beyond the limit are not learned from IGMP snooping. Another alternative is to set the limit from the configuration mode by entering the ip igmp snooping l2-entry-limit <max-entries> command. Increasing the value of max-entries could cause a crash due to high use of system resources.
Error Message%MCAST-6-IGMP_CGMP_MODE : IGMP snooping now is running in IGMP_CGMP mode on vlan [dec]
Explanation IGMP snooping has detected a switch or a router that uses the CGMP protocol. The system has changed to a mode that allows that device to work.
Recommended Action No action is required.
Error Message%MCAST-6-IGMP_ONLY_MODE : IGMP snooping now is running in IGMP_ONLY mode on vlan [dec]
Explanation IGMP snooping is running on a network where there are no devices that use the CGMP protocol so it can run in a mode with no support for CGMP.
Recommended Action No action is required.
MCT1E1 Messages
The following are CT1/CE1 shared port adapter messages.
Error Message%MCT1E1-3-INITFAIL : MCT1E1 (bay [dec]), Init Failed at [chars] - line [dec] arg [hex]
Explanation The VPA failed to complete its hardware initialization.
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.
MCX Messages
The following are voice port adapter messages.
Error Message%MCX-2-TXBADVC : [chars] at Address [hex]\n
Explanation The CHOPIN VIP multi-channel port adapter contained an invalid Tx VC.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support and show controllers vip slot-number tech-support output commands, with slot-number being the slot number of the affected port adapter. 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.
MEM_HM Messages
The following are memory health monitor messages.
Error Message%MEM_HM-3-HM_OPERATION_FAILED : Failed to [chars] [chars] for Low [chars] Rule.
Explanation The memory HM subsystem has failed a health monitor operation. The health monitor rule is not operational. This error does not have any adverse effects on memory operations or the health monitor.
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%MEM_HM-3-HM_REGISTRATION_FAILED : The Memory subsystem failed to register with HM.
Explanation Registration of the memory HM subsystem with the health monitor has failed. No memory-related HM rules are created.
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.
MEM_MGR Messages
The following are memory management messages.
Error Message%MEM_MGR-3-MEM_MGR_EXCEED_MAX : memory pool exceeds maximum ([dec] bytes) allowed.
Explanation An attempt was made to allocate a buffer from a memory pool that has reached its maximum limit. The affected memory pool is specified in the message text.
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%MEM_MGR-3-MEM_MGR_INVALID : The Memory Management code encounters an invalid parameter.
Explanation The Memory Management code has received an invalid parameter from its caller.
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%MEM_MGR-3-MEM_MGR_NOMEM : Out of memory
Explanation The system has exhausted its available memory.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. 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.
MEMSCAN Messages
The following are memory scan messages.
Error Message%MEMSCAN-3-INHEAD : Parity error([hex]) found in block header
Explanation A parity error has been found in a critical field of a block header.
Recommended Action Schedule a reboot of the system to clear memory as soon as possible. If this parity error is accessed by the router during normal operation, the router will crash. If more parity errors are found at this address after the reboot, replace the DRAM in the router or the processor board.
Error Message%MEMSCAN-3-NOHEAD : No block header for parity error([hex]) until [hex]
Explanation A parity error has been found for an address that has no block header.
Recommended Action Schedule a reboot of the system to clear memory as soon as possible. If this parity error is accessed by the router during normal operation, the router will crash. If more parity errors are found at this address after the reboot, replace the DRAM in the router or the processor board.
METS Messages
The following are memory-leak analysis, system-related messages.
Error Message%METS-3-BADMETHOD : Cannot process [chars] method [int]
Explanation A method list function encountered a method list that was unknown or that could not be handled.
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%METS-2-INITFAIL : Can't start analysis
Explanation The requested operation failed because of a lack of resources. The shortage might be temporary.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration. Retry the commands.
Error Message%METS-3-NOREGION : No region found: [chars]
Explanation A resource failure has occurred. A region has not been found.
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%METS-3-NULLPOOL : Can't process null pool: [chars]
Explanation A resource failure has occurred. The region has a null pool.
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.
MFIB Messages
The following are Multicast Forwarding Information Base (MFIB) messages.
Error Message%MFIB-3-ADJ_CREATE_FAIL : Multicast adjacency creation failed for [chars]
Explanation The MFIB has failed to create a multicast adjacency. MFIB fast switching is not available on the interface.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%MFIB-3-ADJ_FAST_CREATE_FAIL : Multicast fast-interface creation failed for [chars]
Explanation The MFIB has failed to create an interface data structure for fast switching. MFIB fast switching is not available on the interface.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%MFIB-6-MRIB_DISC : Mrib diconnected, ([chars],[chars]) event cancelled
Explanation A packet triggering a data-driven event has been received, but the connection to the MRIB was down. The notification has been canceled.
Recommended Action No action is required.
Error Message%MFIB-3-MRIB_ENTRY_FAIL : Entry-creation failed for [chars],[chars]
Explanation The MFIB has attempted to create an entry as a result of a MRIB update, but the operation failed because of a memory shortage.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%MFIB-3-MRIB_INTRF_FAIL : Entry-update failed for [chars],[chars]
Explanation The MFIB has attempted to update an entry because of an MRIB update, but the operation failed because of a memory shortage.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%MFIB-3-MRIB_OPEN_FAIL : MRIB connection-open failed
Explanation The MFIB has failed to open a connection with the MRIB.
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%MFIB-3-MRIB_REG_FAIL : MRIB registration failed
Explanation The MFIB has failed to register with the MRIB.
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%MFIB-3-MRIB_UNBIND_FAIL : MRIB unbind failed
Explanation The MFIB has failed to unbind from the MRIB.
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%MFIB-3-MRIB_UPD_FAIL : Mrib notification failed for ([chars],[chars])
Explanation A packet triggering a data-driven event has been received, but the attempt to notify the MRIB has failed.
Recommended Action If this message recurs, 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%MFIB-3-NETWORK_GET_FAIL : MFIB can not get network offset: datagram [hex]; network [hex]
Explanation The MFIB failed to find a suitable packet network offset.
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%MFIB-3-NETWORK_SET_FAIL : MFIB can not set network offset: datagram [hex]; length [dec]; offset [dec]
Explanation The MFIB failed to set an offset within the packet.
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%MFIB-6-PAK_TOO_SHORT : Packet too short from [chars], datagram size [dec], tl [dec]
Explanation An IP/IPv6 packet that was received is too short.
Recommended Action No action is required.
Error Message%MFIB-3-TBL_RM_FAIL : MRIB table deletion failed
Explanation The MFIB has failed to retrieve the table that is to be deleted.
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.
MFIB_STATS Messages
The following are MFIB statistics messages.
Error Message%MFIB_STATS-2-MFIB_STATS_LC_FAILED_GET_COUNTERS : Linecard failed in getting counters due to null table. af = [int], v6 def tbl [hex], v4 def tbl [hex]
Explanation The line card has failed in retrieving entry counters because a table was of a null value.
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%MFIB_STATS-2-MFIB_STATS_LC_FAILED_GET_IPC_MSG : Linecard failed allocating ipc message buffer
Explanation The line card failed to allocate a buffer for the purpose of sending statistics.
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%MFIB_STATS-2-MFIB_STATS_LC_FAILED_SEND_MSG : Linecard failed in sending msg to the Route Processor error = [chars]
Explanation The line card has failed in sending a statistics message to the Route Processor.
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%MFIB_STATS-2-MFIB_STATS_RP_FAILED_GET_IPC_MSG : RP failed allocating ipc message buffer for linecard, slot = [dec]
Explanation The Route Processor failed to allocate a buffer to retrieve line card statistics.
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%MFIB_STATS-2-MFIB_STATS_RP_FAILED_REPLY_MSG : RP received reply with error status from linecard, slot = [dec]
Explanation The Route Processor received a reply in a statistics message from a line card that contained one or more errors.
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.
MGCP_APP Messages
The following are Media Gateway Control Protocol (MGCP) application-specific messages.
Error Message%MGCP_APP-6-MGCPAPP_FALLBACK_ACTIVATED : The gateway is in fallback mode\n
Explanation Communication with the call agent has been disrupted.
Recommended Action Reestablish the connectivity between the gateway and the CA.
Error Message%MGCP_APP-6-MGCPAPP_FALLBACK_DEACTIVATED : The gateway is out of fallback mode\n
Explanation Communication with call the call agent has been reestablished.
Recommended Action No action is required.
Error Message%MGCP_APP-6-MGCPAPP_FALLBACK_TIMER_FAIL : Unable to start fallback timer\n
Explanation The keepalive message timer could not be started.
Recommended Action Check the size of available memory to ensure that there is enough free memory.
MGCP_RF Messages
The following are Media Gateway Control Protocol (MGCP) High Availability messages.
Error Message%MGCP_RF-3-RF_REG_FAILED : RF registration for the MGCP RF client failed with return code [int]
Explanation The MGCP RF client has failed to register properly with RF. This condition should not occur and should be reported.
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%MGCP_RF-3-SEND_MSG_FAILED : The MGCP RF client failed to send a message to the peer system (op [int])
Explanation The MGCP RF client could not send a message to the peer (standby or active) system and bulk synchronization might not be complete. This condition should not occur and should be reported.
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.
MHA Messages
The following are Marvel high availability messages.
Error Message%MHA-3-UNKNOWN_RED_MODE_VALUE : Unknown AS5850 Redundancy Mode value [dec] for Redundancy Mode [chars]
Explanation The platform's HA infrastructure has encountered an internal error related to the current redundancy mode. This condition should not occur and indicates a software problem.
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.
MHA_LINE Messages
The following are Marvel high availability line messages.
Error Message%MHA_LINE-3-BAD_PEER_IPC_PORT : Cannot open the peer [chars] IPC port with [chars] error.
Explanation The test command could not be sent because the peer IPC port could not be opened.
Recommended Action Ensure that the peer RSC is operational and active. Ensure that the RSC is operating properly. If this message recurs, 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%MHA_LINE-3-IPC_MSG_ERROR : IOSDIAGS IPC messsage received with [chars] error.
Explanation The IPC message for the MHA line diagnostic test is invalid.
Recommended Action Ensure that the peer RSC is operational and active. Ensure that the RSC is operating properly. If this message recurs, 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%MHA_LINE-3-IPC_PORT_CREATE_ERROR : Named IPC port for [chars] could not be created with [chars] error.
Explanation A named IPC port could not be created.
Recommended Action Ensure that the peer RSC is operational and active. Ensure that the RSC is operating properly. If this message recurs, 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%MHA_LINE-3-IPC_PORT_REG_ERROR : Named IPC port for [chars] could not be (delayed) registered with [chars] error.
Explanation A named IPC port could not be registered.
Recommended Action Ensure that the peer RSC is operational and active. Ensure that the RSC is operating properly. If this message recurs, 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%MHA_LINE-3-IPC_REPLY_ERROR : Cannot send a IPC reply after receiving a request type [dec] with [chars] error.
Explanation An IPC reply could not be sent.
Recommended Action Ensure that the peer RSC is operational and active. Ensure that the RSC is operating properly. If this message recurs, 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%MHA_LINE-3-NEGFAILED : HA line negotiation failed. RSC7 is being reset to prevent deadlock
Explanation During system initialization, the two RSCs in the system determine which RSC will become the primary (and, later, the active) RSC. If there is a glare condition during this determination, RSC7 should perform an operation to make the other RSC the primary RSC. If RSC7 does not perform this operation, RSC6 will reboot RSC7 to prevent a deadlock condition.
Recommended Action Ensure that both RSCs are running Cisco IOS software that can support HA. The images should be the same version of Cisco IOS software, unless an upgrade is in progress. If the two software images are the same version, or if this message recurs, 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%MHA_LINE-3-NODEBPROCESS : HA line debouncing process failed to start
Explanation During system initialization, the process used to "debounce" the HA line for the Cisco AS5850 could not be created. This condition might be caused by a lack of available system memory. As a result of this condition, EHSA negotiation cannot take place. No redundancy modes can be used. If this message recurs, it can be indicative of a programming error in the Marvel High Availability subsystem that is causing too much memory to be used for this subsystem.
Recommended Action If this message recurs, 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%MHA_LINE-3-NONEGPROCESS : HA line negotiation process failed to start
Explanation During system initialization, the process used to "debounce" the HA line for the Cisco AS5850 could not be created. This condition might be caused by a lack of available system memory. As a result of this condition, EHSA negotiation cannot take place. No redundancy modes can be used. If this message recurs, it can be indicative of a programming error in the Marvel High Availability subsystem that is causing too much memory to be used for this subsystem.
Recommended Action If this message recurs, 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.
MHA_RF Messages
The following are Marvel high availability (MHA) redundancy feature (RF) interactive messages.
Error Message%MHA_RF-3-HANDOVER_INVALID : The redundancy handover command cannot be executed: [chars]
Explanation An error occurred during the RSC's hand-over of owned slots to the peer RSC.
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%MHA_RF-3-INTERNAL_ERROR : AS5850 HA internal error: [chars]
Explanation The platform's HA infrastructure has detected an internal error. This condition should not occur and indicates a software problem.
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.
MIC Messages
The following are port adapter messages.
Error Message%MIC-7-ADD_SERIAL_NUM : Added serial number in position [dec]
Explanation The system has found a unique serial number associated with the MIC that has been discovered and has added it to the list of "in use" serial numbers to check for possible serial number duplication.
Recommended Action This is an informational message only. No action is required.
Error Message%MIC-2-AUTHENTICATE_FAIL : Authentication failed for device ID #[dec]
Explanation The MIC could not be authenticated because of an altered or corrupt EEPROM.
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%MIC-7-AUTHENTICATE_PASS : Device ID #[dec] authenticated
Explanation The device has been authenticated.
Recommended Action This is an informational message only. No action is required.
Error Message%MIC-2-BADIDB : MIC interface idb incorrect, [hex]
Explanation The mobile interface card system control block (PASCB) data structure indicates a zero interface descriptor block (IDB).
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%MIC-2-BADINTERFACE : Out of range PCI Adaptor interface, [dec] on bay [dec]
Explanation The software specified an out-of-range mobile interface card interface port.
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%MIC-2-BADMIC : MIC interface slot incorrect, [hex]
Explanation An incorrect mobile interface card interface slot has been specified.
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%MIC-2-BADMIC2 : PA MIC null adapter, [hex]
Explanation A null mobile interface card interface has been specified.
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%MIC-2-BADMICBAY : Out of range PCI Adaptor bay [dec]
Explanation The software specified an out-of-range bay for the mobile interface card.
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%MIC-3-CONFIG : Recommended MIC configuration exceeded only [dec] MIC's are allowed on bus [dec]\n
Explanation The total number of mobile interface cards exceeds the capacity of this system.
Recommended Action Refer to the configuration guidelines for the maximum number of mobile interface cards allowed for the system.
Error Message%MIC-3-DEACTIVATED : MIC in bay [[dec]] is deactivated
Explanation The mobile interface card is being deactivated.
Recommended Action If this change was not requested, 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%MIC-3-DUP_SERIAL_NUM : Authentication failed due to duplicate serial number
Explanation A mobile interface card has been discovered in the system that uses the same serial number as another mobile interface card in the same system. This duplication might be caused by copying of the EEPROM contents from another EEPROM or by a manufacturing error.
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%MIC-2-EEPROM : EEPROM read failed for device ID #[dec]
Explanation The system failed to read the EEPROM. This error could be caused by either a missing EEPROM on the mobile interface card or a hardware problem.
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%MIC-3-MICCREATE : Unable to create driver for MIC type [dec] in bay [dec]
Explanation A possible memory shortage or adapter hardware error has occurred.
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%MIC-3-NOTSUPPORTED : MIC in slot[dec] ([chars]) is not supported on this platform [chars]
Explanation This MIC is not supported on this chassis or CPU card.
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%MIC-2-PCI_CONFIG_FAIL : Failed to configure device #[dec]
Explanation The PCI configuration registers were not successfully configured.
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%MIC-7-PCI_CONFIG_PASS : Device #[dec] successfully configured
Explanation The PCI configuration registers have been successfully configured.
Recommended Action This is an informational message only. No action is required.
Error Message%MIC-4-PCIVALID : PCI activation failed, bay [dec], [hex]
Explanation The system received an invalid PCI signal from the MIC. This condition is probably caused by a hardware failure.
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%MIC-3-REVNOTSUPPORTED : MIC in slot[dec] ([chars]) requires base h/w revision of ([dec].[dec]) for this [chars]
Explanation A newer hardware revision of the mobile interface card is required for functional operation on this mobile router.
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%MIC-0-RUPTCONFLICT : Conflict detected when trying to install [chars] interrupt handler, bay [dec].
Explanation An attempt was made to register an interrupt handler for either a nonexistent port adapter or an incorrect interrupt priority level.
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%MIC-3-SLOTNOTSUPPORTED : The MIC cannot operate when the rotary switch is in position [dec]. Change the switch position to one of the supported, unused positions 0-[dec]
Explanation The mobile interface card cannot operate with the switch in the position noted.
Recommended Action Change the switch position to one of the supported, unused positions. To identify the slot and switch positions supported by this MIC, refer to the configuration guide.
Error Message%MIC-2-UNDEFIO : Unsupported I/O Controller (type [dec]) in I/O Bay. The I/O Controller network interfaces will be unavailable.
Explanation The software does not have a driver for the type of mobile interface card in the specified bay.
Recommended Action Ensure that the image you are running is supposed to support this card. Check to see that the card is properly seated. If this message recurs, 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%MIC-2-UNDEFMIC : Undefined MIC type [dec] in bay [dec]
Explanation The software does not have a driver for the type of mobile interface card in the specified bay.
Recommended Action Ensure that the image you are running is supposed to support this card. Check to see that the card is properly seated. If this message recurs, 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.
MICA Messages
The following are Modem ISDN Channel Aggregation (MICA) messages.
Error Message%MICA-1-BRDDMAWARN : Slot [dec] MICA Board reports a DMA warning: [dec]
Explanation A MICA modem board has reported a DMA reset.
Recommended Action If this message recurs, 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%MICA-1-BRDRECOVER : Slot [dec] MICA Board requested recovery.
Explanation A MICA modem board has requested a recovery.
Recommended Action If this message recurs, 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%MICA-1-BRDWARNING : Slot [dec] MICA Board reports a warning: [dec]
Explanation A MICA modem board has reported a warning.
Recommended Action If this message recurs, 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.