Fujitsu P2X0-0202-01EN manual Log Messages Server Status Change Code, Bad Parameter parameter Code

Page 58

6.4 Log Messages

Server Status Change (CODE 012)

[Explanation]	There has been a change in the target device’s status.
[Response]	If the component that caused the problem is included in the message, login to the
	target device and check the status of that component.
	When "No hardware error detected." is displayed, there is no need to do anything.
	Detection of the offline status is indicated when "No hardware report detected.
	(Offline)" is displayed. In this case, check for problems with the target device, fail-
	ures in the communications route, and errors in the setup file.

Work files create to "temp directory" (CODE 014)

[Explanation]	ETERNUSmgr has created a work file in the directory indicated in this message.
[Response]	None

■Warning Messages for Parameter Settings (CODE 1XX)

Bad Parameter "parameter" (CODE 102)

[Explanation]	This parameter setting is invalid.
[Response]	Correct the parameter setting.

Undefined Parameter "parameter" (CODE 103)

[Explanation]	This parameter setting is not recognized.
[Response]	Correct the parameter setting.

Parameter too long "parameter" (CODE 104)

[Explanation]	Too many characters are used in this parameter setting.
[Response]	Correct the parameter setting.

Not NULL Parameter "parameter" (CODE 105)

[Explanation]	NULL is not allowed for this parameter setting.
[Response]	Set the parameter.

Directory Name too long "directory name" (CODE 106)

[Explanation]	The directory name is too long.
[Response]	Set a shorter directory name.

■Warning Messages (CODE 3XX)

Can't Connect Server "server:port" (CODE 301)

[Explanation]	Failed to connect to the machine.
[Response]	Check the network environment (IP address, etc.).

Can't Send Mail "name@server" (CODE 304)

[Explanation]	Failed to send an E-mail.
[Response]	Check the mail server is operating.

50

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

All Rights Reserved, Copyright © FUJITSU LIMITED 2007

Image 58

Contents Page Page Preface Structure of this ManualPreface Related MaterialFollowing are related materials Acknowledgments AbbreviationsThis page is intentionally left blank Contents Contents IndexAbout ETERNUSmgr ETERNUSmgr OutlineNetwork Requirements ETERNUSmgr Outline ETERNUSmgr System ConfigurationClient communication About ETERNUSmgr Managing Server communication Target Device Monitoring and Failure Notification Target Device Configuration BrowserETERNUSmgr Functions ETERNUSmgr FunctionsTarget Device Setup and Maintenance Yes Can be monitored, No Cannot be monitoredETERNUSmgr Server Required Software and HardwareMail Server ETERNUSmgr for Windows Client This page is intentionally left blank Setup Setup filesSetup files Setting Items and Parameters Required by each OS Modifying the ETERNUSmgr Setup ETERNUSmgr for Solaris OS and Linux ProcedureFor Windows Setting ItemsTarget Device Settings Target AddressTarget Type When the actual polling exceeds the scheduled polling timePolling Interval POLLINGTIME=300Target Flag Detect Offline TargetsAlarm Mailing Interval Mail Notification SettingsAdmin Mail Address Busy Target Detection TimeMail Server Smtp Port ETERNUSmgr for Windows only AdminmailsvMail Server Address ETERNUSmgr for Windows only MAILSENDTIME=300Alarm History File Directory Alarm History File SettingsSender Mail Address Number of Days Alarm History Files are Kept Alarm History Index URLHtmlalarmfileurl up to 64 characters Setup Parameter Alarm Text File SettingsAlarm Text Files Directory Alarm Text Date FilesNumber of Days Alarm Text Date Files are Kept Log File SettingsLog Files Directory Number of Days Log Files are Kept Changing the Windows version setting to D\ETERNUSmgr\log1\LOGFILEDAY=7 Modifying the ETERNUSmgr Top Menu System Output Log FileETERNUSmgr for Solaris OS and Linux Procedure Copying/Modifying the Top Menu FilesEditing Top Menu file menu.htm Setting the Link to the Alarm History FilesInstallation Location Machine Name Storage systems other than ETERNUS2000Setup Example ↓ Becomes HtmlMonitoring Multiple Target Devices Setup File CautionsCreating a Setup File for Each Target Device Format STX-.INIMonitoring Multiple Target Devices File name starts with STX and ends with .INI2nd Target Device ETERNUS2000#1 Adding the Extra Target Devices to the Top Menu FileExample 1st Target Device ETERNUS3000#1 3rd Target Device ETERNUS3000#2Status of 000.000.000.000 -- font color=red*Offline*/font ETERNUSmgr for Solaris OS and Linux Startup and ShutdownStarting Up ETERNUSmgr ETERNUSmgr for Solaris OS and Linux Shutting Down ETERNUSmgr Setting the ETERNUSmgr Daemon for Automatic StartupSolaris 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 Control Interfaces Top Menu Select RAID Device menuShow hardware error detect log list menu ETERNUS6000Solaris OS, Linux, and Windows Version Cautions ETERNUSmgr User Guide -Introduction- P2X0-0202-01EN Detectoffline = True Uninstall Windows only cautionsMessages Alarm History MessagesExample Alarm History File YYYYMMDDHHmmSSn.htmlAlarm Text Date Files Alarm Text FilesStxgrYYYYMMDD.log ETERNUSmgr VxxLxx Http Polling engine was started Alarm Text Fixed FileMail Messages Hardware Status was changed. See belowSerial number Component#Serial NumberStatusStatus Log Messages Regular Messages CodeBad Parameter parameter Code Log Messages Server Status Change CodeWork files create to temp directory Code Undefined Parameter parameter CodeFatal Error Messages Code Cant Create Directory path Code Log Messages Cant Allocate Memory CodeBad IP Address host name or IP address Code Not Find Parameter parameter CodeAn example of log message output is shown below Result of a target device status inquiry SuccessLog Messages Index Htmlalarmfilename HtmlalarmfilepathLogfileday Index ETERNUSmgr User Guide -Introduction P2X0-0202-01EN