Re: Issue with net-snmp as agent - tcpConnState table incomplete

2009-11-16 Thread Dave Shield
2009/11/16 Simon Helson : > However, there is a difference: > > host001:~# netstat -lntp |grep 48109 > tcp        0      0 0.0.0.0:48109               0.0.0.0:* >     LISTEN      2220/httpd-api-gw > > host002:~# netstat -lntp |grep 48109 > tcp        0      0 :::48109                    :::* >    

Re: Issue with net-snmp as agent - tcpConnState table incomplete

2009-11-16 Thread Simon Helson
(fixed from address to stop list complaining about non-member posts) > >> the output of the second snmpwalk command (from host002) is below - >> just to show that it's not listing the first N ports, it seems to be a >> random selection: > > Compare these results with the netstat output. > What do

Re: Issue with net-snmp as agent - tcpConnState table incomplete

2009-11-16 Thread Dave Shield
> Is there a config setting somewhere that limits the amount of rows > returned by net_snmp that I'm missing? I've been hunting and can't > find anything. No. > the output of the second snmpwalk command (from host002) is below - > just to show that it's not listing the first N ports, it seems t

Issue with net-snmp as agent - tcpConnState table incomplete

2009-11-16 Thread Simon Helson
Hoping someone on here has seen this before and can help.. I have two hosts, both running net-snmp as an agent, versions as below: net-snmp-5.3.2.2-5.el5 net-snmp-libs-5.3.2.2-5.el5 Configurations are identical from what I can see, however if I query the tcpConnState table, one server gives me t