Hello Dave,
Thank you for the comments.
I would see to it that i study more on agent and extending the support for
agent.
With Regards
Anirudha Patil
On Wed, Oct 31, 2012 at 6:06 PM, Dave Shield wrote:
> On 31 October 2012 11:59, Anirudha Patil wrote:
> > I have a concern about "snmpset" command. I'm not able to set a
> > hrStorageDescr or hrStorageType.
>
> Correct.
> From the definition of these objects in HOST-RESOURCES-MIB:
>
> hrStorageType OBJECT-TYPE
> MAX-ACCESS read-only
> ::= { hrStorageEntry 2 }
>
> hrStorageDescr OBJECT-TYPE
> MAX-ACCESS read-only
>::= { hrStorageEntry 3 }
>
> "read-only" means that you cannot issue a SET command on such objects.
>
>
>
> > I have also manually tried changing the MAX-ACCESS for the objects
> > in their corresponding MIB [/usr/share/snmp/mibs], but still its not
> working
>
> a) This is an internationally agreed standard MIB.
> You can't simply decide to change it unilaterally.
>
> b) The code within the agent that implements this MIB has been written
> following the standard definitions. As such, these objects are
> implemented as read-only objects. There is simply no code
> within the agent to handle SET requests for them
> Even if you go your own way and ignore issues of interoperability,
> you are still going to have to write additional code for the agent,
> so
> that it knows how to handle SET requests for these objects - how to
> process the assignment, how to save the new state so that it's
> retained when the agent restarts, etc, etc
>
> The agent is not a magic box - you can't simply edit a text file and expect
> everything to just start working. You need to supply the missing code.
>
> Dave
>
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct___
Net-snmp-users mailing list
Net-snmp-users@lists.sourceforge.net
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
