NetXMS Support Forum

Nice catch!
Fixed, will be released in upcoming 2.0-M2.

Quote from: volkoff on January 23, 2015, 06:19:24 PM
Funny bug:
configuration parameter in nxagent ListenAddress actually read backwards.
So instead of 192.168.1.2 you should write 2.1.168.192

У нас сейчас нет свободных ресурсов на бекпорт из 2.0 - насколько это критично?

That's a bug. Filtered indexes (with "WHERE ..." clause) are introduced in SQL Sever 2008.

https://dev.raden.solutions/issues/747

As a workaround - uncheck "initialise database", edit file C:\NetXMS\lib\sql\dbinit_mssql.sql: remove "WHERE ..." part from this "CREATE INDEX" and initialise database by hand:
1) open "cmd" window
2) cd c:\netxms\bin
3) nxdbmgr init C:\NetXMS\lib\sql\dbinit_mssql.sql
4) net start "NetXMS Core"

В скрипте точно нет ошибок? Только что проверил такую конфигурацию:

https://www.dropbox.com/s/ln8ozbzr0wmsoj5/Screenshot%202015-01-20%2023.59.33.png?dl=0
https://www.dropbox.com/s/wbno0ratkx7utqe/Screenshot%202015-01-21%2000.00.16.png?dl=0
https://www.dropbox.com/s/v32zkt9ic7tad4f/Screenshot%202015-01-21%2000.00.59.png?dl=0

А вот если в скрипте сделать ошибку:
https://www.dropbox.com/s/ispi1xg2nsu6lyr/Screenshot%202015-01-21%2000.02.00.png?dl=0

Yep, that's a bug. You can extract these libs from netxms-server package or wait for upcoming 2.0-M2.

https://dev.raden.solutions/issues/744

General answer is "no" - nxsl do not provide any way to do a back resolve. We can add function for that and then it can be implemented quite easily: in EPP, in create alarm /  send notification section – you use %{scriptName} instead of the message (%m, usually), and in this "scriptName"  (from Script Library) you do any transformation you like (extract IP, resolve and combine message back together). You can register feature request in our bug tracker: https://dev.raden.solutions/projects/netxms/.

Right now you can do this kind of a hack:
1) in EPP add "execute external application" as action
2) write script (shell, python, application - anything), which split message, extract IP, do back resolve, compose new message
3) push it back to NetXMS using "nxevent" command line utility. Note, you should use different event for that – or you'll create infinite loop.

Check this section of the guide: https://www.netxms.org/documentation/adminguide/subagents.html#dbquery

User "admin" with id=0 (name doesn't matter, actually – you can change it after installation) is a special case, it have all permissions by default – and it's enforced by the server. This user also can't be deleted. However, you can disable it.

That's weird, you can try to undeploy, stop servlet container, remove working/temp directory and start deploy war file again.

Check this database (netxms_db) for existing tables. Did you run wizard more than once?

Yes, you need to install agent on the servers. Agent-less monitoring only works with SNMP-capable devices.

Replace "{instance}" in DCI configuration with actual mount point (e.g. "/home" on Unix or "C:" on Windows)
Another option is to setup instance discovery: https://www.youtube.com/watch?v=HSs9mP_0XK0

Hello.

Check this tutorial: http://wiki.netxms.org/wiki/How_to_send_e-mail_notification_when_disk_space_is_low
Video tutorials by Tomas Kirnak: https://www.youtube.com/playlist?list=PLt3aE2eGS5P9L72H82S83MrKx2uz5x8gv

Sorry, but it's not fixed yet. It's registered as issue #735

It looks like Kyocera have some issues with SNMP implementation on this MFU.
You can check that with snmpwalk:

ifAdminStatus (1 - up, 2 - down, 3 - testing):
nxsnmpwalk -c public TARGET_IP .1.3.6.1.2.1.2.2.1.7

ifOperStatus (1 - up, 2 - down, 3 - testing, 4 - unknown, 5 - dormant, 6 - notPresent, 7 - lowerLayerDown):
nxsnmpwalk -c public TARGET_IP .1.3.6.1.2.1.2.2.1.8