Table Of Contents
TEMUX84 Messages
TENGIGE_LC Messages
TI1570 Messages
TLV Messages
TMCIPC Messages
TN Messages
TOASTER_IPC Messages
TOPN Messages
TR Messages
TRACKING Messages
TRANGE Messages
TRANSCIEVER Messages
TRUNK Messages
TRUNK_CLOCK Messages
TTY Messages
TTYDRIVER Messages
TUNSS Messages
TXCONN Messages
UBR10K Messages
UBR10K_REDUNDANCY Messages
UBR10K_TCC Messages
UBR7200IPC Messages
UBRIFCON Messages
UBRLCCOREDUMP Messages
UBRLCDUMP Messages
UBRLCIFCON Messages
UBRSNMP Messages
UDLD-SP Messages
UNIXLC_SPA Messages
UNIXRP_SPA
UNIX_SPA Messages
UPCONV Messages
UPGRADE Messages
USBFLASH Messages
USB_HOST_STACK Messages
USB_TOKEN Messages
USB_TOKEN_FILESYS Messages
V6FIB Messages
VALENCIA Messages
VDD Messages
VFI Messages
VIP Messages
VIPMLP Messages
VIP_MDR Messages
VLAN Messages
VLAN_MAPPING_ISSU Messages
VOA Messages
VOICE_FSM Messages
VOICE_RC Messages
VPA Messages
VPD Messages
VPDN Messages
VPLS_NP_CLIENT Messages
VPN_HW Messages
VPNSMIOS Messages
VQPCLIENT Messages
VRFS Messages
VRRP Messages
WCCP Messages
WiSM Messages
WS_ALARM Messages
WS_DEFERRED Messages
WSHTF Messages
WSIPC Messages
X25 Messages
X40G Messages
X40G_LI Messages
X40G_L2_ACL Messages
X40G_PC_QOS Messages
X40G_QOS Messages
X40G_SACL Messages
XCCTSP_VOICE Messages
XCONNECT Messages
XCPA Messages
XCVR Messages
XDR Messages
XXX Messages
TEMUX84 Messages
The following are PMC Temux-84 driver messages.
Error Message
%TEMUX84-3-BSWAITERR
: temux84 Byte-Sync indirect access failed, [chars]
Explanation The hardware busy bit has not been cleared.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TEMUX84-3-RTTBWAITERR
: temux84 RTTB indirect access failed, [chars]
Explanation The hardware busy bit has not been cleared.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TEMUX84-3-SBIWAITERR
: temux84 SBI indirect access failed, [chars]
Explanation The hardware busy bit has not been cleared.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TEMUX84-3-T1E1WAITERR
: temux84 T1E1 indirect access failed, [chars]
Explanation The hardware busy bit has not been cleared.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TEMUX84-3-T3E3PMONERR
: temux84 T3E3 PMON update failed, [chars]
Explanation The T3E3 PMON counter failed to latch.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
TENGIGE_LC Messages
The following are 10 Gigabit Ethernet line card messages.
Error Message
%TENGIGE_LC-3-TENGIGE_CDL_HEC_ETX_ALM_CLR
: CLEARED : [chars] CDL HEC error count:
[chars]
Explanation The CDL HEC error alarm has cleared.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-INTF_CREATE_FAILED
: Interface Create Failed : [chars]
Explanation Interface data structure creation or initialization has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-6-LASER_DISABLED
: Laser disabled as per user configuration
[[dec]/[dec]]
Explanation The laser has been disabled as specified by the user configuration.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-6-LASER_DISABLED_BY_HW
: Laser disabled as per laser safety
configuration [[dec]/[dec]]
Explanation The laser has been disabled as specified by the user configuration.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-6-LASER_OK
: Laser on [[dec]/[dec]] is ready for traffic !!
Explanation The laser has been disabled as specified by the user configuration.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-6-LASER_SOFT_START
: Starting the 10GE trunk laser turn on procedures
for : [dec], [dec]
Explanation Starting the 10GE trunk laser turn on procedures
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-LASER_TEMP_ERR
: Laser Temperature Alarm : [dec]/[dec]
Explanation Laser temperature error 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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-6-LASER_TEMP_WAIT
: Waiting for the laser to reach the expected
temperature level : [dec]/[dec]
Explanation Laser temperature waiting 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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-LASER_TX_POWER_ERR
: Laser did not reach the expected power level...
disabling now : [dec]/[dec]
Explanation Laser power error 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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-6-LASER_TX_POWER_WAIT
: Waiting for the 10GE laser to reach steady
power : [dec]/[dec]
Explanation The 10 Gigabit Ethernet transponder module is waiting for the laser to reach steady
power.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-6-LASER_DISABLED
: Laser disabled as per user configuration
[[dec]/[dec]]
Explanation Laser power ok 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
%TENGIGE_LC-6-LASER_DISABLED_BY_HW
: Laser disabled as per laser safety
configuration [[dec]/[dec]]
Explanation Laser power ok 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
%TENGIGE_LC-3-LASER_TEMP_ERR
: Laser Temperature Alarm : [dec]/[dec]
Explanation Laser temperature error 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
%TENGIGE_LC-3-MIB_TENGIGE_CDL_HEC_ETX_ALM
: CDL HEC error count; [chars]
Explanation The error count for the CDL HEC has exceeded the maximum allowed level.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-MIB_TENGIGE_CETXE
: Line Code Err count; [chars]
Explanation The 10 Gigabit Ethernet receiver detects a line code error.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-MIB_TENGIGE_LASER_FAILURE
: Laser failure detected during soft-start
procedures : [chars]
Explanation A laser failure 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
%TENGIGE_LC-3-MIB_TENGIGE_LOSYNC_ALM
: Loss of Sync ; [chars]
Explanation The Gigabit Ethernet function has lost its 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
%TENGIGE_LC-3-MIB_TENGIGE_LSBIAS_ALM
: Laser BIAS threshold exceeded alarm; laser
is starting to die : [chars]
Explanation The laser bias has exceeded the alarm level.
Error Message Copy the message exactly as it appears on the console or in the system log. Research and
attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some
messages, these tools and utilities will supply clarifying information. Search for resolved software issues
using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still
require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-6-MIB_TENGIGE_TRUNK_LOSYNC_PALM
: Trunk side Loss of Sync Prealarm;
[chars]
Explanation The trunk lost its synchronization while it was receiving data.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-MIB_TENGIGE_LSTMP_ALM
: Laser exceeded the operating temperature
threshold : [chars]
Explanation The laser temperature threshold exceeded
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-6-MIB_TENGIGE_TRUNK_RX_LCK_PALM
: Trunk side Loss of Lock Pre-Alarm:
[chars]
Explanation The trunk-side receive has lost synchronization and is not receiving light; the system has
switched to the other side.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-MIB_TENGIGE_TXLCK_ALM
: Loss of Lock on Transmit : [chars]
Explanation The ingress has lost synchronization for the transmit.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-MIB_TENGIGE_OVF_ALM
: Transmit FIFO overflow : [chars]
Explanation A transmit FIFO overflow 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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-MIB_TENGIGE_RXLCK_ALM
: Loss of Lock on Receive : [chars]
Explanation An ingress loss-of-synchronization alarm for the Rx function has been raised.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-MIB_TENGIGE_RXLOP_ALM
: Receive Loss Of Light : [chars]
Explanation A loss-of-light alarm for the Rx function has been raised.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-6-MIB_TENGIGE_RXLOP_PALM
: Trunk side Receive Loss Of Light Pre-Alarm
: [chars]
Explanation An egress loss-of-light alarm for the Tx function has been raised.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-MIB_TENGIGE_SF_ALM
: Signal Failure : [chars]
Explanation Unavailable.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-MIB_TENGIGE_SW_ALM
: Autofailover switch failed to switch to the
other branch
Explanation Because of a mechanical defect, the autofailover switch has failed to change to the other
branch.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-6-MIB_TENGIGE_TRUNK_CDL_HETX_PALM
: Trunk side CDL HEC error count;
[chars]
Explanation The trunk side CDL HEC error count threshold exceeded the Prealarm.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-6-MIB_TENGIGE_TRUNK_CDL_RFOF_IND
: Trunk side CDL Drop FIFO OvrFL
Prealarm; [chars]
Explanation The trunk side has detected that an excess of CDL messages are being dropped because
of a FIFO overflow 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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-6-MIB_TENGIGE_TRUNK_CETXE_PALM
: Trunk side Line Code err count
Prealarm; [chars]
Explanation The trunk-side receive line code error count has exceeded the pre-alarm level.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-6-TENGIGE_FOV_IND
: Trunk Receive splitter Hardware Autofailover
occured: [chars]
Explanation A hardware switchover has occurred on the splitter.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-TENGIGE_CDL_HEC_ETX_ALM
: [chars] side CDL HEC error count: [chars]
Explanation CDL HEC error count threshold exceeded
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-TENGIGE_CDL_HEC_ETX_ALM_CLR
: CLEARED : [chars] CDL HEC error count:
[chars]
Explanation CDL HEC error count threshold exceeded
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-TENGIGE_CETXE
: [chars] side Line Code Err count: [chars]
Explanation The 10 Gigabit Ethernet Line Code error count exceeded the 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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-TENGIGE_CETXE_CLR
: CLEARED : [chars] Line code Err count: [chars]
Explanation The line code error alarm is cleared.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-6-TENGIGE_FOV_IND
: Trunk Receive splitter Hardware Autofailover
occured: [chars]
Explanation Trunk Receive splitter autofailover has occured.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-TENGIGE_LOSYNC_ALM
: [chars] side Loss of Sync lock: [chars]
Explanation The 10 Gigabit Ethernet protocol monitor has detected a loss of synchronization 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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-TENGIGE_LOSYNC_ALM_CLR
: CLEARED : [chars] Loss of Sync lock: [chars]
Explanation The Gigaboit Ethernet Loss of Syncronization alarm has cleared.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-TENGIGE_LSBIAS_ALM
: [chars] Laser BIAS threshold exceeded alarm;
laser is starting to die; [chars]
Explanation The 10 Gigabit Ethernet laser bias current has exceeded the maximum allowed level.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-TENGIGE_LSBIAS_ALM_CLR
: CLEARED : [chars] Laser BIAS threshold
[chars]
Explanation The laser bias threshold alarm has cleared.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-TENGIGE_LSTMP_ALM
: [chars] Laser exceeded the operating temperature
threshold: [chars]
Explanation The 10 Gigabit Ethernet laser temperature has exceeded the maximum recommended
operating temperature.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-TENGIGE_LSTMP_ALM_CLR
: CLEARED : [chars] Laser temperature
threshold: [chars]
Explanation The laser temperature alarm has cleared.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-TENGIGE_OVF_ALM
: [chars] Transmit to Trunk FIFO overflow: [chars]
Explanation The Transmit FIFO has overflowed.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-TENGIGE_OVF_ALM_CLR
: CLEARED : [chars] Transmit to Trunk FIFO
overflow: [chars]
Explanation The Tx trunk buffer overflow alarm has cleared.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-TENGIGE_RXLCK_ALM
: [chars] Loss of Lock on Receive: [chars]
Explanation The 10 Gigabit Ethernet CDR unit cannot lock onto the incoming 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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-TENGIGE_RXLCK_ALM_CLR
: CLEARED : [chars] Loss of Lock on Receive:
[chars]
Explanation The loss lock has cleared.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-TENGIGE_RXLOP_ALM
: [chars] Receive Loss Of Light: [chars]
Explanation The 10 Gigabit Ethernet receiver detects a loss of light on the client side.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-TENGIGE_RXLOP_ALM_CLR
: CLEARED : [chars] Loss Of Light: [chars]
Explanation The loss-of-light alarm has cleared.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-TENGIGE_SF_ALM
: Signal Failure : [chars]
Explanation The 10 Gigabit Ethernet detects a loss of synchronization or loss of lock. Excessive
attenuation can cause this error.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-TENGIGE_SF_ALM_CLR
: CLEARED : [chars] Signal Failure : [chars]
Explanation The signal failure alarm has cleared.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-TENGIGE_SW_ALM
: Autofailover switch failed to switch to the other
branch: [chars]
Explanation The hardware switchover to the standby path has failed. This error could occur because
of a bad switch on the line card motherboard.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-6-TENGIGE_TRUNK_CDL_HETX_PALM
: Trunk side CDL HEC error count:
[chars]
Explanation The trunk side CDL HEC error count threshold has exceeded the Prealarm.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-6-TENGIGE_TRUNK_CDL_RFOF_IND
: Trunk side CDL Drop FIFO OvrFL: [chars]
Explanation The trunk side has detected that an excess of CDL messages are being dropped because
of a FIFO overflow 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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-6-TENGIGE_TRUNK_CETXE_PALM
: Trunk side Line Code err count: [chars]
Explanation The trunk-side receive line code error count has exceeded the pre-alarm level.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-6-TENGIGE_TRUNK_RX_LCK_PALM
: Trunk side Loss of Lock Pre-Alarm:
[chars]
Explanation The trunk-side receive has lost synchronization and is not receiving light; the system has
switched to the other side.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-6-TENGIGE_TRUNK_RX_LOSYNC_PALM
: Trunk side Loss of Sync lock
Prealarm: [chars]
Explanation The trunk lost its synchronization while it was receiving data.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-6-TENGIGE_TRUNK_RX_PALM
: Trunk side Loss of Light Pre-Alarm: [chars]
Explanation The 10 Gigabit Ethernet receiver detects a loss-of-light or power level below the
configured low threshold on the previous active 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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-6-TENGIGE_TRUNK_RX_SF_PALM
: Trunk side Signal Failure Prealarm:
[chars]
Explanation The 10 Gigabit Ethernet receiver detects a loss of synchronization or loss of lock on the
trunk Rx.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-TENGIGE_TXLCK_ALM
: [chars] Loss of Lock on Transmit: [chars]
Explanation The 10 Gigabit Ethernet transponder detects a loss of lock on the transmit.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-TENGIGE_TXLCK_ALM_CLR
: CLEARED : [chars] Loss of Lock on Transmit:
[chars]
Explanation The loss of lock on transmit error has cleared.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-TENGIGE_TXLOP_ALM
: [chars] Transmit Loss Of Light: [chars]
Explanation The 10 Gigabit Ethernet transponder detects a loss of light on the transmit.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-TENGIGE_TXLOP_ALM_CLR
: CLEARED : [chars] Transmit Loss Of Light:
[chars]
Explanation The loss of light on transmit error has cleared.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TENGIGE_LC-3-XPLTA2D
: Err calculating xpolated value: [chars]
Explanation The physubcard or IDPROM pointer 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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
TI1570 Messages
The following are the PCI/TI1570-based ATM port adapter error messages.
Error Message
%TI1570-3-BLOCKCMDFAIL
: [chars] block command (code [dec]) failed, error code
[dec]
Explanation An internal hardware or software error has occurred.
Recommended Action If the message recurs, copy the message exactly as it appears on the console or
in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%TI1570-1-DEVICEINITFAIL
: PCI configuration for [chars] in slot [dec]
Explanation The ATM Port Adapter failed to complete hardware initialization.
Recommended Action Reset the adapter. This should not be a recurring condition. If the message
recurs, copy the message exactly as it appears on the console or in the system log. Research and
attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With
some messages, these tools and utilities will supply clarifying information. Search for resolved
software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TI1570-3-DISCOVER
: Found [dec] out of [dec] devices (ID [hex]) in bay [dec]
Explanation The ATM-PCI Port Adapter software driver found fewer devices than it was configured
to expect. This could mean that the missing one(s) failed to start and may have failed.
Recommended Action Try shutting off the power, re-seating the card, and rebooting. If the message
recurs, copy the message exactly as it appears on the console or in the system log. Research and
attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With
some messages, these tools and utilities will supply clarifying information. Search for resolved
software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TI1570-3-FAILSETUPVC
: Interface [chars], Failed to setup vc [dec] (Cause:
[chars])
Explanation A hardware failure in the ATM-PCI Port Adapter might have 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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TI1570-3-FAILTEARDOWNVC
: Interface [chars], Failed to down vc [dec] (Cause:
[chars])
Explanation An ATM virtual circuit could not be shut down for the reason shown in the error
message. 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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TI1570-7-FRAMERINT
: TI1500 framer interrupt isr1 [hex], isr2 [hex], isr3 [hex]
Explanation The ATM-PCI port adapter driver has received and handled a framer interrupt.
Recommended Action No action is required.
Error Message
%TI1570-1-IDBINITFAIL
: [chars] for subunit [dec] in bay [dec]
Explanation The ATM Port Adapter failed to complete hardware initialization.
Recommended Action Reset the adapter. This should not be a recurring condition. 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. Search for resolved
software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TI1570-1-INITFAIL
: [chars] [chars]
Explanation The ATM Port Adapter failed to complete hardware initialization. Details of the failure
are shown in the error message.
Recommended Action Reset the adapter. This should not be a recurring condition. 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. Search for resolved
software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TI1570-3-NOPCIMB
: TI1570 unit [dec]: PCI mini buffer unavailable.
Explanation An internal hardware or software error has occurred.
Recommended Action If the message recurs, copy the message exactly as it appears on the console or
in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%TI1570-3-NOPCIMEMORY
: TI1570 unit [dec]: PCI memory unavailable.
Explanation The system experience memory exhaustion in the PCI/packet memory. This is probably
due to heavy traffic congestion but could also be a software error.
Recommended Action Review the configuration for performance bottlenecks. If the message recurs,
copy the message exactly as it appears on the console or in the system log. Research and attempt to
resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some
messages, these tools and utilities will supply clarifying information. Search for resolved software
issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TI1570-3-NOSYSMEMORY
: TI1570 unit [dec]: SYSTEM memory unavailable.
Explanation Memory exhaustion has occurred in the ATM-PCI Port Adapter driver.
Recommended Action If the message recurs, copy the message exactly as it appears on the console or
in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%TI1570-3-NOTTI1570
: Bay [dec] device ID seen as [hex], expected [hex]
Explanation The ATM-PCI port adapter driver could not recognize the interface chips.
Recommended Action Power down, reseat the interface card, and reboot. If the message recurs, copy
the message exactly as it appears on the console or in the system log. Research and attempt to
resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some
messages, these tools and utilities will supply clarifying information. Search for resolved software
issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl.
If you still require assistance, open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TI1570-3-NOTXDESCSPACE
: [chars] No tx buffer descriptor space in particle, data
block [hex], data start [hex]
Explanation This message is probably caused by memory exhaustion. Memory could not be allocated
by the driver for a packet.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration.
Error Message
%TI1570-3-PCI_PERROR
: TI1570 unit [dec]: PCI parity error ([hex])
Explanation A parity error occurred on the PCI bus. This probably indicates an existing or
developing hardware failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TI1570-3-PLXNOTFOUND
: Bay [dec] device ID seen as [hex], expected #[hex]
Explanation The ATM-PCI Port Adapter driver found incorrect device IDs on the specified card.
This could indicate either a hardware failure, or it may indicate that the Cisco IOS software must be
upgraded to recognize newer hardware.
Recommended Action Power down, reseat the interface card, and reboot. Check if newer software is
required for your hardware. If the message recurs, copy the message exactly as it appears on the
console or in the system log. Research and attempt to resolve the issue using the tools and utilities
provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply
clarifying information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TI1570-3-RBDCORRUPT
: TI1570: received corrupted shadow particle pointer
Explanation The ATM-PCI port adapter driver has experienced an internal error that was caused by
a software or hardware failure.
Recommended Action If the message recurs, copy the message exactly as it appears on the console or
in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TI1570-3-RXFREEZE
: [chars] receive freeze [dec]
Explanation This message indicates that excessive traffic congestion on the ATM interface may have
resulted in cell loss. The cell buffers of the PCI-ATM interface were full when a cell arrived on the
interface, resulting in a receive freeze condition. A small number of freezes might not be a cause for
concern.
Recommended Action If the message recurs, copy the message exactly as it appears on the console or
in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TI1570-3-RX_HALT
: TI1570 unit [dec]: Receive Channel Halt
Explanation A hardware failure involving the ATM-PCI port adapter 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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TI1570-3-TXDATANOTALIGNED
: [chars] tx buffer data start not aligned to 32 bit
boundary, data block[hex], data start [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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TI1570-3-TXDMANOTFLUSHED
: TX DMA not flushed
Explanation A transmit DMA channel failed to flush its buffers during the shutdown of an ATM
interface. This failure error could indicate either a hardware or a software failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TI1570-3-TXFREEZE
: [chars] transmit freeze [dec]
Explanation The PCI-ATM interface had to stop the transmitter while waiting for data. A small
number of freezes might not be a cause for concern.
Explanation If the message recurs, copy the message exactly as it appears on the console or in the
system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
TLV Messages
The following are the TLV messages.
Error Message
%TLV-3-GET
: Reading data type [dec]
Explanation An expected field in the TLV buffer is either missing or malformed.
Recommended Action If the message recurs, copy the message exactly as it appears on the console or
in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%TLV-3-UPDATE
: Unable to write type [dec]
Explanation An attempt to update a TLV entry has failed.
Recommended Action If the message recurs, copy the message exactly as it appears on the console or
in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
TMCIPC Messages
The following are the TMCIPC messages.
Error Message
%TMCIPC-4-DUP
: Received a duplicated IPC record for [chars] with seq #:[dec].
Explanation While retrieving information from the PXF processors through a packetized
Inter-Processor Communication (IPC) scheme, a duplicate packet sequence number was detected.
The sequence number in the current record is the same as the sequence number in the previous
message. The duplicate packet is dropped. This message is normally due to retransmissions from the
PXF processors when the Route Processor load is high.
Explanation Copy the message exactly as it appears on the console or in the system log. Research
and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac.
With some messages, these tools and utilities will supply clarifying information. Search for resolved
software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
TN Messages
The following are the TN Messages.
Error Message
%TN-2-BADCONN
: Bad conn pointer [hex] closing all connections on terminal line
[dec]
Explanation An internal software error has occurred.
Recommended Action If the message recurs, copy the message exactly as it appears on the console or
in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TN-2-BADLOGIN
: Bad login string pointer [hex]
Explanation An internal software error has occurred.
Recommended Action If the message recurs, copy the message exactly as it appears on the console or
in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TN-3-BADSTATE
: Illegal state [dec]
Explanation An internal software error has occurred.
Recommended Action If the message recurs, copy the message exactly as it appears on the console or
in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TN-3-READLINE
: Unknown return code [dec] from telnet_readline()
Explanation An internal software error has occurred.
Recommended Action If the message recurs, copy the message exactly as it appears on the console or
in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
TOASTER_IPC Messages
The following are Toaster Interprocess Communication (IPC) messages.
Error Message
%TOASTER_IPC-3-BAD_TIMEOUT
: Invalid timeout parameter ([dec]ms is < [dec], or >
[dec]).
Explanation Timeout parameter passed in 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
%TOASTER_IPC-3-NO_RES
: Could not allocate resource: [chars]
Explanation The named resource could not be allocated, possibly at 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
%TOASTER_IPC-3-NO_STATE
: Attempt to pass a bad message to the Toaster.
Explanation A null pointer or a bad message buffer was detected.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TOASTER_IPC-3-STILL_BLOCKED
: Unexpected state while blocked, waiting for IPC
response.
Explanation The process waiting for an IPC response was awakened but the blocked flag was still set.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TOASTER_IPC-3-TOO_LONG
: Invalid message length.
Explanation Requested message > TT_IPC_MESSAGE_MAX_SIZE.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
TOPN Messages
The following are TOPN Counters messages.
Error Message
%TOPN_COUNTERS-5-AVAILABLE
: TopN report [dec] is available
Explanation The specified report is ready and can be viewed by the users.
Recommended Action No action is required.
Error Message
%TOPN_COUNTERS-5-DELETED
: TopN report [dec] deleted by [chars]
Explanation The specified report has been deleted by the user.
Recommended Action No action is required.
Error Message
%TOPN_COUNTERS-5-KILLED
: TopN report [dec] task killed by [chars] [chars]
Explanation The system was in the process of generating the specified report, but the specified user
terminated the report before its completion.
Recommended Action No action is required.
Error Message
%TOPN_COUNTERS-5-NOPORTS
: No interfaces in the system match the interface type for
the generation of the topN report [dec]
Explanation There were no interfaces in the system which matched the interface type selected in the
specified report.
Recommended Action No action is required.
Error Message
%TOPN_COUNTERS-5-STARTED
: TopN collection for report [dec] started by [chars]
Explanation The TopN report that was requested by the specified user starts with the specified report
number.
Recommended Action No action is required.
TR Messages
The following are the TR messages.
Error Message
%TR-3-BADBRDGPARMS
: Unit [dec], bad bridge parameters: bridge_num=[dec],
max_rd=[dec]
thisring=[dec], targetring=[dec]
Explanation An internal software error occurred.
Recommended Action If the message recurs, copy the message exactly as it appears on the console or
in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%TR-3-BADBUFFSIZE
: Unit [dec], bad buffersize = [dec]
Explanation An internal software error occurred.
Recommended Action If the message recurs, copy the message exactly as it appears on the console or
in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%TR-3-BADFIRM
: Unit [dec], Tokenring firmware download failed
got [hex], expected [hex], at address [hex].[hex]
Explanation An internal software 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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%TR-3-BADFIRMTYPE
: Unit [dec], bad firmware type code during [chars]. type=[hex],
fw=[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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%TR-3-BADFUNC
: Unit [dec], bad functional address=[hex], ring mode=[hex]
Explanation An internal software error has occurred.
Recommended Action If the message recurs, copy the message exactly as it appears on the console or
in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%TR-3-BADSTART
: Unit [dec], Start completion and wrong idb state - state= [dec]
Explanation An internal software error occurred.
Recommended Action If the message recurs, copy the message exactly as it appears on the console or
in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%TR-3-DIAGFAIL
: Interface [chars] failed init diags ([hex]), [chars]
Explanation The microcode attempted to run its diagnostics on the chip and failed.
Recommended Action Enter the clear interface command.
Error Message
%TR-3-INITFAIL
: Unit [dec], init failed. result code=[hex], error code=[hex]
Explanation The Token Ring hardware failed to initialize properly.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%TR-3-INTFAIL
: Unit [dec] interface failure: [hex] [hex] [hex], idb state [dec]
Explanation The Token Ring Monitor firmware detected a fatal error due either to
an internal software problem or to a hardware failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%TR-3-MODEFAIL
: Unit [dec], change mode failed. result code=[hex], error
code=[hex]
Explanation An internal hardware or 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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%TR-3-NOFIRM
: Unit [dec], no TMS380 firmware present. eagle=[hex], magic=[hex]
Explanation An internal hardware or 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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%TR-3-OPENFAIL2
: Unit [dec], open failed: check the lobe cable DB-9 connection.
Explanation The Token Ring interface was unable to insert itself into the ring,
and the error code returned indicates a wiring problem.
Recommended Action Check the cable connecting the router to the Token Ring MAU, and attempt to
open the interface again. This generally can be accomplished by issuing the clear interface tokenring
command.
Error Message
%TR-2-PANICINF
: Unit [dec], PI [hex] [hex] [hex] [hex] [hex] [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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%TR-2-PANICTYPE
: Unit [dec], [chars] error
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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%TR-3-RESETFAIL
: Unit [dec], reset failed, error code [hex].
Explanation An internal software error occurred.
Recommended Action If the message recurs, copy the message exactly as it appears on the console or
in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%TR-3-SETBRIDGEFAIL
: Unit [dec], set bridge failed (code [hex]).
Explanation A hardware error has occurred. The source routing accelerator (SRA) chip on the Token
Ring card 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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%TR-3-SETFUNFAIL
: Unit [dec], set functional address failed (code [hex]).
Explanation An internal software error has occurred.
Recommended Action If the message recurs, copy the message exactly as it appears on the console or
in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%TR-3-SETGRPFAIL
: Unit [dec], set group address failed (code [hex]).
Explanation An internal software error has occurred.
Recommended Action If the message recurs, copy the message exactly as it appears on the console or
in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%TR-6-STATE
: [chars]: Ring Status: [chars]
Explanation This message is displayed when the chipset reports a status change for the Token Ring.
This information also is used to determine automatically whether the interface is still available for
propagating network traffic.
Recommended Action No action is required.
TRACKING Messages
The following are Enhanced Object Tracking messages.
Error Message
%TRACKING-5-STATE
: [dec] [chars] [chars] [chars] [chars]->[chars]
Explanation Tracked object changed state.
Recommended Action No action is required.
TRANGE Messages
The following are the TRANGE messages.
Error Message
%TRANGE-2-NOMEMORY
: Alloc fail for time-range config buffer. Disabling distributed
mode on lc
Explanation Unable to malloc a buffer to send time-range configuration down to line cards.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in non-zipped, plain-text (.txt) format: the output of the show chunks
command and your pertinent troubleshooting logs.
Error Message
%TRANGE-2-WRONGREQUEST
: Invalid request to allocate chunk of size [dec]
Explanation A request has been made to allocate a time-range chunk greater than the maximum
allowed size (TRANGE_LARGE_CHUNK_SZ).
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center 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
%TRANGE-2-WRONGSIZE
: Incorrect length trange ipc xdr of len=[dec] received
Explanation The RP sent a time-range configuration message of the wrong size.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center 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.
TRANSCIEVER Messages
The following are the Transciever subsystem messages.
Error Message
%TRANSCEIVER-3-INTERNAL_ERROR
: [chars]
Explanation The transceiver subsystem encountered an internal software error. The error message
contains text which can be used to help identify the nature of the problem.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
TRUNK Messages
The following are the E1/T1 trunk card error messages.
Error Message
%TRUNK-3-BADCARDTYPE
: Unknown type [hex] in shelf [dec] slot [dec]
Explanation The card in the specified slot and shelf has not been recognized as either a T1 or E1
interface. This indicates a hardware or software failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TRUNK-3-BADFW
: Invalid framer firmware code file.
Explanation The software has detected an invalid framer firmware image that cannot be downloaded.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TRUNK-3-BADMSG
: Bad doorbell message type to framer: [dec]
Explanation An invalid or undefined message type has been sent to the framer 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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TRUNK-3-BADSLOT
: Invalid value ([dec]) for shelf [dec]; exceeds [dec]
Explanation An internal software error has occurred. An attempt has ben made to reference a shelf
number larger than the installed maximum.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TRUNK-3-HBEAT
: No longer receiving heartbeats from framer CPU.
Explanation Communication from the framer processor to the trunk card processor has stopped. The
framer processor is no longer passing status to the trunk card processor nor accepting messages from
the trunk card 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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TRUNK-3-INITFAIL
: Trunk card initialization failed due to: [chars]
Explanation Trunk card initialization has failed for the reason that is reported within the error
message string.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TRUNK-3-NOMEM
: Insufficient memory for slot: [dec] in shelf: [dec]
Explanation Router memory was exhausted while allocating memory for use with the specified slot
and shelf.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant,
upgrade to a larger memory configuration.
Error Message
%TRUNK-3-NOMSGS
: Cannot send message to framer; no more messages available
Explanation The memory buffer for message passing between the trunk card and framer processors
has been exhausted. Either the messages are not being picked up or are being generated too quickly.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
TRUNK_CLOCK Messages
The following are the clocking error messages.
Error Message
%TRUNK_CLOCK-6-BAD_CLOCKS
: There are no good clocks in the system. Remain in
HOLDOVER mode
Explanation The clock selection algorithm has failed to select any clock as the TDM primary clock.
Recommended Action No action is required.
Error Message
%TRUNK_CLOCK-6-EXTERNAL
: Switching to the user configured external clock on
motherboard
Explanation The TDM primary clock is switching from the default clock to the user-configured
external clock in motherboard.
Recommended Action No action is required.
Error Message
%TRUNK_CLOCK-6-FREERUN
: Switching to the user configured freerunning clock on
motherboard
Explanation The TDM primary clock is switching from the default clock to the user-configured
free-running clock in the motherboard.
Recommended Action No action is required.
Error Message
%TRUNK_CLOCK-3-NOMEMORY
: Failed to allocate memory for the clocks
Explanation The clock switching software has failed to allocate memory while adding a clock.
Recommended Action No action is required.
Error Message
%TRUNK_CLOCK-6-SWITCH
: Switching to the clock on slot [dec] port [dec] priority
[dec] as the current primary has gone bad
Explanation he TDM primary clock has switched to a backup clock that is coming in through the
specified trunk because the current primary clock has failed.
Recommended Action No action is required.
Error Message
%TRUNK_CLOCK-6-TRUNK
: Switching to the user configured trunk clock on slot [dec]
port [dec] priority [dec]
Explanation The TDM primary clock is switching from the default clock to the user configured trunk
clock.
Recommended Action No action is required.
Error Message
%TRUNK_DFC-3-CONTRCREATE
: Failed to create controller for [dec]/[dec]
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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TRUNK_DFC-3-DSX3CONTEXT
: Failed to create context for dsx3 controller in
[dec]/[dec]
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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TRUNK_DFC-3-SDRAM_TEST_FAILED
: Trunk DFC in slot [dec]: SDRAM failed
[[hex]..[hex]]
Explanation The trunk DFC SDRAM test has failed, indicating a failed memory location.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%TRUNK_DFC-3-TRUNK_FIRMWARE_DOWNLOAD_FAILED
: Could not download trunk firmware in
slot [dec]
Explanation The trunk firmware cannot be downloaded.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%TRUNK_DFC-3-TRUNK_FIRMWARE_NOT_READY
: Trunk DFC firmware in slot [dec] is not
ready
Explanation The trunk DFC firmware has failed to start.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%TRUNK_DFC-3-TRUNK_RESET_FAILED
: Reset failed for Trunk DFC ROM in slot [dec]
Explanation The trunk DFC cannot be taken out of reset 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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%TRUNK_DFC-3-TRUNK_ROM_FAILED
: Trunk DFC ROM in slot [dec] failed: [chars]
Explanation The trunk DFC ROM has failed to boot properly.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%TRUNK_DFC-3-TRUNK_SLOT_CREATE
: Failed to create trunk slot instance for slot
[dec]
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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
TTY Messages
The following are the TTY-retaled messages
Error Message
%TTY-3-AUTOCONFIG
: TTY[t-line]: Modem auto-configuration failed
Explanation Modem auto-configuration has failed either because the modem rejected the
configuration string or because of a timeout. Apply the configuration string mannually.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TTY-3-NOPROCESS
: Cannot create [chars] process
Explanation Failed to create the process.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
TTYDRIVER Messages
The following are the router shelf asynchronous driver error messages.
Error Message
%TTYDRIVER-3-BADENCAP
: Unknown encapsulation on interface [chars]
Explanation A software error has occurred resulting in an unknown encapsulation type on the
interface specified by the error 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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TTYDRIVER-3-NOPARTS
: No particles available to set up for output on tty [chars]
Explanation A software error has occurred resulting in an unexpected exhaustion of the pool of data
buffers used by the modem drivers.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TTYDRIVER-3-NOTXPART
: Non-zero outcount but no transmit particle on tty [chars]
Explanation A software error has occurred and left a software structure in an unexpected state.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TTYDRIVER-3-RTSLOW
: RTS is incorrectly deasserted for tty [chars]; reasserting
now
Explanation A software error has occurred resulting in an invalid state for the RTS modem 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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TTYDRIVER-3-UNKNOWN_PORT_ARCH_TYPE
: Unknown port type ([dec])
Explanation A software error has occurred due to an unrecognised port type.
Explanation Copy the message exactly as it appears on the console or in the system log. Research
and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac.
With some messages, these tools and utilities will supply clarifying information. Search for resolved
software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
TUNSS Messages
The following are the tunnel security messages.
Error Message
%TUNSS-3-PROTECTION_PROCESS_FAIL
: Failed to create tunnel security process
Explanation We failed to start a processes necessary to do tunnel protection.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
TXCONN Messages
The following are Cisco Transaction Connection (CTRC) error messages.
Error Message
%TXCONN-5-CONNIDLETIMEOUT
: Client [IP_address] connected to server [chars] has
timed out after [time-stamp].
Explanation The client was idle for too long, and the idle timeout configured
for the txconn server expired.
Recommended Action This is an informational message only.
Error Message
%TXCONN-3-INVALIDTRANS
: Bad Transaction ID, flushing out request for client
[IP_address] connected server [chars], killing connection.
Explanation An invalid input stream has been detected and ignored.
Recommended Action This is an informational message only.
Error Message
%TXCONN-3-NOSESSION
: Out of resource, cannot create transaction for client
[IP_address] connected server [chars], killing connection.
Explanation The router is out of memory.
Recommended Action This is an informational message only.
Error Message
%TXCONN-5-SECFAIL
: APPC security failed, client [IP_address] using userid
'[chars]' for server [chars]
Explanation The user ID or password issued by the client was rejected by the remote database server.
Recommended Action This is an informational message only.
Error Message
%TXCONN-5-TARGETDOWN
: CICS server [chars] has become unavailable. Recovery is in
progress.
Explanation A CICS server for a configured destination has become unavailable. All client
connections to this server will be rejected until it becomes available again.
Recommended Action This is an informational message only.
Error Message
%TXCONN-5-TARGETUP
: CICS server [chars] is now available.
Explanation A CICS server that was previously unavailable has become available. All client
connections to this server will now be accepted.
Recommended Action This is an informational message only.
Error Message
%TXCONN-5-TRANSIDLETIMEOUT
: Transaction [hex] of Client [IP_address] connected to
server [chars] has timed out after [time-stamp].
Explanation The transaction was idle for too long, and the idle timeout configured for the CTRC
server has expired.
Recommended Action This is an informational message only.
Error Message
%TXCONN-3-TXEXCEPTION
: Exception [chars] from transaction [chars] to [chars] from
client [IP_address]
Explanation An unexpected transaction 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. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%TXCONN-3-UNEXPECTEDREQ
: Unexpected client data, flushing out the request for
client [IP_address] connected server [chars].
Explanation An invalid input stream has been detected and ignored.
Recommended Action This is an informational message only.
UBR10K Messages
The following are Schooner RP Subsystem messages.
Error Message
%UBR10K-3-CFRNOINDEX
: Classifier control block index allocation failure
Explanation The system has run out of PXF resources to set up any new packet classifier state.
Recommended Action This would typically happen only on a very overloaded system. Remove CMs
from this system.
Error Message
%UBR10K-3-CFRNOMACRWIP
: Invalid IP address mapping for of CPE [enet] belonging to
CM [enet]
Explanation Due to an inconsistency between the PXF FIB and the RP CPE data structures, the
packet classification state cannot be setup correctly.
Recommended Action Try to force the CPE to get an IP address 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
%UBR10K-0-CLI_CMD
: CMTS([dec]/[dec]), [chars] failed
Explanation Most likely a software 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
%UBR10K-0-CLI_CONFIG
: CMTS([dec]/[dec]/[dec]), schrp_cli_cmd failed in [chars]
Explanation Most likely a software 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
%UBR10K-2-CLI_UNSUPPORTED_CMD
: cable modem <ipaddr/macaddr> cmd not supported in
Schooner
Explanation Currently unsupported command.
Recommended Action No action is required.
Error Message
%UBR10K-6-CM_INCONSISTENCY
: CM state inconsistency [enet](msgp [enet]), sid [dec]
([dec]), mac state [dec], hwidb [chars]
Explanation Received INIT_CM for an online CM.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR10K-6-COMPAT_IGNORED
: OIR compatibility is disabled because [chars]
Explanation OIR compatibility is disabled because of a conflict with another feature.
Recommended Action Disable OIR compatability or the conflicting feature.
Error Message
%UBR10K-6-COMPAT_INC_CARD
: [chars] in slot [dec]/[dec] is not compatible with the
saved configuration. [chars] configuration has been discarded.
Explanation The saved configuration could not be used on the current card.
Recommended Action Manually reconfigure the line card interfaces.
Error Message
%UBR10K-6-COMPAT_NO_CFG
: OIR compatibility does not support the [chars] in slot
[dec]/[dec]. [chars]
Explanation A line card that is supported by the OIR compatibility feature is not supported in the
specified slot or subslot.
Recommended Action This is most likely a software problem and should be reported to development.
OIR compatibility for the given slot or subslot should be disabled until the problem is resolved.
Error Message
%UBR10K-6-COMPAT_UNS_CARD
: Did not find a saved configuration for the [chars] in
slot [dec]/[dec].
Explanation There is no storage area allocated for saving the configuration of the card.
Recommended Action Manually reconfigure the line card interfaces.
Error Message
%UBR10K-3-FPSUBINIT
: Unable to create subinterface [chars] for hw interface
[chars] in the fast path
Explanation The system was unable to create the cable subinterface data structures in the fast path.
Recommended Action Gather information about running configuration and amount of memory in the
system. Copy the message exactly as it appears on the console or in the system log. Research and
attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR10K-1-INITFAIL
: Schooner subsystem init fails:([chars])
Explanation Schooner System initialization failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR10K-1-INVALID_DIVHDR
: Invalid diversion hdr on pkt: cause [dec], channel
[hex], length [dec]
Explanation RP received a corrupt diverted packet from the cable line card.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR10K-1-INVALIDPRIMSID
: Dropping punted pkt from sid [dec] prim sid [dec] src
[enet] hw [chars]
Explanation RP received a diverted packet with invalid primary sid from the cable line card.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR10K-1-INVALIDSID
: Dropping punted pkt from sid [dec] src [enet] hw [chars]
Explanation RP received a corrupt diverted packet from the cable line card.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR10K-1-IPCFAIL
: Schooner subsystem IPC init fails for interface [chars] on
[chars]: in [chars]()
Explanation Schooner System IPC initialization failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR10K-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 RP. This type of incompatibility could happen if the RP and
Schooner line card are using different IOS versions due to an RP oir event.
Recommended Action A microcode reload will solve the problem.
Error Message
%UBR10K-1-POWCYCLE
: Power cycle slot [dec]/[dec]
Explanation Recover from MC16S HW initialization failure.
Recommended Action If this happens to non-MC16S CLC, copy the message exactly as it appears on
the console or in the system log. Research and attempt to resolve the issue using the tools and
utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR10K-3-QALLOCFAIL
: Failure to allocate QoS queue for service flow [int], CM
[enet]
Explanation The system has run out of PXF queues.
Recommended Action This would typically happen only on a very overloaded system. The only
solution is to remove CMs from this system.
Error Message
%UBR10K-3-QALLOCFAIL_INFO
: Failure to allocate QoS queue: [chars]
Explanation The system has run out of PXF queues, providing additional debugging information.
Recommended Action This would typically happen only on a very overloaded system. The only
solution is to remove CMs from this system.
Error Message
%UBR10K-3-QUEUEFULL
: Unable to enqueue since the queue is full
Explanation The system wants to enqueue a message, but is unsuccessful.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR10K-1-SNMP_GETINDEX_FAIL
: Cannot get SNMP physical Index for [chars]
Explanation Schooner System initialization failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR10K-1-SNMP_SENDCMD_FAIL
: Error sending command type [dec], which [dec]
Explanation Schooner System initialization failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR10K-1-SNMP_SENDINFO_FAIL
: Error sending SNMP info to [chars]
Explanation Schooner System initialization failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR10K-0-SNMP_SET_IPC
: Schooner SNMP SET([dec]/[dec]), [chars] failed
Explanation SNMP SET failed due to either IPC failure or line card SET 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
%UBR10K-0-STACK_PROT_UNSUPPORTED
: test cable stack-prot is not supported on card
Explanation Currently unsupported command.
Recommended Action No action is required.
Error Message
%UBR10K-6-STATESYNC
: Redundancy state synchronization failure slot [dec]/[dec] -
([chars])
Explanation A failure occurred in trying to synchronize GE state information.
Recommended Action If this message recurs, copy the message exactly as it appears on the console
or in the system log. Research and attempt to resolve the issue using the tools and utilities provided
at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR10K-1-UNKEVT
: Schooner subsystem unknown event:([dec]) in [chars], for
interface [chars]
Explanation Schooner System receive unknown event type.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR10K-1-UNKREQ
: Schooner subsystem unknown request:([dec])
Explanation Schooner System received unknown request type.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR10K-1-UNKVECT
: Schooner subsystem unknown vector:([dec])
Explanation Schooner System received unknown vector.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR10K-3-VOLTABNORMAL
: The PEM [dec] voltage value [dec] is abnormal
Explanation The chassis voltage value is abnormal.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
UBR10K_REDUNDANCY Messages
The following are Schooner RP Redundancy messages.
Error Message
%UBR10K_REDUNDANCY-3-CHKPT_INTERNAL
: Internal PRE checkpointing error [[chars]]
Explanation An internal error occurred within the PRE checkpointing code.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR10K_REDUNDANCY-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 RP. This type of incompatibility could happen if the RP and
Schooner line card are using different IOS versions due to an RP oir event.
Recommended Action A microcode reload will solve the problem.
Error Message
%UBR10K_REDUNDANCY-4-RP_HA_STDBY_INCONSISTENT
: Standby PRE is in inconsistent
state. [chars] [chars].
Explanation An internal error has occurred within the PRE configuration or data synchronization
code.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
UBR10K_TCC Messages
The following are Timing Communication Control Card support messages.
Error Message
%UBR10KTCC-2-ACTIVE_TCC
: TCCplus card [dec]/[dec] is active with [chars] as clock
reference
Explanation The TCCplus Card became active.
Recommended Action Informational message only. No action is required.
Error Message
%UBR10KTCC-1-BADCLK
: Cable Line Card [dec]/[dec] reports Bad Clock Status for
TCCplus card in [dec]/1
Explanation Error in the clock received on the BackPlane.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR10KTCC-1-BADTCC
: TCCplus card in [dec]/1 put under maintenance due to: [chars]
Explanation There could be some failure in the MTSS of the TCCplus card.
Recommended Action Replace TCCplus card.
Error Message
%UBR10KTCC-1-BLKCMD
: Schooner System IPC failure for TCCplus card
Explanation C10k_card_send_blocking_cmd 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
%UBR10KTCC-4-CHG_CLK_REF
: Clock reference source changed to [chars], TCCplus card
[dec]/[dec]
Explanation Two reasons for the change in clock reference.
1) LOS of previous source reference.
2) Primary / Secondary T1 reference of active card is now available.
Recommended Action Check reference source.
Error Message
%UBR10KTCC-3-EVNTLEN
: TCCplus card Event internal error, [chars] [dec] [dec]
Explanation Internal Event error in TCCplus 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
%UBR10KTCC-1-LCLOSC
: Cable Line Card [dec]/[dec] using the local oscillator
Explanation Error in the clock received on the BackPlane.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR10KTCC-2-LOS
: Loss of signal with clock reference [chars] in TCCplus card
[dec]/[dec]
Explanation The clock reference was lost.
Recommended Action Check reference source.
Error Message
%UBR10KTCC-1-NOTCC
: No working TCCplus card available in the system
Explanation There is no TCCplus card or there could be some failure in the MTSS of the TCCplus
card and it is put under maintanence.
Recommended Action Replace TCCplus card.
Error Message
%UBR10KTCC-1-SWTCHERR
: Unable to switch TCCplus card configuration. Other card is
not present or in Maintenance
Explanation Other card is not present or in Maintenance state.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
UBR7200IPC Messages
The following are UBR7200 MCU IPC messages.
Error Message
%UBR7200IPC-2-BADINTERFACE
: Out of range Card interface, [dec] on slot [dec]
Explanation The software has specified an out-of-range 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.
Error Message
%UBR7200IPC-2-BADRSRCNUM
: Invalid resource number from PXF ([dec]). (PLEASE REPORT
THIS!)
Explanation The PXF hardware diversion path specified a bad resource 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
%UBR7200IPC-2-BADSLOT
: Out of range card slot index[dec]
Explanation The software specified an out-of-range card slot index.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR7200IPC-2-BADSLOTSUBSLOT
: Out of range card slot/subslot pair[dec]/[dec]
Explanation The software specified an out-of-range card slot or subslot pair.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR7200IPC-2-CARDRECUR
: Recursive loop while getting the daughtercard info for
card type [dec]
Explanation While getting the daughter card info for the chassismib, the platform snmp code goes
into an infinite loop.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR7200IPC-2-CARDTYPEERROR
: card in slot [[dec]/[dec]] is of incorrect type [hex]
Explanation The specified card is incompatible with the 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
%UBR7200IPC-3-CLI_CMD
: [dec]/[dec]: CLI cmd failed in function [chars]
Explanation Most likely a software 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
%UBR7200IPC-0-CLI_CONFIG
: CMTS([dec]/[dec]/[dec]), schrp_cli_cmd failed in
[chars]
Explanation Most likely a software 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
%UBR7200IPC-3-CLI_IPC_MALLOC
: Memory allocation request failed in [chars]
Explanation Could not allocate memory for distributed CLI operation.
Recommended Action Enter the show memory command to analyze memory usage.
Error Message
%UBR7200IPC-2-CLI_UNSUPPORTED_CMD
: cable modem <ipaddr/macaddr> cmd not supported
on MC28U
Explanation Currently unsupported command.
Recommended Action No action is required.
Error Message
%UBR7200IPC-6-CM_INCONSISTENCY
: CM state inconsistency [enet](msgp [enet]), sid
[dec] ([dec]), mac state [dec], hwidb [chars]
Explanation The line card and the route processor (RP) card have different CM states. This error
might occur if IPC is lost during a switchover.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR7200IPC-3-DEACTIVATED
: card in slot [[dec]/[dec]] disabled.
Explanation The card is being deactivated.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR7200IPC-1-DISCOVER_ENET
: Failed to init Ethernet device [dec]
Explanation The software could not initialize.
Recommended Action Power down, reseat the interface card, and reboot. 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
%UBR7200IPC-1-DISCOVER_SAR
: Failed to init SAR device [dec]
Explanation The software could not initialize.
Recommended Action Power down, reseat the interface card, and reboot. 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
%UBR7200IPC-3-INITFAIL
: [chars] - initialization of interface failed
Explanation Unavailable.
Recommended Action Unavailable.
Error Message
%UBR7200IPC-3-IPCERR
: IPC message error ([dec])
Explanation Error from IOS IPC layer on line card Port API port.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR7200IPC-3-IPCFAIL
: [chars]: IPC command [chars] to interface failed in [chars]
Explanation System IPC initialization failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR7200IPC-3-IPCOPENFAIL
: slot [int]: could not open IPC port for port id [hex]
Explanation IPC port open to mcu card failed — indicates that the card is down or there is a transient
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
%UBR7200IPC-3-LC_DEFOBJ
: Default linecard object invoked for type ([dec])
Explanation The default card IPC API object was invoked since there was no registered handler for
that object.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR7200IPC-3-LC_OBJERR
: [chars]
Explanation A card IPC API object 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
%UBR7200IPC-4-MSGVERSION
: Incompatible message version with slot [dec]
Explanation There is incompatibility between the message version being sent by the line card and
the message version used by the RP/NPE. This type of incompatibility could happen if the RP/NPE
and line card are using different IOS versions due to an RP/NPE oir event.
Recommended Action A microcode reload will solve the problem.
Error Message
%UBR7200IPC-3-NOACK
: Access to [chars] temperature sensor failed
Explanation Accesses to chassis temperature sensor has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR7200IPC-4-PCIVALID
: PCI activation failed, slot [dec], [hex]
Error Message
%UBR7200IPC-3-PLUGIN_UNKNOWN
: Unknown card type [hex] in slot [dec]/[dec].
Explanation The card in the specified slot is not a known type.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR7200IPC-3-QUEUEFULL
: Unable to enqueue since the queue is full
Explanation The system wants to enqueue a message, but is unsuccessful.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR7200IPC-1-SNMP_GETINDEX_FAIL
: Cannot get SNMP physical Index for [chars]
Explanation LC System initialization failure.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR7200IPC-4-TEST
: Test command no. [dec] executed by user
Explanation Unavailable.
Recommended Action Unavailable.
Error Message
%UBR7200IPC-3-UNEXP_INTR
: Interrupt [chars] not expected, masking off
Explanation An interrupt of a certain type was signalled, but the interrupt handler for this type of
interrupt is not yet installed.
Recommended Action This problem should be self-correcting but indicates either a hardware or a
software defect. If it is a hardware defect, further problems are to be expected. If it is a software
problem, certain types of error and alarm conditions may be left undetected. Copy the message
exactly as it appears on the console or in the system log. Research and attempt to resolve the issue
using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBR7200IPC-1-UNKEVT
: Subsystem unknown event:([dec]) in [chars], for interface
[chars]
Explanation Subsystem received unknown event type.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
UBRIFCON Messages
The following are Schooner RP subsystem messages.
Error Message
%UBRIFCON-3-NOPROC
: Unable to create the if-console background process
Explanation The system wants to create a background process to handle if-console data from the line
cards, but is unsuccessful.
Recommended Action Gather information about the number of processes running and amount of
memory in the system. Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBRIFCON-3-NOQUEUE
: Unable to create the if-console background queue
Explanation The system wants to create a background process queue to handle if-console data from
the line cards, but is unsuccessful.
Recommended Action Gather information about the number of processes running and amount of
memory in the system. Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
UBRLCCOREDUMP Messages
The following are UBR Line Card Coredump subsystem messages.
Error Message
%UBRLCCOREDUMP-3-BADCLOSE
: Can't close slave core socket for slot [dec]/[dec]
Explanation The system just finished dumping a core file from a line card. It tried to close this file
on the remote system and failed.
Recommended Action Debug network connections and user privileges.
Error Message
%UBRLCCOREDUMP-3-BADOPEN
: Can't open slave core socket for slot [dec]/[dec]
Explanation The system wants to dump a core file to a remote sytem, but it is unable to open the
remote file.
Recommended Action Check to ensure the remote system is accessable and the protocol is set up
correctly.
Error Message
%UBRLCCOREDUMP-3-BADSLOTNUMBER
: Refusing dump because card slot number is out of
bounds for card [dec]/[dec].
Explanation The NPE/PRE card has refused this dump because slot number is out of bounds.
Recommended Action Check IPC debug message for malformed packet.
Error Message
%UBRLCCOREDUMP-3-BADWRITE
: Can't write [chars] to slave core socket for slot
[dec]/[dec]
Explanation The system is trying to write a core dump file to a remote sytem. The file was opened,
and an error occurred during a write to the file.
Recommended Action Check network and disk space available.
Error Message
%UBRLCCOREDUMP-2-EOM
: Cannot allocation memory for [chars]
Explanation The system cannot allocate memory for the coredump subsystem.
Recommended Action Add more memory.
Error Message
%UBRLCCOREDUMP-3-ILLMSG
: Coredump message received from slot [dec]/[dec] (not in
dump state)
Explanation A core dump message from a line card that the should not be dumping core arrived at
the PRE.
Recommended Action Gather information about the state of line cards. Copy the message exactly as
it appears on the console or in the system log. Research and attempt to resolve the issue using the
tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBRLCCOREDUMP-3-ILLNVGEN
: Illegal call to cr10k_rp_lc_cfg_coredump_nvgen
Explanation The NVGEN routine was called, but nvgen was not set.
Recommended Action Gather information about the processes running on this platform and the
traceback. Copy the message exactly as it appears on the console or in the system log. Research and
attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBRLCCOREDUMP-3-ILLTD
: Testdump only valid on line cards (not allowed on PREs)
Explanation You cannot run a line card coredump test for an PRE.
Recommended Action Do not run this test.
Error Message
%UBRLCCOREDUMP-6-LERP
: Cannot configure linecard exceptions for [chars] PRE
Explanation The exception line card commands can only be used to configure exceptions on a line
card. PRE are not allowed.
Recommended Action Enter the exception command without line card to configure PRE core dumps.
Error Message
%UBRLCCOREDUMP-3-NOMSG
: No message on queue
Explanation A core dump message from a line card that the should not be dumping core arrived at
the PRE.
Recommended Action Gather information about the state of line cards . Copy the message exactly as
it appears on the console or in the system log. Research and attempt to resolve the issue using the
tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBRLCCOREDUMP-3-NOPROC
: Unable to create data handler process
Explanation The system wants to write a core dump file to a remote system but it is unable to start a
process to dump the file.
Recommended Action Gather information about the number of processes running and amount of
memory in the system. Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBRLCCOREDUMP-3-NOQUEUE
: Cannot create queue to receive dump packets for slot
[dec]/[dec]
Explanation The system is trying to write a core dump file to a remote sytem. It could not create a
queue to hold dump data coming from the line cards.
Recommended Action Add memory.
Error Message
%UBRLCCOREDUMP-3-REFUSAL
: Refusing [chars] dump for card [dec]/[dec].
Explanation The PRE/NPE card has refused this dump because CLI is not configured for it, or file
access violation on the tftp server.
Recommended Action Check exception-slave CLI on NPE.
Error Message
%UBRLCCOREDUMP-4-TIMEOUT
: [chars] (major [dec], minor [dec])
Explanation The system is trying to write a core dump file, but the PRE timed out waiting for data
from the line card.
Recommended Action Gather information about the line card. Copy the message exactly as it appears
on the console or in the system log. Research and attempt to resolve the issue using the tools and
utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBRLCCOREDUMP-3-TOOLONGFILENAME
: Filename for coredump file is too long for slot
[dec]/[dec]
Explanation Filename is too long for core dump file.
Recommended Action Reduce the length of coredump filename string via CLI.
UBRLCDUMP Messages
The following are UBR CLC crash messages.
Error Message
%UBRLCDUMP-3-CRASHINFO_DUMP
: System Crashed, Trying to send Crashinfo first to
remote server....
Explanation The system has crashed because of an exception. A crashinfo is being generated.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBRLCDUMP-3-FAILEDMEMALLOC
: Unable to allocate memory to read crashinfo from
flash.
Explanation Failed to open the most recent crashinfo file in flash.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBRLCDUMP-3-NOPROC
: Unable to create core dump process.
Explanation Could not start the exception dump process.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBRLCDUMP-3-OPENFLASHFILE
: Unable to open flash crashinfo file on bootflash to
READ: [chars]
Explanation Failed to open the most recent crashinfo file in flash.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBRLCDUMP-3-READFLASHFILE
: Unable to read flash crashinfo file.
Explanation Failed to read the most recent crashinfo file in flash.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UBRLCDUMP-3-SIZEFLASHFILE
: Unable to get size of flash crashinfo file.
Explanation Failed to get size of the most recent crashinfo file in flash.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
UBRLCIFCON Messages
The following are CLC IF console messages.
Error Message
%UBRLCIFCON-3-NOPROC
: Unable to create if-console process.
Explanation Could not start the if-console process.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
UBRSNMP Messages
The following are UBR7200 MCU IPC messages.
Error Message
%UBRSNMP-0-SNMP_SET_IPC
: Schooner SNMP SET([dec]/[dec]), [chars] failed
Explanation SNMP SET failed due to either IPC failure or line card SET 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.
UDLD-SP Messages
The following are UDLD SP messages.
Error Message
%UDLD-3-UDLD_INTERNAL_ERROR
: UDLD internal error: [chars]
Explanation A software sanity check has failed in the course of UDLD processing.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%UDLD-3-UDLD_INTERNAL_IF_ERROR
: UDLD internal error, interface [chars]: [chars]
Explanation A software sanity check has failed in the course of UDLD processing.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Search for resolved software issues using the Bug Toolkit at
http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance,
open a case with the Technical Assistance Center via the Internet at
http://tools.cisco.com/ServiceRequestTool/create/, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%UDLD-SP-4-UDLD_PORT_DISABLED
: UDLD disabled interface [chars], [chars] detected
Explanation An interface has been disabled because the UDLD detected the cause indicated on the
interface. Cause is likely due to bad interface hardware or cable misconfiguration.
Recommended Action Investigate the cable 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. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
UNIXLC_SPA Messages
The following are the UNIXLC_SPA messages.
Error Message
%UNIXLC_SPA-3-C2W_MAIN_INIT_FAIL
: Failed to initialize SPA main c2w bus for
subslot [dec] (status = [dec])
Explanation The SPA driver is not able to initialize SPA main c2w. This indicates a hardware error.
Recommended Action No action is required.
Error Message
%UNIXLC_SPA-3-CMDNOINT
: HWIDB Null for command [dec], port [hex]
Explanation The Route Processor passed down a port number that is unknown on the
carrier 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. 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
%UNIXLC_SPA-3-DEVICE_ERROR
: subSlot [dec], spatype [hex]. Device error: [chars]
Explanation An error related to a device on the SPA is detected.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center 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
%UNIXLC_SPA-3-EFC_CHAN_ERR
: EFC error - interface [chars], vc [dec], anyphy [dec],
err_code [dec] : [chars]
Explanation Failed to configure efc channel/parameters.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UNIXLC_SPA-3-EFC_FC_MAP_FAIL
: Failed to update EFC flow control identifier for
interface [chars] (status = [dec])
Explanation The SPA driver is not able to update the datapath EFC flow control identifier for the
interface specified in the message. This indicates a hardware error.
Recommended Action No action is required.
Error Message
%UNIXLC_SPA-3-EFC_PROV_FAIL
: Failed to provision EFC for interface [chars] (status
= [dec])
Explanation The SPA driver is not able to provision EFC for the interface specified in the message.
This indicates a hardware error.
Recommended Action No action is required.
Error Message
%UNIXLC_SPA-3-EFC_UNPROV_FAIL
: Failed to unprovision EFC for VC [chars] (status =
[dec])
Explanation The SPA driver is not able to unprovision EFC for the interface specified in the message.
This indicates a hardware error.
Recommended Action No action is required.
Error Message
%UNIXLC_SPA-3-FCI_NOT_SET
: Bay [dec] - FCI type not set
Explanation An FCI type of zero was detected
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UNIXLC_SPA-3-HWIDB_FAILURE
: Creation: port [dec] vc [dec]
Explanation Failed to create a HWIDB.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center 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
%UNIXLC_SPA-3-INVALID_ANYPHY
: Bay [dec] - Invalid anyphy number [int] for vc [dec]
Explanation Interface has invalid anyphy mumber
Recommended Action Seach 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl or contact your Cisco technical
support representative. Be sure to provide the the information you have gathered and a 'show
tech-support' to your support representative, or attach it to your case in non-zipped, plain text format
(.txt).
Error Message
%UNIXLC_SPA-3-INVALID_IF
: Attempted to access HWIDB for port [int] on slot [dec]
subSlot [dec]
Explanation The IOU attempted to access the HWIDB associated with
a non-existent port.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UNIXLC_SPA-3-ISR_RC_ERROR
: ISR return code out of range. rc=[dec]
Explanation The ISR error return code 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. 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
%UNIXLC_SPA-3-LINKREC_ERROR
: Link record error - Bay [dec] vc [dec], error code
[dec]
Explanation An error has been encountered while processing the link record 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
%UNIXLC_SPA-4-MAX_BANDWIDTH
: Total SPA bandwidth exceeds line card capacity of
[int] Mbps
Explanation The total bandwidth of SPAs exceeds the rated capacity of this line card.
Recommended Action Refer to the line card guidelines for the maximum allowed aggregated SPA
bandwidth for the line card.
Error Message
%UNIXLC_SPA-4-MAX_BANDWIDTH_NS
: Total SPA bandwidth exceeds line card capacity,
full utilization of installed SPA interfaces is not supported
Explanation The total bandwidth of SPAs exceeds the rated capacity of this line card.
Recommended Action Refer to the line card guidelines for the maximum allowed aggregated SPA
bandwidth for the line card
Error Message
%UNIXLC_SPA-3-MESSAGE_ERROR
: Bay [dec]: [chars]
Explanation An unexpected 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
%UNIXLC_SPA-3-NETCLK_FAIL
: Failed to [chars] SPA reference clock on [chars]
Explanation The SPA driver is not able to correctly configure the SPA reference clock on the
specified interface. This indicates a hardware error.
Recommended Action No action is required.
Error Message
%UNIXLC_SPA-3-NULL_SPA_BAY
:
Explanation Pointer to object for bay [dec] 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. 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
%UNIXLC_SPA-3-POWER
: Bay [dec] 12V power is [chars]
Explanation This message indicates the SPA 12V power 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
%UNIXLC_SPA-3-SONET_CLOCK_FAILED
: SPA Sonet clock has failed (status = [hex])
Explanation The SPA SONET clock has failed. SPAs that rely on the SPA SONET clock for proper
operation, such as POS and ATM will be affected.
Recommended Action If the SPA Sonet clock does not recover, perform an OIR.
Error Message
%UNIXLC_SPA-3-SONET_CLOCK_RECOVERED
: SPA Sonet clock has recovered (status =
[hex])
Explanation SPA SONET clock has recovered.
Recommended Action No action is required.
Error Message
%UNIXLC_SPA-4-SPABUS
: Subslot [dec], [chars] SPA BUS access failed. timeout=[int]
err=[int] par=[int] err_c=[hex] addr=[hex] data =[hex]
Explanation The SPABUS has reported an error.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UNIXLC_SPA-4-SPABUS2
: Subslot [dec] SPA BUS access failed. No SPA present error
Explanation The SPABUS has reported an error.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UNIXLC_SPA-3-SPA_CTRL_EFC_CONFIG_FAILURE
: Subslot, spa controller EFC
configuration failure, error [dec]
Explanation Failed to configure SPA controller EFC.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UNIXLC_SPA-3-SPA_CTRL_INIT_FAILURE
: Subslot [dec], spa controller initialisation
failure, error [dec]
Explanation Failed to initialize SPA controller.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UNIXLC_SPA-3-SPI4_CONFIG_FAILURE
: Bay [dec], spi4 configuration failure, error
[dec]
Explanation Failed to configure the SPI4 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
%UNIXLC_SPA-3-SPI4_INIT_FAILURE
: Bay [dec] initialization failure
Explanation Failed to create the SPI4 subblock.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UNIXLC_SPA-3-UNIXIPCALLOCFAIL
: Failed to allocate Common IPC buffer [chars]
Explanation The carrier card failed to allocate a buffer for communication with 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.
UNIXRP_SPA
The following are the UNIXRP_SPA messages.
Error Message
%UNIXRP_SPA-6-CARDRELOAD
: Module [int] reload due to SPA insert in [int]/[int].
Explanation The card is reset, when inserting a SPA on this carrier card.
Recommended Action No action is required.
Error Message
%UNIXRP_SPA-3-CI_UPDATE_FAIL
: Failed to update connection identifier for
interface [chars]
Explanation The SPA driver is not able to update the datapath connection identifier for the interface
specified in the message. This indicates a software error.
Recommended Action No action is required.
Error Message
%UNIXRP_SPA-3-DPIDX_LKUP_FAIL
: Failed to retrieve datapath identifier for
interface [chars]
Explanation The SPA driver is not able to retrieve the datapath identifier for the interface specified
in the message. This indicates a software error.
Recommended Action No action is required.
Error Message
%UNIXRP_SPA-3-FLOWID_ALLOC_FAIL
: Failed to allocate a flow control identifier for
interface [chars]
Explanation The SPA driver is not able to allocate the datapath flow control identifier for the
interface specified in the message. This indicates a software error.
Recommended Action No action is required.
Error Message
%UNIXRP_SPA-3-FLOWID_RELEASE_FAIL
: Failed to release a flow control identifier for
interface [chars] (status = [dec])
Explanation The SPA driver is not able to release the datapath flow control identifier for the interface
specified in the message. This indicates a software error.
Recommended Action No action is required.
Error Message
%UNIXRP_SPA-3-HWIDB_FAILURE
: Creation: slot [dec] subSlot [dec] port [dec] vc
[dec]
Explanation Failed to create an interface HWIDB.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center 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
%UNIXRP_SPA-3-HWIDB_INIT_FAIL
: Failed to initialize data structure for SPA port
[dec]/[dec]/[dec]
Explanation A SPA driver was not able to properly initialize a data structure mentioned in the
message. This indicates a software error.
Recommended Action No action is required.
Error Message
%UNIXRP_SPA-3-INVALID_PORT_NUM
: slot=[dec] port=[dec], hwidbType=[hex],
max_port_num=[dec], LCtype=[hex]
Explanation The port number 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. 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
%UNIXRP_SPA-3-IPCALLOCFAIL
: Failed to allocate IPC buffer [chars]
Explanation The RP failed to allocate a buffer for communication with a SPA
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UNIXRP_SPA-3-MAX_SPA
: Power to IPSEC-SPA-2G in [chars] is denied because it has
exceeded the number allowed([dec])
Explanation The number of IPSEC-SPA-2G in a chassis is limited.This message is displayed when
the number of IPSEC-SPA-2G inthe chassis has exceeded this limit.
Recommended Action Use only the number of supported IPSEC-SPA-2G.
Error Message
%UNIXRP_SPA-3-NO_HOST_INFO
: slot [dec] subSlot [dec], spaType [hex]
Explanation Failed to get information about the host linecard.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center 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
%UNIXRP_SPA-3-NULL_DATA_STRUCTURE
: NULL
Explanation A SPA driver is not able to retrieve the data structure mentioned in the message. This
indicates a software error.
Recommended Action No action is required.
Error Message
%UNIXRP_SPA-3-NULL_HWIDB_SPA_BAY_PORT
: HWIDB not found: slot [dec], bay [dec],
port [dec]
Explanation A NULL HWIDB is 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. 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
%UNIXRP_SPA-3-NULL_SPA_BAY
:
Explanation The pointer to object for slot [dec], bay [dec] 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. 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
%UNIXRP_SPA-4-SPA_CMD_NO_RESP
: [chars]: No response for interface configuration
command [int]
Explanation A timeout has occurred while the RP was waiting for a response from line card. This
may happen due to line card CPU being too busy to respond to the command.
Recommended Action No action is required.
Error Message
%UNIXRP_SPA-3-SPA_NO_HOST_INFO
: slot [dec] subSlot [dec], PID [chars]
Explanation Failed to get information about the host line card.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information. 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
%UNIXRP_SPA-4-SPA_RESP_CMD_MISMATCH
: [chars]: Expecting response to interface
configuration command [int] but received response to command [int].
Explanation An internal synchronization error has occurred while configuring the interface. The
configuration may not have succeeded.
Recommended Action Check that the running configuration for the interface is correct. If this message
occurred on the standby, try reloading the standby to ensure that its configuration is in sync. If the
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
%UNIXRP_SPA-3-VC_PROV_FAIL
: Failed to provision interface [chars]
Explanation The SPA driver is not able to provision the interface specified in the message. Verify
that the SPA hardware is not provisioned above the supported limit. Otherwise, this indicates a
hardware error.
Recommended Action No action is required.
UNIX_SPA Messages
The following are the UNIX_SPA messages.
Error Message
%UNIX_SPA-3-CREATION_FAILURE
: slot=[dec] subslot=[dec], spa_type=[hex],
lc_type=[hex].
Explanation The system failed to create a SPA object.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information. 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
%UNIX_SPA-3-DIAG_CONFIG
: [chars] did not complete [dec]/[dec]
Explanation An error has occurred during the diagnostic test.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information. 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
%UNIX_SPA-3-INVALID_DATA_INSTANCE
: interface type [chars], slot [dec] port [dec]
vc [dec] : [chars]
Explanation Data required to support the interface is not available.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information. 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
%UNIX_SPA-3-INVALID_IF_INDEX
: index= [dec], spaType=[hex], slot [dec] subSlot
[dec] slotunit [dec] vc [dec]
Explanation Index for the interface is not valid.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center 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
%UNIX_SPA-3-INVALID_INDX_RANGE
: index1= [dec], index2= [dec], maxIndex= [dec]
Explanation An invalid index range has been 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. 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
%UNIX_SPA-3-INVALID_SLOT_NUM
: slot= [dec], max slot = [dec]
Explanation An invalid slot number has been 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. 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
%UNIX_SPA-3-INVALID_SLOTUNIT_NUM
: cardwide-port = [dec], max cardwide-port =
[dec]
Explanation An invalid cardwide-port number has been 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. 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
%UNIX_SPA-3-IPC_FAILURE
: IPC failure while [chars]
Explanation An error has occurred while preparing or sending an IPC 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
%UNIX_SPA-3-MEM_ALLOC_ERROR
: [chars]
Explanation Memory allocation error.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%UNIX_SPA-3-NULL_HWIDB
: [chars] called with NULL hwidb
Explanation A NULL HWIDB 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. 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
%UNIX_SPA-3-NULL_SPA_PTR
:
Explanation A pointer to a SPA object 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. 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
%UNIX_SPA-3-NULL_VFT
: [chars] virtual function table is not initialized.
spaType=[hex]
Explanation A required function table is not 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. 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
%UNIX_SPA-3-NULL_VFUNC
: [chars] vector is not initialized. spaType=[hex]
Explanation A required function vector is not 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. 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
%UNIX_SPA-3-POWER_CYCLE
: [chars] occurred on Shared Port Adapter [int]/[int]
Explanation An error has occurred which will cause the Shared Port Adapter to be power cycled.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information. 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
%UNIX_SPA-3-SENDCFGFAIL
: Failed to send configuration for [chars] to carrier-card
for subslot=[dec]/[dec]
Explanation Sending configuration has failed.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information. Attach the following
information to your case in non-zipped, plain-text (.txt) format: the output of the show logging and
show tech-support commands and your pertinent troubleshooting logs.
Error Message
%UNIX_SPA-3-SPA_CREATION_FAILURE
: slot=[dec] subslot=[dec], PID=[chars]
lc_type=[hex].
Explanation Failed to create a SPA object.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information. 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
%UNIX_SPA-3-SPA_SB_CREATION_FAILURE
: Failed to create SPA SB
Explanation Failed to create a SPA subblock.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center 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
%UNIX_SPA-3-UNSUPPORTED_DATA
: Data conversion error ([chars], [hex])
Explanation An internal software error has occurred when converting the data specified in the
message from one representation to another.
Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case with the Technical Assistance Center 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.
UPCONV Messages
The following are CMTS Upconverter error and log messages.
Error Message
%UPCONV-3-ALARM
: interface [chars] upconverter alarm [chars]
Explanation An alarm is reported by the upconverter.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative with the gathered information.
Error Message
%UPCONV-3-BAD
: interface [chars] Cannot initialize upconverter
Explanation Could not initialize the upconverter.
Recommended Action Copy the message exactly as it appears on the console or in the system log.
Research and attempt to resolve the issue using the tools and utilities provided at
http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying
information. Also perform a search of the Bug Toolkit
http://www.cisco.com/pcgi-bin/Support/Bugtool/home.pl. If you still require assistance, open a case
with the Technical Assistance Center via the Internet
http://tools.cisco.com/ServiceRequestTool/create, or contact your Cisco technical support
representative and provide the representative w