NetXMS Support Forum

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

I've added feature request for supporting search by partial MAC address: https://track.radensolutions.com/issue/NX-2154.

Best regards,
Victor

In geo map you specify coordinates of center point, but when used for network map background those are coordinates of top left corner (so when you resize geo map view center point stays and map expands in all directions, but when you expand network map view with geo background top left corner stays and map is expanded to bottom/right direction).

Best regards,
Victor

Hi,

no, currently it's not possible.

Best regards,
Victor

Hi!

What NetXMS version you are running? There were recent fixes in LLDP code (in version 3.9.229).

Best regards,
Victor

Hi!

Do you have SQL Server Native Client installed?

Best regards,
Victor

Hi all!

Raden Solutions is participating in GITEX Technology Week 2021 exhibition https://www.gitex.com in Dubai, from 17th till 21st of October.

Join us at GITEX to check out our products, ask any questions regarding IT or payment infrastructure monitoring, or just for a random chat.

You can find us at stand H3-C20 (Hall 3, Latvian National Stand).

Best regards,
Victor

Hello!
I just checked MIB compiler source, and it actually should handle DISPLAY-HINT clause. Could you please provide full MIB file trhat cause error? Also, what NetXMS version you are using?

Best regards,
Victor

Quote from: gdodd on October 05, 2021, 04:10:21 AM
- Fixed bug in centralized agent upgrade on Windows

Does that mean once server and agent are on 3.9.298, future centralized agent upgrades should work? Or should it work with just server on 3.9.298?

I am trying to upgrade Windows agents 3.9.280 from Linux server 3.9.298 and get the "Agent's version doesn't match..." error message.

Unfortunately most issues with file transfer and upgrade in 3.9 were agent related, so you have to upgrade agent somehow. Once both server and agent are on 3.9.298, further upgrades should work fine. We will discuss internally if we can do something server-side to allow upgrade of previous versions.

Best regards,
Victor

Hi all!

We just published new patch release for version 3.9 - 3.9.298. Changes since previous patch release:

- Improved file delivery policy editor
- Fixed bug in centralized agent upgrade on Windows
- New endpoint /events in web API for sending events
- Filtering by primary host name in web API endpoint /objects
- Fixed session agent crash on 32 bit Windows systems
- Fixed issues:
        NX-2129 (File delivery policy on Windows Agent causing .part0 to be added to the filename)
        NX-2130 (If file in file delivery policy is updated new version is appended to the old one instead of replacing it)
        NX-2133 (Set subagent column as instance on table Agent.SubAgents)
        NX-2134 (Agent crashes if invalid owner or group set in file delivery policy)

Best regards,
Victor

Hi all!

We just published new patch release for version 3.9 - 3.9.280. Changes since previous patch release:

- External audit logging via LEEF protocol
- Improved process table in Windows agent
- Windows service manager in GUI
- Process manager in GUI
- Optimized working with ICMP
- Object alias shown in geo map tooltips
- Geo map tooltips work in web UI
- Added option to hide other objects in object geolocation view
- Object names can be shown on geo maps
- Fixed issues with Chassis/Rack placement properties page save
- Fixed bug in standard deviation calculation in ping subagent
- Fixed incorrect limit on dashboard element span in UI property page
- Fixed file transfer issue when upgrading agents from Package Manager
- Fixed issues:
        NX-2115 (Allow adding image in chassis properties without selecting a rack)
        NX-2118 (Changes in ICMP statistic collection period are not applied until server restart)
        NX-2119 (Agent table "ICMP.Targets" should have "Standard deviation" column)
        NX-2121 (Status map view should show node aliases)
        NX-2124 (Log parser hangs on lines longer than 4095 characters)
        NX-2125 (Server incorrectly reads IP network mask from VMWare ESXi and vCenter)

Best regards,
Victor

Hi,

few notes here. First, you don't need both session agent and user agent - use agent has all the functionality of session agent.
And you can select "Install user support application" in unattended installer by adding to installer command line option

/MERGETASKS="useragent"

Best regards,
Victor

Try to set debug level to 7 for tag ncd.msteams - you should see more detailed diagnostic in the log then.

Best regards,
Victor

Hi,

\ is an escape character in NXSL string, so for actually passing \ to regex processor, you can escape it, like this: "^\\.1\\.3\\.6".

In simple cases you can use like instead of regexp matching. For example, to match all OIDs starting with .1.3.6.1.2.1 you can use condition

if (oid like ".1.3.6.1.2.1.*")
{
   /* match, dio something */
}


Best regards,
Victor