On 16 October 2012 14:10, Giuseppe Modugno wrote:
> In this case, why to use the "service object" somethingChangedOID? The
> OID of the changed instance can be retrieved from the "extra" (not
> specified in the MIB) varbind that contains the value too, so the
> OBJECTS clause for the notification
Il 16/10/2012 09:56, Dave Shield ha scritto:
> Remember that you can always append additional varbinds to a
> notification payload - over and above those listed in the MIB definitions.
> So as well as the
> somethingChangedOID.0 = theOidThatChanged
>
> varbind, the notification could also con
On 16 October 2012 09:05, Giuseppe Modugno wrote:
>> Remember that you can always append additional varbinds to a
>> notification payload - over and above those listed in the MIB definitions.
> Really? I thought I was forced to append just the varbinds defined in
> the MIB. Which is the RFC wher
Il 16/10/2012 09:56, Dave Shield ha scritto:
> On 16 October 2012 08:32, Giuseppe Modugno wrote:
>> Now I'd like to have an agent that sends a notification for *each*
>> parameter: if an alarm occurs, if the user change a setting (even
>> through SNMP SET) and so on.
>>
>> The only approach I know
On 16 October 2012 08:32, Giuseppe Modugno wrote:
> Now I'd like to have an agent that sends a notification for *each*
> parameter: if an alarm occurs, if the user change a setting (even
> through SNMP SET) and so on.
>
> The only approach I know is to define in the MIB a different
> NOTIFICATION-
[email protected]
Subject: Re: Notification Filtering
On 3 March 2011 11:29, Shreyas Deodhar wrote:
> Here's the snmpd.conf file
[snip]
Ummm yes, that ought to be working.
I'm not sure what's going wrong here.
All I can suggest is that you try with a more rec
On 9 March 2011 15:44, Shreyas Deodhar wrote:
> Is there any platform dependency here?
There shouldn't be, no.
The filtering is handled purely within the core agent code.
There isn't any relevant O/S-specific code.
All I can suggest is that you run the agent under a debugger,
and single-step thr
On 3 March 2011 11:29, Shreyas Deodhar wrote:
> Here's the snmpd.conf file
[snip]
Ummm yes, that ought to be working.
I'm not sure what's going wrong here.
All I can suggest is that you try with a more recent version
of the agent (although the only related fix that I can spot
should be p
[email protected] [mailto:[email protected]] On Behalf
Of Dave Shield
Sent: Thursday, March 03, 2011 4:16 PM
To: Shreyas Deodhar
Cc: [email protected]
Subject: Re: Notification Filtering
On 3 March 2011 10:21, Shreyas Deodhar wrote:
>>>What are the access control set
On 3 March 2011 10:21, Shreyas Deodhar wrote:
>>>What are the access control settings for your agent?
> I am using net-snmp version 5.4.1, with write community as 'private'
Can you please post the full contents of your snmpd.conf file.
I've just tried the same command you posted on an age
-Original Message-
From: [email protected] [mailto:[email protected]] On Behalf
Of Dave Shield
Sent: Thursday, March 03, 2011 3:27 PM
To: Shreyas Deodhar
Cc: [email protected]
Subject: Re: Notification Filtering
On 3 March 2011 09:37, Shreyas Deodhar wrote:
&
On 3 March 2011 09:37, Shreyas Deodhar wrote:
> [root@localhost Desktop]# snmpset -v2c -c private
>snmpNotifyFilterRowStatus.\"noColdStart\".1.3.6.1.6.3.1.1.5.1 i createAndGo
>snmpNotifyFilterType.\"noColdStart\".1.3.6.1.6.3.1.1.5.1 i excluded
>
> Error in packet.
> Reason: notWritable (T
On 1 March 2011 09:29, Nilesh karle wrote:
> Can anybody please share some information on 'Notification Filtering'
> project current status?
> Is it in place already ?
Support for notification filtering has been in place for some time.
I believe that the main thing that is missing is some simple
I really need an opinion about my questions to fix it in the right way.
I have fixed it for v5.4.3 and plan to do it for 5.6 too.
Regards,
Claus
On 20.10.2010, at 23:06, Claus Klein wrote:
I have some question about the code at the end of this function:
1.) Why is the send_trap_to_sess() cal
I have some question about the code at the end of this function:
1.) Why is the send_trap_to_sess() called for each entry at sinks
without check the snmpNotifyFilter?
2.) And why is the snmpNotifyFilter called via callback 2 times (with
v1 and v2 trap pdu)?
3.) Why is the callback called to
I didn't see a response to this old message, and I hope you solved the problem
on your own. Just answering for the archives in case someone else ran into
this same problem.
On Fri, 9 Oct 2009 07:58:33 -0700 (PDT) nathan wrote:
N> hi,
N> I want to send some project-specific info from net-snmp clien
> "hm" == hussaini mukadam <[EMAIL PROTECTED]> writes:
>> From the FAQ section , I came to know that latest NET-SNMP agent(5.4.1
hm> version) does not currently support notification log filtering. All
hm> notifications are sent to all configured destinations. There is a
hm> preliminary impleme
Okay, I looked into notification_log.c code a little bit more and found
nlmlogVariableTable is kind of implemented in 5.3.1, see the function
log_notification(). But the problem is that it doesn't populate anything.
The following is an example when nlmLogTable logged one notification,
however, noth
> On Fri, 23 Jun 2006 10:02:20 +0100, Dave Shield <[EMAIL PROTECTED]> said:
Dave> Probably not explicitly - it's just SNMP SET requests, to set the
Dave> appropriate values for a filter entry.
FYI, we're working on a document at SPARTA that will be eventually
exported into the Net-SNMP tutor
Passera Pablo-APP015 wrote:
> Thanks for your response. I saw that tables in the code, but I couldn't
> find any easy way to configure the filters. For instance, to add a new target
> in the snmpNotifyTable one can use the trapssess token in the snmpd.conf file
> but it doesn't configure
Passera Pablo-APP015; [email protected]
Subject: Re: Notification filtering support
HI,
The below is not accurate in describing the "standard" way for configuring SNMP
notification originators as specified by the objects defined in RFC 3413.
First, implementations are
HI,
The below is not accurate in describing the "standard" way
for configuring SNMP notification originators as specified
by the objects defined in RFC 3413.
First, implementations are not required to objects in RFC 3413,
and I personally believe that they were not well designed.
However, if you
Passera Pablo-APP015 wrote:
>What about the SNMP-NOTIFICATION-MIB? I was taking a look to that mib and it
>seems to be used for sending notifications to specific NMs.
>
Yes - that MIB has been used by the Net-SNMP agent for some time.
It can be used to configure where notifications should be sent
know what is that? Is it a
book?
Thanks,
Pablo
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Robert Story
Sent: Monday, June 19, 2006 12:15 PM
To: sheeba shirley
Cc: [email protected]
Subject: Re: Notification filtering support
On Sa
On Sat, 17 Jun 2006 11:00:50 -0700 (PDT) sheeba wrote:
SS> I am working on net-snmp for developing an agent.We
SS> need notofication filter option to send different
SS> filter options to different managers.As per net-snmp
SS> FAQ, notification filtering is not supported.Is there
SS> any work around
On Mon, 09 Jan 2006 05:08:33 + Madhav wrote:
MK> I would like to work on the notification filtering project
MK> work. Can you send me some detailed info about the project?
Have you tried net-snmp 5.3? It has notification filtering support.
--
NOTE: messages sent directly to me, i
Madhav kelkar wrote:
I would like to work on the notification filtering project
work. Can you send me some detailed info about the project?
I have worked on this project before as my assisned tasks
in one of the company. Now I would like to contribute the same to the
n
On Fri, 09 Dec 2005 14:01:08 + Dave wrote:
DS> As part of tidying up the snmptrapd.conf documentation,
DS> I was thinking about renaming the 'dontRetainLogs' directive
DS> to bring it into line with the other similar trapd directives
DS> (i.e. deprecating it in favour of 'doNotRetainLogs')
DS>
On Tue, 2005-06-21 at 14:05, [EMAIL PROTECTED] wrote:
> Can particular manager register to receive particular
> Notification/trap/alarm in Net-SNMP agent?
No.
>From the FAQ:
Where are these traps sent to?
-
[snip]
Note that all notifications will be se
29 matches
Mail list logo
