[prev in list] [next in list] [prev in thread] [next in thread] 

List:       net-snmp-bugs
Subject:    [ net-snmp-Bugs-494630 ] tcp.tcp.CurrEstab.0 wrong in FreeBSD and elsewhere
From:       "SourceForge.net" <noreply () sourceforge ! net>
Date:       2005-10-18 23:18:58
Message-ID: E1ES0jS-0004Qy-I7 () sc8-sf-web2 ! sourceforge ! net
[Download RAW message or body]

Bugs item #494630, was opened at 2001-12-18 16:52
Message generated for change (Comment added) made by tanders
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=112694&aid=494630&group_id=12694

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: agent
Group: freeBSD
>Status: Pending
Resolution: None
Priority: 7
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Nobody/Anonymous (nobody)
Summary: tcp.tcp.CurrEstab.0 wrong in FreeBSD and elsewhere

Initial Comment:
the value of tcp.tcp.CurrEstab.0 is 0 (zero) in FreeBSD
4.4 (also cheched on 4.1 version). 

----------------------------------------------------------------------

>Comment By: Thomas Anders (tanders)
Date: 2005-10-19 01:18

Message:
Logged In: YES 
user_id=848638

Can you please retest with a recent version, preferrably
5.2.2.rc1 or later?
TCP-MIB::tcpCurrEstab.0 has been reported to work fine on
FreeBSD (2005-09-25 on net-snmp-coders for 5.2.2.preX).

----------------------------------------------------------------------

Comment By: Michael J. Slifcak (slif)
Date: 2004-06-28 18:42

Message:
Logged In: YES 
user_id=88697

at 28-Jun-2004
freebsd 4.x/5.x , net-snmp 5.1 patch  and HEAD branches
    first walk CurrEstab is still zero
    second walk CurrEstab is correct

----------------------------------------------------------------------

Comment By: Michael J. Slifcak (slif)
Date: 2004-06-23 15:43

Message:
Logged In: YES 
user_id=88697

at 23-Jun-2004
freebsd 4.x/5.x , net-snmp 5.1 patch
    first walk CurrEstab is still zero
    second walk CurrEstab is correct

freebsd 4.x/5.x, net-snmp main branch
    CurrEstab remains zero until invoking snmpwalk tcpConnTable


----------------------------------------------------------------------

Comment By: Michael J. Slifcak (slif)
Date: 2004-06-04 15:33

Message:
Logged In: YES 
user_id=88697

Oops! 4.x agent always shows tcpCurrEstab as zero.


----------------------------------------------------------------------

Comment By: Michael J. Slifcak (slif)
Date: 2004-06-03 22:52

Message:
Logged In: YES 
user_id=88697

This problem is not unique to FreeBSD, so the
Summary line was changed.

The 4.x agent does not exhibit this problem.


The 5.x agent relies on previous access to tcpConnectTable,
and simply returns the number of established or "close wait"
connections.  
However, as the tcpCurrEstab object is lexicographically ordered
so that it is seen before the tcp ConnectTable is seen,
the connection count information is not valid.
Until some one has time to address this,
You can get best results by scanning the tcpConnectTable first,
and then read the tcpCurrEstab object to obtain the
correct value.


----------------------------------------------------------------------

Comment By: John Naylon (jbpn)
Date: 2001-12-18 16:56

Message:
Logged In: YES 
user_id=93926

What version of the package are you using?

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=112694&aid=494630&group_id=12694


-------------------------------------------------------
This SF.Net email is sponsored by:
Power Architecture Resource Center: Free content, downloads, discussions,
and more. http://solutions.newsforge.com/ibmarch.tmpl
_______________________________________________
Net-snmp-bugs mailing list
Net-snmp-bugs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-bugs
[prev in list] [next in list] [prev in thread] [next in thread]