Template:FAQ:Applications 11

There are three possible reasons for this:

The majority of MIB objects are defined as "read-only" and inherently cannot be changed via SET requests.

Of those that can in principle be changed, not all have been implemented as such in this agent.

Even if SET support has been implemented, the agent may not be configured to allow write access to this object.

The example configuration file shipped with the basic distribution only allows write access for the local host itself (and a suitable community name must be configured first). 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.