RE: DB locked ?

Trap flow inside the system is the following:

1. Trap received
2. Trap passed through list of configured traps to find matching event
3. If matching event found, this event generated, else SNMP_UNKNOWN_TRAP
event generated

After that, standard event processing took place:

1. Event passed through event processing policy, so alarms can be
generated and actions executed
2. If appropriate event template has "write to log" flag, event being
written to event log

So, if you wish to see your traps in alarm viewer, you should configure
event processing policy appropriately. Policy configuration accessible
through "Control Panel -> Event Processing Policy". Idea is similar to
firewall - policy is a set of rules, where each rule consist of two
parts - matching and action. In matching part, you specify event source
(host, subnet, group of hosts or any), event (set of specific event
codes or any), severity (all or only specific severity codes). If event
matches to the rule, action part is executed. Action part consis of two
fields - alarm and actions. In alarm field, you can specify that you
wish to generate alarm from the event, and this alarm will be visible in
alarm viewer. In action part, you can specify one or more actions to be
executed - send email, send SMS, execute command, etc. You can also take
a look at step-by-step configuration example at
http://www.netxms.org/documentation/confexample/ which may give you an
idea how to generate alarms and execute actions from events.

Best regards,
Victor

> -----Original Message-----
> From: TIM MOORE [mailto:MOORET10_at_odjfs.state.oh.us]
> Sent: Friday, February 24, 2006 10:15 PM
> To: netxms-users_at_alk.lv; Victor Kirhenshtein
> Subject: Re: [netxms-users] DB locked ?
>
>
> Victor, thanks for this information. I will see what I can
> figure out with the traps.
>
> I was also wondering if there was any way to allow Events and
> Traps to hit the alarm window or event window if the device
> is not able to be polled with snmp. In other words, we have
> business partners that forward traps to us, but we can't poll
> their devices. We can add the device to the console, but we
> do not know the community string. Since they are forwarding
> the traps to us, is there anyway to accept them and be able
> to send a page on them? I tried this with a router in our
> network without polling it and the event window didn't show the trap.
> Ideas?
>
>
>
> --------------------------------------
> Tim Moore
> 614.387.8197
> Network Operations Center
> ODJFS
>
> >>> victor_at_opticom.lv 2/24/2006 12:20:43 PM >>>
>
> SNMP MIBs and SNMP traps
>
> In NetXMS, MIBs are used only in MIB browser, to allow easier
> selection of SNMP OIDs. To populate MIB browser with new
> MIBs, you should do the
> following:
>
> 1. Put your new MIBs into MIB directory of your NetXMS
> server, usually /usr/local/share/netxms/var/mibs on UNIX or
> C:\NetXMS\var\mibs on Windows. 2. cd to your MIB directory 3.
> Compile all your MIBs together by running command
>
> nxmibc -d .
>
> You should get file netxms.mib updated.
> Disconnect and reconnect your console. Console will notice
> changes in MIB files and download updated netxms.mib to
> workstation. After that, you will see new OIDs in MIB browser.
>
>
> SNMP TRAPS
>
> Short instruction for processing SNMP traps with NetXMS -
> copy/paste from my another post, so it may look little strange:
>
> First, you should create mapping between SNMP trap and NetXMS
> event. To do this, go to View -> Control Panel -> SNMP traps.
> You will see some default mappings for standard SNMP traps.
> Select Trap -> New... To create new trap mapping. System will
> match trap OID to OID in map entry, and if OID in map entry
> is shorter or equal to trap's OID, event specified in map
> entry will be generated. To start, I suggest you to create
> map entry with OID ".1" and event SNMP_UNMATCHED_TRAP. This
> will match all traps with OIDs starting with ".1" (usually
> any traps). When you have setup trap to event mapping, you
> should see generated events in event log (View -> Event Log).
> If you wish to generate alarms or execute programs when you
> receive SNMP trap, you should configure event processing
> policy (View -> Control Panel -> Event Processing
> Policy) to process SNMP_UNMATCHED_TRAP or any other events
> you generate. In event processing policy you can specify that
> you wish to create an alarm from event or perform some
> actions. Please note that if you wish to do very granular
> processing of traps, most likely you will have to create
> custom events, which can be done with event configurator (View
> ->
> Control Panel -> Events).
> Please note that server will process SNMP traps only for
> hosts registered in database.
>
> Additional comments:
>
> 1. You may use MIB browser for selecting trap OIDs from the
> MIBs you have added - use "Select..." buttons in
> configuration dialogs. 2. If you have any ideas of improving
> trap configuration - send them to the list, you are welcome.
>
> Best regards,
> Victor
>
> > -----Original Message-----
> > From: TIM MOORE [mailto:MOORET10_at_odjfs.state.oh.us]
> > Sent: Friday, February 24, 2006 3:25 PM
> > To: NetXMS Users
> > Subject: Re: [netxms-users] DB locked ?
> >
> >
> >
> > Forwarding to all users.
> >
> > Well, I have some good news. I loaded this on a regular compaq pc
> > running Fedora Core 4. So far no crashes. I wonder it has anything

> > to do with SuSE SLES. I am going to reload the server I was running

> > Netxms on and put a Red Hat based distro on it and see if it runs
> > stable.
> >
> > I have just a couple questions that I can't find answers in the
> > documentation.
> >
> > 1) Is there a way to do some network discovery? I thought I saw
> > that there was a way, but can't find anything in the netxms console.

> > Or is there a way to populate the devices in the tree?
> >
> > 2) Has anyone populated the server with more mibs for the
> snmp traps?
>
> > If you look at the snmp trap configurator, it seems there are only 6

> > by default? What is the easiest way of going about this? I need as

> > many cisco mibs as possible. Are these trap mibs or regular device
> > mibs?
> >
> >
> >
> > --------------------------------------
> > Tim Moore
> > 614.387.8197
> > Network Operations Center
> > ODJFS
> >
> > --------------------------------------
> > Tim Moore
> > 614.387.8197
> > Network Operations Center
> > ODJFS
> >
> > >>> Alex Kirhenshtein <alk_at_ctco.lv> 2/21/2006 9:27:22 AM >>>
> > My bad, i remembered now.
> >
> > Does it leave a core file? If no, can you set core limit to
> > unlimited (run "ulimit -c unlimited" before netxmsd) and try again?
> >
> > If it crashed and there is a core file, then i'll will be happy to
> see
> > backtrace:
> >
> > # gdb /path/bin/netxmsd /path/core
> > (first argument - executable file, second - core file)
> > gdb> backtrace
> > (this will show you backtrace)
> >
> > or, if you don't have gdb installed, just send me executable + core.
> >
> > thanks in advance, alex.
> >
> > On Tue, 2006-02-21 at 08:58 -0500, TIM MOORE wrote:
> > > I was not trying to shutdown netxmsd. It died on its own. If I
> > leave
> > > it up over 1 day's time, it crashes and leaves the db locked.
> > >
> > > I am running 0.2.9 on SuSE SLES9 on a Compaq ML360 server. I gave
> > the
> > > specs in a prior email regarding my server. I'm the one who had
> to
> > use
> > > the stdarg settings in a few files to get it to compile.
> > >
> > > --------------------------------------
> >
> >
> >
> > This e-mail message, including any attachments, is for the sole use
> > of the intended recipient(s) and may contain private, confidential,
> > and/or privileged information. Any unauthorized review, use,
> > disclosure, or distribution is prohibited. If you are not the
> > intended recipient, employee, or agent responsible for delivering
> > this message, please contact the sender by reply e-mail and destroy
> > all copies of the original e-mail message.
> >
> >
>
>
> This e-mail message, including any attachments, is for the
> sole use of the intended recipient(s) and may contain
> private, confidential, and/or privileged information. Any
> unauthorized review, use, disclosure, or distribution is
> prohibited. If you are not the intended recipient, employee,
> or agent responsible for delivering this message, please
> contact the sender by reply e-mail and destroy all copies of
> the original e-mail message.
>
>
Received on Fri Feb 24 2006 - 22:48:06 EET