This section explains the troubleshooting steps to be performed when the server switchover or server failback process fails.
If server switchover or server failback is performed without all the conditions specified in "9.3 Server Switchover Conditions" in the "Setup Guide VE" being satisfied, one of the following error messages may be output:
Switchover:
FJSVrcx:ERROR:61143:switchover:failed FJSVrcx:ERROR:69122:timeout occurred while executing power control modules
Failback:
FJSVrcx:ERROR:61143:failback:failed FJSVrcx:ERROR:69122:timeout occurred while executing power control modules
Use the following procedure to confirm and correct the problem.
Recheck the spare server conditions with reference to "9.3 Server Switchover Conditions" in the "Setup Guide VE".
If any conditions are not satisfied, change the configuration to ensure that all conditions are met.
The corrective action differs depending on the switchover method used for switchover of the server to the spare server.
When using the HBA address rename method
If the following error message is output to the managed server console, the WWN may have failed to be set for the server HBA.
Take the action specified for "Message number 61308" of "Messages". Note that in this case there is no need to set the WWN again.
FJSVrcx:ERROR:61308:WWN setting failed. code=%1,%2
An internal error code is displayed in %1.
One of the following messages is displayed in %2.
When using the storage affinity switchover method
The destination server differs depending on the progress of the server switchover operations.
From Recent Operations of the ROR console, check [Progress Details]-[Progress List] for the server switchover to identify which operation has failed.
When the error occurred during an operation prior to [Checking server boot]
Restore the primary server environment and then perform server switchover again.
Perform the following procedure to restore the access path settings.
For details on how to use the storageadm zone command, refer to the "ETERNUS SF Storage Cruiser Operation Guide".
When the error occurred during [Checking server boot] or subsequent operations
The operations before starting the OS on the spare server have been completed, and the error has occurred during subsequent operations. Restore the spare server environment.
[OVM for SPARC]
If server switchover for an OVM for SPARC environment has failed, restore the server environment manually.
The destination server differs depending on the progress of the server switchover operations.
From Recent Operations of the ROR console, check [Progress Details]-[Progress List] for the server switchover to identify which operation has failed.
When an error occurs during operations before [Backing up of the OVM XML configuration information]
Restore the primary server environment and then perform server switchover again.
Use the storageadm zone add/delete command to restore the zoning of primary servers and host affinity configurations.
For details on how to use the storageadm zone command, refer to the "ETERNUS SF Storage Cruiser Operation Guide".
Configure the domain configuration information used in the control domain from XSCF.
Execute the following command.
XSCF>setdomainconfig -p 0
After executing the command, select the domain configuration.
When an error occurs during [Backing up of the OVM XML configuration information] or subsequent operations
The operations before starting the OS on the spare server have been completed, but an error has occurred during a subsequent operation.
Manually execute the operations that were skipped and continue the operation.
Manually execute any of the following operations that were skipped:
Backing up of the OVM XML configuration information
No operation is necessary.
Restoration of the domain configuration
Restore all domain configurations on the system from the XML file of the domain configuration saved before server switchover.
Execute the following command.
primary# ldm init-system -r -i /etc/opt/FJSVrcvat/config/ovm_config.xml
Restarting of the control domain
No operation is necessary.
Waiting for completion of stopping of the OS
No operation is necessary.
Waiting for completion of starting of the server
No operation is necessary.
Restoration of PCIe
Reconfigure the physical I/O devices allocated to the control domain and IO domain.
The same physical I/O device may have been configured for both the control domain and IO domain by OVM specification.
Reconfigure the allocations of physical I/O devices.
The list of PCIe endpoint devices can be confirmed using the ldm list-io command.
For details, refer to the "Oracle VM Server for SPARC Administration Guide" provided by Oracle.
Restarting of the control domain
Execute the following command and restart the control domain.
primary# shutdown -y -i6 -g0
Waiting for completion of stopping of the OS
No operation is necessary.
Waiting for completion of starting of the server
No operation is necessary.
Restoration of the virtual console
Reconfigure the port number used for the console of the guest domain.
When the port number of a certain console for the guest domain is configured during setup of the environment using OVM specifications, that port number may be disabled.
If the configured port number is disabled, reconfigure the port number.
Use the ldm set-vconsole command to set the port number.
For details, refer to the "Oracle VM Server for SPARC Administration Guide" provided by Oracle.
Restarting of the IO domain
Restart the IO domain.
When the IO domain has not been created outside the control domain, this operation is not necessary.
Restarting of the guest domain
After starting of the IO domain is complete, start each guest domain.
Saving of the domain configuration information to the firmware
Execute the following command.
primary# ldm add-spconfig Domain configuration information name
Refreshing of switchover status
No operation is necessary.
Save the XML files of OVM configuration information.
Automatic saving of XML files of configuration information stops during server switchover operations.
To start automatic saving of XML files, save the XML files of configuration information from the GUI or the CLI.
For details, refer to the following: