Fujitsu P2X0-0202-01EN manual Setup files

Page 17

Chapter 2

Setup

This chapter explains how to setup ETERNUSmgr. Setup must be performed with administrator privilege.

2.1Setup files

2

An ETERNUSmgr setup file is used to setup ETERNUSmgr to monitor a target device. The initial setup files are generated automatically in the installation directory when ETERNUSmgr is installed. See the "ETERNUS8000, ETERNUS4000, ETERNUS2000, ETERNUS6000, ETERNUS3000 ETERNUSmgr Install Guide" of each OS for details of installing ETERNUSmgr.

The parameters in each setup file must be adjusted to match the target device. After making the necessary settings, shutdown and re-start the ETERNUSmgr to enable the new settings. Refer to "Chapter 3 Startup and Shutdown" (page 31) for details on starting up and shutting down the system.

It is recommended that you make a backup of the current setup files before making any changes. Keep this backup until you have verified that the new setup files operate normally.

Caution:

You can edit only the setup file parameters described in this guide. Do not delete comments or blank lines from any setup files, and do not add anything other than parameters. Failure to follow these instructions may hinder performance and/or cause problems during future upgrades.

Setup file names must be in the following format:

STX-.INI

If the file name is other than as specified above, ETERNUSmgr will not be able to detect the file.

The only place setup files should be saved is the installation directory. If a setup file is saved in another directory, ETERNUSmgr will not be able to find it.

The following setup file parameters must be set:

•Target Address (See → page 12)

•Target Type (See → page 13)

•Target Flag (See → page 14)

•Alarm History Files Directory (See → page 17)

The setup file parameters required will vary according to the operating system and target device type. The following list shows parameter types in the setup file and setting items for each OS.

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

All Rights Reserved, Copyright © FUJITSU LIMITED 2007

9

Image 17

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