This guide discusses procedures and safeguards relating to the use of ETERNUSmgr to config-
ure ETERNUS DX400 series, ETERNUS DX8000 series, ETERNUS2000, ETERNUS4000,
ETERNUS8000, ETERNUS3000, ETERNUS6000, or GR series device (hereafter referred to as
a "ETERNUS Disk storage system" or "device"), as well as details of how to conduct mainte
nance 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.
Structure of this Manual
This guide consists of the following 6 chapters.
Preface
-
Fourth Edition
October 2009
•Chapter 1 About ETERNUSmgr
This chapter explains the functions of ETERNUSmgr, its structure, and what other software is
required to operate it.
•Chapter 2 Setup
This chapter explains how to configure ETERNUSmgr and additionally explains how to
monitor multiple machines with ETERNUSmgr.
•Chapter 3 Startup and Shutdown
This chapter discusses how to startup and shutdown ETERNUSmgr.
•Chapter 4 Control Interfaces (Top Menu)
This chapter explains the screens used by ETERNUSmgr.
•Chapter 5 Cautions
This chapter explains important points to keep in mind when using ETERNUSmgr.
•Chapter 6 Messages
This chapter explains the various messages displayed when setting up and using
ETERNUSmgr.
P2X0-0202-04ENZ0
ETERNUS Disk storage systems ETERNUSmgr User Guide -Introduction-
3
Copyright 2009 FUJITSU LIMITED
Preface
Related Material
The following are related materials:
• ETERNUS DX400/DX8000 series ETERNUSmgr User Guide -Settings/Maintenance-
• ETERNUS2000 ETERNUSmgr User Guide -Settings/M a int en an ce - for mo de ls 10 0 an d 200
• ETERNUS3000 ETERNUSmgr User Guide -Settings/Maintenance- for model 50
• ETERNUS3000 ETERNUSmgr User Guide -Settings/Maintenance- for models 80, 100, 200,
• ETERNUS6000 ETERNUSmgr User Guide -Settings/Maintenance-
• ETERNUS8000, ETERNUS4000 ETERNUSmgr User Guide -Settings/Mainten an ce -
• ETERNUS4000 models 80 and 100 ETERNUSmgr User Guide -Settings/Maintenance-
• ETERNUS GR740, GR820, GR840 GRmgr User Guide -Settings/Maintenance-
• ETERNUS GR710 GRmgr User Guide -Settings/Maintenance-
• ETERNUS Disk storage systems ETERNUSmgr Install Guide for Solaris™ Operating System
• ETERNUS Disk storage systems ETERNUSmgr Install Guide for Windows®
• ETERNUS Disk storage systems ETERNUSmgr Install Guide for Linux
• ETERNUS Disk storage systems ETERNUSmgr Install Guide for HP-UX
• ETERNUS Disk storage systems ETERNUSmgr Install Guide for AIX
• ETERNUS DX410, DX440 Disk storage system User Guide
• ETERNUS DX8100, DX8400, DX8700 Disk storage system User Guide
• ETERNUS2000 Disk storage system User Guide for models 100 and 200
• ETERNUS3000 storage system User Guide for model 50
• ETERNUS3000 storage system User Guide for model 80
• ETERNUS3000 storage system User Guide for model 100
• ETERNUS3000 storage system User Guide for models 200, 400, and 600
• ETERNUS3000 storage system User Guide for models 300, 500, and 700
• ETERNUS6000 storage system User Guide
• ETERNUS8000 Disk storage system User Guide for models 800, 1200, and 2200
• ETERNUS8000 Disk storage system User Guide for models 700, 900, 1100, and 2100
• ETERNUS4000 Disk storage system User Guide for models 400 and 600
• ETERNUS4000 Disk storage system User Guide for models 300 and 500
• ETERNUS4000 storage system User Guide for model 100
• ETERNUS4000 storage system User Guide for model 80
300, 400, 500, 600, and 700
P2X0-0202-04ENZ0
ETERNUS Disk storage systems ETERNUSmgr User Guide -Introduction-
4
Copyright 2009 FUJITSU LIMITED
Preface
Acknowledgments
• Microsoft, Windows, and Windows Server are either registered tradema rks 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 countr ies.
• Java and all Java-related trademarks, and logos are trademarks and registered trademarks of
Sun Microsystems, Inc. in the USA and other countries.
• Sun, Sun Microsystems, Sun logo, Solaris, and all Solaris-rela ted trademarks, and logos are
trademarks and registered trademarks of Sun Microsystems, Inc. in the USA and other
countries and are used under license from Sun Microsystems Inc.
• AIX is a trademark of IBM Corp.
• HP-UX is a trademark of Hewlett-Packard Company in the U.S. and other countries.
• Linux is a registered trademark of Linus Torvalds in the USA and other countries.
• SUSE is a registered trademark of SUSE Linux AG., a subsidiary of Novell, Inc.
• Red Hat, RPM, and all Red Hat-based trademarks and logos are trademarks or registered
trademarks of Red Hat, Inc. in the USA and other countries.
• Netscape and Netscape Communicator are registered trademarks of Netscape
Communications Corporation in the USA and other countries.
• Mozilla and Firefox are registered trademarks of Mozilla Foundation.
• Adobe Acrobat is a trademark of Adobe Systems Incorporated.
• The company names, product names and service names mentioned in this document are
registered trademarks or trademarks of their respective companies.
Abbreviations
The following products will be represented throughout this manual in the following abbreviations.
ETERNUS Disk storage systems ETERNUSmgr User Guide -Introduction-
7
Copyright 2009 FUJITSU LIMITED
Chapter 1About ETERNUSmgr
The ETERNUSmgr provides functions for administrators to manage the ETERNUS DX400
series, ETERNUS DX8000 series, ETERNUS2000, ETERNUS4000, ETERNUS8000,
ETERNUS3000, ETERNUS6000, and GR series disk ETERNUS Disk storage systems (hereaf
ter, "ETERNUS Disk storage system" or "device"). There are two parts that support the manage-
ment 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 ETERNUS Disk storage systems. The ETERNUSmgr backend
programs are part of the firmware within each of the ETERNUS Disk storage systems, which are
used to display the status and perform settings and maintenance of each respective ETERNUS
Disk storage system.
This guide explains the installation and operation of the ETERNUSmgr frontend.
The ETERNUSmgr frontend provides three specific optional functions: 1) a portal for access to
each of several ETERNUS Disk storage systems, 2) customer e-mail notification of events, and
3) event and log recording and display. The ETERNUSmgr firmware on each
storage
the customer has a central monitoring system, which fields SNMP Traps (For example ETER
NUS SF Storage Cruiser), and does not need to directly receive e-mail notification of events,
then the ETERNUSmgr frontend and the Management Server are not necessary. When service
actions are necessary, direct logon to the specific
Web browser, can be used to access the ETERNUSmgr backend programs. When events occur
in an
vices provide notice to the Fujitsu Global Support Center, which in turn can notify the customer.
system can provide SNMP Traps. A central monitoring system is required. However, if
ETERNUS Disk storage system, REMCS (REMote Customer Support system) e-mail ser-
-
ETERNUS Disk
-
ETERNUS Disk storage system, using the
1.1ETERNUSmgr Outline
ETERNUSmgr can be installed on any server (hereafter referred to as "ETERNUSm gr server")
with a Windows® 2000, Windows Server® 2003, Windows Server® 2003 R2, Solaris OS, HP-
UX, AIX, or Linux operating system installed.
The ETERNUSmgr server connects to the target devices through a Local Area Network (LAN).
An administrator can determine the state of the target devices or perform maintenance proce-
dures from any computer with a Web browser installed.
Administrators can be notified by E-mail of the details of har dware failures detected by
ETERNUSmgr. It is possible to disable mail notification in ETERNUSmgr.
The illustration below shows a sample connection setup for the ETERNUSmgr.
P2X0-0202-04ENZ0
ETERNUS Disk storage systems ETERNUSmgr User Guide -Introduction-
8
Copyright 2009 FUJITSU LIMITED
Chapter 1 About ETERNUSmgr
>1.1 ETERNUSmgr Outline
ETERNUSmgr System Configuration
Managing Server
Windows/Solaris OS/HP-UX/AIX/Linux
Mail Server
(Windows version excluded)
Web Server program
Frontend
- Status monitoring and
mail notification
LAN
Mail Server
(Windows
version Only)
Work Server
Fibre
Channel
Client
Web Browser
Java Runtime Environment
(for ETERNUS2000)
WAN
ETERNUS Disk storage
system
Backend
- Status display
- Configuration display
and change
- Setup and
maintenance
The ETERNUSmgr server and work server may be collocated on the same physical server.
The management server must be running when ETERNUSmgr is used to perform maintenance
tasks.
■Network Requirements
When setting up the firewall between the server, client, and target device, the following port num-
bers must be set to allow the subsequent transmission to pass the firewall.
•Client communication
Communication
target
Managing Server80/tcp (*1)Client → Managing
Target Device
(ETERNUS2000)
Target Device
(Other than
ETERNUS2000)
*1:Depends on Web Server program settings
*2:Port number can be changed for the ETERNUS DX400 series, ETERNUS DX8000 series,
ETERNUS4000 models 300, 400, 500, and 600, and ETERNUS8000.
Port No./
Protocol
Communication
direction
Function
Display top menu
Server
Display alarm history
files
80/tcp or 443/
tcp
Client → Target DeviceDisplay device
configuration
Setup and maintenance
80/tcp (*2)Client → Target DeviceDisplay device
configuration
Setup and maintenance
P2X0-0202-04ENZ0
ETERNUS Disk storage systems ETERNUSmgr User Guide -Introduction-
9
Copyright 2009 FUJITSU LIMITED
Chapter 1 About ETERNUSmgr
>1.2 ETERNUSmgr Functions
•Managing Server communication
Communication
target
Target Device
(ETERNUS2000)
Target Device
(Other than
ETERNUS2000)
Mail Server
(Windows version
only)
*1:Port number can be changed for the ETERNUS DX400 series, ETERNUS DX8000 series,
ETERNUS4000 models 300, 400, 500, and 600, and ETERNUS8000.
*2:Default value (port number can be changed depending on the mail server program)
Port No./
Protocol
80/tcpManaging Server →
80/tcp (*1)Managing Server →
25/tcp (*2)Managing Server →
Communication
Target Device
Target Device
Mail Server
Set firewall as necessary when E-mails are to be relayed between servers.
1.2ETERNUSmgr Functions
ETERNUSmgr provides the following three functions.
• Target Device Configuration Browser
• Target Device Monitoring and Failure Notification
• Target Device Setup and Maintenance
direction
Function
Device monitoring
Device monitoring
Mail notification
■Target Device Configuration Browser
This displays the hardware structure of the ta rget devices.
■Target Device Monitoring and Failure Notification
Target device failure is monitored for. When a failure occurs, a history of the fault is saved as an
HTML file (called an "alarm history file" from here on), and the administrator is notified by E-mail
of the file's location and content. As the alarm history file is kept for a fixed period of time, the
administrator can browse the failure his tory later, as time permits.
The error monitoring function records the enclosure number where the error occurred. The error
monitoring function can detect only the error location in terms of drive enclosures, controller
enclosures, and battery enclosures, not detailed error loc ation such as hard disk, CPU, etc. To
obtain detailed location once an error is detected, please use ETERNUSmgr's [Device Status
Display] window (the window in which the entire device is displayed).
Specifically, when an error has been detected, the red warn ing lamp for an enclos ure (Drive
Enclosure, Controller Enclosure, Battery Enclosure) on the [Device Status Display] window is
activated. For details on the [Device Status Display] window, see "ETERNUSm gr User Guide -
Settings/Maintenance-".
The extent to which a device can be monitored depends on its model number. Components that
can be monitored for each type of target device are shown in the following list.
P2X0-0202-04ENZ0
ETERNUS Disk storage systems ETERNUSmgr User Guide -Introduction-
10
Copyright 2009 FUJITSU LIMITED
Chapter 1 About ETERNUSmgr
>1.2 ETERNUSmgr Functions
List of components that can be monitored for each target device
Component
Controller
enclosure
Drive
enclosure
Battery
enclosure
FC cableNoYesYes
RCI cableNoYesYes
DEI cableNoNoNo
PANELNoNoNo
Battery unitNoNoNo
Battery
charger unit
Device model
GR710GR720, GR730
YesYesYes
NoYesYes
NoNoNo
NoNoNo
GR740, GR820,
GR840
Device model
ETERNUS3000
Compone
nt
Controller
enclosure
Drive
enclosure
Battery
enclosure
FC cableNoYesYesNoYesYes
RCI cableNoYesYesNoYesNo
DEI cableNoNoNoNoNoYes
PANELNoNoNoNoNoYes
Battery
unit
Battery
charger
unit
model
50
YesYesYesYesYesYes
NoYesYesYesYesYes
NoNoYesNo (*1)NoNo
NoNoNoNoNoYes
NoNoNoNoNoYes
models
80
and100
models
200, 300,
400, 500,
600, and
700
ETERNUS
2000
ETERNUS
4000
models 80
and 100
ETERNUS
DX400
series
ETERNUS
DX8000
series
ETERNUS
8000,
ETERNUS
4000,
ETERNUS
6000
P2X0-0202-04ENZ0
(Yes: Can be monitored, No: Cannot be monitored)
*1:Battery is installed in the controller enclosure
ETERNUS Disk storage systems ETERNUSmgr User Guide -Introduction-
11
Copyright 2009 FUJITSU LIMITED
Chapter 1 About ETERNUSmgr
>1.3 Required Software and Hardware
Besides being able to detect a change in a target device's condition from normal to faulty
operation and vice-versa, the device monitoring function is also able to detect changes in the
type of problem encountered (such as the change from Offline to Alarm).
■Target Device Setup and Maintenance
This allows the target device to be setup and maintained . T h is is do ne b y means of the following
functions:
• Target Device Settings
• Collecting the Log Information of the Target Device
1.3Required Software and Hardware
The following software and hardware are necessary for ETERNUSmgr:
See the operation connection configuration diagram "ETERNUSmgr System Configuration"
(page 9).
List of required software and hardware
HardwareSoftwareSolaris OS/LinuxWindows
ETERNUSm
gr Server
Mail ServerMail server programNoYes/No
PCWeb browserYesYes
Web server programYes/No
Mail server programYes/No
(Yes: Necessary, Yes/No: Necessary in some cases, No: Not necessary)
Yes/No
■ETERNUSmgr Server
The following software is also needed on the ETERNUSmgr server.
Use the mail server program included with ETERNUSmgr if the OS is Solaris OS, HP-UX, AIX or
Linux.
•Web server program
By installing or enabling a Web server program on the ETERNUSmgr Server, user can
browse alarm history and ETERNUSmgr portal page linking multiple ETERNUS systems
(
"Chapter 4 Control Interfaces (Top Menu)" (page 46)). Web server program is not required if
neither feature is required.
We do not specify which Web server to use as long as it has the capability to show a list of
directory contents, as this is required to list the alarm history files.
P2X0-0202-04ENZ0
•Mail server program (ETERNUSmgr for Solaris OS, HP-UX, AIX, and Linux)
ETERNUSmgr supports a function to notify administrators of alarms by E-mail. This function
requires a mail server program.
ETERNUSmgr for Solaris OS, HP-UX, AIX and Linux uses Sendmail, which should come with
each OS, and this must be setup on the ETERNUSmgr server.
The mail server is not required if the E-mail notification function is not used.
ETERNUS Disk storage systems ETERNUSmgr User Guide -Introduction-
12
Copyright 2009 FUJITSU LIMITED
Chapter 1 About ETERNUSmgr
>1.3 Required Software and Hardware
■Mail Server (ETERNUSmgr for Windows®)
ETERNUSmgr supports a function to notify administrators of alarms by E-mail. A mail server is
necessary to send E-mails.
[Suitable mail servers]
• UNIX server with Sendmail that supports the SMTP protocol (including Linux server)
• Windows® 2000 Server, Windows® 2003 Server, or Windows® 2003 Server R2 that supports
the SMTP service (standard feature)
If the ETERNUSmgr server is a Windows® 2000 Server, Windows® 2003 Server, or Windows®
2003 Server R2 that supports the SMTP service (standard feature), then a differen t mail server is
not needed.
The mail server is not required if the E-mail notification function is not used.
■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.
Operation windows used by ETERNUSmgr are su pp or te d by the fo llow i ng browse rs:
• For ETERNUS GR series, ETERNUS3000 model 50
[Web Browsers]
- Microsoft® Internet Explorer 5.5 + Service Pack 2 or later
- Netscape Communicator 4.5 or later
• For ETERNUS2000
[Web Browsers]
- Microsoft® Internet Explorer 6.0 or later
- Mozilla Firefox™ 1.5.0.10 or later
- Netscape 7.1 or later (Windows® environment)
• For ETERNUS3000 (except model 50), ETERNUS4000 models 80 and 100
[Web Browsers]
- Microsoft® Internet Explorer 6.0 + Service Pack 1 or later
- Netscape 6.0 or later (Windows® environment)
• For , ETERNUS DX400 series, ETERNUS DX8000 series, ETERNUS4000 model 300, 400,
500, and 600, and ETERNUS8000
[Web Browsers]
- Microsoft® Internet Explorer 6.0 + Service Pack 2
- Microsoft® Internet Explorer 7.0
- Netscape 6.0 or later (Windows® environment)
P2X0-0202-04ENZ0
ETERNUS Disk storage systems ETERNUSmgr User Guide -Introduction-
13
Copyright 2009 FUJITSU LIMITED
Chapter 1 About ETERNUSmgr
>1.3 Required Software and Hardware
• For ETERNUS6000
[Web Browsers]
- Microsoft® Internet Explorer 6.0 or later
- Netscape 6.0 or later (Windows® environment)
•Java Runtime Environment
Java Runtime Environment must be installed to perform settings and maintenance of the
following device.
• For ETERNUS2000
[Required Software]
- Java Runtime Environment 5.0 Update 11 or later
- Java Runtime Environment 6.0 Update 3 or later
Web browsers older than or other than those shown above may not
display the window correctly.
The current status of Web browser support may be found in the latest
manual for each device.
P2X0-0202-04ENZ0
ETERNUS Disk storage systems ETERNUSmgr User Guide -Introduction-
14
Copyright 2009 FUJITSU LIMITED
Chapter 2Setup
This chapter explains how to setup ETERNUSmgr.
Setup must be performed with administrator privilege.
2.1Setup 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 "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 39) 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.
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 18)
• Target Type (See → page 20
• Target Flag (See → page 20
• Alarm History Files Directory (See → page 24
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-04ENZ0
ETERNUS Disk storage systems ETERNUSmgr User Guide -Introduction-
15
Copyright 2009 FUJITSU LIMITED
Chapter 2 Setup
>2.1 Setup files
Setting Items and Parameters Required by each OS
Solaris OS,
Setting itemParameter
Target Address
Polling IntervalPOLLING_TIMEYes/NoYes/No
Admin Mail AddressADMIN_MAILYes/No (*1)Yes/No (*1)
Alarm Mailing IntervalMAIL_SEND_TIMEYes/No (*1)Yes/No (*1)
Alarm History File DirectoryHTML_ALARMFILE_PATHYesYes
Alarm History Index URLHTML_ALARMFILE_URL
Number of Days Alarm History
Files are Kept
Log Files DirectoryLOGFILE_PATHYes/NoYes/No
Number of Days Log Files are
Alarm Text Files DirectoryTEXT_ALARMFILE_NAME
Number of Days Alarm Text
Files are Kept
TARGET_ADDRYesYes
TARGET_PORTYes/NoYes/No
HTML_ALARMFILE_DAYYes/NoYes/No
LOGFILE_DAYYes/NoYes/No
TEXT_ALARMFILE_DAY
HP-UX, AIX,
and Linux
Yes/No
(*1)(*2)
Yes/No
(*3)(*4)
Yes/No
(*3)(*4)
Windows®
Yes/No
(*1)(*2)
Yes/No
(*1)(*2)
Yes/No
(*3)(*4)
Yes/No
(*3)(*4)
P2X0-0202-04ENZ0
(Yes: Must be set, Yes/No: Optional (can be omitted), -: No applicable setting)
*1:If the Admin Mail Address (ADMIN_MAIL) is omitted, the Alarm Mailing Interval (MAIL_SEND_TIME)
and the Alarm History Index URL (HTML_ALARMFILE_URL) are ignored even if specified. These are
valid only when the Admin Mail Address (ADMIN_MAIL) has been specified. In the Wi ndows®
version, in addition to this, the Mail Server Address (ADMIN_MAILSV) and Mail Server SMTP Port
(SMTP_PORT) are enabled only when the Admin Mail Address (ADMIN_MAIL) has been specified.
*2:If the Admin Mail Address (ADMIN_MAIL) has been specified, the Alarm History Index URL
(HTML_ALARMFILE_URL) may not be omitted. The Alarm History Index URL
(HTML_ALARMFILE_URL) can be omitted only when the Admin Mail Address (ADMIN_MAIL) has
been omitted. In the Windows® version, in addition to this, the Mail Server Address (ADMIN_MAILSV)
cannot be omitted.
*3:If the Alarm Text Files Directory (TEXT_ALARMFILE_NAME) is omitted, the Number of Days Alarm
Text Files are Kept (TEXT_ALARMFILE_DAY) is ignored. The Number of Days Alarm Text Files are
Kept is only enabled when the Alarm Text Files Directory has been specified.
*4:Alarm Text Files Directory (TEXT_ALARMFILE_NAME), Number of Days Alarm Text Files are Kept
(TEXT_ALARMFILE_DAY), the Busy Target Detection Time (BUSY_TIME), and Sender Mail Address
(MAIL_FROM) are not described in the initial setup file. Add if necessary.
ETERNUS Disk storage systems ETERNUSmgr User Guide -Introduction-
16
Copyright 2009 FUJITSU LIMITED
Chapter 2 Setup
>2.2 Modifying the ETERNUSmgr Setup
Device Specific Setup Parameters (differences only)
Setting itemParameter
Target Device
(may be
changed)
Target Flag
(cannot be
changed)
TARGET_TYPE
TARGET_FLAGFixed at "1"Fixed at "2"Fixed at "4"
ETERNUS
GR710, GR720,
GR730,
ETERNUS3000
Default setting is
"GR710",
"GR720",
"GR730", or
"ETERNUS3000"
Target Type
ETERNUS
GR740, GR820,
GR840,
ETERNUS6000
Default setting is
"GR740",
"GR820",
"GR840", or
"ETERNUS6000"
ETERNUS DX400
series,
ETERNUS DX8000
series,
ETERNUS2000,
ETERNUS4000,
ETERNUS8000
Default setting is
"ETERNUS DX400",
"ETERNUS DX8000",
"ETERNUS2000",
"ETERNUS4000", or
"ETERNUS8000"
2.2Modifying the ETERNUSmgr Setup
This section explains how to change the setup of ETERNUSmgr for Solaris OS, HP-UX, AIX,
Linux, or Windows®.
Use a text editor to modify the setup file. Any text editor can be use d as none has be en specified.
2.2.1ETERNUSmgr for Solaris OS, HP-UX, AIX, and Linux Procedure
This section explains what to do for the Solaris OS, HP-UX, AIX, and Linux versions of
ETERNUSmgr.
The procedure shown is for changing the settings that were set during installation.
This explanation uses ETERNUSmgr's default installation directory "/opt/FJSVgrmgr/" as an
example.
Procedure
1Confirm the contents of the installation directory.
Make sure that the necessary files and directories (stxchk, _STXPOLL.INI,
STXPOLL_1.INI, stxpoll, stxpolld, www/) have all been installed.
P2X0-0202-04ENZ0
# ls /opt/FVSVgrmgr/
stxchk _STXPOLL.INI STXPOLL_1.INI stxpoll stxpolld www/
ETERNUS Disk storage systems ETERNUSmgr User Guide -Introduction-
17
Copyright 2009 FUJITSU LIMITED
Chapter 2 Setup
>2.3 Setting Items
2Edit the STXPOLL_1.INI file.
Vi editor is used here.
# vi /opt/FJSVgrmgr/STXPOLL_1.INI
When setting up multiple target devices, copy an existing setup file to make the setup easier. For
details on how to do this, see "2.5
Monitoring Multiple Target Devices" (page 34).
2.2.2ETERNUSmgr for Windows® Procedure
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
End of procedure
1Confirm 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).
2Edit the STXPOLL_1.INI file.
Edit the STXPOLL_1.INI file using a text editor (Notepad, etc.).
2.3Setting Items
This section explains the setting items (parameters) in the setup files.
2.3.1Target Device Settings
This section explains the settings that allow ETERNUSmgr to monitor a target device.
End of procedure
■Target Address
P2X0-0202-04ENZ0
The target address parameter is used to set the IP address or host name assigned to the target
device.
The target port number does not need to be changed (the default number is normally used).
Target address cannot be omitted. ETERNUSmgr will not start if this parameter has not been
set.
Specify SVP IP address if the ETERNUS6000 is using SVP.
ETERNUS Disk storage systems ETERNUSmgr User Guide -Introduction-
18
Copyright 2009 FUJITSU LIMITED
Chapter 2 Setup
>2.3 Setting Items
[Default value]
TARGET_PORT = 80
(TARGET_ADDR must be set. There is no default.)
[Parameter]
TARGET_ADDR (up to 64 characters)
TARGET_PORT (0-65535)
[Example]
TARGET_ADDR=127.0.0.1 or T ARGET_ADDR=host-name.domain-name.com
TARGET_PORT=80
• As the default port number is normally used, the target por t p arameter is
initially commented out.
• If the target address is changed, the target address must also be
changed in the top menu ("menu.htm").
■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)
[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 excee d the set time. In such cases, the
start of the next polling time is delayed until the previous polling finishes:
When the actual polling finishes within the scheduled polling time:
Scheduled polling
interval
Actual polling
interval
Per schedule
300 sec300 sec300 sec300 sec
150 sec
Scheduled start OK
Per schedulePer schedule
150 sec150 sec200 sec
P2X0-0202-04ENZ0
ETERNUS Disk storage systems ETERNUSmgr User Guide -Introduction-
19
Copyright 2009 FUJITSU LIMITED
Chapter 2 Setup
>2.3 Setting Items
When the actual polling exceeds the scheduled polling time:
Scheduled polling
interval
Actual polling
interval
Schedule
recalculated
300 sec300 sec300 sec300 sec
400 sec
Scheduled
start NG
Holding
Delayed start
Schedule
recalculated
150 sec450 sec
Per schedule
150 sec
Unless there is some special reason to change this parameter, it is
recommended to keep the default. For this reason the parameter is initially
commented out.
■Target Type
Sets the target device type. Two parameters are provided: TARGET_TYPE and TARGET_FLAG
These parameters cannot be omitted. ETERNUSmgr will not start if these parame ter have not
been set.
[Parameter]
TARGET_TYPE (up to 256 characters)
[Example]
Any character string can be used to describe the target device type.
When the type of target device is ETERNUS2000:
TARGET_TYPE=ETERNUS2000
• 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 ("ETERNUS
DX400", ETERNUS DX8000", "ETERNUS2000", "ETERNUS4000",
"ETERNUS8000", "ETERNUS3000", "ETERNUS6000", "GR710",
"GR720", "GR730", "GR740", "GR820", or "GR840"). The character
string in TARGET_TYPE is used when the administrator is notified by E-
mail, and in the alarm history files.
■Target Flag
Set to either 1, 2 or 4 according to the Target Type being monitored.