9.3.1 Reconfiguration of Hardware Properties

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.

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.
When the system board or GSPB of a PRIMEQUEST 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.
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 SPARC Enterprise servers, the hardware properties are automatically re-configured.

Re-configuring Hardware Properties after Server Replacement

For Rack Mount and Tower Servers
Use the following procedure to re-configure properties for replaced hardware.
1. If the agent or ServerView Agents has already been registered, power on the server.
  Additional Information
  When a server using SAN boot has a hardware exchange that results in the MAC address used for the admin LAN being changed, the OS and an agent cannot be started.
  In this case, the server should be started once, and the MAC address confirmed on the BIOS (hardware) screen. After the MAC address is confirmed, power off the server again.
2. In the ROR 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.
    Additional Information
    When a server is powered off for the reason given in the Additional Information in 1., the item for input of the value of NIC1 is displayed. In this case, input the MAC address confirmed in the Additional Information in 1.
  - 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 PRIMEQUEST 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 ROR 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.
For SPARC Enterprise Servers
Note that in this case there is no need to set the hardware information again.
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"