Downloads |
Table Of Contents
System Messages for Cisco IOS XE
Cisco ASR 1000 Series Routers Documentation
Obtaining Technical Assistance
System Messages for Cisco IOS XE
First Published: July 1, 2008Last Updated: April 21, 2009This publication lists and describes system messages for Cisco IOS XE software, up to and including Cisco IOS XE Release 2.2. The system software sends these messages to the console (and, optionally, to a logging server on another system) during operation. Not all system messages indicate problems with your system. Some are purely informational, and others may help diagnose problems with communications lines, internal hardware, or the system software.
This manual only contains messages that are specific to Cisco IOS XE software on the Cisco ASR 1000 Series Routers. Many system messages on the Cisco ASR 1000 Series Routers are inherited from the IOS sub-package; for this reason, this document should be used with the Cisco IOS Release 12.2SR System Message Guide to gather all system message documentation for the Cisco ASR 1000 Series Routers.
Contents
Related Documentation
This section refers you to other documentation that also might be useful relating to your Cisco ASR 1000 Series Router. The documentation listed below is available online.
Cisco ASR 1000 Series Routers Documentation
The Cisco ASR 1000 Series has a documentation roadmap that provides listings to a broad range of documentation available for the Cisco ASR 1000 Series Routers. See the Cisco ASR 1000 Series Router Documentation Roadmap at:
http://cisco.com/en/US/products/ps9343/products_documentation_roadmaps_list.html
The documentation homepage for the Cisco ASR 1000 Series Routers contains a wide variety of hardware and software information for the Cisco ASR 1000 Series Routers and can be viewed at:
http://cisco.com/en/US/products/ps9343/tsd_products_support_series_home.html
The documentation homepage for Cisco IOS XE contains Cisco IOS XE technology guides and feature documentation and can be viewed at:
http://cisco.com/en/US/products/ps9587/tsd_products_support_series_home.html
For information on commands, see one of the following resources:
•
Cisco IOS XE Software Command References
•
Additional Resources
The Cisco Technical Assistance Center (TAC) has made available to all registered users an online tool, the Cisco IOS Error Message Decoder, for researching and resolving messages.
All you have to do is copy an error message or a command output from your screen and paste it into the appropriate text fields of the tool. Within moments, the tool responds with an interpretation of your text. The Cisco IOS Error Message Decoder makes it easy for you to distinguish between messages that are purely informational and those that alert you to potential problems. This tool provides you with an explanation of the error message, a recommended action, and links to suggested online Cisco technical support resources. For help with researching and resolving your Cisco IOS messages, the Cisco IOS Error Message Decoder tool is found at http://www.cisco.com/pcgi-bin/Support/Errordecoder/index.cgi.
Obtaining Technical Assistance
When the recommended action of an error message advises that you contact Cisco technical support, open a case with the Cisco Technical Assistance Center (TAC). You can access the TAC Service Request Tool on the Cisco Worldwide Contacts page at: http://www.cisco.com/en/US/support/tsd_cisco_worldwide_contacts.html.
Access to all tools on the Cisco Technical Support Website requires a Cisco.com user ID and password.
How This Manual Is Organized
The system messages provide descriptions of system messages related to the Cisco IOS software. The messages are organized according to the particular system facility that produces the messages. The facility sections appear in alphabetical order, and within each facility section, messages are listed alphabetically by mnemonic. Each message is followed by an explanation and a recommended action.
For alphabetizing purposes, lowercase and uppercase letters are treated the same.
The index of messages is alphabetized as follows:
1.
2.
3.
How to Read System Messages
System messages begin with a percent sign (%) and are structured as follows. The text in bold are required elements of the System Message, the text in italics are optional elements of the System Message.
%FACILITY-SEVERITY-MNEMONIC: Message-textFACILITY is a code consisting of two or more uppercase letters that indicate the facility to which the message refers. A facility can be a hardware device, a protocol, or a module of the system software.
SEVERITY is a single-digit code from 0 to 7 that reflects the severity of the condition. The lower the number, the more serious the situation. Table 1 lists the severity levels.
MNEMONIC is a code that uniquely identifies the system message.
Message-text is a text string describing the condition. This portion of the message sometimes contains detailed information about the event, including terminal port numbers, network addresses, or addresses that correspond to locations in the system memory address space. Because the information in these variable fields changes from message to message, it is represented here by short strings enclosed in square brackets ([ ]). A decimal number, for example, is represented as [dec]. Table 2 lists the representation of variable fields and the type of information in them.
The following is a sample system message:
%LINK-2-BADVCALL: Interface [chars], undefined entry pointSome messages also indicate the card and slot reporting the error. These messages begin with a percent sign (%) and are structured as follows:
%CARD-SEVERITY-MSG:SLOT %FACILITY-SEVERITY-MNEMONIC: Message-textCARD is a code that describes the type of card reporting the error. CIP, CIP2, ECPA, ECPA4, FEIP, PCPA, and VIP are possible card types.
MSG is a mnemonic that indicates that this is a message. It is always shown as MSG.
SLOT indicates the slot number of the card reporting the error. It is shown as SLOT followed by a number (for example, SLOT5).
Note
System message severity levels correspond to the keywords assigned by the logging console and logging monitor global configuration commands that define where and at what level these messages appear. In general, the default is to log messages from level 0 (emergencies) to level 7 (debugging). However, the default level varies by platform. For more information, see the system configuration chapter and descriptions of the logging console and logging monitor commands in the appropriate Cisco IOS XE configuration guide and command reference publications.
Table 2 Representation of Variable Fields in Messages
[char]
Single character
[chars]
Character string
[hex]
Hexadecimal number
[int]
Unsigned integer
Message Traceback Reports
Some messages describe internal errors and contain traceback information. This information is very important and should be included when you report a problem to your technical support representative.
The following sample message includes traceback information:
-Process= "Exec", level= 0, pid= 17 -Traceback= 1A82 1AB4 6378 A072 1054 1860System Messages
This section contains the system messages for Cisco IOS XE. The messages are grouped according to the following facility names:
ACL Messages
Error Message %ACL-4-UNEXPECTED_PKT_TYPE : type [dec], int [dec] [chars]putExplanation Access control list (ACL) logging has encountered an unexpected packet type.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %ACL-4-UNEXPECTED_STATE : type [dec], int [chars] [chars]put, w0: [hex], w1: [hex]Explanation An access control list (ACL) hardware setup error has occurred.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
ALG_COM Messages
Error Message %ALG_COM-4-CHUNK_CREATE_FAIL : [chars]Explanation An application layer gateway (AlG) request to create a data chunk failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %ALG_COM-4-CHUNK_EXTEND_FAIL : [chars]Explanation An application layer gateway (AlG) request to extend a data chunk failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %ALG_COM-4-IPC_INIT_FAILED : [dec]Explanation An application layer gateway (AlG) IPC handler initialization failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
ALG_PROXY Messages
Error Message %ALG_PROXY-4-PROXY_MEM_EXTEND_FAILED : ALG IPC subtype: [dec]Explanation An application layer gateway (ALG) attempt to extend memory failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %ALG_PROXY-4-PROXY_MEM_REQ_FAILED : ALG IPC subtype: [dec]Explanation An application layer gateway (ALG) request for more memory failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %ALG_PROXY-5-PROXY_IPC_INVALID_MSG : [dec]Explanation The application layer gateway (ALG) experienced an invalid interprocess communications (IPC) message subtype.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %ALG_PROXY-5-PROXY_IPC_INVALID_MSG_LEN : [dec]:[dec] len [dec] flags [hex] source [dec]Explanation The application layer gateway (ALG) experienced an invalid interprocess communications (IPC) message length.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
APPFW Messages
Error Message %APPFW-7-IM_AOL_CLIENT_VERSION : im-aol [chars]Explanation The AOL client version is not supported.
Recommended Action No action is required.
Error Message %APPFW-7-IM_AOL_SESSION : im-aol [chars] service session initiator [chars]Explanation The AOL AIM well known service message has been detected.
Recommended Action No action is required.
Error Message %APPFW-7-IM_MSN_CLIENT_VERSION : im-msn [chars]Explanation The MSN client version is not supported.
Recommended Action No action is required.
Error Message %APPFW-7-IM_MSN_SESSION : im-msn [chars] service session initiator [chars]Explanation The MSN messager well known service message has been detected.
Recommended Action No action is required.
Error Message %APPFW-7-IM_YAHOO_CLIENT_VERSION : im-yahoo [chars]Explanation The YAHOO client version is not supported.
Recommended Action No action is required.
Error Message %APPFW-7-IM_YAHOO_P2P_CHAT : im-yahoo text-chat service session: %Ci:[int]Explanation The Yahoo text chat service session has been detected.
Recommended Action No action is required.
Error Message %APPFW-7-IM_YAHOO_SESSION : im-yahoo [chars] service session initiator %Ci:[int] [chars] [dec] bytes [chars] responderExplanation The Yahoo YMSGR well known service message has been detected.
Recommended Action No action is required.
Error Message %APPFW-7-P2P_PORT_HOP : [chars] using [chars] port - [chars]Explanation A peer-to-peer protocol has been detected using a non-standard
Recommended Action No action is required.
Error Message %APPFW-7-P2P_SERVICE : Identified [chars] [chars] [chars] - [chars]Explanation A peer-to-peer protocol has been detected on the session.
Recommended Action No action is required.
ARL_PROXY Messages
Error Message %ARL_PROXY-4-GPM_ALLOC_FAILED : GPM allocation for reply failed pak_size [hex] reply_size [hex]Explanation The ACL range lookup (ARL) global packet memory (GPM) buffer could not be allocated for a reply.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %ARL_PROXY-4-IPC_UNHANDLED : type: [dec]Explanation An unknown message was received by the ACL range lookup (ARL) client proxy.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
ASR1000
Error Message %ASR1000_PEM-4-PEMFAIL : The PEM in slot [dec] is switched off or encountering a failureExplanation The Power Entry Module (PEM) hardware is either switched off, or is reporting a failure condition due to a possible installation or power problem, or other hardware failure.
Recommended Action Following proper safety and grounding guidelines, verify the installation of the PEM and confirm that the hardware is fully seated and properly screwed in. Verify that power is connected and turned on. Verify that the PEM is turned on. If these actions do not resolve the problem, copy the error message exactly as it appears on the console or in the system log. Open a case with the Technical Assistance Center via the Internet, or contact your Cisco technical support representative and provide the representative with the gathered information.
ATTN Messages
Error Message %ATTN-3-MBOX_REG_FAIL : return code [dec]Explanation Registration of the handler function for a mailbox event failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %ATTN-3-PROXY_INIT_FAIL_IPC_REG : return code [dec]Explanation Initialization of an attention proxy failed due to an error.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %ATTN-4-PROXY_IPC_ALLOC_FAILED : [chars]Explanation Allocation of an IPC packet buffer by the attention proxy failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %ATTN-4-PROXY_IPC_SEND_FAILED : [chars]Explanation Transmission of an IPC message by the attention proxy failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %ATTN-4-PROXY_UNHANDLED_MSG : subtype [dec]Explanation An attention proxy received a message with an unknown subtype.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %ATTN-4-SYNC_TIMEOUT : msecs since last timeout %llu, missing packets [dec]Explanation An attention sync command timed out.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
BIPC Messages
Error Message %BIPC-3-BIPC_PERFORMANCE : buffer size request [int] failedExplanation An internal buffer allocation has failed.
Recommended Action No action is required. If the problem persists, or router performance is noticeably degraded, contact Cisco technical support. 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 gathered information.
Error Message %BIPCMGR-3-INVALID_TDL_ERROR_ON_MARSHAL TDL : epoch error on marshal [int] unexpected: [chars]Explanation The bipc manager has attempted to marshal a message to be sent. The tdl library has generated an error on marshal that is unexpected. The message was not sent.
Recommended Action This is unexpected. 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 gathered information.
BOOT Messages
Error Message %BOOT-0-DRV_LOADFAIL : Failed to load driver [chars] ( [chars] )Explanation A kernel driver that was critical to the functioning of the system failed to load.
Recommended Action Note the time of the error message and check the kernel error logs for additional information on the problem. If you are unable to resolve this problem, copy the error message and the output of show platform software tech-support into a plaintext file and contact Cisco technical support.
Error Message %BOOT-6-DRV_LOAD : Loaded driver [chars]Explanation A kernel driver that was critical to the functioning of the system was successfully loaded.
Recommended Action No user action is necessary. This message indicates the system is functioning normally and is provided for informational purposes only.
Error Message %BOOT-3-APP_STARTFAIL : Failed to launch process [chars]Explanation A process that does not affect the forwarding of network traffic failed to start.
Explanation If the failed process is not something that needs to be corrected, do not address this message. If the failed process needs to be addressed, install new software and reload the router.
Error Message %BOOT-0-APP_STARTFAILCRIT : Failed to launch a critical process [chars]Explanation A process important to the chassis has failed.
Recommended Action Note the time of the message and investigate the error message logs to learn more about the problem. If the problem persists or cannot be resolved, copy the error message and the output of show platform software tech-support into a plaintext file and contact Cisco technical support.
Error Message %BOOT-6-APP_START : The process [chars] has startedExplanation The process has successful launched and begun executing.
Recommended Action No user action is necessary. This message indicates the system is functioning normally and is provided for informational purposes only.
Error Message %BOOT-3-DUAL_BOOT_MEMORY : Dual IOS boot indicated in ROMMON ([chars]), unavailable on [chars] RPExplanation Running two IOS instances on the same RP is unavailable on route-processors with insufficient memory
Recommended Action Unset the specified ROMMON variable or increase the memory on the route-processor.
BSHELL Messages
Error Message %BSHELL-6-BSHELL_UPGRADE_DETECTED : [[chars]] New software detected. Bshell instance restarting.Explanation The diagnostic shell detected a new installation of diagnostic shell software. The diagnostic shell instance exits and restarts with the new software version.
Recommended Action This is an informational message only. No action is required.
Error Message %BSHELL-6-SMAN_CONNECTION_LOST : [[chars]] Shell Manager connection lostExplanation The diagnostic shell was disconnected from the Shell Manager and the Shell Manager process is no longer available. This type of error is experienced if a software upgrade is in progress.
Recommended Action This is an informational message only. No action is required. Once the Shell Manager process has restarted, the diagnostic shell will reconnect.
Error Message %BSHELL-6-SMAN_CONNECTION_FAILED : [[chars]] Shell Manager connect failed: [chars]Explanation The diagnostic shell is unable to connect to the Shell Manager, possibly because the Shell Manager process is no longer available. This type of error is experienced if a software upgrade is in progress.
Recommended Action No action is required. Once the Shell Manager process has restarted, the diagnostic shell will reconnect.
Error Message %BSHELL-6-SESSION_STARTED : [[chars]] bshell session started for user '[chars]'Explanation A user has started a diagnostic shell session.
Recommended Action This is an informational message only. No action is required.
Error Message %BSHELL-6-SESSION_ENDED : [[chars]] bshell session ended for user '[chars]'Explanation A user has exited a diagnostic shell session.
Recommended Action This is an informational message only. No action is required.
Error Message %BSHELL-3-EXEC_PREPARE_FAIL : [[chars]] Command execution prepare failedExplanation The diagnostic shell was unable to prepare the requested interactive command for execution. The command failed.
Recommended Action Check the diagnostic shell trace file for more information on the underlying failure.
Error Message %BSHELL-3-EXEC_FAIL : [[chars]] Command execution failedExplanation The diagnostic shell was unable to execute the requested interactive command.
Recommended Action Check the diagnostic shell trace file for more information on the underlying failure.
Error Message %BSHELL-3-EXEC_DIRECTIVE_FAIL : [[chars]] Command directive execution failed: [chars]Explanation The diagnostic shell was unable to execute the requested directive.
Recommended Action Check the diagnostic shell trace file for more information on the underlying failure.
Error Message %BSHELL-3-TERMINAL_OPERATION_FAIL : [[chars]] Terminal [chars] [chars] failed: [chars]Explanation The diagnostic shell was unable to get or set terminal properties. An attempt to change or act on terminal properties failed.
Recommended Action Restart the diagnostic shell and reattempt the failed operation
Error Message %BSHELL-3-GET_HOSTNAME_FAIL : [[chars]] Get hostname failed: [chars]Explanation The diagnostic shell was unable to read the hostname from the kernel.
Recommended Action No action is required. The diagnostic shell periodically checks for hostname changes to set the user prompt.
Error Message %BSHELL-3-SEND_MESSAGE_FAILED : [[chars]] Send message [chars] failed: [chars]Explanation The diagnostic shell was unable to send a message to the Shell Manager.
Recommended Action Retry the operation or start a new diagnostic shell session.
Error Message %BSHELL-3-RECEIVE_MESSAGE_FAILED : [[chars]] Receive message [chars] failed: [chars]Explanation The diagnostic shell was unable to receive a message from the Shell Manager
Recommended Action Retry the operation or start a new diagnostic shell session.
CCE Messages
Error Message %CCE-4-limit(CCE_IPV6_COMPR_CLASSIFY_FAIL : Dataplane IPV6 compression classification error for interface [chars]Explanation Internal software error in which the dataplane experienced an interface compression classification error.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CCE-4-limit(CCE_NON_TCAM_CLASSIFY : Dataplane classification error for interface [chars]Explanation Internal software error in which the dataplane experienced an interface classification error.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
CEF_PROXY Messages
Error Message %CEF_PROXY--PROXY_IPC_ADJ_IDX_FAILED : [hex]Explanation The express forwarding engine failed to obtain an adjacency index from an IPC packet.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CEF_PROXY--PROXY_IPC_ADJ_ID_HASH_FAILED :Explanation The express forwarding engine failed to obtain a hash address.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CEF_PROXY--PROXY_IPC_INIT_FAILED : [dec]Explanation The express forwarding engine IPC handler initialization failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CEF_PROXY--PROXY_IPC_INVALID_MSG : [hex]Explanation The express forwarding engine received an invalid IPC messages subtype.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CEF_PROXY--PROXY_IPC_OCE_CHAIN_PTR_FAILED : [hex]Explanation The express forwarding engine experienced an OCE chain pointer failure.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CEF_PROXY--PROXY_IPC_PACKET_ALLOCATION_FAILED : [hex]Explanation The express forwarding engine failed to allocate sufficient packet buffer for the IPC.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CEF_PROXY--PROXY_IPC_PACKET_SEND_FAILED : [hex]Explanation The express forwarding engine failed to send an IPC packet.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
CHUNK Messages
Error Message %CHUNK-4-limit(BAD_CHUNK_MAGIC : head_chunk [hex]; data [hex];chunkmagic [hex]; freechunkmagic [hex]Explanation An invalid memory chunk magic was detected in a memory chunk element.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CHUNK-4-limit(CHUNK_BAD_REFCNT : refcnt=[dec] data=[hex]Explanation The memory chunk manager detected a bad reference count.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CHUNK-4-limit(CHUNK_CORRUPT : chunk [hex]; data [hex]; start [hex]; end [hex]Explanation The the memory chunk manager detected memory corruption.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CHUNK-4-limit(INVALID_ELEM_SIZE : requested [int]Explanation An invalid element size request was made to the memory chunk manager.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CHUNK-4-limit(SIBLING_ERR : Tried to destroy sibling memory chunk [hex]Explanation The memory chunk manager experienced an invalid sibling condition.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
CMCC Messages
Error Message %CMCC-3-DDR_SINGLE_BIT_ERROR : Single-bit DRAM ECC error: mme: [int], sbe: [int], address: [hex], pid: [int], name: [chars]Explanation The SIP DRAM experienced a single-bit error checking code (ECC) error.
Recommended Action No action is required. This error is usually self-correcting. If the problem persists, you may need to replace the SIP.
Error Message %CMCC-0-CPLD_INITIALIZATION : The SIP CPLD has failed initialization :[chars]Explanation A SIP complex programmable logic device (CPLD) failed to initialize. This error could be caused by a hardware or software driver defect.
Recommended Action Examine the logs for CPLD driver or hardware errors. Verify that the software and CPLD versions are compatible.
Error Message %CMCC-0-CPLD_IOCTL : A CPLD driver I/O control has failed because [chars]Explanation A complex programmable logic device (CPLD) I/O driver control has failed. This error could be caused by a hardware or software driver defect.
Recommended Action Examine the logs for CPLD driver and hardware errors. If the problem persists, 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 gathered information
Error Message %CMCC-0-C2W_INITIALIZATION : The SIP C2W has failed initialization because [chars]Explanation The C2W bus on the SIP is used to read the shared port adapter (SPA) IDPROM. This error indicates that the SIP C2W bus failed to initialize.
Recommended Action Examine the logs for C2W driver errors. If the problem persists, 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 gathered information.
Error Message %CMCC-3-C2W_READ : An C2W read has failed because [chars]Explanation An attempt to read the C2W bus has failed. This error could be caused by a hardware or software defect.
Recommended Action Examine the logs for C2W driver errors.
Error Message %CMCC-3-C2W_WRITE : An I2C write has failed because [chars]Explanation An attempt to write to the inter-integrated circuit (I2C) has failed. This error could be caused by a hardware or software defect.
Recommended Action Examine the logs for I2C driver errors.
Error Message %CMCC-0-SERDES_INITIALIZATION : The SIP Serial Bridge ASIC has failed initialization because [chars]Explanation The SIP serial bridge ASIC failed to initialize. This error could be caused by a hardware defect, software driver defect, or improper internal configuration.
Recommended Action Examine the logs for serial bridge ASIC driver and hardware errors. If the problem persists, 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 gathered information
Error Message %CMCC-0-SERDES_IOCTL : A Serial Bridge driver I/O control has failed because [chars]Explanation A serial bridge driver I/O control has failed. This error could be caused by a hardware or software driver defect.
Recommended Action Examine the logs for serial bridge driver or hardware errors. If the problem persists, 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 gathered information.
Error Message %CMCC-0-HT_INITIALIZATION : The SIP HyperTransport has failed initialization because [chars]Explanation A SIP HyperTransport (HT) CPU bus failed to initialize. This error could be caused by a hardware defect or HT driver defect.
Recommended Action Examine the logs for HT driver or hardware errors. If the problem persists, 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 gathered information.
Error Message %CMCC-0-HT_IOCTL : A SIP HyperTransport driver I/O control has failed because [chars]Explanation A physical layer interface module (PLIM) HyperTransport (HT) driver I/O has failed. This error could be caused by a hardware defect or HT driver defect.
Recommended Action Examine the logs for HT driver or hardware errors. If the problem persists, 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 gathered information.
Error Message %CMCC-0-PLIM_INITIALIZATION : The PLIM has failed initialization because [chars]Explanation The physical layer interface module (PLIM) failed to initialize. This error could be caused by a hardware defect or a PLIM driver defect.
Recommended Action Examine the logs for PLIM driver or hardware errors. If the problem persists, 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 gathered information.
Error Message %CMCC-0-PLIM_IOCTL : A PLIM driver I/O control has failed because [chars]Explanation A physical layer interface module (PLIM) driver I/O has failed. This error could be caused by a hardware defect or a PLIM driver defect.
Recommended Action Examine the logs for PLIM driver or hardware errors. If the problem persists, 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 gathered information.
Error Message %CMCC-0-PLIM_HALT : A PLIM driver has critical error [chars], [int], param [int] param [int]Explanation A physical layer interface module (PLIM) HyperTransport (HT) driver I/O has failed. This error could be caused by a hardware defect or an HT driver defect.
Recommended Action Restart the SIP. If the problem persists, you may need to replace the PLIM.
Error Message %CMCC-3-PLIM_STATUS : A PLIM driver informational error [chars], param [int] param [int]Explanation A physical layer interface module (PLIM) HyperTransport (HT) driver I/O has failed. This error could be caused by a hardware defect or an HT driver defect.
Recommended Action Examine the logs for PLIM or hardware errors.
Error Message %CMCC-3-IDPROM_ACCESS : Failed access or process an IDPROM because [chars]Explanation The system failed to access an IDPROM or an IDPROM process failed. This error could be caused by a hardware defect, software defect, or incorrect IDPROM content.
Recommended Action Examine the logs for IDPROM or hardware errors.
Error Message %CMCC-3-IDPROM_SENSOR : One or more sensor fields from the idprom failed to parse properly because [chars].Explanation One or more IDPROM sensors failed to parse. This error most likely occurred because of a checksum failure in the IDPROM.
Recommended Action Examine the logs for IDPROM or hardware errors.
Error Message %CMCC-0-CHASSIS_TYPE : The chassis type [chars] is invalid.Explanation The system has detected an invalid chassis type. This error could be caused by a hardware defect, software defect, or incorrect IDPROM content.
Recommended Action Examine the logs for IDPROM or hardware errors. If the problem persists, 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 gathered information.
Error Message %CMCC-0-CHASFS_OBJECT_CREATE : Failed to create chassis filesystem object [chars] because [chars]Explanation The system failed to create a chassis filesystem object. This error could be caused by a software defect or a filesystem failure.
Recommended Action Restart the SIP. If the problem persists, 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 gathered information.
Error Message %CMCC-0-CHASFS_PROPERTY_CREATE : Failed to create chassis filesystem object [chars] property [chars] because [chars]Explanation The system failed to create a chassis filesystem object property. This error could be caused by a software defect or a filesystem failure.
Recommended Action Restart the SIP. If the problem persists, 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 gathered information.
Error Message %CMCC-0-CHASFS_PROPERTY_GET : Failed to read chassis filesystem object [chars] property [chars] because [chars]Explanation The system failed to read a chassis filesystem object property. This error could be caused by a software defect or a filesystem failure.
Recommended Action Restart the SIP. If the problem persists, 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 gathered information.
Error Message %CMCC-0-CHASFS_PROPERTY_SET : Failed to write chassis filesystem object [chars] property [chars] because [chars]Explanation The system failed to write a chassis filesystem object property. This error could be caused by a software defect or a filesystem failure.
Recommended Action Restart the SIP. If the problem persists, 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 gathered information.
Error Message %CMCC-0-CHASFS_OBJECT_WATCH : Failed to watch chassis filesystem object [chars] because [chars]Explanation The system failed to watch a chassis filesystem object. This error could be caused by a software defect or a filesystem failure.
Recommended Action Restart the SIP. If the problem persists, 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 gathered information.
Error Message %CMCC-0-CHASFS_OBJECT_NOT_PRESENT : Expected chassis filesystem object [chars][chars] not present.Explanation The system was unable to find an expected chassis filesystem object. This error could be caused by a software defect or a filesystem failure.
Recommended Action Restart the SIP. If the problem persists, 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 gathered information.
Error Message %CMCC-0-CHASFS_PROPERTY_NOT_PRESENT : Expected chassis filesystem object [chars] property [chars] not present.Explanation The system cannot locate a chassis filesystem object property. This error could be caused by a software defect or a filesystem failure.
Recommended Action Restart the SIP. If the problem persists, 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 gathered information.
Error Message %CMCC-0-CHASFS_LOCATION_TRANSLATE : Failed to translate a location to a chasfs object name because [chars]Explanation The system failed to translate a data sensor location to the chassis filesystem (CHASFS) module. This error could be caused by a software defect.
Recommended Action Restart the SIP. If the problem persists, 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 gathered information.
Error Message %CMCC-0-PEER_INVALID : A peer table entry has invalid state.Explanation An invalid state occurred in a peer table entry. This error could be caused by a software defect or system resource limitation.
Recommended Action Restart the SIP.
Error Message %CMCC-0-UIPEER_CREATE : Failed to create user interface peer.Explanation The system failed to create a user interface peer. This error could be caused by a software defect or system resource limitation.
Recommended Action Restart the SIP.
Error Message %CMCC-0-SERVICES_INITIALIZATION : Failed to initialize general application services because [chars]Explanation The system failed to initialize certain application services. This error could be caused by a software defect or system resource limitation.
Recommended Action Restart the SIP.
Error Message %CMCC-0-IPC_INITIALIZATION : IPC initialization failed because [chars]Explanation An inter-process communication (IPC) initialization failed. This error could be caused by a software defect or system resource limitation.
Recommended Action Restart the SIP.
Error Message %CMCC-0-IPC_CONNECT_MASTER : IPC connection to the active RP failed because [chars]Explanation The inter-process communication (IPC) connection to the active route processor (RP) failed. This error could be caused by a software defect or system resources limitation.
Recommended Action Restart the SIP.
Error Message %CMCC-0-IPC_CONNECTION_INVALID : An IPC connection has invalid state.Explanation An inter-process communication (IPC) connection has an invalid state. This error could be caused by a software defect or system resource limitation.
Recommended Action Restart the SIP.
CMFP Messages
Error Message %CMFP-3-DDR_SINGLE_BIT_ERROR : Single-bit DRAM ECC error: mme: [int], sbe: [int], address: [hex], pid: [int], name: [chars]Explanation A single-bit data corruption error has occurred in the forwarding processor (FP).
Recommended Action These errors are self-correcting. If the problem persists, the FP hardware may need to be replaced.
Error Message %CMFP-3-IDPROM_ACCESS : Failed access or process an IDPROM because [chars]Explanation Access to an IDPROM failed due to a hardware or software defect, or incorrect IDPROM content.
Recommended Action Examine the system logs for IDPROM and hardware errors. Copy the error message and related information 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 gathered nformation.
Error Message %CMFP-3-IDPROM_SENSOR : One or more sensor fields from the idprom failed to parse properly because [chars].Explanation Output from the IDPROM sensors failed to parse, commonly caused by a checksum failure in the IDPROM.
Recommended Action Examine the system logs for IDPROM and hardware errors. If the problem persists, 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 gathered information.
Error Message %CMFP-3-MASTERSHIP_UPDATE : An error ([chars]) has occurred while communicating the mastership role of this FP to the CPP. The FP is currently [chars]Explanation An error occurred while communicating a change in the state (Active, Active with a Standby, or Standby) of the forwarding processor (FP). The error can cause an inconsistency of expected states between FPs and could affect the replication of state between the FPs.
Recommended Action Examine the system logs for errors. This error is usually temporary.
Error Message %CMFP-0-SPI4_MUX_HALT : SPI4 MUX driver has detected a critical error [chars]Explanation A SPI4 MUX driver has failed or detected a critical hardware fault. This could be due to a hardware defect or driver defect.
Recommended Action The only corrective action is to restart the FP
Error Message %CMFP-3-SPI4_MUX_STATUS : SPI4 MUX driver has detected a informational error [chars] (occurred [int] time(s))Explanation A SPI4 MUX driver has failed or detected a information hardware fault. This could be due to a hardware defect or driver defect.
Recommended Action Examine the logs for SPI4 MUX and hardware errors.
Error Message %CMFP-3-CPLD_ECSR_ERROR : An error has been detected on the ECSR busExplanation An error has been detected on the ECSR bus. This may cause problems when accessing the fowarding processor
Recommended Action Some of these errors are catastrophic and others are not. If the FRU did not restart assume corrective action was taken. Please check the chassis-manager logs for errors.
Error Message %CMFP-3-CPLD_ERP_ERROR : An error has been detected on the ERP bus (cause [int], phase [int])Explanation An error has been detected on the ERP bus. This may cause problems when accessing the fowarding processor
Recommended Action Some of these errors are catastrophic and others are not. If the FRU did not restart assume corrective action was taken. Please check the chassis-manager logs for errors.
Error Message %CMFP-3-N2_DDR_MBE : The encryption processor has detected an uncorrectable multi-bit error in memory at address [int]Explanation The encryption processor has detected an uncorrectable multi-bit in memory. This could be due to a hardware defect.
Recommended Action Examine the logs for encryption processor hardware errors.
CMRP Messages
Error Message %CMRP-0-CPLD_INITIALIZATION : The RP CPLD has failed initialization because [chars]Explanation The RP CPLD has failed to initialize. This could be due to a hardware or software driver defect.
Recommended Action Examine the hardware and CPLD driver logs and see if the logs provide information about a correctable problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-CPLD_IOCTL : A CPLD driver I/O control has failed because [chars]Explanation A CPLD driver I/O control has failed. This could be due to a hardware or software driver defect.
Recommended Action Examine the hardware and CPLD driver logs and see if the logs provide information about a correctable problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-I2C_INITIALIZATION : The RP I2C has failed initialization because [chars]Explanation The RP I2C has failed to initialize. These components provide low-level communications between the RP and the other cards in the system.
Recommended Action Note the time of the error message and examine the logs for I2C errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-3-I2C_READ : An I2C read has failed because [chars]Explanation An I2C read has failed. This could be due to a hardware or software defect.
Recommended Action Note the time of the error message and examine the logs for I2C errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-3-I2C_WRITE : An I2C write has failed because [chars]Explanation An I2C write has failed. This could be due to a hardware or software defect.
Recommended Action Note the time of the error message and examine the logs for I2C errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-BITS_INITIALIZATION : The RP BITS E1/T1 interface has failed initialization because [chars]Explanation The RP BITS E1/T1 interface has failed to initialize. This could be due to a hardware defect, a software driver defect or improper configuration.
Recommended Action Note the time of the error message and examine the logs for BITS driver or hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative
Error Message %CMRP-0-WANPLL_INITIALIZATION : The RP WAN PLL has failed initialization because [chars]Explanation The RP WAN PLL has failed to initialize. This could be due to a hardware or software driver defect.
Recommended Action Note the time of the error message and examine the logs for WAN PLL or hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-DDR_INITIALIZATION : The RP DDR has failed initialization because [chars]Explanation The RP DDR has failed to initialize. This could be due to a hardware or software driver defect.
Recommended Action Note the time of the error message and examine the logs for DDR or hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-3-DDR_SINGLE_BIT_ERROR : Single-bit DRAM ECC error: mme: [int], sbe: [int], address: [hex], pid: [int], name: [chars]Explanation The RP DRAM has single-bit ECC errors.
Recommended Action In most cases, the system self-corrects these single-bit ECC errors and no user action is necessary. If the problem persists, gather the console output with the error message along with the show tech-support command output and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-SERDES_INITIALIZATION : The RP Serial Bridge ASIC has failed initialization because [chars]Explanation The RP Serial Bridge ASIC has failed to initialize. This could be due to a hardware defect, software driver defect or improper internal configuration.
Recommended Action Note the time of the error message and examine the logs for Serial Bridge ASIC and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-3-HWLIB_INITIALIZATION : The hardware library has failed to initialize because [chars]Explanation This could be due to a hardware defect, software driver defect or improper internal configuration.
Recommended Action Note the time of the error message and examine the logs for CPLD hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-SERDES_IOCTL : A Serial Bridge driver I/O control has failed because [chars]Explanation A Serial Bridge driver I/O control has failed. This could be due to a hardware or software driver defect.
Recommended Action Note the time of the error message and examine the logs for Serial Bridge driver or hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-SERDES_INTERRUPT_DISPATCH : Serial Bridge interrupt dispatch error: [chars]Explanation Failed to dispatch an error interrupt from the Serial Bridge. This could be due to a software defect or inconsistent internal state.
Recommended Action Note the time of the error message and examine the logs for Serial Bridge errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-3-SERDES_ESI_LOCK_FAIL : The Serial Bridge ESI link between [chars] and [chars] failed to lockExplanation A Serial Bridge ESI link did not lock. This could be due to a hardware defect or a software configuration error.
Recommended Action Note the time of the error message and examine the logs for Serial Bridge and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-3-PFU_INITIALIZATION : The RP has failed to initialize a Power Supply/Fan module controller because [chars]Explanation The RP failed to initialize a Power Supply or Fan module controller. This could be due to a hardware defect or C2W access failure.
Recommended Action Note the time of the error message and examine the logs for C2W and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-HT_INITIALIZATION : The RP HyperTransport has failed initialization because [chars]Explanation The RP HyperTransport has failed initialization. This could be due to a hardware defect or HT driver defect.
Recommended Action Note the time of the error message and examine the logs for HT driver and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-HT_IOCTL : A RP HyperTransport driver I/O control has failed because [chars]Explanation A RP HyperTransport driver I/O has failed. This could be due to a hardware defect or HT driver defect.
Recommended Action Note the time of the error message and examine the logs for HT driver and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-6-HT_STATUS : R[int] hypertransport configured for F[int] activeExplanation The RP HyperTransport driver was properly configured for a newly active FP.
Recommended Action No user action is necessary. This is as informational message indicating normal system operation.
Error Message %CMRP-0-EHSA_INITIALIZATION : EHSA initialization has failed because [chars]Explanation EHSA has failed initialization. This could be due to a hardware or software defect.
Recommended Action Note the time of the error message and examine the logs for EHSA and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-EHSA_STATE_GET : Failed to get EHSA state because [chars]Explanation Failed to get EHSA state. This could be due to a hardware or software defect.
Recommended Action Note the time of the error message and examine the logs for EHSA and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-EHSA_STATE_SET : Failed to set EHSA state because [chars]Explanation Failed to set EHSA state. This could be due to a hardware or software defect.
Recommended Action Note the time of the error message and examine the logs for EHSA and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-3-IDPROM_ACCESS : Failed to access or process IDPROM '[chars]': [chars]Explanation Failed access or process an IDPROM. This could be due to a hardware defect, software defect or incorrect IDPROM content.
Recommended Action Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-3-IDPROM_SENSOR : One or more sensor fields from the idprom failed to parse properly because [chars].Explanation One or more sensor fields from the IDPROM failed to parse properly. This problem is often the result of a checksum failure in the IDPROM.
Recommended Action Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-CHASSIS_TYPE : The chassis type [chars] is invalid.Explanation The chassis type is invalid. This could be due to a hardware defect, software defect or incorrect IDPROM content.
Recommended Action Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-CHASSIS_STATUS : Failed to get chassis hardware status because [chars]Explanation The system failed to get the chassis hardware status.
Recommended Action Note the time of the error message and examine the logs for CPLD driver or hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-3-SENSOR_INITIALIZATION : Failed to initialize sensor monitoring because [chars].Explanation Sensor monitoring failed to initialize.
Recommended Action Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-3-SENSOR_TYPE : The sensor type is [int] is invalid.Explanation A sensor type is invalid. This could be due to a hardware defect, software defect or incorrect IDPROM content.
Recommended Action Note the time of the error message and examine the logs for IDPROM and hardware errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-CHASFS_OBJECT_CREATE : Failed to create chassis filesystem object [chars] because [chars]Explanation The hardware failed to create a chassis filesystem object.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-3-CHASFS_OBJECT_DESTROY : Failed to destroy chassis filesystem object [chars] because [chars]Explanation A chassis filesystem object that should have been destroyed was not destroyed.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-CHASFS_PROPERTY_CREATE : Failed to create chassis filesystem object [chars] property [chars] because [chars]Explanation A chassis filesystem property was not properly created.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-3-CHASFS_PROPERTY_DESTROY : Failed to destroy chassis filesystem proprty [chars]/[chars] because [chars]Explanation A chassis filesystem property that should have been destroyed was not destroyed.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-CHASFS_PROPERTY_GET : Failed to read chassis filesystem object [chars] property [chars] because [chars]Explanation A chassis filesystem property was not properly read by the system.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-CHASFS_PROPERTY_SET : Failed to write chassis filesystem object [chars] property [chars] because [chars]Explanation A chassis filesystem property failed to write.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-CHASFS_OBJECT_WATCH : Failed to watch chassis filesystem object [chars] because [chars]Explanation A chassis filesystem object was not watched because of the reason stated in the error message.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-CHASFS_OBJECT_NOT_PRESENT : Expected chassis filesystem object [chars] not present.Explanation A chassis filesystem object expected to be present is not. This could be due to a software defect or filesystem failure.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-CHASFS_PROPERTY_NOT_PRESENT : Expected chassis filesystem object [chars] property [chars] not present.Explanation A chassis filesystem object property expected to be present is not. This could be due to a software defect or filesystem failure.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-CHASFS_LOCATION_TRANSLATE : Failed to translate a location to a chasfs object name because [chars]Explanation The chassis manager failed to translate a location to a chasfs object name.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-INVALID_ARGUMENT : A system function was given an invalid argument.Explanation A system function was given an invalid argument. This is due to a software defect.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-ROLE_ADDRESS_UPDATE : Failed to update role-based EOBC IP addresses because [chars].Explanation The system failed to update a role-based EOBC IP address for the reason stated in the message line.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-ACTIVE_SLOTBAY_BIAS : The configured active slot/bay bias [int] is invalid.Explanation The configured active slot/bay bias is not 0 or 1. The default value of 0 is used.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-EVENT_LIBRARY : An event facility initialization or maintenance function failed because [chars]Explanation An event facility initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-PEER_TABLE : A peer table initialization or maintenance function failed because [chars]Explanation A peer table initialization or maintenance function failed. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-3-PEER_INVALID : A peer table entry has invalid state.Explanation A peer table entry has an invalid state. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-UIPEER_CREATE : Failed to create user interface peer.Explanation The system failed to create a user interface peer.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-SLOTS_INITIALIZATION : Failed to initialize chassis slot information because [chars]Explanation The system failed to initialize the chassis slot information.
Recommended Action Note the time of the error message and examine the logs for IDPROM or software errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-SLOT_INVALID : A card absolute slot number cannot be determined for this chassis typeExplanation An absolute slot number is invalid. This could be due to a software defect or incorrect IDPROM content.
Recommended Action Note the time of the error message and examine the logs for IDPROM or software errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-SIGNAL_INITIALIZATION : Failed to initialize signals because [chars]Explanation The system failed to initialize signals.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-SERVICES_INITIALIZATION : Failed to initialize general application services because [chars]Explanation The system failed to initialize application services.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-INTERNALS_INITIALIZATION : Failed to initialize internal state because [chars]Explanation The system failed to initilize the internal state for the reason mentioned in the error message.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-FP_MASTERSHIP_SET : Failed to set FP mastership because [chars]Explanation The router failed to establish ESP mastership.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-3-RP_MASTERSHIP_SET : Failed to set RP mastership [chars] because [chars]Explanation The router failed to establish RP mastership.
Recommended Action Reload the router.
Error Message %CMRP-0-RESOLVE_FRU : Failed to determine [chars] card because [chars]Explanation The router failed to determine a FRU state.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-IPC_INITIALIZATION : IPC initialization failed because [chars]Explanation IPC initialization failed. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-IPC_CONNECT_MASTER : IPC connection to the active RP failed because [chars]Explanation IPC connection to the active RP failed. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-IPC_CONNECTION_INVALID : An IPC connection has invalid state.Explanation An IPC connection has an invalid state. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-MQIPC_INITIALIZATION : MQIPC initialization failed because [chars]Explanation MQIPC initialization failed. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-MQIPC_ADVANCE : Failed to advance MQIPC queue because [chars]Explanation The MQIPC initialization failed.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-MESSAGE_REGISTER : Failed to register with active RP because [chars]Explanation The active RP failed to register.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-MESSAGE_RESPONSE : An invalid message response was received because [chars]Explanation An invalid message response was received. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-MESSAGE_RELAY : Failed to relay a message because [chars]Explanation Failed to relay a message. This could be due to a software defect or system resource exhaustion.
Recommended Action In most cases, the problem can be corrected by reloading the impacted hardware using the hw-module [slot | subslot] slot-number reload command. If the reload fails to correct the problem, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-3-PFU_MISSING : The platform does not detect a power supply in slot [int]Explanation There is no power supply in one of the power supply slots.
Recommended Action Insert a power supply into the empty slot. The router requires two power supplies because the fans in the power supply are needed to cool the router.
Error Message %CMRP-3-PFU_OIR : Failed to handle a [chars] oir event for PEM in slot [int], [chars]Explanation A power supply was inserted or removed into or from a router and the software did not properly handle the event.
Recommended Action Force an RP switchover if the system is configured with two RPs. If a switchover does not correct the problem or cannot be performed, reloading the router should resolve the issue.
Error Message %CMRP-3-PFU_FAN : Failed to handle fan failure for [chars] in slot [int], [chars]Explanation One or more fans have failed and the system is unable to properly handle the fan failure.
Recommended Action Force an RP switchover if the system is configured with two RPs. If a switchover does not correct the problem or cannot be performed, reloading the router should resolve the issue.
Error Message %CMRP-3-PFU_FAILURE : Failed to handle power supply failure for [chars] in slot [int], [chars]Explanation A power supply has failed and the system is unable to properly handle the failure.
Recommended Action Force an RP switchover if the system is configured with two RPs. If a switchover does not correct the problem or cannot be performed, reloading the router should resolve the issue.
Error Message %CMRP-3-PEM_REMOVE_SHUT : The system will shut down in [int] minutesExplanation A power supply has been removed and the router will shutdown to protect itself from overheating in the amount of time stated in the error message.
Recommended Action Reinsert a power supply into the power supply slot as soon as possible. The second power supply is required because the fans in the power supply are essential in monitoring router temperature.
Error Message %CMRP-6-FP_HA_STATUS : F[int] redundancy state is [chars]Explanation The ESP has transitioned into a new High Availability state.
Recommended Action No user action is necessary. This is an informational message.
Error Message %CMRP-6-FP_HA_SB_NOTREADY : FP switchover: F[int] [chars]Explanation The standby ESP is not ready for a switchover.
Recommended Action No user action is necessary.
Error Message %CMRP-3-FRU_NOPARTNUM : Cannot get part number for [chars]: [chars].Explanation The FRU IDPROM cannot be read or does not contain a valid part number field.
Recommended Action The FRU IDPROM should be repaired.
Error Message %CMRP-3-FRU_INCOMPATIBLE : [chars] has been held in reset: [chars] is incompatible with [chars]Explanation The part number read from the FRU IDPROM is invalid for this chassis type.
Recommended Action Remove the FRU from the chassis.
Error Message %CMRP-3-PWR_FAULT : Shutting down [chars] because power fault on primary is [chars] and secondary is [chars]Explanation The FRU has been shutdown as a result of a power issue.
Recommended Action Check to ensure the router is receiving power. Otherwise, note the time of the error message and examine the logs for power-related errors. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-PWR_FAULT_INITIALIZATION : Power fault monitor initialization has failed because [chars]Explanation The power fault monitor has failed to initialize.
Recommended Action Note the time of the error message and examine the Chassis Manager logs. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-0-RESOURSE : Resource allocation failed in [chars] because [chars]Explanation The system is unable to allocate the requested resource.
Recommended Action In most cases, this message is seen as a result of a temporary resource issue. Retry the request for the resource when the system is experiencing lower traffic volumes. If the message persists, reload the router using the reload command.
Error Message %CMRP-6-RP_SWITCH_SB_SYNC : RP switchover: [chars]Explanation The RP switch synchronization timer expired.
Recommended Action No user action is necessary.
Error Message %CMRP-3-RP_SWITCH_SB_NOT_READY : RP switchover: [chars]Explanation An RP switchover occurred when the standby RP was not ready. The standby RP reset.
Recommended Action No user action is necessary. Allow the standby RP to reset.
Error Message %CMRP-0-SYSPAGE_WRITE_ERROR : The syspage chassis-type write has failed because [chars]Explanation The syapge chassis-type write failed. This could be due to a software defect.
Recommended Action Note the time of the error message and examine the Chassis Manager logs. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-3-HWMOD_FAIL : hw-module [chars] command failed ([chars])Explanation The last hw-module command that was entered failed to complete
Recommended Action Retry the command. If the retry of the command fails, reload the router. If reloading the router fails to resolve the problem, note the time of the error message and examine the Chassis Manager logs. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, and the output of show tech-support and provide the gathered information to a Cisco technical support representative.
Error Message %CMRP-3-RP_SB_RELOAD : Reload of Standby RP failed: [chars]Explanation A request to reload the standby RP failed.
Recommended Action Manually reload the standby RP. If that fails, configure SSO or RPR and then attempt the reload. If the problem persists, note the time of the error message and examine the Chassis Manager logs. If the logs provide information about a correctable problem, correct the problem. If the problem is not correctable or the logs are not helpful, collect the output of the error message, the logs, show redundancy state, and the output of show tech-support and provide the gathered information to a Cisco technical support representative
Error Message %CMRP-6-RP_SB_RELOAD_REQ : Reloading Standby RP: [chars]Explanation A requested reload of Standby RP has been requested.
Recommended Action No action is necessary.
Error Message %CMRP-3-RP_RESET : RP is resetting : [chars]Explanation This RP is resetting due to the reason specified.
Recommended Action No action is necessary.
Error Message %CMRP-6-DUAL_IOS_STARTING : Software redundant IOS configured; starting standby in [int] seconds.Explanation Chassis manager received notification that IOS software redundancy has been configured. The standby IOS will be started in the time specified.
Recommended Action No action is necessary.
Error Message %CMRP-6-DUAL_IOS_STOPPING : Bringing down standby IOSExplanation Chassis manager received notification to stop the standby IOS instance. This may be for a redundancy mode change. Depending on the reason, the standby may be subsequently restarted.
Recommended Action No action is necessary.
Error Message %CMRP-6-DUAL_IOS_REBOOT_REQUIRED : Configuration must be saved and the chassis must be rebooted for IOS redundancy changes to take effectExplanation Chassis manager received notification that IOS software redundancy has been configured. For these changes to take effect, the system must be restarted.
Recommended Action Reload the chassis.
Error Message %CMRP-6-SINGLE_IOS_REBOOT_RECOMMENDED : Configuration must be saved and the chassis should be rebooted for optimal single-IOS executionExplanation Chassis manager received notification that IOS software redundancy has been unconfigured. For optimal runtime resource allocation, the system must be restarted.
Recommended Action Reload the chassis.
Error Message %CMRP-3-CHASSIS_MONITOR_FRU_BOOT_STATUS : Reloading [chars] because the FRU boot status is unknownExplanation The time at which the FRU started booting is not available. This time is used to check the boot status of the FRU.
Recommended Action Remove the FRU from the chassis is the FRU is continously reloaded.
Error Message %CMRP-3-CHASSIS_MONITOR_ONLINE_TIME_EXCEEDED : Reloading [chars] because it has failed to come onlineExplanation A FRU has failed to come online within the maximum boot time.
Recommended Action Remove the FRU from the chassis is the FRU is continously reloaded.
Error Message %CMRP-3-CHASSIS_MONITOR_READY_TIME_EXCEEDED : Reloading [chars] because it has failed to become ready for packet processingExplanation The FRU failed to become ready within the maximum ready time. This message applies to FP FRUs. A switchover will be performed is another FP is available.
Recommended Action Remove the FRU from the chassis is the FRU is continously reloaded.
Error Message %CMRP-3-CHASSIS_MONITOR_ONLINE_TIME_IGNORED : [chars] exceeded online time but will not be reset because fault ignore is configuredExplanation The FRU failed to come online within the maximum online time. This message applies to all FRUs. A reload will not be performed because fault ignore is configured.
Recommended Action No action is necessary.
Error Message %CMRP-3-CHASSIS_MONITOR_READY_TIME_IGNORED : [chars] exceeded ready time but will not be reset because fault ignore is configuredExplanation The FRU failed to become ready within the maximum ready time. This message applies to FP FRUs. A switchover and/or reload will not be performed because fault ignore is configured.
Recommended Action No action is necessary.
CPP_BQS Messages
Error Message %CPPBQS-4-QMOVEFAIL : CPP [dec] schedule [chars] queue move failed (%#x) - SEID=%#x SID=%#XExplanation A Cisco QuantumFlow Processor buffering, queing and scheduling (BQS) schedule queue move operation failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPBQS-4-REPARENTFAIL : CPP [dec] schedule [chars] reparent failed (%#x) - SEID=%#X SID=%#xExplanation A Cisco QuantumFlow Processor buffering, queing and scheduling (BQS) schedule reparent operation failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPBQS-5-QMOVEDONE : CPP [dec] schedule [chars] queue move doneExplanation Though an error occurred during a Cisco QuantumFlow Processor buffering, queing and scheduling (BQS) schedule queue move operation, the operation completed successfully.
Recommended Action No action required. To investigate the cause of the error, examine the logs for hardware or software errors.
Error Message %CPPBQS-5-QMOVESTUCK : CPP [dec] schedule [chars] queue move stuckExplanation A Cisco QuantumFlow Processor buffering, queing and scheduling (BQS) schedule queue move operation could not proceed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_BQS-3-MPASS_FS_REG : CPP BQS PROXY feature special vector [dec] registrationExplanation Cisco QuantumFlow Processor internal software error. The buffering, queing and scheduling (BQS) of the multipass registration failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_BQS-3-PROXY_IPC_INIT_FAILED : CPP BQS Proxy IPC interface initialization failureExplanation Cisco QuantumFlow Processor internal software error. The buffering, queing and scheduling (BQS) initialization failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_BQS-4-CARVE : [chars]: size [int] SW carved out memory region initialization failed.Explanation A buffering, queing and scheduling (BQS) proxy failed to initialize the software memory region.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_BQS-4-CMD_ACTIVE : CPP BQS Proxy Command, correlator [int]Explanation A buffering, queing and scheduling (BQS) proxy command was received, but the correlator failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_BQS-4-INIT_FAILED : CPP BQS RM Proxy, region [chars]Explanation A buffering, queing and scheduling (BQS) proxy failed to initialize or resize the managed software.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_BQS-4-INVALID_SUBTYPE : CPP BQS RM Proxy subtype [int]Explanation A buffering, queing and scheduling (BQS) proxy failed after receiving an invalid sub-type.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_BQS-4-PROXY_IPC_SEND : failure: [chars]Explanation A buffering, queing and scheduling (BQS) proxy send response failed causing the response to be dropped.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_BQS-4-RESIZE : CPP BQS Proxy Memory Manager, region [chars]Explanation A buffering, queing and scheduling (BQS) proxy failed to resize the managed software.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPBQS-5-limit(SRTMEMLOW : CPP [dec] HW [chars]:[chars] schedule resources depleted - [dec]%% availableExplanation Cisco QuantumFlow Processor internal software error. The buffering, queing and scheduling (BQS) resources have dropped below critical threshold.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
CPPDRV Messages
Error Message %CPPDRV-3-HALT : [chars]([dec]) Interrupt : [chars] Seq:%03d Halt bit set.Explanation A serious Cisco QuantumFlow Processor hardware error has occured.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPDRV-4-ALLOC_NOTF : CPP[dec]: Failed to Allocate: ([chars])Explanation A Cisco QuantumFlow Processor function failed to allocate data.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information..
Error Message %CPPDRV-4-CLEANUP_NOTF : Failed to Cleanup: ([chars])Explanation A Cisco QuantumFlow Processor function failed to clean up data.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPDRV-4-DESTROY_NOTF : Failed to destroy connection :([chars])Explanation A Cisco QuantumFlow Processor function failed to end a connection.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPDRV-4-FATAL_ACQUIRE_LOCK : CPP[dec]: ([hex]) Failed to acquire memory lock [chars]Explanation Cisco QuantumFlow Processor software failed to acquire a shared memory lock.
Recommended Action Examine the logs for software and hardware errors. If the problem persists, 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 gathered information..
Error Message %CPPDRV-4-FATAL_ALLOCATE : CPP[dec]: ([hex]) Failed to allocate [chars] - [chars]Explanation The Cisco QuantumFlow Processor failed to allocate data.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPDRV-4-FATAL_ATTACH : CPP[dec]: ([hex]) FAILED: to attach [chars]Explanation A Cisco QuantumFlow Processor device failed to attach.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information..
Error Message %CPPDRV-4-FATAL_CREATE : ([hex]) Failed to create [chars] - [chars]Explanation The Cisco QuantumFlow Processor failed to create a device.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPDRV-4-FATAL_CREATE_ID : CPP[dec]: ([hex]) Failed to create [chars] - [chars]Explanation The Cisco QuantumFlow Processor failed to create a device.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPDRV-4-FATAL_GET_DETAILS : CPP[dec]: ([hex]) Failed to get [chars] details - [chars]Explanation The Cisco QuantumFlow Processor failed to obtain device details.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPDRV-4-FATAL_INIT : ([hex]) Failed to initialize [chars] - [chars]Explanation The Cisco QuantumFlow Processor failed to initialize a device.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPDRV-4-FATAL_INIT_ID : CPP[dec]: ([hex]) Failed to initialize [chars] - [chars]Explanation The Cisco QuantumFlow Processor failed to initialize a device.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPDRV-4-FATAL_INTERNAL : CPP[dec]: ([hex]) Internal Error [chars]Explanation The Cisco QuantumFlow Processor experienced an internal coding error.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPDRV-4-FATAL_INTERRUPT_CLEAR : CPP[dec]: ([hex]) Failed to clear [chars] interruptExplanation The Cisco QuantumFlow Processor failed to clear an interrupt node.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPDRV-4-FATAL_INTERRUPT_HANDLER : CPP[dec]: ([hex]) Failed to register [chars] interrupt handler - [chars]Explanation The Cisco QuantumFlow Processor failed to register an interrupt handling routine.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPDRV-4-FATAL_INTERRUPT_INIT : CPP[dec]: ([hex]) Failed to initialize [chars] interrupt - [chars]Explanation The Cisco QuantumFlow Processor failed to initialize an interrupt handling routine.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPDRV-4-FATAL_INTERRUPT_OPEN : CPP[dec]: ([hex]) Failed to access [chars] interrupt node - [chars]Explanation The Cisco QuantumFlow Processor failed to open an interrupt handling routine.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPDRV-4-FATAL_MEM_CLEAR : CPP[dec]: ([hex]) Failed to clear memory [chars]Explanation The Cisco QuantumFlow Processor software failed to clear a memory location.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPDRV-4-FATAL_MEM_SIZE : CPP[dec]: ([hex]) Failed to acquire memory size [chars]Explanation The Cisco QuantumFlow Processor software failed to acquire size information for a block of memory.
Recommended Action Examine the logs for software or hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPDRV-4-FATAL_MEM_WRITE : CPP[dec]: ([hex]) Failed to write to memory [chars]Explanation The Cisco QuantumFlow Processor software failed to write to a memory location.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPDRV-4-FATAL_PLAT_DB : CPP[dec]: ([hex]) Platform failure accessing [chars]Explanation The Cisco QuantumFlow Processor platform database query failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPDRV-4-FATAL_RELEASE_LOCK : CPP[dec]: ([hex]) Failed to release memory lock [chars]Explanation The Cisco QuantumFlow Processor software failed to release a shared memory lock.
Recommended Action Examine the logs for software or hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPDRV-4-FATAL_UNSUPPORT : CPP[dec]: ([hex]) - unsupported CPP TYPE. CPP TYPE:[dec]Explanation The Cisco QuantumFlow Processor experienced an unsupported CPP type.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPDRV-4-HOT : [chars]([dec]) Interrupt : [chars] Seq:%03d repeating interrupt has been disabled.Explanation A repeating hardware interrupt has been disabled on the Cisco QuantumFlow Processor.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPDRV-4-INIT_NOTF : Failed to initialize: ([chars])Explanation A Cisco QuantumFlow Processor function failed to initialize.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPDRV-4-INIT_NOTF_ID : CPP[dec]: Failed to initialize: ([chars])Explanation A Cisco QuantumFlow Processor function failed to initialize.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPDRV-4-LOCKDOWN : [chars]([dec]) CPP Driver LOCKDOWN due to fatal error.Explanation A fatal error for a Cisco QuantumFlow Processor driver has caused driver lockdown.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPDRV-4-TCAM_PERR : [chars]([dec]) TCAM Parity error TCAM device #[dec] at offset 0x%08X.Explanation The Cisco QuantumFlow Processor has experienced a parity error in a ternary content addressable memory (TCAM) device.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPDRV-4-TCAM_PERR_FAILURE : [chars]([dec]) Failed to correct TCAM Parity error. Parity error detection disabled.Explanation The Cisco QuantumFlow Processor has experienced a parity error in a ternary content addressable memory (TCAM) device. The Cisco QuantumFlow Processor has failed to correct the TCAM parity error and further parity error detection has been disabled.
Recommended Action Examine the logs for software or hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPDRV-7-INTR : [chars]([dec]) Interrupt : [chars]Explanation A Cisco QuantumFlow Processor hardware interrupt has occurred.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPDRV-5-limit(ADRSPC_LIMIT : Address space limit [int] KB reached,Explanation Cisco QuantumFlow Processor attempted to map additional forwarding engine address space.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
CPPEXMEM Messages
Error Message %CPPEXMEM-5-LOWMEM : CPP [dec] [chars] memory low - [dec] percent depletedExplanation A Cisco QuantumFlow Processor memory resource has dropped below a critical level.
Recommended Action No action is required.
Error Message %CPPEXMEM-6-MEM : CPP [dec] [chars] memory recovered - [dec] percent depletedExplanation A Cisco QuantumFlow Processor memory resource has recovered after having dropped below the low threshold level.
Recommended Action No action is required.
Error Message %CPPEXMEM-4-limit(NOMEM : CPP [dec] [chars] memory allocation ([chars]) failedExplanation An allocation for a Cisco QuantumFlow Processor memory resource has failed.
Recommended Action No action is required.
CPP_FM Messages
Error Message %CPP_FM-5-CPP_FM_FIELD_IGNORED : Matching on field type [int] ([chars] value [int] ([hex]))Explanation The user is attempting to use a classification criterion that is not supported by the Cisco QuantumFlow Processor.
Recommended Action No action is required.
CPPFPM Messages
Error Message %CPPFPM-7-FMANACLLOGMISSMSG : access-list logging datapath rate-limited or missed [int] packet[chars]Explanation Packet matching logs were missed because the access list log messages were rate-limited or no access list log buffers were available.
Recommended Action No action is required.
Error Message %CPPFPM-7-IPACCESSLOGDP : list [chars] [chars] [chars] [chars] [chars]-> [chars] ([int]/[int]), [int] packet[chars]Explanation A packet whose IP address matches the access list log criteria was detected.
Recommended Action No action is required.
Error Message %CPPFPM-7-IPACCESSLOGNP : list [chars] [chars] [int] [chars] [chars]-> [chars], [int] packet[chars]Explanation A packet whose IP address matches the access list log criteria was detected.
Recommended Action No action is required.
Error Message %CPPFPM-7-IPACCESSLOGP : list [chars] [chars] [chars] [chars]([int]) [chars]-> [chars]([int]), [int] packet[chars]Explanation A packet whose IP address matches the access list log criteria was detected.
Recommended Action No action is required.
CPP_FR Messages
Error Message %CPP_FR-3-PROXY_IPC_INIT_FAILED : Frame Relay Proxy IPC interface initialization failureExplanation A Cisco QuantumFlow Processor experienced an internal software error in which a frame relay proxy initialization failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_FR-4-INV_PROXY_MSG : CPP FR Proxy received invalid IPC message ID [dec]Explanation A Cisco QuantumFlow Processor experienced an internal software error in which a frame relay proxy received an invalid message identification.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_FR-4-PROXY_IPC_ALLOC_FAIL : CPP Frame Relay Proxy response to msg id [int] lost due toExplanation A Cisco QuantumFlow Processor experienced an internal software error in which a frame relay proxy message response failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
CPPHA Messages
Error Message %CPPHA-4-BULKSYNC : bulk sync processing failed to completeExplanation A Cisco QuantumFlow Processor bulk synchronization processing failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information..
Error Message %CPPHA-4-CDMDONE : CPP [dec] microcode crashdump creation completed.Explanation A Cisco QuantumFlow Processor CDM operation completed generating a microcode crashdump.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPHA-4-FAILURE : CPP [dec] failure [chars] detectedExplanation A Cisco QuantumFlow Processor failure has been detected.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPHA-4-FAULT : CPP:[dec] desc:[chars] det:[chars] class:[chars] sev:[chars] id:[dec] cppstate:[chars]Explanation A Cisco QuantumFlow Processor fault has occurred.
Recommended Action No action is required.
Error Message %CPPHA-4-FAULTCRASH : CPP [dec] unresolved fault detected, initiating crash dump.Explanation A Cisco QuantumFlow Processor unresolved fault has been detected, initiating a crash dump.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPHA-4-INITFAIL : CPP [dec] initialization failed - [chars] (%#x)Explanation A Cisco QuantumFlow Processor initialization failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPHA-4-NOCDM : CPP [dec] CDM not running.Explanation A Cisco QuantumFlow Processor CDM process is not running.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPPHA-7-SYSINIT : CPP HA system [chars].Explanation A Cisco QuantumFlow Processor system initialization state is achieved.
Recommended Action No action is required.
Error Message %CPPHA-8-READY : CPP [dec] loading and initialization completeExplanation The Cisco QuantumFlow Processor has been successfully loaded and initialized, and is ready to be configured for forwarding packets.
Recommended Action No action is required.
Error Message %CPPHA-8-START : CPP [dec] [chars] image [chars]Explanation A Cisco QuantumFlow Processor is starting with the specified image.
Recommended Action No action is required.
Error Message %CPPHA-8-SYSREADY : CPP client process [chars] ([dec] of [dec]) ready.Explanation A Cisco QuantumFlow Processor client process has begun and it has registered with the HA server.
Recommended Action No action is required.
Error Message %CPPHA-4-limit(FAULTRATE : CPP:[dec] desc:[chars] det:[chars] class:[chars] sev:[chars] id:[dec] cppstate:[chars]Explanation A Cisco QuantumFlow Processor fault has occurred.
Recommended Action No action is required.
CPP_IPHC_PROXY Messages
Error Message %CPP_IPHC_PROXY-4-INVALID_IPC_INPUT : [chars] CPP IPHC Client Proxy failureExplanation The Cisco QuantumFlow Processor IP header compression (IPHC) experienced an invalid interprocess communications (IPC) message subtype.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
CPP_LDN Messages
Error Message %CPP_LDN-3-PROXY_IPC_INIT_FAILED : CPP LDN Proxy IPC interface initialization failureExplanation There was a Cisco QuantumFlow Processor internal software error. LDN IPC interface initialization failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_LDN-4-PROXY_GPM_RSRC_FAIL : failure: [chars]Explanation The LDN proxy failed in performing a GPM operation.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_LDN-4-PROXY_IPC_INVALID : failure: [dec]Explanation The LDN proxy received an invalid IPC message from the client.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_LDN-4-PROXY_IPC_SEND : failure: [chars]Explanation An LDN proxy send response failed causing the response to be dropped.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
CPP_MLP Messages
Error Message %CPP_MLP-3-PROXY_IPC_INIT_FAILED : CPP MLP Proxy IPC interface initialization failureExplanation A Cisco QuantumFlow Processor function failed in an attempt to initialize MLP. The MLP bundle interfaces will not be functional while this condition exists.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_MLP-4-EARLY_RX_CLEANUP : CPP MLP Early Receive cleanup error ([chars])Explanation A Cisco QuantumFlow Processor function failed in an attempt to cleanup multilink early receive.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_MLP-4-EARLY_RX_INIT : CPP MLP Early Receive initialization error ([chars])Explanation A Cisco QuantumFlow Processor function experienced a multilink early receive error. This could cause lost MLP encapsulated packets during member link or bundle bringup and possibly cause a failure to complete member link or bundle initialization.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_MLP-4-INV_PROXY_MSG : CPP MLP Proxy received invalid Message ID [dec]Explanation A Cisco QuantumFlow Processor error in which an invalid MLP message ID was received.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_MLP-4-PROXY_B_TX_IDLE_LINK_TRANSITION : CPP MLP Proxy ([chars] [chars]) invalid Bundle state [chars] ([dec]) forExplanation A Cisco QuantumFlow Processor error in which a multilink idle-link transition invalid bundle state was received.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_MLP-4-PROXY_DUP_LINK_ID : CPP MLP Proxy ([chars] [chars]) duplicate Link ID [dec] for interface [chars]Explanation A Cisco QuantumFlow Processor error in which a duplicate MLP proxy message link ID was received. The associated MLP bundle interface or member link interface may not be functional while this condition exists.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_MLP-4-PROXY_INV_BUFFER_LIMIT : CPP MLP Proxy ([chars] [chars]) indicated an invalid Rx buffer limitExplanation A Cisco QuantumFlow Processor error in which an invalid MLP buffer limit was reached. The associated MLP bundle interface may not be functional while this condition exists.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_MLP-4-PROXY_INV_BUNDLE_STATE : CPP MLP Proxy ([chars] [chars]) invalid Bundle state [chars] ([dec]) forExplanation A Cisco QuantumFlow Processor error involving an invalid MLP bundle state. The associated MLP bundle interface may not be functional while this condition exists.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_MLP-4-PROXY_INV_CLASS_INFO : CPP MLP Proxy ([chars] [chars]) invalid Class Info (Base: 0x%08x, Num: [dec])Explanation A Cisco QuantumFlow Processor error involving invalid MLP proxy class information. The associated MLP bundle interface may not be functional while this condition exists.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_MLP-4-PROXY_INV_LINK_ID : CPP MLP Proxy ([chars] [chars]) invalid Link ID [dec] for interface [chars]Explanation A Cisco QuantumFlow Processor error in which an invalid MLP proxy message link ID was received. The associated MLP bundle interface or member link interface may not be functional while this condition exists.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_MLP-4-PROXY_INV_LINK_STATE : CPP MLP Proxy ([chars] [chars]) invalid Link state [chars] ([dec]) for interfaceExplanation A Cisco QuantumFlow Processor error involving an invalid MLP Proxy link state. The associated MLP bundle member link interface may not be functional while this condition exists.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_MLP-4-PROXY_INV_LOST_FRAG_TO : CPP MLP Proxy ([chars] [chars]) indicated an invalid lost fragment timeout ([dec]} for interface [chars]Explanation A Cisco QuantumFlow Processor error in which an invalid MLP proxy lost fragment timeout was detected. The associated MLP bundle interface may not be functional while this condition exists.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_MLP-4-PROXY_INV_MRRU : CPP MLP Proxy ([chars] [chars]) invalid MRRU [dec] for interface [chars]Explanation A Cisco QuantumFlow Processor error in which an MLP proxy message contained an invalid MRRU interface. The associated MLP bundle interface may not be functional while this condition exists.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_MLP-4-PROXY_INV_RX_TX_INTF_VALUE : CPP MLP Proxy ([chars] [chars]) invalid Rx/Tx interface value [dec] for interface [chars]Explanation A Cisco QuantumFlow Processor error in which an MLP proxy contained an invalid Rx/Tx interface value. The associated MLP bundle or memeber link interface may not be functional while this condition exists.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_MLP-4-PROXY_INV_TX_LINK_FRAG_SIZE : CPP MLP Proxy ([chars] [chars]) indicated an invalid Tx Link optimal fragment size ([dec]) for interface [chars]Explanation A Cisco QuantumFlow Processor error in which an MLP Proxy contains an invalid Tx link optimal fragment size. The associated MLP bundle member link interface may not be functional while this condition exists.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_MLP-4-PROXY_INV_TX_LINK_WEIGHT : CPP MLP Proxy ([chars] [chars]) indicated an invalid Tx Link weightExplanation A Cisco QuantumFlow Processor error in which an MLP proxy message indicated an invalid Tx link weight. The associated MLP bundle member link interface may not be functional while this condition exists.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_MLP-4-PROXY_IPC_ALLOC_FAIL : CPP MLP Proxy ([chars]) response lost due to buffer allocation failure (Interface [chars]}Explanation A Cisco QuantumFlow Processor error in which an MLP proxy response was lost due to buffer allocation failure. The associated MLP bundle or member link interface may not be functional while this condition exists.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_MLP-4-PROXY_LAI_TX_IDLE_LINK_TRANSITION : CPP MLP Proxy ([chars] [chars]) invalid Link state [chars] ([dec]) for interface [chars]/[chars]Explanation A Cisco QuantumFlow Processor error involving an invalid link state while performing an idle-link transition. The associated MLP bundle or member link interface may not be functional while this condition exists.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_MLP-4-PROXY_LIA_TX_IDLE_LINK_TRANSITION : CPP MLP Proxy ([chars] [chars]) invalid Link state [chars] ([dec]) for interface [chars]/[chars]Explanation A Cisco QuantumFlow Processor error involving an invalid link state while performing an idle-link transition. The associated MLP bundle or member link interface may not be functional while this condition exists.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_MLP-4-PROXY_MAX_FRAGS_UNDEFINED : CPP MLP Proxy ([chars] [chars]) max fragments undefined for interface [chars]Explanation A Cisco QuantumFlow Processor MLP Proxy error in which the maximum fragments parameter was undefined. The associated MLP bundle or member link interface may not be functional while this condition exists.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_MLP-4-PROXY_NULL_BUNDLE : CPP MLP Proxy ([chars] [chars]) NULL Bundle sub-block for interface [chars]Explanation A Cisco QuantumFlow Processor error in which there is an MLP proxy was received with a null bundle sub-block. The associated MLP bundle or member link interface may not be functional while this condition exists.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_MLP-4-PROXY_NULL_LINK : CPP MLP Proxy ([chars] [chars]) NULL Member Link sub-block for interface [chars]Explanation A Cisco QuantumFlow Processor error in which there is an MLP proxy was received with a null member-link sub-block. The associated MLP bundle or member link interface may not be functional while this condition exists.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_MLP-5-PROXY_IPC_ALLOC_FAIL2 : CPP MLP Proxy ([chars]) response lost due to buffer allocation failure (Interface [chars])Explanation A Cisco QuantumFlow Processor error in which an MLP proxy response was lost due to buffer allocation failure. The associated MLP bundle or member link interface may not be functional while this condition exists.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_MLP-5-PROXY_SYNC : CPP MLP Proxy ([chars] [chars]) Bundle/Link sync issue with interface [chars]Explanation A Cisco QuantumFlow Processor experienced an error in which there is an invalid MLP proxy bundle or link interface syncronization.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
CPP_NAT Messages
Error Message %CPP_NAT_PROXY-4-limit(INVALID_IPC_INPUT : number of instances is invalid; it is [dec]Explanation Cisco QuantumFlow Processor network address translation (NAT) proxy received an IPC with an unexpected format or data.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_NAT_PROXY-4-limit(INVALID_IPC_SUBTYPE : subtype is [dec]Explanation Cisco QuantumFlow Processor network address translation (NAT) proxy received an IPC with an unexpected subtype.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_NAT_PROXY-4-limit(NAT_INIT_FAIL : nat init failure rc= [dec]Explanation The Cisco QuantumFlow Processor network address translation (NAT) proxy experienced an initialization failure
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %CPP_NAT_PROXY-4-limit(NAT_SEND_IPC_FAIL : rc= [dec]Explanation The Cisco QuantumFlow Processor network address translation (NAT) proxy experienced a failure when trying to send an IPC.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
CPPOSLIB Messages
Error Message %CPPOSLIB-4-CLEAN_NOTIFY : Failed to cleanup: ([chars])Explanation A Cisco QuantumFlow Processor function failed to cleanup data.
Recommended Action No action is required.
Error Message %CPPOSLIB-4-GET_NOTIFY : Failed to get data: ([chars])Explanation A Cisco QuantumFlow Processor function failed to obtain data.
Recommended Action No action is required.
Error Message %CPPOSLIB-4-INIT_NOTIFY : Failed to initialize: ([chars])Explanation A Cisco QuantumFlow Processor function failed to initialize.
Recommended Action No action is required.
Error Message %CPPOSLIB-4-REGISTER_NOTIFY : Failed to register: ([chars])Explanation A Cisco QuantumFlow Processor function failed to register.
Recommended Action No action is required.
Error Message %CPPOSLIB-4-limit(ERROR_NOTIFY : [chars] encountered an errorExplanation The Cisco QuantumFlow Processor encountered a print error message at the console.
Recommended Action No action is required.
CPPTCAMRM Messages
Error Message %CPPTCAMRM-7-HIGH_WATER_MARK : TCAM resources in the system is limited.Explanation A Cisco QuantumFlow Processor ternary content addressable memory (TCAM) device has a limited number of free cells remaining to allocate.
Recommended Action No action is required.
Error Message %CPPTCAMRM-7-LOW_WATER_MARK : There is sufficient TCAM resources in the system.Explanation A Cisco QuantumFlow Processor ternary content addressable memory (TCAM) device has sufficient number of free cells left for allocation.
Recommended Action The message is for information purposes. No action is required.
Error Message %CPPTCAMRM-7-TCAM_RSRC_ERR : Allocation failed because of insufficient TCAM resources in theExplanation A Cisco QuantumFlow Processor ternary content addressable memory (TCAM) device has no free cells remaining to accomodate the current allocation request.
Recommended Action No action is required.
EMD Messages
Error Message %EMD-3-PFU_INITIALIZATION : The RP has failed to initialize a Power Supply/Fan module controller because [chars]Explanation The route processor (RP) failed to initialize a power supply or a fan module controller. This error could be caused by a hardware defect or a C2W access failure.
Recommended Action Examine the logs for C2W and hardware errors.
Error Message %EMD-3-IDPROM_ACCESS : Failed access or process an IDPROM because [chars]Explanation The system failed to access an IDPROM or an IDPROM process failed. This error can occur from a hardware defect, software defect, or incorrect IDPROM content.
Recommended Action Examine the logs for IDPROM and hardware errors.
Error Message %EMD-3-IDPROM_SENSOR : One or more sensor fields from the idprom failed to parse properly because [chars].Explanation One or more IDPROM sensor fields failed to parse properly. The most likely reason is a checksum failure in the IDPROM from incorrect IDPROM content.
Recommended Action Examine the logs for IDPROM and hardware errors.
Error Message %EMD-3-SENSOR_INITIALIZATION : Failed to initialize sensor monitoring because [chars].Explanation The system failed to initialize an IDPROM sensor monitoring process. This error can occur from a hardware defect, software defect, or incorrect IDPROM content.
Recommended Action Examine the logs for IDPROM and hardware errors.
Error Message %EMD-0-EVENT_LIBRARY : An event facility initialization or maintenance function failed because [chars]Explanation An event facility initialization or maintenance function failed. This error could be due to a software defect or system resource limitation.
Recommended Action Restart the card.
Error Message %EMD-0-RESOLVE_FRU : Failed to determine [chars] card because [chars]Explanation The system was unable to to determine a card state. This error could be due to a software defect or system resource limitation.
Recommended Action Restart the card.
Error Message %EMD-0-SERVICES_INITIALIZATION : Failed to initialize general application services because [chars]Explanation The system failed to initialize the application services. This error could be due to a software defect or system resource limitation.
Recommended Action Restart the card.
ERSPAN Messages
Error Message %ERSPAN-4-MEM_INIT_FAILED : Allocation of [chars] memory failed for ERSPANExplanation Encapsulated remote switch port analyzer (ERSPAN) initialization of a channel pool failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %ERSPAN-4-PKT_REPLICA_INIT_FAILED : Register to Generic Packet Replication failed for ERSPANExplanation Encapsulated remote switch port analyzer (ERSPAN) initialization of the packet replication registration failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
ESS_FEATURE Messages
Error Message %ESS_FEATURE-4-ESF_STUB : CPP ESS per-session feature ([chars]) executes stub entry in [chars] directionExplanation A Cisco QuantumFlow Processor experienced an internal software error involving the ESS per-session feature stub entry.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
ESS_IPSUB Messages
Error Message %ESS_IPSUB-4-ESS_IPSUB_STUB : CPP ESS IPSUB executes stub entry in [chars] directionExplanation A Cisco QuantumFlow Processor experienced an internal software error involving the ESS IPSUB stub entry.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %ESS_IPSUB-4-FSOL_THROTTLE_ERR : Allocation of [chars] memory failed for ESS IP SubscriberExplanation Allocation of the memory resource demanded by the ESS IPSUB FSOL throttle failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
ESS_PROXY Messages
Error Message %ESS_PROXY-3-IPC_THROTTLE_ERR : Allocation of [chars] memory failed for ESS ProxyExplanation Allocation of a memory resource demanded by the ESS proxy throttle failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %ESS_PROXY-3-KA_CHANNEL_ALLOC_FAILED : CPP ESS Proxy Session Keepalive channel creation failure.Explanation A Cisco QuantumFlow Processor experienced an internal software error in which the ESS proxy session keepalive creation failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %ESS_PROXY-3-KA_PKT_REPLICA_REG_FAILED : CPP ESS Proxy Session Keepalive packet replication registrationExplanation A Cisco QuantumFlow Processor experienced an internal software error in which the ESS proxy session keepalive packet replication registration failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %ESS_PROXY-3-KA_PKT_TMPL_BFR_ALLOC_FAILED : CPP ESS Proxy Session Keepalive packet template allocation failureExplanation A Cisco QuantumFlow Processor experienced an internal software error in which the ESS proxy session keepalive packet template allocation failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %ESS_PROXY-3-KA_TIMER_INIT_FAILED : CPP ESS Proxy Session Keepalive timer initialization failure.Explanation A Cisco QuantumFlow Processor experienced an internal software error in which the ESS proxy session keepalive timer initialization failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %ESS_PROXY-3-PROXY_IPC_INIT_FAILED : CPP ESS Proxy IPC interface initialization failureExplanation A Cisco QuantumFlow Processor experienced an internal software error in which the ESS proxy IPC interface initialization failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %ESS_PROXY-4-PROXY_BAD_MSG : CPP ESS Proxy received bad length message type [dec]Explanation A Cisco QuantumFlow Processor experienced an internal software error in which the ESS proxy received a message with an incompatible lenght parameter.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %ESS_PROXY-4-PROXY_INV_MSG : CPP ESS Proxy received invalid message type [dec]Explanation A Cisco QuantumFlow Processor experienced an internal software error in which the ESS proxy received an invalid message type.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %ESS_PROXY-4-PROXY_IPC_ALLOC_FAILED : CPP ESS Proxy [chars] message lost due to message bufferExplanation A Cisco QuantumFlow Processor experienced an internal software error in which an ESS proxy message was dropped due to a problem with message buffer allocation.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %ESS_PROXY-4-PROXY_IPC_NO_HDLR : CPP ESS Proxy received unregistered message type [dec]Explanation A Cisco QuantumFlow Processor experienced an internal software error in which an ESS proxy received an unregistered message type.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %ESS_PROXY-4-PROXY_IPC_SEND_FAILED : CPP ESS Proxy [chars] message lost due to message sent failureExplanation A Cisco QuantumFlow Processor experienced an internal software error in which an ESS proxy message was lost during sending.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information..
ESS_SWITCH Messages
Error Message %ESS_SWITCH-4-ESS_STUB : CPP ESS switching ([chars]) feature executes stub entry in [chars] directionExplanation A Cisco QuantumFlow Processor experienced an internal software error involving ESS switching stub entry.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %ESS_SWITCH-4-limit(STATS_INVALID_PTR : CPP ESS Switching invalid statistics block for session [chars].Explanation An internal software error in which involving a Cisco QuantumFlow Processor ESS switching session
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
EXLOG Messages
Error Message %EXLOG-4-BADDST : type [int] (index [int])Explanation An internal data structure was found to contain an invalid value.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %EXLOG-4-PAKMEM : allocation error ([int] bytes)Explanation An attempt to allocate a packet buffer failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %EXLOG-4-QMPKT : packet queuing error [int]Explanation An attempt to queue an internally-generated packet failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
FMFP Messages
Error Message %FMFP-3-INTERFACE_OBJECT_NOT_FOUND : Interface object lookup by [chars] not found for interface [int]Explanation The desired interface object was not found.
Recommended Action Examine the interface state in the operating system, route processor (RP) and forwarding processor (FP) forwarding manager logs.
Error Message %FMFP-3-OBJ_DWNLD_TO_CPP_FAILED : [chars] download to CPP failedExplanation An object has failed to download to the Cisco QuantumFlow Processor (CQFP)
Recommended Action Examine the list of error objects in the forwarding processor (FP) forwarding manager asynchronous object logs.
Error Message %FMFP_ACL-3-ACL_OBJECT_DOWNLOAD : [chars][chars] fail to download because [chars].Explanation The access control list (ACL) object has failed to download. This could be due to a hardware or software resource limitation or a software defect.
Recommended Action Check the logs for information on the relevant object download states. Remove the ACL attachment to the interface or delete the ACL. Reboot the forwarding processor (FP).
Error Message %FMFP_ACL-3-ACL_LIMIT_EXCEEDED : ACL [chars] exceeded limitation of [int] ACEs per ACLExplanation A software limitation has been exceeded.
Recommended Action Reduce the access control list (ACL) configuration. A reboot of the forwarding processor (FP) is recommended.
Error Message %FMFP_ACL-3-ACL_PROTOCOL_CHECK : ACL [chars] protocol does not match what was previously configuredExplanation The error occurs for one of two reasons. An access control list (ACL) reference was made to an ACL of a different protocol; or an ACL was added or edited when there were similarly named ACL references of a different protocol
Recommended Action Remove the conflicting ACL or the conflicting ACL references.
Error Message %FMFP_URPF-3-OBJECT_DOWNLOAD : Unicast RPF [chars] on inteface [chars] fail to download because [chars].Explanation The unicast reverse path forwarding (URPF) operation failed to download. This can be caused by a hardware or software resource limitation or a software defect.
Recommended Action Check the logs for information on the relevant download states. Remove the uRPF feature enabled on any interface. Reboot the forwarding processor (FP).
Error Message %FMFP_URPF-3-LIST_DOWNLOAD : Unicast RPF list [chars] for list [int] fail to download because [chars].Explanation The unicast reverse path forwarding (URPF) list failed to download. This can be caused by a hardware or software resource limitation or software defect.
Recommended Action Check the logs for information on the relevant download states. Reboot the forwarding processor (FP).
FNF Messages
Error Message %FNF-4-limit(CLEANUP_ENTRY : FailedExplanation Netflow failed to clean up a record for reuse.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FNF-4-limit(FNF_UNSUPPORTED_AGG_FMT : Format: [dec]Explanation Netflow does not support this aggregation type.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FNF-4-limit(FNF_UNSUPPORTED_EXP_FMT : Format: [dec]Explanation Netflow does not support this export format.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FNF-4-limit(FNF_UNSUPPORTED_OPTION : Option: [dec]Explanation Netflow does not support this export option.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FNF-4-limit(INVALID_CMD : Flow builder encountered an invalid command: [dec].Explanation The flow builder does not support the command
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FNF-4-limit(KEY_SIZE_INVALID : Unexpected key fields size: [dec]Explanation The netflow attempted to install a flow with an invalid key fields size.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FNF-4-limit(REFCNT_TIMEOUT : never reached 0 for entry [hex]Explanation The netflow timed out while waiting for a flow cache entries reference count.
Recommended Action No action is required, this error is self-correcting. However, if router performance is noticeably degraded, contact Cisco Technical Assistance. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message %FNF-4-limit(UNSUPPORTED_PROT : [chars]Explanation This protocol is unsupported.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FNF-5-limit(FREE_LIST_EMPTY : Monitor: [hex]Explanation The netflow attempted to install a flow resulting in no free flow.
Recommended Action No action is required; this error is self-correcting. However, if router performance is noticeably degraded, contact Cisco Technical Assistance. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message %FNF_PROXY-4-limit(AGE_INIT : Failed with return code: [dec]Explanation Netflow failed to initialize the ager.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FNF_PROXY-4-limit(AGE_SHUT : Failed with return code: [dec]Explanation Netflow failed to shutdown the ager.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FNF_PROXY-4-limit(EXPORT_INIT : Failed with return code: [dec]Explanation Netflow failed to initialize the exporter.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FNF_PROXY-4-limit(EXPORT_OPTION_REFRESH_TIMER_START : Failed for exporter: [hex] with return code: [dec]Explanation Netflow failed to start an option refresh timer.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FNF_PROXY-4-limit(EXPORT_OPTION_REFRESH_TIMER_STOP : Failed for exporter: [hex] with return code: [dec]Explanation Netflow failed to stop an option refresh timer.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FNF_PROXY-4-limit(EXPORT_SHUT : Failed with return code: [dec]Explanation Netflow failed to shutdown the exporter.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FNF_PROXY-4-limit(EXPORT_TEMPLATE_BIND : Failed for exporter: [hex] with return code: [dec]Explanation Netflow failed to bind a template.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FNF_PROXY-4-limit(EXPORT_TEMPLATE_EXT_FIELDS_UPDATE : Failed for exporter: [hex] with return code: [dec]Explanation Netflow failed to update template extended fields.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FNF_PROXY-4-limit(EXPORT_TEMPLATE_REFRESH : Failed for exporter: [hex] with return code: [dec]Explanation Netflow failed to send a template refresh.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FNF_PROXY-4-limit(EXPORT_TEMPLATE_REFRESH_TIMER_START : Failed for exporter: [hex] with return code: [dec]Explanation Netflow failed to start a template refresh timer.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FNF_PROXY-4-limit(EXPORT_TEMPLATE_REFRESH_TIMER_STOP : Failed for exporter: [hex] with return code: [dec]Explanation Netflow failed to stop a template refresh timer.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FNF_PROXY-4-limit(EXPORT_TEMPLATE_UNBIND : Failed for exporter: [hex] with return code: [dec]Explanation Netflow failed to unbind a template.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FNF_PROXY-4-limit(EXPORT_TIMER_INIT : Failed with return code: [dec]Explanation Netflow failed to initialize the export timer.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FNF_PROXY-4-limit(EXPORT_TIMER_SHUT : Failed with return code: [dec]Explanation Netflow failed to shutdown the export timer.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FNF_PROXY-4-limit(FLOW_CACHE_WALK : Failed for session: [hex] with return code: [dec]Explanation Netflow failed to process a flow cache walk request.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FNF_PROXY-4-limit(FREE_LIST_INIT : Failed with return code: [dec]Explanation Netflow failed to initialize the free list.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FNF_PROXY-4-limit(FREE_LIST_POOL_ADD : Failed with return code: [dec]Explanation Netflow failed to populate the free list.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FNF_PROXY-4-limit(OBJ_MODIFY : Failed with return code: [dec]Explanation Netflow failed to process an object modify request.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FNF_PROXY-4-limit(STATS : Failed with return code: [dec]Explanation Netflow failed to process a stats request.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FNF_PROXY--PROXY_IPC_SEND_FAILED : [dec]Explanation An attempt to send an IPC proxy request failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information..
Error Message %FNF_PROXY-4-IPC_UNHANDLED : type [dec]Explanation An unknown message was received by the netflow client proxy.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FNF_PROXY-4-PROXY_IPC_PAK_ALLOC_FAILED :Explanation An attempt to allocate an IPC packet failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
FRAG Messages
Error Message %FRAG--FRAG_DESC_MEM_INIT_FAILED :Explanation Failure occurred while initializing a fragment descriptor pool.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FRAG--FRAG_DESC_MEM_REQ_FAILED :Explanation An IPC failure occurred when attempting to request additional fragment descriptors.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FRAG--FRAG_STATE_MEM_INIT_FAILED :Explanation A failure occurred while initializinga fragment state pool.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FRAG--FRAG_STATE_MEM_REQ_FAILED :Explanation An IPC failure occurred when attempting to request additional fragment state pool.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FRAG-4-REASSEMBLY_DBG : Reassembly/VFR encountered an error: [chars], [chars] %lu, [chars] %luExplanation A virtual fragment reassembly (VFR) operation encountered a runtime error as indicated.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FRAG-4-REASSEMBLY_ERR : Reassembly/VFR encountered an error: [chars]Explanation A virtual fragment reassembly (VFR) operation encountered a runtime error as indicated.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
FRAG_DESC_PROXY Messages
Error Message %FRAG_DESC_PROXY--PROXY_IPC_FRAG_MEM_EXTEND_FAILED :Explanation An attempt to increase the fragment descriptor pool failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FRAG_DESC_PROXY--PROXY_IPC_FRAG_MEM_INIT_FAILED :Explanation Initialization of the fragment descriptor pool failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FRAG_DESC_PROXY--PROXY_IPC_INIT_FAILED : [dec]Explanation An IPC handler initialization failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information..
Error Message %FRAG_DESC_PROXY--PROXY_IPC_INVALID_MSG : [hex]Explanation An invalid IPC message subtype was encountered.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FRAG_DESC_PROXY--PROXY_IPC_VFR_MEM_EXTEND_FAILED :Explanation An attempt to increase the virtual fragment reassembly (VFR) state pool failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FRAG_DESC_PROXY--PROXY_IPC_VFR_MEM_INIT_FAILED :Explanation An attempt to initialize the virtual fragment reassembly (VFR) state pool failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
FTP Messages
Error Message %FTP_ALG-4-limit(BAD_L7_DATA :Explanation Bad L7 data was received from a firewall or network address translation (NAT) process.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FTP_ALG-4-limit(CHUNK_CREATE_FAIL :Explanation A chunk create process failed. The FTP ALG cannot finish initialization.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FTP_ALG-4-limit(L7_DATA_CREATE_ERROR :Explanation FTP experienced an L7 data creation error.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FTP_ALG-4-limit(WRITEBACK_ERROR :Explanation FTP experienced a writeback error.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
FW Messages
Error Message %FW-4-limit(FTP_NON_MATCHING_IP_ADDR : [chars]Non-matching address %Ci used in [chars] -- FTP client %Ci FTP server %CiExplanation An FTP client attempted to use an invalid PORT command or FTP server.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FW-4-limit(FTP_PRIV_PORT : [chars]Privileged port [int] used in [chars] -- FTP client %Ci FTP server %CiExplanation An FTP client attempted to use an invalid PORT command or FTP server.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FW-4-limit(FTP_SESSION_NOT_AUTHENTICATED : [chars]Command issued before the session is authenticatedExplanation An FTP client attempted to use an invalid PORT command or FTP server.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FW-4-limit(NOTFOUND : [chars]Session context for (%Ci:[int]) => (%Ci:[int]) not found.Explanation The ZBF code was searching its database for information that was not found.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FW-4-limit(RESPONDER_WND_SCALE_INI_NO_SCALE : Dropping packet - Invalid Window Scale option for session %Ci:[int]Explanation The firewall detected an invalid packet from responder to initiator.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FW-4-limit(SMTP_INVALID_COMMAND : [chars]Invalid SMTP command ([chars])(total [dec] chars) from initiator (%Ci:[int])Explanation The ZBF code detected an invalid SMTP command from an initiator.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FW-4-limit(SMTP_UNSUPPORTED_PARAMETER : [chars]Unsupported SMTP parameter ([chars]) from initiator (%Ci:[int])Explanation The ZBF code detected an invalid or unsupported parameter.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FW-5-limit(ALERT_OFF : (target:class)-([chars]:[chars]):[chars], count ([int]/[int]) current 1-min rate: [int]Explanation The number of half-open connections or new connections is excessive.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FW-5-limit(ALERT_ON : (target:class)-([chars]:[chars]):[chars], count ([int]/[int]) current 1-min rate: [int]Explanation The maximum number of incomplete high threshold of half-open connections has been reached.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FW-5-limit(HOST_TCP_ALERT_ON : (target:class)-([chars]:[chars]):Max tcp half-open connections ([int]) exceeded for host %Ci.Explanation The maximum number of incomplete host limit of half-open TCP connections has been reached.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FW-5-limit(RESPONDER_ZERO_WND_SCALE_FACTOR_INI_NO_SCALE : Accepting packet -Window Scale option for session %Ci:[int] to %Ci:[int]Explanation The firewall detected an invalid packet from responder to initiator.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FW-5-limit(SESSIONS_MAXIMUM : Number of sessions for the firewall policy onExplanation This message indicates that the number of established ZBF sessions has reached a maximum.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FW-5-limit(SESSION_THRESHOLD_EXCEEDED : [chars]Number of sessions for the firewall rule '[chars]' applied onExplanation This message indicates that a session threshold was exceeded.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FW-5-limit(SKINNY_INSPECTION_DISABLED : Skinny Inspection Disabled; Error = [chars]Explanation The skinny inspection is disabled due to internal errors.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FW-5-limit(TCP_MAJORDOMO_EXEC_BUG : [chars]Majordomo Execute Attack - from %Ci to %CiExplanation A bug in the Majordomo program could allow remote users to initiate an attack on the system.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FW-5-limit(TCP_SENDMAIL_BAD_FROM_SIG : [chars]Sendmail Invalid Sender - from %Ci to %CiExplanation Internal error triggered by any mail message with a ''pipe'' (|) symbol in the body of the sender message.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FW-5-limit(TCP_SENDMAIL_BAD_TO_SIG : [chars]Sendmail Invalid Recipient - from %Ci to %CiExplanation Internal error triggered by any mail message with a ' 'pipe'' (|) symbol in the body of the recipient message.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FW-5-limit(TCP_SENDMAIL_DECODE : [chars]Sendmail Decode Alias - from %Ci to %CiExplanation Internal error triggered on any mail message with '': decode@'' in the header.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FW-5-limit(TCP_SENDMAIL_INVALID_COMMAND : [chars]Invalid SMTP command - %Ci to %CiExplanation Internal error triggered by an invalid SMTP command in the mail message.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FW-5-limit(TCP_SENDMAIL_OLD_SIG : [chars]Archaic Sendmail Attacks - from %Ci to %CiExplanation Internal error triggered when ''wiz'' or ''debug'' commands are sent to the SMTP port.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FW-6-limit(EMAIL_DROP_FRAGMENT : [chars]Dropping [chars] command fragment from initiator (%Ci:[int])Explanation The ZBF code detected a pipelined POP3/IMAP command fragment.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FW-6-limit(IMAP_INVALID_COMMAND : [chars]Invalid IMAP command from initiator (%Ci:[int]): [chars]Explanation The ZBF code detected an invalid IMAP command from the initiator.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FW-6-limit(IMAP_NON_SECURE_LOGIN : [chars]LOGON IMAP command from initiator (%Ci:[int]): [chars]Explanation The ZBF code detected a cleartext logon attempt in the inspected IMAP command sent by the initiator.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FW-6-limit(POP3_INVALID_COMMAND : [chars]Invalid POP3 command from initiator (%Ci:[int]): [chars]Explanation The ZBF code detected an invalid POP3 command.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FW-6-limit(POP3_NON_SECURE_LOGIN : [chars]LOGON POP3 command from initiator (%Ci:[int]): [chars]Explanation The ZBF code detected a cleartext logon attempt in the inspected POP3 command sent by the initiator.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FW-7-limit(DROP_PKT : Dropping [chars] pkt %Ci:[int] => %Ci:[int]Explanation A packet was dropped during a firewall inspection.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FW-7-limit(INIT : Firewall inspection startup completed; beginning operation.Explanation Firewall inspection is configured on at least one interface.
Recommended Action No action is required.
Error Message %FW-7-limit(LOG_SUMMARY : [int] [chars] packet[chars] [chars] fromExplanation Log summary provided for the number of packets dropped or passed.
Recommended Action No action is required.
Error Message %FW-7-limit(PASS_PKT : (target:class)-([chars]:[chars])Explanation Packet was passed by firewall inspection.
Recommended Action No action is required.
Error Message %FW-7-limit(PRE_ALLOCATED_MEDIA_CHANNEL : [chars]Pre-Allocated [chars] channel from %Ci[[int]:[int]] to %Ci[[int]:[int]]Explanation ZBF inspection has pre-allocated data-structures and created ACEs.
Recommended Action No action is required.
Error Message %FW-7-limit(SESS_AUDIT_TRAIL : (target:class)-([chars]:[chars]):Stop [chars] session: initiator (%Ci:[int]) sent [int] bytes -- responder (%Ci:[int]) sent [int] bytesExplanation Information message that documents the per-session transaction log of network.
Recommended Action No action is required.
Error Message %FW-7-limit(SESS_AUDIT_TRAIL_START : (target:class)-([chars]:[chars]):Start [chars] session: initiator (%Ci:[int]) -- responder (%Ci:[int]) [chars]Explanation Information message that documents the opening of an inspection session.
Recommended Action No action is required.
Error Message %FW-3-BLOCK_HOST : (target:class)-([chars]:[chars]):Blocking new TCP connections to host %Ci for [int] minute[chars] (half-open count [int] exceeded).Explanation Any new TCP connections are blocked as explained by the message text.
Recommended Action No action is required.
Error Message %FW-4-HTTP_JAVA_BLOCK : [chars]JAVA applet is blocked from (%Ci:[int]) to (%Ci:[int]).Explanation The firewall has blocked Java applet in the HTTP channel as explained by the message text.
Recommended Action No action is required.
Error Message %FW-4-INTERNAL_ERROR : IP Firewall internal failure -- [chars]Explanation The system experienced a general internal firewall failure.
Recommended Action No action is required.
Error Message %FW-4-TIMER_WHEEL_INIT_FAILED : Timer Wheel initialization failedExplanation The Timer Wheel initialization failed.
Recommended Action No action is required.
Error Message %FW-5-UNBLOCK_HOST : (target:class)-([chars]:[chars]):New TCP connections to host %Ci no longer blockedExplanation New TCP connections are no longer blocked.
Recommended Action No action is required.
Error Message %FW-7-SESS_AUDIT_TRAIL_CHANGE : [chars]Change to [chars] session: initiator (%Ci:[int]) sent [int] bytes -- responder (%Ci:[int]) sent [int] bytesExplanation This message documents the change in protocol for an inspection or audit.
Recommended Action No action is required.
FWALL Messages
Error Message %FWALL-4-limit(FW_ALG_INVALID_TYPE : [chars] [dec]:[dec]Explanation An invalid application layer gateway (ALG) type was passed to the firewall.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FWALL-4-limit(FW_NO_STATS : [dec]:[dec]Explanation The client has not provided stats for the given protocol application.
Recommended Action Provide the missing information.
Error Message %FWALL-4-limit(HA_INVALID_MSG_RCVD : invalid [chars] [dec] opcode [hex]Explanation The system received an invalid firewall high availability (HA) message.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FWALL-4-limit(HA_INVALID_STATE : [dec]Explanation The system experienced an invalid firewall high availability (HA) state.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FWALL-8-limit(FW_NO_ALERT_CAUSE : [dec]Explanation The system experienced an unsupported alert cause.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FWALL-8-limit(FW_NO_DROP_CAUSE : [dec]Explanation The system experienced an unsupported drop cause.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FWALL_PROXY--PROXY_FWALL_INIT_FAILED : [dec]Explanation An attempt to initialize the firewall failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FWALL_PROXY--PROXY_HA_MEM_EXTEND_FAILED :Explanation Attempt to increase the high availability (HA) retry pool failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FWALL_PROXY--PROXY_HA_MEM_INIT_FAILED :Explanation Initialization of the high availability (HA) retry pool failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FWALL_PROXY--PROXY_HOSTDB_MEM_EXTEND_FAILED :Explanation Attempt to increase the host database pool failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FWALL_PROXY--PROXY_HOSTDB_MEM_INIT_FAILED :Explanation Attempt to initialize the host database pool failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FWALL_PROXY--PROXY_HSL_ADD_DEST_FAILED :Explanation An attempt by the high speed log (HSL) to add a destination failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FWALL_PROXY--PROXY_HSL_ALREADY_INIT :Explanation The high speed log (HSL) is already initialized.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FWALL_PROXY--PROXY_HSL_BIND_FAILED :Explanation A high speed log (HSL) bind failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FWALL_PROXY--PROXY_HSL_BIND_TEMPLATE_FAILED : [dec]Explanation The high speed log (HSL) bind template failed at a given index.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FWALL_PROXY--PROXY_HSL_CREATE_FAILED :Explanation A high speed log (HSL) creation failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FWALL_PROXY--PROXY_HSL_ENABLE_FAILED :Explanation A high speed log (HSL) enable action failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FWALL_PROXY--PROXY_HSL_MODIFY_DEST_FAILED :Explanation A high speed log (HSL) attempt to modify a destination failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FWALL_PROXY--PROXY_HSL_MODIFY_FAILED :Explanation A high speed log (HSL) modification action failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FWALL_PROXY--PROXY_HSL_NOT_INIT : [int]Explanation The high speed log (HSL) logger is not initialized.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FWALL_PROXY--PROXY_IPC_ALLOC_FAILED : [int]Explanation An inter process communication (IPC) allocation failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FWALL_PROXY--PROXY_IPC_FAILED : [chars] [dec]Explanation An inter process communication (IPC) message allocation for firewall failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FWALL_PROXY--PROXY_IPC_INIT_FAILED : [dec]Explanation An inter process communication (IPC) handler initialization failed.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FWALL_PROXY--PROXY_IPC_INVALID_MSG : [hex]Explanation An invalid inter process communication (IPC) message subtype was received.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FWALL_PROXY--PROXY_IPC_INVALID_MSG_LEN : [dec]:[dec] len [dec] flags [hex] source [dec]Explanation There was an invalid inter process communication (IPC) message length.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FWALL_PROXY--PROXY_IPC_SEND_CLEAR_FAILED : [dec]Explanation An inter process communication (IPC) send reply failed to a request to clear a firewall session.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FWALL_PROXY--PROXY_IPC_SEND_DEBUG_FAILED : [dec]Explanation An inter process communication (IPC) send failed to reply to a request for firewall session debug.
Recommended Action Examine the logs for hardware errors. If the problem persists, 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 gathered information.
Error Message %FWALL_PROXY--PROXY_IPC_SEND_FAILED : [int]:[chars]
