Chapter 6 Messages
>
6.2 Alarm Text Files
ETERNUS Disk storage systems ETERNUSmgr User Guide -Introduction-
53
Copyright 2009 FUJITSU LIMITED
P2X0-0202-04ENZ0
Example Alarm History File
The following alarm history file was created on December 1st 2008 for an ETERNUS4000
with the target address 10.20.30.40.
The "alarm history messages" shown above indicate the status results obtained from the target
device.
The following message is output when all components of the target device are normal.
If target device monitoring does not work properly (due to LAN drop-out, failure on the network
path, or incorrect target address setting, etc.), and the Detect Offline Targets parameter has
been set, the following message will be output.
See
"6.3 E-mail Messages" (page 54)
, "Hardware Status was changed. See below ..." for details
of the messages displayed in the alarm history file.
Note that "Hardware Status was changed. See below ..." is not an actual alarm history message.
6.2
Alarm Text Files
This section explains the alarm text files that are generated by ETERNUSmgr.
Alarm text files are a compilation of the alarm history messages for a single day in a text format.
See
"6.1 Alarm History Messages" (page 52)
for more information on the alarm history mes-
sages.
Alarm text files are categorized into the following types:
•
Alarm Text Date Files
Contains the individual alarm history messages that record the ongoing status of the target
device, collected on a day-by-day basis.
•
Alarm Text Fixed File
Contains the same alarm history messages as the latest alarm text date file, saved under a
settable name.
"No hardware error detected."
"No hardware report detected. (Offline)"
Date:1/12/2008
ETERNUS4000 Address:10.20.30.40
ControllerEnclosure#0001:ALARM
ControllerEnclosure#0002:BTU-CAUTION
ControllerEnclosure#0003:ALARM&BTU-CAUTION
DriveEnclosure#0003:ALARM
ETERNUSmgr(stxpoll) V20L30
ETERNUS4000 Hardware Status List
Header
(title, date, address of the target device)
Alarm List
Footer
(ETERNUSmgr Version)