Port Status - Field Help
Configuration Settings
Edit any of the values on the 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 value for port 21 is 900; the default value for port 23
is 32,000,000. The default value for all other ports is 300 and can also be set at the
executor and cluster levels.
- 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.
- 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
rule affinity.
- Port protocol
- The port protocol. It may be overridden on a per-cluster or per-port basis. Possible
values are TCP, UDP, or both protocols (TCP/UDP) and can also be set
at the executor and cluster levels. The default value is TCP/UDP.
- Cross port affinity (applies to Dispatcher's NAT/NAPT and MAC Based forwarding methods only)
- The default is the port's own port number. To enable cross port affinity,
set the cross port value to a port which:
- shares the same cluster address
- shares the same servers
- has the same (non-zero) sticky time value
- has the same sticky address mask bits value
Cross port affinity is the sticky/affinity feature expanded to cover
across multiple ports. When a client first makes a connection to one of the
ports, the server is selected. When subsequent connections come in from the
same client on the same port or a shared port (cross port), the same server
will be accessed.
- Sticky address mask bits
- The number of high-order bits which can be defined for the client IP address mask.
Possible values are 8, 16, 24 and 32. The default is 32 bits, which disables
the sticky/affinity address masking feature.
Sticky address masking is an affinity feature enhancement to group clients
together based upon common subnet address (that is, common high-order bits
of the IP address). When sticky/affinity address masking is enabled, for all subsequent
connections coming in from the same subnet, the same server will be selected.
- Maximum number of half open connections
- The number of half open connections allowable before an alert signal is passed to indicate a possible
denial of service attack. The default is zero. In order to analyze incoming
requests for half-open connections, this number must be set to an integer greater than zero.
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 running on this 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.
- KBytes transferred per second
- The number of kilobytes being transferred per second on this port.
- Number of half open connections
- The number of half open connections on this port.
- Forwarding Method
- Displays the forwarding method protocols for this port:
- MAC Based forwarding (default)
- NAT/NAPT
- content-based routing
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.
To remove a server, highlight the server in the list and click remove.
- List of Rules
To refresh the list at any time, click refresh.
See the Network Dispatcher Administration Guide for more details about
rules-based load-balancing. You may download or view the Administration Guide from
WebSphere Edgeserver's website
library page.
|