There is a mismatch between the template numbering
+
for this entry, and the FAQ entries that refer to it.
+
This follows a re-ordering of the entries in the
+
Applications section.
+
-->
There are three possible reasons for this:
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.
+
* 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.