NetXMS Support Forum

Hello!

It's a misleading field "Proxy" in node creation dialog - it only sets agent proxy. Node object has two different properties - agent proxy and SNMP proxy, and SNMP proxy can be set only after node object creation in object's properties (my mistake, will correct it in next release). Now, you have to set "SNMP proxy" attribute in node's D properties correctly and try to re-poll it. If system will reject configuration polls because node is down (another problem which needs to be solved) you will have to restart the NetXMS server. This should clear "node unreachable" flag and allow you to do a configuration poll. If this will not help, I'll send you a patch for server that will fix this problem with configuration poll. Are you running NetXMS server on Windows or UNIX (so do you need updated Windows installation or updated source code)?

Best regards,
Victor

Hello all!

Version 0.2.15 is out. Changes from previous release:

- Added initial support for cluster monitoring
- Added preliminary support for management packs
- Added SNMP proxy functionality to agent
- IPSO agent improved
- Added Extended Checksum subagent
- Added ODBC Query subagent
- New agent parameters: Process.CountEx(), File.Time.Access(),
  File.Time.Change(), and File.Time.Modify()
- Parameters File.Size() and File.Count() improved
- Parameters Process.XXX improved
- NXSL improved: implemented switch ... case statement and break statement
- Windows console:
  - Now able to download and install update from web server pointed
    by NetXMS management server
  - Object browser improved
  - Graphs improved: implemented printing and "copy to clipboard"
    function
  - Added server history in login dialog
  - Added option "hide empty values" in last DCI values view
- Fixed issues: #105, #123, #131, #135, #140, #142, #145

There are many bugs still open in bugtracker, and some features requires enchancements, so I hope that we will release 0.2.16 with fixes/small improvements shortly (not after 2 month as for last few versions).

Best regards,
Victor

Hello!

Just implemented SNMP proxy functionality, so you will find it in 0.2.15

Best regards,
Victor

Very strange... Another option left - setup connetion to MS SQL via ODBC. To do this, follow these steps:

1. Create appropriate data source via Administartive Tools -> Data Sources (ODBC). You must create System DSN. Call this DSN NETXMS.
2. Change netxmsd.conf file:

DBDriver = odbc.ddr
DBServer = NETXMS

Note that DBServer now is the name of ODBC DSN.

After that, try to run nxdbmgr init again.

Also, what database rights assigned to the database user you are using?

Best regards,
Victor

Hello,

I think that problem is that you use an account with Windows authentication. Now you have two ways - create an account with SQL authentication (it's an easier way), or configure NetXMS for Windows authentication.

If you decide way 1:

1. Create new standard SQL account, let's say netxms_user, set it's authentication mode to SQL authentication, and set it's password (for example, NetXMSPass).
2. Modify your netxmsd.conf accordingly:

DBLogin = netxms_user
DBPassword = NetXMSPass

3. Run nxdbmgr init again, and ensure that tables was created (you should have ~50 tables).

NetXMS server should start.

If you decide way 2:

1. Change netxmsd.conf:

DBLogin = *

2. Change settings for "NetXMS Core" service - by default, it is running as "Local System" account, you should change it to your domain account which have access to SQL database (in service properties on "Log On" tab).
3. Run nxdbmgr init again, and ensure that tables was created (you should have ~50 tables). Please note that because of Windows authentication, account you will be logged in at the time you will run nxdbmgr should also have access to SQL database.

Hope this helps!

Best regards,
Victor

Hello!

Some additional questions:
1. What version of MSSQL server you are using?
2. Cold you please connect to database with Enterprise Manager and send me list of tables presented in database netxms_db and content of "config" table?
3. Could you please change LogFile entry in netxmsd.conf to some file, run NetXMS server in debug mode:

netxmsd --debug-all --dump-sql standalone

and send me the log file?

Possible problems I can imagine now:

1. mssql.ddr expect that login given in DBLogin is an SQL "Standard" user with SQL authentication, not a Windows account. Maybe you create an account with Windows authentication?
2. mssql.ddr doesn't work correctly for some unknown reasons. I hope that debug log will give me more hints.
3. mssql.ddr can only work via TCP/IP. Ensure that TCP/IP is enabled in SQL server.

Best regards,
Victor

Hi!

This functionality is planned, but not implemented yet. It will be implemented in 0.2.15 or 0.2.16, depending on amount of free time I'll have.

Best regards,
Victor

Hello!

Looks like your database was not properly initialized. Try to run

nxdbmgr init ..\lib\sql\dbinit_mssql.sql

(assuming you are in NetXMS bin directory). Also, can you send your server's configuration file (netxmsd.conf)?

Best regards,
Victor

Hello!

You can create "push" parameter for node object A (for example, called PingTime), and then use nxpush utility to update this parameter's value from server. If your management server is running on UNIX, you can add the following command to your crontab to be executed every minute:

nxpush -u admin -P netxms 127.0.0.1 A:PingTime=`nxget 127.0.0.1 Icmp.Ping\(A_address\)`

Of course, you will have to use actual user name and password and replace A with your dumb node name and A_address with it's address. Every execution of this command will request agent for current ping response time, and store it as a new value of node A DCI PingTime.

Hope this helps!

Best regards,
Victor

Script will be

$1 / 48

Best regards,
Victor

You should compile them first. Standing in the directory where all mibs reside, run the following command:

nxmibc -d .

nxmibc is located in NetXMS bin directory, so on Windows you probably will need to run it as

..\..\bin\nxmibc -d .

If everything goes OK, MIB compiler should produce updated file netxms.mib in mibs directory. You don't need to restart NetXMS server, just console. Console will detect that mib file is updated and download it. After that, you will see new oids in mib browser.

Best regards,
Victor

P.S. You may also wish to add -z option to produce compressed netxms.mib, which will be significantly smaller than uncompressed.

Hello!

Currently, you can achieve this with saving/restoring desktop configurations. Open graph windows and arrange them as you like, then select menu Desktop -> Save as... and save your layout. When you will need to open these windows again, go to Desktop -> Restore or simple press Ctrl+Shift+F3 and select layout you wish to load. You can configure as many layouts as you wish. Configurations are per-user, so each user has it's own set of saved desktops, but system administartor can copy saved desktops between users via Desktop -> Manage.

In the future versions we will also add the possibility to predefine graphs and quickly open them from the menu.

Hope this helps!

Best regards,
Victor

Hello!

It's a bug in configure, I'll fix it in next release. For now, try to run configure that way:

LDFLAGS=-lz ./configure --with-server --with-agent --with-mysql

This should help.

Best regards,
Victor

Finally, version 0.2.14 is out! Changes from previous version:

- Alarm system improved (three state alarms, helpdesk status, etc.)
- Added new DCI data source: push agents
- Threshold state now saved across NetXMS server restarts
- Added possibility to specify custom threshold rearm event instead of
  SYS_THRESHOLD_REARMED
- Added threshold processing option "Always process all thresholds"
- Implemented "data collection error" threshold checking function
- Implemented "mean absolute deviation" threshold checking function
- Added possibility to set confirmation messages for object tools
- Object tools "Shutdown system", "Restart system", "Restart agent"
  asks confirmation by default
- Implemented agent traps and added trap sending API for subagents
- Object comments added
- Network discovery configuration simplified
- Active network discovery implemented
- Windows console:
  - Console changed to use UNICODE internally
  - Event processing policy editor improved
  - Added confirmation for object deletion
  - Implemented sorting in object tools tables
- Server ported to AIX and HP-UX
- Agent ported to HP-UX
- Agent for AIX improved
- Fixed issues: #104, #109, #110, #111, #112, #113, #115, #116, #117, #119,
                #121, #124, #125, #126, #127, #133, #139

Best regards,
Victor

Hello!

Looks like server you trying to get DCI from is not responding to SNMP queries from NetXMS server. Check the following:
1. In the properties of a taget server object, go to "Cappabilities" tab and check that isSNMP attribute is "TRUE";
2. Check that community string and SNMP version set correctly;
3. Check that there are no firewall between NetXMS server and target server that blocks SNMP traffic;
4. Run configuration poll (right-click on object, then select Poll -> Configuration) and see for any SNMP-related messages.

Best regards,
Victor