Re: sysObjectID still returns an incorrect value

On Wed, Sep 15, 2010 at 2:52 PM, Fulko Hew <[email protected]> wrote:

> As long as I was testing 5.6.rc2, I thought I'd test it to
> see if the 'sysObjectID is truncated' issue was resolved.
>
> What I see is that the value is now returned as padded with zeros.
> I.e.
>
> 1.3.6.1.2.1.1.2.0:
> 1.3.6.1.4.1.8072.3.2.10.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0
>
> and it doesn't matter if the default is overidden with a custom
> value from the snmpd.conf file.  It too is zero padded.
>

I've narrowed it down (ie. found it)

 agent/mibgroup/mibII/system_mib.c line 339

defines the watcher utility as:

WATCHER_MAX_SIZE | WATCHER_SIZE_IS_PTR | WATCHER_SIZE_UNIT_OIDS,

whereas the value passed in via sysObjectIDByteLength has already been
converted
into bytes.  so the above statement on line 339
should instead be:

WATCHER_MAX_SIZE | WATCHER_SIZE_IS_PTR

------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev

_______________________________________________
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