The Guest OS Associated with the L-Server Does Not Start Properly When the L-Server Assigned with an Image is Started for the First Time.
[Description]
When an L-Server assigned with an image is started for the first time or when the guest OS is being started, one of the following messages is displayed on the guest OS console and the guest OS fails to startup.
"The computer restarted unexpectedly or encountered an unexpected error." is displayed
"Windows could not parse or process the unattend answer file for pass [specialize]" is displayed
"Your Product Key uniquely identifies your copy of windows." is displayed on the product key entry screen
"The system could not log you on. Make sure your User name and domain are correct, then type your password again. Passwords are case-sensitive. " is displayed
[Corrective Action]
The parameters set for the OS specified when creating an L-Server may be incorrect. Set the correct values and perform the operation again.
For a. through c.:
Check the product key value. If the value is not correct, set the correct value.
For d.:
Check the administrator password value. If the value is not correct, set the correct value.
For details on the parameters set for the OS, refer to "10.2.5 [OS] Tab" or "10.3.5 [OS] Tab" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When System Failure Occurs on the Admin Server or Manager, or Job Cancellation or Timeout Occurs on the VM Management Software, Creating or Starting the L-Server Fails, and VM Guests in the Process of Being Created Using Server Virtualization Software Remain.
[Description]
When the following events occur while creating or starting the L-Server, one of the following messages may be output in the event log, and creating or starting of the L-Server will fail.
Occurred Problems
System failure, or reboot of the admin server or manager
Job cancel or time out on VM management software
Server switchover in which managers are operating using the HA function of cluster software or server virtualization software
Messages
|
After starting the manager again, one of the following messages is output in the event log, and creating or starting the L-Server that was being created before the manager stopped may fail.
|
For details on the messages, refer to "Message number 67390" or "Message number 67392".
When the message above is output, VM guest in process of creation may remain on server virtualization software.
[Corrective Action]
Make sure that the manager is running, and use the following procedure for restoration:
Check the VM guest name related to the error message above with the event log on the ROR console. The VM guest name is displayed for the resource name in the event log.
Display the VM management console, and check if the VM guest checked in 1. exists. Also, confirm that an existing disk has been attached.
If a VM guest exists and an existing virtual disk has been attached at 2., detach the virtual disk. For details on how to detach virtual disks, refer to the server virtualization software manual. (*1)
*1: When the server virtualization software is Hyper-V, select "No" for the "When a virtual hard disk file is removed from a virtual machine, it can also be removed from the virtual machine host. Do you want Virtual Machine Manager to do this for you?" displayed when deleting a virtual disk.
If there is a VM guest that meets the condition in 2., delete it from the VM management console. For details on how to delete VM guests, refer to the server virtualization software manual. (*2)
*2: When server virtualization software is VMware, select "Delete from Disk", when deleting VM guests.
After confirming from the server tree or orchestration tree on the ROR console that the VM guest that was checked in 1. does not exist, create or start the L-Server again.
When System Failure Occurs on the VM Management Server or VM Management Software during L-Server Creation, Creating or Starting the L-Server Fails but VM Guests Being Created on Server Virtualization Software may Remain.
[Description]
If system failure occurs on the VM management software server or VM management software while creating or starting the L-Server, one of the following messages may be output in the event log, and creating or starting of the L-Server will fail.
|
For details on the messages, refer to "Message number 67390" and "Message number 67392".
When the message above is output, VM guest in process of creation may remain on server virtualization software.
[Corrective Action]
Make sure that the VM management software is running, and use the following procedure for restoration.
Check the resource name related to the error message above with the event log on the ROR console. The VM guest name is displayed for the resource name.
Display the VM management console, and check if the VM guest checked in 1. exists. Also, confirm that an existing disk has been attached.
If a VM guest exists and an existing virtual disk has been attached at 2., detach the virtual disk. For details on how to detach virtual disks, refer to the server virtualization software manual. (*1)
*1: When the server virtualization software is Hyper-V, select "No" for the "When a virtual hard disk file is removed from a virtual machine, it can also be removed from the virtual machine host. Do you want Virtual Machine Manager to do this for you?" displayed when deleting a virtual disk.
If there is a VM guest that meets the condition in 2., delete it from the VM management console.
For details on how to delete VM guests, refer to the server virtualization software manual. (*2)
*2: When server virtualization software is VMware, select "Delete from Disk", when deleting VM guests.
Check if the VM management software can communicate with the manager. Select the VM management software in the server resource tree of the ROR console, and check if the status displayed on the main panel is "normal".
After confirming from the server tree or orchestration tree on the ROR console that the VM guest that was checked in 1. does not exist, create or start the L-Server again.
When Creation of an L-Server Takes a Long Time, or L-Server Creation Fails and "Message number 67390" is Displayed.
[Description]
Due to hardware failure, L-Server creation may take an excessive amount of time.
When it does take a long time, the following message is output and L-Server creation may fail.
FJSVrcx:ERROR:67390:creating VM guest failed. detail=timeout occurred |
For details on the message, refer to "Message number 67390".
[Corrective Action]
There is a possibility that the hardware of the server used for L-Server creation has failed.
Check the following:
When the server used to create the L-Server is a blade server, if failure of the Fibre Channel switch blade has occurred
When the server used to create the L-Server is a blade server, if failure of the LAN switch blade has occurred
When hardware failure has occurred, update the hardware information held by the server virtualization software.
For details on how to update hardware information, refer to the server virtualization software manual.
When Starting an L-Server, "Message number 67320" is Displayed, and Starting of the L-Server Fails.
[Description]
When starting the L-Server, the following message is displayed, and starting of the L-Server may fail.
|
The following causes are possible:
Migration has been performed on VMware.
VMware DRS has been enabled.
VMware DPM has been enabled and a VM host in standby mode exists in the same cluster as the target VM host of L-Server creation.
For details on the message, refer to "Message number 67320".
[Corrective Action]
For a. and b:
In the ROR console orchestration tree, right-click the target L-Server, and select [Update] from the popup menu. Check if the resource status of the updated L-Server is normal.
For c:
Start the L-Server from VM management software.
When a Physical L-Server is Created or Started, "Message number 61162" is Displayed, then Creation or Startup of the L-Server Fails.
[Description]
When a physical L-Server for which "Resource release" has been set in the [Server] tab of the [Create an L-Server] dialog or of the [Modify an L-Server] dialog is created or started, the following message may be displayed and the operation fails.
FJSVrcx:ERROR:61162:resource state(s) differ from actual state(s) in VIOM. |
[Corrective Action]
A VIOM server profile may remain.
To recover from the error, manually delete the VIOM server profile.
The name of the server profile is given as "L-Server name_admin ID".
Check the relevant server profile, delete the VIOM profile, and then restart the physical L-Server.
When an L-Server is Created or Started, "Message number 62511" is Displayed, then Creation or Startup of the L-Server Fails.
[Description]
When creating or starting the L-Server, the following message is displayed, and creation or startup of the L-Server may fail.
When using ETERNUS DX80 S2, ETERNUS DX90 S2, or ETERNUS DX400 S2 series storage
FJSVrcx:ERROR:62511:failed to control obj. IF=%1,message="ERROR:ssmgr3514:The specified value has already been registered." |
When using storage other than ETERNUS DX80 S2, ETERNUS DX90 S2, or ETERNUS DX400 S2 series
FJSVrcx:ERROR:62511:failed to control obj. IF=%1,message="ERROR:ssmgr3419:The specified alias name has already been registered." |
In obj, the resource name of the storage management software is displayed.
In %1, the internal function name is displayed.
Creation or startup of the L-Server failed because the alias name of the affinity group has already been defined when ETERNUS storage was created.
[Corrective Action]
Using the following procedure, identify the overlapping affinity group, delete the unnecessary affinity group or the unnecessary affinity group and the Volume defined in the unnecessary affinity group, and then create the L-Server again.
Check the resource name of the unused address set resource (WWN) with the smallest number.
Execute the following command:
>Installation_folder\Manager\bin\rcxadm addrset show -name Resource_name_of_the_Address_Set_Resource(WWN) <RETURN> |
Identify the unused address set resource (WWN) with the smallest number.
The range of the "start" and "end" inside the AddressSet tag becomes the range of the Address set resource (WWN).
In the range of address set resources (WWN), all addresses other than those below are considered unused address set resources (WWN).
Addresses which are not used for management by Resource Orchestrator, and are displayed in the Exclude tag
Addresses which have been allocated, and are displayed in the Reserve tag
From the unused address set resources, identify the one with the smallest number.
Example
When the output result is the one below, the resource name of the unused address set resource (WWN) with the smallest number will be "20:01:00:17:42:50:00:02".
<?xml version="1.0" encoding="utf-8"?>
<AddressSet name="wwndata1" id="540" label="wwn1" subnet="" mask="" start="20:01:00:17:42:50:00:00" end="20:01:00:17:42:50:00:0f">
<Comment>wwn-test-data-1</Comment>
<Exclude>
20:01:00:17:42:50:00:00
</Exclude>
<Reserve>
20:01:00:17:42:50:12:01 AM
</Reserve>
</AddressSet> |
Identify the alias name of the affinity group created when creating ETERNUS storage during L-Server creation.
Extract the characters corresponding to "XX" below from the resource name of the unused address set resource (WWN) with the smallest number. These characters become the alias name of the affinity group created when creating ETERNUS storage.
"YY:XX:YY:YY:YY:XX:XX:XX" |
Example
For "20:01:00:17:42:50:00:02" it would be "01500002".
Identify the affinity group to delete.
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 if the alias name of the affinity group identified in 2. is included in the affinity group alias names displayed in "NAME".
If the alias name is included
The relevant affinity group will be the target of deletion.
If the alias name is not included
Collect troubleshooting data, and then contact Fujitsu technical staff.
Check the affinity group number that is displayed for "NUMBER" of the relevant affinity group.
Check if the HBA to use the affinity group exists.
Executing the following command displays the affinity group number, which is used from the host and from the WWPN of the HBA that uses ETERNUS.
>ESC_manager_installation_folder\Manager\opt\FJSVssmgr\sbin\storageadm zone info -hex <RETURN> |
The lines after the output result of "<<< FC CA Zone Information >>>", the affinity group numbers that are used from the VM host and from the WWPN of the HBA that uses ETERNUS are collectively displayed for each storage unit.
For the target ETERNUS, check if the affinity group number identified in step 3. is included.
There may be multiple relevant lines.
If an affinity group number is not contained
There is an HBA which uses the relevant affinity group number.
When access to ETERNUS from the VM host using the relevant HBA is not necessary
Check the WWPN of the CA that is displayed for "CA_WWPN" and the WWPN of the HBA that is displayed for "HBA_WWPN", then execute the following procedure.
When access to ETERNUS from the VM host using the relevant HBA is necessary
Collect troubleshooting data, and then contact Fujitsu technical staff.
If an affinity group number is not contained
Execute step 6.
Delete the definition of the HBA that uses the affinity group number.
Executing the following command deletes all definitions of HBAs that were checked in step 4.
>ESC_manager_installation_folder\Manager\opt\FJSVssmgr\sbin\storageadm zone delete -storage CA_WWPN,Affinity_group_number -hba HHBA_WWPN -update all <RETURN> |
Identify the volume to delete.
Execute the following command to display the volume numbers of each Volume defined in the affinity group identified in step 3.
>ESC_manager_installation_folder\Manager\opt\FJSVssmgr\sbin\storageadm affinity info -ipaddr ETERNUS_IP_address -affinitygroup Affinity_group_number <RETURN> |
The Volume with the volume number matching that displayed in "VOLUME" becomes the target of deletion.
Delete the affinity group.
Execute the following command to delete the affinity group identified in step 3.
>ESC_manager_installation_folder\Manager\opt\FJSVssmgr\sbin\storageadm affinity delete -ipaddr ETERNUS_IP_address -affinitygroup Affinity_group_number <RETURN> |
Decide whether the Volume should be deleted.
Do not delete the Volume when the volume number identified in step 6. corresponds to the LUN created in advance.
The LUN created in advance can be checked by the following method.
Execute the following command: Check that the IP address of ETERNUS is displayed for "UNIT_NAME", and examine the line where "VOLUME_ID" contains the volume number confirmed in step 6.
>Installation_folder\Manager\bin\rcxadm disk list -verbose <RETURN> |
When "Yes" is displayed for "PRE_CREATED" in the relevant line
It is not necessary to delete the Volume, as the Volume is the LUN created in advance.
When "No" is displayed for "PRE_CREATED" in the relevant line
It is necessary to delete the Volume, as the Volume is not the LUN created in advance. Proceed to the following procedure.
Delete the Volume.
Execute the following command to delete the Volume identified in step 6.
>ESC_manager_installation_folder\Manager\opt\FJSVssmgr\sbin\storageadm volume delete -ipaddr ETERNUS_IP_address -volume Volume_number[,Volume_number,...] <RETURN> |
When any other message is displayed from the storage management software, refer to the manual of the storage management software, take the necessary corrective action for the message, and then perform the operation again.
When Creating an L-Server using a Specific Type of Image, Login is Impossible when using VMs which use Japanese Keyboard Environments.
[Description]
When creating an L-Server using images with the following OS types, login to VMs using Japanese keyboard environments may fail.
Windows Server 2008
Windows 7
Windows Vista
[Corrective Action]
Log in to a VM guest using a software keyboard, by opening "Regional and Language Options" on the Control Panel, and set the appropriate language.
Creation of an L-Server for Windows Using VMware Fails, and "Message number 67390" is Displayed.
[Description]
When creating an L-Server specifying an image for Windows using VMware, the following message is displayed, and creation of the L-Server may fail.
FJSVrcx:ERROR:67390:creating VM guest failed. detail= (customize VM guest name:task result error,vmerrno=104,ip=IP address) |
The following causes are possible:
Sysprep is not located on VMware vCenter Server.
If the OS type for the VM guest is Windows, installation of Sysprep is required.
The Sysprep located on VMware vCenter Server is incorrect.
The correct Sysprep file, decided according to the OS version for the VM guest (Windows 2000, Windows XP, and Windows 2003) and the CPU architecture (x86 and x64) is necessary.
When using Windows Server 2008, Sysprep is not required because it is set up in the OS. For details on the message, refer to "Message number 67390".
[Corrective Action]
Perform the following corrective actions:
For a.:
Locate Sysprep on VMware vCenter Server.
For b.:
Confirm the OS version for the VM guest and CPU architecture, and locate Sysprep on VMware vCenter Server.
For details on the location for Sysprep, refer to the description for the Microsoft Sysprep tool in the "vSphere Virtual Machine Administration Guide" manual released by VMware, Inc.
Refer to the relevant version of document, referring to the following URL:
URL: http://www.vmware.com/support/pubs/vs_pubs.html (As of February 2012) |
When Creating a Physical L-Server, Configuration of the Network Information Fails.
[Description]
During physical L-Server creation, if the following message is output, configuration of the network information has failed.
FJSVrcx:ERROR:67192:communication error.target=target |
[Corrective Action]
When configuration of the network information fails, the physical L-Server cannot be deleted.
Perform the corrective action according to "Corrective Action" for the message.
Then configure the network information using the following method.
Configure the network environment
Execute the rcxadm lserver setup command to send the network information to an L-Server.
For details on the command, refer to "1.3.1 rcxadm lserver".
When Opening the Physical L-Server Console Screen, the iRMC Management Window may be Opened.
[Description]
When right-clicking the target physical L-Server in the orchestration tree, and selecting [Console Screen] from the popup menu, the L-Server console screen is opened. After this is done once, this operation may open the iRMC management window instead of the physical L-Server console screen.
In this case, the following message is displayed on the iRMC management window.
Login required to continue. |
[Corrective Action]
Perform the following corrective actions:
Close the displayed iRMC management window.
Then open the physical L-Server console screen again from the ROR console.
Cannot Communicate Outside of the Chassis after Creating the L-Server.
[Description]
If the switch blade is being used is in end host mode, then there may have been a pin-group other than the default pin-group created.
[Corrective Action]
Delete all but the default pin-group.
When Creating or Turning on an L-Server, "Message number 67295" or "Message number 67210" may be Displayed even Though the Operation is Successfully Completed.
[Description]
If the manager is overloaded, one of the following error messages may be displayed when operations like creating an L-Server are performed.
FJSVrcx:ERROR:67295:L-Server name:duplicate resource name found
FJSVrcx:ERROR:67210:L-Server name is busy
When the above message is displayed, the corresponding operation may be still be being performed. Check the progress of the operation in Recent Operations or the Event Log.
[Corrective Action]
Check the following:
The hardware configuration of the admin server does not meet the requirements for a manager.
Refer to "1.5 Hardware Environment" in the "Setup Guide CE" and confirm that the hardware conditions described are met.
The CPU utilization of the admin server may be too high.
Check if any high CPU usage applications are running on the admin server.
When Creating or Starting a Physical L-Server Using Physical Server Usage Change, the Update of VIOM Configuration Information in Recent Operations may be Displayed.
[Description]
It shows that VIOM profiles have been updated on a different physical L-Server from before, based on the usage change of physical L-Servers.
That is not the problem as only VIOM profiles are updated. The information may be displayed multiple times, depending on the timing.
[Corrective Action]
No action is necessary.
