Difference between revisions of "Template:FAQ:Applications 11"
From Net-SNMP Wiki
(5.4 release synchronisation) |
m (Latest FAQ revision - preparing for 5.5 release) |
||
| Line 7: | Line 7: | ||
There are three possible reasons for this: | There are three possible reasons for this: | ||
| − | * Many MIB objects are defined as "read-only" and inherently cannot be changed via SET requests. Attempts to do so will typically be | + | * Many MIB objects are defined as "read-only" and inherently cannot be changed via SET requests. Attempts to do so will typically be rejected by the <CODE>'snmpset'</CODE> command without ever being sent to the agent. |
* 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). | * 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). | ||
Latest revision as of 09:42, 28 May 2009
There are three possible reasons for this:
- Many MIB objects are defined as "read-only" and inherently cannot be changed via SET requests. Attempts to do so will typically be rejected by the
'snmpset'command without ever being sent to the agent.
- 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).
- Even if SET support has been implemented, the agent may not be configured to allow write access to this object.
Ready-installed distributions (such as those shipped with Linux) tend to be configured with read-only access to part of the mib tree (typically just the system group) and no write access at all.
To change this, you will need to set up the agent's access control configuration. See the AGENT section for more details.
Note that neither the community string "public" nor "private" can be used to set variables in a typical default configuration.
