How does EMANATE deal with Gets, GetNexts, and Sets when different rows of a table are in different subagents?
This depends very much on what sort of message it is: • Keep in mind that for each MIB object for which there are multiple subagents, the master agent has a priority-sorted list of subagents which have that object. • When a Get request arrives at the master agent, each subagent which has a matching object database entry is asked (in order of priority), “Do you have this instance?” The value returned by the first subagent that responds affirmatively is returned in the response. • When a GetNext request arrives at the master agent, all subagents which have that object are asked, “What is the next instance you have after this OID?” When all responses from subagents have arrived, the lexicographically smallest object is returned. • If a Set request arrives at the master agent, it calls the test methods for each subagent which has that object, and the first subagent that returns a non-fatal error status “wins”. Again, they are checked in priority order.
Related Questions
- Can I define a Substitution Rule which uses the contents of a different table to determine which rows are updated in the primary table?
- How does EMANATE deal with Gets, GetNexts, and Sets when different rows of a table are in different subagents?
- Can different rows of a table be in different subagents?
