3.5.3 Canceling server startup in the event of a shared resource connection error
In the event of a connection error on a shared resource and a user command error, you can cancel startup of the active server and the hot standby operation. You can specify whether server startup is to be canceled for each resource.
If a connection error occurs on a shared resource, HA Monitor continues connection processing on the remaining shared resources, cancels startup of the active server, and then disconnects all shared resources. If the hot standby operation is to be canceled, HA Monitor terminates the standby server forcibly.
If the start retry function is used during hot standby processing, HA Monitor waits until the server is restarted.
- Organization of this subsection
(1) Shared resources subject to this processing
The following types of shared resources are subject to this processing:
-
Shared disks
-
File systems
-
LANs (IP address settings in the server-alias-name.up file)
-
User commands
(2) Required environment settings
This subsection describes how to specify the settings.
(a) Specifying shared disk settings
Specify use in the vg_neck operand in the server environment definition. You can change the vg_neck operand value with the HA Monitor command for dynamically changing a server's shared resources (mondevice command).
(b) Specifying file system settings
Specify use in the fs_neck operand in the server environment definition.
(c) Specifying LAN settings
Specify use in the ip_neck operand in the server environment definition.
You must also create a server-alias-name.up file, which is a LAN status settings file in HA Monitor. Use the sample file provided by HA Monitor. For details, see 6.12.2 Specifying LAN status settings files.
(d) Specifying user command settings
By specifying use in the uoc_neck operand in the server environment definition, you can cancel server startup whenever the execution result of the user command is not 0.
Note that HA Monitor checks for errors only for user commands that are executed at the start of server startup processing or at the start of server hot standby. The results of user commands executed at any other times are ignored.
For details about user commands, see 6.19 Creating user commands.