When Trying to Open the [Migrate an L-Server] Dialog for an L-Server with unknown Status, it may Indicate Loading but not become Operable.
[Description]
When trying to open the [Migrate an L-Server] dialog for an L-Server with unknown status, it may indicate loading but not become operable. The following causes are possible:
A VM guest used on the L-Server has been deleted from server virtualization software
During L-Server deletion, system failure of the VM management software server or VM management software has occurred
During L-Server deletion, system failure of admin server or manager occurs
[Corrective Action]
Close the [Migrate an L-Server] dialog, when loading takes a very long time.
After that, check that the admin server, manager, VM management software server, or VM management software have been started, and perform the relevant operation.
For a.:
Delete the L-Server.
For b. or c.:
Delete the L-Server again.
The Status of an L-Server is Displayed as unknown, and "Message number 67154" or "Message number 67178" is Displayed Even if Operations Other Than L-Server Deletion are Performed.
[Description]
The status of an L-Server is displayed as unknown, and even if operations other than L-Server deletion are performed, the following message is displayed.
FJSVrcx:ERROR:67154:server OS:not found |
The following causes are possible:
A VM guest used on the L-Server has been deleted from server virtualization software
During L-Server deletion, system failure of the VM management software server or VM management software has occurred
During L-Server deletion, system failure of admin server or manager occurs
A VM guest used on the L-Server has been moved from server virtualization software to a VM host which is unregistered in VM pool
For details on the messages, refer to "Message number 67154" or "Message number 67178".
[Corrective Action]
Check that the admin server, manager, VM management software server, or VM management software have been started, and perform the relevant operation.
For a.:
Delete the L-Server.
For b. or c.:
Delete the L-Server again.
For d.:
Migrate VM guests being used on the L-Server to VM hosts which are already registered in the VM pool.
When Deleting an L-Server, "Message number 67391", "Message number 67210" or "Message number 67280" are Displayed and Deletion Fails.
[Description]
The VM host, which the L-Server is running on, detects that the VM guest of the L-Server does not exist, so the following messages are output and L-Server deletion fails.
|
For details on the messages, refer to "Message number 67391", "Message number 67210", and "Message number 67280".
[Corrective Action]
Check the name of the VM guest of the L-Server using the GUI or the CLI.
When using the GUI:
Display the ROR console.
Select the L-Server on the orchestration tree.
Select the [Resource Details] tab on the main panel, and check the guest name of the resource.
When using the CLI:
Execute the following command:
>rcxadm lserver show -name L-Server_name <RETURN> |
Check the display of "VmGuest:".
If the VM guest name is not displayed, delete the L-Server again.
If the VM guest name is displayed, check that migration is not being performed from the management screen of the VM management software, and then delete the L-Server again.
When any message is output during deletion of the L-Server, check that the VM guest name of the L-Server is not displayed, and then delete the L-Server again.
Migrating an L-Server between Servers Fails, and "Message number 67385" is Displayed.
[Description]
After starting an L-Server operating on a VMware VM host, when migration between servers is performed before completion of starting of the OS, the following message is output and migration fails.
FJSVrcx:ERROR:67385:migrating VM guest failed. VM_guest_name migrate from source_server to destination_server. detail=(message,vmerrno=150,ip=IP_address) |
For details on the message, refer to "Message number 67385".
[Corrective Action]
Perform the operation again after starting of the L-Server's OS is complete.
When a Virtual L-Server is Stopped, "Message number 69122" is Displayed, and Stopping of the L-Server Fails.
[Description]
When stopping the L-Server, the following message may be displayed, and stopping of the L-Server will fail.
FJSVrcx:ERROR:69122:timeout occurred while executing power control modules. |
Timeout occurs because shutdown of the OS running on the L-Server takes a long time.
For details on the messages, refer to "Message number 69122" of "Messages VE".
[Corrective Action]
Use the following procedure to change the wait time for stopping the L-Server.
Change the wait time.
Change the parameter value given in the following file, according to your environment.
Specify the parameter value in seconds. Do not change other parameters.
The Target File
[Windows]
Installation_folder\Manager\rails\config\rcx\vm_guest_params.rb
[Linux]
/opt/FJSVrcvmr/rails/config/rcx/vm_guest_params.rb
Parameter
SHUTDOWN_TIMEOUT
Example
When you change the wait time from 5 minutes to 15 minutes
Before changing: SHUTDOWN_TIMEOUT = 300
After changing: SHUTDOWN_TIMEOUT = 900
Restart the Manager.
The changed value is enabled.
[Windows]
>Installation_folder\Manager\bin\rcxadm mgrctl stop <RETURN> |
[Linux]
# /opt/FJSVrcvmr/bin/rcxadm mgrctl stop <RETURN> |
When a Disk Resource is Connected to an L-Server, "Message number 62511" is Displayed and Connection Fails.
[Description]
When a disk resource is connected to an L-Server, the following message may be displayed, and connection fails.
FJSVrcx:ERROR:62511:failed to control obj. IF=%1, message="ERROR:ssmgr3422:As for specified volume Volume_number, the LUN mapping is done." |
In obj, the resource name of the storage management software is displayed.
In %1, the internal function name is displayed.
Connecting a disk resource to an L-Server has failed, because the Volume corresponding to the disk resource has already been mapped.
[Corrective Action]
The disk resource may be being used by another server.
If a Volume corresponding to a disk resource that has wrongly been specified from another server was being used, delete the mapping definition of the Volume to cancel the relation to the server. After that, connect the disk resource to the L-Server again.
Check the affinity group number of each ETERNUS storage.
Execute the following command to display the affinity groups of each ETERNUS storage that is managed using ESC.
>ESC_manager_installation_folder\Manager\opt\FJSVssmgr\sbin\storageadm affinity info -ipaddr ETERNUS_IP_address <RETURN> |
Check all affinity group numbers that are displayed for "NUMBER".
Check the details of each affinity group to identify the affinity group numbers that have been defined for the mapped Volume.
Using the affinity group numbers checked in 1., view the Volume number defined for each affinity group. Find the affinity group with the volume number "VOLUME" displayed in the message.
>ESC_manager_installation_folder\Manager\opt\FJSVssmgr\sbin\storageadm affinity info -ipaddr ETERNUS_IP_address -affinitygroup Affinity_group_number <RETURN> |
Delete a Volume from the affinity group.
When the affinity group has multiple mapping definitions
Execute the following command to delete the Volume from the affinity group that was checked in 2., which corresponds to the volume number that is displayed in the message.
>ESC_manager_installation_folder\Manager\opt\FJSVssmgr\sbin\storageadm affinity update -ipaddr ETERNUS_IP_address -affinitygroup Affinity_group_number -delete -volume Volume_number <RETURN> |
When the affinity group has only one mapping definition
Check HBAs that use the affinity group, then delete the definition of the HBA.
After that, delete the affinity group.
Executing the following command displays the affinity group number, which is used from the WWPN of the CA of ETERNUS, from the WWPN of the HBA that uses ETERNUS, and from the server.
>ESC_manager_installation_folder\Manager\opt\FJSVssmgr\sbin\storageadm zone info -hex <RETURN> |
In the lines after the output result of "<<< FC CA Zone Information >>>", the affinity group numbers that are used from the WWPN of the CA of ETERNUS, from the WWPN of the HBA that uses ETERNUS, and from the server are collectively displayed for each storage unit.
Check the WWPN of the CA and HBA which correspond to the affinity group.
Execute the following command to delete the definition of an HBA.
>ESC_manager_installation_folder\Manager\opt\FJSVssmgr\sbin\storageadm zone delete -storage CA_WWPN,Affinity_group_number -hba HHBA_WWPN -update all <RETURN> |
Execute the following command to delete an affinity group.
>ESC_manager_installation_folder\Manager\opt\FJSVssmgr\sbin\storageadm affinity delete -ipaddr ETERNUS_IP_address -affinitygroup Affinity_group_number <RETURN> |
When "Message number 67320" is Displayed after Recovery of the Manager from System Failure Due to L-Server Power Operations.
[Description]
If system failure occurs on the manager after L-Server power operations (power on or off, or reboot), restoring the manager automatically performs the power operation, and it may fail. In this case, the following messages will be output in the event log.
When the power is turned ON
FJSVrcx:ERROR:67320:power control error. target=target detail=(xm create::Error: VM name 'VM_guest_name' already in use by domain Number,vmerrno=400,ip=IP_address) |
When the power is turned OFF
FJSVrcx:ERROR:67320:power control error. target=target detail=(xm shutdown::Error: Domain 'VM_guest_name' does not exist.,vmerrno=400,ip=IP_address) |
[Corrective Action]
As a power operation is being performed on the L-Server, ignore the error.
When an RHEL-Xen Agent is Registered, "Message number 67359" is Displayed, and Registration of the Agent Fails.
[Description]
When registering an RHEL-Xen agent, the following message is displayed, and registration of the agent may fail.
RcxError (FJSVrcx:ERROR:67359:VM_host_name: VM host registration failed detail=(get_host_info::/opt/FJSVrcxxen/bin/xen_plugin: line Number: Number – Number - (Number - ): syntax error: operand expected (error tok...,vmerrno=400,ip= VM_host_IP_address)) |
For details on the message, refer to "Message number 67359".
[Corrective Action]
The parameters set for the following file in the VM host for registration may be incorrect:
/etc/xen/xend-config.sxp
Open the file and check that parameters are correct.
For details on the parameters, refer to the "Red Hat Enterprise Linux 5 Virtualization Guide".
Red Hat Enterprise Linux 5 Virtualization Guide
URL: http://docs.redhat.com/docs/en-US/Red_Hat_Enterprise_Linux/5/html/Virtualization/index.html (As of February 2012) |
Example
Check that the following parameter in the VM host, defining the minimum amount of memory to reserve, is described along a format.
(dom0-min-mem Memory_capacity)
