Chapter 6 Messages
Alarm text date files are automatically deleted when they are older than the limit specified in the setup file. See "Number of Days Alarm Text Date Files are Kept" (page 20) for more information about the setup 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 "2.3.4 Alarm Text File Settings" (page 19) 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.
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.
See "6.1 Alarm History Messages" (page 45) and "6.3
6.3E-mail Messages
The administrator can be sent
This section explains the
ETERNUSmgr VxxLxx - HTTP Polling engine was started.
[Explanation] | The polling engine has started. |
[Response] | None |
Hardware Status was changed. See below...
[Explanation] | There has been a change in the target device’s status. |
[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. |
6
P2X0-0202-01EN ETERNUSmgr User Guide -Introduction-
All Rights Reserved, Copyright © FUJITSU LIMITED 2007
47
