Niels Baggesen writes:
> > I tried with SimpleMib browser as well as MGSOFT Mib browser.
>
> In that case you should direct your question towards them, why they
> accept a trap with unknown credentials.
Indeed, some trap receivers always accept and print traps regardless of
whether or not it ha
Den 25-04-2023 kl. 17:46 skrev Simon Chamlian:
Something else.
I tried with SimpleMib browser as well as MGSOFT Mib browser.
In that case you should direct your question towards them, why they
accept a trap with unknown credentials.
Note, that you have asked to send the trap in the clear,
Something else.
I tried with SimpleMib browser as well as MGSOFT Mib browser.
On Tue, Apr 25, 2023 at 10:30 AM Niels Baggesen via Net-snmp-coders <
net-snmp-coders@lists.sourceforge.net> wrote:
> Which trap receiver are you using? snmptrapd, or something else?
>
> /Niels
> Den 25-04-2023 kl.
Which trap receiver are you using? snmptrapd, or something else?
/Niels
Den 25-04-2023 kl. 15:10 skrev Simon Chamlian:
I tried the command:
snmptrap -v 3 -u Simon -a MD5 -A SimonPass -l authNoPriv
172.27.37.227 "" coldStart.0
(with security name : Simon and authentication password : S
I tried the command:
snmptrap -v 3 -u Simon -a MD5 -A SimonPass -l authNoPriv 172.27.37.227
"" coldStart.0
(with security name : Simon and authentication password : SimonPass ).
These parameters are not set in any config files anywhere.
On another PC with IP 172.27.37.227, I have a MIB
On Sat, 15 Apr 2023 at 11:12, Simon Chamlian wrote:
>
> snmptrap -v 3 -u Simon -a MD5 -A SimonPass -l authNoPriv 172.27.37.227
> "" coldStart.0
>
> I do receive the trap on my Trap Receiver even if I didn't specify a
> Username and Authentication password in the MIB browser (on 172.27.37.227 )
On Tue, 08 Mar 2016 10:44:31 +0800 mr.seviien wrote:
MS> Hi Robert, I have some problem about snmpd.conf. For example,
MS> trapsink 192.168.1.2 public for sending v1 trap. trap2sink
MS> 192.168.1.2 public for sending v2c trap. My question is what
MS> configuration is for sending v3 trap? "Trapsess
Hi Robert, I have some problem about snmpd.conf. For example, trapsink
192.168.1.2 public for sending v1 trap. trap2sink 192.168.1.2 public for
sending v2c trap. My question is what configuration is for sending v3 trap?
"Trapsess " is wrong. Thanks! On 2016-03-04 21:21 , Robert Story Wrote: On M
On Mon, 24 Nov 2014 12:11:32 +0530 Rizwan wrote:
RA> Under IPv6 environment, sent snmptrap after setting clientaddr in
RA> snmp.conf, It is sent from another interface.
RA> [...]
RA> I looked into IPv4 code and feel like same code is missing under IPv6
RA> section.
Yes, I'd noticed that myself rec
On 9 November 2011 00:11, Nguyen Dinh Phong wrote:
> The question here is if it's OK to have two traps from the same system with
> different timestamp/uptime?
Sure - I don't see why not.
> Would it cause any confusion for the trap receiver?
That's impossible to answer - you haven't said anythi
Hi,
When I restart snmpd, I notice that the agent would come up and send a cold
start trap using its own uptime in the trap PDU, probably 1 sec. In my system,
there is also a monitoring process that sending a trap every time any process
in the system restart. For this, the uptime is the system
On 4 November 2011 11:53, wrote:
> I developed a “snmpd” application using netsnmp library and sending the trap
> from sub-agent to snmpd application by using the following command
>
> #snmptrap -v 3 -u MD5User -e 0x1020304050 -a MD5 -A "The Net-SNMP Demo
> Password" -l authNoPriv 10.140.185.
On 4 November 2011 06:37, Magnus Fromreide wrote:
> Also if you use agentxtrap instead of snmptrap then you have the option
> of not specifying the uptime. In that case the master agent will fill in
> the uptime so you get the behaviour you are asking for.
Note that in this case, it *is* the SNM
On Thu, 2011-11-03 at 23:52 +, Dave Shield wrote:
> On 3 November 2011 17:19, Nguyen Dinh Phong wrote:
> > Shouldn't the default uptime for the snmptrap utility
> > should also be the agent uptime?
>
> Not really, no.
>
> The uptime value is meant to be the uptime value of the sending SNMP e
On 3 November 2011 17:19, Nguyen Dinh Phong wrote:
> Shouldn't the default uptime for the snmptrap utility
> should also be the agent uptime?
Not really, no.
The uptime value is meant to be the uptime value of the sending SNMP entity.
If you're sending a trap using "snmptrap", then snmptrap is t
Den 19-09-2011 18:43, sundararaman.dheivanaya...@wipro.com skrev:
> Hi,
> Please provide some sample program to receive trap using net-snmp API.
apps/snmptrapd.c in the source tar-ball
/Niels
--
Niels Baggesen - @home - Århus - Denmark - n...@users.sourceforge.net
The purpose of computing is in
On 1 April 2011 00:54, akshata s harkantra wrote:
> After I identified the notifcation object, the following is working
>
> snmptrap -v 1
> But the same thing when I try using v2/v3 version ,It gives the following
> error [Changing -v to 2c or 3]
As Erik has indicated - the structure of S
mptrap.
Eirik Nordbrøden
(+47) 90174789
> From: akshata s harkantra [mailto:akshata.harkan...@gmail.com]
> Sent: 1. april 2011 01:54
> To: Dave Shield
> Cc: net-snmp-coders@lists.sourceforge.net
> Subject: Re: snmptrap command
>
> Thanks Dave for your suggestion.
>
Thanks Dave for your suggestion.
After I identified the notifcation object, the following is working
snmptrap -v 1 -c public -M "my mibs path" "address" SNMPv2-MIB::snmpTrapOID
localhost 5 1 '' SNMPv2-MIB::sysName.0 s "test"
For the above command I see the string "test" getting received on the
On 31 March 2011 07:48, akshata s harkantra wrote:
> I need to send a message or string using snmptrap command to the receiver end.
>snmptrap -v 2c -c public "ipaddress" sysDescr.0
No.
The OID that you send with snmptrap must be the OID of a *notification* object.
(i.e. one defined using NOT
On Thu, Jun 24, 2010 at 6:12 AM, Dave Shield wrote:
> On 23 June 2010 16:15, Leonardo Chiquitto wrote:
>> I just realized that v1 traps generated by "snmptrap" do not respect the
>> address set in "v1trapaddress". I understand this is expected because
>> the configuration option is exclusive to t
On 23 June 2010 16:15, Leonardo Chiquitto wrote:
> I just realized that v1 traps generated by "snmptrap" do not respect the
> address set in "v1trapaddress". I understand this is expected because
> the configuration option is exclusive to the agent (ie, set in snmpd.conf).
>
> Is this something wo
On Mon, 2010-01-25 at 13:48 -0800, nathan wrote:
> Hi,
> I'm wondering if are there any examples to show me how to implement
> snmptrap with acknowledgement, or snmpinform, from an agent. I am
> using agentx.
If you are sending traps from an agentx subagent then the semantics of
NOTIFY-PDU is tha
...@lysator.liu.se]
Sent: Friday, December 11, 2009 12:44 AM
To: Hayes, Paul - CS
Cc: net-snmp-coders@lists.sourceforge.net
Subject: Re: Snmptrap - how to specify the agent-addr for an IPv6 address
On Thu, 2009-12-10 at 18:10 -0500, Hayes, Paul - CS wrote:
> Dear Sirs,
> Wondering what the correc
On Thu, 2009-12-10 at 18:10 -0500, Hayes, Paul - CS wrote:
> Dear Sirs,
> Wondering what the correct form is for specifying an IPv6 source
> (agent-address) within an snmptrap command line?
>
> The trap will be issued to the target host IP address
> (2005::::0148:0036:0051:0001) when
On Tue, Mar 31, 2009 at 01:45:24PM -0700, dan anderson wrote:
> Repped to
> https://sourceforge.net/tracker/?func=detail&aid=2723881&group_id=12694&atid=112694
> with two solutions (depending on whether the problem is the app's
> fault for storing the source address in the wrong place or the
> lib
Repped to
https://sourceforge.net/tracker/?func=detail&aid=2723881&group_id=12694&atid=112694
with two solutions (depending on whether the problem is the app's
fault for storing the source address in the wrong place or the
library's for ignoring a field in the PDU it's given).
If anyone has the k
Tested and confirmed that setting pdu->agent_addr does not cause that
to be used as the agent's source address when snmp_send(session, pdu)
is called. (GNU/Linux, x86, close to default build options, but should
happen like this with the majority of cases.)
Is this a bug in the utility, or is this
On 05/12/06, Patai Tamás <[EMAIL PROTECTED]> wrote:
> Is it possible to get the clear result of the snmget command back to the
> application?
$ man snmpcmd
OUTPUT OPTIONS
-OvOutput only the variable value, not the OID:
snmpget -c public -v 1 -Ov localhost ip.ipForwar
Hi,
When I receive a trap I can send the 'snmptrapd' ouput to an application
that is configured in the snmpd.conf.
However there are traps where some member variables reference to OIDs. In
this case I have to make an 'snmpget' call for that mib variable.
Is it possible to get the clear result
Hi,
Finally I sent it and there was no problem.
thanks
Tamas
- Original Message -
From: "Dave Shield" <[EMAIL PROTECTED]>
To: "Patai Tamás" <[EMAIL PROTECTED]>
Cc: "Wes Hardaker" <[EMAIL PROTECTED]>;
Sent: Thursday, November 02, 2006 3:
On 02/11/06, Patai Tamás <[EMAIL PROTECTED]> wrote:
> For exaple this could be a trap I need to handle.
> The full text I gess is more than 1kB if I send it in this format:
[snip]
But you're *not* sending it in that format.
All of the OIDs will be transmitted as numeric OIDs (and binary value
ssage -
From: "Wes Hardaker" <[EMAIL PROTECTED]>
To: "Patai Tamás" <[EMAIL PROTECTED]>
Cc: <net-snmp-coders@lists.sourceforge.net>
Sent: Thursday, November 02, 2006 3:23
PM
Subject: Re: snmptrap length
>>>>>> "PT" == Patai Tamás <[
On 02/11/06, Patai Tamás <[EMAIL PROTECTED]> wrote:
> Is there an upper limit for the length of a trap the snmptrap can handle?
Yes - there does seem to be an upper limit, but it's fairly high.
Some quick tests show that snmptrap is happy with a payload of 36K,
but objects to a payload of 72K. (
> "PT" == Patai Tamás <[EMAIL PROTECTED]> writes:
PT> If there is such limitation, then is there an option for sending
PT> longer longer traps, ie. more than 500 or 1000 characters.
If your command line interface can't handle it, you could probably
build a C program that used the API to send
On Tue, 11 Apr 2006 16:01:11 +0300 Ofer wrote:
OG> snmpCmd = "/usr/bin/snmptrap -v 2c -c public " + nmsIpAddress +
OG> " '' PROXY-MIB::proxyWrongUserPassTrap
OG> PROXY-MIB::proxyWrongUserPassTrap s " + snmpTrapDesc;
OG> Logger.logInformation(this, snmpCmd);
OG> Run
> On Tue, 21 Feb 2006 10:07:59 +0100, "Christian Dahlqvist" <[EMAIL
> PROTECTED]> said:
Christian> I' would like to know what is the best practice in my
Christian> case. I want to use snmptrap in a embedded system with
Christian> limited memory to send trap/inform to a manager. Can I
Chri
On Tue, 2005-07-05 at 09:30 +0530, [EMAIL PROTECTED] wrote:
> Can we use the snmptrap application for sending traps/inform of the
> propriety MIB’s?
Yes.
> Do we need to update any Net-SNMP config files?
No.
You may need to run 'snmptrap -m PROPRIETRY-MIB '
if you want to use the name of
First, please don't post to both lists.
On Wed, 16 Feb 2005 21:48:48 -0800 (PST) raja wrote:
RK> "snmptrapd -f -P" to capture notifications,but failed
RK> to capture any notifications.i am sure that my code
RK> generates traps.
Try
snmptrapd -f -Le -d
That will dump all packets receive
39 matches
Mail list logo
