Wes,

Thanks for taking the time to read the problem.  Just wanted to bump cuz I'm 
leaving this position and wanted to try and button this up before I am gone. I 
understand completely that this is volunteer only :D We're currently planning 
on migrating from 5.4.1.2 to  5.6.1 but this problem with HP is hampering that 
effort.

Anyways to answer your questions.

>What's the exact command line you're using [obfuscating any secrets of
>course]?  Can you walk anything with the command line, or are you just
>missing that particular section of the mib tree?

The exact command I'm using is:
Snmpwalk -c <comm> -v2c localhost:<portnumber> .enterprises.232 ( can also use 
.1.3.6.1.4.1.232 - but yields same results )


>If you can walk other parts of the tree, but not that one then the
>problem is either with the agent you're talking to (which I think you
>said is HPs, but some of your sentences seemed to contradict that).  If
>it's with the HP agent you'll need to talk to them, of course, as we're
>not likely able to tell you what they're agent supports and doesn't.

This appears only to be a problem with this module in conjunction with net-snmp 
5.6.1.  A walk of a freshly compiled SNMP 5.6.1 agent with the configure 
options listed in the original email provide me a perfectly good walk.  After 
the walk, I register the hp shared object with the snmpd.conf using a dlmod 
line in the snmpd.conf ( dlmod /usr/lib64/libcmaX64.so ).  After I do that I 
get all of the errors listed in the original email and get no response on 
.enterprises.232 ( hp's oids ).  If I do the exact same thing on any older 
version of net-snmp ( with the same version of the shared object  from HP ) 
everything works fine and I can walk .enterprises.232.  So Net-SNMP 5.5 ( which 
comes with RHEL6 ) works.  Our old version of net-snmp (5.4.1.2) works.  The 
only one that doesn't is this latest version 5.6.1.  I was really trying to 
find out if anything was done with dlmod functionality that might account for 
the difference.

HP doesn't want to support this because they're saying that Net-SNMP doesn't 
provide a binary for RHEL6 x64 and RHEL 6 x64 currently only provides net-snmp 
5.5 ( which works ).  So kinda stuck between a rock and a hard place and not 
sure at this point if it's HP's code that for some reason only refuses to run 
on 5.6.1 or if it's net-snmp 5.6.1 and changes to it that's causing the problem.

I guess I shouldn't call the hp agent an agent in regards to net-snmp.  It is 
servicing the oids but is providing it's own code via the shared object that I 
loads in via the dlmod.  It's when it registers itself that I'm seeing all 
those duplicate oid registration errors.  If I remove the dlmod line all those 
duplicate errors go away so definitely with that shared object.

> That means two different mib implementations are trying to register at
> the same OID.  Generally this is the result of a misconfigured compile
> or a misconfigured master/subagent pair.

Would that be the net-snmp agent that would be misconfigured or would that be 
the HP shared object?  I did not include any CPQ mibs in the compile when I did 
it.

Thank you Wes,
Jayson

-----Original Message-----
From: Wes Hardaker [mailto:[email protected]] 
Sent: Wednesday, April 20, 2011 1:15 PM
To: Robinson, Jayson A
Cc: [email protected]
Subject: Re: net-snmp 5.6.1 and hp's snmp agents.

>>>>> On Tue, 19 Apr 2011 12:34:12 -0400, "Robinson, Jayson A" 
>>>>> <[email protected]> said:

RJA> Anyone have anything on this?

Unfortunately, the nice people on the list that spend there time
responding to questions generally do so 'when they have time' (cause no
one pays them to do it).  You'll likely need to be patient sometimes...

RJA> Having an issue with net-snmp 5.6.1 and the latest versions of the hp
RJA> snmp agents ( 8.6.3 and 8.7 ).  Anyone have anything similar?  Any
RJA> thoughts where I should go next for support?

RJA> 1.  Cannot walk .enterprises.232 ( HP's SNMP oids ) -
RJA> SNMPv2-SMI::enterprises.232 = No Such Object available on this agent
RJA> at this OID

What's the exact command line you're using [obfuscating any secrets of
course]?  Can you walk anything with the command line, or are you just
missing that particular section of the mib tree?

If you can walk other parts of the tree, but not that one then the
problem is either with the agent you're talking to (which I think you
said is HPs, but some of your sentences seemed to contradict that).  If
it's with the HP agent you'll need to talk to them, of course, as we're
not likely able to tell you what they're agent supports and doesn't. 

Is the HP agent a subagent or the master agent?

RJA> 2.  Receive the following output in the snmpd.log 1861 times:
RJA> duplicate registration: MIB modules CompaqInsight and CompaqInsight
RJA> (oid XXXXXXXX ) - where XXXXXXXX is one of 163 unique oids.

That means two different mib implementations are trying to register at
the same OID.  Generally this is the result of a misconfigured compile
or a misconfigured master/subagent pair.

-- 
Wes Hardaker
Please mail all replies to [email protected]
This communication is for informational purposes only. It is not
intended as an offer or solicitation for the purchase or sale of
any financial instrument or as an official confirmation of any
transaction. All market prices, data and other information are not
warranted as to completeness or accuracy and are subject to change
without notice. Any comments or statements made herein do not
necessarily reflect those of JPMorgan Chase & Co., its subsidiaries
and affiliates.

This transmission may contain information that is privileged,
confidential, legally privileged, and/or exempt from disclosure
under applicable law. If you are not the intended recipient, you
are hereby notified that any disclosure, copying, distribution, or
use of the information contained herein (including any reliance
thereon) is STRICTLY PROHIBITED. Although this transmission and any
attachments are believed to be free of any virus or other defect
that might affect any computer system into which it is received and
opened, it is the responsibility of the recipient to ensure that it
is virus free and no responsibility is accepted by JPMorgan Chase &
Co., its subsidiaries and affiliates, as applicable, for any loss
or damage arising in any way from its use. If you received this
transmission in error, please immediately contact the sender and
destroy the material in its entirety, whether in electronic or hard
copy format. Thank you.

Please refer to http://www.jpmorgan.com/pages/disclosures for
disclosures relating to European legal entities.

------------------------------------------------------------------------------
Fulfilling the Lean Software Promise
Lean software platforms are now widely adopted and the benefits have been 
demonstrated beyond question. Learn why your peers are replacing JEE 
containers with lightweight application servers - and what you can gain 
from the move. http://p.sf.net/sfu/vmware-sfemails
_______________________________________________
Net-snmp-coders mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders

Reply via email to