NetXMS Support Forum

Yes, unfortunately there is a bug in MySQL driver in 1.1.4. I'll try to made a patch tomorrow. Other DB engines should work fine. I do most of the development using Oracle and PostgreSQL, and at some point forgot to make necessary tests at MySQL.

Best regards,
Victor

I have replicated this issue on my system. Looks like a bug in MySQL driver. I'll post a patch when I fix it.

Best regards,
Victor

If you run netxmsd.exe from command line, you should omit -d switch, like this:

netxmsd.exe -D 9

Best regards,
Victor

You should not initialize database if it already contains data. Initialization is for fresh installation on empty database.

Generally I do not recommend to use SQLite in production. It has both performance and upgrade issues, although performance can be insufficient only for relatively large installations. Upgrade problems are related to the fact that SQLite does not support DROP COLUMN operation - so if database upgrade requires column removal from the table, it will fail. It is possible to do upgrade manually in these cases, but it is time consuming and requires digging into the source code of nxdbmgr to see what SQL queries should be executed.

Best regards,
Victor

So, you have MySQL database for 1.0.12 and want to upgrade it to 1.1.4? It should be possible to done it in place. Just install 1.1.4, point it to appropriate database, and run database upgrade. If it shows any error, please send me log/screenshot of nxdbmgr upgrade execution.

Best regards,
Victor

Is there anything in the logs? Also, try to start netxmsd.exe from command line in debug mode (netxmsd.exe -D 9) and look for debug messages.

Best regards,
Victor

What is your production DB engine?

Hi!

DB export uses built-in sqlite engine to create export file. It works with all supported DB engines. What exact file it cannot found?

Best regards,
Victor

Hi!

On Windows, it is Windows Server 2003 or Windows XP, no specific requirements for service packs.

Best regards,
Victor

Hi all!

NetXMS version 1.1.4 is out. Changes from previous release:


- Implemented named parameters for events
- Added integration script for HP EVA disk arrays
- Added driver for Netscreen firewalls
- Usage of DNS names instead of IP address for defining primary
  communication address is now supported (for better support of nodes with
  dynamic IPs)
- New MIBs added: ATM-TC-MIB, CISCO-BRIDGE-EXT-MIB, CISCO-IF-EXTENSION-MIB,
  CISCO-L2L3-INTERFACE-CONFIG-MIB, CISCO-PRIVATE-VLAN-MIB,
  CISCO-VLAN-IFTABLE-RELATIONSHIP-MIB, DVMRP-MIB, IGMP-MIB, IPV6-TC,
  RAPID-CITY-BAY-STACK, RC-MLT-MIB
- Mobile client for Android introduced
- Many small improvements in management console
- Fixed some problems with database export/import
- Fixed issues: #328, #329, #330

Best regards,
Victor

Looks like you need these MIBs: http://www.oidview.com/mibs/1123/md-1123-1.html. At least, trap .1.3.6.1.4.1.1123.4.500.2 is defined in SM10-R2-MIB.

Best regards,
Victor

It's not the trap receiver, but event processing. Currently event's message size limited to 255 characters. Because default event just put everything into message it gets truncated. Usually you will create separate events for traps of interest, and you can carry trap arguments as event parameters, and then use them in actions, for example, without length limitations.

Best regards,
Victor

Hi!

No. it's not possible to match traps with same OID to different events. However, you can do additional matching in event processing policy using scripts, and process same event differently depending on trap parameter values.

Best regards,
Victor

Hi!

I'm not sure that DS3500 supports SNMP at all. In product datasheet on IBM web site there are no mentions of SNMP. Did you try to connect it to monitoring already? If it responds with SNMP, you can do SNMP walk on .1.3.6.1.4.1 subtree and search MIBs based on OIDs you get.

Best regards,
Victor

Hi!

Yes, it's possible. You can separate multiple emails in action definition with ; (semicolon) character. You can use the same macros as in event messages and alarms - they are listed in user manual in chapter 10.6 "Macros for Event Processing".

Best regards,
Victor