Fujitsu ETERNUS User Manual page 49

Chapter 5 Cautions
>
• 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
messages.
-
-
• If, when monitoring multiple target devices, there is a specification error, such as duplication
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
"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 burden
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
-
-
• ETERNUSmgr compatibility with GRmgr versions V10L30 and later (V10L30, V10L40,
V10L50, V10L60)
-
-
P2X0-0202-04ENZ0 ETERNUS Disk storage systems ETERNUSmgr User Guide -Introduction-
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"
"Chapter 2 Setup" (page 15)
The operating logic, data files and log files for GRmgr versions V10L20 or earlier are not
compatible with ETERNUSmgr. When upgrading GRmgr version V10L20 or earlier to
ETERNUSmgr, 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 is compatible with the operating logic, data files and log files of GRmgr
versions 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.
for information on how to modify the setup files, and
49
Copyright 2009 FUJITSU LIMITED