This section explains the 682XX message series.
Description
Writing to the Resource Orchestrator file filename failed.
Corrective Action
Check the system log, resolve the problem, and execute the command again.
If an error message regarding the disk or file system has been output
If a message indicating file system quota limit or insufficient space has been output
Description
The file or directory obj cannot be created.
Corrective Action
Check the access authority for the directory.
Description
Renaming of the Resource Orchestrator file filename failed.
Corrective Action
Check the system log, resolve the problem, and execute the command again.
If an error message regarding the disk or file system has been output
If a message indicating file system quota limit or insufficient space has been output
Description
Deletion of the Resource Orchestrator file filename failed.
Corrective Action
Check the system log, resolve the problem, and execute the command again.
If an error message regarding the disk or file system has been output
Description
Execution of the request during image operation failed.
Corrective Action
Check that the image file storage folder has not been located somewhere other than a network drive or a shared folder on the admin server. If the folder is not on the admin server, change the folder to one that is on the admin server.
Description
The resource could not be accessed as it is locked.
Corrective Action
The resource may not have been able to be accessed due to a high load on the admin server. Perform the operation again after completing any other high-load processes.
Description
The power status could not be obtained from physical_server.
Corrective Action
Check the following items in order, resolve the cause of the problem, and perform the operation again.
Whether communication with the server management unit is possible
Network cable checks
How to Check
Check if the network cable between the admin server and the server management unit is correctly connected.
Corrective Action
If the network cable is damaged
Replace the cable.
If the network cable is connected incorrectly
Reconnect the cable.
Check the power status of a chassis
How to Check
Check if the chassis is powered on.
Corrective Action
Power on the chassis.
For how to check the power status and power on a chassis, refer to the manual of the server being used.
Check the settings of network devices (e.g. LAN switch) being used
How to Check
Check that the duplex mode configurations of the admin LAN composed of the following admin server and managed servers are correct.
Between the NIC of the admin server and the switch port
Between the NIC of the server management unit and the switch port
Corrective Action
If the settings used for duplex mode configuration are incorrect, correct them.
For checks and setup of the admin LAN between the admin server and the server management unit, refer to the manuals of the OS and network switches being used.
Check the Network Environment
How to Check
Execute the ping command on the server where a manager is installed to check the network status.
Check if communication with the server management unit is possible.
[Windows Manager]
>ping the_IP_address_of_the_server_management_unit <RETURN> |
<Example: Normal communication>
Pinging ipaddr with 32 bytes of data: |
<Example: Abnormal communication>
Pinging ipaddr with 32 bytes of data: |
[Linux Manager]
# ping the_IP_address_of_the_server_management_unit <RETURN> |
<Example: Normal communication>
PING host name (ipaddr) 56(84) bytes of data. |
<Example: Abnormal communication>
PING host name (ipaddr) 56(84) bytes of data. |
Corrective Action
Check the following items:
For <Example: Normal communication>
"Port number checks"
For <Example: Abnormal communication>
"Network cable checks"
Port number checks
How to Check
Refer to "Appendix A Port List" in the "Design Guide VE", and check the port numbers of the admin server based on the following.
If port numbers are set
If the same port number or service name is being used
Corrective Action
Change the port number to the proper number.
For how to change port numbers, refer to "8.2 Changing Port Numbers" or "9.1.6 Changing Port Numbers" in the "User's Guide VE".
Check the load on the network of the admin LAN
How to Check
Check the network load of the admin LAN.
The load may be high when image operations (such as backup and restoration of system images, or collection and deployment of cloning images) are being performed for other managed servers connected to the same admin LAN as the server management unit.
Corrective Action
After the process that is causing the high network load finishes, perform the operation again.
If the BIOS/firmware of the managed server is the newest
The BIOS/firmware of the managed server may not be the newest.
Contact Fujitsu technical staff to obtain the newest BIOS/firmware for the managed server.
If the load of the admin server is high
Obtaining the power status may fail due to an increase in the load of the admin server. After completing any other high-load processes other than those of Resource Orchestrator, perform the operation again.
Description
Execution of operation failed on physical_server.
Corrective Action
Check the corrective action of "Message number 68232". If it does not apply, check that Write (reference and updating) authority is possessed for the SNMP setting of the management blade.
Check the SNMP community name set from the ROR console.
Check that the management blade of the managed server has Write (reference and updating) authority for the SNMP community name specified.
If the SNMP community name does not have Write (reference and updating) authority, change the authority settings.
Description
There is not enough disk space available on the manager.
Corrective Action
There is insufficient free disk space in the image file storage folder.
Delete any unnecessary files from the partition containing the image file storage folder.
After resolving the problem, perform the operation again following step 4. of "Message number 68295".
Description
There was no response from physical_server during process on disk.
Corrective Action
Check the following:
If an admin LAN network cable is connected
If an error message is being displayed on the managed server
When using HBA address rename, check the console of the managed server.
When an error is output on the console of the managed server, take the corrective action for "Message number 61308".
If an ephemeral port number is conflicting
Check that the port number used for backup and restoration of system images or for collection and deployment of cloning images is not that of an ephemeral port. If the port number is conflicting, change the port number to one that does not conflict. For details, refer to the following:
For Virtual Edition, "2.1.1.4 Checking Used Port Numbers" in the "Setup Guide VE".
For Cloud Edition, "2.1.1.4 Checking Used Port Numbers" in the "Setup Guide CE".
If the duplicate IP address of the managed server where the error occurred exists on the admin LAN network
When the IP address is duplicated, the managed server cannot communicate successfully. Change the IP address to avoid duplication.
If both the primary server and the spare server have been started
When the server switchover method uses backup and restore, both the primary server and the spare server may have been started. In such cases, the processing of the duplicated IP address will fail. Power off the spare server.
If both the DHCP server and the PXE server on the admin LAN have been started
If both the DHCP server and the PXE server on the admin LAN have been started, stop them.
When ServerView Deployment Manager is on the same server in the same subnet, it is necessary to uninstall the "Related services".
For details of the procedure, refer to the following:
For Virtual Edition, "5.1 deployment_service_uninstall" in the "Reference Guide (Command) VE".
For Cloud Edition, "5.1 deployment_service_uninstall" in the "Reference Guide (Command/XML) CE".
If the load of the admin server is high
Communication during the image operation may have failed because the load of the admin server is high. After completing any other high-load processes other than those of Resource Orchestrator, perform the operation again.
If the load of the admin LAN network is high
Communication during the image operation may have failed because the load of the admin LAN network is high. After completing any other high-load processes other than those of Resource Orchestrator, perform the operation again.
If Watchdog has been enabled on the managed server
There is a chance that Watchdog (a function that automatically resets or powers off a server after detecting a hang-up due to no response from the OS for a set period of time) has been enabled on the managed server.
Check the Watchdog settings on the managed server, and disable them if they have been enabled.
If switching of the NIC used by the admin server for the admin LAN has occurred
If redundancy has been performed for the admin LAN of the admin server, check if switching has occurred.
After resolving the problem, perform the operation again following step 4. of "Message number 68295".
Description
Establishment of a connection to physical_server in order to perform process from the disk failed.
Corrective Action
If another 6825X series message is displayed for the same server on which this message is displayed, refer to the corrective action for that message.
Check the corrective actions of "Message number 68251" and "Message number 68259".
If they do not apply, check the following:
If the settings configured for the system BIOS boot sequence are correct
Check the settings of the system BIOS booting sequence. If the settings are incorrect, perform them again.
If reconfiguration of hardware properties was performed after the server was switched
After checking using the following procedure, resolve the problem:
Use the UI of the server management unit (In the case of the PRIMERGY BX series use the Web UI of the management blade) to check the MAC address of the managed server.
Check the admin LAN (the MAC address) on the details of the managed server resources from the ROR console.
When the checked MAC addresses both differ, refer to the following, and reconfigure the hardware properties.
For Virtual Edition, refer to "6.2.2 Reconfiguration of Hardware Properties" and "6.3.1 Reconfiguration of Hardware Properties" in the "Operation Guide VE".
For Cloud Edition, refer to "9.2.2 Reconfiguration of Hardware Properties" and "9.3.1 Reconfiguration of Hardware Properties" in the "Operation Guide CE".
If the admin LAN NIC was switched to the standby NIC
When redundancy has been performed for the admin LAN, log in to the managed server and check if admin LAN NIC was switched to the standby NIC.
If it has been switched, take the following corrective actions.
When the operating NIC has failed
For Virtual Edition, perform "Replacing and Adding Network Interfaces (Admin LAN, Public LAN)" in "6.3.3 Replacing and Adding Server Components" in the "Operation Guide VE".
For Cloud Edition, perform "Replacing and Adding Network Interfaces (Admin LAN, Public LAN)" in "9.3.3 Replacing and Adding Server Components" in the "Operation Guide CE".
When the operating NIC has not failed
After resolving the cause of the switching to the standby NIC, switch back to the active NIC.
If the correct MAC address was specified for registration
For managed servers other than PRIMERGY BX series servers, check that the admin LAN MAC address set during managed server registration is correct. If the setting is incorrect, reconfigure the hardware properties.
The MAC address can be checked in the resource details of the physical server.
For how to check, refer to "A.6 Resource Details" in the "User's Guide VE".
If the correct Microsoft LAN Manager Module was specified during manager installation
Check that the correct Microsoft LAN Manager Module has been stored in the following folder.
[Windows Manager]
Installation_folder\SVROR\ScwPro\tftp\agent\dos\boot
[Linux Manager]
/var/opt/FJSVscw-tftpsv/tftproot/scw/agent/dos/boot/
For the Microsoft LAN Manager Module, refer to "Microsoft LAN Manager Module" in "2.1.1.1 Software Preparation and Checks" in the "Setup Guide VE" or "Setup Guide CE".
If the Microsoft LAN Manager Module is not correct, stop the manager referring to "2.1 Starting and Stopping the Manager" in the "Operation Guide VE" or "Operation Guide CE". and replace the Microsoft LAN Manager Module.
After that, restart the manager.
If the port number settings are correct
Refer to "Appendix A Port List" in the "Design Guide VE" or "Design Guide CE", and check the port numbers of the admin server based on the following.
If port numbers are set
If the same port number or service name is being used
If the port number is incorrect, change the port number to the proper number.
For how to change port numbers, refer to the following:
For Virtual Edition, refer to "8.2 Changing Port Numbers" or "9.1.6 Changing Port Numbers" in the "User's Guide VE".
For Cloud Edition, refer to "6.2 Changing Port Numbers" or "7.1.6 Changing Port Numbers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If there is a problem with the firewall settings
Check that there are no problems in the firewall settings for the admin server and the managed servers.
If there is a problem, change the firewall settings.
If Watchdog has been enabled on the managed server
There is a chance that Watchdog (a function that automatically resets or powers off a server after detecting a hang-up due to no response from the OS for a set period of time) has been enabled on the managed server.
Check the Watchdog settings on the managed server, and disable them if they have been enabled.
If switching of the NIC used by the admin server for the admin LAN has occurred
If redundancy has been performed for the admin LAN of the admin server, check if switching has occurred.
If DHCP relay agent configuration has been performed on the router
If the subnets for the admin server and the managed server are different, check if DHCP relay agent configuration has been performed on the router.
For details, refer to the following:
For Virtual Edition, "7.6 Configuring the Network Environment" in the "Design Guide VE".
For Cloud Edition, "9.2.4 Settings for Unmanaged Network Devices" in the "Design Guide CE".
If multicast routing settings are configured on the router
If the subnets of the admin server and the managed server are different, check if multicast routing configuration has been performed on the router.
For details, refer to the following:
For Virtual Edition, "7.6 Configuring the Network Environment" in the "Design Guide VE".
For Cloud Edition, "9.2.4 Settings for Unmanaged Network Devices" in the "Design Guide CE".
After resolving the problem, perform the operation again following step 4. of "Message number 68295".
Description
process timed out during image operation.
Corrective Action
Check the following:
When process is reboot, check the corrective action for "Message number 68257".
If the settings configured for the system BIOS boot sequence are correct
Check the settings of the system BIOS booting sequence. If the settings are incorrect, perform them again.
If an error message is being displayed on the managed server
When using HBA address rename, check the console of the managed server.
When an error is output on the console of the managed server, take the corrective action for "Message number 61308".
If the duplicate IP address of the managed server where the error occurred exists on the admin LAN network
When the IP address is duplicated, the managed server cannot communicate successfully. Change the IP address to avoid duplication.
If both the primary server and the spare server have been started
When the server switchover method uses backup and restore, both the primary server and the spare server may have been started. In such cases, the processing of the duplicated IP address will fail. Power off the spare server.
If both the DHCP server and the PXE server on the admin LAN have been started
If both the DHCP server and the PXE server on the admin LAN have been started, stop them.
When ServerView Deployment Manager is on the same server in the same subnet, it is necessary to uninstall the "Related services".
For details of the procedure, refer to "5.1 deployment_service_uninstall" in the "Reference Guide (Command) VE".
If the load of the admin server is high
Communication during the image operation may have failed because the load of the admin server is high. After completing any other high-load processes other than those of Resource Orchestrator, perform the operation again.
If the load of the admin LAN network is high
Communication during the image operation may have failed because the load of the admin LAN network is high. After completing any other high-load processes other than those of Resource Orchestrator, perform the operation again.
If the correct Microsoft LAN Manager Module was specified during manager installation
Check that the correct Microsoft LAN Manager Module has been stored in the following folder.
[Windows Manager]
Installation_folder\SVROR\ScwPro\tftp\agent\dos\boot
[Linux Manager]
/var/opt/FJSVscw-tftpsv/tftproot/scw/agent/dos/boot/
For the Microsoft LAN Manager Module, refer to "Microsoft LAN Manager Module" in "2.1.1.1 Software Preparation and Checks" in the "Setup Guide VE" or "Setup Guide CE".
If the Microsoft LAN Manager Module is not correct, stop the manager referring to "2.1 Starting and Stopping the Manager" in the "Operation Guide VE" or "Operation Guide CE". and replace the Microsoft LAN Manager Module.
After that, restart the manager.
If the port number settings are correct
Refer to "Appendix A Port List" in the "Design Guide VE" or "Design Guide CE", and check the port numbers of the admin server based on the following.
If port numbers are set
If the same port number or service name is being used
If the port number is incorrect, change the port number to the proper number.
For how to change port numbers, refer to the following:
For Virtual Edition, refer to "8.2 Changing Port Numbers" or "9.1.6 Changing Port Numbers" in the "User's Guide VE".
For Cloud Edition, refer to "6.2 Changing Port Numbers" or "7.1.6 Changing Port Numbers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If there is a problem with the firewall settings
Check that there are no problems in the firewall settings for the admin server and the managed servers.
If there is a problem, change the firewall settings.
If Watchdog has been enabled on the managed server
There is a chance that Watchdog (a function that automatically resets or powers off a server after detecting a hang-up due to no response from the OS for a set period of time) has been enabled on the managed server.
Check the Watchdog settings on the managed server, and disable them if they have been enabled.
If there is a mistake in the SNMP agent settings of the management blade
Check if there is a mistake in the SNMP agent settings of the management blade.
For how to perform settings, refer to the following:
For Virtual Edition, "6.2 Configure the Server Environment" in the "Design Guide VE".
For Cloud Edition, "8.2 Configure the Server Environment" in the "Design Guide CE".
If failover has occurred
When operating managers in clusters, check if failover has occurred.
If the correct MAC address was specified during server registration
In an environment with a redundant admin LAN, for managed servers other than PRIMERGY BX series servers, check that the admin LAN MAC address set during managed server registration is correct. If there is an error in the settings, reconfigure the hardware information and specify the correct MAC address.
The MAC address can be checked in the resource details of the physical server.
For how to check, refer to the following:
For Virtual Edition, refer to "A.6 [Resource Details] Tab" in the "User's Guide VE".
For Cloud Edition, refer to "A.6 [Resource Details] Tab" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
For reconfiguration of hardware properties, refer to the following:
For Virtual Edition, refer to "6.2.2 Reconfiguration of Hardware Properties" and "6.3.1 Reconfiguration of Hardware Properties" in the "Operation Guide VE".
For Cloud Edition, refer to "9.2.2 Reconfiguration of Hardware Properties" and "9.3.1 Reconfiguration of Hardware Properties" in the "Operation Guide CE".
If the LAN switch has been registered
If the subnets for the primary server and spare server are different, check if the LAN switch blades connecting to each server have been registered.
If the network settings can be changed for switchover
If the subnets for the primary server and spare server are different, check if the network settings have been configured to change during switchover.
When the settings have not been configured, configure them referring to "18.2 Server Switchover Settings" in the "User's Guide VE".
After resolving the problem, perform the operation again following step 4. of "Message number 68295".
Description
The disk process failed.
Corrective Action
If another 6825X series message is displayed for the same server on which this message is displayed, refer to the corrective action for that message.
Check the following:
There is no problem with disk access on the admin server
Check if an error message regarding the disk or file system has been output to the system log of the admin server.
If the managed server and the admin server can communicate
Check that communication between the managed server and the admin server is available using ping or telnet.
Based on the value of process check the following:
When process is "read"
That the file system is not damaged
Check that the file system of the managed server has not been damaged.
[Windows]
Check using a tool such as chkdsk. If there are any errors, recover them.
[Linux]
Check if the following message is displayed on the console when the managed server is started.
"A "dirty shutdown" may have occurred. "Press Y to perform a filesystem check". If this message is displayed, enter "Y" within five seconds and perform "filesystem check".
If the previous shutdown finished normally
Check if the previous shutdown finished normally.
If it did not finish normally, restart the managed server.
[Linux]
Restart using the following command:
# /sbin/shutdown -F -r now <RETURN> |
When process is "write"
Does the disk of the managed server that is the target of deployment or restoration have sufficient space available
When the disk size of the destination for deployment of a cloning image is smaller than that of the boot disk used for the managed server from which the cloning image was collected, check that the size of the boot disk of the managed server to be added is the same or larger than that of the managed server from which the cloning image was collected.
Can the disk be accessed
Check the BIOS settings of the managed server and confirm that the disk is accessible.
For managed server BIOS settings, refer to the following:
For Virtual Edition, refer to "6.2.7 BIOS Settings of Managed Servers" in the "Design Guide VE".
For Cloud Edition, refer to "8.2.7 BIOS Settings of Managed Servers" in the "Design Guide CE".
If the managed server uses SAN boot check the setting of the SAN devices.
If Watchdog has been enabled on the managed server
There is a chance that Watchdog (a function that automatically resets or powers off a server after detecting a hang-up due to no response from the OS for a set period of time) has been enabled on the managed server.
Check the Watchdog settings on the managed server, and disable them if they have been enabled.
After resolving the problem, perform the operation again following step 4. of "Message number 68295".
Description
An error was detected in the settings of the server.
Corrective Action
Check the following:
If there are any unnecessary files remaining on the managed server
When network settings of a managed server are changed after collection of a cloning image fails, there is a chance that some unnecessary files may remain. Check if any of the following files remain on the managed server. If they are still on the managed server, delete them and check the network settings.
[Windows]
Installation_folder\Agent\var\tmp\ipcfg.nsh
Installation_folder\Agent\var\tmp\ipcfg_now.nsh
[Linux]
/var/opt/FJSVrcxat/tmp/softrm/ifcfg-ethX file (the X of ethX can be any desired letter)
The folder specified in Choose Destination Location of "2.2.2 Installation [Windows] [Hyper-V]" in the "Setup Guide VE".
Does the netsh command operate normally
[Windows]
If collection of a cloning image failed, check the following.
The fixed IP has been changed to DHCP during collection of the cloning image. If the network settings have been changed, return them to those before collection of the cloning image.
Check if any of the following files remain on the managed server. If they do remain, delete the files.
Installation_folder\Agent\var\tmp\ipcfg.nsh
Installation_folder\Agent\var\tmp\ipcfg_now.nsh
Execute the following command and check the return value.
>netsh interface ip set address Interface_name dhcp <RETURN> |
If the return value is something other than 0, remove the cause of the problem.
Return the network settings to those before collection of the cloning image.
Check the storage configuration of the managed server.
You may have attempted to backup or collect a system image from an unsupported storage configuration. Confirm the supported storage configuration. For details, refer to "Chapter 8 Defining and Configuring the Storage Environment" in the "Design Guide VE".
There is a mistake in the method for collecting an image from the managed server.
Refer to the advance preparation of "17.2 Collecting" of "User's Guide VE"
After resolving the problem, perform the operation again following step 4. of "Message number 68295".
Description
An unexpected reboot occurred during the cloning process.
Corrective Action
Check the following:
If operations that affect power control status are being executed simultaneously on the failed managed server
If they were being executed simultaneously, wait until the operations finish.
If Watchdog has been enabled on the managed server
There is a chance that Watchdog (a function that automatically resets or powers off a server after detecting a hang-up due to no response from the OS for a set period of time) has been enabled on the managed server.
Check the Watchdog settings on the managed server, and disable them if they have been enabled.
If failover has occurred
When operating managers in clusters, check if failover has occurred.
After resolving the problem, perform the operation again following step 4. of "Message number 68295".
Description
A timeout was detected during setting of the server.
Corrective Action
Check the corrective actions of "Message number 68251" and "Message number 68259".
If they do not apply, check the following:
If the settings of the image file operation module are correct
Resolve the problem referring to "4.2 Image Operation Issues [Physical Servers] [Hyper-V]" in "Troubleshooting".
If the managed server has been restarted after registration
When the agent was installed before registering the managed server and the managed server has not been rebooted since registration took place, reboot the server.
If NetBIOS is enabled
[Windows]
Execute the following command and check that the NetBIOS of the admin network interface is valid (the status where "NetBIOS over Tcpip. . . . . . . . : Disabled" is not displayed).
When NetBIOS is disabled, enable it according to the Windows manual.
>ipconfig /all <RETURN> |
If reconfiguration of hardware properties was performed after the server was switched
After checking using the following procedure, resolve the problem:
Use the UI of the server management unit (In the case of the PRIMERGY BX series use the Web UI of the management blade) to check the MAC address of the managed server.
Check the admin LAN (the MAC address) on the details of the managed server resources from the ROR console.
When the checked MAC addresses both differ, refer to the following and reconfigure the hardware properties.
For Virtual Edition, refer to "6.2.2 Reconfiguration of Hardware Properties" and "6.3.1 Reconfiguration of Hardware Properties" in the "Operation Guide VE".
For Cloud Edition, refer to "9.2.2 Reconfiguration of Hardware Properties" and "9.3.1 Reconfiguration of Hardware Properties" in the "Operation Guide CE".
If the admin LAN NIC was switched to the standby NIC
When redundancy has been performed for the admin LAN, log in to the managed server and check if admin LAN NIC was switched to the standby NIC.
If it has been switched, take the following corrective actions.
When the operating NIC has failed
For Virtual Edition, perform "Replacing and Adding Network Interfaces (Admin LAN, Public LAN)" in "6.3.3 Replacing and Adding Server Components" in the "Operation Guide VE".
For Cloud Edition, perform "Replacing and Adding Network Interfaces (Admin LAN, Public LAN)" in "9.3.3 Replacing and Adding Server Components" in the "Operation Guide CE".
When the operating NIC has not failed
After resolving the cause of the switching to the standby NIC, switch back to the active NIC.
If the correct MAC address was specified for registration
For managed servers other than PRIMERGY BX series servers, check that the admin LAN MAC address set during managed server registration is correct. If the setting is incorrect, reconfigure the hardware properties.
The MAC address can be checked in the resource details of the physical server.
For how to check, refer to "A.6 [Resource Details] Tab" in the "User's Guide VE" or " User's Guide for Infrastructure Administrators (Resource Management) CE".
If the network interface name is one of a consecutive sequence that starts from 0
[Linux]
Check that the numeral of the managed server's network interface name (ethX) is one of a consecutive sequence starting from 0.
If the sequence does not start from 0 or is not a consecutive sequence, change the network interface name.
If the settings of the public network interface are correct
[Linux]
Refer to the public network interface configuration file "/etc/sysconfig/network-scripts/ifcfg-ethX" (ethX is the interface name of eth0, eth1, etc.) and check that the setting is set as ONBOOT=no.
If the settings of the admin network interface are correct
[Linux]
Refer to the following network configuration file which is the admin network interface configuration file, and check that the values of IPADDR and NETMASK are set correctly.
Red Hat Enterprise Linux
/etc/sysconfig/network-scripts/ifcfg-ethX (ethX is the interface name of eth0, eth1, etc.)
SUSE Linux Enterprise Server
/etc/sysconfig/network/ifcfg-ethX (the X of ethX can be any desired letter)
If the port number settings are correct
Refer to "Appendix A Port List" in the "Design Guide VE" or "Design Guide CE", and check the port numbers of the admin server based on the following.
If port numbers are set
If the same port number or service name is being used
If the port number is incorrect, change the port number to the proper number.
For how to change port numbers, refer to the following:
For Virtual Edition, refer to "8.2 Changing Port Numbers" or "9.1.6 Changing Port Numbers" in the "User's Guide VE".
For Cloud Edition, refer to "6.2 Changing Port Numbers" or "7.1.6 Changing Port Numbers" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
If there is a problem with the firewall settings
Check that there are no problems in the firewall settings for the admin server and the managed servers.
If there is a problem, change the firewall settings.
If Watchdog has been enabled on the managed server
There is a chance that Watchdog (a function that automatically resets or powers off a server after detecting a hang-up due to no response from the OS for a set period of time) has been enabled on the managed server.
Check the Watchdog settings on the managed server, and disable them if they have been enabled.
If failover has occurred
When operating managers in clusters, check if failover has occurred.
After resolving the problem, perform the operation again following step 4. of "Message number 68295".
Description
Booting of physical_server during image operation failed.
Corrective Action
Check the following:
If the hardware configuration of the managed server is uniform
The hardware configuration of the managed server that the cloning image was collected from differs from that of the managed server it is being deployed to.
Check the hardware configuration of the managed server.
If the Windows product key is correct
Check the managed server that has failed to deploy. If it is has stopped at the screen for entry of the Windows key, the Windows product key is incorrect. Correct the license information file on the managed server the cloning image was collected from and collect a new cloning image.
For details, refer to the following:
For Virtual Edition, refer to "17.2 Collecting" in the "User's Guide VE".
For Cloud Edition, refer to "17.5.1 Collecting and Registering" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Cloning images which were not deployed successfully cannot be used.
If the managed server the cloning image was collected from was the domain controller
When Windows cloning images have been deployed, the managed server they were collected from may have been the domain controller. If the managed server images were collected from was the domain controller, release the settings and collect the cloning image again.
Cloning images which were not deployed successfully cannot be used.
If the settings of the license information file are correct
When Windows Server 2008 cloning images have been deployed, the setting details of the license information file may contain a mistake. Check the setting details of the license information file on the managed server the cloning image was collected from or deployed to.
If the setting details contain a mistake, correct the license information file on the managed server the cloning image was collected from and collect a new cloning image.
For details, refer to the following:
For Virtual Edition, refer to "17.2 Collecting" in the "User's Guide VE".
For Cloud Edition, refer to "17.5.1 Collecting and Registering" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Cloning images which were not deployed successfully cannot be used.
If the Sysprep.exe and Setupcl.exe files are correct
When a Windows Server 2003 cloning image has been deployed, there is a chance that incorrect files have been specified for Sysprep.exe and Setupcl.exe. Check that the Sysprep.exe and Setupcl.exe files in the following folder on the managed server the cloning image was collected from match the OS architecture. If they do not match, then reinstall the agent.
Installation_folder\scw\SeparateSetting\sysprep
If an error message is being displayed on the managed server
When using HBA address rename, check the console of the managed server.
When an error is output on the console of the managed server, take the corrective action for "Message number 61308".
If the managed server and the admin server can communicate
Check that communication between the managed server and the admin server is available using ping or telnet.
If the settings of the public network interface are correct
[Linux]
Refer to the public network interface configuration file "/etc/sysconfig/network-scripts/ifcfg-ethX" (ethX is the interface name of eth0, eth1, etc.) and check that the setting is set as ONBOOT=no.
If the settings of the admin network interface are correct
[Linux]
Refer to the following network configuration file which is the admin network interface configuration file, and check that the values of IPADDR and NETMASK are set correctly.
Red Hat Enterprise Linux
/etc/sysconfig/network-scripts/ifcfg-ethX (ethX is the interface name of eth0, eth1, etc.)
SUSE Linux Enterprise Server
/etc/sysconfig/network/ifcfg-ethX (the X of ethX can be any desired letter)
If there are any unnecessary files remaining on the managed server
When network settings of a managed server are changed after collection of a cloning image fails, there is a chance that some unnecessary files may remain. Check if any of the following files remain on the managed server. If they are still on the managed server, delete them and check the network settings.
[Windows]
Installation_folder\Agent\var\tmp\ipcfg.nsh
Installation_folder\Agent\var\tmp\ipcfg_now.nsh
[Linux]
/var/opt/FJSVrcxat/tmp/softrm/ifcfg-ethX file (the X of ethX can be any desired letter)
The folder specified in Choose Destination Location of "2.2.2 Installation [Windows] [Hyper-V]" in the "Setup Guide VE".
If there is a mistake in the network settings of the managed server the cloning image was collected from
Check that the value of the IP address for the NIC allocated to the admin LAN matches the one set in "7.3.2 Registering Blade Servers" or "7.4.1 Registering Rack Mount or Tower Servers" in the "User's Guide VE".
To check the values entered in "7.3.2 Registering Blade Servers" or "7.4.1 Registering Rack Mount or Tower Servers" in the "User's Guide VE", refer to "A.6 Resource Details" in the "User's Guide VE".
[Linux]
When using SUSE Linux Enterprise Server, check whether the settings given in "When using SUSE Linux Enterprise Server" in "2.2.1.1 Software Preparation and Checks" in the "Setup Guide VE" have been performed.
If Watchdog has been enabled on the managed server
There is a chance that Watchdog (a function that automatically resets or powers off a server after detecting a hang-up due to no response from the OS for a set period of time) has been enabled on the managed server.
Check the Watchdog settings on the managed server, and disable them if they have been enabled.
If Sysprep has been executed more than four times in total
When a Windows Server 2008 cloning image that uses MAK license authentication for its activation method is deployed, check if Sysprep has been executed more than four times in total.
If Sysprep has been executed more than four times in total, an error log may have been created with the following path.
Log file name:
Setupper.log
Path:
\Windows\System32\Sysprep\Panther
For details, refer to the following web site.
URL: http://support.microsoft.com/kb/929828 |
As Sysprep is executed when cloning images are deployed, it is not possible to collect and deploy cloning images more than three times.
When Sysprep has been executed four or more times, it is necessary to collect a new cloning image. Collect a cloning image from a managed server on which Sysprep has been executed twice or less, and deploy that cloning image.
Cloning images which were not deployed successfully cannot be used.
After resolving the problem, perform the operation again following step 4. of "Message number 68295".
If above items do not apply, check the following:
If the managed server configuration is in an iSCSI disk configuration
When the managed server operating on an iSCSI disk is Linux, cloning images cannot be collected.
If cloning has been performed, perform restoration of a system image and recover the environment.
[Virtual Edition]
Description
The process on disk was aborted.
Corrective Action
Check the following:
If the disk or storage device attached to the managed server is operating normally
If the RAID device attached to the managed server is operating normally
If the managed server is in a SAN boot environment, is there a problem with the wiring between the storage device and the managed server
If the managed server is in a SAN boot environment, is the fibre channel switch operating normally
If Watchdog has been enabled on the managed server
There is a chance that Watchdog (a function that automatically resets or powers off a server after detecting a hang-up due to no response from the OS for a set period of time) has been enabled on the managed server.
Check the Watchdog settings on the managed server, and disable them if they have been enabled.
After resolving the problem, perform the operation again following step 4. of "Message number 68295".
[Cloud Edition]
Description
The process on disk was aborted.
Corrective Action
Check the following:
If the disk or storage device attached to the managed server is operating normally
If the RAID device attached to the managed server is operating normally
If the managed server is in a SAN boot environment, is there a problem with the wiring between the storage device and the managed server
If the managed server is in a SAN boot environment, is the fibre channel switch operating normally
If Watchdog has been enabled on the managed server
There is a chance that Watchdog (a function that automatically resets or powers off a server after detecting a hang-up due to no response from the OS for a set period of time) has been enabled on the managed server.
Check the Watchdog settings on the managed server, and disable them if they have been enabled.
When a managed server is configured for iSCSI boot:
Check that there are no problems in the connection between the storage unit and the managed server.
After resolving the problem, perform the operation again following step 4. of "Message number 68295".
Description
An image operation was canceled.
Corrective Action
The manager service may have stopped.
Refer to "2.1 Starting and Stopping the Manager" in the "Operation Guide VE" or "Operation Guide CE", and restart the services.
After resolving the problem, perform the operation again following step 4. of "Message number 68295".
Description
Process timed out during cancellation processing of the image operation.
Corrective Action
Communication during the cancellation process for the image operation may have failed because the load of the admin server was high. After completing any other high-load processes other than those of Resource Orchestrator, perform the operation again.
Description
An error occurred during the process after cancellation of the image operation.
Corrective Action
Perform the following procedure if necessary to restore the target server.
When the backup was cancelled
If the managed server has been started
Restart the managed server.
If the managed server has been stopped
Power on the managed server.
When collection of cloning images was cancelled
Take the following corrective actions depending on the managed server's status:
If the managed server has been started
Restart the managed server.
If the managed server has been stopped
Power on the managed server.
Network settings may have been modified. In that case, return the network settings to those before collection of the cloning image, referring to the following file. For details on settings, refer to the manual for the OS.
[Windows]
Installation_folder\Agent\var\tmp\ipcfg.nsh
Installation_folder\Agent\var\tmp\ipcfg_now.nsh
[Linux]
/var/opt/FJSVrcxat/tmp/softrm/ifcfg-ethX
(ethX is the interface name, such as eth0, eth1, etc.)
Delete the file that you used in 2.
Configure automatic starting settings for the following agent services. For details on settings, refer to the manual for the OS.
[Windows]
Resource Coordinator Agent
[Linux]
SCruiserAgent
Start the agent. Refer to "2.2 Starting and Stopping the Agent" in the "Operation Guide VE" or "Operation Guide CE", and restart the services.
When restoration of system images or deployment of cloning images was canceled
If the managed server has been started, power it off.
Perform the operation that was cancelled again, or deploy another image.
When server switchover or failback was cancelled
If the managed server has been started, power it off.
[Cloud Edition]
Description
An error occurred during the process after cancellation of the image operation.
Corrective Action
Perform the following procedure if necessary to restore the target server.
When creation of a physical L-Server was canceled:
Power off the managed server if it is powered on.
When other operations were canceled:
Refer to the corrective action in "Message number 68262".
Description
An internal command error occurred during one of the following operations.
Backup or restoration of a system image
Collection or deployment of a cloning image
Server switchover using backup or restore
During cloning image deployment, if errors occur on some of the servers when deploying the same cloning image to multiple managed servers, deployment to the other servers is stopped.
Corrective Action
If another 6825X series message is displayed for the same server on which this message is displayed, refer to the corrective action for that message.
Check the following and take corrective action.
Check the settings
Check the redundancy of the admin LAN
When redundancy configuration has been performed for the admin LAN, take corrective action based on the following.
After removing the cause of the error, refer to step 4. and execute the failed operation again.
When a cloning image could not be collected
If the operating NIC of the managed server is not available due to use of the redundant admin LAN, cloning images cannot be collected.
Remove the cause of the switch to the standby NIC, switch from the standby NIC back to the operating NIC, and release the redundancy configuration of the admin LAN.
When a cloning image could not be deployed
Check if the cloning image has been deployed with the redundancy configuration of the admin LAN set.
Cloning images with the redundancy configuration of the admin LAN set cannot be deployed to managed servers other than the one from which the cloning image was collected.
Deploy a cloning image that does not have the redundancy configuration of the admin LAN set.
Check if the operating NIC is available.
Remove the cause of the switch to the standby NIC, switch from the standby NIC back to the operating NIC, release the redundancy configuration of the admin LAN, and then deploy the cloning image again.
Check the status of the admin server service
Services explained in "Related services" in "2.1 Starting and Stopping the Manager" in the "Operation Guide VE" or "Operation Guide CE" may have stopped.
Refer to "2.1 Starting and Stopping the Manager" in the "Operation Guide VE" or "Operation Guide CE", and restart the services.
After removing the cause of the error, refer to step 4. and execute the failed operation again.
Check Watchdog on the managed server
When the managed server has been powered off, there is a chance that Watchdog (a function that automatically resets or powers off a server after detecting a hang-up due to no response from the OS for a set period of time) has been enabled on the managed server.
Check the Watchdog settings on the managed server, and disable them if they have been enabled.
After removing the cause of the error, refer to step 4. and execute the failed operation again.
Check preparatory settings
Check that the settings given in "Configuration File Check" in "2.2.1.1 Software Preparation and Checks" in the "Setup Guide VE" or "Setup Guide VE" have been performed.
When using SUSE Linux Enterprise Server, check that the managed server has been configured so that only the NIC used for the admin LAN is active when the server is started.
If the settings have not been performed, perform them and then perform the operation again.
Error information collection
Check detail in the error message.
When "rid=request_ID" is displayed for detail, log in to the admin server using OS administrator authority and execute the following command using the request_ID.
[Windows Manager]
>cd "Installation_folder(*)\SVROR\ScwPro\support" <RETURN> |
[Linux Manager]
# cd /opt/FJSVscw-utils/sbin <RETURN> |
* Note: The folder specified in Choose Destination Location of "2.1.2 Installation [Windows Manager]" in the "Setup Guide VE".
Information
When the admin server is Windows 2003 x64 Edition or Windows 2008 x64 Edition, open the command prompt using the following procedure.
Select [start]-[Run], and execute the following.
"Installation_folder\SVROR\SysWoW64\cmd.exe" |
Installation_folder is the installation folder of Windows.
The error information will be output in HTML format. Use a Web browser to display the output file.
Cause determination and response
Refer to the output error information and perform the following corrective action.
If the "Troubleshoot" column is displayed
Take the corrective action indicated in the "Todo" of the "Troubleshoot" column.
If error log files are created
If the following is displayed in the "Todo" of the "Troubleshoot" column, check error codes and detailed codes referring to the content of the error log file (FJIMGBRS.ERR) stored in the "Error Logs Directory" of the "Detail Information" column.
Detail logs are stored in [Error_Logs_Directory]. |
Example
Abstract of error log files
Date : Tue Apr 25 19:48:33 2006 Error Data : 00130100 00000011 Error Code : 161 000a0805 Message : 0161 The size of the disk is small. Change the size of the partition. |
The first half of the Error Code line is the error code. In this case, the code is "161".
The second half of the Error Code line is the detailed code. In this case, the code is "000a0805".
Check the error code, and choose one of the following corrective actions:
When the error code is "199"
Cause
The managed server has not been shut down normally.
Corrective Action
Reboot the system and shut down the managed servers.
When the error code is something other than 199, collect troubleshooting information and contact Fujitsu technical staff.
If this does not resolve the problem, collect troubleshooting information and contact Fujitsu technical staff.
Recovery
When this does resolve the problem, perform the failed operation again using the following procedure.
When the same cloning image has been deployed to multiple managed servers, deployment to the other servers is stopped. When performing deployment again after performing corrective action, specify all of the servers again.
Booting the managed server
When a managed server on which an error occurred during backup of a system image or collection of a cloning image has been powered off, power it on.
If the managed server has been started, perform the following steps.
If the managed server has not been started, check if the following message is displayed on the screen.
If the message is displayed, press the [ESC] key.
If the message is not displayed, power off the server directly.
Error has occurred!! |
After pressing the [ESC] key, enter "Y" and power it off. After that, power it on again.
If the server does not power off when the [ESC] key is pressed, power off the server directly.
Would you like to turn off this computer? [Y/N] |
Starting agents of Resource Orchestrator
Only perform this operation when an error occurred during collection of cloning images.
During the collection of cloning images, the automatic starting of agents is stopped.
Restart the managed server where the error occurred, and then start the agent.
When starting an agent, refer to "2.2 Starting and Stopping the Agent" in the "Operation Guide VE" or "Operation Guide CE".
[Windows]
When the managed server is Windows, the type of agent startup may be changed to "Disabled". In such cases, use the following procedures to set the startup type to "Automatic", before starting the agent.
Open [Services] from [Administrative Tools] on the Control Panel.
The [Services] window will be displayed.
Right-click the "Resource Coordinator Agent" service and select [Properties] from the displayed menu.
The [Resource Coordinator Agent Properties] window will be displayed.
Select [Automatic] from the [Startup type] of the [General] tab.
Click <OK>.
Delete temporary files
If an error occurred during collection of a cloning image, and the network settings of the managed server have been changed after the error occurred, the following files might remain. If they do remain, delete them.
[Windows]
Installation_folder\Agent\var\tmp\ipcfg.nsh
Installation_folder\Agent\var\tmp\ipcfg_now.nsh
[Linux]
/var/opt/FJSVrcxat/tmp/softrm/ifcfg-ethX (the X of ethX can be any desired letter)
Re-execute
Execute the failed operation again.
[Virtual Edition]
Description
An error has occurred during execution of a manager command.
Corrective Action
When this message is displayed during the execution of the following operations, after resolving the problem based on the content of each detail, perform the operation again following step 4. of "Message number 68295".
When the same cloning image has been deployed to multiple managed servers, deployment to the other servers is stopped. When performing deployment again after performing corrective action, specify all of the servers again.
Backup of a system image
Restoration of a system image
Collection of a cloning image
Deployment of a cloning image
Auto-Recovery of a managed server for which server switchover uses the backup and restore method
Manual switchover or failback to a managed server for which server switchover uses the backup and restore method
When this message is displayed during the execution of operations other than the above, after resolving the problem based on the content of each detail, perform the operation again.
When "code=100"
One of the services in "Related services" of "2.1 Starting and Stopping the Manager" in the "Operation Guide VE" may have stopped on the admin server.
On the admin server, check that the "Related services" have been started, and if there are any services that have stopped, start them.
For how to check and start services, refer to "2.1 Starting and Stopping the Manager" in the "Operation Guide VE".
When starting the manager, communication using the admin LAN may not have been possible.
Check if communication with the agent is possible using the admin LAN, then stop and restart the manager.
For how to stop and start managers, refer to "2.1 Starting and Stopping the Manager" in the "Operation Guide VE".
When "code=107"
When the load of the admin server is high, the internal connection process of a manager may time out.
After completing any other high-load processes other than those of Resource Orchestrator, perform the operation again.
[Cloud Edition]
Description
When creating a physical L-Server:
Deployment of the cloning image failed. The backup/restore procedure for the admin server may have been performed incorrectly.
When not creating a physical L-Server:
An error has occurred during execution of a manager command.
Corrective Action
When creating a physical L-Server:
If a message not related to the above actions is output, collect the corresponding message and troubleshooting data, and contact Fujitsu technical staff.
When not creating a physical L-Server:
When this message is displayed during the execution of the following operations, after resolving the problem based on the content of each detail, perform the operation again following step 4. of "Message number 68295".
When the same cloning image has been deployed to multiple managed servers, deployment to the other servers is stopped. When performing deployment again after performing corrective action, specify all of the servers again.
Backup of a system image
Restoration of a system image
Collection of a cloning image
Deployment of a cloning image
Auto-Recovery of a managed server for which server switchover uses the backup and restore method
Manual switchover or failback to a managed server for which server switchover uses the backup and restore method
When this message is displayed during the execution of operations other than the above, after resolving the problem based on the content of each detail, perform the operation again.
When "code=100"
One of the services in "Related services" of "2.1 Starting and Stopping the Manager" in the "Operation Guide CE" may have stopped on the admin server.
On the admin server, check that the "Related services" have been started, and if there are any services that have stopped, start them.
For how to check and start services, refer to "2.1 Starting and Stopping the Manager" in the "Operation Guide CE".
When starting the manager, communication using the admin LAN may not have been possible.
Check if communication with the agent is possible using the admin LAN, then stop and restart the manager.
For how to stop and start managers, refer to "2.1 Starting and Stopping the Manager" in the "Operation Guide CE".
When "code=107"
When the load of the admin server is high, the internal connection process of a manager may time out.
After completing any other high-load processes other than those of Resource Orchestrator, perform the operation again.
Description
An error has occurred during power control of a managed server.
A detailed message is displayed for detail.
Corrective Action
When this message is displayed during the execution of the following operations, after resolving the problem based on the content of each detail, perform the operation again following step 4. of "Message number 68295".
When the same cloning image has been deployed to multiple managed servers, deployment to the other servers is stopped. When performing deployment again after performing corrective action, specify all of the servers again.
Backup of a system image
Restoration of a system image
Collection of a cloning image
Deployment of a cloning image
Auto-Recovery of a managed server for which server switchover uses the backup and restore method
Manual switchover or failback to a managed server for which server switchover uses the backup and restore method
When this message is displayed during the execution of operations other than the above, after resolving the problem based on the content of each detail, perform the operation again.
When detail is "another process is running"
Perform the operation again after the other process is complete.
When another process is not being executed, wait a short while and then perform the operation again.
When performing operations to a managed server (or resources being used in managed server) simultaneously
The following operations cannot be performed simultaneously on a managed server (or resources being used on managed servers).
In that case, after the processes executed are complete, perform the operation again.
Settings, changes, and deletion of the LAN switch
VLAN settings and changes of the LAN switch
Settings and changes of HBA address rename
Power operation
Turning maintenance LEDs ON and OFF
Reconfiguration of hardware properties
Reading of the system configuration file (Import)
