Filter
Top Products
- Network card driver settings (drivers without a digital signature should be replaced by the latest updated drivers with a digital
signature)
- Access rights to the '\Documents and Settings\Default User' folder
- While a cloning image is being deployed, collection, deployment, and deletion cannot be performed simultaneously on the cloning
images with the same name.
- If a cloning image is deployed to a system with a larger disk capacity than the disk space required for the cloning image, any excessive
disk space becomes unused disk space. This unused disk space can be used for other purposes.
- Destination servers are rebooted several times during cloning image deployment. Make sure that deployment has completed before
restarting operations and making further settings.
- The number of reboots during deployment increases when using the HBA address rename function.
- Communication errors between the admin and destination servers (resulting in an image deployment failure or an [unknown] status
on the destination server) may be caused by improper use of the network parameter auto-configuration function (described in "17.6
Network Parameter Auto-Configuration for Cloning Images"). Examples of improper use are given below.
- Auto-configuration settings were made for the admin LAN
- Auto-configuration settings were made for the public LAN using IP addresses contained within the admin LAN subnet range
Log in to the destination servers on which errors occurred and check for the presence of such settings in the definition file for the
network parameter auto-configuration function.
If incorrect settings were made, perform the following operations to fix communication errors.
- Fix network settings on destination servers
- If the source and destination servers are the same
Restore the system images backed up before cloning image deployment.
- If the destination server is different from the source server
Run the rcxadm lanctl unset command described in "17.6.3 Clearing Settings" to reset network settings to their original values.
If the admin LAN IP address is not set on the source server, set it manually to restore communications between the admin server and
the source server.
- Re-collect the cloning image
Correct any errors found in the definition file for the network parameter auto-configuration function and re-collect the cloning
image.
Re-deploy the cloning image to the destination servers for which deployment failed.
Delete any cloning image that failed to deploy.
- If Windows Server 2008 activation failed during deployment, message number 47233 is displayed.
This message indicates that deployment of Windows Server 2008 completed but that activation failed.
For details on the appropriate corrective action, refer to "Message number 47233" in "Messages".
- When a cloning image is deployed to multiple servers, it may be necessary to enable IGMP snooping on admin LAN switches. If
IGMP snooping is not enabled, transfer performance may deteriorate when ports with different speeds co-exist in the same network,
or multiple image operations are run simultaneously.
17.4 Viewing
This section explains how to display collected cloning images.
In the ROR console, select the [Image List] tab.
A list of cloning images is displayed under the cloning image list.
Use this list to manage the cloning images used by Resource Orchestrator.
- 134 -