Fujitsu P2X0-0202-01EN manual Fatal Error Messages Code

Page 59

	Chapter 6 Messages

Can't Erase File "file name" (CODE 305)
[Explanation]	Failed to delete a file.
[Response]	Confirm your access permissions to the file and its directory. If the file you wish to
	erase does not exist, there is no problem.
Get Status Failed "server:port/path" (CODE 306)
[Explanation]	Failed to obtain the machine status.
[Response]	Check the target device operating status, LAN connection, and LAN status.
Send Data Failed "server:port/path" (CODE 307)
[Explanation]	Failed to communicate with the target device
	(ETERNUSmgr → target).
[Response]	Check the target device operating status, LAN connection, and LAN status.
Receive Data Failed "server:port/path" (CODE 308)
[Explanation]	Failed to communicate with the target device (target → ETERNUSmgr)
[Response]	Check the target device operating status, LAN connection, and LAN status.
Can't update hardware status (CODE 309)
[Explanation]	ETERNUSmgr failed to write the status of the target device onto "menu.htm".
[Response]	Check your access permissions to "menu.htm".
	Check to see if "menu.htm" is being edited while ETERNUSmgr is in operation.

■Fatal Error Messages (CODE 9XX)

Can't Create File "file name" (CODE 901)

[Explanation]	Failed to create a new file.
[Response]	Confirm your access permissions to the directory in which the file is to be created.
	Check to see if there is enough space to save the file.

Can't Open File "file name" (CODE 902)

[Explanation]	Failed to open a file.
[Response]	Confirm your access permissions to the file.

Can't Get File Status "file name" (CODE 903)

[Explanation]	Cannot acquire file status.
[Response]	Confirm your access permissions to the file and its directory.

Can't Create Socket (CODE 904)

[Explanation]	Failed to create a socket.
[Response]	Confirm system resources.

6

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

All Rights Reserved, Copyright © FUJITSU LIMITED 2007

51

Image 59

Contents Page Page Structure of this Manual PrefaceFollowing are related materials Related MaterialPreface Abbreviations AcknowledgmentsThis page is intentionally left blank Contents Index ContentsETERNUSmgr Outline About ETERNUSmgrClient communication ETERNUSmgr Outline ETERNUSmgr System ConfigurationNetwork Requirements 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 MaintenanceMail Server ETERNUSmgr for Windows Required Software and HardwareETERNUSmgr Server 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 onlySender Mail Address Alarm History File SettingsAlarm History File Directory Htmlalarmfileurl up to 64 characters Alarm History Index URLNumber of Days Alarm History Files are Kept Alarm Text Date Files Alarm Text File SettingsAlarm Text Files Directory Setup ParameterLog Files Directory Log File SettingsNumber of Days Alarm Text Date Files are Kept LOGFILEDAY=7 Changing the Windows version setting to D\ETERNUSmgr\log1\Number of Days Log Files are Kept 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 DevicesFile 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 Starting Up ETERNUSmgr Startup and ShutdownETERNUSmgr for Solaris OS and Linux ETERNUSmgr for Solaris OS and Linux Solaris OE example Setting the ETERNUSmgr Daemon for Automatic StartupShutting Down ETERNUSmgr 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 MessagesStxgrYYYYMMDD.log Alarm Text FilesAlarm Text Date Files Hardware Status was changed. See below Alarm Text Fixed FileMail Messages ETERNUSmgr VxxLxx Http Polling engine was startedStatus Component#Serial NumberStatusSerial number 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 Logfileday Htmlalarmfilename HtmlalarmfilepathIndex Index ETERNUSmgr User Guide -Introduction P2X0-0202-01EN