Re: NO SUBJECT

Juergen Schoenwaelder (schoenw@cs.utwente.nl)
Sat, 20 Apr 1996 17:30:11 +0200

Hi!

dlc@silcom.com (David Carmean) wrote:

David> I've just started experimenting again with tkined 1.3.4, and
David> am being frustrated by several behaviors.

All things you mention just show that you don't understand how to use
the tool. (I can understand if someone is frustrated about missing
documentation - but complaining about behaviors that you do not
understand is frustrating for me.) If you are really frustrated about
tkined, either sit down and write some code to improve things or go
and buy a commercial system.

David> First, when I set up an SNMP monitor job which requires a community
David> name other than "public," the community name isn't ever saved
David> in the file. Perhaps I'm setting it wrong...I use the
David> SNMP-Monitor/Set Parameter option from the pulldown. I can get the
David> stripcharts to work fine within that session, but not if I save and
David> restart the view.

You should define an attribute SNMP:Alias or SNMP:Config for these
nodes which either contains an SNMP alias name or the session
configuration options. See the scotty man page for details about SNMP
aliases and session options. All SNMP tools will automatically use
these attributes if they exist.

David> Second, I wanted a certain set of interpreters to come up by
David> default when I start tkined, namely IP-Trouble and SNMP-Monitor. I
David> modified tkined.defaults to accomplish this, but then whenever I
David> load a view that has monitor jobs, it starts another copy of the
David> interpreter...why doesn't it realize that one is already
David> running?

Automatically merging jobs into one interpreter is not always the
right thing to do. It might be useful in your particular environment,
but it can also be very annoying for others how want to keep monitor
jobs seperated. But you have the source so you can change this if you
don't like it.

David> Third, I want to use the SNMP Interface Load monitor on some
David> devices which always report the Interface Speed as zero. I see
David> in the help info that I'm supposed to be able to set an attribute
David> called SNMP-Monitor:IfSpeed to allow this to work, but I can't figure
David> out where or how. To be specific, how can I force ifSpeed.1 to
David> 1544000 for nodeX?

Just set the attribute. Move your mouse to the interface load
stripchart for interface 1 and press the right mouse button. Select
"Create a new attribute", enter the name SNMP-Monitor:IfSpeed and set
the value to 1544000. This should solve your problem.

Juergen