Example Of Using Event Objects; Table 4-7 Reported Events - Hitachi HF-W6500 60 Manual

Table 4-7 is a list of events to be reported to a user and their respective event objects.
No.
1 A PS fan failure occurred.
2 A Front fan1 failure occurred.
3
A Front fan2 failure occurred.
4
5
The temperature inside the chassis became
6
abnormal.
A remote shutdown request was generated.
7
SMART anticipated failure in one of the drives.
8
The power-on (=used) hours exceeded the
9
threshold in one of the drives.
A frequent error correction occurred in one of the
10
memory slots.
Memory failure might occurred in one of the
11
memory slots.
The RAID status is normal.
12
The RAID status is not normal.
13
Nos. 3 and 5: For backward compatibility with old programs.
No.8: This includes the case that getting the failure prediction status of the drive fails.
Nos. 10 and 11: The same event object name is given because memory might fail in either case.
Nos. 12 and 13: Apply to B/T Model only.
No.13: This is also applicable when media errors are configured to be reported.
NOTE
When you use an event object in a program, you need to add "Global\" to the
beginning of the name of the event object.

4.2.3 Example of using event objects

We provide a sample program in C (FanErr.c) to show how to monitor event objects. For
information about the name of the sample program and where you can find it, see "6.2
Sample Programs".

Table 4-7 Reported Events

Event
4-15
4. CHECKING THE HARDWARE STATUS
Event object name
W2KRAS_PSFAN_ERR_EVENT
W2KRAS_FTFAN1_ERR_EVENT
W2KRAS_CPUFAN_ERR_EVENT
W2KRAS_FTFAN2_ERR_EVENT
W2KRAS_FTFAN_ERR_EVENT
W2KRAS_TEMP_ERR_EVENT
W2KRAS_RMTSTDN_EVENT
W2KRAS_HDD_PREDICT_EVENT
HFW_HDD_OVERRUN_EVENT
HFW_MEMORY_ERR_EVENT
HFW_RAID_OPTIMAL_EVENT
HFW_RAID_DEGRADE_EVENT