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
Sending 48 bytes to 192.168.3.2:161
0000: 30 82 00 2C 02 01 00 04 06 70 75 62 6C 69 63 A1 0..,.....public.
0016: 82 00 1D 02 04 6B 75 A2 46 02 01 00 02 01 00 30 .....ku.F......0
0032: 82 00 0D 30 82 00 09 06 05 2B 06 01 02 01 05 00 ...0.....+......
Received 162 bytes from 192.168.3.2:161
0000: 30 82 00 9E 02 01 00 04 06 70 75 62 6C 69 63 A2 0........public.
0016: 82 00 8F 02 04 6B 75 A2 46 02 01 00 02 01 00 30 .....ku.F......0
0032: 82 00 7F 30 82 00 7B 06 08 2B 06 01 02 01 01 01 ...0..{..+......
0048: 00 04 6F 41 50 43 20 45 6D 62 65 64 64 65 64 20 ..oAPC Embedded
0064: 50 6F 77 65 72 4E 65 74 20 53 4E 4D 50 20 41 67 PowerNet SNMP Ag
0080: 65 6E 74 20 28 46 57 20 76 33 2E 30 2E 31 20 53 ent (FW v3.0.1 S
0096: 57 20 76 32 2E 32 2E 34 2E 61 2C 20 48 57 20 42 W v2.2.4.a, HW B
0112: 32 2C 20 4D 4F 44 3A 20 41 50 39 36 30 35 2C 20 2, MOD: AP9605,
0128: 4D 66 67 3A 20 30 33 2F 31 39 2F 31 39 39 38 2C Mfg: 03/19/1998,
0144: 20 53 4E 3A 20 57 41 39 38 31 32 37 34 34 39 36 SN: WA981274496
0160: 31 29 1)
system.sysDescr.0 = APC Embedded PowerNet SNMP Agent (FW v3.0.1 SW
v2.2.4.a, HW B2, MOD: AP9605, Mfg: 03/19/1998, SN: WA9812744961)
Sending 51 bytes to 192.168.3.2:161
0000: 30 82 00 2F 02 01 00 04 06 70 75 62 6C 69 63 A1 0../.....public.
0016: 82 00 20 02 04 6B 75 A2 47 02 01 00 02 01 00 30 .. ..ku.G......0
0032: 82 00 10 30 82 00 0C 06 08 2B 06 01 02 01 01 01 ...0.....+......
0048: 00 05 00 ...
Resending 51 bytes to 192.168.3.2:161
0000: 30 82 00 2F 02 01 00 04 06 70 75 62 6C 69 63 A1 0../.....public.
0016: 82 00 20 02 04 6B 75 A2 47 02 01 00 02 01 00 30 .. ..ku.G......0
0032: 82 00 10 30 82 00 0C 06 08 2B 06 01 02 01 01 01 ...0.....+......
0048: 00 05 00 ...
Resending 51 bytes to 192.168.3.2:161
0000: 30 82 00 2F 02 01 00 04 06 70 75 62 6C 69 63 A1 0../.....public.
0016: 82 00 20 02 04 6B 75 A2 47 02 01 00 02 01 00 30 .. ..ku.G......0
0032: 82 00 10 30 82 00 0C 06 08 2B 06 01 02 01 01 01 ...0.....+......
0048: 00 05 00 ...
Resending 51 bytes to 192.168.3.2:161
0000: 30 82 00 2F 02 01 00 04 06 70 75 62 6C 69 63 A1 0../.....public.
0016: 82 00 20 02 04 6B 75 A2 47 02 01 00 02 01 00 30 .. ..ku.G......0
0032: 82 00 10 30 82 00 0C 06 08 2B 06 01 02 01 01 01 ...0.....+......
0048: 00 05 00 ...
Resending 51 bytes to 192.168.3.2:161
0000: 30 82 00 2F 02 01 00 04 06 70 75 62 6C 69 63 A1 0../.....public.
0016: 82 00 20 02 04 6B 75 A2 47 02 01 00 02 01 00 30 .. ..ku.G......0
0032: 82 00 10 30 82 00 0C 06 08 2B 06 01 02 01 01 01 ...0.....+......
0048: 00 05 00 ...
Resending 51 bytes to 192.168.3.2:161
0000: 30 82 00 2F 02 01 00 04 06 70 75 62 6C 69 63 A1 0../.....public.
0016: 82 00 20 02 04 6B 75 A2 47 02 01 00 02 01 00 30 .. ..ku.G......0
0032: 82 00 10 30 82 00 0C 06 08 2B 06 01 02 01 01 01 ...0.....+......
0048: 00 05 00 ...
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...
Thanks,
Richard
Richard Whittaker on the road or @ work
ICQ UIN 1390720 - You can get ICQ at: http://www.icq.com - Try it today!
WWW Homepage: http://ganges.connections.yk.ca/rwhittak
Work: 867-393-7756
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
