Filter
Top Products
- When using a rack mount or tower server and the server is registered with "Disable" of "Association with server management
software (ServerView)" is selected
[Windows Manager]
>
Installation_folder
\SVROR\Manager\bin\rcxadm server set -name
physical server
-attr bootagt=winpe
<RETURN>
[Linux Manager]
#/opt/FJSVrcvmr/bin/rcxadm server set -name
physical server
-attr bootagt=winpe <RETURN>
- In a SAN boot environment using HBA address rename, and the following model
- PRIMERGY BX960 S1
[Windows Manager]
>
Installation_folder
\SVROR\Manager\bin\rcxadm server set -name
physical server
-attr bootagt=winpe
<RETURN>
[Linux Manager]
#/opt/FJSVrcvmr/bin/rcxadm server set -name
physical server
-attr bootagt=winpe <RETURN>
If the above command has not been executed on the server from which the cloning image is being collected, the cloning image may
not be collected correctly. Delete that cloning image and then redo the cloning image collection.
- It is recommended to back up destination servers before deploying cloning images, as this will simplify the recovery procedure in
case of the deployed cloning image is faulty.
For details on backing up, refer to "16.2 Backup".
Note
- Cloning images cannot be deployed to servers that have been set up as spare servers for other managed servers, when not using I/O
virtualization. Cancel any such settings before deploying a cloning image.
- VLAN settings (on adjacent LAN switch ports) cannot be deployed during server cloning. LAN switch VLAN settings should be set
up before deploying a cloning image.
For details on how to configure VLAN settings on LAN switches, refer to "7.3.4 Configuring VLANs on LAN Switches".
- When deploying a cloning image back to its source server, the source server should be backed up before deployment.
For details on backing up, refer to "16.2 Backup".
If the deployed cloning image is faulty and causes deployment errors, use the following procedure to collect a new cloning image.
1. Restore the system image that was backed up before cloning image deployment.
2. Fix any incorrect settings on the source server
3. Collect a new cloning image
4. Delete the faulty cloning image
- When deploying cloning images to multiple managed servers, if the managed servers belong to different subnets, cloning images
cannot be deployed.
- When using PRIMEQUEST servers, cloning images cannot be deployed to partitions for which UEFI has been set.
When collecting and deploying cloning images, configure the BIOS settings and boot option settings after changing to Legacy boot.
For details on how to change boot options, refer to "9.1.10 Changing Boot Options".
- When using local disks as system disks, and iSCSI storage as data disks, refer to the advisory notes described in "Table 8.1 Supported
Storage Device Configurations" in "8.1.1 Storage Configuration" in the "Design Guide VE".
- 130 -