Cisco IOS XR System Error Message Reference Guide, Release 3.5
Platform Messages
Downloads: This chapterpdf (PDF - 1.51MB) The complete bookPDF (PDF - 18.83MB) | Feedback

Platform Messages

Table Of Contents

Platform Messages

ALPHA_DISPLAY Messages

ASM Messages

BCM_SWITCH Messages

BP_SERVER Messages

CARDMGR Messages

CCTL_ENS Messages

CCTL Messages

CETHHA Messages

CHP Messages

CPUCTRL_PCI Messages

CPUCTRL Messages

CPUCTRLLIB Messages

CSAR Messages

DISCOVERY Messages

DRP_PAIRING_CLIENT Messages

DRP_PAIRING Messages

DSC Messages

DSCMEDIA Messages

EIO Messages

ENVMON_MON Messages

ENVMON Messages

ETH_SRVR Messages

FABIO Messages

FABRIC_CTRL Messages

FAULT_MGR Messages

FAULT Messages

FDIAGS Messages

FFQ Messages

FIB_DBG Messages

FIB_IDB_LIB Messages

FIB_IPV4 Messages

FIB_IPV6 Messages

FIB_LTRACE Messages

G_PLIM_QOS Messages

GSR_FIB_STATS_API Messages

GSR_IPV4_EA Messages

GSR_IPv6_EA Messages

GSR_lc_exmem Messages

GSR_LC_PM Messages

GSR_LIB Messages

GSR_MPLS_EA Messages

GSR_PRP_PM Messages

GSR_TUNNEL_EA Messages

GT_I2C Messages

IPV6_EA Messages

HBAGENT Messages

HFR_IP_EA Messages

HFR_IPV6_EA Messages

HFR_LCPM_SHOW Messages

HFR_MPLS_EA Messages

HFR_PM_TEST Messages

HFR_PM Messages

HSR_ES_CLI Messages

I2C Messages

INV Messages

INVMGR Messages

IPCLC Messages

IPCP_SRVR Messages

IPMCAST Messages

libpcmcia_ide Messages

LIC_UDI Messages

libpcmcia_linux Messages

MBI_HELLO Messages

MBI_LIB_ACCESS Messages

MBI_LIB Messages

MBIMGR Messages

MBUS Messages

MSM Messages

NETIO_LC Messages

NFEA_HW_PROG Messages

obfl Messages

OIRD Messages

PCIMGR Messages

PCMCIA Messages

PCMCIAD Messages

PCTL Messages

PLAT_FIB_MPLS Messages

PLAT_FIB_RP Messages

PLAT_FIB Messages

PLAT_L2FIB_ATOM Messages

PLAT_L2FIB_DEBUG Messages

PLAT_L2FIB_LOCSW Messages

PLAT_L2FIB_LTRACE Messages

PLAT_L2FIB_RP Messages

PLAT_L2FIB Messages

PLAT_V6FIB_RP Messages

PLATFORM_HFR_LIB Messages

PLIM_16P_OC48 Messages

PLATFORM_RP Messages

PM_OS Messages

PLU Messages

PLUTLU Messages

port_cfg Messages

PRP_HW Messages

REEP Messages

ROM_UPGRADE_LIB Messages

ROMMON_BURNER Messages

SCC Messages

SHELFMGR Messages

SPENET Messages

SPWD Messages

SQUID_LOADER Messages

SRP Messages

STP_SHIM Messages

SYSLDR_LC Messages

SYSLDR_RP Messages

SYSLDR Messages

TFQ Messages

TIMESYNC_CLIENT Messages

TIMESYNC Messages

UPGRADE Messages

UPGRADE_FPD Messages

WD Messages

XCVR Messages


Platform Messages


This section contains all Platform related System Error Messages, such as shelf magr, chassis, env ctrl, and so forth. The following facility codes are represented in this module:

ALPHA_DISPLAY Messages

ASM Messages

BCM_SWITCH Messages

BP_SERVER Messages

CARDMGR Messages

CCTL_ENS Messages

CCTL Messages

CETHHA Messages

CHP Messages

CPUCTRL_PCI Messages

CPUCTRL Messages

CPUCTRLLIB Messages

CSAR Messages

DISCOVERY Messages

DRP_PAIRING_CLIENT Messages

DRP_PAIRING Messages

DSC Messages

DSCMEDIA Messages

EIO Messages

ENVMON_MON Messages

ENVMON Messages

ETH_SRVR Messages

FABIO Messages

FABRIC_CTRL Messages

FAULT_MGR Messages

FAULT Messages

FDIAGS Messages

FFQ Messages

FIB_DBG Messages

FIB_IDB_LIB Messages

FIB_IPV4 Messages

FIB_IPV6 Messages

FIB_LTRACE Messages

G_PLIM_QOS Messages

GSR_FIB_STATS_API Messages

GSR_IPV4_EA Messages

GSR_IPv6_EA Messages

GSR_lc_exmem Messages

GSR_LC_PM Messages

GSR_LIB Messages

GSR_MPLS_EA Messages

GSR_PRP_PM Messages

GSR_TUNNEL_EA Messages

GT_I2C Messages

IPV6_EA Messages

HBAGENT Messages

HFR_IP_EA Messages

HFR_IPV6_EA Messages

HFR_LCPM_SHOW Messages

HFR_MPLS_EA Messages

HFR_PM_TEST Messages

HFR_PM Messages

HSR_ES_CLI Messages

I2C Messages

INV Messages

INVMGR Messages

IPCLC Messages

IPCP_SRVR Messages

IPMCAST Messages

libpcmcia_ide Messages

LIC_UDI Messages

libpcmcia_linux Messages

MBI_HELLO Messages

MBI_LIB_ACCESS Messages

MBI_LIB Messages

MBIMGR Messages

MBUS Messages

MSM Messages

NETIO_LC Messages

NFEA_HW_PROG Messages

obfl Messages

OIRD Messages

PCIMGR Messages

PCMCIA Messages

PCMCIAD Messages

PCTL Messages

PLAT_FIB_MPLS Messages

PLAT_FIB_RP Messages

PLAT_FIB Messages

PLAT_L2FIB_ATOM Messages

PLAT_L2FIB_DEBUG Messages

PLAT_L2FIB_LOCSW Messages

PLAT_L2FIB_LTRACE Messages

PLAT_L2FIB_RP Messages

PLAT_L2FIB Messages

PLAT_V6FIB_RP Messages

PLATFORM_HFR_LIB Messages

PLIM_16P_OC48 Messages

PLATFORM_RP Messages

PM_OS Messages

PLU Messages

PLUTLU Messages

port_cfg Messages

PRP_HW Messages

REEP Messages

ROM_UPGRADE_LIB Messages

ROMMON_BURNER Messages

SCC Messages

SHELFMGR Messages

SPENET Messages

SPWD Messages

SQUID_LOADER Messages

SRP Messages

STP_SHIM Messages

SYSLDR_LC Messages

SYSLDR_RP Messages

SYSLDR Messages

TFQ Messages

TIMESYNC_CLIENT Messages

TIMESYNC Messages

UPGRADE Messages

UPGRADE_FPD Messages

WD Messages

XCVR Messages

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-0-FAULT_RECOVERY_ERR The fault recovery procedure for the FromFab component of the fabric driver has failed. The root fault was: [chars]

Explanation    When a hardware fault occurs and the device driver cannot correct it, the Platform Manager is required to reset the ASICs. This error indicates that the Platform Manager failed to reset the ASICs and the hardware on the PRP may not be in an operational state. This condition affects the functionality of the entire router. %s is the Interrupt Source.

Recommended Action    If the system has not failed over automatically and a redundant route processor card has been configured: 1 - force a failover with the following command in admin mode: 'redundancy switchover' 2 - reload the route processor card that failed with the following command in admin mode: 'reload location RP/0/x/CPU0 ' where x is the slot of route processor that generated the error. If no redundant RP is configured you will need to reboot the router by issuing the reload command. Call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-ASM-0-SW_INIT_ERR A software error occurred in the FrFab driver component during initialization: [chars]

Explanation    The fabricq_prp_driver process which controls the FromFab driver on the route processor has failed to initalize and cannot recover automatically. This is a software fault. The FromFab driver controls the hardware that receives data from the fabric. It runs in the fabricq_prp_driver process. An unrecoverable failure of the fabricq_prp_driver process may prevent this route processor card from communicating with other cards on the chassis. %s indicates the type failure

Recommended Action    Restart the fabricq_prp_driver process with the following command: 'process restart fabricq_prp_driver' If the error message appears again, then: if a redundant route processor card has been configured: 1 - force a failover with the following command in admin mode: 'redundancy switchover' 2 - reload the route processor card that failed with the following command in admin mode: 'reload location RP/0/x/CPU0 ' where x is the slot of route processor that generated the error. if no redundant RP is configured you will need to reboot the router by issuing the reload command. If the error recurs call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-ASM-3-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.

BCM_SWITCH Messages

Error Message     
 
    
    
   

%PLATFORM-BCM_SWITCH-6-LINK_STATE_CHANGE Spanning Tree Port [chars] state changed to [chars]

Explanation    Spanning Tree Port's state change indication.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-BCM_SWITCH-7-PCI_ERR PCI fatal error seen on switch [dec] DMA channel [dec] type [chars]

Explanation    The switch encountered a PCI error during a DMA transaction.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

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.

CARDMGR Messages

Error Message     
 
    
    
   

%PLATFORM-CARDMGR-3-BAD_CS_INFO could not get CS revision info!

Explanation    Could not get CS revision info

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CARDMGR-3-CHDIR_FAILED chdir to [chars] failed: [chars]

Explanation    Chdir failed

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CARDMGR-3-MODULE_UNAVAILABLE module [chars] not available

Explanation    Module unavailable

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CARDMGR-3-NO_CARDS_DEFINED no cards defined

Explanation    No cards defined

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CARDMGR-3-NO_DRIVERS_FOUND no device drivers defined

Explanation    No device drivers

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CARDMGR-3-NO_SOCKETS no sockets found!

Explanation    No sockets

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CARDMGR-3-PCMCIA_INIT_ERROR PCMCIA initialization error at: [chars]

Explanation    PCMCIA initialization error

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CARDMGR-3-SELECT_FAILURE select (): [chars]

Explanation    Select failure

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CARDMGR-3-UNSUPPORTED_CARD Unsupported card in socket [dec]

Explanation    Unsupported card

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CARDMGR-6-PRODUCT_INFO product info: [chars]

Explanation    Product info

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-CARDMGR-6-SOCKET_INFO socket [dec]: [chars]

Explanation    Socket info

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-CARDMGR-7-ADJ_RES_FAILED could not adjust resource: [chars]: [chars]

Explanation    Could not adjust resource

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CARDMGR-7-BAD_OPEN could not open [chars]: [chars]

Explanation    Open of file failed

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CARDMGR-7-BIND_FAILED bind '[chars]' to socket [dec] failed: [chars]

Explanation    Bind failed

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CARDMGR-7-BIND_MTD_REGION_FAILED bind MTD '[chars]' to region at [hex] failed: [chars]

Explanation    Bind mtd region failed

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CARDMGR-7-BIND_MTD_SOCKET_FAILED bind MTD '[chars]' to socket [dec] failed: [chars]

Explanation    Bind mtd to socket failed

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CARDMGR-7-CIS_DATA_PARSING_ERROR error parsing CIS([hex]) on socket [dec]: [chars]

Explanation    CIS data parsing error

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CARDMGR-7-CIS_DATA_READ_ERROR error reading CIS data on socket [dec]: [chars]

Explanation    CIS data read error

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CARDMGR-7-CIS_REPLACE_ERROR could not replace CIS: [chars]

Explanation    CIS replace error

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CARDMGR-7-CS_REL_MISMATCH Card Services release does not match

Explanation    Release mismatch

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CARDMGR-7-GET_DEV_INFO_FAILED get device info on socket [dec] failed: [chars]

Explanation    Device info failed

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CARDMGR-7-NO_MEM Malloc failure

Explanation    Out of memory

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CARDMGR-7-OPEN_SOCK_FAILED open_sock(socket [dec]) failed: [chars]

Explanation    Open of socket failed

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CARDMGR-7-READ_FAILED read ([dec]): [chars]

Explanation    Read failed

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CARDMGR-7-THREAD_CREATE_FAILED Thread create failed: [chars]

Explanation    Thread create failed

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CARDMGR-7-UNBIND_FAILED unbind '[chars]' from socket [dec] failed: [chars]

Explanation    Unbind failed

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CARDMGR-7-UNBIND_MTD_FAILED unbind MTD '[chars]' from socket [dec] failed: [chars]

Explanation    Unbind MTD failed

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

CCTL_ENS Messages

Error Message     
 
    
    
   

%PLATFORM-CCTL_ENS-3-ERROR_EXIT Envmon process exiting because [chars], error code [chars]

Explanation    The Chassis Control driver process exited due to the reason mentioned in the message.

Recommended Action    The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. Execute 'show process envmon location ' to verify that the process is up and running. If it is still non-operational, try doing from the admin mode 'process restart envmon location '. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CCTL_ENS-7-OPERATION_FAIL Failed to [chars], error code [chars]

Explanation    The particular operation mentioned in the message failed due to some reason. This is not a critical failure, the process can continue functioning as expected despite the failure.

Recommended Action    Debug message only. No action is required.

CCTL Messages

Error Message     
 
    
    
   

%PLATFORM-CCTL-2-CHASSIS_SHUTDOWN_FAIL Unable to shutdown chassis because [chars]

Explanation    The shutdown of the chassis was unsuccessful due to the mentioned reason.

Recommended Action    Chassis shutdown is typically initiated due to some critical failure. If the software initiated chassis shutdown has failed, then user should intervene and shut down the chassis manually.

Error Message     
 
    
    
   

%PLATFORM-CCTL-2-STANDBY_SHUTDOWN_FAILED Unable to shutdown the standby node as part of chassis shutdown

Explanation    The shutdown of the standby SC/RP node failed during the chassis shutdown process.

Recommended Action    Please power off the chassis manually.

Error Message     
 
    
    
   

%PLATFORM-CCTL-3-ERROR_EXIT Envmon process exiting because [chars], error code [chars]

Explanation    The Chassis Control driver process exited due to the reason mentioned in the message.

Recommended Action    The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover. Execute 'show process envmon location ' to verify that the process is up and running. If it is still non-operational, try doing from the admin mode 'process restart envmon location '. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CCTL-3-READ_POWER_SHELF_TYPE_FAILURE Unable to detect power shelf type. Assuming AC shelf and continuing for now. Please check EEPROM programming on power shelf backplane.

Explanation    We are unable to read the power shelf backplane EEPROM for some reason. Need to check the programming of the backplane.

Recommended Action    Check that the power-shelf is seated correctly, and that the backplane EEPROM is programmed correctly. In the admin mode, use 'show diag power-supply eeprom-info' to check the contents of the EEPROM.

Error Message     
 
    
    
   

%PLATFORM-CCTL-4-UNKNOWN_SHELF_ID Unknown shelf ID [hex] read from power shelf backplane EEPROM - please check EEPROM programming.

Explanation    The value read from the power shelf backplane does not match any of the known shelf ID values. Please check the EEPROM programming.

Recommended Action    Please check the EEPROM programming of the power-shelf backplane. 'show diag power-supply eeprom-info' in admin mode gives a raw dump of the EEPROM data. Refer EDCS-137763 to interpret the data to check if the shelf ID is programmed correctly or not. If the shelf ID is incorrect, the unit will have to be RMA'd to reprogram the EEPROM correctly.

Error Message     
 
    
    
   

%PLATFORM-CCTL-6-TEMP_ALARM [chars] alarm occured for [chars] sensor at temperature [dec] deg C, against configured threshold of [dec] deg C

Explanation    Informational msg indicating temperature at which alarm occured.

Recommended Action    Software will take corrective action on its own. No action is required.

Error Message     
 
    
    
   

%PLATFORM-CCTL-7-OPERATION_FAIL Failed to [chars], error code [chars]

Explanation    The particular operation mentioned in the message failed due to some reason. This is not a critical failure, the process can continue functioning as expected despite the failure.

Recommended Action    Debug message only. No action is required.

CETHHA Messages

Error Message     
 
    
    
   

%PLATFORM-CETHHA-2-CRITICAL Hardware error on control-ethernet port [chars]

Explanation    Hardware error on CPU control ethernet port.

Recommended Action    Remove/Replace the RP.

Error Message     
 
    
    
   

%PLATFORM-CETHHA-4-NOGE RP does not have GE connectivity

Explanation    RP does not have GE connectivity. Reload/failovers may cause problems.

Recommended Action    Check the GE connections on the front panel of the RP/SC and re-connect/replace to make sure atleast one GE connection is there.

CHP Messages

Error Message     
 
    
    
   

%PLATFORM-CHP-0-FAULT_RECOVERY_ERR The fault recovery procedure for the ToFab component of the fabric driver has failed. The root fault was: [chars]

Explanation    When a hardware fault occurs and the device driver cannot correct it, the Platform Manager is required to reset the ASICs. This error indicates that the Platform Manager failed to reset the ASICs and the hardware on the PRP may not be in an operational state. This condition affects the functionality of the entire router. %s is the Interrupt Source.

Recommended Action    If the system has not failed over automatically and a redundant route processor card has been configured: 1 - force a failover with the following command in admin mode: 'redundancy switchover' 2 - reload the route processor card that failed with the following command in admin mode: 'reload location RP/0/x/CPU0 ' where x is the slot of route processor that generated the error. If no redundant RP is configured you will need to reboot the router by issuing the reload command. Call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CHP-3-CRC_ERR chopper dll: block: [chars], entity: [chars] had CRC error, count: [dec]

Explanation    PII block got a packet from the entity mentioned above with a CRC error.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%PLATFORM-CHP-3-DEVICE_HALT TFQ: device halted, sub-block: [chars], halted entity: [chars]

Explanation    TFQ, ASIC got halted. The halted block and its parent block are provided

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CHP-3-DMA_ERR Chopper detected a DMA error: Data [hex]

Explanation    This message indicates that the Chopper hardware found a DMA problem. The hexadecimal data indicates the error register value when the problem is detected. This usually indicates a hardware error.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CHP-3-FATAL chopper dll: fatal error encountered, reason=[chars]

Explanation    iqm, chopper dll manager encountered a fatal error and is not able recover from the error. A reason text will be supplied call support with this text.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CHP-3-FATAL_2 chopper dll: fatal error encountered, reason=[chars], errno=[dec]

Explanation    chopper encountered a fatal error and is not able to recover from the error. A reason text will be supplied call support with this text. An integer errno will also be printed.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CHP-3-FUSILLI_PARITY_ERR Chopper detected a Fusilli parity error: Data [hex]

Explanation    A parity error has been detected on the Chopper to Fusilli interface. The hex number indicates the error cause register value. This usually indicates a hardware problem on the RP. RP may be reset.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CHP-3-GEN_INFO chopper dll: general information,

Explanation    The CHP's informational message.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CHP-3-HWINIT_INCOMPLETE chopper dll: hardware initialization not complete

Explanation    hardware init is not complete.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%PLATFORM-CHP-3-INFO chopper dll: service degrading error, reason = [chars]

Explanation    The chopper encountered an error that would lead to degraded service.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CHP-3-INTR_ENABLE_FAIL chopper dll: intr enable at addr: [hex] mask: [hex] failed.

Explanation    hardware state is not correct.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%PLATFORM-CHP-3-INTR_STATUS_GET_ERR chopper dll: intr status get failed for: [chars]@[hex], rc=[dec]

Explanation    Hardware register read failed.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%PLATFORM-CHP-3-MALLOC_FAILED chopper dll: fatal memory allocation error for bytes

Explanation    CHP encountered a fatal memory allocation error

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%PLATFORM-CHP-3-NOT_AVAILABLE chopper dll: asic is not available

Explanation    hardware state is not correct.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%PLATFORM-CHP-3-NOT_OPERATIONAL chopper dll: asic is not operational, state: [dec]

Explanation    hardware state is not correct.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%PLATFORM-CHP-3-NOT_YET_IMPLEMENTED chopper dll: this function is not yet implemented

Explanation    TFQ, chopper dll , a function is not implemented.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CHP-3-PCI_ERR Chopper detected a PCI error: Data [hex]

Explanation    A PCI error has been detected by the Chopper PCI interface. The hex number indicates the error cause register value. This usually indicates a hardware problem on the RP. RP may be reset.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CHP-3-SRAM_PARITY_ERR Chopper detected a SRAM parity error: Data [hex]

Explanation    A parity error has been detected on the Chopper to SRAM interface. The hex number indicates the error cause register value. This usually indicates a hardware problem on the RP. RP may be reset.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CHP-6-UNHANDLED_HALT chopper dll: halt not handled, parent: [chars], child: [chars], intr: [dec]

Explanation    Hardware halt is not handled.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%PLATFORM-CHP-6-UNHANDLED_INTR chopper dll: intr not handled, parent: [chars], child: [chars], group id: [dec], intr: [dec]

Explanation    Hardware interrupt is not handled in the code, need to implement.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

CPUCTRL_PCI Messages

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL_PCI-3-FAILED_S cpuctrl PCI: [chars]

Explanation    CPUCTRL PCI, this function has failed.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL_PCI-3-FAILED_SD cpuctrl PCI: [chars] [dec]

Explanation    CPUCTRL PCI, this function has failed.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL_PCI-6-LOG_S cpuctrl PCI: [chars]

Explanation    CPUCTRL PCI, event logging.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL_PCI-6-LOG_SD cpuctrl PCI: [chars] [dec]

Explanation    CPUCTRL PCI, event logging.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL_PCI-6-LOG_SS cpuctrl PCI: [chars] [chars]

Explanation    CPUCTRL PCI, event logging.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL_PCI-6-LOG_SXX_1 cpuctrl PCI: [chars] [hex] [hex]

Explanation    CPUCTRL PCI, event logging.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL_PCI-6-LOG_SXX_8 cpuctrl PCI: [chars] [hex] [hex]

Explanation    CPUCTRL PCI, event logging.

Recommended Action    No action is required.

CPUCTRL Messages

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-CDMA_RAM_CORRECTABLE_ERROR Cpuctrl HW detected SBE in [chars] RAM. Key: [hex]
[chars]

Explanation    Indicates a correctable single-bit error occurred on this internal SRAM. The error is corrected transparently. The location will be written automatically before being read again.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-CDMA_RAM_PARITY_ERROR Cpuctrl HW detected parity in [chars] RAM. Key: [hex]
[chars]

Explanation    Indicates an uncorrectable parity error occurred on this internal SRAM.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-CDMA_RAM_UNCORRECTABLE_ERROR Cpuctrl HW detected MBE in [chars] RAM. Key: [hex]
[chars]

Explanation    Indicates an uncorrectable multi-bit error occurred on this internal SRAM.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-ERR_INIT [chars], Reason: [chars]. Exiting.

Explanation    Cpuctrl manager encountered a fatal error and is not able to recover from the error. A reason text will be supplied; please provide this text when calling Cisco support.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-FAULT_REPORT_FAILURE Cannot report CRITICAL fault ([chars]) to PM fault manager

Explanation    Cpuctrl attempted to report a critical fault and was unable to log the message with the fault manager. The message text is supplied.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-HW_DETECTED_ERROR_ISN HW error interrupt Cpuctrl Internal Access failure
interrupt_id = [hex], pci_isnerr_status = [hex]
pci_isnerr_addr_hi = [hex], pci_isnerr_addr_lo = [hex]

Explanation    The cpuctrl driver HW error interrupt handler was invoked and found valid PCI ISN register from a Cpuctrl Internal Access failure.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-HW_DETECTED_ERROR_LINK HW error interrupt link, port = [dec]
interrupt_id = [hex], port_link_error = [hex], port_link_crc_count = [hex]

Explanation    The cpuctrl driver HW error interrupt handler was invoked and found a port with valid link error registers.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-HW_DETECTED_ERROR_PCI_PM HW error interrupt pci pm, port = [dec]
interrupt_id = [hex], pci_pmerr_status = [hex]
pci_pmerr_addr_hi = [hex], pci_pmerr_addr_lo = [hex]

Explanation    The cpuctrl driver HW error interrupt handler was invoked and found valid PCI PM error registers.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-HW_DETECTED_ERROR_PCI_SN HW error interrupt pci sn, port = [dec]
interrupt_id = [hex], pci_snerr_status = [hex]
pci_snerr_addr_hi = [hex], pci_snerr_addr_lo = [hex]

Explanation    The cpuctrl driver HW error interrupt handler was invoked and found valid PCI SN error registers.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-HW_DETECTED_ERROR_PCIX HW error interrupt pcix, port = [dec]
interrupt_id = [hex], pcix_pmerr_comptran_status = [hex], pcix_pmerr_status = [hex]
pcix_pmerr_addr_hi = [hex], pcix_pmerr_addr_lo = [hex]

Explanation    The cpuctrl driver HW error interrupt handler was invoked and found valid PCIX error registers.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-HW_DETECTED_ERROR_PORT HW error interrupt port, port = [dec]
interrupt_id = [hex], port_isn_cause = [hex], port_isn_error = [hex]
port_isn_last_reqhi = [hex], port_isn_last_reqlo = [hex]

Explanation    The cpuctrl driver HW error interrupt handler was invoked and found a port with valid isn error registers.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-HW_GASPP_READ_BUS_ERROR Bus error when attempting User requested GASPP Read, Address = [hex]

Explanation    The user may have entered an invalid address, or else there is a HW problem.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-HW_GASPP_WRITE_ERROR Cpuctrl HW detected error on GASPP write, Address = [hex]

Explanation    The user may have entered an invalid address that is not writable.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-PCI_RAM_CORRECTABLE_ERROR_MASK Cpuctrl HW detected SBE in [chars] RAM. Key: [hex]
[chars]

Explanation    Indicates a correctable single-bit error occurred on this internal SRAM. This memory is considered 'persistent' and requires special handling as described in the 'Data_corrected' row of Table 1.2.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-PCI_RAM_CORRECTABLE_ERROR_OTHER Cpuctrl HW detected SBE in [chars] RAM. Key: [hex]
[chars]

Explanation    Indicates a correctable single-bit error occurred on this internal SRAM. The error is corrected transparently. The location will be written automatically before being read again.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-PCI_RAM_UNCORRECTABLE_ERROR Cpuctrl HW detected MBE in [chars] RAM. Key: [hex]
[chars]

Explanation    Indicates an uncorrectable multi-bit error occurred on this internal SRAM.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-PDMA_RAM_CORRECTABLE_ERROR Cpuctrl HW detected SBE in [chars] RAM. Key: [hex]
[chars]

Explanation    Indicates a correctable single-bit error occurred on this internal SRAM. The error is corrected transparently. The location will be written automatically before being read again.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-PDMA_RAM_PARITY_ERROR Cpuctrl HW detected parity in [chars] RAM. Key: [hex]
[chars]

Explanation    Indicates an uncorrectable parity error occurred on this internal SRAM.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-PDMA_RAM_UNCORRECTABLE_ERROR Cpuctrl HW detected MBE in [chars] RAM. Key: [hex]
[chars]

Explanation    Indicates an uncorrectable multi-bit error occurred on this internal SRAM.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-7-ERR_BAG_REG Bag register failed for rules. Reason: [chars]

Explanation    EDM Bags are used to share information between components using sysdb. This Error indicates that bag registration failed.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-7-ERR_DLL_INIT Dll Initialization for [chars] failed. Reason: [chars]

Explanation    Cpuctrl driver tried to register for a dll but it encountered an error. The driver might lose some of its functionality.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-7-ERR_EVM_CREATE Event Manager create failed for [chars]. Reason: [chars]

Explanation    Cpuctrl Event Manager create error

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-7-ERR_EVM_NOTIFY Event Manager notify failed for [chars]. Reason: [chars]

Explanation    Cpuctrl Event Manager notify error

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-7-ERR_LWM_EVENT_BLOCK LWM Event Manager event block failed. Reason: [chars]

Explanation    Cpuctrl Event Manager event block error

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-7-ERR_SYSDB_EDM_REG Sysdb Register EDM failed. Reason: [chars]

Explanation    Cpuctrl Sysdb Register EDM error

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-7-HW_DETECTED_SPURIOUS_ERROR_PORT HW error interrupt valid on invalid port ([dec])
interrupt_id = [hex]

Explanation    The cpuctrl driver HW error interrupt handler was invoked and found a port with invalid isn error registers.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-7-SPURIOUS_ECCPAR_INTS_THROTTLED Cpuctrl HW detected spurious ECC/PAR interrupts ([dec]). Throttled interrupt.

Explanation    A spruriously high level of ECC/PAR interrupts were detected. The interrupt is throttled to reduce CPU usage.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

CPUCTRLLIB Messages

Error Message     
 
    
    
   

%PLATFORM-CPUCTRLLIB-3-DETECTED_ERROR_PDMA [chars], [dec], port = [dec], queue = [dec]

Explanation    The cpuctrl driver detected an error during packet DMA.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRLLIB-3-HW_DETECTED_ERROR_CDMA HW set the error bit in a CDMA descriptor
CDMA engine = [dec], queue = [dec], index = [dec]
error reg_lo = [hex], error_reg_hi = [hex]

Explanation    CDMA ended in error.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRLLIB-3-HW_DETECTED_ERROR_RX_PDMA HW set the error bit in a RX PDMA descriptor
port = [dec], queue = [dec], index = [dec]

Explanation    The cpuctrl driver detected a buffer marked with an error, possibly a CRC check. The buffer is discarded.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRLLIB-3-INT_WARNING Excess Spurious interrupt on device [chars]

Explanation    The cpuctrllib ASIC Interrupt wrapper has detected that an ASIC driver has not cleared its interrupts at the source for 1000 consecutive times. This is possibly an error in the Driver ISR, that does not process and clear all possible interrupts, or malfunctioning HW. The Interrupt is disabled to prevent the ISR from hogging the CPU.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRLLIB-3-PCI_CONFIGURATION_ERROR Incorrect PCI configuration: [chars]: [dec]

Explanation    Incorrect PCI configuration or a problem with the hardware prevents CPUCTRL from accessing the forwarding ASICs.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRLLIB-3-UNRECOVERED_PIO_ERROR Restarting cpuctrl client [dec] on port [dec] for devid [dec] on unrecovered PIO error notification

Explanation    A PIO error was detected and the responsible client was notified but did not mark the error as recovered. Restarting the client.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRLLIB-4-PORT_INIT_FAILURE Port [dec] could not clear Link errors during init
link_error_reg = [hex], crc_reg = [hex]

Explanation    Port will not operate reliably

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRLLIB-4-PORT_REFRAME_SYNC_FAILURE Port [dec] would not sync on reframe attempt

Explanation    Port will not operate reliably

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRLLIB-4-PORT_REINIT_FAILURE Port [dec] Device chipid mismatch during reframe
id_reg read after reframe = [hex], id_reg during HW discovery = [hex]

Explanation    Port will not operate reliably

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRLLIB-6-NO_BUF_TO_REPLACE RX PDMA Ring out of buf, Port [dec], Q [dec], cur_ind = [dec], tx_ind = [dec], retry [dec]

Explanation    CPUCTRL RX PDMA ring could not replace the buffers. possible low buffer condition.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

CSAR Messages

Error Message     
 
    
    
   

%PLATFORM-CSAR-3-ERROR ERROR [chars]

Explanation    A generic error has occured. Normal operation is not affected.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CSAR-3-SLOT_SHUTDOWN Fabric disconnected from slot [dec], card shut down

Explanation    There are unrecoverable errors while transmitting to the reported slot. The slot has been disconnected from the switching fabric and the card in the slot is marked for shut down.

Recommended Action    Try moving the card in the reported slot to another slot. If this error follows the card, the card is bad. If the card works in another slot, there could be a hardware problem with the switch fabric cards (CSC and SFC.) Contact your technical support representative in all cases.

Error Message     
 
    
    
   

%PLATFORM-CSAR-3-UCAST_STUCK Unicast fabric transmissions to slot [dec] are stuck

Explanation    This error indicates a (possibly temporary) problem in the switch fabric path between the route processor card reporting error and the card in the reported slot. Usual cause is a bad card in the reported slot. The particular card may be shut down when this error is reported.

Recommended Action    Wait several minutes for corrective action to occur. Ignore repeats of this error while corrective action is taking place. Look for error reports about unicast fabric transmissions to other slots. If transmissions to a single slot are stuck it indicates a hardware problem in that slot. Either the card in that slot is bad or the fabric interface to the slot is bad. Try moving the card in the reported slot to another slot. If this error follows the card, the card is bad. If the card works in another slot, there could be a hardware problem with the switch fabric cards (CSC and SFC.) If there are reports for several slots, it is more likely that the switch fabric cards have a fault. Contact your technical support representative in all cases.

Error Message     
 
    
    
   

%PLATFORM-CSAR-4-DEBUG_FAIL Debug registration failed.

Explanation    An internal registration call returned an error. Debug commands for the CSAR device may not be effective. Normal operation is not affected.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-CSAR-4-MCAST_STUCK Multicast fabric transmissions are stuck

Explanation    This error indicates a (possibly temporary) problem in the interface between the route processor card reporting error and the switch fabric.

Recommended Action    Wait several minutes for corrective action to occur. Ignore repeats of this error while corrective action is taking place. Look for error reports about unicast fabric transmissions and take action as recommended for unicast errors. If this message repeats and there is no unicast error reported, then copy the error message exactly as it appears on the console and report it to your technical support representative.

Error Message     
 
    
    
   

%PLATFORM-CSAR-4-UNKNOWN_INTF Unknown Fabric Interface with slot [dec] and port [dec]

Explanation    An internal call for fabric initialization received unexpected slot/port information. Normal operation is not affected.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

DISCOVERY Messages

Error Message     
 
    
    
   

%PLATFORM-DISCOVERY-0-ERR ASIC-ERR: [chars]

Explanation    System Controller asic detected a critical error that will bring the node down. A reason text will be supplied.

Recommended Action    The board will reset and reboot after encountering this error. Check if the board comes up fine after the reboot. If the board does not reboot, try to reload the board manually using CLI. 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-DISCOVERY-3-RAM_ECC_2BIT ASIC-ERR: RAM error #[dec]: Name = [chars] #[dec]: Description = [chars]

Explanation    Two or more bit ECC error (Uncorrectable) found in a RAM Access.

Recommended Action    This is a critical error which will cause board-reset. Check if the board comes up fine after reload. 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-DISCOVERY-4-CPU_LATCH ASIC-ERR: CPU error #[dec]: Name = [chars] #[dec]: Description = [chars] (info latched and follows)

Explanation    Errors observed on the system controller CPU module. A reason text will be supplied.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-DISCOVERY-4-CPU_NOLATCH ASIC-ERR: CPU error #[dec]: Name = [chars] #[dec]: Description = [chars] (info lost)

Explanation    Errors observed on the system controller CPU module for which information may be lost due to other errors. A reason text will be supplied.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-DISCOVERY-4-DEV_LATCH ASIC-ERR: DEV error #[dec]: Name = [chars] #[dec]: Description = [chars] (info latched and follows)

Explanation    Errors seen on the device bus. A reason text will be supplied.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-DISCOVERY-4-DEV_NOLATCH ASIC-ERR: DEV error #[dec]: Name = [chars] #[dec]: Description = [chars] (info lost)

Explanation    Errors seen on the device bus for which information was lost due to other errors or some other condition.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-DISCOVERY-4-PCI_LATCH ASIC-ERR: PCI[dec] error #[dec]: Name = [chars] #[dec]: Description = [chars] (info latched and follows)

Explanation    Error was observed on the system PCI bus. Error description is provided.

Recommended Action    Check if there are any asic errors or asic drivers restarts observed around this error. Check if process 'pci_bus_mgr' is up and runnning. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-DISCOVERY-4-PCI_NOLATCH ASIC-ERR: PCI[dec] error #[dec]: Name = [chars] #[dec]: Description = [chars] (info lost)

Explanation    Error was observed on the system PCI bus for which detailed infromation was lost due to more errors or some other reason.

Recommended Action    Check if there are any asic errors or asic drivers restarts observed around this error. Check if process 'pci_bus_mgr' is up and runnning. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-DISCOVERY-4-RAM_ECC_1BIT_THRESH ASIC-ERR: RAM error #[dec]: Name = [chars] #[dec]: Description = [chars]

Explanation    Threshhold reached for single bit ECC (Corrected) errors.

Recommended Action    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-DISCOVERY-4-SRAM_PARITY ASIC-ERR: SRAM error #[dec]: Description = [chars]

Explanation    Parity Error detected in SRAM.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-DISCOVERY-7-ASMP_ERR_REGS ASIC-ERR: Addr High [hex] Addr Low [hex] Err Attribute [hex], Cause [hex], Command [hex]

Explanation    Details about the error observed on the PCI bus with Atlantis system controller.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-DISCOVERY-7-ASMP_PCI_DETAILS ASIC-ERR: PCI[dec] error #[dec]: Command: [chars], Error Address: [hex] [hex], Error Attribute: [hex]

Explanation    Details about the error observed on the PCI bus with Atlantis system controller.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-DISCOVERY-7-CPU_DETAILS ASIC-ERR: CPU error #[dec]: Error Address: [hex], Address Parity Bits: [hex], Error Data: [hex] [hex], Data Parity Bits: [hex] [hex]

Explanation    Details about the error seen in CPU module.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-DISCOVERY-7-DEV_DETAILS ASIC-ERR: DEV error #[dec]: Error Address: [hex]

Explanation    Details on the device bus error.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-DISCOVERY-7-INFO ASIC-ERR: [chars], [dec]

Explanation    Information message from Discovery driver on software error condition.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-DISCOVERY-7-PCI_DETAILS ASIC-ERR: PCI[dec] error #[dec]: Command: [chars], Byte Enables: [hex] [hex], Error Address: [hex] [hex], Error Data: [hex] [hex], Parity Bits: [hex] [hex]

Explanation    Details about the error observed on the PCI bus.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-DISCOVERY-7-RAM_DETAILS ASIC-ERR: RAM error #[dec]: Error Address: [hex], Error Data: [hex] [hex], Recorded ECC Bits: [hex], Calculated ECC Bits: [hex]

Explanation    Details about the ECC error happenned before.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-DISCOVERY-7-SRAM_DETAILS ASIC-ERR: RAM error #[dec]: Error Address: [hex] [hex], Error Data: [hex] [hex], Parity Bits: [hex]

Explanation    Details on SRAM parity error.

Recommended Action    No action is required.

DRP_PAIRING_CLIENT Messages

Error Message    
 
    
    
   

%PLATFORM-DRP_PAIRING-6-NON_DRP_NODE WARNING: A node with unknown type or a non DRP node [chars] is used for drp pairing configuration

Explanation    DRP_PAIRING process will output this informational message during drp pairing configuration commit time only if one or both of the node(s) used to form the drp pair is not a DRP node. Please note that if the node is not in IOX-RUN state, it's node type will not be determined.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-DRP_PAIRING-6-NOT_SUPPORTED DRP pairing is not supported on CRS-4-CH

Explanation    Because CRS-DRP is not supported in CRS-1 Series 4 Slots Line Card system, therefore, drp pairing configuration will be disabled also.

Recommended Action    No action is required.

Error Message    
 
    
    
   

%PLATFORM-DRP_PAIRING_CLIENT-7-ERR_DLL_INIT [chars], reason: [chars]

Explanation    This message indicates that during dra_pairing dll attach, either debugging or ltrace services cannot be initialized.

Recommended Action    No action is required.

DRP_PAIRING Messages

Error Message     
 
    
    
   

%PLATFORM-DRP_PAIRING-7-ERR_CERR_REG Failed to register with CERR Handler. [chars]

Explanation    --

Recommended Action    '*NONE*'

Error Message     
 
    
    
   

%PLATFORM-DRP_PAIRING-7-ERR_DSC_NODEID Unable to determine the dSC nodeid

Explanation    --

Recommended Action    '*NONE*'

Error Message     
 
    
    
   

%PLATFORM-DRP_PAIRING-7-ERR_EVM_CREATE Event manager create failed. [chars]

Explanation    --

Recommended Action    '*NONE*'

Error Message     
 
    
    
   

%PLATFORM-DRP_PAIRING-7-ERR_GET_MY_NODEID Failed to get my own nodeid. [chars]

Explanation    --

Recommended Action    '*NONE*'

Error Message     
 
    
    
   

%PLATFORM-DRP_PAIRING-7-ERR_PROC_BLOCK [chars]

Explanation    --

Recommended Action    '*NONE*'

Error Message     
 
    
    
   

%PLATFORM-DRP_PAIRING-7-ERR_SERVER_INIT Unable to initialize drp_pairing server. [chars]

Explanation    --

Recommended Action    '*NONE*'

Error Message     
 
    
    
   

%PLATFORM-DRP_PAIRING-7-ERR_SYSDB_ACCESS SysDB operation failed. [chars]

Explanation    --

Recommended Action    '*NONE*'

Error Message     
 
    
    
   

%PLATFORM-DRP_PAIRING-7-ERR_THREAD_CREATE Unable to create a thread. [chars]

Explanation    --

Recommended Action    '*NONE*'

DSC Messages

Error Message     
 
    
    
   

%PLATFORM-DSC-3-ERR_DSC_INIT [chars] - error : [chars] , exiting...

Explanation    The dsc process failed in initialization. This indicates that there was a software error during initialization.

Recommended Action    The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. Verify that the dsc process is up and running by executing the following command at the CLI of the active RP: 'show process dsc' If it is still non-operational, restart the driver by executing the following command at the CLI of the active RP: 'process restart dsc' If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-DSC-3-ERR_INPUT_PRIORITY [chars] - nodeid : [hex]

Explanation    Priority given for the node is not applicable.

Recommended Action    Verify the priority given for this node and enter the correct priority. No action is required.

Error Message     
 
    
    
   

%PLATFORM-DSC-3-ERR_INTERNAL_SW [chars] - error : [chars], exiting...

Explanation    An internal software error occured as indicated in the message.

Recommended Action    The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. Verify that the dsc process is up and running by executing the following command at the CLI of the active RP: 'show process dsc' If it is still non-operational, restart the driver by executing the following command at the CLI of the active RP: 'process restart dsc' If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-DSC-3-ERR_MEM_ALLOC Failed to allocate [dec] bytes, exiting...

Explanation    The dsc process could not allocate memory. This indicates some problem with the system wide memory.

Recommended Action    The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. Verify that the dsc process is up and running by executing the following command at the CLI of the active RP: 'show process dsc' If it is still non-operational, restart the driver by executing the following command at the CLI of the active RP: 'process restart dsc' If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'

Error Message     
 
    
    
   

%PLATFORM-DSC-3-ERR_NULL_SERIAL_ID WARNING ! WARNING ! Received request with zeroed serial number. Assigning rack num [dec] and allowing it to pass, till CSCeg63482 is fixed. If this is multi-chassis, please upgrade ALL RP/SC ROMMONs in this setup to 1.22 !

Explanation    Once ROMMON 1.22 is rolled out, all multi-chassis testbeds should upgrade to it to avoid problems of more than one RP getting the same rack number assigned. This msg warns the operator that an RP was detected that had older ROMMON and should be upgraded ASAP.

Recommended Action    Upgrade the ROMMON to ver 1.32 or more Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-DSC-3-ERR_RACK_DOWN Lost connectivity with rack [chars]

Explanation    This indicates that either the rack is powerdown/shutdown or there is some problem with control ethernet cables or switches between the racks.

Recommended Action    If the rack is not powerdown or shutdown by the operator, then check the control ethernet connectivity between racks. (Check if the cables are okay and also if the switch is operating normally). Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-DSC-3-ERR_SYSDB_CONNECT [chars] - error: [chars]

Explanation    The dsc process could not open connection with sysdb. Hence the show commands will fail. However, the system will continue to function normally.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-DSC-7-ERR_RACK_DELETE [chars]. rack = [dec], [chars]

Explanation    An internal software error occured and this rack could not be removed.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-DSC-7-ERR_RACK_OIR Config cleanup failed following rack [dec] removal - [chars]. error: [chars]

Explanation    Not able to save configuration for this rack.

Recommended Action    Examine chassis based on above error msg.

Error Message     
 
    
    
   

%PLATFORM-DSC-7-ERR_RACK_OIR_TIMEOUT No Response received from configuration manager server.

Explanation    No response received from configuration manager server.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-DSC-7-ERR_STORE_REBOOT_INFO Could not store reboot information for node [hex], [chars]

Explanation    Chassis APIs that write to non volatile memory failed.

Recommended Action    No action is required.

DSCMEDIA Messages

Error Message     
 
    
    
   

%PLATFORM-DSCMEDIA-2-ERR_WAIT_REDUNDANCY Waiting for result of active/standby arbitration...keep trying

Explanation    The redundancy information is needed as an input for the DSC election. Only active cards may become DSC. The information is still unavailable at this time. The DSC election is on hold, waiting for the information to become available. This will prevent proper system operation.

Recommended Action    If this message happens repeatitively, it indicates a problem, likely in the active/standby arbitration module. Collect information using 'show redundancy'.

Error Message     
 
    
    
   

%PLATFORM-DSCMEDIA-2-FATAL DSC media fatal error: [chars]

Explanation    The dsc media dll encountered aa fatal error.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-DSCMEDIA-3-ERROR Error from dsc media dll: [chars]

Explanation    The dsc media dll encountered an internal software error.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-DSCMEDIA-3-ERROR2 Error from dsc media dll: [chars], errno=[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.

EIO Messages

Error Message     
 
    
    
   

%PLATFORM-EIO-7-ERR_ECM [chars]; rc = [chars], exiting...

Explanation    The EIO Library encountered ECM error, therefore failed to send pulse. The System Manager process (sysmgr) will automatically respawn the annunciated process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger MSC reload. After a certain number of MSC reloads, the shelf manager will permanently shutdown the MSC.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-EIO-7-ERR_EDM_INIT [chars]; rc = [chars]

Explanation    The EIO library was unable to register with sysdb as an EDM. The System should still continue to function as normal, with the exception that the 'show' commands for EIO will not be available.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-EIO-7-ERR_LINK_TRAINING [chars]; [chars]

Explanation    The Chip-to-Chip connecting link encountered the annunciated link training error. This link connects the two adjacent ASIC and its required to be in trained state for the ASIC's to commuincate control and data reliably over this channel. In general this is a recoverable error as the ASIC driver's will re-train the link on seeing this error.

Recommended Action    Use the following CLI to make sure the link is properly trained. - show controller eio links all loc If this problem is seen consistently, Run the field diags on the board. If it is possible to isolate the trigger point for this failure, collect all the necessary info (condition) that caused the error. Reload the MSC to avoid inconsistent behavior of the system 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-EIO-7-ERR_LWM_SEND EIO library failed to send message; rc = [chars], exiting...

Explanation    The EIO Library encountered LWM error, therefore failed to send pulse. The System Manager process (sysmgr) will automatically respawn the annunciated process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger MSC reload. After a certain number of MSC reloads, the shelf manager will permanently shutdown the MSC.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-EIO-7-ERR_MEM_ALLOC EIO library failed to allocate [dec] bytes

Explanation    The EIO library was unable to allocate memory.

Recommended Action    Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%PLATFORM-EIO-7-ERR_REGISTER_GET [chars]; rc = [chars]

Explanation    The EIO library encountered the annunciated register access error. This could result in inconsistent behavior of the device/system.

Recommended Action    Run diags on the board. If it is possible to isolate the trigger point for the read failure, collect all the necessary info (condition) that caused the error. Reload the MSC to avoid inconsistent behavior of the system because of this read failure. 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-EIO-7-ERR_REGISTER_SET [chars]; rc = [chars]

Explanation    The EIO library encountered the annunciated register access error. This could result in inconsistent behavior of the device/system.

Recommended Action    Run diags on the board. If it is possible to isolate the trigger point for this failure, collect all the necessary info (condition) that caused the error. Reload the MSC to avoid inconsistent behavior of the system because of this failure. 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.

ENVMON_MON Messages

Error Message     
 
    
    
   

%PLATFORM-ENVMON_MON-4-CLEAR_TEMPERATURE_READ_FAIL Envmon process is able to read temperature from various nodes, setting fan speed as per ambient temperature

Explanation    The envmon_mon process which has previously not been able to read the temperature from various nodes, is now able to read the temperature from atleast one node. Subsequently, the fan speed will be adjusted as per the mean_temp calculation.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON_MON-4-SET_TEMPERATURE_READ_FAIL Envmon process has not been able to read temperature from various nodes for past 7 minutes, setting fan speed to maximum to prevent chassis from heating up

Explanation    The envmon_mon process has not been able to read the temperature from various nodes for the last 5 iterations. This is most likely due to a communications error with remote nodes. Due to this, envmon_mon has no visibility into whether the chassis is being cooled properly or not. So the fans are being set to maximum speed to cover for any potential thermal issues during this time. Once the temperatures are readable, the fan speed will automatically be adjusted as per the ambient temperature.

Recommended Action    Check the communication with the remote nodes. Check if 'show environment temperatures' from admin and exec mode yield any output. If not, please contact support team for further debug and assistance. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

ENVMON Messages

Error Message     
 
    
    
   

%PLATFORM-ENVMON-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 (scan# = [unsigned int])

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 (scan# = [unsigned int])

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 (scan# [unsigned int])

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 (scan# = [unsigned int])

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_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.

Error Message    
 
    
    
   

%PLATFORM-ENVMON-3-NON_COMPLIANT_PS Power Supply [chars] is non Cisco compliant, powering off.

Explanation    Should a non-Cisco power supply be installed into the Cisco QQ chassis, upon detection as non-compliant, IT WILL BE SHUTDOWN. Please note that using non-Cisco power supplies MAY RESULT IN COMPLETE CHASSIS SHUTDOWN due to insufficient power

Recommended Action    Insert Cisco power supply

Error Message     
 
    
    
   

%PLATFORM-ENVMON-4-CLEAR_ALARM [chars] alarm cleared for [chars]

Explanation    A previously occured alarm has been cleared.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-4-SET_ALARM [chars] alarm generated by [chars]

Explanation    An alarm has occured.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-6-LOW_FAN_SPEED_WARNING [chars] is spinning slow - speed is [dec]RPM (register value = [hex])

Explanation    Informational msg indicating that the fan is spinning very slow.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-6-PS_SHUTDOWN_ERROR Unable to power off non compliant Power Supply [chars]

Explanation    Indicates that a non Cisco compliant power supply was detected. The attemp to shutdown this power supply has failed for number of tries.

Recommended Action    Insert Cisco power supply

Error Message     
 
    
    
   

%PLATFORM-ENVMON-6-SEND_PULSE_FAIL Failed to send pulse to shelfmgr to notify [chars]

Explanation    Failure to send pulse to shelfmgr to notify the particular alarm condition.

Recommended Action    No action is required.

ETH_SRVR Messages

Error Message     
 
    
    
   

%PLATFORM-ETH_SRVR-3-TX_STALLED Self test detected that control ethernet transmit functionality has stalled. Restarting to recover.

Explanation    Ethernet server is performing a periodic self test to ensure that transmit has not stalled for any reason. This error msg means that the test failed and transmit has stalled. Eth server will correct the condition by restarting itself and operator needs to do nothing.

Recommended Action    'Copy the error message exactly as it appears on the console or in the system log. Issue the show controllers backplane ethernet trace location command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show controllers backplane ethernet trace location output, call your Cisco technical support representative and provide the representative with the gathered information.'

Error Message     
 
    
    
   

%PLATFORM-ETH_SRVR-3-UNKNOWN_FORUS_PAK ethernet driver received an unknown for us packet. Cmd = [dec]

Explanation    Ethernet driver received an unknown for us packet.

Recommended Action    'Copy the error message exactly as it appears on the console or in the system log. Issue the show controllers backplane ethernet trace location command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show controllers backplane ethernet trace location output, call your Cisco technical support representative and provide the representative with the gathered information.'

Error Message     
 
    
    
   

%PLATFORM-ETH_SRVR-4-INIT_ERR [chars], error = [dec] ([chars])

Explanation    An error occurred during initialization from which eth server cannot recover. The process will restart on its own to attempt a recovery.

Recommended Action    'Copy the error message exactly as it appears on the console or in the system log. Issue the show controllers backplane ethernet trace location command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show controllers backplane ethernet trace location output, call your Cisco technical support representative and provide the representative with the gathered information.'

Error Message     
 
    
    
   

%PLATFORM-ETH_SRVR-7-ERR_FSM RECV_FSM: Type: [chars] Fragments: [dec] src: [chars] dest [chars] size: [dec] [chars]

Explanation    A bad or incomplete frame was received on the node given in the msg. If the messages are not persistent the condition is harmless and no action is required. If the messages are constantly seen, contact tech support with the output of the given command.

Recommended Action    'Copy the error message exactly as it appears on the console or in the system log. Issue the show controllers backplane ethernet location detail command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show controllers backplane ethernet location detail output, call your Cisco technical support representative and provide the representative with the gathered information.'

FABIO Messages

Error Message     
 
    
    
   

%PLATFORM-FABIO-3-ERR_INGRESS [chars]

Explanation    Internal Error

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-FABIO-3-ERR_INIT [chars], with code [chars]

Explanation    Internal Error

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-FABIO-3-ERR_MEM_ALLOC [chars], for size [dec].

Explanation    Failed to allocate memory.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-FABIO-3-ERR_SEND_PKT [chars], [dec], [dec], rc is [dec]

Explanation    Internal Error

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-FABIO-7-ERR_DUPLICATE_STREAMID [chars], stream id [dec] existed

Explanation    Internal Error

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

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-CARD_ID_FPGA_VERSION_MISMATCH Fabric Card type [hex] has an unsupported FPGA version. Card will be shutdown

Explanation    This message indicates that fabric card has a wrong or unsupported version of FPGA. Software cannot monitor the fabric card and it is shutdown.

Recommended Action    Verify the fabric card and chassis is supported by the software. Ensure the fabric card is inserted to the chassis correctly. Provide the 'show diag' info and contact your Cisco technical support representative.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-3-MBUS [chars], errno=[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_MGR Messages

Error Message     
 
    
    
   

%PLATFORM-FAULT_MGR-3-INIT_ERROR Process Initialization Failed: ([chars]%s)

Explanation    The fault-mgr process failed to initialize. This process controls all ASIC resets on all LC's for either internal ASIC problems or larger system issues (ie, fabric control). %s - indicates the reason for the failure. There are 3 types of possible failures, these include: - Checkpointing initialization/creation/restore - Server initialization - Client initialization %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 fault_mgr location 0/x/cpu0' to verify that the process is up and running. If it is still non-operational, try doing 'process restart fault_mgr 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-FAULT_MGR-3-MSG_ERROR ERROR while ([chars]%s)

Explanation    This ios_msg can be used for all kinds of error %s - indicates where the error occured %s - why the error occured

Recommended Action    Execute 'show process fault_mgr location 0/x/cpu0' to verify that the process is up and running. If it is still non-operational, try doing 'process restart fault_mgr 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.

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-PROBLEM_WITH_FDIAG_REQUEST Failed to validate field diagnostic request. Unexpected return code: [dec]

Explanation    There is some problem with field diagnostic software since a function has returned an unexpected value. Internal error: Contact Cisco's TAC. This error could be a software problem. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.

Recommended Action    Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-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-SYSDB_BIND_FAILURE Cannot connect to the system data base. Field diagnostics cannot be run.

Explanation    Cannot bind to path /admin/oper/instmgr-edm/gl in the system data base. This path is used to get the current setting of the config-register on the standby RP. Internal error: Contact Cisco's TAC. This error could be a software problem. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.

Recommended Action    Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-SYSLDR_RESULT_CODE_OUT_OF_BOUNDS Result code from sysloader ([dec]) exceeds list of known messages

Explanation    Coding violation: Sysldr code returns unexpected cause. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.

Recommended Action    Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-SYSTEM_ERR_NO_CONTINUE Sysldr reporting error - Field Diags will not commence testing

Explanation    Sysldr reporting error - time to quit Field Diags Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.

Recommended Action    Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-T_O_D_CONVERT_ERR time of day conversion error

Explanation    Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT. Internal Time Of Day conversion error

Recommended Action    Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-UNRECOGNIZED_CARD Card 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-SYSDB_ITEM_GET_FAILURE There is a problem with the standby RP state. Field diagnostics cannot be run

Explanation    The standby RP does not respond to a configuration query from the active RP. The system data base (sysdb) get of the tuple /admin/oper/instmgr-edm/gl/config-register has failed for the standby RP. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.

Recommended Action    Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail. Check the current state of the standby RP using the 'show platform' command.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-4-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-4-WRONG_CONFIG_REG_VAL WARNING: Field diagnostics cannot be run with the current config-register setting

Explanation    The router must be configured to auto boot the standby RP from disk if the user wants to run field diagnostics on the standby RP. The config-register setting may have been changed manually to the wrong setting by the user.

Recommended Action    Configure the router to disk boot the standby RP. Both the BOOT variable and CONFREG variable must be set correctly. The present settings can be displayed using the 'show variables boot' command when in ADMIN mode. If the BOOT variable appears to be correct then the CONFREG can be set to the correct value (0x102) by issuing the 'config-register 0x102' command in ADMIN mode.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-5-CLEANED_DANGLING_JID_FILE Deleted orphaned Field Diags jid file

Explanation    A file from a previous instance of Field Diags was left. We have now deleted it.

Recommended Action    No action required

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-5-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-0-SW_INIT_ERR A software error occurred in the FromFab driver component during initialization: [chars]

Explanation    The fabricq_prp_driver process which controls the FromFab driver on the route processor has failed to initalize and cannot recover automatically. This is a software fault. The FromFab driver controls the hardware that receives data from the fabric. It runs in the fabricq_prp_driver process. An unrecoverable failure of the fabricq_prp_driver process may prevent this route processor card from communicating with other cards on the chassis. %s indicates the type failure

Recommended Action    Restart the fabricq_prp_driver process with the following command: 'process restart fabricq_prp_driver' If the error message appears again, then: if a redundant route processor card has been configured: 1 - force a failover with the following command in admin mode: 'redundancy switchover' 2 - reload the route processor card that failed with the following command in admin mode: 'reload location RP/0/x/CPU0 ' where x is the slot of route processor that generated the error. if no redundant RP is configured you will need to reboot the router by issuing the reload command. If the error recurs call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-FFQ-3-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.

FIB_DBG Messages

Error Message     
 
    
    
   

%PLATFORM-FIB_DBG-3-ERR_INFO_VERBOSE [chars] [chars] [chars] [dec]

Explanation    PLATFORM FIB, error information

Recommended Action    Encouter internal error during platform FIB debug initialization. Report to your technical support representative.

FIB_IDB_LIB Messages

Error Message     
 
    
    
   

%PLATFORM-FIB_IDB_LIB-3-ERR_STR [chars]: [chars] ([unsigned int])

Explanation    PLATFORM FIB, error information

Recommended Action    Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transcient or persistent. Report to your technical support representative.

Error Message     
 
    
    
   

%PLATFORM-FIB_IDB_LIB-3-ERROR [chars]

Explanation    PLATFORM FIB, error

Recommended Action    Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transcient or persistent. Report to your technical support representative.

FIB_IPV4 Messages

Error Message     
 
    
    
   

%PLATFORM-FIB_IPV4-3-ADJ_ERROR [chars] ifh: [hex], [chars]

Explanation    Platform IPv4 FIB, adjacency error

Recommended Action    Please collect the console log and following traces: show cef trace loc show cef platform trace [common|ipv4] all loc show adjacency hardware trace loc show bundle trace all loc show im trace loc Most of the time, these are harmless transient messages, caused by the delay in FIB and AIB processes learning about new interface. If the errors persist, report to your technical support representative.

Error Message     
 
    
    
   

%PLATFORM-FIB_IPV4-3-ERR_INFO [chars] [dec]

Explanation    Platform IPv4 FIB, error information

Recommended Action    Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace [common|ipv4] all loc ). Also notice if the error message is transient or persistent. If the errors persist, report to your technical support representative.

Error Message     
 
    
    
   

%PLATFORM-FIB_IPV4-3-ERR_STR [chars], [chars] ([unsigned int])

Explanation    Platform IPv4 FIB, error information

Recommended Action    Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace [common|ipv4] all loc ). Also notice if the error message is transient or persistent. If the errors persist, report to your technical support representative.

Error Message     
 
    
    
   

%PLATFORM-FIB_IPV4-3-ERROR [chars]

Explanation    Platform IPv4 FIB, error

Recommended Action    Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace [common|ipv4] all loc ). Also notice if the error message is transient or persistent. If the errors persist, report to your technical support representative.

FIB_IPV6 Messages

Error Message     
 
    
    
   

%PLATFORM-FIB_IPV6-3-ERR_INFO [chars] [dec]

Explanation    Platform IPv6 FIB, error information

Recommended Action    Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace [common|ipv6] all loc ). Also notice if the error message is transient or persistent. If errros persist, report to your technical support representative.

Error Message     
 
    
    
   

%PLATFORM-FIB_IPV6-3-ERR_INFO_VERBOSE [chars] [chars] [chars] [dec]

Explanation    Platform IPv6 FIB, error information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-FIB_IPV6-3-ERROR [chars]

Explanation    Platform IPv6 FIB, error

Recommended Action    Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace [common|ipv6] all loc ). Also notice if the error message is transient or persistent. If errors persist, report to your technical support representative.

FIB_LTRACE Messages

Error Message     
 
    
    
   

%PLATFORM-FIB_LTRACE-3-ERR_INFO_VERBOSE [chars] [dec] [chars] [chars] [dec]

Explanation    PLATFORM FIB, error information

Recommended Action    Encouter internal error during platform FIB ltrace initialization. Report to your technical support representative.

G_PLIM_QOS Messages

Error Message     
 
    
    
   

%PLATFORM-G_PLIM_QOS-2-EVENT_BLOCK An error occurred while handling an event: [chars]

Explanation    The event handling function returned an error which could not be handled

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-G_PLIM_QOS-2-THREAD_CREATE_FAILED Could not create a thread - [chars]

Explanation    pthread_create function failed.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-G_PLIM_QOS-3-ERROR [chars]

Explanation    An error occured prior to debug service initialization

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-G_PLIM_QOS-3-MALLOC_FAILED Could not allocate memory : [chars]

Explanation    Call to malloc() failed.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

GSR_FIB_STATS_API Messages

Error Message     
 
    
    
   

%PLATFORM-GSR_FIB_STATS_API-3-ERROR [chars], error [dec] ([chars])

Explanation    Failed to perform the action specified in the error message.

Recommended Action    'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'

GSR_IPV4_EA Messages

Error Message     
 
    
    
   

%PLATFORM-GSR_IPV4_EA-3-ERROR [chars], error [chars]

Explanation    This is an error message in the c12000 platform specific code software to indicate anomolies that are not FATAL. This error is most likely caused by a temporary situation, so is unlikely to re-occur. %s - indicates the reason for the failure. %s - is the decoded error reason.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

GSR_IPv6_EA Messages

Error Message     
 
    
    
   

%PLATFORM-GSR_IPv6_EA-3-ERROR [chars], error [chars]

Explanation    This is an error message in the c12000 platform specific code software to indicate anomolies that are not FATAL. This error is most likely caused by a temporary situation, so is unlikely to re-occur. %s - indicates the reason for the failure. %s - is the decoded error reason.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

GSR_lc_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-ENGINE_PORT gsr_lc_pm: [chars] [chars]

Explanation    gsr_lc_pm encountered an error and is not able to recover from the error. A reason text will be supplied. call support with this text.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-GSR_LC_PM-3-FATAL GSR_LC_PM: Fatal Error, reason = [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.

GSR_MPLS_EA Messages

Error Message     
 
    
    
   

%PLATFORM-GSR_MPLS_EA-3-ERROR [chars], error [chars]

Explanation    Failed to perform the action specified in the error message.

Recommended Action    'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'

GSR_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.

GSR_TUNNEL_EA Messages

Error Message     
 
    
    
   

%PLATFORM-GSR_TUNNEL_EA-3-ERROR [chars], error [chars]

Explanation    This is an error message in the c12000 platform specific code software to indicate anomolies that are not FATAL. This error is most likely caused by a temporary situation, so is unlikely to re-occur. %s - indicates the reason for the failure. %s - is the decoded error reason.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-GSR_TUNNEL_EA-3-ERROR_PARAM [chars], param1 = [unsigned int], param2 = [unsigned int]

Explanation    This is an error message in the c12000 platform specific code software to indicate some problem with the code. %s - indicates the reason for the failure.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-GSR_TUNNEL_EA-3-ERROR2 [chars]

Explanation    This is an error message in the c12000 platform specific code software to indicate some problem with the code. %s - indicates the reason for the failure.

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.

GT_I2C Messages

Error Message     
 
    
    
   

%PLATFORM-GT_I2C-3-DRV_ERR [chars]

Explanation    Error detected when starting the i2c driver

Recommended Action    None. Driver will exit and restart automatically.

Error Message     
 
    
    
   

%PLATFORM-GT_I2C-3-REWORK_AND_UPGRADE_REQUIRED Detected old PLD version = [hex] on this board. Please upgrade the PLD to atleast [hex], and check for i2c rework

Explanation    Detected that the board has old PLD version. Because of this, we will not be able to detect or correct an i2c bus hang.

Recommended Action    Please upgrade PLD and check i2c rework ASAP on this board.

Error Message     
 
    
    
   

%PLATFORM-GT_I2C-3-UNRECOVERABLE_BUS_HANG Detected i2c bus hang from which sw is unable to recover.

Explanation    As shown in the message.

Recommended Action    Physically OIR the RP board which is having the problem.

Error Message     
 
    
    
   

%PLATFORM-GT_I2C-7-BUS_HANG Detected i2c bus hang, attempting to unhang the bus......

Explanation    Detected i2c bus hang.

Recommended Action    Please capture show gt-i2c trace location and show gt-i2c trace location .

Error Message     
 
    
    
   

%PLATFORM-GT_I2C-7-BUS_UNHANG_SUCCESS Successfully unhung the i2c bus

Explanation    As shown in the message.

Recommended Action    Physically OIR the RP board which is having the problem.

IPV6_EA Messages

Error Message     
 
    
    
   

%PLATFORM-IPV6_EA-3-PLAT_UPD_FAILED Platform update failed: [chars] - [chars]()

Explanation    Platform update 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-IPV6_EA-3-PLAT_UPD_FAILED_GL Platform update failed for [dec] interface: [chars] - [chars]

Explanation    Platform update failed for all interfaces in a batch.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

HBAGENT Messages

Error Message     
 
    
    
   

%PLATFORM-HBAGENT-2-FATAL Fatal error: [chars] [chars], exiting

Explanation    Fatal internal error.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-HBAGENT-2-NODE_RELOAD Reload notification received. Reloading in [dec] secs

Explanation    Message indicating that the node has received a reload notification and the node is going to reload soon.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-HBAGENT-3-API_FAILURE [chars], error: [chars]

Explanation    An infrastructure component has returned an error to the MBI infrastructure, so it may not be able to continue with the current operation.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-HBAGENT-3-THREAD_CREATE Failed to create a thread for [chars]: [chars]

Explanation    This may be a problem with lack of resources. The MBI infrastructure will be unable to carry out all of its expected functionality.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-HBAGENT-4-ATTACH_RECONNECT_HANDLER Failed to attach a reconnect handler to ethernet server coid. If ethernet server restarts, heartbeat agent may not be able to receive/write messages: [chars]

Explanation    Failed to attach a reconnect handler to ethernet server coid. If ethernet server restarts, heartbeat agent may not be able to receive/write messages.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-HBAGENT-4-INIT_LTRACE Failed to initialize hbagent tracing: ([dec] : [chars])

Explanation    The process will continue with it's business, however, cause of why hbagent was not able to initialize tracing should be tracked down. As result of this error, hbagent will not have any tracings.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-HBAGENT-4-SET_HEARTBEAT_PRIORITY Unable to set the heartbeat pulse through ethernet server to high priority. Proceeding with normal priority: [chars]

Explanation    Unable to set the heartbeat pulse of this node to high priority. Proceeding with default priority, however in a high CPU consumption, this node's heartbeat pulse may get lost, causing this node to get reloaded.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-HBAGENT-4-SET_THREAD_PRIORITY Unable to set the thread priority to high. Proceeding with normal priority: [chars]

Explanation    Unable to set the heartbeat pulse of this node to high priority. Proceeding with default priority, however in a high CPU consumption, this node's heartbeat pulse may get lost, causing this node to get reloaded.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-HBAGENT-7-RELOAD_NOTIFICATION_TEST Received a test reload notification, ignore.

Explanation    The node received a test reload notification just to check functionality. The notification is ignored.

Recommended Action    No action is required.

HFR_IP_EA Messages

Error Message     
 
    
    
   

%PLATFORM-HFR_IP_EA-3-CRITICAL HFR IP-EA: Critical error: [chars]

Explanation    HFR IP-EA, Critical error

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-HFR_IP_EA-3-ERROR1 HFR IP-EA: Error: [chars] [dec]

Explanation    HFR IP-EA, error

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-HFR_IP_EA-3-ERROR2 HFR IP-EA: Error: [chars]

Explanation    HFR IP-EA, error

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-HFR_IP_EA-5-DEBUG HFR IP-EA: Debug info: [chars]

Explanation    HFR IP-EA, Debug information

Recommended Action    *SUPPORT*

HFR_IPV6_EA Messages

Error Message     
 
    
    
   

%PLATFORM-HFR_IPV6_EA-3-CRITICAL HFR IP-EA: Critical error: [chars]

Explanation    HFR IP-EA, Critical error

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-HFR_IPV6_EA-3-ERROR1 HFR IP-EA: Error: [chars] [dec]

Explanation    HFR IP-EA, error

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-HFR_IPV6_EA-3-ERROR2 HFR IP-EA: Error: [chars]

Explanation    HFR IP-EA, error

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-HFR_IPV6_EA-5-DEBUG HFR IP-EA: Debug info: [chars]

Explanation    HFR IP-EA, Debug information

Recommended Action    *SUPPORT*

HFR_LCPM_SHOW Messages

Error Message     
 
    
    
   

%PLATFORM-HFR_LCPM_SHOW-3-ERROR HFR_PM_SHOW: [chars] , [chars]

Explanation    HFR_PM_SHOW encountered an error

Recommended Action    Please enable 'debug im api errors', 'debug sysdb access ...' and capture the output.

Error Message     
 
    
    
   

%PLATFORM-HFR_LCPM_SHOW-7-USAGE hfr_pm_show: invalid option passed to hfr_pm_show command. [chars]

Explanation    Startup option supplied to HFR_PM_SHOW is not valid.

Recommended Action    Please re-enter the correct option as described in the usage message 'Usage: hfr_pm_show [-I ] | [-N ]' Example: sh controllers hfr int Ten0/2/0/0 loc 0/2/cpu0, or run hfr_lcpm_show -I TenGigE0_2_0_0 -N 33

HFR_MPLS_EA Messages

Error Message     
 
    
    
   

%PLATFORM-HFR_MPLS_EA-3-ERR PLATFORM MPLS-EA: [chars]

Explanation    CRS-1 MPLS-EA, error

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-HFR_MPLS_EA-3-ERRSTR PLATFORM MPLS-EA: [chars] Error: [chars]([dec])

Explanation    CRS-1 MPLS-EA, error

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-HFR_MPLS_EA-6-INFO PLATFORM MPLS-EA: [chars]: [chars]

Explanation    CRS-1 MPLS-EA, Debug information

Recommended Action    *SUPPORT*

HFR_PM_TEST Messages

Error Message     
 
    
    
   

%PLATFORM-HFR_PM_TEST-3-ERROR hfr_pm_test: fatal error encountered, reason=[chars]

Explanation    hfr_pm test encountered a fatal error and is not able recover from the error. A reason text will be supplied call support with this text.

Recommended Action    This is just test software which the customer does not get. so there is np actiom required.

Error Message     
 
    
    
   

%PLATFORM-HFR_PM_TEST-3-ERROR_2 hfr_pm_test: fatal error encountered, reason=[chars], errno=[dec]

Explanation    hfr_pm_test encountered a fatal error and is not able to recover from the error. A reason text will be supplied call support with this text. An integer errno will also be printed.

Recommended Action    This is just test software which the customer does not get.

HFR_PM Messages

Error Message     
 
    
    
   

%PLATFORM-HFR_PM-3-ERR_FAULT_SENT Cannot send [chars] #[dec] fault=[chars] to shelf mgr. Resetting

Explanation    The specified device has a fault that affects the card functionality. Communication with the Shelf Manager could not be established to send fault information, so the card node will be reset and ideally the problem will not happen again when it comes back up.

Recommended Action    If the node keeps on resetting itself then please collect 'show log' output and contact customer support to diagnose the problem.

Error Message     
 
    
    
   

%PLATFORM-HFR_PM-3-ERROR hfr_pm: error encountered, reason=[chars], errno=[dec]

Explanation    hfr_pm encountered a fatal error and is not able to recover from the error. A text reason and error number will be supplied to describe the error.

Recommended Action    No action is required as the software should be able to recover from this error. Please collect 'show log location ' output, and 'show memory summary location from that location.

Error Message     
 
    
    
   

%PLATFORM-HFR_PM-3-ERROR_INIT hfr_pm: error encountered, reason=[chars]

Explanation    Platform Manager encountered an initialization error A reason text will be supplied to describe the error.

Recommended Action    No action is required as the software should be able to recover from this error. Please collect 'show log location ' output, and 'show memory summary location from that location.

Error Message     
 
    
    
   

%PLATFORM-HFR_PM-3-MALLOC_FAILED fatal memory allocation error for bytes

Explanation    Platform Manager encountered a fatal memory allocation error

Recommended Action    Please collect 'show memory summary location ' to see how much memory is left on that location/node.

Error Message     
 
    
    
   

%PLATFORM-HFR_PM-4-WARNING Platform Manager warning: [chars]

Explanation    The Platform Manager encountered an internal software warning. The software will reattempt to fix the cause of this warning.

Recommended Action    No action is required as the software should be able to recover from this error. Please collect 'show log location '

Error Message     
 
    
    
   

%PLATFORM-HFR_PM-4-WARNING Platform Manager warning: [chars]

Explanation    The Platform Manager encountered an provisioning warning.

Recommended Action    No action is required as the software should be able to recover from this error. Please collect 'show log location '

Error Message     
 
    
    
   

%PLATFORM-HFR_PM-7-ERROR Platform Manager error, reason=[chars], errno=[dec]

Explanation    The Platform Manager encountered an internal software error.

Recommended Action    No action is required as the software should be able to recover from this error. Please collect 'show log location ' output, and 'show memory summary location from that location.

Error Message     
 
    
    
   

%PLATFORM-HFR_PM-7-ERROR_INIT Platform Manager error, reason=[chars]

Explanation    The Platform Manager encountered an internal software initialization error.

Recommended Action    No action is required as the software should be able to recover from this error. Please collect 'show log location ' output, and 'show memory summary location from that location.

HSR_ES_CLI Messages

Error Message     
 
    
    
   

%PLATFORM-HSR_ES_CLI-3-CAPS_LOAD_FAILED Sponge caps load failed, sponge_caps = [dec], rc = [dec] ([chars])

Explanation    Failed to load capsulation DLL

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-HSR_ES_CLI-3-ERR [chars], rc = [dec] ([chars])

Explanation    Generic error. A string explaining the error condition, an error code and a string description of the error are printed.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-HSR_ES_CLI-3-FATAL Fatal error encountered, reason=[chars]

Explanation    HSR ES client encountered a fatal error and is not able recover from the error. A reason text will be supplied call support with this text.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-HSR_ES_CLI-3-FATAL_2 Fatal error encountered, reason=[chars], errno=[dec]

Explanation    HSR ES client a fatal error and is not able to recover from the error. A reason text will be supplied call support with this text. An integer errno will also be printed.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-HSR_ES_CLI-3-FATAL_3 Fatal error encountered, reason=[chars], errno=[dec] ([chars])

Explanation    HSR ES client a fatal error and is not able to recover from the error. A reason text will be supplied call support with this text. An integer errno will also be printed along with string descrioption of the error

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-HSR_ES_CLI-3-UNK_MSG_CODE Connecting to pakman, [chars], msg_code = [dec]

Explanation    Unknwn message code send by Pakman server

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-HSR_ES_CLI-6-INFO [chars]

Explanation    Prints an informational statement

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

I2C Messages

Error Message     
 
    
    
   

%PLATFORM-I2C-6-LC_POWER_FAIL LC power-up failed because - [chars] - as indicated by power status registers

Explanation    None

Recommended Action    Replace the bad part for LC to work.

Error Message     
 
    
    
   

%PLATFORM-I2C-7-BOARD_POWERUP_FAIL Board not powered up (DC_DC_en not asserted) after max timeout of [dec] seconds

Explanation    None

Recommended Action    Check why the board is not yet powered.

Error Message     
 
    
    
   

%PLATFORM-I2C-7-BOARD_POWERUP_NOT_HAPPENED Board not powered up (DC_DC_en not asserted) after [dec] seconds, resending pulse to shelfmgr to powerup this board

Explanation    None

Recommended Action    Check why the board is not yet powered.

Error Message     
 
    
    
   

%PLATFORM-I2C-7-LC_BAD_VRM_INFO LC power-up failed because - [chars] on [chars] is bad - as indicated by power good registers

Explanation    None

Recommended Action    Replace the bad part for LC to work.

Error Message     
 
    
    
   

%PLATFORM-I2C-7-LC_POWERUP_CHECK_FAIL Unable to check LC power status registers because [chars]

Explanation    None

Recommended Action    Manually check why the board is not yet powered.

Error Message     
 
    
    
   

%PLATFORM-I2C-7-SEND_PULSE_FAIL Failed to send pulse because [chars] failed

Explanation    None

Recommended Action    Check the path of file specified for download

INV Messages

Error Message     
 
    
    
   

%PLATFORM-INV-6-NODE_STATE_CHANGE Node: [chars], state: [chars]

Explanation    Inventory Manager output this informational message whenever there is a card state change. This message will indicate the current card state.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-INV-6-OIRIN OIR: Node [chars] inserted

Explanation    Entity specified in the messages is inserted into the chassis and inventory manager is updated. This message is used by CWI/CTM to determine when the entity-related information (read from the EEPROM) is available in inventory database.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-INV-7-ERR [chars]

Explanation    Failure in Inventory Manager resulting in error condition

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-INV-7-ERR_DLL [chars], reason: [chars]

Explanation    Failure in Inventory Manager dllmain function call

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-INV-7-ERR_EDM_CREATE Unable to register for invmgr edm event notification

Explanation    Failure in Inventory Manager event creation

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-INV-7-ERR_EDM_OPEN Unable to start invmgr edm communication channel

Explanation    Failure in Inventory Manager event connect open

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-INV-7-ERR_MEM_ALLOC Unable to allocate memory

Explanation    Failure in Inventory Manager memory allocation error occurred

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-INV-7-ERR_RACK_CREATE Inventory Creation of RACK failed.

Explanation    The RACK entry is a must in inventory management

Recommended Action    None. Inventory Manager process will restart automatically

Error Message     
 
    
    
   

%PLATFORM-INV-7-SYSDB_ERR [chars], reason: [chars]

Explanation    Sysdb api call failed

Recommended Action    No action is required.

INVMGR Messages

Error Message     
 
    
    
   

%PLATFORM-INVMGR-2-ERR_SYSDB_REG_NOTIFY SysDB registration for notification on [chars] failed. Error - [chars]

Explanation    This message indicates that registration for notification failed for the tuple specified. %s - tuple %s - indicates the internal error message

Recommended Action    System manager will automatically respawn this process, up to a fixed number of times, when this error is encountered to recover. Execute 'show process invmgr location 0/x/cpu0' to verify that the process is up and running. If it is non-operational, do 'process restart invmgr location 0/x/cpu0' to manually restart it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-INVMGR-3-ERR_EEPROM_READ EEPROM/NVRAM read failed. Error - [chars], [dec]

Explanation    EEPROM/NVRAM read failed for a chassis, card, or SPA. Inventory information would be incomplete. This would affect information provided to CLI 'show inventory', inventory schema, and the entity related MIBs. %s - indicates the internal error string %d - indicates the internal error code

Recommended Action    Check the card/chassis/SPA.

Error Message     
 
    
    
   

%PLATFORM-INVMGR-3-ERR_INIT Initialization failed. [chars]. [chars]

Explanation    This message indicates that process invmgr failed to initialize and exited. Inventory information would not be available. This would affect CLI 'show inventory', inventory schema, and the entity related MIBs. Some reasons are: 1) System manager process ready notification failed 2) Error waiting for secondary RP to go active 3) Internal API error %s - indicates the internal message. %s - indicates the internal error reason.

Recommended Action    System manager will automatically respawn this process, up to a fixed number of times, when this error is encountered to recover. Execute 'show process invmgr location 0/x/cpu0' to verify that the process is up and running. If it is non-operational, do 'process restart invmgr location 0/x/cpu0' to manually restart it. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-INVMGR-3-ERR_MEM_ALLOC [chars], slot [dec]

Explanation    This message indicates memory allocation failure. Inventory information for the specified slot would be incomplete. This would affect information provided to CLI 'show inventory', inventory schema, and the entity related MIBs for the specified slot. %s indicates the internal data structure that failed allocation for.

Recommended Action    Reduce other system activity to ease memory demands and restart process invmgr via CLI 'process restart invmgr' to recover. If conditions warrant and minimum memory requirements not met, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%PLATFORM-INVMGR-3-ERR_NODEID_CREATE Node ID of slot [dec]. Error - [chars]

Explanation    This message indicates a failure in creating the node ID of the specified slot. Inventory information for the specified slot would be incomplete. This would affect information provided to CLI 'show inventory', inventory schema, and the entity related MIBs for the specified slot. %s - indicates the internal error reason.

Recommended Action    Try restarting the invmgr process via CLI 'process restart invmgr' to recover. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-INVMGR-3-ERR_OBJECT_CREATE Slot [dec]. Error - [chars]

Explanation    This message indicates a failure in creating the object for the specified slot. The entry is not added to the inventory. %s - indicates an internal message

Recommended Action    Issue may be due to lack of memory in the system. If memory shortage is the cause, reduce other system activity to ease memory demands and restart process invmgr via CLI 'process restart invmgr' to recover. If conditions warrant and minimum memory requirements not met, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%PLATFORM-INVMGR-3-ERR_SENSOR_CREATE Slot [dec] sensor [dec] object create failed

Explanation    This message indicates a failure in creating the sensor object for the specified slot and sensor. The sensor entry is not added to the inventory.

Recommended Action    Issue may be due to lack of memory in the system. If memory shortage is the cause, reduce other system activity to ease memory demands and restart process invmgr via CLI 'process restart invmgr' to recover. If conditions warrant and minimum memory requirements not met, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%PLATFORM-INVMGR-3-ERR_SYSDB_BIND SysDB bind to [chars] failed. Error - [chars]

Explanation    This message indicates bind to the specified path failed. Inventory information would be incomplete. This would affect information provided to CLI 'show inventory', inventory schema, and the entity related MIBs. %s - indicates the internal error reason.

Recommended Action    Try restarting the invmgr process via CLI 'process restart invmgr' to recover. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-INVMGR-5-OIRIN OIR: Node [chars] inserted

Explanation    Entity specified in the messages is inserted into the chassis and inventory manager is updated.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-INVMGR-6-NODE_STATE_CHANGE Node: [chars], state: [chars]

Explanation    This message indicates the node state (eg. IOS XR RUN, MBI_RUNNING). A node being a card, SPA, etc. %s - indicates the node/location in rack/slot/instance format %s - indicates the state

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-INVMGR-7-ERR_API [chars] failed for slot [dec]

Explanation    The sensor entry will not be added in inventory

Recommended Action    Check the memory on the system

Error Message     
 
    
    
   

%PLATFORM-INVMGR-7-ERR_NODEID Extract fields from node ID [dec] failed. Error - [chars]

Explanation    This message indicates a failure in extracting fields from the node ID. Inventory information for the specified node ID, if valid, would be incomplete. This would affect information provided to CLI 'show inventory', inventory schema, and the entity related MIBs for the specified node. %s - indicates the internal error.

Recommended Action    Try restarting the invmgr process via CLI 'process restart invmgr' to recover. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-INVMGR-7-FAIL [chars]

Explanation    This message indicates a failure in inventory manager. This is an internal debug message. %s - indicates the failure.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

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.

IPCP_SRVR Messages

Error Message     
 
    
    
   

%PLATFORM-IPCP_SRVR-3-SW_INIT_ERROR IPCP Server process initialization failed - [chars]: [chars]

Explanation    A fatal software error encountered during IPCP Server process initialization. The specific error and cause are appended to the error message. Process will be terminated. Node can't function properly and will be reset.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-IPCP_SRVR-6-IPCP_SERVER_RESTARTED_NODE_REBOOTING IPCP has been restarted. Node [chars] is going down for reboot.

Explanation    IPCP server has been restarted. The node will be reloaded. This is not an error.

Recommended Action    No action is required.

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.

libpcmcia_ide Messages

Error Message     
 
    
    
   

%PLATFORM-libpcmcia_ide-1-CARD_UNAVAILABLE [chars]: Can not access flash device

Explanation    Probably the flash card has been removed.

Recommended Action    Reinsert the flash card.

Error Message     
 
    
    
   

%PLATFORM-libpcmcia_ide-1-FORMAT_DISABLED Boot device [chars] is corrupted and will not be auto formatted

Explanation    The flash card specified is corrupted and was not auto formatted because rommon variable DISABLE_AUTOFORMAT is set.

Recommended Action    Format flash card and reinstall software and configuration.

Error Message     
 
    
    
   

%PLATFORM-libpcmcia_ide-1-FORMAT_FAILED Boot device [chars] is corrupted and could not be formatted

Explanation    The flash card specified is corrupted and could not be formatted due to some flash card failure.

Recommended Action    Format flash card manually, if still fails, replace flash card.

Error Message     
 
    
    
   

%PLATFORM-libpcmcia_ide-2-BOARD_RELOADING Boot device [chars] unavailable. Reload RP to [chars]

Explanation    The RP card is resetting to initiate action specified to fully recover software on corrupted boot device.

Recommended Action    Redundant card should fully recover data from active card. If not redundant then reinstall software and configuration.

Error Message     
 
    
    
   

%PLATFORM-libpcmcia_ide-2-CARD_CORRUPT Disk device [chars][dec]: is corrupted beyond repair. Check fsck log at [chars]

Explanation    The flash card specified was corrupted beyond repair. See log file for specific reason.

Recommended Action    Format or replace flash card.

Error Message     
 
    
    
   

%PLATFORM-libpcmcia_ide-2-CARD_FORMATTED Boot device [chars] was formatted due to corruption. Check log file at [chars]

Explanation    The flash card specified was corrupted beyond repair and was formatted. See log file for specific reason.

Recommended Action    Redundant card should fully recover data from active card. If not redundant then reinstall software and configuration.

Error Message     
 
    
    
   

%PLATFORM-libpcmcia_ide-4-CARD_REPAIRED Disk device [chars][dec]: filesystem was repaired. Check fsck log at [chars]

Explanation    The flash card specified was corrupted and was repaired. See log file for specific reason.

Recommended Action    run install verify and cfs check

Error Message     
 
    
    
   

%PLATFORM-libpcmcia_ide-5-CARD_SWAPPED [chars]: The flash card has been swapped (OIR)

Explanation    The pcmcia flash card has been pulled out from its slot and re-inserted with a same or different card

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-libpcmcia_ide-5-OPERATION_FAILED [chars]: The [chars] operation failed. rc = [dec]

Explanation    The pcmcia software operation specified failed with the specified return code.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-libpcmcia_ide-5-SYSCALL [chars]: system call [chars] failed. rc = [dec]

Explanation    An internal Event Manager Create operation failed

Recommended Action    No action is required.

LIC_UDI Messages

Error Message     
 
    
    
   

%PLATFORM-LIC_UDI-3-ACQUIRE_FAILURE UDI information for the chassis could not be retrieved.

Explanation    dSC re-election is required to determine licensing udi data. 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-LIC_UDI-3-DATA_ACCURACY_UNKNOWN UDI information for the chassis has been derived and may not be accurate.

Explanation    To ensure accurate UDI data, dSC re-election is recommended. 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-LIC_UDI-7-ERR_EVM_CREATE Could not create event manager for udi process. Error: [chars]

Explanation    A event manager create failed.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-LIC_UDI-7-ERR_INTERNAL [chars]: [chars]

Explanation    Miscellaneous software error.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-LIC_UDI-7-ERR_MALLOC Malloc for -[dec] bytes failed

Explanation    Memory allocation failed.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-LIC_UDI-7-ERR_SYSDB_REG_NOTIF Sysdb registration for notification on path -[chars] failed

Explanation    Application failed to register for notification

Recommended Action    No action is required.

libpcmcia_linux Messages

Error Message     
 
    
    
   

%PLATFORM-libpcmcia_linux-7-CHILD_SPAWN pcmciad child [chars] died. Being restarted

Explanation    pcmciad spawns filesystem process and cardmgrd. One of them died and hence being restarted

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-libpcmcia_linux-7-FUNCTION_FAILED [chars]() failed: [chars]

Explanation    The function specified failed

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-libpcmcia_linux-7-MALLOC_FAILED Malloc failed: [chars]

Explanation    Low in memory

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-libpcmcia_linux-7-MOUNT_FAILED pcmciad failed to mount [chars]

Explanation    pcmciad mounts DOS filesystem on ATA devices after DOS filesystem restart. mount failed during restart of DOS filesystem by pcmciad.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-libpcmcia_linux-7-NO_SPAWN_PARAM pcmciad spawn of process [dec] failed, since no information available

Explanation    pcmciad stores the pids of its children in /tmp. For some reason the file might have got corrupted

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-libpcmcia_linux-7-OPEN_FAILED Open of file [chars] failed: [chars]

Explanation    Open of file failed.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-libpcmcia_linux-7-SLEEPON_LOCK_FAILED sleepon_lock failed: [chars]

Explanation    deadlock error.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-libpcmcia_linux-7-SPAWN_FAILED pcmciad spawn of process [chars] failed

Explanation    pcmciad spawns filesystem process and cardmgrd. One of them died and its respawn failed

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

MBI_HELLO Messages

 
    
    
   

%PLATFORM-MBI_HELLO-2-FATAL Fatal error: [chars] [chars], exiting

Explanation    Fatal internal error.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-2-NODE_RELOAD Reload notification received. Reloading in [dec] secs

Explanation    Message indicating that the node has received a reload notification and the node is going to reload soon.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-3-API_FAILURE Unable to [chars], error: [chars]

Explanation    An infrastructure component has returned an error to the MBI infrastructure, so it may not be able to continue with the current operation.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-3-CLOCK_FAIL Clock operation failed ([chars]): [chars]

Explanation    A clock operation failed. This should have only cosmetic effect on the MBI infrastructure.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-3-ETHSERVER_CONNECT The MBI infrastructure was unable to connect to the Ethernet Server error: [chars].

Explanation    A communication problem occurred between the MBI client and Ethernet server. The MBI operation in progress will not be carried out.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-3-ETHSERVER_WRITE The MBI infrastructure was unable to send a message to the Ethernet Server, error: [chars].

Explanation    A communication problem occurred between the MBI client and Ethernet server. The MBI operation in progress will not be carried out.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-3-MALLOC_FAIL Failed to allocate [unsigned int] bytes of memory

Explanation    The requested operation could not be accomplished because of a low memory condition.

Recommended Action    This indicates a low memory condition. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-3-MSG_SEND_FAIL The MBI infrastructure was unable to send a message to the MBI Hello server, error: [chars].

Explanation    A communication problem occurred between the MBI client and server. The MBI operation in progress will not be carried out.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-3-REQUEST_NETMGR_MOUNTPOINT_FAIL Failed to request netmgr mountpoint

Explanation    Failed to request netmgr mountpoint.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-3-SERVER_CONNECT_FAIL The MBI infrastructure was unable to connect to the MBI Hello server, error: [chars].

Explanation    A communication problem occurred between the MBI client and server, perhaps because the communications infrastructure is not yet up. The MBI operation in progress will not be carried out.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-3-THREAD_CREATE Failed to create a thread for [chars]: [chars]

Explanation    This may be a problem with lack of resources. The MBI infrastructure will be unable to carry out all of its expected functionality.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-3-TIMER_TIMEOUT Timer timed out from server : [chars]

Explanation    Timer timed out.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-4-ATTACH_RECONNECT_HANDLER Failed to attach a reconnect handler to ethernet server coid. If ethernet server restarts, heartbeat agent may not be able to receive/write messages: [chars]

Explanation    Failed to attach a reconnect handler to ethernet server coid. If ethernet server restarts, heartbeat agent may not be able to receive/write messages.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-4-INIT_LTRACE Failed to initialize mbi_hello tracing: ([dec] : [chars])

Explanation    The process will continue with it's business, however, cause of why mbi-hello was not able to initialize tracing should be tracked down. As result of this error, mbi-hello will not have any tracings.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-4-SET_HEARTBEAT_PRIORITY Unable to set the heartbeat pulse through ethernet server to high priority. Proceeding with normal priority: [chars]

Explanation    Unable to set the heartbeat pulse of this node to high priority. Proceeding with default priority, however in a high CPU consumption, this node's heartbeat pulse may get lost, causing this node to get reloaded.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-4-SET_THREAD_PRIORITY Unable to set the thread priority to high. Proceeding with normal priority: [chars]

Explanation    Unable to set the heartbeat pulse of this node to high priority. Proceeding with default priority, however in a high CPU consumption, this node's heartbeat pulse may get lost, causing this node to get reloaded.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-7-HBAGENT_EXISTS Mbi-hello was restarted, but detected that hbagent is up and functioning already. Proceeding with passive mode

Explanation    Mbi-hello process was restarted. However, it detected that the hbagent process is already functioning. Hence mbi-hello is going into passive mode by design.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-7-RELOAD_NOTIFICATION_TEST Received a test reload notification, ignore.

Explanation    The node received a test reload notification just to check functionality. The notification is ignored.

Recommended Action    No action is required.

MBI_LIB_ACCESS Messages

Error Message     
 
    
    
   

%PLATFORM-MBI_LIB_ACCESS-3-MSG_SEND_FAIL The MBI infrastructure was unable to send a message to the MBI Hello server, error: [chars].

Explanation    A communication problem occurred between the MBI client and server. The MBI operation in progress will not be carried out.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBI_LIB_ACCESS-3-SERVER_CONNECT_FAIL The MBI infrastructure was unable to connect to the MBI Hello server, error: [chars].

Explanation    A communication problem occurred between the MBI client and server, perhaps because the communications infrastructure is not yet up. The MBI operation in progress will not be carried out.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message    
 
    
    
   

%PLATFORM-MBI_HELLO-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

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.

Error Message    
 
    
   
 
    
    
   

M-MBI_LIB-3-MSG_SEND_FAIL The MBI infrastructure was unable to send a message to the MBI Hello server, error: [chars].

Explanation    A communication problem occurred between the MBI client and server. The MBI operation in progress will not be carried out.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBI_LIB-3-SERVER_CONNECT_FAIL The MBI infrastructure was unable to connect to the MBI Hello server, error: [chars].

Explanation    A communication problem occurred between the MBI client and server, perhaps because the communications infrastructure is not yet up. The MBI operation in progress will not be carried out.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBI_LIB-4-CLOCK_FAIL The MBI infrastructure was unable to determine the time, error: [chars]

Explanation    The infrastructure is behaving incorrectly. This will not affect the operation of the MBI infrastructure, but messages and logs may not contain timestamps.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

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.

MBIMGR Messages

Error Message     
 
    
    
   

%PLATFORM-MBIMGR-3-COPY_MBI_FILE_NAME_FAIL [chars]The MBI infrastructure was unable to copy the MBI file name, error: [chars].

Explanation    The MBI file name is possibly too large or invalid. The MBI operation in progress may not be carried out.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBIMGR-3-DEFAULT_MBI_FAIL [chars]The MBI infrastructure failed to obtain the default MBI for card class [hex], error: [chars].

Explanation    The default MBI is either unknown or missing. The MBI operation in progress may not be carried out.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBIMGR-3-FAILED_TO_CALCULATE_MD5 [chars]Failed to calculate MD5 value from path ([chars]): [chars]

Explanation    Either the path is invalid, or the infrastructure is behaving incorrectly. The MBI operation in progress may not be carried out.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBIMGR-3-FAILED_TO_COMPARE_MD5 [chars]The MBI infrastructure failed to compare MD5 values between the boot request MBI ([chars]) and the MBI stored in dSC ([chars]), error: [chars]. Using the MBI ([chars]) from dSC.

Explanation    Either the MD5 values are invalid, or the infrastructure is behaving incorrectly. The MBI operation in progress may not be carried out.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBIMGR-3-IGNORING_MBI [chars]The MBI infrastructure detected an abnormality with the MBI passed ([chars]). Ignoring this MBI. Error: [chars].

Explanation    The MBI passed was not in the expected form. The MBI infrastructure will ignore this MBI and most likely new MBI will be downloaded from dSC as result.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBIMGR-3-INVALID_ARG [chars]An invalid argument was passed to the MBI infrastructure.

Explanation    An internal error has occurred in an application that has caused it to pass invalid data to the MBI infrastructure. The MBI operation in progress may not be carried out.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBIMGR-3-MALLOC_FAIL [chars]Unable to allocate [unsigned int] bytes of memory

Explanation    The requested operation could not be accomplished because of a low memory condition.

Recommended Action    This indicates a low memory condition. Reduce other system activity to ease memory demands. If conditions warrant, upgrade to a larger memory configuration.

Error Message     
 
    
    
   

%PLATFORM-MBIMGR-3-NODEID_EXTRACT_FAIL [chars]The infrastructure failed to extract the R/S/I elements of node [dec] for for the MBI infrastructure, error: [chars].

Explanation    Either an invalid location is being queried, or the infrastructure is behaving incorrectly. The MBI operation in progress may not be carried out.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBIMGR-3-NODEID_FAIL [chars]The infrastructure failed to inform the MBI infrastructure of the location where it is running, error: [chars].

Explanation    Either an invalid location is being queried, or the infrastructure is behaving incorrectly. The MBI operation in progress may not be carried out.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBIMGR-3-NODEID_TO_IP_ADDR_FAIL [chars]The infrastructure was unable to return the IP address of a node ([dec]) to the MBI infrastructure, error: [chars].

Explanation    Either an invalid location is being queried, or the infrastructure is behaving incorrectly. The MBI operation in progress may not be carried out.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBIMGR-3-NODEID_TO_STR_EXTERNAL_FAIL The infrastructure was unable to create an external representation of a location ([dec]) for the MBI, error: [chars]. Error messages from the MBI infrastructure will not contain the prefix-string that represents the remote location being processed.

Explanation    Either an invalid location is being queried, or the infrastructure is behaving incorrectly. The MBI operation in progress may not be carried out.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBIMGR-3-NULL_PTR Unexpected NULL pointer passed to the MBI infrastructure by a client

Explanation    An internal error has occurred in an application that has caused it to pass invalid data to the MBI infrastructure. The current request or operation may not be carried out.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBIMGR-3-TFTP_INFO_FAIL [chars]The MBI infrastructure failed to populate the TFTP information, error: [chars].

Explanation    The TFTP information is unavailable. The MBI operation in progress may not be carried out.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBIMGR-3-UNKNOWN_BOARDTYPE [chars]An unknown boardtype ([dec]) was passed to the MBI infrastructure.

Explanation    Either an invalid boardtype is being queried, or the infrastructure is behaving incorrectly. The MBI operation in progress may not be carried out.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBIMGR-4-REMOTE_NODEID_MSG_STR_CREATE_FAIL The MBI infrastructure failed to create a message string for a remote location ([dec]), error: [chars]. Error messages from the MBI infrastructure will not contain the prefix-string that represents the remote location being processed.

Explanation    Either an invalid location is being queried, or the infrastructure is behaving incorrectly. The MBI operation in progress may not be carried out.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-MBIMGR-6-MBIVSN_DIGIT_INFO MBIMGR: [chars] ([dec])

Explanation    MBI Mgr general info

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-MBIMGR-6-MBIVSN_STR_INFO MBIMGR: [chars] ([chars])

Explanation    MBI Mgr general info

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-MBIMGR-7-IMAGE_VALIDATED [chars]: MBI [chars] validated

Explanation    A message to indicate which MBI was validated for which location.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-MBIMGR-7-INVALID_MBIVSN [chars]Invalid MBI spec passed in ([chars]): [chars]

Explanation    A problem was found in the MBI spec that was passed in.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Recommended Action   

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-4-SVC_AGENT_ROM_DOWN_REV slot [dec]: mbus rom agent is down-rev (V[dec].[dec]), suggest upgrade to current (V[dec].[dec]). Use the upgrade mbus CLI in admin mode.

Explanation    The version of Mbus agent ROM on slot is not current. %d - is the slot number of the card in question. %d - is the major version of the agent currently in ROM %d - is the minor version of the agent currently in ROM %d - is the major version of the agent that is recommeneded %d - is the minor version of the agent that is recommeneded

Recommended Action    Upgrade the rom agent on the car in the specified slot. In admin mode issue the following command upgrade mbus location 0//cpu0 where is the number of the slot shown in the warning message

Error Message     
 
    
    
   

%PLATFORM-MBUS-7-API_DEBUG [chars] ([hex])

Explanation    mbus debugging information. %s debug or software error message %X error returns code in hexdecimal format.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-MBUS-7-API_DOWNLOAD_FAIL_STATUS download failed ([chars]).

Explanation    mbus debug info %s - a string containing the slot number.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-MBUS-7-API_FILE_OPERATION_FAILED Failed to perform [chars] on file [chars].

Explanation    mbus debug information %s - operation performed on file (e.g. open, close). %s - filename.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-MBUS-7-API_INFO [chars]

Explanation    mbus debug information %s - debug message

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-MBUS-7-API_INFO_DUMP [chars]

Explanation    Displaying mbus debug information. %s - information message to be displayed

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-MBUS-7-API_INVALID_SLOT invalid slot [dec].

Explanation    mbus debug information %d - slot number

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-MBUS-7-API_NULL_PARAMETER unexpected null pointer passed to function.

Explanation    mbus debug information

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-MBUS-7-CLIENT_FAILURE [chars]

Explanation    mbus debug information %s - describes the function that failed

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-MBUS-7-SVC_AGENT_CHECK_FAILED mbus: local agent check failed ([chars]).

Explanation    mbus debug information %s - is a string outlining the action that the system will take to attempt to recover (e.g. forcing RAM download).

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-MBUS-7-SVC_DEBUG [chars] ([hex])

Explanation    mbus debug information. %s - is the debug message

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-MBUS-7-SVC_EOF_UNEXPECTED mbus: EOF unexpected on file [chars].

Explanation    mbus debug information. %s - is the file name in question.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-MBUS-7-SVC_FILE_OPERATION_FAILED mbus: Failed to perform [chars] on file [chars].

Explanation    mbus debug information. %s - indicates the type of file operations (e.g. open, close) %s - is the file name in question.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-MBUS-7-SVC_INFO_DUMP [chars]

Explanation    mbus debug information. %s - is the information being displayed for debug purposes

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-MBUS-7-SVC_INVALID_STREAM mbus: invalid stream [dec].

Explanation    mbus debug information %d - is the stream identifier.

Recommended Action    No action is required.

MSM Messages

Error Message     
 
    
    
   

%PLATFORM-MSM-3-ERR [chars], [chars], err = [hex]

Explanation    Failure in Multishelf Manager.

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.

obfl Messages

Error Message     
 
    
    
   

%PLATFORM-obfl-7-ERR_EVM_CREATE Could not create event manager for obfl process. Error: [chars]

Explanation    A event manager crreate failed.

Recommended Action    None. obfl controller process will restart automatically

Error Message     
 
    
    
   

%PLATFORM-obfl-7-ERR_INTERNAL [chars]: [chars]

Explanation    Miscellaneous software error.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-obfl-7-ERR_MALLOC Malloc for -[dec] bytes failed

Explanation    Memory allocation failed.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-obfl-7-ERR_SYSDB_REG_NOTIF Sysdb registration for notification on path -[chars] failed

Explanation    Application faile to register for notification

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-obfl-7-ERR_THREAD_CREATE Could not create thread. Error: [chars]

Explanation    A thread could not be created.

Recommended Action    None. obfl controller process will restart automatically

Error Message     
 
    
    
   

%PLATFORM-obfl-7-ERROR Error, [chars]

Explanation    Envmon encountered an software error.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-obfl-7-TRACE_INTERNAL [chars]: [chars]

Explanation    software trace.

Recommended Action    No action is required.

OIRD Messages

Error Message     
 
    
    
   

%PLATFORM-OIRD-5-OIRIN OIR: Node [chars] inserted

Explanation    Detected a card is inserted into the chassis.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-OIRD-5-OIROUT OIR: Node [chars] removed

Explanation    Detected a card is removed from the chassis.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-OIRD-7-ASYNC_ATTACH_FAIL Failed to attach handler for async events: [chars]

Explanation    Failed to attach handler for async events.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-OIRD-7-ASYNC_MSG_ERROR Received unexpected message: [dec]

Explanation    Received unexpected async message 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-OIRD-7-CHKPT_FAIL Failed to perform checkpoint services: [chars]

Explanation    Failed to perform checkpoint service functions.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-OIRD-7-EVM_CREATE_FAIL Failed to create event manager: [chars]

Explanation    Failed to create event manager.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-OIRD-7-MMAP_FAIL Failed to map OIR registers to process space

Explanation    Failed to mmap OIR registers.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-OIRD-7-MSG_ATTACH_FAIL Failed to attach handler for sync events: [chars]

Explanation    Failed to attach handler for sync events.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-OIRD-7-MSG_CHAN_CONN_FAIL Failed to connect to message channel: [chars]

Explanation    Failed to attach handler for sync messages.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-OIRD-7-MSG_ERROR Received unexpected message : [chars]

Explanation    Received unexpected message.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.=

Error Message     
 
    
    
   

%PLATFORM-OIRD-7-THREAD_CREATE_FAIL Failed to create thread [chars]

Explanation    Failed to create threads.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-OIRD-7-TIMER_CREATE_FAIL Failed to create timer: [chars]

Explanation    Failed to create timer.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-OIRD-7-TIMER_INIT_FAIL Failed to init timer events: [chars]

Explanation    Failed to init timer events.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-OIRD-7-UNEXPECTED Unexpected: [chars]: [chars]

Explanation    An unexpected condition encountered. This is not necessarily an error, but may help with debugging other problems elsewhere!

Recommended Action    Collect system log information. No action is required.

PCIMGR Messages

Error Message    
 
    
    
   

%PLATFORM-PCIMGR-2-SW_FATAL_ERROR fatal s/w error encountered - [chars], [chars], line [dec]

Explanation    An unrecoverable fatal s/w error was encountered, which resulted in process restart. The exact cause is appended to the error msg. Contact support with this information.

Recommended Action    Reload the board. *SUPPORT*

Error Message    
 
    
    
   

%PLATFORM-PCIMGR-3-MUTEX_LOCK_ERROR [chars]() line[dec]: pci bus manager mutex lock error

Explanation    The mutex lock for accessing register returned error

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-PCIMGR-3-MUTEX_UNLOCK_ERROR [chars]() line[dec]: pci bus manager mutex unlock error

Explanation    The mutex unlock for register operation returned error

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-PCIMGR-3-REG_PM_ERROR [chars]() line[dec]: pci bus manager failed register to platform mgr

Explanation    The function call to pm_fault_register_device returned fail

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

PCMCIA Messages

Error Message     
 
    
    
   

%PLATFORM-PCMCIA-3-PCI_DEV_ATTACH_ERROR PCMCIA driver failed to attach to the pci device

Explanation    can not get pci device info from PCI bus mgr

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-PCMCIA-3-PCI_SVR_ATTACH_ERROR Can't locate PCI server

Explanation    PCMCIA driver can not attach to PCI bus mgr

Recommended Action    'OIR PC Card'

Error Message     
 
    
    
   

%PLATFORM-PCMCIA-7-MEM_MAP_ERROR PCMCIA driver failed mapping io/mem addr space

Explanation    mem/io mapping form pcmcia driver failed

Recommended Action    'Check PC card insertion, format, or unsupported type'

Error Message     
 
    
    
   

%PLATFORM-PCMCIA-7-REG_PM_ERROR PCMCIA driver failed regist to platform mgr

Explanation    The function call to pm_fault_register_device returned fail

Recommended Action    'Check PCMCIAD process'

PCMCIAD Messages

Error Message     
 
    
    
   

%PLATFORM-PCMCIAD-7-FUNCTION_FAILED [chars]() failed: [chars]

Explanation    The function specified failed

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-PCMCIAD-7-KILL_FAILED kill to pid [dec] failed: [chars]

Explanation    Probably the process being killed has already exited

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-PCMCIAD-7-MSGSEND_FAILED MsgSendPulse operation failed: [chars]

Explanation    Failed to send pulse to resmgr thread to handle SIGCHLD

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-PCMCIAD-7-RESTART Pcmciad died and has come back up. Killing its old children

Explanation    pcmciad died and had come back up. It is killing children spawned by old pcmciad so that it can respawn new ones.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-PCMCIAD-7-SIGNAL_OP_FAILED Signal operation [chars] failed: [chars]

Explanation    Singal masking or handler installation failed

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-PCMCIAD-7-UNLINK_FAILED unlink of file [chars] failed: [chars]

Explanation    Should not happen.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

PCTL Messages

Error Message     
 
    
    
   

%PLATFORM-PCTL-3-gsp_msg_failed Failure to notify node state when [chars]: [chars]

Explanation    The internal communication channel among pctl threads is broken.

Recommended Action    Must restart the process.

PLAT_FIB_MPLS Messages

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-2-CRITICAL [chars]

Explanation    PLATFORM FIB, Critical error

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-2-CRITICAL_INFO [chars] [dec]

Explanation    PLATFORM FIB, Critical error information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-3-ERR_DETAIL [chars] [hex], [chars] [dec], [chars]([dec])

Explanation    PLATFORM FIB, error information

Recommended Action    Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-3-ERR_INFO [chars] [dec]

Explanation    PLATFORM FIB, error information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-3-ERR_INFO [chars] [dec]

Explanation    PLATFORM FIB, error information

Recommended Action    Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-3-ERR_INFO_HEX [chars] [hex]

Explanation    PLATFORM FIB, error information

Recommended Action    Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-3-ERR_STR [chars] [chars]([dec])

Explanation    PLATFORM FIB, error information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-3-ERR_STR [chars] [chars]([dec])

Explanation    PLATFORM FIB, error information

Recommended Action    Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-3-ERROR [chars]

Explanation    PLATFORM FIB, error

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-3-ERROR [chars]

Explanation    PLATFORM FIB, error

Recommended Action    Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-3-SHMEM Shared memory [chars], window: [dec] [hex] [chars]

Explanation    PLATFORM FIB, Shared memory errors

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-4-WARNING [chars]

Explanation    PLATFORM FIB, Warning

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-4-WARNING_INFO [chars] [dec]

Explanation    PLATFORM FIB, Warning information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-6-INFO [chars]

Explanation    PLATFORM FIB, Information

Recommended Action    *SUPPORT*

PLAT_FIB_RP Messages

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_RP-3-ERR_INFO PLATFORM-FIB-RP: Error - [chars] [dec]

Explanation    PLATFORM FIB, error information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_RP-3-ERR_INFO_VERBOSE PLATFORM-FIB-RP: Error - [chars] [chars] [chars] [dec]

Explanation    PLATFORM FIB, error information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_RP-3-ERROR PLATFORM-FIB-RP: Error - [chars]

Explanation    PLATFORM FIB, error

Recommended Action    *SUPPORT*

PLAT_FIB Messages

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB-3-ERR_INFO [chars] [dec]

Explanation    PLATFORM FIB, error information

Recommended Action    Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB-3-ERR_INFO_RT [chars] [dec]

Explanation    PLATFORM FIB, error information

Recommended Action    Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB-3-ERR_STR [chars]: [chars] ([unsigned int])

Explanation    PLATFORM FIB, error information

Recommended Action    Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB-3-ERR_STR_RT [chars]: [chars] ([unsigned int])

Explanation    PLATFORM FIB, error information

Recommended Action    Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB-3-ERROR [chars]

Explanation    PLATFORM FIB, error

Recommended Action    Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB-3-ERROR_RT [chars]

Explanation    PLATFORM FIB, error

Recommended Action    Please collect the console log, FIB traces (show cef trace loc ), FIB platform trace (show cef platform trace all loc ). Also notice if the error message is transient or persistent. Report to your technical support representative.

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB-6-FRR_INFO [chars] [hex]

Explanation    IP FRR PLATFORM FIB, Information

Recommended Action    The message is just for information. No action is needed.

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB-6-INFO [chars]

Explanation    PLATFORM FIB, Information

Recommended Action    The message is just for information. No action is needed.

PLAT_L2FIB_ATOM Messages

Error Message     
 
    
    
   

%PLATFORM-PLAT_L2FIB_ATOM-7-DEBUG_ERROR PLATFORM-L2FIB-ATOM: Error - [chars] [chars] [chars] [dec]

Explanation    Failed to initialize the debugging module in the platform L2FIB ATOM component.

Recommended Action    None, platform software will correct itself if this happens.

Error Message     
 
    
    
   

%PLATFORM-PLAT_L2FIB_ATOM-7-INIT_ERROR PLATFORM-L2FIB-ATOM: Error - [chars]

Explanation    Failed to initialize the ATOM module in the platform L2FIB ATOM component.

Recommended Action    None, platform software will correct itself if this happens.

Error Message     
 
    
    
   

%PLATFORM-PLAT_L2FIB_ATOM-7-LTRACE_ERROR PLATFORM-L2FIB-ATOM: Error - [chars] [dec] [chars] [dec]

Explanation    Failed to initialize the ltrace module in the platform L2FIB ATOM component.

Recommended Action    None, platform software will correct itself if this happens.

PLAT_L2FIB_DEBUG Messages

Error Message     
 
    
    
   

%PLATFORM-PLAT_L2FIB_DEBUG-7-REGISTER_FAILED PLATFORM-L2FIB: Error - [chars] [chars] [chars] [dec]

Explanation    Failed to initialize the debugging module in the platform L2FIB component.

Recommended Action    None, platform software will correct itself if this happens.

PLAT_L2FIB_LOCSW Messages

Error Message     
 
    
    
   

%PLATFORM-PLAT_L2FIB_LOCSW-7-DEBUG_ERROR PLATFORM-L2FIB-LOCSW: Error - [chars] [chars] [chars] [dec]

Explanation    Failed to initialize the debugging module in the platform L2FIB LOCSW component.

Recommended Action    None, platform software will correct itself if this happens.

Error Message     
 
    
    
   

%PLATFORM-PLAT_L2FIB_LOCSW-7-INIT_ERROR PLATFORM-L2FIB-LOCSW: Error - [chars]

Explanation    Failed to initialize the LOCSW module in the platform L2FIB LOCSW component.

Recommended Action    None, platform software will correct itself if this happens.

Error Message     
 
    
    
   

%PLATFORM-PLAT_L2FIB_LOCSW-7-LTRACE_ERROR PLATFORM-L2FIB-LOCSW: Error - [chars] [dec] [chars] [dec]

Explanation    Failed to initialize the ltrace module in the platform L2FIB LOCSW component.

Recommended Action    None, platform software will correct itself if this happens.

Error Message     
 
    
    
   

%PLATFORM-PLAT_L2FIB_LOCSW-7-PFI_ERROR PLATFORM-L2FIB-LOCSW: Error - [chars] [chars] [chars] [dec]

Explanation    Failed to initialize the PFI-IFH module in the platform L2FIB LOCSW component.

Recommended Action    None, platform software will correct itself if this happens.

PLAT_L2FIB_LTRACE Messages

Error Message     
 
    
    
   

%PLATFORM-PLAT_L2FIB_LTRACE-7-ERR_INFO_VERBOSE PLATFORM-L2FIB: Ltrace Error - [chars] [dec] [chars] [chars] [dec]

Explanation    PLATFORM L2FIB, error information

Recommended Action    *SUPPORT*

PLAT_L2FIB_RP Messages

Error Message     
 
    
    
   

%PLATFORM-PLAT_L2FIB_RP-3-DEBUG_ERROR PLATFORM-L2FIB-RP: Error - [chars] [chars] [chars] [dec]

Explanation    Failed to initialize the debugging module in the platform L2FIB (D)RP component.

Recommended Action    None, platform software will correct itself if this happens.

PLAT_L2FIB Messages

Error Message     
 
    
    
   

%PLATFORM-PLAT_L2FIB-7-CERR_ERROR PLATFORM-L2FIB: Error - [chars] [chars] [chars] [dec]

Explanation    Failed to initialize the cerrno module in the platform L2FIB component.

Recommended Action    None, platform software will correct itself if this happens.

Error Message     
 
    
    
   

%PLATFORM-PLAT_L2FIB-7-DEBUG_ERROR PLATFORM-L2FIB: Error - [chars] [chars] [chars] [dec]

Explanation    Failed to initialize the debugging module in the platform L2FIB component.

Recommended Action    None, platform software will correct itself if this happens.

Error Message     
 
    
    
   

%PLATFORM-PLAT_L2FIB-7-HW_INIT_ERROR PLATFORM-L2FIB: Error - [chars] [chars] [chars] [dec]

Explanation    Failed to initialize the Platform LC Hardware in L2FIB component.

Recommended Action    None, platform software will correct itself if this happens.

Error Message     
 
    
    
   

%PLATFORM-PLAT_L2FIB-7-LTRACE_ERROR PLATFORM-L2FIB: Error - [chars] [chars] [chars] [dec]

Explanation    Failed to initialize the ltrace module in the platform L2FIB component.

Recommended Action    None, platform software will correct itself if this happens.

PLAT_V6FIB_RP Messages

Error Message     
 
    
    
   

%PLATFORM-PLAT_V6FIB_RP-3-ERR_INFO PLATFORM-FIB-IPV6: [chars] [dec]

Explanation    Platform IPv6 FIB, Error information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_V6FIB_RP-3-ERR_INFO_VERBOSE PLATFORM-FIB-IPV6: [chars] [chars] [chars] [dec]

Explanation    Platform IPv6 FIB, Error information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_V6FIB_RP-3-ERROR PLATFORM-FIB-IPV6: [chars]

Explanation    Platform IPv6 FIB, Error

Recommended Action    *SUPPORT*

PLATFORM_HFR_LIB Messages

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_HFR_LIB-7-AM_I_SC_ERROR Failed to detect hardware board type. Reason: [chars].

Explanation    The platform library service call to find the hardware module type has failed. The calling application handles it appropriately.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

PLIM_16P_OC48 Messages

Error Message     
 
    
    
   

%PLATFORM-PLIM_16P_OC48-3-DEVICE_INTR_CLEAR No Framer/RAC devices are generating excessive interrupts

Explanation    The previously reported excessive interrupts condition has been cleared. Interrupt rate limiting has been disabled.

Recommended Action    none

Error Message     
 
    
    
   

%PLATFORM-PLIM_16P_OC48-3-DEVICE_INTR_DISABLE Excessive interrupts from the [chars] device of port [hex]

Explanation    The specified device is generating excessive interrupts. This message indicates that we are rate limiting the interrupt coming from this device. This indicates a potential HW issue, traffic forwarding (protection switching) may be impacted.

Recommended Action    Check the fiber or the peer connection. If the problem persist after checking fiber and peer router, please contact support.

Error Message     
 
    
    
   

%PLATFORM-PLIM_16P_OC48-6-OIM_OIR Optic Interface Module [chars] for port [dec]

Explanation    The Optic Interface Module (OIM) for the specified port has either been inserted or removed.

Recommended Action    No action is required.

PLATFORM_RP Messages

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_RP-0-CRASH GRP-B Rebooting Now - Replace your broken RP DRAM!

Explanation    Broken DRAM

Recommended Action    Try changing the DRAM to a known working one. If that doesn't work, then it is a software problem which requires a DDTS

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_RP-0-MBE_RMW GRP-B DRAM ECC Fatal Memory Error: MBE_RMW Addr=[hex], TSR=[hex], EER=[hex]

Explanation    GRP-B DRAM ECC Fatal Memory Error: MBE_RMW.

Recommended Action    Try changing the DRAM to a known working one. If that doesn't work, then it is a software problem which requires a DDTS

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_RP-0-SBE_NON_FATAL GRP-B DRAM ECC Non-Fatal Memory Error: SBE Addr=[hex], TSR=[hex], EER=[hex], synd=[hex]

Explanation    GRP-B DRAM ECC Non-Fatal Memory Error: Single Bit Error.

Recommended Action    Try changing the DRAM to a known working one. If that doesn't work, then it is a software problem which requires a DDTS

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_RP-0-SBE_RMW_FATAL GRP-B DRAM ECC Fatal Memory Error: SBE_RMW on Tiger Rev 4, Addr=[hex], TSR=[hex], EER=[hex], synd=[hex]

Explanation    GRP-B DRAM ECC Fatal Memory Error: SBE_RMW .

Recommended Action    Try changing the DRAM to a known working one. If that doesn't work, then it is a software problem which requires a DDTS

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_RP-0-SBE_RMW_NONFATAL GRP-B DRAM ECC Non-Fatal Memory Error: SBE_RMW Addr=[hex], TSR=[hex], EER=[hex], synd=[hex]

Explanation    GRP-B DRAM ECC Non-Fatal Memory Error: SBE_RMW.

Recommended Action    Try changing the DRAM to a known working one. If that doesn't work, then it is a software problem which requires a DDTS

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_RP-0-WPE GRP-B DRAM ECC Fatal Memory Error: WPE Addr=[hex], TSR=[hex], EER=[hex], WPEIR=[hex]

Explanation    GRP-B DRAM ECC Fatal Memory Error: Write Parity Error.

Recommended Action    Try changing the DRAM to a known working one. If that doesn't work, then it is a software problem which requires a DDTS

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_RP-3-child_init [chars]: child: [chars]

Explanation    Errors during the driver normal initialization

Recommended Action    Software problem which requires a DDTS

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_RP-3-CSAR_ECM [chars]

Explanation    none

Recommended Action    Software problem which requires a DDTS

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_RP-3-CSAR_HW_ERR [chars]. Error = [chars]

Explanation    csar hw error

Recommended Action    Software problem which requires a DDTS

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_RP-3-DIEP_SVC_INIT_ERR [chars] [chars]: service=[dec] service_status=[dec]

Explanation    Errors during the initialization of deferent services

Recommended Action    Software problem which requires a DDTS

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_RP-3-FIA_DEVCTL_ERR Unsupported devctl case [dec]

Explanation    An unexpected error has occurred.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_RP-3-FIA_MEM_CHIP_ERR ([chars]): no memory for chip data.

Explanation    An unexpected error has occurred.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_RP-3-FIA_MEM_ERROR ([chars]): FIA failed to initialize memory. Exiting

Explanation    An unexpected error has occurred.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_RP-3-FIA_MMAP_ERROR ([chars]): FIA memory mapping failed. Exiting

Explanation    An unexpected error has occurred.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_RP-3-FIA_SYNC_ERROR ([chars]): FIA failed to sync, los_status [hex], los_error [hex], fia_config [hex]

Explanation    This error usually indicates an internal hardware problem on the card.

Recommended Action    If there are other error reports about the switch fabric (CSC/SFC) then wait several minutes for corrective action. Otherwise, run diagnostics for slot reporting error. Use 'diag slot verbose' command. (This command may not work for the slot containing the primary route processor.) If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_RP-3-HW_DR_MMAP_FAILED [chars] h/w driver cannot do memory map

Explanation    An unexpected error has occurred.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_RP-3-LOW_CPU_MEM slot [dec]: [dec]M present, need [dec]M, RP CPU memory upgrade required

Explanation    For indicating insufficient RP CPU (ie. dram) memory

Recommended Action    Upgrade the CPU (dram) memory on the RP.

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_RP-3-NETIO_FAIL [chars]: dpc failure ( status : [dec] )

Explanation    An unexpected error has occurred.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_RP-3-NO_MUTEX Cannot get netio mutex

Explanation    An unexpected error has occurred.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_RP-3-NORMAL_INIT [chars]: [chars]

Explanation    none

Recommended Action    Software problem which requires a DDTS

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_RP-3-NORMAL_INIT_ERR [chars] [chars]

Explanation    Errors during the driver normal initialization

Recommended Action    Software problem which requires a DDTS

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_RP-3-PARTNER_INIT [chars]: [chars]

Explanation    none

Recommended Action    Software problem which requires a DDTS

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_RP-3-RESET_DATAPATH [chars]: [dec]

Explanation    Errors during the driver normal initialization

Recommended Action    Software problem which requires a DDTS

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_RP-7-DRP_PARTNER_HELPER [chars]

Explanation    Debugging message for drp_partner_helper

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_RP-7-FIA_NOT_RESET FIA was not reset before programming

Explanation    An unexpected error has occurred.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_RP-7-PARTNER_DEBUG [chars]

Explanation    Debugging code

Recommended Action    none

PM_OS Messages

Error Message     
 
    
    
   

%PLATFORM-PM_OS-2-PIC_ARRAY Failed to get PIC array for [chars] context ([hex]), using PFI context ([hex]) and interface handle ([hex]). PFI returned error ([chars]) Forwarding may be impacted on this interface.

Explanation    Failed to get PIC information from PFI that is required for forwarding packets from the specified interface.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show tech-support output, call your Cisco technical support representative and provide the representative with the gathered information.

PLU Messages

Error Message     
 
    
    
   

%PLATFORM-PLU-4-ERR_CORRECTED Hardware Table [dec] consistency restored

Explanation    Errors have been corrected.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-PLU-4-ERR_NOTIFY Hardware Table [dec] may be inconsistent. Attempting correction every [dec] seconds

Explanation    Errors were encountered trying to program hardware tables, forwarding on some entries may be affected, periodic error correction will be attempted.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-PLU-6-BKT_COMPACTED Hardware Table [dec] memory failures corrected with compaction

Explanation    A particular table had persistent memory failures due to heavily fragmented memory. As a last resort we attempted an aggressive memory recovery technique which succeeded. This is an informational message.

Recommended Action    No action is required because the memory failures were auto-corrected.

PLUTLU Messages

Error Message     
 
    
    
   

%PLATFORM-PLUTLU-4-ERR_RESTART_FAILED Failed to restart forwarding on metro

Explanation    An error was encountered while trying to restart forwarding on metro

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-PLUTLU-4-LTRACE_INIT_FAILED Failed to initialise ltrace buffers

Explanation    An error was encountered while initialising the PLU/TLU memory manager This is a non-fatal error for PLU/TLU manager caused by system instability or memory issues

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-PLUTLU-4-REPL_MODE_FAILED Failed to modify replication mode

Explanation    An error was encountered while trying to modify replication mode on metro

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

port_cfg Messages

Error Message     
 
    
    
   

%PLATFORM-port_cfg-3-INIT failed to initialize [chars]: [chars]

Explanation    A submodule was unable to initialze due to the specified 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.

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.

REEP Messages

Error Message     
 
    
    
   

%PLATFORM-REEP-3-ERROR_OPENING_ETHERNET_CONNECTION Failed to open connection to control ethernet server. Err = [chars]

Explanation    The control ethernet transport connection has been lost due to which send/receive for this process over the control ethernet will not work. This impacts standby RP booting.

Recommended Action    If this message is seen persistently, please capture output of 'show process eth_server' and 'show controllers backplane ethernet trace'.

Error Message     
 
    
    
   

%PLATFORM-REEP-3-GET_BOARD_TYPE_FAILED Platform call to determine boardtype failed

Explanation    This is indicative of some very fundamental problem in the the system. Some very basic system initialization has failed.

Recommended Action    Check the board which had the failure.

Error Message     
 
    
    
   

%PLATFORM-REEP-3-I2C_BKPLANE_READ_FAILED I2C access to read backplane EEPROM failed

Explanation    This is indicative of some very fundamental problem in the the system. I2C access to the backplane not working could be due to an I2C hang.

Recommended Action    Gather all the console logs and the i2c trace.

Error Message     
 
    
    
   

%PLATFORM-REEP-3-I2C_SERVER_CONNECT_FAILED Failed to connect to I2C server

Explanation    I2C service is currently unavailable.

Recommended Action    If this condition persists, it will preclude the standby route processor card in that chassis from coming up. So if it is seen persistently, please check the status of the i2c_server process on the active RP.

Error Message     
 
    
    
   

%PLATFORM-REEP-7-REPLY_SEND_FAILED Failed to send reply. Err = [dec]

Explanation    Failed to send reply to client ROMMON.

Recommended Action    Transient occurrence of this message is possible. If this message is seen persistently, and either an MSC, DRP or standby RP is not booting, it is because the control network connectivity service on this node is malfunctioning.

ROM_UPGRADE_LIB Messages

Error Message     
 
    
    
   

%PLATFORM-ROM_UPGRADE_LIB-7-ERROR [chars]

Explanation    --

Recommended Action    'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'

ROMMON_BURNER Messages

Error Message     
 
    
    
   

%PLATFORM-ROMMON_BURNER-3-BAD_ARG Bad command option: [chars] [chars]

Explanation    Bad coammand option.

Recommended Action    No action is required..

Error Message     
 
    
    
   

%PLATFORM-ROMMON_BURNER-3-FILE_OP_ERR [chars]: [chars] in function [chars] at line [dec]

Explanation    Error occured with file operations.

Recommended Action    No action is required..

Error Message     
 
    
    
   

%PLATFORM-ROMMON_BURNER-3-NO_MEM Failed in allocating memory in function [chars] at line [dec]

Explanation    No enough memory.

Recommended Action    No action is required..

Error Message     
 
    
    
   

%PLATFORM-ROMMON_BURNER-5-progress [chars] [chars]

Explanation    Output progress to RP console.

Recommended Action    No action is required..

Error Message     
 
    
    
   

%PLATFORM-ROMMON_BURNER-5-version ROMMON version [dec].[dec] is not supported for this board.

Explanation    Invalid ROMMON version to RP console.

Recommended Action    No action is required.

SCC Messages

Error Message     
 
    
    
   

%PLATFORM-SCC-2-BAD_ID_HW Failed Identification Test in [chars] [[dec]/[dec]]
The module in [chars] in this router may not be a genuine Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco SPA cards or other modules into a Cisco product is the cause of a support issue, Cisco may deny support under your warranty or under a Cisco support program such as SmartNet.

Explanation    'Hardware in the specified location could not be identified as a genuine Cisco product'

Recommended Action    'Contact TAC'

Error Message     
 
    
    
   

%PLATFORM-SCC-2-FAILED_ID_HW Failed Identification Test in [chars] [[dec]/[dec]]

Explanation    'There was a problem while identifying Hardware in the specified location.'

Recommended Action    'Contact TAC'

Error Message     
 
    
    
   

%PLATFORM-SCC-2-PROTO_HW Module ([chars]) is a registered proto-type for Cisco Lab use only, and not certified for live network operation.

Explanation    'Hardware in the specified location is a proto-type module that came from a Cisco Lab'

Recommended Action    'Contact TAC'

SHELFMGR Messages

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-0-CHASSIS_SHUTDOWN CRITICAL: CHASSIS SHUTDOWN initiated due to [chars]

Explanation    Chassis is shutting down due to reason mentioned.

Recommended Action    Examine chassis based on above message. If chassis shutdown is due to low voltage on both power shelves, then please examine the battery and replace if necessary. Note that in all cases of shutdown, the chassis needs to be manually power cycled, or the RPs physically OIR'd so as to boot the chassis again.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-1-CLEAR_ALL_FANTRAYS_REMOVED Atleast one tray has been inserted within 45 seconds (of removing all trays), so the chassis will not be shut down

Explanation    Software has detected that all fan trays were removed which would have shut down the system. But one fan tray was put back within 45 seconds, thus removing the need to shut down the system.

Recommended Action    *None*

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-1-CLEAR_BOTH_FC_REMOVED Atleast one fan controller card has been inserted within 45 seconds (of removing both fan controller cards), so the chassis will not be shut down

Explanation    Software has detected that both fan controller cards were removed which would have shut down the system. But one fan controller was put back within 45 seconds, thus removing the need to shut down the system.

Recommended Action    *None*

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-1-SET_ALL_FANTRAYS_REMOVED Critical Alarm: All fan trays have been removed from the chassis. If at least one tray is not inserted within 45 seconds, the chassis will be shutdown

Explanation    Software has detected that all fan trays have been removed from the chassisbut, but gives user 45 seconds to insert another tray. If no action is taken within 45 seconds, the chassis will be shut down.

Recommended Action    Insert a fan tray within 45 seconds.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-1-SET_BOTH_FC_REMOVED Both fan controller cards have been shutdown or removed from the chassis. If at least one fan controller card is not inserted within 45 seconds, the chassis will be shutdown

Explanation    Software has detected that both fan controller cards have been removed from the chassis but, but gives user 45 seconds to insert atleast one of them back into the chassis. If no action is taken within 45 seconds, the chassis will be shut down.

Recommended Action    Insert a fan controller card within 45 seconds.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-BOARD_NOT_SUPPORTED Shutdown node [chars] since CRS-DRP is not supported on CRS-4-CH

Explanation    This message indicates that the node is being shutdown because it is not supported on the CRS-4 platform.

Recommended Action    Remove the unsupported board and replace it with supported hardware.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-EMPTY_SERIAL_FAIL_BOOT Received boot request from a RP with an empty rack serial number, which indicates an attempt to boot a RP with ROMMON v1.19x as the standby. Boot request is being failed ! Refer to customer documentation for configuring a boot override

Explanation    Shelfmgr is failing a boot request because the serial number string in the boot request is empty. This happens if a RP with ROMMON 1.19x or older is sending a boot request.

Recommended Action    Please upgrade the booting RP to the latest recommended ROMMON.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-FAILED_LOAD Node [chars] fails to load IOS XR image, request to reset ...

Explanation    This message indicates that the node failed to load the IOS XR image for maximum number of retries and will be reset.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-FAILEDPOWERUP Unable to power up slot [chars], request to reset. reason: [chars]

Explanation    This message indicates the board in named slot failed to power up. The node will be reloaded automatically.

Recommended Action    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-FSMTIMEOUT_RESET Node [chars] is reset due to failed bootup

Explanation    This message indicates that the node is not able to boot up

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-INRESET_ALARM Power off node [chars] due to multiple critical alarms, putting into IN_RESET state

Explanation    This message indicates that the node has being brought down to IN_RESET state due to multiple critical alarms.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-INRESET_BRINGDOWN Cannot boot node [chars] due to multiple resets, putting into IN_RESET state

Explanation    This message indicates that the node has reached maximum number of resets allowed, therefore, it is brought down to IN_RESET state.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-NODE_RESET_ALARM Node [chars] in critical alarms, request to reset ...

Explanation    This message indicates that the Shelf Manager or Platform Manager encountered a critical alarm for the node specified. It will attempt to reset the board which sends the alarm.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-NODE_RESET_BRINGDOWN Reset node [chars] due to heartbeat loss

Explanation    This message indicates that the node is being reset because it failed to detect heartbeat pulses.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-POWERDOWN_RESET Node [chars] is powered off due to admin power off request

Explanation    This message indicates that the node will be reset because user has administratively 'power disable' or 'no power disable' the node.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-POWERRELOAD_RESET Node [chars] is reset through power off, then power on

Explanation    This message indicates that the node is being reloaded because of a critical environmental alarm.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-RP_SHUTDOWN RP SHUTDOWN INITIATED due to thermal alarms

Explanation    RP is shutting down due to reason mentioned.

Recommended Action    If there is a standby RP in the router, failover will automatically occur. Otherwise, chassis will be brought down and a manual reboot will be neccessary.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-SHUTDOWN Node [chars] is shutdown due to a critical alarm

Explanation    This message indicates that the node will be brought down because a critical environmental alarm occured.

Recommended Action    Check air-flow, fan trays, and make sure that chassis is well-cooled. Manually boot up the node once the chassis has been checked.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-SHUTDOWN_RESET Node [chars] is reset due to admin shut/no shut request

Explanation    This message indicates that the node will be reset because user has administratively 'shutdown' or 'no shutdown' the node.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-UNEXPECTED_EXIT Warning: [chars] exits, exit reason is [chars]([hex])

Explanation    This message indicates that the Shelf Manager or Platform Manager encountered a critical system(OS) error. It will exit right away.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-UNKNOWN_BOARD Boot request from node [chars] contains invalid board type, This board is being shutdown

Explanation    This message indicates that the board type cannot be recognized, therefore, the node will not be able to boot up. This usually caused by an invalid eeprom content.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-4-CMDLINE_BOOT_OVERRIDE_ENABLED Command line boot override to permit RPs with ROMMON 1.19x to boot as the standby has been enabled

Explanation    This is a warning message to indicate that using '-o override' option while booting the image, the operator will override the default IOS XR behavior which blocks the RP with ROMMON version v1.19x from coming up as the standby.

Recommended Action    Please upgrade the booting RP to the latest recommended ROMMON.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-4-EMPTY_SERIAL_BOOT_OVERRIDE WARNING !!! WARNING !!! Received boot request from a RP with an empty rack serial number. Permitting RP to boot due to [chars] override. Please upgrade RP ROMMON to latest recommended version

Explanation    This informational message informs the user that the Shelfmgr discovered an empty serial number due to an older ROMMON format, but it will allow the RP to boot because the operator had configured to override the restriction of disallow booting a RP with empty serial number.

Recommended Action    Please upgrade the booting RP to the latest recommended ROMMON.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-4-WARM_RLD_FAILED Receive [chars] from [chars], while waiting for MBI_HELLO_WARM

Explanation    Card seems to have been cold reloaded after an attempt to warm reload the card.

Recommended Action    Capture the shelfmgr log and use the 'show shelfmgr trace' CLI in admin-mode to fetch debug information. Also capture sysmgr_nv.log from LC.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-6-NO_PLIM Can not power on node [chars] due to absence of PLIM

Explanation    This message informs the user that the linecard will not be powered on because there is no PLIM inserted.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-6-NODE_NORESET Node [chars] is in NMON state, Cancel reset request

Explanation    This message indicates that the reset request caused by a critical alarm or heartbeat loss will not take effect because the node is being put in NMON state.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-6-NOREASON_RESET Node [chars] is reset due to UNKNOWN reason

Explanation    This message indicates that the node has been reset but the cause is unknown.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-6-USER_RESET Node [chars] is reset due to user reload request

Explanation    This message indicates that the node will be reset because user has requested to reload the node.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-6-WARM_RLD_JUMP Receive MBI_HELLO_ENA from [chars] at [WARM-RLD], status jumped to IOX-RUN

Explanation    Card comes up without MBI_HELLO or MBI_HELLO_WARM, need to check warm-reload is really done successfully.

Recommended Action    Initiate 'show warm-reload detail location ' and check Successful Attempts variables. If one of them is not zero, warm-reload is succeeded. Else, capture the shelfmgr log and use the 'show shelfmgr trace' CLI in admin-mode to fetch debug information. Also capture sysmgr.log and sysmgr_nv.log from LC.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-7-WARM_RLD_FO Receive MBI_HELLO_WARM from [chars] at [Present], LC seems to be under warm-reload

Explanation    Card seems warm reloaded successfully

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-7-WARM_RLD_OK Receive MBI_HELLO_WARM from [chars], new processes are coming up

Explanation    Card seems warm reloaded successfully

Recommended Action    No action is required.

SPENET Messages

Error Message     
 
    
    
   

%PLATFORM-SPENET-7-ERR_DEBUG [chars]

Explanation    Internal error while receiving a packet over the control network on to the service processor. Error is harmless if only one or two are seen. If seen in a persistent manner, call support.

Recommended Action    'Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.'

SPWD Messages

Error Message     
 
    
    
   

%PLATFORM-SPWD-0-ECC_REBOOT Excessive [chars] errors in last hour: [dec]. Node reboot scheduled

Explanation    Large numbers of single or mulitple bit ECC errors have been detected on the sp node in the past hour. The node will be rebooted.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-SPWD-0-MACHINE_CHECK_REBOOT Excessive machine checks in last hour: [dec]. Node reboot scheduled

Explanation    The sp cpu has received an excessive number of machine check exceptions. The node will be rebooted.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-SPWD-0-MISSED_WATCHDOG_REBOOT Multiple watchdog misses in last hour: [dec]. Node reboot scheduled

Explanation    The sp cpu has failed to service the hardware watchdog timer multiple times in the last hour. The node will be rebooted.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-SPWD-4-MACHINE_CHECK Current counts: machine checks: [dec], single bit ECC [dec], multibit ECC [dec], missed watchdogs: [dec]. Cumulative counts: machine checks: [dec], single bit ECC [dec], multibit ECC: [dec], watchdogs: [dec]

Explanation    The sp cpu has received a machine check exception. This can be due because the software has failed to service the watchdog timer, or because of excessive ECC errors.

Recommended Action    Examine the error counts for indications as to the cause of the machine check. Excessive machine checks will cause the sp to reset.

Error Message     
 
    
    
   

%PLATFORM-SPWD-6-HOURLY_COUNTS Hourly summary of watchdog counts: watchdog misses: [dec], single bit ECC errors: [dec], multiple bit ECC errors: [dec], machine check count: [dec].

Explanation    If the watchdog process detects a missed watchdog, single or multiple bit ecc error, or a machine check exception in the last hour, this message and a summary of error counts is printed.

Recommended Action    Contact support if this message is seen more than once a day.

SQUID_LOADER Messages

Error Message     
 
    
    
   

%PLATFORM-SQUID_LOADER-5-progress [chars] [chars]

Explanation    Output progress to RP console.

Recommended Action    No action is required.

SRP Messages

Error Message     
 
    
    
   

%PLATFORM-SRP-2-FATAL [chars] failed: [chars]

Explanation    Some requested operation failed during initialization. The text of the message displays the failed operation with error code.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-SRP-2-MUTEX [chars] failed: [chars]

Explanation    Thread synchronization failure has occurred. The text of the message displays the failed operation with error code.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

STP_SHIM Messages

Error Message     
 
    
    
   

%PLATFORM-STP_SHIM-6-LINK_STATE_CHANGE Spanning Tree Port [chars] state changed to [chars]

Explanation    Spanning Tree Port's state change indication.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-STP_SHIM-6-LOGGING_DEVICE [chars] will be used for storing control ethernet logs. Current logs are under [chars] directory and older logs are under [chars] directory.

Explanation    This is an informational message to indicate the location of for bcm.log, stp.log and stp_shim.log are.

Recommended Action    Do nothing

Error Message     
 
    
    
   

%PLATFORM-STP_SHIM-7-COPY_FAILED Copying of log file to [chars] failed. err = [dec], status = [dec]. Restarting to recover.

Explanation    This is an informational message to indicate that copying a log file to the storage device indicated has failed. This could be because the device was being formatted. The process will restart to recover.

Recommended Action    Do nothing

Error Message     
 
    
    
   

%PLATFORM-STP_SHIM-7-DRV_ERR [chars], [dec]

Explanation    Error condition from switch driver which may affect spanning tree operation on control ethernet. Normally spanning tree can tolerate a few of these errors as long as the driver comes back to a good state. Large number of these messages can indicate bad health of control-ethernet.

Recommended Action    Check if the switch driver process 'bcm_process' is up and running. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-STP_SHIM-7-NO_STORAGE_DEVICE_FOUND Copying of log files to persistent storage is suspended because no persistent storage device (harddisk/PCMCIA disk) found

Explanation    The service that copies /tmp/bcm.log and /tmp/stp.log to persistent storage, did not find any of harddisk, disk0, disk1 or bootflash available

Recommended Action    See if any of harddisk, disk0, disk1 or bootflash are accessible on the RP. If they are accessible, restart bcm_logger.

SYSLDR_LC Messages

Error Message     
 
    
    
   

%PLATFORM-SYSLDR_LC-2-NODE_RELOAD Reload notification received. Reloading in [dec] secs

Explanation    Message indicating that the kAA on the card has received a reload notification from sysldr for powering off the card and the card is going to reload soon. card state is IOX_RUNNING

Recommended Action    Sysldr log needs to be looked into to investigate on the node reload cause. As, sysldr requests to reload the card for various reasons.

Error Message     
 
    
    
   

%PLATFORM-SYSLDR_LC-2-NODE_RELOAD_NOW 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 slot' once to retry loading of the card, for reconnection of the fabric ping.

Error Message     
 
    
    
   

%PLATFORM-SYSLDR-2-MBI_NOLOAD slot [dec]: MBI cannot load IOX, retrying by reloading

Explanation    It is inability of MBI to boot a node's full image.

Recommended Action    This indicates a problem in communication or installation. Tech support should be contacted. Several attempts will be made to retry the image loading, and then the card will be put in the 'reset' state after too many failures.

Error Message     
 
    
    
   

%PLATFORM-SYSLDR-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 slot' 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_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 slot' 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 slot' 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 slot' once to retry loading of the card.

Error Message     
 
    
    
   

%PLATFORM-SYSLDR-3-SHUTDOWN Shutting down card in slot [dec], shutdown configured.

Explanation    Shutdown was configured using the 'hw-module shut' command.

Recommended Action    Ensure the shutdown was expected.

Error Message     
 
    
    
   

%PLATFORM-SYSLDR-3-TOO_LARGE slot [dec]: LC image too large, not loading

Explanation    For displaying notification of LC image being to large to download.

Recommended Action    Obtain a properly built image set.

Error Message     
 
    
    
   

%PLATFORM-SYSLDR-3-UNKNOWN_MOD slot=[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-3-VOL_SHUTDOWN Shutting down card in slot [dec], ordered by Envmon/FCTL/PSARB

Explanation    Card is shut down by Envmon or FCTL or Psarb. It is Volatile shutdown. Please use 'hardware-module reload ..' to bring the card back.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-SYSLDR-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 slot' once to retry loading of the LC.

Error Message     
 
    
    
   

%PLATFORM-SYSLDR-4-WARM_RLD_FAILED Receive DOWNLOAD_SUCCESS from slot [dec], while waiting for DOWNLOAD_SUCCESS_WARM

Explanation    Card seems to have been cold reloaded after an attempt to warm reload the card.

Recommended Action    Capture the sysldr log and use the 'show sysldr trace warm-reload' CLI in admin-mode to fetch debug information. Also capture sysmgr_nv.log from LC.

Error Message     
 
    
    
   

%PLATFORM-SYSLDR-4-WARN_LC_MEM slot [dec]: [dec]M present, recommend [dec]M memory

Explanation    For indicating possibly insufficient LC CPU (ie. dram) memory

Recommended Action    Upgrade the amount of CPU (dram) memory on the LC.

Error Message     
 
    
    
   

%PLATFORM-SYSLDR-4-WARN2 [chars]

Explanation    Unexpected low severity problem.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-SYSLDR-5-BANDWIDTH Fabric bandwidth change: [chars]

Explanation    Failure/recovery/OIR of one or more SFC's or CSC's

Recommended Action    Verify that the desired fabric bandwidth is being used.

Error Message     
 
    
    
   

%PLATFORM-SYSLDR-5-BANDWIDTH_RESTART Fabric bandwidth change: Restarting card in slot [dec]

Explanation    Restoration or OIR of fabric bandwidth has allowed a card to be restarted

Recommended Action    Celebrate.

Error Message     
 
    
    
   

%PLATFORM-SYSLDR-5-DRP_DISABLED DRP in slot [dec] is now disabled, reloading

Explanation    The RP is going to bring down from IOX running state because keep alive message ping is not received to sysldr.

Recommended Action    Ensure that the disabling of this DRP was expected.

Error Message     
 
    
    
   

%PLATFORM-SYSLDR-5-JOIN Joined slot [dec] - already running IOX-LC

Explanation    LC join notification because of sysldr restarted.

Recommended Action    Ensure that the *sysldr* restart was expected.

Error Message     
 
    
    
   

%PLATFORM-SYSLDR-5-LC_ENABLED LC in slot [dec] is now running IOX

Explanation    For displaying health and readiness of LC

Recommended Action    Ensure that the (implied) LC restart was expected.

Error Message     
 
    
    
   

%PLATFORM-SYSLDR-5-MBUS_EEPROM slot [dec]: Unable to get mbus eeprom contents

Explanation    For displaying notification of mbus nonresponsiveness to get eeprom contents.

Recommended Action    This indicates that mbus request to get eeprom contents for show diag command has timed out. Retry the command again.

Error Message     
 
    
    
   

%PLATFORM-SYSLDR-5-MON_DRP Now monitoring DRP in slot [dec] - running IOX-DRP

Explanation    For displaying notification of discovered DRP.

Recommended Action    Ensure that the existence of the external DRP was expected.

Error Message     
 
    
    
   

%PLATFORM-SYSLDR-5-MON_RP Now monitoring RP in slot [dec] - running IOX-RP

Explanation    For displaying notification of discovered RP.

Recommended Action    Ensure that the existence of the external RP was expected.

Error Message     
 
    
    
   

%PLATFORM-SYSLDR-5-OIRIN OIR: Node [chars] inserted

Explanation    Entity specified in the messages is inserted into the chassis.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-SYSLDR-5-OIROUT OIR: Node [chars] removed

Explanation    Entity specified in the messages is removed from the chassis.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-SYSLDR-5-RESTART Restarted slot [dec] - now running IOX-LC

Explanation    For displaying LC restart notification.

Recommended Action    Ensure that the LC restart was expected.

Error Message     
 
    
    
   

%PLATFORM-SYSLDR-5-RESTART_REQ Accepted restart request for slot [dec]

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-0-SW_INIT_ERR A software error occurred in the ToFab driver component during initialization: [chars]

Explanation    The fabricq_prp_driver process which controls the ToFab driver on the route processor has failed to initalize and cannot recover automatically. This is a software fault. The ToFab driver controls the hardware that transmits data to the fabric. It runs in the fabricq_prp_driver process. An unrecoverable failure of the fabricq_prp_driver process may prevent this route processor card from communicating with other cards on the chassis. %s indicates the type failure

Recommended Action    Restart the fabricq_prp_driver process with the following command: 'process restart fabricq_prp_driver' If the error message appears again, then: if a redundant route processor card has been configured: 1 - force a failover with the following command in admin mode: 'redundancy switchover' 2 - reload the route processor card that failed with the following command in admin mode: 'reload location RP/0/x/CPU0 ' where x is the slot of route processor that generated the error. if no redundant RP is configured you will need to reboot the router by issuing the reload command. If the error recurs call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-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] greater than or equal to 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.

UPGRADE_FPD Messages

Error Message     
 
    
    
   

%PLATFORM-UPGRADE_FPD-2-FATAL [chars]

Explanation    A fatal error was encountered, and the program exited.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-UPGRADE_FPD-3-ASYNC_ATTACH Failed to attach async message handler : [chars]

Explanation    Failed to attach async message handler

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-UPGRADE_FPD-3-CHAN_CREATE Failed to create upgrade-fpd channel : [chars]

Explanation    Failed to create lc_fpd_upgrade (driver) channel using event_manager_create.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-UPGRADE_FPD-3-ERROR [chars]

Explanation    An error was encountered

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-UPGRADE_FPD-3-EVT_BLOCK Event block failed : [chars]

Explanation    Failed to block event

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-UPGRADE_FPD-3-FAILED Failed to update FPD : [chars] [chars]

Explanation    The update operation for the specified FPD has failed.

Recommended Action    Retry the operation to update the image. If the retry operation fails, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/cgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     
 
    
    
   

%PLATFORM-UPGRADE_FPD-3-MSG_REPLY Msg reply failed : [chars]

Explanation    Failed to send message reply

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-UPGRADE_FPD-3-SYNC_ATTACH Failed to attach sync message handler : [chars]

Explanation    Failed to attach sync message handler

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-UPGRADE_FPD-4-DOWN_REV [chars] [chars] instance [dec] is down-rev (V[dec].[dec]), upgrade to (V[dec].[dec]). Use the upgrade hw-module fpd CLI in admin mode.

Explanation    For displaying down-rev notification.

Recommended Action    tech support should be contacted for upgrade instructions

Error Message     
 
    
    
   

%PLATFORM-UPGRADE_FPD-4-UP_REV [chars] [chars] instance [dec] is severely up-rev (V[dec].[dec]), downgrade to (V[dec].[dec]). Use the upgrade hw-module fpd CLI in admin mode.

Explanation    For displaying severely up-rev notification.

Recommended Action    tech support should be contacted for downgrade instructions

Error Message     
 
    
    
   

%PLATFORM-UPGRADE_FPD-4-WARNING [chars]

Explanation    display warning messages

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-UPGRADE_FPD-6-PASSED Successfully [chars] [chars] subtype image for [chars] on location [chars]

Explanation    It indicates that a FPD has been upgraded or downgraded successfully. The current image version and the upgraded image version are displayed.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-UPGRADE_FPD-6-START Starting to [chars] [chars] subtype image from [dec].[dec] to [dec].[dec] for [chars] on location [chars]

Explanation    It indicates that a FPD image upgrade or downgrade has started. The current image version and the upgraded image version are displayed.

Recommended Action    No action is required.

WD Messages

Error Message     
 
    
    
   

%PLATFORM-WD-0-INTERRUPT_REBOOT Excessive watchdog interrupts in last hour: [dec]. Node reboot scheduled

Explanation    The cpu has received an excessive number of watchdogs interrupts in the last hour. The node will be rebooted. The total number of interrupts received since the hourly counters were last cleared is displayed.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-WD-4-INTERRUPT Watchdog interrupt: [dec], total in last hour: [dec]

Explanation    The cpu has received an interrupt from the watchdog timer. This indicates that the cpu was too busy to service the watchdog timer for a period of time in the recent past. The interrupt was handled and the timer serviced. Excessive watchdog interrupts will result in the node being reset. The number of interrupts since the cpu last serviced the watchdog and the total number of interrupts since the hourly timer was last cleared are displayed.

Recommended Action    Determine the reason for the watchdog timer expiring. Possible causes include a process spinning at high priority or hardware interrupts flooding the cpu.

Error Message     
 
    
    
   

%PLATFORM-WD-6-HOURLY_COUNT Hourly summary of watchdog interrupts: watchdog interrupts: [dec].

Explanation    This message is displayed once an hour if a watchdog interrupt is seen by the cpu. The count displayed is since the hourly counter was last cleared.

Recommended Action    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

XCVR Messages

Error Message     
 
    
    
   

%PLATFORM-XCVR-3-ERROR XCVR-Err: [chars]

Explanation    This is an error message from the XCVR, it indicates that something has gone wrong internally in the XCVR.

Recommended Action    File a DDTS

Error Message     
 
    
    
   

%PLATFORM-XCVR-6-INFO XCVR-Info: [chars]

Explanation    This is an informational message from the XCVR

Recommended Action    *RECUR*

Error Message     
 
    
    
   

%PLATFORM-XCVR-6-OIR XCVR-OIR: [chars]

Explanation    This is an informational message from the XCVR

Recommended Action    *RECUR*

Error Message     
 
    
    
   

%PLATFORM-XCVR-7-TRACE XCVR-Trace: [chars]

Explanation    This is a debuging message from the XCVR

Recommended Action    *NONE*