Top
ServerView Resource Orchestrator Cloud Edition V3.0.0 Reference Guide for Infrastructure Administrators (Resource Management)

3.1.4 41XXX Series

This section explains the 41XXX message series.

41303

FJSVrcx:WARNING:41303:server_name:server status is changed to status

[Description]

Refer to the explanation in "Message number 41303" in the "Messages VE".

However, for Resource Orchestrator, "warning", "error", or "unknown" may be displayed for the status of the L-Server or the resources that comprise the L-Server.

[Corrective Action]

Refer to the explanation in "Message number 41303" in the "Messages VE".

When "warning", "error", or "unknown" are displayed for status of the L-Server or the resources that comprise the L-Server, perform the following corrective action:

  • Identify the failure location from the ROR console.

    For the operation method using the ROR console, refer to "Chapter 1 User Interface" of the "User's Guide for Infrastructure Administrators (Resource Management) CE".

  • When there is resource management software on the resource, identify the failed part using the resource management software.


41502

FJSVrcx:WARNING:41502:obj:function was skipped (cause)

[Description]

During the operation for obj, part of the process function was skipped to enable continuance of the operation.

The resource name is displayed for obj.
The name of the skipped process is displayed for function.
The reason the process was not performed is displayed for cause.

[Corrective Action]

  • When "StorageChassisFailover" is displayed for function:

    The process obj was skipped by the switchover between operating and standby storage.

    Take corrective action based on the content displayed for cause.

    • "not supported"

      There are no storage unit name or volume identifiers in the disk information.

      Check that the content of the replication definition file is correct.

    • "mirror_definition not found"

      The replication definition file corresponding to a disk registered in Resource Orchestrator does not exist.

      Check that the content of the replication definition file is correct.

    • "not pre_created"

      The disk registered with Resource Orchestrator is not the one created in advance.

      The target is the disk created in advance.