=?windows-1256?Q?RE:_help_o?= =?windows-1256?Q?n_linkUpDo?= =?windows-1256?Q?wnNotifica?= =?windows-1256?Q?tions=FE?=

X Z <[email protected]>
Newsgroups gmane.network.net-snmp.user
Message-ID <[email protected]>
I downloaded 5.5x RPM and did a RPM force upgrade from 5.3.1 to NET-SNMP version 5.6.dev. I don't know where I can get the source RPM that I can build my own.

Now I saw two coldStart and two nsShutdown traps every time I started/stopped agent. Still couldn't see the linkUp and linkDown traps.

Here is the output when I ran the agent:
registered debug token disman:event, 1
disman:event:init: init trigger container
disman:event:init: create trigger container (0x1fea7ad0)
disman:event:init: init trigger container
disman:event:init: Trigger Table
disman:event:init: init trigger container
disman:event:init: Trigger Delta Table
disman:event:init: init trigger container
disman:event:init: Trigger Exist Table
disman:event:init: init trigger container
disman:event:init: Trigger Bool Table
disman:event:init: init trigger container
disman:event:init: Trigger Threshold Table
disman:event:init: init trigger container
disman:event:init: init event container
disman:event:init: create event container (0x1feabcf0)
disman:event:table: Create event entry (_snmpd, _mteTriggerFired)
disman:event:table: Event entry created
disman:event:table: Create event entry (_snmpd, _mteTriggerRising)
disman:event:table: Event entry created
disman:event:table: Create event entry (_snmpd, _mteTriggerFalling)
disman:event:table: Event entry created
disman:event:table: Create event entry (_snmpd, _mteTriggerFailure)
disman:event:table: Event entry created
disman:event:table: Create event entry (_snmpd, _linkDown)
disman:event:table: Event entry created
disman:event:table: Create event entry (_snmpd, _linkUp)
disman:event:table: Event entry created
disman:event:init: init event container
disman:event:init: Event Table container (0x1feabcf0)
disman:event:init: init event container
disman:event:init: Event Set Table container (0x1feabcf0)
disman:event:init: init event container
disman:event:init: Event Notify Table container (0x1feabcf0)
disman:event:init: init event container
Turning on AgentX master support.
Turning on AgentX master support.
disman:event:conf: Storing mteTriggerTable config:
disman:event:conf:   done.
disman:event:conf: Storing mteEventTable config:
disman:event:conf:   done.
disman:event:conf: Storing mteObjectTable config:
disman:event:conf:   done.

Sending 95 bytes to UDP: [127.0.0.1]:162->[0.0.0.0]
........

There are no traces related to linkUp and linkDown events. Looks like it is disabled by default? Is there a way to turn on the event trigger?


Thanks
Xuan



> Date: Sat, 20 Mar 2010 09:49:57 +0000
> Subject: Re: help on linkUpDownNotificationsأ¾
> From: [email protected]
> To: [email protected]
> CC: [email protected]
> 
> 2010/3/20 X Z <[email protected]>:
> > I still didn't see any link down traps. No errors dumped either.
> 
> > Could you please give me some insights why I still didn't see any link down
> > traps? I can only receive coldStart and nsNotifyShutdown traps.
> 
> 
> Can you try with one of the more recent agents?
> (v5.4.x or v5.5)
> 
> Dave
 		 	   		  
_________________________________________________________________
The New Busy is not the old busy. Search, chat and e-mail from your inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID27925::T:WLMTAGL:ON:WL:en-US:WM_HMP:032010_3

------------------------------------------------------------------------------
Download Intel&#174; Parallel Studio Eval
Try the new software tools for yourself. Speed compiling, find bugs
proactively, and fine-tune applications for parallel performance.
See why Intel Parallel Studio got high marks during beta.
http://p.sf.net/sfu/intel-sw-dev

_______________________________________________
Net-snmp-users mailing list
[email protected]
Please see the following page to unsubscribe or change other options:
https://lists.sourceforge.net/lists/listinfo/net-snmp-users
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.