Configurable Parameters

There are a set of configurable parameters for the Oracle Lightweight Availability Collection Tool, which enables you to set default actions based on local site policies. The tool configures itself using the parameters defined in /etc/default/lwact file. The following parameters are configurable:

• LOGDIR parameter

  LOGDIR specifies the path where availability data (hostid.lwact.xml) will be collected. By default, it is collected in /var/log. You can change the value to a different path and the tool will start logging the availability metrics into this new path after the tool is restarted. To retain the availability data collected thus far, you must ensure that the log file is manually copied into the new location; otherwise, the tool will start logging availability data in the new location afresh and the old data will be lost.

  ---

  Note –

  Before you restart the tool, be sure you retain the availability data already collected. To retain this data, manually copy the log file to the new location. If you do not copy the log file, the new data will be logged to the new location, but the old data will not be carried over to this new location when the tool restarts.

  ---

• BACKUP parameter

  BACKUP specifies the path where the Oracle Lightweight Availability Collection Tool will store a backup copy of the log file. By default this entry has the path set to /var/tmp and is commented; therefore, no backup will be stored. If you want a backup, you can un-comment the entry and change the path to your preferred location. The backup file will be found under the path you specify.

• UPDATE parameter

  UPDATE specifies the path where the lwact.update file can be found. By default, the path is /var/tmp. You can modify this path.

  lwact.update is a feature provided by the Oracle Lightweight Availability Collection Tool to auto-update predefined cause codes for any outage. You can use this feature to update a cause code to a single or bulk of hosts for an outage.

  For example, an outage might have occurred on number of hosts within your site due to a power failure. Hence, you might want to update a common cause code across all these hosts for that particular outage. Instead of manually updating the cause code for that event after the outage on each host, you can push this lwact.update file into all these hosts soon after this activity is carried out. The Oracle Lightweight Availability Collection Tool will automatically pick the cause codes mentioned in the lwact.update file and set the cause codes to the outage event accordingly. After completing this update, the file is automatically deleted. By using this feature, you no longer need to manually log into each of the hosts to update the cause code after an outage occurs.

  The structure of the lwact.update file is as follows:

  # This file contains the cause codes for the outage <L1CauseCodeIndex>, <L2CauseCodeIndex>, <L3CauseCodeIndex>

  For example:

  $ cat lwact.update 1,2,7

  Based on the file in this example, after the outage, the tool will set the cause codes as follows: L1=1, L2=2, L3=7

• L1CC, L2CC, L3CC parameters

  The L1CC, L2CC, L3CC enable you to define default cause codes for L1, L2 and L3.

  By default, the Oracle Lightweight Availability Collection Tool logs halt event cause codes as:

  L1=Planned L2=Undefined, L3=Undefined

  By default, it logs the panic event's cause codes as:

  L1=Unplanned L2=Undefined L3=Undefined

  The structure of the L1CC, L2CC, L3CC parameters is as follows:

  L1CC=<L1CauseCodeString> L2CC=<L2CauseCodeString> L3CC=<L3CauseCodeString>

  By default, there are no entries for cause codes in this file. So L1 cause code for halt and panic events are logged as Planned and Unplanned respectively and L2 and L3 cause codes are logged as Undefined. If cause codes are explicitly set for different levels, they override the default cause codes for outage events (both halt and panic). (For specific information about setting cause code values, see Setting Up Cause Codes.)

  ---

  Note –

  If any of the L1CC, L2CC, L3CC values are not valid, then the Oracle Lightweight Availability Collection Tool detects this and logs a corresponding log message in /var/adm/message and sets the invalid cause code entry as Undefined.

  ---

Upon installation, the configurable parameters in the /etc/default/lwact file have the following default values:

LOGDIR=/var/log
#BACKUP=/var/tmp 
UPDATE=/var/tmp

For any changes to take effect, you must restart the Oracle Lightweight Availability Collection Tool.