This section explains the 211XX message series.
Description
The status of the server server_name has been changed to status.
status can be the following statuses: "normal", "stop", and "unknown".
The name of the server is displayed for server_name.
Corrective Action
Check the status of the server server_name has been changed to status. When the status is "normal", or "stop" (after operations to stop the server have been performed), no action is required.
In any other cases, locate the fault using the ROR console.
For operation from the ROR console, refer to the following manuals:
For Virtual Edition
Refer to "Appendix A Screen Layout" in the "User's Guide VE".
For Cloud Edition
Refer to "Appendix A Screen Layout" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Description
Registration of the managed server server_name has been completed successfully.
Corrective Action
No action is required.
Description
A manager has been started.
Corrective Action
No action is required.
Description
A manager has been stopped.
Corrective Action
No action is required.
Description
A service has been started.
The service name started is displayed for service_name.
[Linux]
The PxeMtftp message of the HBA address rename setup service is not output.
Corrective Action
No action is required.
Description
A service has been stopped.
The service name stopped is displayed for service_name.
[Linux]
The PxeMtftp message of the HBA address rename setup service is not output.
Corrective Action
No action is required.
Description
An agent has been started.
Corrective Action
No action is required.
Description
An agent has been stopped.
Corrective Action
No action is required.
[Virtual Edition]
Description
Checking of detail failed because of insufficient information.
When detail is "model check"
This occurs in the following cases:
The admin resources have not been backed up as given in "Chapter 9 Admin Server Backup and Restore" in the "Operation Guide VE".
The restoration fails as a consequence of loss or corruption of the backup admin resources.
Corrective Action
No action is required.
[Cloud Edition]
Description
Checking of detail failed because of insufficient information.
When detail is "model check"
This occurs in the following cases:
The admin resources have not been backed up as given in "10.1 Admin Server Backup and Restore" in the "Operation Guide CE".
The restoration fails as a consequence of loss or corruption of the backup admin resources.
Corrective Action
No action is required.
Description
The processing of operation has been started.
The operation name is displayed for operation.
Corrective Action
No action is required.
Description
The processing of operation has been completed.
The operation name is displayed for operation.
Corrective Action
No action is required.
Description
The processing of operation has been canceled.
The operation name is displayed for operation.
Corrective Action
No action is required.
[Virtual Edition]
Description
The status of the type resource name has been changed to status.
status can be the following statuses: "normal", "stop", and "unknown".
Corrective Action
Check the status of the type resource name that has changed to status. When the status is "normal", or "stop" (after operations to stop the resource have been performed), no action is required.
In any other cases, locate the fault using the ROR console.
For operation from the ROR console, refer to "Appendix A Screen Layout" in the "User's Guide VE".
[Cloud Edition]
Description
The status of the type resource name has been changed to status.
status can be the following statuses: "normal", "stop", and "unknown".
Corrective Action
Check the status of the type resource name that has changed to status. When the status is "normal", or "stop" (after operations to stop the resource have been performed), no action is required.
When "Disk" is displayed for type, and "unknown" is displayed for status
The disk resource may be being used for other than the managed server.
Check that there are no problems.
In other cases
Locate the fault using the ROR console.
For operation from the ROR console, refer to "Appendix A Screen Layout" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When using a Solaris Container as an L-Server or an L-Platform, the poolstat command may not have been completed successfully.
Check the OS status and pool configurations, and identify the cause.
Description
Deletion of the managed server server_name has been completed successfully.
Corrective Action
No action is required.
Description
Registration of the agent has been completed successfully.
Corrective Action
No action is required.
Description
Deletion of the agent has been completed successfully.
Corrective Action
No action is required.
Description
image has been deployed on the managed server server_name.
When deployment is performed simultaneously on multiple servers, multiple names will be displayed for server_name.
Corrective Action
No action is required.
Description
The operation operation will be performed for the server OS server_os_name.
One of the following is displayed for operation:
switchover
The name of the primary server is displayed for server_name1.
The name of the spare server is displayed for server_name2.
failback
The name of the spare server is displayed for server_name1.
The name of the primary server is displayed for server_name2.
Corrective Action
No action is required.
Description
The operation displayed for detail has already been performed.
"Encryption of activation.dat" is displayed for detail.
The password in the license information file has already been encrypted.
Corrective Action
No action is required.
Description
The processing of the function for obj has been aborted.
The reason the processing of function was aborted is displayed for detail.
When detail is "hardware maintenance mode"
The processing of the function was aborted because obj is in hardware maintenance mode.
When detail is "Reserved SB"
Function was aborted because obj's Reserved SB has been set.
Corrective Action
No action is required.
Description
The cancellation process of operation has been started.
The operation name is displayed for operation.
Corrective Action
No action is required.
[Cloud Edition]
Description
When registering the managed server server_name, settings in the definition file filename were used.
Corrective Action
No action is required.
Description
A VM guest has been detected.
The server name of the VM guest is displayed for obj.
"VMguest" is displayed for type.
Corrective Action
No action is required.
[Cloud Edition]
Description
The resource displayed in type has been detected.
One of the following is displayed for type:
"VMguest"
The server name of the VM guest is displayed for obj.
"VM Guest"
[Hyper-V]
When a cloning image has been collected from a virtual L-Server with the VM type Hyper-V, a VM guest name starting with "!temp_ror" is displayed in obj.
"cloning image"
The name and version of the cloning image is displayed in obj.
"snapshot image"
The name and version of the snapshot is displayed in obj.
"vstorage"
The name of the virtual storage resource is displayed in obj.
"storage"
The name of the physical storage unit resource is displayed in obj.
Corrective Action
No action is required.
[Virtual Edition]
Description
A VM guest is no longer under the management of Resource Orchestrator.
The server name of the VM guest is displayed for obj.
"VMguest" is displayed for type.
Corrective Action
No action is required.
[Cloud Edition]
Description
The resource displayed in type is no longer being managed by Resource Orchestrator.
One of the following is displayed for type:
"VMguest"
The server name of the VM guest is displayed for obj.
[VMware]
When the configuration of server virtualization software (VMware) has been modified, the name and version of the cloning image are displayed in obj.
"VM Guest"
[Hyper-V]
When a cloning image has been collected from a virtual L-Server with the VM type Hyper-V, a VM guest name starting with "!temp_ror" is displayed in obj.
"cloning image"
The name and version of the cloning image is displayed in obj.
[VMware]
In environments where VMware vCenter Server is registered as VM management software, when a VM host is deleted from VMware vCenter Server, the name and version of the cloning image is displayed in obj.
"snapshot image"
The name and version of the snapshot is displayed in obj.
[VMware]
When restarting services of vCenter Server registered as VM management software, L-Server snapshots using the vCenter Server may no longer be managed by Resource Orchestrator.
The version of the unmanaged snapshot is displayed in obj.
"vstorage"
The name of the virtual storage resource is displayed in obj.
"storage"
The name of the physical storage unit resource is displayed in obj.
"Disk"
The disk resource name is displayed in obj.
Corrective Action
When modifying configuration of server virtualization software (VMware)
In environments where VMware vCenter Server is registered as VM management software, when deleting a VM host from VMware vCenter Server, take the following corrective action:
Refer to the server virtualization software manual for how to restore the L-Server template. Next, check whether the following message is output:
FJSVrcx:INFO:21161:image(version=version):cloning image is detected. |
If the cloning images were registered in a resource pool, refer to "3.10 rcxadm pool" in the ""Reference Guide (Command/XML) CE" to re-register (register) each cloning image in a resource pool.
Example Command
>rcxadm pool register -name ImagePool -resource master_image -type vm_image <RETURN> |
If the cloning image was being used with an L-Server, refer to "3.6 rcxadm lserver" in the "Reference Guide (Command/XML) CE" to modify the L-Server. Use the following format when specifying the XML file:
<?xml version="1.0" encoding="utf-8"?> <Resources> <LServer name="L-Server_name"> <ServerImageLink name="Cloning_image_name" version="Version"/> </LServer> </Resources> |
Example
<?xml version="1.0" encoding="utf-8"?>
<Resources>
<LServer name="L-Server1">
<ServerImageLink name="master_image" version="3" />
</LServer>
</Resources> |
Example Command
>rcxadm lserver modify -name L-Server1 -file c:\temp\modify.xml <RETURN> |
When restarting the vCenter Server service registered as VM management software
The snapshot identification information notified by vCenter Server before and after restarting of the vCenter Server services may differ. Therefore, Resource Orchestrator determines that the snapshots are no longer managed by vCenter Server, and deletes the snapshot identification information. Snapshots which are not managed by Resource Orchestrator cannot be recognized. However, snapshots exist on vCenter Server.
Operate snapshots which cannot be recognized from the vSphere Client (GUI for vCenter Server).
When operation is not possible, contact your vCenter Server administrator.
To determine the relevant snapshots, check VM guest snapshots managed by the vCenter Server which had its services restarted. Snapshots created by Resource Orchestrator are named as follows: Snapshots with names in this format that are not recognized by Resource Orchestrator are the relevant snapshots.
RCX__L-Server_host_name@version |
L-Server_host_name: a host name for the L-Server which holds relevant snapshots is displayed.
The version of the snapshot displayed in the message is displayed in version.
Delete unnecessary snapshots from vSphere Client.
In other cases
No action is necessary.
Description
A VM guest has been migrated.
The server name of the VM guest is displayed for obj.
"VMguest" is displayed for type.
Corrective Action
No action is required.
[Cloud Edition]
Description
The resource displayed in type has been migrated.
"Disk" is displayed in type.
The name of the disk that has been migrated is displayed in obj.
Corrective Action
No action is required.
Description
Execution of the script script_name has been started.
Corrective Action
No action is required.
Description
Execution of the script script_name has been completed successfully.
Corrective Action
No action is required.
[Cloud Edition]
Description
The configuration information (CPU, memory, disk, etc.) of the L-Server on obj has been updated.
"L-Server" is displayed in type.
Corrective Action
No action is required.
