NetXMS Support Forum

Hi,

what exact console version you are using? Is it desktop or web based?

Best regards,
Victor

Hi,

one of the biggest issues with multi-tenant setup is event processing configuration. Currently there is single policy and access to it is controlled by global access rights. For proper multi-tenant setup we also need separate event processing policies, action configurations, etc. Depending on what you want to achieve it could be easier to run multiple instances of netxmsd, using docker containers for example.

Best regards,
Victor

Debian/Ubuntu packages now available in repository.

Best regards,
Victor

Hi all!

We just published NetXMS version 3.1 patch release 3 (version number 3.1.343). Changes since patch release 2 are following:

- Improved LLDP based topology discovery
- Fixed issue NX-1784 (SQL errors when saving software inventory)
- Fixed resource leak in ICMP code
- Fixed issue NX-1718 (user agent notifications not working on sub-containers)
- Fixed memory leak if network device reports incorrect data in ENTITY MIB
- Additional memory usage diagnostic tools in server
- Added attribute "downSince" to NXSL class "Node"
- Fixed issue NX-1769 (agent crash on startup if incorrect file pattern set in log parser)
- Fixed bug in user agent tray icon loading
- Fixed issue NX-1759
- Correctly set login and password on MQTT broker connection
- Fixed issue NX-1653 (update system access rights for active sessions)
- Fixed issue NX-1761 (phantom output after server script execution ends in error)
- Improved RADIUS related debug messages
- Added NXSL function atan2
- Implemented inodes counters in AIX subagent

We plan it to be last patch release in 3.1 branch before version 3.2 release.

Best regards,
Victor

You can load event from database using function LoadEvent. It accepts single argument - event ID, and returns event object.

Best regards,
Victor

Hi,

currently it is not possible. I've added feature request for that: https://track.radensolutions.com/issue/NX-1785

Best regards,
Victor

Hi,

I just increased maximum password length for nxencpasswd in 3.2 branch.

Best regards,
Victor

Hi,

DCI value length is limited to 255 characters. In your case you can use external parameter provider instead of external parameter, do JSON parsing in agent side script and output all parameters you are interested in as name = value. Then you'll be able to collect them by name as any other agent's parameters.

Best regards,
Victor

Hi,

one option is to use zones and put those routers into different zones. Another option is to mark internal interfaces as "exclude from topology". Second option is easier if you are not interested in anything behind those interfaces.

Best regards,
Victor

Could you show screenshot of overview and interfaces tabs for those nodes?

Best regards,
Victor

Hi,

configuration file looks correct. How exactly you run nxdbmgr? Try to specify full path to old DB config and make sure it is accessible.

Best regards,
Victor

Could you please show output of commands

nxadm -c "show lldp id"

for both nodes, replacing id with actual node ID?

Best regards,
Victor

Hi,

fifth argument to File.FolderCount represents age filter. If < 0, only files created after now - abs(value) will match; if > 0, only files created before now - value will match. For example, to count folders older than one day in /tmp (without recursion) you can use

File.FolderCount(/tmp,*,0,,86400)

Best regards,
Victor

If you get "connect timed out" after you press "Login" button in web UI, that means that backend application cannot connect to NetXMS server. Is NetXMS server on same machine? If not, check that port 4701 on NetXMS server is reachable from web server and that address of NetXMS server set correctly in web application properties.

Best regards,
Victor

Create file batch.sql containing single line

ALTER TABLE idata_119 DROP COLUMN raw_value;


and run command

nxdbmgr batch batch.sql

Best regards,
Victor