4.8.2 Flow of server termination processing

This subsection explains the HA Monitor processing flow when servers are terminated. The details of this processing flow depend on whether the servers are used in the server mode or the monitor mode.

The processing flow explained here assumes that the shared resources are disconnected in the same order in which they were connected. For details about the HA Monitor processing that occurs when shared resources are disconnected in the reverse order from which they were connected, see 4.8.7 Processing flow for disconnecting shared resources in the reverse order from which they were connected.

Note: If you want to access shared resources by using a user command, you must disconnect the shared resources in the reverse order from which they were connected. For details about the specification method, see 3.5.5 Specifying the shared resource separation order.

Organization of this subsection

(1) Processing flow for terminating a server (in the server mode)
(2) Processing flow for terminating a server (in the case where the active server is monitored in the monitor mode)
(3) Processing flow for terminating a server (in the case where monitoring is performed in the standby system in the monitor mode)

(1) Processing flow for terminating a server (in the server mode)

In the server mode, there are two types of server termination processing:

Terminating standby servers when active server termination processing is completed
Terminating standby servers when active server termination processing is started

This subsection explains the flow of HA Monitor processing when servers in the server mode are terminated.

(a) Terminating standby servers when active server termination processing is completed

The following figure shows the flow of HA Monitor processing when standby servers are terminated at the time that active server termination processing is completed.

Figure 4‒49: Processing flow for server termination (server mode: terminating standby servers when active server termination processing is completed)

[Figure]

(b) Terminating standby servers when active server termination processing is started

The following figure shows the flow of HA Monitor processing when standby servers are terminated at the time that active server termination processing is started.

Figure 4‒50: Processing flow for server termination (server mode: terminating standby servers when active server termination processing is started)

[Figure]

To Page Top

(2) Processing flow for terminating a server (in the case where the active server is monitored in the monitor mode)

The following figure shows the flow of processing that HA Monitor performs when terminating a server in the case where the active server is monitored in the monitor mode.

Figure 4‒51: Processing flow for terminating a server (in the case where the active server is monitored in the monitor mode)

[Figure]

Note: In the case where APIs are issued from a UAP (when the monitor-mode program management function is used), the processing flow from the beginning of active server termination processing to the completion of active server normal termination processing differs from the flow shown here. For details, see (2) Flow of server termination processing (when UAPs are monitored).

To Page Top

(3) Processing flow for terminating a server (in the case where monitoring is performed in the standby system in the monitor mode)

The following figure shows the flow of processing that HA Monitor performs when terminating a server in the case where monitoring is performed in the standby system in the monitor mode.

Figure 4‒52: Processing flow for terminating a server (in the case where monitoring is performed in the standby system in the monitor mode)

[Figure]

To Page Top