Fujitsu ServerView Resource Orchestrator Cloud Edition V3.1.0 User Manual page 145

The [Server Name] column displays the names of each destination servers.
By default, server names (computer name or hostname) or physical server names are displayed.
The names specified in this column will be assigned to destination servers as their computer names (for Windows systems)
or system node names (for Linux systems).
Those names can be changed using the following procedure.
1. Double-click the [Server name after deployment] cell of a server.
The [Server name after deployment] cell becomes editable.
2. Enter a new server name.
[Windows]
A string composed of up to 63 alphanumeric characters, underscores, ("_"), and hyphens, ("-").
The string cannot be composed solely of numbers.
[Linux]
A string composed of up to 64 alphanumeric characters, and the following symbols:
"%", "+", ",", "-", ".", "/", ":", "=", "@", "_", "~"
Information
Since the entered server name is also used as the hostname of its corresponding destination server, it is recommended to
use only characters defined in RFC (Request For Comments) 952:
- Alphanumeric characters
- Hyphens, ("-")
- Periods, (".") [Linux]
d.
Click <OK>.
The cloning image deployment process starts.
The process status can be checked in the Recent Operations area of the ROR console.
Clicking <Cancel> in the Recent Operations area displays a confirmation dialog and stops the process.
Note
When this process is cancelled, cloning image deployment to all destination servers is cancelled.
Please note that canceling the deployment of a cloning image does not restore the destination server to the state before
the deployment took place.
3.
Restart applications on the destination server(s).
Perform the following settings if necessary:
-
The settings of NIC redundancy for admin LANs and public LANs
-
The settings of tagged VLANs for NICs
After deployment, destination servers are set to use the admin server as their default gateway.
Reconfigure such network settings if necessary. Check that applications are running properly on destination servers.
At this point, if an application is still using the source server's hostname or IP address (e.g. within application-specific settings or
configuration file), manually update such settings with the destination server values.
Note
When a managed server is a PRIMEQUEST, set the PSA-MMB IP address after deployment. For details, refer to the PRIMERGY
Partition Model manual.
- 129 -