Fujitsu P2X0-0202-01EN manual Number of Days Log Files are Kept, LOGFILEDAY=7

Page 29

Chapter 2 Setup

Initially, immediately after ETERNUSmgr installation, the setup file should contain a parameter that is set to the "log_1" directory under the ETERNUSmgr installation directory specified at installation (specifi- cally, "/opt/FJSVgrmgr/log_1/" for the Solaris OS and Linux versions, and "C:\Program Files\FUJITSU\ETERNUSmgr\log_1" for the Windows® version if the normal installation defaults are accepted). However, if this is likely to overload the file system, consult with the server administrator and change it to a more suitable directory (e.g. "/var/FJSVgrmgr/log_1/" for Solaris OS and Linux, or "D:\ETERNUSmgr\log_1\" for Windows®).

[Parameter]

LOGFILE_PATH (up to 64 characters)

[Example]

Changing the Solaris OS and Linux version setting to "var/FJSVgrmgr/log_1":

LOGFILE_PATH=/var/FJSVgrmgr/log_1/

Changing the Windows® version setting to "D:\ETERNUSmgr\log_1\":

LOGFILE_PATH=D:\ETERNUSmgr\log_1\

Caution:

When monitoring multiple target devices, set a different log file directory for each of the different targets.

Refer to "2.5 Monitoring Multiple Target Devices" (page 27) for details on how to mon- itor multiple target devices.

If the specified log files directory does not exist, it will automatically be created. The directory does not need to be created manually.

Number of Days Log Files are Kept

This parameter specifies how long the log files are kept. Setting the number of days to "0" means that the files are not deleted.

[Default value]

7

[Parameter]

LOGFILE_DAY (0 ~ 65535 days)

[Example]

To store seven days worth of log files

LOGFILE_DAY=7

Caution:

For this parameter, if there is no need for any special setting, it is recommended not to enter any value. This parameter is commented out in the default setup file available after installation.

2

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

All Rights Reserved, Copyright © FUJITSU LIMITED 2007

21

Image 29
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 URL Number 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