9.3.2 Replacing Servers

This section details the procedure to follow when replacing servers.

Information

Follow the same procedure when replacing servers where VM hosts are running.
No specific action is required in Resource Orchestrator when replacing admin servers or HBA address rename setup service servers.

For Rack Mount and Tower Servers

Replacing a Server with Spare Servers Assigned
Use the following procedure to switch applications over to a spare server and replace a server with minimal interruption.
1. Perform Server Switchover
  Switch over the server to replace with its spare server.
  For server switchover, refer to "Chapter 4 Server Switchover" in the "Operation Guide VE".
  The server to replace is automatically powered off after switchover.
2. Replace the Server
  Replace the server.
  Change the BIOS settings of the replacement server to match the operating environment.
  For details on BIOS settings, refer to "8.2 Configuring the Server Environment" in the "Design Guide CE".
  Shut down the server after completing BIOS settings.
  Configure the remote management controller of the replacement server with the same IP address, user name, password, and SNMP trap destination as those set on the original server.
3. Reconfigure Hardware Properties after Replacement
  After replacing the server, reconfigure Resource Orchestrator with the latest hardware properties.
  For details on how to reconfigure hardware properties, refer to "9.3.1 Reconfiguration of Hardware Properties".
  When using VIOM, refer to the manual of ServerView Virtual-IO Manager and perform inventory boot on ServerView Virtual-IO Manager.
  When public LAN (MAC address) information is configured, it is necessary to reconfigure the information. Perform configuration after completing "9.3.2 Replacing Servers".
  For details, refer to "5.5.3 Registering the Public LAN (MAC Address) Information" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
4. Perform Post-server Switchover Operations
  For details on the operations that must be performed after server switchover, refer to "4.3 Post-Switchover Operations" in the "Operation Guide VE".
Replacing a Server with no Spare Server Assigned
Use the following procedure to smoothly replace a server and resume its applications.
1. Place the Server into Maintenance Mode
  Place the primary server to replace into maintenance mode.
  For details on maintenance mode, refer to "Appendix C Maintenance Mode" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
2. Place the Server into VM Maintenance Mode
  When the primary server is a VM host, and can be placed into VM maintenance mode, place it into VM maintenance mode.
  For details on VM maintenance mode, refer to "15.2 VM Maintenance Mode of VM Hosts" in the "User's Guide VE".
3. Create a System Image Backup
  For local boot servers, create a system image backup when possible.
  For details on backing up system images, refer to "Chapter 16 Backup and Restore" in the "User's Guide VE".
  In SAN boot environments, the boot disk can be restored without having to back up and restore a system image.
4. Power the Server Off
  Shut down the server to replace if it is still powered on.
  For details on shutting down servers, refer to "Chapter 14 Power Control" in the "User's Guide VE".
5. Replace the Server
  Replace the server.
  Change the BIOS settings of the replacement server to match the operating environment.
  For details on BIOS settings, refer to "8.2 Configuring the Server Environment" in the "Design Guide CE".
  Shut down the server after completing BIOS settings.
  Configure the remote management controller of the replacement server with the same IP address, user name, password, and SNMP trap destination as those set on the original server.
6. Reconfigure Hardware Properties after Replacement
  After replacing the server, reconfigure Resource Orchestrator with the latest hardware properties.
  For details on how to reconfigure hardware properties, refer to "9.3.1 Reconfiguration of Hardware Properties".
  When using VIOM, refer to the manual of ServerView Virtual-IO Manager and perform inventory boot on ServerView Virtual-IO Manager.
  When public LAN (MAC address) information is configured, it is necessary to reconfigure the information. Perform reconfiguration after completing "9.3.2 Replacing Servers".
  For details, refer to "5.5.3 Registering the Public LAN (MAC Address) Information" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
7. Restore the Boot Disk
  - Local Boot
    There is no need to restore the boot disk if the original disk is installed on the replaced server. Simply power on the replacement server.
    If the boot disk was replaced and a system image backup was collected, restore that backup.
    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".
    Refer to "16.3 Restore" in the "User's Guide VE" for details on how to restore a system image. After the system image is restored, the server will be automatically powered on.
    If there is no backup of the system image, run the installation program again.
  - SAN Boot
    The replaced server can be easily configured to access the original boot disk using I/O virtualization. Therefore, there is no need to restore the boot disk. Simply power on the replacement server.
8. Release VM Maintenance Mode
  When the primary server was placed into VM maintenance mode, release the replaced server from VM maintenance mode.
  For details on VM maintenance mode, refer to "15.2 VM Maintenance Mode of VM Hosts" in the "User's Guide VE".
9. Release the Reference Server from Maintenance Mode
  Release the replaced server from maintenance mode.
  For details on maintenance mode, refer to "Appendix C Maintenance Mode" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Servers with no Agent Registered
Use the following procedure to replace servers on which no Resource Orchestrator agent was registered.
1. Power the Server Off
  Shut down the server to replace if it is still powered on.
  For details on shutting down servers, refer to "Chapter 14 Power Control" in the "User's Guide VE".
2. Replace the Server
  Replace the target server.
  Change the BIOS settings of the replacement server to match the operating environment.
  For details on BIOS settings, refer to "8.2 Configuring the Server Environment" in the "Design Guide CE".
  Shut down the server after completing BIOS settings.
  Configure the remote management controller of the replacement server with the same IP address, user name, password, and SNMP trap destination as those set on the original server.
3. Reconfigure Hardware Properties after Replacement
  After replacing the server, reconfigure Resource Orchestrator with the latest hardware properties.
  For details on how to reconfigure hardware properties, refer to "9.3.1 Reconfiguration of Hardware Properties".
  When using VIOM, refer to the manual of ServerView Virtual-IO Manager and perform inventory boot on ServerView Virtual-IO Manager.
  When public LAN (MAC address) information is configured, it is necessary to reconfigure the information. Perform reconfiguration after completing "9.3.2 Replacing Servers".
  For details, refer to "5.5.3 Registering the Public LAN (MAC Address) Information" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".

For Fujitsu M10/SPARC Enterprise Servers

Replacing a Server with Spare Servers Assigned
Use the following procedure to switch applications over to a spare server and replace a server with minimal interruption.
- When Replacing an HBA
  1. Perform Server Switchover
    Switch over the server to replace with its spare server.
    For server switchover, refer to "Chapter 4 Server Switchover" in the "Operation Guide VE".
    The server to replace is automatically powered off after switchover.
  2. Replace the Server
    Replace the HBA of the server.
    Change the OBP settings of the replacement server to match the operating environment.
    For details on OBP settings, refer to "8.2 Configuring the Server Environment" in the "Design Guide CE".
    Shut down the server after completing OBP settings.
    Configure the remote management controller of the replacement server with the same IP address, user name, password, and SNMP trap destination as those set on the original server.
  3. Change the WWN Information Settings
    Change the WWN information settings for after server replacement to the WWN value of the HBA after server replacement.
    Leave the value of the target CA as the one before changes were made.
  4. Perform Post-server Switchover Operations
    For details on the operations that must be performed after server switchover, refer to "4.3 Post-Switchover Operations" in the "Operation Guide VE".
    Note
    If takeover was performed before replacement of the HBA, release the spare server settings. Change the WWN information settings following the procedure in "Replacing a server with no spare server assigned".
- When not Replacing an HBA
  1. Perform Server Switchover
    Switch over the server to replace with its spare server.
    For server switchover, refer to "Chapter 4 Server Switchover" in the "Operation Guide VE".
    The server to replace is automatically powered off after switchover.
  2. Replace the Server
    Replace components (other than the HBA) of the server.
    Change the OBP settings of the replacement server to match the operating environment.
    For details on OBP settings, refer to "8.2 Configuring the Server Environment" in the "Design Guide CE".
    Shut down the server after completing OBP settings.
    Configure the remote management controller of the replacement server with the same IP address, user name, password, and SNMP trap destination as those set on the original server.
  3. Perform Post-server Switchover Operations
    For details on the operations that must be performed after server switchover, refer to "4.3 Post-Switchover Operations" in the "Operation Guide VE".
Replacing a Server with no Spare Server Assigned
When WWN information has been configured, use the following procedure to change the WWN information to that of the WWPN value of the replaced HBA.
1. Delete the Target CA
  When there are target CA settings in the WWN information, stop the server and then delete the target CA settings (set them as hyphens ("-")).
2. Replace the Server
  Replace the HBA of the server.
  Change the OBP settings of the replacement server to match the operating environment.
  For details on OBP settings, refer to "8.2 Configuring the Server Environment" in the "Design Guide CE".
  Shut down the server after completing OBP settings.
  When the target CA was deleted in step 1, configure zoning and host affinity settings in the WWPN value of the replacement HBA.
  For details, refer to the "ETERNUS SF Storage Cruiser Operation Guide".
3. Change the WWN Information Settings
  Change the WWN information settings for after server replacement to the WWN value of the HBA after server replacement.
  When the target CA was deleted in step 1, configure a new target CA.
  After configuration, restart the server.
  After starting the server, check the status of the server's HBA from ESC.
  When the HBA status is "unknown", delete it.
  When the HBA status is displayed as "access path inheritance is required" (yellow icon), perform access path inheritance.
  For details, refer to the "ETERNUS SF Storage Cruiser Operation Guide".
  When the target CA was not deleted in step 1, configure the target CA as a hyphen ("-").
Information
[OVM for SPARC]
When replacing servers, it is necessary to restore the OVM for SPARC environment.
For details, refer to "4.3.2 Recovery of OVM for SPARC Environments" in the "Operation Guide VE".
When Fujitsu M10-4S are in a Building Block Configuration
No specific action is required in Resource Orchestrator when replacing a LAN switch.

For PRIMEQUEST Servers

Replacing a Server with no Spare Server Assigned
Use the following procedure to smoothly replace a server and resume its applications.
1. Place the Server into Maintenance Mode
  Place the primary server to replace into maintenance mode.
  For details on maintenance mode, refer to "Appendix C Maintenance Mode" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
2. Place the Server into VM Maintenance Mode
  When the primary server is a VM host, and can be placed into VM maintenance mode, place it into VM maintenance mode.
  For details on VM maintenance mode, refer to "15.2 VM Maintenance Mode of VM Hosts" in the "User's Guide VE".
3. Create a System Image Backup
  For local boot servers, create a system image backup when possible.
  For details on backing up system images, refer to "Chapter 16 Backup and Restore" in the "User's Guide VE".
  In SAN boot environments, the boot disk can be restored without having to back up and restore a system image.
4. Power the Server Off
  Shut down the server to replace if it is still powered on.
  For details on shutting down servers, refer to "Chapter 14 Power Control" in the "User's Guide VE".
5. Replace the Server
  Replace the server.
  Use the Maintenance Wizard of the Management Board Web-UI to perform replacement.
  For details on the Maintenance Wizard, refer to the PRIMEQUEST manual.
  Also, change the BIOS settings of the replacement server to match the operating environment.
  For details on BIOS settings, refer to "8.2 Configuring the Server Environment" in the "Design Guide CE".
  Shut down the server after completing BIOS settings.
6. Reconfigure Hardware Properties after Replacement
  After replacing the server, reconfigure Resource Orchestrator with the latest hardware properties.
  For details on how to reconfigure hardware properties, refer to "9.3.1 Reconfiguration of Hardware Properties".
7. Restore the Boot Disk
  - Local Boot
    There is no need to restore the boot disk if the original disk is installed on the replaced server. Simply power on the replacement server.
    If the boot disk was replaced and a system image backup was collected, restore that backup.
    Refer to "16.3 Restore" in the "User's Guide VE" for details on how to restore a system image. After the system image is restored, the server will be automatically powered on.
    If there is no backup of the system image, run the installation program again.
  - SAN Boot
    As the replaced server can be easily configured to access the original boot disk using HBA address rename there is no need to restore the boot disk. Simply power on the replacement server.
8. Release VM Maintenance Mode
  When the primary server was placed into VM maintenance mode, release the replaced server from VM maintenance mode.
  For details on VM maintenance mode, refer to "15.2 VM Maintenance Mode of VM Hosts" in the "User's Guide VE".
9. Release the Reference Server from Maintenance Mode
  Release the replaced server from maintenance mode.
  For details on maintenance mode, refer to "Appendix C Maintenance Mode" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
Servers with no Agent Registered
Use the following procedure to replace servers on which no Resource Orchestrator agent was registered.
1. Power the Server Off
  Shut down the server to replace if it is still powered on.
  For details on shutting down servers, refer to "Chapter 14 Power Control" in the "User's Guide VE".
2. Replace the Server
  Replace the server.
  Use the Maintenance Wizard of the Management Board Web-UI to perform replacement.
  For details on the Maintenance Wizard, refer to the PRIMEQUEST manual.
  Also, change the BIOS settings of the replacement server to match the operating environment.
  For details on BIOS settings, refer to "8.2 Configuring the Server Environment" in the "Design Guide CE".
  Shut down the server after completing BIOS settings.
3. Reconfigure Hardware Properties after Replacement
  After replacing the server, reconfigure Resource Orchestrator with the latest hardware properties.
  For details on how to reconfigure hardware properties, refer to "9.3.1 Reconfiguration of Hardware Properties".