Contents

Manager Status - Field Help

Edit any of the following configuration settings on the Manager Status panel and click Update Configuration.

Proportion given to active connections

A number from 0-100 representing the proportion of weight to be given to the active connections. The default value is 50. The weight of the active connections, plus the weight of new connections, plus the weight of the advisor information, plus the weight of the system monitoring program information must total 100.

Proportion given to new connections

A number from 0-100 representing the proportion of weight to be given to the new connections. The default value is 50. The weight of the active connections, plus the weight of new connections, plus the weight of the advisor information, plus the weight of the system monitoring program information must total 100.

Proportion given specific to the port

A number from 0-100 representing the proportion of weight to be given to the information coming from an advisor about a port. The default value is 0. The weight of the active connections, plus the weight of new connections, plus the weight of the advisor information, plus the weight of the system monitoring program information must total 100.

Proportion given to system metrics

A number from 0-100 representing the proportion of weight to be given to the information from the system metrics, such as from ISS. The default value is 0. The weight of the active connections, plus the weight of new connections, plus the weight of the advisor information, plus the weight of the system monitoring program information must total 100.

Sum of Proportions

The sum of the above proportions. This total must equal 100.

Sensitivity level

A number from 0 to 100 to be used as the weight percentage in setting the minimum sensitivity to weights update. This setting defines when the manager should change its weighting for the server based on external information. The default of 5 creates a minimum sensitivity of 5%.

Smoothing index

A positive floating point number representing an index that smooths the variations in weight when load balancing. The default value is 1.5.

Server monitor agent script

The command which the Server monitor agent (SMA) will issue on the server machines. Value for 'Proportion given to system metrics' must be nonzero to utilize SMA. Two SMA scripts are provided: cpuload (default) returns the percentage of cpu in use, and memload returns the percentage of memory in use. Optionally, a custom script name can be entered in the text entry field.

NOTE: SMA is a system monitor agent which is supported only on a Network Dispatcher machine running on Red Hat Linux platform. All server machines must be on a Linux platform.

Weights refresh cycle

A positive number representing the number of intervals before querying the executor for a refresh of information about new and active connections. The default value is 2.

Update interval

A positive number representing in seconds how often the manager will update weights of the servers to the executor, updating the criteria that the executor uses to load balance client requests. The default value is 2.

Reach update interval (seconds)

A positive number representing the number of seconds between attempts to reach targets in the configuration. The default value is 7.

Manager logging level

The level at which the manager logs its activities: none - 0, minimal - 1, basic - 2, moderate - 3, advanced - 4, verbose - 5. The default is minimal.

Maximum manager log size

A maximum number of bytes to be logged in the manager log file. The default value is unlimited.

Reach logging level

The level at which the manager logs the Reach activities: none - 0, minimal - 1, basic - 2, moderate - 3, advanced - 4, verbose - 5. The default is minimal.

Maximum reach log size (bytes)

An integer representing the maximum number of bytes that will be logged by the reach advisor. The default value is Unlimited.

Binary logging interval (seconds)

The interval, in seconds, of how often information is written to the binary logs. The binary logging feature allows server information to be stored in binary log files for each server defined in the configuration. The manager will send server information to the log server every manager interval. The information will be written to the logs only if the specified log interval seconds have elapsed since the last record was written to the log. Default binary logging interval is 60. The following information is stored in the binary log for each server:

  • cluster address
  • port number
  • server address
  • server weight
  • server total connections
  • server active connections
  • server port load
  • server system load

NOTE: There is some interaction between the settings of the manager interval and the log interval. Since the log server will be provided with information no faster than manager interval seconds, setting the log interval less than the manager interval effectively sets it to the same as the manager interval.

Time until binary log overwritten (hours)

How long, in hours, log files are kept. Log files older than the retention hours specified will be overwritten. The default value is 24.



The following current statistics are also displayed on the Manager Status panel:

Metric port

The number of the port on which a system-monitoring program, such as ISS or work load manager (WLM), will report system loads. The default value is 10004 for Dispatcher, and 10003 for CBR.

Log filename

The name of the manager log file.

Binary logging

Status for binary log setting.



List of Advisors

The currently active advisor names and their port numbers are listed.