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

Page 50

42

●Target device monitoring

•When starting up or rebooting a target device with the ETERNUSmgr already activated and monitoring the device status, during the first few minutes until the target device is up and running, ETERNUSmgr will output alarm history messages and E-mails related to the addition/removal of target device components. These particular messages are output at startup as the target device tries to recognize its own configuration, and are not error mes- sages.

-An example of a message indicating the addition of a drive enclosure is: "Increase Drive Enclosure # 12"

-An example of a message indicating the removal of a drive enclosure is: "Decrease Drive Enclosure # 34"

•If, when monitoring multiple target devices, there is a specification error, such as duplica- tion of information between the multiple setup files, ETERNUSmgr may try to monitor the same target device using the settings from different setup files and end up displaying an error message and terminating the process. When this happens, either delete one of the duplicate setup files or correct the error in the settings of the files. When looking for errors in the settings, in addition to verifying the address of the device that is being monitored ("TARGET_ADDR" parameter), make sure that you also check that the Alarm History Files Directory ("HTML_ALARMFILE_PATH" parameter) and Log Files Directory ("LOGFILE_PATH" parameter) are not duplicated in different setup files. If the values of these parameters are duplicated in different setup files, ETERNUSmgr will try to create conflicting log data in the same directory or file.

Refer to "Chapter 2 Setup" (page 9) for information on how to modify the setup files, and "ETERNUSmgr User Guide -Settings/Maintenance-" for information on ETERNUSmgr error messages and the procedures to use when they appear.

•Configuring multiple ETERNUSmgr instances to monitor the same target device may bur- den the device and overload the connection, resulting in operational errors on the target device. Be careful not to start up multiple ETERNUSmgr instances to monitor the same target device (Excluding situations where ETERNUSmgr is installed into both nodes in a cluster system).

•ETERNUSmgr sends a message to the administrator every time an abnormality is detected. Be aware that if the Alarm Mailing Interval is too short, an excessive number of E-mail messages may be sent to the administrator.

●ETERNUSmgr compatibility with GRmgr

•ETERNUSmgr compatibility with GRmgr versions V10L20 and earlier

-The operating logic, data files and log files for GRmgr versions V10L20 or earlier are not com- patible with ETERNUSmgr. When upgrading GRmgr version V10L20 or earlier to ETER- NUSmgr, uninstall the old GRmgr version before installing ETERNUSmgr. Also, use the new setup files ("STX - .INI") that are generated when ETERNUSmgr is installed.

-The setup files of V10L20 and earlier are not compatible with ETERNUSmgr, and cannot be used.

Using these files will cause a "Bad parameter (CODE 913)" error to occur, and target device monitoring stops.

•ETERNUSmgr compatibility with GRmgr versions V10L30 and later (V10L30, V10L40, V10L50, V10L60)

-ETERNUSmgr is compatible with the operating logic, data files and log files of GRmgr ver- sions V10L30 and later.

-It is possible to use setup files ("STX - .INI") from GRmgr versions V10L30 and later, but the following procedure must be followed:

1 Move the GRmgr V10L30 (or later) setup files to a temporary location. 2 Uninstall V10L30 (or later) GRmgr.

3 Install ETERNUSmgr.

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

All Rights Reserved, Copyright © FUJITSU LIMITED 2007

Page 49 Page 51
Image 50
Page 49 Page 51
Contents Page Page Preface Structure of this ManualFollowing are related materials Related MaterialPreface Acknowledgments AbbreviationsThis page is intentionally left blank Contents Contents IndexAbout ETERNUSmgr ETERNUSmgr OutlineClient communication ETERNUSmgr Outline ETERNUSmgr System ConfigurationNetwork Requirements 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 monitoredMail Server ETERNUSmgr for Windows Required Software and HardwareETERNUSmgr Server 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=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 Setup Parameter Alarm Text File SettingsAlarm Text Files Directory 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 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 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 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.htmlStxgrYYYYMMDD.log Alarm Text FilesAlarm Text Date Files ETERNUSmgr VxxLxx Http Polling engine was started Alarm Text Fixed FileMail Messages Hardware Status was changed. See belowStatus Component#Serial NumberStatusSerial number 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 Logfileday Htmlalarmfilename HtmlalarmfilepathIndex Index ETERNUSmgr User Guide -Introduction P2X0-0202-01EN
Top Page Image Contents