This section explains how to re-configure hardware properties for replaced hardware.
After hardware replacement, it is necessary to re-configure Resource Orchestrator with the new hardware properties.
For PRIMERGY BX servers, the hardware properties are automatically re-configured.
Note
Ensure this operation is performed only after the replacement of one of the following: a server itself, the NIC used for either the admin or public LAN, or the HBA.
If it is not, there is a possibility that operations on the server will not run correctly.
After replacing the hardware, the server status becomes "unknown". The appropriate status can be restored by re-configuring the hardware properties from the server.
Prerequisites
The following prerequisites must be satisfied before this operation can be performed:
Both the replaced server and replacement server must be the same model
A warning message is shown if the model of the replacement server differs from that of the replaced server.
When replacing a PRIMERGY BX server, the replacement server must be inserted into the same slot as used for the replaced server
Hardware properties cannot be re-configured from a server inserted in a different slot. An error occurs if no server is inserted in the slot occupied by the previous server.
The replaced server and replacement server must both be of the same blade type
If the blade types of the replaced and replacement servers are different, an error will occur.
To move a server to a different slot within a chassis, the server must be deleted first, and then registered again after being inserted in its new slot.
Pre-Configuration
For PRIMERGY BX servers, the hardware properties are automatically re-configured.
If automatic re-configuration is not necessary for PRIMERGY BX servers, delete the following file, and then restart the manager.
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data
auto_replace.rcxprop
Re-configuring Hardware Properties after Server Replacement
If the definition file has already been created, there is no need to set the hardware information again.
If the definition file has not been created, use the following procedure to re-configure properties for replaced hardware.
After hardware replacement, insert the server and check that the following message is displayed in the event log.
Server blade added |
After the message is displayed, shut down the server if it is still powered on.
After approximately 30 seconds, right-click the target server in the ROR console server resource tree, and select [Hardware Maintenance]-[Re-configure] from the popup menu.
The [Re-configure Hardware Properties] dialog is displayed.
Click <OK>.
The original hardware properties of the selected managed server are updated with new hardware properties obtained from the replacement server. If the maintenance LED is on it will be turned off automatically.
Note
When registering an agent and performing backups of system images or cloning images, perform one of the following.
Restart the managed server after reconfiguring the hardware properties
Restart the related services described in "2.2 Starting and Stopping an Agent"
