uCosminexus Application Server, Operation, Monitoring, and Linkage Guide
This subsection describes the procedure for stopping the mutual node switching system.
The stopping procedure will be described for the following two cases:
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.
Figure 18-12 Flow for stopping the mutual node switching system
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:
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:
# 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.
# 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.
To end the standby status in the virtual host of the standby node without stopping the virtual host of the executing node:
# monsbystp AP2 |
# monsbystp AP1 |
All Rights Reserved. Copyright (C) 2013, Hitachi, Ltd.