-
Cisco IOS XR System Error Reference Guide for XR1200 Series Platform Specific Messages, Release 3.3
-
Preface
-
Overview
-
Fabric Messages
-
ASIC Fabric Interface Messages
-
High Availability (HA) Messages
-
Installation Messages
-
Internet Protocol (IP) Messages
-
Layer 1 (L1) Messages
-
Layer 2 (L2) Messages
-
Line Card (LC) Messages
-
Media Messages
-
Manageability (MGBL) Messages
-
Operating System (OS) Messages
-
Packet Infrastructure Messages
-
Platform Messages
-
Quality of Service (QOS) Messages
-
Routing Messages
-
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:
1 ALPHA_DISPLAY Messages
Error Message%PLATFORM-ALPHA_DISPLAY-3-INIT_ERROR Process Initialization Failed: ([chars]%s)
Explanation The alphadisplay process failed to initialize. The alphadisplay process controls the 8 characters alphanumeric LEDs on the bottom of all 12000 series line and route processor cards (excluding SIP cards). It provides for the configuration of custom messages as well as the reading of the current output both through CLI and XML. %s - indicates the reason for the failure. There are 2 types of possible failures, these include: - Event Manager Creation Failure - SYSDB Initialization Failure %s - is the decoded error reason
Recommended Action The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. Execute 'show process alphadisplay' to verify that the process is up and running. If it is still non-operational, try doing try doing 'process restart alphadisplay' 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-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-7-EVENT_ERROR Event Failure: ([chars])
Explanation The alphadisplay process received a bad event. The alphadisplay process controls the 8 characters alphanumeric LEDs on the bottom of all 12000 series line and route processor cards (excluding SIP cards). It provides for the configuration of custom messages as well as the reading of the current output both through CLI and XML. %s - is the decoded error reason
Recommended Action Monitor the event messages. The alphadisplay process will handle the failure gracefully but if they continually appear on the console, try doing 'process restart alphadisplay' 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.
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 that a free queue is empty
Explanation The assembler component has detected that one of the free queues used to buffer packets coming from the fabric into the route processor is empty.
Recommended Action The system will most likely recover from this error automatically. No intervention is required. If this error is reported frequently you may want to call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-ASM-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-4-BADDESC_ERR Assembler detected a bad descriptor.
Explanation Assembler detected a bad descriptor in the free queue. The system will usually recover from this error automatically. If the frequency of this alert increases noticeably it could indicate a hardware problem on the route processor card.
Recommended Action The system will normally recover from this error without intervention. If the frequency with which this error occurs increases substantially, call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
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.
BP_SERVER Messages
Error Message%PLATFORM-BP_SERVER-3-ERR_DSC_ELECTION This RP detected more than 2 RPs (active/standby) inserted in the chassis.
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 prompt. Insert other RP cards and load them as required.
Error Message%PLATFORM-BP_SERVER-3-ERR_INIT_DSC Failed to learn if we are running on the DSC ([chars])
Explanation This process needs to know if it runs on the DSC or standby DSC. An error occured while trying to get the information from the DSC process. The process will voluntary exit, and should be restarted.
Recommended Action Verify that the DSC process is running using 'show process' command.
Error Message%PLATFORM-BP_SERVER-3-ERR_MAC_BLK_SIZE Backplane NVRAM contains MAC address info field [hex] which is invalid. Please rectify this problem to ensure quality operation of your router
Explanation There is a MAC address block field in the backplane NVRAM. If the MAC address block field is invalid, there is the possibility of corrupted backplane NVRAM or incompatibility with the software
Recommended Action Verify that the chassis is supported with the version of software. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered.
Error Message%PLATFORM-BP_SERVER-3-INVALID_BP_VERSION Backplane NVRAM contains Backplane Version number [dec] which is invalid. Please rectify this problem to ensure quality operation of your router
Explanation There is a Backplane Version field in the backplane NVRAM. If the Backplane Version field is invalid, there is the possibility of corrupted backplane NVRAM or incompatibility with the software
Recommended Action Verify that the chassis is supported with the version of software. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered.
Error Message%PLATFORM-BP_SERVER-3-INVALID_CHASSIS_MODEL Backplane NVRAM contains chassis model number [dec] which is invalid. Please rectify this problem to ensure quality operation of your router
Explanation Backplane NVRAM contains the chassis model number which the software relies on for chassis identification. This is a complaint about an invalid chassis model number is stored in backplane NVRAM. Software will try its best to use the CSC card in the chassis to determine the chassis model.
Recommended Action Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered.
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.
DSCMEDIA Messages
Error Message%PLATFORM-DSCMEDIA-2-ERR_WAIT_REDUNDANCY Waiting for result of active/standby arbitration...keep trying
Explanation The redundancy information is needed as an input for the DSC election. Only active cards may become DSC. The information is still unavailable at this time. The DSC election is on hold, waiting for the information to become available. This will prevent proper system operation.
Recommended Action If this message happens repeatitively, it indicates a problem, likely in the active/standby arbitration module. Collect information using 'show redundancy'.
Error Message%PLATFORM-DSCMEDIA-2-FATAL DSC media fatal error: [chars]
Explanation The dsc media dll encountered aa fatal error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-DSCMEDIA-3-ERROR Error from dsc media dll: [chars]
Explanation The dsc media dll encountered an internal software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-DSCMEDIA-3-ERROR2 Error from dsc media dll: [chars], errno=[dec] ([chars])
Explanation The dsc media dll encountered an internal software error.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-DSCMEDIA-3-READ_PERSIST Unable to [chars] when parsing persistent file [chars]: [chars] ([chars])
Explanation The dsc process attempted to read dcs election information from non-volatile storage, but encountered a problem. This may cause the wrong RP card to get elected as DSC.
Recommended Action Verify nvram: filesystem integrity. If this is a persistent problem then: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-DSCMEDIA-3-WRITE_PERSIST Unable to [chars] when writing persistent file [chars]: [chars] ([chars])
Explanation The dsc process attempted to store dcs election information to non-volatile storage, but encountered a problem. This may cause the wrong RP card to get elected as DSC on the next chassis cold boot.
Recommended Action Make sure there is free space in local NVRAM. If this is a persistent problem then: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-DSCMEDIA-4-FETCH Unable to [chars] [chars] when fetching initial copy from DSC: [chars] ([chars])
Explanation The process is unable to get an initial copy of the dsc info file from the dsc card. This may cause the wrong RP card to get elected as DSC on the next chassis cold boot.
Recommended Action Restarting the dsc process (proc restart dsc) will cause it to retry the operation and normally recover from this condition. If the issue persists: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-DSCMEDIA-4-LISTEN Unable to listen for multicast messages: [chars] ([chars])
Explanation The process is unable to register to receive multicast messages. This means that the card will not be able to update local non-volatile data with the latest dsc election information coming from remote nodes. This may cause the wrong RP card to get elected as DSC on the next chassis cold boot.
Recommended Action Restarting the dsc process will cause it to re-register to receive dsc persisted updates. If the issue persists: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-DSCMEDIA-4-NO_CSC_SN Could not read Serial Numbers of the Fabric Cards slot 16 & 17; errno=[dec] ([chars])
Explanation Serial Numbers of the Fabric Cards (slots 16 and 17) are used to help determine chassis nativity for the Logical Routers feature. Chassis nativity is part of the algorithm to ensure that on a cold boot, the right RP is elected as the DSC and provides Logical Router boundaries to other RP cards. The lack of CSC serial numbers may cause the wrong RP to be elected DSC when RP cards are shuffled from one chassis to another and a cold boot is performed.
Recommended Action Ensure that Fabric CSC cards are properly inserted in the chassis.
Error Message%PLATFORM-DSCMEDIA-4-WARNING Warning from dsc media dll: [chars]
Explanation The dsc media dll encountered an internal software warning.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-DSCMEDIA-4-WARNING2 Warning from dsc media dll: [chars], errno=[dec] ([chars])
Explanation The dsc media dll encountered an internal software warning.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-DSCMEDIA-6-DSC_ELECTED This node is now [chars]
Explanation A new dSC has been elected.
Recommended Action No action is required.
ENVMON Messages
Error Message%PLATFORM-ENVMON-1-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. The request to sysldr to shut the card, failed.
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-1-SHUTDOWN Environmental Monitor initiated shutdown on slot [dec]
Explanation An environmental sensor has remained in a dangerous operating range, and sysldr is requested to shutdown card 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-1-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-1-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-ADDITIVE_POWER_OVERBUDGET Power consumption has exceeded additive supply mode limit by [dec]W; results unpredictable
Explanation The power calculated in use by the chassis exceeds that available by the powershelf. This condition could result in an outage of the chassis if action is not immediately taken.
Recommended Action Remove some linecards to reduce power consumption, or install a higher capacity powershelf.
Error Message%PLATFORM-ENVMON-2-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-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-2-ENV_POWER_FAILURE The environmental condition on slot [dec] is because of power failure
Explanation Powershelf failure 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 power-shelf' 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-ENV_POWER_FAILURE_CLEAR The environmental condition (Power Failure) on slot [dec] is cleared
Explanation Power failure environmental conditions on the specified slot have cleared.
Recommended Action None required.
Error Message%PLATFORM-ENVMON-2-ENV_POWER_FAULT The environmental condition on slot [dec] is because of power fault
Explanation Powershelf fault 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 power-shelf' 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-ENV_POWER_FAULT_CLEAR The environmental condition (Power Fault) on slot [dec] is cleared
Explanation Power fault environmental conditions on the specified slot have cleared.
Recommended Action None required.
Error Message%PLATFORM-ENVMON-2-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-2-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-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 over-temperature 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-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-2-POWER_BUDGET_OK Power consumption is back within [chars] supply mode limits
Explanation The power calculated in use by the chassis has returned to a value that is within the power supplied by the powershelf.
Recommended Action None required.
Error Message%PLATFORM-ENVMON-2-POWERSUPPLY_CURRENT [chars] current has reached [chars] level at [dec] A
Explanation The current 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_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-2-POWERSUPPLY_NONOP [chars] is Non-Operational
Explanation The power 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_NONOP_CLEAR [chars] has become operational
Explanation The power supply specified has returned to an operational state.
Recommended Action None required.
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-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-2-REDUNDANT_POWER_OVERBUDGET Power consumption has exceeded redundant supply mode limit by [dec]W; power redundancy lost
Explanation The power calculated in use by the chassis exceeds that for which power supply redundancy is available. The chassis now function in additive mode.
Recommended Action Remove some linecards to reduce power consumption, or install a higher capacity powershelf to regain power supply redundancy.
Error Message%PLATFORM-ENVMON-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 over-temperature 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-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-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-2-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.
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 another envmon E5 related error about the hardware or firmware check failing.
Recommended Action *SUPPORT*
Error Message%PLATFORM-ENVMON-3-ERR_CARD_UNSUPPORTED 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-3-ERR_E5_NOSUPPORT 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-ERR_MARGIN_MODE_UNKNOWN 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-ERR_SLOT_INVALID [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-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-UNEXPECTED_PRP_TYPE Unexpected PRP type [hex] in slot [dec]. Assuming PRP-2
Explanation The envmon component received an unexpected PRP type.
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.
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.
Recommended Action *SUPPORT*
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 envmon component will treat this PRP as if it was 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-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-5-ERR_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-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-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-7-BAG_DECODE_FAILED Bag decode on [chars] failed. Error: [chars]
Explanation Could not decode bag
Recommended Action None
Error Message%PLATFORM-ENVMON-7-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-7-ERR_ASSERT Assertion failure due to [chars]
Explanation A fatal internal software error has occurred.
Recommended Action No action is required.
Error Message%PLATFORM-ENVMON-7-ERR_CHKPT Checkpointing error, [chars] : [chars]
Explanation Envmon encountered an error in data checkpointing.
Recommended Action No action is required.
Error Message%PLATFORM-ENVMON-7-ERR_CHKPT_CREATE Could not create checkpoint entry (key [hex]): [chars]
Explanation Envmon encountered an error in data checkpointing.
Recommended Action No action is required.
Error Message%PLATFORM-ENVMON-7-ERR_CHKPT_DELETE Could not delete checkpoint entry (objid [hex]): [chars]
Explanation Envmon encountered an error in data checkpointing.
Recommended Action No action is required.
Error Message%PLATFORM-ENVMON-7-ERR_CHKPT_ITERATE [chars]: [chars]
Explanation Envmon encountered an error in data checkpointing.
Recommended Action No action is required.
Error Message%PLATFORM-ENVMON-7-ERR_CHKPT_RESTORE A corrupted checkpoint was detected: key = [hex], datakey = [hex]. Entry deleted.
Explanation Envmon encountered an error in data checkpointing.
Recommended Action No action is required.
Error Message%PLATFORM-ENVMON-7-ERR_CHKPT_SAVE Could not save checkpoint entry (key [hex], objid [hex]): [chars]
Explanation Envmon encountered an error in data checkpointing.
Recommended Action No action is required.
Error Message%PLATFORM-ENVMON-7-ERR_DEBUG_REG 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-7-ERR_DSC_CONNECT Could not contact the dSC: [chars]
Explanation Environmental monitoring couldn't contact the dSC
Recommended Action None.
Error Message%PLATFORM-ENVMON-7-ERR_DSC_GET 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-7-ERR_EDM_INIT Error initializing envmon EDM ([chars]): [chars]
Explanation An error occurred while setting up the envmon EDM.
Recommended Action No action is required.
Error Message%PLATFORM-ENVMON-7-ERR_EDM_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-7-ERR_EVM_ASYNC_ATTACH 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-7-ERR_EVM_CREATE 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-7-ERR_INTERNAL [chars]: [chars]
Explanation Miscellaneous software error.
Recommended Action No action is required.
Error Message%PLATFORM-ENVMON-7-ERR_LWM_RECEIVE 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-7-ERR_LWM_REPLY 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-7-ERR_MBUS_CEC [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 No action is required.
Error Message%PLATFORM-ENVMON-7-ERR_MBUS_READREG [chars]: Error reading mbus register [hex] on slot [dec]: [chars]
Explanation An error occurred reading an MBus register.
Recommended Action No action is required.
Error Message%PLATFORM-ENVMON-7-ERR_MBUS_RECEIVE [chars]: Error receiving MBus message for slot [dec], type [dec]: [chars]
Explanation An error occurred reading an MBus register.
Recommended Action No action is required.
Error Message%PLATFORM-ENVMON-7-ERR_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-7-ERR_PTHREAD [chars]: pthread manipulation error: [chars]
Explanation A proccess thread call failed.
Recommended Action No action is required.
Error Message%PLATFORM-ENVMON-7-ERR_SLOT_EXTRACT [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-7-ERR_SYSDB_BIND 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-7-ERR_SYSDB_GET 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-7-ERR_SYSDB_REG_NOTIFY 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-7-ERR_THREAD_CREATE 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-7-ERR_TRAP_SEND Error generating Envmon trap notification [chars]: [chars]
Explanation An error occurred while generating trap notification to SNMP
Recommended Action No action is required.
Error Message%PLATFORM-ENVMON-7-ERROR Error, [chars]
Explanation Envmon encountered an software error.
Recommended Action No action is required.
Error Message%PLATFORM-ENVMON-7-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-7-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-7-SYSMGR_PROC_READY_FAILED System Manager's proccess ready failed. Error: [chars]
Explanation A sysmgr process ready API failed.
Recommended Action None.
FABRIC_CTRL Messages
Error Message%PLATFORM-FABRIC_CTRL-2-ACTIVE_RP Encountered error when waiting for the active/standby role of the RP. rc=[hex]
Explanation This message indicates that the fabric control process encounter an error when waiting for the active RP notification. Process exits with error. This is either a system resource issue or a software bug.
Recommended Action Try to restart fctl process to see if problem persists 'process restart fctl'. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-FABRIC_CTRL-2-CARD_STATE [chars], [hex]
Explanation This message indicates that the software tries to set the state of an unknown card. Software is in a bad state.
Recommended Action Try to restart fctl process to see if problem persists 'process restart fctl'. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-FABRIC_CTRL-2-CHKPT_INIT_FAILED Fabric control failed to initialize for data checkpointing, errno = [hex]
Explanation This message indicates that the fabric control process encountered a problem when trying to initialize data checkpointing. Process will abort.
Recommended Action Try to restart fctl process to see if problem persists 'process restart fctl'. Check if system memory is adequate. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-FABRIC_CTRL-2-CHKPT_REGISTRATION_FAILED Fabric control failed to register for data checkpointing, errno = [hex]
Explanation This message indicates that the fabric control process encountered a problem when trying to registering data for checkpointing. Process will abort.
Recommended Action Try to restart fctl process to see if problem persists 'process restart fctl'. Check if system memory is adequate. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-FABRIC_CTRL-2-ERR_MEM_ALLOC [chars]
Explanation This message indicates that the system did not have enough memory available. [chars] is the operation for which there was insufficient memory. System may be in an unstable state.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs
Error Message%PLATFORM-FABRIC_CTRL-2-ERR_MEM_ALLOC No memory avaliable for [chars]
Explanation This message indicates that the system did not have enough memory available. [chars] is the operation for which there was insufficient memory. System is in an unstable state.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-FABRIC_CTRL-2-ERR_REPORT [chars]
Explanation This message indicates that an error detected in the fabric hardware as described in [char]
Recommended Action Follow the instruction on the error message. If it is a suspected hardware failure, reseat the hardware. If reseating the hardware does not fix the error condition, contact your Cisco technical support representative.
Error Message%PLATFORM-FABRIC_CTRL-2-EVENT_LOOP Process event loop exited due to unknown errors. Abort
Explanation This message indicates that the fabric control process encounter an error in its event dispatcher. Process aborts. This is either a system resource issue or a software bug
Recommended Action Try to restart fctl process to see if problem persists 'process restart fctl'. Check if system memory is adequate. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-FABRIC_CTRL-2-FAILED_SYNCH Failed to drive slave clock on card [dec] from [chars]
Explanation This message indicates that the card on slot failed to synchronize clocks with the Master clock. If this condition persists, Slot is unusable.
Recommended Action Check the MBUS agent ROM version of the fabric cards and the card on slot are up-to-date. Check the fabric loader version on slot is up-to-date. Check the temperature of the fabric cards. Reseat the card on slot and all the fabric cards. If reseating the hardware does not fix the error condition, contact your Cisco technical support representative.
Error Message%PLATFORM-FABRIC_CTRL-2-FAILED_TO_RESET_FC Failed to reset fabric card, slot=[dec] in software
Explanation A fabric card failed to reset. This message indicates that the software failed to reset the fabric card on slot . Slot is marked as malfunction and is shutdown.
Recommended Action Check the MBUS agent ROM version of the fabric cards are up-to-date. Check the temperature of the fabric cards. Reseat the primary CSC card. If reseating the hardware does not fix the error condition, contact your Cisco technical support representative.
Error Message%PLATFORM-FABRIC_CTRL-2-FAILED_TO_SEND_CONFIG Failed to send new fabric configuration to slot [dec] after [dec] retries
Explanation This message indicates that the linecard on slot failed to receive the latest fabric configuration data it needs to connect to the fabric. slot is disconnected from the fabric and is unusable.
Recommended Action Reseat the linecard on slot . If reseating the hardware does not fix the error condition, contact your Cisco technical support representative.
Error Message%PLATFORM-FABRIC_CTRL-2-FAILED_TO_SEND_SLOT_BW Failed sending slot bandwidth info to slot [dec] after [dec] retries
Explanation This message indicates that the linecard on slot failed to receive the latest slot bandwidth data it needs to operate. slot is disconnected from the fabric and is unusable.
Recommended Action Reseat the linecard on slot . If reseating the hardware does not fix the error condition, contact your Cisco technical support representative.
Error Message%PLATFORM-FABRIC_CTRL-2-FAILED_TO_SYNC_RP Failed to sync RP (slot=[dec]) to [chars] (slot=[dec])
Explanation This message indicates that the RP on slot failed to synchronize its clock with the Master clock. The RP on slot is unusable if this condition presists. If RP on slot is the primary RP, then the router is unusable.
Recommended Action Check the MBUS agent ROM version of the fabric cards and the RP on slot are up-to-date. Check the temperature of the fabric cards. Reseat the RP on slot and all the fabric cards. If reseating the hardware does not fix the error condition, contact your Cisco technical support representative.
Error Message%PLATFORM-FABRIC_CTRL-2-FAILED_TO_SYNC_RP_TO_CSCS Could not synch primary RP (slot=[dec]) to both CSC1 and CSC0
Explanation This message indicates that the primary RP failed to synchronize its clock with either CSC. If problem persists, router is unusable.
Recommended Action Check the MBUS agent ROM version of the fabric cards and the RP on slot are up-to-date. Check the temperature of the fabric cards. Reseat the RP on slot and all the fabric cards. If reseating the hardware does not fix the error condition, contact your Cisco technical support representative.
Error Message%PLATFORM-FABRIC_CTRL-2-FAILED_TO_SYNC_TO_SELF Failed to sync [chars] (slot [dec]) to itself
Explanation This message indicates that the primary CSC failed to synchronize its clock with itself. If problem persists, router is unusable.
Recommended Action Check the MBUS agent ROM version of the fabric cards are up-to-date. Reseat the primary CSC card. Check the temperature of the fabric cards. If reseating the hardware does not fix the error condition, contact your Cisco technical support representative.
Error Message%PLATFORM-FABRIC_CTRL-2-MBUS_ERROR Unable to send MBUS msg. Error = [dec] ([chars])
Explanation This message indicates that an error occurred when the card tries to communicate with remote on fabric and chassis management via MBUS. Chassis, LCs and fabric is in a bad state.
Recommended Action Verify the MBUS agent ROM version is up-to-date. Reseat the card with the error. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-FABRIC_CTRL-2-NOTIFY_BW_CHG_ERROR new chassis bandwidth, [dec], cannot be sent to clients. Error: [chars]
Explanation This message indicates that chassis bandwidth has changed but fabric control cannot send the info to its clients. Router may be in an unstable state.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-FABRIC_CTRL-2-PROCESS_INIT Encountered critical problem in initialization of [chars]
Explanation This message indicates that the system cannot initialize some critical parts of the fabric software. [chars] are the critical parts that failed. Fabric control process is aborted.
Recommended Action Try to restart fctl process to see if problem persists 'process restart fctl'. Check if system memory is adequate. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-FABRIC_CTRL-3-MBUS [chars], errno=[hex], [chars]
Explanation This message indicates that an error occurred when RP tries to communicate with remote on fabric and chassis management via MBUS. If problem persists, chassis, LCs and fabric is in a bad state.
Recommended Action Verify the MBUS agent ROM version is up-to-date. Try to restart fctl and mbus process to see if problem persists: 'process restart fctl' and 'process restart mbus'. If this is a newly inserted card, try to reseat the card. If problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-FABRIC_CTRL-3-MIB_INIT_ERROR [chars]
Explanation Unable to initialize the debugging facility of fabric MIB. Other fabric MIB capabilities are not disturbed.
Recommended Action Try to restart fctl process to see if problem persists 'process restart fctl'. Check if system memory is adequate. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-FABRIC_CTRL-3-RESTORE_DATA Encountered error restoring checkpointed data
Explanation This message indicates that the system cannot restore checkpointed data of the fabric software. Router may be in an unstable state
Recommended Action Try to restart fctl process to see if problem persists 'process restart fctl'. Check if system memory is adequate. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-FABRIC_CTRL-3-THREAD_CREATE Unable to create thread to detect card insertion/removal for register [dec] : rc=[hex], [chars]
Explanation This message indicates that software encountered an error when creating a thread to detect lincard insertion and removal. Linecards, fabric cards, and RP insertion and removal may not be handled correctly.
Recommended Action Try to restart fctl process to see if problem persists 'process restart fctl'. Check if system memory is adequate. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-FABRIC_CTRL-3-UNKNOWN_CHASSIS The chassis type is not known from reading the backplane
Explanation This message indicates that the software installed on the system does not recognize the chassis type. The Backplane Server has not provided the chassis model. Software cannot monitor the chassis and will abort.
Recommended Action Remove all the RPs from the backplane of the chassis except the active RP. Reload the active RP. Insert the other RPs into the chassis after the active RP is booted up in IOS-XR RUN state. If problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-FABRIC_CTRL-3-UNKNOWN_MSG Unknown msg from slot [dec] with msg type [hex]
Explanation This message indicates that the fabric control process received an unknown msg. The message is ignored.
Recommended Action Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.
Error Message%PLATFORM-FABRIC_CTRL-3-UNSUPPORTED_CHASSIS Chassis type [dec] not supported
Explanation This message indicates that the software installed on the system does not recognize the chassis type. Software cannot monitor the chassis fabric. Fabric cards are shutdown.
Recommended Action Verify the fabric card and chassis is supported by the software. Reseat the all the fabric cards. If reseating the hardware does not fix the error condition, contact your Cisco technical support representative
Error Message%PLATFORM-FABRIC_CTRL-5-FABRIC_CARD_OIR_INSERTED Fabric card [chars] inserted in slot [dec]
Explanation This message indicates that a fabric card on slot is inserted into the chassis. The fabric control software takes care of its insertion automatically. The chassis fabric and card's Fabric Interface ASIC are re-configured accordingly.
Recommended Action No action required.
Error Message%PLATFORM-FABRIC_CTRL-5-FABRIC_CARD_OIR_REMOVED Fabric card [chars] removed from slot [dec]
Explanation This message indicates that a fabric card on slot is removed from the chassis. The fabric control software takes care of its removal automatically. The chassis fabric and card's Fabric Interface ASIC are re-configured accordingly.
Recommended Action No action required.
FAULT Messages
Error Message%PLATFORM-FAULT-2-LC_RESET Reset LC [dec]: Reason - [chars]
Explanation PRP Platform Manager process received an mbus message from the LC fault-mgr process saying the LC will be reloaded. The platform-mgr process is only reporting this message, via mbus, for the LC fault-mgr process - as some HW devices have failed and the slow-path will be down. %d - is the LC that will be reloaded. %s - Contains the reason for the LC reload.
Recommended Action The linecard in question will be automatically reloaded to recover. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-FAULT-3-LC_DEVICE LC [dec]: Reset Device - [chars]
Explanation PRP Platform Manager process received an mbus message from the LC fault-mgr process saying HW devices will be reset. The platform-mgr process is only reporting this message, via mbus, for the LC fault-mgr process - as HW devices are being reset and the slow-path will be down. There will be traffic loss on the LC. %d - is the LC with the faulty device. %s - is the Device and Instance of the fault being addressed.
Recommended Action The linecard in question will have the appropriate HW device reset to recover from the HW issue. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
FDIAGS Messages
Error Message%PLATFORM-FDIAGS-3-BAD_EE_READ failure reading EEPROM ([chars]) values during Field Diag EEPROM update: EEPROM not updated
Explanation After completing Field Diags, the EEPROM update was requested, but there was a read failure during the process. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-BAD_EE_VALS EEPROM update requested with illegal values: 0x% [hex] [hex]: EEPROM not updated
Explanation After completing Field Diags, the EEPROM update was requested with values that are out of bounds. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail. Internal programming error, report to Cisco's TAC
Error Message%PLATFORM-FDIAGS-3-BAD_EE_WRITE failure writing EEPROM @ offset of [hex] during Field Diag EEPROM update: This byte not updated
Explanation After completing Field Diags, the EEPROM update was requested, but there was a write failure during the process. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-BAD_F_DIAG_KILL Unable to kill this existing Field Diag process: rc from kill was [dec]
Explanation Could not kill that job ID for Field Diags Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-CANNOT_GET_JID Cannot determin Job ID for Field Diags process
Explanation Error getting JID Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-CANT_HALT_MYSELF Can not halt myself
Explanation User is requesting a halt for a card which is the master RP and couldn't be running Field Diags anyway.
Recommended Action Try another command.
Error Message%PLATFORM-FDIAGS-3-CANT_SEND_MBUS_MSG_F cannot send mbus messages: errno [dec]: [chars]()
Explanation Unable to complete sending mbus error message Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-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 Wait until the diags completes. If the user desires to re-start diags, use the halt command first, then re-launch diags.
Error Message%PLATFORM-FDIAGS-3-FAB_MBUS_NOT_READY Fabric card MBUS Ram Agent not loaded prior to beginning Field Diags Fabric tests
Explanation After launching Fabric Field Diagnostics, the fabric card appear not have MBUS Ram Agent loaded within the appropriate time. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail. Investigate why MBUS Ram agent is not successfully downloaded on the fabric card.
Error Message%PLATFORM-FDIAGS-3-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 Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-FILE_READ_JID_BAD Cannot read jid data from file
Explanation Could not read that job ID for Field Diags from the file Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-IF_BAD_HALT_OPEN Unable to open Field Diags halt request file [chars]: [chars]
Explanation Error opening halt request file. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-IF_BAD_HALT_WRITE Unable to write Field Diags halt request to file [chars]: [chars]
Explanation Error writing HALT request file Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-IF_BAD_JID_OPEN Unable to open Field Diags state file [chars]: [chars]
Explanation Error opening JID file Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-IF_BAD_JID_READ Unable to read Field Diags state from file [chars]: [chars]
Explanation Error reading JID file Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-IF_BAD_JID_WRITE Unable to write Field Diags state to file [chars]: [chars]
Explanation Error writing JID file Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-IF_FAIL_CONN_SYSLDR_F could not connect to LWM [chars] in [chars]()
Explanation Failed to Connect to sysloader initially Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-IF_FAIL_SEND_SYSLDR_F could not send LWM in [chars]()
Explanation Failed to Connect to sysloader initially Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-IF_FAIL_SYSLDR_DISCONNECT_F could not LWM disconnect from [chars] in [chars]()
Explanation Failed to Connect to sysloader initially Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-IF_FAIL_UUT_LAUNCH UUT launch failed ([chars]). Exiting...
Explanation Failed to Connect to sysloader initially Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-IF_INACTIVITY_TIMEOUT No response from UUT in ~[dec] minutes ([dec] seconds). exiting
Explanation No communication from the UUT in a while. UUT likely became inoperable. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-IF_NON_EXISTANT_JID_OPEN Unable to open Field Diags state file [chars]: [chars]
Explanation Error opening JID file Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-ILLEGAL_FSM_STATE internal (FSM) state change ILLEGAL: was [chars], attempted [dec]
Explanation Bad internal state change Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-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 Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-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 Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-MS_NO_CARD_ID misc svcs: [chars](): Retries failed to get card ID
Explanation Failed to receive back card ID during a diags misc_svcs request. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-MS_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 Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-MS_PRI_CLK_READ misc svcs: [chars]: could not read primary clock
Explanation Failed to read Primary Clock from fctl Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-MS_READ_REG_FAIL Failed in reading register [hex] from slot [dec]
Explanation Failed to read a slot-specific register via an mbus-access Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-MS_READ_REG_FAIL_F Failed in reading register [hex] from slot [dec] in [chars]()
Explanation Failed to read a slot-specific register via an mbus-access Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-MS_UNDEF_MS_MSG misc svcs: [chars]: Undefined MBUS_MISC_SVCS message received: Ignored: msg [hex]
Explanation Misc services server received an unrecognized message Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-MS_WRITE_REG_FAIL Failed in writing [hex] to register [hex] on slot [dec]
Explanation Failed to write a slot-specific register via an mbus-access Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-MS_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 Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-MS_XBAR_MAP misc svcs: [chars]: could not read xbar map
Explanation Failed to read xbar map from fctl Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-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? Field Diags eitgher was not running or was completed prior to this command being entered.
Recommended Action Please 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 when requesting diags be halted.
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. C12000 is a single-chassis system.
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 Time of day (calendar) may not be initialized. Set using the appropriate CLI and options.
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 Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-NON_UUT_IN_STATE Unexpected message received during UUT_ON state: sub-msg [hex] from slot [dec]
Explanation Field Diags was not expecting this type of message at this time. If this problem persists and diags does not complete, Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-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 Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-SPA_ID_FAIL Failure when trying to identify SPA's attached to card in slot [dec]
Explanation A call to mbus_get_spa_type() returned an error Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-SPA_UNSUPPORTED_INSTANCE Requested instance ([dec]) (bay) not supported by this UUT (min=[dec], max=[dec])
Explanation Spa bay requsted not supported
Recommended Action Select a spa bay in within the appropriate range
Error Message%PLATFORM-FDIAGS-3-SPCL_RAM_AGENTDL_FAILED Download of LC Ram Agent diag_mbus_ram.ucode failed
Explanation Download of diag_mbus_ram.ucode failed Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-SYSLDR_RESULT_CODE_OUT_OF_BOUNDS Result code from sysloader ([dec]) exceeds list of known messages
Explanation Coding violation: Sysldr code returns unexpected cause. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-SYSTEM_ERR_NO_CONTINUE Sysldr reporting error - Field Diags will not commence testing
Explanation Sysldr reporting error - time to quit Field Diags Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-T_O_D_CONVERT_ERR time of day conversion error
Explanation Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT. Internal Time Of Day conversion error
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-3-UNRECOGNIZED_CARD Card 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. The requested action or option is not supported by fabric tests.
Recommended Action Review CLI options which are appropriate to fabric card testing.
Error Message%PLATFORM-FDIAGS-4-ERROR_AFTER_RESULTS_REPORT Unexpected return value from reporting results to sysldr: [chars]
Explanation Resulting response from sysldr after reporting final results indicates a non-happy sysldr. Reason in string from sysldr Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-4-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_MSV_SUB_MSG Unexpected Misc Services message subtype [dec] received from slot [dec]
Explanation An unexpected MBUS_FDIAG MISC Services message was received from UUT. Possibly a mal-formed or unfinished software enhancement. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-4-UNEXP_SUB_MSG Unexpected message subtype [dec] received from slot [dec]
Explanation An unexpected MBUS_FDIAG message was received from UUT. Possibly a mal-formed or unfinished software enhancement. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-5-CLEANED_DANGLING_JID_FILE Deleted orphaned Field Diags jid file
Explanation A file from a previous instance of Field Diags was left. We have now deleted it.
Recommended Action No action required
Error Message%PLATFORM-FDIAGS-5-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-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. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-5-IF_TERMINATED_F_DIAGS_OK Successfully terminated Field Diags (jid=[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 Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-5-LC_TYPE_REQUIRES_SPCL_RAM_AGENT Linecard type requires diags_mbus_ram.ucode - downloading
Explanation This card requires a special version of mbus Ram Agent for comaptibility with diags for C2W requests for SPA communication Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
Error Message%PLATFORM-FDIAGS-5-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. This may be test names, progress messages, or failure information generated by the UUT.
Recommended Action No action
Error Message%PLATFORM-FDIAGS-6-RESULT Field Diags COMPLETE on UUT ([chars]) [chars] card type [dec] [[chars]] s/n [chars]
Explanation Field Diagnostics final results
Recommended Action No action
Error Message%PLATFORM-FDIAGS-6-UUT_OUT UUT [chars]: [chars]
Explanation Text output from UUT (Cisco use only) Non error-specific redirected output from diag process to syslog. This may be test names, progress messages, or failure information generated by the UUT.
Recommended Action No action
Error Message%PLATFORM-FDIAGS-6-UUT_OUT_I UUT (init) [chars]: [chars]
Explanation Text output from UUT during init state (Cisco use only) Non error-specific redirected output from diag process to syslog. This may be test names, progress messages, or failure information generated by the UUT.
Recommended Action No action
Error Message%PLATFORM-FDIAGS-7-FORCE_INTO_FSM Forcing into FSM mode, even though sysldr load UUT returned error
Explanation Internal use - ignoring sysldr error, continuing to Field Diags FSM
Recommended Action nothing
Error Message%PLATFORM-FDIAGS-7-NON_HELLO_MSG During Init state, unexpected mbus sub-message [hex] received from slot [dec]
Explanation Field Diags was not expecting this type of message at this time. If this problem persists and diags does not complete, Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.
Recommended Action Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.
FFQ Messages
Error Message%PLATFORM-FFQ-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_FREE_ERR The fabric driver failed to return a buffer to the free list from: [chars]
Explanation The fabric driver has failed to return a packet buffer received from the fabric to the free list. If this error keeps recurring it could result in the depletion of buffer for packet received on the route processor from the fabric. %s is the entity processing the packet.
Recommended Action If this error occurs again copy the system messages exactly as they appear, call your Cisco technical support representative. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-FFQ-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.
Error Message%PLATFORM-FFQ-4-PAK_INVALID Invalid packet type received from fabric on route processor: [dec]
Explanation FFQ has received an invalid packet type from the fabric. This error will not affect the functionality or stability of the system. %d packet type received
Recommended Action If this error occurs continuously call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
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 client API received an error from one of the linecard software driver processes that crashed due to a software problem and the LC must be reloaded. The platform-mgr process controls linecard resets for the software driver processes. If a linecard software driver crashes due to a software problem, it can get into a very bad and may be unrecoverable. This action is taken to reload the linecard immediately. %s - Contains the process and reason for the linecard reload.
Recommended Action The linecard will be automatically reloaded to recover. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-GSR_LC_PM-3-CONN_ERR Process connection failed: ([chars]%s)
Explanation The linecard platform-mgr process failed to connect its process to the route processor processes during process initialization. The platform-mgr process runs on the linecard and handles interface information between the route processor and the linecard hardware drivers. It also stores all local linecard information for every interface configured on the linecard. If the platform-mgr fails to connect, no linecard interfaces can be created or deleted. The platform-mgr show commands will also not be available. %s - indicates the reason for the failure. %s - is the decoded error reason.
Recommended Action The System Manager process (sysmgr) may not automatically respawn this process upon failure if processes get out of sync. Otherwise the process should be restarted. Execute 'show process gsr_pm location 0/x/cpu0' to verify that the process is up and running and has been restarted. If it is still non-operational, or has not been automatically restarted, try doing 'process restart gsr_pm location 0/x/cpu0'. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-GSR_LC_PM-3-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-INIT_ERR Process initialization failed: ([chars]%s)
Explanation The linecard platform-mgr process failed to initialize. The platform-mgr process runs on the linecard and handles interface information between the route processor and the linecard hardware drivers. It also stores all local linecard information for every interface configured on the linecard. If the platform-mgr fails to initialize, no linecard interfaces can be created or deleted. %s - indicates the reason for the failure. %s - is the decoded error reason.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. Execute 'show process gsr_pm location 0/x/cpu0' to verify that the process is up and running. If it is still non-operational, try doing 'process restart gsr_pm location 0/x/cpu0'. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
GSR_LIB Messages
Error Message%PLATFORM-GSR_LIB-3-CONN_ERR Event manager failure: ([chars]%s)
Explanation An error occurred in the system data-base (SysDB) event manager GSR platform library DLL. This DLL controls thread creation, deletion and connections between all other processes and DLL's. If there is a failure in this DLL, a connection will be lost somewhere on the system and failures will occur. %s - indicates the reason for the failure. %s - is the decoded error reason.
Recommended Action The DLL will attempt to recover itself, but if it cannot, the card will probably have to be reloaded as messages will have been lost and the system may be in a bad state. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-GSR_LIB-3-LR_ERR Logical router failure: ([chars]%s)
Explanation An error occurred during a card state change. This DLL controls the node information during a card state change for logical routers. If there is a failure here, the logical router will lose its nodeid information and will get out of sync with the system. %s - indicates the reason for the failure. %s - is the decoded error reason.
Recommended Action The DLL will attempt to recover itself, but if it cannot, the card will need to be reloaded as the system will be in a bad state. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-GSR_LIB-3-PLATFORM_ERR Platform library failure: ([chars]%s)
Explanation An error occurred in the GSR platform library DLL. The GSR platform library DLL controls all node and platform information of the system. If there is a failure here, the overall system will be out of sync and may need to be reloaded. %s - indicates the reason for the failure. %s - is the decoded error reason.
Recommended Action The DLL will attempt to recover itself, but if it cannot, the card will need to be reloaded as the system will be in a bad state. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
GSR_PRP_PM Messages
Error Message%PLATFORM-GSR_PRP_PM-2-CRIT_DEVICE Critical severity error: Device: [chars]
Explanation PRP Platform Manager process received a critical severity hardware error from one of the PRP hardware devices. In the case of the ASIC drivers, PRP-PM receives error reports from the drivers and takes action based on its knowledge of the required ASIC reset sequence. If error reports exceed a threshold then a PRP fail-over is initiated by PRP-PM. A traffic loss on the PRP will occur and an PRP failover may occur to recover. %s - is the Device of the fault being addressed.
Recommended Action The HW device with fault, and appropriate surrounding hw devices, will be reset to recover from the HW issue. The PRP may also request an RP failover to recover. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-GSR_PRP_PM-3-HIGH_DEVICE High severity error: Device: [chars]
Explanation PRP Platform Manager process received a high severity hardware error from one of the PRP hardware devices. In the case of the ASIC drivers, PRP-PM receives error reports from the drivers and takes action based on its knowledge of the required ASIC reset sequence. If error reports exceed a threshold then a PRP fail-over is initiated by PRP-PM. A slight traffic loss on the PRP will occur. %s - is the Device of the fault being addressed.
Recommended Action The HW device with fault, and appropriate surrounding hw devices, will be reset to recover from the HW issue. Copy the error message exactly as it appears on 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-INIT_ERR Process initialization failed: ([chars]%s)
Explanation The PRP platform-mgr process failed to initialize. The PRP Platform Manager process provides fault management services for ASIC drivers and PRP fail-over initiation for Fabric Control (FCTL) If the platform-mgr fails to initialize, the system will be unable to recover due to an asic fault or PRP failover. %s - indicates the reason for the failure. %s - is the decoded error reason.
Recommended Action The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. Execute 'show process gsr_prp_pm' to verify that the process is up and running. If it is still non-operational, try doing 'process restart gsr_prp_pm'. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-GSR_PRP_PM-3-LOW_DEVICE Low severity error: Device: [chars]
Explanation PRP Platform Manager process received a low severity hardware error from one of the PRP hardware devices. In the case of the ASIC drivers, PRP-PM receives error reports from the drivers and takes action based on its knowledge of the required ASIC reset sequence. %s - is the Device of the fault being addressed.
Recommended Action This process is just counting the hardware errors as the asic driver will recover itself, there will be no impact to the system.
INVMGR Messages
Error Message%PLATFORM-INVMGR-2-ERR_SYSDB_REG_NOTIFY SysDB registration for notification on [chars] failed. Error - [chars]
Explanation This message indicates that registration for notification failed for the tuple specified. %s - tuple %s - indicates the internal error message
Recommended Action System manager will automatically respawn this process, up to a fixed number of times, when this error is encountered to recover. Execute 'show process invmgr location 0/x/cpu0' to verify that the process is up and running. If it is non-operational, do 'process restart invmgr location 0/x/cpu0' to manually restart it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-INVMGR-3-ERR_EEPROM_READ EEPROM/NVRAM read failed. Error - [chars], [dec]
Explanation EEPROM/NVRAM read failed for a chassis, card, or SPA. Inventory information would be incomplete. This would affect information provided to CLI 'show inventory', inventory schema, and the entity related MIBs. %s - indicates the internal error string %d - indicates the internal error code
Recommended Action Check the card/chassis/SPA.
Error Message%PLATFORM-INVMGR-3-ERR_INIT Initialization failed. [chars]. [chars]
Explanation This message indicates that process invmgr failed to initialize and exited. Inventory information would not be available. This would affect CLI 'show inventory', inventory schema, and the entity related MIBs. Some reasons are: 1) System manager process ready notification failed 2) Error waiting for secondary RP to go active 3) Internal API error %s - indicates the internal message. %s - indicates the internal error reason.
Recommended Action System manager will automatically respawn this process, up to a fixed number of times, when this error is encountered to recover. Execute 'show process invmgr location 0/x/cpu0' to verify that the process is up and running. If it is non-operational, do 'process restart invmgr location 0/x/cpu0' to manually restart it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-INVMGR-3-ERR_MEM_ALLOC [chars], slot [dec]
Explanation This message indicates memory allocation failure. Inventory information for the specified slot would be incomplete. This would affect information provided to CLI 'show inventory', inventory schema, and the entity related MIBs for the specified slot. %s indicates the internal data structure that failed allocation for.
Recommended Action Reduce other system activity to ease memory demands and restart process invmgr via CLI 'process restart invmgr' to recover. If conditions warrant and minimum memory requirements not met, upgrade to a larger memory configuration.
Error Message%PLATFORM-INVMGR-3-ERR_NODEID_CREATE Node ID of slot [dec]. Error - [chars]
Explanation This message indicates a failure in creating the node ID of the specified slot. Inventory information for the specified slot would be incomplete. This would affect information provided to CLI 'show inventory', inventory schema, and the entity related MIBs for the specified slot. %s - indicates the internal error reason.
Recommended Action Try restarting the invmgr process via CLI 'process restart invmgr' to recover. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-INVMGR-3-ERR_OBJECT_CREATE Slot [dec]. Error - [chars]
Explanation This message indicates a failure in creating the object for the specified slot. The entry is not added to the inventory. %s - indicates an internal message
Recommended Action Issue may be due to lack of memory in the system. If memory shortage is the cause, reduce other system activity to ease memory demands and restart process invmgr via CLI 'process restart invmgr' to recover. If conditions warrant and minimum memory requirements not met, upgrade to a larger memory configuration.
Error Message%PLATFORM-INVMGR-3-ERR_SENSOR_CREATE Slot [dec] sensor [dec] object create failed
Explanation This message indicates a failure in creating the sensor object for the specified slot and sensor. The sensor entry is not added to the inventory.
Recommended Action Issue may be due to lack of memory in the system. If memory shortage is the cause, reduce other system activity to ease memory demands and restart process invmgr via CLI 'process restart invmgr' to recover. If conditions warrant and minimum memory requirements not met, upgrade to a larger memory configuration.
Error Message%PLATFORM-INVMGR-3-ERR_SYSDB_BIND SysDB bind to [chars] failed. Error - [chars]
Explanation This message indicates bind to the specified path failed. Inventory information would be incomplete. This would affect information provided to CLI 'show inventory', inventory schema, and the entity related MIBs. %s - indicates the internal error reason.
Recommended Action Try restarting the invmgr process via CLI 'process restart invmgr' to recover. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-INVMGR-5-OIRIN OIR: Node [chars] inserted
Explanation Entity specified in the messages is inserted into the chassis and inventory manager is updated.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-INVMGR-6-NODE_STATE_CHANGE Node: [chars], state: [chars]
Explanation This message indicates the node state (eg. IOS XR RUN, MBI_RUNNING). A node being a card, SPA, etc. %s - indicates the node/location in // format %s - indicates the state
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-INVMGR-7-ERR_API [chars] failed for slot [dec]
Explanation The sensor entry will not be added in inventory
Recommended Action Check the memory on the system
Error Message%PLATFORM-INVMGR-7-ERR_NODEID Extract fields from node ID [dec] failed. Error - [chars]
Explanation This message indicates a failure in extracting fields from the node ID. Inventory information for the specified node ID, if valid, would be incomplete. This would affect information provided to CLI 'show inventory', inventory schema, and the entity related MIBs for the specified node. %s - indicates the internal error.
Recommended Action Try restarting the invmgr process via CLI 'process restart invmgr' to recover. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-INVMGR-7-FAIL [chars]
Explanation This message indicates a failure in inventory manager. This is an internal debug message. %s - indicates the failure.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
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-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-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-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.
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.
MBI_HELLO Messages
Error Message%PLATFORM-MBI_HELLO-2-NODE_RELOAD Reload notification received. Reloading card in [dec] secs
Explanation Message indicating that the mbi-hello on the card has received a reload notification from sysldr for powering off the card and the card is going to reload soon. Card state is MBI_RUNNING
Recommended Action Sysldr log needs to be looked into to investigate on the node reload cause. As, sysldr requests to reload the card for various reasons.
Error Message%PLATFORM-MBI_HELLO-2-NODE_RELOAD_NOW Node delay time over, reloading now
Explanation Message indicating that the node has received a reload notification from the sysldr and the node is going to reload as the delay is over. This message is logged after the delay over since the NODE_RELOAD message is logged.
Recommended Action Sysldr log needs to be looked into to investigate on the node reload cause. As, sysldr requests to reload the card for various reasons.
Error Message%PLATFORM-MBI_HELLO-7-ERR_MEM_ALLOC Failed to allocate [unsigned int] bytes of memory
Explanation The debug ping to mbi-hello process could not be accomplished because of a low memory condition.
Recommended Action This indicates a low memory condition. Memory on the box must be running low - are there services that can be stopped, or can more memory be added?
Error Message%PLATFORM-MBI_HELLO-7-ERR_MSG_SEND The MBI infrastructure was unable to send a message to the MBI Hello server, error: [chars].
Explanation A communication problem occurred between the MBI client and server. The MBI operation in progress will not be carried out.
Recommended Action The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.
Error Message%PLATFORM-MBI_HELLO-7-ERR_NETMGR_MOUNTPOINT_REQUEST Failed to request QNX net manager mountpoint
Explanation Failed to request netmgr mountpoint. The debug ping to mbi-hello process could not be accomplished.
Recommended Action The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.
Error Message%PLATFORM-MBI_HELLO-7-ERR_SERVER_CONNECT The MBI infrastructure was unable to connect to the MBI Hello server, error: [chars].
Explanation A communication problem occurred between the MBI client and server, perhaps because the communications infrastructure is not set up. The MBI operation in progress will not be carried out.
Recommended Action The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.
Error Message%PLATFORM-MBI_HELLO-7-INFO_CREATE_SUCCESS MBI-Hello: Successful creation of [chars]. Attempt number [dec]
Explanation Successful creation of mbi-hello LWM channel for communication.
Recommended Action NONE
Error Message%PLATFORM-MBI_HELLO-7-TIMER_TIMEOUT The MBI infrastructure timer timed out from server : [chars]
Explanation Timer timed out between the MBI client and server, perhaps because the communications infrastructure is not set up. The MBI operation in progress will not be carried out.
Recommended Action The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.
Error Message%PLATFORM-MBI_HELLO-7-WARNING [chars]
Explanation Error in thread creation for mbi-hello process. The error reason is described in the message log itself.
Recommended Action NONE
MBI_LIB_ACCESS Messages
Error Message%PLATFORM-MBI_LIB_ACCESS-7-ERR_MSG_SEND The MBI infrastructure was unable to send a message to the MBI Hello server, error: [chars].
Explanation A communication problem occurred between the MBI client and server. The MBI operation in progress will not be carried out.
Recommended Action The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.
Error Message%PLATFORM-MBI_LIB_ACCESS-7-ERR_SERVER_CONNECT The MBI infrastructure was unable to connect to the MBI Hello server, error: [chars].
Explanation A communication problem occurred between the MBI client and server, perhaps because the communications infrastructure is not set up. The MBI operation in progress will not be carried out.
Recommended Action The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.
MBI_LIB Messages
Error Message%PLATFORM-MBI_LIB-3-MSG_SEND_FAIL The MBI infrastructure was unable to send a message to the MBI Hello server, error: [chars].
Explanation A communication problem occurred between the MBI client and server. The MBI operation in progress will not be carried out.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-MBI_LIB-3-SERVER_CONNECT_FAIL The MBI infrastructure was unable to connect to the MBI Hello server, error: [chars].
Explanation A communication problem occurred between the MBI client and server, perhaps because the communications infrastructure is not yet up. The MBI operation in progress will not be carried out.
Recommended Action If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
MBUS Messages
Error Message%PLATFORM-MBUS-7-ATTACH_DEBUG [chars]
Explanation mbus debugging information. %s - debug message
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-7-ATTACH_ERR [chars] ([hex])
Explanation mbus debug info %s - attach error information. %X - error return code
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-7-ATTACH_INFO_DUMP [chars]
Explanation mbus debug info %s - attach statistics
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-7-MSG_INFO_DUMP [chars]
Explanation mbus debug information. %s - is the information being displayed for debug purposes
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-7-MSG_INFO_DUMP [chars]
Explanation mbus debug information. %s - is the information being displayed for debug purposes
Recommended Action No action is required.
Error Message%PLATFORM-MBUS-7-MSG_INFO_DUMP [chars]
Explanation mbus debug information. %s - is the information being displayed for debug purposes
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
NFEA_HW_PROG Messages
Error Message%PLATFORM-NFEA_HW_PROG-5-MAX_LIMIT Exceeding max [chars]
Explanation This message indicates that the configuration is exceeding the maximum Sampling Rate of 4 or the maximum Flow Sampler limit of 16 in a given direction.
Recommended Action To configure new sampling rate or new Sampler info, unconfigure the existing Sampler info / Sampling rate and configure with the new one.
PRP_HW Messages
Error Message%PLATFORM-PRP_HW-3-INIT_ERROR Performance route processor initialization failed: ([chars]%s)
Explanation Performance Route Processor (PRP) drivers failed to initialize. The effect is that PRP will not function. %s - indicates the reason for the failure. %s - is the error reason.
Recommended Action The System Manager process (sysmgr) will not respawn this process. Try to reload the PRP first. If it does not recover, power recycle the router. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
SYSLDR_LC Messages
Error Message%PLATFORM-SYSLDR_LC-2-NODE_RELOAD Reload notification received. Reloading in [dec] secs
Explanation Message indicating that the kAA on the card has received a reload notification from sysldr for powering off the card and the card is going to reload soon. card state is IOX_RUNNING
Recommended Action Sysldr log needs to be looked into to investigate on the node reload cause. As, sysldr requests to reload the card for various reasons.
Error Message%PLATFORM-SYSLDR_LC-2-NODE_RELOAD_NOW Node delay time over, reloading now
Explanation Message indicating that the node has received a reload notification and the node is going to reload soon. This message is logged after the delay over since the NODE_RELOAD message is logged.
Recommended Action Sysldr log needs to be looked into to investigate on the node reload cause. As, sysldr requests to reload the card for various reasons.
Error Message%PLATFORM-SYSLDR_LC-3-FATAL [chars]
Explanation A fatal error was encountered, and the program exited. Error in thread creation for mbi-hello process.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR_LC-7-ERR_MSG_SEND msg_send failed to server : [chars]
Explanation Call failed to send message to MBI-Hello LWM server.
Recommended Action The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.
Error Message%PLATFORM-SYSLDR_LC-7-ERR_SERVER_CONNECT Failed to connect to server : [chars]
Explanation A communication problem occurred between the MBI client and server, perhaps because the communications infrastructure is not set up. The MBI operation in progress will not be carried out.
Recommended Action The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.
Error Message%PLATFORM-SYSLDR_LC-7-TIMER_TIMEOUT Timer timed out from server : [chars]
Explanation Timer timed out between the MBI client and server, perhaps because the communications infrastructure is not set up. The MBI operation in progress will not be carried out.
Recommended Action The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.
Error Message%PLATFORM-SYSLDR_LC-7-TIMER_TIMEOUT_MDR Timeout is ignored due to Warm Reload
Explanation Ping request is not received from RP. It's not normal but expected under Warm Reload situation. Only when Warm Relad fails, please collect information.
Recommended Action If Warm Reload fails, please collect admin show sysldr warm-reload
Error Message%PLATFORM-SYSLDR_LC-7-WARNING [chars]
Explanation KAA process failed to collect the Fabric ping diagnostic date.
Recommended Action No action is required.
SYSLDR_RP Messages
Error Message%PLATFORM-SYSLDR_RP-1-NODE_RELOAD_NOW Node delay time over, reloading now
Explanation Message indicating that the PRP has received a reload notification and it is going to be reloaded soon. This message is logged after the delay over since the NODE_RELOAD message is logged.
Recommended Action Sysldr log needs to be looked into to investigate on the node reload cause. As, sysldr requests to reload the card for various reasons.
Error Message%PLATFORM-SYSLDR_RP-2-NODE_RELOAD Reload notification received. Reloading in [dec] secs
Explanation Message indicating that the mbi-hello on the standby PRP has received a reload notification from sysldr for powering off the card and the card is going to reload soon. The card is in MBI-RUNNING state.
Recommended Action Sysldr log needs to be looked into to investigate on the node reload cause. As, sysldr requests to reload the card for various reasons.
Error Message%PLATFORM-SYSLDR_RP-7-ERR_MSG_SEND msg_send failed to server : [chars]
Explanation A communication problem occurred between the MBI client and server. The MBI operation in progress will not be carried out.
Recommended Action The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.
Error Message%PLATFORM-SYSLDR_RP-7-ERR_SERVER_CONNECT Failed to connect to MBI ping server : [chars]
Explanation A communication problem occurred between the MBI client and server, perhaps because the communications infrastructure is not set up. The MBI operation in progress will not be carried out.
Recommended Action The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.
Error Message%PLATFORM-SYSLDR_RP-7-FATAL [chars]
Explanation A fatal error was encountered, for mbi-hello process on standby RP and the program exited.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR_RP-7-TIMER_TIMEOUT Timer timed out from MBI ping server : [chars]
Explanation Timer timed out between the MBI client and server, perhaps because the communications infrastructure is not set up. The MBI operation in progress will not be carried out.
Recommended Action The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.
Error Message%PLATFORM-SYSLDR_RP-7-WARNING [chars]
Explanation Unexpected low severity problem.
Recommended Action No action is required.
SYSLDR Messages
Error Message%PLATFORM-SYSLDR-1-SELF_PING_FAILURE slot [dec]: self ping failure, failover and reloading
Explanation Self fabric ping is failed for the active RP. The chassis will be reloaded with non redundant RP chassis or the failover will happen with the redundant RP chassis.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-2-MBI_NETWORK_DOWN slot [dec]: network connection to MBI down, reloading
Explanation Fabric ping failure for the card, which was in MBI-RUNNING state.
Recommended Action This indicates a problem in MBI communication. A user can try 'hardware-module ' once to retry loading of the card, for reconnection of the fabric ping.
Error Message%PLATFORM-SYSLDR-2-MBI_NOLOAD slot [dec]: MBI cannot load IOX, retrying by reloading
Explanation It is inability of MBI to boot a node's full image.
Recommended Action This indicates a problem in communication or installation. Tech support should be contacted. Several attempts will be made to retry the image loading, and then the card will be put in the 'reset' state after too many failures.
Error Message%PLATFORM-SYSLDR-2-NETWORK_DOWN slot [dec]: network connection down, reloading
Explanation Fabric ping failure for the card, which was in IOX-RUNNING state. Card network is non-responsiveness.
Recommended Action This indicates a problem in qnet communication. A user can try 'hardware-module ' once to retry loading of the card, for reconnection of the fabric ping.
Error Message%PLATFORM-SYSLDR-3-BANDWIDTH_SHUTDOWN Fabric bandwidth change: Shutting down card in slot [dec]
Explanation Loss or OIR of one or more fabric cards has led to the card being shut down
Recommended Action Inspect the SFC and CSC cards.
Error Message%PLATFORM-SYSLDR-3-ENVMON_FCTL_SHUTDOWN Shutting down card in slot [dec], ordered by Envmon/FCTL
Explanation Card is shut down by Envmon or FCTL
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-3-ENVMON_SHUTDOWN Shutting down card in slot [dec], ordered by Envmon.
Explanation Volatile shutdown was ordered by Envmon because environmental problems (with temperature, voltage, power etc) were detected.
Recommended Action Investigate the problems reported by Envmon and correct them. After they are corrected, reload the LC using the 'hardware-module reload' command.
Error Message%PLATFORM-SYSLDR-3-ERROR slot[dec]: [chars], errno=[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 diagnostic binary image download errors.
Recommended Action Initiate the diagnostic again using the 'admin diag' CLI and capture the sysldr log.
Error Message%PLATFORM-SYSLDR-3-FW_NOTFOUND Unable to locate mbus firmware file
Explanation mbus firmware (aka 'ucode') file cannot be found
Recommended Action Obtain sysldr-rp software upgrade.
Error Message%PLATFORM-SYSLDR-3-HARD_FAILURE Hardware error on slot [dec] - stopping
Explanation Card is shutdown due to persistent hardware errors.
Recommended Action Notify your customer support representative.
Error Message%PLATFORM-SYSLDR-3-LOW_LC_MEM slot [dec]: [dec]M present, min [dec]M, [chars]LC not loaded
Explanation For indicating insufficient LC CPU (ie. dram) memory
Recommended Action Upgrade the amount of CPU (dram) memory on the LC.
Error Message%PLATFORM-SYSLDR-3-MALFUNCTION_SHUTDOWN Shutting down card in slot [dec], card is malfunctioning.
Explanation Volatile shutdown was ordered by FCTL because card is malfunctioning.
Recommended Action Investigate the reason for malfunctioning and correct the problem. After they problem is corrected, reload the LC using the 'hardware-module reload' command.
Error Message%PLATFORM-SYSLDR-3-MANY_RESTARTS slot [dec]: too many reload attempts - stopping
Explanation For indicating too many restarts problem.
Recommended Action Ensure that the affected LC is supported. If so, this indicates a problem, and tech support should be contacted. A user could try 'hardware-module ' once to retry loading of the LC.
Error Message%PLATFORM-SYSLDR-3-MBUS_PING_WARN slot [dec]: CPU 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 communication w/ the card's CPU via MBUS. 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 The card network is non-responsiveness and the fabric ping is failed. The card is not reloaded because of 'service sysldr fabric-ping warn' configuration. This indicates a problem in qnet communicaton.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-3-NOT_RESPONDING slot [dec]: [chars] CPU not responding, reloading
Explanation For displaying notification of card software non-responsiveness.
Recommended Action This indicates a problem in communication w/ the card's CPU via MBUS. A user can try 'hardware-module ' once to retry loading of the card.
Error Message%PLATFORM-SYSLDR-3-SHUTDOWN Shutting down card in slot [dec], shutdown configured.
Explanation Shutdown was configured using the 'hw-module shut' command.
Recommended Action Ensure the shutdown was expected.
Error Message%PLATFORM-SYSLDR-3-TOO_LARGE slot [dec]: LC image too large, not loading
Explanation For displaying notification of LC image being to large to download.
Recommended Action Obtain a properly built image set.
Error Message%PLATFORM-SYSLDR-3-UNKNOWN_MOD slot=[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]), [chars]
Explanation For displaying down-rev notification.
Recommended Action Ensure that upgrade instructions are followed properly
Error Message%PLATFORM-SYSLDR-4-MBUS_FW slot [dec]: unsupported mbus fw v[dec].[dec] found, replacing ...
Explanation Found an unsupported mbus firmware version running.
Recommended Action No action required. To prevent, do not run IOS images prior.
Error Message%PLATFORM-SYSLDR-4-MBUS_IN_ROM slot [dec]: mbus agent in ROM, downloading RAM mbus fw v[dec].[dec] ...
Explanation Make sure to keep mbus agent running from RAM fw image
Recommended Action No action required. To prevent, do not run IOS images prior.
Error Message%PLATFORM-SYSLDR-4-NO_AUTO_RESET slot [dec]: card failed, auto-reset disabled, needs 'hardware-module location r/s/i reload'
Explanation Warning a user that a card has failed while they have disabled auto-reset.
Recommended Action If auto-reset disable was not intended, it should be unconfigured. 'hardware-module reload' will get a card out of the terminal UNMONITORED state.
Error Message%PLATFORM-SYSLDR-4-NO_RELOAD_SIM_OIR slot [dec]: LC failed, simulated OIR has been requested - LC is now admin-down
Explanation Warning a user that a card has failed while they have turned on 'simulated-OIR'
Recommended Action If similated OIR was not intended, it should be unset. 'hardware-module reload' will get a card out of the ADMIN-DOWN state that this triggers.
Error Message%PLATFORM-SYSLDR-4-SPA_WARNING slot[dec]: [chars]
Explanation Unexpected low severity problem.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-4-UNSUPPORTED slot [dec]: LC type currently unsupported
Explanation For displaying notification of software non-support.
Recommended Action Ensure that the affected LC is supported. If so, this indicates a problem, and tech support should be contacted. A user could try 'hardware-module ' once to retry loading of the LC.
Error Message%PLATFORM-SYSLDR-4-WARM_RLD_FAILED Receive DOWNLOAD_SUCCESS from slot [dec], while waiting for DOWNLOAD_SUCCESS_WARM
Explanation Card seems to have been cold reloaded after an attempt to warm reload the card.
Recommended Action Capture the sysldr log and use the 'show sysldr trace warm-reload' CLI in admin-mode to fetch debug information. Also capture sysmgr_nv.log from LC.
Error Message%PLATFORM-SYSLDR-4-WARN_LC_MEM slot [dec]: [dec]M present, recommend [dec]M memory
Explanation For indicating possibly insufficient LC CPU (ie. dram) memory
Recommended Action Upgrade the amount of CPU (dram) memory on the LC.
Error Message%PLATFORM-SYSLDR-4-WARN2 [chars]
Explanation Unexpected low severity problem.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-5-BANDWIDTH Fabric bandwidth change: [chars]
Explanation Failure/recovery/OIR of one or more SFC's or CSC's
Recommended Action Verify that the desired fabric bandwidth is being used.
Error Message%PLATFORM-SYSLDR-5-BANDWIDTH_RESTART Fabric bandwidth change: Restarting card in slot [dec]
Explanation Restoration or OIR of fabric bandwidth has allowed a card to be restarted
Recommended Action Celebrate.
Error Message%PLATFORM-SYSLDR-5-DRP_DISABLED DRP in slot [dec] is now disabled, reloading
Explanation The RP is going to bring down from IOX running state because keep alive message ping is not received to sysldr.
Recommended Action Ensure that the disabling of this DRP was expected.
Error Message%PLATFORM-SYSLDR-5-JOIN Joined slot [dec] - already running IOX-LC
Explanation LC join notification because of sysldr restarted.
Recommended Action Ensure that the *sysldr* restart was expected.
Error Message%PLATFORM-SYSLDR-5-LC_ENABLED LC in slot [dec] is now running IOX
Explanation For displaying health and readiness of LC
Recommended Action Ensure that the (implied) LC restart was expected.
Error Message%PLATFORM-SYSLDR-5-MBUS_EEPROM slot [dec]: Unable to get mbus eeprom contents
Explanation For displaying notification of mbus nonresponsiveness to get eeprom contents.
Recommended Action This indicates that mbus request to get eeprom contents for show diag command has timed out. Retry the command again.
Error Message%PLATFORM-SYSLDR-5-MON_DRP Now monitoring DRP in slot [dec] - running IOX-DRP
Explanation For displaying notification of discovered DRP.
Recommended Action Ensure that the existence of the external DRP was expected.
Error Message%PLATFORM-SYSLDR-5-MON_RP Now monitoring RP in slot [dec] - running IOX-RP
Explanation For displaying notification of discovered RP.
Recommended Action Ensure that the existence of the external RP was expected.
Error Message%PLATFORM-SYSLDR-5-OIRIN OIR: Node [chars] inserted
Explanation Entity specified in the messages is inserted into the chassis.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-5-OIROUT OIR: Node [chars] removed
Explanation Entity specified in the messages is removed from the chassis.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-5-RESTART Restarted slot [dec] - now running IOX-LC
Explanation For displaying LC restart notification.
Recommended Action Ensure that the LC restart was expected.
Error Message%PLATFORM-SYSLDR-5-RESTART_REQ Accepted restart request for slot [dec]
Explanation For displaying LC restart requests.
Recommended Action Ensure that the *sysldr* restart request was expected.
Error Message%PLATFORM-SYSLDR-5-RP_DISABLED RP in slot [dec] is now disabled, reloading
Explanation The RP is going to bring down from IOX running state because keep alive message ping is not received to sysldr.
Recommended Action Ensure that the disabling of this RP was expected.
Error Message%PLATFORM-SYSLDR-5-RP_ENABLED RP in slot [dec] is now running IOX
Explanation For displaying health and readiness of RP
Recommended Action None
Error Message%PLATFORM-SYSLDR-6-DEBUG slot[dec]: [chars]
Explanation sysldr debugging information.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-6-INFO [chars]
Explanation For displaying sysldr's informational events.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-7-DEBUG_INIT_EVENT_FAILED [chars]: debug_init_event([chars]) failed error [chars]
Explanation Failed to switch ON debug event on sysldr server side.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-7-DEBUG_REGISTER_FAILED [chars]: debug register failed error [chars]
Explanation Failed to register debug events on sysldr server side.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-7-ERR slot[dec]: [chars]
Explanation sysldr encountered an error condition.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-7-ERR_MEM_ALLOC Insufficient memory.
Explanation Unable to allocate more heap memory.
Recommended Action Make sure the application/process memory usage or leak.
Error Message%PLATFORM-SYSLDR-7-ERR_SYSDB_CONNECTION Connection to sysdb path '[chars]' failed: '[chars]'.
Explanation Unable to maintain connection to a critical sysdb path.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-7-ERR_SYSDB_DELETE slot [dec]: sysdb_item_delete failed for item '[chars]' in file=[chars], line=[dec] ([chars] [hex])
Explanation Unable to delete a sysdb item.
Recommended Action 'No action is required.'
Error Message%PLATFORM-SYSLDR-7-ERR_SYSDB_GET slot [dec]: sysdb_item_get failed for item '[chars]' in file=[chars], line=[dec] ([chars] [hex])
Explanation Unable to set a sysdb item.
Recommended Action 'No action is required.'
Error Message%PLATFORM-SYSLDR-7-ERR_SYSDB_NOTIFY Notification for changes to sysdb bindpoint '[chars]', tuple '[chars]' failed: '[chars]'.
Explanation Unable to receive notifications of changes to a critical sysdb tuple.
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-7-ERR_SYSDB_SET slot [dec]: sysdb_item_set failed for item '[chars]' in file=[chars], line=[dec] ([chars] [hex])
Explanation Unable to set a sysdb item.
Recommended Action 'No action is required.'
Error Message%PLATFORM-SYSLDR-7-FATAL [chars], error=[dec]
Explanation Error in thread/event manager creation for sysldr process.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-SYSLDR-7-INTERNAL_ERROR Internal Error. File [chars], line [dec]: [chars].
Explanation Serious internal logic or data error.
Recommended Action 'No action is required.'
Error Message%PLATFORM-SYSLDR-7-WARM_RLD_OK Receive DOWNLOAD_SUCCESS_WARM from slot [dec], new processes are coming up
Explanation Card seems warm reloaded successfully
Recommended Action No action is required.
Error Message%PLATFORM-SYSLDR-7-WARNING slot[dec]: [chars]
Explanation For displaying sysldr debugging information.
Recommended Action No action is required.
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-ERR_MEM_ALLOC Could not complete operation due to lack of memory: Purpose for memory [chars]
Explanation The system is running out of memory and was not able to allocate sufficient memory to carry out a management operation. %s indicates what the memory was intended for.
Recommended Action Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.
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 Packet [unsigned int] too large: size [unsigned int], status [unsigned int]
Explanation An application attempted to send a packet larger than the hardware can handle from the route processor to another card. This usually indicates a software error. packet %u is the packet handle size %u is the packet size status %u is the buffer status flags
Recommended Action de If this error occurs rarely it will not impact service and can be ignored. If it occurs frequently, contact your Cisco support representative and provide the data that has been gathered. Copy the error message exactly as it appears on 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_FREE_ERR The toFab driver failed to return a buffer to the free list. Details: [chars]
Explanation The fabric driver has failed to return a packet buffer to the free list. If this error keeps recurring it could result in the depletion of buffer for packets sent from the route processor to the fabric. %s is the entity processing the packet.
Recommended Action If this error occurs again copy the system messages exactly as they appear, call your Cisco technical support representative. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-TFQ-3-PAK_INVALID Invalid packet sent to the fabric driver. Packet [hex]
Explanation This message indicates that an invalid packet was sent to the driver handling packets to be sent from the router processor card to other cards in the chassis. The packet will be dropped and the system should recover from the error. %x packet handle.
Recommended Action If this error occurs rarely it should not impact service and can be ignored. If it occurs frequently, contact your Cisco support representative and provide the data that has been gathered. Copy the error message exactly as it appears on 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.
Error Message%PLATFORM-TFQ-4-NODEID_INVALID Node identifier is invalid, rc:[dec] node Id [unsigned int] stream:[dec] flags:[unsigned int]
Explanation A packet destined for a remote card was received by the fabric driver. The destination node in the packet header could not be decoded by the ToFab component of the fabric driver on the route processor. This is a software error and the packet will be dropped. rc:%d is the return code of the function that parsed the node. node Id %u is the node identifier received by the driver which failed to parse stream:%d is the message stream over which the packet was sent to the driver. flags %u are flags used by packet manager to identify the packet.
Recommended Action This error does not affect the performance or functionality of the system. No intervention is required. The packets in question will be dropped. Copy the error message exactly as it appears and report it to your Cisco technical representative together with the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-TFQ-5-UNEXPECTED_PKT Unexpected packet has been received by ToFab driver. Type: [dec]
Explanation An unexpected packet type was sent to the ToFab driver This will not impact functionality or performance. It is being reported for informational purposes only. Type: %d is the type of the packet that the driver rejected.
Recommended Action No intervention is required. A log of these messages together with the gathered data should be kept for future reference by your Cisco technical representative.
TIMESYNC_CLIENT Messages
Error Message%PLATFORM-TIMESYNC_CLIENT-4-ERR_CONNECT_ARB failed to connect to the active/standby arbitration process, ([chars])
Explanation The c12000 arbitration process could not be contacted. This process provides the active/standby state information required to decide whether the local time should be aligned to the chassis system time. This problem may cause the system error messages reported by the specified card to be offset in time, or being displayed without a timestamp.
Recommended Action The problem has only minor system impact, and will not affect traffic. The system will retry and normally recover from such a transient error. However, if this message repeats continuously, report the failure to a service representative. Doing a 'process restart timesync_client' or 'process restart psarb-lc' could clear the problem.
Error Message%PLATFORM-TIMESYNC_CLIENT-4-ERR_GET_ARB_STATE unable to get the active/standby arbitration state, ([chars])
Explanation Unable to get the active/standby state from the arbitration process. This process provides the active/standby state information required to decide whether the local time should be aligned to the chassis system time. This problem may cause the system error messages reported by the specified card to be offset in time, or being displayed without a timestamp.
Recommended Action This could indicate an internal software error. The problem has only minor system impact, and will not affect traffic. The system will retry and normally recover from such a transient error. However, if this message repeats continuously, report the failure to a service representative. Doing a 'process restart timesync_client' or 'process restart psarb-lc' could clear the problem.
Error Message%PLATFORM-TIMESYNC_CLIENT-4-ERR_GET_TIME failed to get system time, ([chars])
Explanation An attempt to read the local time has failed. This can prevent local time to be reported as a response to the 'show clock sync' command. It can also prevent alignment of the local time to the chassis system time broadcasted by the dsc. This may cause the system error messages reported by the specified card to be offset in time, or being displayed without a timestamp.
Recommended Action The problem has only minor system impact, and will not affect traffic. The system will retry and normally recover from such a transient error. However, if this message repeats continuously, report the failure to a service representative. Doing a 'process restart timesync_client' could clear the problem.
Error Message%PLATFORM-TIMESYNC_CLIENT-4-ERR_INIT_DSC Failed to learn if we are running on the DSC ([chars])
Explanation This process needs to know if it runs on the DSC or standby DSC. An error occured while trying to get the information from the DSC process. The process will voluntary exit, and should get automatically restarted.
Recommended Action This could indicate an internal software error. The problem has only minor system impact, and will not affect traffic. The timestamp associated with the system messages originating from this card may show a time offset compared to other cards. The system will retry and normally recover from such a transient error. However, if this message repeats continuously, report the failure to a service representative. Doing a 'process restart timesync_client' or 'process restart dsc' could clear the problem.
Error Message%PLATFORM-TIMESYNC_CLIENT-4-ERR_READ_MBUS failed to read a message from MBUS, ([chars])
Explanation A failure was encountered when receiving a message from the MBUS driver. MBUS is the communication service over which chassis system time is broadcasted. This problem may cause the system error messages reported by the specified card to be offset in time, or being displayed without a timestamp.
Recommended Action The problem has only minor system impact, and will not affect traffic. The system will retry and normally recover from such a transient error. However, if this message repeats continuously, report the failure to a service representative.
Error Message%PLATFORM-TIMESYNC_CLIENT-4-ERR_SET_TIME failed to set system time, ([chars])
Explanation An attempt to set the local time has failed. This problem will prevent alignment of the local time to the chassis system time broadcasted by the dsc. This may cause the system error messages reported by the specified card to be offset in time, or being displayed without a timestamp.
Recommended Action The problem has only minor system impact, and will not affect traffic. The system will retry and normally recover from such a transient error. However, if this message repeats continuously, report the failure to a service representative. Doing a 'process restart timesync_client' could clear the problem.
Error Message%PLATFORM-TIMESYNC_CLIENT-4-ERR_WRITE_MBUS failed to write a message to MBUS, ([chars])
Explanation A failure was encountered when sending a message to the MBUS driver. MBUS is the communication service over which chassis system time is exchanged. This problem will cause the local time to be missing in the 'show clock sync' response.
Recommended Action The problem has no system impact, and will not affect traffic. The problem could be transient and caused by an internal process restart. Retry the 'show clock sync' command and see if the problem goes away. If this message repeats every time the 'show clock sync' command is entered, report the failure to a service representative.
TIMESYNC Messages
Error Message%PLATFORM-TIMESYNC-4-ERR_CONNECT_ARB failed to connect to the active/standby arbitration process, ([chars])
Explanation The c12000 arbitration process could not be contacted. This process provides the active/standby state information required to decide whether the local time should be broadcasted over MBUS communication to other cards. This problem may cause other cards in the chassis to have an unaligned time base, and may cause system error messages reported by the other cards to appear offset in time, or to be displayed without a timestamp.
Recommended Action The problem has only minor system impact, and will not affect traffic. The system will retry and normally recover from such a transient error. However, if this message repeats continuously, report the failure to a service representative. Doing a 'process restart timesync_server' is safe and could clear the problem.
Error Message%PLATFORM-TIMESYNC-4-ERR_GET_ARB_STATE unable to get the active/standby arbitration state, ([chars])
Explanation Unable to get the active/standby state from the arbitration process. This process provides the active/standby state information required to decide whether the local time should be broadcasted over MBUS communication to other cards. This problem may cause other cards in the chassis to have an unaligned time base, and may cause system error messages reported by the other cards to appear offset in time, or to be displayed without a timestamp.
Recommended Action This could indicate an internal software error. The problem has only minor system impact, and will not affect traffic. The system will retry and normally recover from such a transient error. However, if this message repeats continuously, report the failure to a service representative. Doing a 'process restart timesync_server' is safe and could clear the problem.
Error Message%PLATFORM-TIMESYNC-4-ERR_GET_TIME failed to get system time, ([chars])
Explanation An attempt to read the local time has failed. This can prevent local time from being broadcasted to other cards in the chassis. This problem may cause other cards in the chassis to have an unaligned time base, and may cause system error messages reported by the other cards to appear offset in time, or to be displayed without a timestamp.
Recommended Action The problem has only minor system impact, and will not affect traffic. The system will retry and normally recover from such a transient error. However, if this message repeats continuously, report the failure to a service representative. Doing a 'process restart timesync_server' is safe and could clear the problem.
Error Message%PLATFORM-TIMESYNC-4-ERR_WRITE_MBUS failed to write a message to MBUS, ([chars])
Explanation A failure was encountered when sending a message to the MBUS driver. MBUS is the communication service over which chassis system time is exchanged. This problem may cause other cards in the chassis to have an unaligned time base, and may cause system error messages reported by the other cards to appear offset in time, or to be displayed without a timestamp.
Recommended Action The problem has minor system impact, and will not affect traffic. The problem could be transient and caused by an internal process restart. The system will retry and normally recover from such a transient error. However, if this message repeats continuously, report the failure to a service representative. Doing a 'process restart timesync_server' is safe and could clear the problem.
Error Message%PLATFORM-TIMESYNC-5-ERR_GET_LR_INFO failed to get Logical Router information, still trying...([chars])
Explanation Logical Router information is required to know if the local time should be broadcasted to other cards in the system. The process failed to get the Logical Router information within what is considered a normal period. This problem may cause other cards in the chassis to have an unaligned time base, and may cause system error messages reported by the other cards to appear offset in time, or to be displayed without a timestamp.
Recommended Action The problem has minor system impact, and will not affect traffic. The problem could be transient and caused by a slower-than-expected boot phase. The system will retry forever and should normally recover from such an error. After 5 minutes, if 'show clock sync' shows that all cards are time-aligned, then the system recovered. If not, doing a 'process restart timesync_server' is safe and could clear the problem. If the problem persists, report the failure to a service representative.
UPGRADE Messages
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 Check the new fabric-loader size.
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 Check the new ROMMON size.
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 Check the new ROMMON size.
Error Message%PLATFORM-UPGRADE-3-RP_WARNING [chars]
Explanation When upgrading the new rommon, RP's rommon will be corrupted if the user reload the RP. So, The user must not reload RP when it's rommon is being upgraded. If RP's rommon is corrupted, it need to be RMEd !!!
Recommended Action The user must not reload RP when it's rommon is being upgraded.
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 required. The upgrade for the fabric-loader should not be tried for this card.
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 No action required. The upgrade for the ROMMON should not be tried for this card.
Error Message%PLATFORM-UPGRADE-7-ERASE_SECTORS Erase sectors fail for [chars]
Explanation The upgrade of the specfied component (ROMMON/Fabric-loader) failed because failed to erase sectors.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-ERASE_SECTORS Erase sectors fail for [chars]
Explanation The upgrade of the ROMMON failed because failed to erase sectors.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-ERR_BUF_READ Failed to read file [chars]
Explanation The upgrade of the specfied component (ROMMON/Fabric-loader) failed because of a file read system call failed.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-ERR_BUF_READ Failed to read file [chars]
Explanation The upgrade of the ROMMON failed because failed to read the file buffer. It will not affect the existing service on the card.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-ERR_CHAN_CREATE Failed to create upgrade ROM channel : [chars]
Explanation Failed to create upgrade ROM channel using event manager.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-ERR_DEBUG_INIT Debug initialization failed
Explanation Initialization of the debug event failed during ROMMON upgrade. This can be observed when the debug is enabled.
Recommended Action No action is required.
Error Message%PLATFORM-UPGRADE-7-ERR_DEBUG_REG Debug registration failed : [chars]
Explanation debug registration call failed during ROMMON upgrade. This can be observed when the debug is enabled.
Recommended Action No action is required.
Error Message%PLATFORM-UPGRADE-7-ERR_EVENT_MGR [chars] : [chars]
Explanation Generic failure of any event manager API.
Recommended Action Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.
Error Message%PLATFORM-UPGRADE-7-ERR_FILE_OPEN Failed to open file [chars] : [chars]
Explanation The upgrade of the specfied component (ROMMON/Fabric-loader) failed because of a system call fails to open the relevant file.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-ERR_FILE_OPEN Failed to open file [chars] : [chars]
Explanation The upgrade of the ROMMON failed because failed to open the image file. It will not affect the existing service on the card.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-ERR_LWM_REPLY Failed to send reply message : [chars]
Explanation KAA process failed to reply back to sysldr client on the upgrade results using LWM.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-ERR_MEM_ALLOC Failed to allocate memory
Explanation This indicates a low memory condition. The upgrade of the specfied component would fail.
Recommended Action Memory on the box must be running low - are there services that can be stopped, or can more memory be added?
Error Message%PLATFORM-UPGRADE-7-ERR_MEM_ALLOC Failed to allocate memory
Explanation This indicates a low memory condition. The upgrade of the specfied component would fail.
Recommended Action Memory on the box must be running low - are there services that can be stopped, or can more memory be added?
Error Message%PLATFORM-UPGRADE-7-FLASH_DEVICE Flash Device is not AM29LV800B - Linecard upgrade won't continue
Explanation The current driver only supports AM29LV800B flash device.
Recommended Action No action is required.
Error Message%PLATFORM-UPGRADE-7-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 Collect information for Routing Processor type.
Error Message%PLATFORM-UPGRADE-7-GET_SLOT Failed to get slot number
Explanation The platform library call to retrieve the slot information failed.
Recommended Action No action is required.
Error Message%PLATFORM-UPGRADE-7-MMAP Failed to map device address : [chars]
Explanation A system call failed to map the device physical address.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-MMAP Failed to map device address : [chars]
Explanation A system call failed to map the device physical address.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-MUNMAP Failed to unmap mapped object : [chars]
Explanation A system call failed to un-map the device physical address.
Recommended Action No action is required.
Error Message%PLATFORM-UPGRADE-7-MUNMAP Failed to unmap mapped object : [chars]
Explanation A system call failed to un-map the device physical address.
Recommended Action No action is required.
Error Message%PLATFORM-UPGRADE-7-PROGRAM_FLASH Programming flash fail for [chars]
Explanation The upgrade of the specfied component (ROMMON/Fabric-loader) failed because failed in programming flash.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-PROGRAM_FLASH Programming flash fail for [chars]
Explanation The upgrade of the ROMMON failed because failed to erase sectors.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-PROGRAM_FLASH_HEADER Programming flash header fail for [chars]
Explanation The upgrade of the specfied component (ROMMON/Fabric-loader) failed because failed in programming flash header.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-STAT Failed to access file [chars] : [chars]
Explanation The upgrade of the specfied component (ROMMON/Fabric-loader) failed because of file download statistic system call failure.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-STAT Failed to access file [chars] : [chars]
Explanation The upgrade of the ROMMON failed because failed to get file stat. It will not affect the existing service on the card.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-STATUS_SEND Failed to send status
Explanation The KAA process failed to send the upgrade status to the client, sysldr.
Recommended Action The sysldr log needs to be refered for the explanation. The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-VERIFY_FLASH Verify flash fail for [chars]
Explanation The upgrade of the specfied component (ROMMON/Fabric-loader) failed because failed to verify flash.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-VERIFY_FLASH Verify flash fail for [chars]
Explanation The upgrade of the ROMMON failed because failed to verify FLASH.
Recommended Action The upgrade commands needs to be retried on RP.
Error Message%PLATFORM-UPGRADE-7-VERIFY_FLASH_HEADER Verify flash header fail for [chars]
Explanation The upgrade of the specfied component (ROMMON/Fabric-loader) failed because failed to verify flash header.
Recommended Action The upgrade commands needs to be retried on RP.
