Top
ETERNUS SF Express V16.0/ Storage Cruiser V16.0/ AdvancedCopy Manager V16.0 Messages
FUJITSU Storage

Chapter 20 Messages That Begin with Number

There are messages that yy in the error message indicates one of the following function numbers according to the execution function used when an error occurred.

Table 20.1 Function Number and Name

Function Number of yy

Function Name

00

Common agent processing

01

Agent version acquisition

02

Device registration

03

Device deletion

04

Execution processing request

05

Host information collection

06

HBA information collection

07

Storage affinity information collection

08

Multipath information collection

09

Preparation for configuration information collection

10

Configuration information definition

11

Path diagnosis

12

Reserved

13

Reserved

14

Failure monitoring

15

Collection of detail information [error]

001

Internal error (System Error) [function]

Explanation

An internal error occurred.

Parameters

function : Function name

System Response

The system terminates processing.

System Administrator Corrective Action

This error can possibly occur when the installation directory includes spaces.

Do not specify a directory with spaces (e.g., Program Files) as the installation directory.

If you still have a problem, contact Fujitsu Technical Support.

111

A port number could not be set.

Explanation

The port number could not be set.

System Response

The system terminates processing.

System Administrator Corrective Action

Check access permissions for the %SystemRoot%\system32\drivers\etc\services file and then retry.

If you still have a problem, contact Fujitsu Technical Support.

208

The service could not be registered. Service Name: [serviceName]

Explanation

The service shown in serviceName could not be registered.

Parameters

serviceName : Name of the service that could not be registered

System Response

The system terminates processing.

System Administrator Corrective Action

Ensure that no existing service has the same name and then retry.

If you still have a problem, contact Fujitsu Technical Support.

211

SymfoWARE could not be installed.

Explanation

Symfoware could not be installed.

System Response

The system terminates processing.

System Administrator Corrective Action

An old version of Symfoware may have been installed. If Symfoware is already installed, check its version.

If you still have a problem, contact Fujitsu Technical Support.

215

Symfoware Client could not be installed.

Explanation

Installation of Symfoware Client failed.

System Response

The system terminates processing.

System Administrator Corrective Action

Contact Fujitsu Technical Support.

216

Failed to set up the ACCLI.

Explanation

Set up of the ACCLI function failed.

System Response

The system terminates processing.

System Administrator Corrective Action

Contact Fujitsu Technical Support.

217

The AdvancedCopy Manager's manager is already installed.

Explanation

It failed to install the AdvancedCopy Manager's agent because the AdvancedCopy Manager's manager has already been installed.

System Response

The system terminates processing.

System Administrator Corrective Action

Refer to the ETERNUS SF Installation and Setup Guide, and check the installation status of old version agent and incompatible software.

218

The AdvancedCopy Manager's agent is already installed.

Explanation

It failed to install the AdvancedCopy Manager's agent because the AdvancedCopy Manager's agent has already been installed.

System Response

The system terminates processing.

System Administrator Corrective Action

Refer to the ETERNUS SF Installation and Setup Guide, and check the installation status of old version agent and incompatible software.

219

The service is started.
Service Name : [serviceName]

Explanation

It failed to install the AdvancedCopy Manager's agent because the displayed service is running.

Parameters

serviceName : Service name

System Response

The system terminates processing.

System Administrator Corrective Action

Check the status of the displayed service.

If the service is running, perform the installation procedure again after stopping the service.

309

Symfoware Server in a different version-level has already been installed.

Explanation

A different version of Symfoware Server has already been installed.

System Response

The system terminates processing.

System Administrator Corrective Action

It is possible that a Symfoware Server that is not handled is installed. If the Symfoware Server is already installed, take the following action:

  1. Install a Symfoware client with the same version as the installed Symfoware Server, and then re-install the manager.

  2. Save the data of the current Symfoware Server, then uninstall Symfoware Server, and install AdvancedCopy Manager.

1000: Fyy s1 initialized.

Explanation

The agent was successfully initialized and started.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
s1 : Agent

System Administrator Corrective Action

No action is required.

1009: Fyy s1 failed.

Explanation

The agent could not be initialized and started.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
s1 : Agent

System Administrator Corrective Action

If an initialization error message is output, check the content.

If you still have a problem, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

1009: Fyy s1 is failed that CreateEvent() is abnormal.(rc=d1)

Explanation

The agent could not be started because CreateEvent() failed during initialization.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
s1 : Agent
d1 : Return value of CreateEvent()

System Administrator Corrective Action

Check the system environment for problems, such as the operating conditions of other applications.

If you still have a problem, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

1204: Fyy Diagnostic Error: (port=d1/bus=d2/tid=d3/lun=d4) s1 s2 ( d5: s3 )

Explanation

The agent detected a path error during path diagnosis.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
d1 : Port number
d2 : Bus number
d3 : Target number
d4 : LUN number
s1 : Library in which an error was detected
s2 : Library used for path diagnosis
d5 : Return value of the library in which an error was detected
s3 : Error message generated from d5

System Administrator Corrective Action

Check whether the zoning on the switch or device other than the server node subject to path diagnosis has been changed. Also check whether the physical path connections and environment configurations and connections have been changed and whether individual device functions.

1205: Fyy Diagnostic Error: (port=d1/bus=d2/tid=d3/lun=d4) s1 s2 ( d5: s3 )

Explanation

Path diagnosis could not be executed for one of the following reasons:

  • When s1 is sardc_proc_drive_no():

    The physical drive number of the device subject to path diagnosis could not be obtained.

  • When s1 is CreateFile():

    • s2 : Physical drive name (\\\\.\\PhysicalDrive%d)

      The handle of the physical drive number could not be obtained.

    • s2 : "F3GLAADR"

      The MPHD handle could not be obtained.

  • When s1 is DeviceIoControl():

    • s2 : "F3GLAADR"

      Path diagnosis was executed for a device not subject to MPHD control.

  • When s1 is calloc():

    Area acquisition failed.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
d1 : Port number
d2 : Bus number
d3 : Target number
d4 : LUN number
s1 : Library in which an error was detected
s2 : Error information
d5 : Return value of the library in which an error was detected
s3 : Error message generated from d5

System Administrator Corrective Action

The target device may have been specified incorrectly. Check whether the target device to be diagnosed and the configuration and connection of the target server node are correct. Also, check whether a multipath environment and its configuration are normal.

If there is no system problem, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

1206: Fyy Status Error: (port=d1/bus=d2/tid=d3/lun=d4) sense code=d5, sub sense=d6, status=d7.

Explanation

The SCSI command executed for path diagnosis resulted in a SCSI STATUS error.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
d1 : Port number
d2 : Bus number
d3 : Target number
d4 : LUN number
d5 : Sense data of the SCSI command executed for path diagnosis
d6 : Subsense data of the SCSI command executed for path diagnosis
d7 : SCSI STATUS of the SCSI command executed for path diagnosis

System Administrator Corrective Action

The path has no problem but the status of the device subjected to path diagnosis may be abnormal. Check the target device status, and then retry.

If you still have a problem, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

2000: Fyy Configuration error: f=s1,s2=s3.

priority

daemon.err

Explanation

The file content is destroyed.
Example: An entry terminal character (';') cannot be detected.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
s1 : Definition file name
s2 : Message that reports a detected error
s3 : Information (such as status) that determines an error

System Administrator Corrective Action

Check the content of the definition file. If one of the following problems is found, correct the content of the file manually.

If you still have a problem, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

  • When s1 is "/kernel/drv/sd.conf":

    • No entry specification should incur a problem.

      "target=?" should not exist in any entry.
      No entry terminal character (;) should exist.

    • No entry should be duplicated.

  • When s1 is "/kernel/drv/fjpfca.conf":

    • The alias entry specification should incur no problem.

      An alias and WWPN delimiter (:) are wrong.
      WWPN is not a 16-digit hexadecimal number.
      An alias is duplicated.
      No entry terminal character (;) exists.

    • The fcp-bind-target entry specification should have no problem

      An alias is wrong.
      WWPN is not a 16-digit hexadecimal number.
      A definition is duplicated.
      No entry terminal character (;) exists.

    • No entry should be duplicated.

  • When s1 is "/kernel/drv/lpfc.conf":

    • The fcp-bind-WWPN entry specification should incur no problem.

      WWPN is not a 16-digit hexadecimal number.
      A definition is duplicated.
      No entry terminal character (;) exists.

    • No entry should be duplicated.

2005: Fyy Configuration error: Fail to open agent registry subkey(s1).

Explanation

Registry could not be opened.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
s1 : Path of the registry that could not be opened

System Administrator Corrective Action

The registry information may have been damaged. Check the path of the registry that could not be opened.

If there is no system problem, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

2005: Fyy Configuration error: Fail to read agent registry key(s1).

Explanation

Registry could not be read.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
s1 : Path of registry that could not be read

System Administrator Corrective Action

The registry information may have been damaged. Check the path of the registry that could not be read.

If there is no system problem, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

2005: Fyy Configuration error: HBA(s1) driver registry key maybe wrong.

Explanation

Registry information on the HBA driver is invalid.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
s1 : HBA product name

System Administrator Corrective Action

Check the driver registry information. If possible, reinstall the driver and retry.

If you still have a problem, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

2005: Fyy Configuration error: Invalid WWPN definition detected.

Explanation

An error was detected in the descriptions in the agent setting file wwpn.dat.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)

System Administrator Corrective Action

Check wwpn.dat. If an invalid statement is found, correct it and then retry.

If you still have a problem, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

2005: Fyy Configuration error: Invalid Trap-IP definition detected.Line(s1).

Explanation

An error was detected in the descriptions in the trap destination setting file sanm.ip.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
s1 : Line number which detects abnormality

System Administrator Corrective Action

Check sanm.ip. If an invalid statement as IP address is found, correct it and then retry.

If you still have a problem, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

2005: Fyy Configuration error: s1

priority

daemon.err

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)


The meaning differs depending on the parameter s1 output, as follows:

  • When s1 is "The number of configuration HBAs is zero.":

    Explanation

    An inconsistency was detected while HBA information was read.

    System Administrator Corrective Action

    The server node environment may not have been constructed normally.
    Check whether the HBA driver has been installed and recognized correctly by the server node.

  • When s1 is "invalid description in sd.conf.":

    Explanation

    A description error was detected in the /kernel/drv/sd.conf file.

    System Administrator Corrective Action

    Correct the /kernel/drv/sd.conf file.

  • When s1 is one of the following:

    "Invalid output of fc_info -a."
    "Invalid output of fc_info -i."
    "Invalid output of fc_info."

    Explanation

    An error exists in the output result of the fc_info command of the FUJITSU PCI Fibre Channel (fjpfca) driver.

    System Administrator Corrective Action

    Check whether the FUJITSU PCI Fibre Channel (fjpfca) driver installation is correct.

    If this message is output even though the driver installation is correct, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

  • When s1 is one of the following:

    "fjpfca's major number is not found."
    "qla2200's major number is not found."

    Explanation

    The major number for the FUJITSU PCI Fibre Channel (fjpfca) driver could not be obtained. Alternatively, the major number for the Qlogic QLA2200 driver could not be obtained.

    System Administrator Corrective Action

    Check whether the FUJITSU PCI Fibre Channel (fjpfca) driver installation is correct. Alternatively, check whether the Qlogic QLA2200 driver installation is correct.

    If this message is output even though the driver installation is correct, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

  • When s1 is one of the following:

    "fjpfca.conf definition wrong."
    "affinity definition wrong."
    "Affinity definition wrong."
    "alias definition wrong."
    "alias length too long."

    Explanation

    Environment definition file /kernel/drv/fjpfca.conf for the FUJITSU PCI Fibre Channel (fjpfca) driver contains a definition error.

    System Administrator Corrective Action

    Check the definition in the fjpfca.conf file, correct any errors, and then re-execute.

  • When s1 is "Invalid output of IOMPADM.":

    Explanation

    An invalid value was detected while multipath configuration information was read.

    System Administrator Corrective Action

    Check whether MPHD or MPLB is installed correctly. If this message is output even though the driver is installed correctly, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

  • When s1 is "Invalid output of lputil.":

    Explanation

    An error exists in the output result of the lputil command of the Emulex LightPulse FC SCSI/IP Host Bus Adapter driver (lpfc driver). Alternatively, a non-supported version of the Emulex LightPulse FC SCSI/IP Host Bus Adapter driver (lpfc driver) is used.

    System Administrator Corrective Action

    Check whether the driver installation is correct. Alternatively, check whether the driver version is supported.

  • When s1 is "Invalid output of lputil.":

    Explanation

    Environment definition file /kernel/drv/lpfc.conf for the Emulex LightPulse FC SCSI/IP Host Bus Adapter driver (lpfc driver) contains a binding definition error.

    System Administrator Corrective Action

    Check the binding definition in the lpfc.conf file, correct any errors, and then re-execute.

  • When s1 is "Invalidoutput of prtconf. Entry count of fcaw is wrong.":

    Explanation

    An error exists in fcaw data that is output by the prtconf command.

    System Administrator Corrective Action

    Check whether the driver installation is correct.

2010: Fyy An request failed for unmatch between deleting IP address(s1) and any registered one.

Explanation

The agent received an unintended device deletion request.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
s1 : IP address of the Management Server that issued a device deletion request

System Administrator Corrective Action

The agent ignores the unintended device deletion request from the Management Server. Check the Management Server that issued a device deletion request and the Management Server registered the agent. Also check the manager configuration.

If you still have a problem, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

2014: Fyy Configuration error: f=s1,s2

priority

daemon.err

Explanation

The definition file contains a problem.
(For example, the entry may include an invalid number of parameters or a required parameter may be missing)

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
s1 : Definition file name
s2 : Message that indicates the detected error (error data or information that determines the status)

System Administrator Corrective Action

Check the content of the definition file. If one of the following problems is found, correct the content of the file manually.

If no problems are found, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

  • When s1 is "/kernel/drv/sd.conf":

    • No entry specification should incur a problem.

      target=?" should not exist in any entry.
      No entry terminal character (;) should exist.

    • No entry should be duplicated.

  • When s1 is "/kernel/drv/fjpfca.conf":

    • The alias entry specification should incur no problem.

      An alias and WWPN delimiter (:) are wrong.
      WWPN is not a 16-digit hexadecimal number.
      An alias is duplicated.
      No entry terminal character (;) exists.

    • The fcp-bind-target entry specification should have no problem

      An alias is wrong.
      WWPN is not a 16-digit hexadecimal number.
      A definition is duplicated.
      No entry terminal character (;) exists.

    • No entry should be duplicated.

  • When s1 is "/kernel/drv/lpfc.conf":

    • The fcp-bind-WWPN entry specification should incur no problem.

      WWPN is not a 16-digit hexadecimal number.
      A definition is duplicated.
      No entry terminal character (;) exists.

    • No entry should be duplicated.

2015: Fyy Illegal OS type(d1) detected.

Explanation

The operating system is not supported.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
d1 : OS platform ID obtained by GetVersionEx()

System Administrator Corrective Action

Use a supported operating system for operation of the agent.

2016: Fyy Illegal OS Version(d1.d2) detected.

Explanation

The operating system is not supported.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
d1 : OS major number obtained by GetVersionEx()
d2 : OS minor number obtained by GetVersionEx()

System Administrator Corrective Action

Use a supported operating system for operation of the agent.

2105: Fyy The TargetID(d1) is out of range.

Explanation

The agent detected invalid information.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
d1 : Invalid value

System Administrator Corrective Action

Refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

2105: Fyy (s1) exceeded limitation value (d1).

priority

daemon.err

Explanation

The allowable range was exceeded.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
s1 : Explanation of processing
d1 : Tolerance

System Administrator Corrective Action

Retry later.

2200: Fyy Parameter Error. check_flag=d1.

Explanation

There is insufficient information to execute path diagnosis.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
d1 : Error information

System Administrator Corrective Action

Refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

2200: Fyy Parameter Error. Invalid IP Length(d1).

Explanation

The IP address of the Management Server that the agent received during a device addition or deletion request was invalid.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
d1 : Length of received IP address

System Administrator Corrective Action

If there is no system problem, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

2200: Fyy Parameter Error. Invalid Request Action(d1).

Explanation

Request Action issued by the agent to the Management Server is invalid.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
d1 : Request Action value received from the Management Server

System Administrator Corrective Action

Refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

2200: Fyy Parameter Error. s1

priority

daemon.err

Explanation

An internal inconsistency occurred in the parameter data between the server node and Management Server.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
s1 : Message that reports a detected error

System Administrator Corrective Action

Refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

2203: Fyy Invalid OID: s1 (d1).

Explanation

An invalid OID was received.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
s1 : MIB keyword
d1 : Received value

System Administrator Corrective Action

If there is no system problem, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

2204: Fyy Invalid value type=d1, (request=d2).

Explanation

OID was received as the request value but its data type was neither a character string nor a numeric.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
d1 : Data type value of received OID
d2 : OID request value that was received

System Administrator Corrective Action

If there is no system problem, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

2205: Fyy Invalid request=d1.

Explanation

OID request value that was received is invalid.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
d1 : OID request value that was received

System Administrator Corrective Action

Refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

2206: Fyy Request sequence is wrong. reason: s1

Explanation

The sequence of the instructions given to the Management Server by the agent is invalid.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
s1 : Detail information

System Administrator Corrective Action

Refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

2207: Fyy Path Type is wrong. reason: s1

Explanation

Information used for executing path diagnosis is invalid.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
s1 : Error information

System Administrator Corrective Action

Refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

2300: Fyy Invalid IP(s1) address which is already added device.

Explanation

A device addition request was issued from the same Management Server to an agent to which a device had already been added.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
s1 : IP address of the Management Server that issued a device addition request

System Administrator Corrective Action

No action is required.

2305: Fyy Can not be set path, because hddv.conf exists.

priority

daemon.err

Explanation

Processing may have been performed in a multipath environment (in which definition files sd.conf and hddv.conf coexist).

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)

System Administrator Corrective Action

Refer to "Access Path Management" in the ETERNUS SF Storage Cruiser Operation Guide and then restore the environment such that definition file sd.conf can be recognized.

If you still have a problem, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

3100: Fyy System Error: s1: [s2]

The meaning depends on the output of s1 and s2 respectively as follows:

  • Each output of s1 and s2 are as follows:

    s1 : "parentProcess"
    s2 : "command does not exist, or command failed (255)."

    priority

    daemon.err

    Explanation

    Command does not exist or the execution of command failed.

    Parameters

    yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)

    System Administrator Corrective Action

    When Emulex's HBA driver is installed and the lputil command does not exist, this message appears. The lputil command is sometimes regarded as another package, applications kit though it depends on Enulex's HBA driver version. In that case, install applications kit too.

    If the above instruction cannot solve the problem, check the system environment for problems, such as the operating conditions of other application.

    If you still have a problem, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

  • When s1 is Library name:

    priority

    daemon.err

    Explanation

    An error occurred in the C library function or system call.

    Parameters

    yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
    s1 : Library name
    s2 : Supplementary information

    System Administrator Corrective Action

    Check the system environment for problems, such as the operating conditions of other applications.

    If you still have a problem, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

3101: Fyy System Error: Some error has occurred in s1.

Explanation

The error occurred by the library functions other than C library function.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
s1 : Library name

System Administrator Corrective Action

Check the system environment including the operating statuses of other applications for problems.

If you still have a problem, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

3101: Fyy System Error: s1: [s2](d1: s3)

priority

daemon.err

Explanation

An error occurred in the C library function or system call.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
s1 : Library name
s2 : Supplementary information
d1 : Error number (errno)
s3 : Error message character string (strerror (errno))

System Administrator Corrective Action

Check the system environment for problems, such as the operating conditions of other applications.

If you still have a problem, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

3109: Fyy Configuration file backup failed before Initialization. (s1)

priority

daemon.err

Explanation

The definition file could not be backed up when the agent was started.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
s1 : Processing to be performed upon the occurrence of an error

System Administrator Corrective Action

Check the disk capacity and syslog to check the system environment for problems. If you still have a problem, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

3110: Fyy Configuration file copy failed. (s1)

priority

daemon.err

Explanation

The definition file could not be copied to the work backup file.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
s1 : Processing to be performed upon the occurrence of an error

System Administrator Corrective Action

Check the disk capacity and syslog to check the system environment for problems. If you still have a problem, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

3111: Fyy Registry backup failed before Initialization: file(s1) path(s2).

Explanation

The agent failed to back up registry information.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
s1 : Name of failing backup file
s2 : Absolute path of failing backup file

System Administrator Corrective Action

The agent has been started even though it failed to back up information. If the agent has not been started, check the other messages.

For this message, check the target file and the path to the file.

If you still have a problem, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

3112: Fyy Error monitor could not start(IP Address: s1 ).

Explanation

An invalid IP address was detected in the device addition request from the Management Server, and error monitoring could not be started.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
s1 : IP address

System Administrator Corrective Action

Re-execute the device addition operation executed immediately before this message is output.

If you still have a problem, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

3200: Fyy Internal contradiction.

priority

daemon.err

Explanation

The agent detected an internal error.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)

System Administrator Corrective Action

Refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

3400: Fyy Configuration file Modify Error: s1

priority

daemon.err

Explanation

The work file could not be copied to the definition file when configuration information was defined.

Parameters

yy : Function number according to the execution function used when an error occurred. (Refer to "Table 20.1 Function Number and Name".)
s1 : Processing to be performed upon the occurrence of an error

System Administrator Corrective Action

Check the disk capacity and syslog to check the system environment for problems. Restore the related files by referring to "Maintenance of the Administrative Environment" in the ETERNUS SF Storage Cruiser Operation Guide.

If you still have a problem, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

00001 Server IP Address is s1

Severity

INFO

Explanation

The agent was started with IP address s1.

Parameters

s1 : Agent startup IP address

System Administrator Corrective Action

No action is required.

00002 agent is stopped

Severity

INFO

Explanation

The agent has stopped.

System Administrator Corrective Action

No action is required.

00003 agent is not started

Severity

INFO

Explanation

The agent was not started.

System Administrator Corrective Action

No action is required.

10001: SSC Agent started.

priority

daemon.notice

Severity

INFO

Explanation

The agent has started.

System Administrator Corrective Action

No action is required.

11001:s1 (ETERNUS-SSC Agent)

Severity

INFO

Explanation

  • When s1 is "service is started.":

    The agent has started.

  • When s1 is "service is normally stopped.":

    The agent has stopped.

  • When s1 is "service is abnormally stopped.":

    The agent has stopped abnormally.

Parameters

s1 : Message indicating the service status

System Administrator Corrective Action

  • When s1 is "service is started.":

    No action is required.

  • When s1 is "service is normally stopped.":

    No action is required.

  • When s1 is "service is abnormally stopped.":

    The installation environment may have a problem.
    Refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

20001: SSC Agent failed to initialize.

priority

daemon.err

Severity

ERROR

Explanation

An attempt to start the agent failed.

System Administrator Corrective Action

Refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

20002: SSC Agent failed to analyze control text.

priority

daemon.err

Severity

ERROR

Explanation

An error occurred during control statement analysis of the Correlation.ini parameter.

System Administrator Corrective Action

Refer to "Correlation.ini Parameter" in the ETERNUS SF Storage Cruiser Operation Guide to correct the Correlation.ini parameter and restart the agent.

20003: SSC Agent abnormal end.

priority

daemon.err

Severity

ERROR

Explanation

The agent ended abnormally. A possible cause is as follows:

  • The agent was already active.

System Administrator Corrective Action

Check whether the agent is active. If not, refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

21001: s1 s2 (s3)

Severity

INFO

Explanation

An attempt to start the agent was cancelled for the reason described in the detailed information.

Parameters

s1 : Error description
s2 : Detailed information
s3 : Event source name

System Administrator Corrective Action

Refer to "Collecting the troubleshooting information" in the ETERNUS SF Storage Cruiser Operation Guide to collect the information required for troubleshooting and contact Fujitsu Technical Support.

50001: Multipath setting instruction is executed.

priority

daemon.notice

Severity

INFO

Explanation

A multipath setting instruction was issued.

System Administrator Corrective Action

Wait until multipath setting is completed.

The server node is restarted when multipath setting is completed.