On Thu, 1 Jul 2010, Charlie Brady wrote:
> I'm trying to troubleshoot a problem with lost network traffic within a
> cluster. The hardware is HP DL380 with BCM5708 NICs. The only abnormality
> I've spotted is a high number in the ex_filtered_packets statistic.
I forgot to something else unusual too. We are running mrtg on the two
nodes, and snmpd. mrtg is collecting NIC statistics via snmp, and
reporting timeouts sporadically. Since I expect UDP traffic over loopback
to be reliable, I suspect the timeouts are due to delays in snmpd reading
the interface stats.
May 24 22:30:11 vmnode1 crond mrtg: SNMP Error:
May 24 22:30:11 vmnode1 crond mrtg: no response received
May 24 22:30:11 vmnode1 crond mrtg: SNMPv1_Session (remote host:
"localhost" [127.0.0.1].161)
May 24 22:30:11 vmnode1 crond mrtg: community: "public"
May 24 22:30:11 vmnode1 crond mrtg: request ID:
1038152925
May 24 22:30:11 vmnode1 crond mrtg: PDU bufsize: 8000
bytes
May 24 22:30:11 vmnode1 crond mrtg: timeout: 2s
May 24 22:30:11 vmnode1 crond mrtg: retries: 5
May 24 22:30:11 vmnode1 crond mrtg: backoff: 1)
May 24 22:30:11 vmnode1 crond mrtg: at /usr/bin/../lib/mrtg2/SNMP_util.pm
line 490
May 24 22:30:11 vmnode1 crond mrtg: SNMPGET Problem for ifInOctets.4
ifOutOctets.4 sysUptime sysName on public@localhost::::::v4only
May 24 22:30:11 vmnode1 crond mrtg: at /usr/bin/mrtg line 2035
May 24 22:30:11 vmnode1 crond mrtg: Monday, 24 May 2010 at 22:30: WARNING:
skipping because at least the query for ifInOctets.4 on localhost did not
succeed
May 24 22:30:11 vmnode1 crond mrtg: Monday, 24 May 2010 at 22:30: WARNING:
no data for ifInOctets&ifOutOctets:public@localhost. Skipping further
queries for Host localhost in this round.
May 24 22:30:11 vmnode1 crond mrtg: Monday, 24 May 2010 at 22:30: ERROR:
Target[bond0][_IN_] ' $target->[0]{$mode} ' did not eval into defined data
May 24 22:30:11 vmnode1 crond mrtg: Monday, 24 May 2010 at 22:30: ERROR:
Target[bond0][_OUT_] ' $target->[0]{$mode} ' did not eval into defined
data
Charlie
--
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
