Fujitsu P2X0-0202-01EN manual Solaris OS, Linux, and Windows Version Cautions

Page 49

Chapter 5

Cautions

This chapter discusses cautions that should be observed when using ETERNUSmgr.

■Solaris OS, Linux, and Windows® Version Cautions

●Failure Notification

•When the administrator is informed by ETERNUSmgr of a failure in a target device, use the ETERNUSmgr [Device Status Display] screen to find and confirm the status of the failed component. After confirmation, contact your Fujitsu engineer and pass along this information.

•Whenever necessary, ETERNUSmgr outputs history HTML files and log files for each Alarm. If the number of days to keep these files is set too high, or set to "0" (= "do not delete"), a large number of files may build up over an extended period of use. Have the administrator decide the appropriate number of days to keep these files.

●Network environment

•Polling and sending of E-mail may be impossible during a network failure on the ETER- NUSmgr server due to LAN drop-out and failure of communications equipment (e.g. hubs, routers). During such failures, the target devices are not monitored, and if the Detect Offline Targets ("DETECT_OFFLINE") flag is not set, the administrator may be unaware of the failure. Enable the Detect Offline Targets parameter as necessary, and periodically check the ETERNUSmgr log file (only for the log acquisition setting).

•ETERNUSmgr may not be able to respond to an event due to a target device or network overload caused by a device failure. In such a case, refer to "Chapter 3 Startup and Shutdown" (page 31) and manually restart ETERNUSmgr. Before restarting, make sure that the network environment is free from any problem.

•If the ETERNUSmgr server’s network settings are not correct, or there are hardware fail- ures (LAN omissions, communications device failures, etc.) on the LAN path, it can take an overly long time to execute polling or send E-mail, making periodic monitoring of target devices impossible. In particular, in cases where a host name is specified for the target device to be monitored rather than an IP address, and multiple DNS servers are regis- tered for the network, frequent inquiries must be made to the external network to resolve the host name. This can take from several minutes to tens of minutes when the network is not working well.

•When it takes an overly long time to execute polling or send E-mail, check that the net- work devices are operating normally, and that the network settings are correct.

•After rebooting a target device following a failure, etc., make sure that polling is success- fully being conducted by checking the log file. If polling is unsuccessful after the target device has been rebooted (log information is not being output to the log file), refer to "Chapter 3 Startup and Shutdown" (page 31) and manually reboot ETERNUSmgr.

Even after ETERNUSmgr is rebooted, ETERNUSmgr polling requests may still not be received by the target device (log information indicating polling failure is kept to be output to the log file). In this case, the ETERNUSmgr monitoring function may not be working due to network failure. Contact your Fujitsu engineer.

5

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

All Rights Reserved, Copyright © FUJITSU LIMITED 2007

41

Page 48 Page 50
Image 49
Page 48 Page 50
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 BrowserTarget Device Monitoring and Failure Notification ETERNUSmgr FunctionsYes 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 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=300Alarm 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 Files Directory Alarm Text File SettingsSetup Parameter Alarm Text Date FilesNumber 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 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 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 UninstallExample Alarm History File Alarm History MessagesMessages YYYYMMDDHHmmSSn.htmlAlarm Text Date Files Alarm Text FilesStxgrYYYYMMDD.log Mail Messages Alarm Text Fixed FileETERNUSmgr VxxLxx Http Polling engine was started Hardware Status was changed. See belowSerial number Component#Serial NumberStatusStatus 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 Index Htmlalarmfilename HtmlalarmfilepathLogfileday Index ETERNUSmgr User Guide -Introduction P2X0-0202-01EN
Top Page Image Contents