Table Of Contents
CWAN_POSEIDON Messages
The following are OSR GE-WAN RP driver messages.
Error Message%CWAN_POSEIDON-4-CREATEFAIL : IM Driver Creation Failed: Interface [chars]
Explanation Driver failed to create interface with Interface Manager operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%CWAN_POSEIDON-4-DESTROYFAIL : IM Driver Destroy Failed: Interface [chars]
Explanation Driver failed to destroy interface with Interface Manager operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%CWAN_POSEIDON-4-RCVADDRFAIL : IM Driver RCVADDR Failed: Interface [chars]
Explanation Driver failed to register receive address with Interface Manager operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%CWAN_POSEIDON-4-REGISTERFAIL : IM Registration Failed: [chars]
Explanation Driver failed to register with Interface Manager operation.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
CWAN_RP Messages
The following are Constellation WAN RP messages.
Error Message%CWAN_RP-6-CARDRECONCILE : Module type changed on slot [int]/[int] from [int] to [int]
Explanation The WAN module has booted, and it has been detected that it is of a different type than the WAN module that was previously in this slot.
Recommended Action No action is required.
Error Message%CWAN_RP-4-CONFIG_MISMATCH :
Irreconcilable Configuration difference between Active & Standby Supervisors due to OIR/Config Event -> Reloading Standby Supervisor to synchronize the configuration.
Explanation Unexpected configuration difference between Supervisors.
Recommended Action No action is required. This is expected behavior.
Error Message%CWAN_RP-4-EMPTY_CWANBAYS : FLEXWAN in slot [dec] is empty. Please remove the Flexwan or insert it with atleast one PA
Explanation The FLEXWAN in the specified slot does not contain any Port Adapters.
Recommended Action The FLEXWAN should be removed as this is an unsupported configuration
Error Message%CWAN_RP-3-FAILED_CONFIG : Failed to send line card config message [chars] for slot [int] port [int]
Explanation The RP could not send the specified configuration message to the line 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. 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_RP-3-IFCFG_CMD_NOT_OWNER : Process '[chars]' waiting for interface configuration command ([hex]) to slot [int]/[int] without acquiring lock owned by process '[chars]'
Explanation A process on the RP sent an configuration command to the slot specified in the message and a different process waited for the result. This could cause incorrect line card configuration states.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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_RP-4-IFCFG_CMD_TIMEOUT : Interface configuration command ([hex]) to slot [int]/[int] timed out
Explanation The RP sent an configuration command to the slot specified in the message and received no confirmation for the command.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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_RP-4-INCR_CFG_SYNC_FAIL : 7600 incremental running-config sync for [[dec]/[dec]] failed - [chars]([dec]), Reload Standby
Explanation The specified 7600 incremental running-config synchronization failed.
Recommended Action Power cycle the redundant supervisor .
Error Message%CWAN_RP-4-INVALID_UNIT : Invalid 7600 Unit: [[dec]/[dec]].
Explanation The specified 7600 slot/cpu is beyond the Chassis' limit.
Recommended Action Power cycle the redundant supervisor.
Error Message%CWAN_RP-3-IPCPORTFAIL : Failed to open IPC port '[chars]' [chars] with error [chars]
Explanation The RP failed to open a port for communication with a WAN module.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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_RP-6-LC_RESET : The RP is reloaded, resetting slot [dec] is necessary. Please ignore errors if any, till the linecard comes up.
Explanation If the system is running Catalyst operating system software on the supervisor engine and Cisco IOS software on the MSFC, the WAN line cards that power up before the RP powers up will be reset automatically.
Recommended Action No action is required.
Error Message%CWAN_RP-6-NOPWRISSU : Spa inserted in [chars] powered down because ISSU is in progress
Explanation The Spa insertion detected during ISSU upgrade process. It will be acted on upon completion of the ISSU process.
Recommended Action No action is required.
Error Message%CWAN_RP-3-WAN_BRIDGING_CFG_EXCD : The number of VPLS/EoMPLS/Bridging/QinQ VCs exceeded the maximum([int]) supported by slot: [int] [chars]
Explanation The user has attempted to configure more VPLS, EoMPLS and Bridging VCs than the number that is supported by the platform.
Recommended Action Review the configuration guidelines for the features that are being configured and reduce the number of VPLS, EoMPLS and Bridging to the number that is supported by the platform.
CWAN_RP_COPP Messages
The following are CWAN CoPP messages.
Error Message%CWAN_RP_COPP-3-BAD_IPC_MSG : A corrupt IPC message has been received from slot [dec], size [dec]
Explanation The Inter Processor Communication (IPC) infrastructure used by the per-user Control Plane Policing and Protection functionality received a message on the route processor from the given slot and detected that the message is of an unexpected size. This could mean that the message is corrupted, and the desired functionality intended by the message will not be operational.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support ipc and show platform copp rate-limit all 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%CWAN_RP_COPP-3-IPC_FAILED : IPC Messaging to slot [dec] failed, error code = [dec]
Explanation The Inter Processor Communication (IPC) infrastructure used by the per-user Control Plane Policing and Protection functionality encountered a failure on the route processor while attempting to send an IPC message to the line card in the given slot. This could result in the intended functionality becoming fully or partly non-operational on the line card.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support ipc 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%CWAN_RP_COPP-3-IPC_INIT_FAILED : IPC initialization failed.
Explanation The Inter Processor Communication (IPC) infrastructure used by the per-user Control Plane Policing and Protection functionality encountered a failure while initialization on the route processor. This could result in the communication channel between the route processor and the line cards becoming non-operational with respect to the CoPP functionality, and no rate limiters would be enabled on the line card if the user thresholds for packet rates exceeds those on the route processor.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support ipc 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%CWAN_RP_COPP-7-RATE_EXCEEDED : RP detected rate exceed for [chars] on [chars] when LC policing is On
Explanation The per-user Control Plane Policing and Protection infrastructure on the route processor detected that the rate for the given protocol on the given interface exceeds the configured rate even though a rate limiter on the interface is already active on the line card for that protocol. This can probably be transient event, because of few packets escaping the policer because of its accuracy limitations. It is normal to see this behavior occasionally, especially if the packet rate is in the border line of the configured rate.
Recommended Action If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show platform copp rate-limit all 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%CWAN_RP_COPP-6-RL_DISABLED : Rate limiter disabled on [chars] for [chars]
Explanation This message indicates that the per-user rate limiter for the protocol on the given interface on the line card has been disabled by the route processor. The route processor will continue to police the interface, and only the rate limiter on the line card will be disabled, for performance reasons.
Recommended Action If you have configured for automatic un-installation of rate limiters by configuring platform copp observation-period <timeout>, then this message indicates that the rate limiter on the interface was disabled automatically, since it showed normal packet rate for the configured duration. No action needs to be done in this case. If the automatic un-installation has not been configured, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/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_RP_COPP-5-RL_ENABLED : Rate limiter enabled on [chars] for [chars] at [dec][chars]
Explanation This message indicates that the route processor detected that the per-user rate for the given user and protocol has exceeded the configured rate as per the per-user Control Plane Policing and Protection functionality, and thus a rate limiter has been automatically installed on the line card for this interface and protocol.
Recommended Action The per-user rates can be exceeded because of a number of reasons including a power cycle of a connected device, or a genuine requirement from the user side for a high packet rate, or an attempt at denial of service attack on the box by a user. Enter the show platform copp rate-limit <protocol> command to see if exceeded packet count for the interface is too high. Also see if the rate limiters are enabled on several interfaces. Check if the high rate is due to an activity like power cycle of a connected device. If so, this behavior is expected, and just indicates that the system is protecting itself against a high processing requirement for too many packets at the same time. No action is required immediately in this case. Continue monitoring the system for more time and see if the attack subsides. If there was no power cycle on neighboring devices, then see if the dropped count on the interface remains high for longer duration. If the high rate is a transient event, then this can be ignored, and you can disable the rate limiter on the line card by entering the platform copp <interface> <protocol> off command. You might also consider configuring for automatic un-installation of rate-limiters on the line card using the platform copp observation-period <timeout> configuration, so that manual intervention can be avoided for performing this operation. If this interface is under attack for a long duration, then you might consider administrative activities to get more information regarding the affected user, and evaluate the reasons for the high packet rate.
Error Message%CWAN_RP_COPP-3-UNEXPECTED_STATS : Stats for [chars] received on [chars] when the LC policer is not On
Explanation The Inter Processor Communication (IPC) infrastructure used by the per-user Control Plane Policing and Protection functionality received a statistics message from the line card for a rate limiter on the given interface and protocol. However, as per the information on the route processor, there were no rate limiters enabled on the line card for this interface and protocol.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show platform copp rate-limit all debug 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%CWAN_RP_COPP-3-UNKNOWN_IPC_MSG : Unknown IPC message id [dec] received from slot [dec]
Explanation The Inter Processor Communication (IPC) infrastructure used by the per-user Control Plane Policing and Protection functionality received a message on the route processor from the given slot and detected that the message is of an unexpected type. This could mean that the message is corrupted, and the desired functionality intended by the message will not be operational.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support ipc and show platform copp rate-limit all 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.CWAN_SLOT Messages
Error Message%CWAN_SLOT-1-CF_ADDFAILED :
Failed to register chkpt client, client = [dec]
Explanation The CF client could not be registered.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/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_SLOT-1-CF_NOBUF :
Failed to get chkpt buffer, client = [dec]
Explanation Failed to get enough memory for checkpointing.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
CWAN_SPA Messages
The following are CWAN Shared Port Adapter messages.
Error Message%CWAN_SPA-3-DIAG_CONFIG : [chars] did not complete [dec]/[dec]
Explanation An error has occured during diagnostic test.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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_SPA-3-FAILURE : [chars]: SPA failure - cause: [chars] ([hex]), recovery action: [chars] ([dec])
Explanation The SPA failed for the specified reason.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/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_SPA-3-NULL_ATM_DB : Unable to create ATM DB for [chars]
Explanation Data required to support the interface is not available.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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_SPA-3-POWER_CYCLE : [chars] occurred on Shared Port Adapter [int]/[int]
Explanation An error has occurred which will cause the Shared Port Adapter to be power cycled.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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_SPA-3-SPA_CREATION_FAILURE : slot=[dec] subslot=[dec], PID=[chars] lc_type=[hex].
Explanation Failed to create a SPA object.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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.CWPA Messages
The following are Constellation Copperhead messages.
Error Message%CWPA-4-HEADER_TOO_BIG : Needs [dec] bytes, with only [dec] bytes available. Packet size [int], received from [chars], buffer [hex] packet start [hex]:
[hex]:[hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]
[hex]:[hex] [hex] [hex] [hex] [hex] [hex] [hex] [hex]
Explanation A packet was sent from the PA to either the route processor or the line card. That packet did not have enough available space to append the header. A new particle has been linked to the packet to store the header.
Recommended Action No action is required.
Error Message%CWPA-3-PROCCREATEFAIL : Failed to create [chars] process
Explanation The line card failed to create a process which is necessary for proper functioning of the line 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. 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. If it is the stats export process, then you might not see input/output rate and bytes getting incremented in show interface output for flexwan/flexwan2 non- channelized interfaces. However, you can get the statistics from show interface acc or show interface stats.CWPA_BRIDGE Messages
The following are CWPA Bridging messages.
Error Message%CWPABRIDGE-3-BADLTL : [chars] got bad LTL index [hex] for vlan [int] ckt_id [int] sent from RP
Explanation RP has provided the linecard with an invalid value for Local Target Logic index value.
Recommended Action If the bridging traffic stops going through, copy the message exactly as it appears on the console or in the system log. Enter the show log, show cwan bridge, show atm vlan, show mac-address-table dynamic detail, and show cwan ltl commands on the RP console exec prompt. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/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.CWRPSPA Messages
The following are Shared Port Adapter on OSR RP messages.
Error Message%CWRPSPA-6-CARDRELOAD : Module [int] reload due to SPA insert in [int]/[int].
Explanation When inserting a SPA on this carrier card, the cardis reset.
Recommended Action No action is required.
Error Message%CWRPSPA-3-MAX_SPA : Power to IPSEC-SPA-2G in [chars] is denied because it has exceeded the number allowed([dec])
Explanation The number of IPSEC-SPA-2Gs in a chassis is limited. This message is displayed when the number of IPSEC-SPA-2Gs inthe chassis has exceeded this limit.
Recommended Action Use only the number of supported IPSEC-SPA-2Gs.
Error Message%CWRPSPA-5-OUT_OF_RESOURCES : [chars]: Unable to create [chars] due to SPA resource limitations.
Explanation The SPA was unable to create the requested resource due to limited hardware or software resources.
Recommended Action No action is required.
Error Message%CWRPSPA-4-SPA_CMD_NO_RESP : [chars]: No response for interface configuration command "[chars]"
Explanation A timeout occurred while RP was waiting for a response from line card. This might happen due to line card CPU being too busy to respond to the command.
Recommended Action No action is required.
Error Message%CWRPSPA-3-SPA_NO_HOST_INFO : slot [dec] subSlot [dec], PID [chars]
Explanation Failed to get information about the host line 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. 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%CWRPSPA-4-SPA_RESP_CMD_MISMATCH : [chars]: Expecting response to interface configuration command "[chars]" but received response to command "[chars]".
Explanation An internal synchronization error occurred while configuring the interface. The configuration might not have succeeded.
Recommended Action Check that the running configuration for the interface is correct. If this message occurred on the standby, try reloading the standby to ensure that its configuration is in sync. 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.CWSLC Messages
The following are FlexWAN-II and SIP-1 messages.
Error Message%CWSLC-3-DIAGSKIP : Skipped diag for port [dec]
Explanation The line card skipped diagnostics for port.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%CWSLC-3-DIAGWARNING : Backplane DIP switches settings incorrect
Explanation DIP switches need to be set properly.
Recommended Action Refer to the Cisco 7600 SIP and SPA Hardware Installation Guide for information on how DIP switches are to be set.
CWTLC Messages
The following are Constellation WAN Toaster line card messages.
Error Message%CWTLC-3-ATMTXFIFO : [chars]
Explanation The OSM line card has encountered an error with the FPGA that has caused the FIFO queue to exceed the maximum limit. This condition will cause the system to crash.
Recommended Action This error will result in a crash. Collect the crashinfo file in line card, traffic parameters and configuration that triggered the issue, then copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%CWTLC-3-BAD_IFCOMTYPE : Bad ifcom message type=[int]
Explanation The Route Processor (Draco) passed down a message that the software was not prepared to handle.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc., and then copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%CWTLC-3-BADINT : Attempted to access HWIDB for port [int]
Explanation The line card attempted to access structure for interface associated with a non-existent port.
Recommended Action Check if reload of the line card helps, else copy the message exactly as it appears on the console or in the system log. Enter the show diagbus <slno>, from RP, show idb and show cwan vlans from Line card 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%CWTLC-3-BADINTCREATE : Attempted to install HWIDB for port [int]
Explanation The line card failed to install a structure for interface because the associated port number was out of range.
Recommended Action Check if reload of the line card helps, elseCopy the message exactly as it appears on the console or in the system log. Enter the show diagbus <slno>, from RP, show idb, and show cwan vlans from line card 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%CWTLC-3-BADMALUCMD : Unsupported MALU command [dec], arg=[hex], pascb=[hex]
Explanation The Route Processor (Draco) passed down a command that the software was not prepared to handle.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc., and then copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%CWTLC-3-BADMALUCMD2 : Unsupported MALU cmd/arg0=[hex][hex], arg1arg2=[hex][hex], hwidb=[chars]
Explanation The Route Processor (Draco) passed down a command that the software was not prepared to handle.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc., and then copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%CWTLC-5-BUS_SEQ_ERR : Constellation bus Sequence Error. Resetting port ASICS.
Explanation The SP has detected a sequence error on the backplane bus of the OSM. A reset sequence from the EARL has been called to recover from this error. System traffic should recover and continue normally.
Recommended Action If traffic recovers, no action is required. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%CWTLC-3-CMDNOINT : HWIDB Null for command [dec], arg=[hex]
Explanation The Route Processor (Draco) passed down a command that the software was unprepared to handle.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc., and then copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%CWTLC-3-CONST_SWITCHING_BUS_INTERFACE_ASIC_ERR : Constellation Switching Bus Interface Asic [[dec]] error: [chars]
Explanation The CWTLC Switching Bus Interface ASIC received an error.
Recommended Action No action is required if traffic recovers. Otherwise, copy the message exactly as it appears on the console or in the system log. Enter the show platform hardware sculptor fatal, show platform hardware sculptor drop, show platform hardware sculptor errors, and show platform hardware sculptor registers in line card 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%CWTLC-3-CONST_SWITCHING_BUS_INTERFACE_ASIC_HWERR : Constellation Switching Bus Interface Asic [[dec]] HW error: [chars]
Explanation The CWTLC Switching Bus Interface ASIC received a HW error and will be reset.
Recommended Action No action is required if traffic recovers. Otherwise, copy the message exactly as it appears on the console or in the system log. Enter the show platform hardware sculptor fatal, show platform hardware sculptor drop, show platform hardware sculptor errors and show platform hardware sculptor registers 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%CWTLC-5-DATAPATH_RECOVERY_PATCH : EARL reset patch invoked.
Explanation The ASIC on the OSM line card has been reset so that it can recover from constellation bus sequence error. This condition usually occurs under stress traffic with HA-related switchover or a line card OIR operation.System traffic should recover and continue normally.
Recommended Action If traffic recovers, no action is required. Otherwise, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%CWTLC-3-DMA_ENGINE_ASIC_ERR : DMA Engine Asic [[dec]] error: [chars]
Explanation The CWTLC DMA Engine ASIC received an error.
Recommended Action No action is required if traffic recovers. Otherwise, copy the message exactly as it appears on the console or in the system log. Enter the show platform hardware vanallen errors, and show platform hardware vanallen registers in line card 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%CWTLC-0-DMA_ENGINE_ASIC_FATAL_ERR : DMA Engine Asic[[dec]] fatal error: [chars]
Explanation The CWTLC DMA Engine ASIC received a fatal error.
Recommended Action This error will result in a crash. Collect the crashinfo file in line card, traffic parameters and configuration that triggered the issue, then copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%CWTLC-3-EXCEPTION_ERR : [chars]
Explanation The Optical Services Module line card has encountered an error exception.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/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%CWTLC-3-FABRIC_INTERFACE_ASIC_FATAL : OSM Fabric Interface ASIC Fatal Error. ERROR CODE: [chars]
Explanation The OSM Fabric Interface ASIC received a FATAL ERROR.
Recommended Action No action is required if traffic recovers. Otherwise, copy the message exactly as it appears on the console or in the system log. Enter the show platform hardware medusa registers and show platform hardware medusa interrupt from line card 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%CWTLC-6-FABRIC_INTERFACE_ASIC_MODECHANGE : Fabric Interface Asic switching bus Mode changed to [chars]
Explanation The Supervisor has changed the CWTLC Fabric Interface Asic switching bus mode.
Recommended Action No action is required.
Error Message%CWTLC-3-FABRIC_INTERFACE_ASIC_PXF : CWAN PXF Client [[dec]] Not Running
Explanation An ASIC device on the OSM has detected that the designated PXF client is not running.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%CWTLC-5-FABRIC_INTERFACE_ASIC_RE_INIT : Fabric Interface Asic Re-initialize.
Explanation The OSM Fabric Interface ASIC is being re-initialized because of system backplane bus sequence error or fatal ASIC error or on Line card itself.
Recommended Action No action is required if traffic recovers. Otherwise, copy the message exactly as it appears on the console or in the system log. Enter the show platform hardware medusa registers, and show platform hardware medusa interrupt from line card 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%CWTLC-4-FABRICSYNCERRS : [dec] Fabric sync error events in 100ms period
Explanation The CWTLC Cross Bar Switch Fabric interface encountered more synchronization error events than the Supervisor synchronization error threshold allows.
Recommended Action The line card has notified the Supervisor and the fabric interface will be resynchronized. No action is required.
Error Message%CWTLC-4-FABRICSYNC_REQ : Fabric resync requested due to [dec] fabric errors in last 100ms
Explanation The CWTLC Cross Bar Switch Fabric interface encountered more synchronization error events than the Supervisor synchronization error threshold allows.
Recommended Action The line card has notified the Supervisor and the fabric interface will be resynchronized. No action is required.
Error Message%CWTLC-2-FATAL_ATM : [chars]
Explanation The OSM card has encountered a fatal line management interrupt. This error is not recoverable and will cause the system to crash.
Recommended Action This error will result in a crash. Collect the crashinfo file in line card, traffic parameters and configuration that triggered the issue and then copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%CWTLC-0-FATAL_EXCEPTION : [chars]
Explanation The Optical Services Module line card has encountered a fatal exception.
Recommended Action This error will result in a crash. Collect the crashinfo file in line card, traffic parameters and configuration or event that triggered the issue and then copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%CWTLC-3-FR_CHANGEDLCI : frame relay p2p if_number([int]) and dlci([int]) mismatch: [chars] old dlci [int]
Explanation New dlci update comes on a different interface than previous update.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show frame-relay pvc, and in RP show platform frame-relay in Line card 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%CWTLC-3-FR_INTLEVEL : unexpected interrupt level invocation of frame-relay handler:[chars] if_number([dec]) dlci([dec])
Explanation Some feature code inadvertently invoked the linecard frame-relay handler which is designed to run at process-level. This might lead to data corruption and linecard crash.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show frame-relay pvc, in RP and show platform frame-relay in Line card 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%CWTLC-3-FR_RX_TVC : RX_TVC greater than max for [chars] if_number([dec]) dlci([dec])
Explanation The system encountered an error while it was configuring the frame-relay connection. Trying to access the internal resources out of bounds.
Recommended Action Collect the details that triggered the issue, such as any configuration change,switchover etc and then copy the message exactly as it appears on the console or in the system log. Enter the show frame-relay pvc in RP, show platform frame-relay and show platform toaster intfid all in Line card 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%CWTLC-3-INVALID_IF_IDX : invalid if_index ([dec])
Explanation CWTLC received a command with invalid interface index.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc., and then copy the message exactly as it appears on the console or in the system log. Enter the show idb and show cwan vlans from Line card 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%CWTLC-3-IPCALLOCFAIL : Failed to allocate IPC buffer [chars]
Explanation The line card failed to allocate a buffer for communication with the Route Processor (Draco).
Recommended Action Copy the message exactly as it appears on the console or in the system log. Entere the show diagbus <slno> from RP, show memory failures alloc and show memory from Line card 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%CWTLC-3-IPCSENDFAIL : Failed to send IPC message [chars]
Explanation The line card failed to send a message to the Route Processor (Draco).
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc., and then copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%CWTLC-3-LL_FAIL : [chars]: loveletter failed. [chars]
Explanation failed to send loveletter to RP. Either no memory or IPC send failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show frame-relay pvc, show diagbus <slno> in RP, show platform frame-relay, show memory failures alloc and show memory from Line card 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%CWTLC-3-LVLTRTOOBIG : Loveletter length exceeds max, [int] bytes
Explanation The line card attempted to send a large message to the Route Processor (Draco).
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc., and then copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%CWTLC-3-MCAST_REPL_ENGINE_FATAL : Multicast Replication Engine Asic Fatal Error. Resetting ASIC.
Explanation The OSM Multicast Replication Engine ASIC received a FATAL ERROR.
Recommended Action No action is required if traffic recovers. Otherwise, copy the message exactly as it appears on the console or in the system log. Enter the show platform hardware titan registers, and show platform hardware titan errors from line card 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%CWTLC-3-NODISPATCH : Dispatch vector Null, cmd=[dec], dintf=[dec]
Explanation An internal Command sent from RP to LC has not been dispatchedproperly.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc., and then copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. 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%CWTLC-3-NOFABRICPROCESS : No fabric process created
Explanation The CWTLC Cross Bar Switch Fabric interface does not have a link process running: the system failed to create this process. This module will not support the fabric interface
Recommended Action Check if reload of the Line card helps, else copy the message exactly as it appears on the console or in the system log. Enter the show fabric from RP'show processes memory and show processes cpu in Line card commands to gather data that might help identify the nature of the message. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/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%CWTLC-3-NOMEM : [chars]
Explanation The OSM card could not obtain statistics due to a memory exhaustion.
Recommended Action 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. Enter the show diagbus <slno> in RP, show memory failures alloc and show memory from Line card 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%CWTLC-3-NO_STATID : PXF([dec]): no stat_id is available for statistics collection
Explanation The OSM line card has used up all statistics collection resources. No more resources available for further statistics collection.
Recommended Action Reduce number of features configured on this PXF. If conditions warrant, copy the message exactly as it appears on the console or in the system log. Enter the show platform vtms queue, how platform system-drop and show platform toaster stats all from line card 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%CWTLC-3-NULLIFHWIDB : no hwidb (if index [dec])
Explanation CWTLC hwidb pointer is null.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc., and then copy the message exactly as it appears on the console or in the system log. Enter the show idb, show cwan stats and show cwan vlans from Line card 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%CWTLC-2-PCITIMEOUT : Fatal Local I-O Bus [dec] Timeout Addr = [hex]
Explanation The Optical Services Module has encountered a PCI timeout.
Recommended Action Collect the details that triggered the issue, such as oir of linecard, switchover, etc., and then copy the message exactly as it appears on the console or in the system log. Enter the show pci hardware and show pci controller from the line card 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%CWTLC-5-PENDING_PATCH : Invoke pending data recovery patch.
Explanation The ASIC on the OSM line card has been reset so that it can recover from backplane switching bus sequence errors or local hardware ASIC errors. This condition usually occurs under stress trafficwith HA-related switchover or a line card OIR