I am trying to extend agent to support my mib. I was using old api before
but this time I decided going into the newer one. So I started by using
mib2c.mfd.conf as mib2c configuration file and after some effort by
following ifTable tutorial in net-snmp site I succeeded in processing get
requests.
I am trying to extend agent to support my mib. I was using old api before
but this time I decided going into the newer one. So I started by using
mib2c.mfd.conf as mib2c configuration file and after some effort by
following ifTable tutorial in net-snmp site I succeeded in processing get
requests.
Gefei Jiang gji...@ixiacom.com writes:
When I do snmpwalk on one of my table (ntpTable) it displays
Very odd. Can you run snmpwalk with both -d and -Ddump and send us that
output?
--
Wes Hardaker
Parsons
--
Learn
###
-Original Message-
From: Wes Hardaker [mailto:harda...@users.sourceforge.net]
Sent: Thursday, April 17, 2014 6:40 AM
To: Gefei Jiang
Cc: net-snmp-users@lists.sourceforge.net
Subject: Re: Error in packet. Reason: Unknown Error
Hi Everyone,
Is there anyone who has a solution to the issue below:
When I do snmpwalk on one of my table (ntpTable) it displays
the oids with the correct value
Error in packet.
Reason: Unknown Error
I just upgraded my snmp agent (snmpd) from 5.4.2 to 5.7.2.1. Before the upgrade
Hi ,
I am facing this problem in Linux platform.
Can anybody know wats the issue..
Removing DSP from service will fail a general snmpwalk with error in
packet / general failure.
seeing an issue when DSP card in chassis ins removed from service.
Subsequent snmpwalks to chassis aborts
: [192.168.0.211]:39088
Error in packet
Reason: (noSuchName) There is no such variable name in this MIB.
Failed object: UCD-SNMP-MIB::ucdExperimental.18.1.1.3.1
linux-6m2a:/usr/share/snmp/mibs # snmpwalk -v1 -c public 192.168.0.211
.1.3.6.1.4.1.2021.13.18.1.1.3.1
Connection from UDP: [192.168.0.211
I compiled and ran nstAgentSubagentObject example successfully.Then I added a
handler in registration call ( Please see the code below)(a simple subroutine
just print a string).I can compile and run my subagent but when I try to run
snmpget or snmpset I get the error:
Error in Packet
:
Error in Packet.
Reason: (gen Error) A general Failure occured)
Faild Object: NET-SNMP-TUTORIAL-MIB::nstAgentSubagentObject.0
If I remark that printf and compile it again then I can retrieve/set MIB
through snmpget and set.
If I add a sum or sub in code it wont work again
I
Hi Dave,
Sorry, the below issue is a false alarm.
The user has encountered a firewall issue.
So NET-SNMP is properly using the authoritative
engine ID for discovery!
Cheers,
Frank
Frank Fock wrote:
Hi Dave,
I have not forgotten to put together the AgentX
issues that I have found while
Hi Dave,
I have not forgotten to put together the AgentX
issues that I have found while testing NET-SNMP
interoperability. I think I can provide that
report next weekend.
Meanwhile I came across another issue related
to NET-SNMP:
SNMP4J(-Agent) supports engine ID discovery.
A SNMP4J user
Hi Dave,
I have placed this issue on the AgentX mailing list
and reached consensus regarding the null object
identifier usage. This zero length OID must be used
where explicitly mentioned in RFC2741 only. The
references I found refer to the AgentXOpen PDU
and AgentX SearchRanges. A zero length
On 21/02/07, Frank Fock [EMAIL PROTECTED] wrote:
I have placed this issue on the AgentX mailing list
and reached consensus regarding the null object
identifier usage.
Yes - I've been following the discussion.
Do you have an estimation in which NET-SNMP version
this fix will be available?
Hello again
I'll bring it up with the Agentpp developers to see if they should deal
with this differently. At least it seems like they should.
Just a follow up with the answer from Frank Fock:
a 0.0 OID should be encoded like:
02 00 00 00
00 00 00 00
00 00 00 00
and not
00 00 00 00
which
On 14/02/07, Johnny Ljunggren [EMAIL PROTECTED] wrote:
Just a follow up with the answer from Frank Fock:
a 0.0 OID should be encoded like:
02 00 00 00
00 00 00 00
00 00 00 00
and not
00 00 00 00
which is actually a zero length OID
Frank,
how do you interpret the last paragraph of
Hi Dave,
Good point, section 5.1 clearly states that
a null Object Identifier should be encoded
as four 0 bytes. From my point of view,
the term a null Object Identifier refers to
a zero length OID. Given that this is true,
the encoding would be consistent with the
actual value (both have a zero
Dave Shield wrote:
Hmmm, is there a way to block only these types of OID's?
Look in 'agent/mibgroup/agentx/protocol.c' in the
routine agentx_realloc_build_oid(). The first block
of code is special-case handling for the Null OID.
Hurrah, it works!
That should encode .0.0 just as any
On 10/02/07, Johnny Ljunggren [EMAIL PROTECTED] wrote:
Dave Shield wrote:
Can you try turning on packet dumps in the subagent
and issue a GET request for one of the offending instances.
I wasn't quite sure how to do it, but I've got debug output from my master
agent, and an ethereal dump.
Hello
Can you try turning on packet dumps in the subagent
and issue a GET request for one of the offending instances.
I'm not sure whether you're using the normal Net-SNMP agent
running as a subagent, or the simpler subagent-specific framework.
I'm probably using the normal agent. More
On 12/02/07, Johnny Ljunggren [EMAIL PROTECTED] wrote:
Didn't get any output with snmpd -f -X -d but adding -D ALL gave a lot
more information.
Yes - it tends to!
I have extracted the info around the ifSpecific.1 snmpget and put it here:
http://www.navtek.no/~johnny/snmpd/agentxdump.log
Dave Shield wrote:
Didn't get any output with snmpd -f -X -d but adding -D ALL gave a lot
more information.
Yes - it tends to!
:) I couldn't find any information about the different tokens available. I
didn't have access to internet either so I was unable to search for it.
The only thing I
On 12/02/07, Johnny Ljunggren [EMAIL PROTECTED] wrote:
Hmmm, is there a way to block only these types of OID's? It would at least
help through the first deadline I've got.
Try the following.
Look in 'agent/mibgroup/agentx/protocol.c' in the
routine agentx_realloc_build_oid(). The first block
Dave Shield wrote:
On 08/02/07, Johnny Ljunggren [EMAIL PROTECTED] wrote:
I'm pretty sure that the problem lies in the encoding of the OID .0.0,
Can you try turning on packet dumps in the subagent
and issue a GET request for one of the offending instances.
I wasn't quite sure how to do it,
Dave Shield wrote:
I'm pretty sure that the problem lies in the encoding of the OID .0.0,
Can you try turning on packet dumps in the subagent
and issue a GET request for one of the offending instances.
I wasn't quite sure how to do it, but I've got debug output from my master
agent, and an
On 09/02/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
DURING SNMPWALK COMMAND I GOT THIS ERROR..WHAT IS THE SOLUTION..
Error in packet.
Reason: (genError) A general failure occured
The agent didn't like something about the request.
A somewhat vague answer, I know - but it matches
On 08/02/07, Johnny Ljunggren [EMAIL PROTECTED] wrote:
I'm pretty sure that the problem lies in the encoding of the OID .0.0,
Any progress?
Sorry - paid work got in the way :-(
Can you try turning on packet dumps in the subagent
and issue a GET request for one of the offending instances.
Dave Shield wrote:
I'm pretty sure that the problem lies in the encoding of the OID .0.0,
Any progress?
Sorry - paid work got in the way :-(
No worries. BTW: I'm willing to pay to get this sorted though.
Can you try turning on packet dumps in the subagent
and issue a GET request for one
I'm pretty sure that the problem lies in the encoding of the OID .0.0,
Any progress? I'll try to look myself, but my knowledge of the AgentX
protocol and inner workings of net-snmpd is limited.
A short-time solution for me would be to block all output of .0.0-OID's.
How can I go about doing
HI..
DURING SNMPWALK COMMAND I GOT THIS ERROR..WHAT IS THE SOLUTION..
Error in packet.
Reason: (genError) A general failure occured
mail2web.com – Enhanced email for the mobile individual based on Microsoft®
Exchange - http
Dave Shield wrote:
On 02/02/07, Johnny Ljunggren [EMAIL PROTECTED] wrote:
I've made a master AgentX (using agentpp) that uses net-snmp as subagent
I've done a bit of poking about, and suspect that the Net-SNMP subagent
may
be returning an invalid encoding of .0.0 within the AgentX packet.
On 06/02/07, Johnny Ljunggren [EMAIL PROTECTED] wrote:
Unfortunately the patch didn't seem to help.
Pity :-(
OK - I'll have another look.
One interesting output from this log:
IF-MIB::ifSpecific.1 = Wrong Type (should be OBJECT IDENTIFIER): Variable
has bad type
Yes - I spotted this and got
On 02/02/07, Johnny Ljunggren [EMAIL PROTECTED] wrote:
I've made a master AgentX (using agentpp) that uses net-snmp as subagent
to provide mib-II information. I get a general failure if I try to get
some of the OIDs.
I did some more research and found that only the OIDs defined as OID:
I've made a master AgentX (using agentpp) that uses net-snmp as subagent
to provide mib-II information. I get a general failure if I try to get
some of the OIDs.
I did some more research and found that only the OIDs defined as OID:
SNMPv2-SMI::zeroDotZero will give this error.
ie.
2c -c public localhost
snip some output
IF-MIB::ifOutQLen.2 = Gauge32: 0
IF-MIB::ifOutQLen.3 = Gauge32: 0
Error in packet.
Reason: (genError) A general failure occured
Failed object: IF-MIB::ifOutQLen.3
# snmpwalk -v 2c -c public localhost IF-MIB::ifOutQLen.3
Error in packet.
Reason: (genError
34 matches
Mail list logo
