I wish the following feature could be added to scotty in the future...
Right now we can bind a script to a non-leaf mib variable. Use the
TCP mib as an example, we can do
snmp0 bind tcpConnTable get {...}
The problem is this... When the agent receives a GET request for
a recent TCP connection, the agent may not have had the chance to do
snmp0 instance tcpConnState.x...x $currState
to create the new row in the tcpConnTable. Therefore, the GET
request will return `noSuchName'.
So the agent has to _frequently_ refresh its entire tcpConnTable using
the `job' command, or the mib must provide a special variable for the
manager to request a refresh (like the sample code
scotty/snm/agents/snmpd-proc.tcl.) Either way, it's not elegant and it
wastes resources by refreshing the entire tcpConnTable.
The binding to non-leaf node is currently evaluated _after_ the leaf
node. I'd like to see a binding that's evaluated _before_ the leaf
node is reached, even if the leaf node doesn't exist. That is, I'd
like the traversal of the mib tree to evaluate scripts
on its way down as well as on its way up.
Let's call it `bindbefore'. So the Tcl script will read
snmp0 bindbefore tcpConnTable get {
# Try to find tcp connection based on %o and %i
# then...
%S instance tcpConnState.%o $currState
}
That way, by the time the mib tree traversal reaches the leaf
node, the new row will have been inserted into the tcpConnTable.
And we refreshed only the portion of the table that's actually requested
in the GET.
If there's a good way to achieve similar result in the current version
of scotty, I'd love to learn about it for my project.
--Q Vincent Yin | Repeat vyin@cs.ubc.ca | delete(next->bug); (604) 876-9096 (H) | Until 0 = 1;
-- !! This message is brought to you via the `tkined & scotty' mailing list. !! Please do not reply to this message to unsubscribe. To subscribe or !! unsubscribe, send a mail message to <tkined-request@ibr.cs.tu-bs.de>. !! See http://wwwsnmp.cs.utwente.nl/~schoenw/scotty/ for more information.