Hi, I have installed net-snmp 5.1.2Sa (from SCO Skunkware) as a replacement for the limited SNMP tools (eg getone, getmany, trap_rece etc) shipped with SCO OSR 5.0.7. I have set up a test system using the SCO server and a Cisco 2950 (with SNMP packet debugging enabled).
The SCO command `getone` works without any problems. The command and response are shown below: getone 192.168.1.5 public sysDescr.0 Name: sysDescr.0 Value: Cisco Internetwork Operating System Software IOS (tm) C2950 Software (C2950-I6Q4L2-M), Version 12.1(19)EA1c, RELEASE SOFTWARE (fc2) Copyright (c) 1986-2004 by cisco Systems, Inc. Compiled Mon 02-Feb-04 23:29 by yenanh However, the net-snmp command `snmpget` on the same server results in a timeout, ie snmpget -v1 -c public -d -Lo 192.168.1.5 sysDescr.0 Sending 43 bytes to 192.168.1.5 0000: 30 29 02 01 00 04 06 70 75 62 6C 69 63 A0 1C 02 0).....public... 0016: 04 40 3D BE 72 02 01 00 02 01 00 30 0E 30 0C 06 [EMAIL PROTECTED] 0032: 08 2B 06 01 02 01 01 01 00 05 00 .+......... .... .... Resending 43 bytes to 192.168.1.5 0000: 30 29 02 01 00 04 06 70 75 62 6C 69 63 A0 1C 02 0).....public... 0016: 04 6C 96 8F EA 02 01 00 02 01 00 30 0E 30 0C 06 .l.........0.0.. 0032: 08 2B 06 01 02 01 01 01 00 05 00 .+......... Timeout: No Response from 192.168.1.5. The debug log on the Cisco switch shows it receiving and replying to the SNMP requests sent by `smpget` and `getone` commands, ie 4d01h: SNMP: Packet received via UDP from 192.168.1.21 on Vlan1 4d01h: SNMP: Get request, reqid 1821806570, errstat 0, erridx 0 system.1.0 = NULL TYPE/VALUE 4d01h: SNMP: Response, reqid 1821806570, errstat 0, erridx 0 system.1.0 = Cisco Internetwork Operating System Software 4d01h: SNMP: Packet sent via UDP to 192.168.1.21 The Cisco log output is the same for both commands, which are issued by the root user. There is no firewall on the SCO server and there is no firewall between the switch and the SCO Unix server. There are no errors in any log files on the SCO server and no complaints about missing or incorrect snmp libraries. netstat shows that UDP ports 161 and 162 are not being used by any other processes. Its almost as if the net-snmp commands can transmit on UDP port 161 but not receive any responses. When the detailed debugging is switched on (by setting "dodebugging 1" in snmp.conf), I get a couple of errors near the end of the debugging output. I am not sure if this is significant. A copy of the last section of the debug output containing all the errors is shown below: .... .... heaps of stuff .... snmp_pdu_realloc_rbuild(): snmp_api.c, 3207: dumph_send: dumph_send: error indexerror index dumpx_send: dumpx_send: 02 01 00 02 01 00 dumpv_send: dumpv_send: Integer: 0 (0x00) Integer: 0 (0x00) trace: trace: snmp_pdu_realloc_rbuild(): snmp_api.c, 3220: snmp_pdu_realloc_rbuild(): snmp_api.c, 3220: dumph_send: dumph_send: error statuserror status dumpx_send: dumpx_send: 02 01 00 02 01 00 dumpv_send: dumpv_send: Integer: 0 (0x00) Integer: 0 (0x00) trace: trace: snmp_pdu_realloc_rbuild(): snmp_api.c, 3233: snmp_pdu_realloc_rbuild(): snmp_api.c, 3233: dumph_send: dumph_send: request_idrequest_id dumpx_send: dumpx_send: 02 04 66 93 7C E4 02 04 66 93 7C E4 dumpv_send: dumpv_send: Integer: 1720941796 (0x66937CE4) Integer: 1720941796 (0x66937CE4) trace: trace: _snmp_build(): snmp_api.c, 2778: _snmp_build(): snmp_api.c, 2778: dumph_send: dumph_send: Community StringCommunity String dumpx_send: dumpx_send: 04 06 70 75 62 6C 69 63 04 06 70 75 62 6C 69 63 dumpv_send: dumpv_send: String: public String: public trace: trace: _snmp_build(): snmp_api.c, 2794: _snmp_build(): snmp_api.c, 2794: dumph_send: dumph_send: SNMP Version NumberSNMP Version Number dumpx_send: dumpx_send: 02 01 00 02 01 00 dumpv_send: dumpv_send: Integer: 0 (0x00) Integer: 0 (0x00) trace: trace: _snmp_build(): snmp_api.c, 2812: _snmp_build(): snmp_api.c, 2812: dumph_send: dumph_send: SNMPv1 MessageSNMPv1 Message trace: trace: netsnmp_udp_send(): snmpUDPDomain.c, 166: netsnmp_udp_send(): snmpUDPDomain.c, 166: netsnmp_udp: netsnmp_udp: send 43 bytes from 80bd571 to 192.168.1.5 on fd 4 send 43 bytes from 80bd571 to 192.168.1.5 on fd 4 trace: trace: snmp_sess_select_info(): snmp_api.c, 5622: snmp_sess_select_info(): snmp_api.c, 5622: sess_select: sess_select: for all sessions: for all sessions: 4 4 Timeout: No Response from 192.168.1.5. The same problem occurs with trapd, the SCO command `trap_rece` works by `trapd` doesn't. Any suggestions would be greatly appreciated. Michael _________________________________________________________________ Thousands of jobs, millions of opportunities. Begin here! http://a.ninemsn.com.au/b.aspx?URL=http%3A%2F%2Fninemsn%2Eseek%2Ecom%2Eau&_t=757263760&_r=Hotmail_End_Text_Jul06&_m=EXT ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Net-snmp-users mailing list [email protected] Please see the following page to unsubscribe or change other options: https://lists.sourceforge.net/lists/listinfo/net-snmp-users
