I thought I'd post it here too, for the record:
I submitted an according patch to the tracker:
"SNMPv3 trapsess engineID override" - ID: 3062526
http://sourceforge.net/tracker/?func=detail&aid=3062526&group_id=12694&atid=312694
BR,
Mario
> From: harda.
Forgot to add this:
When I finish with a configure, I get the following as a table:
SNMP Versions Supported 1 2c 3
Building for: nto
Net-SNMP Version: 5.6.rc2
network transport support : Callback Unix Alias TCP UDP IPv4Base SocketBase
TCPBase UDPIPv4Base UDPBase
SNMPv3 Securit ModulesL usm
Agent
Hello
I have followed your suggestion, and get exactly the same error message, as I
posted earlier.
Note, I put in the arguments after the configure.
This error message, comes when I do a 'make agent'.
Regards
From: abraham.varric...@googlemail.com
[mailto:abraham.varric...@googlemail.com] O
On Thu, Sep 16, 2010 at 1:04 AM, Ron Rader wrote:
> However, when I repeated the commands using the network broadcast
> address, snmpget on the Windows machine returned only the first:
>
> C:\>snmpget -v 2c -c public 192.168.63.255 system.sysName.0
> SNMPv2-MIB::sysName.0 = STRING: Smoketest Ter
On Thu, Sep 16, 2010 at 12:11 AM, Ali Mirza, Rashid <
rashid.alimi...@salik.ae> wrote:
> since i was running QNX in VMware, i just re-started the virtual machine,
> and made sure date and time were correct.
> Then i did a configure, without any arguments,
> Then did a make, and am getting the foll
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.
> I.e.
>
> 1.3.6.1.2.1.1.2.0:
> 1.3.6.1.4.1.8072.3.2.10
Hi,
I am having problem with net-snmp ver 5.5. on Solaris 10.
I compiled with gcc v3.4.6
The snmpd was working fine until using "repeat" in the snmpd.conf. But I added
the following:
repeat 300 versionUpdateConfig.0 = 1
then I got:
/etc/snmp/snmpd.conf: line 128: Error: invalid specification
> From: Reinhold Kainhofer [mailto:reinh...@kainhofer.com]
> > An alternative you might try is to derive your individual IP
network
> > broadcast address and see if that works.
> Thanks for the hint, but that doesn't work either
That's unfortunately also common.
I guess that the net-snmp
> From: Reinhold Kainhofer [mailto:reinh...@kainhofer.com]
> get a permission denied, even as root:
>
> r...@einstein:~# snmpget -v 2c -c public 255.255.255.255
1.3.6.1.2.1.1.1.0
> \
> 1.3.6.1.2.1.1.2.0 1.3.6.1.2.1.2.2.1.6.1
> snmpget: Failure in sendto (Permission denied)
This probably h
Am Mittwoch, 15. September 2010, 21:06:16 schrieben Sie:
> > From: Reinhold Kainhofer [mailto:reinh...@kainhofer.com]
> >
> > get a permission denied, even as root:
> >
> > r...@einstein:~# snmpget -v 2c -c public 255.255.255.255
> 1.3.6.1.2.1.1.1.0 1.3.6.1.2.1.1.2.0 1.3.6.1.2.1.2.2.1.6.1
> > snm
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.0.0.0.0.0
and
Hello
this is a continuation of a old thread where the title was net-snmp 5.2.X
compilation errors in QNX Momentics 6.3.0.
I would really appreciate if someone who was compiled the latest version in
QNX, or for that matter any version, and got it working.
Here is my last posting with the error
On Wed, Sep 15, 2010 at 12:01 PM, Fulko Hew wrote:
> On Wed, Sep 15, 2010 at 11:23 AM, Dave Shield
> wrote:
>
>> On 14 September 2010 16:55, Fulko Hew wrote:
>> > When I ran this test, the agent died and needed to be restarted.
>> > The variable I was querying was:
>> >
>> > 1.3.6.1.4.1.2021.8.
hello,
when using snmp tables, is there a way to get to a exact row number.
currently i have to traverse all the rows to get to the one i want.
thanks,
brad.
--
Start uncovering the many advantages of virtual appliances
When search "mailing lists", it does not return anything. (I tried to use very
common keyword, definitely occurred in the discussion.) "Tracker" section
works.
Thanks,
Wei
--
Start uncovering the many advantages of vir
For the SANE (scanner driver) backend of the KONICA MINOLTA magicolor 1690mf
device, I'm implementing SNMP device discovery. It works by sending an SNMP
request to 255.255.255.255 for the OIDs
1.3.6.1.2.1.1.1.0 (SNMPv2-MIB::sysDescr.0)
1.3.6.1.2.1.1.2.0 (SNMPv2-MIB::sysObjectID.0)
1.3.6.1.2.1.2.2
On Wed, Sep 15, 2010 at 11:23 AM, Dave Shield wrote:
> On 14 September 2010 16:55, Fulko Hew wrote:
> > When I ran this test, the agent died and needed to be restarted.
> > The variable I was querying was:
> >
> > 1.3.6.1.4.1.2021.8.1.103.4294967295 aka 'UCD-SNMP-MIB:extIndex'.
>
> Do you get th
On 14 September 2010 16:55, Fulko Hew wrote:
> When I ran this test, the agent died and needed to be restarted.
> The variable I was querying was:
>
> 1.3.6.1.4.1.2021.8.1.103.4294967295 aka 'UCD-SNMP-MIB:extIndex'.
Do you get the same problem when querying
1.3.6.1.4.1.2021.8.1.103.429496729
On Wed, Sep 15, 2010 at 9:27 AM, Fulko Hew wrote:
> On Tue, Sep 14, 2010 at 11:55 AM, Fulko Hew wrote:
>
> ... snip ...
>
>> When I ran this test (snmpgetnext), the agent died and needed to be
>> restarted
>>
>> snmpgetnext -v1 -cpublic -Ir localhost
1.3.6.1.4.1.2021.8.1.103.4294967295
... snip
On Tue, Sep 14, 2010 at 11:55 AM, Fulko Hew wrote:
... snip ...
> When I ran this test (snmpgetnext), the agent died and needed to be
restarted.
> The variable I was querying was:
>
> 1.3.6.1.4.1.2021.8.1.103.4294967295 aka 'UCD-SNMP-MIB:extIndex'.
>
> (FYI. it also happens on other variable
Hi All,
Could anyone tell me authentication[md5-hmac/sha-hmac] of
snmp message done
only on "scoped pdu" or "complete snmp Packet" ?
Rgds,
sanjay
--
Start uncovering the many advantages of virtual applian
21 matches
Mail list logo
