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.
Perform server switchover
Switch over the server to replace with its spare server.
Refer to "Chapter 10 Server Switchover" for details on the switchover function.
After the server has been switched over, its maintenance LED is automatically activated, and the server is powered down.
Replace the server
Replace the server whose maintenance LED is activated.
Change the BIOS settings of the replacement server to match the operating environment.
Refer to "3.5 Configuring the Server Environment" of the "ServerView Resource Coordinator VE Setup Guide" for details on BIOS settings.
Shut down the server after completing BIOS settings.
Re-configure hardware properties following replacement
After replacing the server, re-configure Resource Coordinator VE with the latest hardware properties.
Refer to "9.3 Re-configuring Hardware Properties" for details on how to re-configure hardware properties.
After hardware properties have been re-configured, the maintenance LED is automatically turned off in the RC console.
Perform post-switchover operations
Refer to "10.3 Post-Switchover Operations" and carry out the operations that must be performed after a server switchover.
Replacing a server with no spare server assigned
Use the following procedure to smoothly replace a server and resume its applications.
Put the target server into maintenance mode
Put the primary server to replace into maintenance mode.
Refer to "Appendix F Maintenance Mode" of the "ServerView Resource Coordinator VE Setup Guide" for details on the maintenance mode.
Collect a system image backup
For local boot servers, collect a system image backup when possible.
Refer to "Chapter 8 Backup and Restore" for details and conditions of system image backups.
In a SAN boot environment, the boot disk can be restored without having to back up and restore a system image.
Activate the maintenance LED
Activate the maintenance LED on the server that is to be replaced before shutting it down.
Refer to "9.2 Maintenance LEDs" for details on how to activate maintenance LEDs.
Replace the server
Replace the server whose maintenance LED is activated.
Change the BIOS settings of the replacement server to match the operating environment.
Refer to "3.5 Configuring the Server Environment" of the "ServerView Resource Coordinator VE Setup Guide" for details on BIOS settings.
Shut down the server after completing BIOS settings.
Re-configure hardware properties following replacement
After replacing the server, update Resource Coordinator VE with the latest hardware properties.
Refer to "9.3 Re-configuring Hardware Properties" for details on how to re-configure hardware properties.
After hardware properties have been re-configured, the maintenance LED is automatically turned off in the RC console.
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.
Otherwise, if a system image backup was taken, 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 a backup of the system image does not exist, 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.
Release maintenance mode
Release the replaced server from maintenance mode.
Refer to "Appendix F Maintenance Mode" of the "ServerView Resource Coordinator VE Setup Guide" for details on maintenance mode.
Servers with no Agent registered
Use the following procedure to replace servers on which the Resource Coordinator VE Agent was not registered.
Activate the maintenance LED
Activate the maintenance LED on the server that is to be replaced. Shut down the server if it is still powered on.
Refer to "9.2 Maintenance LEDs" for details on how to activate maintenance LEDs.
Replace the server
Replace the server whose maintenance LED is activated.
Change the BIOS settings of the replacement server to match the operating environment.
Refer to "3.5 Configuring the Server Environment" of the "ServerView Resource Coordinator VE Setup Guide" for details on BIOS settings.
Shut down the server after completing BIOS settings.
Re-configure hardware properties following replacement
After replacing the server, update Resource Coordinator VE with the latest hardware properties.
Refer to "9.3 Re-configuring Hardware Properties" for details on how to re-configure 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.
Perform server switchover
Switch over the server to replace with its spare server.
Refer to "Chapter 10 Server Switchover" for details on the switchover function.
The server to replace is automatically powered off after switchover.
Replace the server
Replace the target server.
Change the BIOS settings of the replacement server to match the operating environment.
Refer to "3.5 Configuring the Server Environment" of the "ServerView Resource Coordinator VE Setup Guide" for details on BIOS settings.
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.
Re-configure hardware properties following replacement
After replacing the server, re-configure Resource Coordinator VE with the latest hardware properties.
Refer to "9.3 Re-configuring Hardware Properties" for details on how to re-configure hardware properties.
Perform post-switchover operations
Refer to "10.3 Post-Switchover Operations" and carry out the operations that must be performed after a server switchover.
Replacing a server with no spare server assigned
Use the following procedure to smoothly replace a server and resume its applications.
Put the target server into maintenance mode
Put the primary server to replace into maintenance mode.
Refer to "Appendix F Maintenance Mode" of the "ServerView Resource Coordinator VE Setup Guide" for details on maintenance mode.
Create a system image backup
For local boot servers, create a system image backup when possible.
Refer to "Chapter 8 Backup and Restore" for details and conditions of system image backups.
In a SAN boot environment, the boot disk can be restored without having to back up and restore a system image.
Shut down the server
Shut down the server to replace if it is still powered on.
Refer to "Chapter 6 Power Control" for details on shutting down servers.
Replace the server
Replace the target server.
Change the BIOS settings of the replacement server to match the operating environment.
Refer to "3.5 Configuring the Server Environment" of the "ServerView Resource Coordinator VE Setup Guide" for details on BIOS settings.
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.
Re-configure hardware properties following replacement
After replacing the server, update Resource Coordinator VE with the latest hardware properties.
Refer to "9.3 Re-configuring Hardware Properties" for details on how to re-configure hardware properties.
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.
Otherwise, if a system image backup was taken, 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 a backup of the system image does not exist, run the installation program again.
SAN boot
The replaced server can be easily configured to access the original boot disk using HBA address rename. Therefore, there is no need to restore the boot disk. Simply power on the replacement server.
Release maintenance mode
Release the replaced server from maintenance mode.
Refer to "Appendix F Maintenance Mode" of the "ServerView Resource Coordinator VE Setup Guide" for details on maintenance mode.
Servers with no Agent registered
Use the following procedure to replace servers on which the Resource Coordinator VE Agent was not registered.
Shut down the server
Shut down the server to replace if it is still powered on.
Refer to "Chapter 6 Power Control" for details on shutting down servers.
Replace the server
Replace the target server.
Change the BIOS settings of the replacement server to match the operating environment.
Refer to "3.5 Configuring the Server Environment" of the "ServerView Resource Coordinator VE Setup Guide" for details on BIOS settings.
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.
Re-configure hardware properties following replacement
After replacing the server, update Resource Coordinator VE with the latest hardware properties.
Refer to "9.3 Re-configuring Hardware Properties" for details on how to re-configure hardware properties.
For SPARC Enterprise Servers
No specific action is required in Resource Coordinator VE.
