hi!
On Tue, Mar 04, 2008 at 10:57:57PM +0700, Agung T. Apriyanto wrote:
> recently i upgrade one of my machine to 4.3-beta, and found the new
> snmp program,
> but i'm still using the net-snmp from ports, and somehow when i try to
> issue the oid
> .1.3.6.1.2.1.4.20.1.2 ( ip address look up ) it did not show anything,
> but if i use opensnmpd
> and issue the same oid, it shows the current ip address.
you mean the new snmpd is working correctly but net-snmp is not? this
doesn't surprise me, there were some issues with net-snmp in the past,
this was one of my reasons to start working on a new implementation.
> also if i
> issue .1.3.6.1.2.1.1.3.0
> it didn't show the machine uptime, but show the snmp daemon uptime (
> same for net-snmp
> and opensnmpd ).
this is the correct behaviour, the following definition is from the
SNMPv2 MIB (RFC 3418):
---snip---
sysUpTime OBJECT-TYPE
SYNTAX TimeTicks
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The time (in hundredths of a second) since the
network management portion of the system was last
re-initialized."
::= { system 3 }
---snap---
> is it some kind of MIB conflict or something ? anyone
> else has same
> problem with me ? can opensnmpd developer confirm me ?
> thank you.
>
there is no conflict between net-snmp and "opensnmpd", they do not
share any configuration and, unlike net-snmpd, the openbsd snmp daemon
does not parse any ASN.1 MIB files on runtime and uses a compiled-in
mib implementation. the only possible conflict is listening on udp
port 161 (snmp).
> rgds,
>
> Agung
>
Reyk
