-
-
-
Preface This guide discusses procedures and safeguards relating to the use of ETERNUSmgr to configure ETERNUS8000, ETERNUS4000, ETERNUS2000, ETERNUS6000, ETERNUS3000, GR series devices, as well as details of how to conduct maintenance on, display the status of, and monitor these devices. This document is specifically written for ETERNUSmgr administrators and operators. Knowledge of UNIX, Linux or Windows® system administration and Web server administration are required by this document.
-
Preface Related Material The following are related materials: • ETERNUS2000 ETERNUSmgr User Guide -Settings/Maintenance- for models 100 and 200 • ETERNUS3000 ETERNUSmgr User Guide -Settings/Maintenance- for model 50 • ETERNUS3000 ETERNUSmgr User Guide -Settings/Maintenance- for models 80, 100, 200, 300, 400, 500, 600, and 700 • ETERNUS6000 ETERNUSmgr User Guide -Settings/Maintenance• ETERNUS8000, ETERNUS4000 ETERNUSmgr User Guide -Settings/Maintenance• ETERNUS4000 models 80 and 100 ETERNUSmgr User Guide -S
-
Preface Acknowledgments • Microsoft, Windows, and Windows Server are either registered trademarks or trademarks of Microsoft Corporation in the USA and/or other countries. • UNIX is a registered trademark of The Open Group in the USA and other countries. • Java and all Java-related trademarks, and logos are trademarks and registered trademarks of Sun Microsystems, Inc. in the USA and other countries.
-
Preface This page is intentionally left blank.
-
Contents Chapter 1 1.1 1.2 1.3 ETERNUSmgr Outline ...................................................................1 ETERNUSmgr Functions ...............................................................4 Required Software and Hardware .................................................6 2.2.1 2.2.2 2.3 2.3.1 2.3.2 2.3.3 2.3.4 2.3.5 2.4 2.4.1 2.4.2 2.5 2.5.1 2.5.2 2.5.3 2 Setup files ......................................................................................9 Modifying the ETERNUSmgr Setup .
-
Contents Chapter 4 Control Interfaces (Top Menu) ............................39 Chapter 5 Cautions................................................................41 Chapter 6 Messages ..............................................................45 6.1 6.2 6.3 6.4 Index vi Alarm History Messages ..............................................................45 Alarm Text Files ...........................................................................46 E-mail Messages .............................
-
Chapter 1 About ETERNUSmgr The ETERNUSmgr provides functions for administrators to manage the ETERNUS8000, ETERNUS4000, ETERNUS2000, ETERNUS6000, ETERNUS3000, and GR series storage systems (hereafter, storage system). There are two parts that support the management facilities, the ETERNUSmgr frontend and ETERNUSmgr backend programs. The ETERNUSmgr frontend is installed in a Managing (or Management) Server to provide specific functions across one or more storage systems.
-
1.
-
Chapter 1 About ETERNUSmgr ● Managing Server communication Communication target Port No.
-
1.2 ETERNUSmgr Functions 1.2 ETERNUSmgr Functions ETERNUSmgr provides the following three functions. • Target Device Configuration Browser • Target Device Monitoring and Failure Notification • Target Device Setup and Maintenance ■ Target Device Configuration Browser This displays the hardware structure of the target devices. ■ Target Device Monitoring and Failure Notification Target device failure is monitored for.
-
Chapter 1 About ETERNUSmgr List of components that can be monitored for each target device Device model Component GR710 GR720, GR730 GR740, GR820, GR840 Controller enclosure Yes Yes Yes Drive enclosure No Yes Yes Battery enclosure No No No FC cable No Yes Yes RCI cable No Yes Yes DEI cable No No No PANEL No No No Battery unit No No No Battery charger unit No No No 1 Device model ETERNUS3000 ETERNUS2000 ETERNUS4000 models 80 and 100 ETERNUS8000 , ETERNUS4000 , ETE
-
1.3 Required Software and Hardware 1.3 Required Software and Hardware The following software and hardware are necessary for ETERNUSmgr: See the operation connection configuration diagram "ETERNUSmgr System Configuration" (page 2).
-
Chapter 1 About ETERNUSmgr ■ Client Device settings and maintenance can be performed from an external client, providing it has a Web browser installed. Java Runtime Environment (JRE) may be necessary for some devices. ● Web browser The alarm history files from ETERNUSmgr are generated in HTML format. Also, device settings and maintenance are performed using CGI scripts or Java applets, which also require a Web browser.
-
1.3 Required Software and Hardware This page is intentionally left blank.
-
Chapter 2 Setup This chapter explains how to setup ETERNUSmgr. Setup must be performed with administrator privilege. 2.1 2 Setup files 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.
-
2.
-
Chapter 2 Setup Device Specific Setup Parameters (differences only) Target Type Setting item 2.
-
2.3 Setting Items 2.2.2 For Windows® The following describes how to edit a setup file for ETERNUSmgr for Windows®. The procedure shown is for changing the settings that were set during installation. Procedure 1 Confirm the contents of the installation directory using Explorer, etc. Make sure the following files and folder have been installed in the installation directory: _stxpoll.ini, STXPOLL.exe, STXPOLL_1.INI, stxpolld.exe, stxsmail.exe, and \www (\www is a folder). 2 Edit the STXPOLL_1.INI file.
-
Chapter 2 Setup ■ Polling Interval This parameter is used to control polling (periodically checking the status) of a target device. Set the polling interval in units of seconds within the range of 1 ~ 65535. [Default value] 300 [Parameter] POLLING_TIME (1-65535) 2 [Example] POLLING_TIME=300 This specifies the Polling Interval (time between the start of one poll to the next). Due to network or device load the actual polling time may exceed the set time.
-
2.3 Setting Items Caution: • Note that even if the TARGET_TYPE and the TARGET_FLAG settings are different, ETERNUSmgr operations are not affected. • Although any character string can be set in TARGET_TYPE, it is recommended to set one of the correct target device types ("ETERNUS8000", "ETERNUS4000", "ETERNUS2000", "ETERNUS6000", "ETERNUS3000", "GR710", "GR720", "GR730", "GR740", "GR820", or "GR840").
-
Chapter 2 Setup ■ Busy Target Detection Time This parameter is used to set the "target device busy" status detection time. Units are seconds. Depending on what the ETERNUS device is doing, its device status can sometimes temporarily become "busy". In particular, the device cannot respond while it is booting. Busy status is temporary, it does not mean device abnormality. When device busy status is detected, ETERNUSmgr inhibits notification with logs or mails of device abnormality for a set period of time.
-
2.3 Setting Items This parameter is not a required setting. If omitted, the default value will be the same as the Polling Interval. [Parameter] MAIL_SEND_TIME (1-65535) [Example] MAIL_SEND_TIME=300 This specifies the Alarm Mailing Interval (time between the sending of one notification E-mail message to the next) for sending E-mail. Due to network or device load the time to send the E-mail may exceed the expected time.
-
Chapter 2 Setup Caution: • This parameter is initially commented out. • Normally, the SMTP port is 25. However, if the SMTP port for the mail server is other than 25 for some reason, correct this parameter to match. ■ Sender Mail Address This parameter is used to change the address from which mail is sent when an error is detected in the storage system. [Default value] ETERNUSmgr@HTTP.polling.
-
2.3 Setting Items Caution: • The alarm history files must be saved in a directory immediately under the directory in which the ETERNUSmgr Top Menu is installed. When changing the location of the alarm history file directory, ensure that all the files (index.htm, menu.htm, fujitsu.gif, eternus.gif) in the parent directory (ETERNUSmgr Top Menu directory) are also moved to the new parent directory. If using multiple setup files, ensure that any modifications are consistently applied to each setup file.
-
Chapter 2 Setup [Parameter] HTML_ALARMFILE_DAY (0-65535 days) [Example] To store seven full days worth of Alarm History files (current day is not included): HTML_ALARMFILE_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 initially commented out in the default setup file available after installation. 2.3.
-
2.3 Setting Items ■ Number of Days Alarm Text Date Files are Kept This parameter specifies how long the alarm text date files are kept. Setting the number of days to "0" means that the files are not deleted. [Default value] 7 [Parameter] TEXT_ALARMFILE_DAY [Example] To save seven days worth of alarm text files: TEXT_ALARMFILE_DAY = 7 Caution: • This parameter is only enabled if the TEXT_ALARMFILE_NAME parameter has been specified.
-
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 (specifically, "/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).
-
2.4 Modifying the ETERNUSmgr Top Menu System ■ Output Log File The output log file setting has the following modes: • No log output (LOGFILE_MODE=0) No logs are output. In the case where a machine frequently has errors and the source of these errors is clear, a large number of similar system log events, none of which require any follow-up, can be generated. In such a case use the "no log" mode to allow the system to run without having to generate the useless log files.
-
Chapter 2 Setup 2.4.1 Copying/Modifying the Top Menu Files This section explains how to copy and edit the top menu files. 2.4.1.1 ETERNUSmgr for Solaris OS and Linux Procedure This section explains what to do for the Solaris OS and Linux versions of ETERNUSmgr. This procedure shows how to change the top menu directory and then edit "menu.htm". If you are not going to change the top menu directory, start from Step 4. Procedure 1 2 Confirm the current Top Menu directory (specified during installation).
-
2.4 Modifying the ETERNUSmgr Top Menu System 2.4.2 2 Copy all the Top Menu files to the new Top Menu directory. 3 Confirm the copy results using Explorer. 4 Edit the copied Top Menu file. Use a text editor such as Note Pad. Editing Top Menu file (menu.htm) Describing how to add a link to the Alarm History files and a matching target device explanation to the Top Menu file.
-
Chapter 2 Setup [Example] The following example is for monitoring an ETERNUS3000 device. Change the link in the Top Menu file, and add an explanation of the location. • Target Address = 000.000.000.000 • Old Alarm History Index URL=http://domain-name/eternus-mgr/html_1/ • New Alarm History Index URL=http://domain-name/eternus-mgr/alarm/ Specify the same value of "HTML_ALARMFILE_URL" specified in the setup file (STX~.INI) to the new Alarm History Index URL.
-
2.4 Modifying the ETERNUSmgr Top Menu System (omission)
Select RAID Device
Show hardware error detect log list
