Dave, Getting back to you on the packets that you requested .... When I run using the snmpd.conf file I generated (the one that works), I didn't see much in the way of packets. The first output below will show this. However, further below, you'll see the output of packets from using the snmpd.conf file in question: Thanks again for your input
====================================== Packet output using snmpd.conf file I generated ================================== #snmpd -f -Le -Dread_config -d # net-snmp (or ucd-snmp) persistent data file. # ######################################################################## #### # STOP STOP STOP STOP STOP STOP STOP STOP STOP # # **** DO NOT EDIT THIS FILE **** # # STOP STOP STOP STOP STOP STOP STOP STOP STOP ######################################################################## #### # # DO NOT STORE CONFIGURATION ENTRIES HERE. # Please save normal configuration tokens for snmpd in SNMPCONFPATH/snmpd.conf. # Only "createUser" tokens should be placed here by snmpd administrators. # (Did I mention: do not edit this file?) # 500 0x414e65774461793500 NULL .1.3.6.1.6.3.10.1.1.2 0x5069c825448c5b6bd4281aaf3c e2ddb5 .1.3.6.1.6.3.10.1.2.2 0x5069c825448c5b6bd4281aaf3ce2ddb5 0x00 read_config: storing: setserialno 764030637 read_config: storing: ########################################################## #### read_config: storing: # # snmpNotifyFilterTable persistent data # read_config: storing: ########################################################## #### read_config: storing: read_config: storing: engineBoots 90 read_config: storing: oldEngineID 0x80001f88801bea6feb47261304 Sending 96 bytes to UDP: [168.159.121.99]:162 0000: 30 5E 02 01 01 04 06 70 75 62 6C 69 63 A7 51 02 0^.....public.Q. 0016: 04 10 62 9C BD 02 01 00 02 01 00 30 43 30 0E 06 ..b........0C0.. 0032: 08 2B 06 01 02 01 01 03 00 43 02 00 B6 30 17 06 .+.......C...0.. 0048: 0A 2B 06 01 06 03 01 01 04 01 00 06 09 2B 06 01 .+...........+.. 0064: 06 03 01 01 05 01 30 18 06 0A 2B 06 01 06 03 01 ......0...+..... 0080: 01 04 03 00 06 0A 2B 06 01 04 01 BF 08 03 02 03 ......+......... NET-SNMP version 5.4.1 ======================================================================== ================================================= ======================================================================== ================================================= When I run using the snmpd.conf file in question which my coworker generated, I get a series of packet output as follows: read_config: storing: read_config: storing: engineBoots 91 read_config: storing: oldEngineID 0x80001f88801bea6feb47261304 Sending 96 bytes to UDP: [168.159.121.153]:162 0000: 30 5E 02 01 01 04 06 70 75 62 6C 69 63 A7 51 02 0^.....public.Q. 0016: 04 4C 8C D8 28 02 01 00 02 01 00 30 43 30 0E 06 .L..(......0C0.. 0032: 08 2B 06 01 02 01 01 03 00 43 02 00 B4 30 17 06 .+.......C...0.. 0048: 0A 2B 06 01 06 03 01 01 04 01 00 06 09 2B 06 01 .+...........+.. 0064: 06 03 01 01 05 01 30 18 06 0A 2B 06 01 06 03 01 ......0...+..... 0080: 01 04 03 00 06 0A 2B 06 01 04 01 BF 08 03 02 03 ......+......... NET-SNMP version 5.4.1 Received 80 bytes from UDP: [127.0.0.1]:34339 0000: 01 01 00 00 00 00 00 00 00 00 00 00 2A 40 D0 4C [EMAIL PROTECTED] 0016: 3C 00 00 00 00 00 00 00 05 04 00 00 01 00 00 00 <............... 0032: 88 1F 00 00 03 00 00 00 02 00 00 00 03 00 00 00 ................ 0048: 19 00 00 00 4E 65 74 2D 53 4E 4D 50 20 41 67 65 ....Net-SNMP Age 0064: 6E 74 58 20 73 75 62 2D 61 67 65 6E 74 00 00 00 ntX sub-agent... Sending 88 bytes to UDP: [127.0.0.1]:34339 0000: 01 12 00 00 05 00 00 00 00 00 00 00 2A 40 D0 4C [EMAIL PROTECTED] 0016: 44 00 00 00 BE 01 00 00 00 00 00 00 04 00 00 00 D............... 0032: 05 04 00 00 01 00 00 00 88 1F 00 00 03 00 00 00 ................ 0048: 02 00 00 00 03 00 00 00 19 00 00 00 4E 65 74 2D ............Net- 0064: 53 4E 4D 50 20 41 67 65 6E 74 58 20 73 75 62 2D SNMP AgentX sub- 0080: 61 67 65 6E 74 00 00 00 agent... Received 20 bytes from UDP: [127.0.0.1]:34339 0000: 01 0D 00 00 05 00 00 00 00 00 00 00 2B 40 D0 4C [EMAIL PROTECTED] 0016: 00 00 00 00 .... Sending 28 bytes to UDP: [127.0.0.1]:34339 0000: 01 12 00 00 05 00 00 00 00 00 00 00 2B 40 D0 4C [EMAIL PROTECTED] 0016: 08 00 00 00 9B 07 00 00 00 00 00 00 ............ -----Original Message----- From: Smith, Randy Sent: Friday, December 21, 2007 4:41 PM To: Smith, Randy; Dave Shield Cc: [email protected] Subject: RE: Timeout: No Response from localhost. P.S The result I posted in the previous email of running the 'startup' script were results using the snmpd.conf file that I generated. When I run the 'startup' script using my coworker's snmpd.conf file, I get the following results: # . ./startup 1523 Simple Test Timeout: No Response from localhost. Now mounting nfs mount: mount: /opt/SUNWspro: Device busy -----Original Message----- From: Smith, Randy Sent: Friday, December 21, 2007 4:36 PM To: 'Dave Shield' Cc: [email protected] Subject: RE: Timeout: No Response from localhost. Silly me! For the snmpd.conf file I generated it's not: rocommunity public .1.3.6.1.2.1.1 but rather: rocommunity whatever And the snmpget -c command works fine. But when I use the snmpd.conf file my coworkder generated (in original email) using community 'whatever' also, I get the timeout. Dave, I have spent most of the day alternating these two conf file and starting and restarting snmpd and the results are the same - the snmpget times out using my coworkers snmpd.conf but works fine using mine. But for the one I generated ( using 'rocommunity whatever' also), it works fine. In each case I am starting the agent on Solaris 9 using the following startup script: ======================================================================== =============== stty erase PATH=$PATH:/opt/emc/dist/local/usr/bin PATH=$PATH:/opt/emc/dist/local/usr/sbin PATH=$PATH:/usr/local/bin export PATH MIBDIRS=/opt/emc/dist/local/usr/share/snmp/mibs export MIBDIRS snmpd& echo "Simple Test" /opt/emc/dist/local/usr/bin/snmpget -v 1 -c whatever localhost SNMPv2-MIB::sysUp Time.0 mount lsca2055:/opt/SUNWspro /opt/SUNWspro PATH=$PATH:/opt/SUNWspro/bin export PATH LD_LIBRARY_PATH=/opt/emc/dist/local/usr/lib export LD_LIBRARY_PATH ======================================================================== ================ FYI, the results of this startup are as follows: # . ./startup 1513 Simple Test DISMAN-EVENT-MIB::sysUpTimeInstance = Timeticks: (176) 0:00:01.76 Now mounting nfs mount: mount: /opt/SUNWspro: Device busy # -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Shield Sent: Friday, December 21, 2007 4:16 PM To: Smith, Randy Cc: [email protected] Subject: Re: Timeout: No Response from localhost. On 21/12/2007, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > fyi, the conf file pasted earlier is one that a coworker devised on AIX > using the snnpconf. However, interestingly, when I use the following > snmpd.conf that I generated myself on Solaris, the 'snmpget -c ....' > works fine. Using which community? "public" or "private"? Because I wouldn't expect the entry rocommunity public .1.3.6.1.2.1.1 to work (since it's missing the network source field, which should come before the OID) > Also, following the 'good' snmpd.conf file, Dave you will > see the output from the snmpd -f -Le -Dread_config -d' using the > snmpd.conf file that my coworker generated. Hmmm.... That output looks OK at first sight. Do you see the packet dump output when you make the query? Can you confirm that the two "snmpget" requests are effectively identical (run from the same host, with exactly the same parameters, apart from the community string)? i.e. /opt/emc/dist/local/usr/bin/snmpget -v 1 -c private localhost SNMPv2-MIB::sysUpTime.0 (with the working config) and /opt/emc/dist/local/usr/bin/snmpget -v 1 -c whatever localhost SNMPv2-MIB::sysUpTime.0 (with the broken config) How are you starting the two agents? What's the exact command you use in each case? Dave ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2005. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ 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
