My dilemma is having a product development team that is delivering
on a Windows x64 platform. I need them to deliver a custom value of
sysObjectID, but there was a bug in (old versions) of Net-SNMP that
prevented the config file override from working. I.e. sysObjectId 5.5.5.5
(
Note: I also
On 1 October 2010 21:13, wrote:
> How do I modify the snmp agent to get it to report a different enterprise
> number?
$ man snmpd.conf
sysDescr STRING
sysObjectID OID
sets the system description or object ID for the agent.
Although
hat I need to do is be able to discover the Host with a "bridge" probe, and
the VM guests with a "system" probe. My problem is that the probes are invoked
based on the sysobjectid. I need to be able to change the sysobjectid on
the HOST Redhat systems, so that it do
> On Wed, 22 Sep 2010 10:37:39 -0400, Fulko Hew said:
FH> I just tested rc3... and I give that release/patch _my_ blessing.
Thanks for the positive feedback!
FH> Now it would be nice If I could also get my other two patches
FH> incorporated that prevent net-SNMP from core dumping under cert
On Mon, Sep 20, 2010 at 8:22 PM, Wes Hardaker <
harda...@users.sourceforge.net> wrote:
> > On Thu, 16 Sep 2010 12:41:38 -0400, Fulko Hew
> said:
>
> FH> Are there any other scenarios that I missed testing?
>
> FYI, I applied your patch to the trunk today.
>
Great!
I just tested rc3... and I
> On Thu, 16 Sep 2010 12:41:38 -0400, Fulko Hew said:
FH> Are there any other scenarios that I missed testing?
FYI, I applied your patch to the trunk today.
--
Wes Hardaker
Please mail all replies to net-snmp-coders@lists.sourceforge.net
On Fri, 17 Sep 2010 13:57:23 -0700 Wes wrote:
WH> This is a patch to patch 2900078 which fixed and broken sysObjectID.
+1
--
Start uncovering the many advantages of virtual appliances
and start using them to simpl
Wes Hardaker wrote:
> This is a patch to patch 2900078 which fixed and broken sysObjectID.
> The patch suggestion comes from Fulko Hew via -coders discussion and
> works for me.
Looks sensible. +1.
+Thomas
---
On Fri, 2010-09-17 at 13:57 -0700, Wes Hardaker wrote:
> This is a patch to patch 2900078 which fixed and broken sysObjectID.
> The patch suggestion comes from Fulko Hew via -coders discussion and
> works for me.
+1
Related to that is the fact that system_parse_config_sysObje
This is a patch to patch 2900078 which fixed and broken sysObjectID.
The patch suggestion comes from Fulko Hew via -coders discussion and
works for me.
Modified net-snmp/agent/mibgroup/mibII/system_mib.c
diff --git a/net-snmp/agent/mibgroup/mibII/system_mib.c
b/net-snmp/agent/mibgroup
esterday
> but got distracted. After making the above change does it fix your
> problem?
>
Yes, It did for me.
I tested:
1/ Net-SNMP reporting its 'internally' defined sysObjectID
2/ a sysObjectID override in the snmpd.conf file.
Are there any other scenarios that I missed testing
> On Wed, 15 Sep 2010 16:00:42 -0400, Fulko Hew said:
FH> WATCHER_MAX_SIZE | WATCHER_SIZE_IS_PTR | WATCHER_SIZE_UNIT_OIDS,
FH> whereas the value passed in via sysObjectIDByteLength has already been
FH> converted
FH> into bytes. so the above statement on line 339
FH> should instead be:
FH>
On Wed, Sep 15, 2010 at 2:52 PM, Fulko Hew 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.
&
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
phil_webs...@dell.com wrote to net-snmp-b...@lists.sourceforget.net:
> Using the sysobjectid directive in snmpd.conf will not work when
> sizeof(oid) > 1.
>
> Here is the patch to system_mib.c that fixes this problem:
Thanks for the patch! Could you please post it to
http://w
Hi All, I am newbie to snmp.
As part of one of the vendor request, I am trying to put the
sysObjectID access to this namespace (1.3.6.1.4.1.234.9.1.9)
sysObjectID should be OBJECT IDENTIFIER ::= { xyz }
1.3.6.1.4.1.234.9.1.9
So I changed my code to register oid for sysObjid to
Hi All, I am newbie to snmp.
As part of one of the vendor request, I am trying to put the
sysObjectID access to this namespace (1.3.6.1.4.1.234.9.1.9)
sysObjectID should be OBJECT IDENTIFIER ::= { xyz }
1.3.6.1.4.1.234.9.1.9
So I changed my code to register oid for sysObjid to
tags 363399 + patch
stop
On 08.06.06 Thomas Anders ([EMAIL PROTECTED]) wrote:
> Hilmar Preusse wrote:
Hi Thomas,
> >So it seems to be a bug in 5.2.2, which has been fixed in 5.3.0.
> >Consider to upgrade the Debian package.
>
> I've just fixed this bug in the 5.2.x CVS branch, too. Patch
> atta
Hilmar Preusse wrote:
> Is the 5.2.2 still actively developed?
> Anyway, the patch fixes the problem. I leave in the DBTS a marker
> that there is a patch for the problem.
The 5.2.x branch is still maintained -- in bug-fixes only mode.
The release cycle for 5.2.3 will start anytime soon, probably
mibII/system_mib.c 11 Aug 2005 17:39:36 - 5.12
@@ -283,7 +283,7 @@
"sysobjectid token not a parsable OID:\n\t%s",
cptr);
config_perror(tmpbuf);
-memcpy(sysObjectID, version_sysoid, version_sysoid_len);
+memcpy(sysObjectID,
>On 5.3.1.pre1, 5.3.1.pre3 and 5.3.0.1.
>
> foo# snmptranslate -mall .1.3.6.1.4.1.8072.3.2.10
> NET-SNMP-TC::linux
>
> So I don't think there's any problem with the (official) net-snmp
> sources. This obviously the correct sysObjectID.0.
>
I did the same experiment u
On 29.05.06 Thomas Anders ([EMAIL PROTECTED]) wrote:
> Hilmar Preusse wrote:
Hi,
> >[EMAIL PROTECTED]:~ $ snmpget -v2c -c public 127.0.0.1:161 .1.3.6.1.2.1.1.2.0
> >SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::dod.0.0.0.0.0.0.0
> >
> >. I've rebuilt the package f
.10
NET-SNMP-TC::linux
So I don't think there's any problem with the (official) net-snmp
sources. This obviously the correct sysObjectID.0.
+Thomas
--
Thomas Anders (thomas.anders at blue-cable.de)
___
Net-snmp-coders mai
Hilmar Preusse wrote:
[EMAIL PROTECTED]:~ $ snmpget -v2c -c public 127.0.0.1:161 .1.3.6.1.2.1.1.2.0
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::dod.0.0.0.0.0.0.0
. I've rebuilt the package from the sources and got the same result.
The configure options of the package do not manipulat
On 28.04.06 Wes Hardaker ([EMAIL PROTECTED]) wrote:
> > On Sat, 22 Apr 2006 11:35:10 +0200, Hilmar Preusse <[EMAIL PROTECTED]>
> > said:
>
> Hilmar> The "net-snmp-admin PGP key" has expired:
>
> Hilmar> [EMAIL PROTECTED]:~ $ gpg --list-keys 7800FEAC
> Hilmar> pub 1024D/7800FEAC 2003-01
> On Sat, 22 Apr 2006 11:35:10 +0200, Hilmar Preusse <[EMAIL PROTECTED]>
> said:
Hilmar> The "net-snmp-admin PGP key" has expired:
Hilmar> [EMAIL PROTECTED]:~ $ gpg --list-keys 7800FEAC
Hilmar> pub 1024D/7800FEAC 2003-01-15 [expired: 2006-01-14]
Hilmar> uid Net-SNMP Ad
On 20.04.06 Thomas Anders ([EMAIL PROTECTED]) wrote:
Hi,
BTW:
The "net-snmp-admin PGP key" has expired:
[EMAIL PROTECTED]:~ $ gpg --list-keys 7800FEAC
pub 1024D/7800FEAC 2003-01-15 [expired: 2006-01-14]
uid Net-SNMP Administrators <[EMAIL PROTECTED]>
Regards,
Hilmar
--
sig
he default configuration. Result:
[EMAIL PROTECTED]:~ $ snmpget -v2c -c public 127.0.0.1:161 .1.3.6.1.2.1.1.2.0
SNMPv2-MIB::sysObjectID.0 = OID: SNMPv2-SMI::dod.0.0.0.0.0.0.0
. I've rebuilt the package from the sources and got the same result.
The configure options of the package do not m
Hilmar Preusse wrote:
So should we go for linux and unknown as platform? Or always
unknown?
I've upstream in Cc. Ask them for either updating the MIB or go for
unknown.
Can you please give your exact platform details?
"unknown" should cover any system not mentioned explicitely before:
hpux9
Hi Hilmar,
> The default value of the sysObjectID is .1.3.6.0.0.0.0.0.0.0, which
> is not a valuable information. I've compared it to an how grown net
> snmp 5.0.6, which give out on that OID the value
> .1.3.6.1.4.1.8072.3.2.xx (where xx is one of the numbers 1-13
> dependi
On 19.04.06 Jochen Friedrich ([EMAIL PROTECTED]) wrote:
Hi Jochen,
> > The default value of the sysObjectID is .1.3.6.0.0.0.0.0.0.0, which
> > is not a valuable information. I've compared it to an how grown net
> > snmp 5.0.6, which give out on that OID the value
>
On Tue, 2006-02-07 at 14:05 -0800, Fong Tsui wrote:
> Does sysObjectID need to be top OID of MIB of the system?
No.
> My original .1.3.6.1.2.1.1.2 == .1.3.6.1.4.1.XXX.2
> The all MIB of the system is under .1.3.6.1.4.1.XXX.2
Is this from a vendor-supplied agent?
The standard
Fong Tsui wrote:
Now if I change .1.3.6.1.2.1.1.2 == .1.3.6.1.4.1.XXX.2.1.3.3.2. All
other MIB stays the same.
Will it be a problem?
Not that I'm aware of.
+Thomas
--
Thomas Anders (thomas.anders at blue-cable.de)
---
This SF.net email
Does sysObjectID need to be top OID of MIB of the system? In
RFC1213-MIB.txt, it doesn’t have this requirement.
My original .1.3.6.1.2.1.1.2
== .1.3.6.1.4.1.XXX.2
The all MIB of the system is
under .1.3.6.1.4.1.XXX.2
Now if I change .1.3.6.1.2.1.1.2
== .1.3.6.1.4.1.XXX.2.1.3.3.2
34 matches
Mail list logo
