Re: Multiple MibWalks

Louis A. Mamakos (louie@TransSys.COM)
Wed, 06 Nov 1996 22:35:31 -0500

Hmmm... this reminds me of something I wanted to do the other day: Have
something like "snmpX walk", but like getbulk where you can provide both
"repeaters" and "non-repeaters". I'd like to be able to use something
like walk to traverse a table, but include a fetch of a fixed mib variable
whenever an SNMP query (GET-NEXT or GET-BULK) get generated on the
network.

Most of the time, of course, I'd like to fetch sysUpTime.0 so that I can
most accurately measure delta times.

And on an unrelated note, has anyone else been surprised that in tkined
the node ids don't seem to be peristant? I have some TCL code that
scans a bunch of routers to produce a mapping of ifIndex indicies to
tkined LINK objects. The mapping is stored as attributes in the NODE
(NODE1, LINK, NODE2) as well as the associated LINK object. Of course,
the next time you invoke tkined and change some stuff around, I think
these mappings are no longer valid. It makes sense *now*.. I may
have to use the name as the unique identifier, and build an index to
reflect the current mapping each time the tkined application is started
up.

louie