Server Status - Field Help
Current Statistics
To refresh statistics at any time, click Refresh Statistics.
- Server
- The server is the unique IP address of the TCP server machine as either a
symbolic name or in IP address format. Or, if you use a
unique name that does not resolve to an IP address you must provide the server
address.
- Server address
- The unique IP address of the TCP server machine as either a host name or in
IP address format. If the server is unresolvable you must provide the address
of the physical server machine
- Port number
- The number of the port to which this server is defined.
- Cluster
- The cluster name or address to which clients connect. The cluster value is either a
symbolic name or in dotted-decimal format. A cluster value of 0.0.0.0 can be used to
specify a wildcard cluster. Please refer to the "Use a wildcard cluster to combine server
configurations" section in the
Load Balancer Administration Guide
for more information.
Note: Supported translations of the Load Balancer Administration Guide can be found on the
WebSphere Application Server - Edge Component Information Center Web site.
- Cluster Address
- The address to which clients connect. The cluster address can be either the
dotted-decimal IP address or the host name of the machine. If the cluster value is not resolvable,
you must provide this IP address of the physical machine.
- Quiesced status
- Specifies whether or not this server has been quiesced. If the server has been quiesced,
then no new connections from a different client can be sent.
- Neighbor status
- Neighbor discovery is the process used to determine the MAC address of the server.
An ICMP packet is generated, and from the response, Load Balancer determines the MAC address of the
server.
The possible status for the neighbor discovery process are:
- OK : The neighbor state for this server is okay.
- Trying : Attempting to establish the neighbor state for this server.
- Unavailable - error : The neighbor state is unavailable because the executor encountered an error during the
calculation process.
- Unavailable - no interface : There was an error when accessing the interface for neighbor discovery.
- Unavailable - server down : Load Balancer did not get a response from the server.
- Total packets received
- Total number of packets received by the server.
- Packets forwarded
- Total number of packets forwarded to the server.
- Packets generated
- Total number of packets generated by Load Balancer for the server.
These packets include ICMP packets that
Load Balancer sends out to request information.
Generated packets are packets that are not received from a client.
- Packets discarded
- Total number of packets that are forwarded to the server but are discarded.
- Packets processed locally
- Total number of packets to be processed locally by Load Balancer.
- Packets with errors
- Total number of packets discarded due to packet error. For example, if the packet headers are too
short, the packets are discarded.
- Kbytes transferred per second
- The number of kilobytes transferred in a one second interval
- Connections per second
- The current number of connections per second on this server as calculated by the manager.
Note: The manager must be running.
- Total connections
- The total number of connections on this server.
- Pre-established connections
- TCP connections for which an initial packet has been received,
but the connection is not yet fully established.
- Active connections
- The number of connections that are in the active state.
- Finished connections
- The number of connections that are in the FIN state. A client sends a FIN packet
to let the server know that the transaction is finished.
Configuration Settings
Edit any of the values on the Configuration Settings tab and click Update Configuration.
- Current status
- The current status of the server. Possible values are:
- Server weight
- The weight for this server that is used in load balancing between servers on
the same port. The default value is 10.
Note: You will be unable to update the server weight while the
manager is running and the server "fixed weight" value is "no" (the default).
If you want to set the server weight and do not want the manager to update the
server weight you set, then set the "fixed weight" value to "yes".
- Fixed weight
- Indicates whether the server weight should stay fixed when
the manager is running. The default is NO. When fixed weight is specified as
NO, the manager will adjust the weight for this
server for optimal performance. If fixed weight has been specified as
YES, the server weight is 'fixed' and will not be updated by the manager.
- HTTP Advisor Request
- This field holds the string which will be used by the HTTP advisor to query the health of
the servers. This value defaults to "Head/HTTP/1.0". It is present for all servers, but it
will only be valid for servers which are advised upon by the HTTP advisor.
Note: This field is disabled until an HTTP advisor is started.
- HTTP Advisor Response
- This field holds the string which will be used by the HTTP advisor to compare to the real
response that is received from the server. This string value defaults to "null".
Note: This field is only available after you have started an HTTP advisor.
Lists
- List of server metrics
- A list of system metrics which have been added to the server and the results
of executing those metrics on the server.
To refresh the list at any time, click Refresh Statistics.
|