Difference between revisions of "Template:FAQ:Applications 10"
(5.4 release synchronisation) |
|||
| Line 1: | Line 1: | ||
This depends on which MIB modules are supported by the agent you are | This depends on which MIB modules are supported by the agent you are | ||
| − | querying and what you're asking for. | + | querying and exactly what you're asking for. |
| − | + | Note that a tree is walked by repeatedly asking for "the next entry" until | |
all the values under that tree have been retrieved. However, the agent has | all the values under that tree have been retrieved. However, the agent has | ||
no idea that this is what's happening - all it sees is a request for "the | no idea that this is what's happening - all it sees is a request for "the | ||
Latest revision as of 15:52, 28 December 2006
This depends on which MIB modules are supported by the agent you are querying and exactly what you're asking for.
Note that a tree is walked by repeatedly asking for "the next entry" until all the values under that tree have been retrieved. However, the agent has no idea that this is what's happening - all it sees is a request for "the next entry after X".
If the object X happens to be the last entry in a sub-tree, the agent will provide the next object supported (as requested) even though this will be in a different subtree. It's up to the querying tool to recognise that this last result lies outside the area of interest, and simply discard it.
If the object X happens to be the last entry supported by the agent, it doesn't have another object to provide, so returns an "end of MIB" indication. The Net-SNMP tools report this with the message above.
But in either case, the actual information provided will be the same.
