On Tue, 9 May 2000, Richard Whittaker wrote:
> At 09:52 PM 5/9/2000 +0200, you wrote:
>
>
> >On Mon, May 08, 2000 at 01:48:13PM -0700, Richard Whittaker wrote:
> > > Hi all be warned first this is a very LONG message!...
> >You unfortunately forgot to include the essential information:
> >a tcpdump trace of a failed SNMP access.
>
> Well, I don't have a TCPDump trace, but I do have the output of an snmpwalk
> -d, etc, etc...
>
> nile:/usr/local/apache/htdocs# snmpwalk -d apc1400 public
>
<snip>
>
> Timeout: No Response from apc1400
>
> Notice how the first query works, but subsequent ones don't?... Now, this
> would normally point to the SNMP adapter as the culprit, HOWEVER, as I
> stated before, I have a WinDoze machine that works perfectly, and can pull
> the entire MIB tree. Also, it makes no sense why a WinDoze machine can ping
> the SNMP adapter, and none of the Linux machines, regardless of their
> disposition on the network... I'll try to get a TCPDump this evening...
Not sure if this relates or not. I have a number of Alpha's running linux
and I have found that I cannot the the latest snmpd to work corrcetly(at
least I think it is an snmpd problem) What I think I have traced it to is
the fact that some of the counters in the alpha are defined as "long".
This means that they are 64 bits long. I can read the data from the
systems up to the point where I try and get the value of one of these
counters then I get a timeout error.
Alvin Starr || voice: (416)585-9971
Interlink Connectivity || fax: (416)585-9974
[EMAIL PROTECTED] ||
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
