For details on OBP settings, refer to "8.2 Configure 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 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 PRIMEQUEST 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 server switchover, refer to "Chapter 4 Server Switchover" in the "Operation Guide VE".
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.
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 Configure the Server Environment" in the "Design Guide CE".
Shut down the server after completing BIOS settings.
3. Re-configure Hardware Properties after Replacement
After replacing the server, re-configure Resource Orchestrator with the latest hardware properties.
For details on how to re-configure hardware properties, refer to "9.3.1 Reconfiguration of Hardware Properties".
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. 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.
- 57 -