Table Of Contents
C6K_MWAM_CENTRALIZED_CONFIG Messages
C6K_SAMI_CENTRALIZED_CONFIG Messages
DHCP_SNOOPING_CAT3550 Messages
C6K_IVRF Messages
The following are C6K internal IVRF messages.
Error Message%C6K_IVRF-3-C6K_IVRF_ERROR : [chars]
Explanation VRF infrastructure failure for Platform's IVRFs.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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.C6K_MPLS_LC Messages
The following are Cisco 7600 Catalyst 6500 MPLS SP or line card messages.
Error Message%C6K_MPLS_LC-3-INVALID_HWAPI_EVENT : Invalid HWAPI event: [chars]
Explanation The event received for the Output Chain Element is incorrect or inconsistent. This could be a transient condition or a software issue in programming the cef/mpls table.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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. Also provide all the network events like changes to the configuration, interface flap, IGP flap, LDP flap, etc. when this error message occurred.Error Message%C6K_MPLS_LC-3-TCAMFAIL : Failed to insert label [dec] to TCAM. Some MPLS packets might be dropped.
Use "mls cef maximum-routes" to modify the TCAM partition or/and consider a hardware upgrade.
Examine the network and collect the necessary information from this setup.
The only way to recover from this state is by reloading the router.Explanation The system failed to allocate a TCAM entry for the specified label for MPLS. The TCAM might be full. Some MPLS packets might be dropped. Enter the mls cef maximum-routes command to modify the TCAM partition or/and consider a hardware upgrade. Examine the network and collect the necessary information from this setup. The only way to recover from this state is by reloading the router.
Recommended Action Reduce the number of routes in the system to free up TCAM space. When you are sure there is enough free TCAM space available, reload the box.
Error Message%C6K_MPLS_LC-3-LABEL_STACK_SIZE : Label [[dec]] is not added to label stack. Current label stack is [[dec] [dec] [dec] [dec] [dec]]
Explanation The label specified in the system message is not added to the label stack bacuase the stack already contains the maximum number of allowed labels. System can not forward data correctly. This condition is caused by an internal software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach 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 message.
Error Message%C6K_MPLS_LC-3-OCE_ERROR : Invalid OCE [[chars]] [hex]
Explanation The Output Chain Element(OCE) specified in the system message is invalid because it can not be processed. This issue can cause problem in data forwarding. This condition is caused by an internal software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%C6K_MPLS_LC-3-SIX_PE_REW_LBL_ENTRY_MISMATCH : The label entry([hex]) in the 6PE rewrite table for incoming label [dec] does not match the passed in label entry([hex])
Explanation The label entry in the 6PE rewrite table for an incoming label does not match the passed in label entry. This is an internal software error
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%C6K_MPLS_LC-5-TCAMEXPRECOVER : TCAM exception recovered for MPLS, traffic will be hardware switched
Explanation At some earlier point in time some of the MPLS forwarding table
couldn't fit into the hardware TCAM. Now the complete MPLS
forwarding table in hardware. Forwarding for the incoming MPLS
packets would be done in hardwareRecommended Action No action is required.
C6K_MPLS_RP Messages
The following are the C6K_MPLS_RP messages.
Error Message%C6K_MPLS_RP-3-BKWLK_FAIL : Backwalk fail ([chars]) [dec] [dec] / [dec]
Explanation Backwalk failed in the LSM replication chain
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%C6K_MPLS_RP-3-FIBIDB_MISMATCH : fibidb mismatch ([chars]) [dec] [dec] / [chars] / [chars]
Explanation FIDIDB mismatch in the LSM replication chain
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%C6K_MPLS_RP-3-FIBIDB_NOVLAN : fibidb has no vlan ([chars]) [dec] [chars]
Explanation FIDIDB has no VLAN in the LSM replication chain.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%C6K_MPLS_RP-2-INIT : [chars]
Explanation The initialization of the Constellation MPLS forwarding infrastructure failed. This will cause problem in the MPLS packet forwarding on the router. The router will be forced to crash to recover from the problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%C6K_MPLS_RP-3-INUSE_BADCNT : inuse count bad ([chars]) [dec] [dec] / [hex] / [dec]
Explanation The inuse count in the LSM replication chain is 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 Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%C6K_MPLS_RP-3-INUSE_BADPTR : inuse pointer mismatch ([chars]) [dec] [dec] / [hex] [hex] [hex] [hex] [hex] [hex]
Explanation There is an inuse pointer mismatch in the LSM replication chain.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%C6K_MPLS_RP-3-INVALID_OBJECT : Invalid object [chars] [dec] ([dec])
Explanation An invalid object found in the LSM replication chain.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%C6K_MPLS_RP-3-INVALID_VRFID : Invalid vrfid([dec]) for label([dec])
Explanation An invalid vrf id is received. The vrf id should be in the
range of 0 - 4095. This is an internal software error.Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%C6K_MWAM_CENTRALIZED_CONFIG-6-ABORT_CFG_DNLD : Aborting pending download of config from supervisor.
Explanation The processor was attempting to download its startup configuration from the supervisor engine, when mwam config-mode local was invoked.
Recommended Action No action is required.
Error Message%C6K_MWAM_CENTRALIZED_CONFIG-6-BEGIN_DOWNLOAD : Downloading config from supervisor
Explanation The processor has begun attempting to download its startup configuration from the supervisor engine rather than from local NVRAM.
Recommended Action No action is required.
Error Message%C6K_MPLS_RP-3-LSM_MAX_PEERS_EXCEEDED : Max peer count (5) exceeded for [chars]
Explanation There are more than 5 peers configured on a FIBIDB.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%C6K_MPLS_RP-3-NULL_FIBIDB : NULL fibidb ([chars]) [dec] [dec]
Explanation A NULL FIBIDB found in the LSM replication chain.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%C6K_MPLS_RP-3-NULL_OBJECT : NULL object ([chars]) [dec] [dec]
Explanation A NULL object found in the LSM replication chain.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%C6K_MPLS_RP-3-PENDING_QERR : pending queue error [chars] ([dec]) [dec]
Explanation The LSM replication VLAN allocation pending queue error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%C6K_MPLS_RP-3-PENDING_QFULL : pending queue full [chars] ([dec])
Explanation The LSM replication VLAN allocation pending queue is full.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%C6K_MPLS_RP-6-PORTCHAN_LOADBAL : Interface [chars] is now eligible for ingress loadbalancing
Explanation The Ingress load balancing is only supported on specific types of line card. If a port channel spans ports on both supported and unsupported line cards, the ingress load balance feature will be disabled for that port channel. The message indicates that all ineligible ports have been removed from the port channel and ingress load balancing is re-enabled.
Recommended Action No action is required.
Error Message%C6K_MPLS_RP-4-PORTCHAN_NOLOADBAL : Interface [chars] no longer eligible for ingress loadbalancing
Explanation The Ingress load balancing is only supported on specific types of line card. If a port channel spans ports on both supported and unsupported line cards, the ingress load balance feature will be disabled for that port channel. The message indicates that a port channel has been modified to include an ineligible port.
Recommended Action Remove ports that do not support ingress load balancing from the port channels displayed in the message.
Error Message%C6K_MPLS_RP-3-VLAN_FAIL : Vlan alloc fail ([chars]) [dec] [chars]
Explanation The VLAN allocation failed in the LSM replication chain.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%C6K_MPLS_RP-3-VLAN_MISMATCH : vlan mismatch ([chars]) [dec] [dec] [dec] [dec] [chars]
Explanation A VLAN mismatch has occurred in the LSM replication chain.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
C6K_MWAM_CENTRALIZED_CONFIG Messages
The following are Multiprocessor WAN Application Module (MWAM) centralized configuration messages.
%C6K_MWAM_CENTRALIZED_CONFIG-6-ABORT_CFG_DNLD : Aborting pending download of config from supervisor.
Explanation The processor was attempting to download its startup configuration from the supervisor engine, when mwam config-mode local was invoked.
Recommended Action No action is required.
Error Message%C6K_MWAM_CENTRALIZED_CONFIG-6-BEGIN_DOWNLOAD : Downloading config from supervisor
Explanation The processor has begun attempting to download its startup configuration from the supervisor engine rather than from local NVRAM.
Recommended Action No action is required.
Error Message%C6K_MWAM_CENTRALIZED_CONFIG-3-DNLD_ABORT_TIMEOUT : Timeout while waiting for download to abort
Explanation The processors on an MWAM will spend up to 30 mintues attempting to download their configurations from the supervisor engine in mwam config-mode supervisor. If during this time, the user invokes mwam config-mode local, an attempt will be made to abort the download from the supervisor engine. The CLI will block for up to 60 seconds while this attempt is made. If the download is not aborted within 60 seconds this message is logged.
Recommended Action Re-attempt the command mwam config-mode local. If this fails, wait out the 30 minutes until the download attempts stop and try again. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%C6K_MWAM_CENTRALIZED_CONFIG-5-DOWNLOAD_ABORTED : Aborted download of startup configuration from supervisor
Explanation The processor is configured for mwam config-mode supervisor. The processor was in the process of attempting to download its startup configuration from the supervisor engine. The user invoked mwam config-mode local. This interrupted the download process and set the processor to use NVRAM for its startup configuration. The current default running configuration has been written to NVRAM.
Recommended Action No action is required.
Error Message%C6K_MWAM_CENTRALIZED_CONFIG-6-DOWNLOAD_COMPLETE : Configuration retrieved from supervisor in slot [dec]
Explanation The processor has successfully retrieved its startup configuration from the supervisor engine in the indicated slot.
Recommended Action No action is required.
Error Message%C6K_MWAM_CENTRALIZED_CONFIG-2-DOWNLOAD_FAILED : Failed to download startup configuration from supervisor
Explanation The processor has failed to download its startup configuration from the supervisor engine. The processor will use the default configuration. The Gigabit Ethernet interface will be shutdown.
Recommended Action Fail functions over to an alternate processor or manually configure the processor from the console. Alternatively, the configuration might be downloaded manually from the supervisor engine with the command copy tftp://<supervisor-ip>/SLOTxPCy.cfg running-config, where <supervisor-ip> should be replaced with 128.0.0.1 if the active supervisor engine is in slot 1 and 128.0.0.2 for slot 2. In the filename SLOTxPCy.cfg, x should be replaced with the slot number of the MWAM and y should be replaced with the failed processor number. To correct the problem, verify that access to the configuration files on the supervisor engine has not been disabled. The configuration command no mwam bootflash access disables access. Verify that the supervisor engine image supports centralized configuration by attempting to manually configure mwam bootflash access. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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. Before contacting Cisco Technical Assistence Center, gather the following additional information:
- Determine if you can use the session to login to the processor that failed its download
- Collect the output from show module
- Collect the log from the supervisor engine as well as any affected MWAM processor
- On the supervisor engine enable debug tftp events and reload the processor that failed. Gather the output.Error Message%C6K_MWAM_CENTRALIZED_CONFIG-2-DOWNLOAD_TASK_FAILED : The MWAM centralized configuration download process failed to start
Explanation An internal error occurred which prevented a required process from starting. The configuration will not be downloaded from the supervisor engine. You will need to reload the processor. You might choose to run this processor in local mode until this problem is resolved.
Recommended Action Fail functions over to an alternate processor or manually configure the processor from the console. Alternatively, the configuration might be downloaded manually from the supervisor engine with the command copy tftp://<supervisor-ip>/SLOTxPCy.cfg running-config, where <supervisor-ip> should be replaced with 128.0.0.1 if the active supervisor engine is in slot 1 and 128.0.0.2 for slot 2. In the filename SLOTxPCy.cfg, x should be replaced with the slot number of the MWAM and y should be replaced with the failed processor number. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%C6K_MWAM_CENTRALIZED_CONFIG-6-INTERFACE_CHOSEN : Preparing internal interface [dec] for config retrieval.
Explanation In mwam config-mode supervisor, processor's 6 and 7 must choose an internal interface to use for downloading the configuration. This message records which interface was chosen.
Recommended Action No action required.
Error Message%C6K_MWAM_CENTRALIZED_CONFIG-3-INVALID_SLOT : Invalid slot: During [chars], slot/cpu number retrieved, [dec]/[dec], ROMMON might be out of date
Explanation The processor has determined that it is using an invalid slot or CPU number while attempting to retrieve configuration information from the supervisor engine.
Recommended Action Verify that the ROMMON is up to date. If it is not, then upgrade it, using upgrade rom-monitor on each processor complex on the MWAM card. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%C6K_MWAM_CENTRALIZED_CONFIG-6-MODE_CHANGED : mwam config-mode changed to [chars]
Explanation The mwam config-mode successfully changed.
Recommended Action No action is required.
Error Message%C6K_MWAM_CENTRALIZED_CONFIG-3-NV_DELETE_FAIL : Failed to delete local startup-config.
Explanation Deletion of local nvram failed. Continuing anyway
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%C6K_MWAM_CENTRALIZED_CONFIG-1-NV_EXCEEDED : Config file [chars] size ([int]) exceeds allowed size ([int]). Deleting local startup-config
Explanation There is not enough space in local nvram to save the configuration after reading from supervisor. Need to reduce size of configuration.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%C6K_MWAM_CENTRALIZED_CONFIG-3-NVRAM_CHANGE_FAILED : Write failed for: [chars], [chars]
Explanation When changing the configuration mode (config-mode) from supervisor to local, the running configuration is copied to nvram:startup-config. When changing the configuration mode from local to supervisor, the running configuration is copied to a file on the supervisor engine's bootflash. This copy operation failed.
Recommended Action If changing from config-mode supervisor to local, perform write erase, wait for the nvram to re-initialize, then retry. When changing from config-mode local to supervisor, verify that no bootflash access has not been configured on the supervisor engine. Verify that there is room on the bootflash of the supervisor engine, using squeeze if necessary. If the problem persists, gather the results of
-dir nvram: on the MWAM
-show bootflash: on the supervisor engine
-show running-config on the MWAM
-show running-config on the supervisor engine
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%C6K_MWAM_CENTRALIZED_CONFIG-3-UNEXPECTED_EVENT : Unexpected event while aborting download of config from supervisor: [dec]:[dec]
Explanation An unexpected internal event has occurred, which interfered with completing the config-mode change. Your system should operate normally otherwise.
Recommended Action Re-enter the command mwam config-mode local. If this fails, wait out the 30 minutes until the download attempts stop and try again. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%C6K_MWAM_CENTRALIZED_CONFIG-5-UPLD_FAILURE : Failed to upload config to [chars] on supervisor. slavebootflash:is hosted on the standby supervisor engine. Failure to write to the slavebootflash: might be safely ignored when there is no standby supervisor engine. Otherwise, check for space on supervisor, squeeze supervisor bootflash: and slavebootflash: as needed
Explanation The processor has failed to upload the running configuration to the indicated supervisor engine.
Recommended Action Verify that mwam bootflash access has not been disabled. Verify that there is space available on the supervisor engines's bootflash: and slavebootflash:. This might require deleting files or squeeze bootflash: from the supervisor engine's console. Failure to write to slavebootflash: is an error only if there is a standby supervisor in the chassis. slavebootflash: must be accessed from the console of the active supervisor engine. If this does not resolve the issue, verify that the internal communication with session slot <slot> processor <proc> command. If the session fails for all processors on the MWAM card, you might need to hw-module module <slot> reset the card to re-establish the communication paths.
Error Message%C6K_MWAM_CENTRALIZED_CONFIG-6-UPLD_SUCCESS : Success: config uploaded to supervisor [chars]
Explanation The processor has successfully uploaded the running configuration to the indicated supervisor engine.
Recommended Action No action is required.
Error Message%C6K_MWAM_CENTRALIZED_CONFIG-3-UPLOAD_FAILED : All writes to supervisor failed.
Explanation The attempt to save the configuration in while in supervisor mode failed
Recommended Action Verify that mwam bootflash access has not been disabled. Verify that there is space available on the supervisor engine's bootflash:. This might require deleting files or squeeze bootflash: from the supervisor engine's console. If this does not resolve the issue, verify that the internal communication with session slot <slot> processor <proc> command. If the session fails for all processors on the MWAM card, you might need to hw-module module <slot> reset the card to re-establish the communication paths. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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. Before contacting Cisco Technical Assistence Center, gather the following additional information:
- On the supervisor engine debug ip tcp rcmd. Set this same debug on the MWAM processor that failed and re-attempt to write memory from the processor which produced the failure. Gather the debug output on the supervisor engine's console and the MWAM processor console.
- On the supervisor engine, do show bootflash: and show slavebootflash:. Gather the output.
- On the supervisor engine, do dir bootflash: and dir slavebootflash:. Gather the output.
- On the supervisor engine and the MWAM processor gather the results of show running-config.
- On the MWAM processor gather the results of ping 128.0.0.1 and ping 128.0.0.2.Error Message%C6K_MWAM_CENTRALIZED_CONFIG-6-UPLOAD_SUCCEEDED : Config uploaded to [dec] supervisor file system(s)
Explanation The MWAM processor is in mwam config-mode supervisor and the configuration has been successfully saved to one or more supervisor engines.
Recommended Action If the number of supervisors indicated does not match the number installed, you might need to verify that the files on bootflash and slavebootflash of the supervisor engine are both up to date and take appropriate actions if not.
Possible actions:
- delete extra files and sqeeze the device where the file is not up to date
- save the configuration again or copy the file from one supervisor engine to the other by hand.C6K_SAMI_CENTRALIZED_CONFIG Messages
The following are Services and Application Module for IP (SAMI) centralized configuration messages.
Error Message%C6K_SAMI_CENTRALIZED_CONFIG-6-ABORT_CFG_DNLD : Aborting pending download of config from supervisor.
Explanation The processor was attempting to download its startup configuration from the supervisor engine, when sami config-mode local was invoked.
Recommended Action No Action is required.
Error Message%C6K_SAMI_CENTRALIZED_CONFIG-6-BEGIN_DOWNLOAD : Downloading config from supervisor
Explanation The processor has begun attempting to download its startup configuration from the supervisor engine rather than from local NVRAM.
Recommended Action No action is required.
Error Message%C6K_SAMI_CENTRALIZED_CONFIG-1-DNLD_ABORT_TIMEOUT : Timeout while waiting for download to abort
Explanation The processors on an SAMI will spend up to 1 mintues attempting to download their configurations from the supervisor engine in sami config-mode supervisor. If during this time, the user invokes sami config-mode local, an attempt will be made to abort the download from the supervisor engine. The CLI will block for up to 60 seconds while this attempt is made. If the download is not aborted within 60 seconds this message is logged.
Recommended Action Re-attempt the command sami config-mode local. If this fails, wait out the 1 minutes until the download attempts stop and try again.
Error Message%C6K_SAMI_CENTRALIZED_CONFIG-6-DOWNLOAD_COMPLETE : Configuration retrieved from [chars]
Explanation The processor has successfully retrieved its startup configuration from the supervisor engine in the indicated slot.
Recommended Action No action is required.
Error Message%C6K_SAMI_CENTRALIZED_CONFIG-2-DOWNLOAD_FAILED : Failed to download startup configuration from [chars]
Explanation The processor has failed to download its startup configuration from the supervisor engine. The processor will use the default configuration.
Recommended Action Fail functions over to an alternate processor or manually configure the processor from the console. Alternatively, the configuration may be downloaded manually from the supervisor endgine with the command copy tftp://<supervisor-ip>/SLOTxSAMICy.cfg running-config, where <supervisor-ip> should be replaced with 127.0.0.<sup slot>1 for the active supervisor and 127.0.0.<sup slot>2 for standby supervisor. In the filename SLOTxSAMICy.cfg, x should be replaced with the slot number of the SAMI and y should be replaced with the failed processor number. To correct the problem, verify that access to configuration files on the supervisor engine has not been disabled. The configuration command no sami bootflash access disables access. Verify that the supervisor engine image supports centralized configuration by attempting to manually configure sami bootflash access.
Error Message%C6K_SAMI_CENTRALIZED_CONFIG-2-DOWNLOAD_TASK_FAILED : The SAMI centralized configuration download process failed to start
Explanation An internal error occurred which prevented a required process from starting. The configuration will not be downloaded from the supervisor engine. You will need to reload the processor. You may choose to run this processor in local mode until this problem is resolved.
Recommended Action Fail functions over to an alternate processor or manually configure the processor from the console. Alternatively, the configuration may be downloaded manually from the supervisor engine with the command copy tftp://<supervisor-ip>/SLOTxSAMICy.cfg running-config, where <supervisor-ip> should be replaced with 127.0.0.<sup slot>1 for the active supervisor and 127.0.0.<sup slot>2 for the standby supervisor. In the filename SLOTxSAMICy.cfg, x should be replaced with the slot number of the SAMI and y should be replaced with the failed processor number.
Error Message%C6K_SAMI_CENTRALIZED_CONFIG-1-INVALID_SLOT : Invalid slot: slot/cpu number retrieved, [dec]/[dec], ROMMON may be out of date
Explanation The processor has determined that it is using an invalid slot or CPU number while attempting to retrieve configuration information from the supervisor engine.
Recommended Action Verify that the ROMMON is up to date. If it is not, then upgrade it, using upgrade rom-monitor on each processor complex on the SAMI card.
Error Message%C6K_SAMI_CENTRALIZED_CONFIG-6-MODE_CHANGED : sami config-mode changed to [chars]
Explanation The SAMI config-mode has successfully changed.
Recommended Action No action is required.
Error Message%C6K_SAMI_CENTRALIZED_CONFIG-3-NV_DELETE_FAIL : Failed to delete local startup-config.
Explanation Deletion of local nvram failed. Continuing anyway
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%C6K_SAMI_CENTRALIZED_CONFIG-1-NV_EXCEEDED : Config file [chars] size ([int]) exceeds allowed size ([int]). Deleting local startup-config
Explanation There is not enough space in local nvram to save the config after reading from supervisor. Need to reduce size of config.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%C6K_SAMI_CENTRALIZED_CONFIG-3-NVRAM_CHANGE_FAILED : Write failed for: [chars], [chars]
Explanation When changing the configuration mode (config-mode) from supervisor to local, the running configuration is copied to nvram:startup-config. When changing the configuration mode from local to supervisor, the running configuration is copied to a file on the supervisor engine's bootflash. This copy operation failed.
Recommended Action If changing from config-mode supervisor to local perform write erase, wait for the nvram to re-initialize, then retry. When changing from config-mode local to supervisor, verify that no bootflash access has not been configured on the supervisor engine. Verify that there is room on the bootflash of the supervisor engine, using squeeze if necessary. If the problem persists, gather the results of
-dir nvram: on the SAMI
-show bootflash: on the supervisor engine
-show running-config on the SAMI
-show running-config on the supervisor engineError Message%C6K_SAMI_CENTRALIZED_CONFIG-3-UNEXPECTED_EVENT : Unexpected event while aborting download of config from supervisor: [dec]:[dec]
Explanation An unexpected internal event has occurred, which interfered with completing the config-mode change. Your system should operate normally otherwise.
Recommended Action Re-attempt the command sami config-mode local. If this fails, wait out the 1 minutes until the download attempts stop and try again.
Error Message%C6K_SAMI_CENTRALIZED_CONFIG-1-UPLD_FAILURE_ACTIVE : Failed to upload [chars] to [chars]. See any prior error messages provided by ifs/rcp. For out of space problems, try squeezing supervisor [chars]
Explanation The processor has failed to upload to the indicated supervisor engine.
Recommended Action Verify that sami bootflash access has not been disabled. Verify that there is space available on thesupervisor engines's bootflash: or bootdisk: whichever is appropriate This may require deleting files and if bootflash: is being usedsqueeze bootflash: from the supervisor engine's console. If this does not resolve the issue, verify that the internal communication with session slot <slot> processor <proc> command. If the session fails for all processors on the SAMI card, you may need to hw-module module <slot> reset the card to re-establish the communication paths. If its a NULL config upload during write erase, configuration files can be manually deleted from the supervisor engine.
Error Message%C6K_SAMI_CENTRALIZED_CONFIG-4-UPLD_FAILURE_STDBY : Failed to upload [chars] to [chars].
[chars] is hosted on the standby supervisor engine. Failure to write to slavebootflash: or slavebootdisk: may be safely ignored when there is no standby supervisor engine. Otherwise, this should be considered as an error. See any prior error messages provided by ifs/rcp. For out of space problems, try squeezing supervisor slavebootflash:Explanation The processor has failed to upload to the indicated supervisor engine.
Recommended Action Verify that sami bootflash access has not been disabled. Verify that there is space available on the standby supervisor engines's slavebootflash: or slavebootdisk: whichever appropriate. Failure to write to slavebootxxxx: is an error only if there is a standby supervisor engine in the chassis.slavebootflash: or slavebootdisk: must be accessed from the console of the active supervisor engine. If this does not resolve the issue, verify that the internal communication with session slot <slot> processor <proc> command. If the session fails for all processors on the SAMI card, you may need to hw-module module <slot> reset the card to re-establish the communication paths. If its a NULL config upload during write erase, configuration files can be manually deleted from the supervisor engine.
Error Message%C6K_SAMI_CENTRALIZED_CONFIG-6-UPLD_SUCCESS : Success: [chars] uploaded to supervisor [chars]
Explanation The processor has successfully uploaded to the indicated supervisor engine.
Recommended Action No action is required.
Error Message%C6K_SAMI_CENTRALIZED_CONFIG-1-UPLOAD_FAILED : All writes for [chars] to supervisor failed.
Explanation The attempt to write the said file while in supervisor mode failed
Recommended Action Verify that sami bootflash access has not been disabled. Verify that there is space available on the supervisor engine's bootflash: or bootdisk: whichever appropriate. This may require deleting files or squeeze bootflash: from the supervisor engine's console. If this does not resolve the issue, verify that the internal communication with session slot <slot> processor <proc> command. If the session fails for all processors on the SAMI card, you may need to hw-module module <slot> reset the card to re-establish the communication paths.
Error Message%C6K_SAMI_CENTRALIZED_CONFIG-6-UPLOAD_SUCCEEDED : [chars] uploaded to [dec] supervisor file system(s)
Explanation The SAMI processor is in sami config-mode supervisor and the said file has been successfully saved to one or more supervisor engines. If the number of supervisors indicated doesn't match the number installed, the user may need to verify that the files on bootflash and slavebootflash of the supervisor engine are both up to date and take appropriate actions if not. Possible actions:
- delete extra files and sqeeze the device where the file is not up to date
- save the configuration again or copy or delete the file from one supervisor engine to the other by handRecommended Action No action is required.
C7304_RP Messages
The following are NP (NSE-100/NSE-150/NPE-G100) messages.
Error Message%C7304_RP-2-CLK_DOM : [chars] clock domain not ready.
Explanation A hardware clock domain on the RP (Route Processor) did not indicate that it was ready. Without all the clocks on the RP the router cannot be fully used and will come up in minimal boot mode. These failures can originate from corrupted FPGA (Field Programmable Gate Array) images on the RP. FPGA images can get corrupted when an RP FPGA upgrade is interrupted/terminated before it could complete.
Recommended Action The router will come up in minimal boot mode and the only interface that can be used then is the management port. Retry the FPGA upgrade. The command to start the FPGA upgrade is upgrade fpga all. After successfully completing the FPGA upgrade, reload the router so it can come up in normal mode. If the FPGA upgrade does not solve the problem, then the problem is most likely a hardware issue. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%C7304_RP-2-CPLD_ACC : CPLD access failed to [chars], mask [hex], register [hex]
Explanation The CPLD logic device needed to be accessed to perform the indicated action in order to apply the specified mask value to the specified CPLD register. This access failed. A consequence of that failure can be that parts of the router are not working.
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%C7304_RP-2-CPLD_RW : Could not [chars] CPLD (register [hex]).
Explanation The CPLD (Complex Programmable Logic Device) on the RP (Route Processor) could not be read or written (see error message) to access the indicated register.
Recommended Action Reload the router and if the problem occurs frequently this could be a hardware issue. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%C7304_RP-2-FPGA_NOT_UP : [chars].
Explanation One or more FPGAs (Field Programmable Gate Arrays) on the RP (Route Processor) have not come up when the system was started. The affected FPGA is indicated in the error message. The typical reason for such failures is that the FPGA upgrade on the RP got interrupted/terminated before it could complete. This can happen due to power loss or due to unexpected router reloads.
Recommended Action The router will come up in minimal boot mode and the only interface that can be used then is the management port. Retry the FPGA upgrade. The command to start the FPGA upgrade is upgrade fpga all. After successfully completing the FPGA upgrade, reload the router so it can come up in normal mode. If the FPGA upgrade does not solve the problem then the problem is most likely a hardware issue. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%C7304_RP-2-MINB : System in minimal boot mode due to monitor variable '[chars]'.
Explanation The router is in minimal boot mode because ROM monitor has a variable called 'MINB' set to a non-zero value. This must have come from a manual intervention and needs to be undone now.
Recommended Action Enter ROM monitor on the router either by using a config-register value that does not automatically boot an image (such as 0x0) or send the break key to the console port (if permitted). At the ROM monitor command prompt enter the following commands:
MINB=
sync
Type the commands exactly as shown above. Now load your image and IOS should come up in normal mode.C7600_ES Messages
The following are C7600-ES WAN line card messages.
Error Message%C7600_ES-5-BRIDGE_ASIC_INTR : The Bridge-ASIC-[chars][[dec]] interrupt asserted. Addr[[hex]]=[hex]
Explanation The Bridge-ASIC on the line card has experienced an interrupt. The recovery action is already taken and no further action is needed.
Recommended Action No action is required.
Error Message%C7600_ES-2-CRITICAL_ERR : C7600-ES Line Card Failure: [chars]
Explanation A critical error has occurred on the C7600-ES Line Card. The message that was previously received on the console or in the system log and cash dump should provide more information of the problem.
Recommended Action If the problem persists, then collect crash dump output. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_ES-5-FPGA_IMAGE_CORRUPTED : [chars] failed to program at power up, presumed corrupted.
Explanation One of the FPGAs failed to program at boot. The board will not and cannot forward traffic in this state. Failure to program presumably caused by corrupted FPGA image. Likely cause of corrupted FPGA image: write failure during FPGA FPD upgrade. Likely cause of FPGA FPD upgrade fauilure: unexpected LC reset during FPD upgrade.
Recommended Action If failure occurred during a FPGA FPD upgrade, ensure that LC was not/will not be inadvertently reset during upgrade. Some FPGA FPD upgrades might require a longer time to complete, and an inadvertent reset during the programming interval will corrupt the FPGA image. If failure did not occur during an FPD upgrade, the FPGA recovery logic will nevertheless necessitate a FPGA FPD upgrade. As a reminder, this requires an FPD bundle file on the supervisor to complete.
Error Message%C7600_ES-5-FPGA_RECOVERY : [chars] recovery invoked.
Explanation FPD is being invoked to recover corrupted FPGA FPD image. Allow a few minutes for programming to complete. FPD will report results from programming FPGA. If FPD reports success, recovery has completed successfully.
Recommended Action Verify that FPD successfully recovered image.
Error Message%C7600_ES-2-IOFPGA_IO_BUS_ERROR : C7600-ES Line Card IOFPGA IO [chars] Bus Error: Error = [hex] Error Address = [hex], Error Data = [hex]
Explanation An unexpected hardware error condition has occurred on the C7600-ES Line Card. SELENE/LINKFPGA/PEFPGA FPGA failed to respond to a read or write access. This message indicates a hardware failure or malfunction. The line card will reload to attempt to fix the problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_ES-3-KPFPGA_FIFO_INT : C7600-ES Line Card Packet Engine Supertycho KPFPGA Interrupt
Explanation An unexpected hardware error condition has occurred on the C7600-ES Line Card. A data traffic between Earl and firmware ASIC Metropolis is flow controlled
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_ES-3-KPFPGA_PARITY_ERR_INT : C7600-ES Line Card Packet Engine Supertycho KPFPGA Parity Error
Explanation An unexpected hardware error condition has occurred on the C7600-ES Line Card. Parity error during KPFPGA register access
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_ES_LINK-6-NETCLK_SUPPORT : The card doesnot support network-clocking, network-clock commands are rejected
Explanation Only Rev2 cards and above supports network-clocking. The network-clock commands for cards with revision number less than 2 will be rejected.
Recommended Action No action is required.
Error Message%C7600_ES-5-MET_TIMEOUT : Rewrite Engine Multicast Expansion Table access timeout recovery action invoked, Address = [hex]
Explanation The line card experienced an IO-BUS timeout while accessing the Multicast Expansion Table. The recovery action is already taken and no further action is needed.
Recommended Action No action is required.
Error Message%C7600_ES-2-NMI_RESET : C7600-ES Line Card NMI reset by SUP
Explanation The Supervisor detected C7600-ES line card as unresponsive and attempted to recover the line card by issuing an Non Maskable Interrupt.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_ES-2-NP_FAILURE : C7600-ES Line Card NP [dec] Failure: [chars]
Explanation An unexpected fatal condition has occurred on the C7600-ES Line Card. The message that was previously received on the console or in the system log and cash dump should provide more information of the problem. This message indicates a NP failure or malfunction. The LC will reset to attempt to fix the problem.
Recommended Action If the problem persists, then collect crash dump output. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_ES-2-NP_WORKAROUND : C7600-ES Line Card NP[[dec]] Workaround [chars] after [[dec]] retries
Explanation The NP workaround routine on the C7600-ES Line Card Passed/Fail.If the workaround failed, it will result in packets not being forwarded.
Recommended Action Attempt to reload the line card. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_ES-3-PE_INT_BUS_ACL_PARITY : C7600-ES Line Card Packet Engine ACL Counter FPGA Parity ErrorIO Bus Error Address = [hex], IO Bus Error Data = [hex]
Explanation An unexpected hardware error condition has occurred on the C7600-ES Line Card. A parity error is detected when reading from the ACL Counter FPGA
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_ES-3-PE_INT_BUS_INV_ADDR_ERR : C7600-ES Line Card Packet Engine Invalid Address Access on Earl CardIO Bus Error Address = [hex], IO Bus Error Data = [hex]
Explanation An unexpected hardware error condition has occurred on the C7600-ES Line Card. An IO Bus transfer from the Baseboard goes to an undefined address on the Earl 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 Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_ES-3-PE_INT_BUS_PARITY : C7600-ES Line Card Packet Engine Bus Parity ErrorIO Bus Error Address = [hex], IO Bus Error Data = [hex]
Explanation An unexpected hardware error condition has occurred on the C7600-ES Line Card. A parity error is detected on the IO Bus from the Baseboard
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_ES-3-PE_INT_BUS_PROTOCOL_ERR : C7600-ES Line Card Packet Engine IO Bus Protocol ErrorIO Bus Error Address = [hex], IO Bus Error Data = [hex]
Explanation An unexpected hardware error condition has occurred on the C7600-ES Line Card. A transfer on the IO Bus between the Baseboard and the Earl FPGA did not follow the bus protocol
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_ES-3-PE_INT_BUS_ST_PARITY : C7600-ES Line Card Packet Engine Supertycho Parity ErrorIO Bus Error Address = [hex], IO Bus Error Data = [hex]
Explanation An unexpected hardware error condition has occurred on the C7600-ES Line Card. A parity error is detected when reading from the Supertycho register.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_ES-3-PE_INT_BUS_TIMEOUT : C7600-ES Line Card Packet Engine Bus Timeout: IO Bus Error Address = [hex], IO Bus Error Data = [hex]
Explanation An unexpected hardware error condition has occurred on the C7600-ES Line Card. Supertycho or the ACL Counter FPGA failed to respond to a read or write access within 1µsec
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_ES-2-PEX_INIT_FAILED : C7600-ES Line Card PCI Express Initialization failed at [chars][[dec]]
Explanation The C7600-ES Line Card received an error during initialization when attempting to initialize the PCI Express interface with the forwarding hardware. A hardware problem has prevented the target line card from fully initializing. This will result in packets not being forwarded.
Recommended Action Attempt to reload the line card. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_ES-2-UNRECOVERABLE_FAILURE : C7600-ES Line Card Unrecoverable Failure for Device: [chars]
Explanation An unexpected fatal condition has occurred on the C7600-ES Line Card. The message that was previously received on the console or in the system log should provide more information on the specific nature of the problem. This message indicates a hardware failure or malfunction. The system will reload to attempt to fix the problem.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.C7600_ES_LINK Messages
The following are C7600-ES WAN line card Link DC messages.
Error Message%C7600_ES_LINK-5-ALS_RESTARTREJ : ALS manual restart command on the Interface [chars] is rejected.
Explanation The most recent Automatic Laser Shutdown manual restart command on the given interface was issued when the ALS statemachine was not in the IDLE state and hence it not accepted.
Recommended Action No action is required.
Error Message%C7600_ES_LINK-3-FPGA_NOT_READY : [chars] reports Link FPGA is not ready (ConfigPLD status [hex])!
Explanation The Link FPGA configuration is not done properly. This could be caused by an incompleted Link FPGA update in a previous FPD upgrade process.
Recommended Action Restart the FPD upgrade. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_ES_LINK-3-INIT_FAILED : Failed to initialize Link Daughtercard.
Explanation Link Daughtercard initilization process failed. The reason for this problem could be Link FPGA not ready, memory allocation failure, or fatal OS kernel error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_ES_LINK-3-INTR_THROTTLE : Interface [chars] PHY interrupt is throttled. Total throttle count [dec].
Explanation 10GE PHY interrupt burst has occurred on one of the interfaces on the link daughtercard. The error message indicates that a throttling mechanism has been applied to this port to avoid any operational damage that could be provoked by this event. The cause for this problem could be bad transceiver, highly frenquent flapping optical signals, or mismatched path signals (e.g. receiving 10GBASE-W signal on 10GE LAN interface), etc.
Recommended Action Check the interface configuration and received signal characteristics. Also verify the XFP transceiver and receive signal path to determine the exact root cause. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_ES_LINK-4-SCPBUF_ERR : Failed to get packet from SCP packet pool for [chars]
Explanation The Line Card failed to allocate a packet from the SCP packet pool for the transceiver control message specified in the error message.
Recommended Action No action is required.
Error Message%C7600_ES_LINK-3-SEND_MSG : Link DC failed to notify driver process about a line state change in the interface port [dec]
Explanation A line state change has occurred on one of the interface ports on the link daughtercard. The error message indicates the port number. The state change notification could not be sent to link daughtercard processor. The cause for this problem could be memory exhaustion.
Recommended Action Enter the show memory summary command to attempt to determine the cause of the error. If it is insufficient system memory, reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.C7600_SSC400 Messages
The following are C7600 Services SPA Carrier Card (SSC400) messages.
Error Message%C7600_SSC400-3-BRDTYPE_INDEX_MISMATCH : [chars]: Board type ([dec]) and card index ([dec]) do not match
Explanation A mismatch was detected between the card index and board type. For C7600-SSC-400, board type is 4 and card index is 191.For C7600-SSC-600, board type is 5 and card index is 224
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_SSC400-3-DCM_FAIL : [chars]: [chars] FPGA module DCM Lock Failure, status:[hex]
Explanation One or more of the Digital Clock Managers (DCM) for the Data Path FPGAs failed to lock. This indicates a hardware failure
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_SSC400-3-DP_COUNTERS : [chars]: Failed to create DP counter process.
Explanation A process is spawned on bootup to monitor the counters of the Data Path FPGAs. There was an error creating this 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_SSC400-7-DP_DISABLE : [chars]: [chars] FPGA is forced disabled.
Explanation This FPGA has been forced disabled. This is a debugging feature.
Recommended Action No action required.
Error Message%C7600_SSC400-3-DP_ERROR : [chars]: Bus Error initializing [chars] FPGA, addr: [hex].
Explanation This FPGA could not be initialized due to a bus error. This condition indicates a hardware failure, possibly due to a failed FPD upgrade.
Recommended Action Enter show hw-module slot fpd. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_SSC400-3-DP_PROGRAMMING : [chars]: [chars] FPGA failed to program.
Explanation This FPGA failed to program. This condition indicates a hardware failure, possibly due to a failed FPD upgrade.
Recommended Action Enter show hw-module slot fpd. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_SSC400-3-DPRX_ERR : [chars]: [chars].
Explanation There was an error receiving data from the SPA, possibly due to data corruption.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_SSC400-3-DPTX_ERR : [chars]: [chars].
Explanation There was an error sending data to the SPA, possibly due to data corruption.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_SSC400-3-DPTX_ERR_MECC : [chars]: [chars]. ERR addr register:[hex].
Explanation There was an error sending data to the SPA, possibly due to data corruption.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_SSC400-3-DPTX_ERR_SECC : [chars]: [chars]. Single bit error count:[hex], ECC ERR addr register:[hex].
Explanation A data corruption error that was automatically fixed was detected while sending data to the SPA.
Recommended Action No action is required if you see this message once. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_SSC400-3-DPTX_QDR : [chars]: Error clearing QDR queue [dec].
Explanation One of the QDR queues did not flush completely.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_SSC400-3-SINGLE_SPA_MODE : [chars]: Module will use only bay [dec]. Bay [dec] is shut.
Explanation This message informs that 7600-SSC-400 is in single-spa-mode.
Recommended Action This message is informational only. No action is required.
Error Message%C7600_SSC400-3-SSC_BAY_SHUT : [chars]: Bay [dec] is shutdown because 7600-SSC-400 is in single-spa-mode
Explanation This message indicates that specified bay is shut down. In single-spa-mode, only one bay is active.
Recommended Action Refer to IPSEC SPA documentation for information about single-spa-mode.
Error Message%C7600_SSC400-3-SW_ERROR : [chars]: [chars]
Explanation This error is seen when there is a problem in internal software coding; it should not be seen under normal 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/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%C7600_SSC400-3-UNKNOWN_BRDTYPE : [chars]: SSC board type [dec] is not supported
Explanation Board type does not belong to either C7600-SSC-600 or C7600-SSC-400.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.C7600_SSC600 Messages
The following are Services SPA Carrier Card (SSC600) messages.
Error Message%C7600_SSC600-3-DPTX_ERR_MECC : [chars]. ERR addr register:[hex].
Explanation There was an error sending data to the SPA, possibly due to data corruption.
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%C7600_SSC600-3-DPTX_ERR_SECC : [chars]. Single bit error count:[hex], ECC ERR addr register:[hex].
Explanation A data corruption error that was automatically fixed was detected while sending data to the SPA.
Recommended Action No action is required if you see this message once. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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.CALL_MGMT Messages
The following are the Call Management subsystem messages.
Error Message%CALL_MGMT-4-CALL_DISC : [chars]
Explanation The specific message text is supplied by the Call Management software. This indicates that a call record is missing from
active call listRecommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
Error Message%CALL_MGMT-1-CALL_LIST : [chars]
Explanation The specific message text is supplied by the Call Management
software. This indicates that internal data was corrupted
due to a software errorRecommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CALL_MGMT-1-CPM_Q_POOL : [chars]
Explanation The specific message text is supplied by the Call Management
software. This indicates a memory exhaustion condition.Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%CALL_MGMT-1-INITSYS : [chars]
Explanation The specific message text is supplied by the Call Management
software. This indicates an initialization failure. When this
occurs, the Call Management subsystem is not operational.Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information.
CALL_RECORD Messages
The following are Modem Call Record messages.
Error Message%CALLRECORD-3-MCOM_TERSE_CALL_FAILED_REC : [chars]
Explanation Terse Mcom Call Failed Record
Recommended Action No action is required.
Error Message%CALLRECORD-3-MCOM_TERSE_CALL_REC : [chars]
Explanation Terse Mcom Call Record
Recommended Action No action is required.
Error Message%CALLRECORD-6-MICA_TERSE_CALL_FAILED_REC : [chars]
Explanation Terse Mica Call Failed Record
Recommended Action No action is required.
Error Message%CALLRECORD-6-MICA_TERSE_CALL_REC : [chars]
Explanation Terse Mica Call Record
Recommended Action No action is required.
Error Message%CALLRECORD-3-MODEM_CALL_REC_ERROR : [chars]
Explanation Record Generated Exceeded Syslog Capability
No action is required.
CARDMGR Messages
The following are SIP-400 Card Manager messages.
Error Message%CARDMGR-2-LI_DEDICATED_ERROR : Error occurred while configuring as dedicated service card for Lawful Intercept.
Explanation An error occurred while configuring SIP-400 as a dedicated service card for Lawful Intercept.
Recommended Action Reload the linecard. If this error occurs again after reload, you will require assistance. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CARDMGR-4-LI_DEDICATED_MODE : Configuring SIP-400 as dedicated service card for Lawful Intercept.
Explanation Configuring SIP-400 as a dedicated service card for Lawful Intercept .
Recommended Action No action is required. This message is informational only.
Error Message%CARDMGR-2-LI_SPA_PLUGIN_ERROR : SIP-400 has been configured as a dedicated service card for Lawful Intercept. SPA inserted in subslot [dec] has been powered down.
Explanation SIP-400 has been configured as a dedicated service card for Lawful Intercept . No SPAs will be allowed online in this mode.
Recommended Action To enable the SPA, deconfigure dedicated service card mode and then reload the line card. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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.CBUS Messages
The following are CiscoBus controller messages.
Error Message%CBUS-3-SRPRSET : Interface [chars], Error ([hex]) [chars] - srp_reset()
Explanation A command to reset an SRP interface was issued by the RSP, but the interface did not respond to the command within the expected time delay. The delay is given for the processor to return the buffers that it has allocated and to perform any necessary cleanup. This condition might be caused by a large number of buffers that have been allocated by the interface due to either heavy traffic or a hardware problem with the interface.
Recommended Action Verify that the card is properly seated. If this error recurs, copy the message exactly as it appears on the console or in the system log. Enter the show tech-support and show logging commands to gather data that might help identify the nature of the message. Research and attempt to resolve the 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/pcgi-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.CCM Messages
The following are cluster control manager messages.
Error Message%CCM-3-CCMINVALEVT : Client[[dec]] received an invalid event[[dec]]
Explanation Cluster Control Manager High Availability feature on standby, detected an invalid event received from active.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CCM-3-CCMNOCLIENT : Client [chars][[dec]] not present
Explanation Cluster Control Manager High Availability features for this client will not work.
Recommended Action Refer to the documentation on configuring High Availability features.
Error Message%CCM-3-CCMREGFAIL : High Availability Registration failed
Explanation Cluster Control Manager High Availability features 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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.CEM Messages
The following are Circuit Emulation messages.
Error Message%CEM-4-ISSU_INCOMPATIBLE :
cem-issu-compat: returned FALSEExplanation The compatibility checking 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CEM-1-ISSU_NOMEMORY : Unit [dec], no memory for [chars]
Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%CEM-3-ISSU_SENDFAILED :
CEM ISSU: send message failed, rc = [dec]
Explanation The sending of a 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CEM-4-ISSU_XFORM :
[chars]: failed, rc=[chars]Explanation The transform 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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.CFGMGR Messages
The following are configuration manager messages.
Error Message%CFGMGR-6-APPLYING_RUNNING_CFG : as new master
Explanation New master is applying backed-up running-configuration.
Recommended Action No action is required.
Error Message%CFGMGR-3-ERROR_APPLYING_STARTUP_CFG : Error Applying Startup Config to Running Config
Explanation The system automatically applied the startup-configuration to the running-configuration, but encountered an error while doing so.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%CFGMGR-4-SLAVE_WRITING_STARTUP_CFG : only master can do that
Explanation An attempt to write to the startup-configuration was made on a slave, which is allowed only on the master.
Recommended Action No action is required.
Error Message%CFGMGR-6-SPURIOUS_SLAVE_ADD : CFG MGR Recvd Spurious New Slave Notification: [int]
Explanation ConfigurationManager was notified about slave that it already knows about.
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CFGMGR-6-UNABLE_TO_NVGEN_BUSY_RUNNING_CFG : config file busy, retrying...
Explanation Master is temporarily unable to nvgen running-configuration.
Recommended Action No action is required.
Error Message%CFGMGR-6-UNABLE_TO_NVGEN_RUNNING_CFG : config file too large...
Explanation Master is unable to nvgen running-configuration.
Recommended Action Undo some configuration commands.
Error Message%CFGMGR-1-UNABLE_TO_SEND_RUN_CFG : unable to send running-cfg, bits: [hex], retrying...
Explanation The system is attempting to push the running configurationto the slave(s).
Recommended Action No action is required.
Error Message%CFGMGR-1-UNABLE_TO_SEND_STARTUP_CFG : unable to send startup-cfg, bits: [hex], retrying...
Explanation The system is attempting to push the startup configurationto the slave(s).
Recommended Action No action is required.
CFIB Messages
The following are Constellation FIB messages.
Error Message%CFIB-3-CFIB_EXCEPTION : FIB TCAM exception for IPv4 unicast. Packets through some routes will be dropped.
Use "mls cef maximum-routes" to modify the FIB TCAM partition or/and consider a hardware upgred.
Examine your network and collect the necessary information from this setup.
The only way to recover from this state is by reload the router.Explanation Either the number of route entries that are installed has exceeded the hardware capacity, or the protocol that generated an exception condition does not have enough route entries reserved.
As a result of this condition, some prefixes will be dropped.
Enter the mls cef maximum-routes command to modify the FIB TCAM partition and reload the router.Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%CFIB-3-CFIB_UNEXPECTED : Unexpected CFIB condition
Explanation An error has occurred where an unexpected condition has been reached in the Constellation FIB code.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%CFIB-7-END_CFIB_EXCEPTION : FIB TCAM exception cleared, all CEF entries will be hardware switched
Explanation FIB TCAM free blocks available again.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%CFIB-7-CFIB_EXCEPTION : FIB TCAM exception for IPv4 unicast. Packets through some routes will be software switched.
Use "mls cef maximum-routes" to modify the FIB TCAM partition.Explanation Either the number of route entries that are installed has exceeded the hardware capacity, or the protocol that generated an exception condition does not have enough route entries reserved.
As a result of this condition, some prefixes will be software switched.
Enter mls cef maximum-routes to modify the FIB TCAM partitionRecommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%CFIB-3-NO_MEMORY_PFIBMSG : no memory for cfib_fibmsg_chunk
Explanation Either the number of route entries that are installed has exceeded the hardware capacity, or the protocol that generated an exception condition does not have enough route entries reserved. As a result of this condition, some prefixes will be dropped.
Recommended Action Enter the mls cef maximum-routes command to modify the FIB TCAM partition and reload the router.
CFIB_TUNNEL_RP Messages
The following are Constellation FIB tunnel messages.
Error Message%CFIB_TUNNEL_RP-4-TUN_L2TPV3_MAX : The supported maximum number of [dec] L2TPv3 tunnels
have been already configuredExplanation The platform supports configuration of the maximum number of L2TPV3 tunnels shown above. This error message is displayed when an attempt is made to configure a tunnel beyond this numerical limit.
Recommended Action No action is required.
Error Message%CFIB_TUNNEL_RP-4-TUN_RECIR_FORCED : The current configuration of hardware and software requires MPLS tunnel recirculation to be enabled. 'mls mpls tunnel-recir' has been added to the running configuration
Explanation When the chassis contains a SIP-600 line card and VRF forwarding is configured on a tunnel interface, MPLS tunnel recirculation must be enabled to prevent the creation of corrupted packets from EARL. The mls mpls tunnel-recir command has been added to the running configuration automatically.
Recommended Action No action is required.
CFM_CONST Messages
The following are CFM on Constellation messages.
Error Message%CFM_CONST-3-AEB_MATCH_REG_UNAVAILABLE : The linecard in slot [dec] does not support AEB mode.Cannot set CFM AEB mode
Explanation The CFM AEB mode is not supported for the slot indicated.
Recommended Action The CFM AEB mode is available only on slots that have have at least one 'prog' (as opposed to '44' or '48') match register. The match registers can be viewed with remote command switch show platform mrm info command.
Error Message%CFM_CONST-3-AEB_ON_EC_UNSUPPORTED : CFM AEB mode is unsupported on etherchannels. Cannot set CFM AEB mode
Explanation The CFM AEB mode is unsupported on ether channels.
Recommended Action Set the CFM AEB mode only on physical (unbundled) ports.
Error Message%CFM_CONST-3-CFM_ON_SUPERVISOR_PORTS_DISABLED : CFM is enabled system wide except it's disabled on supervisor ports due to spanning tree or GVRP configuration.
Explanation Unable to program all port ASIC MAC match registers on supervisor ports for CFM due to hardware limitations on these ports. Continued with enabling CFM system-wide to allow coexistence with other protocols such as PVST or GVRP.
Recommended Action System has handled this by disabling CFM on all supervisor ports. If this is unacceptable, configure STP mode to MST and/or disable GVRP and re-enable CFM or disable CFM completely.
Error Message%CFM_CONST-3-CFM_ON_SUPERVISOR_PORTS_DISALLOWED : CFM is enabled system wide except on supervisor ports due to spanning tree or GVRP configuration.
Explanation Unable to program all port ASIC MAC match registers on supervisor ports for CFM due to hardware limitations on these ports. Continued with enabling CFM system-wide to allow coexistence with other protocols such as PVST or GVRP.
Recommended Action Administrator action may be required. Ensure no CFM traffic is presented to any supervisor ports via configuration. If not possible, configure STP mode to MST and or disable GVRP and re-enable CFM or disable CFM completely.
Error Message%CFM_CONST-6-MAC_OPERATIONALLY : Interface [chars] is MAC operationally [chars].
Explanation The specified interface is MAC operationally up or down.
Recommended Action No action is required.
Error Message%CFM_CONST-3-MAC_OPERATIONALLY_ERROR : The set MAC operationally action on interface [chars] has encountered an error.
Explanation The set MAC operationally action failed and ended abnormally.
Recommended Action No action is required.
Error Message%CFM_CONST-3-MATCH_REG_GLOBAL_RESERVE_FAILED : Unable to program port ASIC MAC match register on one or more slots. Cannot run CFM
Explanation CFM attempted to reserve and program the port ASIC MAC match registers and there are insufficient match registers available. CFM cannot be run.
Recommended Action To free MAC match registers, disable protocols that use the MAC match register. Protocols using port ASIC match registers can be viewed with remote command switch show platform mrm info.
Error Message%CFM_CONST-3-MATCH_REG_RESERVE_FAILED : Unable to program port ASIC MAC match register on slot [dec]. Cannot run CFM
Explanation CFM attempted to reserve a port ASIC MAC match register for the slot indicated and there is no register available. CFM cannot be run without support from all line cards (except supervisors).
Recommended Action Protocols that use the MAC match register must be disabled to free MAC match registers. Protocols using port ASIC match registers can be can be viewed with remote command switch show platform mrm info.
Error Message%CFM_CONST-6-MAC_OPERATIONALLY : Interface [chars] is MAC operationally [chars].
Explanation The specified interface is MAC operationally up or down.
Recommended Action No action is required.
Error Message%CFM_CONST-3-MAC_OPERATIONALLY_ERROR : The set MAC operationally action on interface [chars] has encountered an error.
Explanation The set MAC operationally action failed and ended abnormally.
Recommended Action No action is required.
Error Message%CFM_CONST-3-STP_MODE_CHANGE_NOT_ALLOWED : Unable to change STP mode while CFM is enabled
Explanation STP modes PVST and rapid PVST are not compatible with CFM due to hardware limitations.
Recommended Action Either configure STP mode MST or disable CFM.
CHEIT Messages
%CHE1T1-3-CORRUPT : Corrupt configuration, unsupported [chars] ([int]) encountered
Explanation The ChE1T1 RP driver running configuration is corrupt.
Recommended Action Enter the show c10k, show ipc status commands to gather data that might provide information to determine the nature of the message. If you cannot determine the nature of the message from the error message text or from the show c10k, show ipc status output, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%CHE1T1-3-ERROR : [chars]
Explanation General error information.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CHE1T1-1-INITFAIL : Slot [dec]/[dec] init failure ([chars])
Explanation ChE1T1 initialization failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CHE1T1-2-NOVC : [chars]: packet received for unknown VC [dec]
Explanation The virtual channel encapsulation is corrupted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%CHE1T1-1-RESTARTFAIL : [chars] could not be reset by [chars]
Explanation The restart failed to reset the 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CHE1T1-1-STOPFAIL : [chars] could not be disabled by [chars]
Explanation The shutdown failed to disable the 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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:
[chars]Explanation Unavailable.
Recommended Action Unavailable.
CHKPT Messages
The following are checkpoint facility messages.
Error Message%CHKPT-4-GET_BUFFER : Checkpointing ISSU session ([dec]) failed to get buffer
Explanation Checkpointing ISSU failed to get a buffer.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%CHKPT-4-MSG_SEND : Checkpointing ISSU session ([dec]) failed to send message
Explanation Checkpointing ISSU failed to send negotiation message to peer.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%CHKPT-3-TRANSFORMFAILED : Checkpointing msg header transform failed ([dec])
Explanation This is a transform error as far as check pointing is concerned.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.CHOC12 Messages
The following are CHOC12 port adapter messages.
Error Message%CHOC12-3-CORRUPT : Corrupt configuration, unsupported [chars] ([int]) encountered
Explanation The CHOC12 RP driver running configuration is corrupt.
Recommended Action Enter the show c10k, show ipc status commands to gather data that might provide information to determine the nature of the message. If you cannot determine the nature of the message from the error message text or from the show c10k, show ipc status output, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%CHOC12-3-ERROR : [chars]
Explanation General error information.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CHOC12-1-INITFAIL : Slot [dec]/[dec] init failure ([chars])
Explanation CHOC12 initialization failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CHOC12-4-REDINLCEVT : Redundant inactive i/f ([chars]) event: [chars], reason: [chars]
Explanation Internal redundant LC event.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%CHOC12-3-STATESYNC : Redundancy state synchronization failure slot [dec]/[dec] - ([chars])
Explanation A failure occurred in trying to synchronize CHOC12 state information.
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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.CHOPIN Messages
The following are Cisco Chopin messages.
Error Message%CHOPIN-2-TXBADVC : [chars], vc [dec]
Explanation CHOPIN had a Tx Bad VC.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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 along with output from the show tech-support and show controllers vip slot tech-support commands.CHSTM1 Messages
The following are CHSTM1 messages.
Error Message%CHSTM1-3-CORRUPT : Corrupt configuration, unsupported [chars] ([int]) encountered
Explanation The CHSTM1 RP driver running configuration is corrupt.
Recommended Action Enter the show c10k, show ipc status commands to gather data that might provide information to determine the nature of the message. If you cannot determine the nature of the message from the error message text or from the show c10k, show ipc status output, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%CHSTM1-3-ERROR : [chars]
Explanation General error information.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CHSTM1-1-INITFAIL : Slot [dec]/[dec] init failure ([chars])
Explanation CHSTM1 initialization failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CHSTM1-3-INTERNALISSU : C10K CHSTM1 LC ISSU internal error, [chars] [chars] [dec] [dec]
Explanation Internal C10K CHSTM1 LC ISSU 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/pcgi-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%CHSTM1-3-STATESYNC : Redundancy state synchronization failure slot [dec]/[dec] - ([chars])
Explanation A failure occurred in trying to synchronize CHSTM1 state information.
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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.CI Messages
The following are Cisco 7500 platform chassis interface messages.
Error Message%CI-3-ASPMEM : C6400 equipped with [chars] requires at least [dec] MB of RAM
Only [dec] MB of RAM installed
Explanation The type of feature card installed requires more RAM than is currently installed in the system.
Recommended Action Install the required amount of RAM.
Error Message%CI-6-BLOWEROK : Fan tray module OK
Explanation Chassis fan tray is operating normally.
Recommended Action No action is required.
Error Message%CI-1-CHASSISFAULTYSENSOR : Alarm: Chassis temperature sensor is faulty
Explanation This error occurs when the chassis temperature sensor is faulty.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%CI-6-CHASSIS_SHUTDOWN : Chassis shutdown. Card/subcard not powered up
Explanation Chassis is shutdown. Line cards will not be powered up.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CI-1-CHASSISTEMPCRITICAL : Chassi temperature CRITICAL limit exceeded
Explanation The system chassis temperature critical limit has been exceeded.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CI-3-CHASSISTEMPLOW : Chassis temperature too low
Explanation The system chassis temperature is below -15 degrees C.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%CI-3-CHASSISTEMPMAJOR : Chassis temperature major limit exceeded
Explanation The system chassis temperature major limit has been exceeded.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CI-3-CHASSISTEMPMINOR : Chassis temperature minor limit exceeded
Explanation The system chassis temperature minor limit has been exceeded.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CI-1-CORETEMPCRITICAL : Core temperature CRITICAL limit exceeded
Explanation The system core temperature critical limit has been exceeded. The system will automatically shut down in two minutes.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%CI-3-CORETEMPMAJOR : Core temperature major limit exceeded
Explanation The system core temperature major limit has been exceeded.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CI-3-CORETEMPMINOR : Core temperature minor limit exceeded
Explanation The system core temperature minor limit has been exceeded.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CI-6-CORETEMPOK : Core temperature normal
Explanation Temperature of the system core is normal.
Recommended Action No action is required.
Error Message%CI-1-CRITICALTEMP_LC_SHUT : Alarm: [chars], [chars], [chars], [chars], [chars]
Explanation The error occurs when line cards are shut down duecore temperature exceeding the critical threshold.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%CI-6-ENVNORMAL : [chars] measured at [chars]
Explanation One of the measured environmental test points has returned to normal.
Recommended Action If the situation does not correspond with a normal operation of the system's environmental test points, collect the outputs for the commands show hardware, show env all, show env table, and show env last, and call your technical support representative for assistance.
Error Message%CI-1-FAN_FAILURE_LC_SHUT : Alarm: [chars], [chars], [chars], [chars], [chars]
Explanation The error occurs when line cards are shut down dueto total fan failure or a missing fan tray.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%CI-6-FANOK : Fan tray module OK
Explanation Chassis fan tray is operating normally.
Recommended Action No action is required.
Error Message%CI-3-FCTYPE : Unrecognized Feature Card
Explanation The feature card is not recognized by the software.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CI-1-INLETTEMPCRITICAL : Inlet temperature CRITICAL limit exceeded
Explanation Air intake temperature critical limit has been exceeded. The system will automatically shut down in two minutes.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%CI-3-INLETTEMPMAJOR : Inlet temperature major limit exceeded
Explanation Air intake temperature major limit has been exceeded.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CI-3-INLETTEMPMINOR : Inlet temperature minor limit exceeded
Explanation Air intake temperature minor limit has been exceeded.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CI-6-INLETTEMPOK : Inlet temperature normal
Explanation Temperature of the chassis air intake is normal.
Recommended Action No action is required.
Error Message%CI-6-LINECARD_SHUTDOWN : [chars]
Explanation When two or more of the fans in the chassis fan tray have failedor the fan tray is missing, the line cards will be powered downafter a user configured timer interval. This message is generated before shutting down line cards.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%CI-3-MIB_ALM_SUBMIT : MIB alarm: [chars], [chars], [chars], [chars], [chars]
Explanation Submit An alarm — Let MIB prints out 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CI-4-MULTIPLE_FAN_FAILURE : [chars] [dec] [chars][chars]
Explanation When two or more of the fans in the chassis fan tray have failed or the fan try is missing, the line cards will be powered downafter the user configured timer interval. This warning message is generated one minute after the fans have failed or the fan tray is detected to be missing.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%CI-3-NOACK : Access to [chars] temperature sensor failed
Explanation Accesses to chassis temperature sensor 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CI-1-NOFAN : Fan tray empty
Explanation The chassis fan tray does not exist.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CI-3-NOFORK : Couldn't start environment polling daemon
Explanation The environment monitoring daemon process could not be started during 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CI-1-OUTLETTEMPCRITICAL : Outlet temperature CRITICAL limit exceeded
Explanation Air intake temperature critical limit has been exceeded. The system will automatically shut down in two minutes.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%CI-3-OUTLETTEMPMAJOR : Outlet temperature major limit exceeded
Explanation Air intake temperature major limit has been exceeded.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CI-3-OUTLETTEMPMINOR : Outlet temperature minor limit exceeded
Explanation Air outlet temperature minor limit has been exceeded.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CI-6-OUTLETTEMPOK : Outlet temperature normal
Explanation Temperature of the chassis outlet air is normal.
Recommended Action No action is required.
Error Message%CI-3-PARTFANFAIL : Single fan failure
Explanation Chassis fan tray is not fully functioning.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CI-3-PS_FAIL : Power supply module [dec] failure
Explanation Specified power supply module has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CI-6-PS_MISSING : Power supply module [dec] missing
Explanation Power supply module is not present in the system.
Recommended Action No action is required.
Error Message%CI-6-PSNORMAL : Power supply [int] normal
Explanation One of the router's failed power supplies is working normal now.
Recommended Action If the situation does not correspond with a normal operation of the system's power supplies, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CI-6-PSOK : Power entry module [int] OK
Explanation Power entry module is operating normally.
Recommended Action No action is required.
Error Message%CI-6-PS_OK : Power supply module [dec] OK
Explanation Specified power supply module is operating normally.
Recommended Action No action is required.
Error Message%CI-6-PS_PRESENT : Power supply module [dec] present
Explanation Power supply module is present in the system.
Recommended Action No action is required.
Error Message%CI-3-SHUTDOWN : System shutting down due to over-temperature condition
Explanation Chassis over-temperature timer has expired — system shut down.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CI-0-SHUTFANFAIL : System shutting down due to total fan tray failure
Explanation Chassis fan tray failure timer has expired — system shut down.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CI-0-SHUTFANGONE : System shutting down due to missing fan tray
Explanation The chassis fan does not exist.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CI-0-SHUT_LC_CRITICALTEMP : Line cards shutdown as critical temperature exceeded
[chars]Explanation Chassis temperature has exceeded critical threshold — line card shut down.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CI-0-SHUT_LC_FANFAIL : Line cards are being shut on fan failure
Explanation Chassis fan tray failure timer has expired — line card shut down.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CI-0-SHUT_LC_FANGONE : Line cards are being shut as fan tray is missing
Explanation Chassis fan missing timer has expired — line card shut down.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CI-1-TOTALFANFAIL : Total fan tray failure
Explanation Chassis fan tray has totally 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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.CLCAPPLICATION Messages
The following are CLC Application messages.
Error Message%CLCAPPLICATION-6-INCONSISTENTGATEDB : Gate entry, bin [[dec]], off [[dec]], is in used by [dec]. It will be replaced by [dec]
Explanation Gate database is inconsistent between LC and RP, which is due to gate not cleaned up properly on LC.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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.CLCJIB Messages
The following are CLC JIB messages.
Error Message%CLCJIB-6-BADJIBHDR : [chars]: JIB [dec] DS[dec] Iron bus error packet (count [dec])
[chars]Explanation A packet is dropped by JIB because of an error in the JIBheader.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%CLCJIB-6-BADJIBPKT :
[chars]Explanation A packet is dropped by JIB because of an error in the JIBheader.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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.CLCPLATFORM Messages
The following are CLC Platform messages.
Error Message%CLCPLATFORM-3-UNKNOWPLAT : Unknown Platform ID, [dec].
Explanation The platform is unrecognized. Assuming uBR10K Headsail.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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.CLCSNMP Messages
The following are CLC SNMP messages.
Error Message%CLCSNMP-3-TRAPQFULL : SNMP trap pending queue is full
Explanation A SNMP trap generated on the CLC was dropped because the process tried to enqueue it to a pending queue which was full. This condition occured because IPC was down or the synchronization of SNMP information to the CLC was not completed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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.CLNS Messages
The following are OSI Connectionless Network Service messages.
Error MessageExplanation This message occurs if the interface MTU becomes unusable while ISIS is running on the interface. This condition might be temporary and recoverable.
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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.CLOCK_RECOVERY Messages
The following are 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.
CMP Messages
The following are Cluster Membership Protocol messages.
Error Message%CMP-5-NBR_UPD_SIZE_TOO_BIG : Number of neighbors in neighbor update is [int], maximum number of neighbors allowed in neighbor update is [int]
Explanation The number of cluster neighbors in the clustering neighbor update packet exceeds the number of neighbors supported by the clustering module design.
Recommended Action No action is required.
CNS Messages
The following are CNS messages.
Error MessageExplanation The CNS subsystem experienced an unexpected condition while executing a set of commands. The condition did not cause a failure but also did not correctly execute the commands.
Recommended Action Check the error log for additional information. This message is informational only and does not necessarily indicate that an error occurred.
COBALT Messages
The following are Cobalt messages.
Error Message%COBALT-3-COBALT_MALLOCFAIL : PXF DMA driver malloc failed!
Explanation Not enough free memory for the PXF DMA driver to operate.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%COBALT-3-ECM_ADDR_ERR : PXF DMA ECM [chars], Bad Address Range: [hex] through [hex]
Explanation Access to invalid PXF DMA ECM address.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%COBALT-3-ECM_DETECT_ERR : No PXF DMA ECM detected!
Explanation No access PXF DMA ECM.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%COBALT-3-EPM_ADDR_ERR : PXF DMA EPM [chars], Bad Address Range: [hex] through [hex]
Explanation Access to invalid PXF DMA EPM address.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%COBALT-3-EPM_DETECT_ERR : No PXF DMA EPM detected!
Explanation No access PXF DMA EPM.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%COBALT-3-GP_ADDR_ERR : PXF DMA TABLE [chars], Bad Address Range: [hex] through [hex]
Explanation Access to invalid PXF DMA Cobalt GP register address.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%COBALT-3-INIT_ERR : PXF DMA Initialization failed!
Explanation PXF DMA ASIC 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%COBALT-3-OWN_ERR : [chars] packet buffer, descriptor address [hex], descriptor flags [hex] pak [hex]
Explanation The PXF DMA ASIC driver detected that the descriptor ring is in an inconsistent and unrecoverable state.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%COBALT-3-PARTICLE_COUNT_ERR : Cobalt particle count error
Explanation The PXF DMA ASIC driver detected a packet with too many particles.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%COBALT-3-SDRAM_ADDR_ERR : PXF DMA SDRAM [chars], Bad Address: [hex]
Explanation Access to invalid PXF DMA SDRAM address.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%COBALT-3-SDRAM_DETECT_ERR : No PXF DMA SDRAM detected!
Explanation No access PXF DMA SDRAM.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show hardware pxf dma command to gather data that might help identify the nature of the message. Research and attempt to resolve the 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/pcgi-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%COBALT-3-SPURIOUS_INT_ERR : Spurious PXF DMA Interrupt detected!
Explanation Spurious PXF DMA Interrupt detected.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show hardware pxf dma command to gather data that might help identify the nature of the message. Research and attempt to resolve the 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/pcgi-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%COBALT-2-TBB_LENGTH_ERR : TBB FIFO Debug Data - Register [hex]: [hex]
Explanation The PXF DMA ASIC driver detected TBB Length 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/pcgi-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%COBALT-3-TBL_ADDR_ERR : PXF DMA TABLE [chars], Bad Address Range: [hex] through [hex]
Explanation Access to invalid PXF DMA Cobalt table address.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show hardware pxf dma command to gather data that might help identify the nature of the message. Research and attempt to resolve the 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/pcgi-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%COBALT-3-VCCI_0_ERR : Packet [hex], Length [dec], Channel [dec], VCCI [dec], Flags [hex]
Explanation The PXF DMA ASIC driver detected a VCCI of 0.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show hardware pxf dma command to gather data that might help identify the nature of the message. Research and attempt to resolve the 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/pcgi-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.COBALT3 Messages
The following are Cobalt3 messages.
Error Message%COBALT3-3-COB3ERR : Cobalt3 [chars].
Explanation Cobalt3 generated 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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.COMMON_FIB Messages
The following are CEF address family independent (FIB) messages.
Error Message%COMMON_FIB-4-CHAIN_REMOVE_INCONS1 : Attempting to remove [hex] but prev [hex] points at [hex] instead
Explanation COMMON_FIB_INTERNAL_ERROR.
Recommended Action LOG_STD_ACTION.
Error Message%COMMON_FIB-4-CHAIN_REMOVE_INCONS2 : Attempting to remove [hex] but it has no prev [hex]
Explanation COMMON_FIB_INTERNAL_ERROR.
Recommended Action LOG_STD_ACTION.
Error Message%COMMON_FIB-4-CHAIN_REMOVE_INCONS3 : Attempting to remove [hex] with next [hex] thinks its prev is [hex]
Explanation COMMON_FIB_INTERNAL_ERROR.
Recommended Action LOG_STD_ACTION.
COMPILED Messages
The following are Compiled messages.
Error Message%COMPILED_ACL-4-BACKPOINTER_OVERFLOWED_NOT_EMPTY : [chars]: the back-pointer list for row [int] in node [int] is marked as overflowed but is not empty
Explanation The backpointer list for the row and node is marked as overflowed but is not empty.
Recommended Action Warning message. The row being freed will still be freed normally. No action is required.
Error Message%COMPILED_ACL-4-BACKPOINTER_OVERFLOWED_NOT_EMPTY_REFERENCES : [chars]: the back-pointer list for row [int] in node [int] is marked as overflowed but is not empty
Explanation The backpointer list for the row and node is marked as overflowed but is not empty.
Recommended Action Warning message. The row being freed will still be freed normally. No action is required.
Error Message%COMPILED_ACL-4-BACKPOINTER_PROCESSING_OVERFLOWED : [chars]: processing back-pointers in row [int] in node [int] but the list is marked as overflowed
Explanation An attempt was made to process backpointers for the given row so it could be freed, but the backpointer list for the row is marked overflowed. Software bug.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%COMPILED_ACL-4-BACKPOINTER_WRONG : [chars]: entry at row [int], column [int] in node [int] does not reference row [int] in the node's child
Explanation Backpointer points to wrong location. Software bug or memory corruption.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%COMPILED_ACL-4-BAD_PROCESS_REFERENCES : [chars]: error while processing references for row [int] in node [int]: [chars]
Explanation Error occurred while processing references.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%COMPILED_ACL-4-BAD_ROW_FREE : [chars]: cannot free row [int] in node [int]: [chars]
Explanation An internal error occurred while attempting to free the given row. Software bug or memory corruption 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/pcgi-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%COMPILED_ACL-4-DEFERRED_ENTRY_CONSISTENCY : [chars]: while [chars] in row [int] in node [int], found deferred entry bitmap is [chars] but count is [int]
Explanation Internal software error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%COMPILED_ACL-4-ENTRY_COUNT : [chars]: row entry counters not allocated for node [int] while freeing row [int]
Explanation Internal software error. Row entry counters not allocated for given node while freeing row.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%COMPILED_ACL-3-INTERNAL_ERROR : an unexpected internal error occured: [chars]
Explanation An unexpected internal error occurred. This error might result in one or more flows being punted to the RP or in Turbo ACL not functioning.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%COMPILED_ACL-2-LIST_CREATE : [chars]: failed to create row queue for node [int], Turbo ACL has been disabled temporarily
Explanation The system encountered an error while initializing a data structure required for the correct operation of Turbo ACL processing. Turbo ACL will be disabled until another recompilation has completed successfully.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%COMPILED_ACL-5-LIST_INFO : [chars]: failed to set list information function for node [int]'s row queue (ID [int])
Explanation The system encountered an error while initializing a function vector used for debugging purposes. Turbo ACL will continue to function correctly, but the show list ID command will not show Turbo ACL-specific information for the specified list ID 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%COMPILED_ACL-2-QUEUE_INIT : [chars]: failed to initialize back-pointer list for row [int] in node [int], Turbo ACL has been disabled temporarily
Explanation The system encountered an error while initializing a data structure required for the correct operation of Turbo ACL processing. Turbo ACL will be disabled until another recompilation has completed successfully.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%COMPILED_ACL-4-ROW_THROTTLE : [chars]: unable to re-queue row [int] on row queue for node [int]; node should not have been freed as it was written to only [int] ms ago
Explanation Unable to requeue row.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%COMPILED_ACL-4-ROW_UPDATE : [chars]: cannot process row queue update for row [int] in node [int]: [chars]
Explanation Error occurred while processing row queue update for given row..
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%COMPILED_ACL-4-ROW_UPDATE_ENQUEUE : [chars]: cannot process row queue update for row [int] in node [int]: enqueue failed ([int]/[int] entries, list is [chars]valid, entry is [chars]enqueued)
Explanation Row queue update 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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..COMP_MATRIX Messages
The following are ISSU Compatibility Matrix messages.
Error Message%COMP_MATRIX-4-DISABLED : Compatibility Matrix has been disabled. No image compatibility checking will be done.
Explanation The ISSU compatibility matrix check has been disabled via configuration command no service image-version compatibility. When the standby comes up, no image compatibility checking will be done, which results in SSO redundancy mode even if the active and standby are running different images.
Recommended Action The ISSU compatibility matrix check has been disabled using the global configuration command no service image-version compatibility. Redundancy mode would be SSO. Ensure this is your intention or change configuration using service image-version compatibility.
Error Message%COMP_MATRIX-3-PRST_VBL_DELETE : ISSU Compatibility Matrix was unable to delete a persistent variable from the [chars] system (rc = [dec]).
Explanation The ISSU compatibility matrix was unable to access a persistent variable. There is no way to determine if issu image-version compatibility checking should be enabled or disabled.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show persistent variable command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%COMP_MATRIX-3-PRST_VBL_GET : ISSU Compatibility Matrix was unable to read a persistent variable from the local system (rc = [dec]).
Explanation The ISSU compatibility matrix was unable to access a persistent variable. There is no way to determine if issu image-version compatibility checking should be enabled or disabled.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show persistent variable command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%COMP_MATRIX-3-PRST_VBL_WRITE : ISSU Compatibility Matrix was unable to write to persistent variables on the [chars] system (rc = [dec]).
Explanation The ISSU compatibility matrix was unable to access a persistent variable. There is no way to determine if issu image-version compatibility checking should be enabled or disabled.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show persistent variable command to gather data that may help identify the nature of the error. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.CONST_DIAG Messages
The following are on-line diagnostics messages.
Error Message%CONST_DIAG-4-DIAG_SUGGEST_ACTION_DUE_TO_FABRIC_CHAN_FLOW_CONTROL : Flow control is occurring in the system. Analyze the system traffic and remove the traffic source that causes flow control.
Explanation Diagnostic test has detected fabric low buffer rate.
Recommended Action Flow control is occurring in the system. Analyze the system traffic and remove the traffic source that causes flow control. Enter the show fabric utilization command to check the overall traffic pattern.
Error Message%CONST_DIAG-4-ERROR_COUNTER_DATA : [chars]
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%CONST_DIAG-4-ERROR_COUNTER_WARNING : Module [dec] Error counter exceeds threshold, system operation continue.
Explanation Unavailable.
Recommended Action Unavailable.
Error Message%CONST_DIAG-3-HM_CONFIG_FAIL : [chars] failed in health monitoring configuration (error code [dec])
Explanation The system has detected an unrecoverable 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/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%CONST_DIAG-3-HM_PORT_ERR_3X : Port [dec] on module [dec] is not allowed to clear err-disabled state due to 3rd series of [chars] failures. Port will remain in err-disabled state.
Explanation The datapath corresponding to the port is bad. The port is kept in err-disabled state.
Recommended Action Reset the line card to see if the problem disappears. 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CONST_DIAG-3-SPA_DIAG_FAILURE : Sub-Module [dec]/[dec] has Major online diagnostic failure. [chars]
Explanation This submodule has a Major online diagnostic failure.
Recommended Action Reseat the submodule. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%CONST_MFIB_LC-6-ADJ_V6MCAST_ALLOC_FAILURE : Failed to allocate Adjacency for IPv6 multicast entry (S[ipv6_addr], G[ipv6_addr])
Explanation The system was unable to allocate an adjacency for this particular flow. The affected flow will be retried and will be software switched until it is successfully installed in the hardware.
Recommended Action The adjacency table utilization could be very high and must be brought down. Removing some hardware switched flows would help solve the problem.
Error Message%CONST_MFIB_LC-6-FIB_MCAST_INSTALL_FAILURE : Failed to install FIB multicast entry (table:[dec], S:[chars], G:[chars])
Explanation The maximum FIB entry limit has been exceeded so the FIB entries cannot be allocated by the CONST_MFIB_LC.
Recommended Action The FIB table utilization is too high and must be reduced. The total number of Multicast shortcuts are too large to fit in the FIB table. As a result, the subsequent shortcuts will be software switched. Reducing the FIB utilization by other protocols would help solve the problem.
Error Message%CONST_MFIB_LC-6-FIB_V6MCAST_INSTALL_FAILURE : Failed to install FIB IPv6 multicast entry (S[ipv6_addr], G[ipv6_addr])
Explanation The FIB entry limit has been exceeded so the FIB entries cannot be allocated by the CONST_MFIB_LC.
Recommended Action The FIB table utilization is too high and must be reduced. The total number of Multicast shortcuts are too large to fit in the FIB table. As a result, the subsequent shortcuts will be software switched. Reducing the FIB utilization by other protocols would help solve the problem.
Error Message%CONST_MFIB_LC-6-MET_MCAST_ALLOC_FAILURE : Failed to allocate MET entries for IP multicast entry (S:[chars], G:[chars])
Explanation The system is unable to allocate MET entries for this particular flow. The affected flow will be retried and will be software switched until it gets successfully installed in the hardware.
Recommended Action The MET utilization could be very high and must be reduced. Removing some hardware switched flows would help solve the problem
Error Message%CONST_MFIB_LC-6-NF_V6MCAST_INSTALL_FAILURE : Failed to install Netflow IPv6 multicast entry (S[ipv6_addr], G[ipv6_addr])
Explanation The multicast entry cannot be installed due to Netflow full condition or a Hash collision.
Recommended Action The NetFlow table utilization is too high and must be reduced. The total number of multicast shortcuts are too large to fit in the NetFlow table. As a result, these shortcuts will be software switched. Removing dynamically created NetFlow IPv6 entries or disabling dynamic NetFlow entry creation would help solve the problem.
Error Message%CONST_MFIB_LC-6-SW_V6MCAST_INSTALL_FAILURE : Failed to install IPv6 multicast entry, due to [chars] (S[ipv6_addr], G[ipv6_addr]), C:[dec])
Explanation The system is unable to install an IPv6 entry due to unrecoverable software failures.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show monitor capture point all and show tech-support commands and your pertinent troubleshooting logs.
Error Message%CONST_MFIB_RP-6-REPLICATION_MODE_CHANGE : Replication Mode Change Detected. Current system replication mode is [chars]
Explanation When automatic detection of the replication mode is enabled, the system will transition to ingress mode when an egress-incapable line card is inserted. The system will transition back to egress mode when the last egress-incapable line card is removed. The transition between ingress and egress modes will cause temporary loss of traffic.
Recommended Action To prevent traffic loss, enter the ipv6 mfib hardware-switching replication-mode ingress command.
CONST_V6 Messages
The following are CONST V6 messages.
Error Message%CONST_V6-3-FIB_EXCEP_OFF : Protocol IPv6 recovered from FIB exception
Explanation A reload of the IPv6 CEF table to hardware FIB TCAM was successful. All IPv6 packets will be switched by the hardware.
Recommended Action No action is required.
Error Message%CONST_V6-3-FIB_EXCEP_ON : Failed to insert an IPv6 prefix in hardware FIB TCAM.
Some IPv6 packets might be dropped. Use "mls cef maximum-routes" to modify the FIB TCAM partition or/and consider a hardware upgrade.
Examine your network and collect the necessary information from this setup.
The only way to recover from this state is by reloading the router.Explanation FIB TCAM Exception. The switch failed to insert an IPv6 entry into thehardware FIB TCAM because the total number of software forwarding entries exceeds the hardware FIB TCAM limit.
Some IPv6 packets might be dropped. Enter the mls cef maximum-routes command to modify the FIB TCAM partition or/and consider a hardware upgrade.
Examine your network and collect the necessary information from this setup. The only way to recover from this state is by reloading the router.Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.CONTROLLER Messages
The following are controller messages.
Error Message%CONTROLLER-5-REMLOCALLOOP : Controller [chars], local loop [chars] [chars]
Explanation A configurable controller entered local loopback.
Recommended Action No action is required.
COPTMONMIB Messages
The following are Cisco optical monitoring MIB messages.
Error Message%COPTMONMIB-3-ENTRYADDFAILED : Registering of the interface with ifIndex [dec] to local data structure failed
Explanation An attemt to make an entry for the registering interface 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%COPTMONMIB-3-ENTRYPRESENT : An entry is already present for the registering interface with ifIndex [dec]
Explanation An entry in the OPTICAL MONITORING MIB is already existing for the registering 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.CPU_INTF_FPGA Messages
The following are CPU interface FPGA messages.
Error Message%CPU_INTF_FPGA-2-DEV_INIT_FAILURE : The CPU Interface FPGA initialization failed due to [chars]
Explanation The CPU Interface FPGA initialization was not successful due toa hardware problem with the boardThis condition will cause packet drops.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%CPU_INTF_FPGA-3-DEV_UNPAUSE_FAIL : Status register is [hex]
Explanation An attempt to un-pause traffic from CPU interface FPGA to backplane intf ASIC timed out. This might lead to traffic disruption.
Recommended Action If normal traffic processing does not resume, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%CPU_INTF_FPGA-4-DEV_WARN_INT : [chars]
Explanation The CPU Interface FPGA received a non-fatal interrupt. This should not effect the normal operation of the device.
Recommended Action No action is required.
Error Message%CPU_INTF_FPGA-2-INT : [chars]
Explanation A fatal interrupt has occurred. The specified device has been re-intialized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%CPU_INTF_FPGA-2-NULL_DEV_OBJECT : The CPU Interface FPGA device object pointer is set to NULL
Explanation The memory location of the CPU Interface FPGA device object is invalid.
Recommended Action The CPU Interface FPGA operation is disabled and the device interrupt is now masked. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%CPU_INTF_FPGA-5-PAUSE_FAIL : FPGA status register is [hex]
Explanation An attempt to pause traffic from CPU interface FPGA to backplane intf ASIC timed out. This might lead to traffic disruption sometimes, depending on the status register value in FPGA. FPGA status register currently reads as [hex].
Recommended Action If normal traffic processing does not resume, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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%CPU_INTF_FPGA-3-QUEUE_ALLOC_FAILED : Failed to allocate queue in the CPU Interface FPGA for SPA in bay ([dec])
Explanation Failed to allocate queue for SPA in the given bay. This might lead to traffic disruption.
Recommended Action If normal traffic processing does not resume, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-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.CRYPTO Messages
The following are encryption messages.
Error Message%CRYPTO-3-CONNID_ALLOC_FAIL : Crypto engine failed to allocate a connection ID for negotiation from [IP_address] to [IP_address]
Explanation The crypto engine has exhausted all available connection IDs or is otherwise malfunctioning.
Recommended Action Decrease the number of concurrent connections or inspect the crypto engine.
Error Message%CRYPTO-6-EZVPN_CONNECTION_DOWN : [chars]
Explanation Ezvpn connection is being closed. The IPsec and IKE security associations will also be brought down along with it.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%CRYPTO-6-EZVPN_CONNECTION_UP : [chars]
Explanation Ezvpn connection is up for the client mentioned. Both IPsec and IKE security Associations are up now.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%CRYPTO-4-EZVPN_SA_LIMIT : [chars]
Explanation The limit for maximum no of ezvpn tunnels that can be setup on the platform has been reached. Active SAs will not be terminated, but no additional SAs can be established until the number of existing SAs decreases.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%CRYPTO-3-EZVPN_VINTERFACE_CREATE_ERR : EZVPN([chars]): Virtual-access interface creation failed
Explanation The virtual-interface feature will not work without a virtual-access interface. The EzVPN configuration is unusable. You can choose to remove virtual-interface configuration from ezvpn as a workaround.
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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%CRYPTO-5-GM_REGSTER : Start registration for group [chars] using address [chars]
Explanation Start registration for one group.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%CRYPTO-4-IKE_DENY_SA_REQ : IKE denied an [chars] SA request from [chars] to [chars] due to [chars]
Explanation Call Admission Control is configured globally or at the IKE level on this device. Consequently an IKE SA request was denied do to the reason described in the error message.
Recommended Action Depending on the reason that the request was denied, either reduce the load on the system so that it can handle new IKE SA requests, or increase the maximum allowed IKE sessions if more are needed.
Error Message%CRYPTO-5-IKE_SA_HA_STATUS : IKE sa's if any, for vip [IP_address] will change from [chars] to [chars]
Explanation This is a notification message for crypto ike sa's changing their HA status .
Recommended Action No action is required
Error Message%CRYPTO-4-IKE_SA_LIMIT : IKE active SA count is [int] but SA limit has been set to [int].
Explanation The IKE SA limit that was set is less than the number of active IKE SA. Active SA will not be terminated but no additional IKE SAs can be established unless the limit is increased or the number of active SAs decreases.
Recommended Action Increase the IKE SA limit if necessary to establish connectivity.
Error Message%CRYPTO-4-IKE_SA_NEGO_LIMIT : IKE in-negotiation SA count currently is [int] but new limit has been set to [int].
Explanation The IKE in-negotiation SA limit that was set is less than the current number of in-negotiation IKE SA. As of a result of this, no more new IKE SAs can be created. However, those already in negotiation are allowed to finish.
Recommended Action Increase the IKE SA limit if necessary to establish connectivity.
Error Message%CRYPTO-3-IKMP_QUERY_KEY : Querying key pair failed.
Explanation Querying public key/private key using subject name failed.
Recommended Action Check the subject name in the certificate.
Error Message%CRYPTO-4-IPSEC_ENC_METHOD_NOT_SUPPORTED_FULL_SPEED : Transform [chars] will run with reduced performance because of IPSec transform [chars]
Explanation Configured encryption algorithm will not run on the hardware encryption card. The transform is still usable, but will run with reduced performance.
Recommended Action If you need to use the full performance of the encryption card, specify another encryption algorithm for the ipsec transform.
Error Message%CRYPTO-4-IPSEC_ENC_METHOD_NOT_SUPPORTED_WITH_IKE : Transform [chars] not usable with IKE because of IPSec transform [chars]
Explanation Configured encryption algorithm not uable with IKE with current hardware configuration.
Recommended Action If you need to negotiate this with IKE, specify a valid encryption algorithm for the ipsec transform.
Error Message%CRYPTO-5-IPSEC_SA_HA_STATUS : IPSec sa's if any, for vip [IP_address] will change from [chars] to [chars]
Explanation This is a notification message for crypto ipsec sa's changing their HA status.
Recommended Action No action is required.
Error Message%CRYPTO-6-ISAKMP_MANUAL_DELETE : IKE SA manually deleted. Do 'clear crypto sa peer [chars]' to manually clear IPSec SA's covered by this IKE SA.
Explanation The IKE SA was deleted by user command. However, keepalives for this connection are enabled, and IPSec SAs covered by this IKE SA still exist. Since this IKE SA is now deleted, these IPSec SAs have no IKE SA covering them. The recommended action is to manually delete this IPSec SAs.
Recommended Action Enter the parser command.
Error Message%CRYPTO-3-MTREE_CMD_BLOCK : Mtree command [dec] was blocked from the the mtree process queue.
Explanation An attempt was made to enqueue a command to the crypto mtree manager process even though IPsec is currently operating in HAPX 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%CRYPTO-6-PRNG_SEED_KEY_ERROR : Pseudo-random number generator seed and seed key was identical
Explanation The X9.17 random number specification requires us to check for the same value appearing as the seed and the seed key. This message indicates that the condition was discovered.
Recommended Action The X9.17 random number will occasionally produce this condition, and this is not a problem. However if this message occurs frequently, the system should be manually reloaded. If the message is persistent across reloads, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%CRYPTO-4-RECVD_PKT_NOT_IPSEC : Rec'd packet not an IPSEC packet. (ip) vrf/dest_addr= [chars]/[IP_address], src_addr= [IP_address], prot= [dec]
Explanation Received packet matched crypto map ACL, but is not IPSEC-encapsulated. IPSEC Peer is sending unencapsulated packets. There may simply be a policy setup error on the peer. Some might consider this a hostile event.
Recommended Action Contact the peer's administrator to compare policy settings.
Error Message%CRYPTO_RSA_ISSU-3-GET_BUFFER : Crypto RSA ISSU client failed to get buffer for message.
Error: [dec] ([chars])Explanation Crypto RSA ISSU client failed to get buffer for building a negotiation message. Thus it cannot send the negotiation message to the standby unit. When there is a problem in the negotiaiton the standby unit cannot be brought up.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show logging and show checkpoint client command to gather data that might help identify the nature of the message. Research and attempt to resolve the 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/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%CRYPTO_RSA_ISSU-3-INIT : Crypto RSA ISSU client initialization failed to [chars]. Error: [dec] ([chars])
Explanation Crypto RSA ISSU client could not be initiailzed, this will cause catstrophic failure when ISSU upgrade or downgrade is performed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%CRYPTO_RSA_ISSU-3-INVALID_SESSION : Crypto RSA ISSU client does not have a valid registered session.
Explanation Crypto RSA ISSU client does not have a valid registered session. When there is a problem with the session the standby unit cannot be brought up.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability entries <client_id> and
show issu session <client_id> and
show issu negotiated capability <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the 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/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%CRYPTO_RSA_ISSU-3-MSG_NOT_OK : Crypto RSA ISSU client message type [dec] is not compatible
Explanation Crypto RSA ISSU client received an incompatible message from the peer unit. Since the message is not compatible it cannot be processed by this unit
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability entries <client_id> and
show issu session <client_id> and
show issu negotiated capability <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the 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/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%CRYPTO_RSA_ISSU-3-MSG_SIZE : Crypto RSA ISSU client failed to get the MTU for message type [dec].
Error: [dec] ([chars])Explanation Crypto RSA ISSU client failed to calculate MTU for the message specified. The dot1x ISSU client will not be able to send message to the standby unit.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability entries <client_id> and
show issu session <client_id> and
show issu negotiated capability <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the 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/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%CRYPTO_RSA_ISSU-3-SEND_NEGO_FAILED : Crypto RSA ISSU client failed to send negotiation message.
Error: [dec] ([chars])Explanation Crypto RSA ISSU client failed to send a session negotiation message to the peer. When there is a problem in the ISSU negotiation the standby unit cannot be brought up.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show logging and show checkpoint client commands to gather data that might help identify the nature of the message. Research and attempt to resolve the 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/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%CRYPTO_RSA_ISSU-3-SESSION_NEGO : Crypto RSA ISSU client encountered unexpected client nego_done.
Error: [dec] ([chars])Explanation Crypto RSA ISSU client encountered an unexpected 'client negotiation done'.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu session <client_id> and
show issu negotiated capability <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the 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/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%CRYPTO_RSA_ISSU-3-SESSION_REGISTRY : Crypto RSA ISSU client failed to register session information.
Error: [dec] ([chars])Explanation Crypto RSA ISSU client failed to register session information. When there is a problem with the session the standby unit cannot be brought up.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu capability entries <client_id> and
show issu session <client_id> and
show issu negotiated capability <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the 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/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%CRYPTO_RSA_ISSU-3-SESSION_UNREGISTRY : Crypto RSA ISSU client failed to unregister session information.
Error: [dec] ([chars])Explanation Crypto RSA ISSU client failed to unregister session information.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu session <client_id> and
show issu negotiated capability <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the 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/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%CRYPTO_RSA_ISSU-3-TRANSFORM_FAIL : Crypto RSA ISSU client [chars] transform failed for message type [dec].
Error: [dec] ([chars])Explanation Crypto RSA ISSU client could not transform the message. If the transmit transformation failed, it means that the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, it means that the checkpoint message cannot be applied on the standby unit. In both cases the Crypto RSA state will not be indentical with the active unit.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show issu session <client_id> and
show issu negotiated version <session_id> commands to gather data that might help identify the nature of the message. Research and attempt to resolve the 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/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%CRYPTO-6-TOKENADMINCHANGEPIN : Cryptographic Token [chars] ADMIN PIN change Successful
Explanation The cryptographic token has accepted the new administrator PIN offered bythe router.
Recommended Action Informational message only. No action required.
Error Message%CRYPTO-3-TOKENADMINLOCKEDOUT : Cryptographic Token [chars] Administrator PIN Locked due to too many unsuccessful login attempts
Explanation The cryptographic token has disabled the Admin PIN due to too many login failures .
Recommended Action If the user PIN is also locked out, it will be necessary to reinitialize the card.The data on the card will be lost.
Error Message%CRYPTO-6-TOKENADMINLOGIN : Cryptographic Token [chars] ADMIN Login Successful
Explanation The cryptographic token has accepted the administrator PIN offered bythe router.
Recommended Action Informational message only. No action required.
Error Message%CRYPTO-3-TOKENADMINLOGINFAILED : Cryptographic Token [chars] ADMIN Login FAILED
Explanation The cryptographic token has rejected the administrator PIN offered by the router.
Recommended Action Enter the crypto pki token admin-pin command to enter the correct PIN.
Error Message%CRYPTO-3-TOKENAPIFAILURE : Cryptographic Token [chars] API FAILED, error = [dec]
Explanation The cryptographic token returned an unexpected 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/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%CRYPTO-6-TOKENCHANGEPIN : Cryptographic Token [chars] PIN change Successful
Explanation The cryptographic token has accepted the new PIN offered bythe router.
Recommended Action Informational message only. No action is required.
Error Message%CRYPTO-3-TOKENCHANGEPINFAILED : Cryptographic Token [chars] Change PIN FAILED
Explanation The cryptographic token has rejected the new PIN offered bythe router.
Recommended Action Be sure you are logged in to the token as admin. Try a longer PIN.
Error Message%CRYPTO-6-TOKENINSERTED : Cryptographic token [chars] inserted in [chars]
Explanation A cryptographic token has been detected.
Recommended Action Informational message only. No action is required.
Error Message%CRYPTO-4-TOKENKEYSDEACTIVATED : RSA keypairs from token [chars] and associated IPSEC sessions being deactivated now
Explanation Router RSA keypairs and associated IPSEC sessionsare being deactivated because the token containing them was removed.
Recommended Action Re-insert the crypto token.
Error Message%CRYPTO-4-TOKENKEYTIMEOUT : RSA keypairs for token [chars] and associated IPSEC sessions will be deactivated in [dec] seconds
Explanation Router RSA keypairs and associated IPSEC sessionswill be deactivated when the timeout expires.
Recommended Action Re-insert the crypto token before the timeout expires.
Error Message%CRYPTO-3-TOKENLOCKEDOUT : Cryptographic Token [chars] PIN Locked due to too many unsuccessful login attempts
Explanation The cryptographic token has disabled the user PIN due to too many login failures.
Recommended Action Enter the crypto pki token admin-pin command to enter correct ADMINISTRATOR PIN.
Error Message%CRYPTO-6-TOKENLOGIN : Cryptographic Token [chars] Login Successful
Explanation The cryptographic token has accepted the PIN offered bythe router.
Recommended Action Informational message only. No action is required.
Error Message%CRYPTO-3-TOKENLOGINFAILED : Cryptographic Token [chars] Login FAILED
Explanation The cryptographic token has rejected the PIN offered bythe router.
Recommended Action Enter the crypto pki token user-pin command to enter correct PIN.
Error Message%CRYPTO-6-TOKENLOGOUT : Cryptographic Token [chars] Logout Successful
Explanation The router has logged out from the cryptographic token.
Recommended Action Informational message only. No action is required.
Error Message%CRYPTO-6-TOKENREMOVED : Cryptographic token [chars] removed from [chars]
Explanation A cryptographic token has been detected.
Recommended Action Informational message only. No action is required.
Error Message%CRYPTO-6-TOKENSTOREKEY : Key [chars] stored on Cryptographic Token [chars] Successfully
Explanation A new keypair has been written out to the cryptographic token.
Recommended Action Informational message only. No action is required.
Error Message%CRYPTO-3-TOKENSTOREKEYFAILED : Key [chars] store on Cryptographic Token [chars] Failed
Explanation An error occurred attempting to write a new keypair out to the cryptographic token.
Recommended Action Try logging in to the token. If this message recurs, try logging in as administrator.
Error Message%CRYPTO-6-TOKENTIMEOUTCANCELLED : Cryptographic Token [chars] re-inserted. removal timeout cancelled
Explanation A cryptographic token containing private keyfiles has been re-inserted in time.Router RSA keypairs and associated IPSEC sessionswill be NOT be deactivated.
Recommended Action Informational message only. No action is required.
Error Message%CRYPTO-6-VPN_TUNNEL_STATUS : [chars]
Explanation VPN tunnel status.
Recommended Action No action is required.
CRYPTO_HA_IKE Messages
The following are Crypto High Availability messages.
Error Message%CRYPTO_HA_IKE-4-CRYPTO_HA_NOT_SUPPORTED_BY_HW : Crypto hardware is enabled and it does not support HA operation '[chars]'
Explanation Crypto Hardware is enabled, but the hardware does not support HA operations like insert/extract of keys.
Recommended Action Replace Cryto hardware with one that support HA operations or disable the hardware to use software crypto engine.
Error Message%CRYPTO_HA_IKE-3-FAILOVER_ERROR : Attempt to failover IKE SA ([IP_address]:[IP_address]) failed due to [chars]. No stateful failover available for this SA.
Explanation The HA Active device attempted to checkpoint the state of an IKE SA to the Standby, but the Standby device was unable to create the Standby IKE SA.
Recommended Action Look for other error messages at log level WARNING or turn on debugs to look for the specific reason of the failure.
CRYPTO_HA_IPSEC Messages
The following are Crypto High Availability messages.
Error Message%CRYPTO_HA_IPSEC-4-CRYPTO_HA_NOT_SUPPORTED_BY_HW : Crypto hardware is enabled and it does not support HA operation '[chars]'
Explanation Crypto hardware is enabled, but the hardware does not support HA operations such as insert or extract keys.
Recommended Action Replace Crypto hardware with one that supports HA operations or disable the hardware to use software the crypto engine.
Error Message%CRYPTO_HA_IPSEC-3-FAILOVER_ERROR : Attempt to failover IPSec SA ([IP_address]:[IP_address]) failed due to [chars]. No stateful failover available for this SA.
Explanation The HA Active device attempted to checkpoint the state of an IKE SA to the Standby, but the Standby device was unable to create the Standby IKE SA.
Recommended Action Look for other error messages at log level WARNING or turn on debugs to look for the specific reason of the failure.
Error Message%CRYPTO_HA_IPSEC-3-HA_IPSEC_UPDATE_PROC_FAIL : Start of HA IPSec update process failed
Explanation Starting of the IPSec HA process failed Updates will not be sent from active to standby.
Recommended Action The system might need to be re-booted if this is a part of an IPSec HA setup.
CWAN_ATOM Messages
The following are CWAN ATOM messages.
Error Message%CWAN_ATOM_HA-3-CF_ERROR : [chars] [dec]
Explanation Platform ATOM HA CF client 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/pcgi-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%CWAN_ATOM_HA-2-ISSU_ERROR : [chars] [chars]
Explanation Platform ATOM HA ISSU client 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/pcgi-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%CWAN_ATOM_HA-3-RF_ERROR : [chars] [dec]
Explanation Platform ATOM HA RF client 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/pcgi-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.CWAN_CHOC Messages
The following are Cat6K Channelized OC48/OC12 Route Processor (RP) driver messages.
Error Message%CWAN_CHOC-4-CORRUPT : [chars] information seems to be corrupted, bad value =[int]
Explanation Incorrect parameters were detected internally.
Recommended Action This is only a debug warning message. The unexpected value is discarded.
CWAN_FWD_TABLES Messages
The following are Constellation WAN forwarding tables messages.
Error Message%CWAN_FWD_TABLES-3-CHUNK_CREATE_FAIL : [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CWAN_FWD_TABLES-3-CHUNK_DESTROY_FAIL : [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CWAN_FWD_TABLES-3-CHUNK_MALLOC_FAIL : [chars]
Explanation This error is seen when there is a problem with internal software coding. It should not be seen under normal 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CWAN_FWD_TABLES-3-ENTRY_BUILD_FAIL : [chars] [int]
Explanation This error is seen when there is a problem with internal software coding. It should not be seen under normal 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CWAN_FWD_TABLES-3-INVALID_DEST_INFO : [chars] [hex] [hex] [hex]
Explanation This error is seen when there is a problem with internal software coding. It should not be seen under normal 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-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%CWAN_FWD_TABLES-3-INVALID_INDEX : [chars] [int]