Table Of Contents
C6K_MWAM_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.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 config.
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. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/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 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-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.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_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.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-7-CFIB_EXCEPTION : FIB TCAM exception, Some entries will be software switched
Explanation FIB TCAM free blocks do 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%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.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 Messages
The following are CFM messages.
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.
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.
CFM_CONST Messages
The following are CFM on Constellation messages.
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.
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