1) Contents of snmpd.conf ########################################################################### # # snmpd.conf # # - created by the snmpconf configuration program # ########################################################################### # SECTION: Access Control Setup # # This section defines who is allowed to talk to your running # snmp agent.
# rwuser: a SNMPv3 read-write user # arguments: user [noauth|auth|priv] [restriction_oid] rwuser root # rouser: a SNMPv3 read-only user # arguments: user [noauth|auth|priv] [restriction_oid] rouser netboss # rocommunity: a SNMPv1/SNMPv2c read-only access community name # arguments: community [default|hostname|network/bits] [oid] rocommunity public # rwcommunity: a SNMPv1/SNMPv2c read-write access community name # arguments: community [default|hostname|network/bits] [oid] #rwcommunity private localhost .1.3.6.1.4.1.42.2.15 rwcommunity private ########################################################################### # SECTION: Extending the Agent # # You can extend the snmp agent to have it return information # that you yourself define. # dlmod: dynamically extend the agent using a shared-object # arguments: module-name module-path dlmod seaProxy /usr/sfw/lib/sparcv9/libseaProxy.so dlmod seaExtensions /usr/sfw/lib/sparcv9/libseaExtensions.so ########################################################################### dlmod abc /usr/local/tanisha/src/abc.so ########################################################################### # SECTION: System Information Setup # # This section defines some of the information reported in # the "system" mib group in the mibII tree. # syslocation: The [typically physical] location of the system. # Note that setting this value here means that when trying to # perform an snmp SET operation to the sysLocation.0 variable will make # the agent return the "notWritable" error code. IE, including # this token in the snmpd.conf file will disable write access to # the variable. # arguments: location_string syslocation "System administrators office" syslocation teclab # syscontact: The contact information for the administrator # Note that setting this value here means that when trying to # perform an snmp SET operation to the sysContact.0 variable will make # the agent return the "notWritable" error code. IE, including # this token in the snmpd.conf file will disable write access to # the variable. # arguments: contact_string syscontact "System administrator" syscontact "tanisha" # sysservices: The proper value for the sysServices object. # arguments: sysservices_number sysservices 72 ########################################################################### # SECTION: Trap Destinations # # Here we define who the agent will send traps to. # trapsink: A SNMPv1 trap receiver # arguments: host [community] [portnum] trapsink localhost public # trap2sink: A SNMPv2c trap receiver # arguments: host [community] [portnum] trap2sink localhost public # informsink: A SNMPv2c inform (acknowledged trap) receiver # arguments: host [community] [portnum] informsink localhost public # trapcommunity: Default trap sink community to use # arguments: community-string trapcommunity public # authtrapenable: Should we send traps when authentication failures occur # arguments: 1 | 2 (1 = yes, 2 = no) authtrapenable 1 2) location: /etc/sma/snmp 3) starting the agent /usr/sfw/sbin/snmpd -D abc.so 4) snmpget -v 1 -c public -m "MY-ABC-MIB" 127.0.0.1 MY-ABC-MIB::abc.0 5) o/p: No response: timeout I am able to run snmpset successfully. -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Dave Shield Sent: Thursday, April 30, 2009 2:47 PM To: Tanisha Kashyap Cc: kusuma.bm; [email protected] Subject: Re: MODE_GET: timeout response 2009/4/30 Tanisha Kashyap <[email protected]>: > Access control settings: > # rocommunity: a SNMPv1/SNMPv2c read-only access community name > # arguments: community [default|hostname|network/bits] [oid] > > rocommunity public > > nd m sending the get request with the public string only. > > Cant really understand where else the prob cud be Could you please post the full information about your setup: - what is the full contents of your snmpd.conf ? - where is this file located? - how are you starting the agent? - what is the exact command that you are using to send the GET query? - what output do you see from the agent (in log files, etc). Also, does this problem just affect your new MIB object, or is it more widespread? Can you see *anything * from the agent, or not? Dave "DISCLAIMER: This message is proprietary to Aricent and is intended solely for the use of the individual to whom it is addressed. It may contain privileged or confidential information and should not be circulated or used for any purpose other than for what it is intended. If you have received this message in error,please notify the originator immediately. If you are not the intended recipient, you are notified that you are strictly prohibited from using, copying, altering, or disclosing the contents of this message. Aricent accepts no responsibility for loss or damage arising from the use of the information transmitted by this email including damage from virus." ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ 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
