Table Of Contents
FABRIC Messages
The following are Fabric Interface ASIC (FIA) messages.
Error Message%FABRIC-5-CANNOT_SUPPORT_FP_INVERSION : The module you have installed in slot [dec] is running an older revision of firmware/software which might cause inconsistent system behavior. Refer to the release notes for a minimum recommended software release for mentioned module.
Explanation The module specified in the log cannot support FP bit inversion with the current software/firmware release, fabric clear block will disregard COS setting for this module.
Recommended Action No action is required.
FABRIC_INTF_ASIC Messages
The following are Switch Fabric interface ASIC messages.
Error Message%FABRIC_INTF_ASIC-5-CHAN_LINK_SPEED_OOB : Array access bounds violated, channel_num=[int], link_num=[int], speed=[int]
Explanation IOS code has attempted to access an an internal array with an invalidindex for SSA channel number or link number or speed.
Recommended Action No action is required if there is no system impact. If traffic stops or line card fails, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%FABRIC_INTF_ASIC-4-DEV_CONFIG_FAIL : The Switch Fabric interface ASIC configuration failed
Explanation The Switch Fabric interface ASIC was not successfully configured.
Recommended Action The Switch Fabric interface ASIC could not be configured. If the switch fabric has gone inactive (down), this message can be expected. If the module comes online and traffic processing resumes, ignore this message. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show logging and show version 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%FABRIC_INTF_ASIC-5-DEV_INIT_FAILURE : The Switch Fabric interface ASIC initialization failed
Explanation The Switch Fabric interface ASIC was not successfully initialized.
Recommended Action The Switch Fabric interface ASIC could not be initialized. As a result, this device is not operational and has been disabled. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%FABRIC_INTF_ASIC-4-FABRICCRCERRS : [dec] Fabric CRC error events in 100ms period
Explanation The Switch Fabric interface Fabric interface encountered more crc error events than the Supervisor crc error threshold allows.
Recommended Action The line card has notified the Supervisor and the error has been logged. No action is required.
Error Message%FABRIC_INTF_ASIC-5-FABRICDOWN_CRCERRS : [dec] Fabric CRC error events in 100ms period
Explanation The Switch Fabric interface Fabric interface encountered more CRC errors than the maximum configured threshold. However, the reason for this error is that the switch fabric is inactive (down). The line card has notified the Supervisor of this condition and the error has been logged.
Recommended Action This message indicates normal system operation. No action is required.
Error Message%FABRIC_INTF_ASIC-5-FABRICDOWN_SYNCERRS : [dec] Fabric sync error events in 100ms period
Explanation The Switch Fabric interface Fabric interface encountered more synchronization errors than the maximum configured threshold. However, the reason for this error is that the switch fabric is inactive (down).
Recommended Action This message indicates normal system operation. No action is required.
Error Message%FABRIC_INTF_ASIC-5-FABRICSYNC_DONE : Fabric sync on [chars] channel done.
Explanation The fabric interface ASIC was resynchronized.
Recommended Action No action is required.
Error Message%FABRIC_INTF_ASIC-5-FABRICSYNC_REQ : Fabric ASIC [dec]: Fabric sync requested after [dec] sync errors on serial channel [dec]
Explanation The line card has requested that the supervisor engine resynchronize its fabric interface ASIC.
Recommended Action No action is required.
Error Message%FABRIC_INTF_ASIC-5-NOFABRICPROCESS : The Switch Fabric interface fabric process could not be created
Explanation The Switch Fabric interface 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 Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%FABRIC_INTF_ASIC-5-NULL_DEV_OBJECT : The Switch Fabric interface device object pointer is set to NULL
Explanation The memory location of the Switch Fabric interface device object is invalid.
Recommended Action The Switch Fabric interface ASIC operation is disabled and the device interrupt is now masked. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%FABRIC_INTF_ASIC-5-SMB_ACCESSERROR : The Module Switch Fabric interface ASIC cannot be accessed
Explanation The Switch Fabric interface ASIC access (read or write) failed.
Recommended Action The serial bus that connected to the Switch Fabric interface ASIC on this module is not functioning correctly. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.FEC_ISSUE Messages
The following are the FEC_ISSUE messages.
Error Message%FEC_ISSU-3-BUFFER : FEC ISSU client failed to get buffer for message, error [dec]
Explanation The FEC ISSU client failed to get buffer for building a negotiation message. Hence, it can send the negotiation message to the standby unit. When there is a problem in the negotiation the standby unit cannot be brought up.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%FEC_ISSU-3-CAPABILITY : FEC ISSU client [chars]
Explanation The FEC SWITCH ISSU client observed an error during the capability negotiation. When this error happens there is a mismatch between the client capability between the active and standby unit.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%FEC_ISSU-3-INIT : FEC ISSU client initialization failed at [chars], error [chars]
Explanation The FEC ISSU client could not be initialized. This will cause catastrophic failure when the ISSU upgrade or downgrade is performed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%FEC_ISSU-3-MSG_NOT_OK : FEC ISSU client message [dec] is not compatible
Explanation The FEC ISSU client received an incompatible message from the peer unit. Since the message is not compatible it can be processed by this unit.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%FEC_ISSU-3-MSG_SIZE : FEC ISSU client failed to get the message size for message [dec]
Explanation The FEC ISSU client failed to calculate message size for the message specified. The OIR ISSU client will not be able to send message to the standby unit.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%FEC_ISSU-3-POLICY : FEC ISSU client message type [dec] is [chars]
Explanation The FEC ISSU client received an message type which it does not support. The policy is applied to make the session compatible.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%FEC_ISSU-3-SEND_FAILED : FEC ISSU client failed to send a negotiation message, error [dec]
Explanation The FEC ISSU client could not send a session negotiation message to the peer. When there is a problem in the negotiation the standby unit cannot be brought up.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%FEC_ISSU-3-SESSION : FEC ISSU client [chars]
Explanation The FEC ISSU client observed an error during a session negotiation with the peer unit. When there is a problem with the session the standby unit cannot be brought up.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%FEC_ISSU-3-SESSION_UNREGISTRY : FEC ISSU client failed to unregister session information. Error: [dec] ([chars])
Explanation The FEC ISSU client failed to unregister session information.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%FEC_ISSU-3-TRANSFORM : FEC ISSU client [chars] transform failed, error [chars]
Explanation The FEC ISSU client could not transform the message. If the transmit transformation failed, it indicates that the checkpoint message cannot be sent to the standby unit. If the receive transformation failed, it means that the checkpoint message cannot be applied on the standby unit. In both cases, the FEC state will not be identical with the active unit.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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.FIB Messages
The following are Forwarding Information Base messages.
Error Message%FIB-3-FIBHWIDBINCONS : An internal software error occurred. [chars] linked to wrong hwidb [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%FIB-3-FIBIDBINCONS : An internal software error occurred. [chars] linked to wrong IDB [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%FIB-6-FIBLCTUNDELSEQ : Update received on a linecard for a deleted tunnel([chars]) - ignored.
Explanation An update was received on a linecard for a tunnel that has already been deleted and the update was ignored.
Recommended Action No action is required.
Error Message%FIB-3-FIBSBNOCTRLFN : Missing [chars] subblock control [chars] function for [chars]
Explanation Functions for distributing this subblock are missing from the image.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%FIB-3-MAC_ACCT : [chars]: [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%FIB-3-PREC_ACCT : [chars]: [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.FILESYS Messages
The following are file system messages.
Error Message%FILESYS-4-CLPDINT : Management interrupts are [chars] for pcmcia device in socket [dec]. [chars]
Explanation A faulty PCMCIA flash device might be generating spurious insert or remove interrupts continiously. The PCMCIA controller will be set temporarily to disable interrupt generation and will be re-enabled after a few seconds. This is to avoid storming the CPU with spurious interrupts. If the (alternate) PCMCIA device is inserted while the interrupts are disabled, sometimes the device might not be readable. You have to remove and reinsert the PCMCIA device once again.
Recommended Action Replace the PCMCIA flash device with an alternate.
Error Message%FILESYS_RFS-3-IPC : [chars] [chars]: msg_type [[dec]] sub_type [[dec]]:
IPC error [[chars]]Explanation RFS operation failed due to an IPC 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.FM Messages
The following are Feature Manager messages.
Error Message%FM-4-EXCESSSECONDARY : More than [dec] secondary IP addresses configured on interface [chars]
Explanation When secondary IP addresses are configured on an interface, the hardware is usually programmed so that the ICMP redirect functionality on the CPU is not notified of packets sent between two subnets configured on the same interface. If many secondary IP addresses are configured on the same interface it becomes impractical to program the hardware in this manner, this message is logged, and the CPU will be notified of every packet sent between two subnets on this interface. No ICMP redirects will be sent in error, but the CPU usage might increase because of the additional notifications. You might wish to configure "no ip redirects" on the interface to reduce the CPU load on the system.
Recommended Action Enter the no ip redirects command for this interface.
Error Message%FM-3-LABELERROR : Incorrect label to [chars] vlan label attribute copy callback srclabel [dec], dstlabel [dec]
Explanation The Feature Manager attribute copy callback was called with an incorrect source or destination label.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config 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%FM-3-NOTEMPTY : Illegal copy of attribute to non empty [chars] vlan label [dec]
Explanation The Feature Manager attribute copy callback was called with a destination label already being used by a VLAN or routed port.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show running-config 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%FM-3-UNKNOWNACTION : Unknown VMR access group action [hex]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.FORCE_RPR Messages
The following are high availability force RPR operating mode messages.
Error Message%FORCE_RPR-4-NOT_ON_ACTIVE : [chars]
Explanation Only the Active node might enable this feature. Enure you are on the Active system before trying to enable this 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. Provide the output of the following commands:
show redundancy states, show redundancy history, show version. Also provide the sequence of commands used to produce this error.Error Message%FORCE_RPR-3-PEER_OPER_MODE : Peer node has reset ([dec]) times. [chars]
Explanation The peer node has reset the maximum number allowed before reaching STANDBY-HOT state. The redundancy force-rpr command is enabled and will try to set the peer system to RPR operating mode.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the output of the following commands:
show redundancy states, show redundancy history, show version. Also provide the sequence of commands used to produce this error.Error Message%FORCE_RPR-3-RF_REGISTER : RF error = [dec]. [chars]
Explanation During system initialization, Force RPR component was unable to register with the Redundancy Facility.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Provide the output of the following commands:
show redundancy states, show redundancy history, show version. Also provide the sequence of commands used to produce this error.FPD_MGMT Messages
The following are FPD Management Subsystem messages.
Error Message%FPD_MGMT-4-CFG_NOT_SYNCED : Failed to sync "[chars]" command to standby: [chars]
Explanation A FPD configuration command failed to get synchronized to standby RP due to the indicated error condition. Usually this can happen if the standby RP hardware does not support the type of filesystem supported on the active one.
Recommended Action Configure again the command with a filesystem that is supported on both standby and active RP. To find out if a specific filesystem is also supported on standby RP, the dir ? command can be used to display a list of filesytem supported on both standby and active RP.
Error Message%FPD_MGMT-3-MAJOR_VER_MISMATCH : Major image version mismatch detected with [chars] (FPD ID=[int]) for [chars] card in [chars]. Image will need to be [chars] from version [int].[int] to at least a minimum version of [int].[int]. Current HW version = [int].[int].
Explanation A major image version mismatch has been detected. This incompatibility will need to be resolved by performing an upgrade or downgrade operation either automatically, or manually, to make the card operational. If the automatic upgrade feature is not enabled, or if the system cannot find the necessary FPD image package file, then the card will be disabled.
Recommended Action If the automatic upgrade feature is not enabled, then the affected card will be disabled. Copy the message exactly as it appears on the console or in the system log.Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%FPD_MGMT-3-MISSING_DEV_INFO : Could not find [chars] (FPD ID=[int]) in the list of FPD IDs populated for [chars] card in [chars].
Explanation This error is seen when there is a problem in internal software coding; it should not be seen under normal operation.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%FPD_MGMT-3-PKG_VER_MISMATCH_NOTE : The FPD image package being used ([chars]) is not the right version for this IOS version (it appears that a '[chars]' package was renamed to '[chars]'). An attempt to find the required FPD image will still be performed with this package.
Explanation The indicated FPD image package that is being used in FPD automatic upgrade does not contain the correct version information for the IOS version that is running in the system. This condition can occur if a different version of the FPD image package was renamed to match the filename that the IOS image is expecting to use. The upgrade operation will still be performed by trying to find the required FPD image from the renamed package file.
Recommended Action If the upgrade operation fails because the required FPD image cannot be found with the renamed FPD image package, replace the wrong package file with a valid one and perform the upgrade operation again.
Error Message%FPD_MGMT-5-POST_UPGRADE_REMINDER : [chars] card in [chars] will require a [chars] for the FPD image upgrade to take effect.
Explanation The indicated card will require manual intervention after the FPD image upgrade. The specified operation is required for the upgraded FPD image to take effect.
Recommended Action No action is required.
FPGA Messages
The following are LS1010 chip-specific messages.
Error Message%FPGA-3-ABR : ABR FPGA do not reset properly, Control Register=[hex]
Explanation This message should never be seen on a 6400.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%FPGA-2-DONE_PIN : Done pin or Status pin did not go low, FPGA# [dec]
Explanation The specified FPGA chip showed incorrect status after downloading its control microcode. This is probably caused by a hardware failure. It is a fatal condition for the system and will be followed by a core dump.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%FPGA-2-DOWNLOAD : Download Fail, FPGA# [dec]
Explanation The specified FPGA chip failed to respond after downloading its control microcode. This is probably caused by a hardware failure. It is a fatal condition for the system and will be followed by a core dump.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%FPGA-3-MCAST : Multicast FPGA did not reset properly, Control Register=[hex]
Explanation This message should never be seen on a 6400.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%FPGA-3-NOFORK : Could not start Per-VC counter daemon
Explanation Per-VC counter daemon process could not be started during initialization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%FPGA-2-STATUS_PIN : Error in status pin, FPGA# [dec]
Explanation The specified FPGA chip showed incorrect status after downloading its control microcode. This is probably caused by a hardware failure. It is a fatal condition for the system and will be followed by a core dump.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%FPGA-3-TRAFF : Traffic FPGA do not reset properly, Control Register=[hex]
Explanation This message should never be seen on a 6400.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%FPGA-3-VERSION : Feature Card version invalid/old. Feature Card Version:[dec].[dec], NSP Version:[dec].[dec]
Explanation Invalid or obsolete version of the feature card is installed. It is incompatible with the current NSP version.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.FPOE_DB Messages
The following are FPOE DB log messages.
Error Message%FPOE_DB-4-ENTRY_USAGE_ABOVE : FPOE DB entry usage is above [dec]%<[dec] of [dec]>
Explanation FPOE DB entry usage went above warning threshold.
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%FPOE_DB-4-ENTRY_USAGE_BELOW : FPOE DB entry usage is below [dec]%<[dec] of [dec]>
Explanation FPOE DB entry usage went below warning threshold.
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%FPOE_DB-4-ENTRY_USAGE_FULL : FPOE DB entry usage is full <[dec] of [dec]>
Explanation FPOE DB entry usage is FULL.
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%FPOE_DB-4-ENTRY_USAGE_NOT_FULL : FPOE DB entry usage is not full <[dec] of [dec]>
Explanation FPOE DB entry usage is not FULL.
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.FR Messages
The following are Frame Relay messages.
Error Message%FR-3-FR_INV_OUTPUT_VECTOR : An invalid output vector detected on interface [chars]
Explanation An invalid internal function vector is installed on a Frame Relay interface, which affects the ability of processing outbound traffic on the device.
Recommended Action Remove and re-apply Frame Relay encapsulation on the interface to recover from the error.
Error Message%FR-3-MAP_DELETE_ERROR : [chars]
Explanation An error occurred while deleting a frame-relay map.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%FR-3-MFR_UNEXPECTEDEVENT : MFR Timer process error: event table is NULL for event [dec], state [dec]
Explanation The event was ignored because the state transition table is NULL. Normal processing will continue.
Recommended Action Refer to Bug Toolkit on CCO to check for existing bugs. Copy the message exactly as it appears on the console or in the system log. Enter the show version and show running 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.FRDM336 Messages
The following are FREEDM-336 driver internal messages.
Error Message%FRDM336-3-ANYPHYALLOCFAILED : Anyphy allocation failed for [chars]
Explanation Encountered an error while configuring the ASIC in Linecard.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc. Copy the message exactly as it appears on the console or in the system log. Enter the show controller in Linecard and RP show platform multilink in Linecard 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%FRDM336-3-BUNDLEEXIST : Unexpected bundle([hex]) present in freedm
Explanation Encountered an error while provisioning a bundle.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc. Copy the message exactly as it appears on the console or in the system log. Enter the show controller in Linecard and RP show platform multilink in Linecard 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%FRDM336-3-BUNDLERANGE : bundle([hex]) not within range
Explanation Encountered an error while configuring an ASIC in Linecard.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc. Copy the message exactly as it appears on the console or in the system log. Enter the show controller in Linecard and RP show platform multilink in Linecard 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%FRDM336-3-CC_RESEQ_FIFO_ACT_NOT_CLEAR : FRDM336 base addr ([hex]): Removing CI([hex]) of channel (HDLC channel no:[dec]), timeout ([chars]) waiting for RESEQ_ACT and FIFO_ACT to clear
Explanation Encountered an error in the ASIC of line card, while unprovisioning a channel or Multilink interface.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show controller in Linecard and RP 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%FRDM336-3-CIALLOCFAILED : CI allocation failure for tag=[dec] dlciCos=[dec]
Explanation Encountered an error while configuring an ASIC in Linecard.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc. Copy the message exactly as it appears on the console or in the system log. Enter the show controller in Linecard and RP show platform multilink in Linecard 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%FRDM336-3-CITAGMISMATCH : CI([hex]) does not belong to tag([hex])
Explanation Encountered an error while configuring an ASIC in Linecard.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc. Copy the message exactly as it appears on the console or in the system log. Enter the show controller in Linecard and RP show platform multilink in Linecard 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%FRDM336-3-DEFAULTCI : Unexpected default CI for channel ([hex])
Explanation Encountered an error, while configuring an ASIC in the Linecard.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc. Copy the message exactly as it appears on the console or in the system log. Enter the show controller in Linecard and RP 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%FRDM336-3-DLCICOSRANGE : DLCICOS([hex]) not within range
Explanation Encountered an error, while configuring an ASIC in the Linecard.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc. Copy the message exactly as it appears on the console or in the system log. Enter the show controller in Linecard and RP 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%FRDM336-3-EQM_SIZE_NOT_ZERO : HDLC([dec]) : [hex] [hex] [hex] [hex]
Explanation Encountered an error, while configuring or unconfiguring an ASIC in the Linecard.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc. Copy the message exactly as it appears on the console or in the system log. Enter the show controller in Linecard and RP 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%FRDM336-3-INITERR : FRDM336 chip initialization failed (errcode=[dec]): [chars]
Explanation Required resources to initialize the ASIC in line card unavailable. This is normally due to a hardware issue.
Recommended Action Reinsert the linecard. If still fails, swap hardware, and LOG_STD_SH_TECH_ACTION
Error Message%FRDM336-3-INVALIDANYPHY : Anyphy([hex]) number is not in range
Explanation Encountered an error while configuring the ASIC in Linecard.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc. Copy the message exactly as it appears on the console or in the system log. Enter the show controller in Linecard and RP show platform multilink in Linecard 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%FRDM336-3-INVALIDCI : Either CI([hex]) range not ok or not allocated
Explanation Encountered an error while configuring an ASIC in Linecard.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc. Copy the message exactly as it appears on the console or in the system log. Enter the show controller in Linecard and RP show platform multilink in Linecard 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%FRDM336-3-LLAPI_PROVERR : FRDM336 base addr ([hex]): Channel provisioning (SBI no:[dec] SPE no:[dec] TRIB no:[dec] HDLC channel no:[dec] TS Mask:[hex] Trib i/f mode:[dec]) failed (errcode=[dec]): [chars]
Explanation Encountered an error while configuring an ASIC in Linecard.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc. Copy the message exactly as it appears on the console or in the system log. Enter the show controller in Linecard and RP show platform multilink in Linecard 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%FRDM336-3-LLINT_DET_TSMSKUSEERR : FRDM336 base addr ([hex]): TS mask in use (SBI no:[dec] SPE no:[dec] TRIB no:[dec] TS Mask:[hex] Trib i/f mode:[dec]) by HDLC channel [dec](TS used = [dec]) (errcode=[dec]): [chars]
Explanation Encountered an error while configuring an ASIC in Linecard.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc. Copy the message exactly as it appears on the console or in the system log. Enter the show controller in Linecard and RP show platform multilink in Linecard 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%FRDM336-3-LLINT_TSMSKUSEERR : FRDM336 base addr ([hex]): TS mask in use (SBI no:[dec] SPE no:[dec] TRIB no:[dec] TS Mask:[hex] Trib i/f mode:[dec]) (errcode=[dec]): [chars]
Explanation Encountered an error while configuring an ASIC in Linecard.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc. Copy the message exactly as it appears on the console or in the system log. Enter the show controller in Linecard and RP show platform multilink in Linecard 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%FRDM336-3-NCHUNKSNONZERO : FRDM336 base addr ([hex]): disabling channel(HDLC channel no:[dec], ANY-PHY channel no:[dec]), timeout ([chars]) waiting for RFRAG AP_NCHNKS to clear (value=[hex])
Explanation Encountered an error in the ASIC of line card, This mostly occurs while unprovisioning a channel or Shutting interface.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc. Copy the message exactly as it appears on the console or in the system log. Enter the show controller in Linecard and RP show platform multilink in Linecard 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%FRDM336-3-NCHUNKSNONZERO_CC_RESEQ_FIFO_ACT_SET : FRDM336 base addr ([hex]): disabling channel(HDLC channel no:[dec], ANY-PHY channel no:[dec]), CI:[dec] reSeqAct:[dec] fifoAct:[dec]
Explanation Encountered an error in the ASIC of line card, This mostly occurs while unprovisioning a channel or Shutting interface.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc. Copy the message exactly as it appears on the console or in the system log. Enter the show controller in Linecard and RP show platform multilink in Linecard 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%FRDM336-3-NOANYPHYALLOCATED : No Anyphy number for channel=[dec]
Explanation Encountered an error while configuring an ASIC in line card.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc. Copy the message exactly as it appears on the console or in the system log. Enter the show controller in Linecard and RP show platform multilink in Linecard 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%FRDM336-5-NOBUNDLEPRESENT : bundle([hex]) not present in freedm
Explanation Encountered an error while configuring an ASIC in line card.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc. Copy the message exactly as it appears on the console or in the system log. Enter the show controller in Linecard and RP show platform multilink in Linecard 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%FRDM336-3-NOCIALLOCATED : No CI number for tag=[dec] dlciCos=[dec]
Explanation Encountered an error while configuring an ASIC in line card.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc. Copy the message exactly as it appears on the console or in the system log. Enter the show controller in Linecard and RP show platform multilink in Linecard 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%FRDM336-3-PDDBNULL : Device data block null
Explanation Encountered an error while accessing an ASIC in line card.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc. Copy the message exactly as it appears on the console or in the system log. Enter the show controller in Linecard and RP show platform multilink in Linecard 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%FRDM336-3-POLLTO : FRDM336 indirect poll timeout. base addr:[hex], offset:[hex], value:[hex], mask:[hex], delay:[hex]
Explanation Not able to access a register in the ASIC of line card, this is normally a hardware problem.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc. Copy the message exactly as it appears on the console or in the system log. Enter the show controller in Linecard and RP show platform multilink in Linecard 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%FRDM336-3-PROVERR : FRDM336 Channel provisioning (SBI no:[dec] SPE no:[dec] TRIB no:[dec] HDLC channel no:[dec]) failed (errcode=[dec]): [chars]
Explanation Encountered an error while configuring an ASIC in the Linecard.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show controller in Linecard and RP 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%FRDM336-3-RHDL_TAVAIL_NOT_CLEAR : FRDM336 base addr ([hex]): disabling channel(HDLC channel no:[dec]), timeout ([chars]) waiting for RHDL TAVAIL to clear
Explanation Encountered an error while configuring an ASIC in the line card.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc. Copy the message exactly as it appears on the console or in the system log. Enter the show controller in Linecard and RP show platform multilink in Linecard 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%FRDM336-3-SET_CHANPARAM_ERR : FRDM336 setting parameters of a Channel failed (HDLC channel no:[dec]) failed (errcode=[dec]): [chars]
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show controllerin Linecard and RP 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%FRDM336-3-SET_SPE_ERR : FRDM336 setting configuration of SPE (SBI no:[dec] SPE no:[dec]) to [dec] failed (errcode=[dec]): [chars]
Explanation Encountered an error while configuring an ASIC in the line card.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc. Copy the message exactly as it appears on the console or in the system log. Enter the show controller in Linecard and RP show platform multilink in Linecard 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%FRDM336-3-SET_TRIB_ERR : FRDM336 setting configuration of tributary (SBI no:[dec] SPE no:[dec] TRIB no:[dec]) to [dec] failed (errcode=[dec]): [chars]
Explanation Encountered an error while configuring an ASIC in the line card.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc. Copy the message exactly as it appears on the console or in the system log. Enter the show controller in Linecard and RP show platform multilink in Linecard 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%FRDM336-3-THDL_AVAIL_NOT_CLEAR : FRDM336 base addr ([hex]): disabling channel(HDLC channel no:[dec]), timeout ([chars]) waiting for THDL AVAIL to clear
Explanation Encountered an error while configuring an ASIC in the line card.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc. Copy the message exactly as it appears on the console or in the system log. Enter the show controller in Linecard and RP show platform multilink in Linecard 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%FRDM336-3-TRIB_ENAB_DIS_ERR : FRDM336 [chars] tributary (SBI no:[dec] SPE no:[dec] TRIB no:[dec]) failed (errcode=[dec]): [chars]
Explanation Encountered an error while configuring an ASIC in the line card.
Recommended Action Collect the details that triggered the issue, such as any configuration change, switchover, etc. Copy the message exactly as it appears on the console or in the system log. Enter the show controller in Linecard and RP show platform multilink in Linecard 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.FR_EEK Messages
The following are Frame Relay End-to-End Keepalive messages.
Error Message%FR_EEK-5-FAILED : Interface [chars] - DLCI [dec]
Explanation The end-to-end keepalive protocol has failed for the indicated PVC. A failure occurs when the DLCI is ACTIVE and end-to-end keepalives are enabled but the number of errors due to timeouts or sequence number mismatches has reached the failure threshold. The DLCI is taken out of operation until the protocol recovers.
Recommended Action A persistent failure might indicate a mismatched end-to-end keepalive configuration at each end of the PVC. A transient failure might be due to a temporary loss of connectivity or heavy congestion in the network. This is a rate-limited log message so not all failures might be logged. The show frame-relay end-to-end keepalive failures command can be used to obtain further information on what PVCs have experienced failures.
FR_HA Messages
The following are Frame Relay HA messages.
Error Message%FR_HA-3-ISSU : [chars]: [chars]
Explanation A Frame Relay ISSU error occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%FR_HA-3-SYNC : [chars]: code [dec]
Explanation An error occurred when synchronizinging Frame Relay state to the Standby Route Processor. This might affect Non-Stop Forwarding capability on Frame Relay interfaces during and after switchover until the state is recovered through normal protocol operation.
Recommended Action Reset the standby processor to attempt the synchronization 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%FR_LC_XDR-3-PULL_SEND_ERROR : Error occurred sending FR PVC stats to the RP: error code [int]
Explanation An error occurred while updating the RP with FR PVC stats. Some of the FR PVC counters might be inaccurate.
Recommended Action Some FR PVC stats might be lost. This might be a temporary failure. 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%FR_LC_XDR-3-UNIT_SZ_TOO_BIG : Error occurred sending FR PVC stats to the RP: [chars]: DLCI [dec]: unit sz [int]
Explanation An error occurred while updating the RP with FR PVC stats. Some of the FR PVC counters might be inaccurate.
Recommended Action Some FR PVC stats might be lost. This might be a temporary failure. 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.FR_LMI Messages
The following are Frame Relay Local Management Interface messages.
Error Message%FR_LMI-3-MSG_TOO_BIG : [chars] ([chars]) Status message too big, status of PVCs with dlci values from [dec] will not be reported.
Explanation LMI STATUS message size is too big to fit into interface MTU.
Recommended Action LMI type - cisco - does not support segmentation of STATUS message; either increase the interface MTU or use LMI types - ansi or q933a.
FR_RP Messages
The following are Frame Relay RP messages.
Error Message%FR_RP-3-IPC_STATS_INVALID_DLCI : Error processing IPC msg - msg type [chars]
Explanation An error occurred while processing an IPC stats message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%FR_RP-3-IPC_STATS_INVALID_INTERFACE : Error processing IPC msg - msg type [chars]
Explanation An error occurred while processing an IPC statistics message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%FR_RP-3-IPC_STATS_INVALID_MSG : Error processing IPC msg - msg type [chars]
Explanation An error occurred while processing an IPC stats message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. RResearch and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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%FR_RP-3-IPC_STATS_MISC : Error processing IPC msg - [chars]
Explanation An error occurred while processing an IPC stats message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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.FR_RP_STATS Messages
The following are Frame Relay RP Stats IPC messages.
Error Message%FR_RP_STATS-3-CORRUPT_MSG : FR IPC stats msg is corrupted: buffer [hex]: length [int]
Explanation An error occurred while processing a FR IPC stats message. Some of the FR PVC counters might be inaccurate.
Recommended Action This could be a temporary failure. But there could be a possibility that some of the FR PVC counters might not have updated correctly. 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%FR_RP_STATS-3-INVALID_STAT_UNIT : Error processing FR IPC stats msg: DLCI is out of bounds
Explanation An error occurred while processing a FR IPC stats message. Some of the FR PVC counters might be inaccurate.
Recommended Action This could be a temporary failure that might or might not affect the accuracy of PVC stats. 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%FR_RP_STATS-3-INVALID_UNIT_COUNT : FR IPC stats msg is corrupted: unit count [int]
Explanation An error occurred while processing a FR IPC stats message. Some of the FR PVC counters might be inaccurate.
Recommended Action This could be a temporary failure. But there could be a possibility that some of the FR PVC counters might not have updated correctly. If this messages recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.FR_RP_XDR Messages
The following are Frame Relay RP XDR messages.
Error Message%FR_RP_XDR-3-CLIENT_INIT_ERROR : FR XDR client initialization error: error code [int]
Explanation An error occurred while registering the FR RP XDR client. Distributed packet forwarding over FR will not work.
Recommended Action This is a serious error. Without the FR XDR client, distributed packet forwarding over FR will not work. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%FR_RP_XDR-3-INTERFACE_SETUP_ERROR : Unable to setup FR XDR for interface [chars]
Explanation An error occurred while setting up FR XDR for a FR interface. This will affect distributed packet forwarding over this interface.
Recommended Action This is a serious error. Without FR XDR support, distributed packet forwarding over the FR interface in question will not work. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.FR_VCB Messages
The following are Frame Relay VC bundle messages.
Error Message%FR_VCB-3-ADJ_SRC_ERROR : Error sourcing adjacency - vc-bundle [chars] dlci [dec]
Explanation An error occurred while setting up the adjacency for a member PVC.
Recommended Action Reconfigure the vc-bundle. If this message recurs, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%FR_VCB-3-CONFIG : Configuration error - vcb [chars] - [chars]
Explanation An error occurred while interpreting vc-bundle configuration.
Recommended Action Try reconfiguring the vc-bundle.
Error Message%FR_VCB-3-FIBSW_MISSING_TABLE_ENTRY : FIB switching error - vc-bundle [chars]
Explanation An error occurred while FIB switching packet(s) across vc-bundle.
Recommended Action As a workaround, delete the vc-bundle and employ a PVC to substitute for the vc-bundle.
Error Message%FR_VCB-3-PROCESS_SWITCHING : Switching error - vcb [chars] - [chars]
Explanation An error occurred while switching packet(s) across vc-bundle.
Recommended Action As a workaround, delete the vc-bundle and employ a PVC to substitute for the vc-bundle.
FR_VIP Messages
The following are Frame Relay VIP messages.
Error Message%FR_VIP-5-FLUSH : Flushing frame relay state
Explanation Clearing up frame relay state on the VIP card.
Recommended Action Notification message only. No action is required.
Error Message%FR_VIP-3-INCONSISTENT : Invalid state on VIP: DLCI [dec]: Slot [dec]: Error code [dec]
Explanation An error occurred while processing FR state on the VIP .
Recommended Action Enter the shutdown and no shutdown commands for the frame-relay encapsulated interface for the specified slot.
Error Message%FR_VIP-3-MISSING_STATE : Missing state on VIP: DLCI [dec]: Slot [dec]
Explanation An error occurred while preparing an IPC stats unit .
Recommended Action Enter the shutdown and no shutdown commands for the frame-relay encapsulated interface for the slot in question.
Error Message%FR_VIP-3-SWITCHING : [chars] DLCI [dec]: [chars]
Explanation An error was detected while switching a packet on the VIP.
Recommended Action Enter the shutdown and no shutdown commands to shut down and restart the interface in question, or unconfigure then re-configure, which might solve the problem. 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.FRR_OCE Messages
The following are FRR OCE infrastructure messages.
Error Message%FRR_OCE-3-GENERAL : [chars]
Explanation An internal software error has occurred.
Recommended Action Refer to the Bug Navigator at www.cisco.com to determine if this condition has been previously reported and resolved in a later release.
Error Message%FRR_OCE-3-INVALIDPAR : [chars]
Explanation An internal software error has occurred.
Recommended Action Refer to the Bug Navigator at www.cisco.com to determine if this condition has been previously reported and resolved in a later release.
Error Message%FRR_OCE-3-NULLPOINTER : [chars]
Explanation An internal software error has occurred.
Recommended Action Refer to the Bug Navigator at www.cisco.com to determine if this condition has been previously reported and resolved in a later release.
FS_IPHC Messages
The following are Fast IP Header Compression messages.
Error Message%FS_IPHC-4-LC_IPCSENDFAIL : LC unable to send IPHC msg to RP ([int])
Explanation Line card was unable to send an IP header compression information message to the route processor.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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 possible, also provide the output of the debug ip rtp head and debug ip tcp head commands for the period during which this message appeared.Error Message%FS_IPHC-2-LC_IPHC_SETUP_FAIL : Failed to initialise or allocate memory for IP Compression database.
Explanation IP Compression main database not created due to lack of memory resources.
Recommended Action The line card cannot allocate memory for an IP Compression database. Add more memory if possible to the VIP. Free up memory on the VIP by reducing features used or buffer allocations. Reduce the number of contexts configured on all interfaces on the affected line card by entering the ip rtp compression-connections interface configuration command.
Error Message%FS_IPHC-2-LC_PROC_INIT : LC Failed to initialise distributed IP Hdr Comp Process
Explanation IP Compression Process not created on line card.
Recommended Action A possible reason for a process failing to start is lack of resources. Check memory allocation on line card and either upgrade line card memory or reduce feature burden in it's interface configurations.
Error Message%FS_IPHC-3-MSG_TOO_LARGE : Received IPC message too large to handle ([int])
Explanation IP compression has received an IPC message of a size larger than expected.
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%FS_IPHC-4-RP_IPCSENDFAIL : RP unable to send IPHC msg to LC ([int])
Explanation Route processor was unable to send an IP header compression configuration message to a line card 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. If possible, also provide the output of the debug ip rtp head and debug ip tcp head commands for the period during which this message appeared.Error Message%FS_IPHC-4-RP_NOIPCBUFFER : Unable to malloc IPC msg buffer ([int]) on RP
Explanation Route Processor unable to send IPHC information to Line Card due to lack of memory in it's private memory pool.
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%FS_IPHC-2-RP_NOLCINFO : Unable to malloc state table for LC
Explanation An internal data structure is missing due to lack of memory resources.
Recommended Action The Route Processor is dangerously low on memory resources. Free up memory by removing unwanted feature configuration or upgrade the memory on the system router processor
GBIC_SECURITY Messages
The following are GBIC security check messages.
Error Message%GBIC_SECURITY-4-EEPROM_CRC_ERR : EEPROM checksum error for GBIC in [chars]
Explanation The GBIC in the port specified in the error message has invalid EEPROM data.
Recommended Action Remove the GBIC from the specified port.
Error Message%GBIC_SECURITY-4-EEPROM_READ_ERR : Error in reading GBIC serial ID in [chars]
Explanation Error when reading GBIC type from EEPROM.
Recommended Action Remove GBIC from this Port .
Error Message%GBIC_SECURITY-4-EEPROM_SECURITY_ERR : GBIC in [chars] failed security check
Explanation The GBIC in the port specified in the error message has invalid EEPROM data.
Recommended Action Remove the GBIC from the specified port.
GDOI Messages
The following are Group Domain of Interpretation messages.
Error Message%GDOI-1-GDOI_ACE_DENY : A Group Member ACL policy containing deny was attempted. This is not supported.
Explanation A Group Member ACL policy containing deny was attempted. This is not supported.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GDOI-1-GDOI_ACL_NUM : The ACL has too many entries.
GDOI will honor only the first 100 ACL entries specified.Explanation The ACL has too many entries. GDOI will honor only the first 100 ACL entries specified.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GDOI-5-GM_REGS_COMPL : Registration complete for group [chars] using address [chars]
Explanation Registration is complete.
Recommended Action Notification message only. No action is required.
Error Message%GDOI-4-GM_RE_REGISTER : The IPSec SA created for group [chars] might have been expired or cleared. Re-register to KS.
Explanation The IPSec SA created for one group might have been expired or cleared, need to re-register to KS.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GDOI-1-UNAUTHORIZED_IDENTITY : Group [chars] received registration from unauthorized identity: [chars]
Explanation The registration request was dropped because the requesting device was not authorized to join the group.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. Attach the following information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.Error Message%GDOI-1-UNAUTHORIZED_IPADDR : Group [chars] received registration from unauthorized ip address: [chars]
Explanation The registration request was dropped because the requesting device was not authorized to join the group.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GDOI-1-UNREGISTERED_INTERFACE : Group [chars] received registration from unregistered interface.
Explanation Receiving registration from unregistered interface. Stop processing it.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.GEFC Messages
The following are GE-FC line card messages.
Error Message%GEFC-3-ACCESS_FAIL : LRC access Failed
Explanation LRC access 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%GEFC-3-BDI_E_ALM : End-to-End Backward Defect Indication [chars]
Explanation End-to-End Backward Defect Indication.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEFC-6-FLOW_CTRL_ACTIVE : Flow control become active at slot:[dec] port:[dec]
Explanation Flow control 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%GEFC-6-FLOW_CTRL_DEACTIVE : Flow control become inactive at slot:[dec] port:[dec]
Explanation Flow control deactive.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEFC-3-FPGA_NOT_SUPPORT : Jamesport FPGA need upgrade. slot:[dec] port:[dec] [chars] function
Explanation FPGA on Jamesport Card need upgrade to support JP2 functions.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEFC-3-GEFC_INTRPEND : Pending unexpected interrupt [addr [hex] = [hex]]
Explanation One or more pending unexpected interrupts.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEFC-3-GEFC_MAGICFAIL : Magic number read failed [[chars]]
Explanation The FPGA had reset .
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEFC-3-GEFC_PTFAILASSERTED : Unexpected portfail asserted
Explanation One or more unexpected portfails asserted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEFC-3-GEFC_RDWRFAIL : Read/write failed [[chars]]
Explanation The read/write error occurred when accessing the hardware.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEFC-3-IDPROM_ACCESS_FAIL : Access to IDPROM Failed
Explanation Access To IDPROM 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%GEFC-3-INT_LPBK_FAIL : Internal CardLoopback Failed
Explanation Internal Card Loopback 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%GEFC-3-KPA_TIMEOUT_ALM : Keep-alive timeout [chars]
Explanation Normal packets/CDL Idle packets not received.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEFC-3-LASER_TX_FAULT_ALM : Optic Laser Transmit Fault [chars]
Explanation Transceiver Laser Tx Fault.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEFC-3-LOSS_OF_LIGHT_ALM : Loss of Light [chars]
Explanation Transceiver has cable cut or removed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEFC-3-LOSS_OF_LOCK_ALM : Transceiver CDR Loss of Lock [chars]
Explanation CDR is having trouble locking onto signal.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEFC-3-LOSS_OF_SYNC_ALM : Transceiver Loss of Sync [chars]
Explanation Loss of Syncronization 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%GEFC-3-MIB_HW_LASER_DOWN_ALM : Laser Disabled [chars] [chars] [chars]
Explanation Client Laser Disabled.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEFC-3-MIB_KPA_TIMEOUT_ALM : Keep-alive timeout [chars] [chars] [chars]
Explanation Normal packets/ CDL Idle packets not received.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEFC-3-MIB_LASER_TX_FLT_ALM : Laser Transmit Fault [chars] [chars] [chars]
Explanation Client Laser Transmit Fault.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEFC-3-MIB_LOSS_OF_LIGHT_ALM : Transceiver Loss of Light [chars] [chars] [chars]
Explanation Client side No Light.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEFC-3-MIB_LOSS_OF_LOCK_ALM : Loss of Lock [chars] [chars] [chars]
Explanation Loss of Lock.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEFC-3-MIB_LOSS_OF_SYNC_ALM : Loss of Sync [chars] [chars] [chars]
Explanation Loss of Synchronization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEFC-3-MIB_SFP_VENDOR_UNKNOWN : Unknown Vendor SFP inserted [chars] [chars] [chars]
Explanation SFP is not Cisco qualified.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEFC-3-TX_CRC_ERR_THR_ALM : GEFC TX CRC Error Threshold [chars]
Explanation Tx CRC errors threshold.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEFC-3-UNKNOWN_SFP_INSERTED : Unknown SFP inserted [chars]
Explanation Unknown SFP inserted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.GEN_DB Messages
The following are Generic Database messages.
Error Message%GEN_DB-3-INVALID_CLIENT_TYPE : [chars]: Invalid client type, got [dec] (must be between 0 and [dec])
Explanation This message indicates that client type is outside the expected range.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEN_DB-3-INVALID_RECORD_KEY : [chars]: invalid record key *
Explanation This message indicates that the record key is invalid.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEN_DB-3-KEY_FUNC_DOESNT_EXIST : [chars]: Key function does not exist
Explanation This message indicates that key function being considered does not exist in the database definition.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEN_DB-3-LIST_FAIL : [chars]:[chars]
Explanation This message indicates that a list operations such as enqueue, dequeu 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%GEN_DB-3-LIST_FAIL_FOR_RECORD : [chars]:[dec]:[chars]
Explanation This message indicates that a list operations such as enqueue, dequeu 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%GEN_DB-3-NO_KEY_FUNC : [chars]: [chars][chars]
Explanation This message indicates that key functions are missingfrom the database handle, or key function is a NULL Pointer.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEN_DB-3-NULL_DB_HNDL : NULL Database Handle [chars]
Explanation This message indicates the database handle was NULL.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEN_DB-3-NULL_DB_HNDL_ELEMENT : [chars]: NULL Database Element [chars]
Explanation This message indicates the database handle element was NULL.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEN_DB-3-NULL_TREE_NODE : Node is NULL [chars]
Explanation This message indicates that the tree node being examined is NULL.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEN_DB-3-PARSER_INIT_FAIL : [chars]:[dec]: Parser Could not be initialized
Explanation This message indicates that the IOS Parser command could not be initialized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEN_DB-3-RECORD_DELETE_FAIL : [chars]:[chars]
Explanation This message indicates that a record could not be deleted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEN_DB-3-UNKNOWN_PARSER_CMD : [chars]:[dec]: Unknown Parser Command
Explanation This message indicates that the IOS Parser command was not recognized.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GEN_DB-3-WAVL_FAIL : [chars]: [chars]
Explanation This message indicates that a wavl tree operation failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.GENERAL Messages
The following are Zenith route processor messages.
Error Message%GENERAL-4-ACE_LIMIT : Number of ACEs in [chars] exceeds the maximum of 64K-2 allowed
Explanation Warning: the maximum number of ACEs in an acl is 64K-2 when per-ACE accounting is enabled. This ACL has more than this limit. The per=ACe accounting for all ACEs beyond the limit will be aggregated into ACE numbered 64K-2. per ACE stats beyond this ACE will always show a match statistic of zero.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GENERAL-2-CRITEVENT : [chars]
Explanation Critical 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%GENERAL-3-EREVENT : [chars]
Explanation General error to be used for sanity tests.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GENERAL-3-EREVENT_NUM : [chars] [dec]
Explanation General error to be used for sanity tests
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GENERAL-3-HWCEF_CHUNK : Failed to alloc Mtrie HW mnode from chunk [chars] for [IP_address]/[dec]
Explanation Attempt to allocate memory for a hardware mnode 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%GENERAL-3-HWCEF_FIB_ROOT : Failed to alloc Mtrie HW root for [chars] fib
Explanation Attempt to allocate a hardware mnode root 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%GENERAL-3-HWCEF_MNODE : Failed to alloc Mtrie HW mnode for [IP_address]/[dec] at level [dec]
Explanation Attempt to allocate a hardware mnode structure 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%GENERAL-3-HW_IPV6CEF_CHUNK : Failed to alloc Mtrie HW mnode from chunk [chars] forUnrecognized format ` %P'/[dec]
Explanation Attempt to allocate memory for a hardware mode 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%GENERAL-3-HW_IPV6CEF_FIB_ROOT : Failed to alloc Mtrie HW root for tableid [dec]
Explanation Attempt to allocate a hardware mnode root 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%GENERAL-3-HW_IPV6CEF_MNODE : Failed to alloc Mtrie HW mnode forUnrecognized format ` %P'/[dec] from block [dec]
Explanation Attempt to allocate a hardware mnode structure 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%GENERAL-3-HW_IPV6CEF_MTRIECORRUPT : Could not add prefiUnrecognized format `x%P'/[dec] flags=[dec] at level [dec]
Explanation Internal software error in PXF Mtrie 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.Error Message%GENERAL-6-INFOEVENT : [chars]
Explanation Informational message only.
Recommended Action No action is required.
Error Message%GENERAL-5-NOTEVENT : [chars]
Explanation Informational message only.
Recommended Action No action is required.
Error Message%GENERAL-4-VLAN_WRNEVENT : [chars] [dec] [chars] on interface [chars]
Explanation Warning: the VLAN ID(s) in the transmit packet does not match any configured on the router. This can be as a result of an encapsulation being removed from 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%GENERAL-4-WRN2EVENT : [chars]
Explanation Warning. The VAI could not be added to the ATM sub-interface list. This can be as a result of pvc being removed from the interface via CLI.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GENERAL-4-WRN3EVENT : [chars]
Explanation If sb->next or sb-prev might become nullindicate that SB has been removed from the list.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GENERAL-4-WRNEVENT : [chars]
Explanation Warning. System resource running low.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GENERAL-3-WSHALEVENT : [chars]
Explanation General error to be used for sanity tests.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.GENERIC_SUBBLOCK Messages
The following are Generic subblock messages.
Error Message%GENERIC_SUBBLOCK-2-BUILDXDR : Failed to build message for GSB: [chars]
Explanation An attempt to build a message for distribution of generic subblock 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%GENERIC_SUBBLOCK-2-GSBNOTISSUAWARE : GSB [chars] is not ISSU aware. Cannot distribute it to ISSU-aware slots
Explanation This GSB is expected to be ISSU aware but it is not. It cannot be distributed safely to ISSU-aware slots as it might not be correctly interpreted.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GENERIC_SUBBLOCK-2-LATE_REGISTER : Late registration of GSB type [chars], with id [dec]
Explanation An attempt to register a new generic subblock type was received after subblocks have already been allocated from the control structure with previously registered types.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GENERIC_SUBBLOCK-2-UNPACKXDR : Unpacked [dec] bytes and attempted to consume [dec] bytes for GSB: [chars]
Explanation A discrepancy was detected between length of message expected versus length of message received.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.GLBP Messages
The following are Gateway Load Balancing Protocol messages.
Error Message%GLBP-4-BADVIP : [chars] Grp [dec] address [IP_address] is in the wrong subnet for this interface
Explanation The GLBP virtual IP address contained in the Hello message cannot be learned as it is not within a subnet configured on the interface.
Recommended Action Check the configuration on all GLBP routers and ensure that the virtual IP address is within a configured subnet.
G_QOS_CLASSIFY Messages
The following are Generic QoS TCAM Classification mapper messages.
Error Message%G_QOS_CLASSIFY-4-MACACL_CONFIG : [chars]
Explanation Only source mac address in extended named MAC ACL is supported on X40G line card interfaces.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%G_QOS_CLASSIFY-3-NOMEM : Memory Allocation Failure - [chars]
Explanation Memory required to service one or more Network Processors could not be allocated.
Recommended Action This error may indicate that more memory must be installed on the affected card or platform in order to service all the features and related entities enabled via the configuration. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the information that you have gathered.Error Message%G_QOS_CLASSIFY-3-QOS_CONFIG : error detected: [chars]
Explanation QoS policmap classification configuration error detected.
Recommended Action This configuration error is not considered fatal to the operation of the Network Processors. The software is designed to detect and report the error condition. Change the QOS Policymap Filter configuration to correct the problem.
GRP_C10K_CH_DS3 Messages
The following are Cisco 10000 CH-DS3 RP driver messages.
Error Message%GRP_C10K_CH_DS3-1-ALLOCFAIL : C10K [dec]/[dec][chars] allocation failure
Explanation C10K-channelized-to-DS3 controller or channel memory allocation 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%GRP_C10K_CH_DS3-5-BERT : Interface [chars], BERT [chars]
Explanation The C10K-CH-DS3 driver received and processed BERT completion event.
Recommended Action None, this is just a notification upon receipt of a BERT completion event.
Error Message%GRP_C10K_CH_DS3-3-CORRUPT : Corrupt configuration, unsupported [chars] ([int]) encountered
Explanation The C10K-CH-DS3 RP driver running configuration is corrupt.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GRP_C10K_CH_DS3-5-FAREND : Interface [chars] [chars] far end request of type ([chars])
Explanation The C10K-CH-DS3 driver received and processed a known far end request.
Recommended Action No action is required. This is just a notification upon receipt of a known request from the far end of the link (e.g., loopback).
Error Message%GRP_C10K_CH_DS3-1-MIA : C10K [dec]/[dec] LC removed during initialization
Explanation C10K-channelized-to-DS3 LC was removed during initialization.
Recommended Action Replace the LC, if C10K-channelized-to-DS3 functionality is desired.
Error Message%GRP_C10K_CH_DS3-4-MSGVERSION : Incompatible message version with slot [dec]
Explanation There is incompatibility between the the message version being send by the line card and the message version used by the GRP. This type of incompatibility could happen is GRP and line card using different IOS versions due to a GRP oir event.
Recommended Action The only problem is that pos statistics are not reported to the GRP, a microcode reload will solve the problem.
Error Message%GRP_C10K_CH_DS3-3-OP : Interface ([chars]): [chars]
Explanation The C10K-CH-DS3 RP driver receives an unexpect 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%GRP_C10K_CH_DS3-3-TIMEOUT : Interface ([chars]): [chars]
Explanation The C10K-CH-DS3 RP driver queries the LC for SONET information, the LC did not reply.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GRP_C10K_CH_DS3-3-UNKNOWN_FAREND : Interface [chars] received an unknown far end request ([int])
Explanation The C10K-CH-DS3 RP driver received an unknown far end request.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GRP_C10K_SRP-4-BADSRPSLOT : SRP slot [dec] allocation rejected: Illegal slot specified
Explanation SRP card pair must be configured via the lower odd numbered slot.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GRP_C10K_SRP-4-CARDMISMATCH : SRP slot [dec] allocation rejected: Card type mismatch
Explanation The card type of the card in this slot is not the one expected by command hw-module slot <slot> srp.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GRP_C10K_SRP-4-CARDOVERLAP : SRP slot [de]allocation rejected: Slot [dec] overlaps.
Explanation Command [no] hw-module slot <slot> srp and command hw-module slot <slot-1> srp overlap.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GRP_C10K_SRP-3-INTERNALEVT : SRP LC Event internal error, [chars] [dec] [dec]
Explanation Internal SRP LC event 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%GRP_C10K_SRP-4-MSGVERSION : Incompatible message version with slot [dec]
Explanation There is incompatibility between the the message version being sent by the line card and the message version used by the GRP. This type of incompatibility could happen is GRP and line card using different IOS versions due to a GRP oir 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%GRP_C10K_SRP-3-OP : Interface ([chars]): [chars]
Explanation The SSRP RP driver receives an unexpect 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%GRP_C10K_SRP-4-SRPMODEMISMATCH : SRP slot [dec] allocation rejected: POS mode already configured on slot [dec]
Explanation The modes of the cards forming an SRP pair must both be unitialized before issuing this 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%GRP_C10K_SRP-3-TIMEOUT : Interface ([chars]): [chars]
Explanation The SSRP RP driver queries the LC for SONET information, the LC did not reply.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.GRP_OC48SRPPOS Messages
The following are OC48SRPOS subsystem messages.
Error Message%GRP_OC48SRPPOS-4-ATTACHNOTDONE : OC48 SRP/POS Redundancy : OIR attach not done for slot ([dec])
Explanation Optics type is invalid on standby.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GRP_OC48SRPPOS-4-ATTACHPENDING : OC48 SRP/POS Redundancy : Attach previously pending slot ([dec])
Explanation An OIR attach was already pending on standby when another attach was received.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GRP_OC48SRPPOS-4-CMD_NOT_SUPPORTED : hw-module slot [dec] [chars] command not supported on card type [chars]
Explanation This command is only supported on the dual mode OC48 SRP/POS 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%GRP_OC48SRPPOS-3-INTERNAL : OC48 POS internal error, [chars] [dec] [dec]
Explanation Internal OC48 POS 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%GRP_OC48SRPPOS-3-INTERNALCMD : OC48 SRP/POS LC command internal error, [chars] [dec] [dec]
Explanation Internal POS LC command 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%GRP_OC48SRPPOS-4-MODECONFIGURED : Slot [dec] Mode Change rejected: not ready for mode change
Explanation The card must be fully uninitialized before issuing this 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%GRP_OC48SRPPOS-4-OPTICSINVALID : OC48 SRP/POS Redundancy : Optics type invalid slot ([dec])
Explanation Optics type is invalid on standby.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GRP_OC48SRPPOS-4-POSMODECONFIGURED : POS slot [dec] allocation rejected: mode already configured
Explanation The card is part of an SRP pair and must be uninitialized before issuing this 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%GRP_OC48SRPPOS-4-REDCONFIGURED : POS slot [dec] mode change rejected: redundancy mode configured
Explanation The card is part of a redundant pair. The redundancy association must be removed before changing the card's mode of operation from POS.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GRP_OC48SRPPOS-3-SYNCPARAMS : OC48 SRP/POS Redundancy state sync failure: Invalid parameters ([dec])/([dec])
Explanation A failure occurred on standby when trying to synchronize 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%GRP_OC48SRPPOS-3-SYNCSLOT : OC48 SRP/POS Redundancy state sync failure: Invalid slot ([dec])
Explanation A failure occurred on standby when trying to synchronize 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.GT96100 Messages
The following are GT96100 DMA controller driver messages.
Error Message%GT96100-3-ECC : CPU corrected [dec] single bit memory errors
Explanation The system has seen too many single bit errors.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.GT96K_FE Messages
The following are Cisco 3700 series and Cisco 3631 systems controller messages.
Error Message%GT96K_FE-5-CONFIGNOT : The Inter-PRE Ethernet Interface is not configurable
Explanation The internal ethernet is for system use only.
Recommended Action No action is required.
Error Message%GT96K_FE-3-EXCESSCOLL : FE - interface: [chars] excessive collisions
Explanation An excessive collision count was recorded on this interface.
Recommended Action Monitor the condition for improvement. Degradation could indicate a faulty transmission line or interfaces. 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%GT96K_FE-3-GENERAL : [chars]
Explanation General C10K failure message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support 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%GT96K_FE-3-INV_ETH_CAUSE : FE - interface [chars] invalid interrupt cause (0)
Explanation An invalid value of 0 was read from the ethernet cause register.
Recommended Action Monitor the interface for improvement. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GT96K_FE-2-LATECOLL : FE - interface: [chars] late collision
Explanation An illegal collision has occurred. This is a fatal network error.
Recommended Action If not usable the interface should be reset. A reboot might be necessary. 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%GT96K_FE-5-NOISL : Configure ISL
Explanation An attempt was made to configure ISL on an interface which does not use it.
Recommended Action Allow system to correct itself. No action is required.
Error Message%GT96K_FE-2-NULL_PTR : [chars]: pointer is null
Explanation Unexpected NULL pointer to a data structure.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%GT96K_FE-4-OWNERR : FE - interface: [chars]: protocol [dec]: OWN_ERR
Explanation A packet descriptor ownership error has occurred.
Recommended Action Allow system to correct itself. No action is required.
Error Message%GT96K_FE-3-SPURIDON : FE - interface: [chars] spurious IDON interrupt
Explanation A spurious SMI done interrupt has occurred.
Recommended Action Monitor the interface for improvement. 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%GT96K_FE-1-SUBIF_IPE : Configure IPE subinterface
Explanation An attempt to configure a subinterface on the IPE was made.
Recommended Action Be aware of the IPE port status. Subinterfaces are not allowed. No action is required.
Error Message%GT96K_FE-1-SUBIF_NME : Configure NME subinterface
Explanation An attempt to configure a subinterface on the NME was made.
Recommended Action Be aware of the NME port status. Subinterfaces are not allowed. No action is required.
Error Message%GT96K_FE-4-TOOBIG : FE - interface: [chars]: size [dec]: pak size
Explanation Packet size limit exceeded.
Recommended Action Allow system to correct itself. No action is required.
Error Message%GT96K_FE-4-TOOMANYPART : FE - count: [dec]: protocol [dec]: descriptor count
Explanation Too many particles of a scattered packet for tx ring.
Recommended Action Allow system to correct itself. No action is required.
Error Message%GT96K_FE-3-TXH_RSRCERR : FE - interface [chars] Tx high resoruce error interrupt
Explanation A transmit resource error interrupt has occurred on the high priority ring.
Recommended Action Monitor the interface for improvement. 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%GT96K_FE-3-TXL_RSRCERR : FE - interface [chars] Tx low resoruce error interrupt
Explanation A transmit resource error interrupt has occurred on the low priority ring.
Recommended Action Monitor the interface for improvement. 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%GT96K_FE-3-TXUNDERRUN : FE - interface [chars] Tx underrun interrupt
Explanation A transmit underrun interrupt has occurred.
Recommended Action Monitor the interface for improvement. 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.%GT96K_FE-3-UNDERFLO : FE - interface: [chars] underflow
Explanation An tx underflow condition occurred. Part of the packets data
was not available while transmission in progress. Possible
memory access delays.Recommended Action Allow system to correct itself. No action is required.
HA Messages
The following are High availability system messages.
Error Message%HA-4-CHKPT : Platform CF - [chars]
Explanation Failure in some 7300 checkpointing activity.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HA-4-CHKPTSEND : [chars] (rc [dec], event [chars])
Explanation Failure to send 7300 checkpointing data.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support 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%HA-4-DECODE : Data decode - [chars] ([dec])
Explanation Failure to decode 7300 checkpointing data descriptors.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HA-4-ENCODE : Data Encode - [chars] ([chars])
Explanation Failure to encode 7300 checkpointing data descriptors.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support 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%HA-6-FALLBACK : [chars] - configured mode([chars]), fallback mode([chars])
Explanation This RP redundancy mode fell back to the indicated mode.
Recommended Action No action is required.
Error Message%HA-4-INCOMPATIBLE : Incompatible RP ([chars]) in slot [dec] - Peer RP being held in reset state
Explanation The peer Route Processor (RP) is not compatible with the active RP and it will be held in reset state.
Recommended Action The peer RP must be removed and replaced with a RP that is the same type as the active RP to have it successfully boot as the standby.
Error Message%HA-6-INT_SSO_UNAWARE : [chars] in slot [dec] on [chars] is not SSO capable
Explanation Native GigabitEthernet interfaces on NPE-G100, NSE-150 and NSE-100 are not SSO capable.
Recommended Action No action is required.
Error Message%HA-4-NOBUF : Failed to allocate buffer for inter-RP IPC message receive
Explanation An error was encountered in the reception of IPC messages from the peer Route Processor because a packet buffer to receive the packet could not be allocated.
Recommended Action The show buffers command can be used to confirm that the IPC buffer pool is suffering misses. Intermittent errors will be handled by the IPC mechanism of retries. However, if this error message is seen with regularity, the system might need to be upgraded to have more memory as the IPC buffer pool is automatically sized in direct proportion to the total amount of memory in the system. Note that there is no configuration command to resize the IPC buffer pool.
Error Message%HA-6-NOCOEXIST : Line card in slot [dec] ([chars]) cannot co-exist in [chars] redundancy mode
Explanation The indicated line card cannot coexist with the rest of the system in the system's current redundancy mode.
Recommended Action No action is required.
Error Message%HA-4-NOPROCESS : Creation of [chars] process failed
Explanation Creation of a platform high availability process failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support 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%HA-4-RESET : Reset of [chars] RP triggered [chars]
Explanation Reset of the active RP was triggered by the standby RP in response to some event that caused the standby RP to conclude that the active RP was no longer functional.
Recommended Action The crashing route processor (RP) will produce a crashinfo file and a core dump if that was configured. These files provide information about the events that triggered the RP to reset. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HA-4-RRPDOWN : Standby RP CEF state is down - resetting standby (slot [dec]) to recover
Explanation The platform HA consistency check has determined that the standby RP is not in the correct state for Stateful Switchover (SSO) operation. This condition can be triggered due to errors in other parts of the system that left the standby RP in a state where it could not be functional in SSO mode. The standby RP will be reset in an effort to recover from the problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support 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%HA-6-STANDBY_READY : Standby RP in slot [dec] is operational in [chars]mode
Explanation Indicates standby route processor readiness
Recommended Action No action is required.
Error Message%HA-4-STBYINITFAIL : Initialization of standby Route Processor in slot [dec] failed
Explanation The initialization of the standby route processor failed. This will result in the high availability features not being operational.
Recommended Action If additional error messages indicate that the type of the standby RP is incompatible with the current active RP, then that should be fixed by inserting a compatible standby RP. If the standby RP is of a type that is compatible with the active RP, then an attempt should be made to remove and firmly re-insert the standby RP. 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%HA-6-SWITCHOVER : Route Processor switched from being standby to being active
Explanation This RP switched to become the active RP.
Recommended Action No action is required.
Error Message%HA-4-SYNC : [chars]
Explanation An error was encountered in a data synchronization operation.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support 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%HA-3-TIFKEY : Tifkey [hex] (Card Type [hex], (S)PA Type [hex]) not present in the Standby Tif table (Hash Slot [dec]) - Standby Reloading
Explanation The standby route processor encountered an error in the reception of the TIF number (channel ID) for the indicated interface from the active route processor. In most situations, this error is self-correcting.
Recommended Action This error affects the standby route processor only. Upon encountering this error, standby route processor reloads itself automatically and reestablishes synchronization with the active route processor. If the standby does not reload itself automatically, reload it from the active route processor console by entering the how-module standby reload command. If this command fails, reload the standby by entering the hw-module standby reset command.If the standby route processor still does not reload or this error is seen again, collect the output from show c7300, show c7300 ha tif entries, show c7300 ha statistics, show c7300 ha registers, show redundancy, show redundancy state, show redundancy switchover history, show redundancy history, and show checkpoint clients commands. Also, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HA-3-TIFTAKEN : Tif number [dec] (Card Type [hex], (S)PA Type [hex]) already allocated in the Standby (Hash Index [hex]) - Standby Reloading
Explanation An error was encountered in reserving the TIF (Channel ID) number meant for a specifc physical/logical interface in the standby route processor. This occurs if there is a race condition in the synchronization of TIF numbers and the running configuration from the active route processor to the standby route processor. In most situations, this error is self-correcting.
Recommended Action This error affects the standby route processor only. Upon encountering this error, standby route processor reloads itself automatically and reestablishes synchronization with the active route processor. If the standby does not reload itself automatically, reload it from the active route processor console by entering the how-module standby reload command. If this command fails, reload the standby by entering the hw-module standby reset command.If the standby route processor still does not reload or this error is seen again, collect the output from show c7300, show c7300 ha tif entries, show c7300 ha statistics, show c7300 ha registers, show redundancy, show redundancy state, show redundancy switchover history, show redundancy history, and show checkpoint clients commands. Also, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HA-6-TOOBIG : Running config too big, config sync failed
Explanation The running configuration was too big to be synced.
Recommended Action No action is required.
Error Message%HA-4-UNKNOWN_RP : Failed to extract RP information for the RP in slot [dec] - Peer RP being held in reset state
Explanation The system was unable to extract information about the peer Route Processor (RP) and therefore cannot determine compatibility status. For this reason it will be held in reset state.
Recommended Action The peer RP must be removed and replaced with a RP that is the same type as the active RP to have it successfully boot as the standby.
HA_CLIENT Messages
The following are high availability client messages.
Error Message%HA_CLIENT-3-BS_TO_STBY_FAILED : The [chars] HA client's Bulk Sync phase was unsuccessful
Explanation The nominated HA client encountered an unspecified failure during its bulk-sync phase on the active unit. Because of this condition, the standby unit is now out of synchronization. This condition should not normally happen and should be reported.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HA_CLIENT-4-CF_NOT_BUNDLED : CF failed to go into bundled mode for the [chars] HA client (rc [int])
Explanation The CF did not allow the specified HA client to use the CF bundled mode. The client continues to operate using the CF unbundled mode.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information. 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%HA_CLIENT-3-CF_REG_FAILED : CF registration for the [chars] HA client failed with return code [int]
Explanation The specified HA client has failed to register properly with the CF. This failure should not occur and indicates a software problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HA_CLIENT-3-CLIENT_INIT_FAILED : Initialisation of the [chars] HA client failed (required field(s) missing)
Explanation The HA client utilities code could not initialize the specified client, because some fields required by the utilities code were not provided by the client. This message indicates a software problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HA_CLIENT-3-CP_TO_STBY_FAILED : Delivery of a checkpointing (CP) message from the [chars] HA client failed
Explanation The CF passed information to the nominated HA client on the active unit that indicated a problem with a checkpoint message. One of the checkpointing messages either could not be sent to or did not reach the standby unit. As a result, the standby unit is now out of synchronization. This failure should not normally occur and should be reported.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HA_CLIENT-3-IF_INDEX_ADD_FAILURE : Unable to add an interface index to a table: [chars] (rc=[dec])
Explanation The interface index could not be added to a table. This condition should be reported.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HA_CLIENT-4-IF_INDEX_LOOKUP_FAILURE : Unable to find an interface index: (rc=[dec]) [chars]
Explanation The interface index could not be found. This is a rare, but possible situation, which should be able to correct itself.
Recommended Action No action is required.
Error Message%HA_CLIENT-3-NO_BS_PROCESS : The [chars] HA client failed to create a Bulk Sync process (rc [int])
Explanation The nominated HA client could not create a Cisco IOS process needed to perform a bulk synchronization. As a result, the client's bulk synchronization did not occur and the standby unit is now out of synchronization. This failure should not occur and should be reported.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HA_CLIENT-3-NO_CF_BUFFER : The [chars] HA client failed to get a buffer (len=[int]) from CF (rc=[dec]); checkpointing failed
Explanation The nominated HA client failed to get a buffer from the CF to store checkpointing data. This condition means that the client was unable to send the data to the standby unit and that the standby unit is now out-of-sync. This condition should not normally occur and should be reported.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HA_CLIENT-3-NO_RF_BUFFER : The [chars] HA client failed to get a buffer (len=[int]) from RF
Explanation The nominated HA client failed to get a buffer from the RF to send an RF message to the peer unit. This condition means that the client was unable to send the message to its peer. This error condition should not normally occur and should be reported.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HA_CLIENT-3-PROTO_VER_INCOMPAT : The HA client '[chars]' is incompatible with the peer
Explanation The named HA client cannot communicate with the client on the peer unit. These units cannot be used in a warm or hot standby environment.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HA_CLIENT-4-RESOURCE_RECOVERY_LIST_FAILURE : Failed to create [chars] resource recovery list
Explanation The specified resource recovery list could not be created. This message means that resource recovery cannot be performed at switchover; some of the relevant resources are left unusable. This error should not normally occur and should be reported.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HA_CLIENT-3-RF_MSG_NOT_SENT : Delivery of an RF message from the [chars] HA client failed (rc=[int])
Explanation The RF told the nominated HA client that the RF could not send a message to the peer unit. This error should not normally occur and should be reported.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HA_CLIENT-3-RF_REG_FAILED : RF registration for the [chars] HA client failed with return code [int]
Explanation The specified HA client failed to register properly with the RF. This error should not occur and indicates a software problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HA_CLIENT-3-VALIDITY_CHECK_FAILURE : The HA client detected a validity check failure: [chars]
Explanation The HA client performed a validity check. This check failed and may indicate a serious problem. A reload might be required to recover from this situation
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.HFE_HAL Messages
The following are the HFE_HAL messages.
Error Message%HFE_HAL-3-ADJHWAPI_ADJ : [chars]
Explanation An internal hwapi s/w error. Getting Null platform space for XDR unpacking
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HFE_HAL-3-ADJHWAPI_CEF : [chars]
Explanation An internal HWAPI software error. A NULL platform space has been encountered.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HFE_HAL-3-ADJHWAPI_OCE : [chars]
Explanation An internal HWAPI software error. Getting NULL oce_base from the handle.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HFE_HAL-3-ADJ_INT : HFE_HAL internal error number of Adj's created: [int], number of Adj's deleted: [int]
Explanation An internal HFE_HAL s/w error. More Adjacency deletes than creates
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HFE_HAL-3-ILLEGALARGS : [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HFE_HAL-3-ILLEGAL_OBJ_TYPE : [chars] [chars]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HFE_HAL-3-INCONSISTENCY_ERROR : [chars]
Explanation Inconsistency between software and hardware occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HFE_HAL-3-WRONG_ARG1 : [chars] [hex]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HFE_HAL-3-WRONG_ARG2 : [chars] [chars] [hex]
Explanation An internal software error has occurred.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.HA_CONFIG_SYNC Messages
The following are High Availability configuration synchronization messages.
Error Message%HA_CONFIG_SYNC-3-ISSU_MTU : CONFIG SYNC Failed to get MTU Size for session[[dec]] msg_type[[dec]], MTU[[dec]], rc[[dec]]
Explanation An ISSU configuration Synchronization failed to get Messge MTU. The details about what was attempted and what went wrong will be printed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HA_CONFIG_SYNC-3-ISSU_REG : CONFIG SYNC [chars] rc([dec])
Explanation An ISSU configuration Synchronization Registration Error occurred. The details about what was attempted and what went wrong will be printed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HA_CONFIG_SYNC-3-ISSU_XFORM : CONFIG SYNC [chars] msg_type[[dec]], rc[[dec]]
Explanation An ISSU configuration Synchronization failed to transform messge. The details about what was attempted and what went wrong will be printed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.HARDWARE Messages
The following are hardware resources messages.
Error Message%HARDWARE-3-ASICNUM_ERROR : Port-ASIC number [dec] is invalid
Explanation Each Port-ASIC is identified by an ID.The port ASIC number used is invalid and this is an internal error.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HARDWARE-3-INDEX_ERROR : Index value [dec] is invalid
Explanation The index into the hardware table is out-of-range.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HARDWARE-3-INTRNUM_ERROR : Port-ASIC Interrupt number [dec] is invalid
Explanation The interrupt ID used in a Port-ASIC is invalid.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HARDWARE-3-PORTNUM_ERROR : port number [dec] is invalid
Explanation Each interface in a given Port-ASIC isidentified using an index value. The port-number usedis not valid (out of range).
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HARDWARE-3-STATS_ERROR : Statistics ID [dec] is invalid
Explanation Each statistics supported by the Port-ASIC are identified using an ID. The ID provided by the caller is out of range.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.HCCP Messages
The following are Hot Connection to Connection Protocol messages.
Error Message%HCCP-5-ACTIVE : Grp [dec] Mbr [dec] [chars]: change state from standby to active cause: [chars].
Explanation HCCP group member notifies that it changes from standby to active.
Recommended Action Ensure peer relinquishes the channel.
Error Message%HCCP-3-BADAUTH : Grp [dec] Mbr [dec] [chars]: bad authentication detected.
Explanation HCCP software has detected unauthorized message.
Recommended Action Ensure the shared secret on the Workingmatches the shared secret on the Protect.
Error Message%HCCP-3-BADCHAN : Grp [dec] Mbr [dec] [chars]: channel switch "[chars]" failed, retries exhausted.
Explanation HCCP group member notifies failure in its channel switch.
Recommended Action Ensure channel switch is functioning.
Error Message%HCCP-3-BADMSG : Grp [dec] Mbr [dec] [chars]: received wrong type of message-[chars].
Explanation Certain types of HCCP message are not supposed to be received by Working or Protect.
Recommended Action Check configuration on this interface and the sender's interface.
Error Message%HCCP-4-BADPATYPE : Grp [dec] Mbr [dec] [chars]: peer is not identical.
Explanation HCCP software has detected hardware mismatching of the Working/Protect pair.
Recommended Action Make sure Working and Protect are identical. Otherwise problemmight happen.
Error Message%HCCP-3-BADSTATE : [chars] Grp [dec], inconsistant state !!
Explanation HCCP state inconsistancy after control plane switchover.
Recommended Action Reset the interface.
Error Message%HCCP-4-BADVER : Grp [dec] Mbr [dec] [chars]: bad version [chars] detected.
Explanation HCCP software has detected invalid version number.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HCCP-3-CFG_FAIL : Configuration for interface [chars] failed.
Explanation The process failed to lock configuration session because another process isusing it.
Recommended Action Manually configure the interface.
Error Message%HCCP-5-CHANOFF : Grp [dec] Mbr [dec] [chars]: turning off channel.
Explanation HCCP group member notifies that it turns off channel switch.
Recommended Action Ensure peer controls the channel.
Error Message%HCCP-5-CHANON : Grp [dec] Mbr [dec] [chars]: turning on channel.
Explanation HCCP group member notifies that it turns on channel switch.
Recommended Action Ensure peer relinquishes the channel.
Error Message%HCCP-3-CHAN_TIMER_NOT_RUNNING : Channel timer for group [dec] not running
Error Message%HCCP-5-FAILURE : Grp [dec] Mbr [dec] [chars]: received failure notice-[chars].
Explanation HCCP group member is notified by third party that a failure or failover has just occurred. It reacts to this notification properly.
Recommended Action Check channel failure.
Error Message%HCCP-5-HELLOACK : Grp [dec] Mbr [dec] [chars]: HCCP Hello ACK initiating switchover.
Explanation Internal HCCP Hello ACK msg received: HCCP states are inconsistent.
Recommended Action No action is required.
Error Message%HCCP-3-MISS_STATICSYNC_DONE : HCCP [dec] [chars]: Static Sync Done is missed because [chars], Redo static sync through CLI.
Explanation HCCP static synchronization done is missed because of switch over happened or STATICSYNCDONE message missed.
Recommended Action Perform static synchronization through CLI.
Error Message%HCCP-3-NOINTFC : No interfaces available for IP connection.
Explanation HCCP requires an out-of-band path for inter-router communication.
Recommended Action Configure an out-of-band path for inter-router HCCP communication
Error Message%HCCP-4-NOREVERT : Grp [dec] Mbr [dec]: Revert operation cancelled.
Explanation HCCP group member will not attempt to revert back to the Working interface. Possible reason for this would be that the last failure detected on the Working interface was a keepalive failure.
Recommended Action If the last failure reason on the Working was a keepalive failure, it might have occurred because of a cable cut. Make sure the US/DS coax cables to the Cable Modems have not been disconnected or cut. After fixing the problem, a revert can be attempted manually by entering the command: hccp <grp> switch <mbr> .
Error Message%HCCP-4-NOSUBIF : Grp [dec] [dec] [chars]: [chars].[dec] is not found.
Explanation Protect does not have the sub-interface that Working has.
Recommended Action Ensure Protect has all the sub-interfaces that all Workings have.
Error Message%HCCP-5-NOSWITCHOVER : Grp [dec] Mbr [dec] [chars]: ignored switchover or failover notice.
Explanation HCCP member ignors switchover or failover notice when it has no knowledge of the peer's presence; or a switchover just occurred, the following switchovers are ignored if they arrive within wait-to-restore period.
Recommended Action Might need to check channel failure if it is a failover.
Error Message%HCCP-3-OUT_OF_ORDER_LC2RP : Grp [dec] Mbr [dec] status [chars]: Received LC to RP sync in standby state. Message rejected.
Explanation HCCP software has detected that messages are Out of Order.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HCCP-3-OUT_OF_ORDER_MSG : Grp [dec] Mbr [dec] status [chars]: NULL hp encountered.
Explanation HCCP software has detected that messages are Out of Order.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HCCP-4-PEERBUSY : Grp [dec] Mbr [dec] ([chars]) Switchover aborted. Protect ([chars]) is already ACTIVE for Grp [dec] Mbr [dec] ([chars]).
Explanation HCCP software has detected that the PROTECT interface is alreadyActive for another Working.
Recommended Action Free up the Protect interface by reverting back to the other Working and try this switchover again.
Error Message%HCCP-4-PEER_CRASH : Received crash notification from [IP_address]
Explanation Peer Router crash has been observed. If protecting some interfaces of peer, then those interfaces will switch over.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HCCP-3-PROTECTING_TOO_MANY : Grp [dec] Mbr [dec] status [chars]: Protecting too many Workings.
Explanation HCCP detected that protect is asked to protect too many working i/fs.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HCCP-3-SNMPFAIL : Grp [dec] [chars]: failed to initialize SNMP.
Explanation HCCP group fails to create SNMP message.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HCCP-5-STANDBY : Grp [dec] Mbr [dec] [chars]: change state from active to standby cause: [chars].
Explanation HCCP group member notifies that it changes from active to standby.
Recommended Action Make sure peer controls the channel.
Error Message%HCCP-5-STATICSYNC : Grp [dec] Mbr [dec] [chars]: receiving static sync.
Explanation HCCP group member received RESYNC message and starts to receive static synchronization.
Recommended Action .Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HCCP-6-STATICSYNC_COMPLETED : HCCP static sync for [chars] is completed in [dec] ms.
Explanation HCCP static synchronization for the group(s) in list is completed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HCCP-4-STATICSYNC_WARNING : HCCP static sync warning: [chars].
Explanation HCCP static synchronization might have experienced a race condition.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HCCP-5-SWITCHOVER : Grp [dec] Mbr [dec] [chars]: switching over.
Explanation HCCP group member notifies that it is switching over with the peer.
Recommended Action LOG_STD_NO_ACTION.
Error Message%HCCP-5-SWITCHOVERREADY : Grp [dec] Mbr [dec] [chars]: ready to switchover.
Explanation HCCP group member suspend timer expires, ready to switchover.
Recommended Action LOG_STD_NO_ACTION.
Error Message%HCCP-5-SWITCHREQ : Grp [dec] Mbr [dec] [chars]: requested switchover, retry [dec].
Explanation HCCP group member notifies that it sended switch request.
Recommended Action LOG_STD_NO_ACTION
Error Message%HCCP-3-UNKNOWN_TLV : Grp [dec] Mbr [dec] [chars]: received Unknown TLV type-[dec].
Explanation HCCP software has detected Unknown TLV types,this might not affect the functionality.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.HDLC Messages
The following are High-Level Data Link Control messages.
Error Message%HDLC-4-ISSU_INCOMPATIBLE : hdlc-issu-compat: returned FALSE
Explanation The compatibility checking has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Enter the show tech-support 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%HDLC-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%HDLC-4-ISSU_SENDFAILED : HDLC 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. Enter the show tech-support 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%HDLC-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. Enter the show tech-support 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.HLFM Messages
The following are forwarding manager messages.
Error Message%HLFM-3-MACFREE_ERROR : MAC address [enet], vlad [dec] is still referenced; cannot free
Explanation An attempt was made to free a MAC address before all references to it had been released.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HLFM-3-MAP_ERROR : IP address [IP_address] not in mac tables, mac-address [enet], vlan [dec]
Explanation IP address and mac-address-tables are out of synchronization.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HLFM-3-MOD_SD : Failed to modify Station Descriptor with index [dec], vlan [dec], di [dec], error [dec], mad [dec], ref-count [dec]
Explanation Forwarding Manager trying to modify station descriptor, which is no longer in use or invalid.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.HQF_MAP_TT Messages
The following are TT NP Mapper messages.
Error Message%HQF_MAP_TT-3-HQF : [chars] error detected: [chars] [hex] [hex]
Explanation A software programming error for the HQF TT NP Mapper was detected.
Recommended Action This software programming error is not considered fatal to the operation of the TT NPs. The software is designed to detect and report the error condition. If this message recurs, reset the affected device. Copy the message exactly as it appears on the console or in the system log. Record the output from the show tech show lo command. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support representative and provide the representative with the gathered information.Error Message%HQF_MAP_TT-6-HQF_INFO_OVERSUBSCRIPTION_CLEARED : [chars]
Explanation The HQF over-subscription condition on interface [chars] has cleared.
Recommended Action Informational message only. No action is required.
Error Message%HQF_MAP_TT-6-HQF_INFO_OVERSUBSCRIPTION_DETECTED : [chars]
Explanation The current configuration has resulted in an oversubscription at the HQF level. This can be because of shaping in a parent policy-map, bandwidth being reserved for ATM VPs or MLPoA links or a combination of all of the above.
Recommended Action The router recognized this condition and has modified its behavior to deal with it. However, if this condition is unexpected verify the configuration and make the appropriate changes.
Error Message%HQF_MAP_TT-4-HQF_WARN_RL_1S : [chars] [hex] [hex]
Explanation A warning was generated in the HQF TT NP Mapper.
Recommended Action The router configuration might not be exactly as desired, verify the configuration to make sure it is within the system limits.
Error Message%HQF_MAP_TT-3-NOMEM : Memory Allocation Failure - [chars] ([hex])
Explanation HQF TT NP Mapper could not allocate required memory needed.
Recommended Action This error might indicate that more memory must be installed in order to service all the features and related entities enabled via the configuration. Try to reload the IOS image. If this message recurs, copy the message exactly as it appears on the console or in the system log. Enter the show tech show log 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.HSRP Messages
The following are Hot Standby Router Protocol (HSRP) messages.
Error Message%HSRP-4-BADAUTH : Bad authentication from [IP_address], group [dec], remote state [chars]
Explanation Two routers participating in HSRP disagree on the valid authentication string.
Recommended Action Use the standby authentication command to repair the HSRP authentication discrepancy between the local system and the one whose IP address is reported.
Error Message%HSRP-4-BADAUTH2 : Bad authentication from [IP_address]
Explanation Two routers participating in HSRP disagree on the valid authentication string.