-
Cisco IOS Release 12.0S System Message Guide
-
System Messages Overview
-
AAAA through AUDIT messages
-
AUTORP through C10KSDCC messages
-
C10K_TOASTER through CBUS messages
-
CE3 through CPUIF messages
-
CRYPTO through ECC messages
-
EDGE through EE192 messages
-
EELC through ENV_MON messages
-
ESMP through FM messages
-
FR through GLCSPA messages
-
GRP through GRPSPA messages
-
GRP_CHOCX through GT96K_FE messages
-
HA through I82543 messages
-
ICC through IPV6FIB messages
-
IP_VRF through LC_CHOCX messages
-
LCCOREDUMP through LCINFO messages
-
LCLOG through MBUSFLASH messages
-
MCC192 through MPLS_TE_LM messages
-
MPLS_TE_PCALC through PM3386 messages
-
PM622 through PRP2 messages
-
PS through RSP messages
-
RSVP through SW_MGR messages
-
SYS through TCAM_MGR messages
-
TCATM through XCPA messages
-
Glossary of Acronyms
-
Table Of Contents
C10K1_QUEUE_CFG_GENERAL Messages
C10K2_QUEUE_CFG_GENERAL Messages
C10K_QUEUE_CFG_GENERAL Messages
AUTORP Messages
The following are Protocol Independent Multicast (PIM) version 2 AUTORP messages.
Error Message%AUTORP-5-CRP_REMOVED : C-RP [IP_address] on interface [chars] has been removed
Explanation An IP address on the interface specified on the error message has been removed. This has been performed because either the PIM has been disabled on the interface, or the interface card has been removed.
Recommended Action No action is required.
Error Message%AUTORP-5-MAPPING : RP for [IP_address]/[dec] is now [IP_address]
Explanation A new RP has been elected for the subject group prefix.
Recommended Action No action is required.
Error Message%AUTORP-4-OVERLAP : AutoRP [chars] packet, group [IP_address] with mask [IP_address] removed because of multicast boundary for [IP_address] with mask [IP_address]
Explanation The multicast boundary has a longer network mask than the group that is encoded with Auto-RP.
Recommended Action Use positive permit clauses in the AutoRP access control list.
BCM Messages
The following are BCM controller messages.
Error Message%BCM-4-ECC_L2CACHE : Corrected ECC from L2 cache
Explanation A soft-parity error from the Layer 2 cache has been detected and corrected. Normal system operation should continue.
Recommended Action If there is a regular or sustained occurrence of this message, 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%BCM-4-ECC_MEMORY : Corrected ECC from memory
Explanation A soft-parity error from the memory has been detected and corrected. Normal system operation should continue.
Recommended Action If there is a regular or sustained occurrence of this message, 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.
BFR_GOODIEMGR Messages
The following are BFR Goodie Manager messages.
Error Message%BFR_GOODIEMGR-3-API_ERROR : [chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%BFR_GOODIEMGR-3-DOWNLOAD_ERROR : [chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%BFR_GOODIEMGR-3-EVENT_ERROR : [chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%BFR_GOODIEMGR-3-INTERNAL_ERROR : [chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%BFR_GOODIEMGR-5-INVALID_FRAG : [chars]
Explanation Unavailable.
Recommended Action Unavailable.
BFRP Messages
The following are BFRP messages.
Error Message%BFRP-3-L2FWD : [chars]
Explanation BFRP L2FWD specific error messages.
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.
BFRP_LB Messages
The following are BFRP link bundling messages.
Error Message%BFRP_LB-3-FEATURE_FAIL : LinkBundling: [chars] feature failed
Explanation An exception was encountered with link bundling. The feature for which the regular operation has failed is specified in the error message. The specified feature may not be operational.
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%BFRP_LB-3-MALLOC_FAIL : Memory allocation failure for [chars]
Explanation Memory allocation has failed for the link bundling application.
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%BFRP_LB-3-NO_CHANNEL_IDB : No matching channel interface for the member: [chars]
Explanation No matching channel interface for the member interface has been found. If the messages are persistent and frequent, this condition indicates continued packet loss for the channel interface. If this message appears a few times over a small period of time during specific operations such as user configurations or reloads, this condition is most likely called by timing issues during initialization, and the packet loss might be temporary.
Explanation If this condition occurs during a user configuration or system reload, no action is required. If the message is frequent, reconfigure the member or channel. 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.
BFRP_RLC Messages
The following are BFRP redundant line card messages.
Error Message%BFRP_RLC-3-NULL_CARVE_SLOT : \n Slot pointer received for buffer carve handling is NULL.
Explanation A NULL slot information pointer was passed to the function that performs redundant slot pair handling during a buffer recarve.
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%BFRP_RLC-3-RLC_NULL_PRI_SP : \nNULL slot information pointer returned for primary slot [int]
Explanation The lookup to determine a slot information database pointer returned NULL for the slot number of the primary slot in a redundant slot pair.
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.
BGP Messages
The following are Border Gateway Protocol (BGP) messages.
Error Message%BGP-3-ADDPATH : Number of paths per prefix exceeded allowed maximum of [dec]
Explanation The number of paths per prefix has exceeded the maximum that is allowed. The maximum number of prefixes is specified in the message text. This message indicates that BGP is receiving the same prefix from too many neighbors.
Recommended Action Attempt to restrict the number of neighbors that are sending the same prefix. You can restrict the number of neighbors advertising the same prefix by having robust inbound filters.
Error Message%BGP-4-AFIMPORT : [chars] prefixes imported to [chars] vrf reached the limit [dec]
Explanation The number of prefixes that were imported from another address family to a VRF has reached the configured limit.
Recommended Action Check the number of imported prefixes from the address family and increase the limit if required, or check to see that the route map was imported correctly into the VRF.
Error Message%BGP-3-BADROUTEMAP : Bad parameters in the route-map [chars] applied for [chars]
Explanation Invalid parameters have occurred in the route map.
Recommended Action Correct the route map.
Error Message%BGP-3-BGP_INCONSISTENT : [chars] Inconsistent [chars]
Explanation An inconsistency in the data structures has occurred. This condition is a rare situation and is a result of internal 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%BGP-6-BIGCHUNK : Big chunk pool request ([dec]) for [chars]. Replenishing with malloc
Explanation A large chunk pool has been requested. If the static chunk pools size cannot service the request, it will be serviced with a memory allocation (malloc).
Recommended Action This is an informational message only. If this message is cause for concern, copy the message exactly as it appears on the console or in the system log. Enter the show chunk and show bgp summary commands to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information 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%BGP-5-DAMPENING_DECAY_TIME : Decay time from maximum penalty to suppress penalty is [dec] secs. Maximum penalty: [dec], suppress penalty: [dec]
Explanation The configured dampening parameters may not be feasible. The time window between the maximum penalty and suppress penalty may be low.
Recommended Action If the decay time from the maximum penalty to suppress penalty appears to be too low, increase the half-life time or maximum penalty values.
Error Message%BGP-5-DAMPENING_HIGH_MAX_PENALTY : Maximum penalty ([dec]) is more than allowed maximum ([dec]). Dampening is OFF
Explanation The configured dampening parameters may not be feasible. Maximum penalty is more than allowed maximum. Dampening will be off.
Recommended Action Depending on the value of maximum penalty, adjust the maximum suppress time. Since the maximum penalty is more than allowed maximum, reduce the maximum suppress time. The maximum penalty should be greater than the suppress penalty, but less than maximum allowable penalty.
Error Message%BGP-5-DAMPENING_LOW_MAX_PENALTY : Maximum penalty ([dec]) is less than suppress penalty ([dec]), Dampening is OFF
Explanation Configured dampening parameters may not be feasible. Maximum penalty is less than configured suppress penalty. Dampening will be off.
Recommended Action Depending on the value of maximum penalty adjust maximum suppress time. Since maximum penalty is less than suppress penalty, increase maximum suppress time. Maximum penalty should be greater than suppress penalty but less than maximum allowable penalty.
Error Message%BGP-4-INCORRECT_TTL : Discarded message with TTL [dec] from [chars]
Explanation A BGP message was received with a TTL value that is not within the acceptable configuration parameters.
Recommended Action If you consider the message to be valid, modify the TTL security configuration to an appropriate value. Otherwise, this message could be coming from a spurious source. If you determine that this message is coming from a spurious source, locate and block the source of the messages.
Error Message%BGP-3-INSUFCHUNKS : Insufficient chunk pools for [chars], requested size [dec]
Explanation The size of the static chunk pools are not correct. This condition is caused by an internal software issue.
Recommended Action Collect information regarding chunks and BGP summary.
Error Message%BGP-3-MARTIAN_IP : [chars] Martian prefix [chars] in [chars]
Explanation The specified martian prefix has been found in the BGP message. This condition indicates that there is a problem on the remote 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%BGP-4-MAX_EXTCOMM_EXCEED : Exceeded limit of [dec] extended communities per advertised prefix
Explanation An attempt was made to advertise a prefix with an extended community attribute that contained more extended communities than the allowed limit.
Recommended Action Reduce the configured number of Route Targets or other extended communities that will be added to prefix advertisements so that the limit is not exceeded.
Error Message%BGP-3-MAXPATHS : Too many parallel paths for [IP_address][IP_netmask], maximum is [int]
Explanation The number of parallel paths has exceeded the configured limit.
Recommended Action Increase the number of parallel paths allowed.
Error Message%BGP-4-MAXPFX : No. of [chars] prefix received from [IP_address] reaches [int], max [int]
Explanation The number of prefixes received from a neighbor has reached the warning limit.
Recommended Action Check the number of prefixes that were received from the neighbor and determine whether the limit should be increased.
Error Message%BGP-3-MAXPFXEXCEED : No. of [chars] prefix received from [IP_address]: [int] exceed limit [int]
Explanation The number of prefixes received from a neighbor has exceeded the configured limit.
Recommended Action Check the number prefixes received from the neighbor and determine whether the limit should be increased.
Error Message%BGP-3-MPLS_NOIDB : No route found for BGP peer [IP_address]
Explanation During the check to see whether a given interface is supported for IPv4 BGP MPLS labeling, the next hop interface was not found. The route for reaching the BGP peer is not present in the routing table.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging (and show tech-support) commands and your pertinent troubleshooting logs.
Error Message%BGP-4-MPLS_UNSUPPORTED : IPv4 BGP MPLS labeling is not supported on interface [chars]
Explanation IPv4 BGP MPLS labeling is not supported on the interface. This message appears when this capability is attempted to be negotiated on an interface where this functionality is not supported. As a result, address family AFI or SAFI 1/4 could not be not negotiated over this BGP connection and no IPv4 labeled prefixes could be exchanged.
Recommended Action See the Release Notes for Cisco IOS software, Release 12.0 S for the supported interface types for IPv4 BGP MPLS labeling functionality.
Error Message%BGP-4-NBRTRACK : Route Tracking failed on memory. Neighbor tracking for route-fall-over will stop
Explanation The route tracking system failed to allocate sufficient memory for the route failover application. The neighbor route fall-over application has been deconfigured and will stop tracking neighbor routes. Memory used for the neighbor route fall-over application has been deallocated.
Recommended Action If you determine that the system is stable, reconfigure the neighbor route failover application. If you get this message, neighbor route-failover has been deconfigured.
Error Message%BGP-3-NEGCOUNTER : Prefix-accepted counter negative for peer [IP_address], prefix [IP_address]/[IP_address]
Explanation The number of prefixes received from a neighbor is negative.
Recommended Action Check the prefixes received from the neighbor.
Error Message%BGP-6-NLRI_MISMATCH : Mismatch NLRI negotiation with peer [IP_address]
Explanation The configurations of the NLRI and the BGP peer are not compatible.
Recommended Action Verify that the configuration of the BGP peer is correct. Make any necessary changes and try again. If the problem persists, copy the message exactly as it appears on the console or in the system log. Enter the show tech-support command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%BGP-3-NOBITFIELD : Could not allocate bitfield. Cannot open session to [chars]
Explanation The allocation of the neighbor index for this neighbor has failed 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.
Error Message%BGP-3-NOTIFICATION : [chars] neighbor [IP_address] [dec]/[dec] ([chars]) [dec] bytes [chars]
Explanation An error condition has been detected in the BGP session. A notification is being sent or received and the session will be reset. This message appears only if the log-neighbor-changes command is configured for the BGP process.
Recommended Action This message represents an error in the session, and its origin should be investigated. 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%BGP-3-PFXLISTORF : Received misformatted prefixlist ORF from [IP_address]
Explanation The received prefix list ORF is formatted incorrectly.
Recommended Action Check the prefix list ORF implementation on the neighboring router.
Error Message%BGP-3-PFXORF : Received misformatted prefixlist ORF from [IP_address]
Explanation The received prefix list ORF is not formatted correctly.
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 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%BGP-5-VERSION_WRAP : bgp version wraped
Explanation The BGP table version has reached its maximum value and wrapped around.
Recommended Action This message is informational. However, frequent occurrences of such an event might indicate high error rates or high packet loss in the network and should be investigated.
Error Message%BGP-4-VPNV4NH_IF : Nexthop [IP_address] may not be reachable from neigbor [chars] - not a loopback
Explanation A vpnv4 route has been sent from this system to the IBGP neighbor specified in the error message, and the next hop is one of the directly connected physical interfaces of this system. The label for the next-hop address may be removed in the MPLS cloud one hop before the label should be removed. Since the Provider routers do not have VPN information, the Provider routers do not know where to forward packets with the BGP label. This condition could break connectivity between VPN sites.
Recommended Action Use loopback interfaces as the next hops for VPNv4 IBGP neighbors.
Error Message%BGP-4-VPNV4NH_MASK : Nexthop [IP_address] may not be reachable from neigbor [chars] - not /32 mask
Explanation A VPNv4 route has been sent to an IBGP neighbor. The next-hop address is a loopback that is not using a 32-bit (/32) network mask, OSPF is being used on the loopback, and the OSPF network type of the interface is LOOPBACK. OSPF advertises this address as a host route with a /32 mask, regardless what mask is configured. This conflicts with TDP, which uses configured masks; therefore, the TDP neighbors may not receive a tag for this route. This could break connectivity between sites that belong to the same VPN.
Recommended Action Configure the loopback that is being used as the next-hop loopback to use a 32-bit network mask (/32), or set the network type to point-to-point by entering the ip ospf network point-to-point command.
BIT Messages
The following are dynamic bit list messages.
Error Message%BIT-4-OUTOFRANGE : bit [dec] is not in the expected range of [dec] to [dec]
Explanation An invalid request was detected by the bit list 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.
BM Messages
The following are FPGA buffer manager messages.
Error Message%BM-3-QUIESCE_ERROR : port [dec] queue [chars] not empty after [dec] usecs, retry after shutting all ports on this LC
Explanation Error in FPGA Buffer Manager.
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.
BSTUN Messages
The following are block serial tunneling messages.
Error Message%BSTUN-4-DUPROUTE : Cannot define duplicate route on the \nsame group
Explanation This route command is defined on another interface that belongs to the same group. Duplicate routes cannot be defined on the same group.
Recommended Action Consider defining a new group and moving this interface into that group.
C10720_Access4GE8FE Messages
The following are Cisco 10720 4GE8FE access card messages.
Error Message%C10720_Access4GE8FE-3-FPGA_UPLOAD_FAILED : Access FPGA upload failed. Sanity register is [hex].
Explanation IOS failed to initialize a hardware FPGA device on the Access card after five consecutive attempts. This is a known problem but its occurrance is very rare.
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%C10720_Access4GE8FE-3-GB_CIRCUIT_RESET : Internal circuit [dec] has been reset.
Explanation Unavailable.
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%C10720_Access4GE8FE-3-INIT_DEVICES_FAILED : Initialisation of hardware failed.
Explanation Unavailable.
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%C10720_Access4GE8FE-2-REV1_ACCESS_NOT_SUPPORT : The Rev 1 4GE+8FE hardware is not supported in this version of IOS.
Explanation The 4GE+8FE access card hardware is not supported in the version of Cisco IOS software that is running on the system.
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.
C10720_SFP Messages
The following are Cisco C10720 Small Form Factor Pluggable (SFP) messages.
Error Message%C10720_SFP-3-BADSFP : Non-compliant SFP module.
Explanation The SFP module from this vendor does not comply with Cisco standards.
Recommended Action Obtain an SFP module from a Cisco-approved vendor.
Error Message%C10720_SFP-3-SFP_ERROR_READING : Badly inserted SFP.
Explanation An error has occurred while the system was reading from the SFP. This condition usually indicates an incorrectly inserted SFP.
Recommended Action Re-insert the SFP.
Error Message%C10720_SFP-4-SFP_EVENT_INS : SFP Module Inserted: [chars]
Explanation An SFP module has been inserted.
Recommended Action If this message is expected, no action is required. Otherwise, check the SFP module.
Error Message%C10720_SFP-4-SFP_EVENT_MISSING : SFP Module Missing: [chars]
Explanation An SFP module could not be located.
Recommended Action Check the SFP module.
Error Message%C10720_SFP-4-SFP_EVENT_REM : SFP Module Removed: [chars]
Explanation An SFP module has been removed.
Recommended Action If this message is expected, no action is required. Otherwise, check the SFP module.
Error Message%C10720_SFP-3-SFP_TX_FAULT_RECOVERY_ERROR : Laser error recovery not successful.
Explanation A laser Tx fault occurred on the SFP. The SFP could not be brought back to a normal state.
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.
C10720_SFP_DIAG Messages
The following are Cisco C10720 Small Form Factor Pluggable (SFP) diagnostic messages.
Error Message%C10720_SFP_DIAG-4-SFP_BAD_MODULE : Bad SFP module in port [int][chars]
Explanation The SFP module has failed or is faulty.
Recommended Action Check the SFP module.
Error Message%C10720_SFP_DIAG-4-SFP_DUP_MODULE : Duplicate S/N of SFP module detected in port [int][chars]
Explanation The SFP module has failed or is faulty.
Recommended Action Check the SFP module.
Error Message%C10720_SFP_DIAG-4-SFP_EVENT_INS : SFP Module Inserted: port [int]
Explanation An SFP module has been inserted.
Recommended Action If this message is expected, no action is required. Otherwise, check the SFP module.
Error Message%C10720_SFP_DIAG-4-SFP_EVENT_MISSING : SFP Module Missing: port [int]
Explanation An SFP module could not be located.
Recommended Action Check the SFP module.
Error Message%C10720_SFP_DIAG-4-SFP_EVENT_REM : SFP Module Removed: port [int]
Explanation An SFP module has been removed.
Recommended Action If this message is expected, no action is required. Otherwise, check the SFP module.
Error Message%C10720_SFP_DIAG-4-SFP_EVENT_TX_FAULT : TX FAULT signal [chars] on port [int]
Explanation The SFP module has received a transmittal (Tx) fault signal.
Recommended Action Check the SFP module.
Error Message%C10720_SFP_DIAG-4-SFP_NOT_COMPLIANT : Wrong SFP module compliance in port [int]
Explanation The SFP module is not compliant with the system.
Recommended Action Check the SFP module.
Error Message%C10720_SFP_DIAG-4-SFP_NOT_READY : SFP: Interface [chars][int]/[int] can't come up; SFP modules are not ready
Explanation The SFP modules are not ready.
Recommended Action Wait for the SFP modules to initialize (come up). Otherwise, check the SFP module.
Error Message%C10720_SFP_DIAG-2-SFP_RX_POWER_HI_ALARM : RX power high alarm
Explanation The Rx power has exceeded the configured high alarm limit.
Recommended Action Replace the SFP module.
Error Message%C10720_SFP_DIAG-4-SFP_RX_POWER_HI_WARN : RX power high warning
Explanation The Rx power has exceeded the configured high warning limit.
Recommended Action Replace the SFP module.
Error Message%C10720_SFP_DIAG-2-SFP_RX_POWER_LO_ALARM : RX power low alarm
Explanation The Rx power is lower than the configured low alarm limit.
Recommended Action Replace the SFP module.
Error Message%C10720_SFP_DIAG-4-SFP_RX_POWER_LO_WARN : RX power low warning
Explanation The Rx power is lower than the configured low warning limit.
Recommended Action Replace the SFP module.
Error Message%C10720_SFP_DIAG-2-SFP_TEMP_HI_ALARM : Temperature high alarm
Explanation The internal temperature of the SFP is higher than the configured high alarm level.
Recommended Action Replace the SFP module.
Error Message%C10720_SFP_DIAG-4-SFP_TEMP_HI_WARN : Temperature high warning
Explanation The internal temperature of the SFP is higher than the configured high warning level.
Recommended Action Replace the SFP module.
Error Message%C10720_SFP_DIAG-2-SFP_TEMP_LO_ALARM : Temperature low alarm
Explanation The internal temperature of the SFP is lower than the configured low alarm level.
Recommended Action Replace the SFP module.
Error Message%C10720_SFP_DIAG-4-SFP_TEMP_LO_WARN : Temperature low warning
Explanation The internal temperature of the SFP is lower than the configured low warning level.
Recommended Action Replace the SFP module.
Error Message%C10720_SFP_DIAG-2-SFP_TX_BIAS_HI_ALARM : TX bias high alarm
Explanation The Tx bias has exceeded the configured high alarm level.
Recommended Action Replace the SFP module.
Error Message%C10720_SFP_DIAG-4-SFP_TX_BIAS_HI_WARN : TX bias high warning
Explanation The Tx bias has exceeded the configured high warning level.
Recommended Action Replace the SFP module.
Error Message%C10720_SFP_DIAG-2-SFP_TX_BIAS_LO_ALARM : TX bias low alarm
Explanation The Tx bias is lower than the configured low alarm level.
Recommended Action Replace the SFP module.
Error Message%C10720_SFP_DIAG-4-SFP_TX_BIAS_LO_WARN : TX bias low warning
Explanation The Tx bias is lower than the configured low warning level.
Recommended Action Replace the SFP module.
Error Message%C10720_SFP_DIAG-2-SFP_TX_POWER_HI_ALARM : TX power high alarm
Explanation The Tx output power has exceeded the configured high alarm level.
Recommended Action Replace the SFP module.
Error Message%C10720_SFP_DIAG-4-SFP_TX_POWER_HI_WARN : TX power high warning
Explanation The Tx output power has exceeded the configured high warning level.
Recommended Action Replace the SFP module.
Error Message%C10720_SFP_DIAG-2-SFP_TX_POWER_LO_ALARM : TX power low alarm
Explanation The Tx output power is lower than the configured low alarm level.
Recommended Action Replace the SFP module.
Error Message%C10720_SFP_DIAG-4-SFP_TX_POWER_LO_WARN : TX power low warning
Explanation The Tx output power is lower than the configured low warning level.
Recommended Action Replace the SFP module.
Error Message%C10720_SFP_DIAG-2-SFP_VOLT_HI_ALARM : Vcc high alarm
Explanation The supply voltage has exceeded the high alarm level.
Recommended Action Replace the SFP module.
Error Message%C10720_SFP_DIAG-4-SFP_VOLT_HI_WARN : Vcc high warning
Explanation The supply voltage has exceeded the high warning level.
Recommended Action Replace the SFP module.
Error Message%C10720_SFP_DIAG-2-SFP_VOLT_LO_ALARM : Vcc low alarm
Explanation The supply voltage is lower than the configured low alarm level.
Recommended Action Replace the SFP module.
Error Message%C10720_SFP_DIAG-4-SFP_VOLT_LO_WARN : Vcc low warning
Explanation The supply voltage is lower than the configured low warning level.
Recommended Action Replace the SFP module.
C10K Messages
The following are Constellation 10K Omega messages.
Error Message%C10K-2-BADINTERFACE : Out of range Card interface, [dec] on slot [dec]
Explanation The software specified a card interface that is out of 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%C10K-3-BAD_RETURN_VALUE : call to [chars] failed with return code [dec]\n
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%C10K-2-BADRSRCNUM : Invalid resource number from PXF ([dec]). (PLEASE REPORT THIS!)
Explanation The PXF hardware diversion path specified an invalid resource number.
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%C10K-2-BADSLOT : Out of range card slot index[dec]
Explanation The software specified a card slot index that is out of 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%C10K-2-BADSLOTSUBSLOT : Out of range card slot/subslot pair[dec]/[dec]
Explanation The software specified a card slot or subslot pair that is out of 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%C10K-2-CARDRECUR : Recursive loop while getting the daughtercard info for card 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%C10K-3-CHASSIS : Unknown chassis model.
Explanation The data stored in the midplane is invalid or incomplete.
Recommended Action Contact your Cisco technical support representative to update your system.
Error Message%C10K-3-CONFIG : Recommended port adapter configuration exceeded
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%C10K-4-COOKIE : Corrupt or missing MAC address cookie\n using random base [enet]
Explanation An invalid MAC address has been detected in the backplane 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%C10K-3-DEACTIVATED : card in slot [[dec]/[dec]] disabled.
Explanation The card is being deactivated.
Recommended Action No action is required.
Error Message%C10K-1-DISCOVER_ENET : Failed to init Ethernet device [dec]
Explanation The software failed to initialize the Ethernet device on the interface card specified in the error message.
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%C10K-1-DISCOVER_SAR : Failed to init SAR device [dec]
Explanation The software failed to initialize the SAR device on the interface card specified in the error message.
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%C10K-3-EEPROM_ERROR : [chars]\n
Explanation The system cannot read from, or write to, the EEPROM.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show diag command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%C10K-3-EEPROM_INVALID : Invalid or unprogrammed [chars] EEPROM
Explanation The specified EEPROM has either not been programmed is of the wrong type.
Recommended Action Contact your Cisco customer technical support representative to replace the EEPROM.
Error Message%C10K-3-GENERAL : [chars]\n
Explanation A general C10K failure has occurred. The details in the error message text provide more information on the nature of the 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%C10K-3-IONOT0 : IO card discover in non-zero slot [dec]/[dec]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%C10K-3-IPC : [chars]: IPC Failure
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%C10K-3-IPCOPENFAILED : Couldn't open IPC port for port id [hex] slot [int]/[int]: [chars]
Explanation Information could not be obtained from a line card.
Recommended Action Reseat the line card in the slot specified in the message text.
Error Message%C10K-1-LC_ALERT : [chars]
Explanation An error involving the line card 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%C10K-2-LC_CRIT : [chars]
Explanation An error involving the line card 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%C10K-7-LC_DEBUG : [chars]
Explanation This message provides debug-level information about the line card.
Recommended Action No action is required.
Error Message%C10K-0-LC_EMERG : [chars]
Explanation A serious error involving the line card 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%C10K-3-LC_ERR : [chars]
Explanation An error involving the line card 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%C10K-6-LC_INFO : [chars]
Explanation This message provides information about the line card.
Recommended Action No action is required.
Error Message%C10K-5-LC_NOTICE : [chars]
Explanation This message provides information about the line card.
Recommended Action No action is required.
Error Message%C10K-3-LC_UNKNOWN : [chars]
Explanation An error involving the line card 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