Fujitsu P2X0-0202-01EN manual Mail Messages, Alarm Text Fixed File

Page 55

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 E-mail Messages" (page 47) for more information on the target device status output to the alarm text files.

6.3E-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.

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

Page 54 Page 56
Image 55
Page 54 Page 56
Contents Page Page Structure of this Manual PrefacePreface Related MaterialFollowing are related materials Abbreviations AcknowledgmentsThis page is intentionally left blank Contents Index ContentsETERNUSmgr Outline About ETERNUSmgrNetwork Requirements ETERNUSmgr Outline ETERNUSmgr System ConfigurationClient communication About ETERNUSmgr Managing Server communication ETERNUSmgr Functions Target Device Configuration BrowserETERNUSmgr Functions Target Device Monitoring and Failure NotificationYes Can be monitored, No Cannot be monitored Target Device Setup and MaintenanceETERNUSmgr Server Required Software and HardwareMail Server ETERNUSmgr for Windows Client This page is intentionally left blank Setup files SetupSetup files Setting Items and Parameters Required by each OS ETERNUSmgr for Solaris OS and Linux Procedure Modifying the ETERNUSmgr SetupTarget Address Setting ItemsTarget Device Settings For WindowsPOLLINGTIME=300 When the actual polling exceeds the scheduled polling timePolling Interval Target TypeDetect Offline Targets Target FlagBusy Target Detection Time Mail Notification SettingsAdmin Mail Address Alarm Mailing IntervalMAILSENDTIME=300 AdminmailsvMail Server Address ETERNUSmgr for Windows only Mail Server Smtp Port ETERNUSmgr for Windows onlyAlarm History File Directory Alarm History File SettingsSender Mail Address Number of Days Alarm History Files are Kept Alarm History Index URLHtmlalarmfileurl up to 64 characters Alarm Text Date Files Alarm Text File SettingsAlarm Text Files Directory Setup ParameterNumber of Days Alarm Text Date Files are Kept Log File SettingsLog Files Directory Number of Days Log Files are Kept Changing the Windows version setting to D\ETERNUSmgr\log1\LOGFILEDAY=7 Output Log File Modifying the ETERNUSmgr Top Menu SystemCopying/Modifying the Top Menu Files ETERNUSmgr for Solaris OS and Linux ProcedureStorage systems other than ETERNUS2000 Setting the Link to the Alarm History FilesInstallation Location Machine Name Editing Top Menu file menu.htmSetup Example Html ↓ BecomesFormat STX-.INI Setup File CautionsCreating a Setup File for Each Target Device Monitoring Multiple Target DevicesFile name starts with STX and ends with .INI Monitoring Multiple Target Devices3rd Target Device ETERNUS3000#2 Adding the Extra Target Devices to the Top Menu FileExample 1st Target Device ETERNUS3000#1 2nd Target Device ETERNUS2000#1Status of 000.000.000.000 -- font color=red*Offline*/font ETERNUSmgr for Solaris OS and Linux Startup and ShutdownStarting Up ETERNUSmgr ETERNUSmgr for Solaris OS and Linux Shutting Down ETERNUSmgr Setting the ETERNUSmgr Daemon for Automatic StartupSolaris OE example ETERNUSmgr for Windows ETERNUSmgr for WindowsP2X0-0202-01EN ETERNUSmgr User Guide -Introduction For Windows Registering the ETERNUSmgr Service for Automatic Startup This page is intentionally left blank Select RAID Device menu Control Interfaces Top MenuETERNUS6000 Show hardware error detect log list menuSolaris OS, Linux, and Windows Version Cautions ETERNUSmgr User Guide -Introduction- P2X0-0202-01EN Detectoffline = True Windows only cautions UninstallYYYYMMDDHHmmSSn.html Alarm History MessagesExample Alarm History File MessagesAlarm Text Date Files Alarm Text FilesStxgrYYYYMMDD.log Hardware Status was changed. See below Alarm Text Fixed FileMail Messages ETERNUSmgr VxxLxx Http Polling engine was startedSerial number Component#Serial NumberStatusStatus Regular Messages Code Log MessagesUndefined Parameter parameter Code Log Messages Server Status Change CodeWork files create to temp directory Code Bad Parameter parameter CodeFatal Error Messages Code Not Find Parameter parameter Code Log Messages Cant Allocate Memory CodeBad IP Address host name or IP address Code Cant Create Directory path CodeResult of a target device status inquiry Success An example of log message output is shown belowLog Messages Index Htmlalarmfilename HtmlalarmfilepathLogfileday Index ETERNUSmgr User Guide -Introduction P2X0-0202-01EN
Top Page Image Contents