Connected: An Internet Encyclopedia
RFC 1157 - 4.1.5. The SetRequest-PDU

Top: Connected: An Internet Encyclopedia
Up: Requests For Comments
Up: RFC 1157
Up: 4. Protocol Specification
Up: 4.1. Elements of Procedure
Prev: 4.1.4. The GetResponse-PDU
Next: 4.1.6. The Trap-PDU

### 4.1.5. The SetRequest-PDU

The form of the SetRequest-PDU is identical to that of the GetRequest-PDU except for the indication of the PDU type. In the ASN.1 language:

                      SetRequest-PDU ::=
                          [3]
                              IMPLICIT SEQUENCE {
                                  request-id
                                      RequestID,

                                  error-status        -- always 0
                                      ErrorStatus,

                                  error-index         -- always 0
                                      ErrorIndex,

                                  variable-bindings
                                      VarBindList
                              }

The SetRequest-PDU is generated by a protocol entity only at the request of its SNMP application entity.

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.

2. If, for any object named in the variable-bindings field, the contents of the value field does not, according to the ASN.1 language, manifest a type, length, and value that is consistent with that required for the variable, 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 badValue, and the value of the error-index field is the index of said object name in the received message.

3. If the size of the Get Response type message generated as described below would exceed a local limitation, 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 tooBig, and the value of the error-index field is zero.

4. If, for any object named in the variable-bindings field, the value of the named object cannot be altered for reasons not covered by any of the foregoing rules, 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 genErr and the value of the error-index field is the index of said object name component in the received message.

If none of the foregoing rules apply, then for each object named in the variable-bindings field of the received message, the corresponding value is assigned to the variable. Each variable assignment specified by the SetRequest-PDU should be effected as if simultaneously set with respect to all other assignments specified in the same message.

The receiving entity then sends to the originator of the received message the GetResponse-PDU of identical form except that the value of the error-status field of the generated message is noError and the value of the error-index field is zero.

Next: 4.1.6. The Trap-PDU

Connected: An Internet Encyclopedia
RFC 1157 - 4.1.5. The SetRequest-PDU