9.4 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.

For PRIMERGY BX servers

Replacing a server assigned with spare servers
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 details on the switchover function, refer to "Chapter 10 Server Switchover".
  After the server has been switched over, its maintenance LED is automatically activated, and the server is powered down.
2. Replace the server
  Replace the server whose maintenance LED is activated.
  Change the BIOS settings of the replacement server to match the operating environment.
  For details on BIOS settings, refer to "3.5 Configuring the Server Environment" of the "ServerView Resource Coordinator VE Setup Guide".
  Shut down the server after completing BIOS settings.
3. Re-configure hardware properties after replacement
  After replacing the server, re-configure Resource Coordinator VE with the latest hardware properties.
  For details on how to re-configure hardware properties, refer to "9.3 Re-configuring Hardware Properties".
  After hardware properties have been re-configured, the maintenance LED is automatically turned off in the RC console.
4. Perform post-server switchover operations
  For details on the operations that must be performed after a server switchover, refer to "10.3 Post-Switchover Operations".
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 the maintenance mode, refer to "Appendix F Maintenance Mode" of the "ServerView Resource Coordinator VE Setup Guide".
2. Create a system image backup
  For local boot servers, create a system image backup when possible.
  For details and conditions of system image backups, refer to "Chapter 8 Backup and Restore".
  In SAN boot environments, the boot disk can be restored without having to back up and restore a system image.
3. Activate the maintenance LED
  Activate the maintenance LED on the server that is to be replaced before shutting it down.
  For details on how to activate maintenance LEDs, refer to "9.2 Maintenance LEDs".
4. Replace the server
  Replace the server whose maintenance LED is activated.
  Change the BIOS settings of the replacement server to match the operating environment.
  For details on BIOS settings, refer to "3.5 Configuring the Server Environment" of the "ServerView Resource Coordinator VE Setup Guide".
  Shut down the server after completing BIOS settings.
5. Re-configure hardware properties after replacement
  After replacing the server, re-configure Resource Coordinator VE with the latest hardware properties.
  For details on how to re-configure hardware properties, refer to "9.3 Re-configuring Hardware Properties".
  After hardware properties have been re-configured, the maintenance LED is automatically turned off in the RC console.
6. 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 "8.3 Restoring System Images" 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.
7. Release maintenance mode
  Release the replaced server from maintenance mode.
  For details on the maintenance mode, refer to "Appendix F Maintenance Mode" of the "ServerView Resource Coordinator VE Setup Guide".
Servers with no agent registered
Use the following procedure to replace servers on which no Resource Coordinator VE agent was registered.
1. Activate the maintenance LED
  Activate the maintenance LED on the server that is to be replaced and shut down the server if it is still powered on.
  For details on how to activate maintenance LEDs, refer to "9.2 Maintenance LEDs".
2. Replace the server
  Replace the server whose maintenance LED is activated.
  Change the BIOS settings of the replacement server to match the operating environment.
  For details on BIOS settings, refer to "3.5 Configuring the Server Environment" of the "ServerView Resource Coordinator VE Setup Guide".
  Shut down the server after completing BIOS settings.
3. Re-configure hardware properties after replacement
  After replacing the server, re-configure Resource Coordinator VE with the latest hardware properties.
  For details on how to re-configure hardware properties, refer to "9.3 Re-configuring Hardware Properties".
  After hardware properties have been re-configured, the maintenance LED is automatically turned off in the RC console.

For Rack Mount and Tower Servers

Replacing a server assigned with spare servers
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 details on the switchover function, refer to "Chapter 10 Server Switchover".
  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 "3.5 Configuring the Server Environment" of the "ServerView Resource Coordinator VE Setup Guide".
  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. Re-configure hardware properties after replacement
  After replacing the server, re-configure Resource Coordinator VE with the latest hardware properties.
  For details on how to re-configure hardware properties, refer to "9.3 Re-configuring Hardware Properties".
4. Perform post-server switchover operations
  For details on the operations that must be performed after a server switchover, refer to "10.3 Post-Switchover Operations".
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 the maintenance mode, refer to "Appendix F Maintenance Mode" of the "ServerView Resource Coordinator VE Setup Guide".
2. Create a system image backup
  For local boot servers, create a system image backup when possible.
  For details and conditions of system image backups, refer to "Chapter 8 Backup and Restore".
  In SAN boot environments, the boot disk can be restored without having to back up and restore a system image.
3. Shut down the server
  Shut down the server to replace if it is still powered on.
  For details on shutting down servers, refer to "Chapter 6 Power Control".
4. 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 "3.5 Configuring the Server Environment" of the "ServerView Resource Coordinator VE Setup Guide".
  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.
5. Re-configure hardware properties after replacement
  After replacing the server, re-configure Resource Coordinator VE with the latest hardware properties.
  For details on how to re-configure hardware properties, refer to "9.3 Re-configuring Hardware Properties".
6. 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 "8.3 Restoring System Images" 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.
7. Release maintenance mode
  Release the replaced server from maintenance mode.
  For details on the maintenance mode, refer to "Appendix F Maintenance Mode" of the "ServerView Resource Coordinator VE Setup Guide".
Servers with no agent registered
Use the following procedure to replace servers on which no Resource Coordinator VE agent was registered.
1. Shut down the server
  Shut down the server to replace if it is still powered on.
  For details on shutting down servers, refer to "Chapter 6 Power Control".
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 "3.5 Configuring the Server Environment" of the "ServerView Resource Coordinator VE Setup Guide".
  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. Re-configure hardware properties after replacement
  After replacing the server, re-configure Resource Coordinator VE with the latest hardware properties.
  For details on how to re-configure hardware properties, refer to "9.3 Re-configuring Hardware Properties".

For SPARC Enterprise Servers

Replacing a server assigned with spare servers
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 details on the switchover function, refer to "Chapter 10 Server Switchover".
    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 "3.5 Configuring the Server Environment" of the "ServerView Resource Coordinator VE Setup Guide".
    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 a server switchover, refer to "10.3 Post-Switchover Operations".
    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 details on the switchover function, refer to "Chapter 10 Server Switchover".
    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 "3.5 Configuring the Server Environment" of the "ServerView Resource Coordinator VE Setup Guide".
    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 a server switchover, refer to "10.3 Post-Switchover Operations".
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 "3.5 Configuring the Server Environment" of the "ServerView Resource Coordinator VE Setup Guide".
  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 ESC users 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 ESC users guide.
  When the target CA was not deleted in step 1., configure the target CA as a hyphen ("-").

For PRIMERGY Partition Model servers

Replacing a server assigned with spare servers
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 details on the switchover function, refer to "Chapter 10 Server Switchover".
  The server is automatically powered off after switchover.
2. Replace the server
  Replace the server.
  Use the Maintenance Wizard of the Management Board Web-UI to perform replacement.
  Refer to the PRIMERGY Partition Model manual for details on the Maintenance Wizard.
  Also, change the BIOS settings of the replacement server to match the operating environment.
  For details on BIOS settings, refer to "3.5 Configuring the Server Environment" of the "ServerView Resource Coordinator VE Setup Guide".
  Shut down the server after completing BIOS settings.
3. Re-configure hardware properties after replacement
  After replacing the server, re-configure Resource Coordinator VE with the latest hardware properties.
  For details on how to re-configure hardware properties, refer to "9.3 Re-configuring Hardware Properties".
4. Perform post-server switchover operations
  For details on the operations that must be performed after a server switchover, refer to "10.3 Post-Switchover Operations".
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 the maintenance mode, refer to "Appendix F Maintenance Mode" of the "ServerView Resource Coordinator VE Setup Guide".
2. Create a system image backup
  For local boot servers, create a system image backup when possible.
  For details and conditions of system image backups, refer to "Chapter 8 Backup and Restore".
  In SAN boot environments, the boot disk can be restored without having to back up and restore a system image.
3. Shut down the server
  Shut down the server to replace if it is still powered on.
  For details on shutting down servers, refer to "Chapter 6 Power Control".
4. Replace the server
  Replace the server.
  Use the Maintenance Wizard of the Management Board Web-UI to perform replacement.
  Refer to the PRIMERGY Partition Model manual for details on the Maintenance Wizard.
  Also, change the BIOS settings of the replacement server to match the operating environment.
  For details on BIOS settings, refer to "3.5 Configuring the Server Environment" of the "ServerView Resource Coordinator VE Setup Guide".
  Shut down the server after completing BIOS settings.
5. Re-configure hardware properties after replacement
  After replacing the server, re-configure Resource Coordinator VE with the latest hardware properties.
  For details on how to re-configure hardware properties, refer to "9.3 Re-configuring Hardware Properties".
6. 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 "8.3 Restoring System Images" 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.
7. Release maintenance mode
  Release the replaced server from maintenance mode.
  For details on the maintenance mode, refer to "Appendix F Maintenance Mode" of the "ServerView Resource Coordinator VE Setup Guide".
Servers with no agent registered
Use the following procedure to replace servers on which no Resource Coordinator VE agent was registered.
1. Shut down the server
  Shut down the server to replace if it is still powered on.
  For details on shutting down servers, refer to "Chapter 6 Power Control".
2. Replace the server
  Replace the server.
  Use the Maintenance Wizard of the Management Board Web-UI to perform replacement.
  Refer to the PRIMERGY Partition Model manual for details on the Maintenance Wizard.
  Also, change the BIOS settings of the replacement server to match the operating environment.
  For details on BIOS settings, refer to "3.5 Configuring the Server Environment" of the "ServerView Resource Coordinator VE Setup Guide".
  Shut down the server after completing BIOS settings.
3. Re-configure hardware properties after replacement
  After replacing the server, re-configure Resource Coordinator VE with the latest hardware properties.
  For details on how to re-configure hardware properties, refer to "9.3 Re-configuring Hardware Properties".