When integrating with ESC, it should be configured first. Register the Fibre Channel switches and storage units connected to managed servers on ESC.
Note
When integrating with ESC, do not register servers used as spare server for Resource Orchestrator on ESC.
After registration, collect WWNs of HBAs set on physical servers or WWNs of CAs set on storage units.
From the client window of ESC, collect the WWNs for HBAs contained in the registered servers.
For servers that are not registered on ESC, collect WWNs from the seals, drivers, and utilities provided with HBA cards.
Refer to the storage device manual of each storage device for details.
From the client window of ESC, collect the WWNs for HBAs contained in the registered storage.
Refer to the storage device manual of each storage device for details.
Collected WWNs are reflected in the relationship between physical servers and HBA WWNs from the perspective of the server, and in the relationship between the storage CA and WWNs from the perspective of storage devices.
System configuration requires that the relationship between HBA WWNs, storage CA WWNs, and volumes from the perspective of storage devices be defined clearly.
When using a multi-path configuration, design the values to match the order of HBAs configured as primary servers or spare servers with those of the corresponding CAs.
Information
For integration with ESC, Resource Orchestrator supports configurations where managed servers have up to eight HBA ports mounted.
[OVM for SPARC]
For OVM for SPARC environments, configure the boot settings of the primary server as follows:
XSCF physical partition operation mode
Autoboot(Guest Domain): off
For details, refer to the "Fujitsu SPARC M12 and Fujitsu M10/SPARC M10 XSCF Reference Manual".
OBP settings of all domains (control domain, guest domain, IO domain)
auto-boot?: true
For details, refer to "Oracle VM Server for SPARC Administration Guide" provided by Oracle.
For the status of the OVM for SPARC environment after server switchover, refer to "Appendix A Notes on Operating ServerView Resource Orchestrator" in the "Operation Guide VE".
For OVM for SPARC environments, only LUN (/dev/dsk/cXtXdXs2) can be used as the virtual disk of the guest domain.
Note
If Autoboot(Guest Domain) for XSCF is "on", when the control domain is started, the guest domain is started accordingly.
Due to the specifications of OVM for SPARC, the boot order of the IO domain and the guest domain cannot be controlled. Therefore, if booting of the guest domain starts before the IO domain, booting of the guest domain may fail.
Perform configuration to boot the IO domain and the guest domain in order using the server switchover process of Resource Orchestrator.
For details, refer to "18.5.3 Definition File of IO Domain" in the "User's Guide VE".
If Autoboot(Guest Domain) for XSCF is "off", when the control domain is powered on, the guest domain is not powered on. In this case, each guest domain must be powered on respectively.
If auto-boot? for the guest domain or IO domain is "false", after the server switchover, the boot process of the guest domain or the IO domain is only processed until it reaches the OBP. In this case, after server switchover, manually start the guest domain or IO domain.
If the auto-boot? for the control domain is "false", after server switchover the boot process of the control domain is only processed until it reaches the OBP, so server switchover will fail.
When configuring server switchover settings, set Autoboot(Guest Domain) for the physical partition operation mode on XSCF on the stand-by server to "off".
If server switchover ends abnormally, it will be necessary to restore the environment manually.
In case of such an event, record the information of the environment when performing configuration.
For details on the ldm command, refer to the "Oracle VM Server for SPARC Administration Guide" provided by Oracle.
The port number used for the console of the guest domain (if a fixed console number has been set)
Physical I/O device information allocated to the control domain and the IO domain
For details, refer to "2.5 Server Switchover and Failback Issues" in "Troubleshooting".
Prerequisites for Server Switchover
For details on prerequisites of server switchover, refer to "9.3 Server Switchover Conditions" in the "Setup Guide VE".
