9.3 Re-configuring Hardware Properties

This section explains how to re-configure hardware properties for replaced hardware.

After hardware replacement, it is necessary to re-configure Resource Coordinator VE with the new hardware properties.

Note

Ensure this operation is performed only after the replacement of one of the following: a server itself, the NIC used either for 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.
When the system board or GSPB of a PRIMERGY Partition Model server has been changed, ensure that this operation is performed.
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.

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.

Re-configuring Hardware Properties After Server Replacement

For PRIMERGY BX servers
Use the following procedure to re-configure properties for replaced hardware.
1. After hardware replacement, insert the server and check that the following message is displayed in the event log.
  Server blade added
2. After approximately 30 seconds, right-click the target server in the RC console server resource tree, and select [Hardware Maintenance]-[Re-configure] from the popup menu.
  The [Re-configure Hardware Properties] dialog is displayed.
3. 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.
For rack mount or tower servers
Use the following procedure to re-configure properties for replaced hardware.
1. If the agent has already been registered, power on the server.
2. In the RC console server resource tree, right-click the target server and select [Hardware Maintenance]-[Re-configure] from the popup menu.
  The [Re-configure Hardware Properties] dialog is displayed.
3. Enter MAC addresses for the network interfaces used on the admin LAN.
  This step can be skipped if no network interface was replaced.
  - Admin LAN MAC Address (NIC1)
    Required only if the agent is not registered.
  - MAC address (NIC2) under SAN Boot/admin LAN redundancy
    This item is only required for the following cases.
    - When using the HBA address rename setup service.
    - When using GLS for admin LAN redundancy on the target server.
    - For the spare server of a managed server using admin LAN redundancy.
4. Click <OK>.
  The original hardware properties of the selected managed server are updated with new hardware properties obtained from the replacement server.
For PRIMERGY Partition Model servers
Use the following procedure to re-configure properties for replaced hardware.
1. Replace the system board or GSPB, and insert the server.
2. After approximately 30 seconds, right-click the target server in the RC console server resource tree, and select [Hardware Maintenance]-[Re-configure] from the popup menu.
  The [Re-configure Hardware Properties] dialog is displayed.
3. Click <OK>.
  The original hardware properties of the selected managed server are updated with new hardware properties obtained from the replacement server.