Ipc internal error

All Other Messages

Error Message %BTRACE_ROTATE-3-ARCHIVE_FAIL : Error archiving trace file — [chars]

Explanation While trying to archive a trace file on the active RP, an error occurred that prevented the file transfer. The trace file is not saved.

Recommended Action This message is usually seen as a result of an underlying problem with the harddisk: file system; check the console log for messages related to harddisk: file system messages.

Error Message %CEMA-3-SPA_CMD_FAIL: [chars]: Command [chars]([dec]) failed ([chars]); partial command dump [hex] [hex] [hex] [hex]

Explanation A failure occurred when sending a command to the SPA indicated in the error message.

Recommended Action Research and attempt to resolve the issue using the SPA hardware troubleshooting documentation as well as the tools and utilities provided at http://www.cisco.com/public/support/tac/tools.shtml. If you still require assistance or would like to report a suspected hardware failure, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/ or contact your Cisco technical support representative and provide the representative with the information you have gathered. Be sure to attach to your case the output of the show logging, show monitor event-log spa all, show tech-support and show hw-module subslot target spa tech-support commands, your troubleshooting logs, and the specific error message.

Error Message %CGM-3-CGM_FIPS_BYPASS_TEST : NIST bypass test failed for CGM object [chars].

Explanation Class-Group Manager Security Client database detected a discrepancy in a security sensitive object. 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 object or a parent object in question. If the problem persists reboot the forwarding processor (ESP).

Error Message %CPPCDM-3-ERROR_NOTIFY : QFP [dec] thread [dec] encountered an error -Traceback= [chars] [chars]

Explanation A QFP fault has occurred.

Recommended Action No action is required.

Error Message %CPP_MPASS-3-INVALID_VECTOR : vector [dec]

Explanation An invalid multipass vector was received.

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

Error Message %CPP_NAT64_PROXY-3-INVALID_IPC_INPUT : number of instances is invali

Explanation The NAT64 proxy has received an IPC with an unexpected format/data

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter. Also perform a search of the Bug Search Tool. If you still require assistance, 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.

Error Message %CPP_NAT64_PROXY-3-INVALID_IPC_SUBTYPE : subtype is [dec]

Explanation The NAT64 proxy has received an IPC with an unexpected subtype

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter. Also perform a search of the Bug Search Tool. If you still require assistance, 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.

Error Message %CPP_NAT64_PROXY-3-NAT64_INIT_FAIL : nat64 init failure rc= [dec]

Explanation The NAT proxy has experienced a failure when trying to initialize the NAT64 proxy

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter. Also perform a search of the Bug Search Tool. If you still require assistance, 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.

Error Message %CPP_NAT64_PROXY-3-NAT64_IPC_FAIL : rc= [dec]

Explanation The NAT64 proxy has experienced a failure when trying to send an IPC

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter. Also perform a search of the Bug Search Tool. If you still require assistance, 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.

Error Message %CPP_PKT_SUBBLOCK-3-PKT_SB_MANAGE_FAIL : rc=[hex]

Explanation A packet subblock manage has failed.

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

Error Message %EPOCH-6-EPOCH_REJECTED : Peer [chars] has rejected epoch: [chars]

Explanation This error occurs if epoch from shell-manager has been rejected by the peer.

Recommended Action Check the epoch and peer state.

Error Message %FEATURE_INVOKE-3-CALL_STACK_EXCEEDED : index %

Explanation A request exceeded the feature invocation call stack.

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

Error Message %HMR-3-HASH_SIZE_ZERO : count [dec] poly [dec]

Explanation An invalid hash table size of 0 was detected.

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

Error Message %IFMAP-3-CAUSE_CFG : hash table not initialized

Explanation PAL interface handle to uidb hash table not initialized.

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

Error Message %LSMPI-4-INJECT_FEATURE_ESCAPE : Egress [chars] packet delivered via legacy inject path

Explanation A packet with a CPP supported L3 encapsulation (such as IP) was produced by IOS but delivered to CPP via the L2/legacy inject path instead of the proper L3 inject path. For this packet, outbound features will not be applied and packet accounting will likely be incorrect.

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

Error Message %MCP_UPGRADE_ROMMON-0-ROMMON_UPGRADE_FAIL : ROMMON upgrade failed: partition [chars]

Explanation An attempt to upgrade the ROMmon failed.

Recommended Action Check the system messages to see if any messages appeared that might indicate the source of the ROMmon problem. If you do not find any additional information indicating a correctable problem, collect all output on the screen, in particular the console port output after the upgrade rom-monitor command was entered and the output of show rom-monitor, and provide the collected information to a Cisco technical support representative.

Error Message %MPLS_FORWARDING-2-CAUSE_THROTTLE_ERR : Allocation of mpls throttle [chars] memory failed

Explanation Allocation of memory resource use by the MPLS throttle has failed.

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

Error Message MPLS_LABEL-5-CHANGED: %s min/max label: %u/%u

Explanation The MPLS label range has changed. This message is to notify the NMS of changes.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %MPLS_TP-3-UPDOWN: Tunnel-tp%u, changed state to %s

Explanation The MPLS-TP tunnel-tp interface changed state.

Recommended Action If the state change was unexpected, confirm the configuration settings and those of other LSRs along the tunnel LSPs.

Error Message %MPLS_TP-5-CONFIG_CHANGED: Tunnel-tp%u is %s

Explanation The configuration of the tunnel-tp interface has changed. This message is to notify the NMS of changes.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %MPLS_TP-5-REDUNDANCY: Tunnel-tp%u, switched to %s LSP as active

Explanation The MPLS-TP tunnel-tp interface has changed the LSP over which it data traffic is carried, possibly due to a fault or administrative action, or to restore traffic to the working-LSP after LSP recovery.

Recommended Action If this change is unexpected, examine LSP messages to determine if a fault or other failure has occurred, or is this is due to a lockout condition or configuration change.

Error Message %MPLS_TP_BWPOOL-3-BW_POOL_CHANGED: Bandiwdth pool available to MPLS-TP has changed

Explanation Bandwidth pool available to MPLS-TP has changed. This is either due tothe removal of a link or changing to the pool through CLI configuration

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %MPLS_TP_LINK-5-CONFIG_CHANGED: Link %u, interface %s, next-hop %s %s

Explanation The configuration of the MPLS-TP link has changed. This message is to notify the NMS of changes.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %MPLS_TP_LSP-3-UPDOWN: %s LSP %s is %s%s%s

Explanation The indicated MPLS-TP LSP has gone up or down. If the LSP went down, the failure condition, and the fault source information is provided.

Recommended Action Examine the failure condition and source information to determine why the LSP went down.

Error Message %MPLS_TP_LSP-5-CONFIG_CHANGED: LSP %s is %s

Explanation The configuration of the MPLS-TP midpoint LSP has changed. This message is to notify the NMS of changes.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %MPLS_TP_LSP-5-LOCKOUT: %s LSP %s %s lockout state

Explanation The indicated LSP has entered or exited lockout state due to administrative action at one endpoint

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %MPLS_TP_LSP_FSM-3-LSP_FSM_ERROR: LSP FSM Error occurred. Received event:%s in state:%s

Explanation An erroneous event was received by the TP LSP.This is an error internal to MPLS-TP

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %MPLS_TP_TIMER-3-UNKNOWN_TIMER_TYPE_EXPIRY: Unknown timer type expired:%d

Explanation An unknown MPLS-TP timer type expired. This is an issue internal to MPLS-TP.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %MSG_FIFO-2-MSG_FIFO_CREATE : [chars]: Bad parameter to message fifo creaate [chars] = 0x%08x

Explanation Failed to create message FIFO, possibly due to invalid memory size.

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

Error Message %PBR-3-PBR_CLASSIFY_FAIL : Dataplane classification error for interface [chars]

Explanation The system experienced an internal software error. The dataplane was unable to complete processing of a route map due to a classification failure. This is likely due to a data initialization error.

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

Error Message %PKT_MANIP-3-ALLOC_FAIL : retcode [int]

Explanation A critical failure occurred when trying to obtain packet memory.

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

Error Message %PLIM_QOS-3-ASR1000_RP_PLIM_QOS_FAIL : A software error while configuring the [chars] on slot [dec]

Explanation This error happens when IOS fails to send messages to configure the per slot QoS parameters in forwarding plane.

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

Error Message %PUNT_INJECT-2-CAUSE_CFG_ERR : [chars] [chars] initialization failed

Explanation Initialization of punt and inject cause failed due to invalid configuration parameters.

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

Error Message %RTREE-3-ALLOC_FAIL : aux [hex]

Explanation A Radix Tree request has caused an out of memory condition.

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

Error Message %SERDES-3-SERDES_CRITICAL_ERROR Reloading FRU [chars] due to critial error [chars].

Explanation A critical error has occurred. The condition is serious and the card must be reloaded. This could be due to bad or unknown hardware (chassis or modules). Chassis manager could also initialize the Serdes library with incorrect input parameters.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show platform, show version, show diag chassis eeprom detail, and show diagnostic slot commands to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show platform, show version, show diag chassis eeprom detail, and show diagnostic slot commands and your pertinent troubleshooting logs.

Error Message %TFTP_ALG-3-ALG_STATE_CREATE_FAIL :

Explanation A get or create ALG state failed. The trivial file transfer protocol (TFTP) ALG is unable to process packets.

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

ACE Messages

Error Message %ACE-2-CRYPTOENGERR : Crypto engine error: [chars] ([dec])

Explanation A crypto engine operation did not complete. This error condition can indicate that the crypto engine cannot bind or unbind an interface to a crypto engine. It can also indicate that the crypto engine cannot query an interface ID.

Recommended Action Remove the cryptomap set from the interface by issuing no crypto map command. Then reattach the cryptomap set to the interface using crypto map command. Although removing and reattaching the crypto map might fix the cryptographic engine operation failure, report the failure to your technical support representative along with the sequence of commands that lead to the failure.

Error Message %ACE-2-INTTABOPERR : Internal [chars] table error: [chars]

Explanation Internal table operation fails. This means the state of the module is mostly like inconsistent.

Recommended Action Contact your technical support representative

Error Message %ACE-3-BOOTMSGERR : [chars]: boot error: [chars]

Explanation The ACE completed booting, but with an error status code. ACE will not operate and it will not register with the crypto subsystem.

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

Error Message %ACE-3-CEAL_REGISTRATION : ACE [chars] failed to register.

Explanation The ACE failed to register with CEAL.

Recommended Action Reset the hardware module.

Error Message %ACE-3-CRASHDUMPERR : [chars]: crashdump retrieval error: [chars] [chars]

Explanation An error occurred during crashdump file retrieval from ACE.

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

Error Message %ACE-3-CRASHDUMPSTART : [chars]: crashdump retrieval initiated to file [chars]

Explanation The ACE crashed and was rebooted. Upon reboot, a crashdump file was detected and uploaded to the sup-bootflash filesystem.

Recommended Action Report the crash and transfer the crashdump file to your technical support representative.

Error Message %ACE-3-HAPITRUNC : [chars]: Received truncated HAPI message (tlen=[dec], actual=[dec])

Explanation The received ACE control packet was smaller than the size field indicated.

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

Error Message %ACE-3-INITFAIL : %s: initialization failed (%s)

Explanation ACE initialization sequence failed.

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

Error Message %ACE-3-INVTID : [chars]: [chars] of invalid [chars] trans id [dec]

Explanation An invalid transaction ID of for the indicated transaction type was encountered.

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

Error Message %ACE-3-NOENGINESLOT : Interface [chars] has no crypto engine slot

Explanation An IKE SA was requested for a given interface, but no crypto engine slot was assigned to that interface.

Recommended Action Configure the interface with the crypto engine slot command.

Error Message %ACE-3-NOMORETID : [chars]: out of [chars] transactions

Explanation Transaction pool for the indicated transaction type was exhausted.

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

Error Message %ACE-3-OUTOFID_RL : Too may [chars] IDs in the system. Cannot allocate a new one

Explanation All the IDs of the specified type are in use.

Recommended Action Reduce the traffic load, number of IPSec tunnels and/or frequency of re-key. If this message was seen under light loading conditions, then copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ACE-3-OUTOFRES : Too many [chars] in the system. Cannot allocate a new one

Explanation All VPN-accelerator resources of a particular are in used and thus this allocation request fails.

Recommended Action Remove the cryptomap set from the interface. Reduce the number of that resource in the system. For ACL, reduce the number of ACL permit ACE in the system. For cryptomap, reduce the number of cryptomaps in the system. For SPD and SPD map, reduce the number of interface with cryptomap set attached.

Error Message %ACE-3-TRANSERR : [chars]: [chars] trans [hex]; opcode [hex]; param [hex]; error [hex]; retry cnt [dec]

Explanation An error occurred in the indicated control transaction.

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

Error Message %ACE-3-TRANSERR_RL : [chars]: [chars] trans 0x%

Explanation An error occurred in the indicated control transaction.

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

Error Message %ACE-3-TRANSNAK : [chars]: [chars] NAK trans [hex]; opcode [hex]; param [hex]

Explanation An negative acknowledge occurred in the indicated control transaction.

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

Error Message %ACE-3-TRANSTO : [chars]: [chars] trans 0x%

Explanation An error occurred in the indicated control transaction.

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

Error Message %ACE-4-BV_IDMGR_DESTROY: ACE failed to destroy [chars] ID manager. Leaking memory.

Explanation The ACE failed to destroy memory space for ID management.

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

Error Message %ACE-6-BOOTMSGINFO : [chars]: boot info: [chars]

Explanation The ACE completed booting, but with a non-zero informational status code. This does not indicate an error and ACE will run normally.

Recommended Action No action is necessary.

Error Message %ACE-6-CRASHDUMPEND : [chars]: crashdump retrieval complete

Explanation The ACE crashed and was rebooted. Upon reboot, a crashdump file was detected and uploaded to the sup-bootflash filesystem.

Recommended Action Report the crash and transfer the crashdump file to your technical support representative.

Error Message %ACE-6-INFO : [chars]: [chars]

Explanation This is informational message from ACE

Recommended Action This is informational message from ACE. This occurs in normal operation.

Error Message %ACE-6-SWITCHOVER : VPN-SM switchover: [dec]/[dec] has been [chars] [dec]/[dec]

Explanation A blade to blade switchover has occurred. System performance is not affected.

Recommended Action System performance is not affected. No customer action is necessary.

Error Message %ACE-6-UNEXP_INBOUND_IPSEC : [chars]: received unexpected IPsec packet: src IP: %

Explanation An IPsec packet was unexpectedly forwarded to the RP.

Recommended Action If this message was seen in the context of the router booting while enabling the hardware crypto accelerator, then this message is normal and can be safely ignored. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ACE-6-UNEXP_OUTBOUND_IPSEC : [chars]: received unexpected IPsec packet: src IP: %

Explanation An IPsec packet was unexpectedly forwarded to the RP.

Recommended Action If this message was seen in the context of the router booting, while enabling the hardware crypto accelerator, or with an invalid peer IP address then this message is normal and can be safely ignored. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

ACL Messages

Error Message %ACL-3-UNEXPECTED_PKT_TYPE : type [dec], int [dec] [chars]put

Explanation ACL logging has encountered unexpected packet type.

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

Error Message %ACL-3-UNEXPECTED_STATE : type [dec], int [chars] [chars]put, w0: [hex], w1: [hex]

Explanation An error has occurred in the setup of ACL hardware.

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

Error Message %ACL-4-UNEXPECTED_PKT_TYPE : type [dec], int [dec] [chars]put

Explanation Access control list (ACL) logging has encountered an unexpected packet type.

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

Error Message %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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

ALG_COM Messages

Error Message %ALG_COM-3-ALG_REGISTER_FAILED : [dec]

Explanation ALG registration failed.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter. Also perform a search of the Bug Search Tool. If you still require assistance, 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.

Error Message %ALG_COM-3-CHUNK_CREATE_FAIL : [chars]

Explanation A request to create a chunk failed.

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

Error Message %ALG_COM-3-CHUNK_EXTEND_FAIL : [chars]

Explanation A request to create a chunk failed.

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

Error Message %ALG_COM-3-IPC_INIT_FAILED : [dec]

Explanation IPC handler initialization failed.

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

ALG_PROXY Messages

Error Message %ALG_PROXY-3-PROXY_MEM_EXTEND_FAILED : ALG IPC subtype: [dec]

Explanation Extending memory failed.

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

Error Message %ALG_PROXY-3-PROXY_MEM_REQ_FAILED : ALG IPC subtype: [dec]

Explanation Requesting more memory failed.

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

Error Message %ALG_PROXY-4-PROXY_IPC_INVALID_MSG : [dec]

Explanation Invalid IPC message subtype.

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

Error Message %ALG_PROXY-4-PROXY_IPC_INVALID_MSG_LEN : [dec]:[dec] len [dec] flags [hex] source [dec]

Explanation Invalid IPC message length.

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

ARL_PROXY Messages

Error Message %ARL_PROXY-3-GPM_ALLOC_FAILED : GPM allocation for reply failed pak_size [hex] reply_size [hex]

Explanation GPM could not be allocated for reply.

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

Error Message %ARL_PROXY-3-IPC_UNHANDLED : type: [dec]

Explanation An unknown message was received by the ARL client proxy.

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

ASR1000_APPLIANCE Messages

Error Message %ASR1000_APPLIANCE-3-ACTIVATE_FAIL: Failed to send appliance ’[chars]’ activate message

Explanation During the creation and transmission of the appliance activate TDL message a failure occurred. The message was not successfully sent and therefore the appliance was not activated.

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

Error Message %ASR1000_APPLIANCE-3-DEACTIVATE_FAIL: Failed to send appliance ’[chars]’ de-activate message

Explanation During the creation and transmission of the appliance de-activate TDL message a failure occurred. The message was not successfully sent and therefore the appliance was not de-activated.

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

Error Message %ASR1000_APPLIANCE-3-INIT_FAIL: Failed to initalize required appliance objects

Explanation During the initialization of the resources required for the appliance feature, a memory allocation failure occurred. This has prevented the appliance feature from being enabled.

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

Error Message %ASR1000_APPLIANCE-3-INVALID_APPLIANCE_TIMEOUT: A response timeout occurred for an invalid appliance

Explanation An unexpected condition occurred where the appliance context pointer in the expired timer was set to NULL.

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

Error Message %ASR1000_APPLIANCE-3-INVALID_RF_MSG: Received an invalid RF message type from peer

Explanation An unexpected condition occurred where an invalid timeout type was detected.

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

Error Message %ASR1000_APPLIANCE-3-PKG_PATH_ACTIVATE_FAIL: Failed to find appliance definition file ’[chars]’. Appliance ’[chars]’ will not be activated

Explanation Specified appliance definition file was not found following a switchover. Unable to activate appliance without specified appliance definition file present

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

Error Message %ASR1000_APPLIANCE-3-PKG_PATH_FAIL: Failed to find appliance definition file ’%s’ required by appliance ’%s’

Explanation Specified appliance definition file was not found following a switchover.

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

Error Message %ASR1000_APPLIANCE-3-RESPONSE_TIMEOUT: Appliance %s timed out waiting for a response from Virt-Manager

Explanation Failed to receive a response message from Virt-Manager for last activation operation performed on the named appliance. The appliance’s activation state was marked as deactivated.

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

Error Message %ASR1000_APPLIANCE-3-ROMMON_UNSUPPORTED: ROMMON configuration does not support virtualization

Explanation Virtualization is not supported by the current ROMMON configuration. Verify both the ROMMON version and ROMMON variable ENABLE_VTX are correct to enable virtualization.

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

Error Message %ASR1000_APPLIANCE-3-SEND_RF_MSG: Failed to send RF message to peer — %s

Explanation An unexpected condition occurred where an attempt to send an RF message to peer failed.

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

Error Message %ASR1000_APPLIANCE-3-STBY_PKG_PATH_ACTIVATE_FAIL: Failed to find appliance definition file ’%s’ on Standby. Appliance ’%s’ will not be activated following a switchover

Explanation Specified appliance definition file was not found on Standby. Following a switchover, this appliance will not be activated. Copy appliance definition file to Standby at earliest convenience.

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

Error Message %ASR1000_APPLIANCE-3-STBY_PKG_PATH_FAIL: Failed to find appliance definition file ’%s’ required by appliance ’%s’ on Standby

Explanation Specified appliance definition file was not found on Standby. Configuration was accepted, however upon switchover if this file is not found this configuration will be removed. Copy appliance definition file to Standby at earliest convenience.

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

Error Message %ASR1000_APPLIANCE-3-STBY_ROMMON_UNSUPPORTED: Standby rom-monitor configuration does not support virtualization

Explanation Virtualization is not supported by the current rom-monitor configuration on the Standby. Verify both the rom-monitor version and rom-monitor variable ENABLE_VTX are correct to enable virtualization.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_APPLIANCE-3-UNKNOWN_APPLIANCE_TIMEOUT: A response timeout occurred for unknown appliance %s

Explanation A response time-out occurred for an appliance that is no longer in the appliance database.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_APPLIANCE-3-UNKNOWN_RF_MSG: Received an unknown RF message type (%d) from peer

Explanation An unexpected condition occurred where an unknown timer event was detected.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_APPLIANCE-3-UNKNOWN_TIMEOUT_TYPE: A response timeout occurred for an unknown timeout type (%d)

Explanation An unexpected condition occurred where an unknown timeout type was detected.

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

Error Message %ASR1000_APPLIANCE-3-UNKNOWN_TIMER_EVENT: A timer event occurred for an unknown timer event (%d)

Explanation An unexpected condition occurred where an unknown timer event was detected.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_APPLIANCE-5-ACTIVATION_STATE: %s %s

Explanation The activation state of the named appliance has changed as notified by Virt-Manager.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

ASR1000_APS Messages

Error Message %ASR1000_APS-3-CCCONFIGFAILED : Pair config for interface [chars] Group [dec] failed

Explanation Pair configuration for interface has failed

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter. Also perform a search of the Bug Search Tool. If you still require assistance, 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.

Error Message %ASR1000_APS-3-CONFIG_FAIL : config change for interface [chars] Group [dec] failed

Explanation Configuration for an interface to forwarding plane has failed

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter. Also perform a search of the Bug Search Tool. If you still require assistance, 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.

Error Message %ASR1000_APS-3-DOWNLOADFAIL : Unable to download %s message to %s

Explanation An unexpected condition has occurred which resulted in a configuration not being sent to the reported process.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter. Also perform a search of the Bug Search Tool. If you still require assistance, 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.

Error Message %ASR1000_APS-3-FLOWCONFIGTOCCFAILED : Flow id to cc for interface [chars] Group [dec] failed

Explanation Flow id to cc for an interface has failed

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter. Also perform a search of the Bug Search Tool. If you still require assistance, 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.

Error Message %ASR1000_APS-3-FLOWIDALLOCFAILED : Allocation of APS flow ID with manager failed for interface %s group [dec]

Explanation An unexpected condition has occurred that allocation of APS flow ID. failed

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter. Issue the command to gather data that may help identify the nature of the error. Also perform a search of the Bug Search Tool. If you still require assistance, 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.(show interface

Error Message %ASR1000_APS-3-FLOWIDDELETIONFAILED : Deletion of APS flow ID with manager failed for interface %s group [dec]

Explanation An unexpected condition has occurred that deletion of APS flow ID.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter. Issue the command to gather data that may help identify the nature of the error. Also perform a search of the Bug Search Tool. If you still require assistance, 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.(show interface)

Error Message %ASR1000_APS-3-GROUP_CONFIG_FAIL : Group change for interface [chars] Group [dec] failed

Explanation Group change for interface has failed

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter. Also perform a search of the Bug Search Tool. If you still require assistance, 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.

Error Message %ASR1000_APS-3-PAIR_CONFIG_FAIL : Pair config for interface [chars] Group [dec] failed

Explanation Pair configuration for interface has failed

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter. Also perform a search of the Bug Search Tool. If you still require assistance, 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.

ASR1000_DSP Message

Error Message %ASR1000_DSP-3-ENQUEFAIL: Enqueue of TDL message failed (%s).

Explanation An unexpected condition has occurred which resulted in configuration, resource, or call details not being forwarded.

Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter. Also perform a search of the Bug Search Tool. If you still require assistance, 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.

ASR1000_ETHERCHAN Messages

Error Message %ASR1000_ETHERCHAN-3-LINK_MTU_FAIL : Failure in changing MTU of interface [chars] to port-channel [chars] MTU

Explanation The MTU for the interface mentioned in the message cannot be changed to match the MTU configured on the port channel interface.

Recommended Action Remove the link mentioned in the message from the port-channel group.

Error Message %ASR1000_ETHERCHAN-6-LINK_MTU : Interface [chars] MTU set to port-channel [chars] MTU [dec]

Explanation The MTU for the interface mentioned in the message is changed to match the MTU configured on the port channel interface.

Recommended Action No action is required.

ASR1000_LICENSE Messages

Error Message %ASR1000_LICENSE_BOOT_CLI-3-CHASFS_OBJECT_FAILURE: Unable to create the chassis file system object %s, for storage of the license boot level.

Explanation This system will continue to operate correctly, and if the user performs a write memory, the correct license boot levels will be persisted. The only impact from this problem is the show license image-levels command may not have up to date values.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter. Also perform a search of the Bug Search Tool. If you still require assistance, 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.

Error Message %ASR1000_LICENSE_BOOT_CLI-3-CHASFS_PROPERTY_CREATE_FAILURE: Unable to create the chassis file system Property %s, for storage of a property for the license boot level.

Explanation This system will continue to operate correctly, and if the user performs a write memory, the correct license boot levels will be persisted. The only impact from this problem is the show license image-levels command may not have up to date values

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter. Also perform a search of the Bug Search Tool. If you still require assistance, 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.

Error Message %ASR1000_LICENSE_BOOT_CLI-3-CHASFS_PROPERTY_SET_FAILURE: Unable to set the value %s, for property %s, in the chassis file system for storage of the license boot level.

Explanation This system will continue to operate correctly, and if the user performs a write memory, the correct license boot levels will be persisted.The only impact from this problem is the show license image-levels command may not have up to date values.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter. Also perform a search of the Bug Search Tool. If you still require assistance, 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.

ASR1000_MEMPOOL Messages

Error Message %ASR1000_MEMPOOL_MIB-3-BUFFPOOL_REG_ERROR: Bufferpool register data exceeds allocated memory; Retrieved only [dec] entries.

Explanation Memory allocated is not enough.

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

ASR1000_MGMTVRF Messages

Error Message %ASR1000_MGMTVRF-3-AFI_ATTACH_FAIL: Management VRF AFI %s attach failed

Explanation Cannot create AFI subblock for management of VRF.

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

Error Message %ASR1000_MGMTVRF-3-INTF_ATTACH_FAIL: Management VRF attach to mgmt port failed

Explanation Cannot associate management port to management VRF.

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

Error Message %ASR1000_MGMTVRF-3-PROCESS_CREATE_FAIL: Management VRF process creation failed, %s

Explanation Cannot create IOS process for management port initialization.

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

Error Message %ASR1000_MGMTVRF-3-SET_TABLEID_FAIL: Installing %s Management interface tableid 0x%x failed

Explanation Failed to set management port table id into Linux kernel.

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

Error Message %ASR1000_MGMTVRF-3-VRF_CREATE_FAIL: Management VRF creation failed %s

Explanation Cannot create management VRF during system initialization.

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

Error Message %ASR1000_MGMTVRF-6-CREATE_SUCCESS_INFO: Management vrf [chars] created with ID [dec], ipv4 table-id [hex], ipv6 table-id [hex]

Explanation Management VRF and IPV4, IPV6 tables created for management port.

Recommended Action No action is required.

ASR1000_OIR Messages

Error Message %ASR1000_OIR-3-MODULE : Missing [chars] for [chars]

Explanation A hardware or software error occurred.

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

Error Message %ASR1000_OIR-3-OIRTWICE : Subslot [int]/[int] OIR insertion/removal not paired up: [chars]

Explanation An internal OIR-related error occurred for the specified SPA.

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

Error Message %ASR1000_OIR-3-POWER_CYCLE_IMMINENT : The SPA in subslot [int]/[int] will be power cycled in [dec] seconds.

Explanation The SPA in the specified subslot will be power cycled in the amount of time specified in the error message.

Recommended Action No action is required.

Error Message %ASR1000_OIR-3-PROCMSG : Process msg send failed for process[dec]

Explanation Process message send failed.

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

Error Message %ASR1000_OIR-3-QUIESCE_FAIL : Quiesce failed for subslot %u/%u (error = %d)

Explanation The RP failed to contact the SPA during failover. The SPA will be reset.

Recommended Action No action is required.

Error Message %ASR1000_OIR-3-SPA_INTF_ID_ALLOC_FAILED: Failed to allocate interface identifiers forSPA(%s) in slot/bay: %u/%u

Explanation Failed to get CC buffer and flow control identifiers for the SPA in the specified subslot. Traffic cannot flow through the SPA under this failure condition.This can happen if the system runs out of available identifiers.

Recommended Action Try to reduce the number of interfaces configured in the system either by physically removing the SPAs or by changing the system configuration.

Error Message %ASR1000_OIR-3-UNQUIESCE_FAIL : Unquiesce failed for subslot [int]/[int] (error = [dec])

Explanation The RP failed to unquiesce the SPA in the specified subslot. The SPA will be reset.

Recommended Action No action is required.

Error Message %ASR1000_OIR-6-CARDRECONCILE : SPA type changed on subslot [int]/[int] from [int] to [int]

Explanation The SPA in the specified subslot has been initialized, and it has been detected that it is of a different type to the SPA that was previously in this subslot.

Recommended Action No action is required.

Error Message %ASR1000_OIR-6-INSCARD : Card ([chars]) inserted in slot [chars]

Explanation The OIR facility detected the insertion of a card in the slot number specified in the message.

Recommended Action No action is required.

Error Message %ASR1000_OIR-6-INSSPA : SPA inserted in subslot [int]/[int]

Explanation The OIR facility detected the insertion of a SPA in the subslot number specified in the message.

Recommended Action No action is required.

Error Message %ASR1000_OIR-6-OFFLINECARD : Card ([chars]) offline in slot [chars]

Explanation The OIR facility detected the state change to offline for the card in the slot number specified in the message.

Recommended Action No action is required.

Error Message %ASR1000_OIR-6-ONLINECARD : Card ([chars]) online in slot [chars]

Explanation The OIR facility detected the state change to online for the card in the slot number specified in the message.

Recommended Action No action is required.

Error Message %ASR1000_OIR-6-REMCARD : Card ([chars]) removed from slot [chars]

Explanation The OIR facility detected the removal of a card from the slot number specified in the message.

Recommended Action No action is required.

Error Message %ASR1000_OIR-6-REMSPA : SPA removed from subslot [int]/[int], interfaces disabled

Explanation The OIR facility detected the removal of a SPA from the subslot number specified in the message. The interfaces on that processor will be administratively shut down and marked as removed. The routing table will be flushed of any routes through the removed interfaces.

Recommended Action No action is required.

Error Message %ASR1000_OIR-6-SOFT_RELOADSPA : SPA([chars]) reloaded on [chars]

Explanation The SPA in the specified subslot is reloaded by the command hw-module subslot slot#/subslot# reload.

Recommended Action No action is required.

Error Message %ASR1000_OIR-6-SOFT_STARTSPA : SPA([chars]) restarted in [chars]

Explanation The SPA in the specified subslot is restarted by the command hw-module subslot slot#/subslot# start.

Recommended Action No action is required.

Error Message %ASR1000_OIR-6-SOFT_STOPSPA : SPA([chars]) stopped in [chars], interfaces disabled

Explanation The SPA in the specified subslot is stopped by the command hw-module subslot slot#/subslot# stop. The interfaces on that processor will be administratively shut down and marked as removed. The routing table will be flushed of any routes through the removed interfaces.

Recommended Action No action is required.

Error Message %ASR1000_OIR-6-SPARELOAD : SPA reloaded on subslot [int]/[int]

Explanation The SPA in the specified subslot is reloaded.

Recommended Action No action is required.

Error Message %ASR1000_OIR-6-SYNCSPA: SPA (%s) reloading to come up in %s mode

Explanation The SPA in the specified subslot is reloaded by the command hw-module subslot slot#/subslot# reload

Recommended Action No action is required.

ASR1000_PEM Messages

Error Message %ASR1000_PEM-3-FANFAIL: The fan in slot [dec]/[dec] is encountering a failure condition

Explanation The fan’s hardware is reporting that the fan is failing. This is most likely because the hardware detects the fan as spinning below the minimum speed.

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

Error Message %ASR1000_PEM-3-PEMCHASFSERR : The PEM in slot [dec] has encountered a system software error.

Explanation The PEM’s underlying software for storing PEM state is not working properly.

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

Error Message %ASR1000_PEM-3-PEMFAIL : The PEM in slot [dec] is switched off or encountering a failure

Explanation 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ASR1000_PEM-6-FANOK: The fan in slot [dec]/[dec] is functioning properly

Explanation The fan was reporting a failure condition. This message indicates that the fan is no longer reporting a failure.

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

Error Message %ASR1000_PEM-6-INSPEM_FM : PEM/FM slot P[int] inserted

Explanation The platform detected the insertion of a power/fan module in the slot number specified in the message.

Recommended Action No action is required.

Error Message %ASR1000_PEM-6-PEMOK: The PEM in slot [dec] is functioning properly

Explanation The PEM hardware may have been either switched off, or reporting a failure condition. This message indicates that the PEM is no longer either switched off, or reporting a failure.

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

Error Message %ASR1000_PEM-6-REMPEM_FM: PEM/FM slot P[int] removed

Explanation The platform detected the removal of a power/fan module in the slot number specified in the message.

Recommended Action No action is required.

ASR1000_PROCMIB Messages

Error Message %ASR1000_PROCMIB-4-MSGERR : [chars] Error with process mib message from sub-slot [dec]/[dec], MCP_PROCMIB_LIMIT

Explanation When processing a process MIB message from the specified subslot, the specified error has occurred.

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

Error Message %ASR1000_PROCMIB-4-SENDMSGERR : Failure in sending process mib information from subslot [dec]/[dec] to RP, MCP_PROCMIB_LIMIT

Explanation A failure is encountered when sending process MIB statistics from the IOS driver for the subslot specified in the message to RP IOS. This indicates a software failure.

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

ASR1000_RP Messages

Error Message %ASR1000_RP_ALARM-6-INFO: [chars] [chars] [chars] [chars] [chars]

Explanation Alarm assertion or deassertion information.

Recommended Action No action is required.

Error Message %ASR1000_RP_CFG_NOT-2-MSGIPCINITERROR: Error initializing IPC queue

Explanation An unexpected condition in which IOS could not initialize a message queue to the PSD.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_CFG_NOT-2-MSGNOEXP: Can not construct a ’%s’ message for configuration export: %s

Explanation This error usually indicates either an out of memory condition or a TDL error. If ample memory is available, then the TDL error may indicate a version conflict with respect to configuration.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_CFG_NOT-2-MSGTDLERROR: Error processing TDL message. %d

Explanation An unexpected condition in which IOS has received a TDL message which it cannot process.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_CFG_NOT-2-MSGTDLINITERROR: Configuration Notification messaging module initialization failed: Unable to initialize messaging: %s

Explanation The Configuration Notification subsystem has failed to initialize the infrastructure for messaging with the Plugable Services Daemon. Notification of configuration to critical modules cannot proceed.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_CFG_NOT-3-MSGENCRYPTINVALID: The mcprp_cfg_notify subsystem has seen an encryption type it does not recognize. %d

Explanation An unexpected condition has occurred while IOS is trying to process a username command.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_CFG_NOT-3-MSGIPCTXERROR: IPC transmit error. %d

Explanation An unexpected condition in which IOS encountered an error trying to send a message to another process. %d

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_CFG_NOT-3-MSGNOCAND: Can not construct a candidate entry for configuration export

Explanation This error usually indicates either an out of memory condition or a TDL error. If ample memory is available, then the TDL error may indicate a version conflict with respect to configuration.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_CFG_NOT-3-MSGNOPWARR: Can not construct an array for configuration export

Explanation This error usually indicates either an out of memory condition or a TDL error. If ample memory is available, then the TDL error may indicate a version conflict with respect to configuration.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_CFG_NOT-3-MSGNOREPLMSG: Can not construct a replace message for configuration export

Explanation This error usually indicates either an out of memory condition or a TDL error. If ample memory is available, then the TDL error may indicate a version conflict with respect to configuration.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_CFG_NOT-3-MSGNOUPDATEMSG: Can not construct an update message for configuration export

Explanation This error usually indicates either an out of memory condition or a TDL error. If ample memory is available, then the TDL error may indicate a version conflict with respect to configuration.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_CFG_NOT-3-MSGOBJNULL: An unexpected condition in which IOS has received a null pointer that it expects to be non-null.

Explanation An unexpected condition has occurred while IOS is trying to process a username command.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_CFG_NOT-3-NVWRITE_EXPORT: Failed to export %s notification: %d

Explanation When a ’write memory’ or ’write erase’ operation occurs, the Configuration Notification subsystem exports this event into the chassis file system. This message indicates that the export failed.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_DIAG_TEST-3-MSGDIAGCANTENQUEUE: Online diagnostics could not enqueue a diagnostic test response.

Explanation The asr1000 online diagnostics failed to respond properly to a request by the system to perform a diagnostic test.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_DIAG_TEST-3-MSGDIAGTIMEOUT: A timeout occurred while waiting for an online diagnostic test to finish.

Explanation The asr1000 online diagnostics failed to respond properly to a request by the system to perform a diagnostic test.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_DIAG_TEST-3-MSGIPCTXERROR: IPC transmit error. %d

Explanation An unexpected condition in which IOS encountered an error trying to send a message to another process. %d

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_DIAG_TEST-3-MSGOBJNULL: An unexpected condition in which IOS has received a null pointer that it expects to be non-null.

Explanation An unexpected condition has occurred while IOS is trying to perform online diagnostics work.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_DIAG_TEST-3-MSGRESPTDLERR: A diagnostic test result could not be read properly.

Explanation The asr1000 online diagnostics failed to respond properly to a request by the system to perform a diagnostic test.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_DIAG_TEST-3-MSGTDLERROR: Error processing TDL message. %d

Explanation An unexpected condition in which IOS has received a TDL message which it cannot process.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_DIAG_TEST-4-ERR_CNTR_HM_TEST_DATA: ERROR_COUNTER_DATA: ID:%d IN:%D PO:%d RE:%d RM:%d DV:%u EG:%d CF:%d TF:%d

Explanation Error Counter Monitoring test has failed on one of the cards of ASR1000, Corresponding Data is printed.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_DIAG_TEST-4-ERR_CNTR_HM_TEST_FAIL: ERROR_COUNTER_WARNING: Slot %s Error counter exceeds threshold, system operation continue.

Explanation Error Counter Monitoring test has failed on the given card of ASR1000.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_DIAG_TEST-6-MSGOUTOFORDER: Received a test result after IOS had timed out. [%d,%d]

Explanation When a diagnostic test is performed, IOS waits for the result be returned. If it does not return in a specified period of IOS times out on that test request and moves on.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_DIAG_TEST-6-MSGUNEXPECTEDEVENT: Unexpected event recieved.

Explanation When a diagnostic test is performed, IOS waits for the result be returned. While waiting for the result, IOS unexpectedly received an event it does not recognize and so IOS stopped waiting for the result. The test continued, IOS does not know what the results are and hence cannot report them.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_DPIDB-3-BULK_SYNC: Failed to send %s information to peer

Explanation The bulk synchronization of the DPIDX configuration to the standby RP has failed to complete successfully; DPIDX has therefore taken the action which will result in a reload of the peer in order to once more attempt to successfully synchronize the configuration state which may have failed initially to a transient condition.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_DPIDB-3-CF: Datapath IDB CF operation failed — %s

Explanation Failure in some datapath ID CF activity.

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

Error Message %ASR1000_RP_DPIDB-3-DECODE: Decode via %s of %s failed

Explanation A message of the transport and type described failed in its attempt to be decoded on the standby. The resultant action taken by the standby route processor is an attempt to re-synchronize.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_DPIDB-3-DOWNLOADFAIL: Unable to download %s message to %s

Explanation An unexpected condition has occurred which resulted in a configuration not being sent to the reported process.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_DPIDB-3-DYN_SYNC: Failed to process %s dynamic state

Explanation The incremental synchronization of the DPIDX configuration to the standby RP has failed to complete successfully. This implies that the configuration state between the active and standby RP is inconsistent.

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

Error Message %ASR1000_RP_DPIDB-3-EFPSTATSFAILED: EFP stats message data get error: (%d) for EFP %u on %s

Explanation An unexpected error occurred extracting fields from an EFP stats message.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_DPIDB-3-FASTNOTIFY: Fast notify failed for %s

Explanation A fast notify message failed

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

Error Message %ASR1000_RP_DPIDB-3-FRRLDFLOWIDDELETIONFAILED: Deletion of fast-reroute flow ID with manager failed

Explanation An unexpected condition has occurred that deletion of fast-reroute flow ID.

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

Error Message %ASR1000_RP_DPIDB-3-IDBBADTYPE: Datapath IDB type %d is not valid

Explanation An unexpected condition has occurred as the type of a datapath IDB is not valid.

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

Error Message %ASR1000_RP_DPIDB-3-IDBEXIST: Datapath IDB already exists in this mapping entry: %s-%d

Explanation An unexpected condition has occurred that an attempt is made to save datapath IDB in a mapping entry filled by another.

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

Error Message %ASR1000_RP_DPIDB-3-IDBNONEXIST: Datapath IDB does not exist in this mapping entry: %s-%d

Explanation Datapath IDB lookup points to empty mapping entry.

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

Error Message %ASR1000_RP_DPIDB-3-IDBNOTVAI: Invalid API call for %s

Explanation Failure in an internal API

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

Error Message %ASR1000_RP_DPIDB-3-IDXALLOCFAILED: Datapath IDB index allocation failed: %s

Explanation An unexpected condition has occurred as all the available of datapath IDB indices are used.

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

Error Message %ASR1000_RP_DPIDB-3-IDXBADRANGE: Datapath IDB index %d is not in a valid range

Explanation An unexpected condition has occurred as the index of a datapath IDB is not valid.

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

Error Message %ASR1000_RP_DPIDB-3-IDXDELETIONFAILED: Deletion of datapath IDB index from the database failed (%s — 0x%x) rc %d

Explanation An unexpected condition has occurred that deletion of datapath IDB indices failed.

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

Error Message %ASR1000_RP_DPIDB-3-IDXINSERTFAILED: Insertion of datapath IDB index %d into database failed

Explanation An unexpected condition has occurred that insertion of datapath IDB indices failed.

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

Error Message %ASR1000_RP_DPIDB-3-IDXLOOKUPFAILED: Lookup of datapath IDB index from the database failed (%s)

Explanation An unexpected condition has occurred that lookup of datapath IDB indices failed.

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

Error Message %ASR1000_RP_DPIDB-3-ISSU: %s %s failed; %s

Explanation An operation pertaining to the ISSU support for DPIDX failed to complete using either the CF or IPC transport context with the reason specified

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_DPIDB-3-LIST: List %s failed for %s

Explanation List enqueue or removal failed

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

Error Message %ASR1000_RP_DPIDB-3-NEGOTIATION: Failed to start ISSU %s session negotiation; %s

Explanation The ISSU negotiation with the peer failed to start for either the CF or IPC transport with the reason specified.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_DPIDB-3-NOHWSUBBLOCK: HWIDB %s does not have a ASR1000 subblock

Explanation An unexpected condition has occurred that no ASR1000 subblock was previously allocated for a HWIDB.

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

Error Message %ASR1000_RP_DPIDB-3-NOSWSUBBLOCK: SWIDB %s does not have a ASR1000 subblock

Explanation An unexpected condition has occurred that no ASR1000 subblock was previously allocated for a SWIDB.

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

Error Message %ASR1000_RP_DPIDB-3-NULLTIMER: NULL timer

Explanation A timer is NULL

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

Error Message %ASR1000_RP_DPIDB-3-PROGRESSION: Unable to inform RF of bulk sync completion; %s

Explanation The active route processor has sent a notification to the standby to inform of the completion of the bulk synchronization of the DPIDX configuration. The standby has failed to respond to the active informing that it received the notification noting the reason for the failure. The resultant action taken by the standby route processor is an attempt to re-synchronize.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_DPIDB-3-RECEIVE: Message via %s is %s

Explanation An attempt to receive and process a versioned negotiation or synchronization message has failed due to an internal error being detected by the information received from the IPC or CF components.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_DPIDB-3-REGISTRATION: ISSU %s failed for %s; %s

Explanation An ISSU registration for the set of initial capabilities and sessions failed due to the reason specified. This will have the effect of the DPIDX ISSU support being unavailable between peers.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_DPIDB-3-RF: Datapath IDB RF operation failed — %s

Explanation Failure in some datapath ID RF activity.

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

Error Message %ASR1000_RP_DPIDB-3-RPC: Datapath IDB RPC operation failed — %s

Explanation Failure in some datapath ID RPC activity.

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

Error Message %ASR1000_RP_DPIDB-3-TRANSFORM: %s of %s via %s failed for dpidx %u

Explanation An attempt to either encode or decode a versioned synchronization message has failed due to an internal error encountered by the ISSU component.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_DPIDB-3-TRANSMIT: Unable to send via %s %s %s %s; %s

Explanation An attempt to send a versioned negotiation or synchronization message has failed due to an internal error encountered by the IPC or CF components.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_DPIDB-6-READY: %s peer not ready, discarding %s

Explanation The synchronization attempt for the message has determined that the transport has lost communication with its peer. This is a normal situation which indicates that the standby route-processor is currently out of service implying a simplex redundancy mode.

Error Message %ASR1000_RP_DPIDB-6-RELOAD: %s, reloading %s

Explanation A synchronization attempt between the active and standby RP peers has failed with the reason indicated. The standby peer is reloaded in an attempt to re-synchronize when operating in a stateful redundant mode.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_DPIDB-6-TIMEOUT: Bulk sync is flow controlled by %s

Explanation The bulk synchronization of the DPIDX configuration to the standby RP has encountered a flow control condition which has effected a timeout awaiting the condition to clear. This will result in a reload of the standby RP to allow the bulk synchronization to restart.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_IF_FLOW_IDS-3-BUFF_OFFSET_NULL: Unable to utilize the memory buffer provided by the Checkpoint Facility. This %s CF client has failed to Bulk Sync.

Explanation This error indicates the Checkpoint Facility is having problems recognizing its own buffer layout. If this occurs during Bulk Sync then Bulk Sync will terminate without completing. Otherwise the incremental Sync will fail.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_IF_FLOW_IDS-3-CF_CANNOT_REGISTER: The call to add this %s CF client to the Checkpoint Facility failed with the error %s. This client is unable to proceed and will not be registered.

Explanation For some reason the Checkpoint Facility will not register this client. As a result the Standby will never receive synchronized state from this CF client on the Active RP, The system is not capable of SSO and HA switchover.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_IF_FLOW_IDS-3-CF_SEND_BULK_NONBLOCKED: The Checkpoint Facility reported the error %s while attempting tosend a message. Bulk Sync of this %s CF client is terminating.

Explanation This error indicates the Checkpoint Facility has internal problems related to IPC, and cannot perform a non-blocked send operation.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_IF_FLOW_IDS-3-CF_SEND_INCR_NONBLOCKED: The Checkpoint Facility reported the error %s while attempting tosend a non-blocked message. The Incremental Sync transaction for this %s CF client cannot be sent to the Standby RP.

Explanation This error indicates the Checkpoint Facility has internal problems related to IPC.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_IF_FLOW_IDS-3-DECODE: Decode via CF of %s failed

Explanation A message sent via the CF transport failed in its attempt to be decoded on the standby. The resultant action taken by the standby route processor is an attempt to re-synchronize.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_IF_FLOW_IDS-3-DEFERRED_DURING_BULK_SYNC: Encountered error %s while trying to place an %s transaction on the Deferred list during Bulk Sync for the %s CF client.

Explanation Unable to cache a deferred transaction while Bulk Sync is underway. This can adversely impact SSO state on the Standby RP.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_IF_FLOW_IDS-3-ISSU_OP: %s %s failed; %s

Explanation An operation pertaining to the ISSU support for SPA MARMOT IDs failed to complete using the CF transport context with the reason specified

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_IF_FLOW_IDS-3-NEGOTIATION: Failed to start ISSU %s session negotiation; %s

Explanation The ISSU negotiation with the peer failed to start for either the CF or IPC transport with the reason specified.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_IF_FLOW_IDS-3-NO_BUFF_FOR_SYNC: The Checkpoint Faclity reported the error %s during a request for a buffer length of %d. This %s CF client has failed to synchronize a transaction to the Standby RP.

Explanation This error indicates that the buffer management within the Checkpoint Facility has either run out of buffers, or has some other problem.If this occurs during Bulk Sync then Bulk Sync will terminate without completing. Otherwise the incremental Sync will fail.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_IF_FLOW_IDS-3-RECEIVE: Client reports message CF is %s

Explanation An attempt to receive and process a versioned negotiation or synchronization message has failed due to an internal error being detected by the information received from the CF component.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_IF_FLOW_IDS-3-REGISTRATION: ISSU %s failed for %s; %s

Explanation An ISSU registration for the set of initial capabilities and sessions failed due to the reason specified. This will have the effect of the SPA MARMOT ID ISSU support being unavailable between peers.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_IF_FLOW_IDS-3-RF_ADD_CLIENT_FAILED: The RF facility failed to add this %s client, reason given is %s.

Explanation This indicates the RF facility could not add the client.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_IF_FLOW_IDS-3-RF_IF_ID_REGEN_ERROR: Error code %d encountered trying to regenerate interface flow-control identifer. If id %u resides in slot/subslot/port (%u/%u/%u).

Explanation The background process which performs Flow Control Id Pool regeneration encountered an error. As a consequence the Standby does not have valid Id pools and cannot progress to Active state.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_IF_FLOW_IDS-3-RF_PEER_EVENT_BUFFER: This %s RF client is unable to acquire an event buffer to send an RF peer message, the error %s was returned.

Explanation This indicates the RF facility is unable to provide a message buffer needed to communicate with the RF peer. As a consequence the RF progression may be compromised.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_IF_FLOW_IDS-3-RF_POOL_REGEN_ERROR: Id Pool Regeneration encountered error code %d, cannot switchover.

Explanation The background process which performs Flow Control Id Pool regeneration encountered an error. As a consequence the Standby does not have valid Flow Id pools and cannot progress to Active state.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_IF_FLOW_IDS-3-RF_POOL_REGEN_PROCESS_FAILED: The %s RF client Failed to create the Id Pool Regeneration process.

Explanation The background process which performs Flow Control Id Pool regeneration failed to start. As a consequence the Standby will never obtain the relevant SSO state to enable HA switchover.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_IF_FLOW_IDS-3-RF_PROCESS_FAILED: This %s RF client Failed to create the Bulk Sync Process.

Explanation The background process which performs the RF Bulk Sync failed to be created. As a consequence the Standby will never obtain the relevant SSO state to enable HA switchover.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_IF_FLOW_IDS-3-RF_SEND_PEER: This %s RF client encountered error %s, when attempting to send a peer message.

Explanation This indicates the RF facility could not send a message to the RF peer. As a consequence the RF progression may be compromised.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_IF_FLOW_IDS-3-RF_SPA_ID_REGEN_ERROR: Error code %d encountered trying to regenerate spa %s identifier in slot/subslot (%u/%u)

Explanation The background process which performs Flow Control Id Pool regeneration encountered an error. As a consequence the Standby does not have valid Id pools and cannot progress to Active state.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_IF_FLOW_IDS-3-SEND_FAIL_RELOAD: Checkpoint Facility Failed to send a %s transaction for this %s CF client. Reloading the Standby RP.

Explanation This indicates the underlying Checkpoint Facility could not deliver a message sent from the active RP to the standby RP. The process will automatically reload the standby RP.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_IF_FLOW_IDS-3-TRANSFORM: %s of %s via CF failed

Explanation An attempt to either encode or decode a versioned synchronization message has failed due to an internal error encountered by the ISSU component.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_IF_FLOW_IDS-3-TRANSMIT: Unable to send via %s %s %s %s; %s

Explanation An attempt to send a versioned negotiation or synchronization message has failed due to an internal error encountered by the CF component.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_IF_FLOW_IDS-4-DEF_LIST_REMOVE: Failed to remove one entry from the Deferred Sync list, for the %s CF client.

Explanation An unexpected condition occurred during list maintenance.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_IF_FLOW_IDS-6-CFPEER_CANNOT_RECV: The Checkpoint Peer is not ready to receive messages. The Incremental Sync transaction for this %s CF client will not occur.

Explanation This error indicates the Checkpoint Facility has signalled the peer has gone away.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_IF_FLOW_IDS-6-READY: %s peer not ready, discarding %s

Explanation The synchronization attempt for the message has determined that the transport has lost communication with its peer. This is a normal situation which indicates that the standby route-processor is currently out of service implying a simplex redundancy mode.

Error Message %ASR1000_RP_MGMTE-3-MSGCREATENULL: Cannot allocate %s TDL message

Explanation An unexpected condition in which IOS cannot allocate TDL message for Management Ethernet.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_MGMTE-3-MSGTDLINITERROR: Management ethernet interface messaging module initialization failed: Unable to initialize messaging: %s

Explanation The Management Ethernet interface subsystem has failed to initialize the infrastructure for messaging with the Plugable Services Daemon. Configuration of management Ethernet modules cannot proceed.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_MGMTE-3-PROCESS_CREATE_FAIL: Management ethernet statistics process creation failed

Explanation Cannot create IOS process for RP management Ethernet port statistics collection

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_RP_NV-3-NV_ACCESS_FAIL: Initial read of NVRAM contents failed

Explanation This error happens when the contents of the NVRAM cannot be read during system initialization. The failure may be due to data corruption of the NVRAM contents. The initial configuration dialog will be entered and the configuration must be restored.

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

ASR1000_RP_ATM_SPA Messages

Error Message %ASR1000_RP_ATM_SPA-3-ATM_DPIDB_ALLOC_FAIL: Failed to allocate a data plane identifier for interface [chars] for VCD [dec]

Explanation The SPA driver is not able to allocate the datapath identifier for the VCD under the interface specified in the message. This indicates a software error.

Recommended Action No action is required.

Error Message %ASR1000_RP_ATM_SPA-3-ATM_DPIDB_GET_FAIL: Failed to get a data plane identifier for interface [chars] for VCD [dec]

Explanation The SPA driver is not able to obtain the datapath identifier for the VCD under the interface specified in the message. This indicates a software error.

Recommended Action No action is required.

Error Message %ASR1000_RP_ATM_SPA-3-ATM_FLOWID_GET_FAIL: Failed to get a flow control identifier for interface [chars] for index [dec]

Explanation The SPA driver is not able to obtain the datapath flow control identifier for the data path identifier under the interface specified in the message. This indicates a software error.

Recommended Action No action is required.

Error Message %ASR1000_RP_ATM_SPA-5-MPVCVPSETUP: Interface [chars] has a VC/VP ([dec]) configured already, VC/VP ([dec]) cannot be configured.

Explanation The SPA ATM driver supports configuring only one VC/VP under a point to multi point sub-interface. The sub-interface specified in the message already has VP/VC configured.

Recommended Action No action is required.

Error Message %ASR1000_RP_ATM_SPA-3-PROCESS_FAIL: process creation failed for [chars]

Explanation The Periodic one second process creation failed.This indicates a software error.

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

Error Message %ASR1000_RP_ATM_SPA-4-SETUPVC: Interface [chars], VC ([dec]) setup failed, reason = [dec]

Explanation A command to setup a VC has failed on RP.

Recommended Action The SPA ATM driver has detected a problem creating the internal OAMVC. Reload the indicated SPA card to reconfigure the internal OAM VC. If the error messages recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ASR1000_RP_ATM_SPA-4-TEARDOWNVC: Interface [chars], VC ([dec]) teardown failed, reason = [dec]

Explanation A command to remove a VC configuration has failed on RP.

Recommended Action The SPA ATM driver has detected a problem tearing down the internal OAM VC. Reload the indicated SPA card to do a clean tear down of the internal OAM VC. If the error messages recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

ASR1000_RP_CFG_NOT Messages

Error Message %ASR1000_RP_CFG_NOT-2-MSGIPCINITERROR : Error initializing IPC queue

Explanation An unexpected condition in which IOS could not initialize a message queue to the PSD.

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

Error Message %ASR1000_RP_CFG_NOT-2-MSGNOEXP : Can not construct a ‘[chars]’ message for configuration export: [chars]

Explanation This error usually indicates either an out of memory condition or a TDL error. If ample memory is available, then the TDL error may indicate a version conflict with respect to configuration.

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

Error Message %ASR1000_RP_CFG_NOT-2-MSGTDLERROR : Error processing TDL message. %d

Explanation An unexpected condition in which IOS has received a TDL message which it cannot process.

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

Error Message %ASR1000_RP_CFG_NOT-2-MSGTDLINITERROR : Configuration Notification messaging module initialization failed: Unable to initialize messaging: [chars]

Explanation The Configuration Notification subsystem has failed to initialize the infrastructure for messaging with the Plugable Services Daemon. Notification of configuration to critical modules cannot proceed.

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

Error Message %ASR1000_RP_CFG_NOT-3-MSGENCRYPTINVALID: The mcprp_cfg_notify subsystem has seen an encryption type it does not recognize. [dec]

Explanation An unexpected condition has occurred while IOS is trying to process a username command.

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

Error Message %ASR1000_RP_CFG_NOT-3-MSGIPCTXERROR: IPC transmit error. %d

Explanation An unexpected condition in which IOS encountered an error trying to send a message to another process. %d

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

Error Message %ASR1000_RP_CFG_NOT-3-MSGNOCAND: Can not construct a candidate entry for configuration export

Explanation This error usually indicates either an out of memory condition or a TDL error. If ample memory is available, then the TDL error may indicate a version conflict with respect to configuration.

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

Error Message %ASR1000_RP_CFG_NOT-3-MSGNOPWARR: Can not construct an array for configuration export

Explanation This error usually indicates either an out of memory condition or a TDL error. If ample memory is available, then the TDL error may indicate a version conflict with respect to configuration.

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

Error Message %ASR1000_RP_CFG_NOT-3-MSGNOREPLMSG: Can not construct a replace message for configuration export

Explanation This error usually indicates either an out of memory condition or a TDL error. If ample memory is available, then the TDL error may indicate a version conflict with respect to configuration.

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

Error Message %ASR1000_RP_CFG_NOT-3-MSGNOUPDATEMSG: Can not construct an update message for configuration export

Explanation This error usually indicates either an out of memory condition or a TDL error. If ample memory is available, then the TDL error may indicate a version conflict with respect to configuration.

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

Error Message %ASR1000_RP_CFG_NOT-3-MSGOBJNULL: An unexpected condition in which IOS has received a null pointer that it expects to be non-null.

Explanation An unexpected condition has occurred while IOS is trying to process a username command.

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

Error Message %ASR1000_RP_CFG_NOT-3-NVWRITE_EXPORT: Failed to export [chars] notification: [dec]

Explanation When a ’write memory’ or ’write erase’ operation occurs, the Configuration Notification subsystem exports this event into the chassis file system. This message indicates that the export failed.

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

ASR1000_RP_CTE1_SPA Messages

Error Message %ASR1000_RP_CTE1_SPA-3-CCIPCFAIL: Communication with the CC has failed for Interface [dec]/[dec]

Explanation Communication with the SPA interface processor (SIP) is unavailable.

Recommended Action Either try to configure the shared port adapter (SPA) at a later time, or reload the SIP.

Error Message %ASR1000_RP_CTE1_SPA-3-IPCERR: Internal IPC error [chars]

Explanation Internal IPC error.

Recommended Action Either try to configure the shared port adapter at a later time, or reload the SPA SIP.

Error Message %ASR1000_RP_CTE1_SPA-3-UNSUPERR: NULL

Explanation An internal error as resulted from an unsupported or unexpected message.

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

ASR1000_RP_DIAG_TEST Messages

Error Message %ASR1000_RP_DIAG_TEST-3-MSGDIAGCANTENQUEUE: Online diagnostics could not enqueue a diagnostic test response.

Explanation The Cisco ASR1000 Series Router online diagnostics failed to respond properly to a request by the system to perform a diagnostic test.

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

Error Message %ASR1000_RP_DIAG_TEST-3-MSGDIAGTIMEOUT: A timeout occurred while waiting for an online diagnostic test to finish.

Explanation The Cisco ASR1000 Series Router online diagnostics failed to respond properly to a request by the system to perform a diagnostic test.

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

Error Message %ASR1000_RP_DIAG_TEST-3-MSGIPCTXERROR: IPC transmit error. %d

Explanation An unexpected condition in which IOS encountered an error trying to send a message to another process. [dec]

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

Error Message %ASR1000_RP_DIAG_TEST-3-MSGOBJNULL: An unexpected condition in which IOS has received a null pointer that it expects to be non-null.

Explanation An unexpected condition has occurred while IOS is trying to perform online diagnostics work.

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

Error Message %ASR1000_RP_DIAG_TEST-3-MSGRESPTDLERR : A diagnostic test result could not be read properly.

Explanation The Cisco ASR1000 Series Router online diagnostics failed to respond properly to a request by the system to perform a diagnostic test.

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

Error Message %ASR1000_RP_DIAG_TEST-3-MSGTDLERROR : Error processing TDL message. %d

Explanation An unexpected condition in which IOS has received a TDL message which it cannot process.

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

Error Message %ASR1000_RP_DIAG_TEST-6-MSGOUTOFORDER: Received a test result after IOS had timed out. [%d,%d]

Explanation When a diagnostic test is performed, IOS waits for the result be returned. If it does not return in a specified period of IOS times out on that test request and moves on.

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

Error Message %ASR1000_RP_DIAG_TEST-6-MSGUNEXPECTEDEVENT: Unexpected event recieved.

Explanation When a diagnostic test is performed, IOS waits for the result be returned. While waiting for the result, IOS unexpectedly received an event it does not recognize and so IOS stopped waiting for the result. The test continued, IOS does not know what the results are and hence cannot report them.

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

ASR1000_RP_DPIDB Messages

Error Message %ASR1000_RP_DPIDB-3-BULK_SYNC: Failed to send %s information to peer

Explanation The bulk synchronization of the DPIDX configuration to the standby RP has failed to complete successfully; DPIDX has therefore taken the action which will result in a reload of the peer in order to once more attempt to successfully synchronize the configuration state which may have failed initially to a transient condition.

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

Error Message %ASR1000_RP_DPIDB-3-CF: Datapath IDB CF operation failed — %s

Explanation Failure in some datapath ID CF activity.

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

Error Message %ASR1000_RP_DPIDB-3-DECODE: Decode via %s of %s failed

Explanation A message of the transport and type described failed in its attempt to be decoded on the standby. The resultant action taken by the standby route processor is an attempt to re-synchronize.

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

Error Message %ASR1000_RP_DPIDB-3-DOWNLOADFAIL: Unable to download %s message to %s

Explanation An unexpected condition has occurred which resulted in a configuration not being sent to the reported process.

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

Error Message %ASR1000_RP_DPIDB-3-DYN_SYNC: Failed to process %s dynamic state

Explanation The incremental synchronization of the DPIDX configuration to the standby RP has failed to complete successfully. This implies that the configuration state between the active and standby RP is inconsistent.

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

Error Message %ASR1000_RP_DPIDB-3-EFPSTATSFAILED : EFP stats message data get error: (%d) for EFP %u on %s

Explanation An unexpected error occurred extracting fields from an EFP stats message.

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

Error Message %ASR1000_RP_DPIDB-3-FASTNOTIFY: Fast notify failed for [chars]

Explanation A fast notify message failed.

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

Error Message %ASR1000_RP_DPIDB-3-FRRLDFLOWIDDELETIONFAILED: Deletion of fast-reroute flow ID with manager failed

Explanation An unexpected condition has occurred that deletion of fast-reroute flow ID.

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

Error Message %ASR1000_RP_DPIDB-3-IDBBADTYPE: Datapath IDB type [dec] is not valid

Explanation An unexpected condition has occurred as the type of a datapath IDB is not valid.

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

Error Message %ASR1000_RP_DPIDB-3-IDBEXIST: Datapath IDB already exists in this mapping entry: %s-%d

Explanation An unexpected condition has occurred that an attempt is made to save datapath IDB in a mapping entry filled by another.

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

Error Message %ASR1000_RP_DPIDB-3-IDBNONEXIST: Datapath IDB does not exist in this mapping entry: %s-%d

Explanation Datapath IDB lookup points to empty mapping entry.

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

Error Message %ASR1000_RP_DPIDB-3-IDBNOTVAI: Invalid API call for [chars]

Explanation Failure in an internal API.

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

Error Message %ASR1000_RP_DPIDB-3-IDXALLOCFAILED: Datapath IDB index allocation failed: %s

Explanation An unexpected condition has occurred as all the available of datapath IDB indices are used.

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

Error Message %ASR1000_RP_DPIDB-3-IDXBADRANGE: Datapath IDB index %d is not in a valid range

Explanation An unexpected condition has occurred as the index of a datapath IDB is not valid.

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

Error Message %ASR1000_RP_DPIDB-3-IDXDELETIONFAILED: Deletion of datapath IDB index from the database failed

Explanation An unexpected condition has occurred that deletion of datapath IDB indices failed.

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

Error Message %ASR1000_RP_DPIDB-3-IDXINSERTFAILED: Insertion of datapath IDB index %d into database failed

Explanation An unexpected condition has occurred that insertion of datapath IDB indices failed.

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

Error Message %ASR1000_RP_DPIDB-3-IDXLOOKUPFAILED: Lookup of datapath IDB index from the database failed (%s)

Explanation An unexpected condition has occurred that lookup of datapath IDB indices failed.

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

Error Message %ASR1000_RP_DPIDB-3-ISSU: %s %s failed; %s

Explanation An operation pertaining to the ISSU support for DPIDX failed to complete using either the CF or IPC transport context with the reason specified.

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

Error Message %ASR1000_RP_DPIDB-3-LIST: List [chars] failed for [chars]

Explanation List enqueue or removal failed.

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

Error Message %ASR1000_RP_DPIDB-3-NEGOTIATION: Failed to start ISSU %s session negotiation; %s

Explanation The ISSU negotiation with the peer failed to start for either the CF or IPC transport with the reason specified.

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

Error Message %ASR1000_RP_DPIDB-3-NOHWSUBBLOCK: HWIDB %s does not have a ASR1000 subblock

Explanation An unexpected condition has occurred that no Cisco ASR1000 subblock was previously allocated for a HWIDB.

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

Error Message %ASR1000_RP_DPIDB-3-NOSWSUBBLOCK: SWIDB %s does not have a ASR1000 subblock

Explanation An unexpected condition has occurred that no Cisco ASR1000 subblock was previously allocated for a SWIDB.

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

Error Message %ASR1000_RP_DPIDB-3-NULLTIMER: NULL timer

Explanation A timer is NULL.

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

Error Message %ASR1000_RP_DPIDB-3-PROGRESSION: Unable to inform RF of bulk sync completion; %s

Explanation The active route processor has sent a notification to the standby to inform of the completion of the bulk synchronization of the DPIDX configuration. The standby has failed to respond to the active informing that it received the notification noting the reason for the failure. The resultant action taken by the standby route processor is an attempt to re-synchronize.

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

Error Message %ASR1000_RP_DPIDB-6-READY: [chars] peer not ready, discarding [chars]

Explanation The synchronization attempt for the message has determined that the transport has lost communication with its peer. This is a normal situation which indicates that the standby route-processor is currently out of service implying a simplex redundancy mode.

Recommended Action No action is required.

Error Message %ASR1000_RP_DPIDB-3-RECEIVE: Message via %s is %s

Explanation An attempt to receive and process a versioned negotiation or synchronization message has failed due to an internal error being detected by the information received from the IPC or CF components.

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

Error Message %ASR1000_RP_DPIDB-3-REGISTRATION: ISSU %s failed for %s; %s

Explanation An ISSU registration for the set of initial capabilities and sessions failed due to the reason specified. This will have the effect of the DPIDX ISSU support being unavailable between peers.

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

Error Message %ASR1000_RP_DPIDB-3-RF : Datapath IDB RF operation failed — %s

Explanation Failure in some datapath ID RF activity.

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

Error Message %ASR1000_RP_DPIDB-3-RPC: Datapath IDB RPC operation failed — [chars]

Explanation Failure in some datapath ID RPC activity.

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

Error Message %ASR1000_RP_DPIDB-3-TRANSFORM : %s of %s via %s failed for dpidx %u

Explanation An attempt to either encode or decode a versioned synchronization message has failed due to an internal error encountered by the ISSU component.

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

Error Message %ASR1000_RP_DPIDB-3-TRANSMIT: Unable to send via %s %s %s %s; %s

Explanation An attempt to send a versioned negotiation or synchronization message has failed due to an internal error encountered by the IPC or CF components.

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

Error Message %ASR1000_RP_DPIDB-6-READY : %s peer not ready, discarding %s

Explanation The synchronization attempt for the message has determined that the transport has lost communication with its peer. This is a normal situation which indicates that the standby route-processor is currently out of service implying a simplex redundancy mode.

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

Error Message %ASR1000_RP_DPIDB-6-RELOAD: %s, reloading %s

Explanation A synchronization attempt between the active and standby RP peers has failed with the reason indicated. The standby peer is reloaded in an attempt to re-synchronize when operating in a stateful redundant mode.

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

Error Message %ASR1000_RP_DPIDB-6-TIMEOUT: Bulk sync is flow controlled by %s

Explanation The bulk synchronization of the DPIDX configuration to the standby RP has encountered a flow control condition which has effected a timeout awaiting the condition to clear. This will result in a reload of the standby RP to allow the bulk synchronization to restart.

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

ASR1000_RP_IF_FLOW_IDS Messages

Error Message %ASR1000_RP_IF_FLOW_IDS-3-BUFF_OFFSET_NULL: Unable to utilize the memory buffer provided by the Checkpoint Facility. This [chars] CF client has failed to Bulk Sync.

Explanation This error indicates the Checkpoint Facility is having problems recognizing its own buffer layout. If this occurs during Bulk Sync then Bulk Sync will terminate without completing. Otherwise the incremental Sync will fail.

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

Error Message %ASR1000_RP_IF_FLOW_IDS-3-CF_CANNOT_REGISTER: The call to add this [chars] CF client to the Checkpoint Facility failed with the error [chars]. This client is unable to proceed and will not be registered.

Explanation For some reason the Checkpoint Facility will not register this client. As a result the Standby will never receive synchronized state from this CF client on the Active RP, The system is not capable of SSO and HA switchover.

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

Error Message %ASR1000_RP_IF_FLOW_IDS-3-CF_SEND_BULK_NONBLOCKED: The Checkpoint Facility reported the error [chars] while attempting tosend a message. Bulk Sync of this [chars] CF client is terminating.

Explanation This error indicates the Checkpoint Facility has internal problems related to IPC, and cannot perform a non-blocked send operation.

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

Error Message %ASR1000_RP_IF_FLOW_IDS-3-CF_SEND_INCR_NONBLOCKED: The Checkpoint Facility reported the error [chars] while attempting tosend a non-blocked message. The Incremental Sync transaction for this [chars] CF client cannot be sent to the Standby RP.

Explanation This error indicates the Checkpoint Facility has internal problems related to IPC.

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

Error Message %ASR1000_RP_IF_FLOW_IDS-3-DECODE: Decode via CF of %s failed

Explanation A message sent via the CF transport failed in its attempt to be decoded on the standby. The resultant action taken by the standby route processor is an attempt to re-synchronize.

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

Error Message %ASR1000_RP_IF_FLOW_IDS-3-DEFERRED_DURING_BULK_SYNC: Encountered error [chars] while trying to place an [chars] transaction on the Deferred list during Bulk Sync for the [chars] CF client.

Explanation Unable to cache a deferred transaction while Bulk Sync is underway. This can adversely impact SSO state on the Standby RP.

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

Error Message %ASR1000_RP_IF_FLOW_IDS-3-ISSU_OP: %s %s failed; %s

Explanation An operation pertaining to the ISSU support for SPA MARMOT IDs failed to complete using the CF transport context with the reason specified.

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

Error Message %ASR1000_RP_IF_FLOW_IDS-3-NEGOTIATION: Failed to start ISSU [chars] session negotiation; [chars]

Explanation The ISSU negotiation with the peer failed to start for either the CF or IPC transport with the reason specified.

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

Error Message %ASR1000_RP_IF_FLOW_IDS-3-NO_BUFF_FOR_SYNC: The Checkpoint Faclity reported the error [chars] during a request for a buffer length of [dec]. This [chars] CF client has failed to synchronize a transaction to the Standby RP.

Explanation This error indicates that the buffer management within the Checkpoint Facility has either run out of buffers, or has some other problem.If this occurs during Bulk Sync then Bulk Sync will terminate without completing. Otherwise the incremental Sync will fail.

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

Error Message %ASR1000_RP_IF_FLOW_IDS-3-RECEIVE: Client reports message CF is [chars]

Explanation An attempt to receive and process a versioned negotiation or synchronization message has failed due to an internal error being detected by the information received from the CF component.

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

Error Message %ASR1000_RP_IF_FLOW_IDS-3-REGISTRATION: ISSU [chars] failed for [chars]; [chars]

Explanation An ISSU registration for the set of initial capabilities and sessions failed due to the reason specified. This will have the effect of the SPA MARMOT ID ISSU support being unavailable between peers.

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

Error Message %ASR1000_RP_IF_FLOW_IDS-3-RF_ADD_CLIENT_FAILED: The RF facility failed to add this [chars] client, reason given is [chars].

Explanation This indicates the RF facility could not add the client.

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

Error Message %ASR1000_RP_IF_FLOW_IDS-3-RF_IF_ID_REGEN_ERROR: Error code [dec] encountered trying to regenerate interface flow-control identifer. If id [int] resides in slot/subslot/port ([int]/[int]/[int]).

Explanation The background process which performs Flow Control ID Pool regeneration encountered an error. As a consequence the Standby does not have valid ID pools and cannot progress to Active state.

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

Error Message %ASR1000_RP_IF_FLOW_IDS-3-RF_PEER_EVENT_BUFFER: This [chars] RF client is unable to acquire an event buffer to send an RF peer message, the error [chars] was returned.

Explanation This indicates the RF facility is unable to provide a message buffer needed to communicate with the RF peer. As a consequence the RF progression may be compromised.

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

Error Message %ASR1000_RP_IF_FLOW_IDS-3-RF_POOL_REGEN_ERROR: Id Pool Regeneration encountered error code [dec], cannot switchover.

Explanation The background process which performs Flow Control ID Pool regeneration encountered an error. As a consequence the Standby does not have valid Flow ID pools and cannot progress to Active state.

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

Error Message %ASR1000_RP_IF_FLOW_IDS-3-RF_POOL_REGEN_PROCESS_FAILED: The [chars] RF client Failed to create the Id Pool Regeneration process.

Explanation The background process which performs Flow Control ID Pool regeneration failed to start. As a consequence the Standby will never obtain the relevant SSO state to enable HA switchover.

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

Error Message %ASR1000_RP_IF_FLOW_IDS-3-RF_PROCESS_FAILED: This [chars] RF client Failed to create the Bulk Sync Process.

Explanation The background process which performs the RF Bulk Sync failed to be created. As a consequence the Standby will never obtain the relevant SSO state to enable HA switchover.

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

Error Message %ASR1000_RP_IF_FLOW_IDS-3-RF_SEND_PEER: This [chars] RF client encountered error [chars], when attempting to send a peer message.

Explanation This indicates the RF facility could not send a message to the RF peer. As a consequence the RF progression may be compromised.

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

Error Message %ASR1000_RP_IF_FLOW_IDS-3-RF_SPA_ID_REGEN_ERROR: Error code [dec] encountered trying to regenerate spa [chars] identifier in slot/subslot ([int]/[int])

Explanation The background process which performs Flow Control Id Pool regeneration encountered an error. As a consequence the Standby does not have valid Id pools and cannot progress to Active state.

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

Error Message %ASR1000_RP_IF_FLOW_IDS-3-SEND_FAIL_RELOAD: Checkpoint Facility Failed to send a [chars] transaction for this [chars] CF client. Reloading the Standby RP.

Explanation This indicates the underlying Checkpoint Facility could not deliver a message sent from the active RP to the standby RP. The process will automatically reload the standby RP.

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

Error Message %ASR1000_RP_IF_FLOW_IDS-3-TRANSFORM: [chars] of [chars] via CF failed

Explanation An attempt to either encode or decode a versioned synchronization message has failed due to an internal error encountered by the ISSU component.

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

Error Message %ASR1000_RP_IF_FLOW_IDS-3-TRANSMIT: Unable to send via [chars] [chars] [chars] [chars]; [chars]

Explanation An attempt to send a versioned negotiation or synchronization message has failed due to an internal error encountered by the CF component.

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

Error Message %ASR1000_RP_IF_FLOW_IDS-4-DEF_LIST_REMOVE: Failed to remove one entry from the Deferred Sync list, for the [chars] CF client.

Explanation An unexpected condition occurred during list maintenance.

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

Error Message %ASR1000_RP_IF_FLOW_IDS-6-CFPEER_CANNOT_RECV: The Checkpoint Peer is not ready to receive messages. The Incremental Sync transaction for this [chars] CF client will not occur.

Explanation This error indicates the Checkpoint Facility has signalled the peer has gone away.

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

Error Message %ASR1000_RP_IF_FLOW_IDS-6-READY: [chars] peer not ready, discarding [chars]

Explanation The synchronization attempt for the message has determined that the transport has lost communication with its peer. This is a normal situation which indicates that the standby route-processor is currently out of service implying a simplex redundancy mode.

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

ASR1000_RP_MGMTE Messages

Error Message %ASR1000_RP_MGMTE-3-MSGCREATENULL : Cannot allocate [chars] TDL message

Explanation An unexpected condition in which IOS cannot allocate TDL message for Management Ethernet.

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

Error Message %ASR1000_RP_MGMTE-3-MSGTDLINITERROR: Management ethernet interface messaging module initialization failed: Unable to initialize messaging: [chars]

Explanation The Management Ethernet interface subsystem has failed to initialize the infrastructure for messaging with the Plugable Services Daemon. Configuration of management Ethernet modules cannot proceed.

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

Error Message %ASR1000_RP_MGMTE-3-PROCESS_CREATE_FAIL: Management ethernet statistics process creation failed

Explanation Cannot create IOS process for RP management Ethernet port statistics collection

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

ASR1000_RP_ONLINE_DIAG Messages

Error Message %ASR1000_RP_ONLINE_DIAG-3-MSGMAXCARDS: Online diagnostics maximum number of cards exceeded

Explanation An unexpected condition in which IOS has attempted to register more hardware cards for diagnostics than it expects the maximum to be.

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

Error Message %ASR1000_RP_ONLINE_DIAG-3-MSGOBJNULL: An unexpected condition in which IOS has received a null pointer that it expects to be non-null.

Explanation An unexpected condition has occurred while IOS is trying to perform online diagnostics work.

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

Error Message %ASR1000_RP_ONLINE_DIAG-3-MSGTDLERROR: Error processing TDL message. [dec]

Explanation An unexpected condition in which IOS has received a TDL message which it cannot process.

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

ASR1000_RP_POS_SPA Messages

Error Message %ASR1000_RP_POS_SPA-4-ALLOCFAIL: Interface [dec]/[dec] allocation failed: [chars]

Explanation Required resources are unavailable.

Recommended Action Either upgrade system memory or reconfigure memory usage.

ASR1000_RP_SONET_ALARM Messages

Error Message %ASR1000_RP_SONET_ALARM-6-POS: [chars] [chars] [chars] [chars] [chars]

Explanation This message is generated whenever (a) an alarm is present in the system (and the alarm status has been reported to the RP) or (b) an alarm has been removed from the system (and the alarm status has been reported to the RP.

Recommended Action No action is required.

ASR1000_RP_SPA Messages

Error Message %ASR1000_RP_SPA-3-BAD_IFCOMTYPE: Bad ifcom message type=[int]

Explanation A SPA module passed down a message that the RP software was not prepared to handle.

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

Error Message %ASR1000_RP_SPA-3-CI_UPDATE_FAIL : Failed to update connection identifier for interface [chars]

Explanation The SPA driver is not able to update the datapath connection identifier for the interface specified in the message. This indicates a software error.

Recommended Action No action is required.

Error Message %ASR1000_RP_SPA-3-DPIDX_LKUP_FAIL : Failed to retrieve datapath identifier for interface [chars]

Explanation The SPA driver is not able to retrieve the datapath identifier for the interface specified in the message. This indicates a software error.

Recommended Action No action is required.

Error Message %ASR1000_RP_SPA-3-ERROR : This message can take many forms. It provides information about a software error.

Explanation The SPA module passed down a logger message that is too long for the RP to handle.

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

Error Message %ASR1000_RP_SPA-3-FLOWID_ALLOC_FAIL: Failed to allocate a flow control identifier for interface [chars]

Explanation The SPA driver is not able to allocate the datapath flow control identifier for the interface specified in the message. This indicates a software error.

Recommended Action No action is required.

Error Message %ASR1000_RP_SPA-3-FLOWID_RELEASE_FAIL: Failed to release a flow control identifier for interface [chars] (status = [dec])

Explanation The SPA driver is not able to release the datapath flow control identifier for the interface specified in the message. This indicates a software error.

Recommended Action No action is required.

Error Message %ASR1000_RP_SPA-3-FOREVER: cmd [int] to [chars] (slot [int]/[int]) took [int] usecs, done [hex]

Explanation A CCB command from the RP to a SPA module took longer than expected.

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

Error Message %ASR1000_RP_SPA-3-FRR_CFG_REC_FAIL: Failed to record fast reroute conifguration on [chars]: [chars]

Explanation This message is displayed when a fast reroute configuration is not properly recorded.

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

Error Message %ASR1000_RP_SPA-3-HWIDB_FAILURE: Creation: slot [dec] subSlot [dec] port [dec] vc [dec]

Explanation Failed to create an interface hwidb.

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

Error Message %ASR1000_RP_SPA-3-HWIDB_INIT_FAIL: Failed to initialize data structure for SPA port [dec]/[dec]/[dec]

Explanation A SPA driver was not able to properly initialize a data structure mentioned in the message. This indicates a software error.

Recommended Action No action is required.

Explanation This message can take many forms. It provides information about a software error.

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

Error Message %ASR1000_RP_SPA-3-IFCFG_CMD_NOT_OWNER: Process ’[chars]’ waiting for interface configuration command ([hex]) to slot [int]/[int] without acquiring lock owned by process ’[chars]’

Explanation A process on the RP sent an configuration command to the slot specified in the error message and a different process waited for the result. This could cause incorrect line card configuration states.

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

Error Message %ASR1000_RP_SPA-3-IFCFG_FOREVER: to [chars] (slot [int]/[int]) took [int] usecs, ret_val [int]

Explanation A interface configuration command from the RP to a SPA module took longer than expected.

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

Error Message %ASR1000_RP_SPA-3-IFCFG_NO_UNIQUE_KEY: No unique-key generator registered for interface configuration command [int].

Explanation The High Availability component for SPA modules is unable to properly synchronize state information for the current configuration.

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

Error Message %ASR1000_RP_SPA-3-INVALID_PORT_NUM: slot=[dec] port=[dec], hwidbType=[hex], max_port_num=[dec], LCtype=[hex]

Explanation The port number is out of range.

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

Error Message %ASR1000_RP_SPA-3-IPCALLOCFAIL: Failed to allocate IPC buffer [chars]

Explanation The RP failed to allocate a buffer for communication with a SPA.

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

Error Message %ASR1000_RP_SPA-3-IPCPORT: Failed to [chars] IPC port ’[chars]’, error [chars]

Explanation The linecard failed to create a port for communication with the Route Processor (ASR1000-RP).

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

Error Message %ASR1000_RP_SPA-3-IPCPORTFAIL: Failed to open IPC port ’[chars]’ with error [chars]

Explanation The RP failed to open a port for communication with a SPA module.

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

Error Message %ASR1000_RP_SPA-3-IPCSENDFAIL: Failed to send IPC message [chars]

Explanation The RP failed to send a message to a SPA module.

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

Error Message %ASR1000_RP_SPA-3-MAX_SPA: Power to IPSEC-SPA-2G in %s is denied because it has exceeded the number allowed(%d)

Explanation The number of IPSEC-SPA-2G in a chassis is limited.This message is displayed when the number of IPSEC-SPA-2G in the chassis has exceeded this limit.

Recommended Action Use only the number of supported IPSEC-SPA-2G

Error Message %ASR1000_RP_SPA-3-MISSING_SPA_PKG_ERR: sipspa[chars] package is not installed for slot = [dec] and subslot = [dec], SPA bootup failed.

Explanation This message is displayed when attempting to bootup a SPA without installing a subpackage required for the same.

Recommended Action Download the sub-package required for the affected SPA from the Cisco CCO software download site and install the same. This SPA can be booted in sub-package mode only. Refer to the Cisco ASR platform documentation for obtaining and installing sub-packages.

Error Message %ASR1000_RP_SPA-3-MISSING_SPA_PKG_WARN: sipspa[chars] package is not installed in standby for slot = [dec] and subslot = [dec].

Explanation This message is displayed in standby console when attempting to bootup or restart or reload a WMA SPA without installing a subpackage in the standby RP, although the SPA is or will be operational due to prior wma spa package installation in active RP. If switchover takes place the WMA SPA will still be operational. But any subsequent soft or hard oir of the SPA will fail due to missing sub package required to boot up the SPA. Hence it is recommended to complete the WMA SPA package installation in standby also before switchover or immediately after switchover.

Recommended Action Download the sub-package required for the affected SPA from the Cisco CCO software download site and install the same for the standby RP as is done on active RP. Refer to the Cisco ASR platform documentation for obtaining and installing sub-packages.

Error Message %ASR1000_RP_SPA-3-NO_HOST_INFO: slot [dec] subSlot [dec], spaType [hex]

Explanation Failed to get information about the host linecard.

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

Error Message %ASR1000_RP_SPA-3-NULL_DATA_STRUCTURE : A SPA driver is not able to retrieve the data structure mentioned in the message. This indicates a software error.

Explanation A SPA driver was not able to properly initialize a data structure mentioned in the message. This indicates a software error.

Recommended Action No action is required.

Error Message %ASR1000_RP_SPA-3-PROGRESSION: Unable to inform RF of bulk sync completion; [chars]

Explanation The standby has failed to notify the active that its bulks synchronization of the SPA TSM has completed. The resultant action taken by the standby route processor is an attempt to re-synchronize.

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

Error Message %ASR1000_RP_SPA-3-SPA_NO_HOST_INFO : slot [dec] subSlot [dec], PID [chars]

Explanation Failed to get information about the host linecard.

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

Error Message %ASR1000_RP_SPA-3-UNSUPPORTED_SRVCS_SPA Service SPA (hex) in [dec]/[dec] is not supported. SPA bootup failed.

Explanation This message is displayed when attempting to bootup any service SPA in router running non K9 image, i.e., non-crypto image.

Recommended Action Download the K9 IOS XE sub-packages and the required sub-package for the given service SPA from the Cisco CCO software download site and install the same. This SPA can be booted in sub-package mode only. Refer to the Cisco ASR platform documentation for obtaining and installing sub-packages.

Error Message %ASR1000_RP_SPA-3-VC_FLOWID_ALLOC_FAIL: Failed to allocate a flow control identifier for VC [dec]under interface [chars]

Explanation The SPA driver is not able to allocate the datapath flow control identifier for the VC/interface specified in the message. This indicates a software error.

Recommended Action No action is required.

Error Message %ASR1000_RP_SPA-3-VC_INGID_ALLOC_FAIL: Failed to allocate a ingress identifier for VC [dec] interface [chars]

Explanation The SPA driver is not able to allocate the datapath ingress identifier for the VC/interface specified in the message. This indicates a software error.

Recommended Action No action is required.

Error Message %ASR1000_RP_SPA-3-VC_PROV_FAIL: Failed to provision interface [chars]

Explanation The SPA driver is not able to provision the interface specified in the message. Verify that the SPA hardware is not provisioned above the supported limit. Otherwise, this indicates a hardware error.

Recommended Action No action is required.

Error Message %ASR1000_RP_SPA-4-CCB_PLAYBACK_ERROR: CCB playback failed for slot [dec].

Explanation The High Availability component for SPA modules failed to synchronize some new state information for the specified slot.

Recommended Action Reload the standby supervisor module to force a fresh bulk synchronization. If this error recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ASR1000_RP_SPA-4-CCB_RECORD_ERROR: CCB record failed for slot [dec].

Explanation The High Availability component for SPA modules failed to record some new state information for the specified slot.

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

Error Message %ASR1000_RP_SPA-4-IFCFG_CMD_TIMEOUT: Interface configuration command ([hex]) to slot [int]/[int] timed out

Explanation The RP sent an configuration command to the slot specified in the error message and received no confirmation for the command.

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

Error Message %ASR1000_RP_SPA-4-IFCFG_DFLT_LIST_ERROR: For Interface Configuration command [int], default retval list search resulted [hex] for slot [int]/[int]

Explanation The High Availability component for SPA modules failed to synchronize some new state information for the specified slot.

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

Error Message %ASR1000_RP_SPA-4-IFCFG_PLAYBACK_ERROR: Interface Configuration command [int] playback failed for slot [int]/[int].

Explanation The High Availability component for SPA modules failed to synchronize some new state information for the specified slot.

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

Error Message %ASR1000_RP_SPA-4-IFCFG_RECORD_ERROR: Interface Configuration command [int] record failed for slot [int]/[int].

Explanation The High Availability component for SPA modules failed to record some new state information for the specified slot.

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

Error Message %ASR1000_RP_SPA-4-INCR_CFG_SYNC_FAIL: ASR1000 incremental running-config sync for [[dec]/[dec]] failed — [chars]([dec]), Reload Standby

Explanation The specified Cisco ASR 1000 Series Router incremental running-configuration synchronization failed.

Recommended Action Power cycle the redundant supervisor.

Error Message %ASR1000_RP_SPA-4-IPCFAILED: IPC failed to send RPC message to SPA module

Explanation The RP failed to send an RPC message via IPC to a SPA module.

Recommended Action No action is required.

Error Message %ASR1000_RP_SPA-4-LCLOG_PARSE_ERR: Error parsing logger message: [chars] from subslot [int]/[int]

Explanation The SPA module passed down a logger message that could not be parsed.

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

Error Message %ASR1000_RP_SPA-4-LCLOG_TOOLONG: Message too long from slot [int]/[int]: [int] bytes

Explanation The SPA module passed down a logger message that is too long for the RP to handle.

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

Error Message %ASR1000_RP_SPA-4-SEMAHOG: Process [dec] ([chars]) hogging [chars]! calling proc [dec] ([chars])

Explanation The RP waited too long for a reply to a command sent to a SPA module.

Recommended Action No action is required.

Error Message %ASR1000_RP_SPA-4-SPA_CMD_NO_RESP: [chars]: No response for interface configuration command [int]

Explanation A timeout occurred while RP was waiting for a response from line card. This may happen due to line card CPU being too busy to respond to the command.

Recommended Action No action is required.

Error Message %ASR1000_RP_SPA-4-SPA_RESP_CMD_ERR: [chars]: Received response to interface configuration command [chars] with wrong return value [int].

Explanation An internal error occurred while configuring the interface. The configuration may not have succeeded.

Recommended Action Check that the running configuration for the interface is correct. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ASR1000_RP_SPA-4-SPA_RESP_CMD_MISMATCH: [chars]: Expecting response to interface configuration command [int] but received response to command [int].

Explanation An internal synchronization error occurred while configuring the interface. The configuration may not have succeeded.

Recommended Action Check that the running configuration for the interface is correct. If this message occurred on the standby, try reloading the standby to ensure that its configuration is synchronized. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ASR1000_RP_SPA-6-CARDRELOAD: Module [int] reload due to SPA insert in [int]/[int].

Explanation When inserting a SPA on this carrier card, the card is reset.

Recommended Action No action is required.

Error Message %ASR1000_RP_SPA-6-CTRLRSWITCH : switching controller type from [chars]([dec]) to [chars]([dec]) for subslot [int]/[int].

Explanation When ASR1000-SIP40 is inserted in the slot previously occupied by ASR1000-SIP10 or vice-versa the controller type of the card is overwritten to reflect the current SIP.

Recommended Action No action is required.

Error Message %ASR1000_SPA-6-TDLMSG_INCOMPATIBLE : Failed to copy message [chars]] not allowed for current domain.

Explanation Failure to marshal a message indicates an incompatibility with the intended recipient.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter. Issue the show tech-support command to gather data that may help identify the nature of the error. Also perform a search of the Bug Search Tool. If you still require assistance, 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.

ASR1000_RP_VTYMGT Messages

Error Message %ASR1000_RP_VTYMGT-3-MSGBIPCBUFFER: Unable to acquire a BIPC buffer of length [dec] for sending messages.

Explanation A message was to be sent by IOS, but no BIPC buffer was available. The message to be sent has been discarded and the associated operation failed.

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

Error Message %ASR1000_RP_VTYMGT-3-MSGBIPCERR: Unable to process received BIPC messages for Vty Management, error: [chars]

Explanation An unexpected condition has occurred while IOS was trying to process a received BIPC message for Vty Management.

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

Error Message %ASR1000_RP_VTYMGT-3-MSGBUILDERROR: Error ’[dec]’ building TDL Vty Management message ’[chars]’: [chars]

Explanation An unexpected condition has occurred while IOS is building a TDL response message for Vty Management.

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

Error Message %ASR1000_RP_VTYMGT-3-MSGDISPATCH: Unable to dispatch received TDL messages for Vty Management

Explanation An unexpected condition has occurred while IOS is trying to dispatch to the TDL message handler functions for received TDL messages for Vty Management.

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

Error Message %ASR1000_RP_VTYMGT-3-MSGDISPATCHNULL: Received NULL TDL message

Explanation An unexpected condition in which IOS has received a NULL TDL message for Vty Management.

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

Error Message %ASR1000_RP_VTYMGT-3-MSGENQUEUEERROR: Error queueing TDL Vty Management message ’[chars]’

Explanation An unexpected condition has occurred when IOS attempted to queue a TDL response message for Vty Management.

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

Error Message %ASR1000_RP_VTYMGT-3-MSGERROR: Error ’[dec]’ handling a received TDL message ’[chars]’ for Vty Management: [chars]

Explanation An unexpected condition has occurred while IOS is processing a received Vty Management TDL message.

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

Error Message %ASR1000_RP_VTYMGT-3-MSGEXTAPPUPDATE: Unable to update external application data for line ’[dec]’

Explanation An attempt to update the external application for a line failed unexpectedly. The line update failed and if the line number specified is valid, the line was released.

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

Error Message %ASR1000_RP_VTYMGT-3-MSGINVALIDFIELDINT: Invalid field ’[chars]’ in TDL message ’[chars]’ received: value ’[int]’ for Vty Management

Explanation A message with an invalid field value was received for Vty Management.

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

Error Message %ASR1000_RP_VTYMGT-3-MSGINVALIDFIELDSTR: Invalid field ’[chars]’ value ’[chars]’ in TDL message ’[chars]’ received for Vty Management

Explanation A message with an invalid field value was received for Vty Management.

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

Error Message %ASR1000_RP_VTYMGT-3-MSGMARSHALERROR: Error ’[dec]’ marshaling TDL Vty Management message ’[chars]’: [chars]

Explanation An unexpected condition has occurred while IOS is marshaling TDL response message for Vty Management.

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

Error Message %ASR1000_RP_VTYMGT-3-MSGMISSINGFIELD: Missing field ’[chars]’ in TDL Vty Management message ’[chars]’ received

Explanation A message missing a required field was received for Vty Management.

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

Error Message %ASR1000_RP_VTYMGT-3-MSGVTYCOUNT: Invalid vty count [dec] detected on initialization

Explanation Upon initialization, the Vty Management subsystem checks that the number of available vtys for the platform is valid.

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

Error Message %ASR1000_RP_VTYMGT-3-MSGVTYSVCINIT: Unable to initialize the Vty Management service listen port

Explanation The platform IPC services failed to register the Vty Management service’s need for a listen port. The Vty Management service will be unable to process requests. IOS services will be unavailable to external access methods.

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

Error Message %ASR1000_RP_VTYMGT-3-SET_ACCESS_FAIL: Installing LIIN interface access control failed

Explanation This error happens when the Vty Management subsystem failed to set the access control function for the LIIN, possibly due to IOS out of memory or corruption. Persistent access features into IOS will not work.

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

ASR1000_SCHED Messages

Error Message %ASR1000_SCHED-3-AVL_INSERT_FAIL: Could not insert pid [dec] into process tree

Explanation An avl_insert() failed to add a process structure to the ASR1000 scheduler tree. This should never occur, as the tree is always searched first for the presence of the process.

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

Error Message %ASR1000_SCHED-3-CALLED_FROM_INT: API call incorrectly made from interrupt level

Explanation An external routine provided by the Cisco ASR 1000 Series Router scheduler was incorrectly called from the context of an interrupt handler. This is not a supported use of the external routine; the calling code must be fixed.

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

Error Message %ASR1000_SCHED-3-NEGATIVE_DEPTH: Queue ’[chars]’ consumed more than it produced ([dec])

Explanation Based upon internal state derived from calls to mcp_queue_produced() and mcp_queue_consumed(), more data was consumed from a balanced queue than was produced into it. This is logically impossible, so the presence of this error generally indicates incorrect use of the two above mentioned routines.

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

Error Message %ASR1000_SCHED-3-NULLQ: Invalid API parameter

Explanation An external routine provided by the ASR1000 scheduler was incorrectly called with an invalid (NULL) pointer.

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

ASR1000_SERVICE_ENGINE Messages

Error Message %ASR1000_SERVICE_ENGINE-3-MSGINITFAIL: Initialization of interface %s failed

Explanation The initialization of the interface mentioned in the error message has failed.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_SERVICE_ENGINE-3-MSGOPENFAIL: Cannot open interface %s (%d)

Explanation During the creation of a Service-Engine interface, it is necessary to program the system parameters in the driver. The driver cannot be opened.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_SERVICE_ENGINE-3-MSGSETFAIL: Set id on interface %s (%d)

Explanation During the creation of a Service-Engine interface, it is necessary to program the system parameters in the driver. The failed to accept the programming.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

ASR1000_SIP_CTE1_SPA Messages

Error Message %ASR1000_SIP_CTE1_SPA-3-TDL_ARG_ERR: Interface [dec]/[dec]/[dec]: Bad parameter in message from RP: [chars]

Explanation Bad parameter in message from RP.

Recommended Action Either try to configure the Shared Port Adapter at a later time, or reload the Card Carrier.

Error Message %ASR1000_SIP_CTE1_SPA-3-UNSUPERR: NULL

Explanation An internal error as resulted from an unsupported or unexpected message.

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

ASR1000_SIP_POS_SPA Messages

Error Message %ASR1000_SIP_POS_SPA-4-ALLOCFAIL: SPA resource allocation failed for subslot [dec]/[dec] while [chars]

Explanation The SPA driver in the subslot specified in the message is not able to allocate a system resource. The required system resource is specified in the message.

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

Error Message %ASR1000_SIP_POS_SPA-3-APS: APS([dec]) [chars]

Explanation RP deadman timer expired on CC, CC is sending LAIS to far end.

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

ASR1000_SIP_SPA Messages

Error Message %ASR1000_SIP_SPA-3-APS_CFG_FAIL : Failed to configure APS on [chars]: [chars].

Explanation The SPA driver failed to configure APS on an interface.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter. Also perform a search of the Bug Search Tool. If you still require assistance, 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.

Error Message %ASR1000_SIP_SPA-3-APS_PGP_FAIL : APS PGP Message send failed toslot/tobay [dec]: [dec].

Explanation APS PGP between working and protect has failed

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter. Also perform a search of the Bug Search Tool. If you still require assistance, 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.

Error Message %ASR1000_SIP_SPA-3-ASR1000IPCALLOCFAIL: Failed to allocate Common IPC buffer [chars]

Explanation The Carrier Card failed to allocate a buffer for communication with the Route Processor.

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

Error Message %ASR1000_SIP_SPA-3-BAD_IFCOMTYPE: Bad ifcom message type=[int]

Explanation The Route Processor (ASR1000-RP) passed down a message that the software was not prepared to handle.

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

Error Message %ASR1000_SIP_SPA-3-BADMALUCMD: Unsupported MALU command [dec], arg=[hex], pascb=[hex]

Explanation The Route Processor (ASR1000-RP) passed down a command that the software was not prepared to handle.

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

Error Message %ASR1000_SIP_SPA-3-BADMALUCMD2: Unsupported MALU cmd/arg0=[hex][hex], arg1arg2=[hex][hex], hwidb=[chars]

Explanation The Route Processor (ASR1000-RP) passed down a command that the software was not prepared to handle.

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

Error Message %ASR1000_SIP_SPA-3-C2W_MAIN_INIT_FAIL: Failed to initialize SPA main c2w bus for subslot [dec] (status = [dec])

Explanation The SPA driver is not able to initialize SPA main c2w. This indicates a hardware error.

Recommended Action No action is required.

Error Message %ASR1000_SIP_SPA-3-CMDNOINT: HWIDB Null for command [dec], port [hex]

Explanation The Route Processor passed down a port number that is unknown on the carrier card.

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

Error Message %ASR1000_SIP_SPA-3-DEVICE_ERROR: subSlot [dec], spatype [hex]. Device error: [chars]

Explanation An error related to a device on the SPA is detected.

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

Error Message %ASR1000_SIP_SPA-3-EFC_CHAN_ERR: EFC error — interface [chars], vc [dec], anyphy [dec], err_code [dec] : [chars]

Explanation Failed to configure efc channel/parameters.

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

Error Message %ASR1000_SIP_SPA-3-EFC_FC_MAP_FAIL: Failed to update EFC flow control identifier for interface [chars] (status = [dec])

Explanation The SPA driver is not able to update the datapath EFC flow control identifier for the interface specified in the message. This indicates a hardware error.

Recommended Action No action is required.

Error Message %ASR1000_SIP_SPA-3-EFC_PROV_FAIL: Failed to provision EFC for interface [chars] (status = [dec])

Explanation The SPA driver is not able to provision EFC for the interface specified in the message. This indicates a hardware error.

Recommended Action No action is required.

Error Message %ASR1000_SIP_SPA-3-EFC_UNPROV_FAIL: Failed to unprovision EFC for VC [chars] (status = [dec])

Explanation The SPA driver is not able to unprovision EFC for the interface specified in the message. This indicates a hardware error.

Recommended Action No action is required.

Error Message %ASR1000_SIP_SPA-3-FAST_NOTIFY_ERROR: Failed to send fast notification to [chars] for [chars] [chars].

Explanation The SPA driver failed to deliver a fast notification.

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

Error Message %ASR1000_SIP_SPA-3-FCI_NOT_SET: Bay [dec] — FCI type not set

Explanation An FCI type of zero was detected.

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

Error Message %ASR1000_SIP_SPA-3-FRR_CFG_FAIL: Failed to configure fast reroute on [chars]: [chars].

Explanation The SPA driver failed to configure fast rerouting on an interface.

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

Error Message %ASR1000_SIP_SPA-3-HWIDB_FAILURE: Creation: port [dec] vc [dec]

Explanation Failed to create a hwidb.

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

Error Message %ASR1000_SIP_SPA-3-INVALID_ANYPHY: Bay [dec] — Invalid anyphy number [int] for vc [dec]

Explanation Interface has invalid anyphy number.

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

Error Message %ASR1000_SIP_SPA-3-INVALID_IF: Attempted to access HWIDB for port [int] on slot [dec] subSlot [dec]

Explanation The Cisco ASR 1000 Series Router attempted to access the HWIDB associated with a non-existent port.

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

Error Message %ASR1000_SIP_SPA-3-IPCALLOCFAIL: Failed to allocate IPC buffer [chars]

Explanation The SPA failed to allocate a buffer for communication with the Route Processor (ASR1000-RP).

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

Error Message %ASR1000_SIP_SPA-3-IPCPORT: Failed to [chars] IPC port ’[chars]’, error [chars]

Explanation The linecard failed to create a port for communication with the Route Processor (ASR1000-RP).

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

Error Message %ASR1000_SIP_SPA-3-IPCPORTFAIL: Failed to open IPC port ’[chars]’ [chars] with error [chars]

Explanation The RP failed to open a port for communication with a SPA.

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

Error Message %ASR1000_SIP_SPA-3-IPCSENDFAIL: Failed to send IPC message [chars]

Explanation The Linecard failed to send a message to the Route Processor (ASR1000-RP).

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

Error Message %ASR1000_SIP_SPA-3-ISR_RC_ERROR: ISR return code out of range. rc=[dec]

Explanation The ISR error return code is out of range.

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

Error Message %ASR1000_SIP_SPA-3-LINKREC_ERROR: Link record error — Bay [dec] vc [dec], error code [dec]

Explanation Error processing link record structure.

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

Error Message %ASR1000_SIP_SPA-3-LVLTRTOOBIG: Loveletter length exceeds max, [int] bytes

Explanation The ASR1000-SIP line card attempted to send a large message to the Route Processor (ASR1000-RP).

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

Error Message %ASR1000_SIP_SPA-4-MAX_BANDWIDTH: Total SPA bandwidth exceeds line card capacity of [int] Mbps

Explanation The total bandwidth of SPAs exceeds the rated capacity of this line card.

Recommended Action Refer to the line card guidelines for the maximum allowable aggregated SPA bandwidth for the line card.

Error Message %ASR1000_SIP_SPA-4-MAX_BANDWIDTH_NS: Total SPA bandwidth exceeds line card capacity, full utilization of installed SPA interfaces is not supported

Explanation The total bandwidth of SPAs exceeds the rated capacity of this line card.

Recommended Action Refer to the line card guidelines for the maximum allowed aggregated SPA bandwidth for the line card.

Error Message %ASR1000_SIP_SPA-3-MESSAGE_ERROR: Bay [dec]: [chars]

Explanation An unexpected error has occurred.

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

Error Message %ASR1000_SIP_SPA-3-NETCLK_FAIL: Failed to [chars] SPA reference clock on [chars]

Explanation The SPA driver is not able to correctly configure the SPA reference clock on the specified interface. This indicates a hardware error.

Recommended Action No action is required.

Error Message %ASR1000_SIP_SPA-3-NODISPATCH: Dispatch vector Null, cmd=[dec], dintf=[dec]

Explanation No command dispatch vector was found for the specified interface.

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

Error Message %ASR1000_SIP_SPA-3-POWER: Bay [dec] 12V power is [chars]

Explanation SPA 12V power fault indicator.

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

Error Message %ASR1000_SIP_SPA-3-SONET_CLOCK_FAILED: SPA Sonet clock has failed (status = [hex])

Explanation The SPA SONET clock has failed. SPAs that rely on the SPA SONET clock for proper operation, such as POS and ATM will be affected.

Recommended Action If the SPA Sonet clock does not recover, perform an OIR. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ASR1000_SIP_SPA-3-SONET_CLOCK_RECOVERED: SPA Sonet clock has recovered (status = [hex])

Explanation SPA SONET clock has recovered.

Recommended Action No action is required.

Error Message %ASR1000_SIP_SPA-3-SPA_CTRL_EFC_CONFIG_FAILURE: Subslot, spa controller EFC configuration failure, error [dec]

Explanation Failed to configure SPA controller EFC.

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

Error Message %ASR1000_SIP_SPA-3-SPA_CTRL_INIT_FAILURE: Subslot [dec], spa controller initialisation failure, error [dec]

Explanation Failed to initialize SPA controller.

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

Error Message %ASR1000_SIP_SPA-3-SPA_INTF_ID_CC_ALLOC_FAILED: Failed to allocate interface identifiers for SPA (%s)in slot/bay: %u/%u

Explanation Failed to get CC buffer and flow control identifiers for the SPA in the specified subslot Traffic cannot flow through the SPA under this failure condition.This can happen if the system runs out of available identifiers.

Recommended Action Try to reduce the number of interfaces configured in the system either by physically removing the SPAs or by changing the system configuration

Error Message %ASR1000_SIP_SPA-3-SPI4_CONFIG_FAILURE: Bay [dec], spi4 configuration failure, error [dec]

Explanation Failed to configure SPI4 interface.

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

Error Message %ASR1000_SIP_SPA-3-SPI4_INIT_FAILURE: Bay [dec] initialization failure

Explanation Failed to create SPI4 subblock.

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

Error Message %ASR1000_SIP_SPA-3-SPI4_NOTSYNC: [chars]: Can not synchronize SPI4 bus (host: src [chars]in sync, sink [chars]in sync, spa: src [chars]in sync, sink [chars]in sync).

Explanation SPI4 bus between modular services card and SPA is not synchronized. It indicates either a not properly seated SPA, a hardware failure or an outdated ROMMON/FPGA image.

Recommended Action Ensure that the SPA is properly seated in its subslot and reseat it if required.

Error Message %ASR1000_SIP_SPA-4-MAX_BANDWIDTH : Total SPA bandwidth exceeds line card capacity of %lu Mbps

Explanation The total bandwidth of SPAs exceeds the rated capacity of this line card.

Recommended Action Refer to the line card guidelines for the maximum allowed aggregated SPA bandwidth for the line card.

Error Message %ASR1000_SIP_SPA-4-MAX_BANDWIDTH_NS : Total SPA bandwidth exceeds line card capacity, full utilization of installed SPA interfaces is not supported

Explanation The total bandwidth of SPAs exceeds the rated capacity of this line card.

Recommended Action Refer to the line card guidelines for the maximum allowed aggregated SPA bandwidth for the line card.

Error Message %ASR1000_SIP_SPA-4-SPABUS: Subslot [dec], [chars] SPA BUS access failed. timeout=[int] err=[int] par=[int] err_c=[hex] addr=[hex] data =[hex]

Explanation SPABUS has reported an error.

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

Error Message %ASR1000_SIP_SPA-4-SPABUS2: Subslot [dec] SPA BUS access failed. No SPA present error

Explanation SPABUS has reported an error.

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

Error Message %ASR1000_SIP_SPA-6-LOGGERMSGTOOBIG : Logger message length ([int] bytes) exceeds the maximum allowed size

Explanation The carrier card attempted to send a large message to the Route Processor

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter. Also perform a search of the Bug Search Tool. If you still require assistance, 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.

Error Message %ASR1000_SIP_SPA-6-OIR : Bay [dec] [chars] changed to [chars]

Explanation SPA OIR sequence.

Recommended Action No action is required.

ASR1000_SPA Messages

Error Message %ASR1000_SPA-3-CREATE_TDLH_FAILURE: Failed to create SPA [dec]/[dec] handle

Explanation Failed to create message handle for SPA communication.

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

Error Message %ASR1000_SPA-3-CREATE_TDLMSG_FAILURE: Failed to create [chars] message for [chars].

Explanation Failed to create/allocate necessary TDL message for SPA communication.

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

Error Message %ASR1000_SPA-3-CREATION_FAILURE: slot=[dec] subslot=[dec], spa_type=[hex], lc_type=[hex].

Explanation Failed to create a SPA object.

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

Error Message %ASR1000_SPA-3-DIAG_CONFIG: [chars] did not complete [dec]/[dec]

Explanation An error has occurred during diagnostic test.

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

Error Message %ASR1000_SPA-3-DISPATCH_INIT_TDLH_FAILURE: Failed to initialize dispatch path for SPA [dec]/[dec] handle

Explanation Failed to initialize dispatch path handle for SPA communication.

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

Error Message %ASR1000_SPA-3-DOMAIN_TDLH_FAILURE: [chars], rc = [dec]

Explanation Failed to bind message handle for SPA communication.

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

Error Message %ASR1000_SPA-3-INVALID_CPU_NUM: cpu= [dec], max cpu = [dec]

Explanation An invalid CPU number is specified in one of the internal APIs.

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

Error Message %ASR1000_SPA-3-INVALID_DATA_INSTANCE: interface type [chars], slot [dec] port [dec] vc [dec] : [chars]

Explanation Data required to support the interface is not available.

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

Error Message %ASR1000_SPA-3-INVALID_HANDLE: Failed to get a valid IPC handle for type %u, slot %d, subslot %d.

Explanation The client handle was found to be NULL for the given type/slot/subslot.

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

Error Message %ASR1000_SPA-3-INVALID_HANDLE: Failed to get a valid IPC handle for type %u, slot %d, subslot %d.

Explanation The client handle was found to be NULL for the given type/slot/subslot.

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

Error Message %ASR1000_SPA-3-INVALID_IF_INDEX: index= [dec], spaType=[hex], slot [dec] subSlot [dec] slotunit [dec] vc [dec]

Explanation Index for the interface is not valid.

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

Error Message %ASR1000_SPA-3-INVALID_INDX_RANGE: index1= [dec], index2= [dec], maxIndex= [dec]

Explanation An invalid index range is specified in one of the internal APIs.

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

Error Message %ASR1000_SPA-3-INVALID_RP_SLOT_NUM: slot= [dec], max slot = [dec]

Explanation An invalid RP slot number is specified in one of the internal APIs.

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

Error Message %ASR1000_SPA-3-INVALID_SLOT_NUM: slot= [dec], max slot = [dec]

Explanation An invalid slot number is specified in one of the internal APIs.

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

Error Message %ASR1000_SPA-3-INVALID_SLOTUNIT_NUM: cardwide-port = [dec], max cardwide-port = [dec]

Explanation An invalid cardwide-port number is specified in one of the internal APIs.

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

Error Message %ASR1000_SPA-3-INVALID_SPA_TDL_CCAPI_USAGE:

Explanation Incorrect usage of an internal API that should only be used on CC.

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

Error Message %ASR1000_SPA-3-INVALID_SUBSLOT_NUM: subslot= [dec], max subslot = [dec]

Explanation An invalid subslot number is specified in one of the internal APIs.

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

Error Message %ASR1000_SPA-3-IPC_FAILURE: IPC failure while [chars]

Explanation An error has occurred while preparing or sending an IPC message.

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

Error Message %ASR1000_SPA-3-MEM_ALLOC_ERROR: [chars]

Explanation Memory allocation error.

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

Error Message %ASR1000_SPA-3-NULL_SPA_PTR:

Explanation Pointer to a SPA object is NULL.

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

Error Message %ASR1000_SPA-3-NULL_VFT: [chars] virtual function table is not initialized. spaType=[hex]

Explanation A required function table is not initialized.

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

Error Message %ASR1000_SPA-3-NULL_VFUNC: [chars] vector is not initialized. spaType=[hex]

Explanation A required function vector is not initialized.

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

Error Message %ASR1000_SPA-3-POWER_CYCLE: [chars] occurred on Shared Port Adapter [int]/[int]

Explanation An error has occurred which will cause the Shared Port Adapter to be power cycled.

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

Error Message %ASR1000_SPA-3-SENDCFGFAIL: Failed to send configuration for [chars] to carrier-card for subslot=[dec]/[dec]

Explanation Sending configuration failed.

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

Error Message %ASR1000_SPA-3-SETUP_TDLH_FAILURE: Failed to set the alloc/free handler for SPA [dec]/[dec] handle

Explanation Failed to set the alloc/free handler for SPA communication.

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

Error Message %ASR1000_SPA-3-SPA_CREATION_FAILURE: slot=[dec] subslot=[dec], PID=[chars] lc_type=[hex].

Explanation Failed to create a SPA object.

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

Error Message %ASR1000_SPA-3-UNSUPPORTED_DATA: Data conversion error ([chars], [hex])

Explanation An internal software error has occurred when converting the data specified in the message from one representation to another.

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

ASR1000_SPA_ETHER Messages

Error Message %ASR1000_SPA_ETHER_DAMSELFLY-3-PLIM_QOS: Interface [chars], failed to apply PLIM QOS ([chars]), value = [hex], status = [hex]

Explanation Attempt to apply the configured input classification for the specified interface failed.

Recommended Action This indicates an internal software failure.

Error Message %ASR1000_SPA_ETHER_DAMSELFLY-3-UNSUPPORTED_XCVR: Transceiver type [chars] is not allowed on spa [chars], port [dec],

Explanation This transceiver is not allowed on the SPA.

Recommended Action Consult the documentation and ensure supported transceivers and plugged into the SPA.

Error Message %ASR1000_SPA_ETHER-3-TCAM_VLAN_ERROR: Failed to [chars] VLAN [dec] to/from interface [chars] (status = [dec])

Explanation The access to update the TCAM VLAN filtering table on the SPA failed. The error message indicates the SPA subslot and the affected interface and the VLAN entry that failed.

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

Error Message %ASR1000_SPA_ETHER-3-TCAM_VLAN_TABLE_FULL: Failed to add VLAN [dec] to interface [chars]

Explanation The TCAM VLAN filtering table on the SPA is full. The error message indicates the SPA subslot and the affected interface and the VLAN entry that failed. The specified VLAN identifier will not be added to the TCAM table.

Recommended Action Try to remove some of the registered VLANs for the interface by changing the interface configuration. To verify the VLAN IDs currently in use by an interface, enter the show vlans command.

ASR1000_VMAN Messages

Error Message %ASR1000_VMAN-3-MSGDISPATCH: Unable to dispatch received TDL message from Virt-Manager

Explanation An unexpected condition has occurred while IOS was trying to dispatch a TDL message received from Virt-Manager.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_VMAN-3-MSGINITFAIL: Failed to initalize required vman resource: %s

Explanation During the initialization of the resources required by vman, a failure occurred. This has prevented appliances from being activated.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %ASR1000_VMAN-3-RSPMSGHDLR: Failed to deliver response message: %s

Explanation An unexpected condition has occurred while IOS was trying to deliver a response message to an appliance received from Virt-Manager.

Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac . With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

ASR1000_WD Messages

Error Message %ASR1000_WD-2-HEARTBEAT_FAIL: Heartbeat is not emitted. Heartbeat count:[dec]

Explanation Failure in IOS to generate a heartbeat is an abnormal condition.

Recommended Action This message may be related to an abnormal configuration and system load, or transient high processing demand. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands, the stack trace, and your pertinent troubleshooting logs.

Error Message %ASR1000_WD-2-HOG_DETECT_FAIL: CPUHOG detection failed to start.

Explanation Failure in setting up CPUHOG detection mechanism is an abnormal condition.

Recommended Action This message may be related to an abnormal configuration and system load, or transient high processing demand. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands, the stack trace, and your pertinent troubleshooting logs.

ATMSPA Messages

Error Message %ATMSPA-3-DATA_ERROR: [chars] Error [hex] [chars]

Explanation A datapath protocol violation or sequence error has been detected.

Recommended Action The message text on the console or in the system log provides more information on the specific nature of the error. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ATMSPA-3-FATAL_ERROR: occurred on [chars]. Resetting SPA

Explanation The SPA has been reset due to a critical error in one of its devices. The error could either be a single occurrence of an event or multiple occurrences within a period of time. The message text on the console or in the system log provides more information on the specific nature of the error.

Recommended Action If the SPA is reset more than once, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ATMSPA-3-FPD_VER_DEPENDENCY_NOTE: Cannot perform the requested FPD update operation because [chars] in subslot [int]/[int] has incompatible HW version [int].[int] with FPD image version [dec].[dec] for FPD ID [dec]. Only image version greater than [int].[int] can be used in the update operation of [chars] with HW version greater than [int].[int].

Explanation The version of the FPD image from the FPD image bundle or package is not compatible with the HW version of the target card.

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

Error Message %ATMSPA-3-GEN_ERROR: [chars] Error [hex] [chars]

Explanation The specified error has been detected.

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

Error Message %ATMSPA-3-HW_ERROR: [chars] Error [hex] [chars]

Explanation The specified hardware error has been detected.

Recommended Action The message text on the console or in the system log provides more information on the specific nature of the error. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ATMSPA-2-INITFAIL: [chars] — Init Failed return code: [int]

Explanation The SPA failed to complete hardware initialization. One of the devices in the SPA failed to initialize successfully. Information about the failed device is specified in the message text on the console or in the system log.

Recommended Action Power down and reseat the indicated SPA card. If the condition 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 Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ATMSPA-3-KEEPALIVE_FAILURE: occurred on [chars]. Resetting SPA

Explanation One of the devices of the SPA failed to respond to keepalives due to which SPA has been reset. The message text on the console or in the system log provides more information on which device failed to respond.

Recommended Action If the SPA is reset more than once, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ATMSPA-3-QOS_ALLOC_FAILED: [chars] [chars] [chars]: [dec]

Explanation Traffic shaping parameters could not be configured because the number of unique shaping parameters that are configured on the PVCs or PVPs in this specified ATM SPA is over the maximum limit. The maximum number of unique shaping parameters that can be configured on the PVCs or PVPs is 4096.

Recommended Action Ensure that the total number of unique shaping parameters that are configured on both PVCs and PVPs does not exceed the maximum limit of 4096.

Error Message %ATMSPA-3-SW_ERROR: [chars] Error [hex] [chars]

Explanation The specified software error has been detected.

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

Error Message %ATMSPA-3-VCQ_ERROR: [chars]: VC queue configuration failed due to un-initialized queue table(global identifier [dec])

Explanation Software configuration of a VC queue failed due to un-initialized queue table.

Recommended Action Attempt to perform a soft OIR operation by entering the command that is described in the shared port adapter software configuration guide. If the condition 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 Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %ATMSPA-4-VCSETUP: [chars]: VC setup command received on the LC for an existing VC (VCD [dec])

Explanation A command to set up a VC has been received for a VC that has already been set up. The VC has already been configured by a previous setup VC command from the RP. A duplicate setup command may indicate that the RP did not receive a response from the LC for the previous setup command.

Recommended Action No action is required.

Error Message %ATMSPA-4-VCTEARDOWN: [chars]: VC tear down command received on the LC for a non-existing VC (VCD [dec])

Explanation The VC does not exist on the LC. Most likely, it has been torn down by a previous teardown command from RP. A duplicate teardown command may indicate that the RP did not receive a response from the LC for the previous teardown command.

Recommended Action No action is required.

Error Message %ATMSPA-4-VPSETUP: [chars]: VP setup command received on the LC for an existing VP (VPI [dec])

Explanation A command to set up a VP has been received for a VP that has already been set up. The VP has already been configured by a previous setup VP command from the RP. A duplicate setup command may indicate that the RP did not receive a response from the LC for the previous setup command.

Recommended Action No action is required.

Error Message %ATMSPA-4-VPTEARDOWN: [chars]: VP tear down command received on the LC for a non-existing VP (VPI [dec])

Explanation The VP does not exist on the LC. Most likely, it has been torn down by a previous teardown command from RP. A duplicate teardown command may indicate that the RP did not receive a response from the LC for the previous teardown command.

Recommended Action No action is required.

ATTN Messages

Error Message %ATTN-2-MBOX_REG_FAIL : return code [dec]

Explanation Registration of handler function for mailbox event failed mailbox event failed.

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

Error Message %ATTN-2-PROXY_INIT_FAIL_IPC_REG : return code [dec]

Explanation Initialization of attention proxy failed due to error registering IPC handler function.

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

Error Message %ATTN-3-PROXY_IPC_ALLOC_FAILED : [chars]

Explanation Allocation of an IPC packet buffer by the attention proxy failed.

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

Error Message %ATTN-3-PROXY_IPC_SEND_FAILED : [chars]

Explanation Transmission of an IPC message by the attention proxy failed.

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

Error Message %ATTN-3-PROXY_UNHANDLED_MSG : subtype [dec]

Explanation Attention proxy received a message with an unknown subtype.

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

Error Message %ATTN-3-SYNC_TIMEOUT : msecs since last timeout %llu, missing packets [dec]

Explanation Attention sync command timed out.

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

BACKUP_INTERFACES Messages

Error Message %BACKUP_INTERFACE-5-PREEMPT: Preempting interface %s in backup pair (%s, %s), preemption mode is %s

Explanation Preempting the current forwarding interface in the backup interface pair.

Recommended Action No action is required.

Error Message %BACKUP_INTERFACE-5-VLB_NON_TRUNK: Warning: Flexlink VLB is not allowed on non-trunk ports. Please configure %s to be a trunk port.

Explanation Flexlink VLB detects a non-trunk port.

Recommended Action No action is required.

BFD_MAP Messages

Error Message %BFD_MAP-3-MALLOC: Malloc failure %s

Explanation A malloc failure.

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

Error Message %BFD_MAP-3-MALLOC_MAP: Malloc failure %s %s

Explanation malloc failure

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

Error Message %BFD_MAP-3-WAVL_DELETE: Wavl delete failed for %p

Explanation wavl delete failed.

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

Error Message %BFD_MAP-3-WAVL_INIT_FAIL: Failed initializing wavl tree

Explanation wavl_init failed.

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

Error Message %BFD_MAP-3-WAVL_INSERT_FAIL: Wavl insert failed %s %s

Explanation wavl insert failed.

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

BINOS_LOGIN Messages

Error Message %BINOS_LOGIN-3-AUTHERR : The authentication process failed, [chars]

Explanation This error occurs when there is an error in the system that prevents the user from being successfully authenticated.

Recommended Action No action is required.

Error Message %BINOS_LOGIN-3-PWNOENT : No entry for user [chars] in passwd file

Explanation The username/password authenticated correctly, but the user’s environment could not be established because the user’s environment data is missing.

Recommended Action No action is required.

Error Message %BINOS_LOGIN-3-PAMERR : PAM error [chars] encountered.

Explanation The system encountered a PAM error.

Recommended Action No action is required.

Error Message %BINOS_LOGIN-6-PAMAUTHDENY : User was not authenticated

Explanation User was not authenticated.

Recommended Action No action is required.

Error Message %BINOS_LOGIN-6-PAMMAXTRIES : Maximum number of retries exceeded.

Explanation The user tried and failed too many times to login.

Recommended Action No action is required.

Error Message %BINOS_LOGIN-3-NOTROOT : login attempted to run without proper credentials.

Explanation login cannot be run without proper credentials.

Recommended Action No action is required.

Error Message %BINOS_LOGIN-3-NOTTY : login attempted to run without proper credentials.

Explanation login cannot be run without proper credentials.

Recommended Action No action is required.

BIPC Messages

Error Message %BIPC-3-BIPC_PERFORMANCE : buffer size request [int] failed

Explanation 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 Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %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 Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

BOOT Messages

Error Message %BOOT-0-DRV_INITFAIL : [chars] driver failed to initialize properly

Explanation A kernel driver that is critical to the functioning of the system failed to initialize properly.

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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %BOOT-6-APP_START : The process [chars] has started

Explanation 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] RP

Explanation 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.

Error Message %BOOT-3-PARTIAL_CORE_CLEANUP_FAILURE : Partial core clean up failed for [chars]: [chars]

Explanation During RP boot, a failure occurred cleaning up incomplete core files.

Recommended Action Check the router file systems.

Error Message %BOOT-6-PARTIAL_CORE_REMOVED : Removed incomplete core file: [chars]

Explanation On boot of the RP, an incomplete core file was found and removed. Incomplete core files can happen for a variety or reasons, including the coincidental failure of the active RP while a core file is being generated.

Recommended Action No action required. This is not an error, it is an indication that the system is cleaning up a previous error.

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-JOB_NOTFOUND : Job to cancel is not active

Explanation This error occurs if the job diagnostic shell is requested to cancel, is not active.

Recommended Action Check the status of the requested job.

Error Message %BSHELL-6-SMAN_CONNECTION_LOST : [[chars]] Shell Manager connection lost

Explanation 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 failed

Explanation 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 failed

Explanation 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-3-CCE_IPV6_COMPR_CLASSIFY_FAIL : Dataplane IPV6 compression classification error for interface [chars]

Explanation The system experienced an internal software error. The dataplane was unable to complete processing of an IPv6 prefix classification request due to a miss on a TCAM lookup. This is likely due to a data initialization error.

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

Error Message %CCE-3-CCE_NON_TCAM_CLASSIFY : Dataplane classification error for interface [chars]

Explanation The system experienced an internal software error. The dataplane was unable to complete processing of a classification request because an invalid form of classification was selected. This is likely due to a data initialization error.

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

CEF_PROXY Messages

Error Message %CEF_PROXY-3-PROXY_IPC_ADJ_IDX_FAILED : [hex]

Explanation Failed to get adjacency index from IPC packet.

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

Error Message %CEF_PROXY-3-PROXY_IPC_ADJ_ID_HASH_FAILED :

Explanation Getting Hash Address failed.

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

Error Message %CEF_PROXY-3-PROXY_IPC_INIT_FAILED : [dec]

Explanation IPC handler initialization failed.

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

Error Message %CEF_PROXY-3-PROXY_IPC_OCE_CHAIN_PTR_FAILED : [hex]

Explanation Null OCE Chain pointer.

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

Error Message %CEF_PROXY-3-PROXY_IPC_PACKET_ALLOCATION_FAILED : [hex]

Explanation Failed to allocate packet buffer for IPC.

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

Error Message %CEF_PROXY-3-PROXY_IPC_PACKET_SEND_FAILED : [hex]

Explanation Failed to send IPC packet.

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

Error Message %CEF_PROXY-4-PROXY_IPC_INVALID_MSG : [hex]

Explanation Received an invalid IPC messages subtype.

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

CFC_LISP Messages

Error Message %CFC_LISP-3-NO_VIF: Unable to find %svirtual interface %s

Explanation An internal software error occurred.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

CFT Messages

Error Message %CFT-3-HA_INVALID_MSG_LEN_RCVD : invalid [chars] rg [int] [int] expected [int] opcode [chars] [hex]

Explanation Standby received an invalid Firewall HA message

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter. Also perform a search of the Bug Search Tool. If you still require assistance, 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.

Error Message %CFT-3-HA_INVALID_MSG_RCVD : invalid [chars] [hex] opcode [chars] [hex]

Explanation Standby received an invalid Firewall HA message

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter. Also perform a search of the Bug Search Tool. If you still require assistance, 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.

Error Message %CFT-3-HA_INVALID_RG_RCVD : invalid [chars] opcode [chars] [dec] — rg [dec]:[dec]

Explanation Standby received an invalid Redundancy group

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter. Also perform a search of the Bug Search Tool. If you still require assistance, 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.

Error Message %CFT_API-3-CFT_ERRMSG_MAX_MEMORY: %s %s %d

Explanation The maximum number of concurrent flows allowed has been exceeded. Some flows might not received the provisioned level of service.

Recommended Action This is the platform limit. Either lower the network load on this device or upgrade to a higher capacity platform. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CFT_API-3-CFT_ERRMSG_NO_MEMORY: %s %s %d

Explanation The system was unable to supply the requested memory for flow processing to continue.

Recommended Action Check the available memory on your system. Possible solutions include: disable some features; reduce other system activities to ease memory demands; upgrade to a larger memory configuration. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CFT_API-3-CFT_ERRMSG_UNKNOWN: %s %s %d

Explanation The error message type does not match the possible enumerated definitions.

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

Error Message %CFT_API-4-CFT_ERRMSG_CLIENT_PRE_CREATE_PREVENTED: %s %s %d

Explanation Flow creation was prevented by a flow table client. This may be due to an explicit policy that is enabled.

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

Error Message %CFT_API-4-CFT_ERRMSG_FLOW_CREATION_PREVENTED: %s %s %d

Explanation Flow creation was denied by a the system. A possible denial of service attack may have been detected.

Recommended Action Modify your denial of service policy if this is in error. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CFT_API-5-CFT_ERRMSG_NON_FIRST_IP_FRAGMENT: %s %s %d

Explanation The flow table was unable to process a TCP fragmented packet. Service for these packets may be unavailable.

Recommended Action Enable the virtual fragment reassembly (VFR) functionality.If fragmentation is excessive, try to identify the source in your network topology that is causing packet fragmentation. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CFT_API-5-CFT_ERRMSG_UNSUPPORTED_L3_PROTOCOL: %s %s %d

Explanation An unsupported layer 3 protocol was identified.

Recommended Action Flow based inspection does not support this protocol at this time. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CFT_API-7-CFT_ERRMSG_CLIENT_API: %s %s %d

Explanation A CFT client may have a incorrectly accessed an API.

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

CGC Messages

Error Message %CGC-0-CGC_EMERG: %s

Explanation CGC_INTERNAL_ERROR

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CGC-1-CGC_ALERT: %s

Explanation CGC_INTERNAL_ERROR

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CGC-2-CGC_CRIT: %s

Explanation CGC_INTERNAL_ERROR

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CGC-3-CGC_ERR: %s

Explanation CGC_INTERNAL_ERROR

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CGC-4-CGC_WARNING: %s

Explanation CGC_INTERNAL_ERROR

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CGC-5-CGC_NOTICE: %s

Explanation Normal but significant conditions

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CGC-6-CGC_INFO: %s

Explanation Informational messages

Recommended Action No action is required.

Error Message %CGC-7-CGC_ASSERT: Assertion Failure ( %s @%s:%d) : %s

Explanation CGC_INTERNAL_ERROR

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

CGM Messages

Error Message %CGM-3-CGM_FIPS_BYPASS_TEST : NIST bypass test failed for CGM object [chars].

Explanation Class-Group Manager Security Client database detected a discrepancy in a security sensitive object. 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 object or a parent object in question. If the problem persists reboot the forwarding processor (ESP)

CHASFS Messages

Error Message %CHASFS-3-NOCHASFSDIR : The directory [chars] does not exist.

Explanation No explanation.

Recommended Action No action is required.

Error Message %CHASFS-3-NOINOTIFY : The inotify device could not be opened. Error [dec].

Explanation This error occurs when there is an error in the system that prevents the notification facility from being accessed.

Recommended Action No action is required.

Error Message %CHASFS-3-NORESOLVE_LOCAL_OBJECT : Error resolving local FRU object: [chars]

Explanation An application was not able to create a reference to an object in its local chassis file system.

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

Error Message %CHASFS-3-NOOPEN_PROPERTY : Error opening chassis file system object [chars]: [chars]

Explanation An application was not able to open a an object in its local chassis file system.

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

CHUNK Messages

Error Message %CHUNK-3-BAD_CHUNK_MAGIC : head_chunk %

Explanation An invalid memory chunk magic was detected in a memory chunk element.

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

Error Message %CHUNK-3-CHUNK_BAD_REFCNT : refcnt=[dec] data=[hex]

Explanation The memory chunk manager detected a bad reference count.

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

Error Message %CHUNK-3-CHUNK_CORRUPT : chunk %

Explanation Memory corruption was detected by the memory chunk manager.

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

Error Message %CHUNK-3-INVALID_ELEM_SIZE : requested [int]

Explanation An invalid element size request was made of the memory chunk manager.

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

Error Message %CHUNK-3-SIBLING_ERR : Tried to destroy sibling memory chunk [hex]

Explanation An invalid sibling condition was hit in the Memory Chunk Manager.

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

CLOCK_RECOVERY Messages

Error Message %CLOCK_RECOVERY-6-CLOCK_ACTIVE: [chars] on module [dec]/[dec] is now active

Explanation This message indicates that a recovered or enhanced clock has become active.

Recommended Action No action is required.

Error Message %CLOCK_RECOVERY-4-CLOCK_FAILED: [chars] on module [dec]/[dec] failed

Explanation This message indicates that an active recovered or enhanced clock has failed.

Recommended Action No action is required.

CMAN_IDPROM_ENVMON Messages

Error Message %CMAN_IDPROM_ENVMON-3-CMAN_IDPROM_FIELD_INVALID : The idprom contains an invalid environmental monitoring field.

Explanation If this error occurs then parsing of the environmental monitoring data is aborted. Environmental monitoring will be either incomplete or absent entirely.

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

CMANCC Messages

Error Message %CMANCC-2-CRASHDUMP: Fatal error, calling crashdump, error: [dec] [chars]

Explanation A fatal condition has occurred causing IOS to crashdump. IOS will be restarted automatically.

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

Error Message %CMANCC-3-MSGDISPATCH: Unable to dispatch received message from Chassis Manager

Explanation An unexpected condition has occurred while IOS was trying to dispatch a message received from the Chassis Manager.

Recommended Action Verify that all local components are in the proper operational state. If any inconsistency is found, it may be corrected by off line and restart of the effected component (SPA, Carrier Card).

Error Message %CMANCC-3-MSGIPCERR: Unable to process received IPC messages from Chassis Manager, error: [chars]

Explanation An unexpected condition has occurred while IOS trying to process a received IPC message from Chassis Manager.

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

Error Message %CMANCC-3-UNEXPECTEDEVENT: UDI Auth Process received unknown event (maj %x, min %x).

Explanation UDI authorization process has registered to be notified when a process boolean change event occurs in the router. This message indicates that this process received an event it did not know how to handle.

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

CMANRP Messages

Error Message %CMANRP-2-CRASHDUMP: Fatal error, calling crashdump, error: [dec] [chars]

Explanation A fatal condition has occurred causing IOS to crashdump.

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

Error Message %CMANRP-3-CMSWVERINFO: Unable to process software version information using file %s. Reason: %s. Error: %d

Explanation An unexpected condition has occurred while IOS was trying to process the software version information file. As a result, version information may not be available to an SNMP Manager

Recommended Action No action is required.

Error Message %CMANRP-3-INVERR: Unable to process chassis inventory for file [chars], slot [dec], [chars], error [dec]. Some SPA’s may not be fully configured

Explanation An unexpected condition has occurred while IOS is trying to process the chassis inventory on startup. IOS cannot determine the type and number of all Carrier Cards and SPA’s present in the system. Some configuration relating to these SPA’s may not be applied and leave the system in an inconsistent state.

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

Error Message %CMANRP-3-INVERRSPA: Unable to process chassis inventory for file [chars], SPA subslot [dec]/[dec], [chars], error [dec]. Some SPA’s may not be fully configured

Explanation An unexpected condition has occurred while IOS is trying to process the chassis inventory on startup. IOS cannot determine the type and number of all Carrier Cards and SPA’s present in the system. Some configuration relating to these SPA’s may not be applied and leave the system in an inconsistent state.

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

Error Message %CMANRP-3-MSGDISPATCH: Unable to dispatch received TDL messages from Chassis Manager

Explanation An unexpected condition has occurred while IOS is trying to dispatch to the TDL message handler functions for received TDL messages from Chassis Manager.

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

Error Message %CMANRP-3-MSGDISPATCHNULL: Received NULL TDL message from IOS

Explanation An unexpected condition in which IOS has received a NULL TDL message from Chassis Manager.

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

Error Message %CMANRP-3-MSGIPCERR: Unable to process received IPC messages from Chassis Manager, error: [chars]

Explanation An unexpected condition has occurred while IOS is trying to process a received IPC message from Chassis Manager.

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

Error Message %CMANRP-6-CMHASTATUS: RP switchover, [chars]

Explanation RP switchover events received by chassis manager.

Recommended Action No action is required.

Error Message %CMANRP-6-CMSTATUS: Chassis Manager Process is [chars]

Explanation The current status of Chassis Manager Process.

Recommended Action No action is required.

Error Message %CMANRP-3-UDEVPERMS: An invalid permissions value, %s, was found in a udev file

Explanation The udev files for a particular filesystem contain a description the file system. If the permissions attribute is not recognized then this file system may run with incorrect permissions.

Recommended Action No action is required.

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 Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %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 Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %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 Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %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 Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %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 Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %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 Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %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 Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CMCC-0-HTDP_ENABLE : The HTDP initialization has failed because [chars]

Explanation The Hypertransort datapath failed to initialize. This error could be caused by a hardware defect or HTDP driver defect.

Recommended Action Examine the logs for HTDP 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 Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CMCC-0-CPLD_INTR_ENABLE : The CPLD initialization has failed because [chars]

Explanation The CPLD interrupt enable failed to initialize. This error could be caused by a hardware defect or CPLD driver defect.

Recommended Action Examine the logs for CPLD 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 Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %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 Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CMCC-0-PLIM_HALT : A PLIM driver has critical error [chars], [dec], param [hex] param [hex]

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 block[hex] param count[hex]

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-3-NETWORK_CLOCK_CAL_FAIL : The SIP network clock jitter attenuator calibration fails

Explanation The SIP network clock jitter attenuator calibration cannot complete within certain time. This would incur some SPA LOS alarms or other error events for some SPA port types.

Recommended Action Restart the SIP

Error Message %CMCC-3-NETWORK_CLOCK_CAL_START : The SIP network clock jitter attenuator is calibrating

Explanation The SIP network clock jitter attenuator is calibrating after device unitization stage.

Recommended Action Calibration is required during startup and whenever a new reference clock is selected by the WAN PLL device. Restart the SIP if SPA LOS alarms are seen after this.

Error Message %CMCC-3-NETWORK_CLOCK_DH : The SIP network clock jitter attenuator has entered digital holdover

Explanation A SIP network clock jitter attenuator has entered digital holdover mode and certain SPAs may report LOS alarms.

Recommended Action Examine network clock configuration and ensure all network clock sources are operating correctly. Restart the SIP.

Error Message %CMCC-3-NETWORK_CLOCK_LOS : The SIP network clock jitter attenuator has lost signal

Explanation A SIP network clock jitter attenuator has lost signal from the WAN PLL and certain SPAs may report LOS alarms.

Recommended Action Examine network clock configuration and ensure all network clock sources are operating correctly. Restart the SIP.

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 Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %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 Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %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 Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %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 Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %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 Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %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 Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %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 Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %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 Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %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 Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %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.

Error Message %CMCC-3-SPA_HOTSWAP_CKT_FAIL : SPA on bay [int] has tripped the Hot Swap Circuit during power-up.

Explanation The Hot Swap Circuit for the SPA bay has been tripped. This error could be caused by bad SPA hardware.

Recommended Action Examine the CMCC and PSM OIR logs. Verify whether the recovery reload could bring up the SPA.

Error Message %CMCC-5-SERDES_BLOCK_EVENT : A SerDes link informational error [chars], block [hex] count [hex]

Explanation A serial bridge I/O event has occurred. This event is not serious but is logged for diagnostic purposes.

Recommended Action No user action is required.

CMFP Messages

Error Message %CMRP—1-ACTIVE_SLOTBAY_BIAS : The configured active slot/bay bias [dec] 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—1-CRYPTOGRAPHIC_HW_MISMATCH : ESP[dec] does not support strong cryptography. Chassis will reload.

Explanation IOS software featuring strong cryptography is invalid for use with any non-strong-cryptography Embedded Service Processor. The router node will reload if this combination is encountered.

Recommended Action Install a non-strong-cryptography image of the RP IOS package or replace the indicated Embedded Service Processor with one that supports strong-cryptography

Error Message %CMRP—1-FRU_CPLD_INCOMPATIBLE : [chars] in slot [chars] has been held in reset as its CPLD firmware version is incompatible with [chars]

Explanation This FRU requires a newer CPLD firmware to function properly in this chassis

Recommended Action Upgrade the CPLD firmware on this FRU using the <b> upgrade hw-programmable CPLD file <pkg_file> slot <fru_slot> </b> command. For more information, see http://www.cisco.com/en/US/docs/routers /asr1000/cpld/hw_fp_upgrade.html.

Error Message %CMRP—1-FRU_HWPRG_UPG_FAILED : Failed to [chars] [chars] hardware programmable on [chars] in [chars].

Explanation Upgrade hw-programmable failed to upgrade the CPLD/FPGA firmware on the given FRU

Recommended Action Reload the card and retry to program the hw-programmable. If the card fails to come up contact your Cisco technical support representative.

Error Message %CMRP—1-RP_CPLD_INCOMPATIBLE : All other cards in the system has been held in reset as the Active RP [chars] in slot [chars] has CPLD firmware version that is incompatible with [chars]

Explanation Active RP requires a newer CPLD firmware to function properly in this chassis

Recommended Action Upgrade the CPLD firmware on this FRU using the <b> upgrade hw-programmable CPLD file <pkg_file> slot <fru_slot> </b> command. For more information, see http://www.cisco.com/en/US/docs/routers /asr1000/cpld/hw_fp_upgrade.html for more details.

Error Message %CMFP-3-DDR_SINGLE_BIT_ERROR : Single-bit DRAM ECC error: mme: [int], sbe: [int], address: 0x%08X, 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 message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %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 Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %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 [dec] 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-N2_FATAL_ERROR : An error has been detected on encryption processor: type [chars]

Explanation An error has been detected on encryption processor.

Recommended Action Check the chassis-manager logs for errors.

Error Message %CMFP-3-CPLD_ECSR_ERROR : An error has been detected on the ECSR bus

Explanation An error has been detected on the ECSR bus. This may cause problems when accessing the forwarding processor.

Recommended Action Some of these errors are catastrophic and others are not. If the FRU did not restart assume corrective action was taken. Check the chassis-manager logs for errors.

Error Message %CMFP-3-CPLD_ERP_ERROR : An error has been detected on the ERP bus (cause [dec], phase [dec])

Explanation An error has been detected on the ERP bus. This may cause problems when accessing the forwarding processor.

Recommended Action Some of these errors are catastrophic and others are not. If the FRU did not restart assume corrective action was taken. 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 [dec]

Explanation The encryption processor has detected an un correctable multi-bit in memory. This could be due to a hardware defect.

Recommended Action Examine the logs for encryption processor hardware errors.

Error Message %CMFP-0-N2_DRV_ERROR : Crypto device driver has detected a critical error. [chars]: [chars]

Explanation A crypto device 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 ESP

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-CPLD_INITIALIZATION : The RP CPLD has failed initialization because [chars]

Explanation The release of the software cannot support this chassis. It is likely the software release is old.

Recommended Action Collect the error log and the software version. Contact your Cisco technical support representative for instructions on obtaining the correct version of IOS-XE to run on this hardware.

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-3-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: 0x%08X, 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-3-DUAL_IOS_STANDBY_BAY : Standby bay cannot be launched due to failure in bringing down existing processes (Attempts: [dec])

Explanation During standby bay shutdown, some related processes still remain running for an unexpectedly prolonged period of time. Chassis-manager has timed-out waiting for all related processes to shutdown. As a result, it is unable to notify Process-manager to restart the bay

Recommended Action Examine the logs for standby bay’s Forwarding-manager (fman), Interface-manager (iman), Pluggable-Service-Daemon (psd) and IOS. Ascertain which of these processes is taking too long to shutdown and note the reason. Take corrective action based on the error noted in the log

Error Message %CMRP-3-FP_DOWNREV : [chars] has been held in reset because it is down-rev to the previous FP ([hex] -> [hex]) in the chassis. Reboot the router to bring it up.

Explanation The FP inserted is a lower version than the previous Active FP in the router. Downrev of FP is not supported.

Recommended Action Reboot the router.

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-3-HWPRG_UPG_UNSUPP_SLOT : upgrade of hardware programmables on [chars] is not supported while in slot [chars]. Card will now be powered down.

Explanation upgrade of hw-programmable CPLD/FPGA not supported in the given slot. Move the card to a different slot and perform the upgrade

Recommended Action Move the card to a different slot and perform the upgrade

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_INIT_FAIL : Serial Bridge ESI link [chars] between [chars] and [chars] failed to config

Explanation A Serial Bridge ESI link did not configure. This could be due to a software 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-SERDES_ESI_LOCK_FAIL : The Serial Bridge ESI link between [chars] and [chars] failed to lock

Explanation 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[dec] hypertransport configured for F[dec] active

Explanation 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-3-INCOMPATIBLE_FRU : [chars] in slot [chars] is not compatible with [chars] and so it is disabled

Explanation The Product ID read from the FRU IDPROM is invalid for this hardware configuration.

Recommended Action Remove the FRU from the chassis. Review the Hardware and Software Compatibility Matrix in IOS XE release notes to determine currently supported configurations.

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_UNSUPPORTED : This software does not support the [chars] chassis type.

Explanation The chassis type is not supported by the software version.

Recommended Action Install a version of the software that supports the chassis type.

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 [dec] 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 type

Explanation 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 [dec]

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 [dec], [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 [dec], [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 [dec], [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 [dec] minutes

Explanation 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[dec] 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[dec] [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_HWPRG_UPG_SUCCESS : Hardware programmable [chars] on [chars] in slot [chars] was successfully programed. Card will now be powercycled.

Explanation The hw-programmable CPLD/FPGA was upgraded successfully

Recommended Action No action is required. This is informational message

Error Message %CMRP-3-FRU_HWPRG_UPG_UNSUPP : Upgrade of hardware programmable [chars] on [chars] in slot [chars] is not supported. Card will now be powered down.

Explanation upgrade of hw-programmable CPLD/FPGA not supported.

Recommended Action No action is required. This is informational message

Error Message %CMRP-3-FRU_INVPARTNUM : [chars] has been held in reset because the part number %08X is invalid.

Explanation The FRU IDPROM contains an invalid part number.

Recommended Action The FRU IDPROM should be repaired or the board replaced.

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-UNSUPPORTED_FRU : [chars] in slot [chars] is not supported with [chars] and so it is disabled

Explanation The Product ID read from the FRU IDPROM is not supported in this router. This is due to either chassis or RP limitation indicated in the console log

Recommended Action Remove the FRU from the chassis. Review the Hardware and Software Compatibility Matrix in IOS XE release notes to determine currently supported configurations.

Error Message %CMRP-3-UNSUPPORTED_PEM : [chars] in slot [chars] is not supported with [chars] and it needs to be replaced immediately

Explanation The Product ID read from the PEM IDPROM is not supported in this hardware configuration. It will be allowed to continue but immediate replacement is required

Recommended Action Remove the PEM from the chassis and replace it with a supported PEM. Review the Hardware and Software Compatibility Matrix in IOS XE release notes to determine currently supported configurations.

Error Message %CMRP-3-WANPLL_SETUP : Failed to setup the [chars] of the RP WAN PLL because [chars]

Explanation Failed to setup the RP WAN PLL appropriately. This could be due to a hardware defect of the device.

Recommended Action Note the time of the error message and examine the logs for WAN PLL related hardware errors. Check if the issue is transient or repeatable. If the problem is not recoverable collect the output of the error message and the chassis- manager and IOS logs. Provide the gathered information to a Cisco technical support representative.

Error Message %CMRP-3-RP_MISMATCH : [chars] has been held in reset because the part number differs from that of the active RP

Explanation The part number read from the FRU IDPROM is not compatible with part number of the active RP; therefore, it may not act as a standby.

Recommended Action Remove the FRU from the chassis.

Error Message %CMRP-3-FP_LESSTHAN : [chars] has been held in reset because it is down-rev to the active and cannot act as a standby.

Explanation The part number read from the FP IDPROM is not compatible with part number of the active FP; therefore, it may not act as a standby.

Recommended Action Remove the FP 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 syspage 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 for slot [chars] 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 IOS

Explanation 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 effect

Explanation 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 execution

Explanation 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 unknown

Explanation 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 continuously reloaded.

Error Message %CMRP-3-CHASSIS_MONITOR_FRU_BOOT_RETRIES_EXCEEDED : [chars] has been held in reset because it has failed to successfully boot in [dec] tries

Explanation The FRU has failed to successfully boot in the maximum allowable attempts and is held in reset.

Recommended Action Remove the FRU from the chassis if the FRU continuously fails to boot.

Error Message %CMRP-3-CHASSIS_MONITOR_ONLINE_TIME_EXCEEDED : Reloading [chars] because it has failed to come online

Explanation A FRU has failed to come online within the maximum boot time.

Recommended Action Remove the FRU from the chassis is the FRU is continuously reloaded.

Error Message %CMRP-3-CHASSIS_MONITOR_READY_TIME_EXCEEDED : Reloading [chars] because it has failed to become ready for packet processing

Explanation 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 continuously reloaded.

Error Message %CMRP-3-CHASSIS_MONITOR_ONLINE_TIME_IGNORED : [chars] exceeded online time but will not be reset because fault ignore is configured

Explanation 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 configured

Explanation 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.

Error Message %CMRP-3-CHASSIS_FRU_FAULT_IGNORED_ISSET : CMAN_IGNORE_FRU_FAULTS is set. Some FRU faults will be ignored and FRU may not restart due to a fault

Explanation Debug variable will prevent a FRU from being restarted due to some faults.

Recommended Action No action is necessary.

Error Message %CMRP-3-CHASSIS_FRU_FAULT_IGNORED : CMAN_IGNORE_FRU_FAULTS is set. [chars]: [chars]

Explanation Debug variable will prevent a FRU from being restarted due to some faults.

Recommended Action No action is necessary.

Error Message %CMRP-6-TEST_SPA_OIR_ONLINE_OPS : SPA [dec]/[dec] oir online status is set to [chars]

Explanation Test command executed to either allow/deny the SPA coming online.

Recommended Action If the card does not come online, execute the test command to allow the SPA to come online.

Error Message %CMRP-6-TEST_SPA_OIR_ONLINE_INSERT_DENIED : SPA [dec]/[dec] oir insert is denied

Explanation Test command executed disallowing the SPA to be inserted.

Recommended Action Execute the test command allowing the insertion of the SPA for normal operation.

Error Message %CMRP-6-CRYPTOGRAPHIC_HW_MISMATCH : ESP[dec] does not support strong cryptography. Chassis will reload.

Explanation IOS software featuring strong cryptography is invalid for use with any non-strong-cryptography Embedded Service Processor. The router node will reload if this combination is encountered.

Recommended Action Install a non-strong-cryptography image of the RP IOS package or replace the indicated Embedded Service Processor with one that supports strong-cryptography

Error Message %CMRP-3-INVENTORY_INITIALIZATION : [chars] inventory file could not be read. FRU may need a reload to initialize properly, [chars]

Explanation The FRU inventory file could not be read. The file can possibly be corrupt. The FRU will possibly not initialize properly. The FRU should reset automatically. If it does not, it should be reloaded manually. If the error persists, the FRU will need to be replaced.

Recommended Action Wait a few minutes. If FRU does not reset automatically, it should be manually reloaded. If error persists, the FRU needs to be replaced.

Error Message %CMRP-5-PRERELEASE_HARDWARE : [chars] is pre-release hardware

Explanation The board does have an official production part number.

Recommended Action Immediately contact Cisco for a replacement board.

CMRP_ENVMON Messages

Error Message %CMRP_ENVMON-3-TEMP_FRU_SHUTDOWN_PENDING : WARNING: [chars] temperature sensor on [chars] is in a shutdown FRU state. FRU shutdown will occur in [dec] minutes.

Explanation The FRU is overheating and will be shut down in order to protect the components.

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

Error Message %CMRP_ENVMON-3-TEMP_SYS_SHUTDOWN_PENDING : WARNING: [chars] temperature sensor on [chars] is in a shutdown FRU state. System shutdown will occur in [dec] minutes.

Explanation The FRU is overheating and will be shut down in order to protect the components.

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

Error Message %CMRP_ENVMON-3-TEMP_FRU_SHUTDOWN_NOW : WARNING: [chars] temperature sensor on [chars] is in a shutdown FRU state. FRU shutdown now.

Explanation The FRU is overheating and will be shut down in order to protect the components.

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

Error Message %CMRP_ENVMON-3-TEMP_SYS_SHUTDOWN_NOW : WARNING: [chars] temperature sensor on [chars] is in a shutdown FRU state. System shutdown now.

Explanation The FRU is overheating and will be shut down in order to protect the components.

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

Error Message %CMRP_ENVMON-3-TEMP_WARN_CRITICAL : WARNING: [chars] temperature sensor on [chars] is in a critical state reading [dec]

Explanation The FRU is overheating and will be shut down in order to protect the components.

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

CMRP_PFU Messages

Error Message %CMRP_PFU-6-PFU_INSERTED : [chars] inserted. System shutdown aborted.

Explanation When either a PEM or a FM are removed, the system lacks sufficient cooling capacity. To prevent damage, the system will automatically shut down unless it is replaced.This message serves as notice that the module has been replaced within the required time.

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

Error Message %CMRP_PFU-3-PFU_SHUTDOWN : Shutting down system now because the PEM in slot [dec] was removed and not replaced.

Explanation When either a PEM or a FM are removed, the system lacks sufficient cooling capacity. To prevent damage, the system will automatically shut down unless it is replaced.

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

Error Message %CMRP_PFU-3-PFU_SLOT_VACANT : The platform does not detect a power supply in slot [dec]

Explanation There is no power supply in one of the power supply slots.

Recommended Action Insert a power supply into the empty slot.

Error Message %CMRP_PFU-3-PFU_FANS_DEAD_SHUTDOWN : Shutting down system now because the fans in slot [dec] have all failed.

Explanation When the fans fail then system does not have sufficient cooling capacity. To prevent damage, the system will automatically shut down.

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

Error Message %CMRP_PFU-3-TEMP_FRU_SHUTDOWN : [chars] temperature sensor on [chars] is in a shutdown FRU state. FRU shutdown will occur in [dec] minutes.

Explanation The FRU is overheating and will be shut down in order to protect the components.

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

Error Message %CMRP_PFU-3-TEMP_SYSTEM_SHUTDOWN : [chars] temperature sensor is in a shutdown system state. System shutdown will occur in [dec] minutes.

Explanation The system is overheating and will be shut down in order to protect the components.

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

Error Message %CMRP_PFU-3-PFU_FANS_DEAD : The fans in the [chars] in slot [dec] have all failed.

Explanation The system is in danger of overheating because none of the fans in one of the PEMs are working properly.

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

Error Message %CMRP_PFU-3-PFU_FAN_DEAD : WARNING: Fan [dec] in the [chars] in slot [dec] has failed.

Explanation A fan is not functioning properly.

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

Error Message %CMRP_PFU-3-PFU_IDPROM_READ_ERR : Could not read the PEM/FM idprom in slot P[dec]. The system will run without environmental monitoring for this component

Explanation The idprom contains information required in order to properly operate the environmental monitoring subsystems. The idprom could not be read, therefore no monitoring will take place.

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

Error Message %CMRP_PFU-3-PFU_IDPROM_CORRUPT : The PEM/FM idprom could be read, but is corrupt in slot P[dec] The system will run without environmental monitoring for this component

Explanation The idprom contains information required in order to properly operate the environmental monitoring subsystems. The idprom could not be read, therefore no monitoring will take place.

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

Error Message %CMRP_PFU-3-SHUTDOWN_FAILURE : The system attempted to shut itself down, but failed because [chars]

Explanation The system reached a condition where it should be shut down, but the shutdown call failed. The system should be manually rebooted.

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

Error Message %CMRP_PFU-3-PFU_ZONE_SHUTDOWN : Shutting down system now because PEMs in slot [dec] and [dec] in the same zone failed.

Explanation When both PEMs in a single zone fail, that part of the router will be power down but not the other half. Hence the system is forcibly shutdown.

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

CPPBQS Messages

Error Message %CPPBQS-3-QMOVEFAIL : CPP [dec] schedule [chars] queue move failed (%#x) — SEID=%#x SID=%#X

Explanation A CPP BQS schedule queue move operation failed.

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

Error Message %CPPBQS-3-QMOVESTUCK : QFP [dec] schedule [chars] queue move operation is not progressing as expected — seq [int]

Explanation A QFP schedule queue move operation is not proceeding as expected and can lead to packet drops. The most likely cause of a queue move operation getting stuck is having a rate based queue that has packets enqueued on it that are not being serviced very frequently or being starved due to higher priority queues causing an oversubscription of the physical output interface.

Recommended Action No action is required if QMOVEDONE message is also displayed following QMOVESTUCK. If a QMOVEDONE or QMOVEPROC message is not displayed following QMOVESTUCK, then collect the data from the following show commands: show platform, show platform hardware qfp < active | standby > bqs status, show platform hardware qfp < active | standby > bqs qmove info, show platform hardware qfp < active | standby > bqs qmove child, show platform hardware qfp < active | standby > bqs qmove flush. Open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show platform, show platform hardware qfp < active | standby > bqs status, show platform hardware qfp < active | standby > bqs qmove info, show platform hardware qfp < active | standby > bqs qmove child, and show platform hardware qfp < active | standby > bqs qmove flush commands and your pertinent troubleshooting logs.

Error Message %CPPBQS-3-REPARENTFAIL : CPP [dec] schedule [chars] reparent failed (%#x) — SEID=%#X SID=%#x

Explanation A CPP BQS schedule reparent operation failed.

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

Error Message %CPPBQS-4-QLIMITEXCEEDED : CPP [dec] QoS Queue limit [int] exceeded at [int].

Explanation Max number of QoS queues supported on CPP has been exceeded. Configuration failure is possible, causing unpredictable results.

Recommended Action Reduce the size of the QoS configuration.

Error Message %CPPBQS-4-QMOVEDONE : CPP [dec] schedule [chars] queue move done

Explanation A CPP BQS schedule queue move operation was not proceeding in a timely manner and flagged as being stuck, but has since completed.

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

Error Message %CPPBQS-4-QMOVEPROC : QFP [dec] schedule [chars] queue move in progress seq [int]

Explanation A QFP BQS schedule queue move operation is not proceeding or is proceeding at a slow rate which can lead to packet drops. The most likely cause of a queue move operation getting stuck is having a rate based queue that has packets enqueued on it that are not being serviced very frequently or being starved due to higher priority queues causing an oversubscription of the physical output interface.

Recommended Action No action is required if QMOVEDONE message is also displayed following QMOVEPROC. If QMOVEDONE message is not displayed or you continue to see QMOVEPROC messages displayed, then collect the data from the following show commands: show platform show platform hardware qfp < active | standby > bqs status, show platform hardware qfp < active | standby > bqs qmove info, show platform hardware qfp < active | standby > bqs qmove child, show platform hardware qfp < active | standby > bqs qmove flush. Open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging, show tech-support, show platform show platform hardware qfp < active | standby > bqs status, show platform hardware qfp < active | standby > bqs qmove info, show platform hardware qfp < active | standby > bqs qmove child, and show platform hardware qfp < active | standby > bqs qmove flush commands and your pertinent troubleshooting logs.

Error Message %CPPBQS-4-QMOVESTUCK : CPP [dec] schedule [chars] queue move stuck

Explanation A CPP BQS schedule queue move operation is not proceeding or is proceeding at a slow rate which can lead to packet drops. The most likely cause of a queue move operation getting stuck is having a rate based queue that has packets enqueued on it that is not being serviced very frequently or being starved due to higher priority queues causing an oversubscription of the physical output interface.

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

Error Message %CPPBQS-4-SRTMEMLOW : CPP [dec] HW [chars]:[chars] schedule resources depleted — [dec]%% available

Explanation CPP BQS HW schedule 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.

Error Message %CPPBQS-6-QLIMITOK : CPP [dec] QoS Queue limit [int] was exceeded and is now within platform specifications at [int].

Explanation Max number of QoS queues supported on CPP was exceeded. It is now within platform specifications.

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

CPPDRV Messages

Error Message %CPPDRV-2-HALT : [chars]([dec]) Interrupt : [chars] Seq:%03d Halt bit set.

Explanation A Serious CPP hardware error has occurred.

Recommended Action No action is required.

Error Message %CPPDRV-3-ALLOC_NOTF : CPP[dec]: Failed to Allocate: ([chars])

Explanation A function failed to allocate data.

Recommended Action No action is required.

Error Message %CPPDRV-3-CLEANUP_NOTF : Failed to Cleanup: ([chars])

Explanation A function failed to cleanup data.

Recommended Action No action is required.

Error Message %CPPDRV-3-DESTROY_NOTF : Failed to destroy connection :([chars])

Explanation A function failed to destroy a connection.

Recommended Action No action is required.

Error Message %CPPDRV-3-FATAL_ACQUIRE_LOCK : CPP[dec]: ([hex]) Failed to acquire memory lock [chars]

Explanation SW failed to acquire shared memory lock.

Recommended Action No action is required.

Error Message %CPPDRV-3-FATAL_ALLOCATE : CPP[dec]: ([hex]) Failed to allocate [chars] — [chars]

Explanation Failed to allocate data.

Recommended Action No action is required.

Error Message %CPPDRV-3-FATAL_ATTACH : CPP[dec]: ([hex]) FAILED: to attach [chars]

Explanation Device Failed to attach.

Recommended Action No action is required.

Error Message %CPPDRV-3-FATAL_CPP_SUBDEV_ACCESS : CPP[dec].[dec]: An access error has been reported. Error count [int].
Error Message The system has reported an error while accessing a CPP subdevice
Error Message No action is required.
Error Message %CPPDRV-3-FATAL_CREATE : ([hex]) Failed to create [chars] — [chars]

Explanation Failed to create device.

Recommended Action No action is required.

Error Message %CPPDRV-3-FATAL_CREATE_ID : CPP[dec]: ([hex]) Failed to create [chars] — [chars]

Explanation Failed to create device.

Recommended Action No action is required.

Error Message %CPPDRV-3-FATAL_GET_DETAILS : CPP[dec]: ([hex]) Failed to get [chars] details — [chars]

Explanation Failed to get device details.

Recommended Action No action is required.

Error Message %CPPDRV-3-FATAL_INIT : ([hex]) Failed to initialize [chars] — [chars]

Explanation Failed to initialize device.

Recommended Action No action is required.

Error Message %CPPDRV-3-FATAL_INIT_ID : CPP[dec]: ([hex]) Failed to initialize [chars] — [chars]

Explanation Failed to initialize device.

Recommended Action No action is required.

Error Message %CPPDRV-3-FATAL_INTERNAL : CPP[dec]: ([hex]) Internal Error [chars]

Explanation Internal coding error.

Recommended Action No action is required.

Error Message %CPPDRV-3-FATAL_INTERRUPT_CLEAR : CPP[dec]: ([hex]) Failed to clear [chars] interrupt

Explanation Failed to clear an interrupt node.

Recommended Action No action is required.

Error Message %CPPDRV-3-FATAL_INTERRUPT_HANDLER : CPP[dec]: ([hex]) Failed to register [chars] interrupt handler — [chars]

Explanation Failed to register interrupt handler.

Recommended Action No action is required.

Error Message %CPPDRV-3-FATAL_INTERRUPT_INIT : CPP[dec]: ([hex]) Failed to initialize [chars] interrupt — [chars]

Explanation Failed to initialize an interrupt.

Recommended Action No action is required.

Error Message %CPPDRV-3-FATAL_INTERRUPT_OPEN : CPP[dec]: ([hex]) Failed to access [chars] interrupt node — [chars]

Explanation Failed to open an interrupt.

Recommended Action No action is required.

Error Message %CPPDRV-3-FATAL_MEM_CLEAR : CPP[dec]: ([hex]) Failed to clear memory [chars]

Explanation SW failed to clear memory location.

Recommended Action No action is required.

Error Message %CPPDRV-3-FATAL_MEM_SIZE : CPP[dec]: ([hex]) Failed to acquire memory size [chars]

Explanation SW failed to acquire the size of a block of memory.

Recommended Action No action is required.

Error Message %CPPDRV-3-FATAL_MEM_WRITE : CPP[dec]: ([hex]) Failed to write to memory [chars]

Explanation SW failed to write to a memory location.

Recommended Action No action is required.

Error Message %CPPDRV-3-FATAL_PLAT_DB : CPP[dec]: ([hex]) Platform failure accessing [chars]

Explanation Platform DB query failed.

Recommended Action No action is required.

Error Message %CPPDRV-3-FATAL_RELEASE_LOCK : CPP[dec]: ([hex]) Failed to release memory lock [chars]

Explanation SW failed to release shared memory lock.

Recommended Action No action is required.

Error Message %CPPDRV-3-FATAL_UNSUPPORT : CPP[dec]: ([hex]) — unsupported CPP TYPE. CPP TYPE:[dec]

Explanation Unsupported CPP type.

Recommended Action No action is required.

Error Message %CPPDRV-3-HOT : [chars]([dec]) Interrupt : [chars] Seq:%03d repeating interrupt has been disabled.

Explanation A repeating hardware interrupt has been disabled.

Recommended Action No action is required.

Error Message %CPPDRV-3-INIT_NOTF : Failed to initialize: ([chars])

Explanation A function failed to initialize.

Recommended Action No action is required.

Error Message %CPPDRV-3-INIT_NOTF_ID : CPP[dec]: Failed to initialize: ([chars])

Explanation A function failed to initialize.

Recommended Action No action is required.

Error Message %CPPDRV-3-LOCKDOWN : [chars]([dec]) CPP Driver LOCKDOWN due to fatal error.

Explanation A fatal error has caused the driver to LOCKDOWN.

Recommended Action No action is required.

Error Message %CPPDRV-3-TCAM_PERR : [chars]([dec]) TCAM Parity error TCAM device #[dec] at offset 0x%08X.

Explanation A Parity error has occurred in a TCAM device.

Recommended Action No action is required.

Error Message %CPPDRV-3-TCAM_PERR_FAILURE : [chars]([dec]) Failed to correct TCAM Parity error. Parity error detection disabled.

Explanation Failed to correct a TCAM Parity error and further detection has been disabled.

Recommended Action No action is required.

Error Message %CPPDRV-4-ADRSPC_LIMIT : Address space limit [int] KB reached, mapping block [chars] size [int] dynamically, over limit space: [int] KB

Explanation The process indicated tried to map more of the Forwarding Engine’s address space than was allocated for it. A slower access method will be used instead. This will lower the performance of some operations which require accesses to the Forwarding Engine.

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

Error Message %CPPDRV-4-CORE_TABLE : CPP[dec] specific core dump table ‘[chars]’ not found, using minimal fallback table ‘[chars]’ instead

Explanation The QFP configuration found on this board did not match any of the tables which define which data has to be collected if a fatal error is detected. Instead a minimal table is used which covers most of the QFP registers. The QFP is fully operational.)msgdef_recommended_action

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

Error Message %CPPDRV-6-ACCTRC16B : Access CPP [dec] address 0x%08llX (Blk/Off:[dec]/0x%08llX) [chars] %3d bytes 0x%016llX_%016llX flags 0x%02X

Explanation A CPP access was traced.

Recommended Action No action is required.

Error Message %CPPDRV-6-ACCTRC8B : Access CPP [dec] address 0x%08llX (Blk/Off:[dec]/0x%08llX) [chars] %3d bytes 0x%016llX flags 0x%02X

Explanation A CPP access was traced.

Recommended Action No action is required.

Error Message %CPPDRV-6-INTR : [chars]([dec]) Interrupt : [chars]

Explanation A CPP hardware interrupt has occurred.

Recommended Action No action is required.

CPPEXMEM Messages

Error Message %CPPEXMEM-3-NOMEM : CPP [dec] [chars] memory allocation ([chars]) failed

Explanation An allocation for a CPP memory resource has failed due to running out of memory.

Recommended Action No action is required.

Error Message %CPPEXMEM-3-NOMEM : CPP [dec] [chars] memory allocation ([chars]) failed

Explanation An allocation for a CPP memory resource has failed due to running out of memory.

Recommended Action No action is required.

Error Message %CPPEXMEM-4-LOWMEM : CPP [dec] [chars] memory low — [dec] percent depleted

Explanation A CPP memory resource has dropped below a critical level.

Recommended Action No action is required.

Error Message %CPPEXMEM-4-LOWMEM : CPP [dec] [chars] memory low — [dec] percent depleted

Explanation A CPP memory resource has dropped below a critical level.

Recommended Action No action is required.

Error Message %CPPEXMEM-5-MEM : CPP [dec] [chars] memory recovered — [dec] percent depleted

Explanation A CPP memory resource has recovered above the low threshold level.

Recommended Action No action is required.

Error Message %CPPEXMEM-5-MEM : CPP [dec] [chars] memory recovered — [dec] percent depleted

Explanation A CPP memory resource has recovered above the low threshold level.

Recommended Action No action is required.

CPPFPM Messages

Error Message %CPPFPM-6-FMANACLLOGMISSMSG : access-list logging datapath rate-limited or missed [int] packet[chars]

Explanation Some 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-6-IPACCESSLOGDP : list [chars] [chars] [chars] [chars] [chars]-> [chars] ([int]/[int]), [int] packet[chars]

Explanation A packet matching the log criteria for the given access list was detected.

Recommended Action No action is required.

Error Message %CPPFPM-6-IPACCESSLOGNP : list [chars] [chars] [int] [chars] [chars]-> [chars], [int] packet[chars]

Explanation A packet matching the log criteria for the given access list was detected.

Recommended Action No action is required.

Error Message %CPPFPM-6-IPACCESSLOGP : list [chars] [chars] [chars] [chars]([int]) [chars]-> [chars]([int]), [int] packet[chars]

Explanation A packet matching the log criteria for the given access list was detected.

Recommended Action No action is required.

CPPHA Messages

Error Message %CPPHA-3-BULKSYNC : bulk sync processing failed to complete

Explanation The CPP bulk synchronization processing failed on the standby.

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

Error Message %CPPHA-3-CDMDONE : CPP [dec] microcode crashdump creation completed.

Explanation The CDM has completed generating microcode crashdump.

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

Error Message %CPPHA-3-FAILURE : CPP [dec] failure [chars] detected

Explanation A CPP failure has been detected.

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

Error Message %CPPHA-3-FAULT : CPP:[dec] desc:[chars] det:[chars] class:[chars] sev:[chars] id:[dec] cppstate:[chars] res:[chars] flags:[hex] cdmflags:[hex]

Explanation A CPP fault has occurred.

Recommended Action No action is required.

Error Message %CPPHA-3-FAULTCRASH : CPP [dec] unresolved fault detected, initiating crash dump.

Explanation A unresolved fault detected, initiating crash dump.

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

Error Message %CPPHA-3-FAULTRATE : CPP:[dec] desc:[chars] det:[chars] class:[chars] sev:[chars] id:[dec] cppstate:[chars] res:[chars] flags:[hex] cdmflags:[hex]

Explanation A CPP fault has occurred.

Recommended Action No action is required.

Error Message %CPPHA-3-INITFAIL : CPP [dec] initialization failed — [chars] (%#x)

Explanation A CPP initialization failed.

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

Error Message %CPPHA-3-NOCDM : CPP [dec] CDM not running.

Explanation The CDM process is not running.

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

Error Message %CPPHA-6-SYSINIT : CPP HA system [chars].

Explanation CPP system initialization state.

Recommended Action No action is required.

Error Message %CPPHA-7-READY : CPP [dec] loading and initialization complete

Explanation A CPP has been successfully loaded and initialized, ready to be configured for forwarding packets.

Recommended Action No action is required.

Error Message %CPPHA-7-START : CPP [dec] [chars] image [chars]

Explanation A CPP is being started with the specified image.

Recommended Action No action is required.

Error Message %CPPHA-7-SYSREADY : CPP client process [chars] ([dec] of [dec]) ready.

Explanation A CPP Client process has started and registered with CPP HA Server.

Recommended Action No action is required.

CPP_BQS Messages

Error Message %CPP_BQS-2-MPASS_FS_REG : CPP BQS PROXY feature special vector [dec] registration failed (result: [dec])

Explanation The system experienced an internal software error. CPP multipass registration of a feature special processing vector for BQS Proxy failed. The BQS proxy will not be fully functional while this condition exists.

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

Error Message %CPP_BQS-2-PROXY_IPC_INIT_FAILED : CPP BQS Proxy IPC interface initialization failure (result: [dec]).

Explanation The system experienced an internal software error. CPP BQS initialization detected that the Proxy IPC interface initialization failed. The BQS Proxy will not be functional while this condition exists.

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

Error Message %CPP_BQS-3-CARVE : [chars]: size [int] SW carved out memory region initialization failed.

Explanation A BQS proxy failed to initialize the software memory region.

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

Error Message %CPP_BQS-3-CMD_ACTIVE : CPP BQS Proxy Command, correlator [int]

Explanation A BQS Proxy command was received, but the correlator was still in use. Command was not processed.

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

Error Message %CPP_BQS-3-INIT_FAILED : CPP BQS RM Proxy, region [chars]

Explanation BQS proxy failed due initialize or resize software managed memory.

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

Error Message %CPP_BQS-3-INVALID_SUBTYPE : CPP BQS RM Proxy subtype [int]

Explanation BQS proxy failed because of receiving invalid sub-type or failed to allocate ipc response buffer.

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

Error Message %CPP_BQS-3-PROXY_IPC_SEND : failure: [chars]

Explanation BQS Proxy send response failed, response was dropped.

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

Error Message %CPP_BQS-3-RESIZE : CPP BQS Proxy Memory Manager, region [chars]

Explanation BQS proxy failed to resize software managed memory.

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

Error Message %CPP_BQS_QMOVE-3-PROXY_COMPLETE : Proxy Operation: [chars]

Explanation Operation that was flagged as timed out, has now completed.

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

Error Message %CPP_BQS_QMOVE-3-PROXY_ERROR : Proxy Operation Failed: [chars]

Explanation BQS Proxy operation failed.

Recommended Action Copy the error message exactly as it appears on the console or in the system log. Research and attempt to resolve the error using the Output Interpreter. Also perform a search of the Bug Search Tool. If you still require assistance, 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.

Error Message %CPP_BQS_QMOVE-3-PROXY_TIMEOUT : Proxy Operation: [chars] node_id [hex] data [hex] data [hex]

Explanation BQS Proxy operation timeout. Proxy will continue to retry operation.

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

CPP_FM Messages

Error Message %CPP_FM-3-CPP_FM_FIPS_BYPASS_TEST : NIST bypass test failed for CPP_FM object [chars].

Explanation Classification Feature Manager Security Client database detected a discrepancy in a security sensitive object. 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 object or a parent object in question. If the problem persists reboot the forwarding processor (ESP).

Error Message %CPP_FM-4-CPP_FM_FIELD_IGNORED : Matching on field type [int] ([chars] value [int] ([hex])) not supported for client [chars] ([int]), rule oid: [chars], seqnos: %llu, %llu, %llu: RULE *IGNORED*

Explanation User is trying to use a classification criterion not supported by the feature. For example, user is trying to apply a with a class matching matched on an IPv6 ACL that contains a match on flow-label. The entire rule (e.g. ACE) containing the unsupported criterion is ignored. In our example, only the ACEs containing match on flow label are ignored. All other ACEs are still downloaded to CPP.

Recommended Action No action is required.

CPP_FR Messages

Error Message %CPP_FR-2-PROXY_IPC_INIT_FAILED : Frame Relay Proxy IPC interface initialization failure (result: [dec]).

Explanation The system experienced an internal software error. FR initialization detected that the Proxy IPC interface initialization failed. The FR interfaces may not function properly while this condition exists.

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

Error Message %CPP_FR-3-INV_PROXY_MSG : CPP FR Proxy received invalid IPC message ID [dec]

Explanation The system experienced an internal software error. CPP FR Proxy received an invalid message ID. This message will be ignored.

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

Error Message %CPP_FR-3-PROXY_IPC_ALLOC_FAIL : CPP Frame Relay Proxy response to msg id [int] lost due to buffer allocation failure

Explanation The system experienced an internal software error. CPP Frame Relay Proxy message processing detected a IPC buffer allocation failure during response processing.

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

CPP_IPHC_PROXY Messages

Error Message %CPP_IPHC_PROXY-3-INVALID_IPC_INPUT : [chars] CPP IPHC Client Proxy failure

Explanation IPHC proxy failed because of receiving invalid sub-type or failed to allocate ipc response buffer.

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

CPP_LDN Messages

Error Message %CPP_LDN-2-PROXY_IPC_INIT_FAILED : CPP LDN Proxy IPC interface initialization failure (result: [dec]).

Explanation The system experienced an internal software error. CPP LDN initialization detected that the Proxy IPC interface initialization failed. The LDN Proxy will not be functional while this condition exists.

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

Error Message %CPP_LDN-3-PROXY_GPM_RSRC_FAIL : failure: [chars]

Explanation LDN Proxy failed in performing a GPM operation.

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

Error Message %CPP_LDN-3-PROXY_IPC_INVALID : failure: [dec]

Explanation LDN Proxy received an invalid IPC msg from the client.

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

Error Message %CPP_LDN-3-PROXY_IPC_SEND : failure: [chars]

Explanation LDN Proxy send response failed, response was dropped.

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

CPP_MLP Messages

Error Message %CPP_MLP-3-PROXY_IPC_INIT_FAILED : CPP MLP Proxy IPC interface initialization failure

Explanation A Cisco Quantum Flow Processor function failed in an attempt to initialize MLP. The MLP bundle interfaces will not be functional while this condition exists.

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

Error Message %CPP_MLP-4-EARLY_RX_CLEANUP : CPP MLP Early Receive cleanup error ([chars])

Explanation A Cisco Quantum Flow Processor function failed in an attempt to cleanup multilink early receive.

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

Error Message %CPP_MLP-4-EARLY_RX_INIT : CPP MLP Early Receive initialization error ([chars])

Explanation A Cisco Quantum Flow Processor function experienced a multilink early receive error. This could cause lost MLP encapsulated packets during member link or bundle bring up and possibly cause a failure to complete member link or bundle initialization.

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

Error Message %CPP_MLP-4-INV_PROXY_MSG : CPP MLP Proxy received invalid Message ID [dec]

Explanation A Cisco Quantum Flow Processor error in which an invalid MLP message ID was received.

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

Error Message %CPP_MLP-4-PROXY_B_TX_IDLE_LINK_TRANSITION : CPP MLP Proxy ([chars] [chars]) invalid Bundle state [chars] ([dec]) for

Explanation A Cisco Quantum Flow Processor error in which a multilink idle-link transition invalid bundle state was received.

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

Error Message %CPP_MLP-4-PROXY_DUP_LINK_ID : CPP MLP Proxy ([chars] [chars]) duplicate Link ID [dec] for interface [chars]

Explanation A Cisco Quantum Flow 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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CPP_MLP-4-PROXY_INV_BUFFER_LIMIT : CPP MLP Proxy ([chars] [chars]) indicated an invalid Rx buffer limit

Explanation A Cisco Quantum Flow 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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CPP_MLP-4-PROXY_INV_BUNDLE_STATE : CPP MLP Proxy ([chars] [chars]) invalid Bundle state [chars] ([dec]) for

Explanation A Cisco Quantum Flow Processor error involving an invalid MLP bundle state. The associated MLP bundle interface may not be functional while this condition exists.

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

Error Message %CPP_MLP-4-PROXY_INV_CLASS_INFO : CPP MLP Proxy ([chars] [chars]) invalid Class Info (Base: 0x%08x, Num: [dec])

Explanation A Cisco Quantum Flow Processor error involving invalid MLP proxy class information. The associated MLP bundle interface may not be functional while this condition exists.

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

Error Message %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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CPP_MLP-4-PROXY_INV_LINK_STATE : CPP MLP Proxy ([chars] [chars]) invalid Link state [chars] ([dec]) for interface

Explanation 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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CPP_MLP-4-PROXY_INV_MRRU : CPP MLP Proxy ([chars] [chars]) invalid MRRU [dec] for interface [chars]

Explanation A Cisco Quantum Flow 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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %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 Quantum Flow Processor error in which an MLP proxy contained an invalid Rx/Tx interface value. The associated MLP bundle or member link interface may not be functional while this condition exists.

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

Error Message %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 Quantum Flow 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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CPP_MLP-4-PROXY_INV_TX_LINK_WEIGHT : CPP MLP Proxy ([chars] [chars]) indicated an invalid Tx Link weight

Explanation A Cisco Quantum Flow 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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CPP_MLP-4-PROXY_IPC_ALLOC_FAIL : CPP MLP Proxy ([chars]) response lost due to buffer allocation failure (Interface [chars]}

Explanation A Cisco Quantum Flow 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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %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 Quantum Flow 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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %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 Quantum Flow 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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CPP_MLP-4-PROXY_MAX_FRAGS_UNDEFINED : CPP MLP Proxy ([chars] [chars]) max fragments undefined for interface [chars]

Explanation A Cisco Quantum Flow 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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CPP_MLP-4-PROXY_NULL_BUNDLE : CPP MLP Proxy ([chars] [chars]) NULL Bundle sub-block for interface [chars]

Explanation A Cisco Quantum Flow 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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CPP_MLP-4-PROXY_NULL_LINK : CPP MLP Proxy ([chars] [chars]) NULL Member Link sub-block for interface [chars]

Explanation A Cisco Quantum Flow 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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CPP_MLP-5-PROXY_IPC_ALLOC_FAIL2 : CPP MLP Proxy ([chars]) response lost due to buffer allocation failure (Interface [chars])

Explanation A Cisco Quantum Flow 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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Search Tool at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message %CPP_MLP-5-PROXY_SYNC : CPP MLP Proxy ([chars] [chars]) Bundle/Link sync issue with interface [chars]

Explanation A Cisco Quantum Flow Processor experienced an error in which there is an invalid MLP proxy bundle or link interface synchronization.

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

CPP_NAT_PROXY Messages

Error Message %CPP_NAT_PROXY-3-INVALID_IPC_INPUT : number of instances is invali

Explanation The NAT proxy has received an IPC with an unexpected format/data.

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

Error Message %CPP_NAT_PROXY-3-INVALID_IPC_SUBTYPE : subtype is [dec]

Explanation The NAT proxy has received an IPC with an unexpected subtype.

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

Error Message %CPP_NAT_PROXY-3-NAT_INIT_FAIL : nat init failure rc= [dec]

Explanation The NAT proxy has experienced a failure when trying to initialize NAT.

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

Error Message %CPP_NAT_PROXY-3-NAT_SEND_IPC_FAIL : rc= [dec]

Explanation The NAT proxy has experienced a failure when trying to send an IPC.

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

CPP_PFR_PROXY Messages

Error Message %CPP_PFR_PROXY-3-INVALID_IPC_SUBTYPE : subtype is [dec]

Explanation The PfR proxy has received an IPC with an unexpected subtype.

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

Error Message %CPP_PFR_PROXY-3-PFR_INIT_FAIL : pfr init failure rc= [dec]

Explanation The PFR proxy has experienced a failure when trying to initialize PFR.

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

Error Message %CPP_PFR_PROXY-3-PFR_IPC_PAK_ALLOC_FAILED : rc= [dec]

Explanation Allocation of PFR IPC response packet failed.

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

Error Message %CPP_PFR_PROXY-3-PFR_SEND_IPC_FAIL : rc= [dec]

Explanation The PfR proxy has experienced a failure when trying to send an IPC.

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

CPPOSLIB Messages

Error Message %CPPOSLIB-3-CLEAN_NOTIFY : Failed to cleanup: ([chars])

Explanation A function failed to cleanup data.

Recommended Action No action is required.

Error Message %CPPOSLIB-3-ERROR_NOTIFY : [chars] encountered an error

Explanation Print error message to console.

Recommended Action No action is required.

Error Message %CPPOSLIB-3-GET_NOTIFY : Failed to get data: ([chars])

Explanation A function failed to get data.

Recommended Action No action is required.

Error Message %CPPOSLIB-3-INIT_NOTIFY : Failed to initialize: ([chars])

Explanation A function failed to initialize.

Recommended Action No action is required.

Error Message %CPPOSLIB-3-REGISTER_NOTIFY : Failed to register: ([chars])

Explanation A function failed to register.

Recommended Action No action is required.

CPPTCAMRM Messages

Error Message %CPPTCAMRM-6-HIGH_WATER_MARK : TCAM resources in the system is limited.

Explanation The TCAM device has limited number of free cells left to allocate.

Recommended Action No action is required.

Error Message %CPPTCAMRM-6-HIGH_WATER_MARK : TCAM resources in the system is limited.

Explanation The TCAM device has limited number of free cells left to allocate.

Recommended Action No action is required.

Error Message %CPPTCAMRM-6-LOW_WATER_MARK : There is sufficient TCAM resources in the system.

Explanation The TCAM device has sufficient number of free cells left.

Recommended Action No action is required.

Error Message %CPPTCAMRM-6-LOW_WATER_MARK : There is sufficient TCAM resources in the system.

Explanation The TCAM device has sufficient number of free cells left.

Recommended Action No action is required.

Error Message %CPPTCAMRM-6-TCAM_RSRC_ERR : Allocation failed because of insufficient TCAM resources in the system.

Explanation The TCAM device has no free cells to accommodate the current allocation request.

Recommended Action No action is required.

CRYTO Messages

Error Message %CRYPTO-3-IKE_PAK_IN_Q_TIME_LIMIT_EXCEED: Pak spent too much time in the IKE input queues

Explanation An incoming IKE packet spent too much time in the IKE input queues. This can happen when the IKE subsystem is under heavy load, due to a lot of peers trying to setup SAs simultaneously, and IKE is not able to handle all the incoming packets, in a timely manner.

Recommended Action It is important to understand why many peers are simultaneously trying to setup SAs at the same time. If possible, try to avoid or minimize such network conditions.

Error Message %CRYPTO-3-NOSOCKET: Unable to open %s

Explanation The requested operation could not be accomplished because of a low memory condition.

Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration and restart crypto isakmp process

Error Message %CRYPTO-6-PRNG_SEED_KEY_ERROR: Pseudo-random number generator seed and seed key was identical

Explanation The X9.17 random number specification requires us to check for the same value appearing as the seed and the seed key. This message indicates that the condition was discovered.

Recommended Action The X9.17 random number will occasionally produce this condition, and this is not a problem. However if this message occurs frequently, the system should be manually reloaded. If the message is persistent across reloads, copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %CRYPTO-6-RANDOM: A pseudo-random number was generated twice in succession

Explanation A pseudo-random number generator produced the same number twice in succession.

Recommended Action Under normal circumstances a pseudo-random number generator will occasionally produce the same number twice in succession and this is not a problem. However if this message occurs frequently, the system should be manually reloaded. If the message is persistent across reloads, copy the error message exactly as it appears, and report it to your technical support representative.

Error Message %CRYPTO_RSA_ISSU-3-INIT: Crypto RSA ISSU client initialization failed to %s. Error: %d (%s)

Explanation Crypto RSA ISSU client could not be initiailzed, this will cause catstrophic failure when ISSU upgrade or downgrade is performed.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CRYPTO_RSA_ISSU-3-INVALID_SESSION: Crypto RSA ISSU client does not have a valid registered session.

Explanation Crypto RSA ISSU client does not have a valid registered session. When there is a problem with the session the standby unit cannot be brought up.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show issu capability entries, show issu session and show issu negotiated capability commands and your pertinent troubleshooting logs.

Error Message %CRYPTO_RSA_ISSU-3-MSG_NOT_OK: Crypto RSA ISSU client message type %d is not compatible

Explanation Crypto RSA ISSU client received an incompatible message from the peer unit. Since the message is not compatible it cannot be processed by this unit

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show issu message group, show issu session and show issu negotiated version commands and your pertinent troubleshooting logs.

CTS Messages

Error Message %CTS-0-AUTHZ_OUT_OF_MEM: %s failed to create %s due to insufficient memory

Explanation The system is experiencing insufficent memory.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-0-CTS_EMERG: %s

Explanation CTS_INTERNAL_ERROR

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-0-IFC_OUT_OF_MEM: %s failed to create %s due to insufficient memory

Explanation The system is experiencing insufficent memory.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-1-CTS_ALERT: %s

Explanation CTS_INTERNAL_ERROR

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-1-CTS_CRED_ACTION_NEEDED: CTS credentials are missing or inconsistent in the redundant keystore. Please re-configure cts credentials or execute cts change-password.

Explanation A redundant keystore was detected as either not containing any CTS credentials, or having a different set of credentials as contained in the active keystore. This means that CTS authentication will fail upon switchover unless remedial action is taken before then. Either use the cts credentials… CLI to re-configure the CTS device-id and password, or use the cts change-password… CLI to initiate a password change with the AAA server. Either of these actions will cause the device-id and password to be inserted in both the active and redundant keystores.

Error Message %CTS-2-CTS_CRIT: %s

Explanation CTS_INTERNAL_ERROR

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-ACL_UNCONFIGURED: Access-list %s has been dynamically unconfigured from CTS policy because it has been %s.

Explanation An access-list configured as defining CTS L3 traffic or exemption policy has been deleted or modified so that it can no longer be used for defining CTS policy. It has therefore been removed from the CTS layer3 policy configuration.

Error Message %CTS-3-AUTHZ_ADD_DATA_FAILED: %s failed to add %s to %s

Explanation An error occurred while CTS Authz attempted to build its database.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-AUTHZ_DATA_CREATE_FAILED: %s failed to create %s

Explanation An error occurred while CTS Authz attempts to create an internal data structure.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-AUTHZ_DATA_EXCEEDS_LIMIT: %s encountered %s(%d) exceeds max(%d)

Explanation Data exceeds maximum limits allowed.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-AUTHZ_DATA_FAILED: %s failed to obtain %s

Explanation An error occurred while CTS Authz attempted to get/create a data structure

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-AUTHZ_DATA_NULL: %s encounters NULL %s

Explanation An unexpected NULL pointer/data is encountered.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-AUTHZ_DATA_UNINIT: %s appears uninitialized

Explanation CTS Authz unexpectedly encountered an unitialized data

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-AUTHZ_FAILED_SYNC_RCV: Standby failed receive sync msg(%s)

Explanation An error occcured while the Standby is receiving sync data from the Active.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-AUTHZ_GENERIC_FAILURE: %s %s

Explanation CTS Authz encountered internal error.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-AUTHZ_INSTALL_FAILED: %s failed to install %s %s

Explanation An error occurred while CTS Authz attempted to program the policy.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-AUTHZ_INVALID_DATA: %s encountered invalid %s

Explanation CTS Authz encountered an unexpected invalid data type.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-AUTHZ_NOT_SUPPORTED: %s encountered %s not unsupported

Explanation CTS encountered an unsupported data type or feature. This could be due to incompatibility

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-AUTHZ_POLICY_FAIL_TO_REMOVE: Failed to remove %s policy from the authorization dbase

Explanation An error occured while CTS attempted to remove the specified policy from its database. This could result in an action not being accomplished.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-AUTHZ_POLICY_INGRESS_FAILED: Failed to %s Ingress policy for %s

Explanation An error occurred while CTS attempted to acquire or install anIngress policy from the ACS.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-AUTHZ_POLICY_INTERNAL_FAILED: Failed to acquire/install policy for %s due to internal error

Explanation An error occurred while CTS attempted to acquire/install a policy which may be caused by internal software error

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-AUTHZ_POLICY_PEER_DOWNLOAD_FAILED: Failed to download peer policy for %s

Explanation An error occurred while CTS attempted to acquire peer policy from the ACS.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-AUTHZ_POLICY_RBACL_ACE_FAILED: Failed to %s%s RBACL ’%s’ for SGT=%d due to ACE ’%s’ error

Explanation An error occurred in the ACE while CTS attempted to acquireRBACL policy from the ACS.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-AUTHZ_POLICY_RBACL_FAILED: Failed to %s%s RBACL %s for SGT=%d

Explanation An error occurred while CTS attempted to acquire RBACL policy from the ACS.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-AUTHZ_POLICY_WILDCARD_FAILED: Failed to download default/unknown policy

Explanation An error occurred while CTS attempted to acquire wildcard policy from the ACS.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-AUTHZ_SYNC_FAILED: Failed to send %s sync msg(%s) to Standby

Explanation An error occcured while CTS Authz is performing a sync to the Standby.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-CTS_ERR: %s

Explanation CTS_INTERNAL_ERROR

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-DOT1X_CONFIG_FAILED: Failed to configure dot1x for int(%s)

Explanation An error occcured while CTS attempts to configure dot1x for a CTS link

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-DOT1X_FORCE_PORT_AUTHORIZED_FAILED: Failed to force dot1x port authorized for int(%s)

Explanation An error occcured while CTS attempts to force dot1x port authorized on a CTS link

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-DOT1X_INIT_FAILED: Failed to initialize dot1x for int(%s)

Explanation An error occcured while CTS attempts to initialize dot1x for a CTS link

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-DOT1X_PAE_FAILED: Failed to %s dot1x PAE(%s) for int(%s)

Explanation An error occcured while CTS attempts to start/stop dot1x PAE(s) for a CTS link

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-GCM_NO_LICENSE: CTS link %s is being shut down: please install MACSec Encryption License (http:/www.cisco.com/go/license)

Explanation A MACSec Encryption License is required to use gcm-encryption on secure links. All CTS links configured to run gcm-encryption will be held in administratively down state until the gcm-encrytion is removed from the interface configuration or until a MACSec Encryption License is installed.

Recommended Action Either install a MACSec Encryption License or configure all CTS interfaces with cipher modelists that do not include gcm.

Error Message %CTS-3-GENERIC_FAILURE: %s %s

Explanation CTS Core encountered internal error.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-GLOBAL_DOT1X_DISABLED: Global dot1x config is currently disabled — CTS will not run

Explanation Global dot1x is not enabled and hence, CTS will not run

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-IFC_DATA_DESC_DECODE_FAILED: %s failed to decode the data-descriptori — swidb unknown

Explanation An error occured while the system attempted to decode the data-descriptor in order to obtain the swidb

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-IFC_DATA_DESC_ENCODE_FAILED: %s failed to encode the data-descriptor for int(%s)

Explanation An error occured while the system attempted to encode the swidb into the data-descriptor

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-IFC_DATA_NULL: %s encounters NULL %s

Explanation An unexpected NULL pointer/data is encountered.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-IFC_LINK_OBJ_FAILED: %s failed to get link_obj for int(%s)

Explanation An error occured while CTS IFC attempts to access the link object.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-IFC_SYNC_FAILED: Failed to send %s sync msg(%s) to Standby

Explanation An error occcured while CTS IFC is performing a sync to the Standby.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-IFC_SYNC_FAILED_2: %s, Failed to send %s sync msg(%s) to Standby

Explanation An error occcured while CTS IFC is performing a sync to the Standby.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-INVALID_ACL: Access-list %s invalid for CTS policy: %s.

Explanation An access-list configured as defining CTS L3 traffic or exemption policy cannot be used because of the specified reason.

Error Message %CTS-3-INVALID_MSGID_RCV: %s received invalid HA/ISSU msgId(%d)

Explanation CTS Core encountered an unexpected invalid HA/ISSU message ID.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-LSC_CA_STORE_FAIL: Failed to install certificate of CA that issued our locally-significant certificate

Explanation An error occurred while installing the certificate of our issuing CA. When this error occurs, the locally-significant certificate will be discarded and CTS will continue to use its password credentials for authentication.

Error Message %CTS-3-LSC_ENROLL_FAIL: Failed to set re-enrollment attributes for CTS locally-significant certificate.

Explanation An error occurred while setting the re-enrollment attributes for the new CTS certificate. When this error occurs, the newcertificate will be discarded and CTS will continue to use its password credentials for authentication.

Error Message %CTS-3-LSC_STORE_FAIL: Failed to install newly-provisioned locally-significant certificate.

Explanation An error occurred while installing our locally significant certificate to be used for CTS. This means that we cannot be authenticated using a certificate. If a CTS password is available, we will continue to authenticate using the password.

Error Message %CTS-3-POLICY_COA_RBACL_FAILED: Failed to complete request for update-rbacl(%s-%s)

Explanation An error occurred while CTS attempted to service a Change of Authorization request for the update-rbacl command

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-POLICY_COA_SGT_FAILED: Failed to complete CoA request for update-sgt(%s)

Explanation An error occurred while CTS attempted to service a Change of Authorization request for the update-sgt command

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-POLICY_HA_PROC_FAIL: Error starting up HA switchover Policy refresh process.

Explanation A failure has occurred in switchover which has prevented thepolicy refresh process to be lauched. User should manually refresh policies via the cts refresh policy commad

Recommended Action Issue command cts refresh policy and verify policy timers are active, If timers do not start Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-POLICY_INSTALL_FAIL: An error occurred while trying to program the hardware (error code %d)

Explanation An error occurred while trying to program the hardware to implement the configured policy.

Error Message %CTS-3-PORT_AUTHORIZED_FAILED: Failed to authorize Port for int(%s)

Explanation Port failed to be authorized on a CTS link

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-PP_CTS_EC_NOT_CTS: Physical port is not configured for CTS, but port-channel is.

Explanation Physical port cannot join the channel-group (port-channel) unless CTS configs match the channel.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-PP_CTS_MODE_EC_MISMATCH: Physical port CTS mode does not match the port-channel’s CTS mode.

Explanation Physical port cannot join the port-channel unless their CTS modes match.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-PP_CTS_TIMER_REAUTH_EC_MISMATCH: Cannot bundle interface. CTS Reauth Timer mismatch. %s = %d %s = %d

Explanation Physical port cannot join the port-channel if CTS timer reauthentication values differ.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-PP_NOT_CTS_EC_CTS: Physical port is configured for CTS, but port-channel is not.

Explanation Physical port cannot join the channel-group (port-channel) unless their CTS configs match.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-ROOT_CA_STORE_FAIL: Could not install the CTS trusted-root certificate.

Explanation An error occcured while installing the CTS trusted-root certificate. This means that CTS cannot validate AAA servers’ certifcates received during EAP-FAST exchanges.

Error Message %CTS-3-SEND_MSG_TO_CORE_FAILED: Failed to send msg(%d) to core process

Explanation An error occcured while CTS attempts to send a message event to the core process

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-SSO_NO_LICENSE: CTS GCM links are being shut down. Please install a MACSec Encryption License on the new active supervisor (http:/www.cisco.com/go/license)

Explanation A MACSec Encryption License is required to use gcm-encryption on secure links. If the active supervisor has a license but the standby does not, then links may run GCM encryption. However on switchover all links running GCM will be shut down because the new active does not have a License.

Recommended Action Either install a MACSec Encryption License (http://www.cisco.com/go/license) on each of the redundant supervisors or configure all CTS interfaces with cipher modelists that do not include gcm.

Error Message %CTS-3-STDBY_NO_LICENSE: CTS link %s may be shut down on switchover: please install MACSec Encryption License on the standby supervisor (http:/www.cisco.com/go/license)

Explanation A MACSec Encryption License is required to use gcm-encryption on secure links. If the active supervisor has a license but the standby does not, then links may run GCM encryption. However on switchover all links running GCM will be shut down because the new active does not have a License.

Recommended Action Either install a MACSec Encryption License or configure all CTS interfaces with cipher modelists that do not include gcm.

Error Message %CTS-3-SXP_BINDING_ERR: Binding %s- %s

Explanation SXP binding update error.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-3-SXP_CONN_STATE_CHG_OFF: Connection %s-%d state changed from %s to Off.

Explanation SXP Connection with the specified instance number changed state.

Recommended Action No action is required.

Error Message %CTS-3-SXP_LISTENER: Fail to start global listening socket after TCP process restart.

Explanation SXP on this device can not accept SXP connection setup request from the remote devices.

Recommended Action Disable and enable SXP feature to see if the global listening socket can be restarted.

Error Message %CTS-3-SXP_MSG_PARSE: Connection %s %s

Explanation An error occurred while parsing SXP message.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-4-CTS_WARNING: %s

Explanation CTS_INTERNAL_ERROR

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-4-NO_PROV_SECRET: No shared secret available for provisioning PAC from server %i.

Explanation We are unable to provision or reprovision a CTS PAC because we do not have a configured RADIUS shared secret for the server and there are no valid unexpired PACs that can be used to secure the re-provisioning exchange.

Error Message %CTS-4-PAC_EXP_UNAVAIL: Credential lifetime of PAC (%s) unavailable, no refresh scheduled.

Explanation A PAC in the keystore is missing the Credential Lifetime field in its PAC-info. Since the expiration time is unavailable, we do not know when to schedule a refresh for this PAC.

Error Message %CTS-4-SXP_INTERNAL: CTS SXP %s

Explanation The CTS SXP system encountered internal failure.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-5-CTS_NOTICE: %s

Explanation Normal but significant conditions

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-5-PASSWORD_CHANGE_ONE: CTS password in the keystore has been renamed %s.

Explanation An MSCHAPv2 change-password sequence has been successfully executed and the old password is being renamed for fallback use. This is the first of a 2-part operation. Next the new password will be renamed to become the active password.

Error Message %CTS-5-PASSWORD_CHANGE_TWO: A new CTS password has been installed as %s in the keystore.

Explanation A new CTS password has been installed in the keystore following a successful MSCHAPv2 change-password sequence. The old password has been saved for fallback use.

Error Message %CTS-5-ROOT_CA_STORE_DONE: A trusted-root certificate to be used for CTS has been installed.

Explanation A CTS trusted-root certificate was received from a AAA server during an EAP-FAST enrollment. This certificate will be used for validating all AAA servers’ certificates received from here on.

Error Message %CTS-5-SXP_BINDING_ADD: Binding %s- added to SXP database.

Explanation Binding added to the SXP database.

Recommended Action No action is required.

Error Message %CTS-5-SXP_BINDING_CHG: Binding %s- changed: old connection instance number:%d, old sgt:%d.

Explanation Binding changed in the SXP database.

Recommended Action No action is required.

Error Message %CTS-5-SXP_BINDING_DEL: Binding %s- deleted in SXP database.

Explanation Binding deleted in the SXP database.

Recommended Action No action is required.

Error Message %CTS-5-SXP_BINDING_FWD: Binding %s- is forwarded to the peer.

Explanation SXP forwarded binding to the peer.

Recommended Action No action is required.

Error Message %CTS-5-SXP_BINDING_REQ: SXP received binding forwarding request (%s) binding %s.

Explanation SXP received a binding forwarding request.

Recommended Action No action is required.

Error Message %CTS-5-SXP_BINDING_UPD: Binding %s %s. Update binding manager.

Explanation SXP updated binding manager with the binding change.

Recommended Action No action is required.

Error Message %CTS-5-SXP_DFT_PASSWORD_CHANGE: CTS SXP password changed.

Explanation The SXP system password has been changed.

Recommended Action No action is required.

Error Message %CTS-5-SXP_DFT_SRCIP_CHG: SXP default source IP is changed %i — %i.

Explanation SXP default source IP is changed on this device.

Recommended Action No action is required.

Error Message %CTS-5-SXP_STATE_CHANGE: CTS SXP %s

Explanation The SXP feature has changed operational state. SXP feature is functioning only when the feature is enabled.

Recommended Action No action is required.

Error Message %CTS-5-SXP_VRF_DEL: SXP Connection configuration in VRF:%s is removed.

Explanation A VRF is removed, the connections configured in this VRF should be removed.

Recommended Action No action is required.

Error Message %CTS-6-CTS_INFO: %s

Explanation Informational messages

Recommended Action No action is required.

Error Message %CTS-6-DOT1X_FORCE_PORT_AUTHORIZED_SUCCESS: Successfully forced dot1x port authorized for int(%s)

Explanation Port has been put to FORCE AUTHORIZED on a CTS link

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-6-DOT1X_PAE_CONFIG: %s dot1x PAE(%s) for int(%s)

Explanation The interface has been configured for dot1x PAE(s)

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-6-IFC_CACHE_APPLIED: Cache data applied for int(%s)

Explanation Inform the user that the CTS link is brought up using cache data

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-6-POLICY_COA_DONE: Command %s=%s completed

Explanation A Change of Authorization request has been serviced

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-6-POLICY_COA_NO_ACTION: Command %s=%s has no change

Explanation A Change of Authorization request has been received, but no action was taken due to the system is already in possession of the requested data

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-6-POLICY_COA_NO_SESSION: Command %s=%s has no session associated

Explanation A Change of Authorization request has been received for infomration that the system is not in possession of

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-6-POLICY_COA_RBACL_REQUEST: Command %s=%s-%s

Explanation A Change of Authorization request command is received for update-rbacl

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-6-POLICY_COA_SGT_REQUEST: Command %s=%s

Explanation A Change of Authorization request command is received for update-sgt

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-6-PORT_AUTHORIZED_SUCCESS: Port authorized for int(%s)

Explanation Port has been authorized on a CTS link

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-6-PORT_UNAUTHORIZED: Port unauthorized for int(%s)

Explanation Port has been unauthorized on a CTS link

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS-6-SXP_CONFIG: Connection %s %s

Explanation A SXP configuration error occurred. The connection can not be setup correctly.

Recommended Action Ensure that the connection configure on both ends have the matched mode, IP addresses.

Error Message %CTS-6-SXP_CONN_STATE_CHG: Connection %s-%d state changed from %s to %s.

Explanation SXP Connection with the specified instance number changed state.

Recommended Action No action is required.

Error Message %CTS-6-SXP_SRC_IP: Source IP address (%s %i) does not belong to this device.

Explanation An error occurred while using this source IP address to set up SXP connection.

Recommended Action Re-configure SXP connection to have a valid source IP address.

Error Message %CTS-6-SXP_TIMER_START: Connection %s %s timer started.

Explanation The specified SXP timer started.

Recommended Action No action is required.

Error Message %CTS-6-SXP_TIMER_STOP: Connection %s %s timer stopped.

Explanation The specified SXP timer stopped.

Recommended Action No action is required.

Error Message %CTS-7-CTS_ASSERT: Assertion Failure ( %s @%s:%d) : %s

Explanation CTS_INTERNAL_ERROR

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS_HA-3-CHKPT_REG_FAIL: CTS HA add CTS checkpoint client failure.

Explanation CTS HA failed to add checkpoint client. No CTS data will be synced to Standby in this case.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS_HA-3-RECEIVE_FAILED: CTS HA failed to process message recieved from Active device. CTS component Id %d, message Id %d, max header size %d, size %d, max message size %d.

Explanation CTS HA client on Standby device failed to process checkpoint message. CTS state between the active device and the Standby device is not identical.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS_HA-3-SEND_FAILED: CTS HA failed to send checkpoint message. CTS component Id %d, message Id %d, header size %d, max header size %d, message size %d, max size %d.

Explanation The CTS HA client failed to send a checkpoint CTS state between the active device and the standby device is not identical.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS_HA_ISSU-3-CAP_INVALID_SIZE: CTS HA empty tlv size.

Explanation Received empty tlv list during capability negotiation.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS_HA_ISSU-3-CAP_NOT_COMPATIBLE: CTS HA capability not compatible

Explanation CTS HA failed during capability negotiation.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS_HA_ISSU-3-GET_BUFFER: CTS HA ISSU client failed to get buffer for message. Error: %d (%s)

Explanation The CTS HA ISSU client failed to get buffer space for building a negotiation message. A negotiation message cannot be sent to the standby device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.

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

Error Message %CTS_HA_ISSU-3-INIT: CTS HA ISSU client initialization failed to %s. Error: %d (%s)

Explanation CTS HA ISSU client could not be initialized. This initialization failure must be addressed before in-service software upgrade or downgrade can be performed successfully. If you do not address this failure, there will be downtime during software upgrade or downgrade.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS_HA_ISSU-3-MSG_NOT_COMPATIBLE_WITH_PEER: Message %d in component %d is not compatible with the peer.

Explanation Message not compatible with the peer.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %CTS_HA_ISSU-3-SEND_NEGO_FAILED: CTS HA ISSU client failed to send negotiation message. Error: %d (%s)

Explanation The CTS HA ISSU client failed to send a session negotiation message to the peer device. If a problem occurs with the ISSU session negotiation, the standby device cannot be brought up properly.

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

Error Message %CTS_HA_ISSU-3-SESSION_REGISTRY: CTS HA ISSU client failed to register session information. Error: %d (%s)

Explanation The CTS HA ISSU client failed to register session information. If a problem occurs with the ISSU session registration, the standby device cannot be brought up properly.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show issu capability entries, show issu session and show issu negotiated capability commands and your pertinent troubleshooting logs.

Error Message %CTS_HA_ISSU-3-SESSION_UNREGISTRY: CTS HA ISSU client failed to unregister session information. Error: %d (%s)

Explanation The CTS HA ISSU client failed to unregister session information.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show issu session and show issu negotiated capability commands and your pertinent troubleshooting logs.

Error Message %CTS_HA_ISSU-6-INCOMPAT: CTS HA ISSU client negotiation results incompatible

Explanation The CTS HA ISSU client message version is not compatible on Active and Standby. No CTS data will be synced to Standby in this case

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show issu capability entries, show issu session and show issu negotiated version commands and your pertinent troubleshooting logs.

DATA_DESCR Messages

Error Message %DATA_DESCR-3-ENTRY_EXPIRED: Found expired message entry for descriptor %u-%u/%u/%u/%u

Explanation Data descriptors are used to encode an interface index in a compact fashion for transfer between redundant route processor units. An error occurred during the processing of a data descriptor. The failure most likely occurred because of a software error. The numeric error code in the message output identifies the failing data descriptor index. The system state between the Active and Standby units might not be properly synchronized.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %DATA_DESCR-3-ENTRY_EXPIRED: Found expired message entry for descriptor %u-%u/%u/%u/%u

Explanation HAWKEYE log message.

Recommended Action No action is required.

DMB Messages

Error Message %DMB-0-DMB_EMERG: %s

Explanation DMB_INTERNAL_ERROR

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %DMB-1-DMB_ALERT: %s

Explanation DMB_INTERNAL_ERROR

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %DMB-2-DMB_CRIT: %s

Explanation DMB_INTERNAL_ERROR

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %DMB-3-DMB_ERR: %s

Explanation DMB_INTERNAL_ERROR

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %DMB-4-DMB_WARNING: %s

Explanation DMB_INTERNAL_ERROR

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %DMB-5-DMB_NOTICE: %s

Explanation Normal but significant conditions

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %DMB-6-DMB_INFO: %s

Explanation Informational messages

Recommended Action No action is required.

Error Message %DMB-7-DMB_ASSERT: Assertion Failure ( %s @%s:%d) : %s

Explanation DMB_INTERNAL_ERROR

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

Error Message %DWDM-3-CONFIG_OVERHEAD_TTI: Failed to config %s%s slot %d rc = %d

Explanation The LC driver could not configure the tail traceidentifier for the optical data or transport unit

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit http://www.cisco.com/cgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.

DROP Messages

Error Message %DROP-3-DOUBLE_DROP : First drop error cause [int] update stat cause [int] trace: [hex] [hex]

Explanation The drop infrastructure was called for a packet that was previously dropped.

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

Error Message %DROP-3-RESERVED : [chars]

Explanation An invalid drop cause was passed to the drop infrastructure.

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

DWL Messages

Error Message %DWL-3-LOOP_BACK_DETECTED: Loop-back detected on %s.

Explanation Loop-back may be caused by accidentally plugging a balun cable into the port or there may be a mis configuration in the network.

Recommended Action Correct the problem causing the loopback condition. Then bring the port up by entering the shutdown, then no shutdown interface configuration commands.

DYNCMD Messages

Error Message %DYNCMD-3-CHAINADDFAIL: Parse chain link add failed for ’[chars]’

Explanation An error has occurred when a dynamic command is being added to the IOS command set. The commands specified will not be available.

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

Error Message %DYNCMD-3-CHAINDELFAIL: Parse chain link delete failed for ’[chars]’

Explanation An error has occurred when a dynamic command is being removed from the IOS command set. The commands specified will not be available.

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

Error Message %DYNCMD-3-FLAGSINUSE: New feature flags list [int] invalid while feature flags in use [int]

Explanation IOS received a message to set the feature flags for the CLI. The message received to set the feature flags changed the number of feature flags which is unexpected. The message is ignored.

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

Error Message %DYNCMD-3-FLAGSINVALID: New feature flag list values ([int]) different than expected ([int])

Explanation IOS received a message to set the feature flags for the CLI. The message received does not contains the number of feature flag values that the message list size indicated.

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

Error Message %DYNCMD-3-INIT: Dynamic command subsystem failed to initialize ’[chars]’

Explanation Some features depend on portions of the dynamic command infrastructure.Such features will be unavailable.

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

Error Message %DYNCMD-3-LINKINVALIDALT: Link alternate node message received for node ’[chars]’, which cannot have an alternate.

Explanation IOS received a message to add a command into the CLI. One of the messages to link nodes instructed IOS to link nodes which would result in an invalid construction.

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

Error Message %DYNCMD-3-LINKINVALIDTRANS: Link transition ’[chars]’ message received for node ’[chars]’, which cannot have such a transition.

Explanation IOS received a message to add a command into the CLI. One of the messages to link nodes instructed IOS to link nodes which would result in an invalid construction.

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

Error Message %DYNCMD-3-LINKOUTOFSEQ: Create node message received when in mode ’[chars]’

Explanation IOS received a message to add a command node into the CLI. The message was received out of sequence.

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

Error Message %DYNCMD-3-LINKUNKNOWNACCEPTNODE: Link node message received for unknown accept ([chars]) node ’[int]’

Explanation IOS received a message to add a command into the CLI. One of the messages to link nodes referenced a node unknown to IOS.

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

Error Message %DYNCMD-3-LINKUNKNOWNALTNODE: Link node message received for unknown alternate node ’[int]’

Explanation IOS received a message to add a command into the CLI. One of the messages to link nodes referenced a node unknown to IOS.

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

Error Message %DYNCMD-3-LINKUNKNOWNNODE: Link node message received for unknown node ’[int]’

Explanation IOS received a message to add a command into the CLI. One of the messages to link nodes referenced a node unknown to IOS.

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

Error Message %DYNCMD-3-MSGBIPCBUFFER: Unable to acquire a BIPC buffer for sending messages.

Explanation A message was to be sent by IOS, but no BIPC buffer was available. The message to be sent has been discarded and the associated operation failed.

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

Error Message %DYNCMD-3-MSGBIPCERR: Unable to process received BIPC messages for Dynamic Commands, error: [chars]

Explanation An unexpected condition has occurred while IOS was trying to process a received BIPC message for Dynamic Commands.

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

Error Message %DYNCMD-3-MSGBUILDERROR: Error ’[dec]’ building TDL message ’[chars]’ to send to the Shell Manager

Explanation An unexpected condition has occurred while IOS is building a TDL message to send to the Shell Manager

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

Error Message %DYNCMD-3-MSGDISPATCH: Unable to dispatch received TDL messages for Dynamic Commands

Explanation An unexpected condition has occurred while IOS is trying to dispatch to the TDL message handler functions for received TDL messages for Dynamic Commands.

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

Error Message %DYNCMD-3-MSGDISPATCHNULL: Received NULL TDL message

Explanation An unexpected condition in which IOS has received a NULL TDL message for Dynamic Commands.

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

Error Message %DYNCMD-3-MSGENQUEUEERROR: Error queueing TDL message ’[chars]’ to send to the Shell Manager

Explanation An unexpected condition has occurred when IOS attempted to queue a TDL message to send to the Shell Manager.

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

Error Message %DYNCMD-3-MSGERROR: Error ’[chars]’ handling a received TDL message ’[chars]’ for Dynamic Commands

Explanation An unexpected condition has occurred while IOS is processing a received Dynamic Command TDL message.

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

Error Message %DYNCMD-3-MSGINVALIDFIELDINT: Invalid field ’[chars]’ in TDL message ’[chars]’ received: value ’[int]’ for Dynamic Commands

Explanation A message with an invalid field value was received for Dynamic Command creation.

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

Error Message %DYNCMD-3-MSGINVALIDFIELDSTR: Invalid field ’[chars]’ value ’[chars]’ in TDL message ’[chars]’ received for Dynamic Commands

Explanation A message with an invalid field value was received for Dynamic Command creation.

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

Error Message %DYNCMD-3-MSGMARSHALERROR: Error ’[dec]’ marshaling TDL message ’[chars]’ to send to the Shell Manager

Explanation An unexpected condition has occurred while IOS is marshaling TDL message to send to the Shell Manager.

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

Error Message %DYNCMD-3-MSGMISSINGFIELD: Missing field ’[chars]’ in TDL message ’[chars]’ received from the Shell Manager

Explanation A message missing a required field was received from the Shell Manager.

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

Error Message %DYNCMD-3-NODEDUPLICATE: Create node message received for duplicate node ’[int]’

Explanation IOS received a message to add a command into the CLI. One of the command nodes to be created has an identifier of an existing node. The new node is ignored.

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

Error Message %DYNCMD-3-NODEOUTOFSEQ: Create node message received when in mode ’[chars]’

Explanation IOS received a message to add a command node into the CLI. The message was received out of sequence.

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

Error Message %DYNCMD-3-NODETYPEUNKNOWN: Create node message received for unknown node type ’[dec]’, ’[chars]’

Explanation IOS received a message to add a command into the CLI. One of the command nodes to be created is of a type unknown to IOS.

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

Error Message %DYNCMD-3-PKGERR_LOG_FAIL : Failed to log errors for package ‘[chars]’

Explanation An error has occurred updating the command set for a newly installed package. The commands which failed to transfer could not be saved for further analysis.

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

Error Message %DYNCMD-3-PKGHANDLER_FILE_REMOVE: Package ’[chars]’ failed to remove: [chars] ([chars])

Explanation An error has occurred when a package was attempting to remove a file.This should never fail.

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

Error Message %DYNCMD-3-PKGHANDLER_FILE_WRITE: Package ’[chars]’ failed to write: [chars] ([chars])

Explanation An error has occurred when a package was attempting to write a file.The configuration for the package could not be propagated to associated components.

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

Error Message %DYNCMD-3-PKGINT_API: Package interface failure for package ’[chars]’: [chars]

Explanation Some features’ configuration depends on a packaging infrastructure. Packaged configuration for the specified package will be unavailable.

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

Error Message %DYNCMD-3-PKGINT_ARG: Incorrect argument type for package ’[chars]’, operation ’[chars]’: [chars] ([int])

Explanation An error has occurred loading the command set for a newly installed package. The package is not compatible with the running IOS instance.

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

Error Message %DYNCMD-3-PKGINT_ARGS: Incorrect argument count for package ’%s’, operation ’%s’: %d not %d

Explanation An error has occurred loading the command set for a newly installed package. The package is not compatible with the running IOS instance.

Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the information you have gathered.

Error Message %DYNCMD-3-PKGINT_ARG_NUMBERVAL: Invalid argument value for package ’[chars]’, operation ’[chars]’: [int] ([int])

Explanation An error has occurred loading the command set for a newly installed package. The package is not compatible with the running IOS instance.

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

Error Message %DYNCMD-3-PKGINT_ARG_OPAQUEVAL : Invalid argument value for package ‘[chars]’, operation ‘[chars]’: %p ([int])

Explanation An error has occurred loading the command set for a newly installed package. The package is not compatible with the running IOS instance.

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

Error Message %DYNCMD-3-PKGINT_ARGS: Incorrect argument count for package ’[chars]’, operation ’[chars]’: [dec] not [dec]

Explanation An error has occurred loading the command set for a newly installed package. The package is not compatible with the running IOS instance.

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

Error Message %DYNCMD-3-PKGINT_DIR_CREATE : Package integration failed to create directory: [chars] ([chars])

Explanation An error has occurred when attempting to create a package export directory. This should never fail.

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

Error Message %DYNCMD-3-PKGINT_DIR_MOVE : Package integration failed to move directory: [chars] to [chars] ([chars])

Explanation An error has occurred when attempting to move a package export directory. This should never fail.

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

Error Message %DYNCMD-3-PKGINT_DIR_OPEN : Package integration failed to open directory: [chars] ([chars])

Explanation An error has occurred when attempting to open a package export directory. This should never fail.

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

Error Message %DYNCMD-3-PKGINT_DIR_REMOVE : Package integration failed to remove directory: [chars] ([chars])

Explanation An error has occurred when attempting to remove a package export directory. This should never fail.

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

Error Message %DYNCMD-3-PKGINT_FILE_OPEN : Package integration failed to open file: [chars] ([chars])

Explanation An error has occurred when attempting to open a file in a package export directory. This should never fail.

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

Error Message %DYNCMD-3-PKGINT_FILE_REMOVE : Package integration failed to remove: [chars] ([chars])

Explanation An error has occurred when attempting to remove a package export file. This should never fail.

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

Error Message %DYNCMD-3-PKGINT_INSTALL: Failed to install ’[chars]’: [chars]

Explanation Some features’ configuration depends on a packaging infrastructure. Packaged configuration for the specified package will be unavailable.

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

Error Message %DYNCMD-3-PKGINT_LOAD: Failed to load ’[chars]’: [chars]

Explanation Some features’ configuration depends on a packaging infrastructure. Packaged configuration for the specified package will be unavailable.

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

Error Message %DYNCMD-3-PKGINT_LOCK: Failed to acquire package list lock for ’[chars]’: [chars]

Explanation An error occurred when a configuration package was being installed or removed. This may indicate a timeout which may be a temporary condition.

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

Error Message %DYNCMD-3-PKGINT_OFFSET: Invalid offset argument for package ’[chars]’, operation ’[chars]’: [chars] ([int])

Explanation An error has occurred loading the command set for a newly installed package. The package is not compatible with the running IOS instance.

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

Error Message %DYNCMD-3-PKGINT_PKGLOCK: [chars] failed to acquire package lock for ’[chars]’

Explanation An error occurred when locking a configuration package. The package needs to be locked for processing configuration commands or timer-based processing of configuration data.

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

Error Message %DYNCMD-3-PKGINT_SYMBOL: Package [chars] incompatible: symbol ’[chars]’ is of type [chars], expected [chars]