Some trivial issues about SNMP

Snmpset, which has been plagued for a long time, has been fixed. Previously, it always prompts a nocreation error. After a long time, it cannot find out what the problem was. It turns out that it didn't really understand the meaning of index in table, in the past, the snmpset in table differs much from the snmpset in simple variables, and the index in table is used.

 

First, view all the content in the self-created table.

[Root @ Beijing2008 SNMP] # snmptable-C public localhost. 1.3.6.1.4.1.310.3
SNMP table: mymib: exampletable

Userindex userstatus checktime monset
20 good 0: 0: 20: 30.15 1
21 bad 0: 0: 18: 35.12 2
22 XXX 0: 0: 16: 50.03 3
Then I want to modify the fourth monset column in the table. Next I will pay attention to it.

Previously, snmpset-C public localhost. 1.3.6.1.4.1.310.3.1.4.1 I 99 meant to change the value of 1 in the first line of monset to 99.

The result shows the error I mentioned earlier.

This should be the case after correction.

Snmpset-C public localhost exampletable. exampleentry. monset.20 I 99

This is correct.

The prompt is as follows:

Mymib: monset.20 = integer: 99