Fujitsu P2X0-0202-01EN manual Alarm History Messages, YYYYMMDDHHmmSSn.html, Yyyy

Page 53

Chapter 6

Messages

This chapter explains the messages and message files of ETERNUSmgr. Messages are categorized into the following types:

•Alarm History Messages

•Alarm Text Files

•E-mail Messages

•Log Messages

6.1Alarm History Messages

This section explains the alarm history messages generated by ETERNUSmgr.

If, after ETERNUSmgr polls a target device, the current status of the target device differs from the status at the previous polling operation (i.e. the status of the target device has changed), an ETERNUSmgr alarm history message is issued and saved in an alarm history file. If ETERNUSmgr detects that the target device is offline, an alarm history file is not created.

The alarm history file is saved using the following file naming convention in the directory specified in the setup file. See "Alarm History File Directory" (page 17) for more information about the setup files.

YYYYMMDDHHmmSSn.html

YYYY	: Year
MM	: Month
DD	: Day
HH	: Hour
mm	: Minute
SS	: Second
n	: Sequence number

For example, the alarm history file "200301011020300.htm" was created on January 1st 2003 at 10:20:30. The sequence number is normally 0, but is used to number files sequentially if multiple files are created within the same second.

An alarm history file is created when a change in the target device status is detected while ETERNUSmgr is polling the target device. Alarm history files are automatically deleted when they are older than the limit specified in the setup file. See "Number of Days Alarm History Files are Kept" (page 18) for more infor- mation about the setup files.

Alarm history files are in HTML format for viewing in a Web browser.

Alarm history files are displayed as follows in the Web browser.

Example Alarm History File

The following alarm history file was created on January 1st 2003 for an ETERNUS3000 with the tar- get address 10.20.30.40.

6

P2X0-0202-01EN ETERNUSmgr User Guide -Introduction-

All Rights Reserved, Copyright © FUJITSU LIMITED 2007

45

Image 53

Contents Page Page Structure of this Manual PrefaceFollowing are related materials Related MaterialPreface Abbreviations AcknowledgmentsThis page is intentionally left blank Contents Index ContentsETERNUSmgr Outline About ETERNUSmgrClient communication ETERNUSmgr Outline ETERNUSmgr System ConfigurationNetwork Requirements About ETERNUSmgr Managing Server communication ETERNUSmgr Functions Target Device Configuration BrowserTarget Device Monitoring and Failure Notification ETERNUSmgr FunctionsYes Can be monitored, No Cannot be monitored Target Device Setup and MaintenanceMail Server ETERNUSmgr for Windows Required Software and HardwareETERNUSmgr Server 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 Device Settings Setting ItemsFor Windows Target AddressPolling Interval When the actual polling exceeds the scheduled polling timeTarget Type POLLINGTIME=300Detect Offline Targets Target FlagAdmin Mail Address Mail Notification SettingsAlarm Mailing Interval Busy Target Detection TimeMail Server Address ETERNUSmgr for Windows only AdminmailsvMail Server Smtp Port ETERNUSmgr for Windows only MAILSENDTIME=300Sender Mail Address Alarm History File SettingsAlarm History File Directory Htmlalarmfileurl up to 64 characters Alarm History Index URLNumber of Days Alarm History Files are Kept Alarm Text Files Directory Alarm Text File SettingsSetup Parameter Alarm Text Date FilesLog Files Directory Log File SettingsNumber of Days Alarm Text Date Files are Kept LOGFILEDAY=7 Changing the Windows version setting to D\ETERNUSmgr\log1\Number of Days Log Files are Kept Output Log File Modifying the ETERNUSmgr Top Menu SystemCopying/Modifying the Top Menu Files ETERNUSmgr for Solaris OS and Linux ProcedureInstallation Location Machine Name Setting the Link to the Alarm History FilesEditing Top Menu file menu.htm Storage systems other than ETERNUS2000Setup Example Html ↓ BecomesCreating a Setup File for Each Target Device Setup File CautionsMonitoring Multiple Target Devices Format STX-.INIFile name starts with STX and ends with .INI Monitoring Multiple Target DevicesExample 1st Target Device ETERNUS3000#1 Adding the Extra Target Devices to the Top Menu File2nd Target Device ETERNUS2000#1 3rd Target Device ETERNUS3000#2Status of 000.000.000.000 -- font color=red*Offline*/font Starting Up ETERNUSmgr Startup and ShutdownETERNUSmgr for Solaris OS and Linux ETERNUSmgr for Solaris OS and Linux Solaris OE example Setting the ETERNUSmgr Daemon for Automatic StartupShutting Down ETERNUSmgr 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 UninstallExample Alarm History File Alarm History MessagesMessages YYYYMMDDHHmmSSn.htmlStxgrYYYYMMDD.log Alarm Text FilesAlarm Text Date Files Mail Messages Alarm Text Fixed FileETERNUSmgr VxxLxx Http Polling engine was started Hardware Status was changed. See belowStatus Component#Serial NumberStatusSerial number Regular Messages Code Log MessagesWork files create to temp directory Code Log Messages Server Status Change CodeBad Parameter parameter Code Undefined Parameter parameter CodeFatal Error Messages Code Bad IP Address host name or IP address Code Log Messages Cant Allocate Memory CodeCant Create Directory path Code Not Find Parameter parameter CodeResult of a target device status inquiry Success An example of log message output is shown belowLog Messages Logfileday Htmlalarmfilename HtmlalarmfilepathIndex Index ETERNUSmgr User Guide -Introduction P2X0-0202-01EN