NetXMS Support Forum

If you are not interested in port down events on switches you can block them in event processing policy. You can also block only those for switch ports where peer node is known (by using filter script that will check interface object for peer information) - that way you will have alarms for interfaces where something not monitored by NetXMS is connected but not for those where known nodes are connected.

Best regards,
Victor

Hi,

could you please provide server log with debug level 7 during topology poll for that node?
Also, when does it start? Was it after server upgrade or after some configuration changes?

Best regards,
Victor

Hi!

We are updating data dictionary periodically, but it not always follow schema changes immediately. I'll ask dev team to update it for current 3.9 version.

Best regards,
Victor

Should be in repo for some time already. There was error in publishing process.

Best regards,
Victor

No, it is not possible. We will discuss internally if and how we can implement such functionality.

Best regards,
Victor

Are those graphs on "Performance" tab or you open them somehow?

Best regards,
Victor

Fixed in 3.9.361.

Best regards,
Victor

This bug should be fixed in 3.9.361.

Best regards,
Victor

Hi,

looks like bug in new agent. I will try to reproduce it on my CentOS 7 test system.

Best regards,
Victor

Hi all!

New patch release for NetXMS 3.9 is published (version 3.9.361). Changes since previous patch release:

- Custom port number can be specified in MySQL and MariaDB database drivers
- MySQL subagent can be switched to use MariaDB driver
- Fixed bug in housekeeper (expired DCI data may not be deleted)
- Object filtering in object tree by exact IP address
- State filter in /objects endpoint in web API
- Fixed issues:
        NX-30 (Show thresholds on graph is broken)
        NX-127 (Implement System.CPU.Usage.IoWait in Solaris subagent)
        NX-1448 (It is not possible to specify semicolon as external table separator)
        NX-1450 (External parameters that returns process exit code)
        NX-2157 (Macros are not expanded when uploading file via file delivery policy)
        NX-2166 ("Hide value on last values" does not work)
        NX-2168 (Divide by zero on core start)
        NX-2170 (Macros in shell notification channel are not resolved)

Best regards,
Victor

Hi all!

Raden Solutions is participating in Warsaw Industry Week 2021 exhibition (https://industryweek.pl/en/) in Warsaw, from 8th till 10th of November.

Join us at Warsaw Industry Week to check out our products, ask any questions regarding industrial monitoring, or just for a random chat.

You can find us at stand B2 207.

Best regards,
Victor

Hi,

you can go to Configuration -> Event Configuration. There you can edit built-in templates.

To add MAC address or any other information you can modify message template and call NXSL script to extract necessary information by using %[script_name] macro. For such macro system will lookup script with name given inside [ ] and insert whatever this script returns into resulting message.

Also you can add new event templates from there (either right click anywhere and select "new template", or by pressing plus sign in top right corner).

Best regards,
Victor

Hi all!

We just published next patch release for version 3.9 - 3.9.334. Changes since previous patch release:

- Fixed bar gauge color selection by active DCI threshold
- Bundled SQLite updated to version 3.36.0
- Windows crash dump handler writes compressed dump files
- Improved Juniper driver
- NXSL methods enableConfigurationPolling and enableStatusPolling moved from class "Node" to class "DataCollectionTarget"
- New method enableDataCollection in NXSL class "DataCollectionTarget"
- New agent parameters System.CurrentDate and System.TimeZone
- Fixed bug in cluster resource selection for table DCI
- Fixed possible server deadlock when zone proxies are in use
- Fixed issues:
        NX-2107 (SQL error on server startup)
        NX-2128 (Disabled DCIs with instance discovery generate instance DCIs)
        NX-2131 (Migration from psql-timescale to psql is broken)
        NX-2132 (nxdbmgr check should not delete orphaned idata/tdata records on Timescale database)
        NX-2143 (MIB Explorer "Create Data Collection item..." reports error on Retention time 0 or blank, but is added as "default")
        NX-2144 (Graph Title in Web GUI is truncated, seemingly due to an ampersand)
        NX-2145 (Update HP iLO Template to include support for HP iLOs on G10 servers)
        NX-2148 (MIB compiler throws syntax error if statements in TEXTUAL-CONVENTION definition are in non-standard order)
        NX-2149 (Custom Attribute Inheritance - detached inherited custom attribute not deletable)
        NX-2150 (nxshell session.modifyObject produces Variable not found exception with setSnmpAuthName)

Best regards,
Victor

To suppress alarms on a per-node basis you can just add those nodes to alarm generation rule with "not" condition. To suppress them on DCI level you'll have to use filtering script in EPP rule that somehow will check what DCI it is and decide if alarm should be generated or not.

Best regards,
Victor

SMTP conversation above looks OK. Do you have any logs on your mail relay to check if there are connections from NetXMS server and any possible errors?

Best regards,
Victor