Server Fan Failure Alarm on T1200 EPAP Server.

Asset ID:	1-71-1914129.1
Update Date:	2016-08-15
Keywords:

Solution Type Technical Instruction Sure

Solution 1914129.1 : Server Fan Failure Alarm on T1200 EPAP Server.

Applies to:

Oracle Communications EAGLE (Hardware) - Version EPAP 13.0 and later
Information in this document applies to any platform.

Goal

FAN Alarm on EPAP - B (T1200) Server.

fan: FAILURE:: MAJOR::3000000000000001 -- Server Fan Failure

Solution

On a T1200 Server the following FAN alarm (in syscheck -v) reporting RPM is too low is being observed
Many a times this is a False alarm and can be cleared.

         fan: Checking Status of Server Fans.
         fan: Fan is OK. IPMI,Fan 1A: 16905.000 RPM (min = 4761.000 RPM), CHIP: ipmi
         fan: Fan is OK. IPMI,Fan 1B: 12495.000 RPM (min = 3519.000 RPM), CHIP: ipmi
         fan: Fan is OK. IPMI,Fan 2A: 16422.000 RPM (min = 4761.000 RPM), CHIP: ipmi
         fan: Fan is OK. IPMI,Fan 2B: 12393.000 RPM (min = 3519.000 RPM), CHIP: ipmi
         fan: Fan is OK. IPMI,Fan 3A: 16146.000 RPM (min = 4761.000 RPM), CHIP: ipmi
         fan: Fan is OK. IPMI,Fan 3B: 12444.000 RPM (min = 3519.000 RPM), CHIP: ipmi
*        fan: FAILURE:: MAJOR::3000000000000001 -- Server Fan Failure. This test uses the leaky bucket algorithm.
*        fan: FAILURE:: Fan RPM is too low, IPMI,Fan 4A: 0.000 RPM (min = 4761.000 RPM), CHIP: ipmi
         fan: Fan is OK. IPMI,Fan 4B: 13005.000 RPM (min = 3519.000 RPM), CHIP: ipmi
         fan: Fan is OK. IPMI,Fan 5: 16170.000 RPM (min = 4554.000 RPM), CHIP: ipmi
         fancontrol: Tekserver III doesn't support Fan Controls; will not run test.

As a work around to clear this alarm following can be done:

1) Restart syscheck and verify if the alarm clears:

[root@mps-9293-b ~]# service syscheck stop
Stopping syscheck: [ OK ]
[root@mps-9293-b ~]#
[root@mps-9293-b ~]# service syscheck start
Starting syscheck: [ OK ]

2) Stop syscheck service, reconfigure syscheck service and the restart syscheck service:

#service syscheck stop
#syscheck --unconfig
#syscheck -r
#service syscheck start

3) Restart the Server:

Graceful Restart of EPAP Server(s) for maintenance

1 Log onto MPS-A as root
#
2 Syscheck MPS-A and MPS-B
# syscheck
3 From MPS-A cu to mate MPS-B
# cu –l /dev/ttyS6 –s 115200
Or you can minicom from one server to another.
4 Stop PDBA service (/etc/init.d/Pdba stop) – IF THIS IS A PROVISIONING SITE
# /etc/init.d/Pdba stop
5 Check GUI to ensure backup is not running
6 Shutdown EPAP software on MPS-B
# /etc/init.d/Epap stop
7 Init 6 on MPS-B
# init 6
8 Monitor Startup for errors
9 Check that RTDB on MPS-A and MPS-B are coherent and taking updates
10 Check PDBA to verify it is connected and taking updates.
11 Verify DSMs are updating

Next Action: If the alarm still does not clears or re-appears within a short time then the Server should be replaced with existing hard drive.

Attachments

This solution has no attachment