Fujitsu P2X0-0202-01EN manual Startup and Shutdown, ETERNUSmgr for Solaris OS and Linux

Page 39

Chapter 3

Startup and Shutdown

This chapter explains how to startup and shutdown ETERNUSmgr.

3.1ETERNUSmgr for Solaris OS and Linux

This section explains how to manually startup and shutdown ETERNUSmgr, for Solaris OS and Linux as well as how to set ETERNUSmgr for automatic startup.

3.1.1Starting Up ETERNUSmgr

Perform the following to start ETERNUSmgr for Solaris OS and Linux:

Procedure

1Become the superuser.

#su

2Execute the execution control script with the start option:

#/opt/FJSVgrmgr/stxpoll start

3Confirm the daemon is running:

#ps -e grep stxpolld

999 ? 0:00 stxpolld

3

After ETERNUSmgr has started up, you need to view the log file to confirm whether or not ETER- NUSmgr is in communication with the target device. If using the E-mail notification function, also check that E-mail notification of ETERNUSmgr startup and changes in the target device states is received.

ETERNUSmgr startup can be confirmed by:

•Use the ps command to check that the service is activated.

•Checking the log, and making sure that communication with the target device is normal.

•Checking E-mails, and making sure that communication with the target device is normal (if the E-mail notification function is used).

When monitoring multiple target devices, you must check each target device separately. For example, if monitoring three devices, issue the ps command to check that all three devices are activated, and then browse each of the three logs to make sure that communications with all are normal.

The following message appears when you try to startup ETERNUSmgr by the above procedure and ETER- NUSmgr is running already. ETERNUSmgr must be shutdown before it can be started up. For instructions on how to shut down ETERNUSmgr, refer to "3.1.2 Shutting Down ETERNUSmgr" (page 33).

/opt/FJSVgrmgr/stxpoll: Already running.

*** stxpoll could not start. ***

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

All Rights Reserved, Copyright © FUJITSU LIMITED 2007

31

Image 39

Contents Page Page Structure of this Manual PrefaceRelated Material PrefaceFollowing are related materials Abbreviations AcknowledgmentsThis page is intentionally left blank Contents Index ContentsETERNUSmgr Outline About ETERNUSmgrETERNUSmgr Outline ETERNUSmgr System Configuration Network RequirementsClient communication About ETERNUSmgr Managing Server communication ETERNUSmgr Functions Target Device Configuration BrowserETERNUSmgr Functions Target Device Monitoring and Failure NotificationYes Can be monitored, No Cannot be monitored Target Device Setup and MaintenanceRequired Software and Hardware ETERNUSmgr ServerMail Server ETERNUSmgr for Windows Client This page is intentionally left blank Setup files SetupSetup files Setting Items and Parameters Required by each OS ETERNUSmgr for Solaris OS and Linux Procedure Modifying the ETERNUSmgr SetupTarget Address Setting ItemsTarget Device Settings For WindowsPOLLINGTIME=300 When the actual polling exceeds the scheduled polling timePolling Interval Target TypeDetect Offline Targets Target FlagBusy Target Detection Time Mail Notification SettingsAdmin Mail Address Alarm Mailing IntervalMAILSENDTIME=300 AdminmailsvMail Server Address ETERNUSmgr for Windows only Mail Server Smtp Port ETERNUSmgr for Windows onlyAlarm History File Settings Alarm History File DirectorySender Mail Address Alarm History Index URL Number of Days Alarm History Files are KeptHtmlalarmfileurl up to 64 characters Alarm Text Date Files Alarm Text File SettingsAlarm Text Files Directory Setup ParameterLog File Settings Number of Days Alarm Text Date Files are KeptLog Files Directory Changing the Windows version setting to D\ETERNUSmgr\log1\ Number of Days Log Files are KeptLOGFILEDAY=7 Output Log File Modifying the ETERNUSmgr Top Menu SystemCopying/Modifying the Top Menu Files ETERNUSmgr for Solaris OS and Linux ProcedureStorage systems other than ETERNUS2000 Setting the Link to the Alarm History FilesInstallation Location Machine Name Editing Top Menu file menu.htmSetup Example Html ↓ BecomesFormat STX-.INI Setup File CautionsCreating a Setup File for Each Target Device Monitoring Multiple Target Devices File name starts with STX and ends with .INI Monitoring Multiple Target Devices3rd Target Device ETERNUS3000#2 Adding the Extra Target Devices to the Top Menu FileExample 1st Target Device ETERNUS3000#1 2nd Target Device ETERNUS2000#1Status of 000.000.000.000 -- font color=red*Offline*/font Startup and Shutdown ETERNUSmgr for Solaris OS and LinuxStarting Up ETERNUSmgr ETERNUSmgr for Solaris OS and Linux Setting the ETERNUSmgr Daemon for Automatic Startup Shutting Down ETERNUSmgrSolaris OE example 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 Select RAID Device menu Control Interfaces Top MenuETERNUS6000 Show hardware error detect log list menuSolaris OS, Linux, and Windows Version Cautions ETERNUSmgr User Guide -Introduction- P2X0-0202-01EN Detectoffline = True Windows only cautions UninstallYYYYMMDDHHmmSSn.html Alarm History MessagesExample Alarm History File MessagesAlarm Text Files Alarm Text Date FilesStxgrYYYYMMDD.log Hardware Status was changed. See below Alarm Text Fixed FileMail Messages ETERNUSmgr VxxLxx Http Polling engine was startedComponent#Serial NumberStatus Serial numberStatus Regular Messages Code Log MessagesUndefined Parameter parameter Code Log Messages Server Status Change CodeWork files create to temp directory Code Bad Parameter parameter CodeFatal Error Messages Code Not Find Parameter parameter Code Log Messages Cant Allocate Memory CodeBad IP Address host name or IP address Code Cant Create Directory path CodeResult of a target device status inquiry Success An example of log message output is shown belowLog Messages Htmlalarmfilename Htmlalarmfilepath IndexLogfileday Index ETERNUSmgr User Guide -Introduction P2X0-0202-01EN