Guest

Support

Cisco IOS XE System Messages

Hierarchical Navigation

  • Viewing Options

  • PDF (6.7 MB)
  • Feedback
Cisco IOS XE System Messages

Table Of Contents

Cisco IOS XE System Messages

All Other Messages

ACE Messages

ACL Messages

ALG_COM Messages

ALG_PROXY Messages

ARL_PROXY Messages

ASR1000_APPLIANCE Messages

ASR1000_APS Messages

ASR1000_DSP Message

ASR1000_ETHERCHAN Messages

ASR1000_LICENSE Messages

ASR1000_MEMPOOL Messages

ASR1000_MGMTVRF Messages

ASR1000_MMON Messages

ASR1000_OIR Messages

ASR1000_PEM Messages

ASR1000_PROCMIB Messages

ASR1000_RP Messages

ASR1000_RP_ATM_SPA Messages

ASR1000_RP_CFG_NOT Messages

ASR1000_RP_CTE1_SPA Messages

ASR1000_RP_DIAG_TEST Messages

ASR1000_RP_DPIDB Messages

ASR1000_RP_IF_FLOW_IDS Messages

ASR1000_RP_MGMTE Messages

ASR1000_RP_ONLINE_DIAG Messages

ASR1000_RP_POS_SPA Messages

ASR1000_RP_SONET_ALARM Messages

ASR1000_RP_SPA Messages

ASR1000_RP_VTYMGT Messages

ASR1000_SCHED Messages

ASR1000_SERVICE_ENGINE Messages

ASR1000_SIP_CTE1_SPA Messages

ASR1000_SIP_POS_SPA Messages

ASR1000_SIP_SPA Messages

ASR1000_SPA Messages

ASR1000_SPA_ETHER Messages

ASR1000_VMAN Messages

ASR1000_WD Messages

ATMSPA Messages

ATTN Messages

BACKUP_INTERFACES Messages

BFD_MAP Messages

BINOS_LOGIN Messages

BIPC Messages

BOOT Messages

BSHELL Messages

CCE Messages

CEF_PROXY Messages

CFC_LISP Messages

CFT Messages

CGC Messages

CGM Messages

CHASFS Messages

CHUNK Messages

CISL Messages

CLOCK_RECOVERY Messages

CMAN_IDPROM_ENVMON Messages

CMANCC Messages

CMANRP Messages

CMCC Messages

CMFP Messages

CMRP Messages

CMRP_ENVMON Messages

CMRP_PFU Messages

CPPBQS Messages

CPPDRV Messages

CPPEXMEM Messages

CPPFPM Messages

CPPHA Messages

CPP_BQS Messages

CPP_FM Messages

CPP_FR Messages

CPP_IPHC_PROXY Messages

CPP_LDN Messages

CPP_MLP Messages

CPP_NAT_PROXY Messages

CPP_PFR_PROXY Messages

CPPOSLIB Messages

CPPTCAMRM Messages

CRYTO Messages

CTS Messages

DATA_DESCR Messages

DMB Messages

DROP Messages

DWL Messages

DYNCMD Messages

E_CFM Messages

ECFM_HSBY Messages

EMD Messages

ENVIRONMENT Messages

ENVIRONMENTAL Messages

ERM Messages

ERSPAN Messages

ESF Messages

ESS_FEATURE Messages

ESS_IPSUB Messages

ESS_PROXY Messages

ESS_SWITCH Messages

ETHERNET_PMLACP Messages

ETH_SPA_GEN Messages

ETH_SPA_GILA Messages

ETH_SPA_MAC Messages

EXLOG Messages

EVTMON_PROXY Messages

FAKED Messages

FLEXVPN Messages

FMANFP Messages

FMANRP Messages

FMANRP_ACL Messages

FMANRP_ADJ Messages

FMANRP_CCE Messages

FMANRP_CEF Messages

FMANRP_ESS Messages

FMANRP_FPM Messages

FMANRP_IPHC Messages

FMANRP_IPSEC Messages

FMANRP_MCAST Messages

FMANRP_MFR Messages

FMANRP_MLP Messages

FMANRP_MPLS Messages

FMANRP_NAT Messages

FMANRP_NAT64 Messages

FMANRP_NBAR Messages

FMANRP_NETFLOW Messages

FMANRP_OBJID Messages

FMANRP_PBR Messages

FMANRP_PFR Messages

FMANRP_QOS Messages

FMANRP_RTMAP Messages

FMANRP_SSLVPN Messages

FMANRP_URPF Messages

FMANRP_VRF Messages

FMANRP_WCCP Messages

FMANRP_ZONES Messages

FMFP Messages

FMFP_ACL Messages

FMFP_QOS Messages

FMFP_URPF Messages

FNF Messages

FNF_PROXY Messages

FRAG Messages

FRAG_DESC_PROXY Messages

FTP_ALG Messages

FTP64_ALG Messages

FW Messages

FWALL Messages

FWALL_PROXY Messages

GEN_PROXY Messages

H323_ALG Messages

HA_EM Messages

HA_PROXY Messages

HAL Messages

HARDWARE Messages

HMAN Messages

HW_IDPROM_ENVMON Messages

HW_PFU Messages

IMAP Messages

IMCC Messages

IMGR Messages

IMRP Messages

INFRA Messages

INTERCHASSIS_REDUNDANCY Messages

IOS_LICENSE Messages

IOSD Messages

IOSD_IMCC_CAPI Messages

IOSXE_APS Messages

IOSXE_DSP Messages

IOSXE_ETHERCHAN Messages

IOSXE_FMANRP Messages

IOSXE_IMCC_CAPI Messages

IOSXE_INFRA Messages

IOSXE_LICENSE_BOOT_CLI Messages

IOSXE_LMANRP Messages

IOSXE_MEMPOOL_MIB Messages

IOSXE_MLP Messages

IOSXE_MMON Messages

IOSXE_OIR Messages

IOSXE_PEM Messages

IOSXE_PROCMIB Messages

IOSXE_RP_CFG_NOT Messages

IOSXE_RP_DIAG_TEST Messages

IOSXE_RP_DPIDB Messages

IOSXE_RP_IF_FLOW_IDS Messages

IOSXE_RP_MGMTE Messages

IOSXE_RP_NV Messages

IOSXE_RP_ONLINE_DIAG Messages

IOSXE_RP_SPA Messages

IOSXE_RP_VTYMGT Messages

IOSXE_SCHED Messages

IOSXE_SERVICE_ENGINE Messages

IOSXE_SIP_SPA Messages

IOSXE_SPA Messages

IOSXE_TIMESTAMP_ENGINE Messages

IOSXE_VIRT_INSTANCE Messages

IOSXE_VMAN Messages

IOSXE_WCCP Messages

IOSXE_WD Messages

IPC Messages

IPC_LOG Messages

IPRT Messages

IPSEC Messages

IPV4_Forwarding Messages

IPV4_REASS_PROXY Messages

IPV4_URPF Messages

IPV4_VFR Messages

IPV4MCAST Messages

IPv6_CLI Messages

IPV6_FORWARDING Messages

IPV6_POLICY_API Messages

IPV6MCAST Messages

IPV6_REASS_PROXY Messages

IPV6_URPF Messages

IPV6_VFR Messages

ISISL2 Messages

ISSU Messages

KEYSTORE Messages

L2BD Messages

L4 Messages

LAYER2 Messages

LDP Messages

LI Messages

LIC_AGENT Messages

LIIN Messages

LOGGER Messages

LUA_VM Messages

MBOX Messages

MCP_SYS Messages

MCT1E1 Messages

MEM_MGR Messages

MEM_PROXY Messages

MLRIB Messages

MONITOR Messages

MSG_POS_OC3_OC12_SPA Messages

MX Messages

NAT Messages

NAT64 Messages

NET_CLK_SEL Messages

NETCLK Messages

NILE Messages

OBJGROUP Messages

OCE_FORWARDING Messages

OOM Messages

OTV_APP Messages

OUTPUT_CLK_SEL Messages

PA_PKT Messages

PA_PKT_PROXY Messages

PAM_UPDB Messages

PBUF Messages

PERF_MONITOR_RESOURCE Messages

PERF_TRAFFIC_INFRA Messages

PERF_TRAFFIC_METER Messages

PERF_TRAFFIC_REACT Messages

PKTLOG Messages

PLATFORM Messages

PLATFORM_ENV Messages

PLATFORM_IPV6HOST Messages

PLATFORM_IPv6_UCAST Messages

PLATFORM_NCEF Messages

PLATFORM_NETWORK_CLOCK Messages

PLATFORM_SCC Messages

PLATFORM_UCAST Messages

PLOGDRP Messages

PLU_PROXY Messages

PMAN Messages

POP Messages

PPROT_FSM Messages

PPROT_L3_TRIG Messages

PQ3_TSEC Messages

PTP Messages

PW Messages

QFP_ETH Messages

QFP_FNF Messages

QFP_MLP Messages

QFP_TUN Messages

QFP_XCONNECT Messages

QFPOOR Messages

QOS Messages

RCMD_ALG Messages

RF Messages

RG_AR Messages

RBM Messages

RTSP Messages

SBC Messages

SBC_MPS Messages

SBC_SPF Messages

SCC Messages

SCOOBY Messages

SCCP Messages

SDP Messages

SERIAL_12IN1 Messages

SERVICES Messages

SIP Messages

SM Messages

SMAN Messages

SMANRP Messages

SMTP Messages

SP_MONITOR Messages

SPA Messages

SPA_ATM_ENABLER Messages

SPA_CCB Messages

SPA_CHOCX Messages

SPA_CHOCX_DSX Messages

SPA_CHOCX_MCPRP Messages

SPA_CONSOLE Messages

SPA_CT3 Messages

SPA_DATABUS Messages

SPA_EEPROM Messages

SPA_FPD Messages

SPA_GE_DWDM Messages

SPA_HA Messages

SPA_MIB Messages

SPA_OIR Messages

SPA_PLIM Messages

SPA_PLUGIN Messages

SPA_SE1 Messages

SPA_SRVCS_ENGINE Messages

SPA_SRVCS_IF Messages

SPA_T3E3 Messages

SPA_TDMIM Messages

SPA_WMA Messages

SPACP Messages

SRW Messages

SSL Messages

STILE Messages

SUDI Messages

SUNRPC Messages

SW_MATM Messages

SYSPLAT Messages

TCP Messages

THREAT_DEFENSE Messages

TIME Messages

TODCLK Messages

TTYMON Messages

UI Messages

UICFGEXP Messages

UIPEER Messages

VMAN Messages

VPN Messages

VTCP Messages

VXE_VNIC_IF Messages

WUILOGIN Messages

XDR Messages

XMCP Messages


Cisco IOS XE System Messages


This chapter contains the system messages for Cisco IOS XE software. The messages are grouped according to the following facility names:

All Other Messages

ACE Messages

ACL Messages

ALG_COM Messages

ALG_PROXY Messages

ARL_PROXY Messages

ASR1000_APPLIANCE Messages

ASR1000_APS Messages

ASR1000_DSP Message

ASR1000_ETHERCHAN Messages

ASR1000_LICENSE Messages

ASR1000_MEMPOOL Messages

ASR1000_MGMTVRF Messages

ASR1000_MMON Messages

ASR1000_OIR Messages

ASR1000_PEM Messages

ASR1000_PROCMIB Messages

ASR1000_RP Messages

ASR1000_RP_ATM_SPA Messages

ASR1000_RP_CFG_NOT Messages

ASR1000_RP_CTE1_SPA Messages

ASR1000_RP_DIAG_TEST Messages

ASR1000_RP_DPIDB Messages

ASR1000_RP_IF_FLOW_IDS Messages

ASR1000_RP_MGMTE Messages

ASR1000_RP_ONLINE_DIAG Messages

ASR1000_RP_POS_SPA Messages

ASR1000_RP_SONET_ALARM Messages

ASR1000_RP_SPA Messages

ASR1000_RP_VTYMGT Messages

ASR1000_SCHED Messages

ASR1000_SERVICE_ENGINE Messages

ASR1000_SIP_CTE1_SPA Messages

ASR1000_SIP_POS_SPA Messages

ASR1000_SIP_SPA Messages

ASR1000_SPA Messages

ASR1000_SPA_ETHER Messages

ASR1000_VMAN Messages

ASR1000_WD Messages

ATMSPA Messages

ATTN Messages

BACKUP_INTERFACES Messages

BFD_MAP Messages

BINOS_LOGIN Messages, page 150

BIPC Messages

BOOT Messages

BSHELL Messages

CCE Messages

CEF_PROXY Messages

CFC_LISP Messages

CFT Messages

CGC Messages

CGM Messages

CHASFS Messages

CHUNK Messages, page 161

CISL Messages

CLOCK_RECOVERY Messages

CMAN_IDPROM_ENVMON Messages

CMANCC Messages

CMANRP Messages

CMCC Messages

CMFP Messages

CMRP Messages

CMRP_ENVMON Messages

CMRP_PFU Messages

CPPBQS Messages

CPPDRV Messages

CPPEXMEM Messages

CPPFPM Messages

CPPHA Messages

CPP_BQS Messages

CPP_FR Messages

CPP_IPHC_PROXY Messages

CPP_LDN Messages

CPP_MLP Messages

CPP_NAT_PROXY Messages

CPP_PFR_PROXY Messages

CPPOSLIB Messages

CPPTCAMRM Messages

CRYTO Messages

CTS Messages

DATA_DESCR Messages

DMB Messages

DROP Messages

DWL Messages

DYNCMD Messages

E_CFM Messages

ECFM_HSBY Messages

EMD Messages, page 262

ENVIRONMENT Messages

ENVIRONMENTAL Messages

ERM Messages

ERSPAN Messages

ESF Messages

ESS_FEATURE Messages

ESS_IPSUB Messages

ESS_PROXY Messages

ESS_SWITCH Messages

ETHERNET_PMLACP Messages

ETH_SPA_GEN Messages

ETH_SPA_GILA Messages

ETH_SPA_MAC Messages

EXLOG Messages

EVTMON_PROXY Messages

FAKED Messages

FLEXVPN Messages

FMANFP Messages

FMANRP Messages

FMANRP_ACL Messages

FMANRP_ADJ Messages

FMANRP_CCE Messages

FMANRP_CEF Messages

FMANRP_ESS Messages

FMANRP_FPM Messages

FMANRP_IPHC Messages

FMANRP_IPSEC Messages

FMANRP_MCAST Messages

FMANRP_MFR Messages

FMANRP_MLP Messages, page 305

FMANRP_MPLS Messages

FMANRP_NAT Messages

FMANRP_NAT64 Messages

FMANRP_NBAR Messages

FMANRP_NETFLOW Messages

FMANRP_OBJID Messages

FMANRP_PBR Messages

FMANRP_PFR Messages

FMANRP_QOS Messages

FMANRP_RTMAP Messages

FMANRP_SSLVPN Messages

FMANRP_URPF Messages

FMANRP_VRF Messages

FMANRP_WCCP Messages

FMANRP_ZONES Messages

FMFP Messages

FMFP_ACL Messages

FMFP_QOS Messages

FMFP_URPF Messages

FNF Messages

FNF_PROXY Messages

FRAG Messages

FRAG_DESC_PROXY Messages

FTP_ALG Messages

FTP64_ALG Messages

FW Messages

FWALL Messages

FWALL_PROXY Messages

GEN_PROXY Messages

H323_ALG Messages

HA_EM Messages

HA_PROXY Messages

HAL Messages

HARDWARE Messages

HMAN Messages

HW_IDPROM_ENVMON Messages

HW_PFU Messages

IMAP Messages

IMCC Messages

IMGR Messages

IMRP Messages

INFRA Messages

INTERCHASSIS_REDUNDANCY Messages

IOS_LICENSE Messages

IOSD Messages

IOSD_IMCC_CAPI Messages

IOSXE_APS Messages

IOSXE_DSP Messages

IOSXE_ETHERCHAN Messages

IOSXE_FMANRP Messages

IOSXE_IMCC_CAPI Messages

IOSXE_INFRA Messages

IOSXE_LICENSE_BOOT_CLI Messages

IOSXE_LMANRP Messages

IOSXE_MEMPOOL_MIB Messages

IOSXE_MLP Messages

IOSXE_MMON Messages

IOSXE_OIR Messages

IOSXE_PEM Messages

IOSXE_PROCMIB Messages

IOSXE_RP_CFG_NOT Messages

IOSXE_RP_DIAG_TEST Messages

IOSXE_RP_DPIDB Messages

IOSXE_RP_IF_FLOW_IDS Messages

IOSXE_RP_MGMTE Messages

IOSXE_RP_NV Messages

IOSXE_RP_ONLINE_DIAG Messages

IOSXE_RP_SPA Messages

IOSXE_RP_VTYMGT Messages

IOSXE_SCHED Messages

IOSXE_SERVICE_ENGINE Messages

IOSXE_SIP_SPA Messages

IOSXE_SPA Messages

IOSXE_TIMESTAMP_ENGINE Messages

IOSXE_VIRT_INSTANCE Messages

IOSXE_VMAN Messages

IOSXE_WCCP Messages

IOSXE_WD Messages

IPC Messages

IPC_LOG Messages

IPRT Messages

IPSEC Messages, page 577

IPV4_Forwarding Messages

IPV4_REASS_PROXY Messages

IPV4_URPF Messages

IPV4_VFR Messages

IPV4MCAST Messages

IPv6_CLI Messages

IPV6_FORWARDING Messages

IPV6_POLICY_API Messages

IPV6MCAST Messages

IPV6_REASS_PROXY Messages

IPV6_URPF Messages

IPV6_VFR Messages

ISISL2 Messages

ISSU Messages

KEYSTORE Messages

L2BD Messages

L4 Messages

LAYER2 Messages

LDP Messages

LI Messages

LIC_AGENT Messages

LIIN Messages

LOGGER Messages

LUA_VM Messages

MBOX Messages

MCP_SYS Messages

MCT1E1 Messages

MEM_MGR Messages

MEM_PROXY Messages

MLRIB Messages

MONITOR Messages

MSG_POS_OC3_OC12_SPA Messages

MX Messages

NAT Messages

NAT64 Messages

NET_CLK_SEL Messages

NETCLK Messages

NILE Messages

OBJGROUP Messages

OCE_FORWARDING Messages

OOM Messages

OUTPUT_CLK_SEL Messages

PA_PKT Messages

PA_PKT_PROXY Messages

PAM_UPDB Messages

PBUF Messages

PERF_MONITOR_RESOURCE Messages

PERF_TRAFFIC_INFRA Messages

PERF_TRAFFIC_METER Messages

PERF_TRAFFIC_REACT Messages

PKTLOG Messages

PLATFORM Messages

PLATFORM_ENV Messages

PLATFORM_IPV6HOST Messages

PLATFORM_IPv6_UCAST Messages

PLATFORM_NCEF Messages

PLATFORM_NETWORK_CLOCK Messages

PLATFORM_SCC Messages

PLATFORM_UCAST Messages

PLOGDRP Messages

PLU_PROXY Messages

PMAN Messages

POP Messages

PPROT_FSM Messages

PPROT_L3_TRIG Messages

PQ3_TSEC Messages

PW Messages

QFP_ETH Messages

QFP_FNF Messages

QFP_MLP Messages

QFP_TUN Messages

QFP_XCONNECT Messages

QFPOOR Messages

QOS Messages

RCMD_ALG Messages

RF Messages

RG_AR Messages

RBM Messages

RTSP Messages

SBC Messages

SBC_MPS Messages

SBC_SPF Messages

SCC Messages

SCOOBY Messages

SCCP Messages

SDP Messages

SERIAL_12IN1 Messages

SERVICES Messages

SIP Messages

SM Messages

SMAN Messages

SMANRP Messages

SMTP Messages

SP_MONITOR Messages

SPA Messages

SPA_ATM_ENABLER Messages

SPA_CCB Messages

SPA_CHOCX Messages

SPA_CHOCX_DSX Messages

SPA_CHOCX_MCPRP Messages

SPA_CONSOLE Messages

SPA_CT3 Messages

SPA_DATABUS Messages

SPA_EEPROM Messages

SPA_FPD Messages

SPA_GE_DWDM Messages

SPA_HA Messages

SPA_MIB Messages

SPA_OIR Messages

SPA_PLIM Messages

SPA_PLUGIN Messages

SPA_SE1 Messages

SPA_SRVCS_ENGINE Messages

SPA_SRVCS_IF Messages

SPA_T3E3 Messages

SPA_TDMIM Messages

SPA_WMA Messages

SPACP Messages

SRW Messages

SSL Messages

STILE Messages

SUDI Messages

SUNRPC Messages

SW_MATM Messages

SYSPLAT Messages

TCP Messages

THREAT_DEFENSE Messages

TIME Messages

TODCLK Messages

TTYMON Messages

UI Messages

UICFGEXP Messages

UIPEER Messages

VMAN Messages

VPN Messages

VTCP Messages

VXE_VNIC_IF Messages

WUILOGIN Messages

XDR Messages

XMCP Messages

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_MMON Messages

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

Explanation    An empty file at first, place holder for SHIM errors

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cisco/psn/bssprt/bss. If you still require assistance, open a case with the Technical Assistance Center via the Internet 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_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 subslotslot#/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 subslotslot#/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 subslotslot#/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.

CISL Messages

Error Message    %CISL-1-DEVICE_CERT_NOT_PRESENT: Device Certificate used for licensing 
is not present 

Explanation    Device Certificate Not 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 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.

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 cl