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 tried the following in my conf file, without success:
override 1.3.6.1.2.1.1.2 object_id 5.5.5.5
)
The right answer is to use a more recent version, but...
x64 builds of 5.6 and 5.7 are not available for download.
(and I don't have a Windows dev system, so I can't build it for them.)
My thought was that I could create an AgentX sub-agent that
registers itself on the sysObjectID OID, and would provide my
custom value.
I've tried it, but my sub-agent never gets called.
I've tried it at the default priority of 127, a higher priority
of 1 and a lower priority of 254 during the Register-PDU transaction.
Regardless of what I've tried, the response is always 'NoError',
but my agent never gets called. Am I missing something in the
config file that allows hijacking to occur?
TIA
Fulko
------------------------------------------------------------------------------
Keep Your Developer Skills Current with LearnDevNow!
The most comprehensive online learning library for Microsoft developers
is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3,
Metro Style Apps, more. Free future releases when you subscribe now!
http://p.sf.net/sfu/learndevnow-d2d
_______________________________________________
Net-snmp-coders mailing list
Net-snmp-coders@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/net-snmp-coders
