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

Platform Messages

Table Of Contents

Platform Messages

AFMON_EA_OOR Messages

AFMON_EA_VERIFY Messages

ALPHA_DISPLAY Messages

ARB Messages

ASM Messages

ASR9k_IFLX Messages

BCM_LOGGER Messages

BCM_SWITCH Messages

BP_SERVER Messages

BPE Messages

BRIDGE Messages

CAIBIST Messages

CANB_SERVER Messages

CARD Messages

CARDMGR Messages

CBC Messages

CCI_SSTAR Messages

CCTL_ENS Messages

CCTL Messages

CE_SWITCH Messages

CEMGBL Messages

CETHHA Messages

CHP Messages

CIH Messages

CLKCTRL_T Messages

CLKCTRL Messages

COMMON Messages

CONCERTO Messages

CPUCTRL_SIP700_DLL Messages

CPUCTRL_SIP700 Messages

CPUCTRL Messages

CPUCTRLLIB Messages

CROSSBAR Messages

DIAGS Messages

DISCOVERY Messages

DMAC Messages

DRP_PAIRING_CLIENT Messages

DRP_PAIRING Messages

DSC Messages

DSCMEDIA Messages

EIO Messages

ENV_AGT_DLL Messages

ENVMON_MON Messages

ENVMON Messages

ETH_SRVR_API Messages

ETH_SRVR Messages

ETHER_CTRL_DLL Messages

ETHER_CTRL Messages

FABARBITER Messages

FABIO Messages

FABMGR Messages

FABRIC_CTRL Messages

FAN Messages

FAULT_MGR_CLIENT Messages

FAULT_MGR_EH Messages

FAULT_MGR Messages

FAULT Messages

FCA Messages

FDIAGS Messages

FFQ Messages

FIB_DBG Messages

FIB_IDB_LIB Messages

FIB_LTRACE Messages

FPD_BURNER Messages

FPGAMGR Messages

FSYNC 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_CS Messages

HFR_PM_SHOW Messages

HFR_PM_TEST Messages

HFR_PM Messages

HFR_SPP Messages

HFR_TUNNEL_EA Messages

HORSE Messages

HPI Messages

hytop Messages

I2C_MASTERSHIP Messages

I2C Messages

I2CCTRL Messages

ILITE Messages

INTCTRL Messages

INTEG_SWITCH Messages

INV_AGENT Messages

INV Messages

INVMGR Messages

IPCP_SRVR Messages

JBI Messages

KD Messages

LAMPTEST Messages

LC_CPIDB Messages

LC_CPPIF Messages

LC_CPUCTRL Messages

LC_FPGA_UPGRADE Messages

LC_PIDB Messages

LC_QFPCPUCTRL Messages

libpcmcia_ide Messages

libpcmcia_linux Messages

LIC_UDI Messages

MACE Messages

MANSDORF Messages

MBI_HELLO Messages

MBI_LIB_ACCESS Messages

MBI_LIB Messages

MBIMGR Messages

MBUS Messages

MCE Messages

MCU Messages

MDIO Messages

MGID_OOR Messages

MLAN Messages

MPC8641 Messages

MSM Messages

NFEA_HW_PROG Messages

NFEA_PAL Messages

NP Messages

NPUXBAR_BRIDGE Messages

OBFL_PD Messages

OBFL Messages

obfl Messages

OBFL Messages

obfl Messages

OBFL Messages

obfl Messages

OBFL Messages

obfl Messages

OBFL Messages

obfl Messages

OIRD Messages

PCIE_CLIENT Messages

PCIE_SWITCH Messages

PCIE Messages

PCIER Messages

PCIMGR Messages

PCMCIA Messages

PCMCIAD Messages

PCTL Messages

PDMA_SPP Messages

PEX Messages

PEX8111 Messages

PEX8508 Messages

PEXRC Messages

PFM Messages

PLAT_FIB_GTRIE 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_L2TP Messages

PLAT_L2FIB_LOCSW Messages

PLAT_L2FIB_LTRACE Messages

PLAT_L2FIB_METRO Messages

PLAT_L2FIB_POGO Messages

PLAT_L2FIB_RP Messages

PLAT_L2FIB_SNOOP Messages

PLAT_L2FIB_VPLS Messages

PLAT_L2FIB Messages

PLAT_L2VPN_DEBUG Messages

PLAT_L2VPN_FGID Messages

PLAT_L2VPN_LTRACE Messages

PLAT_L2VPN Messages

PLAT_THOR_L2FIB_ATOM Messages

PLAT_THOR_L2FIB_DEBUG Messages

PLAT_THOR_L2FIB_LOCSW Messages

PLAT_THOR_L2FIB_LTRACE Messages

PLAT_THOR_L2FIB Messages

PLAT_UDI_MGR Messages

PLAT_V6FIB_RP Messages

PLATFORM_ASR9K_LIB Messages

PLATFORM_HFR_LIB Messages

PLDMGR Messages

PLIM_16P_OC48 Messages

PLIM_IPC Messages

PLIM_SERVICES Messages

PLIM_UPGRADE_FPD Messages

PLU Messages

PLUTLU Messages

PM_OS Messages

PORT_CFG Messages

POWERMGR Messages

preroute Messages

PROCMGR_DLL Messages

PROCMGR Messages

PRP_HW Messages

PRP3_FABIO Messages

PRP3_SLR_FABIO Messages

PSARB Messages

PSARBLC Messages

PUNT_INFRA Messages

PUNT_SWITCH Messages

PUNT Messages

PWR_SUPPLY Messages

PWRMON Messages

QFPCPUBridgeFPGA Messages

QOSHAL Messages

RCCLIB Messages

REDDRV Messages

REEP Messages

ROM_UPGRADE_LIB Messages

ROMMON_BURNER Messages

RSP_CPUCTRL Messages

RWMGR Messages

SATORI Messages

SCC Messages

SCF Messages

SE_P2MP_SRVR Messages

SERDES Messages

SERVICE_AGENT Messages

SFP Messages

SHELFMGR_HAL Messages

SHELFMGR Messages

SHOW_VERSION_CMD Messages

SL Messages

SPA_JBI Messages

SPAN_EA Messages

SPAQFPBridgeCtrl Messages

SPB_I2C Messages

SPENET Messages

SPMCE Messages

SQUID_LOADER Messages

STP_SHIM Messages

SYSLDR_LC Messages

SYSLDR_RP Messages

SYSLDR Messages

TFQ Messages

TIMESYNC_CLIENT Messages

TIMESYNC Messages

TLU Messages

TOPMGR Messages

TSEC Messages

TUNL_GRE_EA_PD Messages

TUNNEL_GRE_EA Messages

UPGRADE_FPD Messages

UPGRADE Messages

USB Messages

VCDMA Messages

VKG_AMCC2035 Messages

VKG_BCM8705 Messages

VKG_CPP_LCPM_SHOW Messages

VKG_CPP_PM_TEST Messages

VKG_CPP_PM Messages

VKG_IP_EA Messages

VKG_IPV4_EA Messages

VKG_IPV6_EA Messages

VKG_LCPM_SHOW Messages

VKG_MPLS_EA Messages

VKG_PM_TEST Messages

VKG_PM Messages

VKG_SERDES Messages

WD_PLATFORM Messages

WDMBI Messages

XBAR Messages

XCVR Messages

XFP Messages

ZL Messages

ZPLL_API Messages


Platform Messages


This section contains all Platform related System Error Messages, such as shelf manager, chassis, env ctrl, and so forth.

AFMON_EA_OOR Messages

Error Message     
 
    
    
   

%PLATFORM-AFMON_EA_OOR-4-NP_FLOWS_OOR_GREEN Performance Traffic Monitoring: Monitored flows on NP [unsigned int] no longer at maximum capacity

Explanation    Performance traffic monitoring has cleared an out-of-resource condition. Performance traffic monitoring process on the linecard has detected that the number of flows being monitored on a NP is no longer at maximum.

Recommended Action    None

Error Message     
 
    
    
   

%PLATFORM-AFMON_EA_OOR-4-NP_FLOWS_OOR_RED Performance Traffic Monitoring: Maximum monitored flows ([unsigned int]) reached on NP [unsigned int]

Explanation    Performance traffic monitoring has encountered an out-of-resource condition. Performance traffic monitoring process on the linecard has detected that the number of flows being monitored on a NP has reached maximum capacity. New flows will no longer be learnt

Recommended Action    Reduce the number of flows being monitored on the NP. This can be done by 1) Modifying ACL: (a) Remove the performance traffic service policy from the interface (b) Modify the ACL used in the service policy to be more specific to match a smaller set of flows to be monitored (c) Reapply the service policy to the interface 2) Moving monitored flows to a different interface on a different NP

AFMON_EA_VERIFY Messages

Error Message     
 
    
    
   

%PLATFORM-AFMON_EA_VERIFY-6-POLICY_ERROR Performance traffic service policy verification failed, error [chars]: [chars]

Explanation    Performance traffic service policy verification encountered the specified error

Recommended Action    Correct the performance traffic service policy

ALPHA_DISPLAY Messages

Error Message     
 
    
    
   

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

Explanation    The alpha display process failed to initialize. The alpha display 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 alpha display' to verify that the process is up and running. If it is still non-operational, try doing try doing 'process restart alpha display' If the message recurs, copy the error message exactly as it appears on 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-7-EVENT_ERROR Event Failure: ([chars])

Explanation    The alpha display process received a bad event. The alpha display 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 alpha display process will handle the failure gracefully but if they continually appear on the console, try doing 'process restart alpha display' If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

ARB Messages

Error Message     
 
    
    
   

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

Explanation    Arbiter driver 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-ARB-3-ERR_MEM_ALLOC Error Allocating [dec] bytes of memory

Explanation    Arbiter driver 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-ARB-5-ERR_CONT Continuing execution: [chars]: Caused by [chars]

Explanation    This message indicates an error occurred beyond which execution of the arbiter 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-ARB-7-ERR_EVM_CREATE Event Manager create failed for [chars]. Reason: [chars]

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

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

Explanation    An error occurred in arbiter 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-ARB-7-ERR_LWM_EVENT_BLOCK LWM Event Manager event block failed. Reason: [chars]

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

Explanation    Arbiter driver 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.

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 initialize 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 that a free queue is empty

Explanation    The assembler component has detected that one of the free queues used to buffer packets coming from the fabric into the route processor is empty.

Recommended Action    The system will most likely recover from this error automatically. No intervention is required. If this error is reported frequently you may want to call your Cisco technical support representative and provide the gathered information. Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

ASR9k_IFLX Messages

Error Message     
 
    
    
   

%PLATFORM-ASR9k_IFLX-5-FRONT_PORT_SHARING_WARNING PLATFORM-IFLX: [chars]

Explanation    Only 10/100M IFLX front port sharing mode is supported. No explicit blocking

Recommended Action    Do not config unsupported IFLX front port sharing mode

BCM_LOGGER Messages

Error Message     
 
    
    
   

%PLATFORM-BCM_LOGGER-6-LOGGING_DEVICE Node: [chars]: [chars] will be used for storing control ethernet logs. Current logs are under [chars] directory and older logs are under [chars] directory.

Explanation    This is an informational message to indicate the location of for es_persist, bcm.log, stp.log and stp_shim.log are.

Recommended Action    Do nothing

Error Message     
 
    
    
   

%PLATFORM-BCM_LOGGER-7-COPY_FAILED Copying of log file to [chars] failed. err equals [dec], status equals [dec]. Restarting to recover.

Explanation    This is an informational message to indicate that copying a log file to the storage device indicated has failed. This could be because the device was being formatted. The process will restart to recover.

Recommended Action    Do nothing

Error Message     
 
    
    
   

%PLATFORM-BCM_LOGGER-7-NO_STORAGE_DEVICE_FOUND Copying of control-ethernet log files to persistent storage is suspended because no persistent storage device (harddisk/PCMCIA disk) found

Explanation    The service that copies /tmp/bcm.log, stp.log, es_persist to persistent storage, did not find any of harddisk, disk0, disk1 available

Recommended Action    See if any of harddisk, disk0, disk1 are accessible on the RP. If they are accessible, restart bcm_logger.

BCM_SWITCH Messages

Error Message     
 
    
    
   

%PLATFORM-BCM_SWITCH-2-LINK_SHUT_DOWN Spanning Tree Port [chars] state changed to ADMIN_DOWN

Explanation    Spanning Tree Port's state change by manual intervention.

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Spanning Tree Port's state change indication.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-BCM_SWITCH-2-MMU_ERR Control Ethernet Intra-rack Switch [dec] detected MMU error

Explanation    The switch encountered a MMU error. MMU errors can affect traffic forwarding in the switch.

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-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-GBP_FULL Control Ethernet Intra-rack Switch [dec] detected Memory full condition

Explanation    The switch encountered a memory full condition. Normally this error is not expected. As per the spec, this situation should fix itself. The ports will drop packets in ingress if the situation persists.

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

BRIDGE Messages

Error Message     
 
    
    
   

%PLATFORM-BRIDGE-1-DDR_BUS_BIT_STUCK_0 DDR bus data bit stuck-0

Explanation    DDR bus data bit stuck on bridge 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-BRIDGE-1-DDR_BUS_BIT_STUCK_1 DDR bus data bit stuck-1

Explanation    DDR bus data bit stuck on bridge 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-BRIDGE-1-DDR_BUS_BIT_STUCK_2 DDR bus data bit stuck-2

Explanation    DDR bus data bit stuck on bridge instance-2.

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-BRIDGE-1-DDR_BUS_BIT_STUCK_3 DDR bus data bit stuck-3

Explanation    DDR bus data bit stuck on bridge instance-3.

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-BRIDGE-1-DDR_LOSS_OF_SYNC_0 DDR interface loss of sync-0

Explanation    Loss of sync on DDR interface on bridge 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-BRIDGE-1-DDR_LOSS_OF_SYNC_1 DDR interface loss of sync-1

Explanation    Loss of sync on DDR interface on bridge 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-BRIDGE-1-DDR_LOSS_OF_SYNC_2 DDR interface loss of sync-2

Explanation    Loss of sync on DDR interface on bridge instance-2.

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-BRIDGE-1-DDR_LOSS_OF_SYNC_3 DDR interface loss of sync-3

Explanation    Loss of sync on DDR interface on bridge instance-3.

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-BRIDGE-1-FIFO_0_OFLOW_FIA2BR_0 FIFO-0 FIA to bridge-0 overflow

Explanation    FIFO-0 FIA to bridge 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-BRIDGE-1-FIFO_0_OFLOW_FIA2BR_1 FIFO-0 FIA to bridge-1 overflow

Explanation    FIFO-0 FIA to bridge 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-BRIDGE-1-FIFO_0_OFLOW_FIA2BR_2 FIFO-0 FIA to bridge-2 overflow

Explanation    FIFO-0 FIA to bridge instance-2 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-BRIDGE-1-FIFO_0_OFLOW_FIA2BR_3 FIFO-0 FIA to bridge-3 overflow

Explanation    FIFO-0 FIA to bridge instance-3 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-BRIDGE-1-FIFO_0_OFLOW_NPU2BR_0 FIFO-0 NPU to bridge-0 overflow

Explanation    FIFO-0 NPU to bridge 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-BRIDGE-1-FIFO_0_OFLOW_NPU2BR_1 FIFO-0 NPU to bridge-1 overflow

Explanation    FIFO-0 NPU to bridge 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-BRIDGE-1-FIFO_0_OFLOW_NPU2BR_2 FIFO-0 NPU to bridge-2 overflow

Explanation    FIFO-0 NPU to bridge instance-2 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-BRIDGE-1-FIFO_0_OFLOW_NPU2BR_3 FIFO-0 NPU to bridge-3 overflow

Explanation    FIFO-0 NPU to bridge instance-3 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-BRIDGE-1-FIFO_1_OFLOW_FIA2BR_0 FIFO-1 FIA to bridge-0 overflow

Explanation    FIFO-1 FIA to bridge 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-BRIDGE-1-FIFO_1_OFLOW_FIA2BR_1 FIFO-1 FIA to bridge-1 overflow

Explanation    FIFO-1 FIA to bridge 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-BRIDGE-1-FIFO_1_OFLOW_FIA2BR_2 FIFO-1 FIA to bridge-2 overflow

Explanation    FIFO-1 FIA to bridge instance-2 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-BRIDGE-1-FIFO_1_OFLOW_FIA2BR_3 FIFO-1 FIA to bridge-3 overflow

Explanation    FIFO-1 FIA to bridge instance-3 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-BRIDGE-1-FIFO_1_OFLOW_NPU2BR_0 FIFO-1 NPU to bridge-0 overflow

Explanation    FIFO-1 NPU to bridge 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-BRIDGE-1-FIFO_1_OFLOW_NPU2BR_1 FIFO-1 NPU to bridge-1 overflow

Explanation    FIFO-1 NPU to bridge 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-BRIDGE-1-FIFO_1_OFLOW_NPU2BR_2 FIFO-1 NPU to bridge-2 overflow

Explanation    FIFO-1 NPU to bridge instance-2 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-BRIDGE-1-FIFO_1_OFLOW_NPU2BR_3 FIFO-1 NPU to bridge-3 overflow

Explanation    FIFO-1 NPU to bridge instance-3 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-BRIDGE-1-MAC_0_TX_FIFO_OFLOW_0 MAC on NPU-0 transmit fifo overflow - 0

Explanation    MAC on NPU-0 had transmit fifo overflow on bridge 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-BRIDGE-1-MAC_0_TX_FIFO_OFLOW_1 MAC on NPU-0 transmit fifo overflow - 1

Explanation    MAC on NPU-0 had transmit fifo overflow on bridge 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-BRIDGE-1-MAC_0_TX_FIFO_OFLOW_2 MAC on NPU-0 transmit fifo overflow - 2

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

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-BRIDGE-1-MAC_0_TX_FIFO_OFLOW_3 MAC on NPU-0 transmit fifo overflow - 3

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

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-BRIDGE-1-MAC_1_TX_FIFO_OFLOW_0 MAC on NPU-1 transmit fifo overflow - 0

Explanation    MAC on NPU-1 had transmit fifo overflow on bridge 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-BRIDGE-1-MAC_1_TX_FIFO_OFLOW_1 MAC on NPU-1 transmit fifo overflow - 1

Explanation    MAC on NPU-1 had transmit fifo overflow on bridge 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-BRIDGE-1-MAC_1_TX_FIFO_OFLOW_2 MAC on NPU-1 transmit fifo overflow - 2

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

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-BRIDGE-1-MAC_1_TX_FIFO_OFLOW_3 MAC on NPU-1 transmit fifo overflow - 3

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

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-BRIDGE-1-NPU_0_EGR_Q_ERR_0 NPU-0 egress queue error - 0

Explanation    Egress queue error on NPU-0 interface on bridge 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-BRIDGE-1-NPU_0_EGR_Q_ERR_1 NPU-0 egress queue error - 1

Explanation    Egress queue error on NPU-0 interface on bridge 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-BRIDGE-1-NPU_0_EGR_Q_ERR_2 NPU-0 egress queue error - 2

Explanation    Egress queue error on NPU-0 interface on bridge instance-2.

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-BRIDGE-1-NPU_0_EGR_Q_ERR_3 NPU-0 egress queue error - 3

Explanation    Egress queue error on NPU-0 interface on bridge instance-3.

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-BRIDGE-1-NPU_0_LOSS_OF_SYNC_0 NPU-0 interface loss of sync-0

Explanation    Loss of sync on NPU-0 interface on bridge 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-BRIDGE-1-NPU_0_LOSS_OF_SYNC_1 NPU-0 interface loss of sync-1

Explanation    Loss of sync on NPU-0 interface on bridge 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-BRIDGE-1-NPU_0_LOSS_OF_SYNC_2 NPU-0 interface loss of sync-2

Explanation    Loss of sync on NPU-0 interface on bridge instance-2.

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-BRIDGE-1-NPU_0_LOSS_OF_SYNC_3 NPU-0 interface loss of sync-3

Explanation    Loss of sync on NPU-0 interface on bridge instance-3.

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-BRIDGE-1-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 bridge 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-BRIDGE-1-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 bridge 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-BRIDGE-1-NPU_0_SCH_MEMP_ERR_2 NPU-0 scheduler mem parity error - 2

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

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-BRIDGE-1-NPU_0_SCH_MEMP_ERR_3 NPU-0 scheduler mem parity error - 3

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

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-BRIDGE-1-NPU_0_XAUI_PLL_LOCK_0 NPU-0 XAUI PLL not locked on bridge - 0

Explanation    NPU-0 XAUI PLL not locked on bridge 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-BRIDGE-1-NPU_0_XAUI_PLL_LOCK_1 NPU-0 XAUI PLL not locked on bridge - 1

Explanation    NPU-0 XAUI PLL not locked on bridge 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-BRIDGE-1-NPU_0_XAUI_PLL_LOCK_2 NPU-0 XAUI PLL not locked on bridge - 2

Explanation    NPU-0 XAUI PLL not locked on bridge instance-2.

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-BRIDGE-1-NPU_0_XAUI_PLL_LOCK_3 NPU-0 XAUI PLL not locked on bridge - 3

Explanation    NPU-0 XAUI PLL not locked on bridge instance-3.

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-BRIDGE-1-NPU_0_XAUI_RDY_0 NPU-0 XAUI not ready on bridge - 0

Explanation    NPU-0 XAUI not ready on bridge 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-BRIDGE-1-NPU_0_XAUI_RDY_1 NPU-0 XAUI not ready on bridge - 1

Explanation    NPU-0 XAUI not ready on bridge 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-BRIDGE-1-NPU_0_XAUI_RDY_2 NPU-0 XAUI not ready on bridge - 2

Explanation    NPU-0 XAUI not ready on bridge instance-2.

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-BRIDGE-1-NPU_0_XAUI_RDY_3 NPU-0 XAUI not ready on bridge - 3

Explanation    NPU-0 XAUI not ready on bridge instance-3.

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-BRIDGE-1-NPU_1_EGR_Q_ERR_0 NPU-1 egress queue error - 0

Explanation    Egress queue error on NPU-1 interface on bridge 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-BRIDGE-1-NPU_1_EGR_Q_ERR_1 NPU-1 egress queue error - 1

Explanation    Egress queue error on NPU-1 interface on bridge 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-BRIDGE-1-NPU_1_EGR_Q_ERR_2 NPU-1 egress queue error - 2

Explanation    Egress queue error on NPU-1 interface on bridge instance-2.

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-BRIDGE-1-NPU_1_EGR_Q_ERR_3 NPU-1 egress queue error - 3

Explanation    Egress queue error on NPU-1 interface on bridge instance-3.

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-BRIDGE-1-NPU_1_LOSS_OF_SYNC_0 NPU-1 interface loss of sync-0

Explanation    Loss of sync on NPU-1 interface on bridge 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-BRIDGE-1-NPU_1_LOSS_OF_SYNC_1 NPU-1 interface loss of sync-1

Explanation    Loss of sync on NPU-1 interface on bridge 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-BRIDGE-1-NPU_1_LOSS_OF_SYNC_2 NPU-1 interface loss of sync-2

Explanation    Loss of sync on NPU-1 interface on bridge instance-2.

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-BRIDGE-1-NPU_1_LOSS_OF_SYNC_3 NPU-1 interface loss of sync-3

Explanation    Loss of sync on NPU-1 interface on bridge instance-3.

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-BRIDGE-1-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 bridge 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-BRIDGE-1-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 bridge 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-BRIDGE-1-NPU_1_SCH_MEMP_ERR_2 NPU-1 scheduler mem parity error - 2

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

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-BRIDGE-1-NPU_1_SCH_MEMP_ERR_3 NPU-1 scheduler mem parity error - 3

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

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-BRIDGE-1-NPU_1_XAUI_PLL_LOCK_0 NPU-1 XAUI PLL not locked on bridge - 0

Explanation    NPU-1 XAUI PLL not locked on bridge 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-BRIDGE-1-NPU_1_XAUI_PLL_LOCK_1 NPU-1 XAUI PLL not locked on bridge - 1

Explanation    NPU-1 XAUI PLL not locked on bridge 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-BRIDGE-1-NPU_1_XAUI_PLL_LOCK_2 NPU-1 XAUI PLL not locked on bridge - 2

Explanation    NPU-1 XAUI PLL not locked on bridge instance-2.

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-BRIDGE-1-NPU_1_XAUI_PLL_LOCK_3 NPU-1 XAUI PLL not locked on bridge - 3

Explanation    NPU-1 XAUI PLL not locked on bridge instance-3.

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-BRIDGE-1-NPU_1_XAUI_RDY_0 NPU-1 XAUI not ready on bridge - 0

Explanation    NPU-1 XAUI not ready on bridge 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-BRIDGE-1-NPU_1_XAUI_RDY_1 NPU-1 XAUI not ready on bridge - 1

Explanation    NPU-1 XAUI not ready on bridge 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-BRIDGE-1-NPU_1_XAUI_RDY_2 NPU-1 XAUI not ready on bridge - 2

Explanation    NPU-1 XAUI not ready on bridge instance-2.

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-BRIDGE-1-NPU_1_XAUI_RDY_3 NPU-1 XAUI not ready on bridge - 3

Explanation    NPU-1 XAUI not ready on bridge instance-3.

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-BRIDGE-1-QDR_DATABIT_STUCK_0 QDR memory data bit stuck-0

Explanation    QDR memory data bit stuck on bridge 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-BRIDGE-1-QDR_DATABIT_STUCK_1 QDR memory data bit stuck-1

Explanation    QDR memory data bit stuck on bridge 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-BRIDGE-1-QDR_DATABIT_STUCK_2 QDR memory data bit stuck-2

Explanation    QDR memory data bit stuck on bridge instance-2.

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-BRIDGE-1-QDR_DATABIT_STUCK_3 QDR memory data bit stuck-3

Explanation    QDR memory data bit stuck on bridge instance-3.

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-BRIDGE-1-QDR_M_FREE_EMPTY_0 Multicast free pages empty - 0

Explanation    Multicast free pages empty on bridge 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-BRIDGE-1-QDR_M_FREE_EMPTY_1 Multicast free pages empty - 1

Explanation    Multicast free pages empty on bridge 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-BRIDGE-1-QDR_M_FREE_EMPTY_2 Multicast free pages empty - 2

Explanation    Multicast free pages empty on bridge instance-2.

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-BRIDGE-1-QDR_M_FREE_EMPTY_3 Multicast free pages empty - 3

Explanation    Multicast free pages empty on bridge instance-3.

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-BRIDGE-1-QDR_MEM_ECC_FAIL_0 QDR memory ECC failure on bridge-0

Explanation    QDR memory ECC failure on bridge instance-0.

Recommended Action    Please reload the board using the command 'reload location '. Please verify the bridge 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-BRIDGE-1-QDR_MEM_ECC_FAIL_1 QDR memory ECC failure on bridge-1

Explanation    QDR memory ECC failure on bridge instance-1.

Recommended Action    Please reload the board using the command 'reload location '. Please verify the bridge 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-BRIDGE-1-QDR_MEM_ECC_FAIL_2 QDR memory ECC failure on bridge-2

Explanation    QDR memory ECC failure on bridge instance-2.

Recommended Action    Please reload the board using the command 'reload location '. Please verify the bridge 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-BRIDGE-1-QDR_MEM_ECC_FAIL_3 QDR memory ECC failure on bridge-3

Explanation    QDR memory ECC failure on bridge instance-3.

Recommended Action    Please reload the board using the command 'reload location '. Please verify the bridge 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-BRIDGE-1-QDR_MEM_SELFTEST_FAIL_0 QDR memory self test failure on bridge-0

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

Recommended Action    Please reload the board using the command 'reload location '. Please verify the bridge 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-BRIDGE-1-QDR_MEM_SELFTEST_FAIL_1 QDR memory self test failure on bridge-1

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

Recommended Action    Please reload the board using the command 'reload location '. Please verify the bridge 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-BRIDGE-1-QDR_MEM_SELFTEST_FAIL_2 QDR memory self test failure on bridge-2

Explanation    QDR memory self test failure on bridge instance-2.

Recommended Action    Please reload the board using the command 'reload location '. Please verify the bridge 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-BRIDGE-1-QDR_MEM_SELFTEST_FAIL_3 QDR memory self test failure on bridge-3

Explanation    QDR memory self test failure on bridge instance-3.

Recommended Action    Please reload the board using the command 'reload location '. Please verify the bridge 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-BRIDGE-1-REG_ACCESS_FAIL_0 Register access failure on bridge-0

Explanation    Register access failure on bridge 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-BRIDGE-1-REG_ACCESS_FAIL_1 Register access failure on bridge-1

Explanation    Register access failure on bridge 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-BRIDGE-1-REG_ACCESS_FAIL_2 Register access failure on bridge-2

Explanation    Register access failure on bridge instance-2.

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-BRIDGE-1-REG_ACCESS_FAIL_3 Register access failure on bridge-3

Explanation    Register access failure on bridge instance-3.

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-BRIDGE-1-STATEMC_0_ERR1_0 State machine-0 error-1 on bridge-0

Explanation    State machine - 0 ran into error-1 on bridge 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-BRIDGE-1-STATEMC_0_ERR1_1 State machine-0 error-1 on bridge-1

Explanation    State machine - 0 ran into error-1 on bridge 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-BRIDGE-1-STATEMC_0_ERR1_2 State machine-0 error-1 on bridge-2

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

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-BRIDGE-1-STATEMC_0_ERR1_3 State machine-0 error-1 on bridge-3

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

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-BRIDGE-1-STATEMC_0_ERR2_0 State machine-0 error-2 on bridge-0

Explanation    State machine - 0 ran into error-2 on bridge 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-BRIDGE-1-STATEMC_0_ERR2_1 State machine-0 error-2 on bridge-1

Explanation    State machine - 0 ran into error-2 on bridge 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-BRIDGE-1-STATEMC_0_ERR2_2 State machine-0 error-2 on bridge-2

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

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-BRIDGE-1-STATEMC_0_ERR2_3 State machine-0 error-2 on bridge-3

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

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-BRIDGE-1-STATEMC_0_ERR3_0 State machine-0 error-3 on bridge-0

Explanation    State machine - 0 ran into error-3 on bridge 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-BRIDGE-1-STATEMC_0_ERR3_1 State machine-0 error-3 on bridge-1

Explanation    State machine - 0 ran into error-3 on bridge 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-BRIDGE-1-STATEMC_0_ERR3_2 State machine-0 error-3 on bridge-2

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

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-BRIDGE-1-STATEMC_0_ERR3_3 State machine-0 error-3 on bridge-3

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

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-BRIDGE-1-STATEMC_1_ERR1_0 State machine-1 error-1 on bridge-0

Explanation    State machine - 1 ran into error-1 on bridge 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-BRIDGE-1-STATEMC_1_ERR1_1 State machine-1 error-1 on bridge-1

Explanation    State machine - 1 ran into error-1 on bridge 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-BRIDGE-1-STATEMC_1_ERR1_2 State machine-1 error-1 on bridge-2

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

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-BRIDGE-1-STATEMC_1_ERR1_3 State machine-1 error-1 on bridge-3

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

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-BRIDGE-1-STATEMC_1_ERR2_0 State machine-1 error-2 on bridge-0

Explanation    State machine - 1 ran into error-2 on bridge 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-BRIDGE-1-STATEMC_1_ERR2_1 State machine-1 error-2 on bridge-1

Explanation    State machine - 1 ran into error-2 on bridge 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-BRIDGE-1-STATEMC_1_ERR2_2 State machine-1 error-2 on bridge-2

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

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-BRIDGE-1-STATEMC_1_ERR2_3 State machine-1 error-2 on bridge-3

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

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-BRIDGE-1-STATEMC_1_ERR3_0 State machine-1 error-3 on bridge-0

Explanation    State machine - 1 ran into error-3 on bridge 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-BRIDGE-1-STATEMC_1_ERR3_1 State machine-1 error-3 on bridge-1

Explanation    State machine - 1 ran into error-3 on bridge 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-BRIDGE-1-STATEMC_1_ERR3_2 State machine-1 error-3 on bridge-2

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

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-BRIDGE-1-STATEMC_1_ERR3_3 State machine-1 error-3 on bridge-3

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

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-BRIDGE-1-XAUI_0_CHAN_SYNC_0 XAUI to NPU-0 chan sync error on bridge-0

Explanation    XAUI to NPU-0 chan sync error on bridge 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-BRIDGE-1-XAUI_0_CHAN_SYNC_1 XAUI to NPU-0 chan sync error on bridge-1

Explanation    XAUI to NPU-0 chan sync error on bridge 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-BRIDGE-1-XAUI_0_CHAN_SYNC_2 XAUI to NPU-0 chan sync error on bridge-2

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

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-BRIDGE-1-XAUI_0_CHAN_SYNC_3 XAUI to NPU-0 chan sync error on bridge-3

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

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-BRIDGE-1-XAUI_0_CHAR_ALIGN_0 XAUI to NPU-0 char alignment error on bridge-0

Explanation    XAUI to NPU-0 char alignment error on bridge 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-BRIDGE-1-XAUI_0_CHAR_ALIGN_1 XAUI to NPU-0 char alignment error on bridge-1

Explanation    XAUI to NPU-0 char alignment error on bridge 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-BRIDGE-1-XAUI_0_CHAR_ALIGN_2 XAUI to NPU-0 char alignment error on bridge-2

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

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-BRIDGE-1-XAUI_0_CHAR_ALIGN_3 XAUI to NPU-0 char alignment error on bridge-3

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

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-BRIDGE-1-XAUI_0_MGT_CV_0 XAUI to NPU-0 MGT code violation on bridge-1

Explanation    XAUI to NPU-0 MGT code violation on bridge 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-BRIDGE-1-XAUI_0_MGT_CV_1 XAUI to NPU-0 MGT code violation on bridge-1

Explanation    XAUI to NPU-0 MGT code violation on bridge 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-BRIDGE-1-XAUI_0_MGT_CV_2 XAUI to NPU-0 MGT code violation on bridge-3

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

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-BRIDGE-1-XAUI_0_MGT_CV_3 XAUI to NPU-0 MGT code violation on bridge-3

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

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-BRIDGE-1-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 bridge 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-BRIDGE-1-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 bridge 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-BRIDGE-1-XAUI_0_RX_ALIGN_LOSS_2 XAUI to NPU-0 Rx alignment loss - 2

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

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-BRIDGE-1-XAUI_0_RX_ALIGN_LOSS_3 XAUI to NPU-0 Rx alignment loss - 3

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

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-BRIDGE-1-XAUI_0_STAT_VEC_0 XAUI to NPU-0 state error on bridge-0

Explanation    XAUI to NPU-0 state error on bridge 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-BRIDGE-1-XAUI_0_STAT_VEC_1 XAUI to NPU-0 state error on bridge-1

Explanation    XAUI to NPU-0 state error on bridge 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-BRIDGE-1-XAUI_0_STAT_VEC_2 XAUI to NPU-0 state error on bridge-2

Explanation    XAUI to NPU-0 state error on bridge instance-2.

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-BRIDGE-1-XAUI_0_STAT_VEC_3 XAUI to NPU-0 state error on bridge-3

Explanation    XAUI to NPU-0 state error on bridge instance-3.

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-BRIDGE-1-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 bridge 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-BRIDGE-1-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 bridge 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-BRIDGE-1-XAUI_0_TX_FIFO_OFLOW_2 XAUI to NPU-0 tx fifo overflow - 2

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

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-BRIDGE-1-XAUI_0_TX_FIFO_OFLOW_3 XAUI to NPU-0 tx fifo overflow - 3

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

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-BRIDGE-1-XAUI_1_CHAN_SYNC_0 XAUI to NPU-1 chan sync error on bridge-0

Explanation    XAUI to NPU-1 chan sync error on bridge 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-BRIDGE-1-XAUI_1_CHAN_SYNC_1 XAUI to NPU-1 chan sync error on bridge-1

Explanation    XAUI to NPU-1 chan sync error on bridge 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-BRIDGE-1-XAUI_1_CHAN_SYNC_2 XAUI to NPU-1 chan sync error on bridge-2

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

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-BRIDGE-1-XAUI_1_CHAN_SYNC_3 XAUI to NPU-1 chan sync error on bridge-3

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

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-BRIDGE-1-XAUI_1_CHAR_ALIGN_0 XAUI to NPU-1 char alignment error on bridge-0

Explanation    XAUI to NPU-1 char alignment error on bridge 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-BRIDGE-1-XAUI_1_CHAR_ALIGN_1 XAUI to NPU-1 char alignment error on bridge-1

Explanation    XAUI to NPU-1 char alignment error on bridge 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-BRIDGE-1-XAUI_1_CHAR_ALIGN_2 XAUI to NPU-1 char alignment error on bridge-2

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

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-BRIDGE-1-XAUI_1_CHAR_ALIGN_3 XAUI to NPU-1 char alignment error on bridge-3

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

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-BRIDGE-1-XAUI_1_MGT_CV_0 XAUI to NPU-1 MGT code violation on bridge-0

Explanation    XAUI to NPU-1 MGT code violation on bridge 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-BRIDGE-1-XAUI_1_MGT_CV_1 XAUI to NPU-1 MGT code violation on bridge-1

Explanation    XAUI to NPU-1 MGT code violation on bridge 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-BRIDGE-1-XAUI_1_MGT_CV_2 XAUI to NPU-1 MGT code violation on bridge-2

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

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-BRIDGE-1-XAUI_1_MGT_CV_3 XAUI to NPU-1 MGT code violation on bridge-3

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

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-BRIDGE-1-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 bridge 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-BRIDGE-1-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 bridge 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-BRIDGE-1-XAUI_1_RX_ALIGN_LOSS_2 XAUI to NPU-1 Rx alignment loss - 2

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

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-BRIDGE-1-XAUI_1_RX_ALIGN_LOSS_3 XAUI to NPU-1 Rx alignment loss - 3

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

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-BRIDGE-1-XAUI_1_STAT_VEC_0 XAUI to NPU-1 state error on bridge-0

Explanation    XAUI to NPU-1 state error on bridge 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-BRIDGE-1-XAUI_1_STAT_VEC_1 XAUI to NPU-1 state error on bridge-1

Explanation    XAUI to NPU-1 state error on bridge 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-BRIDGE-1-XAUI_1_STAT_VEC_2 XAUI to NPU-1 state error on bridge-2

Explanation    XAUI to NPU-1 state error on bridge instance-2.

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-BRIDGE-1-XAUI_1_STAT_VEC_3 XAUI to NPU-1 state error on bridge-3

Explanation    XAUI to NPU-1 state error on bridge instance-3.

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-BRIDGE-1-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 bridge 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-BRIDGE-1-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 bridge 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-BRIDGE-1-XAUI_1_TX_FIFO_OFLOW_2 XAUI to NPU-1 tx fifo overflow - 2

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

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-BRIDGE-1-XAUI_1_TX_FIFO_OFLOW_3 XAUI to NPU-1 tx fifo overflow - 3

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

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-BRIDGE-1-XAUI_A_DATABUS_STUCK_0 XAUI-A databus stuck-0

Explanation    XAUI-A databus stuck on bridge 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-BRIDGE-1-XAUI_A_DATABUS_STUCK_1 XAUI-A databus stuck-1

Explanation    XAUI-A databus stuck on bridge 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-BRIDGE-1-XAUI_A_DATABUS_STUCK_2 XAUI-A databus stuck-2

Explanation    XAUI-A databus stuck on bridge instance-2.

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-BRIDGE-1-XAUI_A_DATABUS_STUCK_3 XAUI-A databus stuck-3

Explanation    XAUI-A databus stuck on bridge instance-3.

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-BRIDGE-2-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 bridge 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-BRIDGE-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 bridge 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-BRIDGE-2-MAC_0_RX_FRAME_ERR_2 MAC on NPU-0 receive frame error - 2

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

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-BRIDGE-2-MAC_0_RX_FRAME_ERR_3 MAC on NPU-0 receive frame error - 3

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

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-BRIDGE-2-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 bridge 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-BRIDGE-2-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 bridge 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-BRIDGE-2-MAC_1_RX_FRAME_ERR_2 MAC on NPU-1 receive frame error - 2

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

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-BRIDGE-2-MAC_1_RX_FRAME_ERR_3 MAC on NPU-1 receive frame error - 3

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

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-BRIDGE-2-MCAST_PAGE_ERR_0 Multicast page error on bridge-0

Explanation    Multicast page error on bridge 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-BRIDGE-2-MCAST_PAGE_ERR_1 Multicast page error on bridge-1

Explanation    Multicast page error on bridge 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-BRIDGE-2-MCAST_PAGE_ERR_2 Multicast page error on bridge-2

Explanation    Multicast page error on bridge instance-2.

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-BRIDGE-2-MCAST_PAGE_ERR_3 Multicast page error on bridge-3

Explanation    Multicast page error on bridge instance-3.

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-BRIDGE-2-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 bridge 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-BRIDGE-2-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 bridge 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-BRIDGE-2-NPU_0_FC_DIP2_ERR_2 NPU-0 egress flow control DIP2 parity error - 2

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

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-BRIDGE-2-NPU_0_FC_DIP2_ERR_3 NPU-0 egress flow control DIP2 parity error - 3

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

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-BRIDGE-2-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 bridge 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-BRIDGE-2-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 bridge 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-BRIDGE-2-NPU_0_FC_OOS_2 NPU-0 egress flow control out-of-sync - 2

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

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-BRIDGE-2-NPU_0_FC_OOS_3 NPU-0 egress flow control out-of-sync - 3

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

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-BRIDGE-2-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 bridge 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-BRIDGE-2-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 bridge 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-BRIDGE-2-NPU_1_FC_DIP2_ERR_2 NPU-1 egress flow control DIP2 parity error - 2

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

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-BRIDGE-2-NPU_1_FC_DIP2_ERR_3 NPU-1 egress flow control DIP2 parity error - 3

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

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-BRIDGE-2-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 bridge 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-BRIDGE-2-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 bridge 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-BRIDGE-2-NPU_1_FC_OOS_2 NPU-1 egress flow control out-of-sync - 2

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

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-BRIDGE-2-NPU_1_FC_OOS_3 NPU-1 egress flow control out-of-sync - 3

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

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-BRIDGE-2-QDR_M_WR_ERR_0 Multicast write when free page fifo empty - 0

Explanation    Multicast write when free page fifo empty on bridge 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-BRIDGE-2-QDR_M_WR_ERR_1 Multicast write when free page fifo empty - 1

Explanation    Multicast write when free page fifo empty on bridge 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-BRIDGE-2-QDR_M_WR_ERR_2 Multicast write when free page fifo empty - 2

Explanation    Multicast write when free page fifo empty on bridge instance-2.

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-BRIDGE-2-QDR_M_WR_ERR_3 Multicast write when free page fifo empty - 3

Explanation    Multicast write when free page fifo empty on bridge instance-3.

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-BRIDGE-3-CHKSUM_ERR_0_FIA_0 Checksum error - 0 from FIA on bridge-0

Explanation    Checksum error - 0 from FIA on bridge 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-BRIDGE-3-CHKSUM_ERR_0_FIA_1 Checksum error - 0 from FIA on bridge-1

Explanation    Checksum error - 0 from FIA on bridge 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-BRIDGE-3-CHKSUM_ERR_0_FIA_2 Checksum error - 0 from FIA on bridge-2

Explanation    Checksum error - 0 from FIA on bridge instance-2.

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-BRIDGE-3-CHKSUM_ERR_0_FIA_3 Checksum error - 0 from FIA on bridge-3

Explanation    Checksum error - 0 from FIA on bridge instance-3.

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-BRIDGE-3-CHKSUM_ERR_1_FIA_0 Checksum error - 1 from FIA on bridge-0

Explanation    Checksum error - 1 from FIA on bridge 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-BRIDGE-3-CHKSUM_ERR_1_FIA_1 Checksum error - 1 from FIA on bridge-1

Explanation    Checksum error - 1 from FIA on bridge 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-BRIDGE-3-CHKSUM_ERR_1_FIA_2 Checksum error - 1 from FIA on bridge-2

Explanation    Checksum error - 1 from FIA on bridge instance-2.

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-BRIDGE-3-CHKSUM_ERR_1_FIA_3 Checksum error - 1 from FIA on bridge-3

Explanation    Checksum error - 1 from FIA on bridge instance-3.

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-BRIDGE-3-CRC_ERR_0_FIA_0 CRC error - 0 from FIA on bridge-0

Explanation    CRC error - 0 from FIA on bridge 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-BRIDGE-3-CRC_ERR_0_FIA_1 CRC error - 0 from FIA on bridge-1

Explanation    CRC error - 0 from FIA on bridge 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-BRIDGE-3-CRC_ERR_0_FIA_2 CRC error - 0 from FIA on bridge-2

Explanation    CRC error - 0 from FIA on bridge instance-2.

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-BRIDGE-3-CRC_ERR_0_FIA_3 CRC error - 0 from FIA on bridge-3

Explanation    CRC error - 0 from FIA on bridge instance-3.

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-BRIDGE-3-CRC_ERR_0_NPU_0 CRC error from NPU-0 on bridge-0

Explanation    CRC error from NPU-0 on bridge 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-BRIDGE-3-CRC_ERR_0_NPU_1 CRC error from NPU-0 on bridge-1

Explanation    CRC error from NPU-0 on bridge 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-BRIDGE-3-CRC_ERR_0_NPU_2 CRC error from NPU-0 on bridge-2

Explanation    CRC error from NPU-0 on bridge instance-2.

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-BRIDGE-3-CRC_ERR_0_NPU_3 CRC error from NPU-0 on bridge-3

Explanation    CRC error from NPU-0 on bridge instance-3.

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-BRIDGE-3-CRC_ERR_1_FIA_0 CRC error - 1 from FIA on bridge-0

Explanation    CRC error - 1 from FIA on bridge 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-BRIDGE-3-CRC_ERR_1_FIA_1 CRC error - 1 from FIA on bridge-1

Explanation    CRC error - 1 from FIA on bridge 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-BRIDGE-3-CRC_ERR_1_FIA_2 CRC error - 1 from FIA on bridge-2

Explanation    CRC error - 1 from FIA on bridge instance-2.

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-BRIDGE-3-CRC_ERR_1_FIA_3 CRC error - 1 from FIA on bridge-3

Explanation    CRC error - 1 from FIA on bridge instance-3.

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-BRIDGE-3-CRC_ERR_1_NPU_0 CRC error from NPU-1 on bridge-0

Explanation    CRC error from NPU-1 on bridge 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-BRIDGE-3-CRC_ERR_1_NPU_1 CRC error from NPU-1 on bridge-1

Explanation    CRC error from NPU-1 on bridge 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-BRIDGE-3-CRC_ERR_1_NPU_2 CRC error from NPU-1 on bridge-2

Explanation    CRC error from NPU-1 on bridge instance-2.

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-BRIDGE-3-CRC_ERR_1_NPU_3 CRC error from NPU-1 on bridge-3

Explanation    CRC error from NPU-1 on bridge instance-3.

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-BRIDGE-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 bridge 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-BRIDGE-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 bridge 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-BRIDGE-3-FIA2NPU_0_PKT_MAXLEN_ERR_2 FIA to NPU-0 packet maximum length error - 2

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

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-BRIDGE-3-FIA2NPU_0_PKT_MAXLEN_ERR_3 FIA to NPU-0 packet maximum length error - 3

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

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-BRIDGE-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 bridge 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-BRIDGE-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 bridge 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-BRIDGE-3-FIA2NPU_0_PKT_MINLEN_ERR_2 FIA to NPU-0 packet minimum length error - 2

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

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-BRIDGE-3-FIA2NPU_0_PKT_MINLEN_ERR_3 FIA to NPU-0 packet minimum length error - 3

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

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-BRIDGE-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 bridge 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-BRIDGE-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 bridge 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-BRIDGE-3-FIA2NPU_1_PKT_MAXLEN_ERR_2 FIA to NPU-1 packet maximum length error - 2

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

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-BRIDGE-3-FIA2NPU_1_PKT_MAXLEN_ERR_3 FIA to NPU-1 packet maximum length error - 3

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

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-BRIDGE-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 bridge 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-BRIDGE-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 bridge 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-BRIDGE-3-FIA2NPU_1_PKT_MINLEN_ERR_2 FIA to NPU-1 packet minimum length error - 2

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

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-BRIDGE-3-FIA2NPU_1_PKT_MINLEN_ERR_3 FIA to NPU-1 packet minimum length error - 3

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

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-BRIDGE-3-MISS_EOP_0_FIADDR_0 Missing EOP-0 from FIA DDR on bridge-0

Explanation    Missing EOP-0 from FIA DDR on bridge 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-BRIDGE-3-MISS_EOP_0_FIADDR_1 Missing EOP-0 from FIA DDR on bridge-1

Explanation    Missing EOP-0 from FIA DDR on bridge 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-BRIDGE-3-MISS_EOP_0_FIADDR_2 Missing EOP-0 from FIA DDR on bridge-2

Explanation    Missing EOP-0 from FIA DDR on bridge instance-2.

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-BRIDGE-3-MISS_EOP_0_FIADDR_3 Missing EOP-0 from FIA DDR on bridge-3

Explanation    Missing EOP-0 from FIA DDR on bridge instance-3.

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-BRIDGE-3-MISS_EOP_0_XAUI_0 Missing EOP-0 from XAUI on bridge-0

Explanation    Missing EOP-0 from XAUI on bridge 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-BRIDGE-3-MISS_EOP_0_XAUI_1 Missing EOP-0 from XAUI on bridge-1

Explanation    Missing EOP-0 from XAUI on bridge 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-BRIDGE-3-MISS_EOP_0_XAUI_2 Missing EOP-0 from XAUI on bridge-2

Explanation    Missing EOP-0 from XAUI on bridge instance-2.

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-BRIDGE-3-MISS_EOP_0_XAUI_3 Missing EOP-0 from XAUI on bridge-3

Explanation    Missing EOP-0 from XAUI on bridge instance-3.

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-BRIDGE-3-MISS_EOP_1_FIADDR_0 Missing EOP-1 from FIA DDR on bridge-0

Explanation    Missing EOP-1 from FIA DDR on bridge 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-BRIDGE-3-MISS_EOP_1_FIADDR_1 Missing EOP-1 from FIA DDR on bridge-1

Explanation    Missing EOP-1 from FIA DDR on bridge 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-BRIDGE-3-MISS_EOP_1_FIADDR_2 Missing EOP-1 from FIA DDR on bridge-2

Explanation    Missing EOP-1 from FIA DDR on bridge instance-2.

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-BRIDGE-3-MISS_EOP_1_FIADDR_3 Missing EOP-1 from FIA DDR on bridge-3

Explanation    Missing EOP-1 from FIA DDR on bridge instance-3.

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-BRIDGE-3-MISS_EOP_1_XAUI_0 Missing EOP-1 from XAUI on bridge-0

Explanation    Missing EOP-1 from XAUI on bridge 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-BRIDGE-3-MISS_EOP_1_XAUI_1 Missing EOP-1 from XAUI on bridge-1

Explanation    Missing EOP-1 from XAUI on bridge 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-BRIDGE-3-MISS_EOP_1_XAUI_2 Missing EOP-1 from XAUI on bridge-2

Explanation    Missing EOP-1 from XAUI on bridge instance-2.

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-BRIDGE-3-MISS_EOP_1_XAUI_3 Missing EOP-1 from XAUI on bridge-3

Explanation    Missing EOP-1 from XAUI on bridge instance-3.

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-BRIDGE-3-NPU_0_CONST_BP_0 NPU-0 constantly backpressuring bridge - 0

Explanation    NPU-0 is constantly backpressuring bridge 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-BRIDGE-3-NPU_0_CONST_BP_1 NPU-0 constantly backpressuring bridge - 1

Explanation    NPU-0 is constantly backpressuring bridge 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-BRIDGE-3-NPU_0_CONST_BP_2 NPU-0 constantly backpressuring bridge - 2

Explanation    NPU-0 is constantly backpressuring bridge instance-2.

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-BRIDGE-3-NPU_0_CONST_BP_3 NPU-0 constantly backpressuring bridge - 3

Explanation    NPU-0 is constantly backpressuring bridge instance-3.

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-BRIDGE-3-NPU_0_PKT_MAXLEN_ERR_0 NPU-0 packet maximum length error - 0

Explanation    Packet maximum length error on NPU-0 interface on bridge 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-BRIDGE-3-NPU_0_PKT_MAXLEN_ERR_1 NPU-0 packet maximum length error - 1

Explanation    Packet maximum length error on NPU-0 interface on bridge 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-BRIDGE-3-NPU_0_PKT_MAXLEN_ERR_2 NPU-0 packet maximum length error - 2

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

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-BRIDGE-3-NPU_0_PKT_MAXLEN_ERR_3 NPU-0 packet maximum length error - 3

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

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-BRIDGE-3-NPU_0_PKT_MINLEN_ERR_0 NPU-0 packet minimum length error - 0

Explanation    Packet minimum length error on NPU-0 interface on bridge 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-BRIDGE-3-NPU_0_PKT_MINLEN_ERR_1 NPU-0 packet minimum length error - 1

Explanation    Packet minimum length error on NPU-0 interface on bridge 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-BRIDGE-3-NPU_0_PKT_MINLEN_ERR_2 NPU-0 packet minimum length error - 2

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

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-BRIDGE-3-NPU_0_PKT_MINLEN_ERR_3 NPU-0 packet minimum length error - 3

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

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-BRIDGE-3-NPU_0_TS_CORE_ERR_0 NPU-0 timestamp core error on bridge - 0

Explanation    NPU-0 timestamp core error on bridge 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-BRIDGE-3-NPU_0_TS_CORE_ERR_1 NPU-0 timestamp core error on bridge - 1

Explanation    NPU-0 timestamp core error on bridge 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-BRIDGE-3-NPU_0_TS_CORE_ERR_2 NPU-0 timestamp core error on bridge - 2

Explanation    NPU-0 timestamp core error on bridge instance-2.

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-BRIDGE-3-NPU_0_TS_CORE_ERR_3 NPU-0 timestamp core error on bridge - 3

Explanation    NPU-0 timestamp core error on bridge instance-3.

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-BRIDGE-3-NPU_1_CONST_BP_0 NPU-1 constantly backpressuring bridge - 0

Explanation    NPU-1 is constantly backpressuring bridge 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-BRIDGE-3-NPU_1_CONST_BP_1 NPU-1 constantly backpressuring bridge - 1

Explanation    NPU-1 is constantly backpressuring bridge 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-BRIDGE-3-NPU_1_CONST_BP_2 NPU-1 constantly backpressuring bridge - 2

Explanation    NPU-1 is constantly backpressuring bridge instance-2.

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-BRIDGE-3-NPU_1_CONST_BP_3 NPU-1 constantly backpressuring bridge - 3

Explanation    NPU-1 is constantly backpressuring bridge instance-3.

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-BRIDGE-3-NPU_1_PKT_MAXLEN_ERR_0 NPU-1 packet maximum length error - 0

Explanation    Packet maximum length error on NPU-1 interface on bridge 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-BRIDGE-3-NPU_1_PKT_MAXLEN_ERR_1 NPU-1 packet maximum length error - 1

Explanation    Packet maximum length error on NPU-1 interface on bridge 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-BRIDGE-3-NPU_1_PKT_MAXLEN_ERR_2 NPU-1 packet maximum length error - 2

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

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-BRIDGE-3-NPU_1_PKT_MAXLEN_ERR_3 NPU-1 packet maximum length error - 3

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

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-BRIDGE-3-NPU_1_PKT_MINLEN_ERR_0 NPU-1 packet minimum length error - 0

Explanation    Packet minimum length error on NPU-1 interface on bridge 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-BRIDGE-3-NPU_1_PKT_MINLEN_ERR_1 NPU-1 packet minimum length error - 1

Explanation    Packet minimum length error on NPU-1 interface on bridge 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-BRIDGE-3-NPU_1_PKT_MINLEN_ERR_2 NPU-1 packet minimum length error - 2

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

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-BRIDGE-3-NPU_1_PKT_MINLEN_ERR_3 NPU-1 packet minimum length error - 3

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

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-BRIDGE-3-NPU_1_TS_CORE_ERR_0 NPU-1 timestamp core error on bridge - 0

Explanation    NPU-1 timestamp core error on bridge 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-BRIDGE-3-NPU_1_TS_CORE_ERR_1 NPU-1 timestamp core error on bridge - 1

Explanation    NPU-1 timestamp core error on bridge 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-BRIDGE-3-NPU_1_TS_CORE_ERR_2 NPU-1 timestamp core error on bridge - 2

Explanation    NPU-1 timestamp core error on bridge instance-2.

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-BRIDGE-3-NPU_1_TS_CORE_ERR_3 NPU-1 timestamp core error on bridge - 3

Explanation    NPU-1 timestamp core error on bridge instance-3.

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-BRIDGE-3-PKT_LEN_ERR_0_FIA_0 Packet length error from FIA for NPU-0 on bridge-0

Explanation    Packet length error from FIA for NPU-0 on bridge 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-BRIDGE-3-PKT_LEN_ERR_0_FIA_1 Packet length error from FIA for NPU-0 on bridge-1

Explanation    Packet length error from FIA for NPU-0 on bridge 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-BRIDGE-3-PKT_LEN_ERR_0_FIA_2 Packet length error from FIA for NPU-0 on bridge-2

Explanation    Packet length error from FIA for NPU-0 on bridge instance-2.

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-BRIDGE-3-PKT_LEN_ERR_0_FIA_3 Packet length error from FIA for NPU-0 on bridge-3

Explanation    Packet length error from FIA for NPU-0 on bridge instance-3.

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-BRIDGE-3-PKT_LEN_ERR_0_XAUI_0 Packet length error - 0 from XAUI on bridge-0

Explanation    Packet length error - 0 from XAUI on bridge 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-BRIDGE-3-PKT_LEN_ERR_0_XAUI_1 Packet length error - 0 from XAUI on bridge-1

Explanation    Packet length error - 0 from XAUI on bridge 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-BRIDGE-3-PKT_LEN_ERR_0_XAUI_2 Packet length error - 0 from XAUI on bridge-2

Explanation    Packet length error - 0 from XAUI on bridge instance-2.

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-BRIDGE-3-PKT_LEN_ERR_0_XAUI_3 Packet length error - 0 from XAUI on bridge-3

Explanation    Packet length error - 0 from XAUI on bridge instance-3.

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-BRIDGE-3-PKT_LEN_ERR_1_FIA_0 Packet length error from FIA for NPU-1 on bridge-0

Explanation    Packet length error from FIA for NPU-1 on bridge 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-BRIDGE-3-PKT_LEN_ERR_1_FIA_1 Packet length error from FIA for NPU-1 on bridge-1

Explanation    Packet length error from FIA for NPU-1 on bridge 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-BRIDGE-3-PKT_LEN_ERR_1_FIA_2 Packet length error from FIA for NPU-1 on bridge-2

Explanation    Packet length error from FIA for NPU-1 on bridge instance-2.

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-BRIDGE-3-PKT_LEN_ERR_1_FIA_3 Packet length error - 1 from FIA on bridge-3

Explanation    Packet length error from FIA for NPU-1 on bridge instance-3.

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-BRIDGE-3-PKT_LEN_ERR_1_XAUI_0 Packet length error - 1 from XAUI on bridge-0

Explanation    Packet length error - 1 from XAUI on bridge 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-BRIDGE-3-PKT_LEN_ERR_1_XAUI_1 Packet length error - 1 from XAUI on bridge-1

Explanation    Packet length error - 1 from XAUI on bridge 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-BRIDGE-3-PKT_LEN_ERR_1_XAUI_2 Packet length error - 1 from XAUI on bridge-2

Explanation    Packet length error - 1 from XAUI on bridge instance-2.

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-BRIDGE-3-PKT_LEN_ERR_1_XAUI_3 Packet length error - 1 from XAUI on bridge-3

Explanation    Packet length error - 1 from XAUI on bridge instance-3.

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-BRIDGE-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 bridge 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-BRIDGE-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 bridge 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-BRIDGE-3-XAUI_0_FRAG_ERR_2 XAUI to NPU-0 fragment error - 2

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

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-BRIDGE-3-XAUI_0_FRAG_ERR_3 XAUI to NPU-0 fragment error - 3

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

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-BRIDGE-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 bridge 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-BRIDGE-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 bridge 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-BRIDGE-3-XAUI_1_FRAG_ERR_2 XAUI to NPU-1 fragment error - 2

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

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-BRIDGE-3-XAUI_1_FRAG_ERR_3 XAUI to NPU-1 fragment error - 3

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

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.

CAIBIST Messages

Error Message     
 
    
    
   

%PLATFORM-CAIBIST-3-ERR_HW_BIST [chars] asic instance [dec] bist block [chars] ch [dec] failed on BIST[[hex]].

Explanation    BIST 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-CAIBIST-3-ERR_HW_BIST_TIMEDOUT [chars] asic instance [dec] bist block [chars] BIST timedout.

Explanation    BIST 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-CAIBIST-3-ERR_SW_INIT [chars].

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

CANB_SERVER Messages

Error Message     
 
    
    
   

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

Explanation    Alarm cleared received from CBC, condition has alleviated.

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 indication received from CBC. This may be a serious failure (example: power sequencer failure), however process may continue functioning as expected (or successfully retry) despite the failure.

Recommended Action    Provide the following CLI: (admin)# show env Use the pid from canb-server output to look for matching pid in the pfm output. If the alarm indication does not clear within 30 minutes, contact TAC.

Error Message     
 
    
    
   

%PLATFORM-CANB_SERVER-3-CRC_ERROR CRC error in Rx message from CBC; msg equals [chars], computed CRC equals [hex], throttled count equals [dec]

Explanation    The message received from Canbus Controller has CRC error computed. This is indicative of a low level serial device transmission error. In most cases, the message is fully recoverable automatically.

Recommended Action    Provide the following CLI output: (admin)# show canb trace loc target nodeid (admin)# show canb server-stats loc all (admin)# show env volt Wait 5 minutes, again give CLI: (admin)# show env volt If the voltage output looks correct, then there is likely no negative impact from the CRC error. If the voltage output looks incorrect, wait 30 minutes and give the CLI command again. If the voltage output still looks incorrect, If this error occurs repetitively for a particular card, contact TAC for further evaluation.

Error Message     
 
    
    
   

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

Explanation    The CAN Bus Server 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. Verify process is up and running, give CLI: If it is still non-operational, use CLI: If it is still non-operational, perform card reload. If still non-operational, contacting TAC and performing RSP switchover is recommended.

Error Message     
 
    
    
   

%PLATFORM-CANB_SERVER-3-MESSAGE_FAILED Unexpected CBC message received from slot [dec] [ver [dec].[dec]] for msg type [dec], id [dec], len [dec]

Explanation    A message was received and did not match any outstanding requests and also is not a standalone message. This is not a critical failure, the process can continue functioning as expected despite the message arrival, message is discarded.

Recommended Action    If this appears once or infrequently, it is not necessary to contact TAC. If it appears continuously or comes and goes repeatedly, it is best to please collect the following details and contact TAC. Provide the following CLI output: (admin)# show canb server-stats loc all (admin)# show canb trace loc target nodeid (admin)# debug canb server error loc target nodeid Let the debug run 2 minutes (admin)# undebug canb server error loc target nodeid (admin)# show canb trace loc target nodeid (admin)# show canb server-stats loc all

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    Provide the following debug: (admin)# show canb server-stats loc all (admin)# show canb trace loc target nodeid (admin)# debug canb server error loc target nodeid Let the debug run for 2 minutes (admin)# undebug canb server error loc target nodeid (admin)# show canb server-stats loc all

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-6-UPGRADE_COMPLETED CBC upgrade completed on [chars]

Explanation    This is an informational message indicating that Canbus Controller firmware upgrade is completed on the specified location.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-CANB_SERVER-6-UPGRADE_IN_PROGRESS CBC upgrade in progress on [chars], Page [dec] of range [dec]-[dec]

Explanation    This is an informational message indicating that Canbus Controller firmware upgrade is in progress on the specified location. The page that is being presently upgraded is mentioned in the message. This page number would be in the specified range, corresponding to the Canbus Controller partition that is being upgraded.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-CANB_SERVER-6-UPGRADE_INFO CBC upgrade on [chars]: [chars]

Explanation    This is an informational message related to the Canbus Controller upgrade process on the specified location.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-CANB_SERVER-6-UPGRADE_STARTED Starting CBC upgrade on [chars] with image [chars]

Explanation    This is an informational message indicating that the Canbus Controller firmware on the specified location is going to be upgraded with the image at the specified path.

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    This is a programmed diagnostic debug message.

Recommended Action    No action 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.

CBC Messages

Error Message     
 
    
    
   

%PLATFORM-CBC-1-CANBUS_A_FAILED CBC A failed

Explanation    CBC detected CANBUS A failure. This may be a serious failure, however the system may continue functioning as expected despite the failure.

Recommended Action    Reboot the LC. If the problem 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-CBC-1-CANBUS_B_FAILED CBC B failed

Explanation    CBC detected CANBUS B failure. This may be a serious failure, however the system may continue functioning as expected despite the failure.

Recommended Action    Reboot the LC. If the problem 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-CBC-1-CANBUS_BOTH_FAILED Canbus A and B have failed

Explanation    CBC detected both CANBUS A and CANBUS B have failed. This may be a serious hardware failure.

Recommended Action    Reboot the LC. If the problem 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-CBC-1-CANBUS_FANTRAY_INRUSH_FAILED CBC inrush fan tray has failed

Explanation    CBC has detected that the inrush fan tray has failed. This will result in the LCs getting overheated. Please turn off power to the system.

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

Error Message     
 
    
    
   

%PLATFORM-CBC-1-CANBUS_PWR_FUSE_FAILED CBC power fuse has failed

Explanation    CBC has detected power fuse failure. The proper functioning of the board requires that the current drawn be within the rating of the boards power fuse.

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

Error Message     
 
    
    
   

%PLATFORM-CBC-1-CANBUS_PWR_SEQ_FAILED CBC power sequence failed

Explanation    The CBC alarm indicating that the power up sequence has failed. The proper functioning of the board requires that a successful application of power be applied to the board in the proper sequence.

Recommended Action    Reboot the LC. If the problem 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-CBC-1-SLOT_ID_CHANGE CBC slot id changed

Explanation    CBC detected unexpected slot id change. The system can no longer manage/monitor the card's environment conditions.

Recommended Action    Reboot the LC. If the problem 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-CBC-1-VERSION_ERROR CBC major version error on node [chars]. Expected equals [dec], Actual equals [dec]

Explanation    The CBC on the slot has an incorrect firmware type programmed. The firmware major version does not match the card type.

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

CCI_SSTAR Messages

Error Message     
 
    
    
   

%PLATFORM-CCI_SSTAR-3-ERR_DRV_INIT CPUCtrl (SSTAR) Initialization failed: [chars]

Explanation    The cpuctrl (sstar) driver detected an error during initialization.

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-CCI_SSTAR-3-ERR_EVM_CREATE Failed to create event manager

Explanation    The Fabric driver was unable to create an event manager for processing messages and hence failed to initialize. The System Manager process (sysmgr) will automatically respawn this (sfe_drvr) 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-CCI_SSTAR-3-ERR_INTERRUPT_THREAD_EXIT [chars] priority interrupt thread failed. Exiting.

Explanation    The cpuctrl (sstar) driver detected a critical failure in the interrupt thread initialization. Abort and exit the thread.

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

CCTL_ENS Messages

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

Recommended Action    Debug message only. No action is required.

CCTL Messages

Error Message     
 
    
    
   

%PLATFORM-CCTL-2-CARD_POWERUP_FAIL Unable to powerup card (for node:[chars]) rc: [chars]

Explanation    The hardware powerup was unsuccessful due to the mentioned reason.

Recommended Action    Card powerup is typically initiated when a card needs to power. If that fails, please collect 'show cctl trace shelfmgr loc ' from the node on which this ios-msg is seen.

Error Message     
 
    
    
   

%PLATFORM-CCTL-2-CARD_SHUTDOWN_FAIL Unable to shutdown card(for node: [chars]) rc: [chars]

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

Recommended Action    Card shutdown is typically initiated when a card needs to be hard reset. If that fails, only a software reset be initiated. Please collect 'show cctl trace shelfmgr loc' from the node on which this ios-msg is seen.

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-CPLD_POWER_ALARM Fabric PLD [chars] interrupt detected instance [dec] Channel [dec] [chars] register: [hex]

Explanation    The Fabric PLD power fault alarm was encountered

Recommended Action    A power fault has occurred. If the fault has occurred, node will be shutdown. Please collect syslog and cctl client debug's from the node on which this ios-msg is seen.

Error Message     
 
    
    
   

%PLATFORM-CCTL-2-RESET_SP_FAIL Unable to reset SP node([chars]) rc: [chars]

Explanation    The hard reset of sp was unsuccessful due to the mentioned reason.

Recommended Action    Reset of SP is typically initiated when that SP needs to be hard reset. If that fails, only a software reset be initiated. Please collect 'show cctl trace shelfmgr loc' from the node on which this ios-msg is seen.

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-TAIKO_POWER_ALARM [chars] Alarm detected on Taiko node([dec]) register: [hex]

Explanation    The taiko power alarm was encountered

Recommended Action    Node will be shutdown immediately as hardware error occurred. Please collect 'show cctl trace error' from the node on which this ios-msg is seen.

Error Message     
 
    
    
   

%PLATFORM-CCTL-2-TAIKO_TEMP_ALARM [chars] Alarm detected on Taiko node([dec]) register: [hex]

Explanation    The taiko temperature alarm was encountered

Recommended Action    Node will be shutdown immediately as hardware error occurred. Please collect 'show cctl trace error' from the node on which this ios-msg is seen.

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-UNKNOWN_CHASSIS_ID Unknown Controller/Platform type [hex] read from EEPROM.

Explanation    The value read from the EEPROM does not match any of the known Controller/platform type values.

Recommended Action    Please check the EEPROM programming. 'show diag eeprom-info' in admin mode gives a raw dump of the EEPROM data. Refer EDCS-137763 to interpret the data to check if the Controller/Platform type is programmed correctly or not. If the Controller/Platform type is incorrect, the unit will have to be RMA'd to reprogram the EEPROM correctly. If the Controller/Platform type is correct, EEPROM read is failed due to unknown reason, Its Recommended to Hard OIR of the card.

Error Message     
 
    
    
   

%PLATFORM-CCTL-4-CPLD_POWER_SEQUENCER_FAULT_OR_ALERT Power Sequencer [inst: [dec] channel: [dec] sensor_type: [chars]] detected alarm [chars] value: [dec] threshold: [dec]

Explanation    The fabric power sequencer detected a temperature or power alarm.

Recommended Action    An alarm was detected. If a critical alarm is detected node will be shutdown. Please collect syslog and cctl client debugs from the node where alarm was detected.

Error Message     
 
    
    
   

%PLATFORM-CCTL-4-CPLD_POWER_WARN Fabric PLD [chars] interrupt detected instance [dec] Channel [dec] [chars] register: [hex]

Explanation    The Fabric PLD power alert was encountered

Recommended Action    A power alert has occurred. If the alert has occurred, node will not be shutdown. Please collect syslog and cctl client debug's from the node on which this ios-msg is seen.

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-OPERATION_SUCCESS [chars]

Explanation    The particular operation mentioned in the message succeeded.

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Informational msg indicating temperature at which alarm occurred.

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

Error Message     
 
    
    
   

%PLATFORM-CCTL-6-TEMP_READ_ERR Invalid temp value read for [chars] sensor.

Explanation    Informational msg indicating invalid temperature read

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.

CE_SWITCH Messages

Error Message     
 
    
    
   

%PLATFORM-CE_SWITCH-2-DEADLINE_MONITOR_FAILED Switch process failed to register with deadline monitor, error [chars]

Explanation    ce-switch process failed to register with deadline monitor

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-CE_SWITCH-2-LINK_SHUT_DOWN Intra-rack switch port [dec] state changed to ADMIN_DOWN

Explanation    The intra-rack switch port was administratively shut down.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-CE_SWITCH-2-STACKING_LINK_DOWN Broadcom switch stacking link down

Explanation    The driver was unable to successfully initialize 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.

CEMGBL Messages

Error Message     
 
    
    
   

%PLATFORM-CEMGBL-5-SFP_OIR Control-ethernet external gigabit sfp [chars] - [chars]

Explanation    The control-eth ext ge sfp state changed

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    An unexpected error condition encountered.

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

CETHHA Messages

Error Message     
 
    
    
   

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

Explanation    Hardware error on CPU control ethernet port.

Recommended Action    Remove/Replace the RP.

Error Message     
 
    
    
   

%PLATFORM-CETHHA-2-PORT_FAULT High rate of errors on control ethernet port [chars]

Explanation    The rate of link errors on the control ethernet port has exceeded the threshold. The link should be fixed to avoid disruption in router services.

Recommended Action    Fix the bad link after switching traffic to redundant link.

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-CETHHA-7-STATS_INFO Statistics: [chars]

Explanation    Packet tx/rx statistics on CPU control ethernet port.

Recommended Action    Remove/Replace the RP.

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.

CIH Messages

Error Message     
 
    
    
   

%PLATFORM-CIH-0-ASIC_ERROR_BOARD_RELOAD [chars][[dec]]: reload board due to too many reset

Explanation    Multiple reset occurred, need to reload board

Recommended Action    Due to too many reset, board has been reloaded to recover *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-0-ASIC_ERROR_RELOAD_SYS [chars][[dec]]: [chars] error has occurred[chars]%s [hex] [chars] [chars]

Explanation    An ASIC error has occurred and need to reload system

Recommended Action    An error has happened and need to reload the system. Collect required information and contact TAC *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-0-ASIC_ERROR_SHUTDOWN_BOARD [chars][[dec]]: [chars] error has occurred[chars]%s [hex] [chars] [chars]

Explanation    An ASIC error has occurred and board need shutdown.

Recommended Action    An error has happened and board is shutdown. Collect required information and contact TAC *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-1-ASIC_ERROR_PERSIST [chars][[dec]]: [chars] error has occurred[chars]%s [hex] [chars] [chars]

Explanation    An ASIC error has occurred and been handled.

Recommended Action    *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-1-ASIC_ERROR_PERSIST_HARD_RESET [chars][[dec]]: [chars] error has occurred[chars]%s [hex] [chars] [chars]

Explanation    An ASIC error has occurred and need a hard reset.

Recommended Action    An error has happen and HARD reset has been performed to recover. Collect required information and contact TAC *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-1-ASIC_ERROR_PERSIST_PON_RESET [chars][[dec]]: [chars] error has occurred[chars]%s [hex] [chars] [chars]

Explanation    An ASIC error has occurred and need a power on reset.

Recommended Action    An error has happen and PON reset has been performed to recover. Collect required information and contact TAC *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-1-ASIC_ERROR_PERSIST_REPROG_RESOURCE [chars][[dec]]: [chars] error has occurred[chars]%s [hex] [chars] [chars]

Explanation    An ASIC error has occurred and need reprogram resource.

Recommended Action    An error that causes reprogram resource has happened and been handled *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-1-ASIC_ERROR_PERSIST_REPROG_RESOURCE_THRESH [chars][[dec]]: [chars] error has occurred[chars]%s [hex] [chars] [chars]

Explanation    ASIC errors need to reprogram resource have happened, such errors has crossed threshold.

Recommended Action    Errors that cause reprogram resource have happened and exceeded threshold. The error condition has been handled. *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-1-ASIC_ERROR_PERSIST_RETRAIN_LINK [chars][[dec]]: [chars] error has occurred[chars]%s [hex] [chars] [chars]

Explanation    An ASIC error has occurred and cause retrain link.

Recommended Action    An error that causes retrain link has happened and been handled *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-1-ASIC_ERROR_PERSIST_SCRUB_THRESH [chars][[dec]]: [chars] error has occurred[chars]%s [hex] [chars] [chars]

Explanation    ASIC errors have occurred and need memory scrubbing, such errors have crossed threshold.

Recommended Action    Errors have been handled. *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-1-ASIC_ERROR_PERSIST_SHUTDOWN_LINK_FABRIC [chars][[dec]]: [chars] error has occurred[chars]%s [hex] [chars] [chars]

Explanation    An ASIC error has occurred and cause fabric link shutdown.

Recommended Action    An error that causes fabric link shutdown has happened and been handled *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-1-ASIC_ERROR_PERSIST_SHUTDOWN_LINK_ILITE [chars][[dec]]: [chars] error has occurred[chars]%s [hex] [chars] [chars]

Explanation    An ASIC error has occurred and cause ilite link shutdown.

Recommended Action    An error that causes ilite link shutdown has happened and been handled *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-1-ASIC_ERROR_PERSIST_SPECIAL_HANDLE [chars][[dec]]: [chars] error has occurred[chars]%s [hex] [chars] [chars]

Explanation    An ASIC error has occurred and been handled.

Recommended Action    *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-1-ASIC_ERROR_PERSIST_SPECIAL_HANDLE_THRESH [chars][[dec]]: [chars] error has occurred[chars]%s [hex] [chars] [chars]

Explanation    ASIC errors have occurred and been handled. Such errors have crossed threshold.

Recommended Action    ASIC errors that need special handling have occurred and exceed the threshold. The error condition has been handled *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-1-ASIC_ERROR_PERSIST_THRESHOLD [chars][[dec]]: [chars] error has occurred[chars]%s [hex] [chars] [chars]

Explanation    An ASIC error threshold was crossed.

Recommended Action    *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-1-ASIC_ERROR_RELOAD_BOARD [chars][[dec]]: [chars] error has occurred[chars]%s [hex] [chars] [chars]

Explanation    An ASIC error has occurred and need to reload board

Recommended Action    An error has happened and board is reloaded. Collect required information and contact TAC *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-1-ASIC_ERROR_REQUEST_RELOAD_BOARD [chars][[dec]]: device is not recovered from fault - and reload is requested.

Explanation    An ASIC error has occurred and cause board reload.

Recommended Action    The output message is warning board reload request. *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-1-ASIC_ERROR_SHUTDOWN_LINK_ILITE [chars][[dec]]: [chars] error has occurred[chars]%s [hex] [chars] [chars]

Explanation    An ASIC error has occurred and cause ilite link shutdown.

Recommended Action    An error that causes ilite link shutdown has happened and been handled *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-2-ASIC_ERROR_HARD_RESET [chars][[dec]]: [chars] error has occurred[chars]%s [hex] [chars] [chars]

Explanation    An ASIC error has occurred and hard reset is needed.

Recommended Action    An error has happened and HARD reset has been performed to recover. Collect required information and contact TAC *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-2-ASIC_ERROR_PON_RESET [chars][[dec]]: [chars] error has occurred[chars]%s [hex] [chars] [chars]

Explanation    An ASIC error has occurred and power on reset is needed

Recommended Action    An error has happen and PON reset has been performed to recover. Collect required information and contact TAC *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-3-ASIC_ERROR_SHUTDOWN_LINK_FABRIC [chars][[dec]]: [chars] error has occurred[chars]%s [hex] [chars] [chars]

Explanation    An ASIC error has occurred and cause fabric link shutdown.

Recommended Action    An error that causes fabric link shutdown has happened and been handled *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-3-ASIC_ERROR_SPECIAL_HANDLE_THRESH [chars][[dec]]: [chars] error has occurred[chars]%s [hex] [chars] [chars]

Explanation    ASIC errors have occurred and been handled. Such error have crossed threshold.

Recommended Action    ASIC errors that need special handling have occurred and exceed the threshold. The error condition has been handled. *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-3-COMMON_ERROR [chars]

Explanation    The CIH library encountered an error related to memory or data value.

Recommended Action    An error would be reported to the client application which should handle this condition appropriately. *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-3-MISS_MEM_INFO Leaf node [chars] do not have mem info

Explanation    Missing mem_info while processing error interrupt.

Recommended Action    Error at the memory location will not be corrected in this case. Need add this information to parser generated file *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-5-ASIC_ERROR [chars][[dec]]: [chars] error has occurred[chars]%s [hex] [chars] [chars]

Explanation    An ASIC error has occurred and been handled.

Recommended Action    *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-5-ASIC_ERROR_ASIC_SCAN ASIC SCAN is needed due to ASIC error [hex] with instance [dec]

Explanation    An ASIC error which requires ASIC SCAN has occurred, the ASIC SCAN will be triggered.

Recommended Action    The linecard will be booted after the ASIC SCAN is completed, save the ASIC SCAN output files on the linecard local disk, provide the files to TAC support for further debugging. *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-5-ASIC_ERROR_HARD_RESET_START [chars][[dec]]: HARD_RESET needed [hex]

Explanation    An ASIC error has occurred and need to hard reset, this marks the beginning of it.

Recommended Action    *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-5-ASIC_ERROR_PON_RESET_START [chars][[dec]]: PON_RESET needed [hex]

Explanation    An ASIC error has occurred and need power on reset, this mark the beginning of it.

Recommended Action    *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-5-ASIC_ERROR_REPROG_RESOURCE_THRESH [chars][[dec]]: [chars] error has occurred[chars]%s [hex] [chars] [chars]

Explanation    An ASIC error has occurred and cause reprogram resource, such error has crossed threshold.

Recommended Action    Errors that cause reprogram resource have happened and exceed threshold. This has been handled. *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-5-ASIC_ERROR_RETRAIN_LINK [chars][[dec]]: [chars] error has occurred[chars]%s [hex] [chars] [chars]

Explanation    An ASIC error has occurred and cause retrain link.

Recommended Action    An error that causes retrain link has happened and been handled *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-5-ASIC_ERROR_SCRUB_THRESH [chars][[dec]]: [chars] error has occurred[chars]%s [hex] [chars] [chars]

Explanation    ASIC errors have occurred and need memory scrubbing, such errors have crossed threshold.

Recommended Action    Errors have been handled. *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-5-ASIC_ERROR_SPECIAL_HANDLE [chars][[dec]]: [chars] error has occurred[chars]%s [hex] [chars] [chars]

Explanation    An ASIC error that need special handling has occurred and been handled.

Recommended Action    *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-5-ASIC_ERROR_THRESHOLD [chars][[dec]]: [chars] error has occurred[chars]%s [hex] [chars] [chars]

Explanation    ASIC errors have exceed the threshold.

Recommended Action    *None*

Error Message     
 
    
    
   

%PLATFORM-CIH-7-ASIC_ERROR_REPROG_RESOURCE [chars][[dec]]: [chars] error has occurred[chars]%s [hex] [chars] [chars]

Explanation    An ASIC error has occurred and need to reprogram resource.

Recommended Action    An error that causes reprogram resource has happened and been handled *None*

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.

CLKCTRL Messages

Error Message     
 
    
    
   

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

Explanation    ClkCtrl 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-CLKCTRL-3-ERR_MEM_ALLOC Error Allocating [dec] bytes of memory

Explanation    ClkCtrl 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-CLKCTRL-3-INVALID_64K_INPUT Invalid signal [chars] for Rx mode [chars] on sync [dec] clock-interface

Explanation    The 64k composite clock signal has been invalidated possibly due to loss-of-signal condition or AMI violations.

Recommended Action    1) Ensure cable connection between the configured interface port and external equipment. 2) Ensure valid 64 kHz + 8 kHz Japanese timing signal (defined in G.703 Appendix II.1) is applied at input port.

Error Message     
 
    
    
   

%PLATFORM-CLKCTRL-3-RX_ALARM_AIS Alarm indication signal condition [chars] for Rx mode [chars] on sync [dec] clock-interface

Explanation    The BITS receiver has detected AIS defect for incoming signal. AIS is usually an unframed all-ones signal. For T1 mode AIS is declared when the BITS receiver detects four or fewer zeroes in a 3 ms period. For E1 mode AIS is declared when the BITS receiver detects fewer than three zeroes in two E1 frames.

Recommended Action    1) Ensure framing format on port matches framing format on the line. 2) Trace and check the source of AIS signal. Possibly an incorrect internal configuration in the service provider equipment, or a failure in their upstream connections.

Error Message     
 
    
    
   

%PLATFORM-CLKCTRL-3-RX_ALARM_FRAME_ERR Frame error rate exceeded condition [chars] for Rx mode [chars] on sync [dec] clock-interface

Explanation    For UTI mode alarm is raised if frame error rate exceeds 2%.

Recommended Action    1) Ensure valid BITS/UTI signal is applied at input port.

Error Message     
 
    
    
   

%PLATFORM-CLKCTRL-3-RX_ALARM_LOF Loss of frame condition [chars] for Rx mode [chars] on sync [dec] clock-interface

Explanation    The BITS receiver has detected OOF defect for incoming signal. For T1 mode OOF is declared when out of every four frame bits two or more frame bits are received in error. For E1 mode OOF is declared when three consecutive incorrect FAS is received. Also for E1 mode (CRC-4 framing) OOF can be declared when 915 or more CRC blocks out of 1000 are received in error. Additionally for E1 mode (CAS signalling) OOF can be declared when two consecutive multiframe alignment words are received in error or, for a period of one multiframe, all bits in timeslot 16 are zero.

Recommended Action    1) Ensure framing format on port matches framing format on the line. 2) Configure to other framing format to check if error clears.

Error Message     
 
    
    
   

%PLATFORM-CLKCTRL-3-RX_ALARM_LOS Loss of signal condition [chars] for Rx mode [chars] on sync [dec] clock-interface

Explanation    For T1 mode LOS is declared (as detected by BITS receiver) when no pulses are detected in a window of 192 consecutive pulse intervals. In E1 and 2048 kHz modes LOS is declared when no pulses are detected in a window of 255 consecutive pulse intervals. For UTI mode, LOS is detected by hardware as per J.211 specifications.

Recommended Action    1) Ensure cable connection between the configured interface port and external equipment. 2) Check the cable integrity and cable connectors. The receive pair should be on pins 1,2 on the RJ-45 jack.

Error Message     
 
    
    
   

%PLATFORM-CLKCTRL-3-RX_ALARM_RAI Remote alarm indication condition [chars] for Rx mode [chars] on sync [dec] clock-interface

Explanation    The BITS receiver has detected RAI defect for incoming signal. Receiving remote alarm indication (RAI) means the far-end equipment over the T1/E1 line has a problem with the signal it is receiving from the upstream equipment.

Recommended Action    Verify input BITS clock signal is set up correctly.

Error Message     
 
    
    
   

%PLATFORM-CLKCTRL-3-TX_ALARM_OC Transmit open circuit condition [chars] for Tx mode [chars] on sync [dec] clock-interface

Explanation    BITS transmitter has detected an open circuit condition.

Recommended Action    Ensure cable connection between the configured interface port and external equipment.

Error Message     
 
    
    
   

%PLATFORM-CLKCTRL-3-TX_ALARM_SC Transmit short circuit condition [chars] for Tx mode [chars] on sync [dec] clock-interface

Explanation    Condition raised by BITS transmitter when internal short-circuit resistance is approximately 25 ohms or less.

Recommended Action    None.

Error Message     
 
    
    
   

%PLATFORM-CLKCTRL-3-TX_ALARM_TAF Incorrect frame alignment condition [chars] for Tx mode [chars] on sync [dec] clock-interface.

Explanation    Condition raised possibly due to incorrect internal BITS transmitter configuration.

Recommended Action    Re-configure and verify if condition is cleared. If the problem 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-CLKCTRL-3-TX_ALARM_TMF Incorrect multi-frame alignment condition [chars] for Tx mode [chars] on sync [dec] clock-interface.

Explanation    Condition raised possibly due to incorrect internal BITS transmitter configuration.

Recommended Action    Re-configure and verify if condition is cleared. If the problem 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-CLKCTRL-3-TX_ALARM_TPDV Transmit pulse density violation condition [chars] for Tx mode [chars] on sync [dec] clock-interface

Explanation    In T1 mode TPDV alarm is raised when the transmit data stream does not meet ANSI T1.403 requirements for transmit pulse density.

Recommended Action    Re-configure and verify if condition is cleared. If the problem 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-CLKCTRL-5-ERR_CONT Continuing execution: [chars]: Caused by [chars]

Explanation    This message indicates an error occurred beyond which execution of the ClkCtrl_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-CLKCTRL-5-PLL_T0_STATE_FREERUN The clock-control T0 PLL (reference clock for all interfaces) is [chars] FREERUN mode.

Explanation    No external reference frequency is available for synchronization, so the T0 PLL output is free-running.

Recommended Action    None. This is just a status indication.

Error Message     
 
    
    
   

%PLATFORM-CLKCTRL-5-PLL_T0_STATE_HOLDOVER The clock-control T0 PLL (reference clock for all interfaces) is [chars] HOLDOVER mode.

Explanation    No external reference frequency is available for synchronization, so the T0 PLL output is in holdover, maintaining the most-recent frequency to which it was locked.

Recommended Action    None. This is just a status indication.

Error Message     
 
    
    
   

%PLATFORM-CLKCTRL-5-PLL_T4_STATE_FREERUN The clock-control T4 PLL (reference clock for Sync 0 and Sync 1 ports) is [chars] FREERUN mode.

Explanation    No external reference frequency is available for synchronization, so the T4 PLL output is free-running.

Recommended Action    None. This is just a status indication.

Error Message     
 
    
    
   

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

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

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

Explanation    An error occurred in ClkCtrl 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-CLKCTRL-7-ERR_LWM_EVENT_BLOCK LWM Event Manager event block failed. Reason: [chars]

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

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

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.

CONCERTO Messages

Error Message     
 
    
    
   

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

Explanation    CONCERTO 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-CONCERTO-3-ERR_MEM_ALLOC Error Allocating [dec] bytes of memory

Explanation    CONCERTO 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-CONCERTO-5-ERR_CONT Continuing execution: [chars]: Caused by [chars]

Explanation    This message indicates an error occurred beyond which execution of the concerto_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-CONCERTO-7-ERR_EVM_CREATE Event Manager create failed for [chars]. Reason: [chars]

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

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

Explanation    An error occurred in CONCERTO 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-CONCERTO-7-ERR_LWM_EVENT_BLOCK LWM Event Manager event block failed. Reason: [chars]

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

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

CPUCTRL_SIP700_DLL Messages

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL_SIP700_DLL-0-INIT_ERROR CPU Control, DLL initialization error, [chars]%s

Explanation    The CPU Control, Dynamic Link Library (DLL) failed to initialize. The effect is that the line card may not function or may not function appropriately. The CPU Control DLL provides low level services to other components on the SIP 700 Line Card (LC). These include, among other things, interrupt services and watch dog time out services. If CPU Control services are not available then those mandatory processes that use these services will exit, respawn and retry the initialization. If these services remain unavailable then the LC will not properly boot and will reset itself. This error is generally indicative of a larger LC-wide problem. %s - description of the specific failure encountered %s - error detail, if appropriate

Recommended Action    This error is unlikely to occur by itself nor is it likely to be the root cause of the problem. Please copy the contents of the system log or as much of the contents of the system log as is possible from around the time that the problem occurred, gather output from the 'show tech-support' command, call your Cisco technical support representative and provide the gathered information to the representative.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL_SIP700_DLL-3-CLEANUP_ERROR CPU Control, DLL cleanup error, [chars]%s

Explanation    The CPU Control, Dynamic Link Library (DLL) failed to cleanup. The effect is relatively minimal and should not be of concern in and of itself. Some minor resource may or may not have been properly returned to a system resource pool. %s - description of the specific failure encountered %s - error detail, if appropriate

Recommended Action    Should this error occur repeatedly within the context of other system errors then copy the contents of the system log or as much of the contents of the system log as is possible from around the time that the problem occurred, gather output from the 'show tech-support' command, call your Cisco technical support representative and provide this information to the representative.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL_SIP700_DLL-3-TRACE_ERROR CPU Control, DLL trace error, [chars]%s

Explanation    The CPU Control, Dynamic Link Library (DLL) failed to initialize the LTrace facility. The effect is that the CPU Control debug trace facility is not functional. This means that trace information used by Cisco support to help isolate CPU Control device issues may not be available. This does not impact normal CPU Control device operations. Note that it is unlikely that this failure would occur by itself. This failure is generally indicative of a larger LC-wide problem. %s - description of the specific failure encountered %s - error detail, if appropriate

Recommended Action    No action is required.

CPUCTRL_SIP700 Messages

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL_SIP700-0-EVT_INIT_ERROR CPU Control driver, event manager setup error, [chars]%s

Explanation    The CPU Control driver failed to initialize the event manager. The effect is that the line card may not function or may not function appropriately. The CPU Control driver provides low level services on the SIP 700 Line Card (LC). These include, among other things, access timeout interrupt services and bus parity error interrupt services. The CPU Control driver relies on an event manager to communicate with other components on the SIP 700 LC. If event manager services are not available then the driver process is exited, respawned and the initialization retried. The CPU Control driver is a mandatory process. If the initialization continues to fail after several retries the LC will not properly boot and will reset itself. This error is generally indicative of a larger LC-wide problem. %s - description of the specific failure encountered %s - error detail, if appropriate

Recommended Action    This error is unlikely to occur by itself nor is it likely to be the root cause of the problem. Please copy the contents of the system log or as much of the contents of the system log as is possible from around the time that the problem occurred, gather output from the 'show tech-support' command, call your Cisco technical support representative and provide the gathered information to the representative.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL_SIP700-0-INIT_ERROR CPU Control driver, main setup error, [chars]%s

Explanation    The CPU Control driver failed to initialize. The effect is that the line card may not function or may not function appropriately. The CPU Control driver provides low level services on the SIP 700 Line Card (LC). These include, among other things, access timeout interrupt services and bus parity error interrupt services. If these services are not available then the driver process is exited, respawned and the initialization retried. The CPU Control driver is a mandatory process. If the initialization continues to fail after several retries the LC will not properly boot and will reset itself. This error is generally indicative of a larger LC-wide problem. %s - description of the specific failure encountered %s - error detail, if appropriate

Recommended Action    This error is unlikely to occur by itself nor is it likely to be the root cause of the problem. Please copy the contents of the system log or as much of the contents of the system log as is possible from around the time that the problem occurred, gather output from the 'show tech-support' command, call your Cisco technical support representative and provide the gathered information to the representative.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL_SIP700-0-INTR_INIT_ERROR CPU Control driver, interrupt setup error, [chars]%s

Explanation    The CPU Control driver failed to initialize interrupt processing. The effect is that the line card may not function or may not function appropriately. The CPU Control driver provides low level services on the SIP 700 Line Card (LC). These include, among other things, access timeout interrupt services and bus parity error interrupt services. If these services are not available then the driver process is exited, respawned and the initialization retried. The CPU Control driver is a mandatory process. If the initialization continues to fail after several retries the LC will not properly boot and will reset itself. This error is generally indicative of a larger LC-wide problem. %s - description of the specific failure encountered %s - error detail, if appropriate

Recommended Action    This error is unlikely to occur by itself nor is it likely to be the root cause of the problem. Please copy the contents of the system log or as much of the contents of the system log as is possible from around the time that the problem occurred, gather output from the 'show tech-support' command, call your Cisco technical support representative and provide the gathered information to the representative.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL_SIP700-3-ASICPP_INIT_ERROR CPU Control driver, ASIC Peek/Poke setup error, continuing

Explanation    The CPU Control driver failed to initialize the ASIC Peek/Poke facility. The effect is that the CPU Control driver debug Peek/Poke facility is not functional. This means that CPU Control Peek/Poke commands used exclusively by Cisco support may not be available. This does not impact normal CPU Control device operations. Note that it is unlikely that this failure would occur by itself. This failure is generally indicative of a larger LC-wide problem.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL_SIP700-3-EDM_INIT_ERROR CPU Control driver, External Data Manager setup error, [chars]%s

Explanation    The CPU Control driver failed to initialize External Data Manager (EDM) processing. The effect is that the CPU Control driver show commands are not functional. This means that display information used by customers and Cisco support to monitor the CPU Control device may not be available. This does not impact normal CPU Control device operations. In particular, this failure would impact the 'show controllers CPUCtrl a9k-sip-700' commands. %s - description of the specific failure encountered %s - error detail, if appropriate

Recommended Action    No action is required. If CPU Control display output is required then the cpu_ctrl process can be restarted on the LC in question. This process restart may or may not result in successful EDM initialization depending upon the underlying problem. Note that it is unlikely that this failure would occur by itself. This failure is generally indicative of a larger LC-wide problem.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL_SIP700-3-TRACE_INIT_ERROR CPU Control driver, trace setup error, continuing

Explanation    The CPU Control driver failed to initialize the LTrace facility. The effect is that the CPU Control driver debug trace facility is not functional. This means that trace information used by Cisco support to help isolate CPU Control device issues may not be available. This does not impact normal CPU Control device operations. Note that it is unlikely that this failure would occur by itself. This failure is generally indicative of a larger LC-wide problem.

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. %s - detail description of which asic can not be found

Recommended Action    Investigate the corresponding ASIC driver

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    reload the board

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. %s - name of ram that error occurred %x - key of error node recorded %s - error data

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-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. %s - name of ram that error occurred %x - key of error node recorded %s - error data

Recommended Action    Ignore the message if appears only once. Otherwise reload the board

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. %s - name of ram that error occurred %x - key of error node recorded %s - error data

Recommended Action    If this happen continuously, reload 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-CPUCTRL-3-DETECTED_TX_PDMA_STALL TX PDMA Ring Stalled, port equals [dec] ([chars]), queue equals [dec] ([chars]), cur_ind equals [dec], tx_ind equals [dec].

Explanation    CPUCTRL TX PDMA ring remained full over non-transient period. Packets which could not be sent were discarded. The downstream ASIC may be stalled. Asic error logged with queue details. %d - port number %s - device name %d - queue number %s - client name %d - current descriptor index %d - current refill descriptor index

Recommended Action    check the asic driver described in the error message for possible stall

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-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-3-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-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. %s - error description %s - error code description

Recommended Action    Restart the process

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    If the message recurs, copy the error message exactly as it appears on 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    If the message recurs, copy the error message exactly as it appears on 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    If the message recurs, copy the error message exactly as it appears on 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    If the message recurs, copy the error message exactly as it appears on 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    If the message recurs, copy the error message exactly as it appears on 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    If the message recurs, copy the error message exactly as it appears on 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    check the gaspp command, verify the address and width are correct

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-PCI_RAM_CORRECTABLE_ERROR_MASK Cpuctrl HW detected SBE in [chars] Mask 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. %s - name of ram that sbe occurred %x - key of error node recorded %s - error data

Recommended Action    Ignore this unless it comes with other error message

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. %s - name of ram that sbe occurred %x - key of error node recorded %s - error data

Recommended Action    Ignore this unless it comes with other error message

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. %s - name of ram that error occurred %x - key of error node recorded %s - error data

Recommended Action    Ignore the message if appears only once. Otherwise reload the board

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. %s - name of ram that error occurred %x - key of error node recorded %s - error data

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-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. %s - name of ram that error occurred %x - key of error node recorded %s - error data

Recommended Action    If this happen continuously, reload 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-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. %s - name of ram that error occurred %x - key of error node recorded %s - error data

Recommended Action    If this happen continuously, reload 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-CPUCTRL-3-PERSISTENT_CRC_LINK_FAILURE Cpuctrl port [dec] link is out of frame 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    If the message recurs, copy the error message exactly as it appears on 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_LWM_EVENT_BLOCK LWM Event Manager event block failed. Reason: [chars]

Explanation    Cpuctrl Event Manager event block error

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

Error Message     
 
    
    
   

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

Explanation    Cpuctrl Sysdb Register EDM error.

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

CPUCTRLLIB Messages

Error Message     
 
    
    
   

%PLATFORM-CPUCTRLLIB-3-DETECTED_CDMA_PORT0 CDMA to port 0 channel equals [dec], queue equals [dec] ([chars]). ASIC address [[hex],[hex]]

Explanation    The cpuctrl driver detected an attempt to DMA to port 0. The request was discarded and not performed. %d - channel number %d - queue number %s - client name %x - address high 32 bit %x - address low 32 bit.

Recommended Action    Investigate the client that attempting the DMA access No action is required.

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-CPUCTRLLIB-3-DETECTED_ERROR_PDMA [chars], [dec], port equals [dec] ([chars]), queue equals [dec] ([chars])

Explanation    The cpuctrl driver detected an error during packet DMA.

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

Error Message     
 
    
    
   

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

Explanation    CDMA ended in error.

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRLLIB-4-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    If the message recurs, copy the error message exactly as it appears on 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] ([chars]) could not clear Link errors during init link_error_reg equals [hex], crc_reg equals [hex]

Explanation    Port will not operate reliably.

Recommended Action    If the message recurs, copy the error message exactly as it appears on 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    If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

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

Explanation    Port will not operate reliably

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

Error Message     
 
    
    
   

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

Explanation    Port will not operate reliably

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

Error Message     
 
    
    
   

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

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

Recommended Action    If the message is displayed continuously for just a short period of time, it is likely a temporary condition that RX PDMA Ring is out of buffer. Use command 'show packet-memory inuse summary' to check which process holding most of the packets and restart the process. If the message recurs, copy the error message exactly as 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-1-IN_MEM_ERROR_LNK0 Crossbar driver input memory error on [chars] link 0

Explanation    Crossbar driver detected a input memory error on link 0

Recommended Action    Copy the error message exactly as it appears on 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-1-IN_MEM_ERROR_LNK1 Crossbar driver input memory error on [chars] link 1

Explanation    Crossbar driver detected a input memory error on link 1

Recommended Action    Copy the error message exactly as it appears on 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-1-OUT_MEM_ERROR_LNK0 Crossbar driver output memory error on [chars] link 0

Explanation    Crossbar driver detected an output memory error on link 0

Recommended Action    Copy the error message exactly as it appears on 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-1-OUT_MEM_ERROR_LNK1 Crossbar driver output memory error on [chars] link 1

Explanation    Crossbar driver detected an output memory error on link 1

Recommended Action    Copy the error message exactly as it appears on 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-1-SERDES_ERROR_LNK0 Crossbar driver serdes error on [chars] link 0

Explanation    Crossbar driver detected a serdes error on link 0.

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-1-SERDES_ERROR_LNK1 Crossbar driver serdes error on [chars] link 1

Explanation    Crossbar driver detected a serdes error on link 1.

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-1-XBAR_TIMEOUT_ERROR_LNK0 Crossbar driver detects crossbar timeout error on [chars] link 0

Explanation    Crossbar driver detected an crossbar timeout error on link 0

Recommended Action    Copy the error message exactly as it appears on 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-1-XBAR_TIMEOUT_ERROR_LNK1 Crossbar driver detects crossbar timeout error on [chars] link 1

Explanation    Crossbar driver detected an crossbar timeout error on link 1

Recommended Action    Copy the error message exactly as 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-0-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-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-FPD_IMG_CORRUPTED FPD image integrity check failed,

Explanation    An FPD image in non-volatile memory is corrupted or missing. Each FPD has 2 images stored in non-volatile memory, one is field upgradable version; the 'B' version. The other is the backup version; the 'A' version. If a B version FPD image has gone bad, it can be recovered by following the recommended_action. If the A version has gone bad, the board must be replaced.

Recommended Action    Use the following command to find out which FPD image is bad/missing: 'show log | inc PFM | inc FPD'; 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-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 ([chars]) 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 ([chars]) 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-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-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-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-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-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 running. Copy the error message exactly as it appears on 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 information 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 running. Copy the error message exactly as it appears on 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    Threshold 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-7-ASMP_ERR_REGS ASIC-ERR: Addr High [hex] Addr Low [hex] Err Attribute [hex], Cause [hex], Command [hex]

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

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Details about the error seen in CPU module.

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Details on the device bus error.

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Information message from Discovery driver on software error condition.

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

Error Message     
 
    
    
   

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

Explanation    Details about the error observed on the PCI bus.

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Details about the ECC error happened 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.

DMAC Messages

Error Message     
 
    
    
   

%PLATFORM-DMAC-2-ECC_ERR Un-recoverable ECC error was detected in DMAC device [dec]

Explanation    The DMAC device encountered an unrecoverable ECC error condition. This would require a reset of the device to recover.

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-DMAC-2-PCI_FATAL_ERR Dmac device [dec] encountered fatal PCIe error : [dec]

Explanation    PCIe interface encountered fatal error.

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-DMAC-2-PCI_LINK_DOWN Dmac device [dec] PCIe link down

Explanation    PCIe interface encountered fatal error.

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-DMAC-2-TEMP_ALARM Temperature alarm on DMAC device [dec]

Explanation    The thermal sensor trip point was crossed on DMAC.

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-DMAC-6-PCI_ERR PCI errors were detected in DMAC device [dec]

Explanation    The DMAC device encountered PCI 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-DMAC-7-LINK_STATUS_CHANGE DMAC dev [dec] link state changed to [chars]

Explanation    The DMAC link state changed.

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-DMAC-7-RX_MISS Packets dropped due to buffer overflow on device [dec]

Explanation    Some packets are dropped due to receive buffer overflow in DMAC device. The CLI above will show which queue dropped the packet. This would in general indicate an unexpected CPU busy condition wherein the software is slow in processing packets.

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.

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.

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-NOT_SUPPORTED DRP pairing is not supported on CRS-4-CH

Explanation    Because CRS-DRP is not supported in CRS 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_CHKPT_APPL_INIT drp_pairing chkpt appl initialization failed: [chars].

Explanation    --

Recommended Action    collect 'admin show pair trace' and 'sh checkpoint ltrace jid drp_pairing Job id all location location of the message'

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 occurred 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 test beds 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 [chars], 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_HB_THRESHOLD Missed [dec] consecutive heartbeats from node [chars]. Please check transport connectivity to node

Explanation    Heartbeats over control-ethernet from the node in question are being missed. This usually indicates a CE transport issue. Please check control ethernet connections to and from the node in question. Note, these messages are expected if node in question is going down due to a user trigger such as OIR, failover

Recommended Action    Check the control ethernet connectivity to the node. (Check if the cables are okay and also if the switch is operating normally).

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-INFO_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-DEBUG_INSTALL_WILL_REBOOT_NODE Install operation - reload in progress

Explanation    dSC process is not reloading node since a reload install operation is in progress. Install will reload node after install complete. Heartbeat loss messages are expected during this time.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-DSC-7-DEBUG_MISSED_HEARTBEAT Missed heartbeat from node [chars]

Explanation    Heartbeats over control-ethernet from the node in question are being missed. Continuous messages usually indicate a CE transport issue. Please check control ethernet connections to and from the node in question

Recommended Action    If continuous messages seen, do the following: Check dsc process state from node in question Check the control ethernet connectivity to the node. (Check if the cables are okay and also if the switch is operating normally).

Error Message     
 
    
    
   

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

Explanation    An internal software error occurred 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 repetitively, it indicates a problem, likely in the active/standby arbitration module. Collect information using 'show redundancy'.

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 encountered 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 node ID. 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 encountered 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. Details of the internal software error is reported as part of the error log.

Recommended Action    Copy the error message exactly as it appears on 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. Details of the internal software error is reported as part of the error log.

Recommended Action    Copy the error message exactly as it appears on 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: file system 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_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_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 communicate 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_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_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.

ENV_AGT_DLL Messages

Error Message     
 
    
    
   

%PLATFORM-ENV_AGT_DLL-3-MSG_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    Provide the following CLI: (admin)# show env trace loc target location Wait 1 or 2 minutes

Error Message     
 
    
    
   

%PLATFORM-ENV_AGT_DLL-3-MSG_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    Provide the following CLI: (admin)# show env trace loc target location Wait 1 or 2 minutes

ENVMON_MON Messages

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 at least 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 temperature.

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 at or over shutdown threshold. Card shutdown commencing.

Recommended Action    Verify the failure, give CLI: (admin)# show env -- particularly temperature and fan output Card is put in IN-RESET state, use CLI: to bring card back into service, or a manual unplug / replug of the card.

Error Message     
 
    
    
   

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

Explanation    Chassis ambient temperature has risen at or over shutdown temperature threshold (STT). Entire chassis shutdown commencing.

Recommended Action    No action, this alarm and functionality is deprecated.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-1-CANTSHUT Environmental Monitor was unable to shutdown slot [dec]: [chars]

Explanation    Envmon attempted to shutdown the specified slot due to severely out-of-range conditions, but was unable to do so. The request to sysldr to shut the card, failed.

Recommended Action    Attempt to resolve the problem, referring to system log or envmon traces the show env all command outputs. If operation permits, remove and insert the card, or power down the entire router. If the problem is not resolved, call your technical support representative for assistance.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-1-ENV_POWER_FAILURE The environmental condition on slot [dec] is because of power failure in [chars]

Explanation    Powershelf failure environmental conditions exist on the specified slot. If left untended, they could result in loss of service or even hardware damage.

Recommended Action    Using the 'show environment power-shelf' command and envmon traces to determine the nature of the failure and take corrective action, including replacement of faulty hardware.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-1-ENV_POWER_FAULT The environmental condition on slot [dec] is because of power fault

Explanation    Powershelf fault environmental conditions exist on the specified slot. If left untended, they could result in loss of service or even hardware damage.

Recommended Action    Using the 'show environment power-shelf' command and other associate system messages, determine the nature of the failure and take corrective action, including replacement of faulty hardware.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-1-FAN_REMOVE Fan blower removed from slot [dec]

Explanation    The fan blower module specified was detected as removed.

Recommended Action    None required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-1-PEM_REMOVE [chars] removed from slot [dec]

Explanation    The power entry module specified was detected as removed.

Recommended Action    None required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-1-SHUTDOWN Environmental Monitor initiated shutdown on slot [dec]

Explanation    An environmental sensor has remained in a dangerous operating range, and sysldr is requested to shutdown card to avoid possible damage.

Recommended Action    Attempt to resolve the problem, referring to system log or evnmon traces the show env command outputs. If operation permits, remove and insert the card, or power down the entire router. If the problem is not resolved, call your technical support representative for assistance.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-1-SPA_CANTSHUT Environmental Monitor was unable to shutdown slot [dec] bay [dec]: [chars]

Explanation    Envmon attempted to shutdown the specified spa due to severely out-of-range conditions, but was unable to do so.

Recommended Action    Attempt to resolve the problem, referring to system log or envmon traces the show env command outputs. If operation permits, remove and insert the spa, or power down the line card having the spa. If the problem is not resolved, call your technical support representative for assistance.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-1-SPA_SHUTDOWN Environmental Monitor initiated shutdown on slot [dec] bay [dec]

Explanation    An environmental sensor on the spa has remained in a critical operating range, and is being shutdown to avoid possible damage.

Recommended Action    Attempt to resolve the problem, referring to system log or envmon traces the show env command outputs. If operation permits, remove and insert the spa, or power down the line card having the spa. If the problem is not resolved, call your technical support representative for assistance.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-ADDITIVE_POWER_OVERBUDGET Power consumption has exceeded additive supply mode limit by [dec]W; results unpredictable

Explanation    The power calculated in use by the chassis exceeds that available by the powershelf. This condition could result in an outage of the chassis if action is not immediately taken.

Recommended Action    Use 'sh power-mgr details' to determine the power details. Remove some linecards to reduce power consumption, or install a higher capacity powershelf to regain power supply redundancy.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-ALL_FANTRAYS_MISSING No fan trays present in the chassis, chassis cooling non-operational

Explanation    There are no fan trays plugged into the chassis, chassis cooling is non-operational, and chassis ambient temperature and card temperatures may rise to over temperature conditions.

Recommended Action    Install one or more fan trays, one fan tray will run at full speed by default, two will run at computed speed based on ambient temperature, give CLI: (admin)# show env -- all sensor output (admin)# show env trace -- to see cards shutdown temperature threshold (STT) values Specifically look at temperature sensors output, can refine the scope of output with (admin)# show env temp. As temperatures rise, over temperature and shutdown conditions may occur.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-ALL_FANTRAYS_MISSING_CLEAR One or more fan trays now plugged in, chassis cooling operational

Explanation    One or more fan trays plugged into the chassis, chassis cooling is now in operation. One fan tray runs at full speed by SW default and provides partial chassis cooling, two fan trays run at computed speed based on ambient temperature.

Recommended Action    Give CLI: (admin)# show env -- all sensor output Specifically look at temperature and fan speed sensors output, fan speeds initially adjust to their computed speed given the ambient temperature and then as ambient temperature drops, the fan speeds continue to adjust downward until reaching steady ambient temperature.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-CARD_OVERTEMP Slot [chars] temperature [dec].[dec]C at or above rising T4 threshold [dec].[dec]C

Explanation    Card hot spot temperature has risen at or over critical threshold.

Recommended Action    Verify the failure, give CLI: (admin)# show env -- particularly temperature and fan output (admin)# show env trace -- to see cards STT values Card can operate in this range but is nearing shutdown temperature threshold (STT).

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-CARD_OVERTEMP_CLEAR Slot [chars] temperature [dec].[dec]C returned below falling T4 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 T3 threshold [dec].[dec]C

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

Recommended Action    Verify the failure, give CLI: (admin)# show env -- particularly temperature and fan output (admin)# show env trace -- to see cards STT values Verify the fan speeds have increased to help bring down the temperature, ambient temperature should decrease with the increased fan RPMs. Chassis can continue to operate in this condition, however cards will shutdown when their hot spot temperature reaches shutdown threshold (STT).

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-CHASSIS_OVERTEMP_CLEAR Chassis ambient temperature [dec].[dec]C returned below falling T3 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 RSP plugged 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 (admin)# show environment command to determine the nature of the failure and take corrective action. If the RSP alarm LED output shows either critical, major, or minor LEDs on, there is one or more outstanding environmental conditions present. Other helpful commands are: show log | in ENV (admin)# show env trace show pfm target node ID. More details at ASR9K debugability wiki.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-ENV_CONDITION An environmental condition on slot [dec] [chars]

Explanation    Two possibilities to this message: 1) One or more environmental conditions exist on the specified slot; 2) All environmental conditions on the specified slot have cleared. If env conditions exist and are left untended, they could result in loss of service or even hardware damage.

Recommended Action    Using the 'show environment all', 'show envmon trace' command and other associate system messages, determine the nature of the failure and take corrective action, including replacement of faulty hardware. No action is required if the env condition is cleared.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-ENV_SLOT_FORCE_CLEAR The environmental condition on slot [dec] has cleared because the slot is no longer monitorable

Explanation    All environmental conditions on the specified slot have cleared due to the fact that the card was either removed from the slot or was powered down.

Recommended Action    None required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-ENV_SPA_FORCE_CLEAR The environmental condition on slot [dec] bay [dec] has cleared because the SPA is no longer monitorable

Explanation    All environmental conditions on the specified spa have cleared due to the fact that the spa was either removed from the card or was shut down.

Recommended Action    None required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-FAN The fan array ([chars]) has reached [chars] level.

Explanation    The fan array specified has reached a warning or critical level and is approaching or approached a condition that is outside the acceptable range.

Recommended Action    Use 'sh env fan' and 'sh env trace' Verify the failure and call your technical support representative for repair or replacement.

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, give CLI: (admin)# show env -- particularly fan output If the fan failure does not alleviate after 30 minutes, give CLI: If the problem persists, call your technical support representative for fan tray repair or replacement.

Error Message     
 
    
    
   

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

Explanation    All fans on indicated fan tray returned RPMs to operating level.

Recommended Action    None required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-FANTRAY_COMM_CLEAR Fan tray communication failure cleared on slot [chars]

Explanation    System SW communication with fan tray re-established.

Recommended Action    None required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-FANTRAY_COMM_FAIL Fan tray communication failure on slot [chars]

Explanation    System SW has lost communication with fan tray. Fan tray LED may not be consistent, (admin)# show env fan may no longer be consistent. Fans do continue to run, just no longer under system SW control.

Recommended Action    Verify the failure, give CLI: (admin)# show env (admin)# show canb server-stats loc all every 5 minutes -- rxPkts and txPkts counters should be increasing If the failure does not alleviate after 30 minutes, give CLI: If the problem persists, call your technical support representative for fan tray repair or replacement.

Error Message     
 
    
    
   

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

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

Recommended Action    Verify the failure, give CLI: (admin)# show env -- particularly fan output If the failure does not alleviate after 30 minutes, give CLI: If the problem persists, call your technical support representative for fan tray 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-POWERSUPPLY_CURRENT [chars] current has reached [chars] level at [dec] A (scan# equals [unsigned int])

Explanation    The current supply specified has reached a critical level and is now out of specification.

Recommended Action    Use 'sh env trace' and 'sh env power' and verify the failure and call your technical support representative for repair or replacement.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-POWERSUPPLY_NONOP [chars] is Non-Operational

Explanation    The power supply specified has become non-operational.

Recommended Action    Use 'sh env power' and 'sh env trace' and verify the failure and call your technical support representative for repair or replacement.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-POWERSUPPLY_VOLTAGE [chars] voltage has reached [chars] level at [dec] V (scan# [unsigned int])

Explanation    The voltage supply specified has reached a critical level and is now out of specification.

Recommended Action    Use 'sh envmon trace', 'sh env all' and verify the failure and call your technical support representative for repair or replacement.

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    Use 'sh power-mgr details' to determine the power details. Remove some linecards to reduce power consumption, or install a higher capacity powershelf to regain power supply redundancy.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-SPA_OVERTEMP_SHUTDOWN slot [dec] bay [dec] temperature [dec].[dec]C [chars] threshold [dec].0C

Explanation    SPA temperature has risen over shutdown threshold. SPA 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-2-TEMP [chars] temperature has reached [chars] level at [dec](C)

Explanation    The temperature sensor specified has reached a critical level and is approaching or approached a condition that is outside the acceptable range.

Recommended Action    Attempt to resolve the temperature problem. Check all unit doors are in place and closed. Use 'sh env fans' and check fans are operating. Remove affected cards, check how hot they are and allow to cool and reinsert. Operation of over-temperature equipment is not recommended due to equipment damage.If problem not resolved by above steps, power unit off and call your technical support representative for assistance.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-VOLT_ALARM_SHUTDOWN Voltage sensor [chars] contains value [dec] which is out side of +-10% valid range. Card will be shutdown!

Explanation    Indicates that a voltage sensor contains value that is out side of expected +-10% range. The card will be shutdown to prevent damage to other components

Recommended Action    Replace the hardware

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-VOLT_ALARM_SHUTDOWN_FAILED Card shutdown through RP failed. rc equals [dec], reason equals [chars]. Initiating self-shutdown

Explanation    Indicates that shelfmgr failed to shutdown the card either because of communication failure or because the shelfmgr rejected the shutdown request

Recommended Action    Check shelfmgr traces

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-VOLTAGE [chars] voltage has reached [chars] level at [dec] mV

Explanation    The voltage supply specified has reached a critical level and is now out of specification.

Recommended Action    Use 'sh envmon trace' and verify the failure, and call your technical support representative for repair or replacement.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-VOLTAGE_SUPPLY_FAILED Voltage [chars] equals [dec] not within thresholds

Explanation    Software periodically reads voltages on fabric cards. If the voltage read is out side of +-10% valid range, this message will be displayed.

Recommended Action    Replace the hardware

Error Message     
 
    
    
   

%PLATFORM-ENVMON-3-ASSUME_OLD_E5 slot:[dec] Cannot determine if E5 [chars] supports 12V rail. Assuming legacy E5 card.

Explanation    The envmon component needs to know the E5's hardware type and power controller firmware version in order to determine if the card supports the new daughterboard 12V SPA voltage rail. However, we could not determine one of these components, and so the software is taking the conservative stance of assuming that the E5 does not support the 12V rail. This error should always be preceded by another envmon E5 related error about the hardware or firmware check failing.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-ENVMON-3-ERR_CARD_UNSUPPORTED Card type [dec] in slot [dec] is not supported by environmental monitoring. The card will not be monitored

Explanation    The card inserted in the specified slot cannot be monitored.

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

Error Message     
 
    
    
   

%PLATFORM-ENVMON-3-ERR_E5_NOSUPPORT Card type [dec] in slot [dec] needs hardware rework and is not supported by environmental monitoring. The card will not be monitored

Explanation    The E5 card inserted in the specified slot cannot be monitored since it needs hardware rework.

Recommended Action    Rework the card.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-3-ERR_MARGIN_MODE_UNKNOWN Unknown margin code [hex]

Explanation    An unknown margin mode was received by the erroring function. Consequently it did not know what to do and has aborted the current action.

Recommended Action    Reattempt the last action, to see if you can proceed. Even if you can proceed, be sure to have a defect logged to resolve the issue.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-3-ERR_SLOT_INVALID [chars]: Invalid slot [dec]

Explanation    Invalid slot number.

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

Error Message     
 
    
    
   

%PLATFORM-ENVMON-3-ERROR_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. Verify process is up and running, give CLI: If it is still non-operational, use CLI: If it is still non-operational, perform RSP switchover or card reload.

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    Check for PEM EEPROM contents using test mbus readpem cmd.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-3-FANTRAY_ALARM Fan tray alarm on slot [chars]

Explanation    One or more fans on indicated fan tray operating below or above 30% of the set RPM. This is not a critical condition. If it is below 30%, the remaining fans in operation on this fan tray run at full speed.

Recommended Action    Verify the failure, give CLI: (admin)# show env -- particularly fan and temperature output If the failure does not alleviate after 30 minutes, give CLI: If the problem persists for 1+ days, call your technical support representative for fan tray repair or replacement.

Error Message     
 
    
    
   

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

Explanation    All fans on indicated fan tray 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    Give CLI: If it is still getting operational failure, perform RSP switchover or card reload.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-3-SLOT_INSERTION_THRESHOLD_B [chars] slot insertion current counter exceeds TB [dec] - [chars]

Explanation    Backplane slot connector has card insertions exceed threshold B per current counter statistics.

Recommended Action    Give CLI: (admin)# show plugin slot counts Service the backplane slot connector, contact Cisco TAC for assistance. If possible, reduce the frequency of card insertions into this backplane connector. Current insertion counters may be cleared with (admin)# clear plugin slot counts

Error Message     
 
    
    
   

%PLATFORM-ENVMON-3-UNEXPECTED_PRP_TYPE Unexpected PRP type [hex] in slot [dec]. Assuming PRP-2

Explanation    The envmon component received an unexpected PRP type.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-ENVMON-3-UNKNOWN_E5_FW slot:[dec] Cannot determine E5 power controller firmware version. errno equals [hex]:[chars]

Explanation    The envmon component could not determine the E5's power controller FW version.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-ENVMON-3-UNKNOWN_E5_HW_TYPE slot:[dec] Cannot determine E5 hardware type.

Explanation    The envmon component could not determine the E5 type.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-ENVMON-3-UNKNOWN_PEM Unknown PEM[dec] of type [chars]%s, chassis type [dec]

Explanation    The envmon component could not determine the type of Power Entry Module. This will result in this PEM reporting as a 0W PEM and the power calculations will be inaccurate.

Recommended Action    Check for PEM EEPROM contents using test mbus readpem cmd.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-3-UNKNOWN_PRP_TYPE Cannot determine PRP type in slot [dec], assuming PRP-2.

Explanation    The envmon component could not determine the PRP type. The envmon component will treat this PRP as if it was a PRP-2. If this is really a PRP-1 then the show environmental voltage command will list two extra sensors: PLIM_V7_HDD_5V and PLIM_V6_1.5V, and these sensors will have incorrect voltage and margin states, because they do not really exist. Moreover, the PRP1's PLIM_V4_1.6V volt sensor will be instead listed as PLIM_V4_1.3V. There is no negative impact to the card.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-ENVMON-4-ALARM [chars] alarm [chars] by [chars]

Explanation    Two possibilities to this message 1) An alarm has occurred. If this is a PEM INPUT1 or INPUT2 failure alarm, then it means that low voltage (40V +/- 1V) or no voltage is present on the input. Due to limitations in the hardware, the 'show environment power' CLI command is inaccurate at that low voltage level and may show 0V and 0A for the readings, even though the input voltage is non-zero. In such a condition, a high amperage may also be present. Please measure the voltage/current on all failed PEMs with an oHm meter before performing any maintenance on the power supplies. 2) A previously occurred alarm has been cleared. If this is 'power shelf circuit breaker error' alarm, there might be an internal wiring failure. The power shelf circuit breaker trip wire might be touching the chassis or ground.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-4-BLWR_LIFECYCLE_RESET Resetting the blower life cycle weekly count for slot [dec] after 5 year of expiry

Explanation    The blower life cycle weekly count is supported for 5 years. After 5 year expiry restart the life cycle count.

Recommended Action    None required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-4-CARD_VOLTAGE_ALARM Voltage sensor alarm slot [chars], sensor [chars] measured [dec] mV and out of operational range [dec] - [dec] mV

Explanation    The card voltage sensor has been monitored below or above it's operational range. If the voltage continues to fall or rise, the HW power sequencer may reset the board.

Recommended Action    Verify the failure, give CLI: (admin)# show env table -- voltage sensor threshold ranges (admin)# show env -- all sensor output Specifically look at voltage sensor values, can refine the output by giving show env volt

Error Message     
 
    
    
   

%PLATFORM-ENVMON-4-CARD_VOLTAGE_ALARM_CLEAR Voltage sensor alarm cleared slot [chars], sensor [chars] measured [dec] mV and returned to operational range

Explanation    The card voltage sensor has returned to operational range.

Recommended Action    None required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-4-CB_OFF_ALARM [chars] alarm [chars] by [chars]

Explanation    Two possibilities to this message 1) An alarm has occurred. 2) A previously occurred alarm has been cleared. power shelf circuit breaker alarm, there might be an internal wiring failure. The power shelf circuit breaker trip wire might be touching the chassis or ground. Or circuit breaker on/off triggered.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-4-OLD_E5_FW slot:[dec] E5 has downrev power controller firmware.

Explanation    The envmon component has detected that the E5 in the specified slot has HW capability to support margining and monitoring of the Daughterboard's 12V SPA rail, but the FW does not. The minimum power controller firmware needed is 0.95.

Recommended Action    Upgrade the E5's power controller firmware.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-4-OP_SFP_WARN Port [dec]: [chars]. Reason: [chars]

Explanation    The particular operation mentioned in the message occurred 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-4-OPERATION_WARN [chars], error code [chars]

Explanation    The particular operation mentioned in the message occurred 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    Give CLI:

Error Message     
 
    
    
   

%PLATFORM-ENVMON-4-OVERTEMP [chars] temperature has reached [chars] level

Explanation    The temperature sensor specified has reached a warning level and is approaching or approached a condition that is outside the acceptable range.

Recommended Action    Attempt to resolve the temperature problem. Check all unit doors are in place and closed. Use 'sh env fans' and check fans are operating. Remove affected cards, check how hot they are and allow to cool and reinsert. Operation of over-temperature equipment is not recommended due to equipment damage. If problem not resolved by above steps, power unit off and call your technical support representative for assistance.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-4-PS_NOT_PRESENT_ALARM [chars] alarm [chars] by [chars]

Explanation    Two possibilities to this message 1) An alarm has occurred. 2) A previously occurred alarm has been cleared. power supply not present.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-4-SLOT_INSERTION_THRESHOLD_A [chars] slot insertion current counter exceeds TA [dec] - [chars]

Explanation    Backplane slot connector has card insertions exceed threshold A per current counter statistics.

Recommended Action    Give CLI: (admin)# show plugin slot counts If possible, reduce the frequency of card insertions into this backplane connector. Current insertion counters may be cleared with (admin)# clear plugin slot counts

Error Message     
 
    
    
   

%PLATFORM-ENVMON-4-SPA_OVERTEMP_MAJOR slot [dec] bay [dec] temperature [dec].[dec]C [chars] threshold [dec].0C

Explanation    SPA temperature is risen above or fallen below major 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-5-ERR_MBUS_EEPROM slot [dec]: Unable to read mbus eeprom contents for PCA

Explanation    For displaying notification of mbus nonresponsiveness to get eeprom contents.

Recommended Action    This indicates that mbus request to get eeprom contents for envmon command has timed out.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-5-SPA_OVERTEMP_MINOR slot [dec] bay [dec] temperature [dec].[dec]C [chars] threshold [dec].0C

Explanation    SPA temperature is risen above or fallen below minor 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-6-ENV_POWER_FAILURE_CLEAR The environmental condition (Power Failure) on slot [dec] is cleared in [chars]

Explanation    Power failure environmental conditions on the specified slot have cleared.

Recommended Action    None required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-6-ENV_POWER_FAULT_CLEAR The environmental condition (Power Fault) on slot [dec] is cleared

Explanation    Power fault environmental conditions on the specified slot have cleared.

Recommended Action    None required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-6-FAN_CLEAR The fan array ([chars]) has returned to a normal level.

Explanation    The fan sensor/array has returned to a level that is within the acceptable range.

Recommended Action    None required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-6-FAN_INSERT Fan blower inserted into slot [dec]

Explanation    The fan blower module specified was detected as inserted.

Recommended Action    None 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-OVERTEMP_CLEAR [chars] temperature has returned to a normal level

Explanation    The temperature sensor specified has returned to a level that is within the acceptable range.

Recommended Action    None required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-6-PEM_INSERT [chars] inserted into slot [dec]

Explanation    The power entry module specified was detected as inserted.

Recommended Action    None required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-6-POWERSUPPLY_CURRENT_CLEAR [chars] current has returned to a normal level at [dec] A (scan# equals [unsigned int])

Explanation    The voltage supply specified has returned to a level that is within the acceptable range.

Recommended Action    None required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-6-POWERSUPPLY_NONOP_CLEAR [chars] has become operational

Explanation    The power supply specified has returned to an operational state.

Recommended Action    None required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-6-POWERSUPPLY_VOLTAGE_CLEAR [chars] voltage has returned to a normal level at [dec] V (scan# equals [unsigned int])

Explanation    The voltage supply specified has returned to a level that is within the acceptable range.

Recommended Action    None required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-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 attempt 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-6-TEMP_CLEAR [chars] temperature has returned to a normal level at [dec](C)

Explanation    The temperature sensor specified has returned to a level that is within the acceptable range.

Recommended Action    None required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-6-VOLTAGE_CLEAR [chars] voltage has returned to a normal level at [dec] mV

Explanation    The voltage supply specified has returned to a level that is within the acceptable range.

Recommended Action    None required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-BAG_DECODE_FAILED Bag decode on [chars] failed. Error: [chars]

Explanation    Could not decode bag

Recommended Action    None

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-CACHE_TOO_SMALL Cache size ([dec]) is to small for sensor id ([dec]) from SPA in slot:[dec] bay:[dec]

Explanation    This is a coding defect caught by sanity checks. The envmon subsystem maintains a short term cache for a SPA's voltage margin values. However, the specified SPA is using sensor ids that are too large for our cache. Consequently we will not be able to store or report the voltage margin value for these offending sensors.

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_ASSERT Assertion failure due to [chars]

Explanation    A fatal internal software error has occurred.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_CHKPT Checkpointing error, [chars] : [chars]

Explanation    Envmon encountered an error in data checkpointing.

Recommended Action    we can use 'run chkpt_cli -p envmon_periodic' to find check pointed data

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_CHKPT_CREATE Could not create checkpoint entry (key [hex]): [chars]

Explanation    Envmon encountered an error in data checkpointing.

Recommended Action    we can use 'run chkpt_cli -p envmon_periodic' to find check pointed data

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_CHKPT_DELETE Could not delete checkpoint entry (objid [hex]): [chars]

Explanation    Envmon encountered an error in data checkpointing.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_CHKPT_ITERATE [chars]: [chars]

Explanation    Envmon encountered an error in data checkpointing.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_CHKPT_RESTORE A corrupted checkpoint was detected: key equals [hex], datakey equals [hex]. Entry deleted.

Explanation    Envmon encountered an error in data checkpointing.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_CHKPT_SAVE Could not save checkpoint entry (key [hex], objid [hex]): [chars]

Explanation    Envmon encountered an error in data checkpointing.

Recommended Action    we can use 'run chkpt_cli -p envmon_periodic' to find check pointed data

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_DEBUG_REG Debug registration failed ([chars]).

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

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

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_DSC_CONNECT Could not contact the dSC: [chars]

Explanation    Environmental monitoring couldn't contact the dSC

Recommended Action    None.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_DSC_GET Could not determine relationship to dSC: [chars]

Explanation    Environmental monitoring couldn't determine if it is running on the dSC or not.

Recommended Action    Check 'sh dsc all' and sh process location of dsc to find envmon process running on dsc or not

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_EDM_INIT Error initializing envmon EDM ([chars]): [chars]

Explanation    An error occurred while setting up the envmon EDM.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_EDM_MISSING Unknown error code [hex]

Explanation    One of the look up routines for the ENV_EDM_ERRS_E enumeration received an unexpected error code. Most likely caused by a new enumerated type being added but the table was not updated, or the look up routines are being passed a value that really isn't a ENV_EDM_ERRS_E value.

Recommended Action    None. This is not so bad. These look up routines are suppose to make it easier to debug envmon problems this really has no customer impact, and is only going to make it more troublesome for engineers.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_EVM_ASYNC_ATTACH Event Manager's event_async_attach function failed. Error: [chars]

Explanation    Could not attach an event_handler to handle async messages.

Recommended Action    None. Environmental Monitoring process will restart automatically

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_EVM_CREATE Event Manager create failed. Error: [chars]

Explanation    The Event Manager could not be created.

Recommended Action    None. Environmental Monitoring process will restart automatically

Error Message     
 
    
    
   

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

Explanation    Miscellaneous software error.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_LWM_RECEIVE LWM Message Receive failed. Error: [chars]

Explanation    The Light-Weight Messaging msg_receive function failed.

Recommended Action    None. Environmental Monitoring process will restart automatically

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_LWM_REPLY LWM Message Reply failed. Error: [chars]

Explanation    The Light-Weight Messaging msg_reply function failed.

Recommended Action    None. Environmental Monitoring process will restart automatically

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_MBUS_CEC [chars]: Error reading mbus cec register [hex] on slot [dec] bay [dec]. Status:[hex], Errno:[hex], ErrStr:'[chars]'

Explanation    An error occurred reading an MBus CEC register.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_MBUS_READREG [chars]: Error reading mbus register [hex] on slot [dec]: [chars]

Explanation    An error occurred reading an MBus register.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_MBUS_RECEIVE [chars]: Error receiving MBus message for slot [dec], type [dec]: [chars]

Explanation    An error occurred reading an MBus register.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_NODEID_CREATE nodeid_create for slot [dec] failed. Error: [chars]

Explanation    Platform function return error on invocation

Recommended Action    Ensure the Platform Library is available.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_PTHREAD [chars]: pthread manipulation error: [chars]

Explanation    A process thread call failed.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_SLOT_EXTRACT [chars] nodeid_extract_fields for nodeid [dec] failed. Error: [chars]

Explanation    Platform function return error on invocation

Recommended Action    Ensure the Platform Library is available.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_SYSDB_BIND SysDB bind to [chars] failed. Error: [chars]

Explanation    Could not bind to SysDB.

Recommended Action    Ensure SysDB is available on the system. check show process sysdb and check show sysdb connection.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_SYSDB_REG_NOTIFY SysDB register for notification on [chars] failed. Error: [chars]

Explanation    Could not register for notification in Sysdb.

Recommended Action    None. Environmental Monitoring process will restart automatically

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_SYSDB_REG_VERIF [chars]:[dec] SysDB register configuration verifiers failed. Error: [chars]

Explanation    Could not register for configuration verification in Sysdb.

Recommended Action    None. Environmental Monitoring process will restart automatically.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_THREAD_CREATE Could not create thread. Error: [chars]

Explanation    A thread could not be created.

Recommended Action    None. Environmental Monitoring process will restart automatically

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_TRAP_SEND Error generating Envmon trap notification [chars]: [chars]

Explanation    An error occurred while generating trap notification to SNMP.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERROR Error, [chars]

Explanation    Envmon encountered an software error.

Recommended Action    check envmon traces for respective error msg.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-EVENT_BLOCK_FAILED Event Manager could not block. Error: [chars]

Explanation    Could not block on receiving events from sysdb via event manager

Recommended Action    None. Environmental Monitoring process will restart automatically

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-NOT_ON_DSC Environmental monitoring will only run on the dSC

Explanation    Environmental monitoring only runs on the dSC

Recommended Action    None.

Error Message     
 
    
    
   

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

Explanation    This is a programmed diagnostic debug.

Recommended Action    No action required.

Error Message     
 
    
    
   

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

Explanation    This is a programmed diagnostic debug.

Recommended Action    No action required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-SYSMGR_PROC_READY_FAILED System Manager's process ready failed. Error: [chars]

Explanation    A sysmgr process ready API failed.

Recommended Action    None.

ETH_SRVR_API Messages

Error Message     
 
    
    
   

%PLATFORM-ETH_SRVR_API-3-ERR_ORPHAN_COUNT eth_server_retrieve_clean: client[[dec]]: orphan_count mismatch on RX, bfm_rx_hdl[[hex]] oc[[dec]] loc[[dec]]

Explanation    A partial retrieval of buffers happened for the current process that restarted due to retrieved orphan_count less than actual orphan_count.

Recommended Action    '*SH_CMD show tech-support control ethernet fast location node, on node that print this message, collect dumpcore running of process that print this message, eth_server and bfm-server'

Error Message     
 
    
    
   

%PLATFORM-ETH_SRVR_API-5-NOTICE_SKIP_BUFF eth_server api free: non-fatal in_use[0] case ignoring, src client[[dec]] dst client[[dec]] mem_score[[dec]]

Explanation    A double-free condition has been avoided

Recommended Action    '*SH_CMD show tech-support control ethernet fast location node, on node that print this message, collect dumpcore running of process that print this message, eth_server and bfm-server'

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. Ethernet 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. Ethernet 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-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-PCDS_ERR [chars], pcds at 0x[pointer] value equals [hex]

Explanation    An error occurred inside PCDS data structure. Process continues to run but PCDS data may not be logged properly

Recommended Action    'Copy the error message exactly as it appears on the console or in the system log. Issue the show tech-support control ethernet fast location node, dumpcore running eth_server 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 tech-support control ethernet fast location node, dumpcore running eth_server 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-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    A runtime failure occurred in Ether-ctrl process. Typically, this is an internal error. The message string indicates the reason for the failure. This message also provides an error code. The process can continue functioning as expected despite the failure.

Recommended Action    Collect console log and the following information. - sh platform If 10GE linecard, - sh processes ether_ctrl_lc_10ge location - sh ether-ctrl tenGigE trace location If 1GE linecard, - sh processes ether_ctrl_lc_ge location - sh ether-ctrl gigabitEthernet trace location If the process is non-operational, try doing from the admin mode process restart ether_ctrl_lc_ge location if 1GE process exited or process restart ether_ctrl_lc_19ge location if 1GE process exited.

Error Message     
 
    
    
   

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

Explanation    A runtime failure occurred in Ether-ctrl process. Typically, this is an internal error. The message string indicates the reason for the failure. This message also provides an error code. The process can continue functioning as expected despite the failure.

Recommended Action    Collect console log and the following information. - sh platform If 10GE linecard, - sh processes ether_ctrl_lc_10ge location - sh ether-ctrl tenGigE trace location If 1GE linecard, - sh processes ether_ctrl_lc_ge location - sh ether-ctrl gigabitEthernet trace location If the process is non-operational, try doing from the admin mode process restart ether_ctrl_lc_ge location if 1GE process exited or process restart ether_ctrl_lc_19ge location if 1GE process exited.

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. Collect console log and the following information. - sh platform If 10 GE linecard, - sh processes ether_ctrl_lc_10ge location - sh ether-ctrl tenGigE trace location If 1 GE linecard, - sh processes ether_ctrl_lc_ge location - sh ether-ctrl gigabitEthernet trace location

Error Message     
 
    
    
   

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

Explanation    A runtime failure occurred in Ether-Ctrl process. Typically, this is an internal error. The message string indicates the reason for the failure. This message also provides an error code and a string interpretation of the error code.

Recommended Action    Collect console log and the following information. - sh platform If 10GE linecard, - sh processes ether_ctrl_lc_10ge location - sh ether-ctrl tenGigE trace location If 1 GE linecard, - sh processes ether_ctrl_lc_ge location - sh ether-ctrl gigabitEthernet trace location

Error Message     
 
    
    
   

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

Explanation    A runtime failure occurred in Ether-Ctrl-Mgmt process. Typically, this is an internal error. The message string indicates the reason for the failure. This message also provides an error code and a string interpretation of the error code.

Recommended Action    Collect console log and the following information. - sh platform - sh process ether_ctrl_mgmt

Error Message     
 
    
    
   

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

Explanation    A runtime failure occurred in Ether-Ctrl process. Typically, this is an internal error. The message string indicates the reason for the failure. This message also provides an error code and a string interpretation of the error code.

Recommended Action    Collect console log and the following information. - sh platform - sh processes blocked location If 10 GE linecard, - sh processes ether_ctrl_lc_10ge location - sh ether-ctrl tenGigE trace location If 1 GE linecard, - sh processes ether_ctrl_lc_ge location - sh ether-ctrl gigabitEthernet trace location

Error Message     
 
    
    
   

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

Explanation    A runtime failure occurred in Ether-Ctrl process. Typically, this is an internal error. The message string indicates the reason for the failure. This message also provides an error code and a string interpretation of the error code.

Recommended Action    Collect console log and the following information. - sh platform If 10 GE linecard, - sh processes ether_ctrl_lc_10ge location - sh ether-ctrl tenGigE trace location If 1 GE linecard, - sh processes ether_ctrl_lc_ge location - sh ether-ctrl gigabitEthernet trace location

Error Message     
 
    
    
   

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

Explanation    A runtime failure occurred in Ether-Ctrl process. Typically, this is an internal error. The message string indicates the reason for the failure. This message also provides an error code and a string interpretation of the error code.

Recommended Action    Collect console log and the following information. - sh platform If 10 GE linecard, - sh processes ether_ctrl_lc_10ge location - sh ether-ctrl tenGigE trace location If 1 GE linecard, - sh processes ether_ctrl_lc_ge location - sh ether-ctrl gigabitEthernet trace location

Error Message     
 
    
    
   

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

Explanation    A runtime failure occurred in Ether-Ctrl process. Typically, this is an internal error. The message string indicates the reason for the failure. This message also provides an error code and a string interpretation of the error code.

Recommended Action    Collect console log and the following information. - sh platform If 10 GE linecard, - sh processes ether_ctrl_lc_10ge location - sh ether-ctrl tenGigE trace location If 1 GE linecard, - sh processes ether_ctrl_lc_ge location - sh ether-ctrl gigabitEthernet trace location

Error Message     
 
    
    
   

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

Explanation    A runtime failure occurred in Ether-Ctrl process. Typically, this is an internal error. The message string indicates the reason for the failure. This message also provides an error code and a string interpretation of the error code.

Recommended Action    Collect console log and the following information. - sh platform If 10 GE linecard, - sh processes ether_ctrl_lc_10ge location - sh ether-ctrl tenGigE trace location If 1 GE linecard, - sh processes ether_ctrl_lc_ge location - sh ether-ctrl gigabitEthernet trace location

Error Message     
 
    
    
   

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

Explanation    This message provides information about the pluggable transceiver. Possible causes are not supported speed, autoneg.

Recommended Action    The message is just for information.

Error Message     
 
    
    
   

%PLATFORM-ETHER_CTRL-6-INFO [chars]

Explanation    This message provides information about the kind of events happening in the software at the location where the error is seen. This is not an error message. Typically, following events are logged in this message type. - End of successful initialization of the software. - Start and end of a processing of new object that needs to programmed to the hardware. - Configuration is not applicable to the port.

Recommended Action    The message is just for information. No action is needed.

FABARBITER Messages

Error Message     
 
    
    
   

%PLATFORM-FABARBITER-1-BKR_ERROR Crossbar fabric arbiter driver bkr module error on [chars]

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-1-BKT_ERROR Crossbar fabric arbiter driver bkt module error on [chars]

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-1-CARB_CRM_ERROR Crossbar fabric arbiter driver carb crm error on [chars]

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-1-CARB_ENQDEQ_ERROR Crossbar fabric arbiter driver carb enqdeq error on [chars]

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-1-CARB_FIL_ERROR Crossbar fabric arbiter driver carb filter error on [chars]

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-1-CPU_ACCESS_ERROR Crossbar fabric arbiter driver access 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-1-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-1-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-1-SERDES_ERROR Crossbar fabric arbiter driver serdes error on [chars]

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_CCI_CREATE_Q Still trying to create pdma queue on dev [dec] after [dec] seconds

Explanation    Cannot create pdma queue required. Likely a asic driver does not come up properly %d - 0 ingressq; 1 egressq; 2 fabricq 0; 3 fabricq 1 %d - number of seconds elapsed

Recommended Action    Investigate if driver processes (ingressq, egressq or fabricq) initialized properly.

Error Message     
 
    
    
   

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

Explanation    Encounter problem during process initialization. '%s' contains the explanation of the problem. %s - error description %d - error code %s - error code description

Recommended Action    Restart the fabio_svr process. Contact TAC if problem still exist

Error Message     
 
    
    
   

%PLATFORM-FABIO-3-ERR_QAD_EGRESS_QUEUE_MISSING Failed to find necessary egress QAD queues [chars] ([chars])

Explanation    Failed to find the qad queue for egress packets. This could causes applications using this qad queue not sending out packet %s - QAD queue name %s - thread name

Recommended Action    Reload the card. Copy the error message exactly as it appears on 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_QAD_GET_DEPTH Failed to get depth of qad queue 0x[pointer]

Explanation    Failed to get the qad queue depth (number of packets in queue). This should be because of some issues with the indicated qad queue %p - QAD queue id

Recommended Action    Copy the error message exactly as it appears on 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_QAD_NOTIF QAD transition notification failed 0x[pointer]

Explanation    Failed to get the qad notification of queue depth above or below watermark. This normally indicates there is some issues with the qad queue %p - QAD queue id

Recommended Action    Copy the error message exactly as it appears on 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_QAD_SET_WM Failed to set [chars] for qad queue 0x[pointer]

Explanation    Failed to set the watermark of the indicated qad queue. This should be because of some issues with the qad queue %s - high or low watermark %p - QAD queue id

Recommended Action    Copy the error message exactly as it appears on 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-4-ERR_NETIO_CONN Still trying to connect to pak netio after [dec] seconds

Explanation    Cannot connect to netio pak 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-FABIO-7-ERR_NULL_ARGS --

Explanation    Failed to create thread due to internal error.

Recommended Action    Restart the fabio_svr process

Error Message     
 
    
    
   

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

Explanation    Cannot send packet to pdma queue %s - error description %x - QAD queue id %d - 0 ingressq; 1 egressq; 2 fabricq 0; 3 fabricq 1 %x - error code

Recommended Action    Ignore the message if it only appears once otherwise contact TAC

Error Message     
 
    
    
   

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

Explanation    Cannot send packet to qad queue, likely the qad queue is full and application does not drain the qad queue fast enough %s - error description %d - 0 ingressq; 1 egressq; 2 fabricq 0; 3 fabricq 1 %d - queue number %x - error code

Recommended Action    Ignore the message if it only appears once otherwise contact TAC

FABMGR Messages

Error Message     
 
    
    
   

%PLATFORM-FABMGR-0-XBAR_DIS_FR_PEER Fabric crossbars disabled from peer RSP

Explanation    Peer RSP has disabled fabric crossbars.

Recommended Action    This (standby) RSP must be power cycled. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-FABMGR-1-ARB_SERDES_FAIL Slot [dec]: Failure in Arbiter Serdes Links

Explanation    Persistent failure in serdes link.

Recommended Action    Please try powercycling the board using command: 'hw-module loc reload'. Make sure board is seated 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-FABMGR-1-BAD_XBAR Slot [dec]: XBAR-MASK-[hex] may be faulty

Explanation    Persistent failure in serdes links to all connected linecards.

Recommended Action    Please try powercycling the RSP board using command: 'hw-module loc reload'. Make sure board is seated 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-FABMGR-1-PERSISTENT_SERDES_FAIL Slot [dec]: Persistent failure in Serdes Links

Explanation    Persistent failure in serdes link.

Recommended Action    Please try powercycling the board using command: 'hw-module loc reload'. Make sure board is seated 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.

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://tools.cisco.com/ServiceRequestTool/create/, 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://tools.cisco.com/ServiceRequestTool/create/ , 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://tools.cisco.com/ServiceRequestTool/create/, 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://tools.cisco.com/ServiceRequestTool/create/, 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://tools.cisco.com/ServiceRequestTool/create/ , 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://tools.cisco.com/ServiceRequestTool/create/ , 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://tools.cisco.com/ServiceRequestTool/create/ , 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://tools.cisco.com/ServiceRequestTool/create/, 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 persists. 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-FIA_INIT_LOS_ERROR Persistent LOS detected on fabric card in slot [dec], shutting down the fabric card.

Explanation    This indicates persistent LOS detected on one of the fabric planes. The fabric card having the issue will be shutdown.

Recommended Action    Replace the fabric card that is being shut. In case the problem is persisting after replacing the fabric cards, problem could be with the Active RP.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-2-FIA_MULTI_INIT_LOS_ERROR Persistent LOS detected on [dec] fabric planes.

Explanation    This indicates LOS errors are seen multi fabric planes. This could be issue with active node. This could result in bringing down the system. Replace the fabric card and check for system bootup, if still fails the issue could be active node, replace the active node.

Recommended Action    Replace the fabric cards that are being shut. In case the problem is persisting after replacing the fabric cards, problem could be with the Active RP.

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://tools.cisco.com/ServiceRequestTool/create/ , 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://tools.cisco.com/ServiceRequestTool/create/, 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://tools.cisco.com/ServiceRequestTool/create/, 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-CONNECT_LCS Failure detected on fabric cards [chars] in connecting LC/RPs [chars].

Explanation    This indicates a failure in connecting LC/RPs from fabric due to one of the following reasons either temporary/permanent. 1. There has been a problem in communication over the MBUS. 2. The fabric cards indicated in mask have hardware problem. 3. A LC/RP with bad hardware impacting the MBUS communication is inserted.

Recommended Action    Safely ignore the message if it's one time and no impact on the system. Ignore one time parity errors that may follow. If the trigger is insertion of a new LC/RP, watch for LC/RP reload during next few minutes due to fabric ping failure. Ensure that all the firmware on fabric cards are up to date. Replace the fabric card indicated in the message if the problem persists. If problem is reported on multiple fabric cards, contact Cisco Support.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-3-DISCONNECT_LCS Failure detected on fabric cards [chars] in disconnecting LC/RPs [chars].

Explanation    This indicates a failure in disconnecting LC/RPs from fabric due to one of the following reasons either temporary/permanent. 1. There has been a problem in communication over the MBUS. 2. The fabric cards indicated in mask have hardware problem.

Recommended Action    Safely ignore the message if it's one time and no impact on the system. Ensure that all the firmware on fabric cards are up to date. Replace the fabric card indicated in the message if the problem persists. If problem is reported on multiple fabric cards, contact Cisco Support.

Error Message     
 
    
    
   

%PLATFORM-FABRIC_CTRL-3-GET_CARD_TYPE Failed to determine card type of slot [dec] in [dec] retries

Explanation    This message indicates that the Fabric Controller Software on the active RP has failed to determine the card type for card in slot through retries attempts from the mbus agent.

Recommended Action    Verify the MBUS agent ROM version is up-to-date. Reseat the card with the error. If you still require assistance, contact your Cisco technical support representative and provide him with the following logs show logging show tech-support

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 node via MBUS.

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://tools.cisco.com/ServiceRequestTool/create/ , 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://tools.cisco.com/ServiceRequestTool/create/ , 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://tools.cisco.com/ServiceRequestTool/create/, 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://tools.cisco.com/ServiceRequestTool/create/ , 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://tools.cisco.com/ServiceRequestTool/create/, 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://tools.cisco.com/ServiceRequestTool/create/, 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 necessary 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_MGR_CLIENT Messages

Error Message     
 
    
    
   

%PLATFORM-FAULT_MGR_CLIENT-3-MSG_ERROR [chars]%s

Explanation    This message indicates fault manager client on the LC is unable to send message to server. Fault manager client will try to connect to LWM channel for sending fault indication to the server. If the channel connect or message send fails error details will be displayed. Subsequent LWM messages for clint will succed.*RECUR* %s - Error details %s - why the error occurred

Recommended Action    No action is required.

FAULT_MGR_EH Messages

Error Message     
 
    
    
   

%PLATFORM-FAULT_MGR_EH-3-MSG_ERROR ERROR while ([chars]%s)

Explanation    This error indicates failure in fault manager client for E3/E5 Linecard. This is a non service impacting message. %s - indicates where the error occurred %s - why the error occurred

Recommended Action    No action is required.

FAULT_MGR Messages

Error Message     
 
    
    
   

%PLATFORM-FAULT_MGR-1-MSG_E7_INFO [chars]

Explanation    This is a informational message from E7 fault manager. This indicates that fault manager has received a fault message. %s - Message to be displayed

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-FAULT_MGR-1-MSG_INFO [chars]

Explanation    This is a informational message %s - message that needs to be displayed to the user

Recommended Action    Debug message only. No action is required.

Error Message     
 
    
    
   

%PLATFORM-FAULT_MGR-1-TW_INFO Max errors of [dec] will be tolerated in [dec] sec

Explanation    This informational message tells the timer wheel configuration %d - max_errors %d - max_timer

Recommended Action    Debug message only. No action is required.

Error Message     
 
    
    
   

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

Explanation    The fault-mgr process failed to initialize. This process controls all ASIC resets on all LC's for either internal ASIC problems or larger system issues (for example, fabric control). %s - indicates the reason for the failure. There are 3 types of possible failures, these include: - Checkpointing initialization/creation/restore - Server initialization - Client initialization %s - is the decoded error reason

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

Error Message     
 
    
    
   

%PLATFORM-FAULT_MGR-3-MSG_E7_ERROR ERROR while ([chars]%s)

Explanation    This error indicates failure in fault manager client for E7 Linecard. This is a non service impacting message. %s - why the error occurred.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-FAULT_MGR-3-MSG_ERROR ERROR while ([chars]%s)

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

Recommended Action    Execute 'show process fault_mgr location 0/x/cpu0' to verify that the process is up and running. If it is still non-operational, try doing 'process restart fault_mgr location 0/x/cpu0' If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

FAULT Messages

Error Message     
 
    
    
   

%PLATFORM-FAULT-2-LC_RESET Reset LC [dec]: Reason - [chars]

Explanation    PRP Platform Manager process received an mbus message from the LC fault-mgr process saying the LC will be reloaded. The platform-mgr process is only reporting this message, via mbus, for the LC fault-mgr process - as some HW devices have failed and the slow-path will be down. %d - is the slot number of 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 slot number of 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-CPT4_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-CPT4_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-CRRS4_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-CRRS4_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-TMCAT_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-TMCAT_PAR_ERROR PortCtrl 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-VLK_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-VLK_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-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 determine 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    Miscellaneous 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 process 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 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]