This section explains how to replace and add server components.
Replacing, Adding, and Deleting Network Interfaces (Admin LAN, Public LAN)
The procedure used to replace, add, and delete network interfaces is the same as the one described in "9.2.3 Replacing Servers".
For details, refer to "9.2.3 Replacing Servers".
When adding or removing network interfaces, if the target server is running Red Hat Enterprise Linux 5, Red Hat Enterprise Linux 6, Red Hat Enterprise Linux 7, or Citrix XenServer, after completing the steps described in "9.2.3 Replacing Servers", log in with administrative privileges on the managed server and execute the following command.
# /usr/local/sbin/macbindconfig create <RETURN> |
When using Citrix XenServer, reinstall XenServer referring to the Citrix XenServer manual.
When using Red Hat Enterprise Linux 5 Virtualization (Xen-Based) and not using I/O Virtualization (VIOM), perform the following procedure.
Execute the following command to temporally disable automatic startup of the xend daemon and then restart the managed server.
# chkconfig xend off <RETURN> |
Once the server has restarted, execute the following commands to update MAC address bindings, re-enable automatic startup of the xend daemon, and restart the xend daemon itself.
# /usr/local/sbin/macbindconfig create <RETURN> |
When the configuration of server components has been changed, check the configuration file of the OS, and make any necessary corrections. For details, refer to "Check the Network Interface Definition File" in "2.2.1.1 Software Preparation and Checks" in the "Setup Guide CE".
When adding or removing network interfaces, if the target server is running Red Hat Enterprise Linux 6, after completing the steps described in "9.2.3 Replacing Servers", modify the configuration file.
For details, refer to "Check the Network Interface Definition File" in "2.2.1.1 Software Preparation and Checks" in the "Setup Guide CE".
Replacing an HBA
The procedure used to replace an HBA is the same as that described in "9.2.3 Replacing Servers".
For details, refer to "9.2.3 Replacing Servers".
When using I/O virtualization, the replacement HBA will automatically inherit the WWN originally set on the replaced HBA. Therefore, there is no need to reconfigure access paths on the storage side.
When configuring WWN information, it is necessary to change WWN information settings to the replaced HBA WWN values.
For details on how to change WWN information, refer to "9.1.12 Changing WWN Settings for ETERNUS SF Storage Cruiser Integration" in the "User's Guide VE".
Replacing a boot disk (in local boot environments)
Use the following procedure to replace a boot disk.
Replace the faulty boot disk with a new one.
If the boot disk's content was backed up, restore it.
When the image operation target disk is configured, configure the image operation target disk before performing restoration.
For details, refer to "9.1.13 Changing Target Disks of Image Operations" in the "User's Guide VE".
Information
The backup and restore functions available in Resource Orchestrator can be used to restore the boot disk contents.
For details, refer to "Chapter 16 Backup and Restore" in the "User's Guide VE".
Replacing a System Board
The procedure used to replace a system board is the same as that described in "9.2.3 Replacing Servers".
For details, refer to "9.2.3 Replacing Servers".
Replacing an IO Board
No specific action is required in Resource Orchestrator when replacing an IO board.
Replacing Other Server Components
No specific action is required in Resource Orchestrator when replacing onboard server components like memory modules or other parts.
