This document explains the list of the OID's that are enabled for the snmpset operation.

SNMP set operation on some of the OID's might fail even though they have read-write capable as per the RFC's/standards.

However the Junos doesn't support all of them.

You can notice the following when trying to set the same from the external server.

user@linux-server#snmpset -v2c -c @public 10.85.168.16 1.3.6.1.2.1.31.1.1.1.18.6 s "This is loopback"

Error in packet.

Reason: noAccess <<<<<< This indicates that, this is not allowed for the set operation.

Failed object: iso.3.6.1.2.1.31.1.1.1.18.6

The Junos OS SNMP set operations are supported in the following MIB tables and variables:

• snmpCommunityTable

• eventTable

• alarmTable

• snmpTargetAddrExtTable

• jnxPingCtlTable

• pingCtlTable

• traceRouteCtlTable

• jnxTraceRouteCtlTable

• sysContact.0

• sysName.0

• sysLocation.0

• pingMaxConcurrentRequests.0

• traceRouteMaxConcurrentRequests.0

• usmUserSpinLock

• usmUserOwnAuthKeyChange

• usmUserPublic

• vacmSecurityToGroupTable (vacmGroupName, vacmSecurityToGroupStorageType, and vacmSecurityToGroupStatus)

• vacmAccessTable (vacmAccessContextMatch, vacmAccessReadViewName, vacmAccessWriteViewName, vacmAccessNotifyViewName, vacmAccessStorageType, and vacmAccessStatus)

• vacmViewSpinLock

• vacmViewTreeFamilyTable (vacmViewTreeFamilyMask, vacmViewTreeFamilyType, vacmViewTreeFamilyStorageType, and vacmViewTreeFamilyStatus)

Please refer the following external document for the further details.

https://www.juniper.net/documentation/us/en/software/junos/network-mgmt/topics/topic-map/junos-os-snmp-faqs.html