Local environment variable settings can vary from node to node. The following list describes the local environment variables for RMS:
Possible values: 0, 1
Default: 1 (normal processing of AutoStartUp attribute)
Controls the action of the AutoStartUp attribute for all userApplication objects on the local node. If set to 1 (the default value) the automatic startup of each userApplication is determined by its AutoStartUp attribute (see the "D.1 Attributes available to the user"). If set to 0, the AutoStartUp attribute is ignored and no automatic startup occurs. HV_AUTOSTARTUP can be set in the Cluster Admin Tools menu or by using the hvsetenv command; in either case, the change does not take effect until the next RMS startup.
Possible values: 5 - MAXINT
Default: 30 (seconds). Users do not normally need to change the default setting.
The maximum time (in seconds) that the heartbeat from a node is not received before the base monitor assumes the connection to that node has been lost and starts the UDP heartbeat recovery timer.
Input values less than 5 are converted internally to 5.
Possible values: on, off
Default: off
Determines whether the current log files in the RELIANT_LOG_PATH directory will be deleted when the percentage of used space on the file system containing RELIANT_LOG_PATH is greater than or equal to HV_LOG_ACTION_THRESHOLD. See HV_LOG_ACTION_THRESHOLD for more information.
Possible values: 0 - MAXINT
Default: 20,000,000 (bytes)
Prevents the unlimited growth of the temporary file that RMS uses to supply hvdisp with configuration data and subsequent configuration and state changes. The value of this variable is the maximum size in bytes of the temporary file <RELIANT_PATH>/locks/.rms.<process id of the hvdisp process>.
Possible values: 0 - 99
Default: 30
Defines the maximum number of scripts that RMS can execute at one time. The default (30) is sufficient in most cases.
Possible values: 0, 1
Default: 0
If set to 1, the base monitor process and any memory it allocates will be locked in memory. If set to 0 (the default), the base monitor may be swapped out.
Possible values: 0, 1
Default: 1 (start RMS in the rc script)
Determines if RMS is started in the rc script. If set to 1 (the default value), RMS is started automatically at system boot time. If set to 0, RMS must be started manually. HV_RCSTART can be set in the Cluster Admin Tools menu or by using the hvsetenv command. (Prerequisite for rc start: CONFIG.rms exists and contains a valid entry.)
Possible values: 0 - 99
Default: 50
Defines the real time priority for the RMS base monitor and its detectors. Caution should be used when adjusting this variable. High settings can prevent other OS real-time processes from getting their processor time slice. Low settings can prevent the RMS base monitor from reacting to detector reports and from performing requests from command line utilities.
This variable is processed only on Solaris platforms. It has no effect on Linux platforms.
Possible values: 0, 1
Default: 0
Controls debugging output from RMS scripts. If this variable is set to 1, it overrides the setting for scripts that are generated and managed by the Wizard Tools, causing them to write detailed runtime information about the commands that are executed to the RMS switchlog file. The type of information logged may vary according to the script. This setting applies only to those scripts provided with PRIMECLUSTER products. To disable script debug message logging, delete the HV_SCRIPTS_DEBUG entry or set HV_SCRIPTS_DEBUG=0 in hvenv.local.
Note
When this variable appears in hvenv.local, RMS adds it to the script environment but otherwise makes no attempt to process it. Therefore, it is not reported in the Cluster Admin GUI or in 'hvdisp ENVL' output.
Possible values: 0, 1
Default: 1 (in hvenv)
Controls output to the system log from the RMS base monitor. RMS always records RMS ERROR, FATAL ERROR, WARNING, and NOTICE messages in the RMS switchlog file. By default, these messages are duplicated in the system log file /var/adm/messages (Solaris) or /var/log/messages (Linux). To disable RMS messages in the system log, set HV_SYSLOG_USE=0 in hvenv.local.
Note
It is recommended for Linux to change this variable to 0. If this variable is set to 1 on Linux, under a high load on the system, the system log output will hang due to the performance limit of the system log processing by OS. In this case, RMS may not respond to any heartbeat from other node.
Possible values: 0, 1
Default: 0
Specifies enabling or disabling of function which transmits the ARP packets of takeover IP address from the switching destination node periodically (advertises the communication routes of communication devices) if a node is switched by the I/O fencing in the VMware environment using the I/O fencing function.
If setting to 1, the function is enabled. After this setting is performed, the switching destination node transmits the ARP packets in 60-second cycle. If any of the following conditions are met, the ARP packet transmission ends.
The ARP packets are transmitted in the times specified by the RMS environment variable HV_VM_IP_ADVERTISE_COUNT (for about four hours by default).
The panic switching source node is restarted by the I/O fencing function and CF is started.
The userApplication Offline process is performed in the switching destination node.
If setting to 0, the function is disabled.
Note
When switching userApplication, the communication route to the takeover IP address is updated to the switching destination node in the course of Gls resource or takeover network resource Online process. However, if the panic process on the switching source node is delayed due to OS hang, etc., the communication route may return to the switching source node. This function is enabled when the communication route of takeover IP address returns to the switching source node, the communication route can be re-updated to the switching destination node in a short time.
In any one of the following cases, the function is not enabled even it is set:
Using IPv6 address as the takeover IP address
Not registering Gls resource or the takeover network resource to userApplication
Possible values: valid times
Default: 240 (times)
In the VMware environment using the I/O fencing function, when using the function which transmits the ARP packets of takeover IP address from the switching destination node, the ARP packet transmission times in a 60-second cycle can be specified by this environment variable.
If setting to 0, the restriction of transmission times is eliminated and the ARP packets continue being sent.
Possible values: valid name
Default: <nodename>RMS
The name of the local node in the RMS cluster. The default value of this variable is the node name with an RMS suffix (for example: shasta1RMS), as generated by the following command:
export RELIANT_HOSTNAME=`cftool -l 2>/dev/null | \ tail -1 | cut -f1 -d" "`RMS
If this preset value is not suitable, it must be modified accordingly on all the nodes in the cluster.
The specified cluster node name must correspond to the SysNode name in the <configname>.us configuration file. The node name determines the IP address that RMS uses for establishing contact with this node.
Possible values: any executable
Default: <RELIANT_PATH>/bin/InitScript
Specifies an initialization script to be run by RMS when the system is started. This script is run before any other processes are activated. It is a global script that is run once on every cluster node on which it is defined.
Possible values: any valid path
Default : <RELIANT_PATH>/build
Defines where RMS searches at start time for the configuration files.
Possible values: 0 - MAXINT
Default: 300 (seconds)
Specifies the global period (in seconds) within which all RMS scripts must be terminated. If a specific script cannot be terminated within the defined period, it is assumed to have failed and RMS begins appropriate processing for a script failure.
If this value is too low, error conditions will be produced unnecessarily, and it may not be possible for the applications to go online or offline. An excessively high value is unsuitable because RMS will wait for this period to expire before assuming that the script has failed.
In case the global setting is not appropriate for all objects monitored by RMS, this global value can be overridden by an object-specific setting of the ScriptTimeout attribute.
