> The last option would be what I was looking for, and I am now trying
> the code from at CVS.
> But his has one limitation, one would have to know the context name.

Well, the management station has to have *some* way of specifying
which of the various overlapping systems it is interested in.
That's where the context comes in - new with SNMPv3.


> I didn't know about the concept of "ranges" even though I first thought
> of something like that. My idea was to have several tables where one the
> indexes would differentiate the several instances, kind of like a context
> name. But this didn't workout. Where can I find out more about ranges???

That's described in the AgentX RFCs.
Have a look at RFC 2741  (or whatever thej latest version of that is)

Dave



-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl
_______________________________________________
Net-snmp-users mailing list
[EMAIL PROTECTED]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users

Reply via email to