The specified sensor type of the specified component on the specified blade server is in a non-recoverable state.



Alert Category

Blades (Critical) - mmTrapBladeC

Log Source


Automatically notify service




Example Message

Processor 1, temperature (CPU 1 OverTemp) non-recoverable

Alarm Panel LED (BC T and BC HT)


User response

Refer to the Problem Determination and Service Guide for the specified blade server to determine the device-specific actions to resolve this event. The Problem Determination and Service Guide is available on the Web.

If you do not have access to the Problem Determination and Service Guide, perform these steps:
  1. If the event is related to an over temperature condition:
    1. Check the room ambient temperature to ensure that it is within the operating specifications for the chassis.
    2. If an air filter is installed, make sure that it is cleaned or replaced.
    3. Make sure that all fan/blower modules are running. Replace fan modules if necessary.
    4. Make sure that a device or filler is installed in each bay in the front and rear of the chassis, and make sure that there is nothing covering the bays. Any missing components can cause a major reduction in airflow for the blade server.
  2. If the event is related to an over voltage condition:
    1. If the over voltage problem is occurring on all blade servers, look for other events in the log related to power and resolve those events. If the over voltage problem is occurring on all blade servers in the same power domain, the problem might be in one of the power modules that power that domain (log in to the advanced management module to see the power modules that are associated with each power domain). Replace the power modules, one at a time, to see if the problem is resolved.
    2. If no other blade server has this same problem, the issue is specific to the blade as a hardware or firmware problem. If the blade is still functioning the log can be ignored, but the blade should be monitored to see if the voltages get worse.
  3. Check the IBM Support Web page for any service bulletins that might be related to this problem.