On Thu, 4 Nov 2004 15:13:09 -0000 Maria wrote: MM> >From my understanding of this, I have two options: MM> 1. Move to 5.1.2 and use the trap call back function to detect when MM> alarms MM> have been generated. MM> 2. Write our own master agent, assuming that it can receive MM> notifications of MM> all traps. (Is this possible?)
I'm not sure I understand what you are trying to do here. A master agent would not typically receive traps. That would be the job for the trap daemon. Which isn't to say that you couldn't integrate the two if you wanted to. MM> For the other part (I'm talking about having several subagents, using MM> the same mib, deployed across several nodes). I have the options to: MM> 1. Move to 5.2 where we can change the context name. (I'm still a bit MM> confused about this yet, as I didn't get it working. Will I still MM> only use one OID, but each will have a different context_name? Exactly. MM> This means that if I do an snmpwalk, I will get all the values?) No, because snmpwalk only deals with one context at a time. If you want snmpwalk to see everything within a single context, you have to re-think your MIB design. MM> 2 If I develop my own Master Agent, would option (a) be possible? It MM> would mean that the Master agent would process all the results and return MM> only one value to an SNMP get, or add several rows. That way we only need MM> to expose one MIB both internally and externally - we can generate all MM> the code from this one MIB but each instance would use its own modified MM> 'version' of the OID. Well, you've completely lost me. How about a simple example. You are talking about a single MIB, but wanting multiple instances. So let's say you have a 'PCI Card MIB', and a PC with a single master agent, 3 PCI slots, each with a sub-agent. If the MIB defines cardModel as a scalar, then you need to specify a context to the master agent when asking for cardModel.0, so it knows which card to get the data from. The other two alternatives, which wouldn't require contexts, would be (a) define cardModelOne, cardModelTwo and cardModelThree. This requires that you know how many cards there might be in advance (like when the MIB is published). (b) define a cardTable, and have a slotNumber as the index. Now, can you define what you are trying to do using that example? MM> RedHat does seem to support dlmod. However I don't see how that will be MM> useful for me for our product specific alarms and counters. That means you could load your product modules directly into the 5.1.2 RedHat agent and uses contexts, instead of having to wait for 5.2 where contexts work for AgentX sub-agents. -- Robert Story; NET-SNMP Junkie Support: <http://www.net-snmp.org/> <irc://irc.freenode.net/#net-snmp> Archive: <http://sourceforge.net/mailarchive/forum.php?forum=net-snmp-users> You are lost in a twisty maze of little standards, all different. ------------------------------------------------------- This SF.Net email is sponsored by: InterSystems CACHE FREE OODBMS DOWNLOAD - A multidimensional database that combines robust object and relational technologies, making it a perfect match for Java, C++,COM, XML, ODBC and JDBC. www.intersystems.com/match8 _______________________________________________ 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
