-
Cisco IOS XR System Error Message Reference Guide, Release 3.8.1
-
Preface
-
Overview Messages
-
Access Control List (ACL) Messages
-
Application Infrastructure Messages
-
Diagnostic Messages
-
Fabric Messages
-
Forwarding Messages
-
High Availability (HA) Messages
-
Installation Messages
-
Internet Protocol (IP) Messages
-
Layer 1 Messages
-
Layer 2 Messages
-
License Messages
-
Media Messages
-
Manageability (MGBL) Messages
-
Operating System (OS) Messages
-
Platform Messages
-
Quality of Service (QoS) Messages
-
Routing Messages
-
Security Messages
-
Services Messages
-
Simple Network Management Protocol (SNMP) Messages
-
System Database Messages
-
Index
-
FeedbackTable Of Contents
Platform Messages
This section contains all Platform related System Error Messages, such as shelf magr, chassis, env ctrl, and so forth.
ALPHA_DISPLAY Messages
Error Message%PLATFORM-ALPHA_DISPLAY-6-CHANGE Alpha display on node [chars] changed to [chars] in state [chars]
Explanation Message to indicate that alpha-display was updated with new string or state.
Recommended Action None.
ASM Messages
Error Message%PLATFORM-ASM-0-FAULT_RECOVERY_ERR The fault recovery procedure for the FromFab component of the fabric driver has failed. The root fault was: [chars]
Explanation When a hardware fault occurs and the device driver cannot correct it, the Platform Manager is required to reset the ASICs. This error indicates that the Platform Manager failed to reset the ASICs and the hardware on the PRP may not be in an operational state. This condition affects the functionality of the entire router. %s is the Interrupt Source.
Recommended Action If the system has not failed over automatically and a redundant route processor card has been configured: 1 - force a failover with the following command in admin mode: 'redundancy switchover' 2 - reload the route processor card that failed with the following command in admin mode: 'reload location RP/0/x/CPU0 ' where x is the slot of route processor that generated the error. If no redundant RP is configured you will need to reboot the router by issuing the reload command. Call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-ASM-0-SW_INIT_ERR A software error occurred in the FrFab driver component during initialization: [chars]
Explanation The fabricq_prp_driver process which controls the FromFab driver on the route processor has failed to initalize and cannot recover automatically. This is a software fault. The FromFab driver controls the hardware that receives data from the fabric. It runs in the fabricq_prp_driver process. An unrecoverable failure of the fabricq_prp_driver process may prevent this route processor card from communicating with other cards on the chassis. %s indicates the type failure
Recommended Action Restart the fabricq_prp_driver process with the following command: 'process restart fabricq_prp_driver' If the error message appears again, then: if a redundant route processor card has been configured: 1 - force a failover with the following command in admin mode: 'redundancy switchover' 2 - reload the route processor card that failed with the following command in admin mode: 'reload location RP/0/x/CPU0 ' where x is the slot of route processor that generated the error. if no redundant RP is configured you will need to reboot the router by issuing the reload command. If the error recurs call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-ASM-3-FQEMPTY_ERR Assembler detected that a free queue is empty
Explanation The assembler component has detected that one of the free queues used to buffer packets coming from the fabric into the route processor is empty.
Recommended Action The system will most likely recover from this error automatically. No intervention is required. If this error is reported frequently you may want to call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-ASM-4-BADDESC_ERR Assembler detected a bad descriptor.
Explanation Assembler detected a bad descriptor in the free queue. The system will usually recover from this error automatically. If the frequency of this alert increases noticeably it could indicate a hardware problem on the route processor card.
Recommended Action The system will normally recover from this error without intervention. If the frequency with which this error occurs increases substantially, call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
BCM_SWITCH Messages
Error Message%PLATFORM-BCM_SWITCH-2-LINK_SHUT_DOWN Spanning Tree Port [chars] state changed to ADMIN_DOWN
Explanation Spanning Tree Port's state change by manual intervention.
Recommended Action No action is required.
Error Message%PLATFORM-BCM_SWITCH-2-LINK_STATE_CHANGE Spanning Tree Port [chars] state changed to [chars]
Explanation Spanning Tree Port's state change indication.
Recommended Action No action is required.
Error Message%PLATFORM-BCM_SWITCH-2-PCI_ERR PCI fatal error seen on switch [dec] DMA channel [dec] type [chars]
Explanation The switch encountered a PCI error during a DMA transaction.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
CCTL_ENS Messages
Error Message%PLATFORM-CCTL_ENS-3-ERROR_EXIT Envmon process exiting because [chars], error code [chars]
Explanation The Chassis Control driver process exited due to the reason mentioned in the message.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. Execute 'show process envmon location ' to verify that the process is up and running. If it is still non-operational, try doing from the admin mode 'process restart envmon location '. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CCTL_ENS-7-OPERATION_FAIL Failed to [chars], error code [chars]
Explanation The particular operation mentioned in the message failed due to some reason. This is not a critical failure, the process can continue functioning as expected despite the failure.
Recommended Action Debug message only. No action is required.
CCTL Messages
Error Message%PLATFORM-CCTL-2-CHASSIS_SHUTDOWN_FAIL Unable to shutdown chassis because [chars]
Explanation The shutdown of the chassis was unsuccessful due to the mentioned reason.
Recommended Action Chassis shutdown is typically initiated due to some critical failure. If the software initiated chassis shutdown has failed, then user should intervene and shut down the chassis manually.
Error Message%PLATFORM-CCTL-2-STANDBY_SHUTDOWN_FAILED Unable to shutdown the standby node as part of chassis shutdown
Explanation The shutdown of the standby SC/RP node failed during the chassis shutdown process.
Recommended Action Please power off the chassis manually.
Error Message%PLATFORM-CCTL-3-ERROR_EXIT Envmon process exiting because [chars], error code [chars]
Explanation The Chassis Control driver process exited due to the reason mentioned in the message.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. Execute 'show process envmon location ' to verify that the process is up and running. If it is still non-operational, try doing from the admin mode 'process restart envmon location '. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CCTL-3-MASTERSHIP_EXIT Exiting because not able to [chars] mastership
Explanation The Chassis Control driver process exited as it was not able to grab mastership or unable to release it.
Recommended Action No action is required.
Error Message%PLATFORM-CCTL-3-READ_POWER_SHELF_TYPE_FAILURE Unable to detect power shelf type. Assuming AC shelf and continuing for now. Please check EEPROM programming on power shelf backplane.
Explanation We are unable to read the power shelf backplane EEPROM for some reason. Need to check the programming of the backplane.
Recommended Action Check that the power-shelf is seated correctly, and that the backplane EEPROM is programmed correctly. In the admin mode, use 'show diag power-supply eeprom-info' to check the contents of the EEPROM.
Error Message%PLATFORM-CCTL-4-UNKNOWN_SHELF_ID Unknown shelf ID [hex] read from power shelf backplane EEPROM - please check EEPROM programming.
Explanation The value read from the power shelf backplane does not match any of the known shelf ID values. Please check the EEPROM programming.
Recommended Action Please check the EEPROM programming of the power-shelf backplane. 'show diag power-supply eeprom-info' in admin mode gives a raw dump of the EEPROM data. Refer EDCS-137763 to interpret the data to check if the shelf ID is programmed correctly or not. If the shelf ID is incorrect, the unit will have to be RMA'd to reprogram the EEPROM correctly.
Error Message%PLATFORM-CCTL-6-TEMP_ALARM [chars] alarm occured for [chars] sensor at temperature [dec] deg C, against configured threshold of [dec] deg C
Explanation Informational msg indicating temperature at which alarm occured.
Recommended Action Software will take corrective action on its own. No action is required.
Error Message%PLATFORM-CCTL-7-OPERATION_FAIL Failed to [chars], error code [chars]
Explanation The particular operation mentioned in the message failed due to some reason. This is not a critical failure, the process can continue functioning as expected despite the failure.
Recommended Action Debug message only. No action is required.
CEMGBL Messages
Error Message%PLATFORM-CEMGBL-7-ERROR [chars] : [chars]
Explanation An unexpected error condition encountered.
Recommended Action Collect system log information. No action is required.
CETHHA Messages
Error Message%PLATFORM-CETHHA-2-CRITICAL Hardware error on control-ethernet port [chars]
Explanation Hardware error on CPU control ethernet port.
Recommended Action Remove/Replace the RP.
Error Message%PLATFORM-CETHHA-2-PORT_FAULT High rate of errors on control ethernet port [chars]
Explanation The rate of link errors on the control ethernet port has exceeded the threshold. The link should be fixed to avoid disruption in router services.
Recommended Action Fix the bad link after switching traffic to redundant link.
Error Message%PLATFORM-CETHHA-4-NOGE RP does not have GE connectivity
Explanation RP does not have GE connectivity. Reload/failovers may cause problems.
Recommended Action Check the GE connections on the front panel of the RP/SC and re-connect/replace to make sure atleast one GE connection is there.
CPUCTRL_PCI Messages
Error Message%PLATFORM-CPUCTRL_PCI-3-FAILED_S cpuctrl PCI: [chars]
Explanation CPUCTRL PCI, this function has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL_PCI-3-FAILED_SD cpuctrl PCI: [chars] [dec]
Explanation CPUCTRL PCI, this function has failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL_PCI-6-LOG_S cpuctrl PCI: [chars]
Explanation CPUCTRL PCI, event logging.
Recommended Action No action is required.
Error Message%PLATFORM-CPUCTRL_PCI-6-LOG_SD cpuctrl PCI: [chars] [dec]
Explanation CPUCTRL PCI, event logging.
Recommended Action No action is required.
Error Message%PLATFORM-CPUCTRL_PCI-6-LOG_SS cpuctrl PCI: [chars] [chars]
Explanation CPUCTRL PCI, event logging.
Recommended Action No action is required.
Error Message%PLATFORM-CPUCTRL_PCI-6-LOG_SXX_1 cpuctrl PCI: [chars] [hex] [hex]
Explanation CPUCTRL PCI, event logging.
Recommended Action No action is required.
Error Message%PLATFORM-CPUCTRL_PCI-6-LOG_SXX_8 cpuctrl PCI: [chars] [hex] [hex]
Explanation CPUCTRL PCI, event logging.
Recommended Action No action is required.
CPUCTRL Messages
Error Message%PLATFORM-CPUCTRL-3-ASIC_NOT_FOUND Cpuctrl could not find [chars]
Explanation While booting up, CPUCTRL could not find the required ASICs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-3-ASIC_RESET_FAILURE Cpuctrl could not reset board ASICs. [chars] Error.
Explanation While trying to bring up ASIC links, Cpuctrl manager could not reset MSC and PLIM board ASICs port.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-3-CDMA_RAM_CORRECTABLE_ERROR Cpuctrl HW detected SBE in [chars] RAM. Key: [hex]
[chars]Explanation Indicates a correctable single-bit error occurred on this internal SRAM. The error is corrected transparently. The location will be written automatically before being read again.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-3-CDMA_RAM_PARITY_ERROR Cpuctrl HW detected parity in [chars] RAM. Key: [hex]
[chars]Explanation Indicates an uncorrectable parity error occurred on this internal SRAM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-3-CDMA_RAM_UNCORRECTABLE_ERROR Cpuctrl HW detected MBE in [chars] RAM. Key: [hex]
[chars]Explanation Indicates an uncorrectable multi-bit error occurred on this internal SRAM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-3-DETECTED_TX_PDMA_STALL TX PDMA Ring Stalled, port equals [dec] ([chars]), queue equals [dec] ([chars]), cur_ind equals [dec], tx_ind equals [dec].
Explanation CPUCTRL TX PDMA ring remained full over non-transient period. Packets which could not be sent were discarded. The downstream ASIC may be stalled. Asic error logged with queue details.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-3-ERR_INIT [chars], Reason: [chars]. Exiting.
Explanation Cpuctrl manager encountered a fatal error and is not able to recover from the error. A reason text will be supplied; please provide this text when calling Cisco support.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-3-FAULT_REPORT_FAILURE Cannot report fault ([chars]) to PM fault manager
Explanation Cpuctrl attempted to report a fault and was unable to log the message with the fault manager. The message text is supplied.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-3-HW_DETECTED_ERROR_ISN [chars]
Explanation The cpuctrl driver HW error interrupt handler was invoked and found valid PCI ISN register from a Cpuctrl Internal Access failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-3-HW_DETECTED_ERROR_LINK [chars]
Explanation The cpuctrl driver HW error interrupt handler was invoked and found a port with valid link error registers.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-3-HW_DETECTED_ERROR_PCI_PM [chars]
Explanation The cpuctrl driver HW error interrupt handler was invoked and found valid PCI PM error registers.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-3-HW_DETECTED_ERROR_PCI_SN [chars]
Explanation The cpuctrl driver HW error interrupt handler was invoked and found valid PCI SN error registers.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-3-HW_DETECTED_ERROR_PCIX [chars]
Explanation The cpuctrl driver HW error interrupt handler was invoked and found valid PCIX error registers.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-3-HW_DETECTED_ERROR_PORT [chars]
Explanation The cpuctrl driver HW error interrupt handler was invoked and found a port with valid isn error registers.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-3-HW_GASPP_READ_BUS_ERROR Bus error when attempting User requested GASPP Read, Address equals [hex]
Explanation The user may have entered an invalid address, or else there is a HW problem.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-3-HW_GASPP_WRITE_ERROR Cpuctrl HW detected error on GASPP write, Address equals [hex]
Explanation The user may have entered an invalid address that is not writable.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-3-PCI_RAM_CORRECTABLE_ERROR_MASK Cpuctrl HW detected SBE in [chars] RAM. Key: [hex]
[chars]Explanation Indicates a correctable single-bit error occurred on this internal SRAM. This memory is considered 'persistent' and requires special handling as described in the 'Data_corrected' row of Table 1.2.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-3-PCI_RAM_CORRECTABLE_ERROR_OTHER Cpuctrl HW detected SBE in [chars] RAM. Key: [hex]
[chars]Explanation Indicates a correctable single-bit error occurred on this internal SRAM. The error is corrected transparently. The location will be written automatically before being read again.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-3-PCI_RAM_UNCORRECTABLE_ERROR Cpuctrl HW detected MBE in [chars] RAM. Key: [hex]
[chars]Explanation Indicates an uncorrectable multi-bit error occurred on this internal SRAM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-3-PDMA_RAM_CORRECTABLE_ERROR Cpuctrl HW detected SBE in [chars] RAM. Key: [hex]
[chars]Explanation Indicates a correctable single-bit error occurred on this internal SRAM. The error is corrected transparently. The location will be written automatically before being read again.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-3-PDMA_RAM_PARITY_ERROR Cpuctrl HW detected parity in [chars] RAM. Key: [hex]
[chars]Explanation Indicates an uncorrectable parity error occurred on this internal SRAM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-3-PDMA_RAM_UNCORRECTABLE_ERROR Cpuctrl HW detected MBE in [chars] RAM. Key: [hex]
[chars]Explanation Indicates an uncorrectable multi-bit error occurred on this internal SRAM.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-3-PERSISTENT_CRC_LINK_FAILURE Cpuctrl port [dec] link is unframeable with persistent CRC errors.
Explanation Cpuctrl manager could not bring up the ASIC link on the specified port. This indicates a hardware failure on the MSC or PLIM board.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-7-ERR_BAG_REG Bag register failed for rules. Reason: [chars]
Explanation EDM Bags are used to share information between components using sysdb. This Error indicates that bag registration failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-7-ERR_DLL_INIT Dll Initialization for [chars] failed. Reason: [chars]
Explanation Cpuctrl driver tried to register for a dll but it encountered an error. The driver might lose some of its functionality.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-7-ERR_EVM_CREATE Event Manager create failed for [chars]. Reason: [chars]
Explanation Cpuctrl Event Manager create error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-7-ERR_EVM_NOTIFY Event Manager notify failed for [chars]. Reason: [chars]
Explanation Cpuctrl Event Manager notify error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-7-ERR_LWM_EVENT_BLOCK LWM Event Manager event block failed. Reason: [chars]
Explanation Cpuctrl Event Manager event block error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRL-7-ERR_SYSDB_EDM_REG Sysdb Register EDM failed. Reason: [chars]
Explanation Cpuctrl Sysdb Register EDM error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
CPUCTRLLIB Messages
Error Message%PLATFORM-CPUCTRLLIB-3-DETECTED_CDMA_PORT0 CDMA to port 0 channel equals [dec], queue equals [dec] ([chars]). ASIC address [[hex],[hex]]
Explanation The cpuctrl driver detected an attempt to DMA to port 0. The request was discarded and not performed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRLLIB-3-DETECTED_EGRESSQ_QUEUE0_PDMA TX PDMA to EgressQ queue 0, port equals [dec], queue equals [dec] ([chars]). Buffer Header: [hex]. Initial packet data(hex): [chars]
Explanation The cpuctrl driver detected an attempt to DMA a packet to egressq queue 0. The packet was discarded and not sent.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRLLIB-3-DETECTED_ERROR_PDMA [chars], [dec], port equals [dec] ([chars]), queue equals [dec] ([chars])
Explanation The cpuctrl driver detected an error during packet DMA.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRLLIB-3-HW_DETECTED_ERROR_CDMA HW set the error bit in a CDMA descriptor
CDMA engine equals [dec], queue equals [dec] ([chars]), index equals [dec]
error reg_lo equals [hex], error_reg_hi equals [hex]Explanation CDMA ended in error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRLLIB-3-HW_DETECTED_ERROR_RX_PDMA HW set the error bit in a RX PDMA descriptor
port equals [dec] ([chars]), queue equals [dec] ([chars]), index equals [dec]
Explanation The cpuctrl driver detected a buffer marked with an error, possibly a CRC check. The buffer is discarded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRLLIB-3-INT_WARNING Excess Spurious interrupt on device [chars]
Explanation The cpuctrllib ASIC Interrupt wrapper has detected that an ASIC driver has not cleared its interrupts at the source for 1000 consecutive times. This is possibly an error in the Driver ISR, that does not process and clear all possible interrupts, or malfunctioning HW. The Interrupt is disabled to prevent the ISR from hogging the CPU.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRLLIB-3-PCI_CONFIGURATION_ERROR Incorrect PCI configuration: [chars]: [dec]
Explanation Incorrect PCI configuration or a problem with the hardware prevents CPUCTRL from accessing the forwarding ASICs.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRLLIB-3-UNRECOVERED_PIO_ERROR Restarting cpuctrl client [dec] ([chars]) on port [dec] for devid [dec] ([chars]) on unrecovered PIO error notification
Explanation A PIO error was detected and the responsible client was notified but did not mark the error as recovered. Restarting the client.
Recommended Action No action is required.
Error Message%PLATFORM-CPUCTRLLIB-4-PORT_INIT_FAILURE Port [dec] ([chars]) could not clear Link errors during init
link_error_reg equals [hex], crc_reg equals [hex]Explanation Port will not operate reliably
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRLLIB-4-PORT_NOT_PRESENT Attempt to access Port [dec] which was not discovered
Device ID_reg equals [hex], devid equals [hex]Explanation Port will not operate reliably
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRLLIB-4-PORT_REFRAME_SYNC_FAILURE Port [dec] ([chars]) would not sync on reframe attempt
Explanation Port will not operate reliably
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRLLIB-4-PORT_REINIT_FAILURE Port [dec] ([chars]) Device chipid mismatch during reframe
id_reg read after reframe equals [hex], id_reg during HW discovery equals [hex]Explanation Port will not operate reliably
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-CPUCTRLLIB-6-NO_BUF_TO_REPLACE RX PDMA Ring out of buf, Port [dec] ([chars]), Q [dec] ([chars]), cur_ind equals [dec], tx_ind equals [dec], retry [dec]
Explanation CPUCTRL RX PDMA ring could not replace the buffers. possible low buffer condition.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
DRP_PAIRING Messages
Error Message%PLATFORM-DRP_PAIRING-7-ERR_CERR_REG Failed to register with CERR Handler. [chars]
Explanation --
Recommended Action '*NONE*'
Error Message%PLATFORM-DRP_PAIRING-7-ERR_DSC_NODEID Unable to determine the dSC nodeid
Explanation --
Recommended Action '*NONE*'
Error Message%PLATFORM-DRP_PAIRING-7-ERR_EVM_CREATE Event manager create failed. [chars]
Explanation --
Recommended Action '*NONE*'
Error Message%PLATFORM-DRP_PAIRING-7-ERR_GET_MY_NODEID Failed to get my own nodeid. [chars]
Explanation --
Recommended Action '*NONE*'
Error Message%PLATFORM-DRP_PAIRING-7-ERR_PROC_BLOCK [chars]
Explanation --
Recommended Action '*NONE*'
Error Message%PLATFORM-DRP_PAIRING-7-ERR_SERVER_INIT Unable to initialize drp_pairing server. [chars]
Explanation --
Recommended Action '*NONE*'
Error Message%PLATFORM-DRP_PAIRING-7-ERR_SYSDB_ACCESS SysDB operation failed. [chars]
Explanation --
Recommended Action '*NONE*'
Error Message%PLATFORM-DRP_PAIRING-7-ERR_THREAD_CREATE Unable to create a thread. [chars]
Explanation --
Recommended Action '*NONE*'
DSC Messages
Error Message%PLATFORM-DSC-1-ERR_LOST_ALL_FABRIC_RACKS Lost Connection to all Fabric Racks
Explanation This node has lost connectivity with all fabric racks before the fabric planes came up. This could be a control ethernet problem or the fabrics have reloaded.
Recommended Action Check if fabric chassis are up. If up, check control-ethernet connectivity between this chassis and Fabric chassis. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-DSC-3-ERR_DSC_INIT [chars] - error : [chars] , exiting...
Explanation The dsc process failed in initialization. This indicates that there was a software error during initialization.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. Verify that the dsc process is up and running by executing the following command at the CLI of the active RP: 'show process dsc' If it is still non-operational, restart the driver by executing the following command at the CLI of the active RP: 'process restart dsc' If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-DSC-3-ERR_INPUT_PRIORITY [chars] - nodeid : [hex]
Explanation Priority given for the node is not applicable.
Recommended Action Verify the priority given for this node and enter the correct priority. No action is required.
Error Message%PLATFORM-DSC-3-ERR_INTERNAL_SW [chars] - error : [chars], exiting...
Explanation An internal software error occured as indicated in the message.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. Verify that the dsc process is up and running by executing the following command at the CLI of the active RP: 'show process dsc' If it is still non-operational, restart the driver by executing the following command at the CLI of the active RP: 'process restart dsc' If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-DSC-3-ERR_LTRACE_INIT Could not initialize [chars] trace buffer, error [hex] ([chars])
Explanation ltrace initialization failed
Recommended Action If continuous, contact tech-support Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-DSC-3-ERR_MEM_ALLOC Failed to allocate [dec] bytes, exiting...
Explanation The dsc process could not allocate memory. This indicates some problem with the system wide memory.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. Verify that the dsc process is up and running by executing the following command at the CLI of the active RP: 'show process dsc' If it is still non-operational, restart the driver by executing the following command at the CLI of the active RP: 'process restart dsc' If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PLATFORM-DSC-3-ERR_NULL_SERIAL_ID WARNING ! WARNING ! Received request with zeroed serial number. Assigning rack num [dec] and allowing it to pass, till CSCeg63482 is fixed. If this is multi-chassis, please upgrade ALL RP/SC ROMMONs in this setup to 1.22 !
Explanation Once ROMMON 1.22 is rolled out, all multi-chassis testbeds should upgrade to it to avoid problems of more than one RP getting the same rack number assigned. This msg warns the operator that an RP was detected that had older ROMMON and should be upgraded ASAP.
Recommended Action Upgrade the ROMMON to ver 1.32 or more Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-DSC-3-ERR_RACK_DOWN Lost connectivity with rack [chars]
Explanation This indicates that either the rack is powerdown/shutdown or there is some problem with control ethernet cables or switches between the racks.
Recommended Action If the rack is not powerdown or shutdown by the operator, then check the control ethernet connectivity between racks. (Check if the cables are okay and also if the switch is operating normally). Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-DSC-3-ERR_SYSDB_CONNECT [chars] - error: [chars]
Explanation The dsc process could not open connection with sysdb. Hence the show commands will fail. However, the system will continue to function normally.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-DSC-3-ERR_TRANSPORT Primary transport connection not ok to node [hex], alternate transport connectivity ok
Explanation CRS: This indicates that there is a problem with control ethernet cables or switches to that node. C12k: This indicates that there is a problem with MBUS communication to that node.
Recommended Action CRS: Check the control ethernet connectivity to the node. (Check if the cables are okay and also if the switch is operating normally). C12K: If the error persists for a long time, please check the MBUS communication to the node. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-DSC-4-WARNING_RACK_NUM ROMMON RACK_NUM ( equals [dec]) set inconsistent.
Explanation ROMMON RACK_NUM variable setting is different from the node_id rack field setting.
Recommended Action Set ROMMON RACK_NUM to proper rack number per chassis rack field
Error Message%PLATFORM-DSC-5-NOTICE_RACK_NUM ROMMON RACK_NUM set to 0.
Explanation ROMMON RACK_NUM variable set to 0.
Recommended Action No action is required.
Error Message%PLATFORM-DSC-6-ERR_I_AM_DSC Setting myself as DSC
Explanation Informational message notifying current DSC in system
Recommended Action No action is required.
Error Message%PLATFORM-DSC-7-ERR_RACK_DELETE [chars]. rack equals [dec], [chars]
Explanation An internal software error occured and this rack could not be removed.
Recommended Action No action is required.
Error Message%PLATFORM-DSC-7-ERR_RACK_OIR Config cleanup failed following rack [dec] removal - [chars]. error: [chars]
Explanation Not able to save configuration for this rack.
Recommended Action Examine chassis based on above error msg.
Error Message%PLATFORM-DSC-7-ERR_RACK_OIR_TIMEOUT No Response received from configuration manager server.
Explanation No response received from configuration manager server.
Recommended Action No action is required.
Error Message%PLATFORM-DSC-7-ERR_STORE_REBOOT_INFO Could not store reboot information for node [hex], [chars]
Explanation Chassis APIs that write to non volatile memory failed.
Recommended Action No action is required.
DSCMEDIA Messages
Error Message%PLATFORM-DSCMEDIA-2-ERR_WAIT_REDUNDANCY Waiting for result of active/standby arbitration...keep trying
Explanation The redundancy information is needed as an input for the DSC election. Only active cards may become DSC. The information is still unavailable at this time. The DSC election is on hold, waiting for the information to become available. This will prevent proper system operation.
Recommended Action If this message happens repeatitively, it indicates a problem, likely in the active/standby arbitration module. Collect information using 'show redundancy'.
Error Message%PLATFORM-DSCMEDIA-2-FATAL DSC media fatal error: [chars]
Explanation The dsc media dll encountered aa fatal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-DSCMEDIA-3-ERROR Error from dsc media dll: [chars]
Explanation The dsc media dll encountered an internal software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-DSCMEDIA-3-ERROR2 Error from dsc media dll: [chars], errno equals [dec] ([chars])
Explanation The dsc media dll encountered an internal software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-DSCMEDIA-3-READ_PERSIST Unable to [chars] when parsing persistent file [chars]: [chars] ([chars])
Explanation The dsc process attempted to read dcs election information from non-volatile storage, but encountered a problem. This may cause the wrong RP card to get elected as DSC.
Recommended Action Verify nvram: filesystem integrity. If this is a persistent problem then: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-DSCMEDIA-3-WRITE_PERSIST Unable to [chars] when writing persistent file [chars]: [chars] ([chars])
Explanation The dsc process attempted to store dcs election information to non-volatile storage, but encountered a problem. This may cause the wrong RP card to get elected as DSC on the next chassis cold boot.
Recommended Action Make sure there is free space in local NVRAM. If this is a persistent problem then: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-DSCMEDIA-4-FETCH Unable to [chars] [chars] when fetching initial copy from DSC: [chars] ([chars])
Explanation The process is unable to get an initial copy of the dsc info file from the dsc card. This may cause the wrong RP card to get elected as DSC on the next chassis cold boot.
Recommended Action Restarting the dsc process (proc restart dsc) will cause it to retry the operation and normally recover from this condition. If the issue persists: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-DSCMEDIA-4-LISTEN Unable to listen for multicast messages: [chars] ([chars])
Explanation The process is unable to register to receive multicast messages. This means that the card will not be able to update local non-volatile data with the latest dsc election information coming from remote nodes. This may cause the wrong RP card to get elected as DSC on the next chassis cold boot.
Recommended Action Restarting the dsc process will cause it to re-register to receive dsc persisted updates. If the issue persists: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-DSCMEDIA-4-NO_CSC_SN Could not read Serial Numbers of the Fabric Cards slot 16 & 17; errno equals [dec] ([chars])
Explanation Serial Numbers of the Fabric Cards (slots 16 and 17) are used to help determine chassis nativity for the Logical Routers feature. Chassis nativity is part of the algorithm to ensure that on a cold boot, the right RP is elected as the DSC and provides Logical Router boundaries to other RP cards. The lack of CSC serial numbers may cause the wrong RP to be elected DSC when RP cards are shuffled from one chassis to another and a cold boot is performed.
Recommended Action Ensure that Fabric CSC cards are properly inserted in the chassis.
Error Message%PLATFORM-DSCMEDIA-4-WARNING Warning from dsc media dll: [chars]
Explanation The dsc media dll encountered an internal software warning.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-DSCMEDIA-4-WARNING2 Warning from dsc media dll: [chars], errno equals [dec] ([chars])
Explanation The dsc media dll encountered an internal software warning.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-DSCMEDIA-6-DSC_ELECTED This node is now [chars]
Explanation A new dSC has been elected.
Recommended Action No action is required.
ENVMON Messages
Error Message%PLATFORM-ENVMON-2-ADDITIVE_POWER_OVERBUDGET Power consumption has exceeded additive supply mode limit by [dec]W; results unpredictable
Explanation The power calculated in use by the chassis exceeds that available by the powershelf. This condition could result in an outage of the chassis if action is not immediately taken.
Recommended Action Remove some linecards to reduce power consumption, or install a higher capacity powershelf.
Error Message%PLATFORM-ENVMON-2-POWER_BUDGET_OK Power consumption is back within [chars] supply mode limits
Explanation The power calculated in use by the chassis has returned to a value that is within the power supplied by the powershelf.
Recommended Action None required.
Error Message%PLATFORM-ENVMON-2-REDUNDANT_POWER_OVERBUDGET Power consumption has exceeded redundant supply mode limit by [dec]W; power redundancy lost
Explanation The power calculated in use by the chassis exceeds that for which power supply redundancy is available. The chassis now function in additive mode.
Recommended Action Remove some linecards to reduce power consumption, or install a higher capacity powershelf to regain power supply redundancy.
Error Message%PLATFORM-ENVMON-3-ERROR_READ_AC Failed mbus read when determining AC/DC
Explanation An attempt to read from MBus to determine whether the chassis is AC or DC powered failed. This will result in the supply type reporting as the default of AC.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-ENVMON-3-UNKNOWN_PEM Unknown PEM[dec] of type [chars]%s, chassis type [dec]
Explanation The envmon component could not determine the type of Power Entry Module. This will result in this PEM reporting as a 0W PEM and the power calculations will be inaccurate.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
ETH_SRVR Messages
Error Message%PLATFORM-ETH_SRVR-3-TX_STALLED Self test detected that control ethernet transmit functionality has stalled. Restarting to recover.
Explanation Ethernet server is performing a periodic self test to ensure that transmit has not stalled for any reason. This error msg means that the test failed and transmit has stalled. Eth server will correct the condition by restarting itself and operator needs to do nothing.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log. Issue the show controllers backplane ethernet trace location node command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show controllers backplane ethernet trace location node output, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PLATFORM-ETH_SRVR-3-UNKNOWN_FORUS_PAK ethernet driver received an unknown for us packet. Cmd equals [dec]
Explanation Ethernet driver received an unknown for us packet.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log. Issue the show controllers backplane ethernet trace location node command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show controllers backplane ethernet trace location node output, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PLATFORM-ETH_SRVR-4-INIT_ERR [chars], error equals [dec] ([chars])
Explanation An error occurred during initialization from which eth server cannot recover. The process will restart on its own to attempt a recovery.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log. Issue the show controllers backplane ethernet trace location node command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show controllers backplane ethernet trace location node output, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PLATFORM-ETH_SRVR-7-ERR_FSM RECV_FSM: Type: [chars] Fragments: [dec] src: [chars] dest [chars] size: [dec] [chars]
Explanation A bad or incomplete frame was received on the node given in the msg. If the messages are not persistent the condition is harmless and no action is required. If the messages are constantly seen, contact tech support with the output of the given command.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log. Issue the show controllers backplane ethernet location loc in msg detail command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show controllers backplane ethernet location loc in msg detail output, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PLATFORM-ETH_SRVR-7-INCORRECT_PAK Packet corruption detected in eth_server transmit complete
Explanation Ethernet driver got a corrupted packet in its transmit complete, possibly because its client (EES) has zeroed out the packet contents before eth_server is done with the packet.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log. Issue the show buffer-manager region all context, SH_CMD show buffer-manager region all context, dumpcore running jid/process name of eth_server, ingressq, fabricq_mgr, fsdb_server, fsdb_aserver, sfe_driver & fgid_server command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show buffer-manager region all context, SH_CMD show buffer-manager region all context, dumpcore running jid/process name of eth_server, ingressq, fabricq_mgr, fsdb_server, fsdb_aserver, sfe_driver & fgid_server output, call your Cisco technical support representative and provide the representative with the gathered information.'
FABIO Messages
Error Message%PLATFORM-FABIO-3-ERR_INGQ_CREATE [chars], pri equals [dec], dir equals [dec], failed[[chars]]
Explanation Internal Error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-FABIO-3-ERR_INGRESS [chars]
Explanation Internal Error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-FABIO-3-ERR_INIT [chars], with code([dec]) [chars]
Explanation Internal Error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-FABIO-3-ERR_MEM_ALLOC [chars], for size [dec].
Explanation Failed to allocate memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-FABIO-3-ERR_Q_LOOKUP qad_q_lookup failed, i equals [dec], dir equals [chars], failed[[chars]]
Explanation Internal Error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-FABIO-3-ERR_QUEUE_FOUND Found unexepected QAD queue [chars]
Explanation Internal Error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-FABIO-7-ERR_DUPLICATE_STREAMID [chars], stream id [dec] existed
Explanation Internal Error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-FABIO-7-ERR_SEND_PKT [chars], [dec], [dec], rc is [dec]
Explanation Internal Error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FABRIC_CTRL Messages
Error Message%PLATFORM-FABRIC_CTRL-2-ACTIVE_RP Encountered error when waiting for the active/standby role of the RP. rc equals [hex]
Explanation This message indicates that the fabric control process encounter an error when waiting for the active RP notification. Process exits with error. This is either a system resource issue or a software bug.
Recommended Action Try to restart fctl process to see if problem persists 'process restart fctl'. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. 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%PLATFORM-FABRIC_CTRL-2-CARD_STATE [chars], [hex]
Explanation This message indicates that the software tries to set the state of an unknown card. Software is in a bad state.
Recommended Action Try to restart fctl process to see if problem persists 'process restart fctl'. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. 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%PLATFORM-FABRIC_CTRL-2-CHKPT_INIT_FAILED Fabric control failed to initialize for data checkpointing, errno equals [hex]
Explanation This message indicates that the fabric control process encountered a problem when trying to initialize data checkpointing. Process will abort.
Recommended Action Try to restart fctl process to see if problem persists 'process restart fctl'. Check if system memory is adequate. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. 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%PLATFORM-FABRIC_CTRL-2-CHKPT_REGISTRATION_FAILED Fabric control failed to register for data checkpointing, errno equals [hex]
Explanation This message indicates that the fabric control process encountered a problem when trying to registering data for checkpointing. Process will abort.
Recommended Action Try to restart fctl process to see if problem persists 'process restart fctl'. Check if system memory is adequate. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. 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%PLATFORM-FABRIC_CTRL-2-ERR_MEM_ALLOC No memory avaliable for [chars]
Explanation This message indicates that the system did not have enough memory available. [chars] is the operation for which there was insufficient memory. System is in an unstable 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. 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%PLATFORM-FABRIC_CTRL-2-ERR_MEM_ALLOC [chars]
Explanation This message indicates that the system did not have enough memory available. [chars] is the operation for which there was insufficient memory. System may be in an unstable 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. 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%PLATFORM-FABRIC_CTRL-2-ERR_MEM_ALLOC [chars]
Explanation This message indicates that the system did not have enough memory available. [chars] is the operation for which there was insufficient memory. System may be in an unstable 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. 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%PLATFORM-FABRIC_CTRL-2-ERR_REPORT [chars]
Explanation This message indicates that an error detected in the fabric hardware as described in [char]
Recommended Action Follow the instruction on the error message. If it is a suspected hardware failure, reseat the hardware. If reseating the hardware does not fix the error condition, contact your Cisco technical support representative.
Error Message%PLATFORM-FABRIC_CTRL-2-EVENT_LOOP Process event loop exited due to unknown errors. Abort
Explanation This message indicates that the fabric control process encounter an error in its event dispatcher. Process aborts. This is either a system resource issue or a software bug
Recommended Action Try to restart fctl process to see if problem persists 'process restart fctl'. Check if system memory is adequate. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. 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%PLATFORM-FABRIC_CTRL-2-FAILED_SYNCH Slot [dec] does not see fabric clock from [chars]
Explanation This message indicates that the card on slot int failed to synchronize clocks with the Master clock. If this condition persists, Slot int is unusable.
Recommended Action Check the MBUS agent ROM version of the fabric cards and the card on slot int are up-to-date. Check the fabric loader version on slot int is up-to-date. Check the temperature of the fabric cards. Reseat the card on slot int and all the fabric cards. If reseating the hardware does not fix the error condition, contact your Cisco technical support representative.
Error Message%PLATFORM-FABRIC_CTRL-2-FAILED_TO_RESET_FC Failed to reset fabric card, slot equals [dec] in software
Explanation A fabric card failed to reset. This message indicates that the software failed to reset the fabric card on slot int. Slot int is marked as malfunction and is shutdown.
Recommended Action Check the MBUS agent ROM version of the fabric cards are up-to-date. Check the temperature of the fabric cards. Reseat the primary CSC card. If reseating the hardware does not fix the error condition, contact your Cisco technical support representative.
Error Message%PLATFORM-FABRIC_CTRL-2-FAILED_TO_SEND_CONFIG Failed to send new fabric configuration to slot [dec] after [dec] retries
Explanation This message indicates that the linecard on slot int failed to receive the latest fabric configuration data it needs to connect to the fabric. slot int is disconnected from the fabric and is unusable.
Recommended Action Reseat the linecard on slot int. If reseating the hardware does not fix the error condition, contact your Cisco technical support representative.
Error Message%PLATFORM-FABRIC_CTRL-2-FAILED_TO_SEND_SLOT_BW Failed sending slot bandwidth info to slot [dec] after [dec] retries
Explanation This message indicates that the linecard on slot int failed to receive the latest slot bandwidth data it needs to operate. slot int is disconnected from the fabric and is unusable.
Recommended Action Reseat the linecard on slot int. If reseating the hardware does not fix the error condition, contact your Cisco technical support representative.
Error Message%PLATFORM-FABRIC_CTRL-2-FAILED_TO_SYNC_RP Failed to sync RP (slot equals [dec]) to [chars] (slot equals [dec])
Explanation This message indicates that the RP on slot int failed to synchronize its clock with the Master clock. The RP on slot int is unusable if this condition presists. If RP on slot int is the primary RP, then the router is unusable.
Recommended Action Check the MBUS agent ROM version of the fabric cards and the RP on slot int are up-to-date. Check the temperature of the fabric cards. Reseat the RP on slot int and all the fabric cards. If reseating the hardware does not fix the error condition, contact your Cisco technical support representative.
Error Message%PLATFORM-FABRIC_CTRL-2-FAILED_TO_SYNC_RP_TO_CSCS Could not synch primary RP (slot equals [dec]) to both CSC1 and CSC0
Explanation This message indicates that the primary RP failed to synchronize its clock with either CSC. If problem persists, router is unusable.
Recommended Action Check the MBUS agent ROM version of the fabric cards and the RP on slot int are up-to-date. Check the temperature of the fabric cards. Reseat the RP on slot int and all the fabric cards. If reseating the hardware does not fix the error condition, contact your Cisco technical support representative.
Error Message%PLATFORM-FABRIC_CTRL-2-FAILED_TO_SYNC_TO_SELF Failed to sync [chars] (slot [dec]) to itself
Explanation This message indicates that the primary CSC failed to synchronize its clock with itself. If problem persists, router is unusable.
Recommended Action Check the MBUS agent ROM version of the fabric cards are up-to-date. Reseat the primary CSC card. Check the temperature of the fabric cards. If reseating the hardware does not fix the error condition, contact your Cisco technical support representative.
Error Message%PLATFORM-FABRIC_CTRL-2-MBUS_ERROR Unable to send MBUS msg. Error equals [dec] ([chars])
Explanation This message indicates that an error occurred when the card tries to communicate with remote on fabric and chassis management via MBUS. Chassis, LCs and fabric is in a bad state.
Recommended Action Verify the MBUS agent ROM version is up-to-date. Reseat the card with the error. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. 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%PLATFORM-FABRIC_CTRL-2-NOTIFY_BW_CHG_ERROR new chassis bandwidth, [dec], cannot be sent to clients. Error: [chars]
Explanation This message indicates that chassis bandwidth has changed but fabric control cannot send the info to its clients. Router may be in an unstable 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. 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%PLATFORM-FABRIC_CTRL-2-PROCESS_INIT Encountered critical problem in initialization of [chars]
Explanation This message indicates that the system cannot initialize some critical parts of the fabric software. [chars] are the critical parts that failed. Fabric control process is aborted.
Recommended Action Try to restart fctl process to see if problem persists 'process restart fctl'. Check if system memory is adequate. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. 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%PLATFORM-FABRIC_CTRL-3-CARD_ID_FPGA_VERSION_MISMATCH Fabric Card type [hex] has an unsupported FPGA version. Card will be shutdown
Explanation This message indicates that fabric card has a wrong or unsupported version of FPGA. Software cannot monitor the fabric card and it is shutdown.
Recommended Action Verify the fabric card and chassis is supported by the software. Ensure the fabric card is inserted to the chassis correctly. Provide the 'show diag' info and contact your Cisco technical support representative.
Error Message%PLATFORM-FABRIC_CTRL-3-MBUS [chars], errno equals [hex], [chars]
Explanation This message indicates that an error occurred when RP tries to communicate with remote on fabric and chassis management via MBUS. If problem persists, chassis, LCs and fabric is in a bad state.
Recommended Action Verify the MBUS agent ROM version is up-to-date. Try to restart fctl and mbus process to see if problem persists: 'process restart fctl' and 'process restart mbus'. If this is a newly inserted card, try to reseat the card. If problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. 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%PLATFORM-FABRIC_CTRL-3-MIB_INIT_ERROR [chars]
Explanation Unable to initialize the debugging facility of fabric MIB. Other fabric MIB capabilities are not disturbed.
Recommended Action Try to restart fctl process to see if problem persists 'process restart fctl'. Check if system memory is adequate. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. 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%PLATFORM-FABRIC_CTRL-3-RESTORE_DATA Encountered error restoring checkpointed data
Explanation This message indicates that the system cannot restore checkpointed data of the fabric software. Router may be in an unstable state
Recommended Action Try to restart fctl process to see if problem persists 'process restart fctl'. Check if system memory is adequate. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. 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%PLATFORM-FABRIC_CTRL-3-THREAD_CREATE Unable to create thread to detect card insertion/removal for register [dec] : rc equals [hex], [chars]
Explanation This message indicates that software encountered an error when creating a thread to detect lincard insertion and removal. Linecards, fabric cards, and RP insertion and removal may not be handled correctly.
Recommended Action Try to restart fctl process to see if problem persists 'process restart fctl'. Check if system memory is adequate. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. 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%PLATFORM-FABRIC_CTRL-3-UNKNOWN_CHASSIS The chassis type is not known from reading the backplane
Explanation This message indicates that the software installed on the system does not recognize the chassis type. The Backplane Server has not provided the chassis model. Software cannot monitor the chassis and will abort.
Recommended Action Remove all the RPs from the backplane of the chassis except the active RP. Reload the active RP. Insert the other RPs into the chassis after the active RP is booted up in IOS-XR RUN state. If problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. 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%PLATFORM-FABRIC_CTRL-3-UNKNOWN_MSG Unknown msg from slot [dec] with msg type [hex]
Explanation This message indicates that the fabric control process received an unknown msg. The message is ignored.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the 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://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. 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%PLATFORM-FABRIC_CTRL-3-UNSUPPORTED_CHASSIS Chassis type [dec] not supported
Explanation This message indicates that the software installed on the system does not recognize the chassis type. Software cannot monitor the chassis fabric. Fabric cards are shutdown.
Recommended Action Verify the fabric card and chassis is supported by the software. Reseat the all the fabric cards. If reseating the hardware does not fix the error condition, contact your Cisco technical support representative
Error Message%PLATFORM-FABRIC_CTRL-4-MCAST_PRI_CFG multicast-priority config has no effect on this chassis type
Explanation This message indicates that hw-module fabric multicast-priority was configured but this configuration has no effect on this chassis. It only applies to non-Sphere 124xx chassis. The chassis type is an internal type value.
Recommended Action Customer may wish to deconfigure hw-module fabric multicast-priority, but it is not necesary since this command has no effect on this chassis.
Error Message%PLATFORM-FABRIC_CTRL-5-FABRIC_CARD_OIR_INSERTED Fabric card [chars] inserted in slot [dec]
Explanation This message indicates that a fabric card on slot int is inserted into the chassis. The fabric control software takes care of its insertion automatically. The chassis fabric and card's Fabric Interface ASIC are re-configured accordingly.
Recommended Action No action required.
Error Message%PLATFORM-FABRIC_CTRL-5-FABRIC_CARD_OIR_REMOVED Fabric card [chars] removed from slot [dec]
Explanation This message indicates that a fabric card on slot int is removed from the chassis. The fabric control software takes care of its removal automatically. The chassis fabric and card's Fabric Interface ASIC are re-configured accordingly.
Recommended Action No action required.
FDIAGS Messages
Error Message%PLATFORM-FDIAGS-3-BAD_EE_READ failure reading EEPROM ([chars]) values during Field Diag EEPROM update: EEPROM not updated
Explanation After completing Field Diags, the EEPROM update was requested, but there was a read failure during the process. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-BAD_EE_WRITE failure writing EEPROM @ offset of [hex] during Field Diag EEPROM update: This byte not updated
Explanation After completing Field Diags, the EEPROM update was requested, but there was a write failure during the process. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-BAD_F_DIAG_KILL Unable to kill this existing Field Diag process: rc from kill was [dec]
Explanation Could not kill that job ID for Field Diags Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-CANNOT_GET_JID Cannot determin Job ID for Field Diags process
Explanation Error getting JID Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-CANT_SEND_MBUS_MSG_F cannot send mbus messages: errno [dec]: [chars]()
Explanation Unable to complete sending mbus error message Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-FAB_MBUS_NOT_READY Fabric card MBUS Ram Agent not loaded prior to beginning Field Diags Fabric tests
Explanation After launching Fabric Field Diagnostics, the fabric card appear not have MBUS Ram Agent loaded within the appropriate time. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail. Investigate why MBUS Ram agent is not successfully downloaded on the fabric card.
Error Message%PLATFORM-FDIAGS-3-FABRIC_NOT_DISCONNECTED Problems occurred while trying to disconnect slot [dec] from the fabric. RC equals [hex]
Explanation Field diagnostics encountered a failure while trying to restore the fabric for the slot that was just tested. Field diagnostics uses a FCTL API to disconnect the slot under test from the fabric when it is done. This API failed, returning the specified return value.
Recommended Action This is a software error, please contact Cisco support to report this problem. Please collect syslogs, verbose run log, show diags detail and show controller output. If the slot eventually transitions to the IOS XR RUN state, then no further actions are needed. The system cleaned itself up. However, if the slot remains in the FDIAGS FAIL state (because field diagnostics failed) or stays in the FDIAG PASS state (because the user specified the 'wait' parameter). Then you need to reload the slot to complete the fabric clearing process.
Error Message%PLATFORM-FDIAGS-3-FABRIC_NOT_RESTORED Problems occurred while trying to clear the fabric.
Explanation Field diagnostics encountered a failure while trying to restore the fabric for the slot that was just tested. Other software errors should have been logged before this to provide details about what failed.
Recommended Action This is a software error, please contact Cisco support to report this problem. Please collect syslogs, verbose run log, show diags detail and show controller output.
Error Message%PLATFORM-FDIAGS-3-FAILED_SYSMGR_FORK Failed to fork Field Diags process: [chars]
Explanation Call to fork process for Field Diags failed for given reason Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-FILE_READ_JID_BAD Cannot read jid data from file
Explanation Could not read that job ID for Field Diags from the file Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-IDLE_CELL_GEN_ADDR [chars]() could not determine the idle cell generation address.
Explanation Field diagnostics was not able to determine the idle cell generation address for the router's fabric.
Recommended Action This is a software error, please contact Cisco support to report this problem. Please collect syslogs, verbose run log, show diags detail and show controller output.
Error Message%PLATFORM-FDIAGS-3-IF_BAD_HALT_OPEN Unable to open Field Diags halt request file [chars]: [chars]
Explanation Error opening halt request file. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-IF_BAD_HALT_WRITE Unable to write Field Diags halt request to file [chars]: [chars]
Explanation Error writing HALT request file Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-IF_BAD_JID_OPEN Unable to open Field Diags state file [chars]: [chars]
Explanation Error opening JID file Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-IF_BAD_JID_READ Unable to read Field Diags state from file [chars]: [chars]
Explanation Error reading JID file Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-IF_BAD_JID_WRITE Unable to write Field Diags state to file [chars]: [chars]
Explanation Error writing JID file Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-IF_FAIL_CONN_SYSLDR_F could not connect to LWM [chars] in [chars]()
Explanation Failed to Connect to sysloader initially Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-IF_FAIL_SEND_SYSLDR_F could not send LWM in [chars]()
Explanation Failed to Connect to sysloader initially Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-IF_FAIL_SYSLDR_DISCONNECT_F could not LWM disconnect from [chars] in [chars]()
Explanation Failed to Connect to sysloader initially Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-IF_FAIL_UUT_LAUNCH UUT launch failed ([chars]). Exiting.
Explanation Failed to Connect to sysloader initially Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-IF_INACTIVITY_TIMEOUT No response from UUT in ~[dec] minutes ([dec] seconds). exiting
Explanation No communication from the UUT in a while. UUT likely became inoperable. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-IF_NON_EXISTANT_JID_OPEN Unable to open Field Diags state file [chars]: [chars]
Explanation Error opening JID file Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-ILLEGAL_FSM_STATE internal (FSM) state change ILLEGAL: was [chars], attempted [dec]
Explanation Bad internal state change Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-INVALID_FABRIC 40G fabric is not supported on 12x04 chassis
Explanation Field diagnostics has been asked to do a 40G operation on a 12x04 chassis, which is not a supported fabric chassis combination. Field diagnostics is proceeding with the action as if this where not a 40G fabric.
Recommended Action This is a software error, please contact Cisco support to report this problem. Please collect syslogs, verbose run log, show diags detail and show controller output.
Error Message%PLATFORM-FDIAGS-3-INVALID_SLOT [chars]() encountered an invalid slot ([dec])
Explanation Field diagnostics validated a slot value before using it and found that it was invalid. Consequently this event was raised. Other field diagnostics errors will be raised to further explain the impact of this problem.
Recommended Action This is a software error, please contact Cisco support to report this problem. Please collect syslogs, verbose run log, show diags detail and show controller output.
Error Message%PLATFORM-FDIAGS-3-MS_NODE_ID_CREATE_FAIL_F Could create nodeid for slot [dec]: [chars] in [chars]()
Explanation Failed to create a node identifier. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-MS_PRI_CLK_READ misc svcs: [chars]: could not read primary clock
Explanation Failed to read Primary Clock from fctl Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-MS_READ_REG_FAIL Failed to read register [hex] from slot [dec]. Errval equals [hex].
Explanation Failed to read a slot-specific register via an mbus-access Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-MS_UNDEF_MS_MSG misc svcs: [chars]: Undefined MBUS_MISC_SVCS message received: Ignored: msg [hex]
Explanation Misc services server received an unrecognized message Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-MS_WRITE_REG_FAIL Failed to write [hex] to register [hex] on slot [dec]. Errval equals [hex].
Explanation Failed to write a slot-specific register via an mbus-access Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-MS_XBAR_MAP misc svcs: [chars]: could not read xbar map
Explanation Failed to read xbar map from fctl Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-NO_PRIMARY_CSC Cannot determine which CSC is the primary. RC:[dec]-[dec]
Explanation Field diagnostics needs to know which CSC is the primary before it can run on the fabric cards. However, it was not able to determine which CSC was the primary. The field diagnostics run stops.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-NO_TIME_OF_DAY no time of day
Explanation Time of Day unavailable internally
Recommended Action Time of day (calendar) may not be initialized. Set using the appropriate CLI and options.
Error Message%PLATFORM-FDIAGS-3-NODE_ID_EXTRACTION_FAILED Failed to extract node id from var: line [dec]
Explanation One of the calls to a node ID extraction function returned an error Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-NON_UUT_IN_STATE Unexpected message received during UUT_ON state: sub-msg [hex] from slot [dec]
Explanation Field Diags was not expecting this type of message at this time. If this problem persists and diags does not complete, Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-PROBLEM_WITH_FDIAG_REQUEST Failed to validate field diagnostic request. Unexpected return code: [dec]
Explanation There is some problem with field diagnostic software since a function has returned an unexpected value. Internal error: Contact Cisco's TAC. This error could be a software problem. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-PROG_REG_FAIL Failed [chars] write [hex] to register [hex] on slot/broadcast group [dec]. Errval equals [hex]
Explanation Failed to write a value to the register in the specified slot or broadcast group. Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-RESTORE_DEFAULT_RAM_AGENT FAILURE re-loading default mbus ram agent
Explanation This card requires a special version of mbus Ram Agent for compatibility with diags for C2W requests for SPA communication Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-SPA_ID_FAIL Unable to identify SPA's inserted in slot [dec]
Explanation The field diags processs was unable to determine which SPAs where inserted in the SIP. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-SPA_UNSUPPORTED_INSTANCE Requested instance ([dec]) (bay) not supported by this UUT (min equals [dec], max equals [dec])
Explanation Spa bay requested not supported
Recommended Action Select a spa bay in within the appropriate range
Error Message%PLATFORM-FDIAGS-3-SPCL_RAM_AGENTDL_FAILED Download of LC Ram Agent diag_mbus_ram.ucode failed
Explanation Download of diag_mbus_ram.ucode failed Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-SYSDB_BIND_FAILURE Cannot connect to the system data base. Field diagnostics cannot be run.
Explanation Cannot bind to path /admin/oper/instmgr-edm/gl in the system data base. This path is used to get the current setting of the config-register on the standby RP. Internal error: Contact Cisco's TAC. This error could be a software problem. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-SYSLDR_RESULT_CODE_OUT_OF_BOUNDS Result code from sysloader ([dec]) exceeds list of known messages
Explanation Coding violation: Sysldr code returns unexpected cause. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-SYSTEM_ERR_NO_CONTINUE Sysldr reporting error - Field Diags will not commence testing
Explanation Sysldr reporting error - time to quit Field Diags Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-T_O_D_CONVERT_ERR time of day conversion error
Explanation Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT. Internal Time Of Day conversion error
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-UNRECOGNIZED_CARD Card type ([dec]) is NOT recognized
Explanation This card type is not recognized in this version
Recommended Action If available, upgrade to a more recent version of the diags component.
Error Message%PLATFORM-FDIAGS-3-UNSUPP_CARD Card type not supported
Explanation This card type is not supported in this version
Recommended Action if available, upgrade to a more recent version of the diags component.
Error Message%PLATFORM-FDIAGS-4-ERROR_AFTER_RESULTS_REPORT Unexpected return value from reporting results to sysldr: [chars]
Explanation Resulting response from sysldr after reporting final results indicates a non-happy sysldr. Reason in string from sysldr Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-4-SYSDB_ITEM_GET_FAILURE There is a problem with the standby RP state. Field diagnostics cannot be run
Explanation The standby RP does not respond to a configuration query from the active RP. The system data base (sysdb) get of the tuple /admin/oper/instmgr-edm/gl/config-register has failed for the standby RP. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail. Check the current state of the standby RP using the 'show platform' command.
Error Message%PLATFORM-FDIAGS-4-UNEXP_MSV_SUB_MSG Unexpected Misc Services message subtype [dec] received from slot [dec]
Explanation An unexpected MBUS_FDIAG MISC Services message was received from UUT. Possibly a mal-formed or unfinished software enhancement. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-4-UNEXP_SUB_MSG Unexpected message subtype [dec] received from slot [dec]
Explanation An unexpected MBUS_FDIAG message was received from UUT. Possibly a mal-formed or unfinished software enhancement. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-4-WRONG_CONFIG_REG_VAL WARNING: Field diagnostics cannot be run with the current config-register setting
Explanation The router must be configured to auto boot the standby RP from disk if the user wants to run field diagnostics on the standby RP. The config-register setting may have been changed manually to the wrong setting by the user.
Recommended Action Configure the router to disk boot the standby RP. Both the BOOT variable and CONFREG variable must be set correctly. The present settings can be displayed using the 'show variables boot' command when in ADMIN mode. If the BOOT variable appears to be correct then the CONFREG can be set to the correct value (0x102) by issuing the 'config-register 0x102' command in ADMIN mode.
Error Message%PLATFORM-FDIAGS-5-CLEANED_DANGLING_JID_FILE Deleted orphaned Field Diags jid file
Explanation A file from a previous instance of Field Diags was left. We have now deleted it.
Recommended Action No action required
Error Message%PLATFORM-FDIAGS-5-DIAG_ONLY_SUPPORT_IN_IOX_RUNNING_STATE Field Diagnostics can only be invoked when PRP is in IOX Running state.
Explanation The field diagnostics can only be invoked when the PRP is in IOX Running state.
Recommended Action Not applicable, informational message only
Error Message%PLATFORM-FDIAGS-5-DL_DONE Field Diags download completed on slot [dec]. Status: [chars]
Explanation This is a notice field diags has been downloaded to the specified slot. The next step is that field diags will start running on the specified slot.
Recommended Action Nothing. This is a notice that field diags been downloaded to the specified slot. This is only done when a user manually runs field diags from the CLI.
Error Message%PLATFORM-FDIAGS-5-DL_START Field Diags downloading to slot [dec]
Explanation This is a notice that field diags has started to download to the specified slot.
Recommended Action Nothing. This is a notice that field diags has started to download to the specified slot. This is only done when a user manually runs field diags from the CLI.
Error Message%PLATFORM-FDIAGS-5-DONE Field Diags completed for slot [dec]
Explanation This is a notice that field diags has completed on the specified slot. This is the last field diags related message for this slot.
Recommended Action Nothing. This is a notice that field diags has stopped on the specified slot. If field diags passed the slot will automatically reload IOS, if if failed, the card will remain offline until it is manually reset by the user.
Error Message%PLATFORM-FDIAGS-5-HALT_REQUESTED A halt request is present: Shutting down Field Diags process (FSM)
Explanation FSM has detected that a halt is to be initiated
Recommended Action nothing.
Error Message%PLATFORM-FDIAGS-5-IF_LONGEST_TIME_MSG Longest time inactivity ([dec] secs)(~[dec] minutes) just after [[chars]]
Explanation The longest time difference message preceding this
Recommended Action none - informational only
Error Message%PLATFORM-FDIAGS-5-IF_NO_CONSOLE Can not open /dev/console to write, fdiag quits
Explanation Cannot open console for output. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-5-IF_TERMINATED_F_DIAGS_OK Successfully terminated Field Diags (jid equals [dec], Field Diags state file [chars])
Explanation Success in terminating Field Diags instance on a particular slot
Recommended Action None - Action performed successfully.
Error Message%PLATFORM-FDIAGS-5-IF_TOTAL_TEST_TIME Total Test Time: ~[dec] minutes ([dec] seconds)
Explanation Ho long this set of tests ran for
Recommended Action none - informational only
Error Message%PLATFORM-FDIAGS-5-LC_TYPE_DEFAULT_RAM_AGENT Now restoring default ram agent ([chars])
Explanation This card had the diags ram agent loaded for the test, but will now restore the system one Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-5-LC_TYPE_REQUIRES_SPCL_RAM_AGENT Linecard type requires diags_mbus_ram.ucode - downloading
Explanation This card requires a special version of mbus Ram Agent for compatibility with diags for C2W requests for SPA communication Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-5-START Field Diags starting on slot [dec]
Explanation This is a notice that a user has started field diags on the specified slot.
Recommended Action Nothing. This is a notice that field diags was started on the specified slot. Consequently, this slot will be taken offline as the field diags image is downloaded to and run on the slot.
Error Message%PLATFORM-FDIAGS-5-SYSLDR_FINISH_HANDOFF Sysldr notified of completion: params sl:[dec] wait:[hex] diag_stats:[hex] roe_flag:[hex]
Explanation Just finishing diag command and telling sysldr to handle finished diags state on the same slot
Recommended Action nothing
Error Message%PLATFORM-FDIAGS-6-COMPLETE Field Diags COMPLETE on UUT ([chars]) [chars], card type [dec], [chars] s/n [chars]
Explanation Field diagnostics has completed, where the message identifies the final status, the card's numeric and string type as well as its serial number.
Recommended Action None. This is an informational message to log the completion status of field diagnostics.
Error Message%PLATFORM-FDIAGS-6-OUT [chars]
Explanation Non error-specific redirected output from diag process to syslog. This may be test names, progress messages, or failure information generated by the UUT.
Recommended Action No action
Error Message%PLATFORM-FDIAGS-6-RESULT Field Diags COMPLETE on UUT ([chars]) [chars] card type [dec] [[chars]] s/n [chars]
Explanation Field Diagnostics final results
Recommended Action No action
Error Message%PLATFORM-FDIAGS-6-UUT_OUT UUT [chars]: [chars]
Explanation Text output from UUT (Cisco use only) Non error-specific redirected output from diag process to syslog. This may be test names, progress messages, or failure information generated by the UUT.
Recommended Action No action
Error Message%PLATFORM-FDIAGS-6-UUT_OUT_I UUT (init) [chars]: [chars]
Explanation Text output from UUT during init state (Cisco use only) Non error-specific redirected output from diag process to syslog. This may be test names, progress messages, or failure information generated by the UUT.
Recommended Action No action
Error Message%PLATFORM-FDIAGS-7-FORCE_INTO_FSM Forcing into FSM mode, even though sysldr load UUT returned error
Explanation Internal use - ignoring sysldr error, continuing to Field Diags FSM
Recommended Action nothing
Error Message%PLATFORM-FDIAGS-7-NON_HELLO_MSG During Init state, unexpected mbus sub-message [hex] received from slot [dec]
Explanation Field Diags was not expecting this type of message at this time. If this problem persists and diags does not complete, Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
FFQ Messages
Error Message%PLATFORM-FFQ-0-SW_INIT_ERR A software error occurred in the FromFab driver component during initialization: [chars]
Explanation The fabricq_prp_driver process which controls the FromFab driver on the route processor has failed to initalize and cannot recover automatically. This is a software fault. The FromFab driver controls the hardware that receives data from the fabric. It runs in the fabricq_prp_driver process. An unrecoverable failure of the fabricq_prp_driver process may prevent this route processor card from communicating with other cards on the chassis. %s indicates the type failure
Recommended Action Restart the fabricq_prp_driver process with the following command: 'process restart fabricq_prp_driver' If the error message appears again, then: if a redundant route processor card has been configured: 1 - force a failover with the following command in admin mode: 'redundancy switchover' 2 - reload the route processor card that failed with the following command in admin mode: 'reload location RP/0/x/CPU0 ' where x is the slot of route processor that generated the error. if no redundant RP is configured you will need to reboot the router by issuing the reload command. If the error recurs call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-FFQ-3-PAK_FREE_ERR The fabric driver failed to return a buffer to the free list from: [chars]
Explanation The fabric driver has failed to return a packet buffer received from the fabric to the free list. If this error keeps recurring it could result in the depletion of buffer for packet received on the route processor from the fabric. %s is the entity processing the packet.
Recommended Action If this error occurs again copy the system messages exactly as they appear, call your Cisco technical support representative. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-FFQ-4-PAK_INVALID Invalid packet type received from fabric on route processor: [dec]
Explanation FFQ has received an invalid packet type from the fabric. This error will not affect the functionality or stability of the system. %d packet type received
Recommended Action If this error occurs continuously call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FIB_DBG Messages
Error Message%PLATFORM-FIB_DBG-3-ERR_INFO_VERBOSE [chars] [chars] [chars] [dec]
Explanation PLATFORM FIB, error information
Recommended Action Encouter internal error during platform FIB debug initialization. Report to your technical support representative.
FIB_IDB_LIB Messages
Error Message%PLATFORM-FIB_IDB_LIB-3-ERR_STR [chars]: [chars] ([unsigned int])
Explanation PLATFORM FIB, error information
Recommended Action Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transcient or persistent. Report to your technical support representative.
Error Message%PLATFORM-FIB_IDB_LIB-3-ERROR [chars]
Explanation PLATFORM FIB, error
Recommended Action Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transcient or persistent. Report to your technical support representative.
FIB_LTRACE Messages
Error Message%PLATFORM-FIB_LTRACE-3-ERR_INFO_VERBOSE [chars] [dec] [chars] [chars] [dec]
Explanation PLATFORM FIB, error information
Recommended Action Encouter internal error during platform FIB ltrace initialization. Report to your technical support representative.
G_PLIM_QOS Messages
Error Message%PLATFORM-G_PLIM_QOS-2-EVENT_BLOCK An error occurred while handling an event: [chars]
Explanation The event handling function returned an error which could not be handled
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-G_PLIM_QOS-2-THREAD_CREATE_FAILED Could not create a thread - [chars]
Explanation pthread_create function failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-G_PLIM_QOS-3-ERROR [chars]
Explanation An error occured prior to debug service initialization
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-G_PLIM_QOS-3-MALLOC_FAILED Could not allocate memory : [chars]
Explanation Call to malloc() failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
GSR_FIB_STATS_API Messages
Error Message%PLATFORM-GSR_FIB_STATS_API-3-ERROR [chars], error [dec] ([chars])
Explanation Failed to perform the action specified in the error message.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
GSR_IPv6_EA Messages
Error Message%PLATFORM-GSR_IPv6_EA-3-ERROR [chars], error [chars]
Explanation This is an error message in the c12000 platform specific code software to indicate anomolies that are not FATAL. This error is most likely caused by a temporary situation, so is unlikely to re-occur. %s - indicates the reason for the failure. %s - is the decoded error reason.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
GSR_LC_PM Messages
Error Message%PLATFORM-GSR_LC_PM-2-FAULT_LC LC Reset: Reason - [chars]
Explanation Platform manager Error Handling recieved an error from one of the LC devices. The LC MUST be reset.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-GSR_LC_PM-2-FAULT_LC LC Reset: Reason - [chars]
Explanation Platform manager client API received an error from one of the linecard software driver processes that crashed due to a software problem and the LC must be reloaded. The platform-mgr process controls linecard resets for the software driver processes. If a linecard software driver crashes due to a software problem, it can get into a very bad and may be unrecoverable. This action is taken to reload the linecard immediately. %s - Contains the process and reason for the linecard reload.
Recommended Action The linecard will be automatically reloaded to recover. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-GSR_LC_PM-3-CONN_ERR Process connection failed: ([chars]%s)
Explanation The linecard platform-mgr process failed to connect its process to the route processor processes during process initialization. The platform-mgr process runs on the linecard and handles interface information between the route processor and the linecard hardware drivers. It also stores all local linecard information for every interface configured on the linecard. If the platform-mgr fails to connect, no linecard interfaces can be created or deleted. The platform-mgr show commands will also not be available. %s - indicates the reason for the failure. %s - is the decoded error reason.
Recommended Action The System Manager process (sysmgr) may not automatically respawn this process upon failure if processes get out of sync. Otherwise the process should be restarted. Execute 'show process gsr_pm location 0/x/cpu0' to verify that the process is up and running and has been restarted. If it is still non-operational, or has not been automatically restarted, try doing 'process restart gsr_pm location 0/x/cpu0'. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-GSR_LC_PM-3-ENGINE_PORT gsr_lc_pm: [chars] [hex]
Explanation gsr_lc_pm encountered an error and is not able to recover from the error. A reason text will be supplied. call support with this text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-GSR_LC_PM-3-FATAL GSR_LC_PM: Fatal Error, reason equals [chars]
Explanation Platform manager encountered a fatal error and is not able recover from the error. A reason text will be supplied call support with this text.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-GSR_LC_PM-3-FATAL_2 gsr_lc_pm: fatal error encountered, reason equals [chars], errno equals [dec]
Explanation gsr_lc_pm encountered a fatal error and is not able to recover from the error. A reason text will be supplied call support with this text. An integer errno will also be printed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-GSR_LC_PM-3-INIT_ERR Process initialization failed: ([chars]%s)
Explanation The linecard platform-mgr process failed to initialize. The platform-mgr process runs on the linecard and handles interface information between the route processor and the linecard hardware drivers. It also stores all local linecard information for every interface configured on the linecard. If the platform-mgr fails to initialize, no linecard interfaces can be created or deleted. %s - indicates the reason for the failure. %s - is the decoded error reason.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. Execute 'show process gsr_pm location 0/x/cpu0' to verify that the process is up and running. If it is still non-operational, try doing 'process restart gsr_pm location 0/x/cpu0'. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
GSR_LIB Messages
Error Message%PLATFORM-GSR_LIB-3-CONN_ERR Event manager failure: ([chars]%s)
Explanation An error occurred in the system data-base (SysDB) event manager GSR platform library DLL. This DLL controls thread creation, deletion and connections between all other processes and DLL's. If there is a failure in this DLL, a connection will be lost somewhere on the system and failures will occur. %s - indicates the reason for the failure. %s - is the decoded error reason.
Recommended Action The DLL will attempt to recover itself, but if it cannot, the card will probably have to be reloaded as messages will have been lost and the system may be in a bad state. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-GSR_LIB-3-ERROR [chars] ([chars])
Explanation For displaying error conditions with traceback and an error string.
Recommended Action No action is required.
Error Message%PLATFORM-GSR_LIB-3-LR_ERR Logical router failure: ([chars]%s)
Explanation An error occurred during a card state change. This DLL controls the node information during a card state change for logical routers. If there is a failure here, the logical router will lose its nodeid information and will get out of sync with the system. %s - indicates the reason for the failure. %s - is the decoded error reason.
Recommended Action The DLL will attempt to recover itself, but if it cannot, the card will need to be reloaded as the system will be in a bad state. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
GT_I2C Messages
Error Message%PLATFORM-GT_I2C-3-DRV_ERR [chars]
Explanation Error detected when starting the i2c driver
Recommended Action None. Driver will exit and restart automatically.
Error Message%PLATFORM-GT_I2C-3-REWORK_AND_UPGRADE_REQUIRED Detected old PLD version equals [hex] on this board. Please upgrade the PLD to atleast [hex], and check for i2c rework
Explanation Detected that the board has old PLD version. Because of this, we will not be able to detect or correct an i2c bus hang.
Recommended Action Please upgrade PLD and check i2c rework ASAP on this board.
Error Message%PLATFORM-GT_I2C-3-UNRECOVERABLE_BUS_HANG Detected i2c bus hang from which sw is unable to recover.
Explanation As shown in the message.
Recommended Action Physically OIR the RP board which is having the problem.
Error Message%PLATFORM-GT_I2C-7-BUS_HANG Detected i2c bus hang, attempting to unhang the bus......
Explanation Detected i2c bus hang.
Recommended Action Please capture show gt-i2c trace location active-rp and show gt-i2c trace location standby-rp.
Error Message%PLATFORM-GT_I2C-7-BUS_UNHANG_SUCCESS Successfully unhung the i2c bus
Explanation As shown in the message.
Recommended Action Physically OIR the RP board which is having the problem.
HBAGENT Messages
Error Message%PLATFORM-HBAGENT-2-FATAL Fatal error: [chars] [chars], exiting
Explanation Fatal internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-HBAGENT-2-NODE_RELOAD Reload notification received. Reloading in [dec] secs
Explanation Message indicating that the node has received a reload notification and the node is going to reload soon.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-HBAGENT-3-API_FAILURE [chars], error: [chars]
Explanation An infrastructure component has returned an error to the MBI infrastructure, so it may not be able to continue with the current operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-HBAGENT-3-THREAD_CREATE Failed to create a thread for [chars]: [chars]
Explanation This may be a problem with lack of resources. The MBI infrastructure will be unable to carry out all of its expected functionality.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-HBAGENT-4-ATTACH_RECONNECT_HANDLER Failed to attach a reconnect handler to ethernet server coid. If ethernet server restarts, heartbeat agent may not be able to receive/write messages [chars]
Explanation Failed to attach a reconnect handler to ethernet server coid. If ethernet server restarts, heartbeat agent may not be able to receive/write messages.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-HBAGENT-4-INIT_LTRACE Failed to initialize hbagent tracing: ([dec] : [chars])
Explanation The process will continue with it's business, however, cause of why hbagent was not able to initialize tracing should be tracked down. As result of this error, hbagent will not have any tracings.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-HBAGENT-4-SET_HEARTBEAT_PRIORITY Unable to set the heartbeat pulse through ethernet server to high priority. Proceeding with normal priority: [chars]
Explanation Unable to set the heartbeat pulse of this node to high priority. Proceeding with default priority, however in a high CPU consumption, this node's heartbeat pulse may get lost, causing this node to get reloaded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-HBAGENT-4-SET_THREAD_PRIORITY Unable to set the thread priority to high. Proceeding with normal priority: [chars]
Explanation Unable to set the heartbeat pulse of this node to high priority. Proceeding with default priority, however in a high CPU consumption, this node's heartbeat pulse may get lost, causing this node to get reloaded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-HBAGENT-7-RELOAD_NOTIFICATION_TEST Received a test reload notification, ignore.
Explanation The node received a test reload notification just to check functionality. The notification is ignored.
Recommended Action No action is required.
HFR_IP_EA Messages
Error Message%PLATFORM-HFR_IP_EA-3-CRITICAL HFR IP-EA: Critical error: [chars]
Explanation HFR IP-EA, Critical error
Recommended Action *SUPPORT*
Error Message%PLATFORM-HFR_IP_EA-3-ERROR1 HFR IP-EA: Error: [chars] [dec]
Explanation HFR IP-EA, error
Recommended Action *SUPPORT*
Error Message%PLATFORM-HFR_IP_EA-3-ERROR2 HFR IP-EA: Error: [chars]
Explanation HFR IP-EA, error
Recommended Action *SUPPORT*
Error Message%PLATFORM-HFR_IP_EA-5-DEBUG HFR IP-EA: Debug info: [chars]
Explanation HFR IP-EA, Debug information
Recommended Action *SUPPORT*
HFR_IPV6_EA Messages
Error Message%PLATFORM-HFR_IPV6_EA-3-CRITICAL HFR IP-EA: Critical error: [chars]
Explanation HFR IP-EA, Critical error
Recommended Action *SUPPORT*
Error Message%PLATFORM-HFR_IPV6_EA-3-ERROR1 HFR IP-EA: Error: [chars] [dec]
Explanation HFR IP-EA, error
Recommended Action *SUPPORT*
Error Message%PLATFORM-HFR_IPV6_EA-3-ERROR2 HFR IP-EA: Error: [chars]
Explanation HFR IP-EA, error
Recommended Action *SUPPORT*
Error Message%PLATFORM-HFR_IPV6_EA-5-DEBUG HFR IP-EA: Debug info: [chars]
Explanation HFR IP-EA, Debug information
Recommended Action *SUPPORT*
HFR_L2FIB_METRO_SHOW Messages
Error Message%PLATFORM-HFR_L2FIB_METRO_SHOW-3-ERROR HFR_L2FIB_METRO_SHOW: [chars] , [chars]
Explanation HFR_L2FIB_METRO_SHOW encountered an error
Recommended Action Please enable 'debug im api errors', 'debug sysdb access ...' and capture the output.
Error Message%PLATFORM-HFR_L2FIB_METRO_SHOW-7-USAGE hfr_l2fib_metro_show: invalid option passed to hfr_l2fib_metro_show command. [chars]
Explanation Startup option supplied to HFR_L2FIB_METRO_SHOW is not valid.
Recommended Action Please re-enter the correct option as described in the usage message 'Usage: hfr_l2fib_metro_show [-N node name]' Example: sh controllers hfr int Ten0/2/0/0 loc 0/2/cpu0, or run hfr_l2fib_metro_show -N 33
HFR_LCPM_SHOW Messages
Error Message%PLATFORM-HFR_LCPM_SHOW-3-ERROR HFR_PM_SHOW: [chars] , [chars]
Explanation HFR_PM_SHOW encountered an error
Recommended Action Please enable 'debug im api errors', 'debug sysdb access ...' and capture the output.
Error Message%PLATFORM-HFR_LCPM_SHOW-7-USAGE hfr_pm_show: invalid option passed to hfr_pm_show command. [chars]
Explanation Startup option supplied to HFR_PM_SHOW is not valid.
Recommended Action Please re-enter the correct option as described in the usage message 'Usage: hfr_pm_show [-I intf name] | [-N node name]' Example: sh controllers hfr int Ten0/2/0/0 loc 0/2/cpu0, or run hfr_lcpm_show -I TenGigE0_2_0_0 -N 33
HFR_MPLS_EA Messages
Error Message%PLATFORM-HFR_MPLS_EA-3-ERR PLATFORM MPLS-EA: [chars]
Explanation CRS-1 MPLS-EA, error
Recommended Action *SUPPORT*
Error Message%PLATFORM-HFR_MPLS_EA-3-ERRSTR PLATFORM MPLS-EA: [chars] Error: [chars]([dec])
Explanation CRS-1 MPLS-EA, error
Recommended Action *SUPPORT*
Error Message%PLATFORM-HFR_MPLS_EA-6-INFO PLATFORM MPLS-EA: [chars]: [chars]
Explanation CRS-1 MPLS-EA, Debug information
Recommended Action *SUPPORT*
HFR_PM_TEST Messages
Error Message%PLATFORM-HFR_PM_TEST-3-ERROR hfr_pm_test: fatal error encountered, reason equals [chars]
Explanation hfr_pm test encountered a fatal error and is not able recover from the error. A reason text will be supplied call support with this text.
Recommended Action This is just test software which the customer does not get. so there is np actiom required.
Error Message%PLATFORM-HFR_PM_TEST-3-ERROR_2 hfr_pm_test: fatal error encountered, reason equals [chars], errno equals [dec]
Explanation hfr_pm_test encountered a fatal error and is not able to recover from the error. A reason text will be supplied call support with this text. An integer errno will also be printed.
Recommended Action This is just test software which the customer does not get.
HFR_PM Messages
Error Message%PLATFORM-HFR_PM-3-BAD_PMLIB_SERVER_CONTEXT [chars], svr_ctx equals 0x[pointer], expected_ctx equals 0x[pointer]
Explanation The Platform Manager detected a software error where the received library server context does not match the expected value.
Recommended Action No action is required as the software has rejected the transaction request. Please collect the error message, traceback and 'show log'
Error Message%PLATFORM-HFR_PM-3-ERR_FAULT_FROM_DEVICE Device [chars] #[dec] has a fault equals [chars]. Resetting
Explanation The specified device has a fault that affects the card functionality. The card node will be reset and ideally the problem will not happen again when it comes back up.
Recommended Action If the node keeps on resetting itself then please collect 'show log' output and contact customer support to diagnose the problem.
Error Message%PLATFORM-HFR_PM-3-ERROR hfr_pm: error encountered, reason equals [chars], errno equals [dec]
Explanation hfr_pm encountered a fatal error and is not able to recover from the error. A text reason and error number will be supplied to describe the error.
Recommended Action No action is required as the software should be able to recover from this error. Please collect 'show log location r/s/i' output, and 'show memory summary location r/s/i from that location.
Error Message%PLATFORM-HFR_PM-3-ERROR_INIT hfr_pm: error encountered, reason equals [chars]
Explanation Platform Manager encountered an initialization error A reason text will be supplied to describe the error.
Recommended Action No action is required as the software should be able to recover from this error. Please collect 'show log location r/s/i' output, and 'show memory summary location r/s/i from that location.
Error Message%PLATFORM-HFR_PM-3-MALLOC_FAILED fatal memory allocation error for [dec] bytes
Explanation Platform Manager encountered a fatal memory allocation error
Recommended Action Please collect 'show memory summary location R/S/I' to see how much memory is left on that location/node.
Error Message%PLATFORM-HFR_PM-4-WARNING Platform Manager warning: [chars]
Explanation The Platform Manager encountered an provisioning warning.
Recommended Action No action is required as the software should be able to recover from this error. Please collect 'show log location r/s/i'
Error Message%PLATFORM-HFR_PM-4-WARNING Platform Manager warning: [chars]
Explanation The Platform Manager encountered an internal software warning. The software will reattempt to fix the cause of this warning.
Recommended Action No action is required as the software should be able to recover from this error. Please collect 'show log location r/s/i'
Error Message%PLATFORM-HFR_PM-7-ERROR Platform Manager error, reason equals [chars], errno equals [dec]
Explanation The Platform Manager encountered an internal software error.
Recommended Action No action is required as the software should be able to recover from this error. Please collect 'show log location r/s/i' output, and 'show memory summary location r/s/i from that location.
Error Message%PLATFORM-HFR_PM-7-ERROR_INIT Platform Manager error, reason equals [chars]
Explanation The Platform Manager encountered an internal software initialization error.
Recommended Action No action is required as the software should be able to recover from this error. Please collect 'show log location r/s/i' output, and 'show memory summary location r/s/i from that location.
I2C Messages
Error Message%PLATFORM-I2C-2-VOLTAGE_CHECKING_FAILED Voltages are not within thresholds
Explanation As soon as power is asserted on S2/Jacket cards, s/w will read voltage sensors on the host board. If for any reason reading voltages failed or voltage read are not within +-10% range, then this message will be displayed.
Recommended Action Please collect following traces and try to recover by reloading the S2/Jacket card.
Error Message%PLATFORM-I2C-2-VOLTAGE_SUPPLY_FAILED Voltage [chars] equals [dec] not within thresholds
Explanation As soon as power is asserted on S2/Jacket cards, s/w will read voltage sensors on the host board. If for any reason reading voltages failed or voltage read are not within +-10% range, then this message will be displayed. It will also list which device and value read.
Recommended Action Please collect following traces and try to recover by reloading the S2/Jacket card.
Error Message%PLATFORM-I2C-3-BP_EN_ERROR Error while setting PLD resgister to enable/disable access to backplane: unable to [chars] mastership
Explanation Error while trying to grab or release the lock.
Recommended Action No action is required.
Error Message%PLATFORM-I2C-3-EMPTY_BIT_NOT_CLEARED_ERROR I2C server process restarting due to unrecoverable EMPTY Bit Not Cleared errors
Explanation I2C operation failed because the EMPTY bit is still set after multiple retries. I2C server process will automatically restart to recover from this error condition.
Recommended Action No action is required.
Error Message%PLATFORM-I2C-3-ERR_INIT i2c server process exiting, reason: [chars]
Explanation The i2c server process cannot continue due to error condition mentioned in the message.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover.
Error Message%PLATFORM-I2C-3-LC_BAD_VRM_INFO LC power-up failed because - [chars] on [chars] is bad - as indicated by power good registers
Explanation None
Recommended Action Replace the bad part for LC to work.
Error Message%PLATFORM-I2C-3-LC_POWER_FAIL LC power-up failed because - [chars] - as indicated by power status registers
Explanation None
Recommended Action Replace the bad part for LC to work.
Error Message%PLATFORM-I2C-7-BOARD_POWERUP_FAIL Board not powered up (DC_DC_en not asserted) after max timeout of [dec] seconds
Explanation None
Recommended Action Check why the board is not yet powered.
Error Message%PLATFORM-I2C-7-BOARD_POWERUP_NOT_HAPPENED Board not powered up (DC_DC_en not asserted) after [dec] seconds, resending pulse to shelfmgr to powerup this board
Explanation None
Recommended Action Check why the board is not yet powered.
Error Message%PLATFORM-I2C-7-LC_POWERUP_CHECK_FAIL Unable to check LC power status registers because [chars]
Explanation None
Recommended Action Manually check why the board is not yet powered.
Error Message%PLATFORM-I2C-7-SEND_PULSE_FAIL Failed to send pulse because [chars] failed
Explanation None
Recommended Action Check the path of file specified for download
INTEG_SWITCH Messages
Error Message%PLATFORM-INTEG_SWITCH-2-LINK_SHUT_DOWN Inter-rack switch port [dec] state changed to ADMIN_DOWN
Explanation The inter-rack switch port was administratively shut down.
Recommended Action No action is required.
Error Message%PLATFORM-INTEG_SWITCH-2-STACKING_LINK_DOWN Broadcom 5690 stacking link down
Explanation The driver was unable to successfully initialise the stacking link
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
INV Messages
Error Message%PLATFORM-INV-6- OIR: Node [chars] inserted
Explanation --
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-INV-6-CF_OIRIN Compact Flash is inserted on Node: [chars]
Explanation Compact Flash entity is inserted into the RSP invmgr_agent collects the CF data whenever it is inserted.
Recommended Action Debug message only. No action is required.
Error Message%PLATFORM-INV-6-CF_OIROUT Compact Flash is removed on Node: [chars]
Explanation Compact Flash entity is removed from the RSP invmgr_agent deletes the CF data whenever it is removed.
Recommended Action Debug message only. No action is required.
Error Message%PLATFORM-INV-6-NODE_STATE_CHANGE Node: [chars], state: [chars]
Explanation Inventory Manager output this informational message whenever there is a card state change. This message will indicate the current card state.
Recommended Action No action is required.
Error Message%PLATFORM-INV-6-NODE_STATE_CHANGE Node: [chars], state: [chars]
Explanation Inventory Manager output this informational message whenever there is a card state change. This message will indicate the current card state.
Recommended Action No action is required.
Error Message%PLATFORM-INV-6-NODE_STATE_CHANGE Node: [chars], state: [chars]
Explanation Inventory Manager output this informational message whenever there is a card state change. This message will indicate the current card state.
Recommended Action No action is required.
Error Message%PLATFORM-INV-6-OIRIN OIR: Node [chars] inserted
Explanation Entity specified in the messages is inserted into the chassis and inventory manager is updated. This message is used by CWI/CTM to determine when the entity-related information (read from the EEPROM) is available in inventory database.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-INV-6-OIRIN OIR: Card [chars] inserted
Explanation Entity specified in the messages is inserted into the chassis and inventory manager is updated. This message is used by CWI/CTM to determine when the entity-related information (read from the EEPROM) is available in inventory database.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-INV-6-OIRIN OIR: Node [chars] inserted
Explanation Entity specified in the messages is inserted into the chassis and inventory manager is updated. This message is used by CWI/CTM to determine when the entity-related information (read from the EEPROM) is available in inventory database.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-INV-7-ERR [chars]
Explanation Failure in Inventory Manager resulting in error condition
Recommended Action No action is required.
Error Message%PLATFORM-INV-7-ERR [chars]
Explanation Failure in Inventory Manager resulting in error condition
Recommended Action No action is required.
Error Message%PLATFORM-INV-7-ERR [chars]
Explanation Failure in Inventory Manager resulting in error condition
Recommended Action No action is required.
Error Message%PLATFORM-INV-7-ERR_DLL [chars], reason: [chars]
Explanation Failure in Inventory Manager dllmain function call
Recommended Action No action is required.
Error Message%PLATFORM-INV-7-ERR_DLL [chars], reason: [chars]
Explanation Failure in Inventory Manager dllmain function call
Recommended Action No action is required.
Error Message%PLATFORM-INV-7-ERR_DLL [chars], reason: [chars]
Explanation Failure in Inventory Manager dllmain function call
Recommended Action No action is required.
Error Message%PLATFORM-INV-7-ERR_EDM_CREATE Unable to register for invmgr edm event notification
Explanation Failure in Inventory Manager event creation
Recommended Action No action is required.
Error Message%PLATFORM-INV-7-ERR_EDM_CREATE Unable to register for invmgr edm event notification
Explanation Failure in Inventory Manager event creation
Recommended Action No action is required.
Error Message%PLATFORM-INV-7-ERR_EDM_CREATE Unable to register for invmgr edm event notification
Explanation Failure in Inventory Manager event creation
Recommended Action No action is required.
Error Message%PLATFORM-INV-7-ERR_EDM_OPEN Unable to start invmgr edm communication channel
Explanation Failure in Inventory Manager event connect open
Recommended Action No action is required.
Error Message%PLATFORM-INV-7-ERR_EDM_OPEN Unable to start invmgr edm communication channel
Explanation Failure in Inventory Manager event connect open
Recommended Action No action is required.
Error Message%PLATFORM-INV-7-ERR_EDM_OPEN Unable to start invmgr edm communication channel
Explanation Failure in Inventory Manager event connect open
Recommended Action No action is required.
Error Message%PLATFORM-INV-7-ERR_MEM_ALLOC Unable to allocate memory
Explanation Failure in Inventory Manager memory allocation error occurred
Recommended Action No action is required.
Error Message%PLATFORM-INV-7-ERR_MEM_ALLOC Unable to allocate memory
Explanation Failure in Inventory Manager memory allocation error occurred
Recommended Action No action is required.
Error Message%PLATFORM-INV-7-ERR_MEM_ALLOC Unable to allocate memory
Explanation Failure in Inventory Manager memory allocation error occurred
Recommended Action No action is required.
Error Message%PLATFORM-INV-7-ERR_RACK_CREATE Inventory Creation of RACK failed.
Explanation The RACK entry is a must in inventory management
Recommended Action None. Inventory Manager process will restart automatically
Error Message%PLATFORM-INV-7-ERR_RACK_CREATE Inventory Creation of RACK failed.
Explanation The RACK entry is a must in inventory management
Recommended Action None. Inventory Manager process will restart automatically
Error Message%PLATFORM-INV-7-ERR_RACK_CREATE Inventory Creation of RACK failed.
Explanation The RACK entry is a must in inventory management
Recommended Action None. Inventory Manager process will restart automatically
Error Message%PLATFORM-INV-7-SYSDB_ERR [chars], reason: [chars]
Explanation Sysdb api call failed
Recommended Action No action is required.
Error Message%PLATFORM-INV-7-SYSDB_ERR [chars], reason: [chars]
Explanation Sysdb api call failed
Recommended Action No action is required.
Error Message%PLATFORM-INV-7-SYSDB_ERR [chars], reason: [chars]
Explanation Sysdb api call failed
Recommended Action No action is required.
INVMGR Messages
Error Message%PLATFORM-INVMGR-2-ERR_SYSDB_REG_NOTIFY SysDB registration for notification on [chars] failed. Error - [chars]
Explanation This message indicates that registration for notification failed for the tuple specified. %s - tuple %s - indicates the internal error message
Recommended Action System manager will automatically respawn this process, up to a fixed number of times, when this error is encountered to recover. Execute 'show process invmgr location 0/x/cpu0' to verify that the process is up and running. If it is non-operational, do 'process restart invmgr location 0/x/cpu0' to manually restart it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-INVMGR-3-ERR_EEPROM_READ EEPROM/NVRAM read failed. Error - [chars], [dec]
Explanation EEPROM/NVRAM read failed for a chassis, card, or SPA. Inventory information would be incomplete. This would affect information provided to CLI 'show inventory', inventory schema, and the entity related MIBs. %s - indicates the internal error string %d - indicates the internal error code
Recommended Action Check the card/chassis/SPA.
Error Message%PLATFORM-INVMGR-3-ERR_INIT Initialization failed. [chars]. [chars]
Explanation This message indicates that process invmgr failed to initialize and exited. Inventory information would not be available. This would affect CLI 'show inventory', inventory schema, and the entity related MIBs. Some reasons are: 1) System manager process ready notification failed 2) Error waiting for secondary RP to go active 3) Internal API error %s - indicates the internal message. %s - indicates the internal error reason.
Recommended Action System manager will automatically respawn this process, up to a fixed number of times, when this error is encountered to recover. Execute 'show process invmgr location 0/x/cpu0' to verify that the process is up and running. If it is non-operational, do 'process restart invmgr location 0/x/cpu0' to manually restart it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-INVMGR-3-ERR_MEM_ALLOC [chars], slot [dec]
Explanation This message indicates memory allocation failure. Inventory information for the specified slot would be incomplete. This would affect information provided to CLI 'show inventory', inventory schema, and the entity related MIBs for the specified slot. %s indicates the internal data structure that failed allocation for.
Recommended Action Reduce other system activity to ease memory demands and restart process invmgr via CLI 'process restart invmgr' to recover. If conditions warrant and minimum memory requirements not met, upgrade to a larger memory configuration.
Error Message%PLATFORM-INVMGR-3-ERR_NODEID_CREATE Node ID of slot [dec]. Error - [chars]
Explanation This message indicates a failure in creating the node ID of the specified slot. Inventory information for the specified slot would be incomplete. This would affect information provided to CLI 'show inventory', inventory schema, and the entity related MIBs for the specified slot. %s - indicates the internal error reason.
Recommended Action Try restarting the invmgr process via CLI 'process restart invmgr' to recover. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-INVMGR-3-ERR_OBJECT_CREATE Slot [dec]. Error - [chars]
Explanation This message indicates a failure in creating the object for the specified slot. The entry is not added to the inventory. %s - indicates an internal message
Recommended Action Issue may be due to lack of memory in the system. If memory shortage is the cause, reduce other system activity to ease memory demands and restart process invmgr via CLI 'process restart invmgr' to recover. If conditions warrant and minimum memory requirements not met, upgrade to a larger memory configuration.
Error Message%PLATFORM-INVMGR-3-ERR_SENSOR_CREATE Slot [dec] sensor [dec] object create failed
Explanation This message indicates a failure in creating the sensor object for the specified slot and sensor. The sensor entry is not added to the inventory.
Recommended Action Issue may be due to lack of memory in the system. If memory shortage is the cause, reduce other system activity to ease memory demands and restart process invmgr via CLI 'process restart invmgr' to recover. If conditions warrant and minimum memory requirements not met, upgrade to a larger memory configuration.
Error Message%PLATFORM-INVMGR-3-ERR_SYSDB_BIND SysDB bind to [chars] failed. Error - [chars]
Explanation This message indicates bind to the specified path failed. Inventory information would be incomplete. This would affect information provided to CLI 'show inventory', inventory schema, and the entity related MIBs. %s - indicates the internal error reason.
Recommended Action Try restarting the invmgr process via CLI 'process restart invmgr' to recover. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-INVMGR-5-OIRIN OIR: Node [chars] inserted
Explanation Entity specified in the messages is inserted into the chassis and inventory manager is updated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-INVMGR-5-OIROUT OIR: Node [chars] removed
Explanation Entity specified in the messages is removed from the chassis.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-INVMGR-6-NODE_STATE_CHANGE Node: [chars], state: [chars]
Explanation This message indicates the node state (eg. IOS XR RUN, MBI_RUNNING). A node being a card, SPA, etc. %s - indicates the node/location in rack/slot/instance format %s - indicates the state
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-INVMGR-7-ERR_API [chars] failed for slot [dec]
Explanation The sensor entry will not be added in inventory
Recommended Action Check the memory on the system
Error Message%PLATFORM-INVMGR-7-ERR_NODEID Extract fields from node ID [dec] failed. Error - [chars]
Explanation This message indicates a failure in extracting fields from the node ID. Inventory information for the specified node ID, if valid, would be incomplete. This would affect information provided to CLI 'show inventory', inventory schema, and the entity related MIBs for the specified node. %s - indicates the internal error.
Recommended Action Try restarting the invmgr process via CLI 'process restart invmgr' to recover. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-INVMGR-7-FAIL [chars]
Explanation This message indicates a failure in inventory manager. This is an internal debug message. %s - indicates the failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
MBI_HELLO Messages
Error Message%PLATFORM-MBI_HELLO-2-FATAL Fatal error: [chars] [chars], exiting
Explanation Fatal internal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBI_HELLO-2-NODE_RELOAD Reload notification received. Reloading in [dec] secs
Explanation Message indicating that the node has received a reload notification and the node is going to reload soon.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBI_HELLO-2-NODE_RELOAD Reload notification received. Reloading card in [dec] secs
Explanation Message indicating that the mbi-hello on the card has received a reload notification from sysldr for powering off the card and the card is going to reload soon. Card state is MBI_RUNNING
Recommended Action Sysldr log needs to be looked into to investigate on the node reload cause. As, sysldr requests to reload the card for various reasons.
Error Message%PLATFORM-MBI_HELLO-2-NODE_RELOAD_NOW Node delay time over, reloading now
Explanation Message indicating that the node has received a reload notification from the sysldr and the node is going to reload as the delay is over. This message is logged after the delay over since the NODE_RELOAD message is logged.
Recommended Action Sysldr log needs to be looked into to investigate on the node reload cause. As, sysldr requests to reload the card for various reasons.
Error Message%PLATFORM-MBI_HELLO-3-API_FAILURE Unable to [chars], error: [chars]
Explanation An infrastructure component has returned an error to the MBI infrastructure, so it may not be able to continue with the current operation.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBI_HELLO-3-CLOCK_FAIL Clock operation failed ([chars]): [chars]
Explanation A clock operation failed. This should have only cosmetic effect on the MBI infrastructure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBI_HELLO-3-ERR_SHMEM_ALLOC Failed to allocate shared memory. Error: [chars]
Explanation mbi-hello is not able to allocate shared memory to share information with other processes.
Recommended Action This indicates a low memory condition. Memory on the box must be running low - are there services that can be stopped, or can more memory be added?
Error Message%PLATFORM-MBI_HELLO-3-ERROR [chars] ([chars])
Explanation Error in mbi-hello processing The error reason is described in the message log itself.
Recommended Action NONE
Error Message%PLATFORM-MBI_HELLO-3-ETHSERVER_CONNECT The MBI infrastructure was unable to connect to the Ethernet Server error: [chars].
Explanation A communication problem occurred between the MBI client and Ethernet server. The MBI operation in progress will not be carried out.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBI_HELLO-3-ETHSERVER_WRITE The MBI infrastructure was unable to send a message to the Ethernet Server, error: [chars].
Explanation A communication problem occurred between the MBI client and Ethernet server. The MBI operation in progress will not be carried out.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBI_HELLO-3-INIT_ERR [chars] ([chars])
Explanation Something failed in the initialization. The process will exit as an attempt to recover.
Recommended Action Collect the traces using the command 'show tech shelf' in admin mode. Notify your customer support representative.
Error Message%PLATFORM-MBI_HELLO-3-MALLOC_FAIL Failed to allocate [unsigned int] bytes of memory
Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action This indicates a low memory condition. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-MBI_HELLO-3-MSG_SEND_FAIL The MBI infrastructure was unable to send a message to the MBI Hello server, error: [chars].
Explanation A communication problem occurred between the MBI client and server. The MBI operation in progress will not be carried out.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBI_HELLO-3-REQUEST_NETMGR_MOUNTPOINT_FAIL Failed to request netmgr mountpoint
Explanation Failed to request netmgr mountpoint.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBI_HELLO-3-SERVER_CONNECT_FAIL The MBI infrastructure was unable to connect to the MBI Hello server, error: [chars].
Explanation A communication problem occurred between the MBI client and server, perhaps because the communications infrastructure is not yet up. The MBI operation in progress will not be carried out.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBI_HELLO-3-THREAD_CREATE Failed to create a thread for [chars]: [chars]
Explanation This may be a problem with lack of resources. The MBI infrastructure will be unable to carry out all of its expected functionality.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBI_HELLO-3-TIMER_TIMEOUT Timer timed out from server : [chars]
Explanation Timer timed out.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBI_HELLO-4-ATTACH_RECONNECT_HANDLER Failed to attach a reconnect handler to ethernet server coid. If ethernet server restarts, heartbeat agent may not be able to receive/write messages: [chars]
Explanation Failed to attach a reconnect handler to ethernet server coid. If ethernet server restarts, heartbeat agent may not be able to receive/write messages.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBI_HELLO-4-INIT_LTRACE Failed to initialize mbi_hello tracing: ([dec] : [chars])
Explanation The process will continue with it's business, however, cause of why mbi-hello was not able to initialize tracing should be tracked down. As result of this error, mbi-hello will not have any tracings.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBI_HELLO-4-SET_HEARTBEAT_PRIORITY Unable to set the heartbeat pulse through ethernet server to high priority. Proceeding with normal priority: [chars]
Explanation Unable to set the heartbeat pulse of this node to high priority. Proceeding with default priority, however in a high CPU consumption, this node's heartbeat pulse may get lost, causing this node to get reloaded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBI_HELLO-4-SET_THREAD_PRIORITY Unable to set the thread priority to high. Proceeding with normal priority: [chars]
Explanation Unable to set the heartbeat pulse of this node to high priority. Proceeding with default priority, however in a high CPU consumption, this node's heartbeat pulse may get lost, causing this node to get reloaded.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBI_HELLO-6-LTRACE_INIT_ERR Failed to initialize ltrace buffer in [chars]. Error: [chars]
Explanation Ltrace buffer will not be available. Debuggability will be reduced because of lacking of ltrace buffer.
Recommended Action This indicates a low memory condition. Memory on the box must be running low - are there services that can be stopped, or can more memory be added?
Error Message%PLATFORM-MBI_HELLO-7-ERR_MEM_ALLOC Failed to allocate [unsigned int] bytes of memory
Explanation The debug ping to mbi-hello process could not be accomplished because of a low memory condition.
Recommended Action This indicates a low memory condition. Memory on the box must be running low - are there services that can be stopped, or can more memory be added?
Error Message%PLATFORM-MBI_HELLO-7-ERR_MSG_SEND The MBI infrastructure was unable to send a message to the MBI Hello server, error: [chars].
Explanation A communication problem occurred between the MBI client and server. The MBI operation in progress will not be carried out.
Recommended Action The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.
Error Message%PLATFORM-MBI_HELLO-7-ERR_NETMGR_MOUNTPOINT_REQUEST Failed to request QNX net manager mountpoint
Explanation Failed to request netmgr mountpoint. The debug ping to mbi-hello process could not be accomplished.
Recommended Action The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.
Error Message%PLATFORM-MBI_HELLO-7-ERR_SERVER_CONNECT The MBI infrastructure was unable to connect to the MBI Hello server, error: [chars].
Explanation A communication problem occurred between the MBI client and server, perhaps because the communications infrastructure is not set up. The MBI operation in progress will not be carried out.
Recommended Action The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.
Error Message%PLATFORM-MBI_HELLO-7-HBAGENT_EXISTS Mbi-hello was restarted, but detected that hbagent is up and functioning already. Proceeding with passive mode
Explanation Mbi-hello process was restarted. However, it detected that the hbagent process is already functioning. Hence mbi-hello is going into passive mode by design.
Recommended Action No action is required.
Error Message%PLATFORM-MBI_HELLO-7-INFO_CREATE_SUCCESS MBI-Hello: Successful creation of [chars]. Attempt number [dec]
Explanation Successful creation of mbi-hello LWM channel for communication.
Recommended Action NONE
Error Message%PLATFORM-MBI_HELLO-7-RELOAD_NOTIFICATION_TEST Received a test reload notification, ignore.
Explanation The node received a test reload notification just to check functionality. The notification is ignored.
Recommended Action No action is required.
Error Message%PLATFORM-MBI_HELLO-7-TIMER_TIMEOUT The MBI infrastructure timer timed out from server : [chars]
Explanation Timer timed out between the MBI client and server, perhaps because the communications infrastructure is not set up. The MBI operation in progress will not be carried out.
Recommended Action The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.
Error Message%PLATFORM-MBI_HELLO-7-WARNING [chars]
Explanation Error in thread creation for mbi-hello process. The error reason is described in the message log itself.
Recommended Action NONE
MBI_LIB_ACCESS Messages
Error Message%PLATFORM-MBI_LIB_ACCESS-3-MSG_SEND_FAIL The MBI infrastructure was unable to send a message to the MBI Hello server, error: [chars].
Explanation A communication problem occurred between the MBI client and server. The MBI operation in progress will not be carried out.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBI_LIB_ACCESS-3-SERVER_CONNECT_FAIL The MBI infrastructure was unable to connect to the MBI Hello server, error: [chars].
Explanation A communication problem occurred between the MBI client and server, perhaps because the communications infrastructure is not yet up. The MBI operation in progress will not be carried out.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBI_LIB_ACCESS-7-ERR_MSG_SEND The MBI infrastructure was unable to send a message to the MBI Hello server, error: [chars].
Explanation A communication problem occurred between the MBI client and server. The MBI operation in progress will not be carried out.
Recommended Action The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.
Error Message%PLATFORM-MBI_LIB_ACCESS-7-ERR_SERVER_CONNECT The MBI infrastructure was unable to connect to the MBI Hello server, error: [chars].
Explanation A communication problem occurred between the MBI client and server, perhaps because the communications infrastructure is not set up. The MBI operation in progress will not be carried out.
Recommended Action The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.
MBI_LIB Messages
Error Message%PLATFORM-MBI_LIB-3-MSG_SEND_FAIL The MBI infrastructure was unable to send a message to the MBI Hello server, error: [chars].
Explanation A communication problem occurred between the MBI client and server. The MBI operation in progress will not be carried out.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBI_LIB-3-SERVER_CONNECT_FAIL The MBI infrastructure was unable to connect to the MBI Hello server, error: [chars].
Explanation A communication problem occurred between the MBI client and server, perhaps because the communications infrastructure is not yet up. The MBI operation in progress will not be carried out.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBI_LIB-4-CLOCK_FAIL The MBI infrastructure was unable to determine the time, error: [chars]
Explanation The infrastructure is behaving incorrectly. This will not affect the operation of the MBI infrastructure, but messages and logs may not contain timestamps.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
MBIMGR Messages
Error Message%PLATFORM-MBIMGR-3-COPY_MBI_FILE_NAME_FAIL [chars]The MBI infrastructure was unable to copy the MBI file name, error: [chars].
Explanation The MBI file name is possibly too large or invalid. The MBI operation in progress may not be carried out.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBIMGR-3-DEFAULT_MBI_FAIL [chars]The MBI infrastructure failed to obtain the default MBI for card class [hex], error: [chars].
Explanation The default MBI is either unknown or missing. The MBI operation in progress may not be carried out.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBIMGR-3-FAILED_TO_CALCULATE_MD5 [chars]Failed to calculate MD5 value from path ([chars]): [chars]
Explanation Either the path is invalid, or the infrastructure is behaving incorrectly. The MBI operation in progress may not be carried out.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBIMGR-3-FAILED_TO_COMPARE_MD5 [chars]The MBI infrastructure failed to compare MD5 values between the boot request MBI ([chars]) and the MBI stored in dSC ([chars]), error: [chars]. Using the MBI ([chars]) from dSC.
Explanation Either the MD5 values are invalid, or the infrastructure is behaving incorrectly. The MBI operation in progress may not be carried out.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBIMGR-3-IGNORING_MBI [chars]The MBI infrastructure detected an abnormality with the MBI passed ([chars]). Ignoring this MBI. Error: [chars].
Explanation The MBI passed was not in the expected form. The MBI infrastructure will ignore this MBI and most likely new MBI will be downloaded from dSC as result.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBIMGR-3-INVALID_ARG [chars]An invalid argument was passed to the MBI infrastructure.
Explanation An internal error has occurred in an application that has caused it to pass invalid data to the MBI infrastructure. The MBI operation in progress may not be carried out.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBIMGR-3-MALLOC_FAIL [chars]Unable to allocate [unsigned int] bytes of memory
Explanation The requested operation could not be accomplished because of a low memory condition.
Recommended Action This indicates a low memory condition. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-MBIMGR-3-NODEID_EXTRACT_FAIL [chars]The infrastructure failed to extract the R/S/I elements of node [dec] for for the MBI infrastructure, error: [chars].
Explanation Either an invalid location is being queried, or the infrastructure is behaving incorrectly. The MBI operation in progress may not be carried out.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBIMGR-3-NODEID_FAIL [chars]The infrastructure failed to inform the MBI infrastructure of the location where it is running, error: [chars].
Explanation Either an invalid location is being queried, or the infrastructure is behaving incorrectly. The MBI operation in progress may not be carried out.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBIMGR-3-NODEID_TO_IP_ADDR_FAIL [chars]The infrastructure was unable to return the IP address of a node ([dec]) to the MBI infrastructure, error: [chars].
Explanation Either an invalid location is being queried, or the infrastructure is behaving incorrectly. The MBI operation in progress may not be carried out.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBIMGR-3-NODEID_TO_STR_EXTERNAL_FAIL The infrastructure was unable to create an external representation of a location ([dec]) for the MBI, error: [chars]. Error messages from the MBI infrastructure will not contain the prefix-string that represents the remote location being processed.
Explanation Either an invalid location is being queried, or the infrastructure is behaving incorrectly. The MBI operation in progress may not be carried out.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBIMGR-3-NULL_PTR Unexpected NULL pointer passed to the MBI infrastructure by a client
Explanation An internal error has occurred in an application that has caused it to pass invalid data to the MBI infrastructure. The current request or operation may not be carried out.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBIMGR-3-TFTP_INFO_FAIL [chars]The MBI infrastructure failed to populate the TFTP information, error: [chars].
Explanation The TFTP information is unavailable. The MBI operation in progress may not be carried out.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBIMGR-3-UNKNOWN_BOARDTYPE [chars]An unknown boardtype ([dec]) was passed to the MBI infrastructure.
Explanation Either an invalid boardtype is being queried, or the infrastructure is behaving incorrectly. The MBI operation in progress may not be carried out.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBIMGR-4-REMOTE_NODEID_MSG_STR_CREATE_FAIL The MBI infrastructure failed to create a message string for a remote location ([dec]), error: [chars]. Error messages from the MBI infrastructure will not contain the prefix-string that represents the remote location being processed.
Explanation Either an invalid location is being queried, or the infrastructure is behaving incorrectly. The MBI operation in progress may not be carried out.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBIMGR-6-MBIVSN_DIGIT_INFO MBIMGR: [chars] ([dec])
Explanation MBI Mgr general info
Recommended Action No action is required.
Error Message%PLATFORM-MBIMGR-6-MBIVSN_STR_INFO MBIMGR: [chars] ([chars])
Explanation MBI Mgr general info
Recommended Action No action is required.
Error Message%PLATFORM-MBIMGR-7-IMAGE_VALIDATED [chars]: MBI [chars] validated
Explanation A message to indicate which MBI was validated for which location.
Recommended Action No action is required.
Error Message%PLATFORM-MBIMGR-7-INVALID_MBIVSN [chars]Invalid MBI spec passed in ([chars]): [chars]
Explanation A problem was found in the MBI spec that was passed in.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
MBUS Messages
Error Message%PLATFORM-MBUS-4-SVC_AGENT_ROM_DOWN_REV slot [dec]: mbus rom agent is down-rev (V[dec].[dec]), suggest upgrade to current (V[dec].[dec]). Use the upgrade mbus CLI in admin mode.
Explanation The version of Mbus agent ROM on slot is not current. %d - is the slot number of the card in question. %d - is the major version of the agent currently in ROM %d - is the minor version of the agent currently in ROM %d - is the major version of the agent that is recommeneded %d - is the minor version of the agent that is recommeneded
Recommended Action Upgrade the rom agent on the car in the specified slot. In admin mode issue the following command upgrade mbus location 0/slot/cpu0 where slot is the number of the slot shown in the warning message
Error Message%PLATFORM-MBUS-7-API_DEBUG [chars] ([hex])
Explanation mbus debugging information. %s debug or software error message %X error returns code in hexdecimal format.
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-7-API_DOWNLOAD_FAIL_STATUS download failed ([chars]).
Explanation mbus debug info %s - a string containing the slot number.
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-7-API_FILE_OPERATION_FAILED Failed to perform [chars] on file [chars].
Explanation mbus debug information %s - operation performed on file (e.g. open, close). %s - filename.
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-7-API_INFO [chars]
Explanation mbus debug information %s - debug message
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-7-API_INFO_DUMP [chars]
Explanation Displaying mbus debug information. %s - information message to be displayed
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-7-API_INVALID_SLOT invalid slot [dec].
Explanation mbus debug information %d - slot number
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-7-API_NULL_PARAMETER unexpected null pointer passed to function.
Explanation mbus debug information
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-7-ATTACH_DEBUG [chars]
Explanation mbus debugging information. %s - debug message
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-7-ATTACH_ERR [chars] ([hex])
Explanation mbus debug info %s - attach error information. %X - error return code
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-7-ATTACH_INFO_DUMP [chars]
Explanation mbus debug info %s - attach statistics
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-7-CLIENT_FAILURE [chars]
Explanation mbus debug information %s - describes the function that failed
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-7-MSG_INFO_DUMP [chars]
Explanation mbus debug information. %s - is the information being displayed for debug purposes
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-7-MSG_INFO_DUMP [chars]
Explanation mbus debug information. %s - is the information being displayed for debug purposes
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-7-SVC_AGENT_CHECK_FAILED mbus: local agent check failed ([chars]).
Explanation mbus debug information %s - is a string outlining the action that the system will take to attempt to recover (e.g. forcing RAM download).
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-7-SVC_DEBUG [chars] ([hex])
Explanation mbus debug information. %s - is the debug message
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-7-SVC_EOF_UNEXPECTED mbus: EOF unexpected on file [chars].
Explanation mbus debug information. %s - is the file name in question.
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-7-SVC_FILE_OPERATION_FAILED mbus: Failed to perform [chars] on file [chars].
Explanation mbus debug information. %s - indicates the type of file operations (e.g. open, close) %s - is the file name in question.
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-7-SVC_INFO_DUMP [chars]
Explanation mbus debug information. %s - is the information being displayed for debug purposes
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-7-SVC_INVALID_STREAM mbus: invalid stream [dec].
Explanation mbus debug information %d - is the stream identifier.
Recommended Action No action is required.
NFEA_HW_PROG Messages
Error Message%PLATFORM-NFEA_HW_PROG-6-INFO_MSG [chars]
Explanation Netflow punt rate is more than policer rate, it informs the user when such an event occurs
Recommended Action Reduce netflow sampling rate. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-NFEA_HW_PROG-7-ERR_MSG [chars]
Explanation During initialization, an internal error occurred in Netflow which involves exiting the process.
Recommended Action When this issue happens, it will trigger an automatic restart. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PLAT_FIB_HAL Messages
Error Message%PLATFORM-PLAT_FIB_HAL-3-ERR_DETAIL [chars] [hex], [chars] [dec], [chars]([dec])
Explanation PLATFORM FIB, error information
Recommended Action Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.
Error Message%PLATFORM-PLAT_FIB_HAL-3-ERR_INFO [chars] [dec]
Explanation PLATFORM FIB, error information
Recommended Action Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.
Error Message%PLATFORM-PLAT_FIB_HAL-3-ERR_INFO_HEX [chars] [hex]
Explanation PLATFORM FIB, error information
Recommended Action Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.
Error Message%PLATFORM-PLAT_FIB_HAL-3-ERR_INFO_RT [chars] [dec]
Explanation PLATFORM FIB, error information
Recommended Action Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.
Error Message%PLATFORM-PLAT_FIB_HAL-3-ERR_STR [chars]: [chars] ([unsigned int])
Explanation PLATFORM FIB, error information
Recommended Action Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.
Error Message%PLATFORM-PLAT_FIB_HAL-3-ERR_STR_RT [chars]: [chars] ([unsigned int])
Explanation PLATFORM FIB, error information
Recommended Action Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.
Error Message%PLATFORM-PLAT_FIB_HAL-3-ERROR [chars]
Explanation PLATFORM FIB, error
Recommended Action Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.
Error Message%PLATFORM-PLAT_FIB_HAL-3-ERROR_RT [chars]
Explanation PLATFORM FIB, error
Recommended Action Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.
Error Message%PLATFORM-PLAT_FIB_HAL-6-INFO [chars]
Explanation PLATFORM FIB, Information
Recommended Action The message is just for information. No action is needed.
PLAT_FIB_MPLS Messages
Error Message%PLATFORM-PLAT_FIB_MPLS-3-ERR_DETAIL [chars] [hex], [chars] [dec], [chars]([dec])
Explanation PLATFORM FIB, error information
Recommended Action Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.
Error Message%PLATFORM-PLAT_FIB_MPLS-3-ERR_INFO [chars] [dec]
Explanation PLATFORM FIB, error information
Recommended Action Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.
Error Message%PLATFORM-PLAT_FIB_MPLS-3-ERR_INFO_HEX [chars] [hex]
Explanation PLATFORM FIB, error information
Recommended Action Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.
Error Message%PLATFORM-PLAT_FIB_MPLS-3-ERR_STR [chars] [chars]([dec])
Explanation PLATFORM FIB, error information
Recommended Action Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.
Error Message%PLATFORM-PLAT_FIB_MPLS-3-ERROR [chars]
Explanation PLATFORM FIB, error
Recommended Action Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.
PLAT_FIB_RP Messages
Error Message%PLATFORM-PLAT_FIB_RP-3-ERR_INFO PLATFORM-FIB-RP: Error - [chars] [dec]
Explanation PLATFORM FIB, error information
Recommended Action *SUPPORT*
Error Message%PLATFORM-PLAT_FIB_RP-3-ERR_INFO_VERBOSE PLATFORM-FIB-RP: Error - [chars] [chars] [chars] [dec]
Explanation PLATFORM FIB, error information
Recommended Action *SUPPORT*
Error Message%PLATFORM-PLAT_FIB_RP-3-ERROR PLATFORM-FIB-RP: Error - [chars]
Explanation PLATFORM FIB, error
Recommended Action *SUPPORT*
PLAT_FIB Messages
Error Message%PLATFORM-PLAT_FIB-3-ERR_INFO [chars] [dec]
Explanation PLATFORM FIB, error information
Recommended Action Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.
Error Message%PLATFORM-PLAT_FIB-3-ERR_INFO_RT [chars] [dec]
Explanation PLATFORM FIB, error information
Recommended Action Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.
Error Message%PLATFORM-PLAT_FIB-3-ERR_STR [chars]: [chars] ([unsigned int])
Explanation PLATFORM FIB, error information
Recommended Action Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.
Error Message%PLATFORM-PLAT_FIB-3-ERR_STR_RT [chars]: [chars] ([unsigned int])
Explanation PLATFORM FIB, error information
Recommended Action Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.
Error Message%PLATFORM-PLAT_FIB-3-ERROR [chars]
Explanation PLATFORM FIB, error
Recommended Action Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.
Error Message%PLATFORM-PLAT_FIB-3-ERROR_RT [chars]
Explanation PLATFORM FIB, error
Recommended Action Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.
Error Message%PLATFORM-PLAT_FIB-4-WARNING_RT [chars]
Explanation PLATFORM FIB, warning
Recommended Action If the warning message is persistent, please collect the console log, running-config (show running-config), FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ), and report to your technical support representative.
Error Message%PLATFORM-PLAT_FIB-6-COMM_INFO [chars] [hex]
Explanation PLATFORM FIB, Information
Recommended Action The message is just for information. No action is needed.
Error Message%PLATFORM-PLAT_FIB-6-FRR_INFO [chars] [hex]
Explanation IP FRR PLATFORM FIB, Information
Recommended Action The message is just for information. No action is needed.
Error Message%PLATFORM-PLAT_FIB-6-INFO [chars]
Explanation PLATFORM FIB, Information
Recommended Action The message is just for information. No action is needed.
PLAT_L2FIB_COMMON Messages
Error Message%PLATFORM-PLAT_L2FIB_COMMON-7-HW_INIT_ERROR PLATFORM-L2FIB: Error - [chars] [chars] [chars] [dec]
Explanation Failed to create the Platform LC Hardware in L2FIB component.
Recommended Action None, platform software will correct itself if this happens.
PLAT_L2FIB_DEBUG Messages
Error Message%PLATFORM-PLAT_L2FIB_DEBUG-7-REGISTER_FAILED PLATFORM-L2FIB: Error - [chars] [chars] [chars] [dec]
Explanation Failed to initialize the debugging module in the platform L2FIB component.
Recommended Action None, platform software will correct itself if this happens.
PLAT_L2FIB_LTRACE Messages
Error Message%PLATFORM-PLAT_L2FIB_LTRACE-7-ERR_INFO_VERBOSE PLATFORM-L2FIB: Ltrace Error - [chars] [dec] [chars] [chars] [dec]
Explanation PLATFORM L2FIB, error information
Recommended Action *SUPPORT*
PLAT_L2FIB_METRO Messages
Error Message%PLATFORM-PLAT_L2FIB_METRO-2-QINQ_INIT_ERROR [chars] (error: [chars]). L2FIB Metro L3QinQ initialization failed!
Explanation L2FIB Metro L3QinQ failed to initialize correctly.
Recommended Action None, platform software will correct itself if this happens.
Error Message%PLATFORM-PLAT_L2FIB_METRO-3-BRIDGE_QINQ_ERROR PLATFORM-L2FIB: L2QINQ AC FOR BRIDGE NOT SUPPORTED - [chars]
Explanation VPLS/Bridging configuration with L2 QinQ/QinAny ACs not supported.
Recommended Action None.
Error Message%PLATFORM-PLAT_L2FIB_METRO-3-QINQ_TCAM_WRITE_ERROR PLATFORM-L2FIB: L3 QINQ ERROR - [chars] (error: [chars])
Explanation L2FIB Metro L3 QinQ entries programming in TCAM failed.
Recommended Action Collect L2FIB debugs/traces and report to crs-l2vpn-dev team.
Error Message%PLATFORM-PLAT_L2FIB_METRO-7-HW_INIT_ERROR PLATFORM-L2FIB: Error - [chars] [chars] [dec]
Explanation Failed to initialize the Platform LC Hardware in L2FIB component.
Recommended Action None, platform software will correct itself if this happens.
PLAT_L2FIB_RP Messages
Error Message%PLATFORM-PLAT_L2FIB_RP-3-DEBUG_ERROR PLATFORM-L2FIB-RP: Error - [chars] [chars] [chars] [dec]
Explanation Failed to initialize the debugging module in the platform L2FIB (D)RP component.
Recommended Action None, platform software will correct itself if this happens.
Error Message%PLATFORM-PLAT_L2FIB_RP-3-DEBUG_ERROR PLATFORM-L2FIB-RP: Error - [chars] [chars] [chars] [dec]
Explanation Failed to initialize the debugging module in the platform L2FIB (D)RP component.
Recommended Action None, platform software will correct itself if this happens.
Error Message%PLATFORM-PLAT_L2FIB_RP-3-DEBUG_ERROR PLATFORM-L2FIB-RP: Error - [chars] [chars] [chars] [dec]
Explanation Failed to initialize the debugging module in the platform L2FIB (D)RP component.
Recommended Action None, platform software will correct itself if this happens.
Error Message%PLATFORM-PLAT_L2FIB_RP-7-INIT_ERROR PLATFORM-L2FIB-RP: Error - [chars] [chars] [chars] [dec]
Explanation Failed to initialize the module in the platform L2FIB (D)RP component.
Recommended Action None, platform software will correct itself if this happens.
Error Message%PLATFORM-PLAT_L2FIB_RP-7-LTRACE_ERROR PLATFORM-L2FIB-RP: Error - [chars] [dec] [chars] [dec]
Explanation Failed to initialize the ltrace module in the platform L2FIB (D)RP component.
Recommended Action None, platform software will correct itself if this happens.
PLAT_L2FIB Messages
Error Message%PLATFORM-PLAT_L2FIB-7-CERR_ERROR PLATFORM-L2FIB: Error - [chars] [chars] [chars] [dec]
Explanation Failed to initialize the cerrno module in the platform L2FIB component.
Recommended Action None, platform software will correct itself if this happens.
Error Message%PLATFORM-PLAT_L2FIB-7-DEBUG_ERROR PLATFORM-L2FIB: Error - [chars] [chars] [chars] [dec]
Explanation Failed to initialize the debugging module in the platform L2FIB component.
Recommended Action None, platform software will correct itself if this happens.
Error Message%PLATFORM-PLAT_L2FIB-7-HW_INIT_ERROR PLATFORM-L2FIB: Error - [chars] [chars] [chars] [dec]
Explanation Failed to initialize the Platform LC Hardware in L2FIB component.
Recommended Action None, platform software will correct itself if this happens.
Error Message%PLATFORM-PLAT_L2FIB-7-LTRACE_ERROR PLATFORM-L2FIB: Error - [chars] [chars] [chars] [dec]
Explanation Failed to initialize the ltrace module in the platform L2FIB component.
Recommended Action None, platform software will correct itself if this happens.
Error Message%PLATFORM-PLAT_L2FIB-7-NHOP_ERROR PLATFORM-L2FIB: Error - [chars] [chars] [hex] [hex] [hex] [hex]
Explanation Received NHOP MODIFY to change rx/tx TLU address in the platform L2FIB component.
Recommended Action None, platform software will correct itself if this happens.
Error Message%PLATFORM-PLAT_L2FIB-7-PFI_ERROR PLATFORM-L2FIB: Error - [chars] [chars] [dec]
Explanation Failed to register with PFI infra in the platform L2FIB component.
Recommended Action None, platform software will correct itself if this happens.
PLAT_L2VPN_DEBUG Messages
Error Message%PLATFORM-PLAT_L2VPN_DEBUG-7-REGISTER_FAILED PLATFORM-L2VPN: Error - [chars] [chars] [dec]
Explanation Failed to initialize the debugging module in the platform L2VPN component.
Recommended Action None, platform software will correct itself if this happens.
PLAT_L2VPN_FGID Messages
Error Message%PLATFORM-PLAT_L2VPN_FGID-3-ALLOC_ERROR PLATFORM-L2VPN: Error - [chars] [dec] [chars] [dec]
Explanation Failed to allocate FGID for bridge broadcast doamin.
Recommended Action None, platform software will correct itself if this happens.
Error Message%PLATFORM-PLAT_L2VPN_FGID-3-DEBUG_ERROR PLATFORM-L2VPN: Error - [chars] [chars] [dec]
Explanation Failed to initialize the debugging module in the platform L2VPN component.
Recommended Action None, platform software will correct itself if this happens.
Error Message%PLATFORM-PLAT_L2VPN_FGID-3-DEBUG_ERROR PLATFORM-L2VPN: Error - [chars] [chars] [chars] [dec]
Explanation Failed to initialize the debugging module in the platform L2VPN component.
Recommended Action None, platform software will correct itself if this happens.
Error Message%PLATFORM-PLAT_L2VPN_FGID-3-MEM_ERROR PLATFORM-L2VPN: Error - [chars] [dec]
Explanation Failed to allocate memory from heap.
Recommended Action None, platform software will correct itself if this happens.
Error Message%PLATFORM-PLAT_L2VPN_FGID-3-MEM_ERROR PLATFORM-L2VPN: Error - [chars] [dec]
Explanation Failed to allocate memory from heap.
Recommended Action None, platform software will correct itself if this happens.
Error Message%PLATFORM-PLAT_L2VPN_FGID-3-REMARK_ERROR PLATFORM-L2VPN: Error - [chars] [dec]
Explanation Failed to remark FGID
Recommended Action None, platform software will correct itself if this happens.
Error Message%PLATFORM-PLAT_L2VPN_FGID-3-TIMER_ERROR PLATFORM-L2VPN: Error - [chars] [dec]
Explanation Failed to start realloc timer.
Recommended Action None, platform software will correct itself if this happens.
Error Message%PLATFORM-PLAT_L2VPN_FGID-3-TIMER_ERROR PLATFORM-L2VPN: Error - [chars] [dec]
Explanation Failed to start retry timer.
Recommended Action None, platform software will correct itself if this happens.
Error Message%PLATFORM-PLAT_L2VPN_FGID-7-INIT_ERROR PLATFORM-L2VPN: Error - [chars] [chars] [dec]
Explanation Failed to initialize the module in the platform L2VPN component.
Recommended Action None, platform software will correct itself if this happens.
Error Message%PLATFORM-PLAT_L2VPN_FGID-7-INIT_ERROR PLATFORM-L2VPN: Error - [chars] [chars] [dec]
Explanation Failed to initialize the module in the platform L2VPN component.
Recommended Action None, platform software will correct itself if this happens.
Error Message%PLATFORM-PLAT_L2VPN_FGID-7-LTRACE_ERROR PLATFORM-L2VPN: Error - [chars] [chars] [chars] [dec]
Explanation Failed to initialize the ltrace module in the platform L2VPN component.
Recommended Action None, platform software will correct itself if this happens.
Error Message%PLATFORM-PLAT_L2VPN_FGID-7-LTRACE_ERROR PLATFORM-L2VPN: Error - [chars] [chars] [dec]
Explanation Failed to initialize the ltrace module in the platform L2VPN component.
Recommended Action None, platform software will correct itself if this happens.
PLAT_L2VPN_LTRACE Messages
Error Message%PLATFORM-PLAT_L2VPN_LTRACE-7-ERR_INFO_VERBOSE PLATFORM-L2VPN: Ltrace Error - [chars] [chars] [chars] [dec]
Explanation PLATFORM L2VPN, error information
Recommended Action *SUPPORT*
PLAT_L2VPN Messages
Error Message%PLATFORM-PLAT_L2VPN-3-RSI_ERROR PLATFORM-L2VPN: Error - [chars] [dec] [dec]
Explanation Failed to extract nodeid to rsi value.
Recommended Action None, platform software will correct itself if this happens.
Error Message%PLATFORM-PLAT_L2VPN-3-RSI_ERROR PLATFORM-L2VPN: Error - [chars] [dec] [dec]
Explanation Failed to extract nodeid to rsi value.
Recommended Action None, platform software will correct itself if this happens.
PLATFORM_HFR_LIB Messages
Error Message%PLATFORM-PLATFORM_HFR_LIB-7-AM_I_SC_ERROR Failed to detect hardware board type. Reason: [chars].
Explanation The platform library service call to find the hardware module type has failed. The calling application handles it appropriately.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PLATFORM_HFR_LIB-7-AM_I_SC_ERROR Failed to detect hardware board type. Reason: [chars].
Explanation The platform library service call to find the hardware module type has failed. The calling application handles it appropriately.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PLATFORM_HFR_LIB-7-ERR_GET_BOARD_TYPE Failed to detect hardware board type. Reason: [chars].
Explanation The platform library service call to find the hardware module type has failed. The calling application handles it appropriately.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PLATFORM_HFR_LIB-7-ERR_GET_CARD_TYPE Failed to detect Node [chars] card type. Reason: [chars].
Explanation The platform library service call to find the remote node card type has failed. The calling application handles it appropriately.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PLIM_16P_OC48 Messages
Error Message%PLATFORM-PLIM_16P_OC48-3-DEVICE_INTR_CLEAR No Framer/RAC devices are generating excessive interrupts
Explanation The previously reported excessive interrupts condition has been cleared. Interrupt rate limiting has been disabled.
Recommended Action none
Error Message%PLATFORM-PLIM_16P_OC48-3-DEVICE_INTR_DISABLE Excessive interrupts from the [chars] device of port [hex]
Explanation The specified device is generating excessive interrupts. This message indicates that we are rate limiting the interrupt coming from this device. This indicates a potential HW issue, traffic forwarding (protection switching) may be impacted.
Recommended Action Check the fiber or the peer connection. If the problem persist after checking fiber and peer router, please contact support.
Error Message%PLATFORM-PLIM_16P_OC48-3-GENERIC_ERROR Error: [chars] [chars] [hex]
Explanation The messagen is used to report generic errors.
Recommended Action Contact support.
Error Message%PLATFORM-PLIM_16P_OC48-6-GENERIC_INFO Info: [chars] [chars] [hex]
Explanation The messagen is used to report generic errors.
Recommended Action Contact support.
Error Message%PLATFORM-PLIM_16P_OC48-6-OIM_OIR Optic Interface Module [chars] for port [dec]
Explanation The Optic Interface Module (OIM) for the specified port has either been inserted or removed.
Recommended Action No action is required.
PLIM_IPC Messages
Error Message%PLATFORM-PLIM_IPC-3-API_ERROR [chars]: [hex], [chars]
Explanation An error occurred in plim ipc api module which could involve failure to transport ipc messages between host and intelligent PLIM. Features configured may not work. %x - indicates where/what error occurred %s - why the error occurred
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PLIM_IPC-3-ERROR [chars]: [hex], [chars]
Explanation An error occurred in plim ipc module which could involve failure to transport ipc messages between host and intelligent PLIM. %x - indicates where/what error occurred %s - why the error occurred
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PLIM_IPC-3-INIT_ERROR [chars]: [hex], [chars]
Explanation An error occurred in PLIM IPC module during initialization which will restart the process in order to recover. %x - indicates where/what error occurred %s - why the error occurred
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PLIM_IPC-6-INFO [chars]: [hex], [chars]
Explanation An event occurred in plim ipc module which could involve state of PLIM or PPC. %x, %s - indicates where/what event occurred
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PLIM_SERVICES Messages
Error Message%PLATFORM-PLIM_SERVICES-2-BPARAMS_ERROR [chars] [hex]
Explanation An error in boot parameters reception occurred in Services PLIM. Cause of the error will be mentioned in the message displayed. This error blocks Application Launch on Services PLIM.
Recommended Action Do warm reload of Services PLIM MSC. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PLIM_SERVICES-2-ERR_EVM_EVENT_BLOCK [chars] [hex]
Explanation An error occurred in the event loop.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PLIM_SERVICES-2-ERR_MEM_ALLOC [chars] [hex]
Explanation The requested operation could not be accomplished because of a low memory condition. This error could impact Linux/Application image download and Launch, Services PLIM IPC (Inter Process Communication) etc.
Recommended Action Reduce other system activity to ease memory demands, then restart the process. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-PLIM_SERVICES-2-ERR_PLIM_SERVICES_INIT [chars] [hex]
Explanation An error occurred in initialization of PLIM Services driver. If this occurred during process startup or RP Switchover, then the process may be restarted.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PLIM_SERVICES-2-FLASH_ERROR [chars] [hex]
Explanation An error occurred in READ/WRITE to flash memory. Exact Cause of the error will be mentioned in the message displayed. This error will block Application image launch
Recommended Action Do cold reboot of Services PLIM MSC. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PLIM_SERVICES-2-HEARTBEAT_ERROR [chars] [hex]
Explanation Heartbeat failure notification from octeons was received by the Services PLIM driver or a critical error occured in the thread monitoring heartbeat from octeons.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PLIM_SERVICES-2-IMG_DLOAD_ERROR [chars] [hex]
Explanation An error occurred in downloading Linux/Application image. Cause of the error will be mentioned in the message displayed. This error prevents Services PLIM from coming up to its full functional Active state.
Recommended Action Do cold reboot of Services PLIM MSC. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PLIM_SERVICES-2-IMG_LAUNCH_ERROR [chars] [hex]
Explanation An error occurred in launching Linux/Application image. Cause of the error will be mentioned in the message displayed. This error prevents Services PLIM from coming up to its full functional Active state.
Recommended Action Do cold reboot of Services PLIM MSC If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PLIM_SERVICES-2-MANS_FPGA_ERROR [chars] [hex]
Explanation An error occurred in read/write access of a mans fpga device register.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PLIM_SERVICES-2-MANS_INIT_ERROR [chars] [hex]
Explanation An error occurred in MANS initialization. This means that MANS is currently in Factory mode and this will cause the Services PLIM driver initialization to get blocked.
Recommended Action Upgrade MANS with Field FPGA image If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PLIM_SERVICES-2-UART_ERROR [chars] [hex]
Explanation An error occurred in UART READ/WRITE access to octeon memory. Exact Cause of the error will be mentioned in the message displayed. This error causes Linux/Application image download and launch to fail.
Recommended Action Do cold reboot of Services PLIM MSC. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PLIM_SERVICES-3-ERR_EDM_INIT [chars] [hex]
Explanation Initialization of the EDM server failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PLIM_SERVICES-3-ERR_UBOOT_UPGRADE [chars] [hex]
Explanation An error occurred in fpd upgrade of uboot image..
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PLIM_SERVICES-3-MANS_GASPP_ERROR [chars] [hex]
Explanation An error occurred in MANS GASPP register access. Cause of the error will be mentioned in the message displayed. This error means that communication between Services PLIM and MSC could be affected.
Recommended Action Do warm reload of the Services PLIM MSC. If the issue persists do a cold reboot of the same. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PLIM_SERVICES-6-COLD_RESTART Info: [chars]
Explanation The message is used to report cold reboot of Services PLIM.
Recommended Action *NONE*
Error Message%PLATFORM-PLIM_SERVICES-7-GENERIC_ERROR [chars] [hex]
Explanation A generic error occurred in Services PLIM driver. Cause of the error will be mentioned in the message displayed.
Recommended Action No action is required.
Error Message%PLATFORM-PLIM_SERVICES-7-GENERIC_INFO Info: [chars]
Explanation The message is used to report generic info about Services PLIM driver.
Recommended Action *NONE*
Error Message%PLATFORM-PLIM_SERVICES-7-GENERIC_TILE_ERROR [chars] [hex]
Explanation A generic error occurred in Tile Manager. Cause of the error will be mentioned in the message displayed.
Recommended Action No action is required.
Error Message%PLATFORM-PLIM_SERVICES-7-GENERIC_TILE_INFO Info: [chars]
Explanation The message is used to report generic info regarding tile Finite state machine.
Recommended Action *NONE*
Error Message%PLATFORM-PLIM_SERVICES-7-MANS_GASPP_INFO Info: [chars]
Explanation The message is used to report info regarding MANS gaspp register access
Recommended Action *NONE*
POWERMGR Messages
Error Message%PLATFORM-POWERMGR-0-ENQUEUE Cannot enqueue event [chars] for device [dec]
Explanation Power Manager internal failure occurred; possible low memory condition.
Recommended Action PowerMgr log needs to be looked into to investigate on the failure
Error Message%PLATFORM-POWERMGR-0-ENQUEUE_ZONE Cannot enqueue event [chars] for zone [dec]
Explanation Power Manager internal failure occurred; possible low memory condition.
Recommended Action PowerMgr log needs to be looked into to investigate on the failure
Error Message%PLATFORM-POWERMGR-2-AC_DC_FAILURE Powershelf AC/DC detection failed,status code [dec]
Explanation The AC/DC detection of powershelf failed due to wrong value read from EEPROM or read from wrong location of EEPROM.
Recommended Action PowerMgr log needs to be looked into to investigate on the failure
Error Message%PLATFORM-POWERMGR-2-CANNOT_TALK No alarmcard/busboard module available to communicate w/ PEM[dec]
Explanation No alarmcard or busboard module was found available to talk to the PEMs. This might occur if the MBus agent associated with that module became temporarily unavailable. As such, this error message should only be a cause for concern if it appears repeatedly, over a period of minutes. If it appears just once, it indicates a transient condition, and may be safely ignored. Lastly, note that if this message is seen during chassis bootup, the problem is far more serious, as during that time, the path to the PEMs is assumed stable. In this case, powershelf discovery may fail, and as a result, some linecards may be left in unpowered state. he powershelf does not have adequate capacity to drive the entire chassis. A power system upgrade is recommended; otherwise, please power down cards until there is sufficient power for the load.
Recommended Action PowerMgr log needs to be looked into to investigate on the failure
Error Message%PLATFORM-POWERMGR-2-INITFAIL Resource allocation error encountered during startup
Explanation Power Manager subsystem failed during startup; lack of resources.
Recommended Action PowerMgr log needs to be looked into to investigate on the init failure
Error Message%PLATFORM-POWERMGR-2-INITMEMFAIL Memory allocation error encountered during startup
Explanation Power Manager subsystem failed during startup; lack of resources.
Recommended Action PowerMgr log needs to be looked into to investigate on the init failure
Error Message%PLATFORM-POWERMGR-2-INVALID_COND Invalid condition detected in function [chars] at line [dec]
Explanation A disallowed condition internal to the Power Manager has been detected.
Recommended Action PowerMgr log needs to be looked into to investigate on the invalid condition
Error Message%PLATFORM-POWERMGR-2-LOW_POWER Not enough power to bringup card in slot [dec]
Explanation Customer should upgrade chassis power or reduce the power load by removing some linecards.
Recommended Action PowerMgr log needs to be looked into to investigate on the failure
Error Message%PLATFORM-POWERMGR-2-NO_PATH Alarmcard/busboard module not ready to communicate w/ PEM
Explanation Alarmcard or busboard module was found to be resetting or still running from ROM. This message is seen during chassis bootup. In this case, test chassis is assummed and all Linecards will bootup as default power is asseumed. However note that power manager would still display errors and envmon module would also display powershelf related errors
Recommended Action PowerMgr log needs to be looked into to investigate on the failure
Error Message%PLATFORM-POWERMGR-2-OVERBUDGET Power consumption has exceeded supply[chars] by [dec]W; results unpredictable
Explanation The power calculated in use by the chassis exceeds that available by the powershelf. This condition could result in an outage of the chassis if action is not immediately taken.
Recommended Action Remove some linecards to reduce power consumption, or install a higher capacity powershelf
Error Message%PLATFORM-POWERMGR-2-POWER_INSUFFICIENT Chassis power requirements exceed capacity by [dec]W [chars]
Explanation The powershelf does not have adequate capacity to drive the entire chassis. A power system upgrade is recommended; otherwise, please power down cards until there is sufficient power for the load.
Recommended Action Customer should upgrade chassis power or reduce the power load on this chassis by removing linecards.
Error Message%PLATFORM-POWERMGR-2-TIMEOUT Timed out waiting for power-up decision for slot [dec]
Explanation Power Manager internal failure occurred.
Recommended Action PowerMgr log needs to be looked into to investigate on the timeout
Error Message%PLATFORM-POWERMGR-3-BAD_DATA Failed to get pem equals [dec] data, error status equals [chars]
Explanation Failed to get good data from Pacific pems
Recommended Action No action is required.
Error Message%PLATFORM-POWERMGR-3-BAD_PEC Consequtive 5 pec check failures on pem equals [dec]
Explanation Invalid data returned by Pacific Power supplies can be checked via validating the PEC returned as the last byte of a read request vis-a-vis the PEC that is computed from the incoming data
Recommended Action No action is required.
Error Message%PLATFORM-POWERMGR-3-CANNOT_RESERVE Powershelf capacity insufficient to reserve power for card in slot [dec]
Explanation The powershelf does not have enough capacity to reserve power for the linecard in the specified slot. It will be left unpowered as a result.
Recommended Action PowerMgr log needs to be looked into to investigate on the failure
Error Message%PLATFORM-POWERMGR-3-ERROR [chars]
Explanation For displaying power manager debugging information with an errno.
Recommended Action No action is required.
Error Message%PLATFORM-POWERMGR-3-IMPRECISE Power usage for card in slot [dec] unknown; assuming [dec] watts max
Explanation An entry in the power table could not be found for the card specified. To allow chassis bringup to progress, default values are being used as specified. Note that this error should only occur during development when a new cardtype is being introduced, but its power data has yet to be entered.
Recommended Action PowerMgr log needs to be looked into to investigate on the failure
Error Message%PLATFORM-POWERMGR-3-INTERIM Warning: Interim power entry value being used for cardtype [hex]
Explanation An entry in the power table has been flagged as interim, meaning it is a placeholder used during development while the final power consumption is being determined. This issue will occur only during development of new linecards or power-supplies, and the errmsg exists only to aid developers.
Recommended Action PowerMgr log needs to be looked into to investigate on the failure
Error Message%PLATFORM-POWERMGR-3-INVALID_COMBINATION Invalid PEM combination in [chars]; Found [dec] pems, recommended atleast [dec] pems
Explanation Power Manager has detected less than minimum number of Pacific Pems.
Recommended Action power manager cli needs to be looked into to investigate on the invalid condition.
Error Message%PLATFORM-POWERMGR-3-NODEID_CREATE_ERROR Could not create nodeid for slot [dec] error equals [chars].
Explanation Slot number is probably not known
Recommended Action No action is required.
Error Message%PLATFORM-POWERMGR-3-NOTFOUND No power entry found for cardtype [hex]
Explanation An entry in the power table could not be found for the entity specified. This issue will occur only during development of new linecards or power-supplies, and the errmsg exists only to aid developers.
Recommended Action PowerMgr log needs to be looked into to investigate on the failure
Error Message%PLATFORM-POWERMGR-3-ROM_ERROR_STATUS Unable to get Mbus ROM status from SYSDB. Error equals [chars]
Explanation Unable to get the Mbus ROM status from Sysdb.
Recommended Action No action is required.
Error Message%PLATFORM-POWERMGR-3-STILL_POWERED Cannot poweroff card in slot [dec]; manual removal required
Explanation The card in the specifed slot could not be powered off as part of putting it into a low-power state. As a result, it is unusable, but still contributing to the power consumed in the chassis.
Recommended Action PowerMgr log needs to be looked into to investigate on the failure
Error Message%PLATFORM-POWERMGR-3-SYSDB_BIND_ERROR PM: Unable to sysdb_bind :[chars]
Explanation SYSDB Bind failed
Recommended Action No action is required.
Error Message%PLATFORM-POWERMGR-3-SYSDB_SET_ERROR Failed to create sysdb tuple [chars] for slot [dec]. error equals [chars]
Explanation SYSDB Set or Create failed for that item
Recommended Action No action is required.
Error Message%PLATFORM-POWERMGR-3-UNKNOWN_PEM Unable to determine characteristics of PEM[dec]; skipping
Explanation The characteristics of the power supply installed in the specified slot could not be determined. This supply is being skipped, and discovery of the rest of the powershelf will continue. If no supplies can be found, a failsafe type will be used to allow the chassis to come up to a point at which debugging of the problem is possible.
Recommended Action PowerMgr log needs to be looked into to investigate on the failure
Error Message%PLATFORM-POWERMGR-3-UNKNOWN_PEMS Unable to detect installed power supplies; using failsafe assumptions
Explanation The installed power supplies (i.e., PEMs) could not be detected. To allow the chassis to come up, a set of conservative assumptions have been used for calculating power availability and consumption. Some linecards may be left in an unpowered state as a result.
Recommended Action PowerMgr log needs to be looked into to investigate on the failure
Error Message%PLATFORM-POWERMGR-3-UNKNOWN_SHELF Unable to determine powershelf type; using failsafe assumptions
Explanation The powershelf type could not be determined during bootup. To allow the chassis to come up, a set of conservative assumptions have been used for calculating power availability and consumption. Some linecards may be left in an unpowered state as a result.
Recommended Action PowerMgr log needs to be looked into to investigate on the failure
Error Message%PLATFORM-POWERMGR-4-INVALID_SCALE Power scale factor '[dec]' out of range; ignoring
Explanation TheSYSDB Config variable used to dictate the scale factor for utilizing something other than worst-case power consumption values is out of the allowable range.
Recommended Action PowerMgr log needs to be looked into to investigate on the invalid condition
Error Message%PLATFORM-POWERMGR-4-PEM_DOWN PEM[dec] has powered down
Explanation The power supply specified has powered down.
Recommended Action PowerMgr log needs to be looked into to investigate on the failure
Error Message%PLATFORM-POWERMGR-4-PRIO_SLOT_EMPTY Attempting to reserve power for empty slot [dec]
Explanation The configuration includes a power priority reservation for a slot that does not have a linecard installed within it. Power will not be set aside for this slot, and the command should be removed from the config.
Recommended Action PowerMgr log needs to be looked into to investigate on the failure
Error Message%PLATFORM-POWERMGR-4-TEST_CHASSIS Test chassis detected; using default powershelf configuration
Explanation The type of chassis model was detected as being a test chassis, which does not have many of the resources the Power Manager uses to communicate with the PEMs. Thus, the type of powershelf, as well as type and number of PEMs installed will default to a predefined value, intended to allow the chassis to function unimpeded.
Recommended Action This message is informational only, and should never be seen by the customer.
Error Message%PLATFORM-POWERMGR-4-UNPOWERED PEM[dec] inserted but unpowered
Explanation The power supply specified has been installed in the chassis but is unpowered, most likely because of an unconnected power cord.
Recommended Action Check the power cord and if installed correctly, remove and reinstall the PEM. If the error persists, contact customer support
Error Message%PLATFORM-POWERMGR-5-EVENT_ERROR Spurious QUEUE_EVENT, dequeueing NULL pointer
Explanation Power Manager main event loop encountered internal error.
Recommended Action PowerMgr log needs to be looked into to investigate on the failure
Error Message%PLATFORM-POWERMGR-5-INVALID_EVENT Unexpected event [dec]; ignoring
Explanation Power Manager internal failure occurred; possible low memory condition.
Recommended Action PowerMgr log needs to be looked into to investigate on the failure
Error Message%PLATFORM-POWERMGR-5-MIXED_PEMS Mixing legacy and intelligent PEMs is not recommended
Explanation Both legacy as well as the higher-wattage intelligent PEMs have been detected in the chassis at the same time. While this is a supported configuration, it is not recommended, as it may result in the legacy PEM eclipsing the intelligent PEM by reducing the overall powershelf wattage to that of the former, when running in redundant mode. The formal recommendation is to have both PEMs be of the same type.
Recommended Action PowerMgr log needs to be looked into to investigate on the failure
Error Message%PLATFORM-POWERMGR-5-PEM_UP PEM[dec] powered up successfully, supplying [dec] watts
Explanation The power supply specified has successfully powered up.
Recommended Action PowerMgr log needs to be looked into to investigate on the failure
Error Message%PLATFORM-POWERMGR-5-REMOVED PEM[dec] removed
Explanation The power supply specified has been removed from the chassis.
Recommended Action PowerMgr log needs to be looked into to investigate on the failure
Error Message%PLATFORM-POWERMGR-5-UNKNOWN_TYPE Unable to determine type of PEM[dec]; using failsafe assumptions
Explanation The type of the power supply installed in the specified slot could not be determined. To allow the chassis to come up, it will be categorized as the failsafe type, which allows it to be assumed providing modest power to the chassis. Note that the wattage provided by a failsafe supply may be less than that which the supply is actually providing.
Recommended Action PowerMgr log needs to be looked into to investigate on the failure
Error Message%PLATFORM-POWERMGR-6-BUDGET_OK Chassis power consumption is back within limits[chars]
Explanation The power calculated in use by the chassis has returned to a valid that is within the power supplied by the powershelf.
Recommended Action PowerMgr log needs to be looked into to investigate on the failure
Error Message%PLATFORM-POWERMGR-6-CARD_OVERRIDE Overriding power consumption for card in slot [dec]; now [dec] watts
Explanation Power consumed for the card in the specified slot has been overridden with a value from the config
Recommended Action PowerMgr log needs to be looked into to investigate on the failure
Error Message%PLATFORM-POWERMGR-6-DEBUG [chars][dec]
Explanation power manager debugging information.
Recommended Action No action is required.
Error Message%PLATFORM-POWERMGR-6-INFO [chars]
Explanation For displaying power manager's informational events.
Recommended Action No action is required.
Error Message%PLATFORM-POWERMGR-6-INSERTED PEM[dec] inserted, supplying [dec] watts
Explanation The power supply specified has been installed in the chassis and is now active
Recommended Action PowerMgr log needs to be looked into to investigate on the failure
Error Message%PLATFORM-POWERMGR-6-PEM_OVERRIDE Overriding PEM[dec] rating; now [dec] watts
Explanation Supply power for the PEM specified has been overridden with a value from the config.
Recommended Action PowerMgr log needs to be looked into to investigate on the failure
Error Message%PLATFORM-POWERMGR-6-ZONE_OVERRIDE Number of zones being forcibly set to [dec]
Explanation The number of power zones for the chassis has been overidden with a value from the config.
Recommended Action PowerMgr log needs to be looked into to investigate on the failure
PRP_HW Messages
Error Message%PLATFORM-PRP_HW-3-INIT_ERROR Performance route processor initialization failed: ([chars]%s)
Explanation Performance Route Processor (PRP) drivers failed to initialize. The effect is that PRP will not function. %s - indicates the reason for the failure. %s - is the error reason.
Recommended Action The System Manager process (sysmgr) will not respawn this process. Try to reload the PRP first. If it does not recover, power recycle the router. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PRP3_FABIO Messages
Error Message%PLATFORM-PRP3_FABIO-3-ERR_INGRESS [chars]
Explanation Internal Error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PRP3_FABIO-3-ERR_INIT [chars], with code([dec]) [chars]
Explanation Internal Error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PRP3_FABIO-3-ERR_MEM_ALLOC [chars], for size [dec].
Explanation Failed to allocate memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PRP3_FABIO-7-ERR_DUPLICATE_STREAMID [chars], stream id [dec] existed
Explanation Internal Error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PRP3_FABIO-7-ERR_SEND_PKT [chars], [dec], [dec], rc is [dec]
Explanation Internal Error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PRP3_SLR_FABIO Messages
Error Message%PLATFORM-PRP3_SLR_FABIO-3-ERR_INGRESS [chars]
Explanation Internal Error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PRP3_SLR_FABIO-3-ERR_INIT [chars], with code([dec]) [chars]
Explanation Internal Error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PRP3_SLR_FABIO-3-ERR_MEM_ALLOC [chars], for size [dec].
Explanation Failed to allocate memory.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PRP3_SLR_FABIO-7-ERR_DUPLICATE_STREAMID [chars], stream id [dec] existed
Explanation Internal Error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PRP3_SLR_FABIO-7-ERR_SEND_PKT [chars], [dec], [dec], rc is [dec]
Explanation Internal Error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
PSARB Messages
Error Message%PLATFORM-PSARB-1-WRONG_SLOT Rebooting RP in slot [dec] because it conflicts with an already operational RP in slot [dec].
Explanation Card pairing requires primary/standby cards in specific slots and active RP's need to be in seperate LR's. Adjacency is defined by RP pairing rules (e.g. 0-1, 2-3, 4-5, 6-7). If it's intended to use the conflicting RP as a standby partner, please move the RP adjacent to the active. Or, if the RP is meant to be used in another logical router, please ensure it is assigned to the other LR. %d - indicates the wrong slot number the RP is inserted %d - indicates the slot number of the operational RP
Recommended Action Move standby RP card to correct slot in chassis, or assign to distinct LR.
Error Message%PLATFORM-PSARB-2-MSG_HEARTBEAT_LOST Slot [dec] heartbeat lost
Explanation The active RP has lost the heartbeat of the indicated slot. This error happens after a certain number of messages are lost between the active and the indicated card. %d - indicates the slot number of the card experiencing the problem.
Recommended Action The system will automatically reset the card. If this error repeatedly occurs, try to shut down the card by configuring 'hw-module location slot shutdown' in admin mode. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PSARB-3-INIT_ERR Process initialization failed: ([chars]%s)
Explanation The psarb process failed to initialize. This process is responsible for providing a high level of availability on the GSR router by having a pair of active and standby RPs in the system. When an active RP fails, another RP can take over the functionality of the failed RP. %s - indicates the reason for the failure. %s - the decoded error reason.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-PSARB-3-LR_INFO_FAILURE Failed to get LR info after [dec] seconds rc equals [hex], Retrying...
Explanation PSarb needs LR map and the dSC information before it can proceed with active standby arbitration. The LR information is acquired by connecting to the LRd on the dSC. This error message indicates, the connection to LRd did not succeed, either because the LRd process does not exist or the dSC selection has still not taken place. The system will retry indefinetely to get the LR information and log this message periodically to alert the user of the prevailing condition.
Recommended Action No action is required. This is an informational message. The software will simply take the safest approach of retrying, given the fault that the RP is experiencing.
Error Message%PLATFORM-PSARB-3-TWO_PRIMARY_DETECTED Two primary RPs detected (message from slot [dec])
Explanation There appear to be two PRIMARY RP's in the system. This is due to messaging error when the other RP didn't receive the BID message. %d indicates the primary slot number displaying the message
Recommended Action The two primary RPs will be automatically reset.
Error Message%PLATFORM-PSARB-4-CONFLICT_WITH_DSC Rebooting RP because an active dSC in slot [dec] is detected.
Explanation At any given time, there should be one active dSC in the system. In the event that the active RP detects another active dSC in the system, the RP should reboot itself to recover the condition. This event is expected when creating or deleting SDR configuration. %d - indicates the slot number of the active dSC
Recommended Action Collect the output of all event logs and error messages as they appeared on the console before the card in question was reloaded. To provide the status of the process, issue the 'show process psarb' command and collect the debug information by enabling 'debug psarb'. Also collect psarb lstrace log. Collect 'show redundancy driver trace'.
Error Message%PLATFORM-PSARB-4-PARTNER_NOT_IN_LR This node's partner (slot [dec]) is in a different LR. The standby node will be reset.
Explanation Adjacent RPs must be in the same LR unless if they are both to be booted with an RP image. It is, however, permissable to boot a DRP in one of these slots. Adjacency is defined by RP pairing rules (e.g. 0-1, 2-3, 4-5, 6-7). %d - indicates the slot number of the partner RP
Recommended Action Do not boot RP images in adjacent slots when they are in different LRs. Adjacency is defined by RP pairing rules (e.g. 0-1, 2-3, 4-5, 6-7).
Error Message%PLATFORM-PSARB-4-SPURIOUS_COUNTDOWN Slot [dec] (internal flavor [dec]) is actually not from RP family. Reset cancelled
Explanation The arbitration module watches the health of other RP cards in the system and reloads them if heartbeats are missed. In this case, we were about to reload a card but a final check revealed that the card was not of family RP, so we avoided the reload. This is a safety check to catch an abnormal condition. No problem will result from this type of error.
Recommended Action None
Error Message%PLATFORM-PSARB-5-IOS_RP_DETECTED Detected an RP in slot [dec] is running IOS. Configured it as IOS non-participant.
Explanation PSARB sends an mbus message to all RP running IOS on the chassis, to configure the RP as an IOS non-participant router, therefore, does not interfere with IOX running on this RP. %d - indicates the slot number of the RP that is running IOS on the chassis
Recommended Action Power up the RP that is running IOS with an IOX image. If not, shut down the RP using 'hw-module location slot shutdown' in admin mode.
Error Message%PLATFORM-PSARB-6-DEBUG_REMINDER Reminder: psarb debug mode is still enabled...Disable using run psarbcmd
Explanation This message reminds the user that a debug mode is enabled and must eventually be disabled.
Recommended Action None
Error Message%PLATFORM-PSARB-6-FORCE_DOWN Slot [dec] still not in dump mode, forcing it down
Explanation The specified RP stopped responding, but we did not receive any message indicating that the card is in DUMP mode. Looks like it is still in IOX mode and could potentially try to take over. So, force it to go down.
Recommended Action No action is required. This is an informational message. The software is simply taking the safest approach, given the fault that the specified RP experienced.
Error Message%PLATFORM-PSARB-6-GO_ACTIVE Card is going active.
Explanation When an RP initially boots up, it can take the active role if no other active RP is present. Also a failure on active or a force switch over could cause the standby RP to change state to active. This message is displayed when the PRP card is going active.
Recommended Action This is an informational message only.
Error Message%PLATFORM-PSARB-6-GO_STANDBY Card is going standby.
Explanation When an RP initially boots up, it can take the standby role if an active RP is present. Also a failure on active or a force switch over causes the active RP to change state to standby. This message is displayed when the RP card is going standby.
Recommended Action This is an informational message only.
Error Message%PLATFORM-PSARB-6-IGNORE_TO Now ignoring countdown timeouts
Explanation This message confirms the user selected debug mode
Recommended Action None
Error Message%PLATFORM-PSARB-6-IGNORING_ACTIVE_TIMEOUT Timeout waiting for active RP heartbeats, but not taking over because of configured debug mode
Explanation The active RP is no longer sending heartbeats, but we don't take over becaused of the configured debug mode.
Recommended Action None
Error Message%PLATFORM-PSARB-6-IGNORING_CARD_TIMEOUT Timeout waiting for heartbeats from slot [dec], but ignoring because of configured debug mode
Explanation The specified slot is no longer sending heartbeats, but we don't take any action given the configured debug mode.
Recommended Action None
Error Message%PLATFORM-PSARB-6-MBUS_RX_FAILURE MBUS receive failure detected on standby slot [dec], node gracefully rebooting self
Explanation The specified Standby RP is experiencing receive failures on its MBUS and instead of causing a failover and becoming Primary, it is gracefully rebooting itself to maintain proper health of the system.
Recommended Action No action is required. This is an informational message. The software is simply taking the safest approach, given the fault that the standby RP experienced.
Error Message%PLATFORM-PSARB-6-NOISY Resume sending MBUS heartbeats to other cards
Explanation This message confirms the user selected debug mode
Recommended Action None
Error Message%PLATFORM-PSARB-6-NORMAL_TO Now using normal timeouts
Explanation This message confirms the user selected debug mode
Recommended Action None
Error Message%PLATFORM-PSARB-6-PARTNER_TAKEOVER Two primary RPs detected: myself (slot [dec]) and message from slot [dec]
Explanation There appear to be two PRIMARY RP's in the system. ex-act suicide and the partner takes over. %d indicates the primary and partner slot numbers displaying the message
Recommended Action ex-act RP will be automatically reset.
Error Message%PLATFORM-PSARB-6-QUIET Now now longer sending MBUS heartbeats to other cards
Explanation This message confirms the user selected debug mode
Recommended Action None
Error Message%PLATFORM-PSARB-6-REDCON_NOT_REGISTERED Redcon not registered with psarb for notification rebooting self slot [dec]
Explanation Redundancy controller process is not registered for arbitration state notification, this can leave the system in unstable state. The node is rebooting self to correct this situation.
Recommended Action No action is required. This is an informational message. The software will simply take the safest approach, given the fault that the RP is experiencing.
Error Message%PLATFORM-PSARB-6-RESUME Resuming countdowns
Explanation This message confirms the user selected debug mode
Recommended Action None
Error Message%PLATFORM-PSARB-6-ROLE_LOCKED (slot [dec]) failover prevented - card role is locked
Explanation The role of this card has been locked - failover was prevented. %d - indicates the slot number of the PRP which it's role is locked
Recommended Action No action is required.
Error Message%PLATFORM-PSARB-6-RX_FROM_PARTNER_FAILURE Receive failures from partner slot [dec] detected on slot [dec]
Explanation The specified RP is experiencing receive failures from its partner on its MBUS.
Recommended Action No action is required. This is an informational message. The software will simply take the safest approach, given the fault that the RP is experiencing. Depending on the arbitration role of the RP, a reload of the RP or a FO is imminent.
Error Message%PLATFORM-PSARB-6-SELF_SEND_FAILURE Self send failure detected on slot [dec]
Explanation The specified RP is experiencing self send failures on its MBUS.
Recommended Action No action is required. This is an informational message. The software will simply take the safest approach, given the fault that the RP is experiencing. Depending on the arbitration role of the RP, a reload of the RP or a FO is imminent.
Error Message%PLATFORM-PSARB-6-SUSPEND Turning off our countdowns
Explanation This message confirms the user selected debug mode
Recommended Action None
Error Message%PLATFORM-PSARB-6-TAKE_OVER Take over message received from partner, transition to primary
Explanation The specified RP received a take over message from its partner, indicating that the card should transition to Primary role.
Recommended Action No action is required. This is an informational message. The software is simply taking the safest approach, given the fault that the partner RP experienced.
REDDRV Messages
Error Message%PLATFORM-REDDRV-2-MSG_LOCAL_NODE_DEAD_RELOAD_MYSELF This DRP's other CPU node went down. Reload myself.
Explanation When a CPU in DRP goes down, the other CPU should go down as well.
Recommended Action None; this CPU will reset along with other CPU
Error Message%PLATFORM-REDDRV-2-MSG_PRIMARY_GLARE primary-primary glare (primary msg from node [hex])
Explanation There appear to be two PRIMARY RP's in the system
Recommended Action None; the node which has arbitrated for the least time will be reset.
Error Message%PLATFORM-REDDRV-3-ERROR_EXIT reddrv process exiting because [chars], error code [chars]
Explanation The DRP redundancy driver process exited for the reason mentioned in the message.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process up to a fixed number of times when this error is encountered inorder to recover. Execute 'show process reddrv location ' to verify that the process is up and running after the restart. If it is still non-operational, try doing from the admin mode 'process restart reddrv location '. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-REDDRV-3-ROLE_LOCKED (node [hex]) failover prevented - card role is locked
Explanation The role of this card has been locked - failover was prevented.
Recommended Action A failover was initiated, but could not complete because the card role is locked. Please capture the output of 'show reddrv trace' and 'show drp-reddrv trace'.
Error Message%PLATFORM-REDDRV-5-GO_ACTIVE Card is becoming active.
Explanation Card is becoming active.
Recommended Action No action required, just informational message.
Error Message%PLATFORM-REDDRV-5-GO_BID Card is going to bid state.
Explanation Card is going to bid state.
Recommended Action No action required, just informational message.
Error Message%PLATFORM-REDDRV-5-GO_STANDBY Card is becoming standby.
Explanation Card is becoming standby.
Recommended Action No action required, just informational message.
Error Message%PLATFORM-REDDRV-5-MSG_PARTNER_NODE_DEAD_START_FAILOVER Active DRP's CPU node went down. Perform Failover as I'm standby now.
Explanation When a CPU in active DRP goes down, the standby CPU should failover as active.
Recommended Action None; this CPU will failover to active state
Error Message%PLATFORM-REDDRV-6-RESET_SELF No active RP detected for [dec] seconds; resetting this node
Explanation The node on which reddrv is running, resets itself on loss of heartbeat from the RP.
Recommended Action Check the RP in the system. If present, check the connectivity between RP and the node that went down.
Error Message%PLATFORM-REDDRV-7-MSG_INVALID_MSGLEN reddrv_msg_handler got [dec] expected [dec]
Explanation reddrv_msg_handler received a message of unexpected size
Recommended Action No action required, software will take corrective action on its own.
Error Message%PLATFORM-REDDRV-7-NODE_RESET Resetting node [chars] for correct active/standby arbitration
Explanation The arbitration state machine needs to be able to reset failed nodes, or other nodes on the same card as a failed node, in order to ensure correct behavior of the state machine and no mixed-role cards.
Recommended Action No action required, just informational message.
Error Message%PLATFORM-REDDRV-7-NODE_RESET_FAILED Reset of node [chars] failed with error [chars] - correct active/standby arbitration may not occur in this case
Explanation The arbitration state machine needs to be able to reset failed nodes, or other nodes on the same card as a failed node, in order to ensure correct behavior of the state machine and no mixed-role cards. If this fails, then arbitration may not occur correctly.
Recommended Action Please collect output of 'show redundancy trace', 'show logging' and 'show ltrace shelfmgr'.
Error Message%PLATFORM-REDDRV-7-OPERATION_FAIL Failed to [chars], error code [chars]
Explanation The particular operation mentioned in the message failed due to some reason. This is not a critical failure, the process can continue functioning as expected despite the failure.
Recommended Action Debug message only. No action is required.
Error Message%PLATFORM-REDDRV-7-REDCON_REREGISTER Recon registration invoked more than once
Explanation The reddrv_redcon_register function was called multiple times
Recommended Action No action required, software will automatically take corrective action.
REEP Messages
Error Message%PLATFORM-REEP-3-ERROR_OPENING_ETHERNET_CONNECTION Failed to open connection to control ethernet server. Err equals [chars]
Explanation The control ethernet transport connection has been lost due to which send/receive for this process over the control ethernet will not work. This impacts standby RP booting.
Recommended Action If this message is seen persistently, please capture output of 'show process eth_server' and 'show controllers backplane ethernet trace'.
Error Message%PLATFORM-REEP-3-GET_BOARD_TYPE_FAILED Platform call to determine boardtype failed
Explanation This is indicative of some very fundamental problem in the the system. Some very basic system initialization has failed.
Recommended Action Check the board which had the failure.
Error Message%PLATFORM-REEP-3-I2C_BKPLANE_READ_FAILED I2C access to read backplane EEPROM failed
Explanation This is indicative of some very fundamental problem in the the system. I2C access to the backplane not working could be due to an I2C hang.
Recommended Action Gather all the console logs and the i2c trace.
Error Message%PLATFORM-REEP-3-I2C_SERVER_CONNECT_FAILED Failed to connect to I2C server
Explanation I2C service is currently unavailable.
Recommended Action If this condition persists, it will preclude the standby route processor card in that chassis from coming up. So if it is seen persistently, please check the status of the i2c_server process on the active RP.
Error Message%PLATFORM-REEP-7-REPLY_SEND_FAILED Failed to send reply. Err equals [dec]
Explanation Failed to send reply to client ROMMON.
Recommended Action Transient occurrence of this message is possible. If this message is seen persistently, and either an MSC, DRP or standby RP is not booting, it is because the control network connectivity service on this node is malfunctioning.
ROM_UPGRADE_LIB Messages
Error Message%PLATFORM-ROM_UPGRADE_LIB-7-ERROR [chars]
Explanation --
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
ROMMON_BURNER Messages
Error Message%PLATFORM-ROMMON_BURNER-3-BAD_ARG Bad command option: [chars] [chars]
Explanation Bad coammand option.
Recommended Action No action is required..
Error Message%PLATFORM-ROMMON_BURNER-3-FILE_OP_ERR [chars]: [chars] in function [chars] at line [dec]
Explanation Error occured with file operations.
Recommended Action No action is required..
Error Message%PLATFORM-ROMMON_BURNER-3-NO_MEM Failed in allocating memory in function [chars] at line [dec]
Explanation No enough memory.
Recommended Action No action is required..
Error Message%PLATFORM-ROMMON_BURNER-5-progress [chars] [chars]
Explanation Output progress to RP console.
Recommended Action No action is required..
Error Message%PLATFORM-ROMMON_BURNER-5-version ROMMON version [dec].[dec] is not supported for this board.
Explanation Invalid ROMMON version to RP console.
Recommended Action No action is required..
RWMGR Messages
Error Message%PLATFORM-RWMGR-0-INIT_RETRY_SUCCEEDED RwString Manager succeeded in initializing the [chars] module upon retry.
Explanation An error was previously encountered while initializing one of modules of the rwmgr server. However, the initialization was retried and succeeded.
Recommended Action No action is required.
Error Message%PLATFORM-RWMGR-2-INIT_FAILURE Failed to initialze RwString Manager: [chars]
Explanation This syslog is printed when RwString Manager or its clients fail to initialize necessary data structures and memories. If the error originates from the system call the error message is also printed.
Recommended Action Based on the system error message the user can tell what went wrong. More likely than not, the user has to restart the system. If the problem persists he or she has to contact Cisco customer support team.
Error Message%PLATFORM-RWMGR-2-MALLOC_FAILURE Failed to allocate memory: [chars]
Explanation An explanation is provided in the syslog.
Recommended Action A user should be able to tell what went wrong and take actions accordingly. For instance, if the system runs out of memory then more memory needs to be installed.
Error Message%PLATFORM-RWMGR-4-INIT_ERROR RwString Manager was unable to initialize the [chars] module. Error: '[chars]'. [chars].
Explanation An error was encountered while initializing one of the modules of configuration manager server. The failure of this module initialization is not critical to configuration manager to be completely operational.
Recommended Action Provide the message details to Cisco Support personal.
Error Message%PLATFORM-RWMGR-4-TRACE [chars] Error:[chars]
Explanation This is a non-fatal error and can happen when router is low on memory. It should not affect the functioning of the router, but trace messages may not be logged.
Recommended Action None.
Error Message%PLATFORM-RWMGR-7-INTERNAL [chars]
Explanation An unexpected internal error occurred in the rwmgr subsystem.
Recommended Action Copy the error message exactly as it appears on the console or in the system log. Call your Cisco technical support representative and provide the representative with the gathered information.
SHELFMGR Messages
Error Message%PLATFORM-SHELFMGR-0-CD_IN_RESET_STATE Card Bringup: Reboot card to keep Node: [hex][[chars]] in the IN-RESET state, Reset Code: [dec]
Explanation This message indicates that this node was parked in the in-reset state due to the reason specified.
Recommended Action Use hw-module loc loc reload command to release card from IN-RESET state.
Error Message%PLATFORM-SHELFMGR-0-CHASSIS_SHUTDOWN CHASSIS SHUTDOWN initiated due to [chars]
Explanation Chassis is shutting down due to reason mentioned.
Recommended Action Examine chassis based on above message.
Error Message%PLATFORM-SHELFMGR-0-MAX_RESET_BRINGDOWN Cannot boot node [chars] due to multiple resets, putting into IN_RESET state
Explanation This message indicates that the node has reached maximum number of resets allowed, therefore, it is brought down to IN_RESET state.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-SHELFMGR-1-CLEAR_ALL_FANTRAYS_REMOVED Atleast one tray has been inserted within 45 seconds (of removing all trays), so the chassis will not be shut down
Explanation Software has detected that all fan trays were removed which would have shut down the system. But one fan tray was put back within 45 seconds, thus removing the need to shut down the system.
Recommended Action *None*
Error Message%PLATFORM-SHELFMGR-1-PARTIAL_CHASSIS_SHUTDOWN_POWERUP [chars] linecards and fabric cards due to low voltage warning [chars] from power shelves
Explanation Received message from environment monitor that the voltage is low on the power shelves. So we are shutting down linecards and fabric cards to prevent damage to these boards.
Recommended Action Examine chassis and replace battery or power-shelf.
Error Message%PLATFORM-SHELFMGR-1-SET_ALL_FANTRAYS_REMOVED Critical Alarm: All fan trays have been removed from the chassis. If at least one tray is not inserted within 45 seconds, the chassis will be shutdown
Explanation Software has detected that all fan trays have been removed from the chassisbut, but gives user 45 seconds to insert another tray. If no action is taken within 45 seconds, the chassis will be shut down.
Recommended Action Insert a fan tray within 45 seconds.
Error Message%PLATFORM-SHELFMGR-3-BOARD_NOT_SUPPORTED Shutdown node [chars] since CRS-DRP is not supported on CRS-4-CH
Explanation This message indicates that the node is being shutdown because it is not supported on the CRS-4 platform.
Recommended Action Remove the unsupported board and replace it with supported hardware.
Error Message%PLATFORM-SHELFMGR-3-CHECKPT_MEM_RESTORE_FAILED Error restoring the Shelfmgr Checkpointed memory, rc equals [hex]([chars])
Explanation The Shelfmgr failed to restore its checkpoint memory on a process restart or transition from stby to act.
Recommended Action No action is required.
Error Message%PLATFORM-SHELFMGR-3-CHKPT_MEM_OUT_OF_RANGE Attempting to restore unknown Shelfmgr Chkpt Memory
Explanation The Shelfmgr encountered unexpected checkpoint memory
Recommended Action No action is required.
Error Message%PLATFORM-SHELFMGR-3-CHKPT_MEM_RESTORE_ERR Can not restore checkpoint for the HB Monitor DB for nodeid: [hex], slot: [dec], RecIndex: [dec], rc equals [hex] ([chars])
Explanation Shelfmgr API call to update the HB Monitor database failed.
Recommended Action No action is required.
Error Message%PLATFORM-SHELFMGR-3-EMPTY_SERIAL_FAIL_BOOT Received boot request from a RP with an empty rack serial number, which indicates an attempt to boot a RP with ROMMON v1.19x as the standby. Boot request is being failed ! Refer to customer documentation for configuring a boot override
Explanation Shelfmgr is failing a boot request because the serial number string in the boot request is empty. This happens if a RP with ROMMON 1.19x or older is sending a boot request.
Recommended Action Please upgrade the booting RP to the latest recommended ROMMON.
Error Message%PLATFORM-SHELFMGR-3-FAILED_LOAD Node [chars] fails to load IOS XR image, request to reset ...
Explanation This message indicates that the node failed to load the IOS XR image for maximum number of retries and will be reset.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-SHELFMGR-3-FAILEDPOWERUP Unable to power up slot [chars], request to reset. reason: [chars]
Explanation This message indicates the board in named slot failed to power up. The node will be reloaded automatically.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-SHELFMGR-3-FSMTIMEOUT_RESET Node [chars] is reset due to failed bootup. Node state was: [dec] Timeout ID: [dec]
Explanation This message indicates that the node is not able to boot up
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-SHELFMGR-3-INRESET_ALARM Power off node [chars] due to multiple critial alarms, putting into IN_RESET state
Explanation This message indicates that the node has being brought down to IN_RESET state due to multiple critical alarms.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-SHELFMGR-3-INRESET_INV_CARD_TYPE Boot request from node [chars] contains invalid board type, This board is being shutdown, moved to the IN_RESET state
Explanation This message indicates that the board type cannot be recognized, therefore, the node will not be able to boot up. This usually caused by an invalid eeprom content.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-SHELFMGR-3-INV_NODEID_EVT_IGNORE ERR: Can not retrieve my node: rc equals [hex] ([chars]), Bringdown Req [dec] not process for NodeID: [hex], State: [dec]
Explanation API Call to nodeid_extract_fields() failed.
Recommended Action No action is required.
Error Message%PLATFORM-SHELFMGR-3-INV_NODEID_IN_CHKPT_MEMORY Can not decode nodeID: [hex], RecIndex: [dec], rc equals [hex] ([chars])
Explanation API Call to nodeid_extract_fields() failed.
Recommended Action No action is required.
Error Message%PLATFORM-SHELFMGR-3-NODE_CPU_RESET Node [chars] CPU reset detected.
Explanation This message indicates that the Shelfmgr detected the CPU of the specified node has reset. The specified node will attempt software reload.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-SHELFMGR-3-NODE_DB_CREATE_ERR Unexpected Node DB creation error, Node: [chars][[hex]], evt not processed: [chars][[dec]]
Explanation This message indicates that there was an unexexpected error within the shelfmgr database where the Node Db was not found, or could be created. This causes the shelfmgr not processed the event that it just received.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-SHELFMGR-3-NODE_RESET_ALARM Node [chars] in critical alarms, request to reset ...
Explanation This message indicates that the Shelf Manager or Platform Manager encountered a critical alarm for the node specified. It will attempt to reset the board which sends the alarm.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-SHELFMGR-3-NODE_RESET_BRINGDOWN Reset node [chars] due to heartbeat loss
Explanation This message indicates that the node is being reset because it failed to detect heartbeat pulses.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-SHELFMGR-3-POWERDOWN_RESET Node [chars] is powered off due to admin power off request
Explanation This message indicates that the node will be reset because user has administratively 'power disable' or 'no power disable' the node.
Recommended Action No action is required.
Error Message%PLATFORM-SHELFMGR-3-POWERRELOAD_RESET Node [chars] is reset through power off, then power on
Explanation This message indicates that the node is being reloaded because of a critical environmental alarm.
Recommended Action No action is required.
Error Message%PLATFORM-SHELFMGR-3-RP_SHUTDOWN RP SHUTDOWN INITIATED due to thermal alarms
Explanation RP is shutting down due to reason mentioned.
Recommended Action If there is a standby RP in the router, failover will automatically occur. Otherwise, chassis will be brought down and a manual reboot will be neccessary.
Error Message%PLATFORM-SHELFMGR-3-SHUTDOWN Node [chars] is shutdown due to a critical alarm
Explanation This message indicates that the node will be brought down because a critical environmental alarm occured.
Recommended Action Check air-flow, fan trays, and make sure that chassis is well-cooled. Manually boot up the node once the chassis has been checked.
Error Message%PLATFORM-SHELFMGR-3-SHUTDOWN_RESET Node [chars] is reset due to admin shut/no shut request
Explanation This message indicates that the node will be reset because user has administratively 'shutdown' or 'no shutdown' the node.
Recommended Action No action is required.
Error Message%PLATFORM-SHELFMGR-3-STATE_MSG_DELAY Excessive node state message transmit time detected. [chars] Seq: [dec], Queue Delay: [dec] sec, Transmit Delay: [dec] sec
Explanation The system has detected a possible performance issue causing a delay in shelf management operations.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-SHELFMGR-3-UNKNOWN_BOARD Boot request from node [chars] contains invalid board type, This board is being shutdown
Explanation This message indicates that the board type cannot be recognized, therefore, the node will not be able to boot up. This usually caused by an invalid eeprom content.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-SHELFMGR-4-CMDLINE_BOOT_OVERRIDE_ENABLED Command line boot override to permit RPs with ROMMON 1.19x to boot as the standby has been enabled
Explanation This is a warning message to indicate that using '-o override' option while booting the image, the operator will override the default IOS XR behavior which blocks the RP with ROMMON version v1.19x from coming up as the standby.
Recommended Action Please upgrade the booting RP to the latest recommended ROMMON.
Error Message%PLATFORM-SHELFMGR-4-EMPTY_SERIAL_BOOT_OVERRIDE WARNING !!! WARNING !!! Received boot request from a RP with an empty rack serial number. Permitting RP to boot due to [chars] override. Please upgrade RP ROMMON to latest recommended version
Explanation This informational message informs the user that the Shelfmgr discovered an empty serial number due to an older ROMMON format, but it will allow the RP to boot because the operator had configured to override the restriction of disallow booting a RP with empty serial number.
Recommended Action Please upgrade the booting RP to the latest recommended ROMMON.
Error Message%PLATFORM-SHELFMGR-4-WARM_RLD_FAILED Receive [chars] from [chars], while waiting for MBI_HELLO_WARM
Explanation Card seems to have been cold reloaded after an attempt to warm reload the card.
Recommended Action Capture the shelfmgr log and use the 'show shelfmgr trace' CLI in admin-mode to fetch debug information. Also capture sysmgr_nv.log from LC.
Error Message%PLATFORM-SHELFMGR-6-ABORT Shelfmgr Software Error: [chars]
Explanation An unexpected software event has caused the shelfmgr process to restart.
Recommended Action No action is required.
Error Message%PLATFORM-SHELFMGR-6-NO_PLIM Can not power on node [chars] due to absence of PLIM
Explanation This message informs the user that the linecard will not be powered on because there is no PLIM inserted.
Recommended Action No action is required.
Error Message%PLATFORM-SHELFMGR-6-NODE_DISCOVERY Node State Discovery complete
Explanation Shelf Manager node discovery complete.
Recommended Action No action is required.
Error Message%PLATFORM-SHELFMGR-6-NODE_NORESET Node [chars] is in NMON state, Cancel reset request
Explanation This message indicates that the reset request caused by a critical alarm or heartbeat loss will not take effect because the node is being put in NMON state.
Recommended Action No action is required.
Error Message%PLATFORM-SHELFMGR-6-NODE_STATE_CHANGE [chars] card type:[dec] nstate:[chars]
Explanation Card state transition occurred.
Recommended Action No action is required.
Error Message%PLATFORM-SHELFMGR-6-NOREASON_RESET Node [chars] is reset due to UNKNOWN reason [[dec]]
Explanation This message indicates that the node has been reset but the cause is unknown.
Recommended Action No action is required.
Error Message%PLATFORM-SHELFMGR-6-SYSTEM_COLD_START System cold start detected. Resetting Line Cards.
Explanation The system is recovering either from a cold restart situation or a state where no valid shelf controller cards were available.
Recommended Action No action is required.
Error Message%PLATFORM-SHELFMGR-6-USER_RESET Node [chars] is reset due to user reload request
Explanation This message indicates that the node will be reset because user has requested to reload the node.
Recommended Action No action is required.
Error Message%PLATFORM-SHELFMGR-6-WARM_RLD_JUMP Receive MBI_HELLO_ENA from [chars] at [WARM-RLD], status jumped to IOX-RUN
Explanation Card comes up without MBI_HELLO or MBI_HELLO_WARM, need to check warm-reload is really done successfully.
Recommended Action Initiate 'show warm-reload detail location loc' and check Successful Attempts variables. If one of them is not zero, warm-reload is succeeded. Else, capture the shelfmgr log and use the 'show shelfmgr trace' CLI in admin-mode to fetch debug information. Also capture sysmgr.log and sysmgr_nv.log from LC.
Error Message%PLATFORM-SHELFMGR-7-WARM_RLD_FO Receive MBI_HELLO_WARM from [chars] at [Present], LC seems to be under warm-reload
Explanation Card seems warm reloaded successfully
Recommended Action No action is required.
Error Message%PLATFORM-SHELFMGR-7-WARM_RLD_OK Receive MBI_HELLO_WARM from [chars], new processes are coming up
Explanation Card seems warm reloaded successfully
Recommended Action No action is required.
SHOW_VERSION_CMD Messages
Error Message%PLATFORM-SHOW_VERSION_CMD-7-IFMGR_BIND A Version Manager CLI command was unable to bind to the interface infrastructure, due to error [chars].
Explanation A Version Manager CLI command was unable to bind to the interface infrastructuree from which it obtains information. The command will not contain all expected information.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-SHOW_VERSION_CMD-7-SYSDB_BIND A Version Manager CLI command was unable to bind to the system database, due to error [chars].
Explanation A Version Manager CLI command was unable to bind to the system database from which it obtains information. The command will not contain all expected information.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
SPENET Messages
Error Message%PLATFORM-SPENET-7-ERR_DEBUG [chars]
Explanation Internal error while receiving a packet over the control network on to the service processor. Error is harmless if only one or two are seen. If seen in a persistent manner, call support.
Recommended Action 'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'
STP_SHIM Messages
Error Message%PLATFORM-STP_SHIM-6-LINK_STATE_CHANGE Spanning Tree Port [chars] state changed to [chars]
Explanation Spanning Tree Port's state change indication.
Recommended Action No action is required.
Error Message%PLATFORM-STP_SHIM-6-LOGGING_DEVICE [chars] will be used for storing control ethernet logs. Current logs are under [chars] directory and older logs are under [chars] directory.
Explanation This is an informational message to indicate the location of for bcm.log, stp.log and stp_shim.log are.
Recommended Action Do nothing
Error Message%PLATFORM-STP_SHIM-7-COPY_FAILED Copying of log file to [chars] failed. err equals [dec], status equals [dec]. Restarting to recover.
Explanation This is an informational message to indicate that copying a log file to the storage device indicated has failed. This could be because the device was being formatted. The process will restart to recover.
Recommended Action Do nothing
Error Message%PLATFORM-STP_SHIM-7-DRV_ERR [chars], [dec]
Explanation Error condition from switch driver which may affect spanning tree operation on control ethernet. Normally spanning tree can tolerate a few of these errors as long as the driver comes back to a good state. Large number of these messages can indicate bad health of control-ethernet.
Recommended Action Check if the switch driver process 'bcm_process' is up and running. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-STP_SHIM-7-NO_STORAGE_DEVICE_FOUND Copying of log files to persistent storage is suspended because no persistent storage device (harddisk/PCMCIA disk) found
Explanation The service that copies /tmp/bcm.log and /tmp/stp.log to persistent storage, did not find any of harddisk, disk0, disk1 or bootflash available
Recommended Action See if any of harddisk, disk0, disk1 or bootflash are accessible on the RP. If they are accessible, restart bcm_logger.
SYSLDR_LC Messages
Error Message%PLATFORM-SYSLDR_LC-2-NODE_RELOAD Reload notification received. Reloading in [dec] secs
Explanation Message indicating that the kAA on the card has received a reload notification from sysldr for powering off the card and the card is going to reload soon. card state is IOX_RUNNING
Recommended Action Sysldr log needs to be looked into to investigate on the node reload cause. As, sysldr requests to reload the card for various reasons.
Error Message%PLATFORM-SYSLDR_LC-2-NODE_RELOAD_NOW Calling reboot ([chars])
Explanation Message indicating that the node has received a reload notification and the node is going to reload soon. This message is logged after the delay over since the NODE_RELOAD message is logged.
Recommended Action Sysldr log needs to be looked into to investigate on the node reload cause. As, sysldr requests to reload the card for various reasons.
Error Message%PLATFORM-SYSLDR_LC-3-FATAL [chars]
Explanation A fatal error was encountered, and the program exited. Error in thread creation for mbi-hello process.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR_LC-6-LTRACE_INIT_ERR Failed to initialize ltrace buffer in [chars]. Error: [chars]
Explanation Ltrace buffer will not be available. Debuggability will be reduced because of lacking of ltrace buffer.
Recommended Action This indicates a low memory condition. Memory on the box must be running low - are there services that can be stopped, or can more memory be added?
Error Message%PLATFORM-SYSLDR_LC-7-ERR_MSG_SEND msg_send failed to server : [chars]
Explanation Call failed to send message to MBI-Hello LWM server.
Recommended Action The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.
Error Message%PLATFORM-SYSLDR_LC-7-ERR_SERVER_CONNECT Failed to connect to server : [chars]
Explanation A communication problem occurred between the MBI client and server, perhaps because the communications infrastructure is not set up. The MBI operation in progress will not be carried out.
Recommended Action The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.
Error Message%PLATFORM-SYSLDR_LC-7-TIMER_TIMEOUT Timer timed out from server : [chars]
Explanation Timer timed out between the MBI client and server, perhaps because the communications infrastructure is not set up. The MBI operation in progress will not be carried out.
Recommended Action The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.
Error Message%PLATFORM-SYSLDR_LC-7-TIMER_TIMEOUT_MDR Timeout is ignored due to Warm Reload
Explanation Ping request is not received from RP. It's not normal but expected under Warm Reload situation. Only when Warm Relad fails, please collect information.
Recommended Action If Warm Reload fails, please collect admin show sysldr warm-reload
Error Message%PLATFORM-SYSLDR_LC-7-WARNING [chars]
Explanation KAA process failed to collect the Fabric ping diagnostic date.
Recommended Action No action is required.
SYSLDR_RP Messages
Error Message%PLATFORM-SYSLDR_RP-1-NODE_RELOAD_NOW Calling reboot ([chars])
Explanation Message indicating that the PRP has received a reload notification and it is going to be reloaded soon. This message is logged after the delay over since the NODE_RELOAD message is logged.
Recommended Action Sysldr log needs to be looked into to investigate on the node reload cause. As, sysldr requests to reload the card for various reasons.
Error Message%PLATFORM-SYSLDR_RP-2-NODE_RELOAD Reload notification received. Reloading in [dec] secs
Explanation Message indicating that the mbi-hello on the standby PRP has received a reload notification from sysldr for powering off the card and the card is going to reload soon. The card is in MBI-RUNNING state.
Recommended Action Sysldr log needs to be looked into to investigate on the node reload cause. As, sysldr requests to reload the card for various reasons.
Error Message%PLATFORM-SYSLDR_RP-6-LTRACE_INIT_ERR Failed to initialize ltrace buffer in [chars]. Error: [chars]
Explanation Ltrace buffer will not be available. Debuggability will be reduced because of lacking of ltrace buffer.
Recommended Action This indicates a low memory condition. Memory on the box must be running low - are there services that can be stopped, or can more memory be added?
Error Message%PLATFORM-SYSLDR_RP-7-ERR_MSG_SEND msg_send failed to server : [chars]
Explanation A communication problem occurred between the MBI client and server. The MBI operation in progress will not be carried out.
Recommended Action The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.
Error Message%PLATFORM-SYSLDR_RP-7-ERR_SERVER_CONNECT Failed to connect to MBI ping server : [chars]
Explanation A communication problem occurred between the MBI client and server, perhaps because the communications infrastructure is not set up. The MBI operation in progress will not be carried out.
Recommended Action The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.
Error Message%PLATFORM-SYSLDR_RP-7-FATAL [chars]
Explanation A fatal error was encountered, for mbi-hello process on standby RP and the program exited.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR_RP-7-TIMER_TIMEOUT Timer timed out from MBI ping server : [chars]
Explanation Timer timed out between the MBI client and server, perhaps because the communications infrastructure is not set up. The MBI operation in progress will not be carried out.
Recommended Action The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.
Error Message%PLATFORM-SYSLDR_RP-7-WARNING [chars]
Explanation Unexpected low severity problem.
Recommended Action No action is required.
SYSLDR Messages
Error Message%PLATFORM-SYSLDR-1-PING_FAILURE slot [dec]: ping failure using the fabric connection, last sequence# tx equals [unsigned int], rx equals [unsigned int]
Explanation Fabric ping is failed for the specified card. The card was OK for a while, but then failed to reply to fabric pings.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-1-PING_FAILURE_BOOT slot [dec]: timeout waiting for initial ping using the fabric connection, last tx sequence# equals [unsigned int]
Explanation Following boot, the card never succeeded in replying to fabric pings.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-1-SELF_PING_DISABLED Failed self-ping for a sustained period. Local connection to fabric must be down. auto-reset disabled by user config, so no action will be taken.
Explanation Self fabric ping has failed, which indicates a problem a local problem sending or receiving from the fabric. Gather the logs. Also issue the 'show tech shelf' command in admin mode and collect the resulting file. Call your Cisco technical support representative and provide the representative with the gathered information.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-1-SELF_PING_FAILURE slot [dec]: self ping failure using the fabric connection, last sequence# tx equals [unsigned int], rx equals [unsigned int]
Explanation Self fabric ping is failed for the active RP. The chassis will be reloaded with non redundant RP chassis or the failover will happen with the redundant RP chassis.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-1-SELF_PING_FAILURE_BOOT slot [dec]: timeout waiting for initial self ping using the fabric connection, last tx sequence# equals [unsigned int]
Explanation The card never succeeded in sending fabric pings to itself.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-2-CRITICAL slot[dec]: [chars]
Explanation sysldr encountered an critical error condition.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-2-FABRIC_DOWN slot [dec]: fabric connection is down. Reloading.
Explanation Fabric ping failure for the card, which was in IOX-RUNNING state. Card network is non-responsiveness.
Recommended Action This indicates a problem in qnet communication. A user can try 'hardware-module slot' once to retry loading of the card, for reconnection of the fabric ping.
Error Message%PLATFORM-SYSLDR-2-MBI_FABRIC_DOWN slot [dec]: fabric connection to MBI is down. Reloading.
Explanation Fabric ping failure for the card, which was in MBI-RUNNING state.
Recommended Action This indicates a problem in MBI communication. A user can try 'hardware-module slot' once to retry loading of the card, for reconnection of the fabric ping.
Error Message%PLATFORM-SYSLDR-2-MBI_NOLOAD slot [dec]: MBI cannot load IOX, retrying by reloading
Explanation It is inability of MBI to boot a node's full image.
Recommended Action This indicates a problem in communication or installation. Tech support should be contacted. Several attempts will be made to retry the image loading, and then the card will be put in the 'reset' state after too many failures.
Error Message%PLATFORM-SYSLDR-3-BANDWIDTH_SHUTDOWN Fabric bandwidth change: Shutting down card in slot [dec]
Explanation Loss or OIR of one or more fabric cards has led to the card being shut down
Recommended Action Inspect the SFC and CSC cards.
Error Message%PLATFORM-SYSLDR-3-ENVMON_SHUTDOWN Shutting down card in slot [dec], ordered by Envmon.
Explanation Volatile shutdown was ordered by Envmon because environmental problems (with temperature, voltage, power etc) were detected.
Recommended Action Investigate the problems reported by Envmon and correct them. After they are corrected, reload the LC using the 'hardware-module reload' command.
Error Message%PLATFORM-SYSLDR-3-ERROR slot[dec]: [chars], errno equals [dec]
Explanation For displaying sysldr debugging information with an errno.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-3-ERROR2 [chars] ([chars])
Explanation For displaying sysldr debugging information with error string.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-3-FABRIC_DOWN_WARN slot [dec]: fabric connection down. Please investigate the cause
Explanation The card network is non-responsiveness and the fabric ping is failed. The card is not reloaded because of 'service sysldr fabric-ping warn' configuration. This indicates a problem in qnet communicaton.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-3-FIELD_DIAG_ERROR slot equals [dec], [chars]: [chars]
Explanation Field diagnostic binary image download errors.
Recommended Action Initiate the diagnostic again using the 'admin diag' CLI and capture the sysldr log.
Error Message%PLATFORM-SYSLDR-3-FW_NOTFOUND Unable to locate mbus firmware file
Explanation mbus firmware (aka 'ucode') file cannot be found
Recommended Action Obtain sysldr-rp software upgrade.
Error Message%PLATFORM-SYSLDR-3-HARD_FAILURE Hardware error on slot [dec] - stopping
Explanation Card is shutdown due to persistent hardware errors.
Recommended Action Notify your customer support representative.
Error Message%PLATFORM-SYSLDR-3-LOW_LC_MEM slot [dec]: [dec]M present, min [dec]M, [chars]LC not loaded
Explanation For indicating insufficient LC CPU (ie. dram) memory
Recommended Action Upgrade the amount of CPU (dram) memory on the LC.
Error Message%PLATFORM-SYSLDR-3-MALFUNCTION_SHUTDOWN Shutting down card in slot [dec], card is malfunctioning.
Explanation Volatile shutdown was ordered by FCTL because card is malfunctioning.
Recommended Action Investigate the reason for malfunctioning and correct the problem. After they problem is corrected, reload the LC using the 'hardware-module reload' command.
Error Message%PLATFORM-SYSLDR-3-MANY_RESTARTS slot [dec]: too many reload attempts - stopping
Explanation For indicating too many restarts problem.
Recommended Action Ensure that the affected LC is supported. If so, this indicates a problem, and tech support should be contacted. A user could try 'hardware-module slot' once to retry loading of the LC.
Error Message%PLATFORM-SYSLDR-3-MBUS_PING_WARN slot [dec]: CPU not responding, last sequence# [dec], please investigate the cause.
Explanation For displaying notification of LC software non-responsiveness. The slot is not reloaded because of the 'service sysldr mbus-ping warn' configuration.
Recommended Action This indicates a problem in communication w/ the card's CPU via MBUS. A user can try 'hardware-module slot' once to retry loading of the card.
Error Message%PLATFORM-SYSLDR-3-NOT_RESPONDING slot [dec]: [chars] CPU not responding, last sequence# [dec], reloading
Explanation For displaying notification of card software non-responsiveness.
Recommended Action This indicates a problem in communication w/ the card's CPU via MBUS. A user can try 'hardware-module slot' once to retry loading of the card.
Error Message%PLATFORM-SYSLDR-3-SHUTDOWN Shutting down card in slot [dec], shutdown configured.
Explanation Shutdown was configured using the 'hw-module shut' command.
Recommended Action Ensure the shutdown was expected.
Error Message%PLATFORM-SYSLDR-3-TOO_LARGE slot [dec]: LC image too large, not loading
Explanation For displaying notification of LC image being to large to download.
Recommended Action Obtain a properly built image set.
Error Message%PLATFORM-SYSLDR-3-UNKNOWN_MOD slot equals [dec] mod equals [dec] [chars]
Explanation an unexpected moudle in LC sent the reply to sysldr.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-3-UNPOWER Powering Off card in slot [dec], power-down configured.
Explanation power off was configured using the 'hw-module power disable' command.
Recommended Action Ensure the power off was expected.
Error Message%PLATFORM-SYSLDR-3-VOL_SHUTDOWN Shutting down card in slot [dec], ordered by Envmon/FCTL/PSARB
Explanation Card is shut down by Envmon or FCTL or Psarb. It is Volatile shutdown. Please use 'hardware-module reload ..' to bring the card back.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-3-WARM_RLD_NOT_INITIATED slot[dec]: warm reload not initiated by sysmgr ([chars])
Explanation The card WARM reload request to sysmgr returned an error
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-4-DOWN_REV slot [dec]: [chars] is down-rev (V[dec].[dec]), suggest upgrade to (V[dec].[dec]), [chars]
Explanation For displaying down-rev notification.
Recommended Action Ensure that upgrade instructions are followed properly
Error Message%PLATFORM-SYSLDR-4-ERR [chars] ([chars])
Explanation For displaying sysldr debugging information with an errno string.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-4-MBUS_FW slot [dec]: unsupported mbus fw v[dec].[dec] found, replacing ...
Explanation Found an unsupported mbus firmware version running.
Recommended Action No action required. To prevent, do not run IOS images prior.
Error Message%PLATFORM-SYSLDR-4-MBUS_IN_ROM slot [dec]: mbus agent in ROM, downloading RAM mbus fw v[dec].[dec] ...
Explanation Make sure to keep mbus agent running from RAM fw image
Recommended Action No action required. To prevent, do not run IOS images prior.
Error Message%PLATFORM-SYSLDR-4-NO_AUTO_RESET slot [dec]: card failed, auto-reset disabled, needs 'hardware-module location r/s/i reload'
Explanation Warning a user that a card has failed while they have disabled auto-reset.
Recommended Action If auto-reset disable was not intended, it should be unconfigured. 'hardware-module reload' will get a card out of the terminal UNMONITORED state.
Error Message%PLATFORM-SYSLDR-4-NO_RELOAD_SIM_OIR slot [dec]: LC failed, simulated OIR has been requested - LC is now admin-down
Explanation Warning a user that a card has failed while they have turned on 'simulated-OIR'
Recommended Action If similated OIR was not intended, it should be unset. 'hardware-module reload' will get a card out of the ADMIN-DOWN state that this triggers.
Error Message%PLATFORM-SYSLDR-4-SPA_WARNING slot[dec]: [chars]
Explanation Unexpected low severity problem.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-4-UNSUPPORTED slot [dec]: LC type currently unsupported
Explanation For displaying notification of software non-support.
Recommended Action Ensure that the affected LC is supported. If so, this indicates a problem, and tech support should be contacted. A user could try 'hardware-module slot' once to retry loading of the LC.
Error Message%PLATFORM-SYSLDR-4-WARM_RLD_FAILED Receive DOWNLOAD_SUCCESS from slot [dec], while waiting for DOWNLOAD_SUCCESS_WARM
Explanation Card seems to have been cold reloaded after an attempt to warm reload the card.
Recommended Action Capture the sysldr log and use the 'show sysldr trace warm-reload' CLI in admin-mode to fetch debug information. Also capture sysmgr_nv.log from LC.
Error Message%PLATFORM-SYSLDR-4-WARN_LC_MEM slot [dec]: [dec]M present, recommend [dec]M memory
Explanation For indicating possibly insufficient LC CPU (ie. dram) memory
Recommended Action Upgrade the amount of CPU (dram) memory on the LC.
Error Message%PLATFORM-SYSLDR-4-WARN2 [chars]
Explanation Unexpected low severity problem.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-5-BANDWIDTH Fabric bandwidth change: [chars]
Explanation Failure/recovery/OIR of one or more SFC's or CSC's
Recommended Action Verify that the desired fabric bandwidth is being used.
Error Message%PLATFORM-SYSLDR-5-BANDWIDTH_RESTART Fabric bandwidth change: Restarting card in slot [dec]
Explanation Restoration or OIR of fabric bandwidth has allowed a card to be restarted
Recommended Action Celebrate.
Error Message%PLATFORM-SYSLDR-5-DRP_DISABLED DRP in slot [dec] is now disabled, reloading
Explanation The RP is going to bring down from IOX running state because keep alive message ping is not received to sysldr.
Recommended Action Ensure that the disabling of this DRP was expected.
Error Message%PLATFORM-SYSLDR-5-JOIN Joined slot [dec] - already running IOX-LC
Explanation LC join notification because of sysldr restarted.
Recommended Action Ensure that the *sysldr* restart was expected.
Error Message%PLATFORM-SYSLDR-5-LC_ENABLED LC in slot [dec] is now running IOX
Explanation For displaying health and readiness of LC
Recommended Action Ensure that the (implied) LC restart was expected.
Error Message%PLATFORM-SYSLDR-5-MBUS_EEPROM slot [dec]: Unable to get mbus eeprom contents
Explanation For displaying notification of mbus nonresponsiveness to get eeprom contents.
Recommended Action This indicates that mbus request to get eeprom contents for show diag command has timed out. Retry the command again.
Error Message%PLATFORM-SYSLDR-5-MON_DRP Now monitoring DRP in slot [dec] - running IOX-DRP
Explanation For displaying notification of discovered DRP.
Recommended Action Ensure that the existence of the external DRP was expected.
Error Message%PLATFORM-SYSLDR-5-MON_RP Now monitoring RP in slot [dec] - running IOX-RP
Explanation For displaying notification of discovered RP.
Recommended Action Ensure that the existence of the external RP was expected.
Error Message%PLATFORM-SYSLDR-5-OIRIN OIR: Node [chars] inserted
Explanation Entity specified in the messages is inserted into the chassis.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-5-OIROUT OIR: Node [chars] removed
Explanation Entity specified in the messages is removed from the chassis.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-5-RESTART Restarted slot [dec] - now running IOX-LC
Explanation For displaying LC restart notification.
Recommended Action Ensure that the LC restart was expected.
Error Message%PLATFORM-SYSLDR-5-RESTART_REQ Accepted restart request for slot [dec]. [chars]
Explanation For displaying LC restart requests.
Recommended Action Ensure that the *sysldr* restart request was expected.
Error Message%PLATFORM-SYSLDR-5-RP_DISABLED RP in slot [dec] is now disabled, reloading
Explanation The RP is going to bring down from IOX running state because keep alive message ping is not received to sysldr.
Recommended Action Ensure that the disabling of this RP was expected.
Error Message%PLATFORM-SYSLDR-5-RP_ENABLED RP in slot [dec] is now running IOX
Explanation For displaying health and readiness of RP
Recommended Action None
Error Message%PLATFORM-SYSLDR-6-AUX_CARDS_INFO slot[dec]: [chars]
Explanation For displaying sysldr informational events.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-6-CANJAMRST slot [dec]: non-zero CAN jam reset counter
Explanation The non-volatile MBUS CAN jam reset counter is incremented when the MBUS agent detects a CAM jam condition and hard-resets itself in an attempt to recover. It is an idication thet there might be a faulty MBUS module somewhere in the system, not necesarily on this particular card.
Recommended Action Use the show diags details command to read the EEPROM contents and report this to your technical support representative.
Error Message%PLATFORM-SYSLDR-6-CARD_KDUMPER Card ungraceful reboot detected in slot [dec].
Explanation For displaying health and readiness of a card
Recommended Action Ensure that the card restart was expected.
Error Message%PLATFORM-SYSLDR-6-CARD_REBOOT Card graceful reboot detected in slot [dec].
Explanation The specified slot is graceful rebooting
Recommended Action Ensure that the card restart was expected.
Error Message%PLATFORM-SYSLDR-6-DEBUG slot[dec]: [chars]
Explanation sysldr debugging information.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-6-INFO [chars]
Explanation For displaying sysldr's informational events.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-6-LTRACE_INIT_ERR Failed to initialize ltrace buffer in [chars]. Error: [chars]
Explanation Ltrace buffer will not be available. Debuggability will be reduced because of lacking of ltrace buffer.
Recommended Action This indicates a low memory condition. Memory on the box must be running low - are there services that can be stopped, or can more memory be added?
Error Message%PLATFORM-SYSLDR-6-WARM_RLD_REJECTED Presently unsupported card WARM reload condition: [chars]
Explanation The card WARM reload is presently unsupported in the specified condition
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-7-DEBUG_INIT_EVENT_FAILED [chars]: debug_init_event([chars]) failed error [chars]
Explanation Failed to switch ON debug event on sysldr server side.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-7-DEBUG_REGISTER_FAILED [chars]: debug register failed error [chars]
Explanation Failed to register debug events on sysldr server side.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-7-ERR_MEM_ALLOC Insufficient memory.
Explanation Unable to allocate more heap memory.
Recommended Action Make sure the application/process memory usage or leak.
Error Message%PLATFORM-SYSLDR-7-ERR_SYSDB_CONNECTION Connection to sysdb path '[chars]' failed: '[chars]'.
Explanation Unable to maintain connection to a critical sysdb path.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-7-ERR_SYSDB_DELETE slot [dec]: sysdb_item_delete failed for item '[chars]' in file equals [chars], line equals [dec] ([chars] [hex])
Explanation Unable to delete a sysdb item.
Recommended Action 'No action is required.'
Error Message%PLATFORM-SYSLDR-7-ERR_SYSDB_GET slot [dec]: sysdb_item_get failed for item '[chars]' in file equals [chars], line equals [dec] ([chars] [hex])
Explanation Unable to set a sysdb item.
Recommended Action 'No action is required.'
Error Message%PLATFORM-SYSLDR-7-ERR_SYSDB_NOTIFY Notification for changes to sysdb bindpoint '[chars]', tuple '[chars]' failed: '[chars]'.
Explanation Unable to receive notifications of changes to a critical sysdb tuple.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-7-ERR_SYSDB_SET slot [dec]: sysdb_item_set failed for item '[chars]' in file equals [chars], line equals [dec] ([chars] [hex])
Explanation Unable to set a sysdb item.
Recommended Action 'No action is required.'
Error Message%PLATFORM-SYSLDR-7-FATAL [chars], error equals [dec]
Explanation Error in thread/event manager creation for sysldr process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-SYSLDR-7-INTERNAL_ERROR Internal Error. File [chars], line [dec]: [chars].
Explanation Serious internal logic or data error.
Recommended Action 'No action is required.'
Error Message%PLATFORM-SYSLDR-7-WARM_RLD_OK Receive DOWNLOAD_SUCCESS_WARM from slot [dec], new processes are coming up
Explanation Card seems warm reloaded successfully
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-7-WARNING slot[dec]: [chars]
Explanation For displaying sysldr debugging information.
Recommended Action No action is required.
TOPMGR Messages
Error Message%PLATFORM-TOPMGR-2-INIT_FAILURE Failed to initialze Topology Manager: [chars]
Explanation This syslog is printed when Topology Manager or its clients fail to initialize necessary data structures and memories. If the error originates from the system call the error message is also printed.
Recommended Action Based on the system error message the user can tell what went wrong. More likely than not, the user has to restart the system. If the problem persists he or she has to contact Cisco customer support team.
Error Message%PLATFORM-TOPMGR-2-MALLOC_FAILURE Failed to allocate memory: [chars]
Explanation An explanation is provided in the syslog.
Recommended Action A user should be able to tell what went wrong and take actions accordingly. For instance, if the system runs out of memory then more memory needs to be installed.
Error Message%PLATFORM-TOPMGR-3-CHILD_NOTFOUND Child interface not found: ifhandle equals [unsigned int]
Explanation Although a reference to a child interface is found in the parent interface, the child interface cannot be found via the search routine. Either the child interface failed to be added in the first place or the reference was not cleared when the child was deleted.
Recommended Action Examine the trace buffers and pay attention to all the insert and delete operations.
UPGRADE_FPD Messages
Error Message%PLATFORM-UPGRADE_FPD-2-FATAL [chars]
Explanation A fatal error was encountered, and the program exited.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-UPGRADE_FPD-3-ASYNC_ATTACH Failed to attach async message handler : [chars]
Explanation Failed to attach async message handler
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-UPGRADE_FPD-3-CHAN_CREATE Failed to create upgrade-fpd channel : [chars]
Explanation Failed to create lc_fpd_upgrade (driver) channel using event_manager_create.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-UPGRADE_FPD-3-ERROR [chars]
Explanation An error was encountered
Recommended Action No action is required.
Error Message%PLATFORM-UPGRADE_FPD-3-EVT_BLOCK Event block failed : [chars]
Explanation Failed to block event
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-UPGRADE_FPD-3-FAILED Failed to update FPD : [chars] [chars]
Explanation The update operation for the specified FPD has failed.
Recommended Action Retry the operation to update the image. If the retry operation fails, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-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 and provide the representative with the information you have gathered. 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%PLATFORM-UPGRADE_FPD-3-MSG_REPLY Msg reply failed : [chars]
Explanation Failed to send message reply
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-UPGRADE_FPD-3-SYNC_ATTACH Failed to attach sync message handler : [chars]
Explanation Failed to attach sync message handler
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-UPGRADE_FPD-4-DOWN_REV [chars] [chars] instance [dec] is down-rev (V[dec].[dec]), upgrade to (V[dec].[dec]). Use the upgrade hw-module fpd CLI in admin mode.
Explanation For displaying down-rev notification.
Recommended Action tech support should be contacted for upgrade instructions
Error Message%PLATFORM-UPGRADE_FPD-4-ROMMONA_DOWN_REV [chars] [chars] instance [dec] is down-rev (V[dec].[dec]), upgrade to (V[dec].[dec]). Please consult TAC or Firmware Upgrade documentation before proceeding to upgrade rommonA.
Explanation For displaying down-rev notification.
Recommended Action tech support should be contacted for upgrade instructions
Error Message%PLATFORM-UPGRADE_FPD-4-UP_REV [chars] [chars] instance [dec] is severely up-rev (V[dec].[dec]), downgrade to (V[dec].[dec]). Use the upgrade hw-module fpd CLI in admin mode.
Explanation For displaying severely up-rev notification.
Recommended Action tech support should be contacted for downgrade instructions
Error Message%PLATFORM-UPGRADE_FPD-4-WARNING [chars]
Explanation display warning messages
Recommended Action No action is required.
Error Message%PLATFORM-UPGRADE_FPD-6-PASSED Successfully [chars] [chars] subtype image for [chars] on location [chars]
Explanation It indicates that a FPD has been upgraded or downgraded successfully. The current image version and the upgraded image version are displayed.
Recommended Action No action is required.
Error Message%PLATFORM-UPGRADE_FPD-6-START Starting to [chars] [chars] subtype image from [dec].[dec] to [dec].[dec] for [chars] on location [chars]
Explanation It indicates that a FPD image upgrade or downgrade has started. The current image version and the upgraded image version are displayed.
Recommended Action No action is required.
UPGRADE Messages
Error Message%PLATFORM-UPGRADE-3-FL_SIZE Overflow in fabric-loader upgrade.
New fabric-loader size equals [dec] available size equals [dec]Explanation When upgrading the new fabric-loader, if the size of the new fabric-loader is greater than the avilable size overflow error is reported.
Recommended Action Check the new fabric-loader size.
Error Message%PLATFORM-UPGRADE-3-IMAGE_UNAVAIL Unable to find upgrade image for this cardtype within IOX
Explanation The upgrade was unable to complete because the image to burn into flash could not be located within IOX.
Recommended Action Collect information for Routing Processor type and contact Tech Support.
Error Message%PLATFORM-UPGRADE-3-INVALID_IMAGETYPE Invalid image type specified in upgrade message ([dec])
Explanation The message used to initiate the upgrade contained an image type that was invalid.
Recommended Action Collect information for Routing Processor type and contact Tech Support.
Error Message%PLATFORM-UPGRADE-3-INVALID_MSGTYPE Invalid message type specified in upgrade message ([dec])
Explanation The message used to initiate the upgrade contained a message type that was invalid.
Recommended Action Collect information for Routing Processor type and contact Tech Support.
Error Message%PLATFORM-UPGRADE-3-NEW_ROM_SIZE Overflow in ROM monitor upgrade.
New ROM monitor size equals [dec] available size equals [dec]Explanation When upgrading the new rommon, if the size of the new rommon is greater than the available size overflow error is reported.
Recommended Action Check the new ROMMON size.
Error Message%PLATFORM-UPGRADE-3-NEW_ROM_SIZE Overflow in ROM monitor upgrade.
New ROM monitor size equals [dec] available size equals [dec]Explanation When upgrading the new rommon, if the size of the new rommon is greater than the available size overflow error is reported.
Recommended Action Check the new ROMMON size.
Error Message%PLATFORM-UPGRADE-3-RP_WARNING [chars]
Explanation When upgrading the new rommon, RP's rommon will be corrupted if the user reload the RP. So, The user must not reload RP when its rommon is being upgraded. If RP's rommon is corrupted, it needs to be RMAd.
Recommended Action The user must not reload RP when it's rommon is being upgraded.
Error Message%PLATFORM-UPGRADE-3-SETUP_FAILURE Unable to properly set up upgrade infrastructure. Internal error
Explanation The upgrade was unable to complete because the type of the card did not fall into the expected set of possibilities. This is likely due to an internal programming error.
Recommended Action Collect information for Routing Processor type and contact Tech Support.
Error Message%PLATFORM-UPGRADE-3-VERSION_MISSING Unable to complete upgrade. Cannot determine version info (rc equals [dec])
Explanation The upgrade was unable to complete because the version of either the current ROMMON image or the version of the image to be used for the upgrade could not be determined.
Recommended Action Collect information for Routing Processor type and contact Tech Support.
Error Message%PLATFORM-UPGRADE-7-ERASE_SECTORS Erase sectors fail for [chars]
Explanation The upgrade of the specfied component (ROMMON/Fabric-loader) failed because failed to erase sectors.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-ERASE_SECTORS Erase sectors fail for [chars]
Explanation The upgrade of the ROMMON failed because failed to erase sectors.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-ERR_BUF_READ Failed to read file [chars]
Explanation The upgrade of the ROMMON failed because failed to read the file buffer. It will not affect the existing service on the card.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-ERR_BUF_READ Failed to read file [chars]
Explanation The upgrade of the specfied component (ROMMON/Fabric-loader) failed because of a file read system call failed.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-ERR_CHAN_CREATE Failed to create upgrade ROM channel : [chars]
Explanation Failed to create upgrade ROM channel using event manager.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-ERR_DEBUG_INIT Debug initialization failed
Explanation Initialization of the debug event failed during ROMMON upgrade. This can be observed when the debug is enabled.
Recommended Action No action is required.
Error Message%PLATFORM-UPGRADE-7-ERR_DEBUG_REG Debug registration failed : [chars]
Explanation debug registration call failed during ROMMON upgrade. This can be observed when the debug is enabled.
Recommended Action No action is required.
Error Message%PLATFORM-UPGRADE-7-ERR_EVENT_MGR [chars] : [chars]
Explanation Generic failure of any event manager API.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-UPGRADE-7-ERR_FILE_OPEN Failed to open file [chars] : [chars]
Explanation The upgrade of the ROMMON failed because failed to open the image file. It will not affect the existing service on the card.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-ERR_FILE_OPEN Failed to open file [chars] : [chars]
Explanation The upgrade of the specfied component (ROMMON/Fabric-loader) failed because of a system call fails to open the relevant file.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-ERR_LWM_REPLY Failed to send reply message : [chars]
Explanation KAA process failed to reply back to sysldr client on the upgrade results using LWM.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-ERR_MEM_ALLOC Failed to allocate memory
Explanation This indicates a low memory condition. The upgrade of the specfied component would fail.
Recommended Action Memory on the box must be running low - are there services that can be stopped, or can more memory be added?
Error Message%PLATFORM-UPGRADE-7-ERR_MEM_ALLOC Failed to allocate memory
Explanation This indicates a low memory condition. The upgrade of the specfied component would fail.
Recommended Action Memory on the box must be running low - are there services that can be stopped, or can more memory be added?
Error Message%PLATFORM-UPGRADE-7-FLASH_DEVICE Flash device unsupported. RP ROMMON upgrade aborting
Explanation The flash type discovered does not match the list of supported devices.
Recommended Action Collect information for Routing Processor type.
Error Message%PLATFORM-UPGRADE-7-FLASH_DEVICE Flash Device is not AM29LV800B - Linecard upgrade won't continue
Explanation The current driver only supports AM29LV800B flash device.
Recommended Action No action is required.
Error Message%PLATFORM-UPGRADE-7-GET_SLOT Failed to get slot number
Explanation The platform library call to retrieve the slot information failed.
Recommended Action No action is required.
Error Message%PLATFORM-UPGRADE-7-MMAP Failed to map device address : [chars]
Explanation A system call failed to map the device physical address.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-MMAP Failed to map device address : [chars]
Explanation A system call failed to map the device physical address.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-MUNMAP Failed to unmap mapped object : [chars]
Explanation A system call failed to un-map the device physical address.
Recommended Action No action is required.
Error Message%PLATFORM-UPGRADE-7-MUNMAP Failed to unmap mapped object : [chars]
Explanation A system call failed to un-map the device physical address.
Recommended Action No action is required.
Error Message%PLATFORM-UPGRADE-7-PROGRAM_FLASH Programming flash fail for [chars]
Explanation The upgrade of the specfied component (ROMMON/Fabric-loader) failed because failed in programming flash.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-PROGRAM_FLASH Programming flash fail for [chars]
Explanation The upgrade of the ROMMON failed because failed to erase sectors.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-PROGRAM_FLASH_HEADER Programming flash header fail for [chars]
Explanation The upgrade of the specfied component (ROMMON/Fabric-loader) failed because failed in programming flash header.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-STAT Failed to access file [chars] : [chars]
Explanation The upgrade of the ROMMON failed because failed to get file stat. It will not affect the existing service on the card.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-STAT Failed to access file [chars] : [chars]
Explanation The upgrade of the specfied component (ROMMON/Fabric-loader) failed because of file download statistic system call failure.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-STATUS_SEND Failed to send status
Explanation The KAA process failed to send the upgrade status to the client, sysldr.
Recommended Action The sysldr log needs to be refered for the explanation. The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-VERIFY_FLASH Verify flash fail for [chars]
Explanation The upgrade of the specfied component (ROMMON/Fabric-loader) failed because failed to verify flash.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-VERIFY_FLASH Verify flash fail for [chars]
Explanation The upgrade of the ROMMON failed because failed to verify FLASH.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-VERIFY_FLASH_HEADER Verify flash header fail for [chars]
Explanation The upgrade of the specfied component (ROMMON/Fabric-loader) failed because failed to verify flash header.
Recommended Action The upgrade commands needs to be retried on RP.
VCDMA Messages
Error Message%PLATFORM-VCDMA-7-ERR_BAG_REG Bag register failed for rules. Reason: [chars]
Explanation EDM Bags are used to share information between components using sysdb. This Error indicates that bag registration failed.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-VCDMA-7-ERR_DLL_INIT Dll Initialization for [chars] failed. Reason: [chars]
Explanation Cpuctrl driver tried to register for a dll but it encountered an error. The driver might lose some of its functionality.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-VCDMA-7-ERR_EVM_CREATE Event Manager create failed for [chars]. Reason: [chars]
Explanation Cpuctrl Event Manager create error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-VCDMA-7-ERR_EVM_NOTIFY Event Manager notify failed for [chars]. Reason: [chars]
Explanation Cpuctrl Event Manager notify error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-VCDMA-7-ERR_SYSDB_EDM_REG Sysdb Register EDM failed. Reason: [chars]
Explanation Cpuctrl Sysdb Register EDM error
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
VKG_AMCC2035 Messages
Error Message%PLATFORM-VKG_AMCC2035-3-ERROR_EXIT Exiting because [chars], error code [chars]
Explanation The Ether-Ctrl process exited due to the reason mentioned in the message.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. Execute 'show process ether-ctrl location ' to verify that the process is up and running. If it is still non-operational, try doing from the admin mode 'process restart envmon location '. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-VKG_AMCC2035-3-IF_OPERATION_FAIL [chars], port [dec], error code [chars]
Explanation The particular operation mentioned in the message failed due to some reason. This is not a critical failure, the process can continue functioning as expected despite the failure.
Recommended Action Debug message only. No action is required.
Error Message%PLATFORM-VKG_AMCC2035-3-OPERATION_FAIL Failed to [chars], error code [chars]
Explanation The particular operation mentioned in the message failed due to some reason. This is not a critical failure, the process can continue functioning as expected despite the failure.
Recommended Action Debug message only. No action is required.
Error Message%PLATFORM-VKG_AMCC2035-7-INFO [chars] [chars]
Explanation The particular operation mentioned in the message occured due to some reason. This is not a critical failure, the process can continue functioning as expected despite the failure.
Recommended Action Debug message only. No action is required.
WD_PLATFORM Messages
Error Message%PLATFORM-WD_PLATFORM-2-FAILED_TO_TICK HW Watchdog: instance: [dec], tid: [dec] failed to tick, curr failed tick count: [dec], tick_owner: [dec]
Explanation Some kind of internal fault has occurred.
Recommended Action please check with TAC.
Error Message%PLATFORM-WD_PLATFORM-2-INTERNAL_ERROR HW Watchdog: detected an internal error, [chars]:[dec]
Explanation Some kind of internal fault has occurred.
Recommended Action please check with TAC.
Error Message%PLATFORM-WD_PLATFORM-3-INVALID_TICK_CALL HW Watchdog: invalid ticker thread tid: [dec], not registered
Explanation Some kind of internal fault has occurred.
Recommended Action please check with TAC.
Error Message%PLATFORM-WD_PLATFORM-3-SRP_STATE_CHANGE_REG_FAILED HW Watchdog: registration for sysmgr srp state change notification failed, rc: [dec], [chars]
Explanation Some kind of internal fault has occurred.
Recommended Action please check with TAC.
Error Message%PLATFORM-WD_PLATFORM-4-INVALID_TICKER HW Watchdog: invalid ticker thread added, CPU: [dec], tid: [dec]
Explanation Some kind of internal fault has occurred.
Recommended Action please check with TAC.
Error Message%PLATFORM-WD_PLATFORM-4-WATCHDOG_STATE HW Watchdog: disabled on this node.
Explanation The driver software has detected that the watchdog is disabled on the node. Disabling the watchdog is not a recommended as it can lead to unrecoverable node halts.
Recommended Action Determine the reason for the watchdog being disabled. This could be due to incorrect ROMMON env var WD_WATCHDOG_MODEsetting. If this is set intentionally then no further action is required. Otherwise, please check with TAC.
Error Message%PLATFORM-WD_PLATFORM-6-SRP_READY_STATE HW Watchdog: [chars], [chars]
Explanation Some kind of internal fault has occurred.
Recommended Action please check with TAC.
XCVR Messages
Error Message%PLATFORM-XCVR-3-ERROR XCVR-Err: [chars]
Explanation This is an error message from the XCVR, it indicates that something has gone wrong internally in the XCVR.
Recommended Action File a DDTS
Error Message%PLATFORM-XCVR-3-FAILURE XCVR-FAILURE: [chars]
Explanation This is a failure message from the XCVR
Recommended Action *RECUR*
Error Message%PLATFORM-XCVR-6-ENABLE Transceiver(slot:[dec]/bay:[dec]/port:[dec]) ENABLED
Explanation This is an informational message from the XCVR
Recommended Action *RECUR*
Error Message%PLATFORM-XCVR-6-INFO XCVR-Info: [chars]
Explanation This is an informational message from the XCVR
Recommended Action *RECUR*
Error Message%PLATFORM-XCVR-6-OIR XCVR-OIR: [chars]
Explanation This is an informational message from the XCVR
Recommended Action *RECUR*
Error Message%PLATFORM-XCVR-6-REMOVAL Transceiver(slot:[dec]/bay:[dec]/port:[dec]) REMOVED
Explanation This is an informational message from the XCVR
Recommended Action *RECUR*
Error Message%PLATFORM-XCVR-7-TRACE XCVR-Trace: [chars]
Explanation This is a debuging message from the XCVR
Recommended Action *NONE*