17.7.7 Server-compliant environment settings
In the server-compliant environment settings of the HA monitor, define the environment for the executing server and the standby
server to be operated on the node.
You define the server-compliant environment for the 1-to-1 node switching of the Management Server in the definition file
named servers. The following table lists the contents to be set up in the server-compliant environment settings:
Table 17‒3: Contents to be set up in the server-compliant environment settings (in 1-to-1 node switching of the management server)
Operand
|
Setting contents
|
name
|
Specify the shell script file for starting the Management Server.
Example specification: /home/manager/hamon/bin/manager_mngsvr_start.sh
|
alias
|
Specify the server identification name. Specify the same name in the active node and the spare node.
Example specification: CMS
|
acttype
|
Specify the server starting method. Specify 'monitor' since the server is started using the HA monitor command.
|
termcommand
|
Specify the shell script file for stopping the management server.
Example specification: /home/manager/hamon/bin/manager_mngsvr_stop.sh
|
initial
|
Specify the server startup status.
-
For the active node
Specify 'online'.
-
For the spare node
Specify 'standby'.
|
disk
|
Specify the name of the character type special file for the shared disk device.
Example specification: /dev/vg00
|
lan_updown
|
Specify whether to use the LAN status setup files. Specify use since the LAN status setup files are used here.
|
fs_name
|
Specify the absolute path name of the logical volume corresponding to the switched file system. Note that this setting is
required only when $TPFS is used in the UNIX file.
Example specification: /dev/rdisk0
|
fs_mount_dir
|
Specify the absolute path name of the directory to mount the switched file system. Note that this setting is required only
when $TPFS is used in the UNIX file.
Example of specification: /hamon
|
patrolcommand
|
Specify the shell script file for monitoring the Management Server process.
Example specification: /home/manager/hamon/bin/manager_mngsvr_monitor.sh
|
servexec_retry
|
Specify the frequency of retrying when failure is detected. Specify 0 since the node is switched without retrying when failure occurs.
|
waitserv_exec
|
Specify whether to wait for the execution of the start command to finish when executing the start completion process of the
management server. Specify yes since the server waits for the execution to finish.
|
The examples of the servers file are described below:
- Example of servers file (in the active node)
-
An example of the servers file for the active node is as follows:
server name /home/manager/hamon/bin/manager_mngsvr_start.sh,
alias CMS,
acttype monitor,
termcommand /home/manager/hamon/bin/manager_mngsvr_stop.sh,
initial online,
disk /dev/vg00,
lan_updown use,
fs_name /dev/rdisk0,
fs_mount_dir /hamon,
patrolcommand /home/manager/hamon/bin/manager_mngsvr_monitor.sh,
servexec_retry 0,
waitserv_exec yes;
- Example of servers file (in the spare node)
-
An example of the servers file for the spare node is as follows:
server name /home/manager/hamon/bin/manager_mngsvr_start.sh,
alias CMS,
acttype monitor,
termcommand /home/manager/hamon/bin/manager_mngsvr_stop.sh,
initial standby,
disk /dev/vg00,
lan_updown use,
fs_name /dev/rdisk0,
fs_mount_dir /hamon,
patrolcommand /home/manager/hamon/bin/manager_mngsvr_monitor.sh,
servexec_retry 0,
waitserv_exec yes;
For details on the server-compliant environment settings, see the manual Reliable System Monitoring Functionality HA Monitor.
To Page Top