Fujitsu P2X0-0202-01EN 사용자 설명서
Chapter 6 Messages
47
P2X0-0202-01EN ETERNUSmgr User Guide -Introduction-
All Rights Reserved, Copyright © FUJITSU LIMITED 2007
6
Alarm text date files are automatically deleted when they are older than the limit specified in the setup file.
See
See
files.
■
Alarm Text Fixed File
This is stored in the same directory as the alarm text date files using whatever name is specified in the
setup file. See
setup file. See
for more information about the setup files.
When an alarm history file is created, a line formatted as "Year, Month, Day, Hour, Minutes, Seconds,
Machine Address, and Machine Status as Recorded in the Alarm History File" is added to the alarm text
file.
An example of an alarm text is shown below.
Machine Address, and Machine Status as Recorded in the Alarm History File" is added to the alarm text
file.
An example of an alarm text is shown below.
See
for more information
on the target device status output to the alarm text files.
6.3
E-mail Messages
The administrator can be sent E-mail messages that contain notices of ETERNUSmgr startup and changes
in the target device status. These messages indicating changes in the target device status are identical in
format to the alarm history messages.
This section explains the E-mail messages sent by ETERNUSmgr and how to respond to them.
in the target device status. These messages indicating changes in the target device status are identical in
format to the alarm history messages.
This section explains the E-mail messages sent by ETERNUSmgr and how to respond to them.
ETERNUSmgr VxxLxx - HTTP Polling engine was started.
[Explanation] The polling engine has started.
[Response]
[Response]
None
Hardware Status was changed. See below...
[Explanation] There has been a change in the target device’s status.
[Response]
[Response]
If the component that caused the problem is displayed after this message, login to
the target device and check the status of that component.
When "No hardware error detected." is displayed, there is no need to do anything.
Detection of offline status is indicated when "No hardware report detected.
(Offline)" is displayed. In this case, check for problems with the target device, fail-
ures in the communications route, and errors in the setup file.
When "An error has occurred in controller enclosure. (BUSY)" is displayed, per-
form the following:
For ETERNUS3000
It has been detected that one of the controllers in the controller enclosure cannot
start up. The controller needs to be serviced.
For ETERNUS6000
Indicates that the target device cannot respond due to device stop status, abnormal-
ity of the communication link between the device and SVP, or device boot process-
ing. Check that the target device is operating normally, and that there is no problem
with the communication link between the device and SVP.
For ETERNUS8000, ETERNUS4000, and ETERNUS2000
Indicates that the target device cannot respond due to device stop status or device
boot processing. Check that the target device is operating normally.
the target device and check the status of that component.
When "No hardware error detected." is displayed, there is no need to do anything.
Detection of offline status is indicated when "No hardware report detected.
(Offline)" is displayed. In this case, check for problems with the target device, fail-
ures in the communications route, and errors in the setup file.
When "An error has occurred in controller enclosure. (BUSY)" is displayed, per-
form the following:
For ETERNUS3000
It has been detected that one of the controllers in the controller enclosure cannot
start up. The controller needs to be serviced.
For ETERNUS6000
Indicates that the target device cannot respond due to device stop status, abnormal-
ity of the communication link between the device and SVP, or device boot process-
ing. Check that the target device is operating normally, and that there is no problem
with the communication link between the device and SVP.
For ETERNUS8000, ETERNUS4000, and ETERNUS2000
Indicates that the target device cannot respond due to device stop status or device
boot processing. Check that the target device is operating normally.
20030101130100 10.20.30.40 No hardware error detected.
20030101130600 10.20.30.40 ControllerEnclosure#00:ALARM
20030101144100 10.20.30.40 No hardware error detected.