|
|
− | That's a difficult question. | + | That's not easy to answer in general. |
| + | |
| + | If there's an existing agent that already implements the desired new |
| + | MIB, then it makes sense to re-use that, via whatever extension protocol |
| + | it might support. Ideally, this would be an AgentX sub-agent, since the |
| + | AgentX protocol is deliberately designed for this purpose, and provides |
| + | a fuller and more reliable mechanism than either SMUX or proxied SNMP. |
| + | But if the target subagent only supports SMUX or basic SNMP, then that |
| + | would dictate the extension protocol to use. |
| + | |
| + | Implementing the module directly within the main agent (or via dlmod) |
| + | is probably the most efficient and reliable (since there's minimal |
| + | overheads between the code implementing the MIB module, and the agent |
| + | framework). But it does assume that there's a suitable mechanism for |
| + | retrieving the necessary information. |
| | | |
Exception encountered, of type "Error"