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

Platform Messages

Table Of Contents

Platform Messages

ALPHA_DISPLAY Messages

ASM Messages

BCM_SWITCH Messages

BP_SERVER Messages

BPE Messages

BRIDGE3 Messages

CANB_SERVER Messages

CARD Messages

CARDMGR Messages

CCTL_ENS Messages

CCTL Messages

CEMGBL Messages

CETHHA Messages

CHP Messages

CLKCTRL_T Messages

COMMON Messages

CPUCTRL_PCI Messages

CPUCTRL Messages

CPUCTRLLIB Messages

CROSSBAR Messages

DIAGS Messages

DISCOVERY Messages

DRP_PAIRING_CLIENT Messages

DRP_PAIRING Messages

DSC Messages

DSCMEDIA Messages

EIO Messages

ENVMON_MON Messages

ENVMON Messages

ETH_SRVR Messages

ETHER_CTRL_DLL Messages

ETHER_CTRL Messages

FABARBITER Messages

FABIO Messages

FABRIC_CTRL Messages

FAN Messages

FAULT Messages

FCA Messages

FDIAGS Messages

FFQ Messages

FIB_DBG Messages

FIB_IDB_LIB Messages

FIB_LTRACE Messages

FPD_BURNER 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

HBAGENT Messages

HD Messages

HFR_IP_EA Messages

HFR_IPV6_EA Messages

HFR_L2FIB_METRO_SHOW Messages

HFR_LCPM_SHOW Messages

HFR_MPLS_EA Messages

HFR_PM_TEST Messages

HFR_PM Messages

HSR_ES_CLI Messages

I2C Messages

INTCTRL Messages

INTEG_SWITCH Messages

INV_AGENT Messages

INV Messages

INVMGR Messages

IPCP_SRVR Messages

LAMPTEST Messages

C_CPUCTRL Messages

libpcmcia_ide Messages

libpcmcia_linux Messages

MANSDORF Messages

MBI_HELLO Messages

MBI_LIB_ACCESS Messages

MBI_LIB Messages

MBIMGR Messages

MBUS Messages

MCE Messages

MDIO Messages

MLAN Messages

MPC8641 Messages

MSM Messages

NETIO_LC Messages

NFEA_HW_PROG Messages

NP Messages

OBFL Messages

OIRD Messages

PCIER Messages

PCIMGR Messages

PCMCIAD Messages

PCTL Messages

PEX8111 Messages

PEX8508 Messages

PEXRC Messages

PFM Messages

PLAT_FIB_HAL Messages

PLAT_FIB_MPLS Messages

PLAT_FIB_RP Messages

PLAT_FIB Messages

PLAT_L2FIB_ATOM Messages

PLAT_L2FIB_BRIDGING Messages

PLAT_L2FIB_COMMON Messages

PLAT_L2FIB_DEBUG Messages

PLAT_L2FIB_LOCSW Messages

PLAT_L2FIB_LTRACE Messages

PLAT_L2FIB_METRO Messages

PLAT_L2FIB_RP Messages

PLAT_L2FIB Messages

PLAT_L2VPN_DEBUG Messages

PLAT_L2VPN_FGID Messages

PLAT_L2VPN_LTRACE Messages

PLAT_L2VPN Messages

PLAT_V6FIB_RP Messages

PLATFORM_HFR_LIB Messages

PLIM_16P_OC48 Messages

PLIM_IPC Messages

PLIM_SERVICES Messages

PLU Messages

PLUTLU Messages

PORT_CFG Messages

POWERMGR Messages

PRP_HW Messages

PRP3_FABIO Messages

PRP3_SLR_FABIO Messages

PSARBLC Messages

PUNT_SWITCH Messages

PUNT Messages

PWR_SUPPLY Messages

REDDRV Messages

REEP Messages

ROM_UPGRADE_LIB Messages

ROMMON_BURNER Messages

RSP_CPUCTRL Messages

SC Messages

SCC Messages

SERVICE_AGENT Messages

SFP Messages

SHELFMGR_HAL Messages

SHELFMGR Messages

SHOW_VERSION_CMD Messages

SIMMUX_QAD_SERVER Messages

SIMMUX_SERVER Messages

SPA_JBI Messages

SPWD Messages

SQUID_LOADER Messages

STP_SHIM Messages

SYSLDR_RP Messages

SYSLDR Messages

TEMPO Messages

TFQ Messages

TIMESYNC Messages

TLU Messages

TSEC Messages

UPGRADE_FPD Messages

UPGRADE Messages

USB Messages

VCDMA Messages

WD_PLATFORM_SP Messages

WD_PLATFORM Messages

XCVR Messages

XFP 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

BPE Messages

BRIDGE3 Messages

CANB_SERVER Messages

CARD Messages

CARDMGR Messages

CCTL_ENS Messages

CCTL Messages

CEMGBL Messages

CETHHA Messages

CHP Messages

CLKCTRL_T Messages

COMMON Messages

CPUCTRL_PCI Messages

CPUCTRL Messages

CPUCTRLLIB Messages

CROSSBAR Messages

DIAGS Messages

DISCOVERY Messages

DRP_PAIRING_CLIENT Messages

DRP_PAIRING Messages

DSC Messages

DSCMEDIA Messages

EIO Messages

ENVMON_MON Messages

ENVMON Messages

ETH_SRVR Messages

ETHER_CTRL_DLL Messages

ETHER_CTRL Messages

FABARBITER Messages

FABIO Messages

FABRIC_CTRL Messages

FAN Messages

FAULT Messages

FCA Messages

FDIAGS Messages

FFQ Messages

FIB_DBG Messages

FIB_IDB_LIB Messages

FIB_LTRACE Messages

FPD_BURNER 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

HBAGENT Messages

HD Messages

HFR_IP_EA Messages

HFR_IPV6_EA Messages

HFR_L2FIB_METRO_SHOW Messages

HFR_LCPM_SHOW Messages

HFR_MPLS_EA Messages

HFR_PM_TEST Messages

HFR_PM Messages

HSR_ES_CLI Messages

I2C Messages

INTCTRL Messages

INTEG_SWITCH Messages

INV_AGENT Messages

INV Messages

INVMGR Messages

IPCP_SRVR Messages

LAMPTEST Messages

C_CPUCTRL Messages

libpcmcia_ide Messages

libpcmcia_linux Messages

MANSDORF Messages

MBI_HELLO Messages

MBI_LIB_ACCESS Messages

MBI_LIB Messages

MBIMGR Messages

MBUS Messages

MCE Messages

MDIO Messages

MLAN Messages

MPC8641 Messages

MSM Messages

NETIO_LC Messages

NFEA_HW_PROG Messages

NP Messages

OBFL Messages

OIRD Messages

PCIER Messages

PCIMGR Messages

PCMCIAD Messages

PCTL Messages

PEX8111 Messages

PEX8508 Messages

PEXRC Messages

PFM Messages

PLAT_FIB_HAL Messages

PLAT_FIB_MPLS Messages

PLAT_FIB_RP Messages

PLAT_FIB Messages

PLAT_L2FIB_ATOM Messages

PLAT_L2FIB_BRIDGING Messages

PLAT_L2FIB_COMMON Messages

PLAT_L2FIB_DEBUG Messages

PLAT_L2FIB_LOCSW Messages

PLAT_L2FIB_LTRACE Messages

PLAT_L2FIB_METRO Messages

PLAT_L2FIB_RP Messages

PLAT_L2FIB Messages

PLAT_L2VPN_DEBUG Messages

PLAT_L2VPN_FGID Messages

PLAT_L2VPN_LTRACE Messages

PLAT_L2VPN Messages

PLAT_V6FIB_RP Messages

PLATFORM_HFR_LIB Messages

PLIM_16P_OC48 Messages

PLIM_IPC Messages

PLIM_SERVICES Messages

PLU Messages

PLUTLU Messages

PORT_CFG Messages

POWERMGR Messages

PRP_HW Messages

PRP3_FABIO Messages

PRP3_SLR_FABIO Messages

PSARBLC Messages

PUNT_SWITCH Messages

PUNT Messages

PWR_SUPPLY Messages

REDDRV Messages

REEP Messages

ROM_UPGRADE_LIB Messages

ROMMON_BURNER Messages

RSP_CPUCTRL Messages

SC Messages

SCC Messages

SERVICE_AGENT Messages

SFP Messages

SHELFMGR_HAL Messages

SHELFMGR Messages

SHOW_VERSION_CMD Messages

SIMMUX_QAD_SERVER Messages

SIMMUX_SERVER Messages

SPA_JBI Messages

SPWD Messages

SQUID_LOADER Messages

STP_SHIM Messages

SYSLDR_RP Messages

SYSLDR Messages

TEMPO Messages

TFQ Messages

TIMESYNC Messages

TLU Messages

TSEC Messages

UPGRADE_FPD Messages

UPGRADE Messages

USB Messages

VCDMA Messages

WD_PLATFORM_SP Messages

WD_PLATFORM Messages

XCVR Messages

XFP 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-6-CHANGE Alpha display on node [chars] changed to [chars] in state [chars]

Explanation    Message to indicate that alpha-display was updated with new string or state.

Recommended Action    None.

Error Message     
 
    
    
   

%PLATFORM-ALPHA_DISPLAY-6-CHANGE Alpha display on node [chars] changed to [chars] in state [chars]

Explanation    Message to indicate that alpha-display was updated with new string or state.

Recommended Action    None.

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 equals [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 equals [chars], errno equals [dec]

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

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

Error Message     
 
    
    
   

%PLATFORM-ASM-3-FIA_INTFERR Assembler detected a FIA interface error: Data [hex]

Explanation    Assembler detected an error with the fia interface. The hex number indicates the error cause register value. This usually indicates a hardware problem on the RP.

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

Error Message     
 
    
    
   

%PLATFORM-ASM-3-FIA_PARITYERR Assembler detected a FIA parity error: Data [hex]

Explanation    A parity error has been detected on the assembler to fia interface. The hex number indicates the error cause register value. This usually indicates a hardware problem on the RP.

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

Error Message     
 
    
    
   

%PLATFORM-ASM-3-FQEMPTY_ERR Assembler detected a free queue empty error: Data [hex]

Explanation    Assembler detected a that the free queue is empty. The hex number indicates the error cause register value.

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

Error Message     
 
    
    
   

%PLATFORM-ASM-3-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-GEN_INFO assembler dll: general information,[chars]

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 equals [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 equals [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 [dec] 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 [chars] 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-2-LINK_STATE_CHANGE Spanning Tree Port [chars] state changed to [chars]

Explanation    Spanning Tree Port's state change indication.

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

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

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

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.

BPE Messages

Error Message     
 
    
    
   

%PLATFORM-BPE-3-ERR_INIT Initialization Error: [chars] Reason: [chars]. Exiting.

Explanation    BPE Driver encountered a fatal error and is not able to recover. The supplied text string will explain the reason. 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-BPE-3-ERR_MEM_ALLOC Error Allocating [dec] bytes of memory

Explanation    BPE encountered a fatal memory allocation 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-BPE-5-ERR_CONT Continuing execution: [chars]: Caused by [chars]

Explanation    This message indicates an error occurred beyond which execution of the bpe_driver may continue, attempting to effect recovery or work-around internally, minimizing loss of information/functionality.

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-BPE-7-ERR_EVM_CREATE Event Manager create failed for [chars]. Reason: [chars]

Explanation    BPE 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-BPE-7-ERR_EVM_NOTIFY Event Manager notify failed for [chars]. Reason: [chars]

Explanation    BPE 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-BPE-7-ERR_EXIT Exit on error: [chars]: Caused by [chars]

Explanation    An error occurred in BPE Driver which requires exiting (and, hence, restarting) the process.

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-BPE-7-ERR_LWM_EVENT_BLOCK LWM Event Manager event block failed. Reason: [chars]

Explanation    BPE 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-BPE-7-ERR_LWM_REPLY An error occurred during LWM message reply. Reason: [chars]

Explanation    bpe LWM reply 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.

BRIDGE3 Messages

Error Message     
 
    
    
   

%PLATFORM-BRIDGE3-2-DDR_BUS_BIT_STUCK_0 DDR bus data bit stuck-0

Explanation    DDR bus databit stuck on bridge3 instance-0.

Recommended Action    Please reload the board using the command 'reload 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-BRIDGE3-2-DDR_BUS_BIT_STUCK_1 DDR bus data bit stuck-1

Explanation    DDR bus databit stuck on bridge3 instance-1.

Recommended Action    Please reload the board using the command 'reload 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-BRIDGE3-2-DDR_LOSS_OF_SYNC_0 DDR interface loss of sync-0

Explanation    Loss of sync on DDR interface on bridge3 instance-0.

Recommended Action    Please reload the board using the command 'reload 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-BRIDGE3-2-DDR_LOSS_OF_SYNC_1 DDR interface loss of sync-1

Explanation    Loss of sync on DDR interface on bridge3 instance-1.

Recommended Action    Please reload the board using the command 'reload 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-BRIDGE3-2-MAC_0_RX_FRAME_ERR_1 MAC on NPU-0 receive frame error - 1

Explanation    MAC on NPU-0 received an errored frame interface on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-2-NPU_0_LOSS_OF_SYNC_0 NPU-0 interface loss of sync-0

Explanation    Loss of sync on NPU-0 interface on bridge3 instance-0.

Recommended Action    Please reload the board using the command 'reload 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-BRIDGE3-2-NPU_0_LOSS_OF_SYNC_1 NPU-0 interface loss of sync-1

Explanation    Loss of sync on NPU-0 interface on bridge3 instance-1.

Recommended Action    Please reload the board using the command 'reload 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-BRIDGE3-2-NPU_1_LOSS_OF_SYNC_0 NPU-1 interface loss of sync-0

Explanation    Loss of sync on NPU-1 interface on bridge3 instance-0.

Recommended Action    Please reload the board using the command 'reload 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-BRIDGE3-2-NPU_1_LOSS_OF_SYNC_1 NPU-1 interface loss of sync-1

Explanation    Loss of sync on NPU-1 interface on bridge3 instance-1.

Recommended Action    Please reload the board using the command 'reload 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-BRIDGE3-2-QDR_DATABIT_STUCK_0 QDR memory data bit stuck-0

Explanation    QDR memory databit stuck on bridge3 instance-0.

Recommended Action    Please reload the board using the command 'reload 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-BRIDGE3-2-QDR_DATABIT_STUCK_1 QDR memory data bit stuck-1

Explanation    QDR memory databit stuck on bridge3 instance-1.

Recommended Action    Please reload the board using the command 'reload 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-BRIDGE3-2-QDR_MEM_SELFTEST_FAIL_0 QDR memory self test failure on bridge3-0

Explanation    QDR memory self test failure on bridge3 instance-0.

Recommended Action    Please reload the board using the command 'reload location '. Please verify the bridge3 FPGA is loaded properly. 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-BRIDGE3-2-QDR_MEM_SELFTEST_FAIL_1 QDR memory self test failure on bridge3-1

Explanation    QDR memory self test failure on bridge3 instance-1.

Recommended Action    Please reload the board using the command 'reload location '. Please verify the bridge3 FPGA is loaded properly. 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-BRIDGE3-2-REG_ACCESS_FAIL_0 Register access failure on bridge3-0

Explanation    Register access failure on bridge3 instance-0.

Recommended Action    Please reload the board using command 'reload 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-BRIDGE3-2-REG_ACCESS_FAIL_1 Register access failure on bridge3-1

Explanation    Register access failure on bridge3 instance-1.

Recommended Action    Please reload the board using the command 'reload 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-BRIDGE3-2-XAUI_0_CHAN_SYNC_0 XAUI to NPU-0 chan sync error on bridge3-0

Explanation    XAUI to NPU-0 chan sync error on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-2-XAUI_0_CHAN_SYNC_1 XAUI to NPU-0 chan sync error on bridge3-1

Explanation    XAUI to NPU-0 chan sync error on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-2-XAUI_0_CHAR_ALIGN_0 XAUI to NPU-0 char alignment error on bridge3-0

Explanation    XAUI to NPU-0 char alignment error on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-2-XAUI_0_CHAR_ALIGN_1 XAUI to NPU-0 char alignment error on bridge3-1

Explanation    XAUI to NPU-0 char alignment error on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-2-XAUI_0_MGT_CV_0 XAUI to NPU-0 MGT code violation on bridge3-1

Explanation    XAUI to NPU-0 MGT code violation on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-2-XAUI_0_MGT_CV_1 XAUI to NPU-0 MGT code violation on bridge3-1

Explanation    XAUI to NPU-0 MGT code violation on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-2-XAUI_0_RX_ALIGN_LOSS_0 XAUI to NPU-0 Rx alignment loss - 0

Explanation    Rx alignment loss on XAUI to NPU-0 interface on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-2-XAUI_0_RX_ALIGN_LOSS_1 XAUI to NPU-0 Rx alignment loss - 1

Explanation    Rx alignment loss on XAUI to NPU-0 interface on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-2-XAUI_0_STAT_VEC_0 XAUI to NPU-0 state error on bridge3-0

Explanation    XAUI to NPU-0 state error on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-2-XAUI_0_STAT_VEC_1 XAUI to NPU-0 state error on bridge3-1

Explanation    XAUI to NPU-0 state error on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-2-XAUI_1_CHAN_SYNC_0 XAUI to NPU-1 chan sync error on bridge3-0

Explanation    XAUI to NPU-1 chan sync error on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-2-XAUI_1_CHAN_SYNC_1 XAUI to NPU-1 chan sync error on bridge3-1

Explanation    XAUI to NPU-1 chan sync error on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-2-XAUI_1_CHAR_ALIGN_0 XAUI to NPU-1 char alignment error on bridge3-0

Explanation    XAUI to NPU-1 char alignment error on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-2-XAUI_1_CHAR_ALIGN_1 XAUI to NPU-1 char alignment error on bridge3-1

Explanation    XAUI to NPU-1 char alignment error on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-2-XAUI_1_MGT_CV_0 XAUI to NPU-1 MGT code violation on bridge3-0

Explanation    XAUI to NPU-1 MGT code violation on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-2-XAUI_1_MGT_CV_1 XAUI to NPU-1 MGT code violation on bridge3-1

Explanation    XAUI to NPU-1 MGT code violation on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-2-XAUI_1_RX_ALIGN_LOSS_0 XAUI to NPU-1 Rx alignment loss - 0

Explanation    Rx alignment loss on XAUI to NPU-1 interface on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-2-XAUI_1_RX_ALIGN_LOSS_1 XAUI to NPU-1 Rx alignment loss - 1

Explanation    Rx alignment loss on XAUI to NPU-1 interface on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-2-XAUI_1_STAT_VEC_0 XAUI to NPU-1 state error on bridge3-0

Explanation    XAUI to NPU-1 state error on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-2-XAUI_1_STAT_VEC_1 XAUI to NPU-1 state error on bridge3-1

Explanation    XAUI to NPU-1 state error on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-2-XAUI_A_DATABUS_STUCK_0 XAUI-A databus stuck-0

Explanation    XAUI-A databus stuck on bridge3 instance-0.

Recommended Action    Please reload the board using the command 'reload 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-BRIDGE3-2-XAUI_A_DATABUS_STUCK_1 XAUI-A databus stuck-1

Explanation    XAUI-A databus stuck on bridge3 instance-1.

Recommended Action    Please reload the board using the command 'reload 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-BRIDGE3-3-CHKSUM_ERR_0_FIA_0 Checksum error - 0 from FIA on bridge3-0

Explanation    Checksum error - 0 from FIA on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-CHKSUM_ERR_0_FIA_1 Checksum error - 0 from FIA on bridge3-1

Explanation    Checksum error - 0 from FIA on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-CHKSUM_ERR_1_FIA_0 Checksum error - 1 from FIA on bridge3-0

Explanation    Checksum error - 1 from FIA on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-CHKSUM_ERR_1_FIA_1 Checksum error - 1 from FIA on bridge3-1

Explanation    Checksum error - 1 from FIA on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-CRC_ERR_0_FIA_0 CRC error - 0 from FIA on bridge3-0

Explanation    CRC error - 0 from FIA on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-CRC_ERR_0_FIA_1 CRC error - 0 from FIA on bridge3-1

Explanation    CRC error - 0 from FIA on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-CRC_ERR_0_NPU_0 CRC error from NPU-0 on bridge3-0

Explanation    CRC error from NPU-0 on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-CRC_ERR_0_NPU_1 CRC error from NPU-0 on bridge3-1

Explanation    CRC error from NPU-0 on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-CRC_ERR_1_FIA_0 CRC error - 1 from FIA on bridge3-0

Explanation    CRC error - 1 from FIA on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-CRC_ERR_1_FIA_1 CRC error - 1 from FIA on bridge3-1

Explanation    CRC error - 1 from FIA on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-CRC_ERR_1_NPU_0 CRC error from NPU-1 on bridge3-0

Explanation    CRC error from NPU-1 on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-CRC_ERR_1_NPU_1 CRC error from NPU-1 on bridge3-1

Explanation    CRC error from NPU-1 on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-FIA2NPU_0_PKT_MAXLEN_ERR_0 FIA to NPU-0 packet maximum length error - 0

Explanation    Packet maximum length error on FIA to NPU-0 interface on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-FIA2NPU_0_PKT_MAXLEN_ERR_1 FIA to NPU-0 packet maximum length error - 1

Explanation    Packet maximum length error on FIA to NPU-0 interface on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-FIA2NPU_0_PKT_MINLEN_ERR_0 FIA to NPU-0 packet minimum length error - 0

Explanation    Packet minimum length error on FIA to NPU-0 interface on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-FIA2NPU_0_PKT_MINLEN_ERR_1 FIA to NPU-0 packet minimum length error - 1

Explanation    Packet minimum length error on FIA to NPU-0 interface on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-FIA2NPU_1_PKT_MAXLEN_ERR_0 FIA to NPU-1 packet maximum length error - 0

Explanation    Packet maximum length error on FIA to NPU-1 interface on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-FIA2NPU_1_PKT_MAXLEN_ERR_1 FIA to NPU-1 packet maximum length error - 1

Explanation    Packet maximum length error on FIA to NPU-1 interface on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-FIA2NPU_1_PKT_MINLEN_ERR_0 FIA to NPU-1 packet minimum length error - 0

Explanation    Packet minimum length error on FIA to NPU-1 interface on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-FIA2NPU_1_PKT_MINLEN_ERR_1 FIA to NPU-1 packet minimum length error - 1

Explanation    Packet minimum length error on FIA to NPU-1 interface on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-FIFO_0_OFLOW_FIA2BR_0 FIFO-0 FIA to bridge3-0 overflow

Explanation    FIFO-0 FIA to bridge3 instance-0 overflow.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-FIFO_0_OFLOW_FIA2BR_1 FIFO-0 FIA to bridge3-1 overflow

Explanation    FIFO-0 FIA to bridge3 instance-1 overflow.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-FIFO_0_OFLOW_NPU2BR_0 FIFO-0 NPU to bridge3-0 overflow

Explanation    FIFO-0 NPU to bridge3 instance-0 overflow.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-FIFO_0_OFLOW_NPU2BR_1 FIFO-0 NPU to bridge3-1 overflow

Explanation    FIFO-0 NPU to bridge3 instance-1 overflow.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-FIFO_1_OFLOW_FIA2BR_0 FIFO-1 FIA to bridge3-0 overflow

Explanation    FIFO-1 FIA to bridge3 instance-0 overflow.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-FIFO_1_OFLOW_FIA2BR_1 FIFO-1 FIA to bridge3-1 overflow

Explanation    FIFO-1 FIA to bridge3 instance-1 overflow.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-FIFO_1_OFLOW_NPU2BR_0 FIFO-1 NPU to bridge3-0 overflow

Explanation    FIFO-1 NPU to bridge3 instance-0 overflow.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-FIFO_1_OFLOW_NPU2BR_1 FIFO-1 NPU to bridge3-1 overflow

Explanation    FIFO-1 NPU to bridge3 instance-1 overflow.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-MAC_0_RX_FRAME_ERR_0 MAC on NPU-0 receive frame error - 0

Explanation    MAC on NPU-0 received an errored frame interface on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-MAC_0_TX_FIFO_OFLOW_0 MAC on NPU-0 transmit fifo overflow - 0

Explanation    MAC on NPU-0 had transmit fifo overflow on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-MAC_0_TX_FIFO_OFLOW_1 MAC on NPU-0 transmit fifo overflow - 1

Explanation    MAC on NPU-0 had transmit fifo overflow on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-MAC_1_RX_FRAME_ERR_0 MAC on NPU-1 receive frame error - 0

Explanation    MAC on NPU-1 received an errored frame interface on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-MAC_1_RX_FRAME_ERR_1 MAC on NPU-1 receive frame error - 1

Explanation    MAC on NPU-1 received an errored frame interface on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-MAC_1_TX_FIFO_OFLOW_0 MAC on NPU-1 transmit fifo overflow - 0

Explanation    MAC on NPU-1 had transmit fifo overflow on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-MAC_1_TX_FIFO_OFLOW_1 MAC on NPU-1 transmit fifo overflow - 1

Explanation    MAC on NPU-1 had transmit fifo overflow on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-MISS_EOP_0_FIADDR_0 Missing EOP-0 from FIA DDR on bridge3-0

Explanation    Missing EOP-0 from FIA DDR on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-MISS_EOP_0_FIADDR_1 Missing EOP-0 from FIA DDR on bridge3-1

Explanation    Missing EOP-0 from FIA DDR on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-MISS_EOP_0_XAUI_0 Missing EOP-0 from XAUI on bridge3-0

Explanation    Missing EOP-0 from XAUI on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-MISS_EOP_0_XAUI_1 Missing EOP-0 from XAUI on bridge3-1

Explanation    Missing EOP-0 from XAUI on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-MISS_EOP_1_FIADDR_0 Missing EOP-1 from FIA DDR on bridge3-0

Explanation    Missing EOP-1 from FIA DDR on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-MISS_EOP_1_FIADDR_1 Missing EOP-1 from FIA DDR on bridge3-1

Explanation    Missing EOP-1 from FIA DDR on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-MISS_EOP_1_XAUI_0 Missing EOP-1 from XAUI on bridge3-0

Explanation    Missing EOP-1 from XAUI on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-MISS_EOP_1_XAUI_1 Missing EOP-1 from XAUI on bridge3-1

Explanation    Missing EOP-1 from XAUI on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-NPU_0_EGR_Q_ERR_0 NPU-0 egress queue error - 0

Explanation    Egress queue error on NPU-0 interface on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-NPU_0_EGR_Q_ERR_1 NPU-0 egress queue error - 1

Explanation    Egress queue error on NPU-0 interface on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-NPU_0_FC_DIP2_ERR_0 NPU-0 egress flow control DIP2 parity error - 0

Explanation    Egress flow control DIP2 parity error on NPU-0 interface on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-NPU_0_FC_DIP2_ERR_1 NPU-0 egress flow control DIP2 parity error - 1

Explanation    Egress flow control DIP2 parity error on NPU-0 interface on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-NPU_0_FC_OOS_0 NPU-0 egress flow control out-of-sync - 0

Explanation    Egress flow control out-of-sync on NPU-0 interface on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-NPU_0_FC_OOS_1 NPU-0 egress flow control out-of-sync - 1

Explanation    Egress flow control out-of-sync on NPU-0 interface on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-NPU_0_PKT_MAXLEN_ERR_0 NPU-0 packet maximum length error - 0

Explanation    Packet maximum length error on NPU-0 interface on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-NPU_0_PKT_MAXLEN_ERR_1 NPU-0 packet maximum length error - 1

Explanation    Packet maximum length error on NPU-0 interface on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-NPU_0_PKT_MINLEN_ERR_0 NPU-0 packet minimum length error - 0

Explanation    Packet minimum length error on NPU-0 interface on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-NPU_0_PKT_MINLEN_ERR_1 NPU-0 packet minimum length error - 1

Explanation    Packet minimum length error on NPU-0 interface on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-NPU_0_SCH_MEMP_ERR_0 NPU-0 scheduler mem parity error - 0

Explanation    Scheduler Hang, Sram or egress mid-fifo parity error on NPU-0 interface on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-NPU_0_SCH_MEMP_ERR_1 NPU-0 scheduler mem parity error - 1

Explanation    Scheduler Hang, Sram or egress mid-fifo parity error on NPU-0 interface on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-NPU_1_EGR_Q_ERR_0 NPU-1 egress queue error - 0

Explanation    Egress queue error on NPU-1 interface on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-NPU_1_EGR_Q_ERR_1 NPU-1 egress queue error - 1

Explanation    Egress queue error on NPU-1 interface on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-NPU_1_FC_DIP2_ERR_0 NPU-1 egress flow control DIP2 parity error - 0

Explanation    Egress flow control DIP2 parity error on NPU-1 interface on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-NPU_1_FC_DIP2_ERR_1 NPU-1 egress flow control DIP2 parity error - 1

Explanation    Egress flow control DIP2 parity error on NPU-1 interface on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-NPU_1_FC_OOS_0 NPU-1 egress flow control out-of-sync - 0

Explanation    Egress flow control out-of-sync on NPU-1 interface on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-NPU_1_FC_OOS_1 NPU-1 egress flow control out-of-sync - 1

Explanation    Egress flow control out-of-sync on NPU-1 interface on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-NPU_1_PKT_MAXLEN_ERR_0 NPU-1 packet maximum length error - 0

Explanation    Packet maximum length error on NPU-1 interface on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-NPU_1_PKT_MAXLEN_ERR_1 NPU-1 packet maximum length error - 1

Explanation    Packet maximum length error on NPU-1 interface on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-NPU_1_PKT_MINLEN_ERR_0 NPU-1 packet minimum length error - 0

Explanation    Packet minimum length error on NPU-1 interface on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-NPU_1_PKT_MINLEN_ERR_1 NPU-1 packet minimum length error - 1

Explanation    Packet minimum length error on NPU-1 interface on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-NPU_1_SCH_MEMP_ERR_0 NPU-1 scheduler mem parity error - 0

Explanation    Scheduler Hang, Sram or egress mid-fifo parity error on NPU-1 interface on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-NPU_1_SCH_MEMP_ERR_1 NPU-1 scheduler mem parity error - 1

Explanation    Scheduler Hang, Sram or egress mid-fifo parity error on NPU-1 interface on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-PKT_LEN_ERR_0_FIA_0 Packet length error - 0 from FIA on bridge3-0

Explanation    Packet length error - 0 from FIA on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-PKT_LEN_ERR_0_FIA_1 Packet length error - 0 from FIA on bridge3-1

Explanation    Packet length error - 0 from FIA on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-PKT_LEN_ERR_0_XAUI_0 Packet length error - 0 from XAUI on bridge3-0

Explanation    Packet length error - 0 from XAUI on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-PKT_LEN_ERR_0_XAUI_1 Packet length error - 0 from XAUI on bridge3-1

Explanation    Packet length error - 0 from XAUI on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-PKT_LEN_ERR_1_FIA_0 Packet length error - 1 from FIA on bridge3-0

Explanation    Packet length error - 1 from FIA on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-PKT_LEN_ERR_1_FIA_1 Packet length error - 1 from FIA on bridge3-1

Explanation    Packet length error - 1 from FIA on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-PKT_LEN_ERR_1_XAUI_0 Packet length error - 1 from XAUI on bridge3-0

Explanation    Packet length error - 1 from XAUI on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-PKT_LEN_ERR_1_XAUI_1 Packet length error - 1 from XAUI on bridge3-1

Explanation    Packet length error - 1 from XAUI on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-QDR_MEM_ECC_FAIL_0 QDR memory ECC failure on bridge3-0

Explanation    QDR memory ECC failure on bridge3 instance-0.

Recommended Action    Please reload the board using the command 'reload location '. Please verify the bridge3 FPGA is loaded properly. 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-BRIDGE3-3-QDR_MEM_ECC_FAIL_1 QDR memory ECC failure on bridge3-1

Explanation    QDR memory ECC failure on bridge3 instance-1.

Recommended Action    Please reload the board using the command 'reload location '. Please verify the bridge3 FPGA is loaded properly. 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-BRIDGE3-3-STATEMC_0_ERR1_0 State machine-0 error-1 on bridge3-0

Explanation    State machine - 0 ran into error-1 on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-STATEMC_0_ERR1_1 State machine-0 error-1 on bridge3-1

Explanation    State machine - 0 ran into error-1 on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-STATEMC_0_ERR2_0 State machine-0 error-2 on bridge3-0

Explanation    State machine - 0 ran into error-2 on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-STATEMC_0_ERR2_1 State machine-0 error-2 on bridge3-1

Explanation    State machine - 0 ran into error-2 on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-STATEMC_0_ERR3_0 State machine-0 error-3 on bridge3-0

Explanation    State machine - 0 ran into error-3 on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-STATEMC_0_ERR3_1 State machine-0 error-3 on bridge3-1

Explanation    State machine - 0 ran into error-3 on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-STATEMC_1_ERR1_0 State machine-1 error-1 on bridge3-0

Explanation    State machine - 1 ran into error-1 on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-STATEMC_1_ERR1_1 State machine-1 error-1 on bridge3-1

Explanation    State machine - 1 ran into error-1 on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-STATEMC_1_ERR2_0 State machine-1 error-2 on bridge3-0

Explanation    State machine - 1 ran into error-2 on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-STATEMC_1_ERR2_1 State machine-1 error-2 on bridge3-1

Explanation    State machine - 1 ran into error-2 on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-STATEMC_1_ERR3_0 State machine-1 error-3 on bridge3-0

Explanation    State machine - 1 ran into error-3 on bridge3 instance-0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-STATEMC_1_ERR3_1 State machine-1 error-3 on bridge3-1

Explanation    State machine - 1 ran into error-3 on bridge3 instance-1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-XAUI_0_FRAG_ERR_0 XAUI to NPU-0 fragment error - 0

Explanation    XAUI interface to NPU-0 reported fragmentation error on TX side on bridge3 instance - 0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-XAUI_0_FRAG_ERR_1 XAUI to NPU-0 fragment error - 1

Explanation    XAUI interface to NPU-0 reported fragmentation error on TX side on bridge3 instance - 1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-XAUI_0_TX_FIFO_OFLOW_0 XAUI to NPU-0 tx fifo overflow - 0

Explanation    XAUI interface to NPU-0 reported tx fifo overflow on bridge3 instance - 0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-XAUI_0_TX_FIFO_OFLOW_1 XAUI to NPU-0 tx fifo overflow - 1

Explanation    XAUI interface to NPU-0 reported tx fifo overflow on bridge3 instance - 1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-XAUI_1_FRAG_ERR_0 XAUI to NPU-1 fragment error - 0

Explanation    XAUI interface to NPU-1 reported fragmentation error on TX side on bridge3 instance - 0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-XAUI_1_FRAG_ERR_1 XAUI to NPU-1 fragment error - 1

Explanation    XAUI interface to NPU-1 reported fragmentation error on TX side on bridge3 instance - 1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-XAUI_1_TX_FIFO_OFLOW_0 XAUI to NPU-1 tx fifo overflow - 0

Explanation    XAUI interface to NPU-1 reported tx fifo overflow on bridge3 instance - 0.

Recommended Action    If the error persists, please reload the board using the command 'reload 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-BRIDGE3-3-XAUI_1_TX_FIFO_OFLOW_1 XAUI to NPU-1 tx fifo overflow - 1

Explanation    XAUI interface to NPU-1 reported tx fifo overflow on bridge3 instance - 1.

Recommended Action    If the error persists, please reload the board using the command 'reload 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.

CANB_SERVER Messages

Error Message     
 
    
    
   

%PLATFORM-CANB_SERVER-3-ALARM_CLEARED Clear alarm from CBC in slot [dec], alarm code [chars]

Explanation    Alarm notification received from CBC. This may be a serious failure, however process may continue functioning as expected (or successfully retry) despite the failure.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-CANB_SERVER-3-ALARM_INDICATION Raise alarm from CBC in slot [dec], alarm code [chars]

Explanation    Alarm notification received from CBC. This may be a serious failure, however process may continue functioning as expected (or successfully retry) despite the failure.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-CANB_SERVER-3-ERROR_EXIT Canbus-server process exiting in [chars].[dec], error code [chars]

Explanation    The CAN Bus Server/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 canb-server location ' to verify that the process is up and running. If it is still non-operational, try doing from the admin mode 'process restart canb-server 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-CANB_SERVER-3-OPERATION_FAIL Failed in [chars].[dec], error code [chars]

Explanation    The particular operation mentioned in the message failed due to some reason. This may be a serious failure, however process may continue functioning as expected (or successfully retry) despite the failure.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-CANB_SERVER-6-OPERATION_INFO [chars].[dec], Info - [chars]

Explanation    Informational condition and/or failure. The process can continue functioning as expected despite the failure.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-CANB_SERVER-7-OPERATION_DEBUG Failed in [chars].[dec], [dec], [dec], error code [chars]

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

Recommended Action    Debug message only. No action is required.

CARD Messages

Error Message     
 
    
    
   

%PLATFORM-CARD-0-OVERCURRENT ClkCtrl detected an overcurrent condition on card [chars]

Explanation    ClkCtrl driver detected a card overcurrent 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.

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

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-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-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-ERROR_EXIT Envmon process exiting because [chars], error code [chars]

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

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

Error Message     
 
    
    
   

%PLATFORM-CCTL-3-MASTERSHIP_EXIT Exiting because not able to [chars] mastership

Explanation    The Chassis Control driver process exited as it was not able to grab mastership or unable to release it.

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-CCTL-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-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-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.

Error Message     
 
    
    
   

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

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

Recommended Action    Debug message only. No action is required.

CEMGBL Messages

Error Message     
 
    
    
   

%PLATFORM-CEMGBL-7-ERROR [chars] : [chars]

Explanation    An unexpected error condition encountered.

Recommended Action    Collect system log information. No action is required.

CETHHA Messages

Error Message     
 
    
    
   

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

Explanation    Hardware error on CPU control ethernet port.

Recommended Action    Remove/Replace the RP.

Error Message     
 
    
    
   

%PLATFORM-CETHHA-2-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.

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 equals [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 equals [chars], errno equals [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,[chars]

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 equals [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 equals [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 [dec] 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 [chars] 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.

CLKCTRL_T Messages

Error Message     
 
    
    
   

%PLATFORM-CLKCTRL_T-2-DEV_VERSION_ERROR Timing driver version is not compatible with the hardware FPGA version. S/W ver: [dec]:[dec] H/W ver: [dec]:[dec]

Explanation    Timing driver software version is not compatible with the hardware FPGA version.

Recommended Action    Upgrade the ClkCtrl Timing FPGA image using the FPD procedure. 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-CLKCTRL_T-2-EEPROM_OVERCURRENT ClkCtrl detected an EEPROM overcurrent condition

Explanation    ClkCtrl detected an EEPROM overcurrent condition

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

Error Message     
 
    
    
   

%PLATFORM-CLKCTRL_T-2-PARITY_ERROR Timing software detected a parity error address equals [dec] data equals [dec]

Explanation    Timing software detected a parity error from interrupt controller

Recommended Action    If a redundant RSP card has been configured: 1 - force a failover with the following command in admin mode: 'redundancy switchover'. 2 - reload the RSP card that failed with the 'reload location' command in admin mode. If no redundant RSP is configured, you will need to reboot the router by issuing the above reload command. 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.

COMMON Messages

Error Message     
 
    
    
   

%PLATFORM-COMMON-0-LC_HEADLESS_ACT_RSP_HB_REQ_FAILURE Headless RSP Detected: No HB requests from the active RSP.

Explanation    This LC has timed out waiting for Heartbeat requests from the active RSP.

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

Error Message     
 
    
    
   

%PLATFORM-COMMON-0-RSP_HEADLESS_ACT_RSP_HB_REQ_FAILURE Headless RSP Detected: No HB requests from the active RSP.

Explanation    This RSP has timed out waiting for Heartbeat requests from the active RSP.

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

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

Error Message     
 
    
    
   

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

Explanation    CPUCTRL PCI, event logging.

Recommended Action    No action is required.

CPUCTRL Messages

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-ASIC_NOT_FOUND Cpuctrl could not find [chars]

Explanation    While booting up, CPUCTRL could not find the required ASICs.

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

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-ASIC_RESET_FAILURE Cpuctrl could not reset board ASICs. [chars] Error.

Explanation    While trying to bring up ASIC links, Cpuctrl manager could not reset MSC and PLIM board ASICs port.

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-CDMA_RAM_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_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-CDMA_RAM_UNCORRECTABLE_ERROR Cpuctrl HW detected MBE in [chars] RAM. Key: [hex]
[chars]

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

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

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-DETECTED_TX_PDMA_STALL TX PDMA Ring Stalled, port equals [dec], queue equals [dec], cur_ind equals [dec], tx_ind equals [dec].

Explanation    CPUCTRL TX PDMA ring remained full over non-transient period. Packets which could not be sent were discarded. The downstream ASIC may be stalled. Asic error logged with queue details.

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-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-FAULT_REPORT_FAILURE Cannot report fault ([chars]) to PM fault manager

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

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

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-HW_DETECTED_ERROR_ISN [chars]

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

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

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-HW_DETECTED_ERROR_ISN HW error interrupt Cpuctrl Internal Access failure
interrupt_id equals [hex], pci_isnerr_status equals [hex]
pci_isnerr_addr_hi equals [hex], pci_isnerr_addr_lo equals [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 equals [dec]
interrupt_id equals [hex], port_link_error equals [hex], port_link_crc_count equals [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_LINK [chars]

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

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

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-HW_DETECTED_ERROR_PCI_PM [chars]

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

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

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-HW_DETECTED_ERROR_PCI_PM HW error interrupt pci pm, port equals [dec]
interrupt_id equals [hex], pci_pmerr_status equals [hex]
pci_pmerr_addr_hi equals [hex], pci_pmerr_addr_lo equals [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 [chars]

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

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

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-HW_DETECTED_ERROR_PCI_SN HW error interrupt pci sn, port equals [dec]
interrupt_id equals [hex], pci_snerr_status equals [hex]
pci_snerr_addr_hi equals [hex], pci_snerr_addr_lo equals [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 [chars]

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

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

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-HW_DETECTED_ERROR_PCIX HW error interrupt pcix, port equals [dec]
interrupt_id equals [hex], pcix_pmerr_comptran_status equals [hex], pcix_pmerr_status equals [hex]
pcix_pmerr_addr_hi equals [hex], pcix_pmerr_addr_lo equals [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 [chars]

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

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

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-HW_DETECTED_ERROR_PORT HW error interrupt port, port equals [dec]
interrupt_id equals [hex], port_isn_cause equals [hex], port_isn_error equals [hex]
port_isn_last_reqhi equals [hex], port_isn_last_reqlo equals [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 equals [hex]

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-PCI_RAM_CORRECTABLE_ERROR_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_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-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_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_PARITY_ERROR Cpuctrl HW detected parity in [chars] RAM. Key: [hex]
[chars]

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-PERSISTENT_CRC_LINK_FAILURE Cpuctrl port [dec] link is unframeable with persistent CRC errors.

Explanation    Cpuctrl manager could not bring up the ASIC link on the specified port. This indicates a hardware failure on the MSC or PLIM board.

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-7-ERR_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_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_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_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_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-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 equals [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_CDMA_PORT0 CDMA to port 0 channel equals [dec], queue equals [dec]. ASIC address [[hex],[hex]]

Explanation    The cpuctrl driver detected an attempt to DMA to port 0. The request was discarded and not performed.

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

Error Message     
 
    
    
   

%PLATFORM-CPUCTRLLIB-3-DETECTED_EGRESSQ_QUEUE0_PDMA TX PDMA to EgressQ queue 0, port equals [dec], queue equals [dec]. Buffer Header: [hex]. Initial packet data(hex): [chars]

Explanation    The cpuctrl driver detected an attempt to DMA a packet to egressq queue 0. The packet was discarded and not sent.

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

Error Message     
 
    
    
   

%PLATFORM-CPUCTRLLIB-3-DETECTED_ERROR_PDMA [chars], [dec], port equals [dec], queue equals [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-DETECTED_ERROR_PDMA [chars], [dec], port equals [dec], queue equals [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 equals [dec], queue equals [dec], index equals [dec]
error reg_lo equals [hex], error_reg_hi equals [hex]

Explanation    CDMA ended in error.

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

Error Message     
 
    
    
   

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

Explanation    CDMA ended in error.

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-CPUCTRLLIB-3-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-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-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 equals [hex], crc_reg equals [hex]

Explanation    Port will not operate reliably

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

Error Message     
 
    
    
   

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

Explanation    Port will not operate reliably

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

Error Message     
 
    
    
   

%PLATFORM-CPUCTRLLIB-4-PORT_NOT_PRESENT Attempt to access Port [dec] which was not discovered
Device ID_reg equals [hex], devid equals [hex]

Explanation    Port will not operate reliably

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

Error Message     
 
    
    
   

%PLATFORM-CPUCTRLLIB-4-PORT_REFRAME_SYNC_FAILURE Port [dec] 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_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 equals [hex], id_reg during HW discovery equals [hex]

Explanation    Port will not operate reliably

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

Error Message     
 
    
    
   

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

Explanation    Port will not operate reliably

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

CROSSBAR Messages

Error Message     
 
    
    
   

%PLATFORM-CROSSBAR-2-SERDES_ERROR Crossbar driver serdes error

Explanation    Crossbar driver detected a serdes error.

Recommended Action    This error is a momentary error. If this error persists for a period of 60 seconds after all the cards are in IOS-XR RUN state using the 'show platform' command, please attempt to correct the error by reloading the card by issuing the command: 'hw-module loc 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-CROSSBAR-3-IN_MEM_ERROR Crossbar driver input memory error

Explanation    Crossbar driver detected a input memory 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-CROSSBAR-3-OUT_MEM_ERROR Crossbar driver output memory error

Explanation    Crossbar driver detected an output memory 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-CROSSBAR-3-XBAR_TIMEOUT_ERROR Crossbar driver detects crossbar timeout error

Explanation    Crossbar driver detected an crossbar timeout 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.

DIAGS Messages

Error Message     
 
    
    
   

%PLATFORM-DIAGS-3-BOOTFLASH_CORRUPTED BOOTFLASH integrity check failed,

Explanation    Some FPD image in bootflash is corrupted or missing. Each FPD has 2 images stored in bootfalsh, 1 is field upgradable version, that is the 'B' version; the other is the backup version, which is the 'A' version. If a B version FPD image has gone bad, it can be recovered by following the recommended_action. If one A version has gone bad, have the board replaced.

Recommended Action    Use the following command to find out which FPD image is bad/missing: 'show log | inc PFM | inc FLASH'; If it is the B version (the upgradable version), then reprogram the image using the upgrade command: 'admin' 'upgrade hw fpd fpga-selection force location node-failed' If any A version is bad, Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-DIAGS-3-EXCESSIVE_ECC_SBE_ERROR Excessive ECC Single-bit errors

Explanation    The number of single-bit ECC errors has crossed the error threshold.

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

Error Message     
 
    
    
   

%PLATFORM-DIAGS-3-FAB_MCAST_SC0_FAILED Fabric multicast loopback (SC0) failure count crossed threshold.

Explanation    A problem is detected by loopback test to the first Crossbar chip (chip#0) on this RSP.

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

Error Message     
 
    
    
   

%PLATFORM-DIAGS-3-FAB_MCAST_SC1_FAILED Fabric multicast loopback (SC1) failure count crossed threshold.

Explanation    A problem is detected by loopback test to the second Crossbar chip (chip#1) on this RSP.

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

Error Message     
 
    
    
   

%PLATFORM-DIAGS-3-FAB_UNICAST_FAILED Fabric unicast loopback failure count crossed threshold.

Explanation    A problem is detected by loopback test to the Crossbar chips on this RSP.

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

Error Message     
 
    
    
   

%PLATFORM-DIAGS-3-INVALID_DEVICE_ID Device identity readback value is incorrect

Explanation    Device identity readback value 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-DIAGS-3-LC_EOBC_FAILED_BOTH_RSP LC lost EOBC heartbeat to both RSPs.

Explanation    This line card has lost EOBC heartbeat to both RSPs

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

Error Message     
 
    
    
   

%PLATFORM-DIAGS-3-LC_EOBC_FAILED_RSP0 EOBC Heartbeat failure count for RSP0 crossed threshold.

Explanation    This line card has lost EOBC heartbeat to RSP0.

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

Error Message     
 
    
    
   

%PLATFORM-DIAGS-3-LC_EOBC_FAILED_RSP1 EOBC Heartbeat failure count for RSP1 crossed threshold.

Explanation    This line card has lost EOBC heartbeat to RSP1.

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

Error Message     
 
    
    
   

%PLATFORM-DIAGS-3-LC_EOBC_FAILED_STBY_RSP LC lost EOBC heartbeat to the Standby RSP.

Explanation    This line card has lost EOBC heartbeat to the standby RSP.

Recommended Action    If this happens during system booting and switchover or when the standby RSP is not in 'IOS XR RUN' state, this message can be safely ignored. Otherwise, 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-DIAGS-3-LC_EOBC_NO_RSP_UP No RSP is up, LC EOBC heartbeat skipped. [chars]

Explanation    This line card found there is no RSP present in the system.

Recommended Action    This condition should not last long, the line card should reset. No action is required.

Error Message     
 
    
    
   

%PLATFORM-DIAGS-3-LC_EOBC_SEND_FAILED Failed to send a heartbeat to RSP [chars]

Explanation    This line card has failed to transmit a heartbeat to a RSP over EOBC.

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

Error Message     
 
    
    
   

%PLATFORM-DIAGS-3-LC_NP_LOOPBACK_FAILED NP loopback failure count crossed threshold, [chars]

Explanation    This line card has detected a problem with the packet punt and injection path between this line card CPU and some network processor(s), and the consecutive failure count has reached or crossed the failure threshold.

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

Error Message     
 
    
    
   

%PLATFORM-DIAGS-3-PUNT_FABRIC_DATA_PATH_FAILED System punt, fabric and data path failure count crossed threshold, [chars]

Explanation    A problem is detected on the system punt, fabric or data path between this RSP CPU to one or more of the network processor(s) on some line card(s).

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

Error Message     
 
    
    
   

%PLATFORM-DIAGS-3-SCRATCH_TEST_ERROR Device scratch register test has failed

Explanation    The CPU at the failed location has failed to access the named device scratch register.

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

Error Message     
 
    
    
   

%PLATFORM-DIAGS-3-SRSP_ACTIVE_EOBC_FAILED Heartbeat failed over active EOBC, [chars]

Explanation    Standby RSP has detected an error with the active eobc link between this standby RSP and one or more line card)(s)

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

Error Message     
 
    
    
   

%PLATFORM-DIAGS-3-SRSP_ACTIVE_EOBC_MCAST_FAILED Failed to broadcast heartbeat over active EOBC.

Explanation    Standby RSP failed to transmit heartbeat to all nodes via active EOBC links.

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

Error Message     
 
    
    
   

%PLATFORM-DIAGS-3-SRSP_STANDBY_EOBC_FAILED Heartbeat failed over Standby EOBC, [chars]

Explanation    Standby RSP has detected an error with the standby eobc link between this standby RSP and one or more line card)(s)

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

Error Message     
 
    
    
   

%PLATFORM-DIAGS-3-SRSP_STANDBY_EOBC_MCAST_FAILED Failed to broadcast heartbeat over standby EOBC.

Explanation    Standby RSP failed to transmit heartbeat to all nodes via standby EOBC links.

Recommended Action    Copy the error message exactly as 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-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-ERR_KD_MMAP Failed to mmap to Kernel dumper information in syspage, error: [chars].

Explanation    Failed to mmap to Kernel dumper information in syspages.

Recommended Action    This is a critical error which will cause process to restart for error recovery. Collect the syslog or console log. 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-ERR_SET_REBOOT_CAUSE Failed to set reboot cause into syspage, error: [chars].

Explanation    The failure on setting reboot cause to syspage before performing Kernel Dump.

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-3-RAM_ECC_2BIT ASIC-ERR: RAM error #[dec]: Name equals [chars] #[dec]: Description equals [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-3-RAM_ECC_2BIT ASIC-ERR: RAM error #[dec]: Name equals [chars] #[dec]: Description equals [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 equals [chars] #[dec]: Description equals [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_LATCH ASIC-ERR: CPU error #[dec]: Name equals [chars] #[dec]: Description equals [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 equals [chars] #[dec]: Description equals [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-CPU_NOLATCH ASIC-ERR: CPU error #[dec]: Name equals [chars] #[dec]: Description equals [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 equals [chars] #[dec]: Description equals [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_LATCH ASIC-ERR: DEV error #[dec]: Name equals [chars] #[dec]: Description equals [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 equals [chars] #[dec]: Description equals [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-DEV_NOLATCH ASIC-ERR: DEV error #[dec]: Name equals [chars] #[dec]: Description equals [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 equals [chars] #[dec]: Description equals [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_LATCH ASIC-ERR: PCI[dec] error #[dec]: Name equals [chars] #[dec]: Description equals [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 equals [chars] #[dec]: Description equals [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-PCI_NOLATCH ASIC-ERR: PCI[dec] error #[dec]: Name equals [chars] #[dec]: Description equals [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 equals [chars] #[dec]: Description equals [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-RAM_ECC_1BIT_THRESH ASIC-ERR: RAM error #[dec]: Name equals [chars] #[dec]: Description equals [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 equals [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-4-SRAM_PARITY ASIC-ERR: SRAM error #[dec]: Description equals [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_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-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-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-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-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-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-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.

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

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.

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-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-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-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-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-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-7-ERR_CERR_REG Failed to register with CERR Handler. [chars]

Explanation    --

Recommended Action    '*NONE*'

Error Message     
 
    
    
   

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

Explanation    --

Recommended Action    '*NONE*'

Error Message     
 
    
    
   

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

Explanation    --

Recommended Action    '*NONE*'

Error Message     
 
    
    
   

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

Explanation    --

Recommended Action    '*NONE*'

Error Message     
 
    
    
   

%PLATFORM-DRP_PAIRING-7-ERR_PROC_BLOCK [chars]

Explanation    --

Recommended Action    '*NONE*'

Error Message     
 
    
    
   

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

Explanation    --

Recommended Action    '*NONE*'

Error Message     
 
    
    
   

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

Explanation    --

Recommended Action    '*NONE*'

Error Message     
 
    
    
   

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

Explanation    --

Recommended Action    '*NONE*'

DSC Messages

Error Message     
 
    
    
   

%PLATFORM-DSC-1-ERR_LOST_ALL_FABRIC_RACKS Lost Connection to all Fabric Racks

Explanation    This node has lost connectivity with all fabric racks before the fabric planes came up. This could be a control ethernet problem or the fabrics have reloaded.

Recommended Action    Check if fabric chassis are up. If up, check control-ethernet connectivity between this chassis and Fabric chassis. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

Explanation    Priority given for the node is not applicable.

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-DSC-3-ERR_LTRACE_INIT Could not initialize [chars] trace buffer, error [hex] ([chars])

Explanation    ltrace initialization failed

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-DSC-3-ERR_TRANSPORT Primary transport connection not ok to node [hex], alternate transport connectivity ok

Explanation    CRS: This indicates that there is a problem with control ethernet cables or switches to that node. C12k: This indicates that there is a problem with MBUS communication to that node.

Recommended Action    CRS: Check the control ethernet connectivity to the node. (Check if the cables are okay and also if the switch is operating normally). C12K: If the error persists for a long time, please check the MBUS communication to the node. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-DSC-4-WARNING_RACK_NUM ROMMON RACK_NUM ( equals [dec]) set inconsistent.

Explanation    ROMMON RACK_NUM variable setting is different from the node_id rack field setting.

Recommended Action    Set ROMMON RACK_NUM to proper rack number per chassis rack field

Error Message     
 
    
    
   

%PLATFORM-DSC-5-NOTICE_RACK_NUM ROMMON RACK_NUM set to 0.

Explanation    ROMMON RACK_NUM variable set to 0.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-DSC-6-ERR_I_AM_DSC Setting myself as DSC

Explanation    Informational message notifying current DSC in system

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Not able to save configuration for this rack.

Recommended Action    Examine chassis based on above error msg.

Error Message     
 
    
    
   

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

Explanation    No response received from configuration manager server.

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Chassis APIs that write to non volatile memory failed.

Recommended Action    No action is required.

DSCMEDIA Messages

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

Explanation    The dsc media dll encountered aa fatal error.

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

Error Message     
 
    
    
   

%PLATFORM-DSCMEDIA-3-ERR_CCTL [chars]; rc equals [chars]

Explanation    DSC could not read back plane EEPROM. This might affect the booting up of the standby. If the standby does not boot then the work around is to set the rack number to backplane eeprom association using the following cli. (admin-config)#dsc serial serial-id rack rack-num

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-DSCMEDIA-3-ERR_CCTL [chars]; rc equals [chars]

Explanation    DSC could not read back plane EEPROM. This might affect the booting up of the standby. If the standby does not boot then the work around is to set the rack number to backplane eeprom association using the following cli. (admin-config)#dsc serial serial-id rack rack-num

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-DSCMEDIA-3-ERR_EVM [chars] ; rc equals [chars]

Explanation    DSC Media DLL has encounered the annunciated Event Manager error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.

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-DSCMEDIA-3-ERR_EVM [chars] ; rc equals [chars]

Explanation    DSC Media DLL has encounered the annunciated Event Manager error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.

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-DSCMEDIA-3-ERR_NODEID [chars]; rc equals [chars]

Explanation    DSC Media DLL failed to get the nodeid. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.

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-DSCMEDIA-3-ERR_NODEID [chars]; rc equals [chars]

Explanation    DSC Media DLL failed to get the nodeid. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.

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-DSCMEDIA-3-ERR_TRANSPORT [chars]

Explanation    DSC Media DLL has encounered the annunciated transport error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.

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-DSCMEDIA-3-ERR_TRANSPORT [chars]

Explanation    DSC Media DLL has encounered the annunciated transport error. The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times the error is encountered, to recover. If the problem continues, sysmgr will trigger node reload. After a certain number of node reloads, the shelf manager will permanently shutdown the node.

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-DSCMEDIA-3-ERROR Error from dsc media dll: [chars]

Explanation    The dsc media dll encountered an internal software error.

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

Error Message     
 
    
    
   

%PLATFORM-DSCMEDIA-3-ERROR2 Error from dsc media dll: [chars], errno equals [dec] ([chars])

Explanation    The dsc media dll encountered an internal software error.

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

Error Message     
 
    
    
   

%PLATFORM-DSCMEDIA-3-READ_PERSIST Unable to [chars] when parsing persistent file [chars]: [chars] ([chars])

Explanation    The dsc process attempted to read dcs election information from non-volatile storage, but encountered a problem. This may cause the wrong RP card to get elected as DSC.

Recommended Action    Verify nvram: filesystem integrity. If this is a persistent problem then: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-DSCMEDIA-3-WRITE_PERSIST Unable to [chars] when writing persistent file [chars]: [chars] ([chars])

Explanation    The dsc process attempted to store dcs election information to non-volatile storage, but encountered a problem. This may cause the wrong RP card to get elected as DSC on the next chassis cold boot.

Recommended Action    Make sure there is free space in local NVRAM. If this is a persistent problem then: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-DSCMEDIA-4-ERR_THREAD_MUTEX_LOCK [chars] ; rc equals [chars]

Explanation    DSC media DLL encountered an error while locking a mutex. The operation related to the resource may be affected while the system continues to run 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-DSCMEDIA-4-ERR_THREAD_MUTEX_LOCK [chars] ; rc equals [chars]

Explanation    DSC media DLL encountered an error while locking a mutex. The operation related to the resource may be affected while the system continues to run 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-DSCMEDIA-4-ERR_THREAD_MUTEX_UNLOCK [chars]; rc equals [chars]

Explanation    DSC media DLL encountered an error while un-locking a mutex. The operation related to the resource may be affected while the system continues to run 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-DSCMEDIA-4-ERR_THREAD_MUTEX_UNLOCK [chars]; rc equals [chars]

Explanation    DSC media DLL encountered an error while un-locking a mutex. The operation related to the resource may be affected while the system continues to run 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-DSCMEDIA-4-FETCH Unable to [chars] [chars] when fetching initial copy from DSC: [chars] ([chars])

Explanation    The process is unable to get an initial copy of the dsc info file from the dsc card. This may cause the wrong RP card to get elected as DSC on the next chassis cold boot.

Recommended Action    Restarting the dsc process (proc restart dsc) will cause it to retry the operation and normally recover from this condition. If the issue persists: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-DSCMEDIA-4-LISTEN Unable to listen for multicast messages: [chars] ([chars])

Explanation    The process is unable to register to receive multicast messages. This means that the card will not be able to update local non-volatile data with the latest dsc election information coming from remote nodes. This may cause the wrong RP card to get elected as DSC on the next chassis cold boot.

Recommended Action    Restarting the dsc process will cause it to re-register to receive dsc persisted updates. If the issue persists: Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-DSCMEDIA-4-NO_CSC_SN Could not read Serial Numbers of the Fabric Cards slot 16 & 17; errno equals [dec] ([chars])

Explanation    Serial Numbers of the Fabric Cards (slots 16 and 17) are used to help determine chassis nativity for the Logical Routers feature. Chassis nativity is part of the algorithm to ensure that on a cold boot, the right RP is elected as the DSC and provides Logical Router boundaries to other RP cards. The lack of CSC serial numbers may cause the wrong RP to be elected DSC when RP cards are shuffled from one chassis to another and a cold boot is performed.

Recommended Action    Ensure that Fabric CSC cards are properly inserted in the chassis.

Error Message     
 
    
    
   

%PLATFORM-DSCMEDIA-4-WARNING Warning from dsc media dll: [chars]

Explanation    The dsc media dll encountered an internal software warning.

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

Error Message     
 
    
    
   

%PLATFORM-DSCMEDIA-4-WARNING2 Warning from dsc media dll: [chars], errno equals [dec] ([chars])

Explanation    The dsc media dll encountered an internal software warning.

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

Error Message     
 
    
    
   

%PLATFORM-DSCMEDIA-6-DSC_ELECTED This node is now [chars]

Explanation    A new dSC has been elected.

Recommended Action    No action is required.

EIO Messages

Error Message     
 
    
    
   

%PLATFORM-EIO-4-ERR_LWM_SEND EIO library failed to send message; rc equals [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_ECM [chars]; rc equals [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_ECM [chars]; rc equals [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 equals [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_EDM_INIT [chars]; rc equals [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 driver-name 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_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 driver-name 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 equals [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_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 equals [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_GET [chars]; rc equals [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 equals [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.

Error Message     
 
    
    
   

%PLATFORM-EIO-7-ERR_REGISTER_SET [chars]; rc equals [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.

Error Message     
 
    
    
   

%PLATFORM-ENVMON_MON-4-TEMPERATURE_READ_FAIL Envmon process has been [chars] to read temperature from various nodes

Explanation    Two possibilities to this message 1) The envmon_mon process has been unable 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. Setting fan speed to maximum to prevent chassis from heating up. 2) 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. Setting fan speed as per 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.. No action is required if the envmon process is able to read telperature.

ENVMON Messages

Error Message     
 
    
    
   

%PLATFORM-ENVMON-0-CARD_OVERTEMP_SHUTDOWN Slot [chars] temperature [dec].[dec]C at or above STT [dec].[dec]C

Explanation    Card temperature has risen over shutdown threshold. Card shutdown commencing.

Recommended Action    Verify the failure, use show env to help. If the failure does not alleviate, call your technical support representative for repair or replacement.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-0-CHASSIS_OVERTEMP_SHUTDOWN Chassis ambient temperature [dec].[dec]C at or over shutdown T3 threshold [dec].[dec]C

Explanation    Chassis ambient temperature has risen at or over T3 threshold. Entire chassis shutdown commencing.

Recommended Action    Call your technical support representative.

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-CARD_OVERTEMP Slot [chars] temperature [dec].[dec]C at or above rising T2 threshold [dec].[dec]C

Explanation    Card temperature has risen at or over critical threshold.

Recommended Action    Verify the failure, use show env to help. If the failure does not alleviate, call your technical support representative for repair or replacement.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-CARD_OVERTEMP_CLEAR Slot [chars] temperature [dec].[dec]C returned below falling T1 threshold [dec].[dec]C

Explanation    Card temperature has returned to operating range.

Recommended Action    None required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-CHASSIS_OVERTEMP Chassis ambient temperature [dec].[dec]C at or above rising T2 threshold [dec].[dec]C

Explanation    Chassis ambient temperature is over critical threshold. Ambient temperature is the average of the temperature inlet sensor for all plugged in cards in the chassis.

Recommended Action    Verify the failure, use show env to help. Verify the fans have increased to help bring down the temperature. Entire chassis will shutdown at or above T3 threshold. If the failure does not alleviate, call your technical support representative for assistance.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-CHASSIS_OVERTEMP_CLEAR Chassis ambient temperature [dec].[dec]C returned below falling T1 threshold [dec].[dec]C

Explanation    Chassis ambient temperature has returned to operating range. Ambient temperature is the average of the temperature inlet sensor for all plugged in cards in the chassis.

Recommended Action    None required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-ENV_CONDITION Outstanding environmental condition [chars] in the chassis

Explanation    One or more environmental conditions exits in the chassis. If left unattended, they can result in loss of service or physical equipment damage.

Recommended Action    Use 'show environment' command and other system messages to determine the nature of the failure and take corrective action.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-FAN_CLEAR Fan failure cleared on slot [chars], fan [dec], RPM [dec]

Explanation    The indicated fan has measured RPM returning to operating level.

Recommended Action    None required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-FAN_FAIL Fan failure on slot [chars], fan [dec], RPM [dec]

Explanation    The indicated fan has measured RPM below operating level.

Recommended Action    Verify the failure, use show env to help. If the failure does not alleviate, call your technical support representative for repair or replacement.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-FANTRAY_CLEAR Fantray failure cleared on slot [chars]

Explanation    All fans on indicated fantray returned RPMs to operating level.

Recommended Action    None required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-FANTRAY_FAIL Fantray failure on slot [chars]

Explanation    One or more fans on indicated fantray measured RPM below operating level. Remaining fans in operation on this fantray running at full speed.

Recommended Action    Verify the failure, use show env to help. If the failure does not alleviate, call your technical support representative for repair or replacement.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-POWER_BUDGET_OK Power consumption is back within [chars] supply mode limits

Explanation    The power calculated in use by the chassis has returned to a value that is within the power supplied by the powershelf.

Recommended Action    None required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-REDUNDANT_POWER_OVERBUDGET Power consumption has exceeded redundant supply mode limit by [dec]W; power redundancy lost

Explanation    The power calculated in use by the chassis exceeds that for which power supply redundancy is available. The chassis now function in additive mode.

Recommended Action    Remove some linecards to reduce power consumption, or install a higher capacity powershelf to regain power supply redundancy.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-3-ERROR_EXIT Envmon process exiting in [chars].[dec], error code [chars]

Explanation    The Envmon 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-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-FANTRAY_ALARM Fantray alarm on slot [chars]

Explanation    One or more fans on indicated fantray operating at below or above 30% of the set RPM. Remaining fans in operation on this fantray running at full speed.

Recommended Action    Verify the failure, use show env to help. If the failure does not alleviate, call your technical support representative for repair or replacement.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-3-FANTRAY_ALARM_CLEAR Fantray alarm cleared on slot [chars]

Explanation    All fans on indicated fantray operating at the set RPM.

Recommended Action    None required.

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-3-OPERATION_FAIL Failed in [chars].[dec], error code [chars]

Explanation    The particular operation mentioned in the message failed due to some reason. This may be a serious failure, however process may continue functioning as expected (or successfully retry) despite the failure.

Recommended Action    No action is required.

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-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 equals [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.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-OP_DBG Debug [chars]. ([dec],[dec],[dec],[dec],[dec]): error code [chars]

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

Recommended Action    Debug message only. No action is required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-OPERATION_DEBUG Debug [chars]. ([dec],[dec],[dec]): error code [chars]

Explanation    The particular operation mentioned in the message provide data due to some failure 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.

ETH_SRVR Messages

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

Explanation    Ethernet driver received an unknown for us packet.

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

Error Message     
 
    
    
   

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

Explanation    Ethernet driver received an unknown for us packet.

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

Error Message     
 
    
    
   

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

Explanation    Ethernet driver received an unknown for us packet.

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-ETH_SRVR-4-POISON_PILL_FORUS_PAK ethernet driver received a poison pill for us packet. Cmd equals [dec]

Explanation    Ethernet driver received a poison pill for us packet.

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

Error Message     
 
    
    
   

%PLATFORM-ETH_SRVR-4-queue_err [chars], buffer equals [pointer]

Explanation    Application tried to handle a buffer not part of queue. Use the CLI 'show controllers backplane ethernet trace buffstat location node*' to determine if there is a queue leak.

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-ETH_SRVR-7-INCORRECT_PAK Packet corruption detected in eth_server transmit complete

Explanation    Ethernet driver got a corrupted packet in its transmit complete, possibly because its client (EES) has zeroed out the packet contents before eth_server is done with the packet.

Recommended Action    'Copy the error message exactly as it appears on the console or in the system log. Issue the show buffer-manager region all context, SH_CMD show buffer-manager region all context, dumpcore running jid/process name of eth_server, ingressq, fabricq_mgr, fsdb_server, fsdb_aserver, sfe_driver & fgid_server command to gather data that may provide information to determine the nature of the error. If you cannot determine the nature of the error from the error message text or from the show buffer-manager region all context, SH_CMD show buffer-manager region all context, dumpcore running jid/process name of eth_server, ingressq, fabricq_mgr, fsdb_server, fsdb_aserver, sfe_driver & fgid_server output, call your Cisco technical support representative and provide the representative with the gathered information.'

ETHER_CTRL_DLL Messages

Error Message     
 
    
    
   

%PLATFORM-ETHER_CTRL_DLL-3-CONNECTION_OPERATION_FAIL Failed to [chars], error code [chars]

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

Recommended Action    Debug message only. No action is required.

Error Message     
 
    
    
   

%PLATFORM-ETHER_CTRL_DLL-3-MSG_OPERATION_FAIL Failed to [chars], port [dec], error code [chars]

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

Recommended Action    Debug message only. No action is required.

ETHER_CTRL Messages

Error Message     
 
    
    
   

%PLATFORM-ETHER_CTRL-3-ERROR_EXIT Exiting because [chars], error code [chars]

Explanation    The Ether-Ctrl process exited due to the reason mentioned in the message.

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

Error Message     
 
    
    
   

%PLATFORM-ETHER_CTRL-3-IF_OPERATION_FAIL [chars], port [dec], error code [chars]

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

Recommended Action    Debug message only. No action is required.

Error Message     
 
    
    
   

%PLATFORM-ETHER_CTRL-3-MGMT_IF_FAIL [chars], port [dec], error code [chars]

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

Recommended Action    Debug message only. No action is required.

Error Message     
 
    
    
   

%PLATFORM-ETHER_CTRL-3-MUTEX_OPERATION_FAIL [chars], [dec] error code [chars]

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

Recommended Action    Debug message only. No action is required.

Error Message     
 
    
    
   

%PLATFORM-ETHER_CTRL-3-OPERATION_FAIL [chars], error code [chars]

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

Recommended Action    Debug message only. No action is required.

Error Message     
 
    
    
   

%PLATFORM-ETHER_CTRL-3-PORT_INDEX_FAIL Port index ([dec]) is out of range, error code [chars]

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

Recommended Action    Debug message only. No action is required.

Error Message     
 
    
    
   

%PLATFORM-ETHER_CTRL-3-UNKNOWN_CODE Unknown code ([dec]) is out of range at [chars]

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

Recommended Action    Debug message only. No action is required.

Error Message     
 
    
    
   

%PLATFORM-ETHER_CTRL-4-COUNTER_OVFL [chars], port [dec], counter number [dec]

Explanation    The particular scenario mentioned in the message was detected for an unknown reason. This is not a critical failure, the process can continue functioning as expected despite the event.

Recommended Action    Debug message only. No action is required.

Error Message     
 
    
    
   

%PLATFORM-ETHER_CTRL-4-XCVR_WARNING [chars] for port ([dec]) is [chars] and disabled

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

Recommended Action    Debug message only. No action is required.

Error Message     
 
    
    
   

%PLATFORM-ETHER_CTRL-7-INFO [chars]

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

Recommended Action    Debug message only. No action is required.

FABARBITER Messages

Error Message     
 
    
    
   

%PLATFORM-FABARBITER-2-BKR_ERROR Crossbar fabric arbiter driver bkr module error

Explanation    Crossbar fabric arbiter driver detected a bkr module 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-FABARBITER-2-BKT_ERROR Crossbar fabric arbiter driver bkt module error

Explanation    Crossbar fabric arbiter driver detected a bkt module 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-FABARBITER-2-CARB_CRM_ERROR Crossbar fabric arbiter driver carb crm error

Explanation    Crossbar fabric arbiter driver detected a carb crm 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-FABARBITER-2-CARB_ENQDEQ_ERROR Crossbar fabric arbiter driver carb enqdeq error

Explanation    Crossbar fabric arbiter driver detected a carb enqdeq 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-FABARBITER-2-CARB_FIL_ERROR Crossbar fabric arbiter driver carb filter error

Explanation    Crossbar fabric arbiter driver detected a carb filter 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-FABARBITER-2-CPU_ACCESS_ERROR Crossbar fabric arbiter driver acess non-exist address location error

Explanation    Crossbar fabric arbiter driver detected an access non-exist address location 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-FABARBITER-2-CPU_PERR_ERROR Crossbar fabric arbiter driver cpu parity error

Explanation    Crossbar fabric arbiter driver detected a parity error from 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-FABARBITER-2-CPU_PROTOCOL_ERROR Crossbar fabric arbiter driver protocol error

Explanation    Crossbar fabric arbiter driver detected a protocol error from 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-FABARBITER-2-SERDES_ERROR Crossbar fabric arbiter driver serdes error

Explanation    Crossbar fabric arbiter driver detected a serdes error

Recommended Action    The error is a momentary error. If this error persists for a period of 60 seconds, please attempt to correct the error by reloading the card using the command: hw-module location reload

FABIO Messages

Error Message     
 
    
    
   

%PLATFORM-FABIO-3-ERR_INGQ_CREATE [chars], pri equals [dec], dir equals [dec], failed[[chars]]

Explanation    Internal Error

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

Error Message     
 
    
    
   

%PLATFORM-FABIO-3-ERR_INGRESS [chars]

Explanation    Internal Error

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

Error Message     
 
    
    
   

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

Explanation    Internal Error

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

Error Message     
 
    
    
   

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

Explanation    Failed to allocate memory.

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

Error Message     
 
    
    
   

%PLATFORM-FABIO-3-ERR_Q_LOOKUP qad_q_lookup failed, i equals [dec], dir equals [chars], failed[[chars]]

Explanation    Internal Error

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

Error Message     
 
    
    
   

%PLATFORM-FABIO-3-ERR_QUEUE_FOUND Found unexepected QAD queue [chars]

Explanation    Internal Error

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

Error Message     
 
    
    
   

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

Explanation    Internal Error

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

Error Message     
 
    
    
   

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

Explanation    Internal Error

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

FABRIC_CTRL Messages

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-2-ACTIVE_RP Encountered error when waiting for the active/standby role of the RP. rc equals [hex]

Explanation    This message indicates that the fabric control process encounter an error when waiting for the active RP notification. Process exits with error. This is either a system resource issue or a software bug.

Recommended Action    Try to restart fctl process to see if problem persists 'process restart fctl'. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-2-CARD_STATE [chars], [hex]

Explanation    This message indicates that the software tries to set the state of an unknown card. Software is in a bad state.

Recommended Action    Try to restart fctl process to see if problem persists 'process restart fctl'. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-2-CHKPT_INIT_FAILED Fabric control failed to initialize for data checkpointing, errno equals [hex]

Explanation    This message indicates that the fabric control process encountered a problem when trying to initialize data checkpointing. Process will abort.

Recommended Action    Try to restart fctl process to see if problem persists 'process restart fctl'. Check if system memory is adequate. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-2-CHKPT_REGISTRATION_FAILED Fabric control failed to register for data checkpointing, errno equals [hex]

Explanation    This message indicates that the fabric control process encountered a problem when trying to registering data for checkpointing. Process will abort.

Recommended Action    Try to restart fctl process to see if problem persists 'process restart fctl'. Check if system memory is adequate. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-2-ERR_MEM_ALLOC No memory avaliable for [chars]

Explanation    This message indicates that the system did not have enough memory available. [chars] is the operation for which there was insufficient memory. System is in an unstable state.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-2-ERR_MEM_ALLOC [chars]

Explanation    This message indicates that the system did not have enough memory available. [chars] is the operation for which there was insufficient memory. System may be in an unstable state.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-2-ERR_MEM_ALLOC [chars]

Explanation    This message indicates that the system did not have enough memory available. [chars] is the operation for which there was insufficient memory. System may be in an unstable state.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-2-ERR_REPORT [chars]

Explanation    This message indicates that an error detected in the fabric hardware as described in [char]

Recommended Action    Follow the instruction on the error message. If it is a suspected hardware failure, reseat the hardware. If reseating the hardware does not fix the error condition, contact your Cisco technical support representative.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-2-EVENT_LOOP Process event loop exited due to unknown errors. Abort

Explanation    This message indicates that the fabric control process encounter an error in its event dispatcher. Process aborts. This is either a system resource issue or a software bug

Recommended Action    Try to restart fctl process to see if problem persists 'process restart fctl'. Check if system memory is adequate. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-2-FAILED_SYNCH Slot [dec] does not see fabric clock from [chars]

Explanation    This message indicates that the card on slot int failed to synchronize clocks with the Master clock. If this condition persists, Slot int is unusable.

Recommended Action    Check the MBUS agent ROM version of the fabric cards and the card on slot int are up-to-date. Check the fabric loader version on slot int is up-to-date. Check the temperature of the fabric cards. Reseat the card on slot int and all the fabric cards. If reseating the hardware does not fix the error condition, contact your Cisco technical support representative.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-2-FAILED_TO_RESET_FC Failed to reset fabric card, slot equals [dec] in software

Explanation    A fabric card failed to reset. This message indicates that the software failed to reset the fabric card on slot int. Slot int is marked as malfunction and is shutdown.

Recommended Action    Check the MBUS agent ROM version of the fabric cards are up-to-date. Check the temperature of the fabric cards. Reseat the primary CSC card. If reseating the hardware does not fix the error condition, contact your Cisco technical support representative.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-2-FAILED_TO_SEND_CONFIG Failed to send new fabric configuration to slot [dec] after [dec] retries

Explanation    This message indicates that the linecard on slot int failed to receive the latest fabric configuration data it needs to connect to the fabric. slot int is disconnected from the fabric and is unusable.

Recommended Action    Reseat the linecard on slot int. If reseating the hardware does not fix the error condition, contact your Cisco technical support representative.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-2-FAILED_TO_SEND_SLOT_BW Failed sending slot bandwidth info to slot [dec] after [dec] retries

Explanation    This message indicates that the linecard on slot int failed to receive the latest slot bandwidth data it needs to operate. slot int is disconnected from the fabric and is unusable.

Recommended Action    Reseat the linecard on slot int. If reseating the hardware does not fix the error condition, contact your Cisco technical support representative.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-2-FAILED_TO_SYNC_RP Failed to sync RP (slot equals [dec]) to [chars] (slot equals [dec])

Explanation    This message indicates that the RP on slot int failed to synchronize its clock with the Master clock. The RP on slot int is unusable if this condition presists. If RP on slot int is the primary RP, then the router is unusable.

Recommended Action    Check the MBUS agent ROM version of the fabric cards and the RP on slot int are up-to-date. Check the temperature of the fabric cards. Reseat the RP on slot int and all the fabric cards. If reseating the hardware does not fix the error condition, contact your Cisco technical support representative.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-2-FAILED_TO_SYNC_RP_TO_CSCS Could not synch primary RP (slot equals [dec]) to both CSC1 and CSC0

Explanation    This message indicates that the primary RP failed to synchronize its clock with either CSC. If problem persists, router is unusable.

Recommended Action    Check the MBUS agent ROM version of the fabric cards and the RP on slot int are up-to-date. Check the temperature of the fabric cards. Reseat the RP on slot int and all the fabric cards. If reseating the hardware does not fix the error condition, contact your Cisco technical support representative.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-2-FAILED_TO_SYNC_TO_SELF Failed to sync [chars] (slot [dec]) to itself

Explanation    This message indicates that the primary CSC failed to synchronize its clock with itself. If problem persists, router is unusable.

Recommended Action    Check the MBUS agent ROM version of the fabric cards are up-to-date. Reseat the primary CSC card. Check the temperature of the fabric cards. If reseating the hardware does not fix the error condition, contact your Cisco technical support representative.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-2-MBUS_ERROR Unable to send MBUS msg. Error equals [dec] ([chars])

Explanation    This message indicates that an error occurred when the card tries to communicate with remote on fabric and chassis management via MBUS. Chassis, LCs and fabric is in a bad state.

Recommended Action    Verify the MBUS agent ROM version is up-to-date. Reseat the card with the error. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-2-NOTIFY_BW_CHG_ERROR new chassis bandwidth, [dec], cannot be sent to clients. Error: [chars]

Explanation    This message indicates that chassis bandwidth has changed but fabric control cannot send the info to its clients. Router may be in an unstable state.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-2-PROCESS_INIT Encountered critical problem in initialization of [chars]

Explanation    This message indicates that the system cannot initialize some critical parts of the fabric software. [chars] are the critical parts that failed. Fabric control process is aborted.

Recommended Action    Try to restart fctl process to see if problem persists 'process restart fctl'. Check if system memory is adequate. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-3-CARD_ID_FPGA_VERSION_MISMATCH Fabric Card type [hex] has an unsupported FPGA version. Card will be shutdown

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

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

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-3-MBUS [chars], errno equals [hex], [chars]

Explanation    This message indicates that an error occurred when RP tries to communicate with remote on fabric and chassis management via MBUS. If problem persists, chassis, LCs and fabric is in a bad state.

Recommended Action    Verify the MBUS agent ROM version is up-to-date. Try to restart fctl and mbus process to see if problem persists: 'process restart fctl' and 'process restart mbus'. If this is a newly inserted card, try to reseat the card. If problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-3-MIB_INIT_ERROR [chars]

Explanation    Unable to initialize the debugging facility of fabric MIB. Other fabric MIB capabilities are not disturbed.

Recommended Action    Try to restart fctl process to see if problem persists 'process restart fctl'. Check if system memory is adequate. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-3-RESTORE_DATA Encountered error restoring checkpointed data

Explanation    This message indicates that the system cannot restore checkpointed data of the fabric software. Router may be in an unstable state

Recommended Action    Try to restart fctl process to see if problem persists 'process restart fctl'. Check if system memory is adequate. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-3-THREAD_CREATE Unable to create thread to detect card insertion/removal for register [dec] : rc equals [hex], [chars]

Explanation    This message indicates that software encountered an error when creating a thread to detect lincard insertion and removal. Linecards, fabric cards, and RP insertion and removal may not be handled correctly.

Recommended Action    Try to restart fctl process to see if problem persists 'process restart fctl'. Check if system memory is adequate. Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-3-UNKNOWN_CHASSIS The chassis type is not known from reading the backplane

Explanation    This message indicates that the software installed on the system does not recognize the chassis type. The Backplane Server has not provided the chassis model. Software cannot monitor the chassis and will abort.

Recommended Action    Remove all the RPs from the backplane of the chassis except the active RP. Reload the active RP. Insert the other RPs into the chassis after the active RP is booted up in IOS-XR RUN state. If problem persists, copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-3-UNKNOWN_MSG Unknown msg from slot [dec] with msg type [hex]

Explanation    This message indicates that the fabric control process received an unknown msg. The message is ignored.

Recommended Action    Copy the message exactly as it appears on the console or in the system log. Research and attempt to resolve the issue using the tools and utilities provided at http://www.cisco.com/tac. With some messages, these tools and utilities will supply clarifying information. Search for resolved software issues using the Bug Toolkit at http://www.cisco.com/pcgi-bin/Support/Bugtool/launch_bugtool.pl. If you still require assistance, open a case with the Technical Assistance Center via the Internet at http://www.cisco.com/cgi-bin/front.x/case_tools/caseOpen.pl, or contact your Cisco technical support representative and provide the representative with the information you have gathered. Attach the following information to your case in nonzipped, plain-text (.txt) format: the output of the show logging and show tech-support commands and your pertinent troubleshooting logs.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-3-UNSUPPORTED_CHASSIS Chassis type [dec] not supported

Explanation    This message indicates that the software installed on the system does not recognize the chassis type. Software cannot monitor the chassis fabric. Fabric cards are shutdown.

Recommended Action    Verify the fabric card and chassis is supported by the software. Reseat the all the fabric cards. If reseating the hardware does not fix the error condition, contact your Cisco technical support representative

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-4-MCAST_PRI_CFG multicast-priority config has no effect on this chassis type

Explanation    This message indicates that hw-module fabric multicast-priority was configured but this configuration has no effect on this chassis. It only applies to non-Sphere 124xx chassis. The chassis type is an internal type value.

Recommended Action    Customer may wish to deconfigure hw-module fabric multicast-priority, but it is not necesary since this command has no effect on this chassis.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-5-FABRIC_CARD_OIR_INSERTED Fabric card [chars] inserted in slot [dec]

Explanation    This message indicates that a fabric card on slot int is inserted into the chassis. The fabric control software takes care of its insertion automatically. The chassis fabric and card's Fabric Interface ASIC are re-configured accordingly.

Recommended Action    No action required.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-5-FABRIC_CARD_OIR_REMOVED Fabric card [chars] removed from slot [dec]

Explanation    This message indicates that a fabric card on slot int is removed from the chassis. The fabric control software takes care of its removal automatically. The chassis fabric and card's Fabric Interface ASIC are re-configured accordingly.

Recommended Action    No action required.

FAN Messages

Error Message     
 
    
    
   

%PLATFORM-FAN-0-OVERCURRENT ClkCtrl detected an overcurrent condition on Fan [chars]

Explanation    ClkCtrl detected an overcurrent condition on Fan

Recommended Action    Please replace the fan. 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.

FCA Messages

Error Message     
 
    
    
   

%PLATFORM-FCA-2-CPT_DEV_VERSION_ERROR PHY controller driver version is not compatible with the hardware version. [chars]

Explanation    PHY controller driver version is not compatible with PHY controller hardware version.

Recommended Action    Upgrade the PHY controller CPLD image using the FPD procedure, followed by reloading the board. 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-FCA-2-CPT_PAR_ERROR PHY controller driver detected parity errors

Explanation    PHY controller driver detected a parity error.

Recommended Action    Please correct the problem by reloading the board using command 'reload 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-FCA-2-CRRS_DEV_VERSION_ERROR Port controller version is not compatible with the hardware version. [chars]

Explanation    Port controller driver version is not compatible with the hardware version.

Recommended Action    Upgrade the Port controller FPGA image using the FPD procedure, followed by reloading the board. 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-FCA-2-CRRS_PAR_ERROR Port controller driver detected parity errors

Explanation    Port controller driver detected a parity error

Recommended Action    Please correct the problem by reloading the board using command 'reload 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-FCA-2-CT2_DEV_VERSION_ERROR Port controller driver version is not compatible with the hardware version. [chars]

Explanation    Port controller driver version is not compatible with the hardware version.

Recommended Action    Upgrade the Port controller FPGA image using the FPD procedure followed by reloading the board. 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-FCA-2-CT2_PAR_ERROR Port controller driver detected parity errors

Explanation    Port controller driver detected a parity error

Recommended Action    Please correct the problem by reloading the board using command 'reload 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-FCA-2-LB_DEV_VERSION_ERROR PHY controller driver version is not compatible with the hardware version. [chars]

Explanation    PHY controller driver version is not compatible with the hardware version.

Recommended Action    Upgrade the PHY controller CPLD image followed by reloading the board. 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-FCA-2-LBO_PAR_ERROR PHY controller driver detected parity errors

Explanation    PHY controller driver detected a parity error.

Recommended Action    Please correct the problem by reloading the board using command 'reload 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-FCA-2-SFP_I2C_PHY_ACK_ERROR SFP I2C PHY Ack error

Explanation    Port controller driver detected I2C access error on PHY SFP port.

Recommended Action    Ensure that the SFP plugged in is supported. If not, replace the SFP. 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-FCA-2-SFP_I2C_PHY_TM_ERROR I2C PHY operation got either aborted/failed

Explanation    Port controller driver detected I2C timeout error on PHY SFP port.

Recommended Action    Ensure that the SFP plugged in is supported. If not, replace the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_0 Port controller driver detected a TX fault on the SFP port 0

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_1 Port controller driver detected a TX fault on the SFP port 1

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_10 Port controller driver detected a TX fault on the SFP port 10

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_11 Port controller driver detected a TX fault on the SFP port 11

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_12 Port controller driver detected a TX fault on the SFP port 12

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_13 Port controller driver detected a TX fault on the SFP port 13

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_14 Port controller driver detected a TX fault on the SFP port 14

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_15 Port controller driver detected a TX fault on the SFP port 15

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_16 Port controller driver detected a TX fault on the SFP port 16

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_17 Port controller driver detected a TX fault on the SFP port 17

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_18 Port controller driver detected a TX fault on the SFP port 18

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_19 Port controller driver detected a TX fault on the SFP port 19

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_2 Port controller driver detected a TX fault on the SFP port 2

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_20 Port controller driver detected a TX fault on the SFP port 20

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_21 Port controller driver detected a TX fault on the SFP port 21

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_22 Port controller driver detected a TX fault on the SFP port 22

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_23 Port controller driver detected a TX fault on the SFP port 23

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_24 Port controller driver detected a TX fault on the SFP port 24

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_25 Port controller driver detected a TX fault on the SFP port 25

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_26 Port controller driver detected a TX fault on the SFP port 26

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_27 Port controller driver detected a TX fault on the SFP port 27

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_28 Port controller driver detected a TX fault on the SFP port 28

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_29 Port controller driver detected a TX fault on the SFP port 29

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_3 Port controller driver detected a TX fault on the SFP port 3

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, do SFP OIRs a few times. 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-FCA-2-SFP_LNK_FAULT_ERROR_30 Port controller driver detected a TX fault on the SFP port 30

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_31 Port controller driver detected a TX fault on the SFP port 31

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_32 Port controller driver detected a TX fault on the SFP port 32

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_33 Port controller driver detected a TX fault on the SFP port 33

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_34 Port controller driver detected a TX fault on the SFP port 34

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_35 Port controller driver detected a TX fault on the SFP port 35

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_36 Port controller driver detected a TX fault on the SFP port 36

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_37 Port controller driver detected a TX fault on the SFP port 37

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_38 Port controller driver detected a TX fault on the SFP port 38

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_39 Port controller driver detected a TX fault on the SFP port 39

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_4 Port controller driver detected a TX fault on the SFP port 4

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_5 Port controller driver detected a TX fault on the SFP port 5

Explanation    Port controller driver detected a TX fault on the SFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_6 Port controller driver detected a TX fault on the SFP port 6

Explanation    Port controller driver detected a TX fault on the SFP port 6.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_7 Port controller driver detected a TX fault on the SFP port 7

Explanation    Port controller driver detected a TX fault on the SFP port 7.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port 7 interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_8 Port controller driver detected a TX fault on the SFP port 8

Explanation    Port controller driver detected a TX fault on the SFP port 8.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port 8 interface. If the problem persists, please OIR the SFP. 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-FCA-2-SFP_LNK_FAULT_ERROR_9 Port controller driver detected a TX fault on the SFP port 9

Explanation    Port controller driver detected a TX fault on the SFP port 9.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port 9 interface. If the problem persists, please OIR the SFP. 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-FCA-2-XFP_I2C_ERROR Port controller driver detected I2C access error on XFP port

Explanation    Port controller driver detected I2C access error on XFP port.

Recommended Action    Ensure that the XFP plugged in is supported. If not, please replace the XFP. If the problem persists, please OIR the XFP. 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-FCA-2-XFP_LNK_FAULT_ERROR_0 XFP Link TX fault error on port 0

Explanation    Port controller driver detected a TX fault on the XFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. Do XFP OIR. 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-FCA-2-XFP_LNK_FAULT_ERROR_1 XFP Link TX fault error on port 1

Explanation    Port controller driver detected a TX fault on the XFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. Do XFP OIRs. 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-FCA-2-XFP_LNK_FAULT_ERROR_2 XFP Link TX fault error on port 2

Explanation    Port controller driver detected a TX fault on the XFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. Do XFP OIR. 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-FCA-2-XFP_LNK_FAULT_ERROR_3 XFP Link TX fault error on port 3

Explanation    Port controller driver detected a TX fault on the XFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. Do XFP OIR. 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-FCA-2-XFP_LNK_FAULT_ERROR_4 XFP Link TX fault error on port 4

Explanation    Port controller driver detected a TX fault on the XFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. Do XFP OIR. 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-FCA-2-XFP_LNK_FAULT_ERROR_5 XFP Link TX fault error on port 5

Explanation    Port controller driver detected a TX fault on the XFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. Do XFP OIR. 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-FCA-2-XFP_LNK_FAULT_ERROR_6 XFP Link TX fault error on port 6

Explanation    Port controller driver detected a TX fault on the XFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. Do XFP OIR. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-FCA-2-XFP_LNK_FAULT_ERROR_7 XFP Link TX fault error on port 7

Explanation    Port controller driver detected a TX fault on the XFP port.

Recommended Action    In config mode, do a 'shut' and 'no shut' on port interface. Do XFP OIR. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-FCA-3-SFP_I2C_ACK_ERROR Port controller driver detected I2C access error on SFP port

Explanation    Port controller driver detected I2C access error on SFP port.

Recommended Action    Ensure that the SFP plugged-in is supported. If not, please replace the SFP. If the problem persists, please OIR the SFP. 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-FCA-3-SFP_I2C_TM_ERROR Port controller driver detected I2C timeout error on SFP port

Explanation    Port controller driver detected I2C timeout error on SFP port.

Recommended Action    Ensure that the SFP plugged in is supported. If not, please replace the SFP. If the problem persists, please OIR the SFP. 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.

FDIAGS Messages

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-BAD_EE_READ failure reading EEPROM ([chars]) values during Field Diag EEPROM update: EEPROM not updated

Explanation    After completing Field Diags, the EEPROM update was requested, but there was a read failure during the process. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-BAD_EE_WRITE failure writing EEPROM @ offset of [hex] during Field Diag EEPROM update: This byte not updated

Explanation    After completing Field Diags, the EEPROM update was requested, but there was a write failure during the process. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-BAD_F_DIAG_KILL Unable to kill this existing Field Diag process: rc from kill was [dec]

Explanation    Could not kill that job ID for Field Diags Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-BUFFER_TOO_SMALL The [chars] buffer is too small - need [dec]; have [dec].

Explanation    The current IOS-XR field diagnostics command failed because the software found that an internally configured buffer was not large enough.

Recommended Action    This is an internal software error. Please contact Cisco's support organization to report this problem. Please collect syslogs, verbose run log and show diags detail.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-CANNOT_GET_JID Cannot determin Job ID for Field Diags process

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

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-CANT_SEND_MBUS_MSG_F cannot send mbus messages: errno [dec]: [chars]()

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

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-FAB_MBUS_NOT_READY Fabric card MBUS Ram Agent not loaded prior to beginning Field Diags Fabric tests

Explanation    After launching Fabric Field Diagnostics, the fabric card appear not have MBUS Ram Agent loaded within the appropriate time. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.

Recommended Action    Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail. Investigate why MBUS Ram agent is not successfully downloaded on the fabric card.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-FABRIC_NOT_DISCONNECTED Problems occurred while trying to disconnect slot [dec] from the fabric. RC equals [hex]

Explanation    Field diagnostics encountered a failure while trying to restore the fabric for the slot that was just tested. Field diagnostics uses a FCTL API to disconnect the slot under test from the fabric when it is done. This API failed, returning the specified return value.

Recommended Action    This is a software error, please contact Cisco support to report this problem. Please collect syslogs, verbose run log, show diags detail and show controller output. If the slot eventually transitions to the IOS XR RUN state, then no further actions are needed. The system cleaned itself up. However, if the slot remains in the FDIAGS FAIL state (because field diagnostics failed) or stays in the FDIAG PASS state (because the user specified the 'wait' parameter). Then you need to reload the slot to complete the fabric clearing process.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-FABRIC_NOT_RESTORED Problems occurred while trying to clear the fabric.

Explanation    Field diagnostics encountered a failure while trying to restore the fabric for the slot that was just tested. Other software errors should have been logged before this to provide details about what failed.

Recommended Action    This is a software error, please contact Cisco support to report this problem. Please collect syslogs, verbose run log, show diags detail and show controller output.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-FAILED_SYSMGR_FORK Failed to fork Field Diags process: [chars]

Explanation    Call to fork process for Field Diags failed for given reason Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-FILE_READ_JID_BAD Cannot read jid data from file

Explanation    Could not read that job ID for Field Diags from the file Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-IDLE_CELL_GEN_ADDR [chars]() could not determine the idle cell generation address.

Explanation    Field diagnostics was not able to determine the idle cell generation address for the router's fabric.

Recommended Action    This is a software error, please contact Cisco support to report this problem. Please collect syslogs, verbose run log, show diags detail and show controller output.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-IF_BAD_HALT_OPEN Unable to open Field Diags halt request file [chars]: [chars]

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

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-IF_BAD_HALT_WRITE Unable to write Field Diags halt request to file [chars]: [chars]

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

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-IF_BAD_JID_OPEN Unable to open Field Diags state file [chars]: [chars]

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

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-IF_BAD_JID_READ Unable to read Field Diags state from file [chars]: [chars]

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

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-IF_BAD_JID_WRITE Unable to write Field Diags state to file [chars]: [chars]

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

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-IF_FAIL_CONN_SYSLDR_F could not connect to LWM [chars] in [chars]()

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

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-IF_FAIL_SEND_SYSLDR_F could not send LWM in [chars]()

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

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-IF_FAIL_SYSLDR_DISCONNECT_F could not LWM disconnect from [chars] in [chars]()

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

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-IF_FAIL_UUT_LAUNCH UUT launch failed ([chars]). Exiting.

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

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-IF_INACTIVITY_TIMEOUT No response from UUT in ~[dec] minutes ([dec] seconds). exiting

Explanation    No communication from the UUT in a while. UUT likely became inoperable. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-IF_NON_EXISTANT_JID_OPEN Unable to open Field Diags state file [chars]: [chars]

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

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-ILLEGAL_FSM_STATE internal (FSM) state change ILLEGAL: was [chars], attempted [dec]

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

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-INVALID_FABRIC 40G fabric is not supported on 12x04 chassis

Explanation    Field diagnostics has been asked to do a 40G operation on a 12x04 chassis, which is not a supported fabric chassis combination. Field diagnostics is proceeding with the action as if this where not a 40G fabric.

Recommended Action    This is a software error, please contact Cisco support to report this problem. Please collect syslogs, verbose run log, show diags detail and show controller output.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-INVALID_SLOT [chars]() encountered an invalid slot ([dec])

Explanation    Field diagnostics validated a slot value before using it and found that it was invalid. Consequently this event was raised. Other field diagnostics errors will be raised to further explain the impact of this problem.

Recommended Action    This is a software error, please contact Cisco support to report this problem. Please collect syslogs, verbose run log, show diags detail and show controller output.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-MALFORMED_INSTALL_PATH [chars]. Failing path is ([chars])

Explanation    The field diagnostics proxy on the standby RP has received an install path from the install infrastructure, but it is not formatted as expected. Consequently field diagnostics is not able to execute on the standby RP.

Recommended Action    Internal error: Contact Cisco's TAC. Collect screen output from the active and standby consoles, 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 create a node identifier. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-MS_PRI_CLK_READ misc svcs: [chars]: could not read primary clock

Explanation    Failed to read Primary Clock from fctl Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-MS_READ_REG_FAIL Failed to read register [hex] from slot [dec]. Errval equals [hex].

Explanation    Failed to read a slot-specific register via an mbus-access Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-MS_UNDEF_MS_MSG misc svcs: [chars]: Undefined MBUS_MISC_SVCS message received: Ignored: msg [hex]

Explanation    Misc services server received an unrecognized message Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-MS_WRITE_REG_FAIL Failed to write [hex] to register [hex] on slot [dec]. Errval equals [hex].

Explanation    Failed to write a slot-specific register via an mbus-access Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-MS_XBAR_MAP misc svcs: [chars]: could not read xbar map

Explanation    Failed to read xbar map from fctl Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-NO_PRIMARY_CSC Cannot determine which CSC is the primary. RC:[dec]-[dec]

Explanation    Field diagnostics needs to know which CSC is the primary before it can run on the fabric cards. However, it was not able to determine which CSC was the primary. The field diagnostics run stops.

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-NO_TIME_OF_DAY no time of day

Explanation    Time of Day unavailable internally

Recommended Action    Time of day (calendar) may not be initialized. Set using the appropriate CLI and options.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-NODE_ID_EXTRACTION_FAILED Failed to extract node id from var: line [dec]

Explanation    One of the calls to a node ID extraction function returned an error Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-NON_UUT_IN_STATE Unexpected message received during UUT_ON state: sub-msg [hex] from slot [dec]

Explanation    Field Diags was not expecting this type of message at this time. If this problem persists and diags does not complete, Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-PROBLEM_WITH_FDIAG_REQUEST Failed to validate field diagnostic request. Unexpected return code: [dec]

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

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-PROG_REG_FAIL Failed [chars] write [hex] to register [hex] on slot/broadcast group [dec]. Errval equals [hex]

Explanation    Failed to write a value to the register in the specified slot or broadcast group. Internal error: Contact Cisco's TAC. Collect syslogs, verbose run log and show diags detail.

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-RESTORE_DEFAULT_RAM_AGENT FAILURE re-loading default mbus ram agent

Explanation    This card requires a special version of mbus Ram Agent for compatibility with diags for C2W requests for SPA communication Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-RP_FILE_PATH Unable to obtain file path for RP field diagnostics image. Fail code: [hex]

Explanation    The field diagnostics proxy on the standby RP was not able to determine the file path for the RP's field diagnostics binary. An infrastructure function failed, returning the fail code displayed. Consequently, field diagnostics is not able to execute on the standby RP.

Recommended Action    Internal error: Contact Cisco's TAC. Collect screen output from the active and standby consoles, syslogs, verbose run log and show diags detail.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-RP_INSTALL_PATH Unable to obtain install path for RP field diagnostics image. Fail code: [hex]

Explanation    The field diagnostics proxy on the standby RP was not able to determine the install path for the RP's field diagnostics binary. An infrastructure function failed, returning the fail code displayed. Consequently, field diagnostics is not able to execute on the standby RP.

Recommended Action    Internal error: Contact Cisco's TAC. Collect screen output from the active and standby consoles, syslogs, verbose run log and show diags detail.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-SPA_ID_FAIL Unable to identify SPA's inserted in slot [dec]

Explanation    The field diags processs was unable to determine which SPAs where inserted in the SIP. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-SPA_UNSUPPORTED_INSTANCE Requested instance ([dec]) (bay) not supported by this UUT (min equals [dec], max equals [dec])

Explanation    Spa bay requested not supported

Recommended Action    Select a spa bay in within the appropriate range

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-SPCL_RAM_AGENTDL_FAILED Download of LC Ram Agent diag_mbus_ram.ucode failed

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

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-SYSDB_BIND_FAILURE Cannot connect to the system data base. Field diagnostics cannot be run.

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-UNRECOGNIZED_CARD Card type ([dec]) is NOT recognized

Explanation    This card type is not recognized in this version

Recommended Action    If available, upgrade to a more recent version of the diags component.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-UNSUPP_CARD Card type not supported

Explanation    This card type is not supported in this version

Recommended Action    if available, upgrade to a more recent version of the diags component.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-VARIABLE_GET Unable to get variable '[chars]'. Fail code: [hex]

Explanation    The field diagnostics proxy on the standby RP was not able to obtain the specified environment variable. Consequently it was not able to adjust the environment to run the field diagnostics application on the standby RP.

Recommended Action    Internal error: Contact Cisco's TAC. Collect screen output from the active and standby consoles, syslogs, verbose run log and show diags detail.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-3-VARIABLE_SET Unable to set variable '[chars]'. Fail code: [hex]

Explanation    The field diagnostics proxy on the standby RP was not able to modify the specified environment variable. Consequently it was not able to adjust the environment to run the field diagnostics application on the standby RP.

Recommended Action    Internal error: Contact Cisco's TAC. Collect screen output from the active and standby consoles, syslogs, verbose run log and show diags detail.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-4-BOOT_ALREADY_SET BOOT variable is already set.

Explanation    The field diagnostics proxy on the standby RP was attempting to modify the standby's environment variables in order to run the field diagnostics binary. However, it found that the BOOT variable was already set. This is unexpected, but should not be harmful. The application continued with its attempt to load and run the field diagnostics application on the standby RP.

Recommended Action    If the warning continuously appears when running field diagnostics on the standby RP, or if the standby RP fails to load and launch the field diagnostics application then contact Cisco's TAC. Collect screen output from the active and standby consoles, syslogs, verbose run log and show diags detail.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-4-ERROR_AFTER_RESULTS_REPORT Unexpected return value from reporting results to sysldr: [chars]

Explanation    Resulting response from sysldr after reporting final results indicates a non-happy sysldr. Reason in string from sysldr Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-4-SYSDB_ITEM_GET_FAILURE There is a problem with the standby RP state. Field diagnostics cannot be run

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

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-4-UNEXP_MSV_SUB_MSG Unexpected Misc Services message subtype [dec] received from slot [dec]

Explanation    An unexpected MBUS_FDIAG MISC Services message was received from UUT. Possibly a mal-formed or unfinished software enhancement. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-4-UNEXP_SUB_MSG Unexpected message subtype [dec] received from slot [dec]

Explanation    An unexpected MBUS_FDIAG message was received from UUT. Possibly a mal-formed or unfinished software enhancement. Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-4-UNSUPPORTED_RP_HW_CONFIG Field diagnostics cannot be run on [chars].

Explanation    IOS-XR Field diagnostics is not currently supported on the specified RP configuration.

Recommended Action    This is a warning. This is not a defect. The user attempted to execute IOS-XR field diagnostics on an unsupported RP configuration.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-4-WRONG_CONFIG_REG_VAL WARNING: Field diagnostics cannot be run with the current config-register setting

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

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

Error Message     
 
    
    
   

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

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

Recommended Action    No action required

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-5-DIAG_ONLY_SUPPORT_IN_IOX_RUNNING_STATE Field Diagnostics can only be invoked when PRP is in IOX Running state.

Explanation    The field diagnostics can only be invoked when the PRP is in IOX Running state.

Recommended Action    Not applicable, informational message only

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-5-DL_DONE Field Diags download completed on slot [dec]. Status: [chars]

Explanation    This is a notice field diags has been downloaded to the specified slot. The next step is that field diags will start running on the specified slot.

Recommended Action    Nothing. This is a notice that field diags been downloaded to the specified slot. This is only done when a user manually runs field diags from the CLI.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-5-DL_START Field Diags downloading to slot [dec]

Explanation    This is a notice that field diags has started to download to the specified slot.

Recommended Action    Nothing. This is a notice that field diags has started to download to the specified slot. This is only done when a user manually runs field diags from the CLI.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-5-DONE Field Diags completed for slot [dec]

Explanation    This is a notice that field diags has completed on the specified slot. This is the last field diags related message for this slot.

Recommended Action    Nothing. This is a notice that field diags has stopped on the specified slot. If field diags passed the slot will automatically reload IOS, if if failed, the card will remain offline until it is manually reset by the user.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-5-HALT_REQUESTED A halt request is present: Shutting down Field Diags process (FSM)

Explanation    FSM has detected that a halt is to be initiated

Recommended Action    nothing.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-5-IF_LONGEST_TIME_MSG Longest time inactivity ([dec] secs)(~[dec] minutes) just after [[chars]]

Explanation    The longest time difference message preceding this

Recommended Action    none - informational only

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-5-IF_NO_CONSOLE Can not open /dev/console to write, fdiag quits

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

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-5-IF_TERMINATED_F_DIAGS_OK Successfully terminated Field Diags (jid equals [dec], Field Diags state file [chars])

Explanation    Success in terminating Field Diags instance on a particular slot

Recommended Action    None - Action performed successfully.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-5-IF_TOTAL_TEST_TIME Total Test Time: ~[dec] minutes ([dec] seconds)

Explanation    Ho long this set of tests ran for

Recommended Action    none - informational only

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-5-LC_TYPE_DEFAULT_RAM_AGENT Now restoring default ram agent ([chars])

Explanation    This card had the diags ram agent loaded for the test, but will now restore the system one Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-5-LC_TYPE_REQUIRES_SPCL_RAM_AGENT Linecard type requires diags_mbus_ram.ucode - downloading

Explanation    This card requires a special version of mbus Ram Agent for compatibility with diags for C2W requests for SPA communication Internal error: Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.

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

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-5-START Field Diags starting on slot [dec]

Explanation    This is a notice that a user has started field diags on the specified slot.

Recommended Action    Nothing. This is a notice that field diags was started on the specified slot. Consequently, this slot will be taken offline as the field diags image is downloaded to and run on the slot.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-5-SYSLDR_FINISH_HANDOFF Sysldr notified of completion: params sl:[dec] wait:[hex] diag_stats:[hex] roe_flag:[hex]

Explanation    Just finishing diag command and telling sysldr to handle finished diags state on the same slot

Recommended Action    nothing

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-6-COMPLETE Field Diags COMPLETE on UUT ([chars]) [chars], card type [dec], [chars] s/n [chars]

Explanation    Field diagnostics has completed, where the message identifies the final status, the card's numeric and string type as well as its serial number.

Recommended Action    None. This is an informational message to log the completion status of field diagnostics.

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-6-OUT [chars]

Explanation    Non error-specific redirected output from diag process to syslog. This may be test names, progress messages, or failure information generated by the UUT.

Recommended Action    No action

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-6-RESULT Field Diags COMPLETE on UUT ([chars]) [chars] card type [dec] [[chars]] s/n [chars]

Explanation    Field Diagnostics final results

Recommended Action    No action

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-6-UUT_OUT UUT [chars]: [chars]

Explanation    Text output from UUT (Cisco use only) Non error-specific redirected output from diag process to syslog. This may be test names, progress messages, or failure information generated by the UUT.

Recommended Action    No action

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-6-UUT_OUT_I UUT (init) [chars]: [chars]

Explanation    Text output from UUT during init state (Cisco use only) Non error-specific redirected output from diag process to syslog. This may be test names, progress messages, or failure information generated by the UUT.

Recommended Action    No action

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-7-FORCE_INTO_FSM Forcing into FSM mode, even though sysldr load UUT returned error

Explanation    Internal use - ignoring sysldr error, continuing to Field Diags FSM

Recommended Action    nothing

Error Message     
 
    
    
   

%PLATFORM-FDIAGS-7-NON_HELLO_MSG During Init state, unexpected mbus sub-message [hex] received from slot [dec]

Explanation    Field Diags was not expecting this type of message at this time. If this problem persists and diags does not complete, Contact Cisco's TAC. This error could be a software problem or could be related to failing hardware. Please report this to TAC along with other supportive log information to determine the best course of action for this UUT.

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

FFQ Messages

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-FFQ-3-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 equals [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 equals [chars], errno equals [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,[chars]

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 equals [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 [chars] 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 equals [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 [chars] 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.

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.

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

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.

Error Message     
 
    
    
   

%PLATFORM-FIB_IDB_LIB-3-ERROR [chars]

Explanation    PLATFORM FIB, error

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

FIB_LTRACE Messages

Error Message     
 
    
    
   

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

Explanation    PLATFORM FIB, error information

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

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.

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.

FPD_BURNER Messages

Error Message     
 
    
    
   

%PLATFORM-FPD_BURNER-3-BAD_ARG Bad command option: [chars] [chars]

Explanation    Bad coammand option.

Recommended Action    No action is required..

Error Message     
 
    
    
   

%PLATFORM-FPD_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-FPD_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-FPD_BURNER-5-progress [chars] [chars]

Explanation    Output progress to RP console.

Recommended Action    No action is required..

Error Message     
 
    
    
   

%PLATFORM-FPD_BURNER-5-version [chars] version [dec].[dec] is not supported for this board.

Explanation    Invalid FPD version to RP console.

Recommended Action    No action is required..

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 equals [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 equals [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] [hex]

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

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

Error Message     
 
    
    
   

%PLATFORM-GSR_LC_PM-3-FATAL GSR_LC_PM: Fatal Error, reason equals [chars]

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

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

Error Message     
 
    
    
   

%PLATFORM-GSR_LC_PM-3-FATAL_2 gsr_lc_pm: fatal error encountered, reason equals [chars], errno equals [dec]

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

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

Error Message     
 
    
    
   

%PLATFORM-GSR_LC_PM-3-INIT_ERR Process initialization failed: ([chars]%s)

Explanation    The linecard platform-mgr process failed to initialize. The platform-mgr process runs on the linecard and handles interface information between the route processor and the linecard hardware drivers. It also stores all local linecard information for every interface configured on the linecard. If the platform-mgr fails to initialize, no linecard interfaces can be created or deleted. %s - indicates the reason for the failure. %s - is the decoded error reason.

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

GSR_LIB Messages

Error Message     
 
    
    
   

%PLATFORM-GSR_LIB-3-CONN_ERR Event manager failure: ([chars]%s)

Explanation    An error occurred in the system data-base (SysDB) event manager GSR platform library DLL. This DLL controls thread creation, deletion and connections between all other processes and DLL's. If there is a failure in this DLL, a connection will be lost somewhere on the system and failures will occur. %s - indicates the reason for the failure. %s - is the decoded error reason.

Recommended Action    The DLL will attempt to recover itself, but if it cannot, the card will probably have to be reloaded as messages will have been lost and the system may be in a bad state. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-GSR_LIB-3-ERROR [chars] ([chars])

Explanation    For displaying error conditions with traceback and an error string.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-GSR_LIB-3-LR_ERR Logical router failure: ([chars]%s)

Explanation    An error occurred during a card state change. This DLL controls the node information during a card state change for logical routers. If there is a failure here, the logical router will lose its nodeid information and will get out of sync with the system. %s - indicates the reason for the failure. %s - is the decoded error reason.

Recommended Action    The DLL will attempt to recover itself, but if it cannot, the card will need to be reloaded as the system will be in a bad state. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

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 equals [unsigned int], param2 equals [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 equals [hex] on this board. Please upgrade the PLD to atleast [hex], and check for i2c rework

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

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

Error Message     
 
    
    
   

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

Explanation    As shown in the message.

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

Error Message     
 
    
    
   

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

Explanation    Detected i2c bus hang.

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

Error Message     
 
    
    
   

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

Explanation    As shown in the message.

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

HBAGENT Messages

Error Message     
 
    
    
   

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

Explanation    Fatal internal error.

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

Error Message     
 
    
    
   

%PLATFORM-HBAGENT-2-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-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-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-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-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-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_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-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.

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.

HD Messages

Error Message     
 
    
    
   

%PLATFORM-HD-2-DEV_HARDDISK_DEVICE_ERR Hard disk device error

Explanation    Hard disk encountered media errors

Recommended Action    This error is a momentary error and software should be able to correct 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-HD-3-DEV_HARDDISK_RESTART Hard disk restarted

Explanation    Hard disk restart is taking excess time.

Recommended Action    Please attempt to restart the hd_drv process using command: 'process restart hd_drv'. 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.

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-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-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-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*

Error Message     
 
    
    
   

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

Explanation    HFR IP-EA, Debug information

Recommended Action    *SUPPORT*

HFR_L2FIB_METRO_SHOW Messages

Error Message     
 
    
    
   

%PLATFORM-HFR_L2FIB_METRO_SHOW-3-ERROR HFR_L2FIB_METRO_SHOW: [chars] , [chars]

Explanation    HFR_L2FIB_METRO_SHOW encountered an error

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

Error Message     
 
    
    
   

%PLATFORM-HFR_L2FIB_METRO_SHOW-7-USAGE hfr_l2fib_metro_show: invalid option passed to hfr_l2fib_metro_show command. [chars]

Explanation    Startup option supplied to HFR_L2FIB_METRO_SHOW is not valid.

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

HFR_LCPM_SHOW Messages

Error Message     
 
    
    
   

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

Explanation    HFR_PM_SHOW encountered an error

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

Error Message     
 
    
    
   

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

Explanation    HFR_PM_SHOW encountered an error

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

Error Message     
 
    
    
   

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

Explanation    Startup option supplied to HFR_PM_SHOW is not valid.

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

Error Message     
 
    
    
   

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

Explanation    Startup option supplied to HFR_PM_SHOW is not valid.

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

HFR_MPLS_EA Messages

Error Message     
 
    
    
   

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

Explanation    CRS-1 MPLS-EA, error

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

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

Explanation    CRS-1 MPLS-EA, error

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

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

Explanation    CRS-1 MPLS-EA, Debug information

Recommended Action    *SUPPORT*

HFR_PM_TEST Messages

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

HFR_PM Messages

Error Message     
 
    
    
   

%PLATFORM-HFR_PM-3-BAD_PMLIB_SERVER_CONTEXT [chars], svr_ctx equals 0x[pointer], expected_ctx equals 0x[pointer]

Explanation    The Platform Manager detected a software error where the received library server context does not match the expected value.

Recommended Action    No action is required as the software has rejected the transaction request. Please collect the error message, traceback and 'show log'

Error Message     
 
    
    
   

%PLATFORM-HFR_PM-3-ERR_FAULT_FROM_DEVICE Device [chars] #[dec] has a fault equals [chars]. Resetting

Explanation    The specified device has a fault that affects the card functionality. The card node will be reset and ideally the problem will not happen again when it comes back up.

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

Error Message     
 
    
    
   

%PLATFORM-HFR_PM-3-ERR_FAULT_SENT Cannot send [chars] #[dec] fault equals [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 equals [chars], errno equals [dec]

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

Explanation    Platform Manager encountered a fatal memory allocation error

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

Error Message     
 
    
    
   

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

Explanation    Platform Manager encountered a fatal memory allocation error

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

Error Message     
 
    
    
   

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

Explanation    The Platform Manager encountered an provisioning warning.

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

Error Message     
 
    
    
   

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

Explanation    The Platform Manager encountered an provisioning warning.

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

Explanation    The Platform Manager encountered an internal software error.

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

Error Message     
 
    
    
   

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

Explanation    The Platform Manager encountered an internal software error.

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

Error Message     
 
    
    
   

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

Explanation    The Platform Manager encountered an internal software initialization error.

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

Error Message     
 
    
    
   

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

Explanation    The Platform Manager encountered an internal software initialization error.

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

HSR_ES_CLI Messages

Error Message     
 
    
    
   

%PLATFORM-HSR_ES_CLI-3-CAPS_LOAD_FAILED Sponge caps load failed, sponge_caps equals [dec], rc equals [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 equals [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 equals [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 equals [chars], errno equals [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 equals [chars], errno equals [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 equals [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-3-BP_EN_ERROR Error while setting PLD resgister to enable/disable access to backplane: unable to [chars] mastership

Explanation    Error while trying to grab or release the lock.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-I2C-3-EMPTY_BIT_NOT_CLEARED_ERROR I2C server process restarting due to unrecoverable EMPTY Bit Not Cleared errors

Explanation    I2C operation failed because the EMPTY bit is still set after multiple retries. I2C server process will automatically restart to recover from this error condition.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-I2C-3-ERR_INIT i2c server process exiting, reason: [chars]

Explanation    The i2c server process cannot continue due to error condition mentioned in the message.

Recommended Action    The System Manager process (sysmgr) will automatically respawn this process, up to a fixed number of times when this error is encountered, to recover.

Error Message     
 
    
    
   

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

Explanation    None

Recommended Action    Replace the bad part for LC to work.

Error Message     
 
    
    
   

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

Explanation    None

Recommended Action    Replace the bad part for LC to work.

Error Message     
 
    
    
   

%PLATFORM-I2C-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_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-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-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

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

INTCTRL Messages

Error Message     
 
    
    
   

%PLATFORM-INTCTRL-2-BLG_RDY_ERROR Interrupt controller driver fab arbiter ready error

Explanation    Interrupt controller driver detected a fab arbiter ready error (ack not received).

Recommended Action    Please correct the problem by reloading the board using command 'reload 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-INTCTRL-2-BLG_RX_PAR_ERROR Interrupt controller driver crossbar fabric arbiter receive parity error

Explanation    Crossbar fabric arbiter reported to Interrupt controller that the data it received had parity error

Recommended Action    Please correct the problem by reloading the board using command 'reload 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-INTCTRL-2-BLG_TX_PAR_ERROR Interrupt controller driver crossbar fabric arbiter transmit parity error

Explanation    Interrupt controller FPGA reported that data it received from crossbar fabric arbiter had parity error

Recommended Action    Please correct the problem by reloading the board using command 'reload 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-INTCTRL-2-CLKCTRL_DACK_ERROR Interrupt controller driver Timing and CPI controller data ack error

Explanation    Interrupt controller driver detected an data ack error from Timing and CPI controller FPGA

Recommended Action    Please try to correct the problem by reloading the board using command 'reload 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-INTCTRL-2-CLKCTRL_RX_PAR_ERROR Interrupt controller driver Timing and CPI controller parity error on receive interface

Explanation    Timing and CPI controller FPGA reported that the data it received had parity error

Recommended Action    Please correct the problem by reloading the board using command 'reload 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-INTCTRL-2-CLKCTRL_TX_PAR_ERROR Interrupt controller driver Timing and CPI controller parity error on transmit interface

Explanation    Interrupt controller FPGA reported that data it received from Timing and CPI controller FPGA had parity error

Recommended Action    Please correct the problem by reloading the board using command 'reload 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-INTCTRL-2-CPU_PRT_A_ERROR Interrupt controller driver cpu address parity error

Explanation    Interrupt controller driver detected an address parity error from the cpu

Recommended Action    Please try to correct the problem by reloading the board using command 'reload 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-INTCTRL-2-CPU_PRT_D_ERROR Interrupt controller driver cpu data parity error

Explanation    Interrupt controller driver detected a data parity error from the cpu

Recommended Action    Please try to correct the problem by reloading the board. 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-INTCTRL-2-DEV_VERSION_ERROR Interrupt controller driver version is not compatible with the hardware version. [chars]

Explanation    Interrupt controller driver version is not compatible with the hardware version.

Recommended Action    Upgrade the Interrupt controller FPGA image using FPD procedure. 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-INTCTRL-2-OCT_RDY_ERROR Interrupt controller driver crossbar fabric interface ready error

Explanation    Interrupt controller driver detected a crossbar fabric interface ready error (ack not received).

Recommended Action    Please correct the problem by reloading the board using command 'reload 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-INTCTRL-2-OCT_RX_PAR_ERROR Interrupt controller driver octopus receive parity error

Explanation    Crossbar fabric interface reported to interrupt controller that the data it received had parity error

Recommended Action    Please correct the problem by reloading the board using command 'reload 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-INTCTRL-2-OCT_TX_PAR_ERROR Interrupt controller driver crossbar fabric interface transmit parity error

Explanation    Interrupt controller FPGA reported that data it received from crossbar fabric interface had parity error

Recommended Action    Please correct the problem by reloading the board using command 'reload 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-INTCTRL-2-PUNT_RDY_ERROR Interrupt controller driver PUNT ready error

Explanation    Interrupt controller driver detected a PUNT ready error (ack not received).

Recommended Action    Please correct the problem by reloading the board using command 'reload 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-INTCTRL-2-PUNT_RX_PAR_ERROR Interrupt controller driver PUNT receive parity error

Explanation    PUNT FPGA reported to Interrupt controller that the data it received had parity error

Recommended Action    Please correct the problem by reloading the board using command 'reload 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-INTCTRL-2-PUNT_TX_PAR_ERROR Interrupt controller driver PUNT transmit parity error

Explanation    Interrupt controller FPGA reported that data it received from crossbar fabric arbiter had parity error

Recommended Action    Please correct the problem by reloading the board using command 'reload 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-INTCTRL-2-THERM_ALARM_ERROR Interrupt controller driver Thermal Alarm

Explanation    Interrupt controller driver detected a thermal error.

Recommended Action    Ensure the fans are working and the board is not overheated. 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-INTCTRL-2-THERM_OVERT_ERROR Interrupt controller driver Thermal Over Temperature

Explanation    Interrupt controller driver detected a thermal over temperature

Recommended Action    Ensure the fans are working & the board is not overheated. 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.

INTEG_SWITCH Messages

Error Message     
 
    
    
   

%PLATFORM-INTEG_SWITCH-2-STACKING_LINK_DOWN Broadcom 5690 stacking link down

Explanation    The driver was unable to successfully initialise the stacking link

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

INV_AGENT Messages

Error Message     
 
    
    
   

%PLATFORM-INV_AGENT-3-ERROR_EXIT Exiting because [chars], error code [chars]

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

Recommended Action    Debug message only. No action is required.

Error Message     
 
    
    
   

%PLATFORM-INV_AGENT-3-OPT_FAIL Failed to [chars], error code [chars]

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

Recommended Action    Debug message only. No action is required.

Error Message     
 
    
    
   

%PLATFORM-INV_AGENT-6-IF_OIRIN SFP/XFP OIR: [chars] port_num: [dec] is inserted, state: [dec]

Explanation    SFP or XFP enity is inserted into the line card inv_agent collects the port data whenever it is presented.

Recommended Action    Debug message only. No action is required.

Error Message     
 
    
    
   

%PLATFORM-INV_AGENT-6-IF_OIROUT SFP/XFP OIR: [chars] port_num: [dec] is removed, state: [dec]

Explanation    SFP or XFP enity is removed from the line card inv_agent removes the port data ehne

Recommended Action    Debug message only. No action is required.

Error Message     
 
    
    
   

%PLATFORM-INV_AGENT-7-INFO [chars]

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

Recommended Action    Debug message only. No action is required.

INV Messages

Error Message     
 
    
    
   

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

Explanation    --

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

Error Message     
 
    
    
   

%PLATFORM-INV-6-CF_OIRIN Compact Flash is inserted on Node: [chars]

Explanation    Compact Flash entity is inserted into the RSP invmgr_agent collects the CF data whenever it is inserted.

Recommended Action    Debug message only. No action is required.

Error Message     
 
    
    
   

%PLATFORM-INV-6-CF_OIROUT Compact Flash is removed on Node: [chars]

Explanation    Compact Flash entity is removed from the RSP invmgr_agent deletes the CF data whenever it is removed.

Recommended Action    Debug message only. No action is required.

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-INV-7-ERR [chars]

Explanation    Failure in Inventory Manager resulting in error condition

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-INV-7-ERR [chars]

Explanation    Failure in Inventory Manager resulting in error condition

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-INV-7-ERR [chars]

Explanation    Failure in Inventory Manager resulting in error condition

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Failure in Inventory Manager dllmain function call

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Failure in Inventory Manager dllmain function call

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Failure in Inventory Manager dllmain function call

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Failure in Inventory Manager event creation

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Failure in Inventory Manager event creation

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Failure in Inventory Manager event creation

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Failure in Inventory Manager event connect open

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Failure in Inventory Manager event connect open

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Failure in Inventory Manager event connect open

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Failure in Inventory Manager memory allocation error occurred

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Failure in Inventory Manager memory allocation error occurred

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Failure in Inventory Manager memory allocation error occurred

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    The RACK entry is a must in inventory management

Recommended Action    None. Inventory Manager process will restart automatically

Error Message     
 
    
    
   

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

Explanation    The RACK entry is a must in inventory management

Recommended Action    None. Inventory Manager process will restart automatically

Error Message     
 
    
    
   

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

Explanation    The RACK entry is a must in inventory management

Recommended Action    None. Inventory Manager process will restart automatically

Error Message     
 
    
    
   

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

Explanation    Sysdb api call failed

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Sysdb api call failed

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Sysdb api call failed

Recommended Action    No action is required.

INVMGR Messages

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

Recommended Action    Check the card/chassis/SPA.

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-INVMGR-5-OIROUT OIR: Node [chars] removed

Explanation    Entity specified in the messages is removed from the chassis.

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

Explanation    The sensor entry will not be added in inventory

Recommended Action    Check the memory on the system

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-INVMGR-7-FAIL [chars]

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

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

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.

LAMPTEST Messages

Error Message     
 
    
    
   

%PLATFORM-LAMPTEST-6-ABORTED Lamp test aborted. [chars]

Explanation    Lamp Test has been aborted due to an internal error.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-LAMPTEST-6-COMPLETE Lamp test is now complete.

Explanation    Test of all system LEDs has now finished.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-LAMPTEST-6-INITIATED Lamp test has been initiated.

Explanation    Test of all system LEDs is now in progress.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-LAMPTEST-6-REJECTED Lamp Test attempt rejected because a lamp test is already in progress.

Explanation    Lamp Test cannot be executed because another lamp test operation is already in progress.

Recommended Action    No action is required.

C_CPUCTRL Messages

Error Message     
 
    
    
   

%PLATFORM-LC_CPUCTRL-0-NO_RSP_ACT_ERROR LC CPU controller driver detected no active RSP in the system

Explanation    LC CPU controller driver detected no active RSP in the system.

Recommended Action    If there are no RSPs present or if both RSPs are undergoing a reload, then this is an expected message. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-LC_CPUCTRL-0-NO_RSP_PRESENT_ERROR LC CPU controller driver has detected no RSP in the system

Explanation    LC is unable to detect any RSPs in the chassis.

Recommended Action    If there indeed is no RSP present in the chassis, then this is an expected message. If RSP is plugged in and powered on, and if this message appears, then contact support team.

Error Message     
 
    
    
   

%PLATFORM-LC_CPUCTRL-2-ACT_ARB_ERROR LC CPU controller driver detected inconsistency in active arbiter signals

Explanation    LC CPU controller driver detected inconsistency between raw and decoded active arbiter signals.

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

Error Message     
 
    
    
   

%PLATFORM-LC_CPUCTRL-2-ACT_RSP_ERROR LC CPU controller driver detected inconsistency in active RSP signal

Explanation    LC CPU controller driver detected inconsistency between raw and decoded active RSP signals.

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

Error Message     
 
    
    
   

%PLATFORM-LC_CPUCTRL-2-BOARD_REV_ERROR LC CPU controller driver detected board revision mismatch

Explanation    LC CPU controller driver version is not compatible with the current Board.

Recommended Action    Reset the board. 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-LC_CPUCTRL-2-BOARD_REV_PAR_ERROR LC CPU controller driver detected board revision parity error

Explanation    LC CPU controller driver detected a board revision parity error.

Recommended Action    Reset the board. 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-LC_CPUCTRL-2-DEV_VERSION_ERROR LC CPU controller driver version is not compatible with the hardware version. [chars]

Explanation    LC CPU controller driver version is not compatable with the hardware version.

Recommended Action    Upgrade the CPU controller FPGA image using FPD procedure followed by reloading of the board using command 'reload 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-LC_CPUCTRL-2-NO_ARB_ACT_ERROR LC CPU controller driver detected no active fabric in the system.

Explanation    LC CPU controller driver detected no active arbiter in the system.

Recommended Action    If there are no RSPs present or if both RSPs are undergoing a reload, then this is an expected message. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-LC_CPUCTRL-2-NO_FAB_ACT_ERROR LC CPU controller driver no active fabric in the system

Explanation    LC CPU controller driver detected no active fabric in the system.

Recommended Action    If there are no RSPs present or if both RSPs are undergoing a reload, then this is an expected message. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-LC_CPUCTRL-2-RSP_PAR_ERROR LC CPU controller driver detected fabric parity from RSP

Explanation    LC CPU controller driver detected fabric parity from RSP.

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

Error Message     
 
    
    
   

%PLATFORM-LC_CPUCTRL-2-TX_RX_PAR_ERROR LC CPU controller driver detected Tx/Rx parity error

Explanation    LC CPU controller driver detected a parity error on Tx/Rx

Recommended Action    Reset the board. 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.

libpcmcia_ide Messages

Error Message     
 
    
    
   

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

Explanation    Probably the flash card has been removed.

Recommended Action    Reinsert the flash card.

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    An internal Event Manager Create operation failed

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

MANSDORF Messages

Error Message     
 
    
    
   

%PLATFORM-MANSDORF-2-CRITICAL_ERROR Error: [chars] [hex]

Explanation    The message is used to report MANSDORF critical errors.

Recommended Action    Contact support.

Error Message     
 
    
    
   

%PLATFORM-MANSDORF-3-GENERIC_ERROR Error: [chars] [hex]

Explanation    The message is used to report MANSDORF generic errors.

Recommended Action    Contact support.

Error Message     
 
    
    
   

%PLATFORM-MANSDORF-6-GENERIC_INFO Info: [chars]

Explanation    The message is used to report MANS generic info.

Recommended Action    Contact support.

MBI_HELLO Messages

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-2-ESERVER_DOWN [chars]

Explanation    The card could not send HB Reply because the EOBC server connection is down.

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

Error Message     
 
    
    
   

%PLATFORM-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-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-HEADLESS_RSP_TIMER_INIT_FAILED [chars]: errno: [chars]

Explanation    The card could not set up its timer to detect the Headless RSP condition.

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

Explanation    Message indicating that the mbi-hello on the card has received a reload notification from sysldr for powering off the card and the card is going to reload soon. Card state is MBI_RUNNING

Recommended Action    Sysldr log needs to be looked into to investigate on the node reload cause. As, sysldr requests to reload the card for various reasons.

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-2-NODE_RELOAD_NOW Node delay time over, reloading now

Explanation    Message indicating that the node has received a reload notification from the sysldr and the node is going to reload as the delay is over. This message is logged after the delay over since the NODE_RELOAD message is logged.

Recommended Action    Sysldr log needs to be looked into to investigate on the node reload cause. As, sysldr requests to reload the card for various reasons.

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-3-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-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-CORRUPTED_HB_REQ_MSG Invalid hb seq number received: [dec]

Explanation    'The HB Req message that was sent has an invalid seq number in 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-MBI_HELLO-3-ERR_SHMEM_ALLOC Failed to allocate shared memory. Error: [chars]

Explanation    mbi-hello is not able to allocate shared memory to share information with other processes.

Recommended Action    This indicates a low memory condition. Memory on the box must be running low - are there services that can be stopped, or can more memory be added?

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-3-ERROR [chars] ([chars])

Explanation    Error in mbi-hello processing The error reason is described in the message log itself.

Recommended Action    NONE

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-3-ETHSERVER_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-ETHSERVER_WRITE The MBI infrastructure was unable to send a message to the Ethernet Server, error: [chars].

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

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

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-3-INIT_ERR [chars] ([chars])

Explanation    Something failed in the initialization. The process will exit as an attempt to recover.

Recommended Action    Collect the traces using the command 'show tech shelf' in admin mode. Notify your customer support representative.

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

Explanation    Failed to request netmgr mountpoint.

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

Error Message     
 
    
    
   

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

Explanation    Failed to request netmgr mountpoint.

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

Explanation    Timer timed out.

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

Error Message     
 
    
    
   

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

Explanation    Timer timed out.

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

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-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-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-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_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-4-SET_THREAD_PRIORITY Unable to set the thread priority to high. Proceeding with normal priority: [chars]

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

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

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-6-LTRACE_INIT_ERR Failed to initialize ltrace buffer in [chars]. Error: [chars]

Explanation    Ltrace buffer will not be available. Debuggability will be reduced because of lacking of ltrace buffer.

Recommended Action    This indicates a low memory condition. Memory on the box must be running low - are there services that can be stopped, or can more memory be added?

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-7-ERR_MEM_ALLOC Failed to allocate [unsigned int] bytes of memory

Explanation    The debug ping to mbi-hello process could not be accomplished because of a low memory condition.

Recommended Action    This indicates a low memory condition. Memory on the box must be running low - are there services that can be stopped, or can more memory be added?

Error Message     
 
    
    
   

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

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

Recommended Action    The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-7-ERR_NETMGR_MOUNTPOINT_REQUEST Failed to request QNX net manager mountpoint

Explanation    Failed to request netmgr mountpoint. The debug ping to mbi-hello process could not be accomplished.

Recommended Action    The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.

Error Message     
 
    
    
   

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

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

Recommended Action    The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-7-INFO_CREATE_SUCCESS MBI-Hello: Successful creation of [chars]. Attempt number [dec]

Explanation    Successful creation of mbi-hello LWM channel for communication.

Recommended Action    NONE

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-7-TIMER_TIMEOUT The MBI infrastructure timer timed out from server : [chars]

Explanation    Timer timed out between the MBI client and server, perhaps because the communications infrastructure is not set up. The MBI operation in progress will not be carried out.

Recommended Action    The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.

Error Message     
 
    
    
   

%PLATFORM-MBI_HELLO-7-WARNING [chars]

Explanation    Error in thread creation for mbi-hello process. The error reason is described in the message log itself.

Recommended Action    NONE

MBI_LIB_ACCESS Messages

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

Recommended Action    The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.

Error Message     
 
    
    
   

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

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

Recommended Action    The debug ping to mbi-hello process, should be retried using lwm_ping on the K-shell of the card.

MBI_LIB Messages

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-MBI_LIB-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.

Error Message     
 
    
    
   

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

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

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

MBIMGR Messages

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-MBIMGR-3-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-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_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-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