Fujitsu 2X0-0202-01EN User Manual

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.

Structure of this Manual

This guide consists of the following 6 chapters.

● 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.

Preface

August 2007

● 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-01EN ETERNUSmgr User Guide -Introduction-

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 -Settings/Maintenance-

• ETERNUS GR740, GR820, GR840 GRmgr User Guide -Settings/Maintenance-

• ETERNUS GR710 GRmgr User Guide -Settings/Maintenance-

• ETERNUS8000, ETERNUS4000, ETERNUS2000, ETERNUS6000, ETERNUS3000 ETERNUSmgr Install Guide for Solaris™ Operating System

• ETERNUS8000, ETERNUS4000, ETERNUS2000, ETERNUS6000, ETERNUS3000 ETERNUSmgr Install Guide for Windows®

• ETERNUS8000, ETERNUS4000, ETERNUS2000, ETERNUS6000, ETERNUS3000 ETERNUSmgr Install Guide for Linux

• ETERNUS2000 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 storage system User Guide for models 700, 900, 1100, and 2100

• ETERNUS4000 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

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

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.

• Sun, Sun Microsystems, Sun logo, Solaris, and all Solaris-related 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.

• 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.

• Other company names and their products are trademarks or registered trademarks of their respective companies.

Preface

Abbreviations

The following products will be represented throughout this manual in the following abbreviations.

• Microsoft® Windows® 2000 Server operating system, Microsoft® Windows® 2000 Advanced Server operating system, and Microsoft® Windows® 2000 Datacenter Server operating system are abbreviated as Windows® 2000.

• Microsoft® Windows Server® 2003, Standard Edition, and Microsoft® Windows Server® 2003, Enterprise Edition are abbreviated as Windows Server® 2003.

• Microsoft® Windows Server® 2003 R2, Standard Edition, and Microsoft® Windows Server® 2003 R2, Enterprise Edition are abbreviated as Windows Server® 2003 R2.

• Windows® refers to all of the Windows products listed here: Windows® 2000, Windows Server® 2003, and Windows Server® 2003 R2.

• Solaris™ Operating System is abbreviated as Solaris OS.

Screen shot(s) reprinted with permission from Microsoft Corporation.

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

iii

Preface

This page is intentionally left blank.

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

Chapter 1 About ETERNUSmgr..............................................1

1.1 ETERNUSmgr Outline ...................................................................1

1.2 ETERNUSmgr Functions ...............................................................4

1.3 Required Software and Hardware .................................................6

Chapter 2 Setup.......................................................................9

2.1 Setup files ......................................................................................9

2.2 Modifying the ETERNUSmgr Setup ............................................11

2.2.1 ETERNUSmgr for Solaris OS and Linux Procedure .......................................................11

2.2.2 For Windows® ................................................................................................................12

2.3 Setting Items ...............................................................................12

2.3.1 Target Device Settings ..................................................... .................................... ... ........12

2.3.2 E-mail Notification Settings .............................................................................................15

2.3.3 Alarm History File Settings ..............................................................................................17

2.3.4 Alarm Text File Settings ...................................................... .. ..................................... ... ..19

2.3.5 Log File Settings .............................................................................................................20

2.4 Modifying the ETERNUSmgr Top Menu System .........................22

2.4.1 Copying/Modifying the Top Menu Files ................................................................... ... ... ..23

2.4.2 Editing Top Menu file (menu.htm) ...................................................................................24

2.5 Monitoring Multiple Target Devices .............................................27

2.5.1 Setup File Cautions .........................................................................................................27

2.5.2 Creating a Setup File for Each Target Device .................................................................27

2.5.3 Adding the Extra Target Devices to the Top Menu File ..................................................29

1 2 3 4 5 6

Chapter 3 Startup and Shutdown.........................................31

3.1 ETERNUSmgr for Solaris OS and Linux .....................................31

3.1.1 Starting Up ETERNUSmgr ..............................................................................................31

3.1.2 Shutting Down ETERNUSmgr ........................................................................................33

3.1.3 Setting the ETERNUSmgr Daemon for Automatic Startup .............................................33

3.2 ETERNUSmgr for Windows® ......................................................34

3.2.1 Starting Up ETERNUSmgr ..............................................................................................34

3.2.2 Shutting Down ETERNUSmgr ........................................................................................37

3.2.3 Registering the ETERNUSmgr Service for Automatic Startup ........................................37

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

Contents

Chapter 4 Control Interfaces (Top Menu)............................39

Chapter 5 Cautions................................................................41

Chapter 6 Messages..............................................................45

6.1 Alarm History Messages ..............................................................45

6.2 Alarm Text Files ...........................................................................46

6.3 E-mail Messages .........................................................................47

6.4 Log Messages .............................................................................49

Index ......................................................................................55

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

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. The ETERNUSmgr backend programs are part of the firmware within each of the storage systems, which are used to display the status and perform settings and maintenance of each respective 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 storage systems, 2) customer e-mail notification of events, and 3) event and log recording and display. The ETERNUSmgr firmware on each storage system can provide SNMP Traps. A central monitoring system is required. However, if the customer has a central monitoring system, which fields SNMP Traps (For example SOFTEK 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 storage system, using the Web browser, can be used to access the ETERNUSmgr backend programs. When events occur in a storage system, REMCS (REMote Customer Support system) e-mail services provide notice to the Fujitsu Global Support Center, whi ch in turn can notify the customer.

1.1 ETERNUSmgr Outline

ETERNUSmgr can be installed on any server (hereafter referred to as "ETERNUSmgr server") with a Windows® 2000, Windows Server® 2003, Windows Server® 2003 R2 , Solaris OS, 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 procedures from any computer with a Web browser installed. Administrators can be notified by E-mail of the details of hardware 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-01EN ETERNUSmgr User Guide -Introduction-

1.1 ETERNUSmgr Outline

ETERNUSmgr System Configuration

Managing Server

Windows/Solaris OS/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 GR series, ETERNUS8000, ETERNUS4000, ETERNUS2000, ETERNUS6000, ETERNUS3000

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 numbers must be set to allow the subsequent transmission to pass the firewall.

● Client communication

Communication target Port No./Protocol Communication direction Function Managing Server 80/tcp (*1) Client → Managing Server Display top menu

Target Device (ETERNUS2000)

Target Device (Other than ETERNUS2000)

*1: Depends on Web Server program settings *2: Port number can be changed for ETERNUS8000, ETERNUS4000 models 300, 500, and 700

80/tcp or 443/tcp Client → Target Device Display device configuration

80/tcp (*2) Client → Target Device Display device configuration

Display alarm history files

Setup and maintenance

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

Chapter 1 About ETERNUSmgr

● Managing Server communication

Communication target Port No./Protocol Communication dir ection Function Target Device

(ETERNUS2000) Target Device

(Other than ETERNUS2000)

Mail Server (Windows version only)

*1: Port number can be changed for ETERNUS8000, ETERNUS4000 models 300, 500, and 700 *2: Default value (port number can be changed depending on the mail server program)

80/tcp Managing Server → Tar-

get Device

80/tcp (*1) Managing Server → Tar-

get Device

25/tcp (*2) Managing Server → Mail

Server

Device monitoring

Mail notification

Set firewall as necessary when E-mails are to be relayed between servers.

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

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. 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 history 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 location 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 whic h the entire device is displayed). Specifically, when an error has been detected, the red warning lamp for an enclosure (Drive Enclosure, Controller Enclosure, Battery Enclosure) on the [Device Status Display] window is activated. For details on the [Device Status Display] window, see "ETERNUSmgr User Guide -Setting s/ 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.

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

List of components that can be monitored for each target device

Chapter 1 About ETERNUSmgr

Component

Controller enclosure

Drive enclosure

Battery enclosure

FC cable No Yes Yes RCI cable No Yes Yes DEI cableNoNoNo PANELNoNoNo Battery unit No No No Battery charger

unit

Component

model 50

Controller enclosure

Drive enclosure

Battery enclosure

FC cable No Yes Yes No Yes Yes RCI cable No Yes Yes No Yes No DEI cable No No No No No Yes PANEL No No No No No Yes Battery unit No No No No No Yes Battery

charger unit

Yes Yes Yes Yes Yes Yes

No Yes Yes Yes Yes Yes

No No Yes No (*1) No No

No No No No No Yes

GR710 GR720, GR730 GR740, GR820, GR840

Yes Yes Yes

No Yes Yes

No No No

ETERNUS3000

models

models 80

and100

200, 300, 400, 500, 600, and

700

Device model

ETERNUS2000

ETERNUS4000

models 80 and

100

ETERNUS8000

ETERNUS4000

ETERNUS6000

(Yes: Can be monitored, No: Cannot be monitored)

*1: Battery is installed in the controller enclosure

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. This is done by means of the following functions:

• Target Device Settings

• Collecting the Log Information of the Target Device

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

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).

List of required software and hardware

Hardware Software Solaris OS/Linux Windows

ETERNUSmgr Server

Mail Server Mail server program No Yes/No PC Web browser Yes Yes

■ 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 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 ("Chapte r 4 Control

Interfaces (Top Menu)" (page 39)). 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.

Web server program Yes/No Mail server program Yes/No

(Yes: Necessary, Yes/No: Necessary in some cases, No: Not necessary)

Yes/No

● Mail server program (ETERNUSmgr for Solaris OS 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 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.

■ Mail Server (ETERNUSmgr for Windows®)

ETERNUSmgr supports a function to notify administrators of alarms by E-mail. A mail serv er is n ecessary 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 different mail server is not needed. The mail server is not required if the E-mail notification function is not used.

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

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. Operation windows used by ETERNUSmgr are supported by the following browsers:

• 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

- Mozilla Firefox™ 1.5.0.10

• For ETERNUS300 model 80 or higher, 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 ETERNUS4000 model 300 or higher, ETERNUS8000

[Web Browsers]

- Microsoft® Internet Explorer 6.0 + Service Pack 2

- Netscape 6.0 or later (Windows® environment)

• For ETERNUS6000

[Web Browsers]

- Microsoft® Internet Explorer 6.0 or later

- Netscape 6.0 or later (Windows® environment)

Caution:

W e b browsers older than or other than those shown above may not display the window correctly.

● 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

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

1.3 Required Software and Hardware

This page is intentionally left blank.

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

Chapter 2

Setup

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

2.1 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. 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-

)

2.1 Setup files

Setting Items and Parameters Required by each OS

Setting item Parameter

Target Address

Polling Interval POLLING_TIME Yes/No Yes/No Admin Mail Address ADMIN_MAIL Yes/No (*1) Yes/No (*1) Alarm Mailing Interval MAIL_SEND_TIME Yes/No (*1) Yes/No (*1) Alarm History File Directory HTML_ALARMFILE_PATH Yes Yes Alarm History Index URL HTML_ALARMFILE_URL Yes/No (*1)(*2) Yes/No (*1)(*2) Number of Days Alarm History Files

are Kept Log Files Directory LOGFILE_PATH Yes/No Yes/No Number of Days Log Files are Kept LOGFILE_DAY Yes/No Yes/No Output Log Files LOGFILE_MODE Yes/No Yes/No Target Device TARGET_TYPE Yes Yes Target Flag TARGET_FLAG Yes Yes Detect Offline Targets DETECT_OFFLINE Yes/No Yes/No Mail Server Address ADMIN_MAILSV — Yes/No (*1)(*2) Mail Server SMTP Port SMTP_PORT — Yes/No (*1) Sender Mail Address MAIL_FROM Yes/No (*4) Yes/No (*4) Busy Target Detection Time BUSY_TIME Yes/No (*4) Yes/No (*4) Alarm Text Files Directory TEXT_ALARMFILE_NAME Yes/No (*3)(*4) Yes/No (*3)(*4) Number of Days Alarm Text Files

are Kept

TARGET_ADDR Yes Yes TARGET_PORT Yes/No Yes/No

HTML_ALARMFILE_DAY Yes/No Yes/No

TEXT_ALARMFILE_DAY Yes/No (*3)(*4) Yes/No (*3)(*4)

Solaris OS

and Linux

Windows®

(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_T IME ) a nd

the Alarm History Index URL (HTML_ALARMFILE_URL) are ignored even if specifie d. These are va lid only when the Admin Mail Address (ADMIN_MAIL) has been specified. In the Windows® 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.

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

Device Specific Setup Parameters (differences only)

Setting item Parameter

Target Device (may be changed)

Target Flag (cannot be changed)

TARGET_TYPE

TARGET_FLAG Fixed at "1" Fixed at "2" Fixed at "4"

ETERNUS

GR710, GR720,

GR730,

ETERNUS3000

Default setting is "GR710", "GR720", "GR730", or "ETERNUS3000"

GR740, GR820,

ETERNUS6000

Default setting is "GR740", "GR820", "GR840", or "ETERNUS6000"

2.2 Modifying the ETERNUSmgr Setup

This section explains how to change the setup of ETERNUSmgr for Solaris OS, Linux, or Windows®. Use a text editor to modify the setup file. Any text editor can be used as none has been specified.

Target Type

ETERNUS

GR840,

Chapter 2 Setup

ETERNUS8000, ETERNUS4000,

ETERNUS2000

Default setting is "ETERNUS8000", "ETERNUS4000", or "ETERNUS2000"

2.2.1 ETERNUSmgr for Solaris OS and Linux Procedure

This section explains what to do for the Solaris OS 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.

rocedure

1 Confirm 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.

# ls /opt/FVSVgrmgr/ stxchk _STXPOLL.INI STXPOLL_1.INI stxpoll stxpolld www/

2 Edit 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 27)

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

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.

rocedure

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.

Edit the STXPOLL_1.INI file using a text editor (Notepad, etc.).

2.3 Setting Items

This section explains the setting items (parameter s) in the setup files.

2.3.1 Target Device Settings

This section explains the settings that allow ETERNUSmgr to monito r a target device.

■ Target Address

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.

[Default value]

TARGET_PORT = 80 (TARGET_ADDR must be set. There is no default.)

[Parameter]

T A RGET_ADDR (up to 64 characters) TARGET_PORT (0-65535)

[Example]

TARGET_ADDR=127.0.0.1 or TARGET_ADDR=host-name.domain-name.com TARGET_PORT=80

Caution:

• As the default port number is normally used, the target port parameter is initially commented out.

• If the target address is changed, the target address must also be changed in the top menu ("menu.htm").

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

+ 46 hidden pages