18.7.2 Stopping the mutual node switching system
This subsection describes the procedure for stopping the mutual node switching system.
The stopping procedure will be described for the following two cases:
-
When stopping the virtual hosts of both the executing node and the standby node
-
When stopping only the virtual host of the standby node
- Organization of this subsection
(1) When stopping the virtual hosts of both the executing node and the standby node
The procedure for stopping the virtual hosts of both the executing node and standby node will be described below.
The following figure shows the flow for stopping the mutual node switching system when the virtual hosts of both the executing node and standby node are stopped.
|
- Reference note
-
The virtual host 1 and virtual host 2 can be stopped in any order. This manual describes the procedure of stopping in the order of virtual host 1 and virtual host 2.
Stop all the virtual hosts, and then stop the Management Server for the hosts of Application Server 1 and Application Server 2.
For steps 1 and 2 in the figure for stopping Management Server, see the following manuals:
-
In a system executing J2EE applications
See 4.1.3 Procedure for stopping a system in the uCosminexus Application Server Management Portal User Guide.
-
In a system executing batch applications
See 6.1.3 Procedure for stopping a system in the uCosminexus Application Server Management Portal User Guide.
Note that if auto-stop settings are specified, the Management Server and Administration Agent also stop while the host stops, and therefore, you can omit the stages 1 and 2. For details on how to stop the systems, see 2.6 Settings for starting and stopping the system.
The procedure for stopping the virtual host shown in the figure is described below. To stop the virtual host in the hosts of Application Server 1 and Application Server 2:
-
To stop the virtual host in Application Server 1
-
Run the monend command in Application Server 1 to stop the virtual host 1 of the executing node.
# monend AP1
As a result, the executing node 1 (virtual host 1) of Application Server 1 will stop. Also, stop instruction is automatically sent to the standby node by the HA monitor and the standby node 1 (virtual host 1) of Application Server 2 also stops.
-
-
To stop the virtual host in Application Server 2
-
Run the monend command in Application Server 2 to stop the virtual host 2 of the executing node.
# monend AP2
As a result, the executing node 2 (virtual host 2) of Application Server 2 will stop. Also, stop instruction is automatically sent to the standby node by the HA monitor and the standby node 2 (virtual host 2) of Application Server 1 also stops.
-
(2) When stopping only the virtual host of the standby node
To end the standby status in the virtual host of the standby node without stopping the virtual host of the executing node:
-
To end the standby status in the standby node 2 (virtual host 2) of Application Server 1
Run the following command in the host of Application Server 1:
# monsbystp AP2
-
To end the standby status in the standby node 1 (virtual host 1) of Application Server 2
Run the following command in the host of Application Server 2:
# monsbystp AP1