Re :Set command with error "noSuchPacket"
"vishal_nitr" <[email protected]>
| Newsgroups | gmane.network.net-snmp.user |
|---|---|
| Message-ID | <1219684179.S.9250.1433.f4mail-234-226.rediffmail.com.1219727875.16389@webmail.rediffmail.com> |
Hi Letha, The error you are getting is different from the error you will get if the object is present and is read only but you are trying SET the object. In that case you will get error like "Not writable object".are you able to do "GET" operation on it ? Instaed of using MIB name in "set" command use "-m ALL" option if you still get the same error try using the exact OID of the "bDTDisplayName" object.if this gives you the same error then look into your Makefile whether you have compiled that object or not.On Mon, 25 Aug 2008 22:38:11 +0530 "Letha Jacob" wrote Hi All, I am using Net-SNMP version 5.4.1.2 I tried using the net-snmp "set" command. I am able to set the values of variables like "system.sysName.0". But, wh en I try to set the values of objects in my MIB file, I get the error :- Error in packet. Reason: (noSuchName) There is no such variable name in this MIB. This name doesn't exist: BDTMI B::bDTDisplayName.0 Net-SNMP site specifies the following reasons for this error :- 1. The agent may not be configured to allow write access to this object. Ans : My 'snmpd.conf' file looks like :- rocommunity public 127.0.0.1 rwcommunity npublic 127.0.0.1 The command which I gave was : -> snmpset -v 1 -c npublic localhost BDTMIB::bDTDisplayName.0 Error in packet. Reason: (noSuchName) There is no such variable name in this MIB. This name doesn't exist: BDTMIB::bDTDisplayName.0 At the same time, the foll command works successfully:- -> snmpset -v 1 -c npublic localhost system.sysName.0 I tried giving unique community name for the object like : rwcommunity napublic 127.0.0.1 BDT MIB::bDTDisplayName.0 But, this too failed. 2.Many MIB objects are defined as "read-only" and inherently cannot be changed via SET requests. Attempts to do so will ty pically be dropped by the 'snmpset' command without ever being sent to the agent. Ans: I ran the command as 'root'. How can I know if the object is inherently "read-only" ? If yes, how can I change it? 3.Of those objects that can in principle be changed, the agent may not include the code necessary to support SET requests. (GET and GETNEXT are much easier to handle - particularly for objects relating to the internals of the underlying operating system). Ans: I am using a straight forward 'set' command. Since, I am able to set the "system" objects, I dont think that this is an issue with the code for SET request. It might be a problem with the access to the required MIB file. Kindly help. Thanks and Regards, Vishal Kotalwar, Software Engineer, Aricent, Chennai-35. 09884074047. ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ 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