-
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
CALLRECORD Messages
The following are Modem Call Record messages.
Error Message%CALLRECORD-3-SCM_TERSE_CALL_FAILED_REC : [chars]
Explanation An attempt to write a terse SCM call record has failed.
Recommended Action No action is required.
Error Message%CALLRECORD-3-SCM_TERSE_CALL_REC : [chars]
Explanation A terse SCM call record has been successfully written.
Recommended Action No action is required.
CALLTREAT_NOSIGNAL Messages
The following are Call Treatment (TREAT) messages.
Error Message%CALLTREAT_NOSIGNAL-3-HIGH_CPU_5SEC_LOAD : System experiencing high cpu utilization.\n
Explanation The system does not have enough CPU resources available to allocate a new resource.
Recommended Action Ensure that the call setup rate is within the supported capacity of this gateway. Enter the show processes cpu command to see which processes are consuming the most CPU capacity and, if appropriate, reduce other system activity to ease CPU demands. By default, the system will reject calls if the 5-second CPU utilization on the gateway exceeds 89 percent. The default value can be overridden by enabling call treatment and entering the call threshold global cpu-5sec command.
Error Message%CALLTREAT_NOSIGNAL-3-HIGH_CPU_AVERAGE_LOAD : System experiencing high average cpu utilization.\n
Explanation On the basis of the average CPU utilization over a 60-second interval or over an interval configured through the call threshold poll-interval command, the system does not have enough available CPU resources to accept a new call.
Recommended Action Ensure that the call setup rate is within the supported capacity of this gateway. Verify that the current call setup rate is supported on this gateway. Enter the show processes cpu command to see which processes are consuming the most CPU capacity and, if appropriate, reduce other system activity to ease CPU demands. By default, the system will reject calls if the 5-second CPU utilization on the gateway exceeds 98 percent. The default value can be overridden by enabling call treatment and entering the call threshold global cpu-avg command.
Error Message%CALLTREAT_NOSIGNAL-3-HIGH_CPU_ONE_MIN_LOAD : System experiencing high cpu utilization over one minute interval.\n
Explanation On the basis of the average CPU utilization over a 60 second interval, the system does not have sufficient available CPU resources.
Recommended Action Ensure that the call setup rate is within the supported capacity of this gateway. Enter the show processes cpu command to see which processes are consuming the most CPU capacity and, if appropriate, reduce other system activity to ease CPU demands. By default, the system will reject resource allocation if the 5-second CPU utilization on the gateway exceeds 98 percent.
Error Message%CALLTREAT_NOSIGNAL-3-HIGH_IOMEM_USAGE : System running low on I/O memory.\n
Explanation The system does not have enough free I/O memory.
Recommended Action Ensure that the gateway has the recommended amount of I/O memory for this Cisco IOS software feature set and version. Enter the show memory and show processes memory commands to see which processes are consuming the most memory. Verify that the memory usage is appropriate for these processes and, if so, reduce other system activity to ease CPU demands. The high and low thresholds for I/O memory utilization can be configured by enabling call treatment and entering the call threshold global io-mem command.
Error Message%CALLTREAT_NOSIGNAL-3-HIGH_MEMORY_USAGE : System running low on memory.
Explanation The system does not have enough free memory to allocate a new resource.
Recommended Action Ensure that the gateway has the recommended amount of memory for this Cisco IOS software feature set and version. Enter the show memory and show processes memory commands to see which processes are consuming the most memory. Verify that the memory usage is appropriate for these processes and, if so, reduce other system activity to ease CPU demands. By default, the system will reject calls if there is less than 2 percent free processor memory on the gateway. This value can be overridden by enabling call treatment and entering the call threshold global total-mem command.
Error Message%CALLTREAT_NOSIGNAL-3-HIGH_PROCMEM_USAGE : System running low on processor memory.\n
Explanation The system does not have enough free processor memory.
Recommended Action Ensure that the gateway has the recommended amount of processor memory for this Cisco IOS software feature set and version. Enter the show memory and show processes memory commands to see which processes are consuming the most memory. Verify that the memory usage is appropriate for these processes and, if so, reduce other system activity to ease CPU demands. The high and low thresholds for processor memory utilization can be configured by enabling call treatment and entering the call threshold global proc-mem command.
Error Message%CALLTREAT_NOSIGNAL-3-HIGH_TOTAL_CALLS : High call volume.\n
Explanation The system is experiencing a high call volume.
Recommended Action Perform one or all of the following actions:
•
Disable the call threshold feature.
•
•
CDMA_PDSN Messages
The following are CDMA PDSN messages.
Error Message%CDMA_PDSN-3-CMDNOTCONFIGURED : Attempt to open session without virtual-template configured
Explanation The PDSN has refused to open the session because a virtual template has not been configured.
Recommended Action Configure a virtual template by entering the cdma pdsn virtual-template command.
Error Message%CDMA_PDSN-4-CONFIG_ERROR : Master slave PDSN clustering configured or in progress.
Explanation Either the active PDSN or the standby PDSN functionality is being configured in this PDSN. The intelligent selection feature, or peer-to-peer clustering feature, cannot be configured on the same PDSN that runs either the active PDSN or the standby PDSN functionality.
Recommended Action Either do not configure the PDSN selection feature, or unconfigure either the active PDSN or the standby PDSN.
Error Message%CDMA_PDSN-3-FSDROPPAK : No session [chars]
Explanation The system cannot find a session in the FS path. The packet has been dropped. This condition indicates an internal 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%CDMA_PDSN-3-GRPPROFERROR : Group Profile contains UserClass/IpTech as MobileIP
Explanation The group profile contains a User Class or IP Tech Value of "MobileIP". MSID-based access using a group profile cannot use "MobileIP" as its User Class or IP Tech Value.
Recommended Action Check and correct the group profile in the AAA server.
Error Message%CDMA_PDSN-3-GRPPROFERROR2 : Group Profile contains VPDN attributes
Explanation The group profile contains VPDN attributes. MSID-based access using a group profile cannot have VPDN attributes.
Recommended Action Check and correct the group profile in the AAA server.
Error Message%CDMA_PDSN-1-PPPNOMEMALERT : No memory to create a vaccess
Explanation An internal CDMA PDSN PPP 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%CDMA_PDSN-4-PPPUNEXPWARNING : Unexpexted event [dec]
Explanation An internal error involving CDMA PDSN PPP processing 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%CDMA_PDSN-3-PPPVACERR : Free Virtual Access interface failure
Explanation An internal error occurred while the virtual template was being freed.
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%CDMA_PDSN-3-PREPAIDUNSUPPORTED : Prepaid is not supported by this image
Explanation A user profile using "Prepaid" was specified. "Prepaid" is not supported by this Cisco IOS software image.
Recommended Action Remove the configuration of "CRB_ENTITY_TYPE" from the user profile.
Error Message%CDMA_PDSN-3-PROFERROR1 : Group Profile error in case of UC/IP_Tech as NotDefined
Explanation MSID-based access was attempted using a group profile with "No User Class" or "IP Tech" with SPI in the profile. Access will be attempted without IPCP address negotiation.
Recommended Action Check and correct the group profile in the AAA server.
Error Message%CDMA_PDSN-3-PROFERROR2 : Group Profile error as profile has no REALM
Explanation MSID-based access was attempted using a group profile with no realm.
Recommended Action Check and correct the group profile in the AAA server.
Error Message%CDMA_PDSN-3-RPA11TO : A11 Registration Update re-transmission timed out at gre tunnel[dst:[IP_address]].
Explanation An RP(A10-A11) connectivity problem has occurred.
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%CDMA_PDSN-3-RPBADPACKET : BAD Packet : [chars]-[chars]-[dec]
Explanation An invalid packet was received from the mobile node. The format of the received packet is not included in the TR45 specifications.
Recommended Action If this message recurs consistently, 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%CDMA_PDSN-3-RPUNEXPECTEDMSG : Unknown [chars] Message Type = [dec]
Explanation The format of the received packet is not included in the TR45 specifications. This condition indicates an internal 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%CDMA_PDSN-3-SMMAXEXCEEDED : Attempt to exceed maximum [chars] allowed ([dec])
Explanation An attempt was made to exceed the maximum configured values of the PCF or session. The PDSN has refused this attempt.
Recommended Action Increase the maximum configuration value by entering the cdma pdsn maximum pcf/session command.
Error Message%CDMA_PDSN-3-SNMPSESSION : SNMP: CDMA SESSION tree creation error
Explanation The creation of an internal structure has failed. This condition was probably caused by low available memory. SNMP reporting might not work properly.
Recommended Action Reduce other activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%CDMA_PDSN-3-SNMPTREE : SNMP: CDMA PCF tree creation error
Explanation The creation of an internal structure has failed. This condition was probably caused by low available memory. SNMP reporting might not work properly.
Recommended Action Reduce other activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
CDSX_MODULE Messages
The following are network module messages.
Error Message%CDSX_MODULE-3-FDLLLOOPDOWN : Controller [chars] - FDL line loopdown code detected, deactivating line loopback.
Explanation The system has detected FDL line loopdown code on the unit. Line loopback mode is being deactivated.
Recommended Action No action is required.
Error Message%CDSX_MODULE-3-FDLLLOOPUP : Controller [chars] - FDL line loopup code detected, activating line loopback mode.
Explanation The system has detected FDL line loopup code on the unit. Line loopback mode is being activated.
Recommended Action No action is required.
Error Message%CDSX_MODULE-3-FDLLREQFAILED : Controller [chars] - Failed to put the remote end in line loopback mode via FDL.
Explanation The T1 FDL line loopup code was sent to the remote end, but the remote end did not activate line loopback mode. This condition could be caused by a problem with the controller configuration or by a physical problem with the line.
Recommended Action Check to verify that the controllers are both operational and enabled (up).
Error Message%CDSX_MODULE-3-FDLLREQOK : Controller [chars] - Remote end is put in line loopback mode via FDL.
Explanation The T1 FDL line loopup code was sent to the remote end from the unit and the remote end has successfully activated line loopback mode.
Recommended Action No action is required.
Error Message%CDSX_MODULE-3-FDLPLOOPDOWN : Controller [chars] - FDL payload loopdown code detected, deactivating payload loopback.
Explanation The system has detected FDL payload loopdown code on the unit. The payload loopback mode is being deactivated.
Recommended Action No action is required.
Error Message%CDSX_MODULE-3-FDLPLOOPUP : Controller [chars] - FDL payload loopup code detected, activating payload loopback mode.
Explanation The system has detected FDL payload loopup code on the unit. The payload loopback mode is being activated.
Recommended Action No action is required.
Error Message%CDSX_MODULE-3-FDLPREQFAILED : Controller [chars] - Failed to put the remote end in payload loopback mode via FDL.
Explanation The T1 FDL payload loopup code was sent to the remote end, but the remote end did not activate payload loopback. This condition could be caused by a problem with the controller configuration or by a physical problem with the line.
Explanation Check to verify that the controllers are both operational and enabled (up).
Error Message%CDSX_MODULE-3-FDLPREQOK : Controller [chars] - Remote end is put in payload loopback mode via FDL.
Explanation The T1 FDL payload loopup code was sent to the remote end from the unit and the remote end has successfully activated the payload loopback mode.
Recommended Action No action is required.
Error Message%CDSX_MODULE-3-IBOCLOOPDOWN : Controller [chars] - IBOC loopdown code detected, deactivating line loopback.
Explanation The system has detected IBOC loopdown code on the unit. Line loopback mode is being deactivated.
Recommended Action No action is required.
Error Message%CDSX_MODULE-3-IBOCLOOPUP : Controller [chars] - IBOC loopup code detected, activating line loopback mode.
Explanation The system has detected IBOC loopup code on the unit. Line loopback mode is being activated.
Recommended Action No action is required.
Error Message%CDSX_MODULE-3-IBOCREQFAILED : Controller [chars] - Failed to put the remote end in line loopback mode via IBOC.
Explanation The T1 IBOC loopup code was sent to the remote end, but the remote end did not activate line loopback mode. This condition could be caused by a problem with the controller configuration or by a physical problem with the line.
Explanation Check to verify that the controllers are both operational and enabled (up).
Error Message%CDSX_MODULE-3-IBOCREQOK : Controller [chars] - Remote end is put in line loopback mode via IBOC.
Explanation The T1 IBOC loopup code was sent to the remote end from the unit and the remote end has successfully activated line loopback mode.
Recommended Action No action is required.
Error Message%CDSX_MODULE-3-T1REQCANCELLED : Controller [chars] - T1 remote loopback has been cancelled.
Explanation T1 loopdown code has been sent to the remote end from this unit. The remote end is assumed to have received the loopdown code and deactivated loopback mode. However, no test is performed to ensure that the remote end has deactivated loopback mode.
Recommended Action No action is required.
CEIPNM Messages
The following are Circuit Emulation over IP Network Module messages.
Error Message%CEIPNM-2-OIR : Unexpected card type plugged into slot [dec] \n
Explanation An OIR operation has been performed, and the card that was inserted was of an unexpected type.
Recommended Action Insert the correct type of card or reboot the system. No action is required.
Error Message%CEIPNM-2-RESET_FAIL : (sw) slot([dec]) ceipnm reset fail!\n
Explanation The firmware did not correctly boot up correctly after a network module was reset.
Recommended Action Save your router configurations, power down the router, and reboot the system. You may have to reseat the network module in the specified bay. 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%CEIPNM-1-UNSUPPORTED : \n[chars]\n
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%CEIPNM-5-UPDOWN : cem [dec]/[dec]/[dec], changed state to [chars]
Explanation A configurable interface has changed its state.
Recommended Action No action is required.
Error Message%CEIPNM-2-WATCH_DOG : Got WATCHDOG Interrupt from NM at slot [dec] \n
Explanation A firmware crash has been detected.
Recommended Action Save your router configurations, power down the router, reinsert the network module in the specified bay, 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.
CFG Messages
The following are messages relating to invalid Cisco 1840 configurations.
Error Message%CFG-3-CARD_NOT_SUPPORTED : Slot [dec]: [chars]
Explanation The specified line card is not recognized by the system.
Recommended Action Replace the line card with a supported line card, or upgrade the software to a Cisco IOS software image that supports this card.
Error Message%CFG-6-ECAN_NEEDS_DSP : PVDM-ECAN requires PVDM-DSP or MS-AIM.
Explanation The echo-cancellation PVDM that is present in the router will not function properly without a PVDM DSP or multiservice AIM module.
Recommended Action Add a PVDM DSP or multiservice AIM module to the system to enable echo cancellation.
Error Message%CFG-6-EXTRA_AIM : AIM-VPN in AIM slot [dec] will be ignored.
Explanation This product supports only one AIM-VPN at a time. Only the first AIM-VPN that was found will be used.
Recommended Action Remove the extra AIM.
Error Message%CFG-6-HWIC_ESW_NO_DCARD : HWIC_ESW in slot [dec] lacks ILP daughtercard.
Explanation This router has an inline power supply that can support inline-powered Ethernet on a HWIC ESW with an ILP daughter card. However, the HWIC ESW line card in the slot specified in the message does not have a daughter card and so cannot support inline-powered Ethernet.
Recommended Action Add an ILP daughter card to the HWIC ESW line card.
Error Message%CFG-6-HWIC_ESW_NO_ILP : Internal inline power supply required to support HWIC_ESW with ILP daughtercard.
Explanation This router contains at least one HWIC ESW with an ILP daughter card. This card can support inline-powered Ethernet if it contains an internal inline power supply. However, the power supply currently present on this router does not provide inline power support.
Recommended Action If you wish to use inline power, replace the power supply in your router with one that can provide inline power.
Error Message%CFG-6-ILP_DEAD : Inline Power Supply module is not working.
Explanation This router has an inline power supply module, but it is not functioning properly. Inline-powered Ethernet will not operate correctly. This condition indicates a defective inline power supply.
Recommended Action Replace the inline power supply.
Error Message%CFG-6-ILP_NO_HWIC_ESW : Inline powered ethernet requires a HWIC_ESW with ILP daughtercard.
Explanation This router contains an inline power supply that can support inline-powered Ethernet on an HWIC ESW with an ILP daughter card. However, no HWIC ESW card with an ILP is present in the router.
Recommended Action To fully utilize the router power supply, install an HWIC ESW card with an ILP daughter card.
Error Message%CFG-6-ILP_NO_PAN : Inline powered ethernet requires a PAN-HWIC with ILP daughtercard.
Explanation This router has an inline power supply that can support inline-powered Ethernet on an HWIC-4ESW or HWICD-9ESW with an inline power daughter card. However, no HWIC-4ESW or HWICD-9ESW card with inline power is present in the router.
Recommended Action Install an HWIC-4ESW or HWICD-9ESW card with an inline power daughter card to fully utilize the power supply of the router.
Error Message%CFG-6-PAN_NO_DCARD : PAN-HWIC in slot [dec] lacks ILP daughtercard.
Explanation This router has an inline power supply that can support inline-powered Ethernet on an HWIC-4ESW or HWICD-9ESW with an inline power daughter card. However, the HWIC-4ESW or HWICD-9ESW card in the slot specified in the message does not have an inline power daughter card and cannot support inline-powered Ethernet.
Recommended Action Add an inline power daughter card to the HWIC-4ESW or HWICD-9ESW.
Error Message%CFG-6-PAN_NO_ILP : Internal inline power supply required to support PAN with ILP daughtercard.
Explanation This router has at least one HWIC-4ESW or HWICD-9ESW with an inline power daughter card. This card can support inline-powered Ethernet if an internal inline power supply is present. However, the power supply currently present on this router does not provide inline power support.
Recommended Action Replace the power supply in your router with one that can provide inline power if inline power support is required.
Error Message%CFG-6-UNKNOWN_AIM : AIM module in AIM slot [dec] is not supported by this IOS image. Card info: [chars].
Explanation The AIM in the specified AIM slot is not recognized or supported by the Cisco IOS software image that is operational on the system.
Recommended Action Either replace the AIM with an AIM that is supported or upgrade to a Cisco IOS software image that supports this AIM.
Error Message%CFG-6-VIC_NEEDS_DSP : Slot [dec]: Voice requires a PVDM-DSP or MS-AIM.
Explanation At least one voice card was found in the router. The voice card will not function properly without a PVDM DSP or a multiservice AIM module.
Recommended Action Add a PVDM DSP or a multiservice AIM module to enable voice capability.
Error Message%CFG-3-WIC_NOT_ALLOWED_IN_VIC_SLOT : Slot [dec]: [chars]
Explanation The WIC that was detected is not supported in the specified slot. Slot 1 supports VICs only.
Recommended Action Move the WIC to another slot that can support it.
CHANNEL_BANK Messages
The following are Channel Bank messages.
Error Message%CHANNEL_BANK-5-UPDOWN : Channel Bank [chars] state is [chars]
Explanation The channel bank status has been changed.
Recommended Action Verify that the voice ports in the channel bank are enabled (UP).
C_GIGE Messages
The following are common device driver messages for the dual-port Gigabit Ethernet back card subsystem.
Error Message%C_GIGE-3-GEMAXADDR : [chars], expected [hex], actual [hex]
Explanation There are too many MAC addresses in the filter table.
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%C_GIGE-3-GEMISMATCH : [chars], expected [hex], actual [hex]
Explanation PCI initialization for the common Gigabit Ethernet subsystem 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%C_GIGE-3-INITFAIL : C_GIGE initialization failed, [chars]
Explanation Initialization for the common Gigabit Ethernet subsystem 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%C_GIGE-3-INTERNAL : C_GIGE internal error, [chars]
Explanation The system has detected an error in the internal common Gigabit Ethernet 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%C_GIGE-3-MAJOR_FAULT : C_GIGE unrecoverable error, [chars], error_code=[hex]
Explanation The system has detected an operation error in the common Gigabit Ethernet 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%C_GIGE-3-MIBINITFAIL : C_GIGE MIB initialization failed, [chars]
Explanation MIB initialization for the common Gigabit Ethernet subsystem 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%C_GIGE-4-TOOBIG : C_GIGE - interface: [chars]: size [dec]: pak size
Explanation A packet larger than the maximum allowed packet size has been received.
Recommended Action The system will correct this condition. No action is required.
Error Message%C_GIGE-6-UNKNOWN : Unknown message ([dec]) received ([chars]) from interface [chars]
Explanation The driver has received an unknown message from the back card.
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.
CHARLOTTE Messages
The following are dual OC-3 PoS port adapter messages.
Error Message%CHARLOTTE-1-INITFAIL : Failed to initialize port [dec].
Explanation The PA-POS-2OC3 port adapter driver failed to complete its IDB 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.
Error Message%CHARLOTTE-3-INVALIDPCI : Device reported [hex]
Explanation Hardware initialization of the PA-POS-2OC3 port adapter has failed. The PCI device contains an invalid identifier.
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%CHARLOTTE-1-PCIINITFAIL : PCI initialization failed.
Explanation The PA-POS-2OC3 port adapter driver 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.
Error Message%CHARLOTTE-3-UNSUPPORTED : [chars]
Explanation The PA-POS-2OC3 port adapter is not supported on this platform. The system log specifies the part of the system that requires an upgrade.
Recommended Action Upgrade your system to a platform that supports the PA-POS-2OC3 port adapter. Refer to the system log to determine what part of your system requires an upgrade.
CHKPT Messages
The following messages support the checkpoint (CHKPT) facility.
Error Message%CHKPT-4-DISABLED : Check Pointing is disabled. Client [chars] should not be calling any CPF API
Explanation The checkpointing feature has been disabled. This condition might be caused by a timing issue.
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%CHKPT-4-DUPID : Duplicate checkpoint client ID ([dec]).
Explanation The checkpoint facility has detected a duplicate checkpoint client ID.
Recommended Action No action is required.
Error Message%CHKPT-3-ILLEGAL : ILLEGAL call to CPF API on ([chars]) by ([chars]).
Explanation A severe error involving a checkpointing operation 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%CHKPT-4-INVALID : Invalid checkpoint client ID ([dec]).
Explanation The checkpoint facility has detected an invalid checkpoint client ID.
Recommended Action No action is required.
Error Message%CHKPT-3-IPCPORT : Unable to create IPC port on ([chars]).
Explanation The checkpoint facility is unable to create a port for interprocess communication.
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%CHKPT-3-IPCSESSION : Unable to open an IPC session for communicating with ([chars]). rc= [dec]
Explanation The checkpoint facility is unable to open an interprocess communication session.
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%CHKPT-3-NOMEM : Unable allocate resource for CPF on ([chars]).
Explanation A severe error involving a checkpointing operation 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%CHKPT-3-RFREG : Unable to register checkpoint as client of RF.
Explanation The checkpoint facility is unable to register with the RF as a client.
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%CHKPT-4-SENDFAILED : Checkpointing send failed client ([dec])
Explanation This warning message indicates that the checkpoint facility was unable to send checkpoint information to a client.
Recommended Action No action is necessary.
Error Message%CHKPT-3-TPPORT : Unable to create TP port on ([chars]).
Explanation A severe error involving checkpointing 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%CHKPT-3-TPSESSION : Unable to open an TP session for communicating with ([chars]). rc= [dec]
Explanation A severe error involving checkpointing 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%CHKPT-3-UNKNOWNMSG : Unknown message recieved from peer on standby for client ([dec]).
Explanation The checkpoint facility has received an unknown message from a peer. This peer is in standby mode for the client specified in the message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
CHOC12 Messages
The following are CHOC12 port adapter messages.
Error Message%CHOC12-3-CORRUPT : Corrupt configuration, unsupported [chars] ([int]) encountered
Explanation The CHOC12 RP driver running configuration is corrupt.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show c10k and show ipc status commands to gather data that may provide information to determine 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%CHOC12-3-ERROR : [chars]
Explanation This message provides general error information.
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%CHOC12-1-INITFAIL : Slot [dec]/[dec] init failure ([chars])
Explanation The CHOC12 port adapter has failed to initialize.
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%CHOC12-4-REDINLCEVT : Redundant inactive i/f ([chars]) event: [chars], reason: [chars]
Explanation An internal redundant line card event 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%CHOC12-1-UNSUPPORTED : \n[chars]
Explanation The CHOC12 port adapter is not supported.
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.
CHOPIN Messages
The following are Cisco Chopin messages.
Error Message%CHOPIN-2-TXBADVC : [chars], vc [dec]\n
Explanation The Chopin versatile interface processor multichannel port adapter contains 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 commands, with slot-number being the slot number of the affected line card, 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, show tech-support, show tech-support and show controllers vip slot-number tech-support commands and your pertinent troubleshooting logs.
CHSTM1 Messages
The following are CHSTM1 messages.
Error Message%CHSTM1-3-CORRUPT : Corrupt configuration, unsupported [chars] ([int]) encountered
Explanation The running configuration for the CHSTM1 RP driver is corrupt.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show c10k and show ipc status commands to gather data that may provide information to determine 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%CHSTM1-3-ERROR : [chars]
Explanation This message provides general error information.
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%CHSTM1-1-INITFAIL : Slot [dec]/[dec] init failure ([chars])
Explanation An CHSTM1 initialization failure 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.
CI Messages
The following are Cisco 7500 platform chassis interface (CI) messages.
Error Message%CI-3-ASPMEM : C6400 equipped with [chars] requires at least [dec] MB of RAM
Only [dec] MB of RAM installed\nExplanation The type of feature card installed requires more RAM than is currently installed in the system.
Recommended Action Install the required amount of RAM in the system.
Error Message%CI-5-ASPREV : ***WARNING*** Hot swapping the ASP will cause hardware damage. \n
Explanation This warning message appears during a Cisco LS1010 or Cisco C5x00 startup. The ASP is not hot-swappable on the Cisco LS1010 even though it is hot-swappable on the C5x00 platforms. Removing an ASP from a Cisco LS1010 while the system is operating causes the system to shut down and might cause hardware damage to the ASP. If this warning appears on a C5x00 platform, it indicates that the ASP is not hot-swappable.
Recommended Action Heed the warning. Do not remove a non-hot-swappable ASP while the power is on.
Error Message%CI-3-ASPREVC5500 : ***WARNING*** Cannot determine Power Supply type/detect Power Supply fan alarm \n
Explanation This warning message appears during C5x00 startup. The revision of the ASP installed in the router is unable to provide information about the power supply type and fan status.
Recommended Action If this condition is a cause for concern, 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%CI-3-BLOWER : [chars] fan failure
Explanation One of the router's cooling fans has failed.
Recommended Action Replace the fan as soon as possible because the router might shut down or fail to operate properly.
Error Message%CI-6-BLOWEROK : Fan tray module OK
Explanation The chassis fan tray is operating normally.
Recommended Action No action is required.
Error Message%CI-1-CORETEMPCRITICAL : Core temperature CRITICAL limit exceeded
Explanation The system core temperature critical limit has been exceeded. The system will automatically shut down in two minutes.
Recommended Action Attempt to resolve the temperature problem. 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%CI-3-CORETEMPMAJOR : Core temperature major limit exceeded
Explanation The system core temperature major limit has been exceeded.
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%CI-3-CORETEMPMINOR : Core temperature minor limit exceeded
Explanation The system core temperature minor limit has been exceeded.
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%CI-6-CORETEMPOK : Core temperature normal
Explanation The temperature of the system core is normal.
Recommended Action No action is required.
Error Message%CI-6-ENVNORMAL : [chars] measured at [chars]
Explanation One of the measured environmental test points has returned to normal.
Recommended Action If the situation does not correspond with a normal operation of the system's environmental test points, collect the outputs for the commands show hardware, show env all, show env table, and show env last, and call your technical support representative for assistance.
Error Message%CI-3-FCTYPE : Unrecognized Feature Card\n
Explanation The feature card is not recognized by the software.
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%CI-1-INLETTEMPCRITICAL : Inlet temperature CRITICAL limit exceeded
Explanation The air intake temperature critical limit has been exceeded. The system will automatically shut down in two minutes.
Recommended Action Attempt to resolve the temperature problem. 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%CI-3-INLETTEMPMAJOR : Inlet temperature major limit exceeded
Explanation The air intake temperature major limit has been exceeded.
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%CI-3-INLETTEMPMINOR : Inlet temperature minor limit exceeded
Explanation The air intake temperature minor limit has been exceeded.
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%CI-6-INLETTEMPOK : Inlet temperature normal
Explanation The temperature of the chassis air intake is normal.
Recommended Action No action is required.
Error Message%CI-3-NOACK : Access to [chars] temperature sensor failed
Explanation The chassis temperature sensor could not be accessed.
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%CI-1-NOFAN : Fan tray empty
Explanation The chassis fan tray does not exist.
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%CI-3-NOFORK : Couldn't start environment polling daemon
Explanation The environment-monitoring daemon process could not be started during system 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.
Error Message%CI-3-PARTFANFAIL : Single fan failure
Explanation The chassis fan tray is not fully functioning.
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%CI-6-PSCHANGE : Power supply [int] changed from [chars] to [chars]
Explanation The CI reports that a power supply was either installed, removed, or changed.
Recommended Action If the explanation does not correspond to a physical change in the system's power supplies, 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%CI-3-PSFAIL : Power entry module [int] failure
Explanation The power entry module 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%CI-3-PSFANFAIL : Power supply fan [int] failure
Explanation One of the router's power supply fans has failed.
Recommended Action Repair the fan or replace the power supply as soon as possible. If the failure condition persists, the loss of cooling will cause the power supply to fail.
Error Message%CI-6-PSFANOK : Power supply fan [int] OK
Explanation The specified power supply fan has changed status to an acceptable condition. This informational message is displayed after the replacement of a bad power supply or anytime the software determines that a failure condition has been corrected.
Recommended Action No action is required.
Error Message%CI-6-PSOK : Power entry module [int] OK
Explanation The power entry module is operating normally.
Recommended Action No action is required.
Error Message%CI-3-PSTYPE : ***WARNING*** Incompatible power supply types -\n One is AC, other is DC. \n
Explanation The system detects an AC and a DC power supply within the same chassis. Mixing AC and DC power supplies is not supported.
Recommended Action Change one of the power supplies so that they are both of the same type.
Error Message%CI-3-TEMP : Overtemperature warning
Explanation The temperature sensor indicates a high-temperature condition.
Recommended Action Make sure that the room temperature is not too high and that air flow to the chassis is not blocked. If this condition persists, the system shuts down to avoid damage. If you are unable to resolve the problem on your own, 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%CI-3-SHUTDOWN : System shutting down due to over-temperature condition
Explanation The timer has expired for a chassis over-temperature condition. The system is shutting down.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CI-0-SHUTFANFAIL : System shutting down due to total fan tray failure
Explanation The timer has expired for a chassis fan tray failure condition. The system is shutting down.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CI-0-SHUTFANGONE : System shutting down due to missing fan tray
Explanation The chassis fan does not exist.
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%CI-6-TEMPOK : Temperature OK
Explanation The temperature sensor indicates that the chassis air temperature has returned to acceptable levels.
Recommended Action No action is required.
Error Message%CI-1-TOTALFANFAIL : Total fan tray failure
Explanation The chassis fan tray has experienced a total 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%CI-3-VOLTAGE : Voltage out of range
Explanation The voltage has reached a critical level and is now out of acceptable range.
Recommended Action Verify the failure and call your technical support representative for repair or replacement.
Error Message%CI-6-VOLTAGEOK : Voltage OK
Explanation The voltage level has changed status to an acceptable condition.
Recommended Action No action is required.
CLNS Messages
The following are Open System Interconnection (OSI) Connectionless Network Service (CLNS) messages.
Error Message%CLNS-4-AUTH_FAIL : [chars]: [chars] authentication failed
Explanation An IS-IS packet (either an IIH, CSNP, PSNP or LSP) was received and did not pass an authentication check.
Recommended Action If this error persists, check the originating router to ensure that the authentication mode and password matches.
Error Message%CLNS-3-FILTERS : Adjacency with [chars] is denied due to misconfiguration of filters
Explanation The IS-IS or CLNS adjacency filters might be misconfigured on an interface. This error condition occurs when a CLNS filter expression that uses the source keyword is applied to IS-IS or CLNS adjacency filters.
Recommended Action Do not use the source keyword when applying filter expressions to filter CLNS or IS-IS adjacencies. Remove the CLNS filter expression that contains the source keyword by entering the no clns filter-expr exp_name command, with exp_name being the name to apply a filter expression.
Error Message%CLNS-3-IPLIST : ISIS: [chars] [hex], [IP_address] [IP_address]
Explanation An internal error has occurred in IS-IS.
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%CLNS-4-LSP_MAXSEQ : [chars][chars]: attempt to exceed LSP maximum sequence number for LSP [chars]
Explanation An attempt was made to exceed the maximum sequence number for an LSP.
Recommended Action Protocol will shut down for max-lsp-lifetime + 1 minute. This is a very unlikely natural occurrence. Investigate to find the source of any out of order reception, generation, or incrementing of this LSP's sequence number.
Error Message%CLNS-3-LSPFULL : [chars]: L[dec] LSP filled to capacity [chars]
Explanation A hardware or software 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%CLNS-3-LSPFULL_OVERLOAD : [chars]: Schedule L[dec] LSP to set overload bit
Explanation The LSP was filled to capacity. After applying any "lsp-full" suppress options, the system was still unable to recover from this condition. The Overload bit has now been set on the LSP.
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%CLNS-3-LSPLIST : ISIS: [chars] [hex], index [dec]
Explanation An internal error has occurred in IS-IS.
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.
CNS Messages
The following are Cisco Networking Services (CNS) messages.
Error Message%CNS-6-NO_EVENT_AGENT : CNS EVENT AGENT IS NOT CONFIGURED
Explanation The CNS event agent is not configured. The event that was to be sent to it will be dropped.
Recommended Action Configure the CNS event agent.
COBALT Messages
The following are COBALT messages.
Error Message%COBALT-3-COBALT_MALLOCFAIL : PXF DMA driver malloc failed!
Explanation The PXF DMA driver cannot operate because of insufficient available memory.
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%COBALT-3-INIT_ERR : PXF DMA Initialization failed!
Explanation The PXF DMA ASIC could not initialize.
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%COBALT-3-OWN_ERR : [chars] packet buffer, descriptor address [hex], descriptor flags [hex] pak [hex]
Explanation The PXF DMA ASIC driver detected that the descriptor ring is in an inconsistent and unrecoverable 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.
Error Message%COBALT-3-SDRAM_ADDR_ERR : PXF DMA SDRAM [chars], Bad Address: [hex]
Explanation An invalid PXF DMA SDRAM address was detected.
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%COBALT-3-SDRAM_DETECT_ERR : No PXF DMA SDRAM detected!
Explanation The PXF DMA SDRAM could not be accessed.
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%COBALT-3-SPURIOUS_INT_ERR : Spurious PXF DMA Interrupt detected!
Explanation A spurious PXF DMA interrupt operation has been detected.
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%COBALT-2-TBB_LENGTH_ERR : TBB FIFO Debug Data - Register [hex]: [hex]
Explanation The PXF DMA ASIC driver has detected an error involving the length of a TBB.
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%COBALT-3-VCCI_0_ERR : Packet [hex], Length [dec], Channel [dec], VCCI [dec], Flags [hex]
Explanation The PXF DMA ASIC driver detected a VCCI of 0.
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.
CONTROLLER Messages
The following are controller messages.
Error Message%CONTROLLER-5-DOWNDETAIL : Controller [chars], changed state to [chars] due to [chars]
Explanation A configurable controller has changed its state.
Recommended Action No action is required.
Error Message%CLNS-4-LSP_MAXSEQ : [chars][chars]: attempt to exceed LSP maximum sequence number for LSP [chars]
Explanation An attempt was made to exceed the maximum sequence number for an LSP.
Recommended Action Protocol will shut down for max-lsp-lifetime + 1 minute. This is a very unlikely natural occurrence. Investigate to find the source of any out of order reception, generation, or incrementing of this LSP's sequence number.
CPOS Messages
The following are common Packet over SONET messages.
Error Message%CPOS-3-HW_FAULT : POS HW error, [chars], error_code=[hex]
Explanation A PoS operation error has occurred in the hardware.
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%CPOS-3-INTERNAL : POS internal error, [chars]
Explanation An internal PoS 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%CPOS-3-MAJOR_FAULT : POS unrecoverable error, [chars], error_code=[hex]
Explanation A unrecoverable PoS operation 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%CPOS-3-MIBINITFAIL : POS MIB initialization failed, [chars]
Explanation The MIB initialization for PoS 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%CPOS-5-PERIODIC_STATS : POS periodic stats collection not run for [dec] seconds
Explanation There is a delay in collecting PoS statistics. This delay usually occurs when the RP is busy with high-priority tasks and can trigger line alarms for a short period of time. The time-based statistics for this interface can also become skewed.
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%CPOS-3-POSMISMATCH : [chars], expected [hex], actual [hex]
Explanation PCI initialization for POS 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.