SNMP-Set from Tkined

Brevoort A.J.J (A.J.J.Brevoort@research.ptt.nl)
Tue, 12 Sep 1995 16:04 +0200

Hello,
Thanks for helping me out, I'll summarize what I had to do to set some
variables.
I installed CMU-snmpd as agent and use Tkined/Scotty as manager, both
running on the same Linux machine. For now I'm using SNMPv1.

Most variables are read-only, for experimentation purposes, one you can set
is
Internet.mgmt.mib-2.system.sysContact.

First way to change its value:
>From tkined, under the tools menu fire up the SNMP-Browser.
In the SNMP-Browser menu, change the community from public to private, as
system.sysContact is defined as such.
Start the MIB Browser.
In it's window, walk to mgmt -> mib-2 -> system.
Clicking on sysContact will show you the current value.
On the right side is a <set> button. Clicking this will give you a dialog
box, you
can enter the new value there.
To check whether it was changed, click the <walk> button. This will display
a tree starting from the current point, in this case just sysContact.

Another way should be from the SNMP-Tree:
Fire SNMP-Tree up from the tools menu, this will show a part of the
MIB-Tree.
>From the MIB-2 menu, choose system.
This shows the system subtree.
Now click on sysContact, and choose "show mib variable" from the menu that
appears. It will show you the current value.
Clicking again and choosing "set" doesn't work but instead dumps this to
stderr:
| can't read "option(agent,.top0)": no such element in array
| while executing
| "set name $option(agent,$top)..."
| (procedure "SetValue" line 6)
| invoked from within
| "SetValue .top0.c 1.3.6.1.2.1.1.4"
| invoked from within
| ".top0.c.popup invoke active"
| ("uplevel" body line 1)
| invoked from within
| "uplevel #0 [list $w invoke active]"
| invoked from within
| "if {[$w type active] == "cascade"} {
| $w postcascade active
| set menu [$w entrycget active -menu]
| tkMenuFirstEntry $menu
| } elseif {[$w type activ ..."
| (procedure "tkMenuInvoke" line 2)
| invoked from within
| "tkMenuInvoke .top0.c.popup"
| (command bound to event)
which is probably useful for debugging purposes. If this has been fixed I'd
like to know!

Good luck,
Arno