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 sync requested on [chars] 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.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-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-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.