In the OEM Console The Value Of FAN Sensor State Is "ns"

Asset ID:	1-72-1459739.1
Update Date:	2012-09-26
Keywords:

Solution Type Problem Resolution Sure

Solution 1459739.1 : In the OEM Console The Value Of FAN Sensor State Is "ns"

Applies to:

Exadata Database Machine X2-2 Full Rack - Version All Versions to All Versions [Release All Releases]
Information in this document applies to any platform.
In OEM console the plugin reports a value of FAN Sensor State as "ns" (see attachment)

Symptoms

In the Exadata ILOM , the OEM console value of the FAN Sensor State is "ns".

For your machine There are only 4 fan modules in this type of server and all tacho readings are within specification.

The "OEM console" output as displayed in this SR is looking for 7 Fan modules distributed over 2 fan boards (FB1 and FB0).

This is the configuration of a different server (x4170 as opposed to a X4170 M2).
This display shows 4 good fan modules(FM) and 3 in state "ns" and X4170 M2 server only has 4 fan modules

So for the moment you can ignore the 3 'ns' fans.

If you see less than 4 fans with good tacho readings you should raise an Oracle Service Request.

If you start seeing 7 fan modules again you can run the procedure supplied to correct the configuration.

Cause

This is related to <Bug :11853101> - ILOM PLUGIN DOESN'T READ FAN SENSOR CORRECTLY

Solution

Upgrade to 12.1.0.2 GC or later which is available now. The problem is fixed in this release and above.

Or use this workaround:

8.0 Updating the SDR Cache File

The plug-in includes a Sensor Device Record (SDR) cache file to improve performance when requesting information from the Service Processor.
In is unlikely this cache will need to be updated, but the following procedure can be used at any time to refresh the sdr cache file.
A Service Processor firmware update which includes support for certain new hardware, such as a raid cards containing additional fans, would
require an sdr cache refresh. Run the following commands as the oracle Grid Control agent user:

a) Locate the existing cache file under the agent home:

% cd [Agent Home]/sysman/admin/scripts/emx/oracle_x2cn

% ls x2_cn_sdr.sdrx2_cn_sdr.sdr

b) Create a new cache file in the /var/tmp directory:

% ipmitool -I lan -H [SP Host name] -U oemuser -P oempasswd -L USER sdr dump /var/tmp/x2_cn_sdr.sdr

c) Use the new cache to verify it was dumped properly:

% ipmitool -I lan -H [SP Host name] -U oemuser -P oempasswd -L USER -S /var/tmp/x2_cn_sdr.sdr sel list last 20

d) Move the new cache file into the oracle_x2cn directory:

% cp oracle_x2cn oracle_x2cn.old

% mv /var/tmp/x2_cn_sdr.sdr [Agent Home]/sysman/admin/scripts/emx/oracle_x2cn

Attachments

This solution has no attachment