Not specifically network saturation - but something a little more
specific...
Take a look at
http://src.opensolaris.org/source/xref/onnv/onnv-gate/usr/src/uts/common/inet/tcp/tcp_input.c
around line 1362.
1362 if (listener->tcp_conn_req_cnt_q >= listener->tcp_conn_req_max)
{
1363 mutex_exit(&listener->tcp_eager_lock);
1364 TCP_STAT(tcps, tcp_listendrop);
Seems like each time this is true:
listener->tcp_conn_req_cnt_q >= listener->tcp_conn_req_max
we will increment the counter.
I'm expecting this is more about the rate of connection requests to the
system rather than non-specific network saturation (which could manifest
in a variety of ways.).
This blog seems to have some good detail on it:
http://blogs.sun.com/terrygardner/entry/solaris_tcp_ip_parameters_tcp
As does the Solaris tunables guide...
http://docsun.cites.uiuc.edu/sun_docs/C/solaris_9/SUNWaadm/SOLTUNEPARAMREF/p34.html
and ndd -get /dev/tcp can show you the current values.
What problem are you trying to solve? Are you simply trying to
understand the metric, or is there an underlying issue you are
experiencing that's caused you to pick out this metric?
Cheers!
Nathan.
Tony MacDoodle wrote:
Hello,
Would network saturation cause the following:
tcp_listendrop * 625597*
*
*
------ Utilisation ------ ------ Saturation ------
Date Time %CPU %Mem %Disk %Net CPU Mem
Disk Net
Tue Apr 27 17:22:11 2010 38.45 18.28 0.00 191.12 1.18 0.00
0.00 0.00
Tue Apr 27 17:22:16 2010 2.72 18.29 0.00 19.13 0.20 0.00
0.00 0.00
Tue Apr 27 17:22:21 2010 21.98 18.50 0.00 98.57 0.39 0.00
0.00 0.00
*
*
*
*
*
*
------------------------------------------------------------------------
_______________________________________________
ldoms-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
_______________________________________________
ldoms-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/ldoms-discuss
