I forgot to mention that it's with 5.3.1.
Alex
Alex Burger wrote:
> My extension has registered .1.3.6.1.2.1.2 using
> netsnmp_register_handler. The extension also supports .1.3.6.1.2.1.4,
> but this OID has not been registered.
>
> If I do an snmpget .1.3.6.1.2.1.4.1.0, it fails with:
>
>
My extension has registered .1.3.6.1.2.1.2 using
netsnmp_register_handler. The extension also supports .1.3.6.1.2.1.4,
but this OID has not been registered.
If I do an snmpget .1.3.6.1.2.1.4.1.0, it fails with:
Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Fa
On 10/10/06, Juergen Schoenwaelder <[EMAIL PROTECTED]> wrote:
> c) The opposite of b) would be to require that each transport provides
>its own check function in order to localize the problem. The proper
>way to do this would be to add a additional function pointer to the
>netsnmp_trans