Contents

Port Status - Field Help

Configuration Settings

Edit any of the values on the Content Based Routing Port Status panel and click Update Configuration.

Stale timeout
The number of seconds during which there can be no activity on a connection before that connection is removed. The default is 300.

Weight bound
The weight bound for this port. The default value is 20 and can also be set at the executor and cluster level.

Maximum number of servers
The maximum number of servers for this port. The default value is 32 and can also be set at the executor and cluster levels.

Default sticky time
The sticky time for this port. 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. The default value is 0, meaning that the port is not sticky. Sticky time can also be set at the executor and cluster levels.
Note: Once a client has an affinity record at the port level, all subsequent requests from that client within the sticky time interval will not be analyzed by rules. Port affinity has precedence over checking.



Current Statistics

Cluster address
The IP address of the cluster to which port is defined.

Port number
The number of the port.

Number of servers
The number of servers currently active on the port.

Maximum server weight
The maximum server weight for servers on this port. The weight is based on internal counters in the executor, feedback from the advisors, and feedback from a system-monitoring program such as Metric Server.

Total active connections
The current total number of active connections for this port.

Connections per second
The current number of connections per second for this port.


Lists

List of Servers
The numerical dotted decimal address (such as 9.37.52.11) and weight (such as 10) of the currently active servers. Weights are applied to all servers on a port. Requests will be distributed between servers based on their weights relative to each other. For example, if one server is set to a weight of 10 and the other to 5, the server set to 10 should get twice as many requests as the server set to 5.

List of Rules
The list of rules shows:
  • Rule name - rules that are currently active.
  • Rule priority - the priority assigned to the rule. Lower priority rules are evaluated first. (A rule with a priority of 1 will be evaluated before a rule with a priority of 2.) The first rule that is satisfied will be used. Once a rule has been satisfied, no further rules are evaluated.
  • Rule type - rules types are based on things such as: client IP address, time of day, connections per second for a port, active connections total for a port, content, and always true.

See the Network Dispatcher Administration Guide for more details about rules-based load balancing.