Cisco IOS XR System Error Reference Guide for CRS-1 Router Platform Specific Messages, Release 3.3
Platform Messages
Downloads: This chapterpdf (PDF - 522.0KB) The complete bookPDF (PDF - 1.82MB) | Feedback

Platform Messages

Table Of Contents

Platform Messages

ALPHA_DISPLAY Messages

BCM_SWITCH Messages

CCTL Messages

CETHHA Messages

CPUCTRL_PCI Messages

CPUCTRL Messages

CPUCTRLLIB Messages

DISCOVERY Messages

DRP_PAIRING_CLIENT Messages

DRP_PAIRING Messages

DSCMEDIA Messages

EIO Messages

ENVMON_MON Messages

ENVMON Messages

ETH_SRVR Messages

HBAGENT Messages

HFR_IP_EA Messages

HFR_IPV6_EA Messages

HFR_LCPM_SHOW Messages

HFR_MPLS_EA Messages

HFR_PM_TEST Messages

HFR_PM Messages

HSR_ES_CLI Messages

I2C Messages

INV Messages

MBI_HELLO Messages

MBI_LIB_ACCESS Messages

MBI_LIB Messages

MBIMGR Messages

MSM Messages

OIRD Messages

PCTL Messages

PLAT_FIB_DBG Messages

PLAT_FIB_IDB_LIB Messages

PLAT_FIB_LTRACE Messages

PLAT_FIB_MPLS Messages

PLAT_FIB_RP Messages

PLAT_FIB Messages

PLAT_V4FIB Messages

PLAT_V6FIB_RP Messages

PLAT_V6FIB Messages

PLATFORM_HFR_LIB Messages

PLIM_16P_OC48 Messages

PLU Messages

PLUTLU Messages

port_cfg Messages

REEP Messages

ROM_UPGRADE_LIB Messages

ROMMON_BURNER Messages

SHELFMGR Messages

SPENET Messages

SPWD Messages

STP_SHIM Messages

WD Messages


Platform Messages


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

ALPHA_DISPLAY Messages

BCM_SWITCH Messages

CCTL Messages

CETHHA Messages

CPUCTRL_PCI Messages

CPUCTRL Messages

CPUCTRLLIB Messages

DISCOVERY Messages

DRP_PAIRING_CLIENT Messages

DRP_PAIRING Messages

DSCMEDIA Messages

EIO Messages

ENVMON_MON Messages

ENVMON Messages

ETH_SRVR Messages

HBAGENT Messages

HFR_IP_EA Messages

HFR_IPV6_EA Messages

HFR_LCPM_SHOW Messages

HFR_MPLS_EA Messages

HFR_PM_TEST Messages

HFR_PM Messages

HSR_ES_CLI Messages

I2C Messages

INV Messages

MBI_HELLO Messages

MBI_LIB_ACCESS Messages

MBI_LIB Messages

MBIMGR Messages

MSM Messages

OIRD Messages

PCTL Messages

PLAT_FIB_DBG Messages

PLAT_FIB_IDB_LIB Messages

PLAT_FIB_LTRACE Messages

PLAT_FIB_MPLS Messages

PLAT_FIB_RP Messages

PLAT_FIB Messages

PLAT_V4FIB Messages

PLAT_V6FIB_RP Messages

PLAT_V6FIB Messages

PLATFORM_HFR_LIB Messages

PLIM_16P_OC48 Messages

PLU Messages

PLUTLU Messages

port_cfg Messages

REEP Messages

ROM_UPGRADE_LIB Messages

ROMMON_BURNER Messages

SHELFMGR Messages

SPENET Messages

SPWD Messages

STP_SHIM Messages

WD Messages

ALPHA_DISPLAY Messages

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.

BCM_SWITCH Messages

Error Message     
 
    
    
   

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

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

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

CCTL Messages

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

Recommended Action    Please power off the chassis manually.

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

Explanation    Informational msg indicating temperature at which alarm occured.

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

Error Message     
 
    
    
   

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

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

Recommended Action    Debug message only. No action is required.

CETHHA Messages

Error Message     
 
    
    
   

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

Explanation    Hardware error on CPU control ethernet port.

Recommended Action    Remove/Replace the RP.

Error Message     
 
    
    
   

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

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

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

CPUCTRL_PCI Messages

Error Message     
 
    
    
   

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

Explanation    CPUCTRL PCI, this function has failed.

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

Error Message     
 
    
    
   

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

Explanation    CPUCTRL PCI, this function has failed.

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

Error Message     
 
    
    
   

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

Explanation    CPUCTRL PCI, event logging.

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    CPUCTRL PCI, event logging.

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    CPUCTRL PCI, event logging.

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    CPUCTRL PCI, event logging.

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    CPUCTRL PCI, event logging.

Recommended Action    No action is required.

CPUCTRL Messages

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

Explanation    Cpuctrl Event Manager create error

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

Error Message     
 
    
    
   

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

Explanation    Cpuctrl Event Manager notify error

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

Error Message     
 
    
    
   

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

Explanation    Cpuctrl Event Manager event block error

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

Error Message     
 
    
    
   

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

Explanation    Cpuctrl Sysdb Register EDM error

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

Error Message     
 
    
    
   

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

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

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

CPUCTRLLIB Messages

Error Message     
 
    
    
   

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

Explanation    The cpuctrl driver detected an error during packet DMA.

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

Error Message     
 
    
    
   

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

Explanation    CDMA ended in error.

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Port will not operate reliably

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

Error Message     
 
    
    
   

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

Explanation    Port will not operate reliably

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

Error Message     
 
    
    
   

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

Explanation    Port will not operate reliably

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

Error Message     
 
    
    
   

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

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

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

DISCOVERY Messages

Error Message     
 
    
    
   

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

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

Recommended Action    This is a critical error which will cause board-reset. Check if the board comes up fine after reload. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-DISCOVERY-4-SRAM_PARITY ASIC-ERR: SRAM error #[dec]: Description = [chars]

Explanation    Parity Error detected in SRAM.

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

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Details about the error seen in CPU module.

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Details on the device bus error.

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Information message from Discovery driver on software error condition.

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

Error Message     
 
    
    
   

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

Explanation    Details about the error observed on the PCI bus.

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Details about the ECC error happenned before.

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Details on SRAM parity error.

Recommended Action    No action is required.

DRP_PAIRING_CLIENT Messages

Error Message     
 
    
    
   

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

DSCMEDIA Messages

Error Message     
 
    
    
   

%PLATFORM-DSCMEDIA-3-ERR_EVM [chars] ; rc = [chars]

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

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

Error Message     
 
    
    
   

%PLATFORM-DSCMEDIA-3-ERR_NODEID [chars]; rc = [chars]

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

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

Error Message     
 
    
    
   

%PLATFORM-DSCMEDIA-3-ERR_TRANSPORT [chars]

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

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

Error Message     
 
    
    
   

%PLATFORM-DSCMEDIA-4-ERR_THREAD_MUTEX_LOCK [chars] ; rc = [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 = [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.

EIO Messages

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

Recommended Action    Use the following CLI to make sure the link is properly trained. - show controller eio links all loc If this problem is seen consistently, Run the field diags on the board. If it is possible to isolate the trigger point for this failure, collect all the necessary info (condition) that caused the error. Reload the MSC to avoid inconsistent behavior of the system If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

%PLATFORM-EIO-7-ERR_LWM_SEND EIO library failed to send message; rc = [chars], exiting...

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

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

Error Message     
 
    
    
   

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

Explanation    The EIO library was unable to allocate memory.

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

Error Message     
 
    
    
   

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

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

Recommended Action    Run diags on the board. If it is possible to isolate the trigger point for the read failure, collect all the necessary info (condition) that caused the error. Reload the MSC to avoid inconsistent behavior of the system because of this read failure. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

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

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

Recommended Action    Run diags on the board. If it is possible to isolate the trigger point for this failure, collect all the necessary info (condition) that caused the error. Reload the MSC to avoid inconsistent behavior of the system because of this failure. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

ENVMON_MON Messages

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

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

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

ENVMON Messages

Error Message     
 
    
    
   

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

Explanation    An alarm has occured.

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    A previously occured alarm has been cleared.

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

ETH_SRVR Messages

Error Message     
 
    
    
   

%PLATFORM-ETH_SRVR-3-NODE_DOWN Received poison pill ... taking node down

Explanation    Ethernet driver received an unknown for us packet.

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

Explanation    Ethernet driver received an unknown for us packet.

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

HBAGENT Messages

Error Message     
 
    
    
   

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

Explanation    Fatal internal error.

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

HFR_IP_EA Messages

Error Message     
 
    
    
   

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

Explanation    HFR IP-EA, Critical error

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

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

Explanation    HFR IP-EA, error

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

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

Explanation    HFR IP-EA, error

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

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

Explanation    HFR IP-EA, Debug information

Recommended Action    *SUPPORT*

HFR_IPV6_EA Messages

Error Message     
 
    
    
   

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

Explanation    HFR IP-EA, Critical error

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

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

Explanation    HFR IP-EA, error

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

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

Explanation    HFR IP-EA, error

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

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

Explanation    HFR IP-EA, Debug information

Recommended Action    *SUPPORT*

HFR_LCPM_SHOW Messages

Error Message     
 
    
    
   

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

Explanation    HFR_PM_SHOW encountered an error

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

Error Message     
 
    
    
   

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

Explanation    Startup option supplied to HFR_PM_SHOW is not valid.

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

HFR_MPLS_EA Messages

Error Message     
 
    
    
   

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

Explanation    CRS-1 MPLS-EA, error

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

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

Explanation    CRS-1 MPLS-EA, error

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

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

Explanation    CRS-1 MPLS-EA, Debug information

Recommended Action    *SUPPORT*

HFR_PM_TEST Messages

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

HFR_PM Messages

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

Explanation    Platform Manager encountered a fatal memory allocation error

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

Explanation    The Platform Manager encountered an internal software error.

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

Error Message     
 
    
    
   

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

Explanation    The Platform Manager encountered an internal software initialization error.

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

HSR_ES_CLI Messages

Error Message     
 
    
    
   

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

Explanation    Failed to load capsulation DLL

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

Explanation    Unknwn message code send by Pakman server

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

Error Message     
 
    
    
   

%PLATFORM-HSR_ES_CLI-6-INFO [chars]

Explanation    Prints an informational statement

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

I2C Messages

Error Message     
 
    
    
   

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

Explanation    None

Recommended Action    Replace the bad part for LC to work.

Error Message     
 
    
    
   

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

Explanation    None

Recommended Action    Check why the board is not yet powered.

Error Message     
 
    
    
   

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

Explanation    None

Recommended Action    Check why the board is not yet powered.

Error Message     
 
    
    
   

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

Explanation    None

Recommended Action    Replace the bad part for LC to work.

Error Message     
 
    
    
   

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

Explanation    None

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

Error Message     
 
    
    
   

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

Explanation    None

Recommended Action    Check the path of file specified for download

INV Messages

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-INV-7-ERR [chars]

Explanation    Failure in Inventory Manager resulting in error condition

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Failure in Inventory Manager dllmain function call

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Failure in Inventory Manager event creation

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Failure in Inventory Manager event connect open

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Failure in Inventory Manager memory allocation error occurred

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    The RACK entry is a must in inventory management

Recommended Action    None. Inventory Manager process will restart automatically

MBI_HELLO Messages

Error Message     
 
    
    
   

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

Explanation    Fatal internal error.

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

Explanation    Failed to request netmgr mountpoint.

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

Explanation    Timer timed out.

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

MBI_LIB_ACCESS Messages

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

MBI_LIB Messages

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

MBIMGR Messages

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

%PLATFORM-MBIMGR-3-UNKNOWN_BOARDTYPE [chars]An unknown boardtype ([dec]) was passed to the MBI infrastructure.

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

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

Error Message     
 
    
    
   

%PLATFORM-MBIMGR-4-REMOTE_NODEID_MSG_STR_CREATE_FAIL The MBI infrastructure failed to create a message string for a remote location ([dec]), error: [chars]. Error messages from the MBI infrastructure will not contain the prefix-string that represents the remote location being processed.

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

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

Error Message     
 
    
    
   

%PLATFORM-MBIMGR-6-MBIVSN_DIGIT_INFO MBIMGR: [chars] ([dec])

Explanation    MBI Mgr general info

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-MBIMGR-6-MBIVSN_STR_INFO MBIMGR: [chars] ([chars])

Explanation    MBI Mgr general info

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-MBIMGR-7-IMAGE_VALIDATED [chars]: MBI [chars] validated

Explanation    A message to indicate which MBI was validated for which location.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-MBIMGR-7-INVALID_MBIVSN [chars]Invalid MBI spec passed in ([chars]): [chars]

Explanation    A problem was found in the MBI spec that was passed in.

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

MSM Messages

Error Message     
 
    
    
   

%PLATFORM-MSM-3-ERR [chars], [chars], err = [hex]

Explanation    Failure in Multishelf Manager.

Recommended Action    No action is required.

OIRD Messages

Error Message     
 
    
    
   

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

Explanation    Detected a card is inserted into the chassis.

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

Error Message     
 
    
    
   

%PLATFORM-OIRD-5-OIROUT OIR: Node [chars] removed

Explanation    Detected a card is removed from the chassis.

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

Error Message     
 
    
    
   

%PLATFORM-OIRD-7-ASYNC_ATTACH_FAIL Failed to attach handler for async events: [chars]

Explanation    Failed to attach handler for async events.

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

Error Message     
 
    
    
   

%PLATFORM-OIRD-7-ASYNC_MSG_ERROR Received unexpected message: [dec]

Explanation    Received unexpected async message type.

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

Error Message     
 
    
    
   

%PLATFORM-OIRD-7-CHKPT_FAIL Failed to perform checkpoint services: [chars]

Explanation    Failed to perform checkpoint service functions.

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

Error Message     
 
    
    
   

%PLATFORM-OIRD-7-EVM_CREATE_FAIL Failed to create event manager: [chars]

Explanation    Failed to create event manager.

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

Error Message     
 
    
    
   

%PLATFORM-OIRD-7-MMAP_FAIL Failed to map OIR registers to process space

Explanation    Failed to mmap OIR registers.

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

Error Message     
 
    
    
   

%PLATFORM-OIRD-7-MSG_ATTACH_FAIL Failed to attach handler for sync events: [chars]

Explanation    Failed to attach handler for sync events.

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

Error Message     
 
    
    
   

%PLATFORM-OIRD-7-MSG_CHAN_CONN_FAIL Failed to connect to message channel: [chars]

Explanation    Failed to attach handler for sync messages.

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

Error Message     
 
    
    
   

%PLATFORM-OIRD-7-MSG_ERROR Received unexpected message : [chars]

Explanation    Received unexpected message.

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

Error Message     
 
    
    
   

%PLATFORM-OIRD-7-THREAD_CREATE_FAIL Failed to create thread [chars]

Explanation    Failed to create threads.

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

Error Message     
 
    
    
   

%PLATFORM-OIRD-7-TIMER_CREATE_FAIL Failed to create timer: [chars]

Explanation    Failed to create timer.

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

Error Message     
 
    
    
   

%PLATFORM-OIRD-7-TIMER_INIT_FAIL Failed to init timer events: [chars]

Explanation    Failed to init timer events.

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

Error Message     
 
    
    
   

%PLATFORM-OIRD-7-UNEXPECTED Unexpected: [chars]: [chars]

Explanation    An unexpected condition encountered. This is not necessarily an error, but may help with debugging other problems elsewhere!

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

PCTL Messages

Error Message     
 
    
    
   

%PLATFORM-PCTL-3-gsp_msg_failed Failure to notify node state when [chars]: [chars]

Explanation    The internal communication channel among pctl threads is broken.

Recommended Action    Must restart the process.

PLAT_FIB_DBG Messages

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_DBG-3-ERR_INFO_VERBOSE PLATFORM-FIB: Error - [chars] [chars] [chars] [dec]

Explanation    PLATFORM FIB, error information

Recommended Action    *SUPPORT*

PLAT_FIB_IDB_LIB Messages

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_IDB_LIB-3-ERR_INFO PLATFORM-FIB: Error - [chars] [dec]

Explanation    PLATFORM FIB, error information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_IDB_LIB-3-ERR_STR PLATFORM-FIB: Error - [chars]: [chars]([unsigned int])

Explanation    PLATFORM FIB, error information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_IDB_LIB-3-ERROR PLATFORM-FIB: Error - [chars]

Explanation    PLATFORM FIB, error

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_IDB_LIB-6-INFO PLATFORM-FIB: [chars]

Explanation    PLATFORM FIB, Information

Recommended Action    *SUPPORT*

PLAT_FIB_LTRACE Messages

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_LTRACE-3-ERR_INFO_VERBOSE PLATFORM-FIB: Error - [chars] [dec] [chars] [chars] [dec]

Explanation    PLATFORM FIB, error information

Recommended Action    *SUPPORT

PLAT_FIB_MPLS Messages

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-2-CRITICAL [chars]

Explanation    PLATFORM FIB, Critical error

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-2-CRITICAL [chars]

Explanation    PLATFORM FIB, Critical error

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-2-CRITICAL_INFO [chars] [dec]

Explanation    PLATFORM FIB, Critical error information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-2-CRITICAL_INFO [chars] [dec]

Explanation    PLATFORM FIB, Critical error information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-3-ERR_DETAIL [chars] [hex], [chars] [dec], [chars]([dec])

Explanation    PLATFORM FIB, error information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

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

Explanation    PLATFORM FIB, error information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

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

Explanation    PLATFORM FIB, error information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-3-ERR_STR [chars] [chars]([dec])

Explanation    PLATFORM FIB, error information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-3-ERR_STR [chars] [chars]([dec])

Explanation    PLATFORM FIB, error information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-3-ERROR [chars]

Explanation    PLATFORM FIB, error

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-3-ERROR [chars]

Explanation    PLATFORM FIB, error

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-3-SHMEM Shared memory [chars], window: [dec] [hex] [chars]

Explanation    PLATFORM FIB, Shared memory errors

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-3-SHMEM Shared memory [chars], window: [dec] [hex] [chars]

Explanation    PLATFORM FIB, Shared memory errors

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-4-WARNING [chars]

Explanation    PLATFORM FIB, Warning

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-4-WARNING [chars]

Explanation    PLATFORM FIB, Warning

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-4-WARNING_INFO [chars] [dec]

Explanation    PLATFORM FIB, Warning information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-4-WARNING_INFO [chars] [dec]

Explanation    PLATFORM FIB, Warning information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-6-INFO [chars]

Explanation    PLATFORM FIB, Information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_MPLS-6-INFO [chars]

Explanation    PLATFORM FIB, Information

Recommended Action    *SUPPORT*

PLAT_FIB_RP Messages

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_RP-3-ERR_INFO PLATFORM-FIB-RP: Error - [chars] [dec]

Explanation    PLATFORM FIB, error information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_RP-3-ERR_INFO_VERBOSE PLATFORM-FIB-RP: Error - [chars] [chars] [chars] [dec]

Explanation    PLATFORM FIB, error information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB_RP-3-ERROR PLATFORM-FIB-RP: Error - [chars]

Explanation    PLATFORM FIB, error

Recommended Action    *SUPPORT*

PLAT_FIB Messages

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB-3-ERR_INFO PLATFORM-FIB: Error - [chars] [dec]

Explanation    PLATFORM FIB, error information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB-3-ERR_STR PLATFORM-FIB: Error - [chars]: [chars]([unsigned int])

Explanation    PLATFORM FIB, error information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB-3-ERROR PLATFORM-FIB: Error - [chars]

Explanation    PLATFORM FIB, error

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_FIB-6-INFO PLATFORM-FIB: [chars]

Explanation    PLATFORM FIB, Information

Recommended Action    *SUPPORT*

PLAT_V4FIB Messages

Error Message     
 
    
    
   

%PLATFORM-PLAT_V4FIB-3-ERR_INFO PLATFORM-FIB-IPV4: Error - [chars] [dec]

Explanation    Platform IPv4 FIB, Error information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_V4FIB-3-ERR_STR PLATFORM-FIB-IPV4: Error - [chars], [chars] ([unsigned int])

Explanation    Platform IPv4 FIB, Error string information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_V4FIB-3-ERROR PLATFORM-FIB-IPV4: Error - [chars]

Explanation    Platform IPv4 FIB, Error

Recommended Action    *SUPPORT*

PLAT_V6FIB_RP Messages

Error Message     
 
    
    
   

%PLATFORM-PLAT_V6FIB_RP-3-ERR_INFO PLATFORM-FIB-IPV6: [chars] [dec]

Explanation    Platform IPv6 FIB, Error information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_V6FIB_RP-3-ERR_INFO_VERBOSE PLATFORM-FIB-IPV6: [chars] [chars] [chars] [dec]

Explanation    Platform IPv6 FIB, Error information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_V6FIB_RP-3-ERROR PLATFORM-FIB-IPV6: [chars]

Explanation    Platform IPv6 FIB, Error

Recommended Action    *SUPPORT*

PLAT_V6FIB Messages

Error Message     
 
    
    
   

%PLATFORM-PLAT_V6FIB-3-ERR_INFO PLATFORM-FIB-IPV6: Error - [chars] [dec]

Explanation    Platform IPv6 FIB, Error information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_V6FIB-3-ERR_INFO_VERBOSE PLATFORM-FIB-IPV6: Error - [chars] [chars] [chars] [dec]

Explanation    Platform IPv6 FIB, Error information

Recommended Action    *SUPPORT*

Error Message     
 
    
    
   

%PLATFORM-PLAT_V6FIB-3-ERROR PLATFORM-FIB-IPV6: Error - [chars]

Explanation    Platform IPv6 FIB, Error

Recommended Action    *SUPPORT*

PLATFORM_HFR_LIB Messages

Error Message     
 
    
    
   

%PLATFORM-PLATFORM_HFR_LIB-7-AM_I_SC_ERROR Failed to detect hardware board type. Reason: [chars].

Explanation    The platform library service call to find the hardware module type has failed. The calling application handles it appropriately.

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

PLIM_16P_OC48 Messages

Error Message     
 
    
    
   

%PLATFORM-PLIM_16P_OC48-6-OIM_OIR Optic Interface Module [chars] for port [dec]

Explanation    The Optic Interface Module (OIM) for the specified port has either been inserted or removed.

Recommended Action    No action is required.

PLU Messages

Error Message     
 
    
    
   

%PLATFORM-PLU-4-ERR_CORRECTED Hardware Table [dec] consistency restored

Explanation    Errors have been corrected.

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

Error Message     
 
    
    
   

%PLATFORM-PLU-4-ERR_NOTIFY Hardware Table [dec] may be inconsistent. Attempting correction every [dec] seconds

Explanation    Errors were encountered trying to program hardware tables, forwarding on some entries may be affected, periodic error correction will be attempted.

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

PLUTLU Messages

Error Message     
 
    
    
   

%PLATFORM-PLUTLU-4-COMPACT_INSUFF_PGS Warning [chars] - (direc [dec] table [dec], chan [dec])

Explanation    'Periodically a compaction process ensures that fragmented memory is returned back to the free pool and a new chunk of memory holds the trie, the new chunk will not be as fragmented as the old one might be which leads to a substantial saving in memory. This is done by building a new trie, by allocating a fresh chunk of memory and then freeing the memory that the old trie resides in. The message indicates that we tried to build the new trie without reserving enough memory first. This is harmless by itself because the reserve request is supposed to be an accurate estimate but not perfect so when a request for memory comes in beyond what has been reserved the new memory will be allocated if available. If not available then we enter a loop that we can't recover from without freeing memory in other tries. A warning message is logged to track this error.

Recommended Action    'Verify that the table isn't inconsistent. A message appears saying so if the table is inconsistent. If not inconsistent then the system is functioning fine, however do provide the output of the message back to cisco-support for further debugging'

Error Message     
 
    
    
   

%PLATFORM-PLUTLU-4-ERR_RESTART_FAILED Failed to restart forwarding on metro

Explanation    An error was encountered while trying to restart forwarding on metro

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

Error Message     
 
    
    
   

%PLATFORM-PLUTLU-4-REPL_MODE_FAILED Failed to modify replication mode

Explanation    An error was encountered while trying to modify replication mode on metro

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

port_cfg Messages

Error Message     
 
    
    
   

%PLATFORM-port_cfg-3-INIT failed to initialize [chars]: [chars]

Explanation    A submodule was unable to initialze due to the specified error

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

REEP Messages

Error Message     
 
    
    
   

%PLATFORM-REEP-3-ERROR_OPENING_ETHERNET_CONNECTION Failed to open connection to control ethernet server. Err = [chars]

Explanation    The control ethernet transport connection has been lost due to which send/receive for this process over the control ethernet will not work. This impacts standby RP booting.

Recommended Action    If this message is seen persistently, please capture output of 'show process eth_server' and 'show controllers backplane ethernet trace'.

Error Message     
 
    
    
   

%PLATFORM-REEP-3-GET_BOARD_TYPE_FAILED Platform call to determine boardtype failed

Explanation    This is indicative of some very fundamental problem in the the system. Some very basic system initialization has failed.

Recommended Action    Check the board which had the failure.

Error Message     
 
    
    
   

%PLATFORM-REEP-3-I2C_BKPLANE_READ_FAILED I2C access to read backplane EEPROM failed

Explanation    This is indicative of some very fundamental problem in the the system. I2C access to the backplane not working could be due to an I2C hang.

Recommended Action    Gather all the console logs and the i2c trace.

Error Message     
 
    
    
   

%PLATFORM-REEP-3-I2C_SERVER_CONNECT_FAILED Failed to connect to I2C server

Explanation    I2C service is currently unavailable.

Recommended Action    If this condition persists, it will preclude the standby route processor card in that chassis from coming up. So if it is seen persistently, please check the status of the i2c_server process on the active RP.

Error Message     
 
    
    
   

%PLATFORM-REEP-7-REPLY_SEND_FAILED Failed to send reply. Err = [dec]

Explanation    Failed to send reply to client ROMMON.

Recommended Action    Transient occurrence of this message is possible. If this message is seen persistently, and either an MSC, DRP or standby RP is not booting, it is because the control network connectivity service on this node is malfunctioning.

ROM_UPGRADE_LIB Messages

Error Message     
 
    
    
   

%PLATFORM-ROM_UPGRADE_LIB-7-ERROR [chars]

Explanation    --

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

ROMMON_BURNER Messages

Error Message     
 
    
    
   

%PLATFORM-ROMMON_BURNER-3-BAD_ARG Bad command option: [chars] [chars]

Explanation    Bad coammand option.

Recommended Action    No action is required..

Error Message     
 
    
    
   

%PLATFORM-ROMMON_BURNER-3-FILE_OP_ERR [chars]: [chars] in function [chars] at line [dec]

Explanation    Error occured with file operations.

Recommended Action    No action is required..

Error Message     
 
    
    
   

%PLATFORM-ROMMON_BURNER-3-NO_MEM Failed in allocating memory in function [chars] at line [dec]

Explanation    No enough memory.

Recommended Action    No action is required..

Error Message     
 
    
    
   

%PLATFORM-ROMMON_BURNER-5-progress [chars] [chars]

Explanation    Output progress to RP console.

Recommended Action    No action is required..

Error Message     
 
    
    
   

%PLATFORM-ROMMON_BURNER-5-version ROMMON version [dec].[dec] is not supported for this board.

Explanation    Invalid ROMMON version to RP console.

Recommended Action    No action is required..

SHELFMGR Messages

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-1-CLEAR_BOTH_FANTRAYS_REMOVED Atleast one tray has been inserted within 45 seconds (of removing both trays), so the chassis will not be shut down

Explanation    Software has detected that both fan trays were removed which would have shut down the system. But one fan tray was put back within 45 seconds, thus removing the need to shut down the system.

Recommended Action    *None*

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-1-PARTIAL_CHASSIS_SHUTDOWN_POWERUP [chars] linecards and fabric cards due to low voltage warning [chars] from power shelves

Explanation    Received message from environment monitor that the voltage is low on the power shelves. So we are shutting down linecards and fabric cards to prevent damage to these boards.

Recommended Action    Examine chassis and replace battery or power-shelf.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-1-SET_BOTH_FANTRAYS_REMOVED Both fan trays have been removed from the chassis. If at least one tray is not inserted within 45 seconds, the chassis will be shutdown

Explanation    Software has detected that both fan trays have been removed from the chassisbut, but gives user 45 seconds to insert another tray. If no action is taken within 45 seconds, the chassis will be shut down.

Recommended Action    Insert a fan tray within 45 seconds.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-EMPTY_SERIAL_FAIL_BOOT Received boot request from a RP with an empty rack serial number, which indicates an attempt to boot a RP with ROMMON v1.19x as the standby. Boot request is being failed ! Refer to customer documentation for configuring a boot override

Explanation    Shelfmgr is failing a boot request because the serial number string in the boot request is empty. This happens if a RP with ROMMON 1.19x or older is sending a boot request.

Recommended Action    Please upgrade the booting RP to the latest recommended ROMMON.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-FAILED_LOAD Node [chars] fails to load IOS XR image, request to reset ...

Explanation    This message indicates that the node failed to load the IOS XR image for maximum number of retries and will be reset.

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

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-FAILEDPOWERUP Unable to power up slot [chars], request to reset. reason: [chars]

Explanation    This message indicates the board in named slot failed to power up. The node will be reloaded automatically.

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

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-FSMTIMEOUT_RESET Node [chars] is reset due to failed bootup

Explanation    This message indicates that the node is not able to boot up

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

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-INRESET_ALARM Power off node [chars] due to multiple critial alarms, putting into IN_RESET state

Explanation    This message indicates that the node has being brought down to IN_RESET state due to multiple critical alarms.

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

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-INRESET_BRINGDOWN Cannot boot node [chars] due to multiple resets, putting into IN_RESET state

Explanation    This message indicates that the node has reached maximum number of resets allowed, therefore, it is brought down to IN_RESET state.

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

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-NODE_RESET_ALARM Node [chars] in critical alarms, request to reset ...

Explanation    This message indicates that the Shelf Manager or Platform Manager encountered a critical alarm for the node specified. It will attempt to reset the board which sends the alarm.

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

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-NODE_RESET_BRINGDOWN Reset node [chars] due to heartbeat loss

Explanation    This message indicates that the node is being reset because it failed to detect heartbeat pulses.

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

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-POWERDOWN_RESET Node [chars] is powered off due to admin power off request

Explanation    This message indicates that the node will be reset because user has administratively 'power disable' or 'no power disable' the node.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-POWERRELOAD_RESET Node [chars] is reset through power off, then power on

Explanation    This message indicates that the node is being reloaded because of a critical environmental alarm.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-RP_SHUTDOWN RP SHUTDOWN INITIATED due to thermal alarms

Explanation    RP is shutting down due to reason mentioned.

Recommended Action    If there is a standby RP in the router, failover will automatically occur. Otherwise, chassis will be brought down and a manual reboot will be neccessary.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-SHUTDOWN Node [chars] is shutdown due to a critical alarm

Explanation    This message indicates that the node will be brought down because a critical environmental alarm occured.

Recommended Action    Check air-flow, fan trays, and make sure that chassis is well-cooled. Manually boot up the node once the chassis has been checked.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-SHUTDOWN_RESET Node [chars] is reset due to admin shut/no shut request

Explanation    This message indicates that the node will be reset because user has administratively 'shutdown' or 'no shutdown' the node.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-UNKNOWN_BOARD Boot request from node [chars] contains invalid board type, This board is being shutdown

Explanation    This message indicates that the board type cannot be recognized, therefore, the node will not be able to boot up. This usually caused by an invalid eeprom content.

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

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-4-CMDLINE_BOOT_OVERRIDE_ENABLED Command line boot override to permit RPs with ROMMON 1.19x to boot as the standby has been enabled

Explanation    This is a warning message to indicate that using '-o override' option while booting the image, the operator will override the default IOS XR behavior which blocks the RP with ROMMON version v1.19x from coming up as the standby.

Recommended Action    Please upgrade the booting RP to the latest recommended ROMMON.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-4-EMPTY_SERIAL_BOOT_OVERRIDE WARNING !!! WARNING !!! Received boot request from a RP with an empty rack serial number. Permitting RP to boot due to [chars] override. Please upgrade RP ROMMON to latest recommended version

Explanation    This informational message informs the user that the Shelfmgr discovered an empty serial number due to an older ROMMON format, but it will allow the RP to boot because the operator had configured to override the restriction of disallow booting a RP with empty serial number.

Recommended Action    Please upgrade the booting RP to the latest recommended ROMMON.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-4-WARM_RLD_FAILED Receive MBI_HELLO from [chars], while waiting for MBI_HELLO_WARM

Explanation    Card seems to have been cold reloaded after an attempt to warm reload the card.

Recommended Action    Capture the shelfmgr log and use the 'show shelfmgr trace' CLI in admin-mode to fetch debug information. Also capture sysmgr_nv.log from LC.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-6-NO_PLIM Can not power on node [chars] due to absence of PLIM

Explanation    This message informs the user that the linecard will not be powered on because there is no PLIM inserted.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-6-NODE_NORESET Node [chars] is in NMON state, Cancel reset request

Explanation    This message indicates that the reset request caused by a critical alarm or heartbeat loss will not take effect because the node is being put in NMON state.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-6-NOREASON_RESET Node [chars] is reset due to UNKNOWN reason

Explanation    This message indicates that the node has been reset but the cause is unknown.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-6-USER_RESET Node [chars] is reset due to user reload request

Explanation    This message indicates that the node will be reset because user has requested to reload the node.

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-6-WARM_RLD_JUMP Receive MBI_HELLO_ENA from [chars] at [WARM-RLD], status jumped to IOX-RUN

Explanation    Card comes up without MBI_HELLO or MBI_HELLO_WARM, need to check warm-reload is really done successfully.

Recommended Action    Initiate 'show warm-reload detail location ' and check Successful Attempts variables. If one of them is not zero, warm-reload is succeeded. Else, capture the shelfmgr log and use the 'show shelfmgr trace' CLI in admin-mode to fetch debug information. Also capture sysmgr.log and sysmgr_nv.log from LC.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-7-WARM_RLD_FO Receive MBI_HELLO_WARM from [chars] at [Present], LC seems to be under warm-reload

Explanation    Card seems warm reloaded successfully

Recommended Action    No action is required.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-7-WARM_RLD_OK Receive MBI_HELLO_WARM from [chars], new processes are coming up

Explanation    Card seems warm reloaded successfully

Recommended Action    No action is required.

SPENET Messages

Error Message     
 
    
    
   

%PLATFORM-SPENET-7-ERR_DEBUG [chars]

Explanation    Internal error while receiving a packet over the control network on to the service processor. Error is harmless if only one or two are seen. If seen in a persistent manner, call support.

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

SPWD Messages

Error Message     
 
    
    
   

%PLATFORM-SPWD-4-MACHINE_CHECK Current counts: machine checks: [dec], single bit ECC [dec], multibit ECC [dec], missed watchdogs: [dec]. Cumulative counts: machine checks: [dec], single bit ECC [dec], multibit ECC: [dec], watchdogs: [dec]

Explanation    The sp cpu has received a machine check exception. This can be due because the software has failed to service the watchdog timer, or because of excessive ECC errors.

Recommended Action    Examine the error counts for indications as to the cause of the machine check. Excessive machine checks will cause the sp to reset.

Error Message     
 
    
    
   

%PLATFORM-SPWD-6-HOURLY_COUNTS Hourly summary of watchdog counts: watchdog misses: [dec], single bit ECC errors: [dec], multiple bit ECC errors: [dec], machine check count: [dec].

Explanation    If the watchdog process detects a missed watchdog, single or multiple bit ecc error, or a machine check exception in the last hour, this message and a summary of error counts is printed.

Recommended Action    Contact support if this message is seen more than once a day.

STP_SHIM Messages

Error Message     
 
    
    
   

%PLATFORM-STP_SHIM-6-COPY_FAILED Copying of log file to [chars] failed. err = [dec], status = [dec]. Restarting to recover.

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

Recommended Action    Do nothing

Error Message     
 
    
    
   

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

Explanation    Spanning Tree Port's state change indication.

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

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

Recommended Action    Do nothing

Error Message     
 
    
    
   

%PLATFORM-STP_SHIM-7-DRV_ERR [chars], [dec]

Explanation    Error condition from switch driver which may affect spanning tree operation on control ethernet. Normally spanning tree can tolerate a few of these errors as long as the driver comes back to a good state. Large number of these messages can indicate bad health of control-ethernet.

Recommended Action    Check if the switch driver process 'bcm_process' is up and running. If the message recurs, copy the error message exactly as it appears on the console or in the system log, call your Cisco technical support representative and provide the representative with the gathered information.

Error Message     
 
    
    
   

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

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

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

WD Messages

Error Message     
 
    
    
   

%PLATFORM-WD-4-INTERRUPT Watchdog interrupt: [dec], total in last hour: [dec]

Explanation    The cpu has received an interrupt from the watchdog timer. This indicates that the cpu was too busy to service the watchdog timer for a period of time in the recent past. The interrupt was handled and the timer serviced. Excessive watchdog interrupts will result in the node being reset. The number of interrupts since the cpu last serviced the watchdog and the total number of interrupts since the hourly timer was last cleared are displayed.

Recommended Action    Determine the reason for the watchdog timer expiring. Possible causes include a process spinning at high priority or hardware interrupts flooding the cpu.

Error Message     
 
    
    
   

%PLATFORM-WD-6-HOURLY_COUNT Hourly summary of watchdog interrupts: watchdog interrupts: [dec].

Explanation    This message is displayed once an hour if a watchdog interrupt is seen by the cpu. The count displayed is since the hourly counter was last cleared.

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