Fujitsu P2X0-0202-01EN manual Alarm Text Files, Alarm Text Date Files, StxgrYYYYMMDD.log

Page 54

6.2 Alarm Text Files

ETERNUS3000 Hardware Status List

Date:1/1/2003

ETERNUS3000 Address:10.20.30.40

ControllerEnclosure#0001:ALARM

ControllerEnclosure#0002:BTU-CAUTION

ControllerEnclosure#0003:ALARM&BTU-CAUTION

DriveEnclosure#0003:ALARM

ETERNUSmgr(stxpoll) V20L20

Header

(title, date, address of the target device)

Alarm List

Footer

(ETERNUSmgr Version)

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.

"No hardware error detected."

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.

"No hardware report detected. (Offline)"

See "6.3 E-mail Messages" (page 47), "Hardware Status was changed. See below ..." for details of the mes- sages displayed in the alarm history file.

Note that "Hardware Status was changed. See below ..." is not an actual alarm history message.

6.2Alarm 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 45) for more information on the alarm history messages.

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 tar- get 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.

■Alarm Text Date Files

The alarm text date file is saved in the directory specified in the setup file using the following file naming convention. See "2.3.4 Alarm Text File Settings" (page 19) for more information about the setup files.

stxgrYYYYMMDD.log

YYYY : Year

MM: Month

DD : Day

46

For example, "stxgr20030101.log" indicates an alarm text date file that was created on January 1, 2003. Alarm text date files are created/updated when an alarm history file is created. Alarm text date files are cre- ated/updated when an alarm history file is created.

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

All Rights Reserved, Copyright © FUJITSU LIMITED 2007

Page 53 Page 55
Image 54
Page 53 Page 55
Contents Page Page Preface Structure of this ManualRelated Material PrefaceFollowing are related materials Acknowledgments AbbreviationsThis page is intentionally left blank Contents Contents IndexAbout ETERNUSmgr ETERNUSmgr OutlineETERNUSmgr Outline ETERNUSmgr System Configuration Network RequirementsClient communication About ETERNUSmgr Managing Server communication Target Device Monitoring and Failure Notification Target Device Configuration BrowserETERNUSmgr Functions ETERNUSmgr FunctionsTarget Device Setup and Maintenance Yes Can be monitored, No Cannot be monitoredRequired Software and Hardware ETERNUSmgr ServerMail Server ETERNUSmgr for Windows Client This page is intentionally left blank Setup Setup filesSetup files Setting Items and Parameters Required by each OS Modifying the ETERNUSmgr Setup ETERNUSmgr for Solaris OS and Linux ProcedureFor Windows Setting ItemsTarget Device Settings Target AddressTarget Type When the actual polling exceeds the scheduled polling timePolling Interval POLLINGTIME=300Target Flag Detect Offline TargetsAlarm Mailing Interval Mail Notification SettingsAdmin Mail Address Busy Target Detection TimeMail Server Smtp Port ETERNUSmgr for Windows only AdminmailsvMail Server Address ETERNUSmgr for Windows only MAILSENDTIME=300Alarm History File Settings Alarm History File DirectorySender Mail Address Alarm History Index URL Number of Days Alarm History Files are KeptHtmlalarmfileurl up to 64 characters Setup Parameter Alarm Text File SettingsAlarm Text Files Directory Alarm Text Date FilesLog File Settings Number of Days Alarm Text Date Files are KeptLog Files Directory Changing the Windows version setting to D\ETERNUSmgr\log1\ Number of Days Log Files are KeptLOGFILEDAY=7 Modifying the ETERNUSmgr Top Menu System Output Log FileETERNUSmgr for Solaris OS and Linux Procedure Copying/Modifying the Top Menu FilesEditing Top Menu file menu.htm Setting the Link to the Alarm History FilesInstallation Location Machine Name Storage systems other than ETERNUS2000Setup Example ↓ Becomes HtmlMonitoring Multiple Target Devices Setup File CautionsCreating a Setup File for Each Target Device Format STX-.INIMonitoring Multiple Target Devices File name starts with STX and ends with .INI2nd Target Device ETERNUS2000#1 Adding the Extra Target Devices to the Top Menu FileExample 1st Target Device ETERNUS3000#1 3rd Target Device ETERNUS3000#2Status of 000.000.000.000 -- font color=red*Offline*/font Startup and Shutdown ETERNUSmgr for Solaris OS and LinuxStarting Up ETERNUSmgr ETERNUSmgr for Solaris OS and Linux Setting the ETERNUSmgr Daemon for Automatic Startup Shutting Down ETERNUSmgrSolaris 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 Control Interfaces Top Menu Select RAID Device menuShow hardware error detect log list menu ETERNUS6000Solaris OS, Linux, and Windows Version Cautions ETERNUSmgr User Guide -Introduction- P2X0-0202-01EN Detectoffline = True Uninstall Windows only cautionsMessages Alarm History MessagesExample Alarm History File YYYYMMDDHHmmSSn.htmlAlarm Text Files Alarm Text Date FilesStxgrYYYYMMDD.log ETERNUSmgr VxxLxx Http Polling engine was started Alarm Text Fixed FileMail Messages Hardware Status was changed. See belowComponent#Serial NumberStatus Serial numberStatus Log Messages Regular Messages CodeBad Parameter parameter Code Log Messages Server Status Change CodeWork files create to temp directory Code Undefined Parameter parameter CodeFatal Error Messages Code Cant Create Directory path Code Log Messages Cant Allocate Memory CodeBad IP Address host name or IP address Code Not Find Parameter parameter CodeAn example of log message output is shown below Result of a target device status inquiry SuccessLog Messages Htmlalarmfilename Htmlalarmfilepath IndexLogfileday Index ETERNUSmgr User Guide -Introduction P2X0-0202-01EN
Top Page Image Contents