Re: How to recognize different agent callbacks as triggered by same SNMP PDU?
Peder Chr. Norgaard (pcn@tbit.dk)
Tue, 25 Jul 1995 21:16:31 +0200 (CDT)
>
> Hi!
>
> "Peder Chr. Norgaard" <pcn@tbit.dk> said:
>
> Peder> For efficiency in processing GetRequests and GetNextRequests,
> Peder> and for consistency checking in processing SetRequests involving the
> Peder> RowStatus Textual Convention I find it neccessary to be able to
> Peder> recognize a set of calls of commands hooked by "snmp bind" as being
> Peder> triggered by the same PDU. Ideally, some kind of PDU identification
> Peder> could be expanded with the '%' convention, just as the %i, %i, and %v
> Peder> are for now.
>
> I think the %V and %R substitutions should solve your problem. %V will
> be expanded to the complete varbind list and %R expands to the request
> id (which should be unique in conjunction with the agent address %A
> and port number %P). See the scotty man page for the list of supported
> % substitutions.
This almost solve the problem (again, I posed the question because
I did not appreciate that the %V, %R etc was expanded in "snmp bind"
commands, too).
There is a problem, however. The request id as seen by an agent
implementation is unique in conjunction with the network address and
port number of the *manager*, not the *agent*.
Could you add a format escape that expanded to the network address and port
number of the manager? These data must surely be available somewhere.
Until that, I can easily get along just by using the request ID alone;
while I am developing I run the only manager using the stuff anyway.
>
> Juergen
>
best regards
--peder chr.
Peder Chr. Norgaard
Telebit Communications A/S
Denmark