WIN-63-0098

HITACHI INDUSTRIAL COMPUTER

HF-W2000 Model 58/55/50
RAS FEATURES MANUAL

Read and retain this manual.
• Read safety instructions carefully, and ensure that you understandthem before beginning operations.

• Keep this manual on hand for reference.

USER'SMANUALIf you plan to export this product, verify the laws and regulations
that are relevant to export to foreign countries, including the Foreign
Exchange and Foreign Trade Act of Japan and the export controls of
the United States, and complete all required procedures. If anythingis unclear, contact a sales representative.

First Edition, April 2020, WIN-63-0098●●

Do not copy the contents of this manual without permission.
The contents of this manual are subject to change without notice.

All Rights Reserved, Copyright © 2020, Hitachi Industrial Products, Ltd.
IC (FL-MW2007)

SAFETY INSTRUCTIONS
Carefully read and sufficiently understand the following safety precautions before operating the equipment.
● Operate the equipment by following the instructions and procedures described in this manual.
● In particular, note the safety precautions displayed on the equipment or in this manual and follow them.
Failure to do so might result in personal injury and property damage, including damage to the equipment.
● Safety precautions are indicated by one of the following headings. A heading is either a safety alert symbol;
a word such as DANGER, WARNING, CAUTION, or NOTICE; or a combination of both.
This is a safety alert symbol. This symbol is used to indicate potential hazards
that might result in personal injury or death. Follow the instructions in thesafety messages that follow this symbol to avoid possible injury or death.
DANGER: This symbol is used to indicate imminent hazards that are highly likely
to result in serious personal injury or death.
WARNING: This symbol is used to indicate potential hazards that might result inserious personal injury or death.
CAUTION: This symbol is used to indicate potential hazards that might result inmoderate or minor personal injury.
NOTICE:

This symbol is used to indicate hazards that might result in equipment
or property damage, but not personal injury.

The term serious injury as described here is an injury that has aftereffects and requires hospitalization for
medical treatment or long-term follow-up care. Examples of serious injuries are vision loss, burns (causedby dry heat), low-temperature burns, electric-shock injuries, broken bones, and poisoning. A moderate orminor injury is an injury that does not require either hospitalization for medical treatment or long-term
follow-up care. Examples of such injuries are burns and electric-shock injuries.
Damage not related to personal injury is damage other than personal injury. Examples of such damage aredamage or loss of personal property, failure of or damage to the product, and loss of data.
The heading NOTE is used to indicate a cautionary note about the handling or operation of the equipment.

S-1

SAFETY INSTRUCTIONS (Continued)● Do not attempt to perform any operations that are not described in this manual. If you encounter any
problems with the equipment, contact your maintenance personnel.
● Read this manual carefully, and sufficiently understand the directions and precautions in this manual before
operating the equipment.
● Keep this manual nearby so that you are able to refer to it as needed.
● Although every effort has been made in this manual to specify the most complete and relevant precautions
regarding the equipment, unexpected incidents might occur. When using the equipment, use your own
judgment on matters related to safety, in addition to following the instructions herein.

S-2

SAFETY INSTRUCTIONS (Continued)

1. Safety Warnings in This Manual

1.1

Safety warnings indicated as NOTICE● When the failure of a drive is anticipated, the drive might experience hardware failure in the near future.
We recommend backing up the data and replacing the drive. For information about how to replace adrive, see the HF-W2000 Model 58/55/50 INSTRUCTION MANUAL (manual number WIN-62-0073).
(Page 2-3)

● When the OS deadlocks, processes in the OS cannot run as scheduled, and the facility that is using thisequipment might be affected due to delays in processing. If the OS deadlocks, resolve the problem
immediately.
(Page 2-6)

● If this equipment continues to operate after a fan failure is detected, internal parts such as the processor
will not cool sufficiently, which might cause the thermal runaway of the system due to a malfunction in
the equipment, or result in damage to parts.
(Page 3-3)

● When the Hardware status window shows an error in the hardware, resolve the problem causing theerror immediately.
(Page 4-2)

● When the failure of a drive is anticipated, the drive might experience hardware failure in the near future.
We recommend backing up the data and replacing the drive. For information about how to replace adrive, see the HF-W2000 Model 58/55/50 INSTRUCTION MANUAL (manual number WIN-62-0073).
(Page 4-9)

● If this equipment continues to operate after a fan failure is detected, internal parts such as the processor
will not cool sufficiently, which might cause the thermal runaway of the system due to a malfunction in
the equipment, or result in damage to parts. If possible, enable the automatic shutdown feature.
● If the automatic shutdown feature is not used, have a user application detect fan failures by using a RAS
event, and shutdown the equipment when such failures are detected.
(Page 5-2)

S-3

SAFETY INSTRUCTIONS (Continued)● The log function exits asynchronously without waiting for data to actually be written to a log file. Thismeans that this function does not return an error even when writing to a log file fails for some reason.
We recommend recording important information in the OS event log.
(Page 6-15)● The CPU load increases while memory dump files are being collected. While the CPU is under a highload, the operation of user applications can be disturbed. Make sure that you do not collect memory
dump files by using the log information collection window while applications for business use are
running on this equipment.
(Page 7-4)

● While the equipment is running in simulation mode, monitoring of the actual hardware status is disabled.
Errors, including fan failures and abnormal temperatures, cannot be detected. Never use this equipment
in simulation mode for business use. Use the simulation feature only for testing user applications andchecking the notification interface of the RAS software.
(Page 8-2)

S-4

PREFACE
This manual describes how to use the Reliability, Availability, and Serviceability (RAS) features of the HITACHIINDUSTRIAL COMPUTER HF-W2000 Model 58/55/50 (abbreviated hereinafter to this equipment).

Structure of this manualThis manual consists of the following:
CHAPTER 1 CAPABILITIES OF THE RAS FEATURES
CHAPTER 2 ITEMS MONITORED BY THE RAS FEATURES
CHAPTER 3 SETTING UP THE RAS FEATURES
CHAPTER 4 CHECKING THE HARDWARE STATUS
CHAPTER 5 CONTROLLING THE HARDWARE
CHAPTER 6 LIBRARY FUNCTIONSCHAPTER 7 FEATURES RELATED TO MAINTENANCE AND FAILURE ANALYSISCHAPTER 8 SIMULATING THE HARDWARE STATUS

Precautions for using the RAS features● Precautions for the RAS external contact interface
This manual describes a RAS external contact interface. Note that this interface is an optional feature.

● Precautions for event log entries at the startup of the SNMP service
When you enable the SNMP service, a standard feature of Windows®, in order to use remote notifications, an error
log entry with event ID 1500 might be recorded upon startup of the SNMP service. This event log entry is recorded
when SNMP trap notifications have not been set up. Set up the trap notifications as described in 4.5.3 Enabling
remote notifications.

● User Account Control
If User Account Control (UAC) is enabled in Windows®, User Account Control dialog boxes might be displayedwhen you attempt to run an application or a command. In this case, click OK or Continue.

Trademarks• Microsoft®, Windows®, Windows Server®, Windows NT®, and Visual Basic® are registered trademarks ortrademarks of Microsoft Corporation in the United States and other countries.
• All other product names of software and hardware described in this manual that are not from Hitachi are theregistered trademarks, trademarks, or products of their respective owners.

iNote on storage capacity calculations● Memory capacities and requirements, file sizes and storage requirements, etc., are calculated according to theformula 2n:
1 KB (kilobyte) = 1,024 bytes (210 bytes)
1 MB (megabyte) = 1,048,576 bytes (220 bytes)
1 GB (gigabyte) = 1,073,741,824 bytes (230 bytes)
1 TB (terabyte) = 1,099,511,627,776 bytes (240 bytes)● Disk capacities are calculated according to the formula 10n:1 KB (kilobyte) = 1,000 bytes (103 bytes)
1 MB (megabyte) = 1,0002 bytes (106 bytes)
1 GB (gigabyte) = 1,0003 bytes (109 bytes)
1 TB (terabyte) = 1,0004 bytes (1012 bytes)ii

CONTENTS
SAFETY INSTRUCTIONS ........................................................................................................... S-1
CHAPTER 1 CAPABILITIES OF THE RAS FEATURES ................................... 1-1
CHAPTER 2 ITEMS MONITORED BY THE RAS FEATURES ........................ 2-1
2.1 Fan Monitoring ...................................................................................................................................................... 2-1
2.2 Monitoring the Temperature Inside the Chassis .................................................................................................... 2-2
2.3 Drive Failure Prediction (SMART monitoring) ..................................................................................................... 2-3
2.4 Drive Usage Monitoring ........................................................................................................................................ 2-4
2.5 Memory Monitoring .............................................................................................................................................. 2-5
2.6 OS Deadlock Monitoring ....................................................................................................................................... 2-6
2.7 Watchdog Timer Monitoring ................................................................................................................................. 2-8
2.7.1 Automatic retriggering feature for a watchdog timer ...................................................................................... 2-8
2.7.2 Using a watchdog timer to monitor user programs ......................................................................................... 2-9
2.8 RAID Monitoring (B Model Only) ...................................................................................................................... 2-11
2.8.1 RAID status transition .................................................................................................................................. 2-12
2.8.2 Note about media errors ................................................................................................................................ 2-13

CHAPTER 3 SETTING UP THE RAS FEATURES ............................................. 3-1
3.1 RAS Setup Window ............................................................................................................................................... 3-1
3.1.1 Overview ......................................................................................................................................................... 3-1
3.1.2 Opening the RAS Setup window .................................................................................................................... 3-2
3.1.3 Using the RAS Setup window ........................................................................................................................ 3-3
3.1.4 Editing pop-up notification messages ........................................................................................................... 3-14

CHAPTER 4 CHECKING THE HARDWARE STATUS ..................................... 4-1
4.1 Hardware Status Window ...................................................................................................................................... 4-2
4.1.1 Overview ......................................................................................................................................................... 4-2
4.1.2 Hardware status icon ....................................................................................................................................... 4-3
4.1.3 Hardware status window ................................................................................................................................. 4-7
4.2 RAS Event Notifications ..................................................................................................................................... 4-13
4.2.1 Overview ....................................................................................................................................................... 4-13
4.2.2 Detecting an event ........................................................................................................................................ 4-13
4.2.3 Example of using event objects .................................................................................................................... 4-14
4.3 Pop-up Notifications ............................................................................................................................................ 4-15
4.3.1 Overview ....................................................................................................................................................... 4-15

iii

4.3.2 Messages to be displayed .............................................................................................................................. 4-16
4.3.3 Pop-up notification settings .......................................................................................................................... 4-16
4.4 Functionality of the Digital LEDs for Status Indications ..................................................................................... 4-17
4.4.1 Overview ....................................................................................................................................................... 4-17
4.4.2 Displayed status codes .................................................................................................................................. 4-18
4.4.3 Status display modes ..................................................................................................................................... 4-21
4.4.4 Priorities of displayed codes ......................................................................................................................... 4-22
4.4.5 Control functions for the digital LEDs for status indications ....................................................................... 4-22
4.5 Remote Notifications ........................................................................................................................................... 4-23
4.5.1 Overview ....................................................................................................................................................... 4-23
4.5.2 Hardware conditions that can be acquired by using remote notifications ..................................................... 4-24
4.5.3 Enabling remote notifications ....................................................................................................................... 4-25
4.5.4 Objects in the extended MIB for HF-W ........................................................................................................ 4-30
4.5.5 Extended MIB file for HF-W ........................................................................................................................ 4-37
4.6 Status Acquisition by Using the RAS Library ..................................................................................................... 4-38

CHAPTER 5 CONTROLLING THE HARDWARE ............................................. 5-1
5.1 Automatic Shutdown of the Equipment ................................................................................................................. 5-2
5.1.1 Automatic shutdown upon detection of a fan failure ...................................................................................... 5-2
5.1.2 Automatic shutdown when detecting an abnormally high temperature .......................................................... 5-3
5.1.3 Automatic shutdown when a remote shutdown request is detected through the contact input ....................... 5-3
5.2 Controlling the Hardware by Using the RAS Library ........................................................................................... 5-4
5.3 RAID Configuration Control Command (raidctrl) (B Model Only) ...................................................................... 5-5

CHAPTER 6 LIBRARY FUNCTIONS .................................................................. 6-1
6.1 RAS Library .......................................................................................................................................................... 6-1
6.1.1 Overview ......................................................................................................................................................... 6-1
6.1.2 Shutdown function (BSSysShut) .................................................................................................................... 6-3
6.1.3 Watchdog timer control function (WdtControl) ............................................................................................. 6-4
6.1.4 Control functions for the general-purpose external contact outputs (GendoControl and GendoControlEx) .. 6-8
6.1.5 Get functions for the general-purpose external contact inputs (GetGendi and GetGendiEx) ....................... 6-11
6.1.6 Log function (MConWriteMessage) ............................................................................................................. 6-14
6.1.7 Get function for the memory condition (GetMemStatus) ............................................................................. 6-16
6.1.8 Get function for the drive condition (hfwDiskStat) ...................................................................................... 6-18
6.1.9 Get function for the RAID status (hfwRaidStat) (B model only) ................................................................. 6-22
6.1.10 Control functions for the digital LEDs for status indications (SetStCode7seg, TurnOff7seg,
SetMode7seg) ............................................................................................................................................. 6-25
6.2 Sample Programs ................................................................................................................................................. 6-28

iv

CHAPTER 7 FEATURES RELATED TO MAINTENANCE AND FAILUREANALYSIS ....................................................................................... 7-1
7.1 Notifications Regarding the Cause of a Bug Check (Blue Screen) ........................................................................ 7-1
7.1.1 Overview ......................................................................................................................................................... 7-1
7.1.2 Supported causes of a bug check (blue screen) ............................................................................................... 7-2
7.1.3 Event log ......................................................................................................................................................... 7-3
7.2 Log Information Collection Window ..................................................................................................................... 7-4
7.2.1 Overview ......................................................................................................................................................... 7-4
7.2.2 Starting the log information collection window .............................................................................................. 7-4
7.2.3 Using the log information collection window ................................................................................................. 7-5
7.2.4 Closing the log information collection window .............................................................................................. 7-7
7.3 Logging Trends in the Temperature Inside the Chassis ......................................................................................... 7-8
7.3.1 Overview ......................................................................................................................................................... 7-8
7.3.2 Log files .......................................................................................................................................................... 7-8
7.3.3 Logging frequency setup command .............................................................................................................. 7-10

CHAPTER 8 SIMULATING THE HARDWARE STATUS ................................. 8-1
8.1 Hardware Status Simulation .................................................................................................................................. 8-1
8.1.1 Overview ......................................................................................................................................................... 8-1
8.1.2 Using the simulation feature ........................................................................................................................... 8-3
8.1.3 Precautions when you use the Simulation Tool window .............................................................................. 8-15
8.1.4 Event log entries ........................................................................................................................................... 8-17
8.1.5 Remote notifications ..................................................................................................................................... 8-18v

FIGURES
Figure 1-1 RAS Setup window .................................................................................................................................... 1-2
Figure 1-2 Hardware status icon .................................................................................................................................. 1-3
Figure 2-1 State of the status lamp and the CPUSTOP contact ................................................................................... 2-7
Figure 2-2 Example flowchart of monitoring the operational state of a user program ................................................ 2-9
Figure 2-3 RAID status transitions ............................................................................................................................ 2-12
Figure 2-4 Example of a message box when a media error occurs ............................................................................ 2-13
Figure 3-1 RAS Setup window .................................................................................................................................... 3-1
Figure 3-2 Shutdown settings items ............................................................................................................................. 3-3
Figure 3-3 Items in the watchdog timer settings .......................................................................................................... 3-5
Figure 3-4 Items in the drive usage monitoring settings .............................................................................................. 3-7
Figure 3-5 Advanced settings for drive usage monitoring ........................................................................................... 3-8
Figure 3-6 Items in the digital LEDs for status indications settings .......................................................................... 3-10
Figure 3-7 Items in the pop-up notification settings .................................................................................................. 3-11
Figure 3-8 Advanced pop-up notification settings ..................................................................................................... 3-12
Figure 3-9 Format of a message definition file .......................................................................................................... 3-15
Figure 4-1 Hardware status window ............................................................................................................................ 4-2
Figure 4-2 Example of displaying the description of an icon (when the hardware status is normal) .......................... 4-6
Figure 4-3 Example of displaying the description of an icon (when the hardware status has an error) ....................... 4-6
Figure 4-4 Menu of the hardware status icon .............................................................................................................. 4-6
Figure 4-5 Starting the Hardware status window ......................................................................................................... 4-7
Figure 4-6 Confirmation message when disconnecting the drive in drive bay 1 ....................................................... 4-11
Figure 4-7 Message when a request to disconnect the drive in drive bay 1 is rejected .............................................. 4-11
Figure 4-8 Hardware status window (example display in the case of an error) ......................................................... 4-12
Figure 4-9 Example pop-up message notification ..................................................................................................... 4-15
Figure 4-10 Digital LEDs for status indications ........................................................................................................ 4-17
Figure 4-11 Hardware status codes ............................................................................................................................ 4-18
Figure 4-12 Application status code .......................................................................................................................... 4-19
Figure 4-13 Status indication LEDs when a bug check (blue screen) occurs ............................................................ 4-19
Figure 4-14 Example of the status display mode ....................................................................................................... 4-21
Figure 6-1 Behavior of the WDTTO contact ............................................................................................................... 6-7
Figure 6-2 Behavior of the WDTTO contact (when the OS shuts down) .................................................................... 6-7
Figure 6-3 Behavior of the GENDO contact ............................................................................................................. 6-10
Figure 6-4 Format of log information ........................................................................................................................ 6-14
Figure 7-1 Folder structure for collected data .............................................................................................................. 7-7
Figure 7-2 Format of the log information (1) .............................................................................................................. 7-9
Figure 7-3 Format of the log information (2) .............................................................................................................. 7-9viFigure 8-1 Simulation Tool window ............................................................................................................................ 8-1
Figure 8-2 Procedure for using the simulation mode ................................................................................................... 8-3
Figure 8-3 Description of the Simulation Tool window .............................................................................................. 8-6

vii

TABLES
Table 1-1 Overview of RAS features ........................................................................................................................... 1-1
Table 2-1 State of the equipment in terms of fan monitoring and state of the MCALL contact .................................. 2-1
Table 2-2 State of the equipment in terms of monitoring the temperature inside the chassis and state of the
MCALL contact .......................................................................................................................................... 2-2
Table 2-3 State of the equipment in terms of OS deadlock monitoring and state of the status lamp ........................... 2-6
Table 2-4 State of the equipment in terms of OS deadlock monitoring and state of the CPUSTOP contact ............... 2-6
Table 2-5 RAID status and the state of the MCALL contact ..................................................................................... 2-11
Table 2-6 RAID statuses and their descriptions ......................................................................................................... 2-12
Table 3-1 Features that can be set up in the RAS Setup window ................................................................................ 3-1
Table 3-2 Section names and defined messages ........................................................................................................ 3-16
Table 3-3 Items displayed in the object list for each option selected in the event list ............................................... 3-19
Table 4-1 Hardware status icon ................................................................................................................................... 4-5
Table 4-2 Fan condition and displayed information .................................................................................................... 4-8
Table 4-3 Temperature condition and displayed information ...................................................................................... 4-8
Table 4-4 Drive condition and displayed information ................................................................................................. 4-9
Table 4-5 Drive type and displayed information ....................................................................................................... 4-10
Table 4-6 RAID status and displayed information .................................................................................................... 4-10
Table 4-7 Reported events ......................................................................................................................................... 4-13
Table 4-8 Displayed messages ................................................................................................................................... 4-16
Table 4-9 Hardware status codes ............................................................................................................................... 4-18
Table 4-10 Codes displayed when a bug check (blue screen) occurs ........................................................................ 4-20
Table 4-11 Status display modes ............................................................................................................................... 4-21
Table 4-12 Priority of codes in hardware status display mode .................................................................................. 4-22
Table 4-13 Priority of codes in application status display mode ............................................................................... 4-22
Table 4-14 Objects related to the hardware status ..................................................................................................... 4-30
Table 4-15 Objects related to the RAS feature settings ............................................................................................. 4-33
Table 4-16 Objects related to operating modes ......................................................................................................... 4-33
Table 4-17 Objects related to the extended MIB for HF-W ...................................................................................... 4-34
Table 4-18 Objects related to the trap notification (when an error occurs) ............................................................... 4-35
Table 4-19 Objects related to trap notifications (when the equipment has recovered from an error) ........................ 4-36
Table 4-20 Objects related to trap notifications (operating modes) ........................................................................... 4-37
Table 5-1 RAID status displayed in the output of the raidctrl command ..................................................................... 5-6
Table 5-2 Drive status displayed in the output of the raidctrl command ..................................................................... 5-6
Table 5-3 Error messages of the raidctrl command ................................................................................................... 5-11
Table 6-1 RAS library functions .................................................................................................................................. 6-1
Table 6-2 Actions for WdtControl that are specified by dwCmd ................................................................................ 6-4
Table 6-3 List of actions of the GendoControl function specified by dwCmd ............................................................ 6-8
Table 6-4 List of actions of the GendoControlEx function specified by dwPort ......................................................... 6-9

viii

Table 6-5 List of actions of the GendoControlEx function specified by dwCmd ........................................................ 6-9
Table 6-6 List of actions of the GetGendiEx function specified by dwPort .............................................................. 6-12
Table 6-7 List of values stored in Dimm_Status ........................................................................................................ 6-16
Table 6-8 List of values stored in Disk_Status .......................................................................................................... 6-19
Table 6-9 List of defined values ................................................................................................................................ 6-20
Table 6-10 Values stored in Level in the HFW_ARRAY_STATUS structure ......................................................... 6-23
Table 6-11 Values stored in DiskNumber in the HFW_ARRAY_STATUS structure .............................................. 6-23
Table 6-12 Values stored in Status in the HFW_ARRAY_STATUS structure ......................................................... 6-23
Table 6-13 Possible combinations that can be set in Status in the HFW_ARRAY_STATUS structure ................... 6-24
Table 6-14 List of values specified by dwMode in the SetMode7seg function ......................................................... 6-27
Table 6-15 List of provided sample programs ........................................................................................................... 6-28
Table 7-1 Supported causes of bug checks (blue screens) ........................................................................................... 7-2
Table 7-2 Event log entries recorded by this feature ................................................................................................... 7-3
Table 7-3 Log files ....................................................................................................................................................... 7-8
Table 8-1 Event log entries recorded by this feature ................................................................................................. 8-17ix

This page is intentionally left blank.

1. CAPABILITIES OF THE RAS FEATURES

CHAPTER 1 CAPABILITIES OF THE RAS FEATURESThe HF-W series comes with Reliability, Availability, and Serviceability (RAS) features to provide high reliability.
The following is an overview of the RAS features.

Table 1-1 Overview of RAS features
Category
Monitoring

Item
Hardware status monitoring
OS deadlock monitoring
Watchdog timer monitoring

GUI features settings

RAS Setup window

Status checks

GUI display

Hardware status window

Notifications

Event notifications
Pop-up notifications
Digital LEDs for status indications
Remote notifications
Status acquisition by using library functions

Control

Shutdown/startup
suppression

Automatic shutdown
Shutdown via library functions
Startup suppression when severe failures occur
Controlling general-purpose external contacts (HJ-F2050-11, HJ-F2050-12,
and HJ-F2050-13)
Controlling digital LEDs for status indications

Library functions
Maintenance/
failure analysis

RAS library
Memory dumps

Memory dump collection
Bug check (blue screen) cause notifications
Log information collection window
Maintenance operation support commands
Logging trends of the temperature inside the chassis

Simulation

Hardware status simulation

1-1

1. CAPABILITIES OF THE RAS FEATURES

Monitoring(1)

Hardware status monitoring
This feature monitors the hardware status of this equipment, including fan status, drive status, and thetemperature inside the chassis.

(2)

OS deadlock monitoring
This feature monitors the operational state of the OS by using the dedicated timer implemented within thisequipment. As long as the process with the highest priority (real-time priority class) can run properly, thestatus lamp on the front of this equipment is lit in green.

(3)

Watchdog timer monitoring
This feature monitors whether processes are scheduled properly by using the watchdog timer implemented
within this equipment. This feature also offers a library for using the watchdog timer.

GUI features settings(4)

RAS Setup window
This window provides a graphical user interface for configuring RAS feature settings, including theconditions on automatic shutdown and the watchdog timer settings.

Figure 1-1 RAS Setup window

1-2

1. CAPABILITIES OF THE RAS FEATURES

Status checks(5)

Hardware status window
This window displays the hardware status of this equipment via a graphical interface. An icon in the
notification area of the taskbar displays the hardware status at all times.

Figure 1-2 Hardware status icon

(6)

Event notifications
This feature allows user applications to check the hardware status of this equipment by monitoring the statusof event objects.

(7)

Pop-up notifications
This feature displays pop-up messages to notify users that errors have occurred in the equipment hardware.

(8)

Digital LEDs for status indications
The digital LEDs for status indications are on the front of this equipment, and notify users when errors occur
in the equipment hardware. These LEDs can be used by a user application to, for example, notify the user ofapplication failures.

(9)

Remote notifications
This feature enables a remote device to check the hardware status of the equipment. It also notifies the
remote device whenever the hardware status changes.

(10) Status acquisition by using library functions
This feature allows user applications to obtain the hardware status of this equipment by using the RAS
library.

Control(11) Automatic shutdown
This feature automatically shuts down the equipment when it detects a fan failure, an abnormal temperatureinside the chassis, or a remote shutdown signal input. Configure the settings shown in (4) RAS Setup window
to enable or disable the automatic shutdown feature.
(12) Shutdown via library functions
You can shutdown the equipment from a user application by using the RAS library.
(13) Startup suppression when severe failures occur
This feature suppresses startup of this equipment to protect the hardware when a failure, such as a fan failure,is detected during OS startup.
(14) Controlling general-purpose external contacts (HJ-F2050-11, HJ-F2050-12, and HJ-F2050-13) and digital
LEDs for status indications
This feature allows users to control the general-purpose external contacts and the digital LEDs for statusindications by using the RAS library.
Input and output general-purpose external contacts are available. If you use these contacts, signals can be
input from an external device to this equipment, and signals can be output from this equipment to an external
device see the HF-W2000 Model 58/55/50 INSTRUCTION MANUAL (manual number WIN-62-0073).

1-3

1. CAPABILITIES OF THE RAS FEATURES

Library functions(15) RAS libraryThis feature offers library functions for recording log information, in addition to the library functions offeredby the status check (10) and control (12 and 14) items.

Maintenance/failure analysis(16) Memory dump collection
This feature records the contents of the system memory in a file (a memory dump file) when the NMI switch
is pressed after a failure occurs, for example, after the equipment stops unexpectedly. By analyzing the datain this memory dump, you can investigate the cause of the failure.
(17) Bug check (blue screen) cause notifications
This feature detects a bug check (blue screen), and records the cause in the event log.
(18) Log information collection window
In this window you can use a graphical user interface to collect log data and memory dump files for thisequipment.
(19) Maintenance operation support commands
These commands include a command used for saving failure information, such as memory dump files andevent log files, to external media.
(20) Logging trends of the temperature inside the chassis
This feature periodically measures the temperature inside the chassis of this equipment and records the data
in a file.

Simulation(21) Hardware status simulation
This feature simulates the hardware status of this equipment. You can use this feature to test user applications
and check the notification interface of the RAS software without an actual hardware failure having occurred.

This manual explains features (1) through (12), (14), (15), (17), (18), (20), and (21). For details about the otherfeatures, see the HF-W2000 Model 58/55/50 INSTRUCTION MANUAL (manual number WIN-62-0073).

1-4

2. ITEMS MONITORED BY THE RAS FEATURES

CHAPTER 2 ITEMS MONITORED BY THE RAS FEATURES
This chapter describes the items monitored by the RAS features.
For information about the hardware specifications of the RAS external contact interface (optional) described in thischapter and how to use each contact, see the HF-W2000 Model 58/55/50 INSTRUCTION MANUAL (manual number
WIN-62-0073).

2.1 Fan Monitoring
The fan monitoring feature monitors the multiple fans located in this equipment, and notifies users when one of thefans malfunctions via the following methods:(1)

Hardware status window(2)

Event notifications(3)

Pop-up notifications(4)

Digital LEDs for status indications(5)

Remote notifications(6)

Automatic shutdown(7)

Alarm lamp

For details about (1) through (5), see Chapter 4. CHECKING THE HARDWARE STATUS. For details about (6), see
5.1 Automatic Shutdown of the Equipment.
If you use the MCALL contact of the RAS external contact interface, the external hardware connected to the RAS
external contact interface can detect malfunctions in this equipment. The following table shows how the state of the
MCALL contact changes.

Table 2-1 State of the equipment in terms of fan monitoring and state of the MCALL contact
Status of this equipment

MCALL contact

During startup of the equipment or when the power is off

Open

When the fans are operating normally or have recovered from a malfunction

Open

During a fan malfunction

ClosedThe alarm lamp (as well as the MCALL contact of the RAS external contact interface) is not dedicated to fanmonitoring and, therefore, is not turned off (opened) when the system recovers from a fan malfunction as long as amalfunction is detected for other monitored items.

2-1

2. ITEMS MONITORED BY THE RAS FEATURES

2.2 Monitoring the Temperature Inside the Chassis
This feature monitors the temperature inside the chassis by using the temperature sensor in this equipment, andnotifies users when the temperature inside the chassis becomes abnormally high via the following methods:(1)

Hardware status window(2)

Event notifications(3)

Pop-up notifications(4)

Digital LEDs for status indications(5)

Remote notifications(6)

Automatic shutdown(7)

Alarm lamp

For details about (1) through (5), see Chapter 4. CHECKING THE HARDWARE STATUS. For details about (6), see
5.1 Automatic Shutdown of the Equipment.
If you use the MCALL contact of the RAS external contact interface, the external hardware connected to the RAS
external contact interface can detect malfunctions in this equipment. The following table shows how the state of the
MCALL contact changes.

Table 2-2 State of the equipment in terms of monitoring the temperature inside the chassis andstate of the MCALL contact
Status of this equipment
During startup of the equipment or when the power is off

MCALL contact
Open

When the temperature is normal or has recovered from being abnormally high OpenWhen the temperature is abnormally high

ClosedThe alarm lamp (as well as the MCALL contact of the RAS external contact interface) is not dedicated to monitoring
the temperature inside the chassis and, therefore, is not turned off (opened) when the system recovers from anabnormally high temperature as long as a malfunction is detected for other monitored items.

2-2

2. ITEMS MONITORED BY THE RAS FEATURES

2.3 Drive Failure Prediction (SMART monitoring)
The HDD/SSD drives in this equipment have the Self-Monitoring, Analysis and Reporting Technology (SMART)
feature, which continuously monitors the condition of the drives and anticipates failures before they manifest. The
drive failure prediction feature notifies users when a drive might fail in near future via the following methods:(1)

Hardware status window(2)

Event notifications(3)

Pop-up notifications(4)

Digital LEDs for status indications(5)

Remote notifications(6)

hfwDiskStat function in the RAS library

For details about (1) through (5), see Chapter 4. CHECKING THE HARDWARE STATUS.
For details about (6), see 6.1.8 Get function for the drive condition (hfwDiskStat).

NOTICE
When the failure of a drive is anticipated, the drive might experience hardware failure in thenear future. We recommend backing up the data and replacing the drive. For information about
how to replace a drive, see the HF-W2000 Model 58/55/50 INSTRUCTION MANUAL (manual
number WIN-62-0073).

NOTE• It is not possible for the drive failure prediction feature to anticipate all failures. Therefore, a drive
might fail before the drive failure prediction feature anticipates any failures.
• This feature only monitors internal drives that are recognized during OS startup. If you connect a new
drive or replace a drive with a new drive for maintenance or other reasons, it might take a long time torecognize the new drive upon the first startup after the new drive is connected, and the drive might not
be recognized as a drive to be monitored. In this case, restart this equipment.

2-3

2. ITEMS MONITORED BY THE RAS FEATURES

2.4 Drive Usage Monitoring
The drive usage monitoring feature adds up the power-on hours of a drive in this equipment. If the total power-on
hours exceeds a set value, the feature notifies users via the methods below. By using this feature, you can keep trackof when to replace drives and prevent drive failures that are caused by using drives for too long.
(1)

Hardware status window(2)

Event notifications(3)

Pop-up notifications(4)

Remote notifications(5)

hfwDiskStat function in the RAS library

For details about (1) through (4), see Chapter 4. CHECKING THE HARDWARE STATUS.
For details about (5), see 6.1.8 Get function for the drive condition (hfwDiskStat).
This feature can be enabled or disabled in the RAS Setup window. If you disable this feature, notifications via themethods described above are disabled. For details, see 3.1.3 Using the RAS Setup window.

NOTE• This monitoring feature is active while the OS is running, that is, from OS startup to OS shutdown.
When the OS is not running, drive power-on hours are not monitored.
• This feature records the serial number (unique ID) of a drive in the equipment in a drive management
information file. If you install a drive that does not match the serial numbers recorded in the drive
management information file, the cumulative power-on hours for the drive are automatically reset.
• This feature is not designed to anticipate drive failure, but we recommend replacing drives when theirpower-on hours exceed the set value for preventive maintenance of components with a limited life. For
information about how to replace a drive, see the HF-W2000 Model 58/55/50 INSTRUCTION
MANUAL (manual number WIN-62-0073).
• This feature only monitors internal drives that are recognized during OS startup. If you connect a new
drive or replace a drive with a new drive for maintenance or other reasons, it might take a long time torecognize the new drive upon the first startup after the new drive is connected, and the drive might not
be recognized as a drive to be monitored. In this case, restart this equipment.

2-4

2. ITEMS MONITORED BY THE RAS FEATURES

2.5 Memory Monitoring
Memory with error checking and correcting (ECC) is installed in this equipment. A single-bit error in the memory
can be automatically corrected without interfering with the operation of the equipment. On the other hand, memory
might have failed in the following cases of single-bit errors, and we recommend that you replace the memory
modules for preventive maintenance:
1. A single-bit error frequently occurs while the OS is running.
2. A single-bit error continuously occurs each time the OS starts.
If the memory might have failed, the memory monitoring feature notifies users of this information via the following
methods:(1)

Event notifications(2)

Pop-up notifications(3)

Remote notifications(4)

GetMemStatus function in the RAS library

To maintain backward compatibility with previous versions of the equipment, (2) and (3) report High frequency ofmemory error correction for error case 1, and Possible memory failure for error case 2. In the case of (1) and (4),both error cases are handled as memory errors, and the same value is returned.

For details about (1) through (3), see Chapter 4. CHECKING THE HARDWARE STATUS. For details about (4), see
6.1.7 Get function for the memory condition (GetMemStatus).

NOTE
For information about how to replace a memory module, see the HF-W2000 Model 58/55/50
INSTRUCTION MANUAL (manual number WIN-62-0073).

2-5

2. ITEMS MONITORED BY THE RAS FEATURES

2.6 OS Deadlock Monitoring
The OS deadlock monitoring feature uses a timer implemented in this equipment to monitor the operational state of
the OS to detect situations where a process with real-time priority cannot run. Such situations (hereinafter referred toas an OS deadlock) occurs if, for example, a runaway kernel exists or all CPU load is used up by a driver. When an
OS deadlock is detected, this feature notifies users via the status lamp on the front of this equipment.

Table 2-3 State of the equipment in terms of OS deadlock monitoring andstate of the status lamp
Status of this equipment

Status lamp

During startup of the equipment or when the power is off

Red

When an OS deadlock has not occurred or the system has recovered from an OS
deadlock

Green

When an OS deadlock has occurredRed

If you use the CPUSTOP contact of the RAS external contact interface, external hardware connected to the RAS
external contact interface can detect an OS deadlock. The following table shows how the state of the CPUSTOP
contact changes.

Table 2-4 State of the equipment in terms of OS deadlock monitoring andstate of the CPUSTOP contact
Status of this equipment

CPUSTOP contact

During startup of the equipment or when the power is off

ClosedWhen an OS deadlock has not occurred or the system has recovered from an OS
deadlockOpen

When an OS deadlock has occurred

ClosedNOTICE
When the OS deadlocks, processes in the OS cannot run as scheduled, and the facility that isusing this equipment might be affected due to delays in processing. If the OS deadlocks,
resolve the problem immediately.

NOTE• For this feature, an OS deadlock is defined as a state where a process with the highest priority (realtime priority class) cannot run.
• When the OS starts, the status lamp is lit green when this feature starts.
• When the OS shuts down, the status lamp becomes red when this feature stops. Note that when thestatus lamp turns red, the shutdown process is not complete. Do not turn off the power at this point.

2-6

2. ITEMS MONITORED BY THE RAS FEATURES

Figure 2-1 shows how the state of the status lamp and the state of the CPUSTOP contact change.

Power ONOS monitoring
timer starts being
retriggered

OS monitoring timer
times out

OS shutdown
startsOS shutdown
Power off

Contact open
(Status lamp: green)
3 sec.

3 sec.

Contact closed(Status lamp: red)

OS startup

Timer isretriggered
Timer isretriggered

CPU load
is used up by Timer isretriggereda driverTime →
Timer stops being
retriggered

Figure 2-1 State of the status lamp and the CPUSTOP contact

The dotted lines in Figure 2-1 denote the state of the contact, and the thick line denotes the transition of the state of
the contact.

2-7

2. ITEMS MONITORED BY THE RAS FEATURES

2.7 Watchdog Timer Monitoring
This equipment has a watchdog timer. By retriggering a watchdog timer automatically, this feature monitors whether
processes are scheduled properly. In addition, this feature can be used, for example, to monitor the operational stateof user programs by using dedicated library functions.

2.7.1 Automatic retriggering feature for a watchdog timer
This feature is implemented via a process that retriggers a watchdog timer periodically. This process runs with
the idle priority. If the amount of CPU time used by processes with a priority higher than the idle priority classexceeds a set value, the watchdog timer times out. You can use this feature to, for example, detect a runaway
application process and so on.
You can set up the watchdog timer timeout and the retrigger interval in the RAS Setup window. For information
about how to use the RAS Setup window, see 3.1.3 Using the RAS Setup window. The factory default settings
are as follows:
Timeout

60 (seconds)

Retrigger interval

20 (seconds)

2-8

2. ITEMS MONITORED BY THE RAS FEATURES

2.7.2 Using a watchdog timer to monitor user programs
To use a watchdog timer to monitor the operational state of a user program, you can use a configuration where,
for example, the user program periodically retriggers the watchdog timer (that is, it resets the watchdog timer tothe initial value) and another program checks whether a timeout occurs for the watchdog timer. The flowchart
for this configuration is shown below.

Monitored program

Monitoring program

Process a user-definedprogramCheck whether atimeout occurs for thewatchdog timer

Trigger the watchdog
timer

Retrigger

Get the value of thetimeout counter

HF-W
Watchdog timer

Figure 2-2 Example flowchart of monitoring the operational state of a user program

2-9

2. ITEMS MONITORED BY THE RAS FEATURESIn Figure 2-2, the monitored program is configured to periodically retrigger the watchdog timer.
The monitoring program periodically checks the timeout counter of the watchdog timer and, if the value of thetimeout counter (that is, the remaining time until timeout expires) is zero, a timeout is determined to haveoccurred.
The fact that a timeout occurred means that the monitored program was not able to retrigger the watchdog timer
for at least the length of the timeout. In this example, another program detects the timeout of the watchdog timer,
but if you use the RAS external contact interface, the WDTTO contact is closed when a timeout occurs for thewatchdog timer. In this case, external hardware connected to the RAS external contact interface can monitor theoperational state of a user program.
A program can use a watchdog timer by calling the library function WdtControl. For information about how
to use the WdtControl function and how the WDTTO contact of the RAS external contact interface works,
see 6.1.3 Watchdog timer control function (WdtControl).

NOTE
If you are using the WdtControl function, you cannot use the automatic retriggering feature for thewatchdog timer. To use the WdtControl function, select Retriggered by application program under
Watchdog timer setting. For information about how to use the RAS Setup window, see 3.1.3 Using theRAS Setup window.

2-10

2. ITEMS MONITORED BY THE RAS FEATURES

2.8 RAID Monitoring (B Model Only)
The B model has a RAID1 feature (hereinafter indicated simply as RAID), generally known as mirror disk (mirroring).
The RAID monitoring feature monitors the RAID status of this equipment. If the status of the RAID changes, thisfeature notifies users or an application via the following methods:(1)

Hardware status window(2)

Event notifications(3)

Pop-up notifications(4)

Digital LEDs for status indications(5)

Remote notifications(6)

Alarm lamp

(7)

hfwDiskStat and hfwRaidStat functions in the RAS library(8)

RAID configuration control command (raidctrl)

For details about (1) through (5), see Chapter 4. CHECKING THE HARDWARE STATUS.
For details about (7), see 6.1.8 Get function for the drive condition (hfwDiskStat) and 6.1.9 Get function for the RAID
status (hfwRaidStat) (B model only). For details about (8), see 5.3 RAID Configuration Control Command (raidctrl)(B Model Only).
If you use the MCALL contact of the RAS external contact interface, the external hardware connected to the RAS
external contact interface can detect malfunctions in this equipment. The following table shows how the state of the
MCALL contact changes.

Table 2-5 RAID status and the state of the MCALL contact
RAID status

MCALL contact

NormalOpen#

ClosedDegraded , Unknown#: This also applies when the reporting of media errors is configured.

The alarm lamp (as well as the MCALL contact of the RAS external contact interface) is not dedicated to monitoring
the RAID status, therefore, is not turned off (opened) when the RAID status recovers as long as a malfunction isdetected for other monitored items.

2-11

2. ITEMS MONITORED BY THE RAS FEATURES

2.8.1 RAID status transition
Table 2-6 lists and describes the RAID statuses. Figure 2-3 shows the state transitions.

Table 2-6 RAID statuses and their descriptions
RAID status
Description

Detailed
information
NormalDegraded--

Redundant data is intact, and the RAID is operating normally.

--

One drive failed, and a part of the redundant data is corrupted.

Rebuild

The RAID is being rebuilt due to a drive replacement or other reason.

Fail

--

Both drives failed.

Unknown--

Acquisition of the RAID status failed, or the array configuration is abnormal.

A media error occurs.
NormalOne drive fails.
One drive isdisconnected manually.

Degraded

Degraded

The RAID rebuild
process iscomplete.

Drive
replacement

An error occurs
in the newdrive.

Degraded(Rebuild)

Both drives fail.

Fail

Figure 2-3 RAID status transitions

2-12

The RAID rebuild
process is complete.
(A read error occurs in
the copy source drive.)2. ITEMS MONITORED BY THE RAS FEATURES

2.8.2 Note about media errors
A media error is a state where there is a problem with data integrity while the RAID status is normal. If a readerror occurs at the copy-source drive during a rebuild process, the rebuild process will finish, but the sector datathat could not be read is already lost, indicating a data integrity problem.

Handling media errors as failures
The severity of this data-integrity problem depends on whether bad sectors with read errors are actually used.
If the bad sectors are used, there is a real problem with data integrity. If the bad sectors are not used, there is no
problem.
This is why this equipment allows you to, depending on how the system is operated, select whether to report
media errors. When using the factory default settings, media errors are not reported.
Use the RAID configuration control command (raidctrl) to select whether to report media errors. (For details,
see 5.3 RAID Configuration Control Command (raidctrl) (B Model Only).)
A media error can be reported via the following methods:(1) Event notifications(2) Digital LEDs for status indications(3) Remote notifications(4) Alarm lamp(5) Message box(6) MCALL contact of the RAS external contact interface

Figure 2-4 Example of a message box when a media error occurs

2-13

2. ITEMS MONITORED BY THE RAS FEATURES

Note that, regardless of the setting for whether to report media errors, you can check whether media errors
occur via the following methods:(7) Hardware status window(8) hfwRaidStat function in the RAS library(9) RAID configuration control command (raidctrl)

For details about (1) through (3) and (7), see Chapter 4. CHECKING THE HARDWARE STATUS. For details
about (8), see 6.1.9 Get function for the RAID status (hfwRaidStat) (B model only). For details about (9), see 5.3
RAID Configuration Control Command (raidctrl) (B Model Only).

2-14

3. SETTING UP THE RAS FEATURES

CHAPTER 3 SETTING UP THE RAS FEATURES
3.1 RAS Setup Window
3.1.1 Overview
In the RAS Setup window, you can set up the following features.

Table 3-1 Features that can be set up in the RAS Setup window
Item
Automatically shutdown if a fan failure is detected
Shutdown
settings

Automatically shutdown if an abnormally high temperature is detected
Automatically shutdown if a remote shutdown is requested

Watchdog timer settings
Drive usage monitoring settings
Digital LEDs for status indications settings
Pop-up notification settings

Figure 3-1 shows the RAS Setup window. This figure shows the factory default settings.

Figure 3-1 RAS Setup window

3-1

3. SETTING UP THE RAS FEATURES

3.1.2 Opening the RAS Setup window
To open the RAS Setup window, perform the following procedure.
Before you open this window, you need to sign in to the computer as an administrator.
1. Click Start.
2. From the list of applications, click RAS Software.
3. Click RAS Setup.

NOTE
The RAS Setup window cannot be used by multiple users at the same time. If you use, for example, user
switching to try to start instances of this window from multiple consoles, the following message appears.
If you receive this message, close the RAS Setup window from other consoles, and then try opening theRAS Setup window again.

3-2

3. SETTING UP THE RAS FEATURES

3.1.3 Using the RAS Setup window(1)

Shutdown settings
You can select whether this equipment is automatically shutdown in each of the following cases: a fan
failure, an abnormally high temperature, and a remote shutdown request.

Figure 3-2 Shutdown settings items● Automatically shutdown if fan failure has been detected. check box• Selected: This equipment will automatically shutdown (factory default setting).
• Cleared: This equipment will not automatically shutdown.
● Automatically shutdown if abnormally high temp. has been detected. check box• Selected: This equipment will automatically shutdown.
• Cleared: This equipment will not automatically shutdown (factory default setting).
● Automatically shutdown if remote shutdown is requested. check box• Selected: This equipment will automatically shutdown (factory default setting).
• Cleared: This equipment will not automatically shutdown.
To change the current setting, click the check box that you want to change.

NOTICE
If this equipment continues to operate after a fan failure is detected, internal parts such as theprocessor will not cool sufficiently, which might cause the thermal runaway of the system due toa malfunction in the equipment, or result in damage to parts.

3-3

3. SETTING UP THE RAS FEATURES

NOTE• If you clear the Automatically shutdown if fan failure has been detected check box, the following
cautionary message appears. Enable this feature (select the check box) whenever possible.

If you click Cancel when you this message appears, the check box returns to the selected state. If you
click OK, the check box is cleared.
• After an automatic shutdown initiated by this feature is complete, the power turns off.
• The remote shutdown input is polled every 5 seconds. This means that it might take up to 5 seconds
from when a remote shutdown is requested to when the actual shutdown process starts.

3-4

3. SETTING UP THE RAS FEATURES(2)

Watchdog timer settings
You can set up the watchdog timer of this equipment.
You can select one of the following ways of using the watchdog timer by clicking the radio button
corresponding to the item:• Not used.
• Retriggered by an application program.
• Automatic retrigger.
The factory default setting is Automatic retrigger.

Figure 3-3 Items in the watchdog timer settings● Not used
If you select this item, the watchdog timer stops, and the watchdog timer will not time out. In addition, you
cannot use the watchdog timer by calling the WdtControl function of the RAS library.
● Retriggered by application programs
If you select this item, you can monitor the operational state of a user program by controlling the watchdog
timer by using the WdtControl function of the RAS library.

NOTE
When you change the setting to Retriggered by application program, the watchdog timer stops once.
While the watchdog timer is stopped, it will never time out. When a user application retriggers thewatchdog timer by using the WdtControl function of the RAS library, the watchdog timer resumes its
countdown. You can check the state of the watchdog timer (whether it is counting down or stopped) byusing the WdtControl function.

3-5

3. SETTING UP THE RAS FEATURES● Automatic retrigger
If you select this item, the watchdog timer is automatically retriggered by the automatic retriggering featureof the watchdog timer. In addition, you cannot use the watchdog timer by calling the WdtControl
function of the RAS library.
If this item is selected, you can configure the retrigger interval of the automatic retriggering feature and thetimeout of the watchdog timer.
• Timeout
This sets the timeout of the watchdog timer by using single-byte numeric characters. Enter an integer
value between 5 and 60 (in seconds). The factory default setting is 60 seconds.
• Retrigger intervalThis sets the retrigger interval of the automatic retriggering feature of the watchdog timer by using
single-byte numeric characters. Enter an integer value between 1 and (timeout - 4) (in seconds). The
factory default setting is 20 seconds.
You can set a timeout and retrigger interval only if you select Automatic retrigger. If Automatic
retrigger is not selected, you cannot enter these values.

3-6

3. SETTING UP THE RAS FEATURES(3)

Drive usage monitoring settings
You can set up the drive usage monitoring settings. By clicking Advanced, you can configure the advanced
settings of this feature.

Figure 3-4 Items in the drive usage monitoring settings● Function is available check box• Selected: Drive usage monitoring is enabled. (factory default setting)• Cleared: Drive usage monitoring is disabled.
To change the current setting, click the check box.
If drive usage monitoring is disabled, you cannot use the notification features described in 2.4 Drive Usage
Monitoring such as indicating whether the value of the drive power-on (used) hours exceeds the threshold.

3-7

3. SETTING UP THE RAS FEATURES● Advanced button
If drive usage monitoring is enabled, click Advanced to display the window shown in Figure 3-5. If drive
usage monitoring is disabled, this button is grayed out and unavailable.

Figure 3-5 Advanced settings for drive usage monitoring● Function is available check box• Selected: Drive usage monitoring is enabled. (factory default setting)• Cleared: Drive usage monitoring is disabled.

● The box in It reports when the used hours passes

hours

Specify a threshold (a single-byte number) for the drive power-on (used) hours so that you can be notified
when the value of the drive power-on (used) hours exceeds the threshold. Enter an integer value in hours
ranging from 100 to the maximum value at 100-hour increments. The factory default setting is 20000
hours.
The maximum value that can be set is 99900 hours.

3-8

3. SETTING UP THE RAS FEATURES

If you want to clear the current cumulative power-on (used) hours, click Reset to clear the value. The
following message then appears:

If you click OK when the message appears, the value of the current cumulative power-on (used) hours iscleared. Click Cancel to leave the value as is.

To apply any advanced settings that you changed, click OK.
To discard the changes, click Cancel. The window then closes and the changes are lost.

3-9

3. SETTING UP THE RAS FEATURES(4)

Digital LEDs for status indications settings
You can set up the display mode of the digital LEDs for status indications located on the front of theequipment.

Figure 3-6 Items in the digital LEDs for status indications settings● Show Hardware status check box• Selected: Hardware status display mode (factory default setting)• Cleared: Application status display mode
To change the current setting, click the check box.
For details about the functionality of the digital LEDs for status indications, including its display modes, see
4.4 Functionality of the Digital LEDs for Status Indications.

3-10

3. SETTING UP THE RAS FEATURES(5)

Pop-up notification settings
You can set up the pop-up notification settings. Clicking Advanced allows you to configure the advanced
settings of this feature.

Figure 3-7 Items in the pop-up notification settings● Function is available check box• Selected: Pop-up notifications are enabled.
• Cleared: Pop-up notifications are disabled (factory default setting).
To change the current setting, click the check box.
If the Function is available check box is not selected, Advanced is grayed out and unavailable.

3-11

3. SETTING UP THE RAS FEATURES● Advanced button
Click Advanced to display the following window.

A/S model

B modelFigure 3-8 Advanced pop-up notification settings

Events• Fan failure• Abnormally high temp.
• Drive failure prediction• Drive usage excess• RAID error is detected. (B model only)• Error correcting in memory• Memory failure
You can disable or enable pop-up notifications for each of these items.
● Check box for each item
• Selected: Pop-up notifications are enabled (factory default setting)• Cleared: Pop-up notifications are disabled.
To change the current setting, click the check box.
If the monitoring feature is disabled, the system will not send notifications even if pop-up notifications areenabled.

3-12

3. SETTING UP THE RAS FEATURES

Message editing
You can edit the pop-up notification messages and check the messages after you edit them. For information
about how to edit and check these messages, see 3.1.4 Editing pop-up notification messages.

To apply any advanced settings that you changed, click OK. To discard the changes, click Cancel. The
window then closes and the changes are lost.

(6)

Applying the changes you made in (1) through (5) or discarding the changes
If you changed the settings in (1) through (5) and want to apply the changes, click OK. The RAS Setup
window closes and the settings are applied immediately. To discard the changed settings, click Cancel. TheRAS Setup window then closes and the changes are lost.

3-13

3. SETTING UP THE RAS FEATURES

3.1.4 Editing pop-up notification messages(1)

Editing pop-up notification messages
If you want to edit the messages that are used for pop-up notifications, click Edit. Notepad launches, and themessage definition file for pop-up notifications is opened. Edit the messages in the following format.

NOTE
While you are editing messages, you cannot do the following:• Click Edit.
• Click Set default.
• Click Display message.
• Close the RAS Setup window (by clicking OK or Cancel).
If you attempt to perform one of these actions, the following cautionary message appears.

If you click OK when this message appears, you return to the RAS Setup window.

3-14

3. SETTING UP THE RAS FEATURES■ Format of a message definition file
The format of a message definition file is as follows.

;-- Example of the definition of messages -Section[SYSTEM-FAN]
Line1=""
Line2=""

Line3="System fan revolutions deteriorated significantly."
Key

Value

[CPU-FAN]
Line1=""
Line2=""

Line3="CPU fan revolutions deteriorated significantly."

Figure 3-9 Format of a message definition file

A message definition file consists of sections, keys, and key values.
Each section contains keys and their values. A key and its value are separated by an equal sign (=).
Lines that start with a semicolon (;) are comment lines.

3-15

3. SETTING UP THE RAS FEATURES■ Descriptions in a message definition file
1. Section
The following table shows a list of section names that you can define for this feature, and an explanationof the message that you define for each section.

Table 3-2 Section names and defined messages
Section nameDefined message[SYSTEM-FAN]

A message displayed when a system fan failure is detected.

[CPU-FAN]

A message displayed when a CPU fan failure is detected.

[TEMP]

A message displayed when an abnormal temperature is detected inside the chassis.

[DRV1-SMART]#1

A message displayed when a drive failure prediction (SMART) is detected for drive bay 1.

[DRV2-SMART]#1

A message displayed when a drive failure prediction (SMART) is detected for drive bay 2.

[DRV1-OFFLINE]#2

A message displayed when a RAID failure is detected due to a drive failure in drive bay 1.

[DRV2-OFFLINE]#2

A message displayed when a RAID failure is detected due to a drive failure in drive bay 2.

[DRV1-OVERRUN]#1

A message displayed when the drive power-on (used) hours exceed the defined value fordrive bay 1.

[DRV2-OVERRUN]#1

A message displayed when the drive power-on (used) hours exceed the defined value fordrive bay 2.

[DIMM1-ERR]

A message displayed when error corrections are detected frequently in DIMM1.

[DIMM2-ERR]

A message displayed when error corrections are detected frequently in DIMM2.

[DIMM1- FAILURE]

A message displayed when a memory failure might have occurred in DIMM1.

[DIMM2- FAILURE]

A message displayed when a memory failure might have occurred in DIMM2.
#1: Regardless of the installed drive, this section name is fixed.
#2: B model only.

3-16

3. SETTING UP THE RAS FEATURES

2. Keys
For a key, specify the line number of the line displayed as a part of the pop-up message.
In this feature, you can use the keys Line1 through Line5 for each section.
If you specify keys other than Line1 through Line5, those keys are ignored.

3. Values
Specify one line of the message displayed as a part of the pop-up message for a value.
For each key, you can assign a maximum of 50 bytes of characters (up to 25 double-byte characters). If
you specify more than 50 bytes of characters, the characters from the 51th byte onward are ignored.
If a line includes space characters, enclose the entire value in double quotation marks ("). An empty
value is treated as a newline character.

NOTE• When you save the changes, make sure you use Save in the menu. If you do not, the changes you mademight not be saved properly.
• While you are editing a message definition file, do not use another application to edit the same file. If
you edit a message definition file from multiple applications at the same time, the changes might not besaved properly.
• When you edit a pop-up notification message, make sure that the message clearly states that an error
occurred. If you continue to use this equipment while an error persists, your system might besignificantly affected.

3-17

3. SETTING UP THE RAS FEATURES(2)

Checking pop-up notification messages
You can check the changes you made in the message for each of the following items:• Fan failure• Abnormally high temp.
• Drive failure prediction• Drive usage excess• RAID error is detected. (B model only)• Error correcting in memory• Memory failure
The following shows how to check changes you make to the messages.
1. From the Event list, select the event you want to check.
In this list, only the items under Events selected by using the check boxes appear. If no items under Events
have been selected by using the check boxes, you cannot select an item from the event list.

Example of selecting fan failure

2. From the Object list, select the object that you want to check.
The items that appear in this list depend on the item that you selected in step 1.

Example of selecting the system fan

3-18

3. SETTING UP THE RAS FEATURES

The following table shows items displayed in the Object list for each option you select in the Event list.

Table 3-3 Items displayed in the object list for each option selected in the event list
Option in the event list

Items in the object list

Fan failure

System fan, CPU fan

Abnormally high temp.

Temperature inside the chassis

Drive failure prediction

Drive bay 1, Drive bay 2

Drive usage excess
RAID error detection

Drive bay 1, Drive bay 2

Error correction in memory

DIMM1, DIMM2

Possible memory failure

3. Click Display message.
A pop-up notification message appears based on the changes you made. After you confirm the message,
click OK.

If the message has not been edited or there is something wrong in the message definition file, the following
message appears. Click OK to go back to the RAS Setup window. Correct the changes that you made in
the message.

3-19

3. SETTING UP THE RAS FEATURES(3)

Restoring the default messages
If you want to return the pop-up notification messages to the default values, click Set default. The following
message appears. Click Yes to discard the changes you made in the message definition file.

If you click No, the changes are not deleted, and the messages do not return to the default values.

3-20

4. CHECKING THE HARDWARE STATUS

CHAPTER 4 CHECKING THE HARDWARE STATUS
You can check the hardware status of this equipment by using the following methods:(1)

Checking by using a GUI
You can check the hardware status of this equipment by using a graphical interface. For details, see 4.1
Hardware Status Window.

(2)

Checking by using a user application
A user application can check the hardware status of this equipment by monitoring the status of event objects.
For details, see 4.2 RAS Event Notifications.
A user application can also obtain the hardware status of this equipment by using the RAS library. For
details, see 4.6 Status Acquisition by Using the RAS Library.

(3)

Checking on the desktop of this equipment
A pop-up message appears to notify users when errors occur in the hardware of this equipment. For details,
see 4.3 Pop-up Notifications.

(4)

Checking by using the digital LEDs for status indications on the front of this equipment
The digital LEDs for status indications are located on the front of this equipment and notify users whenerrors occur in the hardware of this equipment. These LEDs can also be used by user applications to, forexample, notify maintenance personnel of failures. For details, see 4.4 Functionality of the Digital LEDs for
Status Indications.

(5)

Checking from a remote device
A remote device can check the hardware status of this equipment. A remote device can also be notified
whenever the hardware status changes. For details, see 4.5 Remote Notifications.

4-1

4. CHECKING THE HARDWARE STATUS

4.1 Hardware Status Window
4.1.1 Overview
After you sign in to this equipment, there will always be an icon in the notification area of the taskbar to display
the hardware status. If you double-click or right-click this icon to display a pop-up menu and then click Display
Hardware status, detailed information about the hardware status of this equipment is displayed.
This window displays the following information:• Condition of the fan• Condition of the temperature inside the chassis• Drive failure prediction (SMART monitoring) condition• Drive power-on (used) hours• RAID status (B model only)

A/S model

B modelFigure 4-1 Hardware status window

NOTICE
When the Hardware status window shows an error in the hardware, resolve the problem
causing the error immediately.

NOTE• For information about how to replace a replaceable component, see the HF-W 2000 Model 58/55/50
INSTRUCTION MANUAL (manual number WIN-62-0073).
• This window displays only the internal drives that are recognized at OS startup. If you connect a new
drive or replace a drive with a new drive, for example, for maintenance, it might take a long time torecognize the new drive the first time the equipment starts up after the new drive is connected, andinformation about the drive might not be displayed. If such cases, restart this equipment.

4-2

4. CHECKING THE HARDWARE STATUS

4.1.2 Hardware status icon
There will always be an icon in the notification area of the taskbar to display the hardware status.

Note that, when you are using the factory default settings, the icon does not appear. If you click the arrow at theside of the notification area, the icon appears. If you want to always have the icon appear in the notification areaof the taskbar, right-click the task bar, and then from the menu that appears, click Settings. Then, in the windowthat appears, click Select which icons appear on the taskbar, and then turn on the icon for envdisp MFC
Application.

Right-click the taskbar to display the menu.

4-3

4. CHECKING THE HARDWARE STATUS

NOTE
In rare cases, registering the hardware status icon to the taskbar fails, and the following message appears.
If this happens, perform the following procedure to retry the registration of the hardware status icon.

1. Click OK in the dialog box.
2. Click Start.
3. In the list of applications, click RAS Software, and then click RAS Status

4-4

4. CHECKING THE HARDWARE STATUS(1)

List of displayed icons and description of each icon
Table 4-1 shows a list of displayed icons and a description of each icon. A description of the displayed icon
appears when you point the mouse to an icon.

Table 4-1 Hardware status iconNo.
1

HardwarestatusNormalIcon

Description of the icon
The hardware status is normal.

2

A fan failed.

3

An abnormal temperature was detected.

4

A fan failed. An abnormal temperature was detected.

5

A fan failed. A drive failure is possible.

6

An abnormal temperature was detected. A drive failure is possible.

7

A fan failed. An abnormal temperature was detected. A drive failure ispossible.

8

A fan failed. The power-on (used) hours exceeded the threshold.
Error

9

An abnormal temperature was detected. The power-on (used) hours exceeded
the threshold.

10

A fan failed. An abnormal temperature was detected. The power-on (used)
hours exceeded the threshold.

11

A RAID error was detected.

12

A fan failed. A RAID error was detected.

13

An abnormal temperature was detected. A RAID error was detected.

14

A fan failed. An abnormal temperature was detected. A RAID error was
detected.

15
16

CautionA drive failure is possible.
The power-on (used) hours exceeded the threshold.

Nos. 5 through 7 and 15: When both "The power-on (used) hours exceeded the threshold" and "A drive failure ispossible" happen at the same time, the description of the icon does not show "The power-on(used) hours exceeded the threshold".
Nos. 11 through 14: When both "A drive failure is possible" (or "The power-on (used) hours exceeded the threshold")
and the disconnection of a drive due to a RAID error (OFFLINE) happen at the same time, thedescription of the icon does not show "A drive failure is possible" (or "The power-on (used)
hours exceeded the threshold").
Nos. 15 and 16: If a hardware status error is detected at the same time, the icon for a hardware status error isdisplayed.

4-5

4. CHECKING THE HARDWARE STATUS

Figures 4-2 and 4-3 show examples of displaying the description of an icon when the hardware status of thisequipment is normal and when the hardware status has an error.

Figure 4-2 Example of displaying the description of an icon (when the hardware status is normal)

Figure 4-3 Example of displaying the description of an icon (when the hardware status has an error)(2)

Menu of the hardware status icon
If you right-click the icon, a pop-up menu appears.

Right-click the icon to display a popup menu.

Figure 4-4 Menu of the hardware status icon

● Display hardware status
Click this to display the Hardware status window.
● Undisplay the icon
Click this to delete the icon from the notification area of the taskbar.

4-6

4. CHECKING THE HARDWARE STATUS

4.1.3 Hardware status window
The Hardware status window shows the details of the hardware status of this equipment.
Figure 4-5 shows how to open the Hardware status window.

2. The Hardware status window opens.

Notification area of the taskbar

1. Double-click the hardware status icon.
Alternatively, right-click the icon to display a popup menu,
and then from the displayed menu, click Display hardware status.

Figure 4-5 Starting the Hardware status window

4-7

4. CHECKING THE HARDWARE STATUS(1)

Description of the window
1. Fan condition
This shows the current status of the fans.

Table 4-2 Fan condition and displayed information
Fan condition

Icon

Information

NormalThe fan is working normally.

Excessively low rotation speed

A fan failure was detected.
For details, refer to the event log.

2. Temperature condition
This shows the current status of the temperature inside the chassis.

Table 4-3 Temperature condition and displayed information
Temperature status

Icon

Information

NormalThe current temperature is normal.

Abnormally high temperature

The temperature in the unit has exceeded the maximum.

4-8

4. CHECKING THE HARDWARE STATUS

3. Drive condition
This shows the current status of the drives. In the following areas, the drive conditions of drive bay 1 anddrive bay 2 are displayed.

Table 4-4 Drive condition and displayed information
No.

Drive condition

Icon

Information

1

NormalThis condition is healthy.

2

Failure prediction by SMART

A failure might be imminent.

3

Excessive drive usage

The hours that the drive has been used exceed theprescribed value.

4

5

6
7

Error

The drive isoffline.

The drive is offline.

The driveis being rebuilt.

The drive is being rebuilt.

Unknown

Unknown

Not installed

No drive is connected.

Nos. 4 and 5: These descriptions apply only to the B model.

NOTICE
When the failure of a drive is anticipated, the drive might experience hardware failure in thenear future. We recommend backing up the data and replacing the drive. For information about
how to replace a drive, see the HF-W2000 Model 58/55/50 INSTRUCTION MANUAL (manual
number WIN-62-0073).

4-9

4. CHECKING THE HARDWARE STATUS

4. Drive typeThis displays the type of the drive.

Table 4-5 Drive type and displayed information
No.

Drive type

Displayed information

1

HDD

[HDD]

2

SSD

[SSD]

3

Unknown[---]

5. Drive used hours
The number of hours that the drive has been used (the cumulative hours to date) is displayed. The value ofthe cumulative hours is updated every hour between 0 and 100 hours, and every 10 hours after that. The
range of the cumulative hours that can be displayed is from 0 and 99990 (hours). If drive usage monitoringis disabled, the number of hours that the drive has been used cannot be displayed.

6. RAID status (B model only)
The RAID status is displayed.

Table 4-6 RAID status and displayed information
RAID status
No.

Detailed

Displayed information

Note

information
1
2

Normal3--

45DegradedUnknown[Optimal][Optimal (Media Error)]A media error occurred.

[Degrade][Degrade (Media Error)][Degrade (Rebuild: xx%)] xx: Progress of the rebuild process

Rebuilding

6
7

--

--

[Degrade (Rebuild: xx%,Media Error)][Unknown]

4-10

xx: Progress of the rebuild process
A media error occurred.

4. CHECKING THE HARDWARE STATUS

7. OFFLINE button (B model only)
Click this button to disconnect the corresponding drive from the RAID.
This button works only when the drive condition of a drive in the RAID is either "Normal", "Failure
prediction by SMART", or "Excessive drive usage".
To disconnect a drive, you must have administrator privileges. Sign in to the computer as an administrator
and click OFFLINE.
When you click OFFLINE, a confirmation message similar to the one shown in Figure 4-6 appears. To
disconnect the drive from the RAID and set the drive to offline, click Yes. If you click No, the drive will
not be disconnected.

Figure 4-6 Confirmation message when disconnecting the drive in drive bay 1

NOTE• A disconnected drive cannot be set back to online and used again. Before disconnecting a drive, ensurethat you have selected the correct drive to be disconnected.
• Note that if User Account Control (UAC) is disabled and a user without administrator privileges clicks
OFFLINE, the following message appears, and the drive will not be disconnected. When you need to
disconnect a drive, sign in to the computer as an administrator and click OFFLINE.

Figure 4-7 Message when a request to disconnect the drive in drive bay 1 is rejected• You cannot disconnect a drive from a remote session.

4-11

4. CHECKING THE HARDWARE STATUS

8. Refresh button
If you click this button, the latest hardware status is acquired, and the information in the window isrefreshed.
9. OK button
Click this button to close the Hardware status window
Figure 4-8 shows the Hardware status window when there is a hardware status error.

Figure 4-8 Hardware status window (example display in the case of an error)

4-12

4. CHECKING THE HARDWARE STATUS

4.2 RAS Event Notifications
4.2.1 Overview
When an event that must be reported to a user occurs, such as a hardware failure, this feature notifies anapplication of the event by setting an event object to the signaled state.
The application can detect event such as hardware failures by monitoring when the event objects are set to thesignaled state.
Event objects are reset to the nonsignaled state when the cause of the event is cleared.

4.2.2 Detecting an event
To detect an event:
1. Use the OpenEvent Windows API function to get the handle to the event object.
Specify SYNCHRONIZE for the parameter dwDesiredAccess (the access to the event object).
2. Use the WaitForSingleObject or WaitForMultipleObject Windows API function to monitor
when the event object is set to the signaled state.
Table 4-7 lists the events to be reported to a user and their respective event objects.

Table 4-7 Reported events
No.

Event

Event object name1

A system fan failure occurred.

W2KRAS_SYSFAN_ERR_EVENT

2A CPU fan failure occurred.

W2KRAS_CPUFAN_ERR_EVENT3

The temperature inside the chassis became abnormal.

W2KRAS_TEMP_ERR_EVENT

4

A remote shutdown request was generated.

W2KRAS_RMTSTDN_EVENT

5SMART anticipated a failure in one of the drives.

W2KRAS_HDD_PREDICT_EVENT

6

The power-on (used) hours exceeded the threshold for one of the drives. HFW_HDD_OVERRUN_EVENT

7

Frequent error corrections occurred in one of the memory slots.

8

A possible failure was detected in one of the memory slots.

9

The RAID status is normal.

HFW_RAID_OPTIMAL_EVENT10The RAID status is abnormal.

HFW_RAID_DEGRADE_EVENTHFW_MEMORY_ERR_EVENT

Nos. 7 and 8: The same event object name is assigned, because both events indicate a possible memory failure.
No. 10: The event object is also signaled if notification of media errors is enabled (set to ON) and a media error
occurs.

NOTE
When you use an event object in a program, you need to add Global＼ to the beginning of the name ofthe event object.

4-13

4. CHECKING THE HARDWARE STATUS

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 the name of thesample program and information about where you can find it, see 6.2 Sample Programs.

4-14

4. CHECKING THE HARDWARE STATUS

4.3 Pop-up Notifications
4.3.1 Overview
When an event that must be reported to a user occurs, such as a hardware failure, this feature notifies a user ofthe event by displaying a pop-up message on the desktop. By using this feature, a user can identify that an event
such as a hardware failure occurred.
More specifically, a pop-up message is displayed in the following cases:● A fan failure is detected.
● An abnormally high temperature is detected inside the chassis.
● A drive failure is anticipated (by SMART).
● The drive power-on (used) hours exceeded the threshold.
● An error correction in memory is frequently detected.
● A RAID error is detected (B model only).
Figure 4-9 shows an example pop-up message notification when a system fan failure has occurred.

Click the Close button [×]to close the window.

Click OK to close the window.

Figure 4-9 Example pop-up message notification

4-15

4. CHECKING THE HARDWARE STATUS

4.3.2 Messages to be displayed
Table 4-8 shows a list of the pop-up notification messages that this feature outputs.
You can edit these messages. For details about editing messages, see 3.1.4 Editing pop-up notification messages.

Table 4-8 Displayed messages
No.

Event

Pop-up notification message

1

A system fan failure occurred.

The revolutions of the system fan deteriorated significantly.

2

A CPU fan failure occurred.

The revolutions of the CPU fan deteriorated significantly.

3

The temperature inside the chassis became
abnormal.

The temperature has exceeded the prescribed value.

4

SMART anticipated a drive failure.

A failure might be imminent on the drive in drive bay %1.

5

The number of hours that the drive has been The number of hours that the drive in drive bay %1 has been
powered on (used) exceeds the threshold.
used has exceeded the prescribed value.

6

Frequent error corrections occur in memory. Error corrections occurred with high frequency in DIMM %1.

7

A possible memory failure was detected.

DIMM %1 might have failed.

8

A RAID error occurred.

The RAID status is DEGRADE. (Drive bay %1)

Nos. 4 and 5: %1 denotes the drive bay number.
Nos. 6 and 7: %1 denotes the DIMM slot number.
No. 8: This message is displayed for the B model only.

4.3.3 Pop-up notification settings
This feature can be enabled or disabled in the RAS Setup window. In the factory default settings, this feature isdisabled. If this feature is disabled, pop-up messages are not displayed.
For details, see 3.1.3 Using the RAS Setup window.

4-16

4. CHECKING THE HARDWARE STATUS

4.4 Functionality of the Digital LEDs for Status Indications
4.4.1 Overview
When an event that must be reported to a user occurs, such as a hardware failure, this feature notifies the user ofthe event by displaying a code via the digital LEDs for status indications located on the front of this equipment.
By using this feature, a user can identify when an event such as a hardware failure occurs.
In addition, a user application can output any code on the digital LEDs for status indications by using libraryfunctions. A code is displayed as a two-digit hexadecimal number.

The system status is displayed
as a two-digit hexadecimal code.

(1)

(2)

Status indication LEDs
(1) RAS status(2) Application status(3) BIOS status(3)

Figure 4-10 Digital LEDs for status indications

4-17

4. CHECKING THE HARDWARE STATUS

4.4.2 Displayed status codes(1)

Hardware status code
A hardware status code is displayed when an error has occurred in the hardware status of this equipment. If
the hardware status is normal, no hardware status code is displayed.
When a hardware status code is displayed, the leftmost LED in the status indication LEDs is lit.

If the hardware status is normal

If the hardware status is not normal

Off

On

Figure 4-11 Hardware status codes

Table 4-9 lists the hardware status codes.

Table 4-9 Hardware status codes
No.

Status code

1

12

A system fan failure occurred.

Cause

2

13

A CPU fan failure occurred.

3

21

The temperature inside the chassis became abnormal.

4

31

A failure is anticipated for the drive in drive bay 1.

5

32

A failure is anticipated for the drive in drive bay 2.

6

41

Drive bay 1 is offline.

742

Drive bay 2 is offline.

84c

RAID is in an unknown status.

Priority
2
3
4

1

9
4d
A RAID media error occurred.
Nos. 6 through 9: These status codes are displayed for the B model only.

If multiple failures occur at the same time, the status code with the highest priority (the status code with thesmallest value in the Priority column of Table 4-9) is displayed. If multiple failures with the same priority
occur at the same time, the status code of the failure that was detected last is displayed.

4-18

4. CHECKING THE HARDWARE STATUS(2)

Application status codes
An application status code is displayed by a user application by using the library functions provided by thisfeature.
When an application status code is displayed, the center LED of the status indication LEDs is lit.

On

Figure 4-12 Application status code(3)

Code displayed for a bug check (blue screen)This error code is displayed when a bug check (blue screen) occurs during system operation. Regardless ofthe status display mode, this error code is displayed with the highest priority. For information about the status
display modes, see 4.4.3 Status display modes.
When a bug check (blue screen) occurs, the status indication LEDs are lit as shown in Figure 4-13.
If the display code is not 80

On

If the display code is 80

On

On

Figure 4-13 Status indication LEDs when a bug check (blue screen) occurs

4-19

4. CHECKING THE HARDWARE STATUS

Table 4-10 shows a list of codes displayed when a bug check (blue screen) occurs.

Table 4-10 Codes displayed when a bug check (blue screen) occurs
No.

Code

1

F8

Cause

2

F9

3

FA

An uncorrectable memory error occurred.

4

Fb

The NMI button is pressed.

580

An error other than the preceding occurred.

A parity error occurred in the PCI bus.

For information about the priority used to display each code, see 4.4.4 Priorities of displayed codes.

4-20

4. CHECKING THE HARDWARE STATUS

4.4.3 Status display modes
This feature has two display modes: hardware status display mode and application status display mode.

Table 4-11 Status display modes
Status display mode

Description

Hardware status display mode

When the hardware status is normal, an application status code is displayed.
When the hardware status has an error, a hardware status code has higher
display priority.

Only an application code is displayed.
Application status display mode Even when the hardware status has an error, the hardware status code is not
displayed.

The status display mode can be configured in the RAS Setup window. The factory default setting is the hardware
status display mode.
For information about how to use the RAS Setup window, see 3.1.3 Using the RAS Setup window.
Note that if the hardware status is normal and there is no application status code to display, the LEDs are all off.
Figure 4-14 shows an example of what is displayed in the status display mode. The dotted lines in Figure 4-14
denote the respective display modes, and the thick line denotes the transition of the state of the LEDs.

Recovery from
hardware error
Hardware status
code is displayed

Hardwareerror occurs

Recovery from
hardware error

Hardwareerror occurs

Application status
code is displayed
User application stops
using the LEDs

LED is off
User application
starts using the LEDs

LEDs are requested byuser applications

Figure 4-14 Example of the status display mode

4-21

Time →

4. CHECKING THE HARDWARE STATUS

4.4.4 Priorities of displayed codes
The following shows the priorities of the codes displayed by this feature.

(1)

In the hardware status display mode

Table 4-12 Priority of codes in hardware status display mode
Code class

Priority order

Code displayed when a bug check (blue screen) occurs

1

Hardware status code2

Application status code3

• The code displayed when a bug check (blue screen) occurs has the highest priority.
• The priority of a hardware status code differs depending on its cause. For details, see 4.4.2 Displayed
status codes.

(2)

In the application status display mode

Table 4-13 Priority of codes in application status display mode
Code class

Priority order

Code displayed when a bug check (blue screen) occurs

1

Application status code2

• The code displayed when a bug check (blue screen) occurs has the highest priority.

4.4.5 Control functions for the digital LEDs for status indications
The following functions are offered as library functions for controlling the digital LEDs for status indications.
For details about the library functions, see 6.1 RAS Library.
 To display an application status code: Use the SetStCode7seg function.
 To turn off the currently displayed application status code: Use the TurnOff7seg function.
 To set the status display mode: Use the SetMode7seg function.

4-22

4. CHECKING THE HARDWARE STATUS

4.5 Remote Notifications
4.5.1 Overview
If you use this feature from a remote device, you can check hardware conditions over the network that, without
this feature, can only be checked when you are nearby this equipment. With this feature, even when hardware
conditions cannot be checked nearby this equipment because, for example, the system administrator is awayfrom this equipment or this equipment is built into the facility, the hardware conditions can be checked from aremote device.
This feature uses the Simple Network Management Protocol (SNMP) to notify users of hardware conditions.
This allows you to use commercially available network management software that supports SNMP and tomonitor distributed instances of this equipment and other devices, all from a single location.

NOTE• Remote notifications use SNMP, a protocol in the application layer of the TCP/IP, and User Datagram
Protocol (UDP) in the transport layer. This means that if the network load is high, the hardware
conditions might not be received properly.
• Remote notifications use the SNMP service, a standard feature of Windows®. For details about how to
enable the standard Windows® SNMP service, see 4.5.3 Enabling remote notifications.

4-23

4. CHECKING THE HARDWARE STATUS

4.5.2 Hardware conditions that can be acquired by using remote notifications
The following hardware conditions and settings can be acquired from a remote device:• Fan condition• Temperature condition inside the chassis• Drive condition• Memory condition• RAID status (B model only)• I/O status of the general-purpose external contacts• RAS feature settings• Operating mode (normal mode)• Version information of the extended Management Information Base (MIB) for HF-W

The following transitions of the hardware conditions are sent as notifications to users by using a trap.
(1)

Fan condition• Normal → Error• Error → Normal(2)

Temperature condition inside the chassis• Normal → Error• Error → Normal(3)

Drive condition• Normal → Failure anticipated• Normal → Used hours exceeded the threshold(4)

Memory condition• Normal → Frequent error corrections• Normal → Possible failure detected• Frequent error corrections → Normal(5)

RAID status (B model only)• Optimal → Error (Degrade, Unknown)• Error (Degrade, Unknown) → Optimal(6)

Operating mode
• HF-W stopped → Started in normal mode
• Running in normal mode → Running in simulation mode

4-24

4. CHECKING THE HARDWARE STATUS

4.5.3 Enabling remote notifications
This feature is disabled when you are using the factory default settings. Remote notifications use the standard
Windows® SNMP service. If you enable the SNMP service, remote notifications are enabled.
When using remote notifications, perform the following procedure to enable the SNMP service:(1)

Opening the SNMP Service Properties window
1. If you have not signed in to the computer as an administrator, do so.
2. Open the Services window:• Open the Control Panel.
• Double-click System and Security, Administrative Tools, and Services.
3. Double-click SNMP Service to open the SNMP Service Properties window.

4-25

4. CHECKING THE HARDWARE STATUS(2)

SNMP security configuration
1. In the SNMP Service Properties window, click the Security tab.

2. If you want to send a trap message whenever authentication fails, select the Send authentication trap
check box.
3. Under Accepted community names, click Add. The SNMP Service Configuration window is displayed.
In the Community rights list, select READ ONLY. In the Community Name box, enter the community
name that you want to use, and then click Add.

4. Specify whether to accept SNMP packets from hosts.
If you want to accept SNMP packets from any manager on the network:• Select Accept SNMP packets from any host.
If you want to restrict SNMP packets:• Select Accept SNMP packets from these hosts.
• Click Add.
• The SNMP Service Configuration window appears. Enter the host name or the IP or IPX address of thehost that you want to accept SNMP packets from, and then click Add.

5. In the SNMP Service Properties window, click Apply.

4-26

4. CHECKING THE HARDWARE STATUS(3)

SNMP trap configuration
1. In the SNMP Service Properties window, click the Traps tab.

2. Under Community name, enter the name of the community that trap messages are to be sent to, and thenclick Add to list.
3. Under Trap destinations, click Add. The SNMP Service Configuration window is displayed. Enter thehost name or the IP or IPX address of a destination that you want to send traps to, and then click Add.

4. In the SNMP Service Properties window, click Apply.

4-27

4. CHECKING THE HARDWARE STATUS(4)

Starting the SNMP service
1. In the SNMP Services Properties window, click the General tab.

2. Click Start. The SNMP service starts and remote notifications for hardware statuses are enabled.
3. To start the SNMP service automatically upon the next OS startup, in the Startup type list, selectAutomatic.
4. In the SNMP Service Properties window, click OK.

NOTE• If, when the SNMP service starts, there is an error for which notifications by using a trap is configured,
the trap is sent when the SNMP service starts.
• If Windows Firewall is configured to block the SNMP service, you cannot acquire the hardware statusof a remote device. If the firewall is set up to block the SNMP service, perform the following procedure
to undo the setting.
Note, however, that the SNMP service can pass through the Windows Firewall by default, so in that case
you do not have to perform the following procedure:
1. If you have not signed in to the computer as an administrator, do so.
2. Open the Control Panel, and then click System and Security.
3. Under Windows Firewall, click Allow app or feature through Windows Firewall.

4-28

4. CHECKING THE HARDWARE STATUS

4. The Allowed apps window appears. Click Change settings, and under Allowed apps and features,
select the SNMP Service check box.

5. Click OK.

4-29

4. CHECKING THE HARDWARE STATUS

4.5.4 Objects in the extended MIB for HF-W
To acquire the hardware status of this equipment from a remote device, use the extended MIB for HF-W. Thissection provides a list of objects defined in the extended MIB for HF-W and a description of these objects.
(1)

Objects related to the hardware conditions and settings
Table 4-14 lists the objects related to the hardware status and a description of these objects. The object ID ofeach object is obtained either by replacing the following x with the object in the following table or replacing
the following y with the object number in the table.
For N in the object number, specify a value in the range from 1 to the number of monitoring targets.
For z, specify the index number acquired from each entry.
However, for the extended MIB for HF-W, the value of N specified for acquisition of an index number is thesame as the index number that can be acquired. (If 1 is specified for N, the index number is 1.)

Object ID: .iso.org.dod.internet.private.enterprises.Hitachi.systemExMib.
hfwExMib.hfwRasStatus.x (where x is an object in the following table)
or.1.3.6.1.4.1.116.5.45.1.y (where y is an object number in the following table)

Table 4-14 Objects related to the hardware status(1/3)
ObjectnumberNo.

Object1

hfwFan.fanNumber

2

hfwFan.fanTable.fanEntry.fan
Index number of
1.2.1.1.N
Index
fanEntry3

hfwFan.fanTable.fanEntry.fan
1.2.1.2.z
Name

Fan name

System fan: System fan
CPU fan: CPU fan

4

hfwFan.fanTable.fanEntry.fan
1.2.1.3.z
StatusFan condition

1: Normal
2: Error5

hfwTemp.tempNumber

6

hfwTemp.tempTable.TempEntry.
Index number of
2.2.1.1.N
tempIndex
tempEntry

7

hfwTemp.tempTable.TempEntry.
2.2.1.2.z
tempName

Name of the temperature
to be monitored

Internal temperature:
Temperature inside thechassis8

hfwTemp.tempTable.TempEntry.
2.2.1.3.z
tempStatus

Temperature condition

1: Normal
2: Error9

hfwHdd.hddNumber

10

hfwHdd.hddTable.hddEntry.hdd
Index number of
3.2.1.1.N
Index
hddEntry

1.1.0

Description of the values

The number of monitored
fans

---

Number of monitored
temperatures

2.1.0

3.1.0

Description

Number of monitored
drive bays

4-30

---

---

4. CHECKING THE HARDWARE STATUS

(2/3)
No.

ObjectObjectnumberDescription11

hfwHdd.hddTable.hddEntry.hdd
3.2.1.2.z
StatusDrive condition12

hfwHdd.hddTable.hddEntry.hdd
3.2.1.3.z
UseTime

Drive power-on (used)hours(in hours)

13

hfwHdd.hddTable.hddEntry.hdd
3.2.1.4.z
Type

Drive type

Description of the values
1: Healthy
2: Not installed
3: Failure anticipated
5: Used hours exceeded thethreshold
7: Offline
8: Rebuild
12: Incomplete data
99: Unknown-1: HDD
2: SSD
99: Unknown

Number of monitored
memory slots--

15

hfwMem.memTable.memEntry.mem
5.2.1.1.N Index of memEntry
Index

--

16

hfwMem.memTable.memEntry.mem
5.2.1.2.z
Name

14 hfwMem.memNumber

17

5.1.0

hfwMem.memTable.memEntry.mem
5.2.1.3.z
Status18 hfwRaid.raidNumber

4.1.0

DIMM name

DIMM1: DIMM1 slot
DIMM2: DIMM2 slot

Memory condition

1: Normal
2: Error (Frequent error
corrections occur or apossible failure is detected.)
3: Not installed

Number of monitored
arrays--19

hfwRaid.raidTable.raidEntry.
Index number of
4.2.1.1.N
raidIndex
raidEntry

20

hfwRaid.raidTable.raidEntry.
4.2.1.2.z
raidStatus

RAID status

1: Optimal
2: Degrade
4: Unknown

21

hfwRaid.raidTable.raidEntry.
4.2.1.3.z
raidLevel

RAID level

1: RAID1

22

hfwRaid.raidTable.raidEntry.
4.2.1.4.z
raidProgress

Progress of the rebuild
process (in %)--23

hfwRaid.raidTable.raidEntry.
4.2.1.5.z
raidMediaError

Whether a media error
occurred

1: No media error occurred.
2: Media error occurred.

Number of generalpurpose external contact
inputs--24 hfwGenDI.gendiNumber
25

6.1.0

hfwGenDI.gendiTable.gendiEnt
Index number of
6.2.1.1.N
ry.gendiIndex
gendiEntry

4-31

--

--

4. CHECKING THE HARDWARE STATUS

(3/3)
No.

ObjectObjectnumberDescription

Description of the values

26

hfwGenDI.gendiTable.gendiEntr
y.gendiName

6.2.1.2.z

GENDI: GENDI contact
Name of general-purpose GENDI0: GENDI0 contact
external input contact
GENDI1: GENDI1 contact
GENDI2: GENDI2 contact27

hfwGenDI.gendiTable.gendiEntr
y.gendoStatus

6.2.1.3.z

Input status of general0: Openpurpose external contact 1: Closed

7.1.0

Number of generalpurpose external contact -outputs

28 hfwGenDO.gendoNumber29

hfwGenDO.gendoTable.gendoEntr
y.gendoIndex

Index number of
7.2.1.1.N gendoEntry30

hfwGenDO.gendoTable.gendoEntr
y.gendoName

7.2.1.2.z

GENDO0: GENDO0 contact
Name of general-purpose
GENDO1: GENDO1 contact
external output contact
GENDO2: GENDO2 contact31

hfwGenDO.gendoTable.gendoEntr
y.gendoStatus

7.2.1.3.z

Output status of general- 0: Openpurpose external contact 1: Closed--

No. 1: For this equipment, the value is set to 2.
No. 5: For this equipment, the value is set to 1.
No. 9: The number of internal drives that can be installed in the HF-W is set for the number of monitored drive bays.
For this equipment, the value is set to 2.
No. 14: The number of memory slots is set for the number of monitored memory slots.
For this equipment, the value is set to 2.
No. 18: For models other than the B model, the value is set to 0.
Nos. 19 through 23: These are supported by the B model only.
No. 24: For this equipment, the value is set to 4.
No. 28: For this equipment, the value is set to 3.

4-32

4. CHECKING THE HARDWARE STATUS

Table 4-15 shows a list of the objects related to the RAS feature settings and a description of those objects.
The object ID of each object is obtained either by replacing the following x with the object in the following
table or replacing the following y with the object number in the table.

Object ID: .iso.org.dod.internet.private.enterprises.Hitachi.systemExMib.
hfwExMib.hfwRasSetting.x (where x is an object in the following table)
or.1.3.6.1.4.1.116.5.45.2.y (where y is an object number in the following table)

Table 4-15 Objects related to the RAS feature settings
No.

ObjectnumberObjectDescription of
the values

Description

1

hfwFanAutoShutdown

1

Automatic shutdown when a fan failure occurs

1: Enabled
2: Disabled2

hfwTempAutoShutdown

2

Automatic shutdown when the temperature isabnormal

1: Enabled
2: Disabled3

hfwRemoteShutdown3

Automatic shutdown when a remote shutdown is 1: Enabled
requested
2: Disabled

Table 4-16 shows a list of the objects related to operating modes and a description of those objects. The
object ID of each object is obtained either by replacing the following x with the object in the following tableor replacing the following y with the object number in the table.

Object ID: .iso.org.dod.internet.private.enterprises.Hitachi.systemExMib.
hfwExMib.hfwRasInfo.x (where x is an object in the following table)
or.1.3.6.1.4.1.116.5.45.3.y (where y is an object number in the following table)

Table 4-16 Objects related to operating modes
No.
1

ObjecthfwRasMode

Objectnumber
1

Description
Operating mode

4-33

Description of the values
1: Normal mode
2: Simulation mode

4. CHECKING THE HARDWARE STATUS

Table 4-17 shows a list of the objects related to the version information of the extended MIB for HF-W and a
description of those objects. The object ID of each object is obtained either by replacing the following x withthe object in the following table or replacing the following y with the object number in the table.

Object ID: .iso.org.dod.internet.private.enterprises.Hitachi.system.
hfw.hfwExMibInfo.x (where x is an object in the following table)
or.1.3.6.1.4.1.116.3.45.1.y (where y is an object number in the following table)

Table 4-17 Objects related to the extended MIB for HF-W
No.

ObjectObjectnumberDescription

Description of
the values

1

Version1

Version number of the extended MIB for HF-W--

2

Revision

5

Revision number of the extended MIB for HFW

--

4-34

4. CHECKING THE HARDWARE STATUS(2)

Objects related to trap notifications
Table 4-18 shows a list of the objects related to trap notifications when an error occurs, as well as a
description and notification data for those objects. The enterprise ID for the trap notification when an error
occurs is as follows:Enterprise ID: .iso.org.dod.internet.private.enterprises.Hitachi.systemAP.
hfwMibTrap.hfwRasErrorTrap
or.1.3.6.1.4.1.116.7.45.1

Table 4-18 Objects related to the trap notification (when an error occurs)
(1/2)
No.

ObjectTrap
number

hfwFanError
1

Description
A fan failure
occurs.

1

hfwTempError2

2

hfwSmartDet
ect

Object used

Name of the failed fan

fanStatus

2: ErrorhfwFanStMsg

Revolution of %1
deteriorated remarkably.
Internal temperature

44

hfwMemError
5

6

2: ErrorInternal temperature
exceeded prescribed value.

hddIndex

The drive bay number of the drive forwhich a failure is anticipated by
SMART

hddStatus

3: Failure anticipated
A failure may be imminent
on the drive of the drive
bay%2.

hfwSmartStMsg

hfwHddOverR
un

Value

fanName

The temperature tempName
inside the chassis tempStatus
becomes
hfwTempStMsg
abnormal.
A failure is
anticipated forthe drive.

3

3

Notification data

The drive power- hddIndex
on (used) hours
exceeded thethreshold.
hddStatus

The drive bay number of the drive forwhich the power-on hours exceeded thethreshold

5: Used hours exceeded the threshold.
hfwHddUseTimeSt Used hours on the drive ofMsg
the drive bay%2 exceeded
prescribed value.
memNameFrequent error
Name of the memory slot with frequentcorrections occur.
error corrections
memStatus
2: Error (frequent error correction)
hfwMemStMsg

4-35

In the %3, error correcting
have occurred with highfrequency.

4. CHECKING THE HARDWARE STATUS

(2/2)
No.

ObjectTrap
numberhfwMemFailu
re6

8

hfwArrayErr
or

7

7

Description

Notification data
Object used

memNameA possible
memory failure is
detected.
memStatus

A RAID error
occurs.

hfwMemFailMsg
raidIndex
hfwArrayStMsg

Value
Name of the memory slot for which a
possible memory failure was detected
2: Error (possible memory failure
detected)%3 failure might occur.
1
An error occurred on
Array%4.

No. 1: %1 denotes the name of the failed fan.
Nos. 3 and 4: %2 denotes the drive bay number.
Nos. 5 and 6: %3 denotes the name of the memory slot for which error corrections occur frequently or for which a
possible memory failure was detected.
No. 7:%4 denotes the number of the array with an error. For this equipment, the array number is always 1.
Table 4-19 shows a list of the objects related to the trap notification when the equipment has recovered froman error and a description of those objects. The enterprise ID for the trap notification when the equipment has
recovered from an error is as follows:Enterprise ID: .iso.org.dod.internet.private.enterprises.Hitachi.systemAP.
hfwMibTrap.hfwRasRecoverTrap
or.1.3.6.1.4.1.116.7.45.2

Table 4-19 Objects related to trap notifications (when the equipment has recovered from an error)
No.

ObjectTrap
numberRecovery fromabnormaltemperature in
the chassis

tempName
tempStatus
hfwTempStMsg

6

Recovery fromfrequent error
corrections

memNamememStatus
hfwMemStMsg

7

Recovery fromRAID error

raidIndex
hfwArrayStMsg

hfwTempReco
ver2

hfwMemRecover
3

4

hfwArrayRec
overObject used
fanNamefanStatus
hfwFanStMsg

1

2

Notification data

Recovery fromfan failure

hfwFanRecover
1

Description

No. 1: %1 denotes the name of the recovered fan.

4-36

Value
Name of the recovered fan
1: Normal
Revolutions of %1 returned
to normal value.
Internal temperature
1: Normal
Internal temperature
returned to prescribedvalue.
Name of the recovered memory slot
1: Normal
In the %2, frequency of theerrorcorrectings deteriorated.
1
Array%3 is restored.

4. CHECKING THE HARDWARE STATUS

No. 3: %2 denotes the name of the memory slot that recovered from frequent error corrections.
No. 4: %3 denotes the number of the array that recovered from an error. For this equipment, the array number isalways 1.

Table 4-20 shows a list of the objects related to trap notifications when the equipment starts in normal mode
and a description of those objects. The enterprise ID for the trap notifications related to operating modes is asfollows:

Enterprise ID: .iso.org.dod.internet.private.enterprises.Hitachi.systemAP.
hfwMibTrap.hfwRasInfoTrap
or.1.3.6.1.4.1.116.7.45.3

Table 4-20 Objects related to trap notifications (operating modes)
Notification data

No.

ObjectTrap
numberhfwRasServi
ce
Started1

Startup in normalmode

hfwRasMode

1

2

Transition tosimulation mode

hfwRasMode2

hfwSimulati
on
ModeStarted

Description

Object used
hfwRasStartMsg

hfwRasStartMsg

Value
1: Normal mode
RAS Service isrunning.
2: Simulation mode
RAS Service switchedto Simulation Mode.

4.5.5 Extended MIB file for HF-W
The extended MIB file for HF-W is as follows:

Extended MIB file for HF-W: %ProgramFiles%＼HFWRAS＼mib＼hfwExMib.mib

4-37

4. CHECKING THE HARDWARE STATUS

4.6 Status Acquisition by Using the RAS Library
You can use the RAS library to acquire the following hardware conditions. For details about the RAS library, see 6.1
RAS Library.
● To acquire the memory condition: Use the GetMemStatus function.
● To acquire the drive condition: Use the hfwDiskStat function.
● To acquire the RAID status: Use the hfwRaidStat function (B model only).

4-38

5. CONTROLLING THE HARDWARE

CHAPTER 5 CONTROLLING THE HARDWARE
The RAS features can exercise the following controls over this equipment:(1) Automatic shutdown of the equipment
When a hardware error occurs or a remote shutdown request through the contact input is detected, the equipment can
automatically shutdown. For details, see 5.1 Automatic Shutdown of the Equipment.

(2) Controlling the hardware by using the RAS library
A user application can control the hardware of this equipment by using the RAS library. For details, see 5.2 Controllingthe Hardware by Using the RAS Library.

(3) Displaying and controlling the RAID status by using the RAID configuration control command
The RAID configuration control command displays the status of the RAID and its drives. The command can forcibly
disconnect a drive and change the RAID settings. For details, see 5.3 RAID Configuration Control Command (raidctrl)(B Model Only).

5-1

5. CONTROLLING THE HARDWARE

5.1 Automatic Shutdown of the Equipment
This feature automatically shuts down the equipment when running the equipment would pose a danger, when a fan
failure or an abnormally high temperature is detected. Automatically shutting down the equipment can protect theinternal parts, such as the processor, from thermal degradation and can prevent thermal runaway of the system due toa malfunction of this equipment. The equipment can be also be automatically shutdown by a remote shutdown signal
input from an external device.

5.1.1 Automatic shutdown upon detection of a fan failure
When the equipment detects an error in one of the fans, the equipment automatically shuts down.
• This feature can be enabled or disabled in the RAS Setup window. When using the factory default settings,
this feature is enabled. For details, see 3.1.3 Using the RAS Setup window.
• Alternatively, a user application can detect a fan failure by using a RAS event and shutdown the equipment.
For information about RAS events, see 4.2 RAS Event Notifications.

NOTICE If this equipment continues to operate after a fan failure is detected, internal parts such as
the processor will not cool sufficiently, which might cause the thermal runaway of the system
due to a malfunction in the equipment, or result in damage to parts. If possible, enable theautomatic shutdown feature.
 If the automatic shutdown feature is not used, have a user application detect fan failures byusing a RAS event, and shutdown the equipment when such failures are detected.

NOTE
For details about how to replace a fan, see the HF-W2000 Model 58/55/50 INSTRUCTION MANUAL(manual number WIN-62-0073).

5-2

5. CONTROLLING THE HARDWARE

5.1.2 Automatic shutdown when detecting an abnormally high temperature
When the temperature sensor in this equipment detects that the temperature is abnormally high inside the chassis,
the equipment automatically shuts down.
• This feature can be enabled or disabled in the RAS Setup window. When using the factory default settings,
this feature is disabled. For details, see 3.1.3 Using the RAS Setup window.
• Alternatively, a user application can detect abnormally high temperatures by using a RAS event and shutdown
the equipment. For details about RAS events, see 4.2 RAS Event Notifications.

NOTE• If the temperature inside the chassis is high, parts can degrade rapidly due to heat. In this case,continuing to use this equipment is not advisable in terms of the equipment life. On the other hand, if
the temperature is abnormally high when the fans are working properly, the abnormally hightemperature must be caused by an external factor, such as malfunctioning air conditioning at thelocation of the equipment. You can isolate the cause of the abnormally high temperature while theequipment is running. Because of this, this feature is disabled when you are using the factory default
settings.
• If you continue to operate this equipment after an abnormally high temperature is detected and thetemperature further rises to a dangerous level, the equipment forcibly shuts down and the power turns
off. This is intended to prevent erratic system operation and the destruction of parts, and occurs
regardless of whether this feature is disabled.

5.1.3 Automatic shutdown when a remote shutdown request is detected through the contact input
If this feature is enabled, this equipment automatically shuts down when the remote shutdown contact(RMTSTDN contact) in the RAS external contact interface is closed. Using this feature allows you to shutdown
this equipment from a remote location.
• This feature can be enabled or disabled in the RAS Setup window. When using the factory default settings,
this feature is enabled. For details, see 3.1.3 Using the RAS Setup window.
• Alternatively, a user application can detect a remote shutdown request through the contact input by using a
RAS event and shutdown the equipment. For information about RAS events, see 4.2 RAS Event Notifications.

5-3

5. CONTROLLING THE HARDWARE

5.2 Controlling the Hardware by Using the RAS Library
By using the RAS library functions, you can shutdown the system and control the general-purpose external contacts
and the digital LEDs for status indications. For details about the library functions, see 6.1 RAS Library.
● To shutdown the system: Use the BSSysShut function.
● To control the watchdog timer: Use the WdtControl function.
● To control the general purpose-external contact outputs: Use the GendoControlEx and GendoControl
functions.
● To control the general-purpose external contact inputs: Use the GetGendiEx and GetGendi functions.
● To control the digital LEDs for status indications: Use the SetStCode7seg, TurnOff7seg, and
SetMode7seg functions.

5-4

5. CONTROLLING THE HARDWARE

5.3 RAID Configuration Control Command (raidctrl) (B Model Only)
The raidctrl command displays the status of the RAID and its drives. The command can also forcibly disconnect
a drive and change the RAID settings. This command can be launched from the command prompt. The followingshows how to use this command.

Nameraidctrl - RAID drive status display and configuration control, settings updates

Syntaxraidctrl [/OFFLINE drive-number] [/NOTIFY [{ON|OFF}]] [/INCOMPLETE [{ON|OFF}]][/REBUILD] [/LOAD[{H|M|L}]] [/MANUAL [{ON|OFF}]]

Functionality
The raidctrl command displays the status of the RAID and the drives in the RAID, controls theconfiguration of those drives, and changes the settings for RAID. This command offers one of the following
features depending on the specified options.
• With no options:
The status of the RAID and the drives in the RAID is displayed.
• When the /OFFLINE option is specified:
The specified drive is forcibly disconnected and set to offline.
• When the /NOTIFY option is specified:
You can switch whether notifications are sent through the interface of this equipment when a media error
occurs.
• When the /INCOMPLETE option is specified:
You can select whether to disconnect a drive if there is any possibility of a data mismatch between the drives.
• When the /REBUILD option is specified:
The rebuild process is started on all drives ready for the process.
• When the /LOAD option is specified:
You can specify the level of the load on the system during the rebuild process.
• When /MANUAL option is specified:
You can select whether to start a rebuild process manually or automatically when a drive is replaced.

NOTE• You must have administrator privileges to execute this command, excepting cases where you executethe command without specifying any options.
Open a command prompt as an administrator, and then execute the raidctrl command.
In addition, you cannot execute those actions from a remote session, excepting cases where you executethe command without specifying any options.
• Do not run multiple instances of this command at the same time.

5-55. CONTROLLING THE HARDWARE(1)

Displaying the status of the RAID and its drives (without specifying any options)If you execute the raidctrl command without specifying any options, the command will output the statusof the RAID and the drives in the RAID on this equipment. Tables 5-1 and 5-2 show the status of the RAID
and drives displayed in the output.

Table 5-1 RAID status displayed in the output of the raidctrl commandNo.

Displayed Status

Description

1

OPTIMAL

The RAID is working properly.

2

DEGRADEThe RAID is being degraded.

3

DEGRADE (REBUILD xx%)UNKNOWN

The RAID is undergoing a rebuilding process.

4
Unknown status
Nos. 1 through 3: If a media error occurs, (MEDIA ERROR) is appended to the end of the displayed status.
Example: If a media error occurs when the RAID is operating normally:
OPTIMAL (MEDIA ERROR)

Table 5-2 Drive status displayed in the output of the raidctrl commandNo.

Displayed Status

Description

1

ONLINEThe drive is working properly.

2

OFFLINE

The drive is disconnected from the RAID.

3

INCOMPLETE DATA

The drive is disconnected from RAID because of data
mismatch between drives.

4

REBUILDThe RAID is undergoing a rebuilding (copying) process.

5

NOT CONNECTED

The drive is not connected.

6

UNKNOWN

Unknown status

The following is an example of the output when the raidctrl command is executed without specifying
any options:C:＼>raidctrl
ARRAY STATUS
1
DEGRADEDRIVE STATUS
1
ONLINE2
OFFLINEC:＼>

5-6

5. CONTROLLING THE HARDWARE(2)

Disconnecting a drive (by specifying the /OFFLINE option)
If you execute the raidctrl command with the /OFFLINE option, the specified drive is forcibly
disconnected and set to offline.
This option can be used only when the RAID status is OPTIMAL. Only 1 or 2 can be specified for drivenumber. If you specify any other values, an error message is displayed, and the command exits.
The following is an example of executing the /OFFLINE command to disconnect a drive bay 1. When amessage is displayed to confirm whether you want to disconnect, enter y to actually disconnect the drive bay 1.
If you enter n, disconnecting the drive bay 1 is canceled, and the command exits.

C:＼>raidctrl /OFFLINE 1
The drive of the drive bay1 will be made offline.
Are you sure you want to continue with this process? [y/n]yAn offline request on the drive of the drive bay1 was sent.
C:＼>

NOTE
A disconnected drive cannot be set to online and used again.
Make sure that you select the correct drive.

(3)

Switching whether notifications are sent regarding media errors when they occur (by specifying the/NOTIFY option)
If you execute the raidctrl command by specifying the /NOTIFY option, you can switch the setting forwhether notifications are sent regarding media errors when they occur.
If the /NOTIFY option is specified alone, the current notification setting is displayed.
When using the factory default settings, notifications are not sent regarding media errors.
The following are examples of executing the command by specifying the /NOTIFY option.
• To check the media error notification setting: raidctrl /NOTIFY

C:＼>raidctrl /NOTIFY
MEDIA ERROR Notify Setting:ONC:＼>• To enable media error notifications: raidctrl /NOTIFY ON• To disable media error notifications: raidctrl /NOTIFY OFF

5-7

5. CONTROLLING THE HARDWARE(4)

Switching when incomplete data occurs (by specifying the /INCOMPLETE option)
If you execute the raidctrl command by specifying the /INCOMPLETE option, you can select whether todisconnect or to continue using the drive in drive bay 2 if there is any possibility of a data mismatch between
the drives due to, for example, an unexpected power shutdown. If the /INCOMPLETE option is specified
without ON or OFF, the current setting is displayed. The factory default setting is OFF (continue using thedrive).
This setting is enabled after restarting the equipment.
The following are examples of executing the command with the /INCOMPLETE option.
• To check the incomplete data setting: raidctrl /INCOMPLETE

C:＼>raidctrl /INCOMPLETE
Incomplete Data Setting:OFFC:＼>• To disconnect the drive if there is any possibility of a data mismatch: raidctrl /INCOMPLETE ON• To continue using the drive even if there is any possibility of a data mismatch:raidctrl /INCOMPLETE OFF

5-8

5. CONTROLLING THE HARDWARE(5)Starting the rebuilding process (by specifying the /REBUILD option)
If you execute the raidctrl command with the /REBUILD option, the rebuilding process starts when it ispossible to do so. If the /REBUILD option is specified, the rebuilding process starts under one of thefollowing conditions:• The drive in drive bay 2 is disconnected because the possibility of a data mismatch between drives is
detected. (That is, the drive status of drive bay 1 is ONLINE and the drive status of drive bay 2 isINCOMPLETE DATA.)• A new drive is installed when the rebuild start method setting is MANUAL. (That is, one of the drive
statuses of the two drives is ONLINE and the other is OFFLINE.)

NOTE• Even when one of the drive statuses is ONLINE and the other is OFFLINE, the rebuilding process does
not start for the OFFLINE drive if the drive status of the drive was set to OFFLINE due to a failure. A
rebuilding process starts for an OFFLINE drive only if the drive status of the drive was set to
OFFLINE because the drive was newly installed.

The following are examples of executing the command by using the /REBUILD option.

C:＼>raidctrl /REBUILD
This might take several seconds to start rebuild.
Are you sure you want to continue with this process? [y/n] yThis command completeed successfully.
C:＼>

NOTE
• The rebuilding process takes time to start. If the rebuilding process does not start within 3 minutes,
check the system log in the event log of Windows®.

5-9

5. CONTROLLING THE HARDWARE(6)

Setting the load during a rebuilding process (with the /LOAD option)
If you execute the raidctrl command by using the /LOAD option, you can set the level of the write loadon the system to the drive during a rebuilding process. If the /LOAD option is specified without H, M, or L,
the current setting is displayed. You can adjust the write load by changing this setting. Be aware, however,that the lower the load, the longer the rebuilding process takes to finish. When you change this setting, the
new setting is effective after this equipment restarts. The factory default setting is H (perform the rebuilding
process with a high load).
The following are examples of executing the command with the /LOAD option:

C:＼>raidctrl /LOAD
Rebuild Load Level:HIGH
C:＼>• To select a high load (HIGH): raidctrl /LOAD H• To select a medium load (MIDDLE): raidctrl /LOAD M• To select a low load (LOW): raidctrl /LOAD L(7)

Switching the rebuilding start method (by specifying the /MANUAL option)
If you execute the raidctrl command by using the /MANUAL option, you can select whether to start therebuilding process manually when a drive is replaced. If the /MANUAL option is specified without ON or
OFF, the current setting is displayed. The factory default setting is OFF (the rebuilding process starts
automatically).
This setting is enabled after the equipment restarts.
The following are examples of executing the command by specifying the /MANUAL option.
• To check the settings of the method used to start rebuilding: raidctrl /MANUAL

C:＼>raidctrl /MANUAL
Manual Rebuild:OFFC:＼>• To start the rebuilding process manually after a drive is replaced: raidctrl /MANUAL ON• To start the rebuilding process automatically after a drive is replaced: raidctrl /MANUAL OFF

5-10

5. CONTROLLING THE HARDWARE

Diagnosis
When the raidctrl command finishes normally, it returns the exit code 0.
If the command terminates abnormally, one of the error messages listed in Table 5-3 is displayed, and thecommand returns an exit code other than 0.

Table 5-3 Error messages of the raidctrl commandNo.
1

Error message

Description

2

Usage:raidctrl [/OFFLINE drive-number][/NOTIFY [{ON|OFF}]][/INCOMPLETE[{ON|OFF}]][/REBUILD][/LOAD [{H|M|L}]][/MANUAL [{ON|OFF}]]Specified Drive is invalid.

3

There is an error in the specified options.
Specify the options correctly.

The drive is not in a valid drive status.

No valid drive found.

No valid drive was found.

4

An error occurred in %1. errorcode= %2

An unexpected error (%2) occurred in the function (%1).
Retry the command. If the same error message persists,
restart this equipment.

5

You do not have the privilege to
execute this command option.
Please execute this command option
again on "Administrator: Command
Prompt".

You do not have administrator privileges.
Log on to the computer as an administrator, and then run
the command again. If User Account Control (UAC) is
enabled, open a command prompt as an administrator,
and then run the command.

6

Access denied.
Log on console session,
And execute this command option again
on "Administrator: Command Prompt".

You cannot use this command by specifying this option
from a remote session.
Log on to a console session and run the command again.
If User Account Control (UAC) is enabled, open a
command prompt as an administrator , and then run thecommand again.

7

raidctrl: This function was executed on The command was executed on a model other than the Ba non-RAID model.
model.
This command can be executed only on the B model.

5-11This page is intentionally left blank.

6. LIBRARY FUNCTIONSCHAPTER 6 LIBRARY FUNCTIONS
A user application can get and control the hardware status of this equipment by using the library functions provided
by the RAS features.
For information about the hardware specifications of the RAS external contact interface described in this chapter andhow to use each contact, see the HF-W2000 Model 58/55/50 INSTRUCTION MANUAL (manual number WIN-620073).

6.1 RAS Library
6.1.1 Overview
This chapter describes the interface for the library functions provided by the RAS features.
Table 6-1 lists the RAS library functions.

Table 6-1 RAS library functions
No.

Function nameUse

1

BSSysShutShuts down the equipment.

2

WdtControl

Retriggers, gets the status of, and stops the watchdog timer.

3

GendoControl

Opens and closes the general-purpose external contact output(GENDO0) (for backward compatibility).

4

GendoControlEx

Opens and closes the general-purpose external contact outputs(GENDO0, GENDO1, and GENDO2).

5

GetGendi

Gets the status of the general-purpose external contact input(GENDI) (for backward compatibility).

6

GetGendiEx

Gets the status of the general-purpose external contact inputs(GENDI, GENDI0, GENDI1, and GENDI2).

7

MconWriteMessage

Records a specified message (characters) in the log files of thisequipment.

8

GetMemStatus

Acquires the condition of the memory installed in this equipment.

9

hfwDiskStat

Acquires the status of a drive.

10 hfwRaidStat

Acquires the RAID status (B model only).

11 SetStCode7seg

Outputs an application status code by using the digital LEDs forstatus indications.

12 TurnOff7seg

Clears an application status code from the digital LEDs for statusindications.

13 SetMode7seg

Configures the status display mode of the digital LEDs for statusindications.

DLL
w2kras.dll

hfwras.dll
ctrl7seg.dll

These functions are offered by the DLLs (w2kras.dll, hfwras.dll, and ctrl7seg.dll).

6-1

6. LIBRARY FUNCTIONS

NOTE
Do not copy or move w2kras.dll, hfwras.dll, or ctrl7seg.dll to another directory. If you doso, the RAS features of this equipment cannot run properly.

The functions offered by w2kras.dll and ctrl7seg.dll can be called from Visual Basic®, which
requires .NET. When you call the functions numbered 1 through 7 and 11 through 13 from Visual Basic®, add_VB to the end of the name of each function. The function parameters are the same. For example, when you callthe WdtControl function from Visual Basic®, use the function name WdtControl_VB.

The following files are provided as import libraries:%ProgramFiles%＼HFWRAS＼lib＼w2kras.lib%ProgramFiles%＼HFWRAS＼lib＼hfwras.lib%ProgramFiles%＼HFWRAS＼lib＼ctrl7seg.lib
When you use a library, link the corresponding import library.

The following files are provided as header files for the libraries:%ProgramFiles%＼HFWRAS＼include＼w2kras.h%ProgramFiles%＼HFWRAS＼include＼hfwras.h%ProgramFiles%＼HFWRAS＼include＼ctrl7seg.h
When you use a library in C, include the corresponding header file.

6-2

6. LIBRARY FUNCTIONS

6.1.2 Shutdown function (BSSysShut)Name
BSSysShut - System shutdown

Syntax#include <w2kras.h>int BSSysShut(reboot-argument)
int reboot; /*Reboot flag*/

Description
BSSysShut shuts down the system.
The reboot argument is used to specify whether to reboot the system after a shutdown.
reboot-argument = 0: The power to this equipment turns off after a shutdown.
reboot-argument ≠ 0: The system reboots after a shutdown.

Diagnosis
0: Successful completion (system shutdown processing has started)
1: Shutdown privilege acquisition error
2: Internal error (OS shutdown failed)

Sample program
We provide a sample program that uses this function in C. For the name of the sample program andinformation about where you can find it, see 6.2 Sample Programs.

6-3

6. LIBRARY FUNCTIONS

6.1.3 Watchdog timer control function (WdtControl)(1)Function interface

Name
WdtControl - Watchdog timer control and status acquisition

Syntax#include <w2kras.h>
BOOL WdtControl(DWORD dwCmd, PDWORD pdwCount);

Description
This function performs the action specified by dwCmd on the watchdog timer.
To use this function, in the RAS Setup window, select Retriggered by application program. under
Watchdog timer setting. If the watchdog timer setting is different, this function terminates with an error. If
you call the GetLastError Windows API function, the error code W2KRAS_WDT_NONMANUAL is returned.
The following describes the parameters of this function.

dwCmd:
This parameter specifies the action to perform on the watchdog timer. The following options are available
for this parameter.

Table 6-2 Actions for WdtControl that are specified by dwCmd
dwCmd

Explanation of the action

WDT_SET (0x00)

Specifies the timeout value in seconds.

WDT_STOP (0x01)

Stops the watchdog timer.

WDT_STAT (0x02)

Acquires the status of the watchdog timer.

If a value other than these is specified, the function terminates with an error. If you call the GetLastError
Windows API function, the error code W2KRAS_INVALID_PARAMETER is returned.
pdwCount:If dwCmd is WDT_SET, you can configure the timeout value of the watchdog timer by using the variable
pointed to by pdwCount and calling this function.
Specify a value from 1 to 63 in seconds. If a value outside this range is specified, the function terminateswith an error. If you call the GetLastError Windows API function, the error code
W2KRAS_INVALID_PARAMETER is returned.
When this function returns, the value of the variable pointed to by pdwCount is undefined. Do not use thevalue.
If dwCmd is WDT_STOP, the value of pdwCount is ignored. When this function returns, the value of thevariable pointed to by pdwCount is undefined. Do not use the value.
If dwCmd is WDT_STAT, the remaining time in seconds until the watchdog timer expires when thefunction is called is stored in the variable pointed to by pdwCount. If the value of the variable pointed to

6-4

6. LIBRARY FUNCTIONS

by pdwCount is 0 when the function returns, the watchdog timer has already timed out.
Note that the value of the variable pointed to by pdwCount when the function is called is ignored.
Diagnosis
If this function ends successfully, the function returns TRUE. If the function terminates with an error, thefunction returns FALSE.
If this function terminates with an error, call the GetLastError Windows API function to get the error code.
The error codes returned by this function itself are as follows:
Error code (value)

Description

W2KRAS_INVALID_PARAMETER(0x2001)W2KRAS_WDT_NONMANUAL(0x2002)

The specified parameters contain an error.

W2KRAS_NOT_INITIALIZE(0x2005)W2KRAS_INTERNAL_ERROR(0x2007)

Startup of the RAS software is not yet complete.

This function cannot be used because Retriggered byapplication program. is not selected under Watchdog timer
setting in the RAS Setup window.

An internal error occurred.

Other error codes come from the Windows API functions used by this function. For details about these error
codes, see the Windows API Help.

Sample program
We provide a sample program that uses this function in C. For the name of the sample program andinformation about where you can find it, see 6.2 Sample Programs.
For information about how to monitor the operational state of a user program by using the watchdog timer, see
2.7.2 Using a watchdog timer to monitor user programs.

6-5

6. LIBRARY FUNCTIONS(2)

Behavior of the WDTTO contact of the RAS external contact interface
This section describes the behavior of the WDTTO contact of the RAS external contact interface under thefollowing conditions:● When the equipment starts
The WDTTO contact is closed.
● When the OS starts
The WDTTO contact is closed when the OS starts. The WDTTO contact opens when the watchdog timer isretriggered by the automatic retriggering feature for the watchdog timer or by the WdtControl function.
● When the WdtContol function is calledIf dwCmd is WDT_SET:The WDTTO contact opens. If the watchdog timer is not retriggered afterward within the specified
timeout period, the contact closes. If the watchdog timer is retriggered when the contact is closed, the
WDTTO contact opens.
If dwCmd is WDT_STOP:
The WDTTO contact opens. In this case, the countdown of the watchdog timer is stopped andconsequently the watchdog timer does not time out.
● When the automatic retriggering feature for the watchdog timer is used
The WDTTO contact opens. The process for this function runs at the idle priority. If the amount of CPU
time used by processes with a priority higher than the idle priority class exceeds a set value, the watchdog
timer times out and the contact closes. Thereafter, when CPU time becomes available and the process forthis function can run, the watchdog timer resumes being retriggered and the WDTTO contact opens.
Figure 6-1 shows an example of the behavior of the WDTTO contact when an application controls thewatchdog timer by using the WdtControl function. In this example, the timeout of the watchdog timer
specified by the WdtControl function is 10 seconds.

6-6

6. LIBRARY FUNCTIONS

WDT is retriggered.
WdtControl function is called.
Power turns on. (Timeout: 10 seconds)
WDT times out.

Power turns off.

Contact open
(normal)
WDT has stopped.
10 seconds
Contact closed(WDT has timed out.)

WDT isretriggered.

OS startup

Time →

WDT is retriggered.

WDT stops.
WdtControl function is called.

Figure 6-1 Behavior of the WDTTO contact

The dotted lines in Figure 6-1 denote the states of the contact and the thick line denotes the transition of thestate of the contact.
Figure 6-2 shows an example of the behavior of the WDTTO contact when the OS shuts down. In thisexample, the timeout of the watchdog timer is 60 seconds. The process that retriggers the watchdog timer
terminates during shutdown, and consequently the watchdog timer times out.

WDT is retriggered.

OS shutdown starts.

WDT times out.

Power turns off.

Contact open
(normal)
60 seconds
Contact closed(WDT has timed out.)
Time →

WDT isretriggered.
WDT is retriggered.

Figure 6-2 Behavior of the WDTTO contact (when the OS shuts down)

The dotted lines in Figure 6-2 denote the states of the contact and the thick line denotes the transition of thestate of the contact.

NOTE
This explanation assumes that the RAS external contact interface is HJ-F2050-11. If you are using HJF2050-12 as the RAS external contact interface, the behavior of the contact is the opposite of what isshown here. The contact is open when the contact described in the figure is closed, and vice versa.

6-7

6. LIBRARY FUNCTIONS

6.1.4 Control functions for the general-purpose external contact outputs (GendoControl andGendoControlEx)
Use the GendoControl and GendoControlEx functions to control the outputs to the general-purpose
external contact of the RAS external contact interface.
(1)

Function interface (GendoControl)

Name
GendoControl - Output control for the general-purpose external contact (GENDO0)

Syntax#include <w2kras.h>
BOOL GendoControl(DWORD dwCmd);

Description
This function performs the action specified by dwCmd on the general-purpose external contact (GENDO0) of
the RAS external contact interface. This function is for backward compatibility only.
Table 6-3 lists the actions that can be specified by dwCmd.

Table 6-3 List of actions of the GendoControl function specified by dwCmd
dwCmd

Explanation of the action

GENDO_OPEN (0x00)

Opens the general-purpose external contact (GENDO0).

GENDO_CLOSE (0x01)

Closes the general-purpose external contact (GENDO0).

If a value other than these is specified, the function terminates with an error. If you call the
GetLastError Windows API function, the error code W2KRAS_INVALID_PARAMETER is returned.
Diagnosis
If this function ends successfully, the function returns TRUE. If the function terminates with an error, thefunction returns FALSE.
If this function terminates with an error, call the GetLastError Windows API function to get the error code.
The error codes returned by this function itself are as follows:
Error code (value)
W2KRAS_INVALID_PARAMETER(0x2001)W2KRAS_NOT_INITIALIZE(0x2005)W2KRAS_INTERNAL_ERROR(0x2007)

Description
The specified parameters contain an error.
Startup of the RAS software is not yet complete.
An internal error occurred.

Other error codes come from the Windows API functions used by this function. For details about these error
codes, see the Windows API Help.

6-8

6. LIBRARY FUNCTIONS(2)Function interface (GendoControlEx)

Name
GendoControlEx - Output control for the general-purpose external contact (GENDO0, GENDO1, GENDO2)

Syntax#include <w2kras.h>
BOOL GendoControlEx(DWORD dwPort, DWORD dwCmd);

Description
This function performs the action specified by dwCmd on the general-purpose external contact (GENDO0,
GENDO1, or GENDO2) of the RAS external contact interface specified by dwPort.
Table 6-4 lists the actions that can be specified by dwPort.

Table 6-4 List of actions of the GendoControlEx function specified by dwPort
dwPortExplanation of the action

GENDO0_PORT (0x01)

Performs the action on the general-purpose external contact(GENDO0).

GENDO1_PORT (0x02)

Performs the action on the general-purpose external contact(GENDO1).

GENDO2_PORT (0x03)

Performs the action on the general-purpose external contact(GENDO2).

Table 6-5 lists the actions that can be specified by dwCmd.

Table 6-5 List of actions of the GendoControlEx function specified by dwCmd
dwCmd

Explanation of the action

GENDO_OPEN (0x00)

Opens the general-purpose external contact specified by
dwPort.

GENDO_CLOSE (0x01)

Closes the general-purpose external contact specified by
dwPort.

If a value other than these is specified, the function terminates with an error. If you call the GetLastError
Windows API function, the error code W2KRAS_INVALID_PARAMETER is returned.

6-9

6. LIBRARY FUNCTIONS

Diagnosis
If this function ends successfully, the function returns TRUE. If the function terminates with an error, thefunction returns FALSE.
If this function terminates with an error, call the GetLastError Windows API function to get the error code.
The error codes returned by this function itself are as follows:
Error code (value)
W2KRAS_INVALID_PARAMETER(0x2001)W2KRAS_NOT_INITIALIZE(0x2005)W2KRAS_INTERNAL_ERROR(0x2007)

Description
The specified parameters contain an error.
Startup of the RAS software is not yet complete.
An internal error occurred.

Other error codes come from the Windows API functions used by this function. For details about these error
codes, see the Windows API Help.

Sample program
We provide a sample program that uses this function in C. For the name of the sample program andinformation about where you can find it, see 6.2 Sample Programs.
(3)

Behavior of the general-purpose external contact (GENDO0, GENDO1, or GENDO2) of the RAS external
contact interface
These general-purpose external contacts open when the power turns on or off.
Figure 6-3 shows the behavior of the GENDO0 contact when the GendoControl function is used.

Power turns off.

Contact open

Contact closed
Power turns on.

Time →

GendoControl function
is executed.
(GENDO_CLOSE)

GendoControl
function is executed.
(GENDO_OPEN)

GendoControl function is
executed. (GENDO_CLOSE)

Figure 6-3 Behavior of the GENDO contact

The dotted lines in Figure 6-3 denote the states of the contact and the thick line denotes the transition of thestate of the contact.
The explanation in this section applies to both RAS external contact interfaces, the HJ-F2050-11 and the HJF2050-12.

6-10

6. LIBRARY FUNCTIONS

6.1.5 Get functions for the general-purpose external contact inputs (GetGendi and GetGendiEx)
Use the GetGendi and GetGendiEx functions to get the inputs for the general-purpose external contact of
the RAS external contact interface.
(1)

Function interface (GetGendi)

Name
GetGendi - Status acquisition of the general-purpose external contact input (GENDI)

Syntax#include <w2kras.h>
DWORD GetGendi(VOID);

Description
This function gets the status of the general-purpose external contact input (GENDI) of the RAS external
contact interface. This function is for backward compatibility only.
To use this function, in the RAS Setup window, clear the Automatically shutdown if remote shutdown isrequested. check box under Shutdown setting. If this check box is selected, the function terminates with anerror. If you call the GetLastError Windows API function, the error code W2KRAS_RMTSTDN_ON isreturned.

Return values
1: External contact GENDI is closed.
0: External contact GENDI is open.
0xffffffff: The function terminated with an error.

Diagnosis
If this function terminates with an error, the function returns 0xffffffff.
If this function terminates with an error, call the GetLastError Windows API function to get the error code.
The error codes returned by this function itself are as follows:
Error code (value)

Description

W2KRAS_RMTSTDN_ON(0x2003)

This function cannot be used because the Automatically
shutdown if remote shutdown is requested. check box isselected under Shutdown setting in the RAS Setup window.

W2KRAS_NOT_INITIALIZE(0x2005)W2KRAS_INTERNAL_ERROR(0x2007)

Startup of the RAS software is not yet complete.
An internal error occurred.

Other error codes come from the Windows API functions used by this function. For details about these error
codes, see the Windows API Help.

6-11

6. LIBRARY FUNCTIONS(2)Function interface (GetGendiEx)

Name
GetGendiEx - Status acquisition of the general-purpose external contact inputs (GENDI, GENDI0,
GENDI1, and GENDI2)

Syntax#include <w2kras.h>
DWORD GetGendiEx(DWORD dwPort);

Description
This function gets the status of the general-purpose external contact inputs (GENDI, GENDI0, GENDI1,
and GENDI2) of the RAS external contact interface that was specified by dwPort.
Table 6-6 lists the actions that can be specified by dwPort.

Table 6-6 List of actions of the GetGendiEx function specified by dwPort
dwPortExplanation of the action

GENDI_PORT (0x00)

Gets the status of the general-purpose external contact(GENDI).

GENDI0_PORT (0x01)

Gets the status of the general-purpose external contact(GENDI0).

GENDI1_PORT (0x02)

Gets the status of the general-purpose external contact(GENDI1).

GENDI2_PORT (0x03)

Gets the status of the general-purpose external contact(GENDI2).

If a value other than these is specified, the function terminates with an error. If you call the
GetLastError Windows API function, the error code W2KRAS_INVALID_PARAMETER is returned.
If you want to specify GENDI_PORT for dwPort and get the status of GENDI, in the RAS Setup window,
clear the Automatically shutdown if remote shutdown is requested. check box under Shutdown setting.
If this check box is selected, the function terminates with an error. If you call the GetLastError
Windows API function, the error code W2KRAS_RMTSTDN_ON is returned.

Return values
1: The external contact specified by dwPort is closed.
0: The external contact specified by dwPort is open.
0xffffffff: The function terminates with an error.

6-12

6. LIBRARY FUNCTIONS

Diagnosis
If this function terminates with an error, the function returns 0xffffffff.
If this function terminates with an error, call the GetLastError Windows API function to get the error
code. The error codes returned by this function itself are as follows:
Error code (value)

Description

W2KRAS_INVALID_PARAMETER(0x2001)W2KRAS_RMTSTDN_ON(0x2003)

The specified parameters contain an error.

W2KRAS_NOT_INITIALIZE(0x2005)W2KRAS_INTERNAL_ERROR(0x2007)

Startup of the RAS software is not yet complete.

This function cannot get the status of GENDI because theAutomatically shutdown if remote shutdown isrequested. check box is selected under Shutdown settingin the RAS Setup window.

An internal error occurred.

Other error codes come from the Windows API functions used by this function. For details about theseerror codes, see the Windows API Help.

Sample program
We provide a sample program that uses this function in C. For the name of the sample program andinformation about where you can find it, see 6.2 Sample Programs.

6-13

6. LIBRARY FUNCTIONS

6.1.6 Log function (MConWriteMessage)

Name
MConWriteMessage - Logging

Syntax#include <w2kras.h>
VOID WINAPI MConWriteMessage(LPSTR lpBuffer);

Description
The MConWriteMessage function writes the specified message (characters) to a log file. The file name ishfwrasa.log or hfwrasb.log.
The message is written along with the time stamp.
Two log files are available, and the size of each file is 64 KB. When the size of the log recorded in the log filethat is currently being used exceeds 64 KB, the log file used for logging switches to the other log file.
The following describes the parameters of this function.
lpBuffer:
This parameter specifies a pointer to a string that contains the message (characters) to be written.
To easily identify the application that records each log entry, specify a message that starts with the nameof the application, as shown in the following example.
Checking log information
This function records log information in text format in the following files. When the size of the log recorded in
the log file that is currently being used exceeds 64 KB, the log file used for logging switches to another log file.
• %ProgramFiles%＼HFWRAS＼log＼hfwrasa.log• %ProgramFiles%＼HFWRAS＼log＼hfwrasb.log
You can check log information by opening the files described here by using an application such as Notepad.
The format of the log information is as follows:

YYYY/MM/DD hh:mm:ss - Specified log information
YYYY/MM/DD hh:mm:ss - Specified log information
YYYY/MM/DD hh:mm:ss - Specified log information
:

YYYY
MM
DD
hh
mm
ss

: Year: Month: Day: Hour (24-hour clock): Minute: Second

Figure 6-4 Format of log information

Initially, each of the files contains an EOF character (ASCII code 0x1a).

6-14

6. LIBRARY FUNCTIONS

Sample program
We provide a sample program that uses this function in C. For the name of the sample program andinformation about where you can find it, see 6.2 Sample Programs.

NOTICEThe log function exits asynchronously without waiting for data to actually be written to a log file.
This means that this function does not return an error even when writing to a log file fails forsome reason. We recommend recording important information in the OS event log.

NOTE
• This function has the same name as the message console function provided by the Hitachi software
W2K-PLUS, but this function does not output to the message console.
• To reduce the amount of resources used, this function, for example, opens and closes a pipe every time
the function is called. This means that this function has a relatively large overhead. Even when you arerecording multiple message lines, use one function call to output the message.
• This function does not support Unicode strings. Always use ANSI strings. Log entries for messages are
stored in text files. In these text files, the combination of the two characters ＼r＼n is interpreted as a
newline.
If you want to include a newline character in a string specified by lpbuffer, insert ＼r＼n in the string.

6-15

6. LIBRARY FUNCTIONS

6.1.7 Get function for the memory condition (GetMemStatus)

Name
GetMemStatus - Memory status acquisition

Syntax#include <w2kras.h>
BOOL GetMemStatus(PMEM_DATA pMemData);

Description
The GetMemStatus function sets the condition of the memory in this equipment in the structure pointed toby pMemData. The following describes the parameters of this function.

pMemData:
This parameter specifies a pointer to a MEM_DATA structure that stores the acquired memory condition.
typedefstruct MEM_DATA {int

Dimm_Number;//Number of DIMM slots in this equipment

DWORD

Dimm_Status[4];//Condition of each DIMM

} MEM_DATA, *PMEM_DATA;
When this function ends successfully, the maximum number of DIMMs is stored in Dimm_Number.
Each element of Dimm_Status stores a value described in the following table. Note that the number ofvalid elements is Dimm_Number. (For example, if Dimm_Number is 2, the elements up to
Dimm_Status[1] are valid.) The elements after that are reserved. The values of these reserved
elements are undefined. Do not use these values.

Table 6-7 List of values stored in Dimm_Status
Value

Description

MEMORY_NOMAL (0x00)

The memory is working properly.

MEMORY_ERR_DETECT (0x01)

Frequent error correction occurs or a possible failure is
detected.

MEMORY_NOT_MOUNTED (0x02)

No DIMMs are installed.

6-16

6. LIBRARY FUNCTIONS

For this model, the correspondence between the Dimm_Status elements and DIMM names is as follows:
Element

DIMM nameDimm_Status[0]DIMM1

Dimm_Status[1]DIMM2

Diagnosis
If this function ends successfully, the function returns TRUE. If the function terminates with an error, thefunction returns FALSE. When this function terminates with an error, the value stored in pMemData is invalid.
If this function terminates with an error, call the GetLastError Windows API function to get the error code.
The error codes returned by this function itself are as follows:
Error code (value)
W2KRAS_INVALID_PARAMETER(0x2001)W2KRAS_NOT_INITIALIZE(0x2005)W2KRAS_MEMST_INVALID(0x2007)

Description
The specified parameters contain an error.
Startup of the RAS software is not yet complete.
The memory condition cannot be acquired.

Other error codes come from the Windows API functions used by this function. For details about these error
codes, see the Windows API Help.

Sample program
We provide a sample program that uses this function in C. For the name of the sample program andinformation about where you can find it, see 6.2 Sample Programs.

6-17

6. LIBRARY FUNCTIONS

6.1.8 Get function for the drive condition (hfwDiskStat)Name
hfwDiskStat - Drive status acquisition

Syntax#include <hfwras.h>
BOOL hfwDiskStat(PHFW_DISK_STATUS phfwDiskStatus);

Description
The hfwDiskStat function sets the drive conditions in a structure pointed to by phfwDiskStatus.
The following describes the parameters of this function.

phfwDiskStatus:
This parameter specifies a pointer to an HFW_DISK_STATUS structure that stores the drive conditions.
typedefstruct HFW_DISK_STATUS{
DWORD

Disk_Count;

DWORD

Disk_Status[16];//Drive condition} HFW_DISK_STATUS, *PHFW_DISK_STATUS;
Disk_Count stores the number of arrays in the valid Disk_Status.

6-18

6. LIBRARY FUNCTIONS

Disk_Status[n] stores the logical sum of the values for the type (the upper 16 bits) and condition (thelower 16 bits) of the drive in drive bay n + 1. Table 6-8 shows the values stored in Disk_Status.

Table 6-8 List of values stored in Disk_Status

Disk_Status
Upper 16 bits
Lower 16 bits

Description

0x0001The drive type is HDD.

0x0002The drive type is SDD.

0x0001The drive is working properly.

0x0002The drive is disconnected from the RAID.#2

0x0004

A new drive is connected to the RAID and is being rebuilt.#2

0x0008

Drive failure prediction (SMART) is detected.

0x0010A drive is not connected.

0x0020The drive condition could not be acquired.

0x0040The drive power-on (used) hours exceeded the threshold.#1

0x0400The drive is disconnected from the RAID (incomplete data).#2#1: This value is not stored if drive usage monitoring is disabled.
#2: This value is returned for the B model only.

Note that if multiple conditions exist at the same time, the logical sum of the values shown in Table 6-8 is stored.
• If drive failure prediction (SMART) is detected and the drive power-on (used) hours exceeded the threshold at
the same time:
0x0048 is stored in the lower 16 bits of Disk_Status.

6-19

6. LIBRARY FUNCTIONS

Table 6-9 lists the defined values relating to the drive type and condition.

Table 6-9 List of defined values
Defined value
DRIVETYPE_HDD(0x00010000)
DRIVETYPE_SSD(0x00020000)
DISKSTAT_HEALTHY(0x00000001)
DISKSTAT_OFFLINE(0x00000002)
DISKSTAT_REBUILD(0x00000004)
DISKSTAT_SMART(0x00000008)
DISKSTAT_NOT_CONNECTED(0x00000010)
DISKSTAT_UNKNOWN(0x00000020)
DISKSTAT_OVERRUN(0x00000040)
DISKSTAT_INCOMPLETE_DATA(0x00000400)

Description
The drive type is HDD.
The drive type is SDD.
The drive is working properly.
The drive is disconnected from the RAID.
A new drive is connected to the RAID and is being rebuilt.
Drive failure prediction (SMART) is detected.
A drive is not connected.
The drive condition could not be acquired.
The drive power-on (used) hours exceeded the threshold.
The drive is disconnected from the RAID (incomplete data).

6-20

6. LIBRARY FUNCTIONS

Diagnosis
If this function ends successfully, the function returns TRUE. If the function terminates with an error, thefunction returns FALSE. When this function terminates with an error, the value stored in phfwDiskStatus isinvalid.
If this function terminates with an error, call the GetLastError Windows API function to get the error code.
The error codes returned by this function itself are as follows:
Error code (value)
HFWRAS_INVALID_PARAMETER(0x20000001)
HFWRAS_NOT_INITIALIZE(0x20000002)
HFWRAS_INTERNAL_ERROR(0x20000003)

Description
The specified parameters contain an error.
Startup of the RAS software is not yet complete.
An internal error occurred.

Other error codes come from the Windows API functions used by this function. For details about these error
codes, see the Windows API Help.

Sample program
We provide a sample program that uses this function in C. For the name of the sample program andinformation about where you can find it, see 6.2 Sample Programs.

6-21

6. LIBRARY FUNCTIONS

6.1.9 Get function for the RAID status (hfwRaidStat) (B model only)Name
hfwRaidStat - RAID status acquisition

Syntax#include <hfwras.h>
BOOL hfwRaidStat(PHFW_RAID_STATUS phfwRaidStatus);

Description
The hfwRaidStat function sets the RAID status in the structure pointed to by phfwRaidStatus.
The following describes the parameters of this function.

NOTE
The hfwRaidStat function cannot acquire the drive status. Use the hfwDiskStat function toacquire the drive status.

phfwRaidStatus:
This parameter specifies a pointer to an HFW_RAID_STATUS structure that stores the RAID status.
typedefstruct HFW_RAID_STATUS{
DWORDArray_Count;// Number of monitored arrays

HFW_ARRAY_STATUS

Array[16];// Array information} HFW_RAID_STATUS, *PHFW_RAID_STATUS ;Array_Count shows the number of monitored RAID arrays on this equipment (1).
Each element of Array shows the status of the corresponding RAID. The number of valid elements isreturned in Array_Count. (This value is 1, which means only Array[0] is valid.) The elements afterthat are reserved. The values of these reserved elements are NULL. Do not access these elements. The
HFW_ARRAY_STATUS structure is defined as follows:
typedefstruct HFW_ARRAY_STATUS{
DWORD

Level;//RAID level

DWORD

Disk_Number;//Drives in the RAIDDWORDStatus;//RAID status

DWORD

Progress;//Progress (0% - 99%)

} HFW_ARRAY_STATUS, *PHFW_ARRAY_STATUS ;6-22

6. LIBRARY FUNCTIONS

Level stores the RAID level. The meaning of each value that can be stored in Level is as follows:

Table 6-10 Values stored in Level in the HFW_ARRAY_STATUS structureNo.
1Defined value
HFW_RAID1 (0x00000001)

Description
RAID1 is set up.

DiskNumber sets the value that indicates the drive bays used by the RAID. The set value is the logical sum of
the following, which for this equipment is always 0x00000003.

Table 6-11 Values stored in DiskNumber in the HFW_ARRAY_STATUS structure
No.

Defined value

Description

1

HFW_DISK1 (0x00000001)

Drive bay 1 is used by the RAID.

2

HFW_DISK2 (0x00000002)

Drive bay 2 is used by the RAID.

Status stores the value that indicates the RAID status. The logical sum of some of the following values is set.
Numbers 1 through 3 denote RAID statuses, and numbers 4 and 5 denote detailed information.

Table 6-12 Values stored in Status in the HFW_ARRAY_STATUS structure
No.
1
2
3
4
5

Defined value
HFW_RAID_OPTIMAL(0x00000001)
HFW_RAID_DEGRADE(0x00000004)
HFW_RAID_UNKNOWN(0x00000008)
HFW_RAID_REBUILD(0x00010000)
HFW_RAID_MEDIA_ERROR(0x00020000)

Description
The RAID is working properly.
The RAID has degenerated.
The RAID status is unknown.
One of the drives is being rebuilt.
A media error occurred.

For example, while the rebuilding process is underway, the RAID status is that the RAID has degenerated(HFW_RAID_DEGRADE) and the detailed information is that a drive is being rebuilt (HFW_RAID_REBUILD).
Therefore, the logical sum of these two (HFW_RAID_DEGRADE | HFW_RAID_REBUILD) is set in Status.

6-23

6. LIBRARY FUNCTIONS

Possible combinations are as follows:

Table 6-13 Possible combinations that can be set in Status in the HFW_ARRAY_STATUS structure
No.

RAID status

1

HFW_RAID_OPTIMALNone
HFW_RAID_MEDIA_ERROR

HFW_RAID_DEGRADE

4None
HFW_RAID_MEDIA_ERROR

5

HFW_RAID_REBUILD

6

HFW_RAID_REBUILD | HFW_RAID_MEDIA_ERROR

2
3

7

HFW_RAID_UNKNOWN

Detailed information

None

For Progress, the progress of the rebuilding process is set. If the RAID status value (Status) does notcontain HFW_RAID_REBUILD, 0 is set.

Diagnosis
If this function ends successfully, the function returns TRUE. If the function terminates with an error, thefunction returns FALSE. When this function terminates with an error, the value stored in phfwRaidStatus isinvalid.
If this function terminates with an error, call the GetLastError Windows API function to get the error code.
The error codes returned by this function itself are as follows:
Error code (value)
HFWRAS_INVALID_PARAMETER(0x20000001)
HFWRAS_NOT_INITIALIZE(0x20000002)
HFWRAS_INTERNAL_ERROR(0x20000003)
HFWRAS_NOT_RAID(0x20000101)

Description
The specified parameters contain an error.
Startup of the RAS software is not yet complete.
An internal error occurred.
This equipment on which this function is being executed
is not a RAID model.

Other error codes come from the Windows API functions used by this function. For details about these error
codes, see the Windows API Help.

Sample program
We provide a sample program that uses this function in C. For the name of the sample program andinformation about where you can find it, see 6.2 Sample Programs.

6-24

6. LIBRARY FUNCTIONS

6.1.10 Control functions for the digital LEDs for status indications (SetStCode7seg, TurnOff7seg,
SetMode7seg)(1)

Application status code display function (SetStCode7seg)

Name
SetStCode7seg - Displaying an application status code
Syntax#include <ctrl7seg.h>
BOOL SetStCode7seg(DWORD dwStCode);
Description
This function outputs an application status code to the digital LEDs for status indications. On the digital LEDs
for status indications, the value specified by this function is displayed in hexadecimal.
The following describes the parameters of this function.
dwStCode:This parameter specifies an application status code to be displayed by using the LEDs. You can specify avalue from 0 to 255. If a value outside this range is specified, the function terminates with an error. If you
call the GetLastError Windows API function, the error code CTRL7SEG_INVALID_PARAMETER
is returned.
Diagnosis
If this function ends successfully, the function returns TRUE. If the function terminates with an error, thefunction returns FALSE.
If this function terminates with an error, call the GetLastError Windows API function to get the error code.
The error codes returned by this function itself are as follows:
Error code (value)
CTRL7SEG_INVALID_PARAMETER(0x2001)

Description
The specified parameters contain an error.

Other error codes come from the Windows API functions used by this function. For details about these error
codes, see the Windows API Help.
Sample program
We provide a sample program that uses this function in C. For the name of the sample program andinformation about where you can find it, see 6.2 Sample Programs.

6-25

6. LIBRARY FUNCTIONS(2)Application status code clear function (TurnOff7seg)

Name
TurnOff7seg - Turning off an application status code
Syntax#include <ctrl7seg.h>
BOOL TurnOff7seg(VOID);
Description
This function clears the application status code currently displayed on the digital LEDs for status indications.
When this function is called, the digital LEDs for status indications turn off.
Diagnosis
If this function ends successfully, the function returns TRUE. If the function terminates with an error, thefunction returns FALSE.
If this function terminates with an error, call the GetLastError Windows API function to get the error code.
The error code comes from the Windows API functions used by this function. For details about the error codes,
see the Windows API Help.
Sample program
We provide a sample program that uses this function in C. For the name of the sample program andinformation about where you can find it, see 6.2 Sample Programs.

6-26

6. LIBRARY FUNCTIONS(3)

Status display mode setup function (SetMode7seg)

Name
SetMode7seg - Setting up the status display mode
Syntax#include <ctrl7seg.h>
BOOL SetMode7seg(DWORD dwMode);
Description
This function configures the status display mode of the digital LEDs for status indications.
The following describes the parameters of this function.
dwMode:This parameter specifies the status display mode of the digital LEDs for status indications.
Table 6-14 lists the values that can be specified by dwMode.

Table 6-14 List of values specified by dwMode in the SetMode7seg function
dwModeExplanation of the action

APPST_MODE (0x00)

Selects the application status display mode.

RASST_MODE (0x01)

Selects the status display mode.

If a value other than these is specified, the function terminates with an error. If you call the GetLastError
Windows API function, the error code CTRL7SEG_INVALID_PARAMETER is returned.
Diagnosis
If this function ends successfully, the function returns TRUE. If the function terminates with an error, thefunction returns FALSE.
If this function terminates with an error, call the GetLastError Windows API function to get the error code.
The error codes returned by this function itself are as follows:
Error code (value)
CTRL7SEG_INVALID_PARAMETER(0x2001)

Description
The specified parameters contain an error.

Other error codes come from the Windows API functions used by this function. For details about these error
codes, see the Windows API Help.
Sample program
We provide a sample program that uses this function in C. For the name of the sample program andinformation about where you can find it, see 6.2 Sample Programs.

6-27

6. LIBRARY FUNCTIONS

6.2 Sample Programs
Sample programs file in C that use the RAS library functions are stored in the %ProgramFiles%＼HFWRAS＼
sample directory. Use these files for reference when you develop a program or to verify the operation of thefunctions.
Table 6-15 lists the sample programs.

Table 6-15 List of provided sample programs
No.

File name

Description

1

shutd.c

Sample program for the BSSysShut function

2

wdt.c

Sample program for the WdtControl function

3

gendoex.c

Sample program for the GendoControlEx function

4

gendiex.c

Sample program for the GetGendiEx function

5

MCon.cSample program for the MconWriteMessage function

6

MemErr.c

Sample program for the GetMemStatus function

7

hfwDiskStat.c Sample program for the hfwDiskStat function

8

7seg.cSample program for the control functions of the digital LEDs for statusindications (SetStCode7seg, TurnOff7seg, and SetMode7seg)

9

FanErr.c

Sample program for detecting RAS events (For information about RAS event
notifications, see 4.2 RAS Event Notifications.)

10

hfwRaidStat.c Sample program for the hfwRaidStat function

6-28

7. FEATURES RELATED TO MAINTENANCE AND FAILURE ANALYSISCHAPTER 7 FEATURES RELATED TO MAINTENANCE AND FAILUREANALYSIS
7.1 Notifications Regarding the Cause of a Bug Check (Blue Screen)
7.1.1 Overview
This equipment records the contents of memory in memory dump files when the system is forcibly recoveredfrom an OS lockup, an NMI is generated due to a hardware failure, or an uncorrectable memory error occurs. At
the same time, a blue screen appears and the identification name (NMI_HARDWARE_FAILURE or
WHEA_UNCORRECTABLE_ERROR) appears.
In addition, the code corresponding to the cause of the bug check (blue screen) appears on the digital LEDs forstatus indications installed on the equipment.
This feature detects bug checks (blue screens) and records the cause of the bug checks (blue screens) in the event
log the next time that the OS starts.

NOTE• If you perform an action (for example, a shutdown) that aborts processing during an analysis of thecause of a bug check (blue screen), the cause might not be recordable in the event log. In the case of a 4
GB memory dump file, analyzing the cause of a bug check (blue screen) takes about three minutes.

7-1

7. FEATURES RELATED TO MAINTENANCE AND FAILURE ANALYSIS

7.1.2 Supported causes of a bug check (blue screen)This feature is activated when a bug check (blue screen) appears because of one of the causes described in Table
7-1. Errors due to causes not shown in Table 7-1 are not supported, and 80 is displayed on the digital LEDs forstatus indications installed on the equipment.

Table 7-1 Supported causes of bug checks (blue screens)
Cause

Cause code#1

An NMI is generated by the NMI
Fbbutton.#3
An NMI is generated due to a parity F8 or F9
error at the PCI bus, LPC bus, orelsewhere.
An uncorrectable memory errorFAoccurred.

Contents recorded in the Description columnof the event log#2
A reset signal was input.
The detail code is 0x9201.
A PCI bus parity error occurred.#3
The detail code is 0x9202.
An uncorrectable error occurred in #4.
The detail code is #5.

#1: This code is displayed on the digital LEDs for status indications installed on the equipment.
#2: The event log is shown in Table 7-2.
#3: If the unit is not correctly installed in the expansion slot, a PCI bus parity error (detail code: 00x9202) might bedisplayed.
#4: The DIMM name (DIMM1 or DIMM2) is recorded.
#5: One of the following codes is displayed depending on the DIMM that contained the error:
DIMM1: 0x9218
DIMM2: 0x9217

For information about the actions to take when a blue screen appears, see Chapter 9 in the HF-W2000 Model
58/55/50 INSTRUCTION MANUAL (manual number WIN-62-0073).

7-2

7. FEATURES RELATED TO MAINTENANCE AND FAILURE ANALYSIS

7.1.3 Event log
Table 7-2 shows a list of the event log entries that this feature records. These event log entries are recorded in thesystem log.

Table 7-2 Event log entries recorded by this feature
Event ID
800

SourceHFWRAS_SYS

Type

Category

Information

HFWRAS

Description%1
Detailed code = %2
Note: When an event log entry is recorded, %1 contains a message, and %2 contains the code corresponding to
the message in %1.
%1%2

A reset signal was input.

0x9201

A PCI bus parity error occurred.

0x9202An uncorrectable error occurred in DIMM2.

0x9217

An uncorrectable error occurred in DIMM1.

0x92187-3

7. FEATURES RELATED TO MAINTENANCE AND FAILURE ANALYSIS

7.2 Log Information Collection Window
7.2.1 Overview
In the log information collection window, you can perform the following actions by using the graphical userinterface:(1)

Collecting log data
This feature saves the data used for preventive maintenance and post-failure analysis of a problem. The datais compressed and saved as a single file with the file name logsave.zip.

(2)

Collecting memory dump files
This feature collects memory dump files saved by the OS. The data is saved as a compressed file with the filename memory.zip. At the same time, the minimum memory dump files are also collected.

NOTICEThe CPU load increases while memory dump files are being collected. While the CPU is undera high load, the operation of user applications can be disturbed. Make sure that you do notcollect memory dump files by using the log information collection window while applications forbusiness use are running on this equipment.

7.2.2 Starting the log information collection window
To start the log information collection window, perform the following procedure:
Administrator privileges are required to use this window, so sign in to the computer as an administrator and open
the window.
1. Click Start.
2. Click RAS Software.
3. Click RAS Maintenance Support.

NOTE
The log information collection window cannot be used by multiple users at the same time. If you use user
switching, for example, to try to start instances of the log information collection window from multiple
consoles, an error might occur. In such cases, close the log information collection window on the otherconsoles, and then open the window.

7-4

7. FEATURES RELATED TO MAINTENANCE AND FAILURE ANALYSIS

7.2.3 Using the log information collection window
1. The log information collection window appears. By default, both the Gather log data. and Gather memory
dump files. check boxes are selected. If you do not need to use either of one of these two options, clear the
check box for the option that you do not need, and then click Continue.

2. If the Gather memory dump files. check box is selected, the following message appears. Click OK. If you
click Cancel, you return to the log information collection window without executing the maintenance
operation.

3. The following dialog box appears. Specify the directory in which to save, and then click OK. If you want tocancel the maintenance operation, click Cancel. If you click Cancel, you go back to the log informationcollection window without executing the maintenance operation.

7-5

7. FEATURES RELATED TO MAINTENANCE AND FAILURE ANALYSIS

4. The information selected in step 1 is collected. During the process, a window appears to show the progress. If
the process finishes successfully, the following window appears.
Do not do anything in the windows that appears during the process until The maintenance operation
completed. appears in the following window. After this message appears, click OK.

7-6

7. FEATURES RELATED TO MAINTENANCE AND FAILURE ANALYSIS

5. A directory is created in the directory specified as the directory in which to save. The name of the directory isbased on the date and time of the operation. The collected data is saved in the directory created here.
If the following folder structure is not created, collection of log information might have failed. In such cases,
collect log information again.

SpecifieddirectoryYYMMDD_
hhmm
directory#1

logsave.zip: Log data file#2

MEMORY.zip: Memory dump file
Windowsd
irectory

Minidumpd ... Location whereminimum memory
irectory
dump files are stored

Figure 7-1 Folder structure for collected data

#1: The name of the directory is YYMMDD_hhmm.
YY: Lower two digits of the year, MM: month, DD: day, hh: hour, mm: minute
Example: If the date is saved at 13:59 on Jan 1, 2014
Directory name: 140101_1359#2: The following data is saved.
• If Gather log data. is selected: logsave.zip• If Gather memory dump files. are selected: MEMORY.zip and the minimum memory dump files

6. Double-click the saved logsave.zip and MEMORY.zip files to ensure that you can view the contents ofeach ZIP file.
If you cannot view the contents of the files, collect log information again, because the ZIP files might havebeen corrupted.

7.2.4 Closing the log information collection window
To close the log information collection window, click Cancel.

7-7

7. FEATURES RELATED TO MAINTENANCE AND FAILURE ANALYSIS

7.3 Logging Trends in the Temperature Inside the Chassis
7.3.1 Overview
This feature periodically measures the temperature inside the chassis of this equipment and records the data in alog file. You can adjust the logging frequency for the temperature inside the chassis by using the logging
frequency setup command. The default setting for the logging frequency is 60 minutes. For this setting, you canselect from three options: 10, 30, and 60 minutes.

7.3.2 Log files
The temperature inside the chassis is recorded in a log file at the specified logging frequency. When thisequipment runs continuously for 8 hours or more, the highest and lowest temperatures across 8 hours are also
recorded every 8 hours. For either file, if the log gets full, log entries are overwritten beginning from the oldest
entry.
Table 7-8 shows the names of the log files.

Table 7-3 Log files

Parent folder

File nametemp.csv%ProgramFiles%＼HFWRAS＼
log

Description
The temperature inside the chassis is recorded in thisfile at the logging frequency.
(The maximum number of entries is 51,200.)

The highest and lowest temperatures in 8 hours aretemp_mm.csv recorded in this file.
(The maximum number of entries is 1,100 entries.)

Checking log information
You can check log information by opening the log files by using an application such as Notepad. The files are
in CSV format. You can use a spreadsheet or database software to load the log information and draw graphs.
You can also use the log information collection window or the logsave command to collect the log files. For
information about how to use the logsave command, see 8.4.1 Log information collection command(logsave) in the HF-W2000 Model 58/55/50 INSTRUCTION MANUAL (manual number WIN-62-0073).

7-8

7. FEATURES RELATED TO MAINTENANCE AND FAILURE ANALYSIS

Log information format
The format of the log information is as follows:(1) temp.csv

YYYY/MM/DD hh:mm:ss, yxxx::

YYYY: year, MM: month, DD: day, hh: hour (24-hour clock), mm: minute, ss: second,y: sign (+ or -), xxx: temperature (°C)
If acquisition of the temperature fails, xxx is replaced with ---.

Figure 7-2 Format of the log information (1)(2) temp_mm.csv

YYYY/MM/DD hh:mm:ss, yxxx, yzzz::

YYYY: year, MM: month, DD: day, hh: hour (24-hour clock), mm: minute, ss: second,y: sign (+ or -), xxx: highest temperature (°C)
y: sign (+ or -), zzz: lowest temperature (°C)

Figure 7-3 Format of the log information (2)7-97. FEATURES RELATED TO MAINTENANCE AND FAILURE ANALYSIS

7.3.3 Logging frequency setup command

Name
tmplogset - Logging frequency setup

Syntaxtmplogset

Functionality
This command configures the frequency at which to log trends of the temperature inside the chassis.
The following shows how to use the command.

1.

Open a command prompt.
Administrator privileges are required to run this command, so sign in to the computer as an administrator,
and then open a command prompt.

2.

At the command prompt, run the tmplogset command. The following initial screen appears along withthe current setting. If you enter 2 on the initial screen, the tmplogset command exits without changing
the settings.

>tmplogset
Logging time of the cycle:60 minutes
1. Change at logging cycle [10,30,60 minutes]
2. Exit:_3.

If you enter 1 and then press Enter, the following message appears.

Please select new time of the cycle.
When the return is input, it becomes like a present setting.
1. 10 minutes
2. 30 minutes
3. 60 minutes
:_

7-10

7. FEATURES RELATED TO MAINTENANCE AND FAILURE ANALYSIS

4.

Enter the number corresponding to the new frequency that you want to select, and then press Enter. If thenumber you enter is out of range, the following message appears, prompting you to enter a valid number.

The entered setting is invalid.
Please enter a setting again. [input range: 1-3]

5.

If you enter a number from 1 to 3, the following message appears. The x denotes the time that you
selected.

New logging time of the cycle is x.
Is this value set?(y-YES/n-NO):_

6.

If you enter y and then press Enter, the logging frequency is updated to the new value, and the commandexits. The new setting takes effect when the command exits. If you want to confirm the change, run thiscommand again and check its initial screen.
If you do not want to change the logging frequency, enter n and then press Enter. The following message
appears and the command exits without the setting being changed.

The setting takes no effect, because you enter the letter 'n'

If you do not have administrator privileges when you run the command, the following message appears
and the command exits.

>tmplogset
You do not have the privilege to run this command.
Please run this command again on "Administrator: Command Prompt".

If an internal error occurs when you run the command, the following message appears and the commandexits.

Error: Systemcall failed. (API-name:error-code)

In this message, API-name indicates the name of the Windows API that encountered the error. error-code
shows the error code in hexadecimal. If this message appears, run the command again.

7-11

This page is intentionally left blank.

8. SIMULATING THE HARDWARE STATUS

CHAPTER 8 SIMULATING THE HARDWARE STATUS
8.1 Hardware Status Simulation
8.1.1 Overview
This feature simulates the hardware status and the I/O status of the general-purpose external contact of thisequipment. By simulating these statuses, you can test a user application and check the notification interface of
the RAS software without an actual hardware failure or a connection with the external contact.
To simulate the hardware status and the I/O status of the general-purpose external contact, you need to set the
RAS software to a special mode called simulation mode. In simulation mode, the monitoring of the actual
hardware status is disabled. Never use this equipment in simulation mode for business use.
This feature simulates the following conditions:• Fan condition• Temperature condition inside the chassis• Drive condition (including the drive failure prediction (SMART monitoring) condition and whether the poweron (used) hours have exceeded the threshold)• Memory condition• RAID status (B model only)• I/O status of the general-purpose external contact

Figure 8-1 Simulation Tool window

8-1

8. SIMULATING THE HARDWARE STATUS

The monitoring feature of the RAS software detects change in the simulated hardware status and I/O status of thegeneral-purpose external contact, and then notifies the user of the change through various interfaces.
For information about the interfaces used for notification, see the following sections in this manual:• Fan condition: 2.1 Fan Monitoring• Temperature condition inside the chassis: 2.2 Monitoring the Temperature Inside the Chassis• Drive condition: 2.3 Drive Failure Prediction Function (SMART Monitoring) and 2.4 Drive Usage Monitoring• Memory condition: 2.5 Memory Monitoring• RAID status: 2.8 RAID Monitoring (B Model Only)• Input status of the general-purpose external contact: (2) in 6.1.5 Get functions for the general-purpose external
contact inputs and 4.5 Remote Notifications• Output status of the general-purpose external contact: (2) in 6.1.4 Control functions for the general-purpose
external contact outputs and 4.5 Remote Notifications

NOTICE
While the equipment is running in simulation mode, monitoring of the actual hardware status isdisabled. Errors, including fan failures and abnormal temperatures, cannot be detected. Neveruse this equipment in simulation mode for business use. Use the simulation feature only fortesting user applications and checking the notification interface of the RAS software.

NOTE• While the equipment is running in simulation mode, OS deadlock monitoring cannot be used:• In simulation mode, the memory-monitoring feature records an event (event ID: 525) in the event log
only when a memory error is detected for the first time. Afterward, even if the memory error persists,
the memory monitoring feature does not record events in the event log.
• In simulation mode, when the drive failure prediction feature records an event (event ID: 265) of
SMART detection in the event log, the string XXXXXXXX is used for the model name of the drive.
Also note that you cannot simulate a drive condition of "Unknown" or multiple conditions (forexample, SMART detection and power-on (used) hours exceeded) that occur at the same time.
• The RAID status is automatically updated based on the condition of the drives. Note that you cannot
simulate a RAID status of "Unknown" or a situation in which media errors occur.
• Simulation of the input status of general-purpose external contact is used to check the output from alibrary function, rather than for checking the output of an actual general-purpose external contact.

8-2

8. SIMULATING THE HARDWARE STATUS

8.1.2 Using the simulation feature
Run the simulation mode start command at the command prompt to set the RAS software to the simulation mode.
When the RAS software transitions to the simulation mode, the Simulation Tool window appears on the screen.
You can use this window to simulate the condition of hardware devices. To exit the simulation mode, restart thisequipment.
This subsection describes how to use the simulation mode.
(1)

Overview of the procedure for using the simulation feature
Figure 8-2 shows a rough flowchart of using this feature. The RAS software runs in simulation mode fromthe time that the simulation mode start command is executed until the OS shuts down.

START

The equipment starts.

Sign in to the OS.

Running insimulation mode

Execute the simulation mode startcommand.

For details, see (2).

Perform hardware failure tests in the
Simulation Tool window.

For details, see (3).

Close the Simulation Tool window orstart shutdown.

For details, see (4).

Shutdown process

The equipment turns off or restarts.
END

Figure 8-2 Procedure for using the simulation mode

8-3

8. SIMULATING THE HARDWARE STATUS(2)

Starting the simulation mode
To start the simulation mode, run the simulation mode start command (the simrasstart command) at thecommand prompt.

NOTE• The simulation mode cannot be started from a remote desktop. Before you start the simulation mode,other signed-in users must sign out.
• If the RAS software has already detected a hardware failure, the simulation mode cannot start. Remove
the cause of the failure before using the simulation mode.

1. Open a command prompt.
You need to have administrator privileges to run the simulation mode start command. Sign in to thecomputer as an administrator and open a command prompt.
2. At the command prompt, enter the following, and then press Enter.
>%SystemDrive%＼"Program Files"＼HFWRAS＼sim＼simrasstart
3. The following message about exiting the simulation mode appears. Click OK. If you click Cancel, thesimulation mode does not start.

8-4

8. SIMULATING THE HARDWARE STATUS

4. The following message appears, indicating that the simulation mode starts. Click OK. If you click
Cancel, the simulation mode does not start.

5. The Simulation Tool window appears. This equipment runs in simulation mode from this point forward.
Monitoring of hardware failures is now disabled.

NOTE
The simulation feature performs the following actions while running in simulation mode:• The status lamp is lit between green and red. The CPUSTOP contact switches between OPEN and
CLOSE.
• Every 10 seconds, the Windows® Exclamation sound is played twice. (This sound is audible only when
speakers are connected.)

8-5

8. SIMULATING THE HARDWARE STATUS(3)

Using the Simulation Tool window
When the RAS software transitions to the simulation mode, the Simulation Tool window appears as shown in
Figure 8-3.
You can use the Simulation Tool window to change the condition of hardware devices.
When the Simulation Tool window starts, all hardware devices are set to the normal status.

Shows the name of asimulated device.

Shows the currently set
status of the target device.

Click Apply to apply the contents of
the Setting column.

Shows a new status
to be simulated.

Click End to exit the simulation mode.

Figure 8-3 Description of the Simulation Tool window● TargetShows the name of each simulated hardware device.
Category

TargetFan condition

System fan, CPU fan

Temperature condition inside the chassis

Internal temperature

Drive condition

Drive bay 1, drive bay 2

Memory condition

DIMM1, DIMM2

Input status of the general-purpose external contact

GENDI, GENDI0, GENDI1, GENDI2

Output status of the general-purpose external contact

GENDO0, GENDO1, GENDO2

8-6

8. SIMULATING THE HARDWARE STATUS● Status
Shows the currently set status of each simulated hardware device. The following shows a list of statuses
for each hardware device.
Category

TargetStatusFan condition

System fan, CPU fan

Normal, Error

Temperature condition inside the chassis

Internal temperature

Normal, Error

Drive condition

Drive bay 1, drive bay 2

Healthy, SMART Detected,
Overrun, Not Connected,
Offline#, Rebuild#,
Incomplete data#

Memory condition

DIMM1, DIMM2

Normal, Error, Failure, Not Mounted

Input status of the general-purpose
external contact

GENDI, GENDI0, GENDI1,
GENDI2

Open, Closed

Output status of the general-purpose
external contact#: B model only

GENDO0, GENDO1, GENDO2

Open, Closed

After the Simulation Tool window starts, all hardware devices are set to Normal or Healthy.
● SettingShows a new status to be simulated for each target hardware device.
If no status to be simulated is set, "---" appears. (After the Simulation Tool window starts, "---" isdisplayed for all hardware devices.)● Apply button
If you click this button, the contents of the Setting column are applied to the status of the hardware
devices.
The monitoring feature of the RAS software detects changes in the status of the hardware devices andnotifies users of the changes through various interfaces.

NOTE
A new hardware status is applied to the notification interface of the RAS software when the following
time elapses after you click Apply in the Simulation Tool window. Wait for the following times to elapse
before you check the results of a simulation.
• Fan condition: About 10 seconds later• Temperature condition inside the chassis: About 15 seconds later• Drive condition: About 5 seconds later• Memory condition: About 10 seconds later• Input status of the general-purpose external contact: Immediately

8-7

8. SIMULATING THE HARDWARE STATUS● End button
If you click this button, a shutdown is performed to exit the simulation mode. Before a shutdown isperformed, the following message appears. Save your data and perform any other necessary tasks, thenclick OK. If you click Cancel, the Simulation Tool window is not closed.

NOTE
Even if the Simulation Tool window exits due to an internal error or other reasons, shutdowns are
performed automatically to exit the simulation mode. Before a shutdown is executed, the following
message appears. Save your data and perform any other necessary actions, and then click OK.

● Minimize button ([_] button)
Click the Minimize button in the upper-right corner of the Simulation Tool window to minimize thewindow.
● Close button ([×] button)
Click the Close button in the upper-right corner of the Simulation Tool window to shutdown and exit thesimulation mode. The behavior after you click this button is the same as when you click End.

8-8

8. SIMULATING THE HARDWARE STATUS

The following procedure shows how to simulate a hardware status by using the Simulation Tool window.
1. Right-click a hardware item that you want to simulate. A pop-up menu appears. The menu lists thestatuses that you can select based on the current hardware status.

2. If you select a status that you want to simulate from the pop-up menu, the selected status is displayedin the Setting columm.

8-9

8. SIMULATING THE HARDWARE STATUS

3. To apply the status displayed in the Setting column to the hardware status, click Apply. This updates
the Status column in the Simulation Tool window.

NOTE
If nothing appears in the Setting column, (that is, --- is shown) or the value is the same as the Status
column after you click Apply, the current status does not change.

8-10

8. SIMULATING THE HARDWARE STATUS

The following shows a list of items in the pop-up menu that are displayed when you right-click eachhardware item.
In the pop-up menu, the current status and the statuses to which the current status can transition aredisplayed. Note that if the current status is the only status that can be displayed, only a grayed-out None
is displayed in the menu.
● Fan condition
No.

Current status1

Normal2

Error

Statuses in the pop-up menu

Note

Normal, Error● Internal temperature condition
No.

Current status1

Normal2

Error

Statuses in the pop-up menu

Note

Normal, Error● Drive condition
A and S models
No.

Current status

Statuses in the pop-up menu

Note

1

Healthy

Healthy, SMART Detected, Overrun, Not Connected#12

SMART Detected

SMART Detected, Not Connected#1, #23

OverrunOverrun, Not Connected#1, #2

4

Not Connected

Not Connected#1, #3#1: The equipment never starts without drive bay 1 being mounted, and consequently, Not connected is
not displayed for drive bay 1 in the pop-up menu.
#2: Transition from SMART Detected or Overrun to Healthy means that the target drive is replacedwith a new one and that the new drive is connected.
#3: We assume that Not Connected means a new drive is connected. Consequently, transitions to
SMART Detected or Overrun are not allowed.

8-11

8. SIMULATING THE HARDWARE STATUS

B modelThe following shows the list of items in the menu when you right-click drive bay 1 or drive bay 2.
No.

Current status

Statuses in the pop-up menu

Note

1

Healthy

Healthy, SMART Detected, Overrun, Not Connected,
Offline, Incomplete data

#1

2

SMART Detected

SMART Detected, Not Connected, Offline,
Incomplete data

#2

3

OverrunOverrun, Not Connected, Offline, Incomplete data

#2

4

Not Connected

Not Connected, Rebuild

5

OfflineNot Connected, Offline, Rebuild

6

Rebuild

Healthy, Not Connected, Offline,
Rebuild#3, #4

7

Incomplete data

Healthy, Not Connected, Offline,
Rebuild, Incomplete data

#3, #4

#1:
#2:
#3:
#4:

If the RAID status is "Degrade", Offline and Not Connected are not displayed.
If the RAID status is "Degrade", None is the only item in the menu and is grayed out.
A transition of the status from Rebuild to Healthy means that the rebuilding process is complete.
We assume that Rebuild means a new drive is connected. Consequently, transitions to SMART Detectedor Overrun are not allowed.

● Memory condition
No.

Current status

Statuses in the popup menu
Normal, Error, Failure, Not Mounted

Note

1

Normal2

Error#1, #2#1

3

Failure#1, #2

4

Not Mounted#1#1: Starting this equipment requires DIMM1. Therefore, Not Mounted is not displayed for DIMM1 in the
pop-up menu.
#2: For the memory condition, Error indicates a frequent memory error correction, and Failure indicatescontinued memory error corrections.

8-12

8. SIMULATING THE HARDWARE STATUS● Input status of general-purpose external contacts
No.

Current status

1

Open

2

ClosedStatuses in the pop-up menu

NoteOpen, Closed● Output status of general-purpose external contacts
No.

Current status

1

Open

2

ClosedStatuses in the popup menu
None

Note
#
#

#: The pop-up menu contains only None because only the control result of GendoControlEx (thecontrol function for general-purpose external contact outputs) is displayed.

8-13

8. SIMULATING THE HARDWARE STATUS(4)

Exiting the simulation mode
To exit the simulation mode, shutdown or restart this equipment. There are no restrictions on how to
shutdown or restart the equipment. In the same way as in its normal operating mode, this equipment isshutdown or restarted in the following cases (for the following reasons):• A shutdown is executed from the Start menu.
• A system shutdown API function, such as the BSSysshut and ExitWindowsEx functions, is
executed.
• The equipment automatically shuts down because a fan failure, an abnormal temperature inside thechassis, or a remote shutdown signal input is detected.
• Ctrl+Alt+Delete is pressed and the power button in the lower-right corner of the screen is used to
shutdown the equipment.
• A blue screen appears because the NMI button was pressed or for another reason.
• The power is forcibly turned off by using the power switch.
The hardware simulation feature automatically shuts down the equipment in the following cases:• The End button or the Close button [×] in the Simulation Tool window is clicked.
• The Simulation Tool window terminates with an error.

NOTE• As explained here, shutting down or restarting the equipment exits the simulation mode. To start thesimulation mode again, execute the simulation mode start command after the equipment restarts.
• If you perform a shutdown or sign-out during the transition to the simulation mode, the following
message appears, indicating that the simulation mode will end and that the system will shutdown.

• When a remote connection is used, the shutdown process can be delayed when the shutdown is
executed for one of the preceding reasons.

8-14

8. SIMULATING THE HARDWARE STATUS

8.1.3 Precautions when you use the Simulation Tool window(1)

When the new status to be simulated is finalized
From the time that you select a new status to be simulated from the pop-up menu in the Simulation Tool
window until when you click Apply, the new status to be simulated is not finalized and can be changed.
The actual status used for simulation is the one shown in the Setting column in the Simulation Tool window
when you click Apply. If nothing is set for Setting (that is, --- appears), the status displayed for Status ismaintained.

8-15

8. SIMULATING THE HARDWARE STATUS(2)Simulating the status of RAID drives
With the B model, the RAID status is determined by the simulation of the condition of the drives used in the
RAID. In some cases, if you select a new status to be simulated for both drives, the condition of the first
drive you selected might change depending on the condition of the second drive you selected. The following
example illustrates the case where Offline is selected for both drives.
1. Select Offline for drive bay 1. Then, select Offline for drive bay 2. (If you select Not Connected
instead, the result will be the same.)

2. When Offline is selected for drive bay 2, the condition of drive bay 1 changes back to --- (nothing isselected).

8-16

8. SIMULATING THE HARDWARE STATUS

8.1.4 Event log entries
To clearly show which log entries for hardware failure originate from the simulation feature, the feature records
the event log entries listed in Table 8-1.
Note that a log entry with event ID 252 is recorded when you click Apply in the Simulation Tool window. Thislog entry is recorded even when none of the items in the Setting column is specified.

Table 8-1 Event log entries recorded by this feature
Event ID

SourceType

Category

Description

250

HFWSIM_SYS

Information

HFWSIM

The simulation mode started.

251

HFWSIM_SYS

Information

HFWSIM

The simulation mode ended.

HFWSIM

The following conditions were set in thesimulation mode.
System fan: %1
CPU fan: %2
Internal Temperature: %3
Drive bay 1: %4
Drive bay 2: %5
DIMM1: %6
DIMM2: %7
GENDI: %8
GENDI0: %9
GENDI1: %10
GENDI2: %11252

HFWSIM_SYS

Information%x in this table denotes the status that was simulated by clicking Apply in the Simulation Tool window.

8-17

8. SIMULATING THE HARDWARE STATUS

8.1.5 Remote notifications
This feature notifies users of the transition of the RAS software to simulation mode by using trap notifications,so that an SNMP manager that monitors this equipment from a remote location can identify that the hardware
statuses that it acquires and the trap notifications for hardware failure (and hardware recovery) that it receives
are generated in simulation mode. In addition, the object value for the operating mode of the RAS software ischanged to the one for the simulation mode.

NOTE
The contents of the hardware statuses that can be acquired and the trap notifications that can be sent are
the same as in the normal mode. For details about the objects of the extended MIB for HF-W, see 4.5
Remote Notifications.

8-18