RE: DB locked ?

Hello!

Network Discovery

Yes, NetXMS is able to do network discovery, but it's disabled by
default. To enable it, you should go to View -> Control Panel -> Server
Configuration in console, select variable "RunNetworkDiscovery" and
change it's value to 1. Then, you should restart NetXMS server so new
settings will take effect. After that, NetXMS server will instantly scan
your network for new hosts and devices and add them to database.
However, it will add EVERYTHING which have an IP address configured -
workstations, printers, etc. If you wish to limit discovery process, you
should create discovery filter. Filter is a script writtent in NXSL -
NetXMS Scripting Language. It will receive information about newly
discovered object and should return 0 if this object should not be added
to database and 1 if it should. You are creating your scripts in Control
Panel -> Script Library. After script is created, you should set
server's variable "DiscoveryFilter" the the name of your script. By
default, NetXMS has 3 pre-defined filters:

1. Filter::Agent - allows only hosts with NetXMS agent installed
2. Filter::SNMP - allows only hosts with SNMP support
3. Filter::AgentOrSNMP - allows only hosts with either NetXMS agent or
SNMP

If you have non-standard SNMP community string on your devices, network
discovery will not work until you change server's variable
"DefaultCommunityString".

Hope this helps!

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.
>
>
Received on Fri Feb 24 2006 - 15:51:02 EET