-
Cisco IOS XR System Error Message Reference Guide, Release 3.2
-
Preface
-
Cisco IOS XR System Error Messages Overview
-
Access Control List (ACL) Error Messages for Cisco IOS XR
-
Fabric (FABRIC) Error Messages for Cisco IOS XR
-
Hardware Accessibility (HA) Messages for Cisco IOS XR
-
Installation (INSTALL) Messages for Cisco IOS XR
-
Internet Protocol (IP) Messages for Cisco IOS XR
-
Layer 2 (L2) Messages for Cisco IOS XR
-
Media (MEDIA) Messages on Cisco IOS XR
-
Manageability (MGBL) Messages for Cisco IOS XR
-
Operating System (OS) Messages for Cisco IOS XR
-
Packet Infrastructure (PKT_INFRA) Messages for Cisco IOS XR
-
Platform (PLATFORM) Messages for Cisco IOS XR
-
Quality of Service (QOS) Messages for Cisco IOS XR
-
Routing (ROUTING) Messages for Cisco IOS XR
-
Security (SECURITY) Messages for Cisco IOS XR
-
Simple Network Management Protocol (SNMP) Messages for Cisco IOS XR
-
System Database (SYSDB) Messages for Cisco IOS XR
-
Feedback
Table Of Contents
Platform Messages
This section contains all Platform related System Error Messages, such as shelf magr, chassis, env ctrl, and so forth. The following facility codes are represented in this module:
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.
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-3-BADDESC_ERR Assembler detected a bad descriptor error: Data [hex]
Explanation Assembler detected a bad descriptor in the free queue. The hex number indicates the error cause register value. This usually indicates a hardware problem on the RP.
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-ASM-3-CRC_ERR assembler dll: block: [chars], entity: [chars] had CRC error, count: [dec]
Explanation PII block got a packet from the entity mentioned above with a CRC error.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-ASM-3-DEVICE_HALT FFQ: device halted, sub-block: [chars], halted entity: [chars]
Explanation FFQ, ASIC got halted. The halted block and its parent block are provided
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-ASM-3-FATAL assembler dll: fatal error encountered, reason=[chars]
Explanation iqm, assembler dll 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-ASM-3-FATAL_2 assembler dll: fatal error encountered, reason=[chars], errno=[dec]
Explanation assembler 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-ASM-3-FIA_INTFERR Assembler detected a FIA interface error: Data [hex]
Explanation Assembler detected an error with the fia interface. The hex number indicates the error cause register value. This usually indicates a hardware problem on the RP.
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-ASM-3-FIA_PARITYERR Assembler detected a FIA parity error: Data [hex]
Explanation A parity error has been detected on the assembler to fia interface. The hex number indicates the error cause register value. This usually indicates a hardware problem on the RP.
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-ASM-3-FQEMPTY_ERR Assembler detected a free queue empty error: Data [hex]
Explanation Assembler detected a that the free queue is empty. The hex number indicates the error cause register value.
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-ASM-3-GEN_INFO assembler dll: general information,
Explanation The ASM's informational 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.
Error Message%PLATFORM-ASM-3-HWINIT_INCOMPLETE assembler dll: hardware initialization not complete
Explanation hardware init is not complete.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-ASM-3-INFO assembler dll: service degrading error, reason = [chars]
Explanation The assembler encountered an error that would lead to degraded service.
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-ASM-3-INTR_ENABLE_FAIL assembler dll: intr enable at addr: [hex] mask: [hex] failed.
Explanation hardware state is not correct.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-ASM-3-INTR_STATUS_GET_ERR assembler dll: intr status get failed for: [chars]@[hex], rc=[dec]
Explanation Hardware register read failed.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-ASM-3-MALLOC_FAILED assembler dll: fatal memory allocation error for bytes
Explanation ASM encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-ASM-3-NOT_AVAILABLE assembler dll: asic is not available
Explanation hardware state is not correct.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-ASM-3-NOT_OPERATIONAL assembler dll: asic is not operational, state: [dec]
Explanation hardware state is not correct.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-ASM-3-NOT_YET_IMPLEMENTED assembler dll: this function is not yet implemented
Explanation FFQ, assembler dll , a function is not implemented.
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-ASM-3-RESET_ERR Assembler is being reset because of too many errors.
Explanation Assembler software driver is seeing too many errors that indicated a problem with the hardware. Some of the error logs prior to this message should indicate the errors that lead to this 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-ASM-6-UNHANDLED_HALT assembler dll: halt not handled, parent: [chars], child: [chars], intr: [dec]
Explanation Hardware halt is not handled.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-ASM-6-UNHANDLED_INTR assembler dll: intr not handled, parent: [chars], child: [chars], group id: [dec], intr: [dec]
Explanation Hardware interrupt is not handled in the code, need to implement.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
BCM Messages
Error Message%PLATFORM-BCM-4-CONNECT_FAIL Broadcom Switch driver not available, Errno [hex]
Explanation Failed to connect to Broadcom Driver 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-BCM-4-MSGSEND_FAIL Message Send Failed in function [chars] , Errno : [hex]
Explanation Failed to send message to Broadcom Driver process using its 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-BCM-4-PULSESEND_FAIL Sending Pulse Failed in function [chars] , Errno : [hex]
Explanation Failed to send Pulse to Broadcom driver process using its 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.
BP_SERVER Messages
Error Message%PLATFORM-BP_SERVER-3-TOO_MANY_RP [chars]
Explanation When more than 2 RPs (active/standby) are used in the same chassis, one must be elected as the dSC, the master of the chassis. In order to select which RP will become the dSC, insert only the RPs that will be part of the Owner Logical Router (maximum of 2 RPs). Once these RPs are fully booted, you may insert other RPs as required and assign them to manage logical routers. At this point, chassis mastership has been determined and subsequent power-cycle of the chassis will support multiple RPs with no problem.
Recommended Action Eject RPs that are unused or not in the Owner Logical Router. Ensure there are no more than 2 RPs inserted. Reload the RPs. Wait for console promt. Insert other RP cards and load them as required.
CARDMGR Messages
Error Message%PLATFORM-CARDMGR-3-ADJ_RES_FAILED could not adjust resource: [chars]: [chars]
Explanation Could not adjust resource
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-CARDMGR-3-BAD_CS_INFO could not get CS revision info!
Explanation Could not get CS revision info
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-CARDMGR-3-BAD_OPEN could not open [chars]: [chars]
Explanation Open of file 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-CARDMGR-3-BIND_FAILED bind '[chars]' to socket [dec] failed: [chars]
Explanation Bind 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-CARDMGR-3-BIND_MTD_REGION_FAILED bind MTD '[chars]' to region at [hex] failed: [chars]
Explanation Bind mtd region 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-CARDMGR-3-BIND_MTD_SOCKET_FAILED bind MTD '[chars]' to socket [dec] failed: [chars]
Explanation Bind mtd to socket 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-CARDMGR-3-CHDIR_FAILED chdir to [chars] failed: [chars]
Explanation Chdir 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-CARDMGR-3-CIS_DATA_PARSING_ERROR error parsing CIS([hex]) on socket [dec]: [chars]
Explanation CIS data parsing 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-CARDMGR-3-CIS_DATA_READ_ERROR error reading CIS data on socket [dec]: [chars]
Explanation CIS data read 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-CARDMGR-3-CIS_REPLACE_ERROR could not replace CIS: [chars]
Explanation CIS replace 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-CARDMGR-3-CS_REL_MISMATCH Card Services release does not match
Explanation Release mismatch
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-CARDMGR-3-GET_DEV_INFO_FAILED get device info on socket [dec] failed: [chars]
Explanation Device info 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-CARDMGR-3-MODULE_UNAVAILABLE module [chars] not available
Explanation Module unavailable
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-CARDMGR-3-NO_CARDS_DEFINED no cards defined
Explanation No cards defined
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-CARDMGR-3-NO_DRIVERS_FOUND no device drivers defined
Explanation No device drivers
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-CARDMGR-3-NO_MEM Malloc failure
Explanation Out of 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-CARDMGR-3-NO_SOCKETS no sockets found!
Explanation No sockets
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-CARDMGR-3-OPEN_SOCK_FAILED open_sock(socket [dec]) failed: [chars]
Explanation Open of socket 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-CARDMGR-3-PCMCIA_INIT_ERROR PCMCIA initialization error at: [chars]
Explanation PCMCIA initialization 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-CARDMGR-3-READ_FAILED read ([dec]): [chars]
Explanation Read 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-CARDMGR-3-SELECT_FAILURE select (): [chars]
Explanation Select 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-CARDMGR-3-THREAD_CREATE_FAILED Thread create failed: [chars]
Explanation Thread create 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-CARDMGR-3-UNBIND_FAILED unbind '[chars]' from socket [dec] failed: [chars]
Explanation Unbind 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-CARDMGR-3-UNBIND_MTD_FAILED unbind MTD '[chars]' from socket [dec] failed: [chars]
Explanation Unbind MTD 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-CARDMGR-3-UNSUPPORTED_CARD Unsupported card in socket [dec]
Explanation Unsupported card
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-CARDMGR-6-PRODUCT_INFO product info: [chars]
Explanation Product info
Recommended Action No action is required.
Error Message%PLATFORM-CARDMGR-6-SOCKET_INFO socket [dec]: [chars]
Explanation Socket info
Recommended Action No action is required.
CCTL Messages
Error Message%PLATFORM-CCTL-3-ENVMON_CFG_INIT_FAIL [CCTL-ENVMON-CFG-INIT]: Unable to create Envmon config space at [chars]
Explanation The process that services the Read EEPROM Protocol requests exitted due to some reason
Recommended Action None.
Error Message%PLATFORM-CCTL-3-ENVMON_INIT_FAIL [CCTL-ENVMON-INIT]: Server process exiting because [chars]
Explanation The process that services the Read EEPROM Protocol requests exitted due to some reason
Recommended Action None.
Error Message%PLATFORM-CCTL-3-FATAL_EXIT [CCTL-ENVMON]: Chassis Control Driver/Envmon process exiting because [chars]
Explanation The Chassis Control driver process exitted due to some reason
Recommended Action None.
Error Message%PLATFORM-CCTL-3-GEN_ERROR [CCTL-ENVMON]: [chars]
Explanation Some error occured
Recommended Action None.
Error Message%PLATFORM-CCTL-3-IDPROM_FATAL_EXIT [READ_EEPROM_PROTOCOL]: Server process exiting because [chars]
Explanation The process that services the Read EEPROM Protocol requests exitted due to some reason
Recommended Action None.
Error Message%PLATFORM-CCTL-3-READ_POWER_SHELF_TYPE_FAILURE [CCTL-ENVMON]: 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 None.
Error Message%PLATFORM-CCTL-3-SENSOR_INIT_FAIL [CCTL-ENVMON]: Unable to initialize the sensors on [chars]
Explanation The Chassis Control driver process was unable to initialize the sensors due to some error, typically no power to the sensors.
Recommended Action None.
Error Message%PLATFORM-CCTL-3-SERVER_FATAL_EXIT [CCTL-SERVER]: Chassis Control Driver LWM server process exiting because [chars]
Explanation The Chassis Control driver LWM server process exitted due to some reason
Recommended Action None.
Error Message%PLATFORM-CCTL-3-SERVER_SEND_SHELFMGR_PULSE_FAILED [CCTL-SERVER]: Unable to send pulse to shelfmgr because an error occured during [chars]. FATAL ERROR: This failure will cause no power to be turned on to the motherboard.
Explanation The Chassis Control driver LWM server process was unable to send pulse to shelfmgr to indicate that process is ready
Recommended Action None.
Error Message%PLATFORM-CCTL-3-SPA_OIR_REGISTER_FAIL [CCTL-ENVMON]: Envmon unable to register for SPA OIR notifications
Explanation The envmon process was unable to register for SPA OIR notifications
Recommended Action None.
Error Message%PLATFORM-CCTL-3-SPA_SERVER_FATAL_EXIT [CCTL-SPA-SERVER]: Chassis Control SPA LWM server process exiting because [chars]
Explanation The Chassis Control SPA LWM server process exitted due to the mentioned reason
Recommended Action None.
Error Message%PLATFORM-CCTL-3-SPA_SHUTDOWN_SYSDB_BIND_FAIL [CCTL-ENVMON]: Envmon unable to bind to the namespace ([chars]) that handles SPA shutdown
Explanation The envmon process was unable to bind to the namespace that handles SPA shutdown, probably due to backend infra not being ready or available.
Recommended Action None.
Error Message%PLATFORM-CCTL-4-DEBUG_INIT_WARN [CCTL-ENVMON]: Unable to initialize debug space
Explanation The Chassis Control driver process was unable to initialize the debug space
Recommended Action None.
Error Message%PLATFORM-CCTL-4-DEBUG_REG_WARN [CCTL-ENVMON]: Unable to register for debug services
Explanation The Chassis Control driver process was unable to register for debug services
Recommended Action None.
Error Message%PLATFORM-CCTL-4-MMAP_FAILED [ENVMON]: mmap call failed, implies [chars]
Explanation Some mmap call failed with the mentioned implications.
Recommended Action None.
Error Message%PLATFORM-CCTL-4-MSG_CHAN_CONN_FAIL [ENVMON]: msg_chan_connect to [chars] failed
Explanation A msg_chan_connect() to the mentioned server path failed.
Recommended Action None.
Error Message%PLATFORM-CCTL-4-MSG_SEND_ASYNC_FAIL [ENVMON]: msg_send_async to [chars] failed
Explanation A msg_send_async() to the mentioned server path failed.
Recommended Action None.
Error Message%PLATFORM-CCTL-4-SERVER_DEBUG_INIT_WARN [CCTL-SERVER]: Unable to initialize debug space
Explanation The Chassis Control driver LWM server process was unable to initialize the debug space
Recommended Action None.
Error Message%PLATFORM-CCTL-4-SERVER_DEBUG_REG_WARN [CCTL-SERVER]: Unable to register for debug services
Explanation The Chassis Control driver LWM server process was unable to register for debug services
Recommended Action None.
Error Message%PLATFORM-CCTL-4-SPA_SERVER_DEBUG_INIT_WARN [CCTL-SPA-SERVER]: Unable to initialize debug space
Explanation The Chassis Control SPA LWM server process was unable to initialize the debug space
Recommended Action None.
Error Message%PLATFORM-CCTL-4-SPA_SERVER_DEBUG_REG_WARN [CCTL-SPA-SERVER]: Unable to register for debug services
Explanation The Chassis Control SPA LWM server process was unable to register for debug services
Recommended Action None.
Error Message%PLATFORM-CCTL-4-SYSDB_WARN [CCTL-ENVMON]: Unable to initialize [chars]
Explanation Chassis Control Driver was unable to initialize the Sysdb namespace
Recommended Action None.
Error Message%PLATFORM-CCTL-4-UNKNOWN_SHELF_ID [CCTL-ENVMON]: 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 values. Please check the EEPROM programming.
Recommended Action None.
Error Message%PLATFORM-CCTL-6-CARD_NOT_FOUND [CCTL-ENVMON]: Card information not found
Explanation There was no sensor information found for this card.
Recommended Action Check the path of file specified for download
Error Message%PLATFORM-CCTL-6-CHASSIS_SHUTDOWN_FAIL [CCTL-ENVMON]: Unable to shutdown chassis because [chars]
Explanation The shutdown of the chassis was unsuccessful due to the mentioned reason.
Recommended Action None.
Error Message%PLATFORM-CCTL-6-TEMP_ALARM [ENVMON]: [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 None.
Error Message%PLATFORM-CCTL-7-CHANGE_TO_DBG [CCTL]: CHANGE THIS MSG TO DEBUG [chars]
Explanation Need to replace this msg with debug
Recommended Action None.
Error Message%PLATFORM-CCTL-7-DEBUG [CCTL_INIT]: Initialization being done for [chars]
Explanation As indicated in 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.
Error Message%PLATFORM-CCTL-7-SERVER_SEND_SHELFMGR_PULSE_SUCCESS [CCTL-SERVER]: SUCCESSFULLY SENT PULSE TO SHELFMGR THAT SP IS BOOTED UP AFTER [dec] retries with [dec]ms per retry
Explanation The Chassis Control driver LWM server process successfully sent a pulse to shelfmgr to indicate that process is ready
Recommended Action None.
CHP Messages
Error Message%PLATFORM-CHP-3-CRC_ERR chopper dll: block: [chars], entity: [chars] had CRC error, count: [dec]
Explanation PII block got a packet from the entity mentioned above with a CRC error.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-CHP-3-DEVICE_HALT TFQ: device halted, sub-block: [chars], halted entity: [chars]
Explanation TFQ, ASIC got halted. The halted block and its parent block are provided
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-CHP-3-DMA_ERR Chopper detected a DMA error: Data [hex]
Explanation This message indicates that the Chopper hardware found a DMA problem. The hexadecimal data indicates the error register value when the problem is detected. This usually indicates a hardware 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-CHP-3-FATAL chopper dll: fatal error encountered, reason=[chars]
Explanation iqm, chopper dll 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-CHP-3-FATAL_2 chopper dll: fatal error encountered, reason=[chars], errno=[dec]
Explanation chopper 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-CHP-3-FUSILLI_PARITY_ERR Chopper detected a Fusilli parity error: Data [hex]
Explanation A parity error has been detected on the Chopper to Fusilli interface. The hex number indicates the error cause register value. This usually indicates a hardware problem on the RP. RP may 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-CHP-3-GEN_INFO chopper dll: general information,
Explanation The CHP's informational 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.
Error Message%PLATFORM-CHP-3-HWINIT_INCOMPLETE chopper dll: hardware initialization not complete
Explanation hardware init is not complete.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-CHP-3-INFO chopper dll: service degrading error, reason = [chars]
Explanation The chopper encountered an error that would lead to degraded service.
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-CHP-3-INTR_ENABLE_FAIL chopper dll: intr enable at addr: [hex] mask: [hex] failed.
Explanation hardware state is not correct.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-CHP-3-INTR_STATUS_GET_ERR chopper dll: intr status get failed for: [chars]@[hex], rc=[dec]
Explanation Hardware register read failed.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-CHP-3-MALLOC_FAILED chopper dll: fatal memory allocation error for bytes
Explanation CHP encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-CHP-3-NOT_AVAILABLE chopper dll: asic is not available
Explanation hardware state is not correct.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-CHP-3-NOT_OPERATIONAL chopper dll: asic is not operational, state: [dec]
Explanation hardware state is not correct.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-CHP-3-NOT_YET_IMPLEMENTED chopper dll: this function is not yet implemented
Explanation TFQ, chopper dll , a function is not implemented.
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-CHP-3-PCI_ERR Chopper detected a PCI error: Data [hex]
Explanation A PCI error has been detected by the Chopper PCI interface. The hex number indicates the error cause register value. This usually indicates a hardware problem on the RP. RP may 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-CHP-3-SRAM_PARITY_ERR Chopper detected a SRAM parity error: Data [hex]
Explanation A parity error has been detected on the Chopper to SRAM interface. The hex number indicates the error cause register value. This usually indicates a hardware problem on the RP. RP may 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-CHP-6-UNHANDLED_HALT chopper dll: halt not handled, parent: [chars], child: [chars], intr: [dec]
Explanation Hardware halt is not handled.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-CHP-6-UNHANDLED_INTR chopper dll: intr not handled, parent: [chars], child: [chars], group id: [dec], intr: [dec]
Explanation Hardware interrupt is not handled in the code, need to implement.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
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_SHOW Messages
Error Message%PLATFORM-CPUCTRL_SHOW-3-FATAL cpuctrl_show: fatal error encountered, reason=[chars]
Explanation cpuctrl show 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-CPUCTRL_SHOW-3-FATAL_2 cpuctrl_show: fatal error encountered, reason=[chars], errno=[dec]
Explanation cpuctrl_show 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-CPUCTRL_SHOW-3-GEN_INFO cpuctrl_show: general information,
Explanation The CPUCTRL_SHOW's informational 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.
Error Message%PLATFORM-CPUCTRL_SHOW-3-INFO cpuctrl_show: service degrading error, reason = [chars]
Explanation The cpuctrl_show encountered an error that would lead to degraded service.
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_SHOW-3-MALLOC_FAILED CPUCTRL_SHOW: fatal memory allocation error for bytes
Explanation CPUCTRL_SHOW encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-CPUCTRL_SHOW-3-NOT_YET_IMPLEMENTED cpuctrl_show: this function is not yet implemented
Explanation CPUCTRL_SHOW, a function was not implemented.
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_SHOW-3-USAGE cpuctrl_show: invalid option passed to cpuctrl_show command.
Explanation Startup option supplied to CPUCTRL_SHOW is not valid.
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.
CPUCTRL_TEST Messages
Error Message%PLATFORM-CPUCTRL_TEST-3-FATAL cpuctrl_test: fatal error encountered, reason=[chars]
Explanation cpuctrl 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 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_TEST-3-FATAL_2 cpuctrl_test: fatal error encountered, reason=[chars], errno=[dec]
Explanation cpuctrl_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 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_TEST-3-GEN_INFO cpuctrl_test: general information,
Explanation The CPUCTRL_TEST's informational 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.
Error Message%PLATFORM-CPUCTRL_TEST-3-INFO cpuctrl_test: service degrading error, reason = [chars]
Explanation The cpuctrl_test encountered an error that would lead to degraded service.
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_TEST-3-MALLOC_FAILED CPUCTRL_TEST: fatal memory allocation error for bytes
Explanation CPUCTRL_TEST encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-CPUCTRL_TEST-3-NOT_YET_IMPLEMENTED cpuctrl_test: this function is not yet implemented
Explanation CPUCTRL_TEST, a function was not implemented.
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_TEST-3-USAGE cpuctrl_test: invalid option passed to cpuctrl_test command.
Explanation Startup option supplied to CPUCTRL_TEST is not valid.
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.
CPUCTRL Messages
Error Message%PLATFORM-CPUCTRL-3-FATAL cpuctrl: fatal error encountered, reason=[chars]
Explanation iq 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-CPUCTRL-3-FATAL_2 cpuctrl: fatal error encountered, reason=[chars], errno=[dec]
Explanation cpuctrl 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-CPUCTRL-3-GEN_INFO cpuctrl: general information,
Explanation The CPUCTRL's informational 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.
Error Message%PLATFORM-CPUCTRL-3-INFO cpuctrl: service degrading error, reason = [chars]
Explanation The cpuctrl encountered an error that would lead to degraded service.
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-MALLOC_FAILED CPUCTRL: fatal memory allocation error for bytes
Explanation CPUCTRL encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-CPUCTRL-3-NOT_YET_IMPLEMENTED cpuctrl: this function is not yet implemented
Explanation CPUCTRL, a function was not implemented.
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-USAGE cpuctrl: invalid option passed to cpuctrl server
Explanation Startup option supplied to CPUCTRL is not valid.
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_ERROR_PDMA [chars], [dec], port = [dec], queue = [dec]
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-EVENT_INFO [chars]: [chars]
Explanation Info message to show unusual events
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 [chars]: HW set the error bit in a CDMA descriptor
CDMA engine = [dec], queue = [dec], index = [dec]
error reg_lo = [hex], error_reg_hi = [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_ISN [chars]: HW error interrupt Cpuctrl Internal Access failure
interrupt_id = [hex], pci_isnerr_status = [hex]
pci_isnerr_addr_hi = [hex], pci_isnerr_addr_lo = [hex]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-CPUCTRLLIB-3-HW_DETECTED_ERROR_LINK [chars]: HW error interrupt link, port = [dec]
interrupt_id = [hex], port_link_error = [hex], port_link_crc_count = [hex]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-CPUCTRLLIB-3-HW_DETECTED_ERROR_PCI_PM [chars]: HW error interrupt pci pm, port = [dec]
interrupt_id = [hex], pci_pmerr_status = [hex]
pci_pmerr_addr_hi = [hex], pci_pmerr_addr_lo = [hex]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-CPUCTRLLIB-3-HW_DETECTED_ERROR_PCI_SN [chars]: HW error interrupt pci sn, port = [dec]
interrupt_id = [hex], pci_snerr_status = [hex]
pci_snerr_addr_hi = [hex], pci_snerr_addr_lo = [hex]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-CPUCTRLLIB-3-HW_DETECTED_ERROR_PCIX [chars]: HW error interrupt pcix, port = [dec]
interrupt_id = [hex], pcix_pmerr_comptran_status = [hex], pcix_pmerr_status = [hex]
pcix_pmerr_addr_hi = [hex], pcix_pmerr_addr_lo = [hex]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-CPUCTRLLIB-3-HW_DETECTED_ERROR_PORT [chars]: HW error interrupt port, port = [dec]
interrupt_id = [hex], port_isn_cause = [hex], port_isn_error = [hex]
port_isn_last_reqhi = [hex], port_isn_last_reqlo = [hex]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-CPUCTRLLIB-3-HW_DETECTED_ERROR_RX_PDMA [chars]: HW set the error bit in a Rx PDMA descriptor
port = [dec], queue = [dec], index = [dec]
Explanation Error Packet received, possibly a CRC 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_DISCOVER_BUS_ERROR [chars]: Bus error occured when trying to read the ID register on Port [dec]
Explanation The HW on this Cpuctrl port is not accessible.
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_GASPP_READ_BUS_ERROR [chars]: Bus error when attempting User requested GASPP Read, Address = [hex]
Explanation The user may have entered an invalid address, or else there is a HW problem.
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_GASPP_WRITE_ERROR [chars]: Cpuctrl HW detected error on GASPP write, Address = [hex]
Explanation The user may have entered an invalid address that is not writable.
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_DISABLE cpuctrllib: [chars]: Excess Spurious interrupts device [chars], Interrupt is disabled
Explanation The cpuctrllib ASIC Interrupt wrapper has detected that an ASIC driver has not cleared it's interrupts at the source for 1000 consecutive times. This is possibly an error in the Driver ISR, that is does not process and clear all possible interrupts, or a malfunctioning HW. The Interrupt is disabled to prevent the ISR from hoggin 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-INT_WARNING cpuctrllib: [chars]: Excess Spurious interrupts device [chars]
Explanation The cpuctrllib ASIC Interrupt wrapper has detected that an ASIC driver has not cleared it's interrupts at the source for 1000 consecutive times. This is possibly an error in the Driver ISR, that is does not process and clear all possible interrupts, or a malfunctioning HW. The Interrupt is disabled to prevent the ISR from hoggin 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-PORT_INIT_FAILURE [chars]: Port [dec] could not clear Link errors during init
link_error_reg = [hex], crc_reg = [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-3-PORT_INIT_FAILURE2 [chars]: Port [dec] Device chipid mismatch during reframe
id_reg read after reframe = [hex], id_reg during HW discovery = [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-3-PORT_INIT_FAILURE3 [chars]: Port [dec] 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-6-NO_BUF_TO_REPLACE CPUCTRL: RX PDMA Ring out of buf, Port [dec], Q [dec], cur_ind = [dec], tx_ind = [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.
CSAR Messages
Error Message%PLATFORM-CSAR-3-ERROR ERROR [chars]
Explanation A generic error has occured. Normal operation is not affected.
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-CSAR-3-SLOT_SHUTDOWN Fabric disconnected from slot [dec], card shut down
Explanation There are unrecoverable errors while transmitting to the reported slot. The slot has been disconnected from the switching fabric and the card in the slot is marked for shut down.
Recommended Action Try moving the card in the reported slot to another slot. If this error follows the card, the card is bad. If the card works in another slot, there could be a hardware problem with the switch fabric cards (CSC and SFC.) Contact your technical support representative in all cases.
Error Message%PLATFORM-CSAR-3-UCAST_STUCK Unicast fabric transmissions to slot [dec] are stuck
Explanation This error indicates a (possibly temporary) problem in the switch fabric path between the route processor card reporting error and the card in the reported slot. Usual cause is a bad card in the reported slot. The particular card may be shut down when this error is reported.
Recommended Action Wait several minutes for corrective action to occur. Ignore repeats of this error while corrective action is taking place. Look for error reports about unicast fabric transmissions to other slots. If transmissions to a single slot are stuck it indicates a hardware problem in that slot. Either the card in that slot is bad or the fabric interface to the slot is bad. Try moving the card in the reported slot to another slot. If this error follows the card, the card is bad. If the card works in another slot, there could be a hardware problem with the switch fabric cards (CSC and SFC.) If there are reports for several slots, it is more likely that the switch fabric cards have a fault. Contact your technical support representative in all cases.
Error Message%PLATFORM-CSAR-4-DEBUG_FAIL Debug registration failed.
Explanation An internal registration call returned an error. Debug commands for the CSAR device may not be effective. Normal operation is not affected.
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-CSAR-4-MCAST_STUCK Multicast fabric transmissions are stuck
Explanation This error indicates a (possibly temporary) problem in the interface between the route processor card reporting error and the switch fabric.
Recommended Action Wait several minutes for corrective action to occur. Ignore repeats of this error while corrective action is taking place. Look for error reports about unicast fabric transmissions and take action as recommended for unicast errors. If this message repeats and there is no unicast error reported, then copy the error message exactly as it appears on the console and report it to your technical support representative.
Error Message%PLATFORM-CSAR-4-UNKNOWN_INTF Unknown Fabric Interface with slot [dec] and port [dec]
Explanation An internal call for fabric initialization received unexpected slot/port information. Normal operation is not affected.
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.
DISCOVERY Messages
Error Message%PLATFORM-DISCOVERY-2-ASMP_ERR_REGS ASIC-ERR: Regs Addr High [hex] Addr Low [hex] Err Attribute [hex], Cause [hex], Command [hex]
Explanation a Discovery bus encountered a fatal 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-DISCOVERY-2-ASMP_PCI_DETAILS ASIC-ERR: PCI[dec] error #[dec]: Command: [chars], Error Address: [hex] [hex], Error Attribute: [hex]
Explanation a Discovery bus encountered a fatal 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-DISCOVERY-2-FATAL ASIC-ERR: Initialization error: [chars]
Explanation a Discovery bus encountered a fatal 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-DISCOVERY-2-FATAL_ATTACH ASIC-ERR: Discovery: [chars] [dec]
Explanation a Discovery bus encountered a fatal 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-DISCOVERY-2-FATAL_CPU_DETAILS ASIC-ERR: CPU error #[dec]: Error Address: [hex], Address Parity Bits: [hex], Error Data: [hex] [hex], Data Parity Bits: [hex] [hex]
Explanation a Discovery bus encountered a fatal 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-DISCOVERY-2-FATAL_CPU_LATCH ASIC-ERR: CPU error #[dec]: Name = [chars] #[dec]: Description = [chars] (info latched and follows)
Explanation a Discovery bus encountered a fatal 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-DISCOVERY-2-FATAL_CPU_NOLATCH ASIC-ERR: CPU error #[dec]: Name = [chars] #[dec]: Description = [chars] (info lost)
Explanation a Discovery bus encountered a fatal 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-DISCOVERY-2-FATAL_DEV_DETAILS ASIC-ERR: DEV error #[dec]: Error Address: [hex]
Explanation a Discovery bus encountered a fatal 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-DISCOVERY-2-FATAL_DEV_LATCH ASIC-ERR: DEV error #[dec]: Name = [chars] #[dec]: Description = [chars] (info latched and follows)
Explanation a Discovery bus encountered a fatal 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-DISCOVERY-2-FATAL_DEV_NOLATCH ASIC-ERR: DEV error #[dec]: Name = [chars] #[dec]: Description = [chars] (info lost)
Explanation a Discovery bus encountered a fatal 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-DISCOVERY-2-FATAL_PCI_DETAILS ASIC-ERR: PCI[dec] error #[dec]: Command: [chars], Byte Enables: [hex] [hex], Error Address: [hex] [hex], Error Data: [hex] [hex], Parity Bits: [hex] [hex]
Explanation a Discovery bus encountered a fatal 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-DISCOVERY-2-FATAL_PCI_LATCH ASIC-ERR: PCI[dec] error #[dec]: Name = [chars] #[dec]: Description = [chars] (info latched and follows)
Explanation a Discovery bus encountered a fatal 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-DISCOVERY-2-FATAL_RAM_DETAILS ASIC-ERR: RAM error #[dec]: Error Address: [hex], Error Data: [hex] [hex], Recorded ECC Bits: [hex], Calculated ECC Bits: [hex]
Explanation a Discovery bus encountered a fatal 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-DISCOVERY-2-FATAL_RAM_ECC_1BIT_THRESH ASIC-ERR: RAM error #[dec]: Name = [chars] #[dec]: Description = [chars]
Explanation Threshhold reached for single bit ECC (Corrected) errors.
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-DISCOVERY-2-FATAL_RAM_ECC_2BIT ASIC-ERR: RAM error #[dec]: Name = [chars] #[dec]: Description = [chars]
Explanation Two or more bit ECC error (Uncorrectable) found in a RAM Access.
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-DISCOVERY-2-FATAL_SRAM_DETAILS ASIC-ERR: RAM error #[dec]: Error Address: [hex] [hex], Error Data: [hex] [hex], Parity Bits: [hex]
Explanation a Discovery bus encountered a fatal 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-DISCOVERY-2-FATAL_SRAM_PARITY ASIC-ERR: SRAM error #[dec]: Description = [chars]
Explanation Parity Error detected in 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-DISCOVERY-4-FATAL_PCI_NOLATCH ASIC-ERR: PCI[dec] error #[dec]: Name = [chars] #[dec]: Description = [chars] (info lost)
Explanation a Discovery bus encountered a fatal 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.
DSC Messages
Error Message%PLATFORM-DSC-2-ERR_RACK_DOWN Lost connectivity with [chars] [dec]
Explanation Rack might be powered down.
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-DSC-2-ERR_READING_SERIAL_ID Could not read serial number for the node [hex]
Explanation Chassis APIs that return serialID after reading from eeprom 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-DSC-3-ERR_2_PARAM [chars]. errno = [dec]
Explanation dSC 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-DSC-3-ERR_INVALID_PARAMETER Invalid parameters being passed: [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-DSC-3-ERR_NO_MEMORY Out of memory
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-DSC-3-ERR_OPEN_FILE Failed opening file: [chars], [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-DSC-3-ERR_RD_FILE Failed reading file: [chars], [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-DSC-3-ERR_STR [chars] ([chars])
Explanation dSC 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-DSC-3-ERR_SYSDB_GET Failed to get item [chars] in SysDB: [hex], [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-DSC-3-ERR_SYSDB_SET Failed to set item [chars] in SysDB: [hex], [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-DSC-3-ERR_TRY_AGAIN dSC election is running, try again later.
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-DSC-3-ERR_WR_FILE Failed writing file : [chars], [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-DSC-6-RACK_SERID_CFG_FAIL serial id [chars] already mapped to rack [dec]!(delete mapping and try again?)
Explanation dSC config failure 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.'
Error Message%PLATFORM-DSC-6-SERID_CHANGED Shelf [dec] serial id changed to [chars]!
Explanation dSC general warning 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.'
Error Message%PLATFORM-DSC-6-WARNING [chars]
Explanation dSC general warning 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.'
DSCMEDIA Messages
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-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-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=[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-ERROR2 Error from dsc media dll: [chars], errno=[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-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-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=[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-4-WARNING2 Warning from dsc media dll: [chars], errno=[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.
EIO Messages
Error Message%PLATFORM-EIO-3-ASIC_ID_MISMATCH eio_dll: ASIC Id mismatch, link_id: [dec], local Id: [dec], peer id: [dec]
Explanation The EIO_DLL's fatal error 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-EIO-3-DATAWINDAGE_MAXED eio_dll: link_id: [dec] training failed even after datawindage maxed.
Explanation The EIO_DLL's fatal error 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-EIO-3-DIAG_STATUS_ERROR eio_dll: ASIC: [chars], link_id: [dec], macro id: [dec], final diag status: [hex]
Explanation The EIO_DLL's fatal error 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-EIO-3-FATAL eio_dll: fatal error encountered, reason=[chars]
Explanation iq 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-EIO-3-FATAL_2 eio_dll: fatal error encountered, reason=[chars], errno=[dec]
Explanation eio_dll 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-EIO-3-GEN_INFO eio_dll: general information,
Explanation The EIO_DLL's informational 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.
Error Message%PLATFORM-EIO-3-INFO eio_dll: service degrading error, reason = [chars]
Explanation The eio_dll encountered an error that would lead to degraded service.
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-EIO-3-INTERFACE_TYPE_MISMATCH eio_dll: interface type mismatch, link_id: [dec], local: [dec], peer: [dec]
Explanation The EIO_DLL's fatal error 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-EIO-3-NOT_YET_IMPLEMENTED eio_dll: this function is not yet implemented
Explanation EIO_DLL, a function was not implemented.
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-EIO-3-TRAINING_TIMEDOUT eio_dll: ASIC: [chars], link_id: [dec] training timeout, last state: [chars].
Explanation The EIO_DLL's fatal error 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.
ENET Messages
Error Message%PLATFORM-ENET-3-ALREADY_INITIALIZED [chars]: the library has already been initialized
Explanation The function enet_init function has been called several times.
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-ENET-3-COOKIE_MISMATCH [chars]: cookie mismatched: cookie = [dec], index = [dec]
Explanation The cookie between the shadow ring and the hardware ring does not match. Some information has been lots between the hardware library and the control ethernet driver library
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-ENET-3-INIT_FAILURE [chars]: [chars] fails (rc = [dec])
Explanation During the initialization of the DLL, a call to another function returns a 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-ENET-3-LOCK_ERROR [chars]: [chars] fails (rc = [dec])
Explanation pthread_mutex_lock/pthread_mutex_unlock fail
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-ENET-3-PROCESSING_ERROR [chars]: could not process all the packets from the driver
Explanation This error message should appear each time the error COOKIE_MISMATCH appears.
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-ENET-3-QUEUE_PACKET_FAIL [chars]: [chars] fails (rc = [dec])
Explanation Fail to add some buffer to the RX queue either at the init stage or after receiving some packets (replace buffer)
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-ENET-3-TOO_MANY_DESC_ALLOCATED [chars]: want to use [dec] descriptors exceeds the hardware can only use [dec]
Explanation The control ethernet library is trying to use more descriptor then the driver (ethernet device) may 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-ENET-3-TOO_MANY_DESC_RETURNED [chars]: driver is returning more than it should: num_desc [dec] num_used ([dec] - [dec])
Explanation The ethernet library driver is returning more descriptor than it should
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-ENET-6-NOT_ENOUGH_DESC [chars]: not enough descriptor available (want to add [dec] but have only [dec] free)
Explanation A message required more than the remaining number of descriptor is trying to be sent. The updating of the rx descriptor fails because too many descriptor need to be updated (not enough room)
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-ENET-7-DUMP_DATA [chars]: [chars]
Explanation Debug 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.
Error Message%PLATFORM-ENET-7-DUMP_DESCRIPTOR [chars]: handle = [hex]; status = [hex] ([chars] len = [dec] [[hex]:[hex]]
Explanation Debug 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.
Error Message%PLATFORM-ENET-7-INVALID_MULTICAST_ADDRESS [chars]: invalid multicast address ([hex]%2.2x.[hex]%2.2x.[hex]%2.2x)
Explanation The address should be a multicast address
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-ENET-7-INVALID_UNICAST_ADDRESS [chars]: invalid unicast address ([hex]%2.2x.[hex]%2.2x.[hex]%2.2x)
Explanation The address should be a unicast address
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-ENET-7-UNEXPECTED_VALUE [chars]: unexpected [chars] (last = [chars])
Explanation Debug 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.
ENVMON Messages
Error Message%PLATFORM-ENVMON-0-CANTSHUT Environmental Monitor was unable to shutdown slot [dec]: [chars]
Explanation Envmon attempted to shutdown the specified slot due to severely out-of-range conditions, but was unable to do so.
Recommended Action Attempt to resolve the problem, referring to system log or the show env command outputs. If operation permits, remove and insert the card, or power down the entire router. If the problem is not resolved, call your technical support representative for assistance.
Error Message%PLATFORM-ENVMON-0-SHUTDOWN Environmental Monitor initiated shutdown on slot [dec]
Explanation An environmental sensor has remained in a dangerous operating range, and is being shutdown to avoid possible damage.
Recommended Action Attempt to resolve the problem, referring to system log or the show env command outputs. If operation permits, remove and insert the card, or power down the entire router. If the problem is not resolved, call your technical support representative for assistance.
Error Message%PLATFORM-ENVMON-0-SPA_CANTSHUT Environmental Monitor was unable to shutdown slot [dec] bay [dec]: [chars]
Explanation Envmon attempted to shutdown the specified spa due to severely out-of-range conditions, but was unable to do so.
Recommended Action Attempt to resolve the problem, referring to system log or the show env command outputs. If operation permits, remove and insert the spa, or power down the line card having the spa. If the problem is not resolved, call your technical support representative for assistance.
Error Message%PLATFORM-ENVMON-0-SPA_SHUTDOWN Environmental Monitor initiated shutdown on slot [dec] bay [dec]
Explanation An environmental sensor on the spa has remained in a critical operating range, and is being shutdown to avoid possible damage.
Recommended Action Attempt to resolve the problem, referring to system log or the show env command outputs. If operation permits, remove and insert the spa, or power down the line card having the spa. If the problem is not resolved, call your technical support representative for assistance.
Error Message%PLATFORM-ENVMON-2-ENV_CONDITION An environmental condition exists on slot [dec]
Explanation One or more environmental conditions exist on the specified slot. If left untended, they could result in loss of service or even hardware damage.
Recommended Action Using the 'show environment' command and other associate system messages, determine the nature of the failure and take corrective action, including replacement of faulty hardware.
Error Message%PLATFORM-ENVMON-2-FAN The fan array ([chars]) has reached [chars] level.
Explanation The fan array specified has reached a warning or critical level and is approaching or approached a condition that is outside the acceptable range.
Recommended Action Verify the failure and call your technical support representative for repair or replacement.
Error Message%PLATFORM-ENVMON-2-FAN_CLEAR The fan array ([chars]) has returned to a normal level.
Explanation The fan sensor/array has returned to a level that is within the acceptable range.
Recommended Action None required.
Error Message%PLATFORM-ENVMON-2-OVERTEMP [chars] temperature has reached [chars] level
Explanation The temperature sensor specified has reached a warning or critical level and is approaching or approached a condition that is outside the acceptable range.
Recommended Action Attempt to resolve the temperature problem. Check all unit doors are in place and closed. Check fans are operating. Remove affected cards, check how hot they are and allow to cool and reinsert. Operation of overtemperature equipment is not recommended due to equipment damage. If problem not resolved by above steps, power unit off and call your technical support representative for assistance.
Error Message%PLATFORM-ENVMON-2-POWERSUPPLY_CURRENT [chars] current has reached [chars] level at [dec] A
Explanation The voltage supply specified has reached a critical level and is now out of specification.
Recommended Action Verify the failure and call your technical support representative for repair or replacement.
Error Message%PLATFORM-ENVMON-2-POWERSUPPLY_NONOP [chars] is Non-Operational
Explanation The powr supply specified has become non-operational.
Recommended Action Verify the failure and call your technical support representative for repair or replacement.
Error Message%PLATFORM-ENVMON-2-POWERSUPPLY_VOLTAGE [chars] voltage has reached [chars] level at [dec] V
Explanation The voltage supply specified has reached a critical level and is now out of specification.
Recommended Action Verify the failure and call your technical support representative for repair or replacement.
Error Message%PLATFORM-ENVMON-2-TEMP [chars] temperature has reached [chars] level at [dec](C)
Explanation The temperature sensor specified has reached a warning or critical level and is approaching or approached a condition that is outside the acceptable range.
Recommended Action Attempt to resolve the temperature problem. Check all unit doors are in place and closed. Check fans are operating. Remove affected cards, check how hot they are and allow to cool and reinsert. Operation of overtemperature equipment is not recommended due to equipment damage. If problem not resolved by above steps, power unit off and call your technical support representative for assistance.
Error Message%PLATFORM-ENVMON-2-VOLTAGE [chars] voltage has reached [chars] level at [dec] mV
Explanation The voltage supply specified has reached a critical level and is now out of specification.
Recommended Action Verify the failure and call your technical support representative for repair or replacement.
Error Message%PLATFORM-ENVMON-3-ASSERT Assertion failure due to [chars]
Explanation A fatal internal software error has occurred.
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-ASSUME_OLD_E5 slot:[dec] Cannot determine if E5 [chars] supports 12V rail. Assuming legacy E5 card.
Explanation The envmon component needs to to know the E5's hardware type and power controller firmware version in order to determine if the card supports the new daughterboard 12V SPA voltage rail. However, we could not determine one of these components, and so the software is taking the conservative stance of assuming that the E5 does not support the 12V rail. This error should always be preceeded by anoter envmon E5 related error about the hardware or firmware check failing.
Recommended Action *SUPPORT*
Error Message%PLATFORM-ENVMON-3-BAG_DECODE_FAILED Bag decode on [chars] failed. Error: [chars]
Explanation Could not decode bag
Recommended Action None
Error Message%PLATFORM-ENVMON-3-CACHE_TOO_SMALL Cache size ([dec]) is to small for sensor id ([dec]) from SPA in slot:[dec] bay:[dec]
Explanation This is a coding defect caught by sanity checks. The envmon subsystem maintains a short term cache for a SPA's voltage margin values. However, the specified SPA is using sensor ids that are too large for our cache. Consequently we will not be able to store or report the voltage margin value for these offending sensors.
Recommended Action *SUPPORT*
Error Message%PLATFORM-ENVMON-3-CHKPT_CREATE_ERROR Could not create checkpoint entry (key [hex]): [chars]
Explanation Envmon encountered an error in data checkpointing.
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-CHKPT_DELETE_ERROR Could not delete checkpoint entry (objid [hex]): [chars]
Explanation Envmon encountered an error in data checkpointing.
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-CHKPT_ERROR Checkpointing error, [chars] : [chars]
Explanation Envmon encountered an error in data checkpointing.
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-CHKPT_ITERATE_ERROR [chars]: [chars]
Explanation Envmon encountered an error in data checkpointing.
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-CHKPT_RESTORE_CORRUPT A corrupted checkpoint was detected: key = [hex], datakey = [hex]. Entry deleted.
Explanation Envmon encountered an error in data checkpointing.
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-CHKPT_SAVE_ERROR Could not save checkpoint entry (key [hex], objid [hex]): [chars]
Explanation Envmon encountered an error in data checkpointing.
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-DSC_CONNECT_FAIL Could not contact the dSC: [chars]
Explanation Environmental monitoring couldn't contact the dSC
Recommended Action None.
Error Message%PLATFORM-ENVMON-3-EDM_ERR_MISSING Unknown error code [hex]
Explanation One of the look up routines for the ENV_EDM_ERRS_E enumeration received an unexpected error code. Most likely caused by a new enumerated type being added but the table was not updated, or the look up routines are being passed a value that really isn't a ENV_EDM_ERRS_E value.
Recommended Action None. This is not so bad. These look up routines are suppose to make it easier to debug envmon problems this really has no customer impact, and is only going to make it more troublesome for engineers.
Error Message%PLATFORM-ENVMON-3-EDM_INIT_FAIL Error initializing envmon EDM ([chars]): [chars]
Explanation An error occurred while setting up the envmon EDM.
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-ERROR Error, [chars]
Explanation Envmon encountered an 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-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-EVENT_BLOCK_FAILED Event Manager could not block. Error: [chars]
Explanation Could not block on receiving events from sysdb via event manager
Recommended Action None. Environmental Monitoring process will restart automatically
Error Message%PLATFORM-ENVMON-3-EVM_ASYNC_ATTACH_FAILED Event Manager's event_async_attach function failed. Error: [chars]
Explanation Could not attach an event_handler to handle async messages.
Recommended Action None. Environmental Monitoring process will restart automatically
Error Message%PLATFORM-ENVMON-3-EVM_CREATE_FAILED Event Manager create failed. Error: [chars]
Explanation The Event Manager could not be created.
Recommended Action None. Environmental Monitoring process will restart automatically
Error Message%PLATFORM-ENVMON-3-EXTRACT_SLOT [chars] nodeid_extract_fields for nodeid [dec] failed. Error: [chars]
Explanation Platform function return error on invocation
Recommended Action Ensure the Platform Library is available.
Error Message%PLATFORM-ENVMON-3-INTERNAL_ERROR [chars]: [chars]
Explanation Miscellaneous 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-ENVMON-3-INVALID_SLOT [chars]: Invalid slot [dec]
Explanation Invalid slot number.
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-LWM_RECEIVE_FAILED LWM Message Receive failed. Error: [chars]
Explanation The Light-Weight Messaging msg_recieve function failed.
Recommended Action None. Environmental Monitoring process will restart automatically
Error Message%PLATFORM-ENVMON-3-LWM_REPLY_FAILED LWM Message Reply failed. Error: [chars]
Explanation The Light-Weight Messaging msg_reply function failed.
Recommended Action None. Environmental Monitoring process will restart automatically
Error Message%PLATFORM-ENVMON-3-MBUS_CEC_ERROR [chars]: Error reading mbus cec register [hex] on slot [dec] bay [dec]. Status:[hex], Errno:[hex], ErrStr:'[chars]'
Explanation An error occurred reading an MBus CEC 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-ENVMON-3-MBUS_RCV_ERROR [chars]: Error receiving MBus message for slot [dec], type [dec]: [chars]
Explanation An error occurred reading an MBus 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-ENVMON-3-MBUS_READREG [chars]: Error reading mbus register [hex] on slot [dec]: [chars]
Explanation An error occurred reading an MBus 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-ENVMON-3-NO_DSC_INFO Could not determine relationship to dSC: [chars]
Explanation Environmental monitoring couldn't determine if it is running on the dSC or not.
Recommended Action None.
Error Message%PLATFORM-ENVMON-3-NODEID_CREATE nodeid_create for slot [dec] failed. Error: [chars]
Explanation Platform function return error on invocation
Recommended Action Ensure the Platform Library is available.
Error Message%PLATFORM-ENVMON-3-NOSUPPORT_E5 Card type [dec] in slot [dec] needs hardware rework and is not supported by environmental monitoring. The card will not be monitored
Explanation The E5 card inserted in the specified slot cannot be monitored since it needs hardware rework.
Recommended Action Rework the card.
Error Message%PLATFORM-ENVMON-3-PTHREAD_ERROR [chars]: pthread manipulation error: [chars]
Explanation A pthread call 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-ENVMON-3-SYSDB_BIND_FAILED SysDB bind to [chars] failed. Error: [chars]
Explanation Could not bind to SysDB
Recommended Action Ensure SysDB is available on the system.
Error Message%PLATFORM-ENVMON-3-SYSDB_GET_FAILED SysDB item_get on [chars] failed. Error: [chars]
Explanation Could not get item value in Sysdb
Recommended Action Ensure item is in Sysdb
Error Message%PLATFORM-ENVMON-3-SYSDB_NOTIFY_REG_FAILED SysDB register for notification on [chars] failed. Error: [chars]
Explanation Could not register for notification in Sysdb
Recommended Action None. Environmental Monitoring process will restart automatically
Error Message%PLATFORM-ENVMON-3-SYSMGR_PROC_READY_FAILED System Manager's sysmgr_proc_ready failed. Error: [chars]
Explanation The sysmgr_proc_ready() function failed.
Recommended Action None.
Error Message%PLATFORM-ENVMON-3-TEST_ALARM [chars] can not send messages to [chars] channel, restarts
Explanation This is a test alarm message to check how ios_msg works.
Recommended Action This is just sample text to see how this matters.
Error Message%PLATFORM-ENVMON-3-THREAD_CREATE_FAILED Could not create thread. Error: [chars]
Explanation A thread could not be created.
Recommended Action None. Environmental Monitoring process will restart automatically
Error Message%PLATFORM-ENVMON-3-TRAP_SEND_ERROR Error generating Envmon trap notification [chars]: [chars]
Explanation An error occurred while generating trap notification to SNMP
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-UNEXPECTED_PRP_TYPE Unexpected PRP type [hex] in slot [dec]. Assuming PRP-2
Explanation The envmon component received an unexpected PRP type. The utility function for determining the PRP type returned a PRP type that was no expected.
Recommended Action *SUPPORT*
Error Message%PLATFORM-ENVMON-3-UNKNOWN_E5_FW slot:[dec] Cannot determine E5 power controller firmware version. errno=[hex]:[chars]
Explanation The envmon component could not determine the E5's power controller FW version. The utility function for determining the E5 FW version returned and error response.
Recommended Action *SUPPORT*
Error Message%PLATFORM-ENVMON-3-UNKNOWN_E5_HW_TYPE slot:[dec] Cannot determine E5 hardware type.
Explanation The envmon component could not determine the E5 type. The utility function for determining the E5 type returned and error response.
Recommended Action *SUPPORT*
Error Message%PLATFORM-ENVMON-3-UNKNOWN_MARGIN_MODE Unknown margin code [hex]
Explanation An unknown margin mode was received by the erroring function. Consequently it did not know what to do and has aborted the current action.
Recommended Action Reattempt the last action, to see if you can proceed. Even if you can proceed, be sure to have a defect logged to resolve the issue.
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.
Error Message%PLATFORM-ENVMON-3-UNKNOWN_PRP_TYPE Cannot determine PRP type in slot [dec], assuming PRP-2.
Explanation The envmon component could not determine the PRP type. The utility function for determining the PRP type returned and error response. The envmon component will treat this PRP as if it where a PRP-2. If this is really a PRP-1 then the show environmental voltage command will list two extra sensors: PLIM_V7_HDD_5V and PLIM_V6_1.5V, and these sensors will have incorrect voltage and margin states, because.. they do not really exist. Moreover, the PRP1's PLIM_V4_1.6V volt sensor will be instead listed as PLIM_V4_1.3V. There is no negative impact to the card.
Recommended Action *SUPPORT*
Error Message%PLATFORM-ENVMON-3-UNSUPPORTED_CARD Card type [dec] in slot [dec] is not supported by environmental monitoring. The card will not be monitored
Explanation The card inserted in the specified slot cannot be monitored.
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-4-DEBUG_FAIL Debug registration failed ([chars]).
Explanation An internal registration call returned an error. Debug commands for the LIB device may not be effective. Normal operation is not affected.
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-4-OLD_E5_FW slot:[dec] E5 has downrev power controller firmware.
Explanation The envmon component has detected that the E5 in the specified slot has HW capability to support margining and monitoring of the Daughterboard's 12V SPA rail, but the FW does not. The minimum power controller firmware needed is 0.95.
Recommended Action Upgrade the E5's power controller firmware.
Error Message%PLATFORM-ENVMON-4-SET_ALARM [chars] alarm generated by [chars]
Explanation An alarm has occured.
Recommended Action None - the action, if any, is taken automatically.
Error Message%PLATFORM-ENVMON-5-MBUS_EEPROM slot [dec]: Unable to read mbus eeprom contents for PCA
Explanation For displaying notification of mbus nonresponsiveness to get eeprom contents.
Recommended Action This indicates that mbus request to get eeprom contents for envmon command has timed out.
Error Message%PLATFORM-ENVMON-6-CLEAR_ALARM [chars] alarm cleared for [chars]
Explanation A previously occured alarm has been cleared.
Recommended Action None.
Error Message%PLATFORM-ENVMON-6-ENV_CONDITION_CLEAR The environmental condition on slot [dec] has cleared
Explanation All environmental conditions on the specified slot have cleared.
Recommended Action None required.
Error Message%PLATFORM-ENVMON-6-ENV_SLOT_FORCE_CLEAR The environmental condition on slot [dec] has cleared because the slot is no longer monitorable
Explanation All environmental conditions on the specified slot have cleared due to the fact that the card was either removed from the slot or was powered down..
Recommended Action None required.
Error Message%PLATFORM-ENVMON-6-ENV_SPA_FORCE_CLEAR The environmental condition on slot [dec] bay [dec] has cleared because the spa is no longer monitorable
Explanation All environmental conditions on the specified spa have cleared due to the fact that the spa was either removed from the card or was shut down.
Recommended Action None required.
Error Message%PLATFORM-ENVMON-6-FAN_INSERT Fan blower inserted into slot [dec]
Explanation The fan blower module specified was detected as inserted.
Recommended Action None requried
Error Message%PLATFORM-ENVMON-6-FAN_REMOVE Fan blower removed from slot [dec]
Explanation The fan blower module specified was detected as removed.
Recommended Action None requried
Error Message%PLATFORM-ENVMON-6-LOW_FAN_SPEED_WARNING [chars] is spinning slow - speed is [dec]RPM (register value = [hex])
Explanation Informational msg indicating that the fan is spinning very slow.
Recommended Action None.
Error Message%PLATFORM-ENVMON-6-NOT_ON_DSC Environmental monitoring will only run on the dSC
Explanation Environmental monitoring only runs on the dSC
Recommended Action None.
Error Message%PLATFORM-ENVMON-6-OVERTEMP_CLEAR [chars] temperature has returned to a normal level
Explanation The temperature sensor specified has returned to a level that is within the acceptable range.
Recommended Action None required.
Error Message%PLATFORM-ENVMON-6-PEM_INSERT [chars] inserted into slot [dec]
Explanation The power entry module specified was detected as inserted.
Recommended Action None requried
Error Message%PLATFORM-ENVMON-6-PEM_REMOVE [chars] removed from slot [dec]
Explanation The power entry module specified was detected as removed.
Recommended Action None requried
Error Message%PLATFORM-ENVMON-6-POWERSUPPLY_CURRENT_CLEAR [chars] current has returned to a normal level at [dec] A
Explanation The voltage supply specified has returned to a level that is within the acceptable range.
Recommended Action None required.
Error Message%PLATFORM-ENVMON-6-POWERSUPPLY_NONOP_CLEAR [chars] has become operational
Explanation The powr supply specified has returned to an operational state.
Recommended Action None required.
Error Message%PLATFORM-ENVMON-6-POWERSUPPLY_VOLTAGE_CLEAR [chars] voltage has returned to a normal level at [dec] V
Explanation The voltage supply specified has returned to a level that is within the acceptable range.
Recommended Action None required.
Error Message%PLATFORM-ENVMON-6-SEND_PULSE_FAIL Failed to send pulse to shelfmgr to notify [chars]
Explanation Failure to send pulse to shelfmgr to notify the particular alarm condition.
Recommended Action None.
Error Message%PLATFORM-ENVMON-6-TEMP_CLEAR [chars] temperature has returned to a normal level at [dec](C)
Explanation The temperature sensor specified has returned to a level that is within the acceptable range.
Recommended Action None required.
Error Message%PLATFORM-ENVMON-6-VOLTAGE_CLEAR [chars] voltage has returned to a normal level at [dec] mV
Explanation The voltage supply specified has returned to a level that is within the acceptable range.
Recommended Action None required.
ETH_SRVR Messages
Error Message%PLATFORM-ETH_SRVR-2-RECV_SEM_ERR [chars], errno = [dec]
Explanation An internal error occurred receiving over over the routers control network. The error can be fatal. Please contact tech support with 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 process eth_server location 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 process eth_server location output, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PLATFORM-ETH_SRVR-2-TX_SEM_ERR [chars], errno = [dec]
Explanation An internal error occurred during transmission over the control network. The error can be fatal. Please contact tech support with 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 process eth_server location 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 process eth_server location output, call your Cisco technical support representative and provide the representative with the gathered information.'
Error Message%PLATFORM-ETH_SRVR-3-FATAL [chars], error = [dec] ([chars])
Explanation A fatal error occurred from eth server cannot recover.
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-ETH_SRVR-3-FREE_ERR [chars]
Explanation Useful info to debug a rare problem
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-ETH_SRVR-3-WARN2 Non-fatal error [chars], error = [dec] ([chars])
Explanation An error occurred which probably isn't fatal but needs to be looked at.
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-ETH_SRVR-4-WARN Non-fatal error - [chars], client id = [dec], errno = [dec]
Explanation An error occurred which probably isn't fatal but can impact eth server's interaction with a client.
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-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 persistant 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 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 detail output, call your Cisco technical support representative and provide the representative with the gathered information.'
FAULT Messages
Error Message%PLATFORM-FAULT-2-ASIC LC [dec] : Reset [chars]
Explanation Fault Manager Error Handling recieved an error from one of the LC devices. The FM will handle the 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-FAULT-2-RESET Reset LC [dec]: Reason - [chars]
Explanation Fault 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.
FCTL Messages
Error Message%PLATFORM-FCTL-2-CHKPT_REGISTRATION_FAILED Fabric control failed to register [chars] with CHKPT, cerrno=[dec]
Explanation FCTL encountered a problem registering with chkpt.
Recommended Action No action required.
Error Message%PLATFORM-FCTL-2-CRIT [chars]
Explanation Software error found.
Recommended Action Wait to see if self-recovery takes place. Report problem.
Error Message%PLATFORM-FCTL-2-ERR_REPORT [chars]
Explanation A problem occurred with a fabric related component.
Recommended Action Log contains instructions. Usually, the failed component is replaced.
Error Message%PLATFORM-FCTL-2-FAILED_SYNCH Failed to drive slave clock on card [dec] from [chars]
Explanation A card failed to synchronize clocks with the Master clock.
Recommended Action Replace failed card.
Error Message%PLATFORM-FCTL-2-FAILED_TO_RESET_FC Failed to reset fabric card for slot=[dec]
Explanation A fabric card failed to reset.
Recommended Action Replace failed fabric card.
Error Message%PLATFORM-FCTL-2-FAILED_TO_SEND_CONFIG Failed sending new config value to slot [dec], num_tries = [dec]
Explanation A linecard failed to receive the latest fabric configuration data.
Recommended Action Replace failed linecard.
Error Message%PLATFORM-FCTL-2-FAILED_TO_SYNC_RP Failed to sync RP (slot=[dec]) to [chars] (slot=[dec])
Explanation The RP failed to synchronize its clock with the Master clock.
Recommended Action Replace failed RP.
Error Message%PLATFORM-FCTL-2-FAILED_TO_SYNC_RP_TO_CSCS Could not synch primary RP (slot=[dec]) to either CSC
Explanation The primary RP failed to synchronize its clock with either CSC.
Recommended Action Replace failed RP.
Error Message%PLATFORM-FCTL-2-FAILED_TO_SYNC_TO_SELF Failed to sync [chars] (slot [dec]) to itself
Explanation The primary CSC failed to synchronize its clock with itself.
Recommended Action Replace failed CSC.
Error Message%PLATFORM-FCTL-2-MBUS_ERROR Failed to access to MBUS server; perhaps it is down. Error = [dec] ([chars])
Explanation A system resource was not available.
Recommended Action Wait to see if self-recovery takes place. Report problem.
Error Message%PLATFORM-FCTL-2-MUTEX_LOCK Failed to lock mutex. Error = [dec] ([chars])
Explanation A system resource may not have been available.
Recommended Action Wait to see if self-recovery takes place. Report problem.
Error Message%PLATFORM-FCTL-2-MUTEX_UNLOCK Failed to unlock mutex. Error = [dec] ([chars])
Explanation A system resource may not have been available.
Recommended Action Wait to see if self-recovery takes place. Report problem.
Error Message%PLATFORM-FCTL-2-NO_MEMORY [chars]
Explanation Memory is not available for the required operation.
Recommended Action Report problem.
Error Message%PLATFORM-FCTL-3-API_RANGE [chars], value=[hex], valid range=[hex]-[hex]
Explanation Software API usage error found.
Recommended Action Wait to see if self-recovery takes place. Report problem.
Error Message%PLATFORM-FCTL-3-API_RANGE_SLOT [chars], value=[hex], valid range=[hex]-[hex], slot=[dec]
Explanation Software API usage error found from a slot.
Recommended Action Wait to see if self-recovery takes place. Report problem.
Error Message%PLATFORM-FCTL-3-API_STR [chars], [chars]
Explanation Software API usage error found.
Recommended Action Wait to see if self-recovery takes place. Report problem.
Error Message%PLATFORM-FCTL-3-API_VALUE [chars], [hex]
Explanation Software API usage error found.
Recommended Action Wait to see if self-recovery takes place. Report problem.
Error Message%PLATFORM-FCTL-3-API_VALUE_SLOT [chars], value=[hex], slot=[dec]
Explanation Software API usage error found from a slot.
Recommended Action Wait to see if self-recovery takes place. Report problem.
Error Message%PLATFORM-FCTL-3-CHASSIS_NOT_SUPPORTED Chassis type [dec] not supported
Explanation The chassis type is not supported.
Recommended Action Wait to see if self-recovery takes place. Report problem.
Error Message%PLATFORM-FCTL-3-EDM_ERROR [chars]:[dec] [chars]
Explanation Software error found.
Recommended Action Wait to see if self-recovery takes place. Report problem.
Error Message%PLATFORM-FCTL-3-ERROR [chars]
Explanation Software error found.
Recommended Action Wait to see if self-recovery takes place. Report problem.
Error Message%PLATFORM-FCTL-3-MBUS [chars], errno=[hex], [chars]
Explanation A system resource was not available.
Recommended Action Wait to see if self-recovery takes place. Report problem.
Error Message%PLATFORM-FCTL-3-NO_CHASSIS Unable to read chassis model
Explanation The Backplane Server has not provided the chassis model.
Recommended Action Wait to see if self-recovery takes place. Report problem.
Error Message%PLATFORM-FCTL-3-SYSDB [chars] [chars], rc=[hex], [chars]
Explanation A system resource was not available.
Recommended Action Wait to see if self-recovery takes place. Report problem.
Error Message%PLATFORM-FCTL-3-THREAD_CREATE_FAIL Fail to create thread [chars]: rc=[hex], [chars]
Explanation Fail to create a thread.
Recommended Action Wait to see if self-recovery takes place. Report problem.
Error Message%PLATFORM-FCTL-4-SHUTDOWN [chars] has been shutdown
Explanation A fabric card has been shutdown. Can be done via an EXEC command or due to environmental monitoring (ENVMON).
Recommended Action Ensure that router has enough fabric bandwidth for line card types. Engine-2 cards require full bandwidth. Redundant clocks recommended. Reactivate or replace fabric card.
Error Message%PLATFORM-FCTL-5-FABRIC_CARD_OIR_INSERTED Fabric card [chars] inserted in slot [dec]
Explanation Notification for inserted fabric card.
Recommended Action No action required.
Error Message%PLATFORM-FCTL-5-FABRIC_CARD_OIR_REMOVED Fabric card [chars] removed from slot [dec]
Explanation Notification for removed fabric card.
Recommended Action No action required.
Error Message%PLATFORM-FCTL-6-NO_SHUTDOWN [chars] has been activated
Explanation A fabric card has been activated. Can be done via an EXEC command.
Recommended Action No action required.
FCTLRP Messages
Error Message%PLATFORM-FCTLRP-2-CHKPT_REGISTRATION_FAILED Fabric control failed to register [chars] with CHKPT, cerrno=[dec]
Explanation FCTL encountered a problem registering with chkpt.
Recommended Action No action required.
Error Message%PLATFORM-FCTLRP-2-CRIT [chars]:[dec] [chars]
Explanation Software error found.
Recommended Action Wait to see if self-recovery takes place. Report problem.
Error Message%PLATFORM-FCTLRP-2-ERR_REPORT [chars]
Explanation A problem occurred with a fabric related component.
Recommended Action Log contains instructions. Usually, the failed component is replaced.
Error Message%PLATFORM-FCTLRP-2-FAILED_SYNCH Failed to drive slave clock on card [dec] from CSC[dec]
Explanation A card failed to synchronize clocks with the Master clock.
Recommended Action Replace failed card.
Error Message%PLATFORM-FCTLRP-3-API_RANGE [chars]:[dec] [chars], value=[hex], valid range=[hex]-[hex]
Explanation Software API usage error found.
Recommended Action Wait to see if self-recovery takes place. Report problem.
Error Message%PLATFORM-FCTLRP-3-API_RANGE_SLOT [chars]:[dec] [chars], value=[hex], valid range=[hex]-[hex], slot=[dec]
Explanation Software API usage error found from a slot.
Recommended Action Wait to see if self-recovery takes place. Report problem.
Error Message%PLATFORM-FCTLRP-3-API_STR [chars]:[dec] [chars], [chars]
Explanation Software API usage error found.
Recommended Action Wait to see if self-recovery takes place. Report problem.
Error Message%PLATFORM-FCTLRP-3-API_VALUE [chars]:[dec] [chars], [hex]
Explanation Software API usage error found.
Recommended Action Wait to see if self-recovery takes place. Report problem.
Error Message%PLATFORM-FCTLRP-3-API_VALUE_SLOT [chars]:[dec] [chars], value=[hex], slot=[dec]
Explanation Software API usage error found from a slot.
Recommended Action Wait to see if self-recovery takes place. Report problem.
Error Message%PLATFORM-FCTLRP-3-ERROR [chars]:[dec] [chars]
Explanation Software error found.
Recommended Action Wait to see if self-recovery takes place. Report problem.
Error Message%PLATFORM-FCTLRP-3-MBUS [chars]:[dec] [chars], errno=[hex], [chars]
Explanation A system resource was not available.
Recommended Action Wait to see if self-recovery takes place. Report problem.
Error Message%PLATFORM-FCTLRP-3-NO_CHASSIS Unable to read chassis model
Explanation The Backplane Server has not provided the chassis model.
Recommended Action Wait to see if self-recovery takes place. Report problem.
Error Message%PLATFORM-FCTLRP-3-SYSDB [chars]:[dec] [chars] [chars], rc=[hex], [chars]
Explanation A system resource was not available.
Recommended Action Wait to see if self-recovery takes place. Report problem.
Error Message%PLATFORM-FCTLRP-3-THREAD_CREATE_FAIL [chars]:[dec] Fail to create thread [chars]: rc=[hex], [chars]
Explanation Fail to create a thread.
Recommended Action Wait to see if self-recovery takes place. Report problem.
Error Message%PLATFORM-FCTLRP-4-SHUTDOWN [chars] has been shutdown
Explanation A fabric card has been shutdown. Can be done via an EXEC command or due to environmental monitoring (ENVMON).
Recommended Action Ensure that router has enough fabric bandwidth for line card types. Engine-2 cards require full bandwidth. Redundant clocks recommended. Reactivate or replace fabric card.
Error Message%PLATFORM-FCTLRP-5-FABRIC_CARD_OIR_INSERTED Fabric card [chars][dec] inserted in slot [dec]
Explanation Notification for inserted fabric card.
Recommended Action No action required.
Error Message%PLATFORM-FCTLRP-5-FABRIC_CARD_OIR_REMOVED Fabric card [chars][dec] removed from slot [dec]
Explanation Notification for removed fabric card.
Recommended Action No action required.
Error Message%PLATFORM-FCTLRP-6-NO_SHUTDOWN [chars] has been activated
Explanation A fabric card has been activated. Can be done via an EXEC command.
Recommended Action No action required.
FDIAGS Messages
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
Recommended Action Investigate
Error Message%PLATFORM-FDIAGS-3-CANNOT_GET_JID Cannot determin Job ID for Field Diags process
Explanation Error getting JID
Recommended Action Investigate
Error Message%PLATFORM-FDIAGS-3-CANT_HALT_MYSELF Can not halt myself
Explanation Self explanatory
Recommended Action Investigate
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
Recommended Action Investigate
Error Message%PLATFORM-FDIAGS-3-CLI_TOO_LONG Command line is too long
Explanation User tried to run Field Diags too much stuff on the CLI
Recommended Action Stop doing that.
Error Message%PLATFORM-FDIAGS-3-DIAG_ALREADY_RUNNING_HERE Field Diagnostics already running on this slot
Explanation Field Diags is already running on this slot. Cannot have two processes on the same slot
Recommended Action Stop doing that
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.
Recommended Action Investigate why MBUS Ram agent is not successfully downloaded on the fabric card.
Error Message%PLATFORM-FDIAGS-3-FAB_UNSTABLE Fabric unstable prior to beginning Field Diags Fabric tests
Explanation After launching Fabric Field Diagnostics, the fabric appear unstable, cards appear to be OIR'd or otherwise not ready for testing.
Recommended Action Don't do OIR's or card power-cycles immediately prior to Field Diags Fabric tests.
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
Recommended Action Investigate
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
Recommended Action Investigate
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.
Recommended Action Investigate
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
Recommended Action Investigate
Error Message%PLATFORM-FDIAGS-3-IF_BAD_JID_OPEN Unable to open Field Diags state file [chars]: [chars]
Explanation Error opening JID file
Recommended Action Investigate
Error Message%PLATFORM-FDIAGS-3-IF_BAD_JID_READ Unable to read Field Diags state from file [chars]: [chars]
Explanation Error reading JID file
Recommended Action Investigate
Error Message%PLATFORM-FDIAGS-3-IF_BAD_JID_WRITE Unable to write Field Diags state to file [chars]: [chars]
Explanation Error writing JID file
Recommended Action Investigate
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
Recommended Action investigate
Error Message%PLATFORM-FDIAGS-3-IF_FAIL_SEND_SYSLDR_F could not send LWM in [chars]()
Explanation Failed to Connect to sysloader initially
Recommended Action investigate
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
Recommended Action investigate
Error Message%PLATFORM-FDIAGS-3-IF_FAIL_UUT_LAUNCH UUT launch failed ([chars]). Exiting...
Explanation Failed to Connect to sysloader initially
Recommended Action investigate
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
Recommended Action investigate
Error Message%PLATFORM-FDIAGS-3-IF_NON_EXISTANT_JID_OPEN Unable to open Field Diags state file [chars]: [chars]
Explanation Error opening JID file
Recommended Action Investigate
Error Message%PLATFORM-FDIAGS-3-ILLEGAL_FSM_STATE internal (FSM) state change ILLEGAL: was [chars], attempted [dec]
Explanation Bad internal state change
Recommended Action Investigate
Error Message%PLATFORM-FDIAGS-3-MAX_CONCURRENT_TESTING_EXCEEDED Concurrent Line Card testing is limited to [dec] requests.
Fabric and PRP tesing must occur alone.Explanation Concurrent Line Card testing is limited.
Recommended Action None, user is restricted from exceeding these limits.
Error Message%PLATFORM-FDIAGS-3-MBUS_MISC_SVCS_FAILED To many retries when sending MBUS_MISC_SVCS general response to UUT
Explanation Retries exceeded preset value. For some reason we did not succeed in sending this response via the mbus
Recommended Action Investigate
Error Message%PLATFORM-FDIAGS-3-MISC_GET_FABRIC_CONFIG_RTN_FAILED To many retries when sending MISC_GET_FABRIC_CONFIG_RTN to UUT
Explanation Retries exceeded preset value. For some reason we did not succeed in sending this response via the mbus
Recommended Action Investigate
Error Message%PLATFORM-FDIAGS-3-MISC_GET_SWITCH_CARD_TYPES_RTN_FAILED To many retries when sending MISC_GET_SWITCH_CARD_TYPES_RTN to UUT
Explanation Retries exceeded preset value. For some reason we did not succeed in sending this response via the mbus
Recommended Action Investigate
Error Message%PLATFORM-FDIAGS-3-MS_NO_CARD_ID misc svcs: [chars](): Retries failed to get card ID
Explanation Failed to receive back card ID
Recommended Action investigate
Error Message%PLATFORM-FDIAGS-3-MS_NODE_ID_CREATE_FAIL_F Could create nodeid for slot [dec]: [chars] in [chars]()
Explanation Failed to write a slot-specific register via an mbus-access
Recommended Action investigate
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
Recommended Action investigate
Error Message%PLATFORM-FDIAGS-3-MS_READ_REG_FAIL Failed in reading register [hex] from slot [dec]
Explanation Failed to read a slot-specific register vis an mbus-access
Recommended Action investigate
Error Message%PLATFORM-FDIAGS-3-MS_READ_REG_FAIL_F Failed in reading register [hex] from slot [dec] in [chars]()
Explanation Failed to read a slot-specific register vis an mbus-access
Recommended Action investigate
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
Recommended Action investigate
Error Message%PLATFORM-FDIAGS-3-MS_WRITE_REG_FAIL Failed in writing [hex] to register [hex] on slot [dec]
Explanation Failed to write a slot-specific register via an mbus-access
Recommended Action investigate
Error Message%PLATFORM-FDIAGS-3-MS_WRITE_REG_FAIL_F Failed in writing [hex] to register [hex] on slot [dec] in [chars]()
Explanation Failed to write a slot-specific register via an mbus-access
Recommended Action investigate
Error Message%PLATFORM-FDIAGS-3-MS_XBAR_MAP misc svcs: [chars]: could not read xbar map
Explanation Failed to read xbar map from fctl
Recommended Action investigate
Error Message%PLATFORM-FDIAGS-3-MUTUAL_EXCL_ROE ROE & COE are mutually exclusive
Explanation User tried to run Field Diags with ROE & COE both.
Recommended Action Stop Doing that
Error Message%PLATFORM-FDIAGS-3-NO_ACTIVE_JID_FOR_THIS_SLOT HALT request ignored, since there is no Field Diag running for slot [dec]
Explanation Can't halt something that isn't running, now can we?
Recommended Action Stop doing that
Error Message%PLATFORM-FDIAGS-3-NO_HALT_ALONE halt request must be exclusive: no other options permitted
Explanation User tried to run Field Diags with halt option and other flage
Recommended Action Halt must be the only option
Error Message%PLATFORM-FDIAGS-3-NO_RUN_ACTIVE_RP Can not run Field Diags on Active RP
Explanation User tried to run field Diags on the master RP - not supported.
Recommended Action Cease this particular launch method OR if user wants to test master RP, force a switchover (failover) and then run the test against that first board.
Error Message%PLATFORM-FDIAGS-3-NO_RUN_MY_NODE Can not run Field Diags on Master (DSC) RP
Explanation User tried to run field Diags on the DSC RP - not supported.
Recommended Action Cease this particular launch method OR if user wants to test master RP, force a switchover (failover) and then go to console of new master RP and run the test against that first board.
Error Message%PLATFORM-FDIAGS-3-NO_RUN_OTHER_RACK C12000 only supports rack 0
Explanation User tried to run field Diags on rack other than 0 - unsupported
Recommended Action Cease this particular launch method
Error Message%PLATFORM-FDIAGS-3-NO_SPA No SPA present on user-selected subslot (instance)
Explanation User requested testing of an empty SPA bay
Recommended Action Select a SPA bay with a SPA present or test entire LC by setting instance to 'CPU0'
Error Message%PLATFORM-FDIAGS-3-NO_TIME_OF_DAY no time of day
Explanation Time of Day unavailable internally
Recommended Action Investigate
Error Message%PLATFORM-FDIAGS-3-NO_WAIT_FOR_STDBY_RP WAIT option illegal for Stand-by RP so that it is available for failover, exiting...
Explanation Wait option illegal for Stand-by RP so that is is available for failover
Recommended Action Stop doing that
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
Recommended Action Investigate
Error Message%PLATFORM-FDIAGS-3-NON_HELLO_MSG During Init state, unexpected sub-message [hex] received from slot [dec]
Explanation Self explanatory
Recommended Action Investigate
Error Message%PLATFORM-FDIAGS-3-NON_UUT_IN_STATE Unexpected message received during UUT_ON state: sub-msg [hex] from slot [dec]
Explanation Self explanatory
Recommended Action Investigate
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 comaptibility with diags for C2W requests for SPA communication
Recommended Action Investigate
Error Message%PLATFORM-FDIAGS-3-SPA_ID_FAIL Failure when trying to identify SPA's attached to card in slot [dec]
Explanation A call to mbus_get_spa_type() returned an error
Recommended Action Investigate
Error Message%PLATFORM-FDIAGS-3-SPA_UNSUPPORTED_INSTANCE Requested instance ([dec]) (bay) not supported by this UUT (min=[dec], max=[dec])
Explanation Spa bay requsted not supported
Recommended Action Investigate
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
Recommended Action Investigate
Error Message%PLATFORM-FDIAGS-3-SYSLDR_RESULT_CODE_OUT_OF_BOUNDS Result code from sysloader ([dec]) exceeds list of known messages
Explanation Coding violation
Recommended Action Sysldr code returns unexpected cause.
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
Recommended Action nothing
Error Message%PLATFORM-FDIAGS-3-T_O_D_CONVERT_ERR time of day conversion error
Explanation Internal Time Of Day conversion error
Recommended Action Investigate
Error Message%PLATFORM-FDIAGS-3-UNRECOGNIZED_CARD Card tupe ([dec]) not NOT recognized
Explanation This card type is not recognized in this version
Recommended Action if available, upgrade to a more recent vesion 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 vesion of the diags component.
Error Message%PLATFORM-FDIAGS-3-UNSUPP_OPT_FABRIC_CARD Option [chars] is not supported for CSC/SFC cards, exiting...
Explanation Certain options are not supported in CSC & SFC cards.
Recommended Action Stop doing that
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
Recommended Action Investigate
Error Message%PLATFORM-FDIAGS-4-TESTLEVEL_OPT_VALUE_MISSING The testlevel option needs a value.
Explanation User failed to input a value with the testlevel opton.
Recommended Action Retype the command
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.
Recommended Action The developer should investigate. This should never happen, but it won't really harm anything.
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 Investigate
Error Message%PLATFORM-FDIAGS-5-DEBUG_OVERRIDE_NO_OVERALL_PASS_FAIL_TO_SYSLDR Debug override: do not send the overall pass/fail result to sysldr.
Explanation Debug override for corner case testing of errors in DevTest.
Recommended Action None as this is a debug override.
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-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-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 preceeding 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 da console for output.
Recommended Action investigate
Error Message%PLATFORM-FDIAGS-5-IF_TERMINATED_F_DIAGS_OK Successfully terminated Field Diags (jid=[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-JID_SHOW Field Diags process jid is [dec]
Explanation Just a notice of what jid this instance of Field Diags is.
Recommended Action No action - notice 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 restire the system one
Recommended Action Notice only
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 comaptibility with diags for C2W requests for SPA communication
Recommended Action Notice only
Error Message%PLATFORM-FDIAGS-5-LOG_OVERALL_PASS_FAIL_RESULT Field Diagnostics COMPLETE on Unit-Under-Test ([chars]): [chars]
Explanation Log the overall pass/fail result of the Field Diagnostics
Recommended Action Not applicable, informational message only
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-5-TEST_THIS Running test for slot [dec] - LOG MESSAGES!
Explanation For testing messages infrastructure
Recommended Action No action - test performed successfully.
Error Message%PLATFORM-FDIAGS-6-OUT [chars]
Explanation Non error-specific redirected output from diag process to syslog
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)
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)
Recommended Action No action
FFQ Messages
Error Message%PLATFORM-FFQ-3-CORRUPT_PKT Corrupted packet, start_offset [hex], length [unsigned int], slot [unsigned int]
Explanation This message indicates that a buffer was received from the fabric with a corrupted buffer header.
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-FFQ-3-CORRUPT_PTR Assembler packet pointer corrupt: pkt [hex], dgram [hex], oq [hex]
Explanation This message indicates that the reassembly buffer pointer used by assembler is incorrect.
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-FFQ-3-FATAL ffq: fatal error encountered, reason=[chars]
Explanation ffq 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-FFQ-3-FATAL_2 ffq: fatal error encountered, reason=[chars], errno=[dec]
Explanation ffq 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-FFQ-3-GEN_INFO ffq: general information,
Explanation The FFQ's informational 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.
Error Message%PLATFORM-FFQ-3-INFO ffq: service degrading error, reason = [chars]
Explanation The ffq encountered an error that would lead to degraded service.
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-FFQ-3-MALLOC_FAILED FFQ: queue [dec] alloc [dec] bytes error for ptr [hex] of max [hex]
Explanation FFQ encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-FFQ-3-MEM_ERR No memory available for Assembler queues in [chars]
Explanation This message indicates that Assembler driver is not able to allocate memory for the Queues and other use. This usually indicates a memory problem.
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-FFQ-3-NOBUF No buffers available for Assembler error [unsigned int]
Explanation This message indicates that there are too many messages coming from the GSR Line Card. There are no more buffers on the RP to handle these messages. Try shutting down debugs on Line Card or reloading it.
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-FFQ-3-NOT_YET_IMPLEMENTED ffq: this function is not yet implemented
Explanation FFQ, a function was not implemented.
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-FFQ-3-PAK_INVALID Invalid packet type [dec]
Explanation FFQ has received an invalid packet type from the fabric.
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-FFQ-3-RATEI No timer interval for [chars]
Explanation An internal data structure was missing a field.
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-FFQ-3-RATEW No timer wheel for [chars]
Explanation An internal data structure was missing a field.
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-FFQ-3-TMR Call to [chars] failed, cerrno=[hex]
Explanation The library call 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-FFQ-3-USAGE ffq: invalid option passed to ffq server
Explanation Startup option supplied to FFQ is not valid.
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.
FIA_API Messages
Error Message%PLATFORM-FIA_API-3-FATAL_ERROR Fatal error: [chars]: [chars]: [dec]
Explanation A fatal error occurred in FIA library which caused the process to exit.
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-FIA_API-6-INFO_MSG Info: [chars]: [chars]
Explanation This is an informational message from the FIA library.
Recommended Action No action is required.
Error Message%PLATFORM-FIA_API-7-DEBUG_MSG Debug: [chars]: [chars] errno [dec]
Explanation This is a debug message from the FIA library to indicate anomolies which are not fatal. These messages should only appear for transient periods.
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.
FIA_CHK_API Messages
Error Message%PLATFORM-FIA_CHK_API-3-FATAL_ERROR Fatal error: [chars]: [chars]: [dec]
Explanation A fatal error occurred in FIA system checkout library which caused the process to exit.
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-FIA_CHK_API-6-INFO_MSG Info: [chars]: [chars]
Explanation This is an informational message from the FIA system checkout library.
Recommended Action No action is required.
Error Message%PLATFORM-FIA_CHK_API-7-DEBUG_MSG Debug: [chars]: [chars] errno [dec]
Explanation This is a debug message in the FIA system checkout library to indicate anomolies which are not fatal. These messages should only appear for transient periods.
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.
FIA Messages
Error Message%PLATFORM-FIA-2-EIO_TRAIN_FAIL EIO link training failure threshold reached. Link will not be re-trained. ASIC instance: [dec], EIO link ID: [dec]
Explanation Repeated attempts to train the EIO links between the FIA and Sprayer ASIC have failed. No further attempts to retrain the link will be made.
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-FIA-3-FATAL_ERROR Fatal error: [chars]: [chars]: [hex]
Explanation A fatal error occurred in the FIA driver which may have caused the process to exit.
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-FIA-3-FATAL_MSG Fatal: [chars]: [chars]
Explanation This message indicates and error has occurred within the FIA driver.
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-FIA-3-PIO_FATAL_ERROR Asic PIO failure : [chars], instance [dec]: rc [dec] cerr [chars] errno [dec] data1 [hex] data2 [hex]
Explanation A fatal error occurred related to access to a FIA device by the FIA driver.
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-FIA-6-INFO_MSG Info: [chars]: [chars]
Explanation This is an informational message from the FIA driver.
Recommended Action No action is required.
Error Message%PLATFORM-FIA-7-DEBUG_MSG Debug: [chars]: [chars] errno [dec]
Explanation This is a debug message in the FIA driver to indicate anomolies which are not fatal. These messages should only appear for transient periods.
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.
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.
GASPP_CLN Messages
Error Message%PLATFORM-GASPP_CLN-3-FATAL gaspp: fatal error encountered, reason=[chars]
Explanation iq 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-GASPP_CLN-3-FATAL_2 gaspp: fatal error encountered, reason=[chars], errno=[dec]
Explanation gaspp 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-GASPP_CLN-3-GEN_INFO gaspp: general information,
Explanation The GASPP's informational 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.
Error Message%PLATFORM-GASPP_CLN-3-INFO gaspp: service degrading error, reason = [chars]
Explanation The gaspp encountered an error that would lead to degraded service.
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-GASPP_CLN-3-MALLOC_FAILED GASPP: fatal memory allocation error for bytes
Explanation GASPP encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-GASPP_CLN-3-NOT_YET_IMPLEMENTED gaspp: this function is not yet implemented
Explanation GASPP, a function was not implemented.
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-GASPP_CLN-3-STRDUP_FAILED GASPP: strdup of string: [chars], failed.
Explanation GASPP encountered a fatal strdup error.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-GASPP_CLN-3-USAGE gaspp: invalid option passed to gaspp server
Explanation Startup option supplied to GASPP is not valid.
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.
GASPP_DRV Messages
Error Message%PLATFORM-GASPP_DRV-3-FATAL gaspp: fatal error encountered, reason=[chars]
Explanation iq 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-GASPP_DRV-3-FATAL_2 gaspp: fatal error encountered, reason=[chars], errno=[dec]
Explanation gaspp 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-GASPP_DRV-3-GEN_INFO gaspp: general information,
Explanation The GASPP's informational 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.
Error Message%PLATFORM-GASPP_DRV-3-INFO gaspp: service degrading error, reason = [chars]
Explanation The gaspp encountered an error that would lead to degraded service.
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-GASPP_DRV-3-MALLOC_FAILED GASPP: fatal memory allocation error for bytes
Explanation GASPP encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-GASPP_DRV-3-NOT_YET_IMPLEMENTED gaspp: this function is not yet implemented
Explanation GASPP, a function was not implemented.
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-GASPP_DRV-3-READ_ERR GASPP: register [chars] is not readable
Explanation this register is a write-only register.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-GASPP_DRV-3-STRDUP_FAILED GASPP: strdup of string: [chars], failed.
Explanation GASPP encountered a fatal strdup error.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-GASPP_DRV-3-USAGE gaspp: invalid option passed to gaspp server
Explanation Startup option supplied to GASPP is not valid.
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-GASPP_DRV-3-WRITE_ERR GASPP: register [chars] is not writable
Explanation this register is a read-only register.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
GASPP_SET Messages
Error Message%PLATFORM-GASPP_SET-3-FATAL gaspp: fatal error encountered, reason=[chars]
Explanation iq 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-GASPP_SET-3-FATAL_2 gaspp: fatal error encountered, reason=[chars], errno=[dec]
Explanation gaspp 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-GASPP_SET-3-GEN_INFO gaspp: general information,
Explanation The GASPP's informational 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.
Error Message%PLATFORM-GASPP_SET-3-INFO gaspp: service degrading error, reason = [chars]
Explanation The gaspp encountered an error that would lead to degraded service.
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-GASPP_SET-3-MALLOC_FAILED GASPP: fatal memory allocation error for bytes
Explanation GASPP encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-GASPP_SET-3-NOT_YET_IMPLEMENTED gaspp: this function is not yet implemented
Explanation GASPP, a function was not implemented.
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-GASPP_SET-3-USAGE gaspp: invalid option passed to gaspp server
Explanation Startup option supplied to GASPP is not valid.
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.
GASPP_SHOW Messages
Error Message%PLATFORM-GASPP_SHOW-3-FATAL gaspp: fatal error encountered, reason=[chars]
Explanation iq 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-GASPP_SHOW-3-FATAL_2 gaspp: fatal error encountered, reason=[chars], errno=[dec]
Explanation gaspp 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-GASPP_SHOW-3-GEN_INFO gaspp: general information,
Explanation The GASPP's informational 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.
Error Message%PLATFORM-GASPP_SHOW-3-INFO gaspp: service degrading error, reason = [chars]
Explanation The gaspp encountered an error that would lead to degraded service.
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-GASPP_SHOW-3-MALLOC_FAILED GASPP: fatal memory allocation error for bytes
Explanation GASPP encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-GASPP_SHOW-3-NOT_YET_IMPLEMENTED gaspp: this function is not yet implemented
Explanation GASPP, a function was not implemented.
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-GASPP_SHOW-3-USAGE gaspp: invalid option passed to gaspp server
Explanation Startup option supplied to GASPP is not valid.
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_lc_exmem Messages
Error Message%PLATFORM-GSR_lc_exmem-1-RES_ERROR System run out of [chars], no pages left
Explanation A error occurred in GSR external memory manager resulting in a failure to provide some system service as indicated in the message text.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PLATFORM-GSR_lc_exmem-3-ERROR exmem: error encountered, reason=[chars]
Explanation The LC external memory manager could not complete proper 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-GSR_lc_exmem-3-FATAL exmem: fatal error encountered, reason=[chars]
Explanation The LC external memory manager could not complete proper 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-GSR_lc_exmem-4-exception [chars]
Explanation A SW exception of unexpected condition or an out of resources (memory, HW profiles, etc) situation.
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 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-3-FATAL GSR_LC_PM: Fatal Error, reason = [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=[chars], errno=[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-FAULT_EH Fault Occurred - Reset [chars]
Explanation Platform manager Error Handling recieved an error from one of the LC devices. The PM will handle the 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-GSR_LC_PM-3-GEN_INFO gsr_lc_pm: general information,
Explanation The GSR_LC_PM's informational 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.
Error Message%PLATFORM-GSR_LC_PM-3-INFO gsr_lc_pm: service degrading error, reason = [chars]
Explanation The gsr_lc_pm encountered an error that would lead to degraded service.
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-MALLOC_FAILED GSR_LC_PM: fatal memory allocation error for bytes
Explanation GSR_LC_PM encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-GSR_LC_PM-3-NOT_YET_IMPLEMENTED gsr_lc_pm: this function is not yet implemented
Explanation GSR_LC_PM, a function was not implemented.
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-USAGE gsr_lc_pm: invalid option passed to gsr_lc_pm server
Explanation Startup option supplied to GSR_LC_PM is not valid.
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_LIB Messages
Error Message%PLATFORM-GSR_LIB-3-EVM_ATTACH_ERR Event manager async attach failed code [dec]
Explanation An internal operation failed. The system will attempt to recover.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative. You may have to restart the card.
Error Message%PLATFORM-GSR_LIB-3-EVM_CREATE_ERR Event manager create failed for [chars] code [dec]
Explanation An internal operation failed. The system will attempt to recover.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative. You may have to restart the card.
Error Message%PLATFORM-GSR_LIB-3-NOMEM Malloc failed for [chars]
Explanation No memory was available for a resource.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative. You may have to restart the card.
Error Message%PLATFORM-GSR_LIB-3-PTHREAD_CREATE_ERR Thread creation failed with code [dec]
Explanation An internal operation failed. The system will attempt to recover.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative. You may have to restart the card.
Error Message%PLATFORM-GSR_LIB-3-QSM_ADD_ERR Could not publish evm name '[chars]' code [dec]
Explanation An internal operation failed. The system will attempt to recover.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative. You may have to restart the card.
Error Message%PLATFORM-GSR_LIB-3-SYSDB_BIND_ERR SysDB bind to [chars] failed with [chars]
Explanation An internal operation failed. The system will attempt to recover.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative. You may have to restart the card.
Error Message%PLATFORM-GSR_LIB-3-SYSDB_EDM_ERR Edm register at bind point failed with ([chars])
Explanation An internal operation failed. The system will attempt to recover.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative. You may have to restart the card.
Error Message%PLATFORM-GSR_LIB-3-THREAD_CTL Kernel call returned error. errno=[dec]
Explanation An internal operation failed. The system will attempt to recover.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative. You may have to restart the card.
Error Message%PLATFORM-GSR_LIB-4-UNREG_ASYNC Error: Got an unregistered for async event ([dec])
Explanation An unexpected event has occurred.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative.
GSR_PRP_PM Messages
Error Message%PLATFORM-GSR_PRP_PM-2-FATAL_PM gsr_prp_pm: Error Handling - FATAL severity error from [chars] device
Explanation Platform manager Error Handling received a FATAL severity error from one of the PRP devices. The PM will handle the 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-GSR_PRP_PM-2-HIGH_PM Reset [chars]
Explanation Platform manager Error Handling received a HIGH severity error from one of the PRP devices. The PM will handle the 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-GSR_PRP_PM-2-LOW_PM gsr_prp_pm: Error Handling - LOW severity error from [chars] device
Explanation Platform manager Error Handling received a LOW severity error from one of the PRP devices. The PM will handle the 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-GSR_PRP_PM-2-UNKNOWN_INST_PM gsr_prp_pm: Error Handling - UNKNOWN device instance received
Explanation Platform manager Error Handling received an unknown device instance from one of the PRP devices. The PM will handle the 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-GSR_PRP_PM-2-UNKNOWN_PM gsr_prp_pm: Error Handling - UNKNOWN severity error from [chars] device
Explanation Platform manager Error Handling received an unknown severity error from one of the PRP devices. The PM will handle the 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-GSR_PRP_PM-3-CHKPT_NORESTORE The driver was not able to restore '[chars]' from checkpointed data.
Explanation No checkpointing record was found in the table.
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_PRP_PM-3-FATAL gsr_prp_pm: fatal error encountered, reason=[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_PRP_PM-3-FATAL_2 gsr_prp_pm: fatal error encountered, reason=[chars], errno=[dec]
Explanation gsr_prp_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_PRP_PM-3-GEN_INFO gsr_prp_pm: general information,
Explanation The GSR_PRP_PM's informational 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.
Error Message%PLATFORM-GSR_PRP_PM-3-INFO gsr_prp_pm: service degrading error, reason = [chars]
Explanation The gsr_prp_pm encountered an error that would lead to degraded service.
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_PRP_PM-3-MALLOC_FAILED GSR_PRP_PM: fatal memory allocation error for bytes
Explanation GSR_PRP_PM encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-GSR_PRP_PM-3-NOT_YET_IMPLEMENTED gsr_prp_pm: this function is not yet implemented
Explanation GSR_PRP_PM, a function was not implemented.
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_PRP_PM-3-USAGE gsr_prp_pm: invalid option passed to gsr_prp_pm server
Explanation Startup option supplied to GSR_PRP_PM is not valid.
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.
GT_I2C Messages
Error Message%PLATFORM-GT_I2C-3-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.
Error Message%PLATFORM-GT_I2C-3-DRV_ERR [chars]
Explanation Error detected when starting the i2c driver
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-GT_I2C-3-REWORK_AND_UPGRADE_REQUIRED Detected old PLD version = [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-6-BUS_HANG Detected i2c bus hang, attempting to unhang the bus......
Explanation Detected i2c bus hang.
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.
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_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 Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-HFR_LCPM_SHOW-3-FATAL hfr_pm_show: fatal error encountered, reason=[chars]
Explanation hfr_pm show 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-HFR_LCPM_SHOW-3-FATAL_2 hfr_pm_show: fatal error encountered, reason=[chars], errno=[dec]
Explanation hfr_pm_show 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-HFR_LCPM_SHOW-3-GEN_INFO hfr_pm_show: general information,
Explanation The HFR_PM_SHOW's informational 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.
Error Message%PLATFORM-HFR_LCPM_SHOW-3-INFO hfr_pm_show: service degrading error, reason = [chars]
Explanation The hfr_pm_show encountered an error that would lead to degraded service.
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-HFR_LCPM_SHOW-3-MALLOC_FAILED HFR_PM_SHOW: fatal memory allocation error for bytes
Explanation HFR_PM_SHOW encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-HFR_LCPM_SHOW-3-NOT_YET_IMPLEMENTED hfr_pm_show: this function is not yet implemented
Explanation HFR_PM_SHOW, a function was not implemented.
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-HFR_LCPM_SHOW-3-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 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.
HFR_PM_TEST Messages
Error Message%PLATFORM-HFR_PM_TEST-3-FATAL hfr_pm_test: fatal error encountered, reason=[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 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-HFR_PM_TEST-3-FATAL_2 hfr_pm_test: fatal error encountered, reason=[chars], errno=[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 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-HFR_PM_TEST-3-GEN_INFO hfr_pm_test: general information,
Explanation The HFR_PM_TEST's informational 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.
Error Message%PLATFORM-HFR_PM_TEST-3-INFO hfr_pm_test: service degrading error, reason = [chars]
Explanation The hfr_pm_test encountered an error that would lead to degraded service.
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-HFR_PM_TEST-3-MALLOC_FAILED HFR_PM_TEST: fatal memory allocation error for bytes
Explanation HFR_PM_TEST encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-HFR_PM_TEST-3-NOT_YET_IMPLEMENTED hfr_pm_test: this function is not yet implemented
Explanation HFR_PM_TEST, a function was not implemented.
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-HFR_PM_TEST-3-USAGE hfr_pm_test: invalid option passed to hfr_pm_test command.
Explanation Startup option supplied to HFR_PM_TEST is not valid.
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.
HFR_PM Messages
Error Message%PLATFORM-HFR_PM-2-FATAL fatal error encountered, reason=[chars]
Explanation hfr_pm 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-HFR_PM-2-FATAL_2 fatal error encountered, reason=[chars], errno=[dec]
Explanation hfr_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-HFR_PM-2-FAULT_CANT_BE_SENT Cannot send [chars] #[dec] fault=[chars] to shelf mgr. Resetting
Explanation The specified device has a fault that affects the card functionality. Communication with the Shelf Manager could not be established to send fault information, so the card node 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-HFR_PM-2-MALLOC_FAILED fatal memory allocation error for bytes
Explanation HFR_PM encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-HFR_PM-2-UPDOWN Card changed state to [chars]
Explanation The card hardware went either up or down.
Recommended Action If the state change was unexpected, check the configuration setting for the card and also check events using 'show logging' 'show interface' and 'show controller' commands.
Error Message%PLATFORM-HFR_PM-3-ERROR HFR_PM error, reason=[chars]
Explanation The Platform Manager 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-HFR_PM-3-ERROR2 HFR_PM error, reason=[chars], errno=[dec]
Explanation The Platform Manager 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-HFR_PM-3-FATAL hfr_pm: fatal error encountered, reason=[chars]
Explanation iq 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-HFR_PM-3-FATAL_2 hfr_pm: fatal error encountered, reason=[chars], errno=[dec]
Explanation hfr_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-HFR_PM-3-GEN_INFO hfr_pm: general information,
Explanation The HFR_PM's informational 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.
Error Message%PLATFORM-HFR_PM-3-INFO hfr_pm: service degrading error, reason = [chars]
Explanation The hfr_pm encountered an error that would lead to degraded service.
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-HFR_PM-3-MALLOC_FAILED HFR_PM: fatal memory allocation error for bytes
Explanation HFR_PM encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-HFR_PM-3-NOT_YET_IMPLEMENTED hfr_pm: this function is not yet implemented
Explanation HFR_PM, a function was not implemented.
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-HFR_PM-3-USAGE hfr_pm: invalid option passed to hfr_pm server
Explanation Startup option supplied to HFR_PM is not valid.
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-HFR_PM-4-WARNING HFR_PM warning: [chars]
Explanation The Platform Manager 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.
HSR_ES_CLI Messages
Error Message%PLATFORM-HSR_ES_CLI-3-CAPS_LOAD_FAILED Sponge caps load failed, sponge_caps = [dec], rc = [dec] ([chars])
Explanation Failed to load capsulation DLL
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-HSR_ES_CLI-3-ERR [chars], rc = [dec] ([chars])
Explanation Generic error. A string explaining the error condition, an error code and a string description of the error are 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-HSR_ES_CLI-3-FATAL Fatal error encountered, reason=[chars]
Explanation HSR ES client 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-HSR_ES_CLI-3-FATAL_2 Fatal error encountered, reason=[chars], errno=[dec]
Explanation HSR ES client 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-HSR_ES_CLI-3-FATAL_3 Fatal error encountered, reason=[chars], errno=[dec] ([chars])
Explanation HSR ES client 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 along with string descrioption of the 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-HSR_ES_CLI-3-UNK_MSG_CODE Connecting to pakman, [chars], msg_code = [dec]
Explanation Unknwn message code send by Pakman server
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-HSR_ES_CLI-6-INFO [chars]
Explanation Prints an informational statement
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.
I2C Messages
Error Message%PLATFORM-I2C-6-BOARD_POWERUP_FAIL [I2C-DEBUG]: 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-6-BOARD_POWERUP_NOT_HAPPENED [I2C-DEBUG]: 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-6-LC_BAD_VRM_INFO [I2C-DEBUG]: 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-6-LC_POWER_FAIL [I2C-DEBUG]: 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-6-LC_POWERUP_CHECK_FAIL [I2C-DEBUG]: 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-6-SEND_PULSE [I2C-DEBUG]: Successfully sent pulse to shelfmgr
Explanation None
Recommended Action Check the path of file specified for download
Error Message%PLATFORM-I2C-6-SEND_PULSE_FAIL [I2C-DEBUG]: Failed to send pulse because [chars] failed
Explanation None
Recommended Action Check the path of file specified for download
INV Messages
Error Message%PLATFORM-INV-3-DLLMAIN_FAIL dllmain: Inventory Manager failed in [chars] (Error: [chars])
Explanation Failure in Inventory Manager dllmain function call
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-3-FAIL Inventory Manager : [chars]
Explanation Failure in Inventory Manager resulting in error 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.
Error Message%PLATFORM-INV-3-FAIL The Inventory Manager Thread : [chars]
Explanation Failure in Inventory Manager resulting in error 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.
Error Message%PLATFORM-INV-3-MSG_RACK_CREATE_FAILED 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-4-WARN Inventory Manager : [chars]
Explanation These failures in Inventory Manager should generate 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-INV-4-WARN Inventory Manager : [chars]
Explanation These failures in Inventory Manager should generate 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.
INVMGR Messages
Error Message%PLATFORM-INVMGR-3-EXTRACT_SLOT nodeid_extract_fields for nodeid [dec] failed. Error: [chars]
Explanation Platform function return error on invocation
Recommended Action Ensure the Platform Library is available.
Error Message%PLATFORM-INVMGR-3-FAIL The Inventory Manager Thread : [chars]
Explanation Failure in Inventory Manager resulting in error 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.
Error Message%PLATFORM-INVMGR-3-INTERNAL_ERROR [chars]: [chars]
Explanation Miscellaneous 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-INVMGR-3-MSG_EEPROM_READ_FAILED [chars]: EEPROM/NVRAM Read Failed for [chars] return code [dec]
Explanation EEPROM/NVRAM read failed for a chassis or Card or SPA
Recommended Action check the card/chassis
Error Message%PLATFORM-INVMGR-3-MSG_GSR_EVM_CREATE_FAILED Event Manager create failed. Error: [chars]
Explanation The Event Manager could not be created.
Recommended Action None. Inventory Manager process will restart automatically
Error Message%PLATFORM-INVMGR-3-MSG_GSR_SYSDB_BIND_FAILED SysDB bind to [chars] failed. Error: [chars]
Explanation Could not bind to SysDB
Recommended Action Ensure SysDB is available on the system.
Error Message%PLATFORM-INVMGR-3-MSG_GSR_SYSDB_NOTIFY_REG_FAILED SysDB register for notification on [chars] failed. Error: [chars]
Explanation Could not register for notification in Sysdb
Recommended Action None. Inventory Manager process will restart automatically
Error Message%PLATFORM-INVMGR-3-MSG_GSR_SYSMGR_PROC_READY_FAILED System Manager's sysmgr_proc_ready failed. Error: [chars]
Explanation The sysmgr_proc_ready() function failed.
Recommended Action None.
Error Message%PLATFORM-INVMGR-3-MSG_RACK_CREATE_FAILED 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-INVMGR-3-NODEID_CREATE nodeid_create for slot [dec] failed. Error: [chars]
Explanation Platform function return error on invocation
Recommended Action Ensure the Platform Library is available.
Error Message%PLATFORM-INVMGR-4-MSG_CARD_CREATE_FAILED Memory for Card in Slot [dec] could not be allocated
Explanation The Card entry will not be added in inventory
Recommended Action check the memory on the system
Error Message%PLATFORM-INVMGR-4-MSG_FUNCTION_FAILED_FOR_CARD Function [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-4-MSG_GENERIC_INFO [chars]: Value [dec]
Explanation Generic Debug messages
Recommended Action check the memory on the system
Error Message%PLATFORM-INVMGR-4-MSG_MEM_ALLOC_FAILED [chars], Could not allocate Memory for Slot [dec]
Explanation Memory could not be allocated
Recommended Action check the memory on the system
Error Message%PLATFORM-INVMGR-4-MSG_OBJECT_CREATE_FAILED [chars], Could not allocate Memory for Slot [dec]
Explanation The entry will not be added in inventory
Recommended Action check the memory on the system
Error Message%PLATFORM-INVMGR-4-MSG_SENSOR_CREATE_FAILED Memory for Slot [dec], Sensor [dec] could not be allocated
Explanation The sensor entry will not be added in inventory
Recommended Action check the memory on the system
Error Message%PLATFORM-INVMGR-4-SYSDB_GET_FAILED sysdb_item_get failed for [chars]
Explanation The sysdb tuple is not available
Recommended Action Tuple need not be there.
Error Message%PLATFORM-INVMGR-4-SYSDB_NOTIFICATION_ARRIVED [chars]: notification arrived for nodeid [dec] value = [dec]
Explanation The sysdb tuple is modified
Recommended Action Nothing
Error Message%PLATFORM-INVMGR-4-WARN Inventory Manager : [chars]
Explanation These failures in Inventory Manager should generate 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-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.
IPCLC Messages
Error Message%PLATFORM-IPCLC-3-EVENT Event ([unsigned int]) [chars] error
Explanation Command/event processing operational errors.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PLATFORM-IPCLC-3-EVENT Event ([unsigned int]) [chars] error
Explanation Command/event processing operational errors.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PLATFORM-IPCLC-3-EVENTSYS Event ([unsigned int]) system call [chars] error (cause: [chars])
Explanation IPC kernel system call errors.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PLATFORM-IPCLC-3-EVENTSYS Event ([unsigned int]) system call [chars] error (cause: [chars])
Explanation IPC kernel system call errors.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PLATFORM-IPCLC-3-INTRLVL LC interrupt level IPC event, [chars]
Explanation LC interrupt level, IPC event processing errors.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PLATFORM-IPCLC-3-INTRLVL LC interrupt level IPC event, [chars]
Explanation LC interrupt level, IPC event processing errors.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PLATFORM-IPCLC-3-MSGERR [chars] ([dec])
Explanation The line card IPC cannot register with the route processor. It cannot exchange messages route processor.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PLATFORM-IPCLC-3-MSGERR [chars] ([dec])
Explanation The line card IPC cannot register with the route processor. It cannot exchange messages route processor.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PLATFORM-IPCLC-3-OP [chars]
Explanation Command/event processing operation errors.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PLATFORM-IPCLC-3-OP [chars]
Explanation Command/event processing operation errors.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PLATFORM-IPCLC-3-REPLY Reply (to cmd [unsigned int]) [chars] error
Explanation Command/event processing operational errors.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PLATFORM-IPCLC-3-REPLY Reply (to cmd [unsigned int]) [chars] error
Explanation Command/event processing operational errors.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PLATFORM-IPCLC-3-REPLYSYS Reply (to cmd [unsigned int]) system call [chars] error (cause: [chars])
Explanation Reply-to-RP-command operation errors.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
Error Message%PLATFORM-IPCLC-3-REPLYSYS Reply (to cmd [unsigned int]) system call [chars] error (cause: [chars])
Explanation Reply-to-RP-command operation errors.
Recommended Action Copy the error message exactly as it appears, and report it to your technical support representative.
IPMCAST Messages
Error Message%PLATFORM-IPMCAST-5-ERR [chars] [chars]=[hex]
Explanation Errors in processing IP multicast packet
Recommended Action Copy the error message exactly as it appears on the console, and report it to your technical support representative.
Error Message%PLATFORM-IPMCAST-5-ERR [chars] [chars]=[hex]
Explanation Errors in processing IP multicast packet
Recommended Action Copy the error message exactly as it appears on the console, and report it to your technical support representative.
LIB_NAME Messages
Error Message%PLATFORM-LIB_NAME-3-WARNING [chars] failed with [chars]
Explanation An internal operation failed.
Recommended Action Copy the message exactly as it appears, and report it to your technical support representative. You may have to restart the card.
Error Message%PLATFORM-LIB_NAME-7-CLASS_OP_ERROR [chars]: Class op [chars] failed on class [chars] : [chars]
Explanation An NRS operation failed on the specified class
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-LIB_NAME-7-CLASS_OP_ERROR [chars]: Class op [chars] failed on class [chars] : [chars]
Explanation An NRS operation failed on the specified class
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-LIB_NAME-7-ENS_OP_ERROR [chars]: ENS op [chars] failed for tag [chars] on class [chars] : [chars]
Explanation An ENS operation failed on the specified class
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-LIB_NAME-7-ENS_OP_ERROR [chars]: ENS op [chars] failed for tag [chars] on class [chars] : [chars]
Explanation An ENS operation failed on the specified class
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-LIB_NAME-7-INIT_ERROR [chars]: Initialization on [chars] failed on class [chars] : [chars]
Explanation An initialization error occured on the specified class
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-LIB_NAME-7-INIT_ERROR [chars]: Initialization on [chars] failed on class [chars] : [chars]
Explanation An initialization error occured on the specified class
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-LIB_NAME-7-NRS_OP_ERROR [chars]: NRS op [chars] failed for tag [chars] on class [chars] : [chars]
Explanation An NRS operation failed on the specified class
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-LIB_NAME-7-NRS_OP_ERROR [chars]: NRS op [chars] failed for tag [chars] on class [chars] : [chars]
Explanation An NRS operation failed on the specified class
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.
libpcmcia_ide Messages
Error Message%PLATFORM-libpcmcia_ide-1-CARD_UNAVAILABLE [chars]: Can not access flash device
Explanation Probably the flash card has been removed.
Recommended Action Reinsert the flash card.
Error Message%PLATFORM-libpcmcia_ide-5-CARD_SWAPPED [chars]: The flash card has been swapped (OIR)
Explanation The pcmcia flash card has been pulled out from its slot and re-inserted with a same or different card
Recommended Action No action is required.
libpcmcia_linux Messages
Error Message%PLATFORM-libpcmcia_linux-3-CHILD_SPAWN pcmciad child [chars] died. Being restarted
Explanation pcmciad spawns filesystem process and cardmgrd. One of them died and hence being restarted
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-libpcmcia_linux-3-FUNCTION_FAILED [chars]() failed: [chars]
Explanation The function specified 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-libpcmcia_linux-3-MALLOC_FAILED Malloc failed: [chars]
Explanation Low in 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-libpcmcia_linux-3-MOUNT_FAILED pcmciad failed to mount [chars]
Explanation pcmciad mounts DOS filesystem on ATA devices after DOS filesystem restart. mount failed during restart of DOS filesystem by pcmciad.
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-libpcmcia_linux-3-NO_SPAWN_PARAM pcmciad spawn of process [dec] failed, since no information available
Explanation pcmciad stores the pids of its children in /tmp. For some reason the file might have got corrupted
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-libpcmcia_linux-3-OPEN_FAILED Open of file [chars] failed: [chars]
Explanation Open of file 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-libpcmcia_linux-3-SLEEPON_LOCK_FAILED sleepon_lock failed: [chars]
Explanation deadlock 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-libpcmcia_linux-3-SPAWN_FAILED pcmciad spawn of process [chars] failed
Explanation pcmciad spawns filesystem process and cardmgrd. One of them died and its respawn 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.
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 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_NOW Delay time over, reloading now
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-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-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-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-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-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-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-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-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-3-WARNING [chars]
Explanation General error in software either in thread creation or in other parts.
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-INFO_CREATE_SUCCESS MBI-H: Success to create [chars]. Attempt number [dec]
Explanation Successful creation of LWM channel.
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-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-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.
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-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-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.
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-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-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 [dec], 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-2-API_CRITICAL mbus_api: [chars]
Explanation The mbus library encountered a critical error 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.
Error Message%PLATFORM-MBUS-3-API_DOWNLOAD_FAIL_STATUS mbus: download failed ([chars]).
Explanation Download status indicates failure.
Recommended Action Make sure MBUS agents are in RAM before downloading. Contact support if message persists.
Error Message%PLATFORM-MBUS-3-API_FILE_OPERATION_FAILED mbus: Failed to perform [chars] on file [chars].
Explanation File operation has failed on the specified file.
Recommended Action If this message repeats, report the failure to a service representative.
Error Message%PLATFORM-MBUS-3-API_FILTER_FAILED mbus: unable to set filter parameter
Explanation The filter operation for specifying type of message to read from the MBUS resmgr has failed.
Recommended Action Contact support.
Error Message%PLATFORM-MBUS-3-API_INVALID_SLOT mbus: invalid slot [dec].
Explanation Invalid slot is used as a parameter to a function.
Recommended Action Contact support.
Error Message%PLATFORM-MBUS-3-API_NULL_PARAMETER mbus: unexpected null pointer passed to function.
Explanation Invalid parameter used for a function.
Recommended Action Contact support.
Error Message%PLATFORM-MBUS-3-API_READ_TOKEN_INVALID mbus: register read token invalid.
Explanation The call to mbus_fetch_register function has provided a invalid token. Mbus_request_register should be called before calling mbus_fetch_register each time.
Recommended Action Contact support.
Error Message%PLATFORM-MBUS-3-API_SET_RATELIMIT_FAILED mbus: unable to set ratelimit.
Explanation Setting mbus tx ratelimit has failed.
Recommended Action Contact support.
Error Message%PLATFORM-MBUS-3-ATTACH_ERR [chars] ([hex])
Explanation For displaying attach error information.
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-3-MSG_CONNECT_ATTACH_FAILED mbus: call to ConnectAttach failed ([chars]).
Explanation Software failed to establish a connection between a process and a channel.
Recommended Action Contact support.
Error Message%PLATFORM-MBUS-3-MSG_CONNECT_ATTACH_FAILED mbus: call to ConnectAttach failed ([chars]).
Explanation Software failed to establish a connection between a process and a channel.
Recommended Action Contact support.
Error Message%PLATFORM-MBUS-3-MSG_CONNECT_ATTACH_FAILED mbus: call to ConnectAttach failed ([chars]).
Explanation Software failed to establish a connection between a process and a channel.
Recommended Action Contact support.
Error Message%PLATFORM-MBUS-3-MSG_EOF_UNEXPECTED mbus: EOF unexpected on file [chars].
Explanation Premature end of file encountered for specified file.
Recommended Action Contact support.
Error Message%PLATFORM-MBUS-3-MSG_EOF_UNEXPECTED mbus: EOF unexpected on file [chars].
Explanation Premature end of file encountered for specified file.
Recommended Action Contact support.
Error Message%PLATFORM-MBUS-3-MSG_EOF_UNEXPECTED mbus: EOF unexpected on file [chars].
Explanation Premature end of file encountered for specified file.
Recommended Action Contact support.
Error Message%PLATFORM-MBUS-3-MSG_FILE_OPERATION_FAILED mbus: Failed to perform [chars] on file [chars].
Explanation File operation has failed on the specified file.
Recommended Action If this message repeats, report the failure to a service representative.
Error Message%PLATFORM-MBUS-3-MSG_FILE_OPERATION_FAILED mbus: Failed to perform [chars] on file [chars].
Explanation File operation has failed on the specified file.
Recommended Action If this message repeats, report the failure to a service representative.
Error Message%PLATFORM-MBUS-3-MSG_FILE_OPERATION_FAILED mbus: Failed to perform [chars] on file [chars].
Explanation File operation has failed on the specified file.
Recommended Action If this message repeats, report the failure to a service representative.
Error Message%PLATFORM-MBUS-3-MSG_INVALID_STREAM mbus: invalid stream [dec].
Explanation Invalid stream is used as a parameter to a function.
Recommended Action Contact support.
Error Message%PLATFORM-MBUS-3-MSG_INVALID_STREAM mbus: invalid stream [dec].
Explanation Invalid stream is used as a parameter to a function.
Recommended Action Contact support.
Error Message%PLATFORM-MBUS-3-MSG_INVALID_STREAM mbus: invalid stream [dec].
Explanation Invalid stream is used as a parameter to a function.
Recommended Action Contact support.
Error Message%PLATFORM-MBUS-3-MSG_TIMER_CREATE_FAILED mbus: call to timer create failed ([chars]).
Explanation Software failed to create a timer for the specified purpose.
Recommended Action Contact support.
Error Message%PLATFORM-MBUS-3-MSG_TIMER_CREATE_FAILED mbus: call to timer create failed ([chars]).
Explanation Software failed to create a timer for the specified purpose.
Recommended Action Contact support.
Error Message%PLATFORM-MBUS-3-MSG_TIMER_CREATE_FAILED mbus: call to timer create failed ([chars]).
Explanation Software failed to create a timer for the specified purpose.
Recommended Action Contact support.
Error Message%PLATFORM-MBUS-3-SVC_AGENT_CHECK_FAILED mbus: local agent check failed ([chars]).
Explanation Unable to determine current state of local agent.
Recommended Action Make sure local MBUS agent is in RAM. If not contact support.
Error Message%PLATFORM-MBUS-3-SVC_CONNECT_ATTACH_FAILED mbus: call to ConnectAttach failed ([chars]).
Explanation Software failed to establish a connection between a process and a channel.
Recommended Action Contact support.
Error Message%PLATFORM-MBUS-3-SVC_EOF_UNEXPECTED mbus: EOF unexpected on file [chars].
Explanation Premature end of file encountered for specified file.
Recommended Action Contact support.
Error Message%PLATFORM-MBUS-3-SVC_FILE_OPERATION_FAILED mbus: Failed to perform [chars] on file [chars].
Explanation File operation has failed on the specified file.
Recommended Action If this message repeats, report the failure to a service representative.
Error Message%PLATFORM-MBUS-3-SVC_INVALID_STREAM mbus: invalid stream [dec].
Explanation Invalid stream is used as a parameter to a function.
Recommended Action Contact support.
Error Message%PLATFORM-MBUS-3-SVC_TIMER_CREATE_FAILED mbus: call to timer create failed ([chars]).
Explanation Software failed to create a timer for the specified purpose.
Recommended Action Contact support.
Error Message%PLATFORM-MBUS-4-API_WARNING mbus_api: [chars]
Explanation The mbus library encountered a warning condition.
Recommended Action No action is required.
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 Version of Mbus agent ROM on slot is not current.
Recommended Action Upgrade the rom agent on the slot. Use admin CLI command upgrade mbus.
Error Message%PLATFORM-MBUS-6-API_DEBUG [chars] ([hex])
Explanation For displaying mbus debugging information.
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-6-API_INFO_DUMP [chars]
Explanation For displaying mbus statistics or feedback information.
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-6-ATTACH_DEBUG [chars]
Explanation For displaying attach debugging information.
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-6-ATTACH_INFO_DUMP [chars]
Explanation For displaying attach statistics or feedback information.
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-6-MSG_DEBUG [chars] ([hex])
Explanation For displaying mbus debugging information.
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-6-MSG_DEBUG [chars] ([hex])
Explanation For displaying mbus debugging information.
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-6-MSG_DEBUG [chars] ([hex])
Explanation For displaying mbus debugging information.
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-6-MSG_INFO_DUMP [chars]
Explanation For displaying mbus statistics or feedback information.
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-6-MSG_INFO_DUMP [chars]
Explanation For displaying mbus statistics or feedback information.
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-6-MSG_INFO_DUMP [chars]
Explanation For displaying mbus statistics or feedback information.
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-6-SVC_DEBUG [chars] ([hex])
Explanation For displaying mbus debugging information.
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-6-SVC_INFO_DUMP [chars]
Explanation For displaying mbus statistics or feedback information.
Recommended Action No action is required.
NETIO_LC Messages
Error Message%PLATFORM-NETIO_LC-3-FAB [chars]: [chars]
Explanation An unexpected error has occurred.
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-NETIO_LC-3-FAB_ERR [chars]: [chars] (type [dec])
Explanation An unexpected error has occurred.
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-NETIO_LC-7-FAB_SEND [chars]: Transmitting Fabric packet (size=[dec])
Explanation debugging msg
Recommended Action NONE
OIRD Messages
Error Message%PLATFORM-OIRD-3-ASYNC_ATTACH_FAIL Failed to attach handler for async events: [chars]
Explanation Failed to attach handler for async events.
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-OIRD-3-EVM_CREATE_FAIL Failed to create event manager: [chars]
Explanation Failed to create event manager.
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-OIRD-3-MMAP_FAIL Failed to map OIR registers to process space
Explanation Failed to mmap OIR 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-OIRD-3-MSG_ATTACH_FAIL Failed to attach handler for sync events: [chars]
Explanation Failed to attach handler for sync events.
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-OIRD-3-MSG_CHAN_CONN_FAIL Failed to connect to message channel: [chars]
Explanation Failed to attach handler for sync 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-OIRD-3-THREAD_CREATE_FAIL Failed to create thread [chars]
Explanation Failed to create threads.
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-OIRD-3-TIMER_CREATE_FAIL Failed to create timer: [chars]
Explanation Failed to create timer.
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-OIRD-3-TIMER_INIT_FAIL Failed to init timer events: [chars]
Explanation Failed to init timer events.
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-OIRD-4-ASYNC_MSG_ERROR Received unexpected async error message of code: [dec]
Explanation Received unexpected async error message code.
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-OIRD-4-CHKPT_FAIL Failed to perform checkpoint services: [chars]
Explanation Failed to perform checkpoint service functions.
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-OIRD-4-MSG_ERROR Received unexpected message of code: [dec]
Explanation Received unexpected 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.=
Error Message%PLATFORM-OIRD-4-UNEXPECTED Unexpected: [chars]: [chars]: [hex]
Explanation An unexpected condition encountered. This is not necessarily an error, but may help with debugging other problems elsewhere!
Recommended Action Collect system log information. No action is required.
Error Message%PLATFORM-OIRD-5-OIRIN OIR: Node [chars] inserted
Explanation Detected a card is inserted into 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-OIRD-5-OIROUT OIR: Node [chars] removed
Explanation Detected a card 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.
PCIMGR Messages
Error Message%PLATFORM-PCIMGR-3-MUTEX_LOCK_ERROR [chars]() line[dec]: pci bus manager mutex lock error
Explanation The mutex lock for accessing register returned 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-PCIMGR-3-MUTEX_UNLOCK_ERROR [chars]() line[dec]: pci bus manager mutex unlock error
Explanation The mutex unlock for register operation returned 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-PCIMGR-3-REG_PM_ERROR [chars]() line[dec]: pci bus manager failed register to platform mgr
Explanation The function call to pm_fault_register_device returned fail
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.
PCMCIA Messages
Error Message%PLATFORM-PCMCIA-3-MEM_MAP_ERROR [chars]() line[dec]: pcmcia driver failed mapping io/mem addr space
Explanation mem/io mapping form pcmcia driver 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-PCMCIA-3-PCI_DEV_ATTACH_ERROR [chars]() line[dec]: pcmcia driver failed attach to pci device
Explanation can not get pci device info from PCI bus mgr
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-PCMCIA-3-PCI_SVR_ATTACH_ERROR [chars]() line[dec]: Can't locate PCI server
Explanation PCMCIA driver can not attach to PCI bus mgr
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-PCMCIA-3-REG_PM_ERROR [chars]() line[dec]: pcmcia driver failed regist to platform mgr
Explanation The function call to pm_fault_register_device returned fail
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.
PCMCIAD Messages
Error Message%PLATFORM-PCMCIAD-3-FUNCTION_FAILED [chars]() failed: [chars]
Explanation The function specified 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-PCMCIAD-3-KILL_FAILED kill to pid [dec] failed: [chars]
Explanation Probably the process being killed has already 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-PCMCIAD-3-MSGSEND_FAILED MsgSendPulse operation failed: [chars]
Explanation Failed to send pulse to resmgr thread to handle SIGCHLD
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-PCMCIAD-3-RESTART Pcmciad died and has come back up. Killing its old children
Explanation pcmciad died and had come back up. It is killing children spawned by old pcmciad so that it can respawn new ones.
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-PCMCIAD-3-SIGNAL_OP_FAILED Signal operation [chars] failed: [chars]
Explanation Singal masking or handler installation 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-PCMCIAD-3-UNLINK_FAILED unlink of file [chars] failed: [chars]
Explanation Should not happen.
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.
PCTL Messages
Error Message%PLATFORM-PCTL-3-gsp_msg_failed Failure in [chars] at Line [dec]. Function [chars] returned Error [chars]
Explanation The internal communication channel among pctl threads is broken.
Recommended Action Must restart the process.
PLATFORM_HFR_LIB Messages
Error Message%PLATFORM-PLATFORM_HFR_LIB-3-AM_I_SC_ERROR [chars]: [chars]
Explanation Failure occured as indicated 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.
PLATFORM_RP Messages
Error Message%PLATFORM-PLATFORM_RP-0-CRASH GRP-B Rebooting Now - Replace your broken RP DRAM!
Explanation Broken DRAM
Recommended Action Try changing the DRAM to a known working one. If that doesn't work, then it is a software problem which requires a DDTS
Error Message%PLATFORM-PLATFORM_RP-0-MBE_RMW GRP-B DRAM ECC Fatal Memory Error: MBE_RMW Addr=[hex], TSR=[hex], EER=[hex]
Explanation GRP-B DRAM ECC Fatal Memory Error: MBE_RMW.
Recommended Action Try changing the DRAM to a known working one. If that doesn't work, then it is a software problem which requires a DDTS
Error Message%PLATFORM-PLATFORM_RP-0-SBE_NON_FATAL GRP-B DRAM ECC Non-Fatal Memory Error: SBE Addr=[hex], TSR=[hex], EER=[hex], synd=[hex]
Explanation GRP-B DRAM ECC Non-Fatal Memory Error: Single Bit Error.
Recommended Action Try changing the DRAM to a known working one. If that doesn't work, then it is a software problem which requires a DDTS
Error Message%PLATFORM-PLATFORM_RP-0-SBE_RMW_FATAL GRP-B DRAM ECC Fatal Memory Error: SBE_RMW on Tiger Rev 4, Addr=[hex], TSR=[hex], EER=[hex], synd=[hex]
Explanation GRP-B DRAM ECC Fatal Memory Error: SBE_RMW .
Recommended Action Try changing the DRAM to a known working one. If that doesn't work, then it is a software problem which requires a DDTS
Error Message%PLATFORM-PLATFORM_RP-0-SBE_RMW_NONFATAL GRP-B DRAM ECC Non-Fatal Memory Error: SBE_RMW Addr=[hex], TSR=[hex], EER=[hex], synd=[hex]
Explanation GRP-B DRAM ECC Non-Fatal Memory Error: SBE_RMW.
Recommended Action Try changing the DRAM to a known working one. If that doesn't work, then it is a software problem which requires a DDTS
Error Message%PLATFORM-PLATFORM_RP-0-WPE GRP-B DRAM ECC Fatal Memory Error: WPE Addr=[hex], TSR=[hex], EER=[hex], WPEIR=[hex]
Explanation GRP-B DRAM ECC Fatal Memory Error: Write Parity Error.
Recommended Action Try changing the DRAM to a known working one. If that doesn't work, then it is a software problem which requires a DDTS
Error Message%PLATFORM-PLATFORM_RP-3-child_init [chars]: child: [chars]
Explanation Errors during the driver normal initialization
Recommended Action Software problem which requires a DDTS
Error Message%PLATFORM-PLATFORM_RP-3-CSAR_ECM [chars]
Explanation none
Recommended Action Software problem which requires a DDTS
Error Message%PLATFORM-PLATFORM_RP-3-CSAR_HW_ERR [chars]. Error = [chars]
Explanation csar hw error
Recommended Action Software problem which requires a DDTS
Error Message%PLATFORM-PLATFORM_RP-3-DIEP_SVC_INIT_ERR [chars] [chars]: service=[dec] service_status=[dec]
Explanation Errors during the initialization of deferent services
Recommended Action Software problem which requires a DDTS
Error Message%PLATFORM-PLATFORM_RP-3-FIA_DEVCTL_ERR Unsupported devctl case [dec]
Explanation An unexpected error has occurred.
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_RP-3-FIA_MEM_CHIP_ERR ([chars]): no memory for chip data.
Explanation An unexpected error has occurred.
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_RP-3-FIA_MEM_ERROR ([chars]): FIA failed to initialize memory. Exiting
Explanation An unexpected error has occurred.
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_RP-3-FIA_MMAP_ERROR ([chars]): FIA memory mapping failed. Exiting
Explanation An unexpected error has occurred.
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_RP-3-FIA_SYNC_ERROR ([chars]): FIA failed to sync, los_status [hex], los_error [hex], fia_config [hex]
Explanation This error usually indicates an internal hardware problem on the card.
Recommended Action If there are other error reports about the switch fabric (CSC/SFC) then wait several minutes for corrective action. Otherwise, run diagnostics for slot reporting error. Use 'diag verbose' command. (This command may not work for the slot containing the primary route processor.) 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-PLATFORM_RP-3-HW_DR_MMAP_FAILED [chars] h/w driver cannot do memory map
Explanation An unexpected error has occurred.
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_RP-3-LOW_CPU_MEM slot [dec]: [dec]M present, need [dec]M, RP CPU memory upgrade required
Explanation For indicating insufficient RP CPU (ie. dram) memory
Recommended Action Upgrade the CPU (dram) memory on the RP.
Error Message%PLATFORM-PLATFORM_RP-3-NETIO_FAIL [chars]: dpc failure ( status : [dec] )
Explanation An unexpected error has occurred.
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_RP-3-NO_MUTEX Cannot get netio mutex
Explanation An unexpected error has occurred.
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_RP-3-NORMAL_INIT [chars]: [chars]
Explanation none
Recommended Action Software problem which requires a DDTS
Error Message%PLATFORM-PLATFORM_RP-3-NORMAL_INIT_ERR [chars] [chars]
Explanation Errors during the driver normal initialization
Recommended Action Software problem which requires a DDTS
Error Message%PLATFORM-PLATFORM_RP-3-PARTNER_INIT [chars]: [chars]
Explanation none
Recommended Action Software problem which requires a DDTS
Error Message%PLATFORM-PLATFORM_RP-3-RESET_DATAPATH [chars]: [dec]
Explanation Errors during the driver normal initialization
Recommended Action Software problem which requires a DDTS
Error Message%PLATFORM-PLATFORM_RP-7-DRP_PARTNER_HELPER [chars]
Explanation Debugging message for drp_partner_helper
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_RP-7-FIA_NOT_RESET FIA was not reset before programming
Explanation An unexpected error has occurred.
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_RP-7-PARTNER_DEBUG [chars]
Explanation Debugging code
Recommended Action none
PLU Messages
Error Message%PLATFORM-PLU-4-ERR_CORRECTED Hardware Table [dec] consistency restored
Explanation Errors have been corrected.
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-PLU-4-ERR_NOTIFY Hardware Table [dec] may be inconsistent ([hex]). Attempting correction every [dec] seconds
Explanation Errors were encountered trying to program hardware tables, forwarding on some entries may be affected, periodic error correction will be attempted.
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.
PRP_HW Messages
Error Message%PLATFORM-PRP_HW-3-BEETLE_DOWNLOAD Beetle : Beetle download procedure fails
Explanation Beetle download procedure fails
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-PRP_HW-3-BEETLE_MAP Beetle : Beetle FPGA not accessible
Explanation It's not possible to map Beetle region.
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-PRP_HW-3-BOARD_TYPE [chars] : board type not defined
Explanation It's impossible to recognize the board type.
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-PRP_HW-3-TURTLE_MAP Turtle : Turtle FPGA not accessible
Explanation It's not possible to map Turtle region.
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.
REEP Messages
Error Message%PLATFORM-REEP-3-ERROR_OPENING_ETHERNET_CONNECTION Failed to open connection to control ethernet server. Err = [dec]
Explanation The control ethernet transport connection has been lost due to which send/recv for this process over the control ethernet will not work. This impacts stby RP booting.
Recommended Action If this message is seen persistently, please contact Cisco support.
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 Gather all the logs and contact Cisco support.
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 logs and contact Cisco support.
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 contact Cisco support.
Error Message%PLATFORM-REEP-3-REPLY_SEND_FAILED Failed to send reply. Err = [dec]
Explanation Failed to send reply to client ROMMON.
Recommended Action Transient occurence of this message is possible. If this message is seen persistently, and either an MSC, DRP or stby RP is not booting, its because the control network connectivity service on this node is malfunctioning. Please contact Cisco support. ios_msg_reep_error_opening_ethernet_connection(rc);
ROM_UPGRADE_LIB Messages
Error Message%PLATFORM-ROM_UPGRADE_LIB-3-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.'
Error Message%PLATFORM-ROM_UPGRADE_LIB-6-INFO [chars]
Explanation Just more information.
Recommended Action 'No action is required.'
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..
SCC Messages
Error Message%PLATFORM-SCC-2-BAD_ID_HW Failed Identification Test in [chars] [[dec]/[dec]]
The module in [chars] in this router may not be a genuine Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco SPA cards or other modules into a Cisco product is the cause of a support issue, Cisco may deny support under your warranty or under a Cisco support program such as SmartNet.
Explanation 'Hardware in the specified location could not be identified as a genuine Cisco product'
Recommended Action 'Contact TAC'
Error Message%PLATFORM-SCC-2-FAILED_ID_HW Failed Identification Test in [chars] [[dec]/[dec]]
Explanation 'There was a problem while identifying Hardware in the specified location.'
Recommended Action 'Contact TAC'
Error Message%PLATFORM-SCC-2-PROTO_HW Module ([chars]) is a registered proto-type for Cisco Lab use only, and not certified for live network operation.
Explanation 'Hardware in the specified location is a proto-type module that came from a Cisco Lab'
Recommended Action 'Contact TAC'
SHELFMGR Messages
Error Message%PLATFORM-SHELFMGR-2-CHASSIS_SHUTDOWN CHASSIS SHUTDOWN INITIATED due to [chars]
Explanation Chassis is shutting down due to reason mentioned.
Recommended Action Examine chassis based on above msg.
Error Message%PLATFORM-SHELFMGR-3-ASYNC_ATTACH_EVENT Failed to attach handler for async events: [chars]
Explanation Failed to attach handler for async events.
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-CCTL_FAIL Failed to get rack type when calling cctl lib [chars] (errcode:[dec])
Explanation *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-SHELFMGR-3-CHKPT_FAIL Fail to initialize checkpoint
Explanation *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-SHELFMGR-3-COMM_FAIL [chars] can not send messages to [chars] channel, restarts
Explanation The internal communication channel among pctl threads is broken.
Recommended Action Must restart the process.
Error Message%PLATFORM-SHELFMGR-3-CONNECTION_FAIL [chars] can not make connections to [chars] channel, restarts
Explanation The internal communication channel among pctl threads is broken.
Recommended Action Must restart the process.
Error Message%PLATFORM-SHELFMGR-3-ENS_PRODUCER_INIT_FAIL ENS/NRS producer initialization error (return code [dec]), shelfmgr is unable to proceed due to unavailable infra services, keep retrying ...
Explanation *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-SHELFMGR-3-ENS_PRODUCER_INIT_OK ENS producer initialization OK after retry
Explanation *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-SHELFMGR-3-ENS_WRITE_ERROR Can't update inventory for node ([chars]) state changes due to ENS notification write error (errcode [dec])
Explanation *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-SHELFMGR-3-ENSNRS_ERROR ENS/NRS call [chars] returns error (errorcode [dec]), retrying ...
Explanation *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-SHELFMGR-3-EVM_CREATE_FAIL Failed to create event manager
Explanation Failed to create event manager.
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-FAILED_LOAD Node [chars] fails to load HFROS, request to reset ...
Explanation *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-SHELFMGR-3-FAILEDPOWERUP Unable to power up slot [chars] (error code [dec]), request to reset ...
Explanation *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-SHELFMGR-3-FAILEDSPAWN shelfmgr_partner failed to spawn top_procs dumping scripts at [dec] ([chars])
Explanation *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-SHELFMGR-3-FSMTIMEOUT_RESET Node [chars] is reset due to failed bootup
Explanation *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-SHELFMGR-3-INRESET_ALARM Power off node [chars] due to multiple critial alarms, putting into IN_RESET state
Explanation *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-SHELFMGR-3-INRESET_BRINGDOWN Cannot boot node [chars] due to multiple resets, putting into IN_RESET state
Explanation *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-SHELFMGR-3-INRESET_FAILEDBOOT Cannot boot node [chars] due to multiple boot retries, putting into IN_RESET state
Explanation *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-SHELFMGR-3-INRESET_MBIBOOT Cannot boot node [chars] due to failure in mbi loading, putting into IN_RESET state
Explanation *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-SHELFMGR-3-NO_PLIM Can not power on node [chars] due to absence of PLIM
Explanation *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-SHELFMGR-3-NODE_NORESET Node [chars] is in NMON state, Cancel reset request
Explanation *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-SHELFMGR-3-NODE_RESET_ALARM Node [chars] in critical alarms, request to reset ...
Explanation *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-SHELFMGR-3-NODE_RESET_BRINGDOWN Reset node [chars] due to heartbeat loss
Explanation *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-SHELFMGR-3-NOREASON_RESET Node [chars] is reset due to UNKNOWN reason
Explanation *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-SHELFMGR-3-OIR_SAVE Failed to save configuration following OIR - error: [chars]
Explanation Not able to save configuration for this node.
Recommended Action Examine chassis based on above msg.
Error Message%PLATFORM-SHELFMGR-3-OIR_TIMEOUT No Response received from configuration manager server.
Explanation No response received from configuration manager server.
Recommended Action None.
Error Message%PLATFORM-SHELFMGR-3-OIRIN OIR: Node [chars] inserted
Explanation *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-SHELFMGR-3-OIROUT OIR: Node [chars] Removed
Explanation *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-SHELFMGR-3-PCB_ALLOCATION_FAIL No free [chars] control block available, restarts
Explanation The pre-allocated control blocks are run out.
Recommended Action Must restart the process.
Error Message%PLATFORM-SHELFMGR-3-POWERDOWN_RESET Node [chars] is powered off due to admin power off request
Explanation *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-SHELFMGR-3-POWERRELOAD_RESET Node [chars] is reset through power off, then power on
Explanation *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-SHELFMGR-3-POWERUP Power up node [chars]
Explanation *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-SHELFMGR-3-QNET_WRITE_ERROR Error while trying to update QNET about node ([chars]) down notification (errcode [dec])
Explanation *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-SHELFMGR-3-RP_SHUTDOWN RP SHUTDOWN INITIATED due to thermal alarms
Explanation RP is shutting down due to reason mentioned.
Recommended Action If standby RP present, nothing to be done - failover should have happened. Else, chassis will be brought down. Needs to be rebooted.
Error Message%PLATFORM-SHELFMGR-3-SET_PRIORITY_ERROR Can not set sender's priority
Explanation *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-SHELFMGR-3-SHUTDOWN Node [chars] is shutdown due to critical alarm
Explanation A critical thermal alarm has caused shutdown of the board.
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 *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-SHELFMGR-3-THREAD_CREATE_FAIL Failed to create [chars] thread
Explanation Failed to create threads.
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] contain invalid boardtype, This board is shutdown for debug
Explanation *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-SHELFMGR-3-USER_RESET Node [chars] is reset due to user reload request
Explanation *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-SHELFMGR-3-WRONG_PLATFORM The shelf manager has to run in the active SC/RP
Explanation *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.
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.'
SPWD Messages
Error Message%PLATFORM-SPWD-0-ECC_REBOOT Excessive [chars] errors in last hour: [dec]. Node reboot scheduled
Explanation Large numbers of single or mulitple bit ECC errors have been detected on the sp node in the past hour. The node will be rebooted.
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-SPWD-0-MACHINE_CHECK_REBOOT Excessive machine checks in last hour: [dec]. Node reboot scheduled
Explanation The sp cpu has received an excessive number of machine check exceptions. The node will be rebooted.
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-SPWD-0-MISSED_WATCHDOG_REBOOT Multiple watchdog misses in last hour: [dec]. Node reboot scheduled
Explanation The sp cpu has failed to service the hardware watchdog timer multiple times in the last hour. The node will be rebooted.
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-SPWD-4-MACHINE_CHECK Current counts: machine checks: [dec], single bit ECC [dec], multibit ECC [dec], missed watchdogs: [dec]. Cumulative counts: machine checks: [dec], single bit ECC [dec], multibit ECC: [dec], watchdogs: [dec]
Explanation The sp cpu has received a machine check exception. This can be due because the software has failed to service the watchdog timer, or because of excessive ECC errors.
Recommended Action Examine the error counts for indications as to the cause of the machine check. Excessive machine checks will cause the sp to reset.
Error Message%PLATFORM-SPWD-6-HOURLY_COUNTS Hourly summary of watchdog counts: watchdog misses: [dec], single bit ECC errors: [dec], multiple bit ECC errors: [dec], machine check count: [dec].
Explanation If the watchdog process detects a missed watchdog, single or multiple bit ecc error, or a machine check exception in the last hour, this message and a summary of error counts is printed.
Recommended Action Contact support if this message is seen more than once a day.
SQUID_LOADER Messages
Error Message%PLATFORM-SQUID_LOADER-5-progress [chars] [chars]
Explanation Output progress to RP console.
Recommended Action No action is required..
SYSLDR_LC Messages
Error Message%PLATFORM-SYSLDR_LC-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-SYSLDR_LC-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-SYSLDR_LC-2-NODE_RELOAD_NOW Delay time over, reloading now
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-SYSLDR_LC-3-MSG_SEND_FAIL msg_send failed to server : [chars]
Explanation msg_send() call 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-SYSLDR_LC-3-SERVER_CONNECT_FAIL Failed to connect to server : [chars]
Explanation Failed to connect to a server.
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_LC-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-SYSLDR_LC-4-WARNING [chars]
Explanation For displaying sysldr lc debugging information.
Recommended Action No action is required.
SYSLDR_RP Messages
Error Message%PLATFORM-SYSLDR_RP-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-SYSLDR_RP-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-SYSLDR_RP-2-NODE_RELOAD_NOW Delay time over, reloading now
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-SYSLDR_RP-3-MSG_SEND_FAIL msg_send failed to server : [chars]
Explanation msg_send() call 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-SYSLDR_RP-3-SERVER_CONNECT_FAIL Failed to connect to server : [chars]
Explanation Failed to connect to a server.
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_RP-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-SYSLDR_RP-4-WARNING [chars]
Explanation Unexpected low severity problem.
Recommended Action No action is required.
SYSLDR Messages
Error Message%PLATFORM-SYSLDR-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-SYSLDR-2-FATAL2 [chars], error=[dec]
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-SYSLDR-3-ALLOC_FAILED Insufficient memory.
Explanation Unable to allocate more heap memory.
Recommended Action No action is required.
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-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 '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-3-DEBUG_REGISTER_FAILED [chars]: debug_register() failed error [chars]
Explanation Failed to register debug events on sysldr server side.
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-3-DRP_MBUS slot [dec]: DRP mbus not responding, reloading
Explanation For displaying notification of DRP software non-responsiveness.
Recommended Action This indicates a problem in mbus comms, and tech support should be contacted. A user can try 'hardware-module ' once to retry reconnection of the DRP.
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-ERR slot[dec]: [chars]
Explanation sysldr encountered an error 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.
Error Message%PLATFORM-SYSLDR-3-ERROR slot[dec]: [chars], errno=[dec]
Explanation For displaying sysldr debugging information with an errno.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-3-FIELD_DIAG_ERROR slot=[dec], [chars]: [chars]
Explanation Field diag. image download errors.
Recommended Action No action is required.
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-INTERNAL_ERROR Internal Error. File [chars], line [dec]: [chars].
Explanation Serious internal logic or data 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-SYSLDR-3-LC_UNUSABLE LC in slot [dec] in unusable state
Explanation For displaying health and readiness of LC
Recommended Action Ensure that the LC configuration is correct and active.
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 ' once to retry loading of the LC.
Error Message%PLATFORM-SYSLDR-3-MBI_MBUS slot [dec]: MBI mbus not responding, reloading
Explanation For displaying notification of MBI software non-responsiveness.
Recommended Action This indicates a problem in mbus comms, and tech support should be contacted. A user can try 'hardware-module ' once to retry reconnection of the card.
Error Message%PLATFORM-SYSLDR-3-MBI_NETWORK_DOWN slot [dec]: network connection to MBI down, reloading
Explanation For displaying notification of network non-responsiveness (to MBI).
Recommended Action This indicates a problem in qnet comms, and tech support should be contacted. A user can try 'hardware-module ' once to retry loading of the card.
Error Message%PLATFORM-SYSLDR-3-MBI_NOLOAD slot [dec]: MBI cannot load IOX, retrying
Explanation For displaying notification of inability of MBI to boot a node's full image.
Recommended Action This indicates a problem in comms or installation. Tech support should be contacted. Several attempts will be made to retry the image loading, and then we give up.
Error Message%PLATFORM-SYSLDR-3-MBUS_PING_WARN slot [dec]: mbus not responding, 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 mbus comms, and tech support should be contacted.
Error Message%PLATFORM-SYSLDR-3-NETWORK_DOWN slot [dec]: network connection down, reloading
Explanation For displaying notification of card network non-responsiveness.
Recommended Action This indicates a problem in qnet comms, and tech support should be contacted. A user can try 'hardware-module ' once to retry loading of the card.
Error Message%PLATFORM-SYSLDR-3-NETWORK_DOWN_WARN slot [dec]: network connection down, please investigate the cause
Explanation For displaying notification of card network non-responsiveness. The card is not reloaded because of 'service sysldr fabric-ping warn' configuration.
Recommended Action This indicates a problem in qnet comms, and tech support should be contacted.
Error Message%PLATFORM-SYSLDR-3-NOT_RESPONDING slot [dec]: LC mbus not responding, reloading
Explanation For displaying notification of LC software non-responsiveness.
Recommended Action This indicates a problem in mbus comms, and tech support should be contacted. A user can try 'hardware-module ' once to retry loading of the LC.
Error Message%PLATFORM-SYSLDR-3-RP_MBUS slot [dec]: RP mbus not responding, reloading
Explanation For displaying notification of RP software non-responsiveness.
Recommended Action This indicates a problem in mbus comms, and tech support should be contacted. A user can try 'hardware-module ' once to retry reconnection of the RP.
Error Message%PLATFORM-SYSLDR-3-SCFG_SLOW slot [dec]: cfgmgr took too long, continuing
Explanation An unacceptable error from cfgmgr; it has taken 2 mins. to save one LC cfg.
Recommended Action Ensure that the system is still usable, and that the LC config is intact.
Error Message%PLATFORM-SYSLDR-3-SELF_PING_FAILURE slot [dec]: self ping failure, failover and reloading
Explanation For displaying notification of the self fabric ping failure
Recommended Action This indicates a problem in self fabric ping, and tech support should be contacted.
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-SYSDB_CONNECTION_FAIL Connection to sysdb path '[chars]' failed: '[chars]'.
Explanation Unable to maintain connection to a critical sysdb path.
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-3-SYSDB_DELETE slot [dec]: sysdb_item_delete failed for item '[chars]' in file=[chars], line=[dec] ([chars] [hex])
Explanation Unable to delete a sysdb item.
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-3-SYSDB_GET slot [dec]: sysdb_item_get failed for item '[chars]' in file=[chars], line=[dec] ([chars] [hex])
Explanation Unable to set a sysdb item.
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-3-SYSDB_NOTIFY_FAIL 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 '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-3-SYSDB_SET slot [dec]: sysdb_item_set failed for item '[chars]' in file=[chars], line=[dec] ([chars] [hex])
Explanation Unable to set a sysdb item.
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-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=[dec] mod=[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-4-DOWN_REV slot [dec]: [chars] is down-rev (V[dec].[dec]), consult technical support. [chars]
Explanation For displaying down-rev notification.
Recommended Action tech support should be contacted for upgrade instructions
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-SCFG_WARN slot [dec]: cfgmgr being slow to save config
Explanation An early warning that cfgmgr is taking over a minute to save an LC config.
Recommended Action Log as a warning, look for the following message.
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 ' once to retry loading of the 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-4-WARNING slot[dec]: [chars]
Explanation For displaying sysldr debugging information.
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 For displaying health and readiness of DRP
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 For displaying LC join notification.
Recommended Action Ensure that the *sysldr* restart was expected.
Error Message%PLATFORM-SYSLDR-5-LC_DISABLED LC in slot [dec] is now disabled
Explanation For displaying health and readiness of LC
Recommended Action Ensure that the disabling of this LC 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 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-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-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]
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 For displaying health and readiness of RP
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-DEBUG slot[dec]: [chars]
Explanation For displaying 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.
TFQ Messages
Error Message%PLATFORM-TFQ-3-BAD_ALIGN TFQ: bad memory alignment on ptr [hex] of bytes [dec]
Explanation TFQ encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-TFQ-3-BUFHDR_INVALID Buffer header invalid, length [unsigned int] start offset [unsigned int]
Explanation This message indicates that a packet was attempted to be sent over the fabric but the buffer header was invalid. This usually indicates a 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-TFQ-3-DESCQ_FULL Chopper desc queue [dec] full - pri [unsigned int] enq [unsigned int] deq [unsigned int] blog [unsigned int] mask [hex]
Explanation This message indicates that too many messages are being sent to the chopper. There is no more room in the chopper descriptor queue to send new packets. This is a temporary condition that should get cleared or the FIA registers on both PRP and LC need investigation.
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-TFQ-3-FATAL tfq: fatal error encountered, reason=[chars]
Explanation tfq 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-TFQ-3-FATAL_2 tfq: fatal error encountered, reason=[chars], Error: [dec], Function: [chars]
Explanation tfq 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-TFQ-3-GEN_INFO tfq: general information,
Explanation The TFQ's informational 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.
Error Message%PLATFORM-TFQ-3-INFO tfq: service degrading error, reason = [chars]
Explanation The tfq encountered an error that would lead to degraded service.
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-TFQ-3-MALLOC_DESC_FAILED TFQ: slot [dec] alloc [dec] bytes error on ptr [hex] of max [hex]
Explanation TFQ encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-TFQ-3-MALLOC_FAILED TFQ: memory alloc [dec] bytes error on ptr [hex] of max [hex]
Explanation TFQ encountered a fatal memory allocation error
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
Error Message%PLATFORM-TFQ-3-MEM_ERR No memory available for Chopper queues in [chars]
Explanation This message indicates that Chopper driver is not able to allocate memory for the Queues and other use. This usually indicates a memory problem.
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-TFQ-3-MSGTOOBIG Particle size too large [unsigned int]
Explanation This message indicates that a packet was attempted to be sent over the fabric but was too large to be sent. This usually indicates a 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-TFQ-3-NODEID_INVALID Node Id invalid, rc:[dec] node:[hex] stream:[dec] paktype:[dec]
Explanation This message indicates that a packet was attempted to be sent over the fabric but the node id was invalid. This usually indicates a 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-TFQ-3-NOT_YET_IMPLEMENTED tfq: this function is not yet implemented
Explanation TFQ, a function was not implemented.
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-TFQ-3-PAK_DUPLICATE_ERR Failed to duplicate packet sent to the chopper old:[hex] new:[hex] loc:[dec]
Explanation This message indicates that there was failure in the case where the Chopper driver had to duplicate a packet.
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-TFQ-3-PAK_INVALID Invalid packet sent to the chopper [hex]
Explanation This message indicates that an invalid packet was sent to the Chopper driver.
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-TFQ-3-PAK_LEGACY TFQ: packet type [dec]
Explanation TFQ is using a legacy packet type
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-TFQ-3-USAGE tfq: invalid option passed to tfq server
Explanation Startup option supplied to TFQ is not valid.
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.
TIMESYNC Messages
Error Message%PLATFORM-TIMESYNC-3-CANT_GET_LRD_INFO failed to get owner LR information from LRD, still trying...errno=[dec] ([chars])
Explanation Logical Router Daemon is not able to tell us which RP is the dSC. We need to know, because timesync server should only run on the dSC.
Recommended Action If this message is received on every boot, report the failure to support.
Error Message%PLATFORM-TIMESYNC-3-CANT_GET_PSARB_STATE (node [hex]): unable to get PSARB state, errno [dec] ([chars])
Explanation Unable to detect PSARB state, PSARB module failure?
Recommended Action Contact support.
Error Message%PLATFORM-TIMESYNC-3-CANT_GET_PSARB_STATE (node [hex]): unable to get PSARB state, errno [dec] ([chars])
Explanation Unable to detect PSARB state, PSARB module failure?
Recommended Action Contact support.
Error Message%PLATFORM-TIMESYNC-3-CANT_GET_TIME (node [hex]): failed to get system time, errno [dec] ([chars])
Explanation An attempt to read the system time has failed.
Recommended Action If this message repeats, report the failure to a service representative.
Error Message%PLATFORM-TIMESYNC-3-CANT_GET_TIME (node [hex]): failed to get system time, errno [dec] ([chars])
Explanation An attempt to read the system time has failed.
Recommended Action If this message repeats, report the failure to a service representative.
Error Message%PLATFORM-TIMESYNC-3-CANT_GET_TIME_ZONE (node [hex]): failed to get system time zone, errno [dec] ([chars])
Explanation An attempt to read the system timezone has failed.
Recommended Action If this message repeats, report the failure to a service representative.
Error Message%PLATFORM-TIMESYNC-3-CANT_GET_TIME_ZONE (node [hex]): failed to get time zone, errno [dec] ([chars])
Explanation An attempt to read the time zone string has failed.
Recommended Action If this message repeats, report the failure to a service representative.
Error Message%PLATFORM-TIMESYNC-3-CANT_MBUS_READV (node [hex]): failed to mbus_readv, errno [dec] ([chars])
Explanation A failure was encountered when receiving a message from the MBUS driver.
Recommended Action If this error persists, then there is (most likely) a hardware problem with the MBUS; contact a service representative.
Error Message%PLATFORM-TIMESYNC-3-CANT_MBUS_READV (node [hex]): failed to mbus_readv, errno [dec] ([chars])
Explanation A failure was encountered when receiving a message from the MBUS driver.
Recommended Action If this error persists, then there is (most likely) a hardware problem with the MBUS; contact a service representative.
Error Message%PLATFORM-TIMESYNC-3-CANT_MBUS_WRITEV (node [hex]): failed to mbus_writev, errno [dec] ([chars])
Explanation A failure was encountered when sending a message to the MBUS driver.
Recommended Action If this error persists, then there is (most likely) a hardware problem with the MBUS; contact a service representative.
Error Message%PLATFORM-TIMESYNC-3-CANT_MBUS_WRITEV (node [hex]): failed to mbus_writev, errno [dec] ([chars])
Explanation A failure was encountered when sending a message to the MBUS driver.
Recommended Action If this error persists, then there is (most likely) a hardware problem with the MBUS; contact a service representative.
Error Message%PLATFORM-TIMESYNC-3-CANT_OPEN_PSARB (node [hex]): failed to open PSARB, errno [dec] ([chars])
Explanation The PSARB module isn't available at this point.
Recommended Action If this message repeats, report the failure to a service representative.
Error Message%PLATFORM-TIMESYNC-3-CANT_OPEN_PSARB (node [hex]): failed to open PSARB, errno [dec] ([chars])
Explanation The PSARB module isn't available at this point.
Recommended Action If this message repeats, report the failure to a service representative.
Error Message%PLATFORM-TIMESYNC-3-CANT_SET_TIME (node [hex]): failed to set system time, errno [dec] ([chars])
Explanation An attempt to set the system time has failed.
Recommended Action If this message repeats, report the failure to a service representative.
Error Message%PLATFORM-TIMESYNC-3-CANT_SET_TIME (node [hex]): failed to set system time, errno [dec] ([chars])
Explanation An attempt to set the system time has failed.
Recommended Action If this message repeats, report the failure to a service representative.
Error Message%PLATFORM-TIMESYNC-3-INVALID_MSG (node [hex]): invalid msg [hex]
Explanation A message was received from the MBUS that had the TIMESYNC message ID in it, but with an unknown sub-command.
Recommended Action Software version mismatch, or possible hardware fault on the MBUS, contact service representative.
Error Message%PLATFORM-TIMESYNC-3-INVALID_MSG (node [hex]): invalid msg [hex]
Explanation A message was received from the MBUS that had the TIMESYNC message ID in it, but with an unknown sub-command.
Recommended Action Software version mismatch, or possible hardware fault on the MBUS, contact service representative.
Error Message%PLATFORM-TIMESYNC-3-THREAD_CREATE_ERROR (node [hex]): failed to get create thread, errno [dec] ([chars])
Explanation An attempt to create time zone thread has failed
Recommended Action If this message repeats, report the failure to a service representative.
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-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-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.
UPGRADE Messages
Error Message%PLATFORM-UPGRADE-3-BUF_READ Failed to read file [chars]
Explanation The read() system call 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-UPGRADE-3-BUF_READ Failed to read file [chars]
Explanation The read() system call 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-UPGRADE-3-CHAN_CREATE Failed to create channel : [chars]
Explanation Failed to create lc_rom_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-3-DEBUG_INIT Debug initialization failed
Explanation Initialization of the debug event 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-UPGRADE-3-DEBUG_REG Debug registration failed : [chars]
Explanation debug_register() call 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-UPGRADE-3-ERASE_SECTORS Erase sectors fail for [chars]
Explanation Failed to erase sectors.
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-3-ERASE_SECTORS Erase sectors fail for [chars]
Explanation Failed to erase sectors.
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-3-EVENT_MGR_FAIL [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-3-FL_SIZE Overflow in fabric-loader upgrade.
New fabric-loader size=[dec] available size=[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 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-3-FLASH_DEVICE Flash Device is not AM29LV800B - Linecard upgrade won't continue
Explanation The current driver only supports AM29LV800B flash device.
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-3-FLASH_DEVICE Flash Device is not AM29F040 - Routing Processor card upgrade won't continue
Explanation The current driver only supports AM29F040 flash device.
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-3-GET_SLOT Failed to get slot number
Explanation The platform library call platform_get_my_slot() fails.
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-3-MMAP Failed to map device address : [chars]
Explanation mmap() system call failed to map the device physical address.
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-3-MMAP Failed to map device address : [chars]
Explanation mmap() system call failed to map the device physical address.
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-3-MSG_REPLY Failed to send reply message : [chars]
Explanation This error is reported when msg_reply() (LWM call) fails.
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-3-MUNMAP Failed to unmap mapped object : [chars]
Explanation munmap() system call 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-UPGRADE-3-MUNMAP Failed to unmap mapped object : [chars]
Explanation munmap() system call 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-UPGRADE-3-NEW_ROM_SIZE Overflow in ROM monitor upgrade.
New ROM monitor size=[dec] available size=[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 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-3-NEW_ROM_SIZE Overflow in ROM monitor upgrade.
New ROM monitor size=[dec] available size=[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 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-3-NOMEM Failed to allocate memory
Explanation This error is reported when malloc()/calloc() type system call fails.
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-3-NOMEM Failed to allocate memory
Explanation This error is reported when malloc()/calloc() type system call fails.
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-3-OPEN Failed to open file [chars] : [chars]
Explanation This error is generated when the open() system call fails.
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-3-OPEN Failed to open file [chars] : [chars]
Explanation This error is generated when the open() system call fails.
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-3-PROGRAM_FLASH Programming flash fail for [chars]
Explanation Failed in programming flash.
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-3-PROGRAM_FLASH Programming flash fail for [chars]
Explanation Failed in programming flash.
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-3-PROGRAM_FLASH_HEADER Programming flash header fail for [chars]
Explanation Failed in programming flash header.
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-3-QSM_ADD Failed to distribute channel using QSM : [chars]
Explanation Fail to distribute the local LWM channel to the RP.
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-3-STAT Failed to access file [chars] : [chars]
Explanation This error is generated when the stat() system call fails.
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-3-STAT Failed to access file [chars] : [chars]
Explanation This error is generated when the stat() system call fails.
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-3-STATUS_SEND Failed to send status
Explanation The msg_send() call failed to send the status update to the client.
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-3-VERIFY_FLASH Verify flash fail for [chars]
Explanation Failed to verify flash.
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-3-VERIFY_FLASH Verify flash fail for [chars]
Explanation Failed to verify flash.
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-3-VERIFY_FLASH_HEADER Verify flash header fail for [chars]
Explanation Failed to verify flash header.
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-4-FABRIC_UPGRADE fabric-downloader upgrade is not required : flash version:[dec].[dec] = new version:[dec].[dec]
Explanation The fabric-downloader version in flash is greater than the new fabric-downloader version being used to upgrade.
Recommended Action No action is required.
Error Message%PLATFORM-UPGRADE-4-ROM_UPGRADE rom-monitor upgrade is not required : flash version:[dec].[dec] = new version:[dec].[dec]
Explanation The rom-monitor version in flash is greater than the new rom-monitor version being used to upgrade.
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.
WD Messages
Error Message%PLATFORM-WD-0-INTERRUPT_REBOOT Excessive watchdog interrupts in last hour: [dec]. Node reboot scheduled
Explanation The cpu has received an excessive number of watchdogs interrupts in the last hour. The node will be rebooted. The total number of interrupts received since the hourly counters were last cleared is displayed.
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-WD-4-INTERRUPT Watchdog interrupt: [dec], total in last hour: [dec]
Explanation The cpu has received an interrupt from the watchdog timer. This indicates that the cpu was too busy to service the watchdog timer for a period of time in the recent past. The interrupt was handled and the timer serviced. Excessive watchdog interrupts will result in the node being reset. The number of interrupts since the cpu last serviced the watchdog and the total number of interrupts since the hourly timer was last cleared are displayed.
Recommended Action Determine the reason for the watchdog timer expiring. Possible causes include a process spinning at high priority or hardware interrupts flooding the cpu.
Error Message%PLATFORM-WD-6-HOURLY_COUNT Hourly summary of watchdog interrupts: watchdog interrupts: [dec].
Explanation This message is displayed once an hour if a watchdog interrupt is seen by the cpu. The count displayed is since the hourly counter was last cleared.
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.
