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

Platform Messages

Table Of Contents

Platform Messages

PLAT_L2FIB_ATOM Messages

PLAT_L2FIB_DEBUG Messages

PLAT_L2FIB_LTRACE Messages

PLAT_L2FIB_RP Messages

PLAT_L2FIB Messages

REEP Messages

ROM_UPGRADE_LIB Messages

ROMMON_BURNER Messages

SCC Messages

SHELFMGR Messages

SPENET Messages

SPWD Messages

SQUID_LOADER Messages

STP_SHIM 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:

PLAT_L2FIB_ATOM Messages

PLAT_L2FIB_DEBUG Messages

PLAT_L2FIB_LTRACE Messages

PLAT_L2FIB_RP Messages

PLAT_L2FIB Messages

REEP Messages

ROM_UPGRADE_LIB Messages

ROMMON_BURNER Messages

SCC Messages

SHELFMGR Messages

SPENET Messages

SPWD Messages

SQUID_LOADER Messages

STP_SHIM Messages

PLAT_L2FIB_ATOM Messages

Error Message     
 
    
    
   

%PLATFORM-PLAT_L2FIB_ATOM-3-DEBUG_ERROR PLATFORM-L2FIB-ATOM: Error - [chars] [chars] [chars] [dec]

Explanation    Failed to initialize the debugging module in the platform L2FIB ATOM component.

Recommended Action    None, platform software will correct itself if this happens.

Error Message     
 
    
    
   

%PLATFORM-PLAT_L2FIB_ATOM-3-INIT_ERROR PLATFORM-L2FIB-ATOM: Error - [chars]

Explanation    Failed to initialize the ATOM module in the platform L2FIB ATOM component.

Recommended Action    None, platform software will correct itself if this happens.

Error Message     
 
    
    
   

%PLATFORM-PLAT_L2FIB_ATOM-3-LTRACE_ERROR PLATFORM-L2FIB-ATOM: Error - [chars] [dec] [chars] [dec]

Explanation    Failed to initialize the ltrace module in the platform L2FIB ATOM component.

Recommended Action    None, platform software will correct itself if this happens.

PLAT_L2FIB_DEBUG Messages

Error Message     
 
    
    
   

%PLATFORM-PLAT_L2FIB_DEBUG-3-REGISTER_FAILED PLATFORM-L2FIB: Error - [chars] [chars] [chars] [dec]

Explanation    Failed to initialize the debugging module in the platform L2FIB component.

Recommended Action    None, platform software will correct itself if this happens.

PLAT_L2FIB_LTRACE Messages

Error Message     
 
    
    
   

%PLATFORM-PLAT_L2FIB_LTRACE-3-ERR_INFO_VERBOSE PLATFORM-L2FIB: Ltrace Error - [chars] [dec] [chars] [chars] [dec]

Explanation    PLATFORM L2FIB, error information

Recommended Action    *SUPPORT*

PLAT_L2FIB_RP Messages

Error Message     
 
    
    
   

%PLATFORM-PLAT_L2FIB_RP-3-DEBUG_ERROR PLATFORM-L2FIB-RP: Error - [chars] [chars] [chars] [dec]

Explanation    Failed to initialize the debugging module in the platform L2FIB (D)RP component.

Recommended Action    None, platform software will correct itself if this happens.

PLAT_L2FIB Messages

Error Message     
 
    
    
   

%PLATFORM-PLAT_L2FIB-3-CERR_ERROR PLATFORM-L2FIB: Error - [chars] [chars] [chars] [dec]

Explanation    Failed to initialize the cerrno module in the platform L2FIB component.

Recommended Action    None, platform software will correct itself if this happens.

Error Message     
 
    
    
   

%PLATFORM-PLAT_L2FIB-3-DEBUG_ERROR PLATFORM-L2FIB: Error - [chars] [chars] [chars] [dec]

Explanation    Failed to initialize the debugging module in the platform L2FIB component.

Recommended Action    None, platform software will correct itself if this happens.

Error Message     
 
    
    
   

%PLATFORM-PLAT_L2FIB-3-HW_INIT_ERROR PLATFORM-L2FIB: Error - [chars] [chars] [chars] [dec]

Explanation    Failed to initialize the Platform LC Hardware in L2FIB component.

Recommended Action    None, platform software will correct itself if this happens.

Error Message     
 
    
    
   

%PLATFORM-PLAT_L2FIB-3-LTRACE_ERROR PLATFORM-L2FIB: Error - [chars] [chars] [chars] [dec]

Explanation    Failed to initialize the ltrace module in the platform L2FIB component.

Recommended Action    None, platform software will correct itself if this happens.

REEP Messages

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

Recommended Action    Check the board which had the failure.

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

Explanation    I2C service is currently unavailable.

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

Error Message     
 
    
    
   

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

Explanation    Failed to send reply to client ROMMON.

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

ROM_UPGRADE_LIB Messages

Error Message     
 
    
    
   

%PLATFORM-ROM_UPGRADE_LIB-7-ERROR [chars]

Explanation    --

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

ROMMON_BURNER Messages

Error Message     
 
    
    
   

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

Explanation    Bad coammand option.

Recommended Action    No action is required..

Error Message     
 
    
    
   

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

Explanation    Error occured with file operations.

Recommended Action    No action is required..

Error Message     
 
    
    
   

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

Explanation    No enough memory.

Recommended Action    No action is required..

Error Message     
 
    
    
   

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

Explanation    Output progress to RP console.

Recommended Action    No action is required..

Error Message     
 
    
    
   

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

Explanation    Invalid ROMMON version to RP console.

Recommended Action    No action is required..

SCC Messages

Error Message     
 
    
    
   

%PLATFORM-SCC-2-BAD_ID_HW Failed Identification Test in [chars] [[dec]/[dec]]
The module in [chars] in this router may not be a genuine Cisco product. Cisco warranties and support programs only apply to genuine Cisco products. If Cisco determines that your insertion of non-Cisco SPA cards or other modules into a Cisco product is the cause of a support issue, Cisco may deny support under your warranty or under a Cisco support program such as SmartNet.

Explanation    'Hardware in the specified location could not be identified as a genuine Cisco product'

Recommended Action    'Contact TAC'

Error Message     
 
    
    
   

%PLATFORM-SCC-2-FAILED_ID_HW Failed Identification Test in [chars] [[dec]/[dec]]

Explanation    'There was a problem while identifying Hardware in the specified location.'

Recommended Action    'Contact TAC'

Error Message     
 
    
    
   

%PLATFORM-SCC-2-PROTO_HW Module ([chars]) is a registered proto-type for Cisco Lab use only, and not certified for live network operation.

Explanation    'Hardware in the specified location is a proto-type module that came from a Cisco Lab'

Recommended Action    'Contact TAC'

SHELFMGR Messages

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-0-CHASSIS_SHUTDOWN CRITICAL: CHASSIS SHUTDOWN initiated due to [chars]

Explanation    Chassis is shutting down due to reason mentioned.

Recommended Action    Examine chassis based on above message. If chassis shutdown is due to low voltage on both power shelves, then please examine the battery and replace if necessary. Note that in all cases of shutdown, the chassis needs to be manually power cycled, or the RPs physically OIR'd so as to boot the chassis again.

Error Message     
 
    
    
   

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

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

Recommended Action    *None*

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-1-CLEAR_BOTH_FC_REMOVED Atleast one fan controller card has been inserted within 45 seconds (of removing both fan controller cards), so the chassis will not be shut down

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

Recommended Action    *None*

Error Message     
 
    
    
   

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

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

Recommended Action    Insert a fan tray within 45 seconds.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-1-SET_BOTH_FC_REMOVED Both fan controller cards have been shutdown or removed from the chassis. If at least one fan controller card is not inserted within 45 seconds, the chassis will be shutdown

Explanation    Software has detected that both fan controller cards have been removed from the chassis but, but gives user 45 seconds to insert atleast one of them back into the chassis. If no action is taken within 45 seconds, the chassis will be shut down.

Recommended Action    Insert a fan controller card within 45 seconds.

Error Message     
 
    
    
   

%PLATFORM-SHELFMGR-3-BOARD_NOT_SUPPORTED Shutdown node [chars] since CRS-DRP is not supported on CRS-4-CH

Explanation    This message indicates that the node is being shutdown because it is not supported on the CRS-4 platform.

Recommended Action    Remove the unsupported board and replace it with supported hardware.

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    RP is shutting down due to reason mentioned.

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

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

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

Explanation    Card seems warm reloaded successfully

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

Explanation    Card seems warm reloaded successfully

Recommended Action    No action is required.

SPENET Messages

Error Message     
 
    
    
   

%PLATFORM-SPENET-7-ERR_DEBUG [chars]

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

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

SPWD Messages

Error Message     
 
    
    
   

%PLATFORM-SPWD-0-ECC_REBOOT Excessive [chars] errors in last hour: [dec]. Node reboot scheduled

Explanation    Large numbers of single or mulitple bit ECC errors have been detected on the sp node in the past hour. The node will be rebooted.

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

Error Message     
 
    
    
   

%PLATFORM-SPWD-0-MACHINE_CHECK_REBOOT Excessive machine checks in last hour: [dec]. Node reboot scheduled

Explanation    The sp cpu has received an excessive number of machine check exceptions. The node will be rebooted.

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

Error Message     
 
    
    
   

%PLATFORM-SPWD-0-MISSED_WATCHDOG_REBOOT Multiple watchdog misses in last hour: [dec]. Node reboot scheduled

Explanation    The sp cpu has failed to service the hardware watchdog timer multiple times in the last hour. The node will be rebooted.

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

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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

SQUID_LOADER Messages

Error Message     
 
    
    
   

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

Explanation    Output progress to RP console.

Recommended Action    No action is required.

STP_SHIM Messages

Error Message     
 
    
    
   

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

Explanation    Spanning Tree Port's state change indication.

Recommended Action    No action is required.

Error Message     
 
    
    
   

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

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

Recommended Action    Do nothing

Error Message     
 
    
    
   

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

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

Recommended Action    Do nothing

Error Message     
 
    
    
   

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

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

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

Error Message     
 
    
    
   

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

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

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