Contents

Executor Status - Field Help

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

Nonforwarding address

The address of this machine in either dotted decimal or host name format. Any packet sent to this address will not be forwarded by the Dispatcher component.

Maximum number of clusters

The maximum number of clusters for load balancing. The default value is 100.

FIN count

The maximum number of finished connections before the Dispatcher garbage collector will clear the memory reserved for those connections. The default value is 4000.

FIN timeout

The maximum number of seconds that connections have been finished before the Dispatcher garbage collector will clear the memory reserved for those connections. The default value is 60.

Wide port number

A port number that is unused on all of the Dispatcher machines in a wide area network. The Dispatcher machines use this port to exchange wide area information.

Default maximum ports per cluster

The default maximum number of ports per cluster. This may be overridden on a per-cluster basis. The default value is 8.

Bandwidth to be shared

The level of bandwidth (kilobytes per second) to be shared at the cluster or executor level. Sharing bandwidth at the cluster level allows a port (or ports) to share a maximum amount of bandwidth across several ports (applications/protocols) within the same cluster. Sharing bandwidth at the executor level allows a cluster (or clusters) within the entire Dispatcher configuration to share a maximum amount of bandwidth. The default value is 0. If the value is zero, then bandwidth cannot be shared.

Note: You should specify a maximum shared bandwidth value that does not exceed the total bandwidth (total server capacity) available.

Default maximum servers per port

The default maximum number of servers per port. It may be overridden on a per-cluster or per-port basis. The default value is 32.

Default port stale timeout

The default number of seconds during which there can be no activity on a connection before that connection is removed. The default for port 21 is 900; the default for port 23 is 32,000,000. The default for all other ports is 300. It may be overridden on a per-cluster or per-port basis.

Default sticky time

The default port sticky time for all future clusters. Sticky time is used to create an affinity relationship between a client and a specific server. After the sticky time has been exceeded, the client may be sent to a server different from the previous. Default port sticky time may be overridden on a per-cluster or per-port basis. The default value is 0, meaning that the port is not sticky.

Default port weight bound

The default weight bound for all future ports. It may be overridden on a per-cluster or per-port basis. The default value is 20.

Default port protocol

The default port type for all future ports. It may be overridden on a per-cluster or per-port basis. Possible values are TCP, UDP, or both protocols (TCP/UDP). The default value is TCP/UDP.



The following current statistics are displayed on the Executor Status panel:

Total received since started

Total number of packets received by the executor since it was started.

Sent to nonforwarding address

Total number of packets sent to the nonforwarding address since the executor started.

Processed locally on this machine

Total number of packets, not for the nonforwarding address, or any cluster, but to be processed locally, by the Dispatcher machine.

Sent to collocated server

Total number of packets explicitly forwarded to a server collocated on the Dispatcher machine.

Forwarded to any cluster

Total number of packets forwarded to any cluster.

Not addressed to active cluster/port

Total number of packets not addressed to any active cluster and port.

KBytes transferred per second

The number of kilobytes transferred over a one second interval.

Connections per second

The current number of connections per second.

Packet error statistics

Headers too short

Total number of packets discarded by the executor because the packet headers were too short.

No port or servers

Total number of packets discarded by the executor which were forwarded to a cluster, but were discarded because either the port:

  • Did not exist
  • Existed but had no servers configured to it

Network adapter failure

Total number of packets not forwarded because of a network adapter failure.

Forwarding errors

Total number of packets with forwarding errors since the executor started. Examples of forwarding errors are:

  • There was an error extracting an encapsulated packet which came in from a wide area network Dispatcher
  • An attempt to forward the packet to either a local or remote server failed



You can refresh the current high availability state table and statistics displayed on the Executor Status panel. Also displayed are a current list of heartbeats and reach targets.

High availability state table:

Primary Host

The address of the primary host in dotted decimal format.

Cluster Address

The cluster address of the primary host in dotted decimal format.

State

The current state of the primary host machine. Possible values are:

  • Active--this machine is load balancing packets
  • Standby--this machine is not load balancing packets; it is monitoring the state of an active Dispatcher
  • Idle--this machine is load balancing packets, and is not trying to establish contact with a partner Dispatcher
  • Listen--this machine is listening for communication from a backup Network Dispatcher

Sub-state

The current sub-state of this machine; only applies if you have started to configure high availability. Possible values are:

  • Synchronized--this machine has established contact with another Dispatcher
  • Not Synchronized--this machine is trying to establish contact with another Dispatcher, but has not yet succeeded

Port number

The number of the port on which this machine is passing back and forth heartbeat messages with its partner.

Role

The current role of this machine. Possible values are:

  • Primary
  • Backup
  • Both (mutual high availability feature)

Recovery strategy

The current recovery strategy for this machine. Possible values are:

  • Auto--an automatic recovery strategy in which the primary machine will resume load balancing packets as soon as it comes back into service
  • Manual--a manual recovery strategy in which the primary machine does not resume load balancing packets until you tell it to takeover