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

Platform Messages

Table Of Contents

Platform Messages

AFMON_EA_OOR Messages

AFMON_EA_VERIFY Messages

ALPHA_DISPLAY Messages

APIV Messages

ARB Messages

ASM Messages

ASR9k_IFLX Messages

AVSM_APIV 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_DRV 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

LIB_ISOLATION 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

NIRVANA 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_HAL 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_BMADJ Messages

PLAT_FIB_EA Messages

PLAT_FIB_ECD 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_MCAST 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

PRM_VERIFY 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

PWHE_EA_PD 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_API Messages

SHELFMGR_HAL Messages

SHELFMGR Messages

SHELFMGRV2 Messages

SHOW_VERSION_CMD Messages

SIM_INFRA Messages

SIM_IPC Messages

SIM_SE Messages

SL Messages

SMITH 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

TIPCP 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_PMLIB_CLIENT Messages

VKG_PMLIB_IM Messages

VKG_PMLIB Messages

VKG_SERDES Messages

VKG_SIS Messages

WD_PLATFORM Messages

WDMBI Messages

XBAR Messages

XCVR Messages

XFP Messages

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

Recommended Action    Reduce the number of flows being monitored on the NP. This can be done by the following:

1. Modify ACL.

Remove the performance traffic service policy from the interface.

Modify the ACL used in the service policy to be more specific to match a smaller set of flows to be monitored.

Reapply the service policy to the interface.

2. Move 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. The %s indicates the reason for the failure. There are 2 types of possible failures which include: Event Manager Creation Failure and SYSDB Initialization Failure. The %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. The %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.

APIV Messages

Error Message     
 
    
    
   

%PLATFORM-APIV-2-API_INCOMPATIBLE Message [dec] in APIV module [chars] is incompatible (reason: [chars])

Explanation    The APIV module message version negotiation 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-APIV-3-MODULE_INCOMPATIBLE APIV module [chars] is incompatible

Explanation    APIV module version negotiation 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-APIV-3-SW_ERROR [chars]

Explanation    An internal software error has occurred for the specified APIV module.

Recommended Action    Copy the error message exactly as 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    This is an 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    This is an 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    This is an 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    This is an 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, issue one of the following:

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. The %s indicates the type failure.

Recommended Action    If the system has not failed over automatically and a redundant route processor card has been configured, issue one of the following:

1. 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, issue one of the following: 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-3-BADDESC_ERR Assembler detected a bad descriptor error: Data [hex]

Explanation    Assembler detected a bad descriptor in the free queue. The hex number indicates the error cause register value. This usually indicates a hardware problem on the RP.

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-ASM-3-DEVICE_HALT FFQ: device halted, sub-block: [chars], halted entity: [chars]

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

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

Error Message     
 
    
    
   

%PLATFORM-ASM-3-FATAL assembler dll: fatal error encountered, reason equals [chars]

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

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

Error Message     
 
    
    
   

%PLATFORM-ASM-3-FATAL_2 assembler dll: fatal error encountered, reason equals [chars], errno equals [dec]

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-ASM-3-FQEMPTY_ERR Assembler detected that a free queue is empty

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

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

Error Message     
 
    
    
   

%PLATFORM-ASM-3-GEN_INFO assembler dll: general information,[chars]

Explanation    This is 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 initialization 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 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. This needs to be implemented.

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. There is no explicit blocking.

Recommended Action    Do not configure unsupported IFLX front port sharing mode.

AVSM_APIV Messages

Error Message     
 
    
    
   

%PLATFORM-AVSM_APIV-3-REGISTRATION_TIMEOUT Timeout ([dec] seconds) waiting for APIV modules registration.

Explanation    The registration of APIV modules has not completed. The specified timeout period has reached and is this event will be considered as a failure that will trigger a reload of the affected card.

Recommended Action    Contact Cisco TAC to diagnose the problem.

Error Message     
 
    
    
   

%PLATFORM-AVSM_APIV-4-MOD_NOT_REGISTERED The [chars] APIV module (module ID equals [dec]) was not registered in time to receive version negotiation event notification.

Explanation    This event will cause the module to fail in APIV versioning negotiation operation.

Recommended Action    Contact Cisco TAC to diagnose the problem.

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.

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

Recommended Action    Do nothing.

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.

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-DIR_NOT_FOUND [chars] directory not found.

Explanation    This is an informational message to indicate that a log directory in the storage device is not found. 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    This is 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    This is 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    This is a 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    This is a 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    This is a 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    This is a 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 is 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 is 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 is 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 is 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    There is a 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    There is a 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    There is a 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    This is a 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    This is a 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    This is a 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    This is a 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    This is a 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    This is a 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    This is a 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    This is a 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    This is a 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    This is a 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    This is a 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    This is a 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    This is a 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    This is a 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    This is a 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    This is a 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    There is an 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    There is an 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    There is an 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    There is an 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    There is a 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    There is a 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    There is a 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    There is a 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 occurred 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 occurred 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 occurred 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 occurred 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 is 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 is 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 is 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 is 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 is 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 is 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 is 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 is 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    There is an 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    There is an 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    There is an 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    There is an 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    There is a 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    There is a 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    There is a 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    There is a 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 occurred 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 occurred 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 occurred 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 occurred 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    The NPU-1 XAUI PLL is 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 is 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 is 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 is 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 is 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 is 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 is 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 is 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 is 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 is 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 is 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 is 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 are 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 are 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 are 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 are 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    There is a 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    There is a 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    There is a 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    There is a 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    There is a 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    There is a 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    There is a 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    There is a 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred 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 occurred when free page FIFO is 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 occurred when free page FIFO is 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 occurred when free page FIFO is 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-DEC_A_CRC_ERR_0 Decoder A CRC Error - 0

Explanation    Decoder A CRC error on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-DEC_A_CRC_ERR_1 Decoder A CRC Error - 1

Explanation    Decoder A CRC error on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-DEC_A_FRAME_ERR_0 Decoder A Framing Error - 0

Explanation    Decoder A framing error on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-DEC_A_FRAME_ERR_1 Decoder A Framing Error - 1

Explanation    Decoder A framing error on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-DEC_A_PKT_LEN_ERR_0 Decoder A Packet Length Error - 0

Explanation    Packet with invalid length encountered by decoder A on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-DEC_A_PKT_LEN_ERR_1 Decoder A Packet Length Error - 1

Explanation    Packet with invalid length encountered by decoder A on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-DEC_A_PWM_ERR_0 Decoder A PWM Error - 0

Explanation    PWM bit level decoder error on decoder A on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-DEC_A_PWM_ERR_1 Decoder A PWM Error - 1

Explanation    PWM bit level decoder error on decoder A on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-DEC_A_TYPE_DISABLED_0 Decode A Type Disabled - 0

Explanation    Packet received for timestamp type disabled on Decoder A on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-DEC_A_TYPE_DISABLED_1 Decode A Type Disabled - 1

Explanation    Packet received for timestamp type disabled on Decoder A on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_LONG_PKT_0_0 Egress long packet detected - 0,0

Explanation    Egress long packet detected on xaui-0 bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_LONG_PKT_0_1 Egress long packet detected - 0,1

Explanation    Egress long packet detected on xaui-0 bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_LONG_PKT_1_0 Egress long packet detected - 1,0

Explanation    Egress long packet detected on xaui-1 bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_LONG_PKT_1_1 Egress long packet detected - 1,1

Explanation    Egress long packet detected on xaui-1 bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_NPH_LEN_0_0 Egress invalid length detected - 0,0

Explanation    Invalid egress NPH length detected on xaui-0 bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_NPH_LEN_0_1 Egress invalid length detected - 0,1

Explanation    Invalid egress NPH length detected on xaui-0 bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_NPH_LEN_1_0 Egress invalid length detected - 1,0

Explanation    Invalid egress NPH length detected on xaui-1 bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_NPH_LEN_1_1 Egress invalid length detected - 1,1

Explanation    Invalid egress NPH length detected on xaui-1 bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_SEG_DATA_FIFO_OFLOW_0_0 Egress seg data fifo overflow - 0,0

Explanation    Egress seg data FIFO overflow on xaui-0 bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_SEG_DATA_FIFO_OFLOW_0_1 Egress seg data fifo overflow - 0,1

Explanation    Egress seg data FIFO overflow on xaui-0 bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_SEG_DATA_FIFO_OFLOW_1_0 Egress seg data fifo overflow - 1,0

Explanation    Egress seg data FIFO overflow on xaui-1 bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_SEG_DATA_FIFO_OFLOW_1_1 Egress seg data fifo overflow - 1,1

Explanation    Egress seg data FIFO overflow on xaui-1 bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_SEG_HDR_EXT_FIFO_OFLOW_0_0 Egress seg hdr ext fifo overflow - 0,0

Explanation    Egress seg hdr ext FIFO overflow on xaui-0 bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_SEG_HDR_EXT_FIFO_OFLOW_0_1 Egress seg hdr ext fifo overflow - 0,1

Explanation    Egress seg hdr ext FIFO overflow on xaui-0 bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_SEG_HDR_EXT_FIFO_OFLOW_1_0 Egress seg hdr ext fifo overflow - 1,0

Explanation    Egress seg hdr ext FIFO overflow on xaui-1 bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_SEG_HDR_EXT_FIFO_OFLOW_1_1 Egress seg hdr ext fifo overflow - 1,1

Explanation    Egress seg hdr ext FIFO overflow on xaui-1 bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_SEG_HDR_FIFO_OFLOW_0_0 Egress seg hdr fifo overflow - 0,0

Explanation    Egress seg hdr FIFO overflow on xaui-0 bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_SEG_HDR_FIFO_OFLOW_0_1 Egress seg hdr fifo overflow - 0,1

Explanation    Egress seg hdr FIFO overflow on xaui-0 bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_SEG_HDR_FIFO_OFLOW_1_0 Egress seg hdr fifo overflow - 1,0

Explanation    Egress seg hdr FIFO overflow on xaui-1 bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_SEG_HDR_FIFO_OFLOW_1_1 Egress seg hdr fifo overflow - 1,1

Explanation    Egress seg hdr FIFO overflow on xaui-1 bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_SGT_FIFO_OFLOW_0_0 Egress sgt fifo overflow - 0,0

Explanation    Egress sgt FIFO overflow on xaui-0 bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_SGT_FIFO_OFLOW_0_1 Egress sgt fifo overflow - 0,1

Explanation    Egress sgt FIFO overflow on xaui-0 bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_SGT_FIFO_OFLOW_1_0 Egress sgt fifo overflow - 1,0

Explanation    Egress sgt FIFO overflow on xaui-1 bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_SGT_FIFO_OFLOW_1_1 Egress sgt fifo overflow - 1,1

Explanation    Egress sgt FIFO overflow on xaui-1 bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_SGT_HDR_EXT_FIFO_OFLOW_0_0 Egress sgt hdr ext fifo overflow - 0,0

Explanation    Egress sgt hdr ext FIFO overflow on xaui-0 bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_SGT_HDR_EXT_FIFO_OFLOW_0_1 Egress sgt hdr ext fifo overflow - 0,1

Explanation    Egress sgt hdr ext FIFO overflow on xaui-0 bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_SGT_HDR_EXT_FIFO_OFLOW_1_0 Egress sgt hdr ext fifo overflow - 1,0

Explanation    Egress sgt hdr ext FIFO overflow on xaui-1 bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_SGT_HDR_EXT_FIFO_OFLOW_1_1 Egress sgt hdr ext fifo overflow - 1,1

Explanation    Egress sgt hdr ext FIFO overflow on xaui-1 bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_SGT2_FIFO_OFLOW_0_0 Egress sgt2 fifo overflow - 0,0

Explanation    Egress sgt2 FIFO overflow on xaui-0 bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_SGT2_FIFO_OFLOW_0_1 Egress sgt2 fifo overflow - 0,1

Explanation    Egress sgt2 FIFO overflow on xaui-0 bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_SGT2_FIFO_OFLOW_1_0 Egress sgt2 fifo overflow - 1,0

Explanation    Egress sgt2 FIFO overflow on xaui-1 bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_SGT2_FIFO_OFLOW_1_1 Egress sgt2 fifo overflow - 1,1

Explanation    Egress sgt2 FIFO overflow on xaui-1 bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-EGR_SP_NOT_ZERO_0_0 Non-zero seg profile detected - 0,0

Explanation    Non-zero seg profile was detected on xaui-0 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-EGR_SP_NOT_ZERO_0_1 Non-zero seg profile detected - 0,1

Explanation    Non-zero seg profile was detected on xaui-0 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-EGR_SP_NOT_ZERO_1_0 Non-zero seg profile detected - 1,0

Explanation    Non-zero seg profile was detected on xaui-1 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-EGR_SP_NOT_ZERO_1_1 Non-zero seg profile detected - 1,1

Explanation    Non-zero seg profile was detected on xaui-1 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_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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-GST_JUMP_ERR_0 GST jump error - 0

Explanation    GST jump error on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-GST_JUMP_ERR_1 GST jump error - 1

Explanation    GST jump error on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-GST_PWM_TIMEOUT_0 GST PWM timeout - 0

Explanation    GST PWM is not received within 1 ms 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-GST_PWM_TIMEOUT_1 GST PWM timeout - 1

Explanation    GST PWM is not received within 1 ms 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-GST_SYNC_ERR_0 GST SYNC ERR - 0

Explanation    GST Sync error on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-GST_SYNC_ERR_1 GST SYNC ERR - 1

Explanation    GST Sync error on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-ING_INV_LEN_0 Ingress invalid length detected - 0

Explanation    Invalid ingress NPH length detected on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-ING_INV_LEN_1 Ingress invalid length detected - 1

Explanation    Invalid ingress NPH length detected on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-ING_L4_ARRAY_OFLOW_0 Ingress L4 array overflow - 0

Explanation    L4 array overflow on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-ING_L4_ARRAY_OFLOW_1 Ingress L4 array overflow - 1

Explanation    L4 array overflow on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-ING_L4_ARRAY_UFLOW_0 Ingress L4 array underflow - 0

Explanation    L4 array underflow on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-ING_L4_ARRAY_UFLOW_1 Ingress L4 array underflow - 1

Explanation    L4 array underflow on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

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

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

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

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

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_SCH_0_HANG_0 NPU-0 scheduler 0 hang - 0

Explanation    Scheduler 0 Hang on NPU-0 interface on bridge instance-0 occurred.

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_0 NPU-0 timestamp core error on bridge - 0

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

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

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

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

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_UPDATE_ERR_0 NPU-0 timestamp update error - 0

Explanation    Timestamp update error on NPU-0 interface on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_UPDATE_ERR_1 NPU-0 timestamp update error - 1

Explanation    Timestamp update error on NPU-0 interface on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

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

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

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

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

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

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

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

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

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_UPDATE_ERR_0 NPU-1 timestamp update error - 0

Explanation    Timestamp update error on NPU-1 interface on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_UPDATE_ERR_1 NPU-1 timestamp update error - 1

Explanation    Timestamp update error on NPU-1 interface on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-PAR_MERR_0 Multi bit mem parity error - 0

Explanation    Multi bit mem parity error on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-PAR_MERR_1 Multi bit mem parity error - 1

Explanation    Multi bit mem parity error on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-PAR_SERR_0 Single bit mem parity error - 0

Explanation    Single bit mem parity error on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-PAR_SERR_1 Single bit mem parity error - 1

Explanation    Single bit mem parity error on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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-SCH_0_HANG_0 Scheduler 0 hang - 0

Explanation    Scheduler 0 Hang on bridge instance-0 occurred.

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-SCH_0_HANG_1 NPU-0 scheduler 0 hang - 1

Explanation    Scheduler 0 Hang on bridge instance-1 occurred.

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-SCH_1_HANG_0 Scheduler 1 hang - 0

Explanation    Scheduler 1 Hang on bridge instance-0 occurred.

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-SCH_1_HANG_1 Scheduler 1 hang - 1

Explanation    Scheduler 1 Hang on bridge instance-1 occurred.

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-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_0_HQ_FULL_0 XAUI 0 High Queue full error - 0

Explanation    Queue full error on XAUI 0 HQ on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_HQ_FULL_1 XAUI 0 High Queue full error - 1

Explanation    Queue full error on XAUI 0 HQ on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_HQ_OFLOW_0 XAUI 0 High Queue overflow error - 0

Explanation    Queue overflow error on XAUI 0 HQ on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_HQ_OFLOW_1 XAUI 0 High Queue overflow error - 1

Explanation    Queue overflow error on XAUI 0 HQ on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_HQ_PKT_LEN_0 XAUI 0 High Queue packet length error - 0

Explanation    Queue packet length error on XAUI 0 HQ on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_HQ_PKT_LEN_1 XAUI 0 High Queue packet length error - 1

Explanation    Queue packet length error on XAUI 0 HQ on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_HQ_SEQ_0 XAUI 0 High Queue sequence error - 0

Explanation    Queue sequence error on XAUI 0 HQ on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_HQ_SEQ_1 XAUI 0 High Queue sequence error - 1

Explanation    Queue sequence error on XAUI 0 HQ on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_LQ_FULL_0 XAUI 0 Low Queue full error - 0

Explanation    Queue full error on XAUI 0 LQ on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_LQ_FULL_1 XAUI 0 Low Queue full error - 1

Explanation    Queue full error on XAUI 0 LQ on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_LQ_OFLOW_0 XAUI 0 Low Queue overflow error - 0

Explanation    Queue overflow error on XAUI 0 LQ on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_LQ_OFLOW_1 XAUI 0 Low Queue overflow error - 1

Explanation    Queue overflow error on XAUI 0 LQ on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_LQ_PKT_LEN_0 XAUI 0 Low Queue packet length error - 0

Explanation    Queue packet length error on XAUI 0 LQ on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_LQ_PKT_LEN_1 XAUI 0 Low Queue packet length error - 1

Explanation    Queue packet length error on XAUI 0 LQ on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_LQ_SEQ_0 XAUI 0 Low Queue sequence error - 0

Explanation    Queue sequence error on XAUI 0 LQ on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_LQ_SEQ_1 XAUI 0 Low Queue sequence error - 1

Explanation    Queue sequence error on XAUI 0 LQ on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_MQ_FULL_0 XAUI 0 Mgmt Queue full error - 0

Explanation    Queue full error on XAUI 0 MQ on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_MQ_FULL_1 XAUI 0 Mgmt Queue full error - 1

Explanation    Queue full error on XAUI 0 MQ on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_MQ_OFLOW_0 XAUI 0 Mgmt Queue overflow error - 0

Explanation    Queue overflow error on XAUI 0 MQ on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_MQ_OFLOW_1 XAUI 0 Mgmt Queue overflow error - 1

Explanation    Queue overflow error on XAUI 0 MQ on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_MQ_PKT_LEN_0 XAUI 0 Mgmt Queue packet length error - 0

Explanation    Queue packet length error on XAUI 0 MQ on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_MQ_PKT_LEN_1 XAUI 0 Mgmt Queue packet length error - 1

Explanation    Queue packet length error on XAUI 0 MQ on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_MQ_SEQ_0 XAUI 0 Mgmt Queue sequence error - 0

Explanation    Queue sequence error on XAUI 0 MQ on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_MQ_SEQ_1 XAUI 0 Mgmt Queue sequence error - 1

Explanation    Queue sequence error on XAUI 0 MQ on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_HQ_FULL_0 XAUI 1 High Queue full error - 0

Explanation    Queue full error on XAUI 1 HQ on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_HQ_FULL_1 XAUI 1 High Queue full error - 1

Explanation    Queue full error on XAUI 1 HQ on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_HQ_OFLOW_0 XAUI 1 High Queue overflow error - 0

Explanation    Queue overflow error on XAUI 1 HQ on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_HQ_OFLOW_1 XAUI 1 High Queue overflow error - 1

Explanation    Queue overflow error on XAUI 1 HQ 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_HQ_PKT_LEN_0 XAUI 1 High Queue packet length error - 0

Explanation    Queue packet length error on XAUI 1 HQ on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_HQ_PKT_LEN_1 XAUI 1 High Queue packet length error - 1

Explanation    Queue packet length error on XAUI 1 HQ on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_HQ_SEQ_0 XAUI 1 High Queue sequence error - 0

Explanation    Queue sequence error on XAUI 1 HQ on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_HQ_SEQ_1 XAUI 1 High Queue sequence error - 1

Explanation    Queue sequence error on XAUI 1 HQ on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_LQ_FULL_0 XAUI 1 Low Queue full error - 0

Explanation    Queue full error on XAUI 1 LQ on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_LQ_FULL_1 XAUI 1 Low Queue full error - 1

Explanation    Queue full error on XAUI 1 LQ on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_LQ_OFLOW_0 XAUI 1 Low Queue overflow error - 0

Explanation    Queue overflow error on XAUI 1 LQ on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_LQ_OFLOW_1 XAUI 1 Low Queue overflow error - 1

Explanation    Queue overflow error on XAUI 1 LQ on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_LQ_PKT_LEN_0 XAUI 1 Low Queue packet length error - 0

Explanation    Queue packet length error on XAUI 1 LQ on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_LQ_PKT_LEN_1 XAUI 1 Low Queue packet length error - 1

Explanation    Queue packet length error on XAUI 1 LQ on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_LQ_SEQ_0 XAUI 1 Low Queue sequence error - 0

Explanation    Queue sequence error on XAUI 1 LQ on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_LQ_SEQ_1 XAUI 1 Low Queue sequence error - 1

Explanation    Queue sequence error on XAUI 1 LQ on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_MQ_FULL_0 XAUI 1 Mgmt Queue full error - 0

Explanation    Queue full error on XAUI 1 MQ on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_MQ_FULL_1 XAUI 1 Mgmt Queue full error - 1

Explanation    Queue full error on XAUI 1 MQ on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_MQ_OFLOW_0 XAUI 1 Mgmt Queue overflow error - 0

Explanation    Queue overflow error on XAUI 1 MQ on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_MQ_OFLOW_1 XAUI 1 Mgmt Queue overflow error - 1

Explanation    Queue overflow error on XAUI 1 MQ on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_MQ_PKT_LEN_0 XAUI 1 Mgmt Queue packet length error - 0

Explanation    Queue packet length error on XAUI 1 MQ on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_MQ_PKT_LEN_1 XAUI 1 Mgmt Queue packet length error - 1

Explanation    Queue packet length error on XAUI 1 MQ on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_MQ_SEQ_0 XAUI 1 Mgmt Queue sequence error - 0

Explanation    Queue sequence error on XAUI 1 MQ on bridge instance-0 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as it appears on the 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_MQ_SEQ_1 XAUI 1 Mgmt Queue sequence error - 1

Explanation    Queue sequence error on XAUI 1 MQ on bridge instance-1 occurred.

Recommended Action    If the error persists, please reload the board using the command 'reload location '. If the message recurs, copy the error message exactly as 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 occurred.

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

Error Message     
 
    
    
   

%PLATFORM-CAIBIST-3-ERR_HW_BIST_TIMEDOUT [chars] asic instance [dec] bist block [chars] BIST timedout.

Explanation    BIST failure occurred.

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

Error Message     
 
    
    
   

%PLATFORM-CAIBIST-3-ERR_SW_INIT [chars].

Explanation    Software initialization error occurred.

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

CANB_SERVER Messages

Error Message     
 
    
    
   

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

Explanation    Alarm cleared was 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 was 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. 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 or 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. 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    This is an 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-RP_ISOLATION [chars] is in RP isolation

Explanation    This is an informational message indicating that target RP has transitioned into RP isolation.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-CANB_SERVER-6-RP_ISOLATION_RESET_REQ CPU reset request ignored for [chars]

Explanation    This is an informational message indicating that RP Isolation is in force, CPU reset request for the target slot is ignored.

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

CARD Messages

Error Message     
 
    
    
   

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

Explanation    ClkCtrl driver detected a card overcurrent condition.

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

CARDMGR Messages

Error Message     
 
    
    
   

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

Explanation    Failure to get CS revision information.

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

Error Message     
 
    
    
   

%PLATFORM-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 is 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 are 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 are found.

Recommended Action    Copy the error message exactly as it appears on 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 are found.

Recommended Action    Copy the error message exactly as it appears on 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    This is a 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 occurred.

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

Error Message     
 
    
    
   

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

Explanation    There is an 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    This is product information.

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    Resource could not be adjusted.

Recommended Action    Copy the error message exactly as it appears on 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    Opening 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 occurred.

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

Error Message     
 
    
    
   

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

Explanation    CIS data read error occurred.

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

Error Message     
 
    
    
   

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

Explanation    CIS replace error occurred.

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

Error Message     
 
    
    
   

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

Explanation    Release mismatch occurred.

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

Error Message     
 
    
    
   

%PLATFORM-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    This card is 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    Opening 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 fantray 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    This is only a debug message. 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 power-up 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 CRS-3 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 CRS-3 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    You are unable to read the power shelf backplane EEPROM for some reason. 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. 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. 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    This is an informational message indicating the temperature at which the 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    This is an informational message indicating an 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    This is only a debug message. 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-2-CRIT [chars] : [chars]

Explanation    An unexpected critical error condition was encountered.

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

Error Message     
 
    
    
   

%PLATFORM-CEMGBL-2-SFP_INVALID_TYPE CE SFP monitor init failed with invalid board type [hex]

Explanation    An unexpected failure in register notification failed.

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

Error Message     
 
    
    
   

%PLATFORM-CEMGBL-4-WARNING [chars] : [chars]

Explanation    An unexpected condition was encountered.

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

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

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

Error Message     
 
    
    
   

%PLATFORM-CEMGBL-7-REGISTER_NOTIFY_FAIL CE register notification failed with cb : [hex] intf : [hex] num_elements : [hex]

Explanation    An unexpected failure in register notification failed.

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 occurred on the 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    This indicates that there are 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, try the following:

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 1XCHOC48/DS3, 1XCHOC12/DS0, and 2XCHOC12/DS0 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, 1XCHOC48/DS3, 1XCHOC12/DS0, and 2XCHOC12/DS0 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    1XCHOC48/DS3, 1XCHOC12/DS0, and 2XCHOC12/DS0 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 1XCHOC48/DS3, 1XCHOC12/DS0, and 2XCHOC12/DS0 to ASIC 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    This is 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 initialization 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    1XCHOC48/DS3, 1XCHOC12/DS0, and 2XCHOC12/DS0 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, 1XCHOC48/DS3, 1XCHOC12/DS0, and 2XCHOC12/DS0 DLL 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 1XCHOC48/DS3, 1XCHOC12/DS0, and 2XCHOC12/DS0 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 1XCHOC48/DS3, 1XCHOC12/DS0, and 2XCHOC12/DS0 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 and needs to be implemented.

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. Reload the board.

Recommended Action    Due to too many resets, the board has been reloaded to recover.

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. Reload the system.

Recommended Action    An error has happened. Reload the system. Collect required information and contact TAC.

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 needs to shutdown.

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

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.

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 needs a power on reset.

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

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 needs reprogram resource.

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

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. Such errors have crossed threshold.

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

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 caused retrain link.

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

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

Recommended Action    Errors have been handled.

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 caused fabric link shutdown.

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

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.

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.

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 causes board reload.

Recommended Action    The output message is a warning board reload request.

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.

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 a hard reset is needed.

Recommended Action    An error has happened and a hard reset has been performed to recover. Collect required information and contact TAC.

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

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 caused fabric link shutdown.

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

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 errors have crossed threshold.

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

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.

Error Message     
 
    
    
   

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

Explanation    Missing mem_info while processing error interrupt occurred.

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

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 and provide the files to TAC support for further debugging.

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 needs power on reset. This marks 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 caused reprogram resource. This error has crossed threshold.

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

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 caused a retrain link.

Recommended Action    An error that causes a retrain link has happened and been handled.

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

Recommended Action    Errors have been handled.

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 needed 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 exceeded 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 needs to reprogram resource.

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

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.

Error Message     
 
    
    
   

%PLATFORM-CLKCTRL_T-2-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_T-2-TX_ALARM_TPDV_SYNC_0 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_T-2-TX_ALARM_TPDV_SYNC_1 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_T-3-INVALID_64K_INPUT_SYNC_0 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 64kHz + 8kHz Japanese timing signal (defined in G.703 Appendix II.1) is applied at input port.

Error Message     
 
    
    
   

%PLATFORM-CLKCTRL_T-3-INVALID_64K_INPUT_SYNC_1 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 64kHz + 8kHz Japanese timing signal (defined in G.703 Appendix II.1) is applied at input port.

Error Message    
 
    
    
   

%PLATFORM-CLKCTRL_T-3-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_T-3-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_T-3-RX_ALARM_AIS_SYNC_0 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 3ms 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 occurred.

Error Message     
 
    
    
   

%PLATFORM-CLKCTRL_T-3-RX_ALARM_AIS_SYNC_1 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 3ms 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 occurred.

Error Message    
 
    
    
   

%PLATFORM-CLKCTRL_T-3-RX_ALARM_FRAME_ERR_SYNC_0 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    Ensure a valid BITS/UTI signal is applied at input port.

Error Message     
 
    
    
   

%PLATFORM-CLKCTRL_T-3-RX_ALARM_FRAME_ERR_SYNC_1 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    Ensure a valid BITS/UTI signal is applied at input port.

Error Message    
 
    
    
   

%PLATFORM-CLKCTRL_T-3-RX_ALARM_LOF_SYNC_0 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_T-3-RX_ALARM_LOF_SYNC_1 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_T-3-RX_ALARM_LOS_SYNC_0 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 2048kHz 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_T-3-RX_ALARM_LOS_SYNC_1 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 2048kHz 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_T-3-RX_ALARM_RAI_SYNC_0 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_T-3-RX_ALARM_RAI_SYNC_1 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_T-3-TX_ALARM_OC_SYNC_0 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_T-3-TX_ALARM_OC_SYNC_1 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_T-3-TX_ALARM_SC_SYNC_0 Transmit short circuit condition [chars] for Tx mode [chars] on sync [dec] clock-interface

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

Recommended Action    None.

Error Message     
 
    
    
   

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

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

Recommended Action    None.

Error Message     
 
    
    
   

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

Explanation    Condition was 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_T-3-TX_ALARM_TAF_SYNC_1 Incorrect frame alignment condition [chars] for Tx mode [chars] on sync [dec] clock-interface.

Explanation    Condition was 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_T-3-TX_ALARM_TMF_SYNC_0 Incorrect multi-frame alignment condition [chars] for Tx mode [chars] on sync [dec] clock-interface.

Explanation    Condition was 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_T-3-TX_ALARM_TMF_SYNC_1 Incorrect multi-frame alignment condition [chars] for Tx mode [chars] on sync [dec] clock-interface.

Explanation    Condition was 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.

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 64kHz + 8kHz 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 3ms 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 occurred.

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    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 2048kHz 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 was 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 was 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 occurred.

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

Error Message     
 
    
    
   

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

Explanation    ClkCtrl Event Manager notify error occurred.

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

Error Message     
 
    
    
   

%PLATFORM-CLKCTRL-7-ERR_EXIT Exit on error: [chars]: Caused by [chars]

Explanation    An error occurred in ClkCtrl Driver which requires exiting 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 occurred.

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

Error Message     
 
    
    
   

%PLATFORM-CLKCTRL-7-ERR_LWM_REPLY An error occurred during LWM message reply. Reason: [chars]

Explanation    ClkCtrl LWM reply error occurred.

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

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.

Recommended Action    Copy the error message exactly as it appears on 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 occurred.

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

Error Message     
 
    
    
   

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

Explanation    CONCERTO Event Manager notify error occurred.

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

Error Message     
 
    
    
   

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

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

Error Message     
 
    
    
   

%PLATFORM-CONCERTO-7-ERR_LWM_REPLY An error occurred during LWM message reply. Reason: [chars]

Explanation    Concerto LWM reply error occurred.

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

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. The %s is the description of the specific failure encountered. The %s is the 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. The %s is the description of the specific failure encountered. The %s is the 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. The %s is the description of the specific failure encountered. The %s is the 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. The %s is the description of the specific failure encountered. The %s is the 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. The %s is the description of the specific failure encountered. The %s is the 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. The %s is the description of the specific failure encountered. The %s is the 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. The %s is the description of the specific failure encountered. The %s is the 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. The %s is the detail description of which ASIC cannot 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    This 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. The %s is the name of ram that error occurred. The %x is the key of error node recorded. The %s is the 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. The %s is the name of ram that error occurred. The %x is the key of error node recorded. The %s is the 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. The %s is the name of ram that error occurred. The %x is the key of error node recorded. The %s is the error data.

Recommended Action    If this happens 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. The %d is the port number. The %s is the device name. The %d is the queue number. The %s is the client name. The %d is the current descriptor index. The %d is the current refill descriptor index.

Recommended Action    Check the ASIC driver described in the error message for a possible stall.

Error Message     
 
    
    
   

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

Explanation    Cpuctrl Event Manager create error occurred.

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

Error Message     
 
    
    
   

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

Explanation    Cpuctrl Event Manager notify error occurred.

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

Error Message     
 
    
    
   

%PLATFORM-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. The %s is the error description. The %s is the error code description.

Recommended Action    Restart the process.

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-HW_DETECTED_ERROR_ISN [chars]

Explanation    The cpuctrl driver hardware 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-IMDR_ABORT The IMDR procedure was aborted by this process. Error [dec] Reason [chars]

Explanation    The CPUCTRL process aborted the IMDR upgrade process. Check prior log messages for possible process crashes or errors.

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

Error Message     
 
    
    
   

%PLATFORM-CPUCTRL-3-IMDR_ERR A error occurred [chars] process imdr. Error [dec] Reason [chars].

Explanation    A failure occurred when interacting with IMDRs. An IMDR operation in progress may be aborted or may not complete successfully.

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

Error Message     
 
    
    
   

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

Explanation    This 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. The %s is the name of ram that sbe occurred. The %x is the key of error node recorded. The %s is the 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    This 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. The %s is the name of ram that sbe occurred. The %x is the key of error node recorded. The %s is the 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. The %s is the name of ram. The %x is the key of error node recorded. The %s is the 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. The %s is the name of ram that occurred. The %x is the key of error node recorded. The %s is the 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. The %s is the name of ram that sbe occurred. The %x is the key of error node recorded. The %s is the 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. The %s is the name of ram that occurred. The %x is the key of error node recorded. The %s is the 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 occurred.

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

Error Message     
 
    
    
   

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

Explanation    Cpuctrl Sysdb Register EDM error occurred.

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

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. The %d is the channel number. The %d is the queue number. The %s is the client name. The %x is the address high 32 bit. The %x is the 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. The client is restarting.

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 an 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 an 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 a 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 a 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 upgrade 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 upgrade 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    Failure to mmap to Kernel dumper information in syspages occurred.

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

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) were 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 were 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 were 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 were 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 were 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 was 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 was 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    There are 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    There are 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    There are 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    There are details on the device bus error.

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    This is an informational 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    There are 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    There are 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    There are 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 a 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 a 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-2-XAUI_FAULT Dmac device [dec] XAUI link down for extended duration

Explanation    DMAC XAUI link went down and stayed down for an extended duration which would affect CE/Fabric connectivity of the RP.

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-6-UNEXPECTED_PCI_CONFIG Unexpected PCIe link state for DMAC [dec]: [dec] lanes Gen [dec], expected [dec] lanes Gen [dec]

Explanation    DMAC came up with a degraded PCIe configuration. Number of lanes and Link speed does not match what is expected.

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, DRP pairing configuration will be disabled.

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, DRP pairing configuration will be disabled.

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Failure when registering with CERR Handler occurred.

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    The DSC node ID cannot be determined.

Recommended Action    None.

Error Message     
 
    
    
   

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

Explanation    Even manager created failed.

Recommended Action    None.

Error Message     
 
    
    
   

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

Explanation    Failure to get node ID occurred.

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    --drp_pairing server is not able to be initialized.

Recommended Action    None.

Error Message     
 
    
    
   

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

Explanation    SysDB operation failed.

Recommended Action    None.

Error Message     
 
    
    
   

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

Explanation    Failure to create a thread occurred.

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 message 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 later. Copy the error message exactly as it appears on 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 power down/shutdown or there is some problem with control ethernet cables or switches between the racks.

Recommended Action    If the rack is not power down 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. 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. XR 12K: 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). XR 12K: 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    This is an 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. Continuos messages usually indicate a CE transport issue. Please check control ethernet connections to and from the node in question

Recommended Action    If continuos 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    Failure to save configuration for this rack occurred.

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 was 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 repeatedly, 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 DSC 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 DSC 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 and 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    There are 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 is required. This alarm and functionality are 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 line cards 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 hotspot 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    No action is 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 hotspot 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    No action is 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 nodeid. More details are at ASR9K debugability wiki.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-2-ENV_CONDITION An environmental condition on slot [dec] [chars]

Explanation    There are 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 environmental 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 environmental 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    No action is 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    No action is 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    No action is 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    No action is 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    No action is 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    No action is 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 line cards 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 was 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    This 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    This 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 specified voltage supply 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 daughter board 12V SPA voltage rail. However, you 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    Copy the error message exactly as it appears on 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_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    This is an 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. 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 command.

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. When the operating speed returns to the set RPM, the alarm clears.


Note Sometimes, an attempt to insert or remove fantrays operating below or above 30% of the set RPM raises the %PLATFORM-ENVMON-3-FANTRAY_ALARM.


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    No action is 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    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    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-3-UNKNOWN_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    Copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative, and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-3-UNKNOWN_E5_HW_TYPE slot:[dec] Cannot determine E5 hardware type.

Explanation    The envmon component could not determine the E5 type.

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

Error Message     
 
    
    
   

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

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

Error Message     
 
    
    
   

%PLATFORM-ENVMON-4-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 years expiry, restart the life cycle count.

Recommended Action    No action is 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 its 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 and (admin)# show env -- all sensor output. Specifically look at voltage sensor values. 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    No action is required.

Error Message    
 
    
    
   

%PLATFORM-ENVMON-4-CB_OFF_ALARM [chars] alarm [chars] by [chars]

Explanation    There are two possibilities to this message:

1. An alarm has occurred.

2. A previously occurred alarm has been cleared. With the 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 is 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 daughter board'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    None.

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 are

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    This is for displaying notification of mbus non responsiveness 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    No action is 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    No action is 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    No action is required.

Error Message    
 
    
    
   

%PLATFORM-ENVMON-6-FAN_INSERT Fan blower inserted into slot [dec]

Explanation    The specified fan blower module was detected as inserted.

Recommended Action    No action is required.

Error Message    
 
    
    
   

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

Explanation    This is an informational message 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 specified temperature sensor specified has returned to a level that is within the acceptable range.

Recommended Action    No action is required.

Recommended Action   

Error Message    

%PLATFORM-ENVMON-6-PEM_INSERT [chars] inserted into slot [dec]

Explanation    The power entry module specified was detected as inserted.

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

Error Message    
 
    
    
   

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

Explanation    Indicates that a non Cisco compliant power supply was detected. The 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 occurred.

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    No action is 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    No action is required.

Error Message    
 
    
    
   

%PLATFORM-ENVMON-7-BAG_DECODE_FAILED Bag decode on [chars] failed. Error: [chars]

Explanation    Failure to decode bag occurred.

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, you will not be able to store or report the voltage margin value for these offending sensors.

Recommended Action    Copy the error message exactly as it appears on 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_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    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    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    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 could not contact the DSC

Recommended Action    None.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_DSC_GET Could not determine relationship to dSC: [chars]

Explanation    Environmental monitoring could not 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    Failure to attach an event_handler to handle async messages occurred.

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

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_LWM_RECEIVE LWM Message Receive failed. Error: [chars]

Explanation    The Light-Weight Messaging msg_recieve function failed.

Recommended Action    None. Environmental Monitoring process will restart automatically

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_LWM_REPLY LWM Message Reply failed. Error: [chars]

Explanation    The Light-Weight Messaging msg_reply function failed.

Recommended Action    None. Environmental Monitoring process will restart automatically

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_MBUS_CEC [chars]: Error reading mbus cec register [hex] on slot [dec] bay [dec]. Status:[hex], Errno:[hex], ErrStr:'[chars]'

Explanation    An error occurred reading an MBus CEC register.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_MBUS_READREG [chars]: Error reading mbus register [hex] on slot [dec]: [chars]

Explanation    An error occurred reading an MBus register.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_MBUS_RECEIVE [chars]: Error receiving MBus message for slot [dec], type [dec]: [chars]

Explanation    An error occurred reading an MBus register.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_NODEID_CREATE nodeid_create for slot [dec] failed. Error: [chars]

Explanation    Platform function return error on invocation

Recommended Action    Ensure the Platform Library is available.

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-ERR_PTHREAD [chars]: pthread manipulation error: [chars]

Explanation    A 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 returned an 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    Failure to bind to SysDB occurred.

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    Failure to register for notification in Sysdb occurred.

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    Failure to register for configuration verification in Sysdb occurred.

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

Error Message     
 
    
    
   

%PLATFORM-ENVMON-7-EVENT_BLOCK_FAILED Event Manager could not block. Error: [chars]

Explanation    Failure to block 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 is 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 is 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    Issue show tech-support control ethernet fast location node on node that printed this message. Collect dump core running of process that printed 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    Issue show tech-support control ethernet fast location node on node that printed this message. Collect dump core running of process that printed 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 ethernet 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 ethernet 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-ISOLATE ethernet server received an Isolate message, all EOBC traffic disabled [chars]

Explanation    Ethernet server received an isolate message to disable all EOBC traffic.

Recommended Action    None. All EOBC traffic on this card is halted.

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, show buffer-manager region all context, dumpcore running jid/process name of eth_server, ingressq, fabricq_mgr, fsdb_server, fsdb_aserver, sfe_driver and 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, show buffer-manager region all context, dumpcore running jid/process name of eth_server, ingressq, fabricq_mgr, fsdb_server, fsdb_aserver, sfe_driver an 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 10 GE linecard, issue the following: sh processes ether_ctrl_lc_10ge location and sh ether-ctrl tenGigE trace location. If 1 GE linecard, issue the following: sh processes ether_ctrl_lc_ge location and sh ether-ctrl gigabitEthernet trace location. If 1 GE process, exit or process restart ether_ctrl_lc_19ge location.

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 10 GE linecard, issue the following: sh processes ether_ctrl_lc_10ge location and sh ether-ctrl tenGigE trace location. If 1 GE linecard, issue the following: sh processes ether_ctrl_lc_ge location and sh ether-ctrl gigabitEthernet trace location. If 1 GE process, exit or process restart ether_ctrl_lc_19ge location.

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, issue the following: sh processes ether_ctrl_lc_10ge location and sh ether-ctrl tenGigE trace location. If 1 GE linecard, issue the following: sh processes ether_ctrl_lc_ge location and sh ether-ctrl gigabitEthernet trace location.

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

Recommended Action    This is only a debug message. No action is required.

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 10 GE linecard, issue the following: sh processes ether_ctrl_lc_10ge location and sh ether-ctrl tenGigE trace location. If 1 GE linecard, issue the following: sh processes ether_ctrl_lc_ge location and 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, and ether_ctrl_mgmt.

Error Message     
 
    
    
   

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

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

Recommended Action    This is only a debug message. No action is required.

Error Message     
 
    
    
   

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

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

Recommended Action    This is only a debug message. No action is required.

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. If 10 GE linecard, issue the following: sh processes ether_ctrl_lc_10ge location and sh ether-ctrl tenGigE trace location. If 1 GE linecard, issue the following: sh processes ether_ctrl_lc_ge location and 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, issue the following: sh processes ether_ctrl_lc_10ge location and sh ether-ctrl tenGigE trace location. If 1 GE linecard, issue the following: sh processes ether_ctrl_lc_ge location and sh ether-ctrl gigabitEthernet trace location.

Error Message    
 
    
    
   

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

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

Recommended Action    This is only a debug message. No action is required.

Error Message    
 
    
    
   

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

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

Recommended Action    This is only a debug message. No action is required.

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, issue the following: sh processes ether_ctrl_lc_10ge location and sh ether-ctrl tenGigE trace location. If 1 GE linecard, issue the following: sh processes ether_ctrl_lc_ge location and sh ether-ctrl gigabitEthernet trace location.

Error Message    
 
    
    
   

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

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

Recommended Action    This is only a debug message. No action is required.

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, issue the following: sh processes ether_ctrl_lc_10ge location and sh ether-ctrl tenGigE trace location. If 1 GE linecard, issue the following: sh processes ether_ctrl_lc_ge location and sh ether-ctrl gigabitEthernet trace location.

Error Message    
 
    
    
   

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

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

Recommended Action    This is only a debug message. No action is required.

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, issue the following: sh processes ether_ctrl_lc_10ge location and sh ether-ctrl tenGigE trace location. If 1 GE linecard, issue the following: sh processes ether_ctrl_lc_ge location and sh ether-ctrl gigabitEthernet trace location.

Error Message     
 
    
    
   

%PLATFORM-ETHER_CTRL-4-XCVR_WARNING [chars] for port [dec] is disabled - [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    This is only a debug message. No action is required.

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 and 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 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. An ASIC driver does not come up properly. The %d is 0 ingressq, 1 egressq, 2 fabricq 0, 3 fabricq 1. The %d is the number of seconds elapsed.

Recommended Action    Investigate if the driver processes (ingressq, egressq or fabricq) are initialized properly.

Error Message     
 
    
    
   

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

Explanation    A problem was encountered during process initialization. The %s contains the explanation of the problem. The %s is the error description. The %d is the error code. The %s is the error code description.

Recommended Action    Restart the fabio_svr process. Contact TAC if the problem still exists.

Error Message     
 
    
    
   

%PLATFORM-FABIO-3-ERR_QAD_EGRESS_QUEUE_MISSING Failed to find necessary egress QAD queues [chars] ([chars])

Explanation    Failure to find the qad queue for egress packets occurred. This could cause applications using this qad queue to not send out packets. The %s is the QAD queue name. The %s is the 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    Failure to get the qad queue depth (number of packets in queue) occurred. This should be because of some issues with the indicated qad queue. The %p is the 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    Failure to get the qad notification of queue depth above or below watermark occurred. This normally indicates there is some issues with the qad queue. The %p is the 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    Failure to set the watermark of the indicated qad queue occurred. This should be because of some issues with the qad queue The %s is the high or low watermark. The %p is the 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    Failure to connect to netio pak server occurred.

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

Error Message     
 
    
    
   

%PLATFORM-FABIO-7-ERR_NULL_ARGS --

Explanation    Failure to create thread due to internal error occurred.

Recommended Action    Restart the fabio_svr process.

Error Message     
 
    
    
   

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

Explanation    Failure to send packets to the pdma queue. The %s is the error description. The %p is the QAD queue ID. The %d is 0 ingressq, 1 egressq, 2 fabricq 0, 3 fabricq 1. The %x is the 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. The %s is the error description. The %p is the QAD queue ID. The %d is 0 ingressq, 1 egressq, 2 fabricq 0, 3 fabricq 1. The %x is the 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 occurred.

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

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

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