Eric> hi. i'm running scotty-1.1.3 under tkined-1.1 on a sun 4.1.3.
Eric> when i try to set a read-write SNMP variable via the mib
Eric> browser i get an error:
Eric> Set operation failed:
Eric> noSuchName 1 {1.3.6.1.2.1.1.4.0 {OCTET STRING} ericm@microunity.com}
Eric> in this case i tried to set system.sysContact.
Eric> it looks like {OCTET STRING} is supposed to be replaced with
Eric> something that's meaningful to SNMP.
The error is meant to read as "the agent responded with a noSuchName
error in varbind number 1. The varbind list itself contains exactly
one varbind with an object identifier 1.3.6.1.2.1.1.4.0 (which is
sysContact.0), the ASN.1 syntax used to encode the value (which is
OCTET STRING since a DisplayString is encoded as an OCTET STRING) and
the value ericm@microunity.com."
Reading RFC 1157, I found:
Upon receipt of the SetRequest-PDU, the receiving entity responds
according to any applicable rule in the list below:
(1) If, for any object named in the variable-bindings field,
the object is not available for set operations in the
relevant MIB view, then the receiving entity sends to the
originator of the received message the GetResponse-PDU of
identical form, except that the value of the error-status
field is noSuchName, and the value of the error-index
field is the index of said object name component in the
received message.
Therefore, I think you are either talking to an agent that does not
allow sets or you have simply not used to right community name (which
identifies the MIB view in SNMPv1. It is unlikely to be a problem with
tkined or scotty. Please check your community name ("Set Parameter" in
the "SNMP Browser" script) and your agent configuration.
Juergen