NetXMS Support Forum

Hello!

I've never try to do anything with Windows Internal Database, but as far as I understand, it's just a variant of MSDE - so it may be possible to run NetXMS on it using SQL server driver (or via ODBC). You have to try.

Best regards,
Victor

Hello!

Looks like your MIB file refers to another MIB file which you don't include in your compilation. Look at the IMPORTS section in your MIB file - it should contain something like

IMPORTS
  .. some text ...
  BITS
  .. some text ..
  FROM another_mib_module

Try to find this additional module and include it in compilation. You can also post your MIB file here, then I'll take a look at it.

Best regards,
Victor

Hello!

It's not implemented yet, property page for object image is just a stub. It's already in our issue tracker, and I hope that I will have time to implement it in near releases.

Best regards,
Victor

Hello!

Most likely you have an old version of flex. You have to use version 2.5.33.

Best regards,
Victor

Hello all!

Finally, after long delay, version 0.2.16 is released! Changes from previous version are:

- Implemented user authentification by certificates
- Management packs fully functional - templates, events, and SNMP traps
  can be exported and imported
- Cluster monitoring improved
- Node names resolution working
- Implemented OCI based driver for Oracle database
- UPS subagent: added support for Microdowell devices
- Windows console:
  - Added layer 2 topology view for compatible switches
  - Object search improved
  - Graphs improved:
    - Area graphs
    - Predefined graphs
    - Minor UI improvements
  - Added possibility to manage/unmanage set of child objects
  - Added possibility to hide unmanaged leaf objects
  - Container objects can be placed above all others
  - Other small UI improvements
- Fixed issues: #90, #106, #120, #143, #147, #148, #149, #150, #152, #153, #155

I plan that next version will be focused on bugfixing and minor improvements and that it will be released in a month or so.

Best regards,
Victor

Hello!

Currently, you have only one way: define two DCIs for each port, and configure threshold for each DCI. Of course, it can be very time consuming for large number of ports. In one of the next versions (0.2.16 or 0.2.17, depending on my free time) we plan to implement "table" DCIs which will allow you to define parameters which differs only in instance only once, and system will automatically generate actual DCIs for each parameter's instance (for each port in your case).

Best regards,
Victor

Hello!

By default, NetXMS server will run active discovery every 2 hours, and passive discovery polls every 15 minutes. You can change this by changing appropriate server parameters: ActiveDiscoveryInterval and DiscoveryPollingInterval (both in seconds). Also, if you have large subnet with a lot of unused addresses, it can take significant amount of time to scan it using active discovery: because for each unused address server will wait for a response until timeout expires, and because timeout is ~6 seconds, if you have /24 subnet with most addresses unused, it will take ~20 minutes to scan them. Firewall between NetXMS server and scanned subnet may also affect discovery time (for example, if firewall blocks TCP connections to port 4700 which NetXMS server will check to determine if agent is running on the host).

Best regards,
Victor

Hello!

I've never seen such error messages, but I'm still using version 167. Also, I recompile Scintilla from source before using it.

Best regards,
Victor

Hello!

Oops, I forgot to add it to the CVS. It will be fixed in next release. For now, you can download it from https://netxms.org/download/patches/002.

Best regards,
Victor

Hello!

The main problem is that PostgreSQL database driver was not linked correctly. This is already known bug, which will be fixed in 0.2.16. For now, you can use workaround described here:

https://www.netxms.org/cgi-bin/mwf/topic_show.pl?tid=29;sid=b7dca035f7436b0605f5ff0d9de0937b

Best regards,
Victor

Hello!

The problem is that libtool cannot find command g++ - which is GNU C++ compiler. Looks like you don't have installed C++ compiler package or it is not in the search path.

Best regards,
Victor

Hello!

It's an error in configure script (reference to libpq missing in libnxddr_pgsql.so because of incorrect link options), I'll fix it in the next release. For now you can use the following workaround:

In the file src/server/dbdrv/pgsql/Makefile find line starting with LDFLAGS = and append -lpq to it. You should get something like this:

LDFLAGS =  -L/usr/local/lib -lpthread -lpq

Then run make clean ; make ; make install in src/server/dbdrv/pgsql directory. This should create correct libnxddr_pgsql.so.

Hope this helps!

Best regards,
Victor

Hello again!

Please note that starting from version 0.2.15, you can also calculate checksum of web pages - this gives you an ability to detect page changes. To get web page checksum, you should load ECS (Extended Checksum) subagent on the node from which you wish to control web page, and then add DCI like below to that node:

ECS.HttpSHA1(URL)

for example, to calculate checksum of www.netxms.org main page, use

ECS.HttpSHA1(https://www.netxms.org)

You will get SHA1 hash for page as a string. You can set threshold on DCI to detect changes in a checksum and process raised events.

Best regards,
Victor

Hello!

To monitor web services, you have two options, depending on your installation:

First option - if you have added machine hosting web server in question to NetXMS as node object.

1) Create "Service" object under your web server's node object
2) Select service type "HTTP"
3) As a request, enter HOST_HEADER:REQUEST_URI, for example, to test URL https://www.netxms.org/index.html enter www.netxms.org:/index.html
4) In a response field, enter regular expression to match server's answer. Below are some examples:
4.1) Just test for code 200 (OK):

^HTTP/1\.[01] 200.*

4.2) To test that server returns code 200 and that page's content has word "netxms":

^HTTP/1\.[01] 200.*netxms.*

Second option - if you don't enter your web server as a node into NetXMS (for example, you wish to check www.ibm.com without creating a node object in your NetXMS database)

1) For the node object representing your NetXMS server, add the following DCI (source - NetXMS agent):

ServiceCheck.HTTP(server_ip_address,port,uri,host_header,response)

For example, to check https://www.netxms.org/index.html just to code 200, use

ServiceCheck.HTTP(159.148.208.90,80,/index.html,www.netxms.org,"^HTTP/1\.[01] 200.*")

This parameter will return the following values:

0 - success (server was connected and return expected response)
1 - invalid arguments was passed (most likely regular expression has incorrect syntax)
2 - cannot connect to server
3 - bad server's response

So you can set threshold for non-zero values and process it.

Please node that you need portchecker subagent to be loaded on machine running NetXMS server. On Windows installation this is default, but on UNIX you should ensure that you have something like

SubAgent = /usr/local/lib/libnsm_portCheck.so

in your agent's configuration file.

Hope this helps!

Best regards,
Victor

Hello!

Yes, there are plans for such compound DCIs - most likely I will implement it in one of the nearest releases.

Best regards,
Victor