Hello All,
net snmp clients (snmpwalk and snmpget) understand types OPAQUE_DOUBLE and
OPAQUE_FLOAT.
However, these are not recognized by HP OpenView and other clients.
Does somebody know a workaround? Is the any way how to teach HP OpenView
(e.g via MIBs) to correctly interpret OPAQUE_DOUBLE
Hello Dave,
thanks for your confirmation. We were trying to avoid string
representation of floats since it is difficult to compare them (e.g. to
preset thresholds).
We will consider fixed point as you are suggesting.
Milan
On Tue, October 2, 2007 10:06 am, Dave Shield wrote:
On 02/10/2007,
Hello Dave,
thanks for replying. For some odd reason I did not get your mail on Tuesday.
I am desperately trying different settings in snmpd.conf but w/o any success.
The current settings are:
com2sec paranoid default public
com2sec readonly default public
com2sec readwrite
Hello Dave,
thanks for your prompt reply.
I will use rocommunity public
but what about view and access ?
MIlan
On Thu, September 6, 2007 12:08 pm, Dave Shield wrote:
On 06/09/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
I am desperately trying different settings in snmpd.conf but w/o
Hello Mike,
the reason for the fact that 1.3.6.1.4.x requests were not passed from the
master agent to the subagent was default (=incorrect in this case) access
configuration of snmpd.conf.
After replacing default with
rocommunity public default .1
things started to work fine.
Previously, I
Hello guys,
I am struggling with netsnmp_handler_registration_create.
I am able to register handlers for some OIDs and I receive requests in the
handler. E.g. when I register for .1.3.6 I receive request for
1.3.6.1.2.1.1.9.1.5.
When I register for 1.3.6.1.4 or 1.3.6.1.4.x.y the requests are
Hello all,
I am experiencing a strange problem. I have written a simple common
handler for MOD_GET a MOD_GETNEXT.
The handler seems to work fine but certain SNMP requests are not passed to
the handler.
Example:
snmpget -v 1 -c public localhost .1.3.6.1.2.1.1.1.1is passed.
snmpget -v 1 -c
Hello Bruce,
I am writing a main agent so I am not running snmpd at all since it would
conflict with my agent.
Is there any way how to turn on debugging in the API functions?
I worked with several logging systems and all of them had some kind of
set_log_level function for filtering of
Hello Graeme,
sorry for bothering you again.
I have tried to merge your code with MFD code. I am obviously doing
something wrong. When I run snmpwalk on the agent I can see that
agent_check_and_process(1) in the main loop finishes but the handler does
not get called.
I get error message from
Hello Graeme,
thanks for your prompt reply.
netsnmp_register_handler( reg ) is hidden in
printf(returned=%d\n, netsnmp_register_handler(reg));
I tried it before without printf and it was doing the same thing.
I have no other handlers and no other agents started.
I considered switching snmp
Hello all,
I am wondering, does somebody know how to set snmp logging level/priority
in C code?
I went through the docs and found only functions for directing logging
output (such as snmp_enable_stderrlog()).
I would like to turn on the DEBUG level to get all the API messages. I do
NOT mean
Hello,
I tried even a specific OID.
I am using snmpwalk on localhost with .1.3.6. I hope this should generate
some requests that could be passed to the handler function.
On the agent side I am getting
Connection from UDP: [127.0.0.1]:-32767
On the snmpwalk side I am getting request timeout.
Hello Graeme,
thanks for your reply.
I will try your code. It seems it might be close to what I need.
Have a nice day.
Milan
On Wed, August 8, 2007 11:11 am, Graeme Wilson wrote:
Hi,
I have done something similar recently (I provide some sample code below
- but note that ultimately
Hello Graeme,
I went through your code and it seems it is exactly what I need.
I am just confused about one thing: how does it plug into snmpd?
I understand that I need to do in agent main() registration (and
un-registration at agent finish) but what do I actually generate?
Should I create a
Hello Mike,
thanks for replying to my question.
I understand that a standard approach is to register the agent for a range
of OISs and to let the agent to be OID aware while the other process
should take care of the underlaying data.
However, I was asked to write an agent that would NOT be
Hello,
I intend to write a simple Net-SNMP agent that would get data from another
process using Inter-process procedure call.
The ideas is as follows: the agent would receive from the SNMP daemon
requests for a given range of OIDs (a sub-tree) pass them to the other
process. The other process
16 matches
Mail list logo
