NetXMS Support Forum

NetXMS 5.1 is finally out! It contains lot of smaller features and improvements on top of version 5.0, mostly around network maps, topology discovery, and visualization.

WIndows users, please note that we have implemented proposed change on limiting Windows server builds. Server build for Windows available on web site is limited to 250 nodes. If you have valid support contract, please contact our support team for unlock key.
Linux binaries or self-built binaries are not limited.

Full change log is following:

-  New automatic map type "hybrid topology"
-  New object class "Circuit"
-  Only read access is needed for dashboard context object for scripting dashboard elements
-  Reading of FDB moved to network device drivers to allow better handling of devices not following standards
-  Peer information on interfaces can be set and cleared manually
-  Added down since nxsl parameter to access point
-  Vlans view merged in to the Ports view
-  Added option to show physical links on L2 ad-hoc map
-  L2 predefined map will not cache results, only ad-hock map results are cached
-  More accurate ad-hoc IP topology maps
-  Unreachable node will be tested for all protocols in each configuration poll
-  Use inetCidrRouteTable, ipCidrRouteTable, and ipForwardTable in addition to ipRouteTable to get routing information via SNMP
-  EtherNet/IP added as DCI data source
-  Improved web UI login pages
-  Separate "Comments" view for objects
-  Templates perspective can be configured to show nodes under assigned templates
-  New attributes in NXSL class "InetAddress" ("isSubnetBase", "isSubnetBroadcast", "subnet")
-  New NXSL function "CalculateDowntime"
-  New method "calculateDowntime" in NXSL class "NetObj"
-  Other UI usability improvements
-  Fixed session agent compatibility issues on Windows 11
-  Optional DCI event "all thresholds deactivated"
-  DCI data type after transformation can be configured separately from input data type
-  New scheduled task handler Agent.ExecuteCommand
-  Improved network map multi link spacing
-  New action System.TerminateUserSession in Windows agent
-  Fixed network map object label scaling on zoom in/out

Fixed issues:

-  NX-253 (Configurable label for Y axis on line charts)
-  NX-834 (DCI Table scroll position in dashboard is reset during refresh)
-  NX-968 (Remove Peer from unmanaged interface)
-  NX-1118 (Add "hide link labels" option for network map dashboard elements)
-  NX-1200 (New object group - Circuits)
-  NX-1288 (Fix selection colors in syslog monitor)
-  NX-1414 (Support for ipCidrRouteTable)
-  NX-1465 (When MIB browser opened, unfold tree and select longest match of device's SNMP object ID)
-  NX-1617 (Show comments window only if comment present)
-  NX-1958 (Support custom font for Label in Dashboard)
-  NX-1973 (Add ability to manually specify a peer for an interface)
-  NX-2034 (Use RENAME COLUMN on SQLite newer than 3.25.0)
-  NX-2353 (Add hotkey to start search in "Search IP address" view)
-  NX-2371 (Separate data types for raw and transformed DCI values)
-  NX-2439 (Implement agent table System.InstalledProducts for ArchLinux)
-  NX-2458 (Add option to nest context dashboard in dashboard)
-  NX-2461 (Smart algorithm for processing counter32/64 roll-over)
-  NX-2488 (Use caching when using web service requests in NXSL)
-  NX-2512 (Not able to import columns for table DCI with origin=script)
-  NX-2517 (Linux agent can crash if some CPUs are disabled)
-  NX-2528 (Markdown Support in Object Comment Sections)
-  NX-2531 (Ability to disable server actions in EPP)
-  NX-2533 (NXSL global variable that contains object tool input field values)
-  NX-2535 (Replace drop down with radio buttons in EPP rule Downtime Control)
-  NX-2538 (Add ability to use IPv4 style netmask in network discovery target properties)
-  NX-2540 (Add $map object for use in map filter script)
-  NX-2541 (All EPP actions should be executed asynchronously)
-  NX-2542 (Add syslog metadata to generated events)
-  NX-2544 (New agent metrics for counting online and offline CPUs)
-  NX-2545 (Exporting a template with big file in a policy causes nxmc to close)
-  NX-2552 (Exception in desktop UI)
-  NX-2562 (Add pollingScheduleType attribute to DCI object)
-  NX-2566 (List of packages is not read correctly on linux systems where alien is installed)
-  NX-2574 (nxevent and nxaevent utilities do not support named event parameters)
-  NX-2580 (Configurable default time range for ad-hoc line charts)
-  NX-2584 (Change network map edit mode to network map lock mode)
-  NX-2586 (Export all to CSV not working in data collection configuration view)
-  NX-2593 (Add option to use properties file for NXShell)
-  NX-2596 (Unable to create zone via Web API)
-  NX-2597 (Log PATH and LD\_LIBRARY\_PATH values on agent startup)
-  NX-2598 (Generate event when all thresholds of a DCI are rearmed)
-  NX-2602 (Audit log not available in context menu for some objects)
-  NX-2606 (no id ranges possible in Configuration->Windows event log parser)
-  NX-2613 (Show gray "Any" in "source objects" list, if it's empty)
-  NX-2617 (Show info in EPP rule that "Accept correlated events" is checked)
-  NX-2618 (Server crash when file upload task configuration is invalid)
-  NX-2619 (SQL insert into nodes failed)
-  NX-2620 (System.ProcessList truncates the full process name or path)
-  NX-2621 (Add "Line chart" item in context menu of map link)

Added in 5.1 - nxshell now reads nxshell.properties if available in current directory or classpath. You can also specify path to properties file in command line.

Best regards,
Victor

This is fixed, fix will be part of release 5.1.

Best regards,
Victor

So the problem here is that AP in question does not support neither LLDP nor CDP (not even spanning tree), so there is no way of getting topology information from it. CDP/LLDP not being supported in this context only means that information collected via those protocols is not made available via SNMP, even if device can send/receive CDP or LLDP packets.
If there is topology information available through vendor MIBs, then we probably can implement topology information reading on driver level.

Best regards,
Victor

Screenshot below shows how we do it. Basic idea is not to send "node up" notification if timer for "node down" notification was not fired yet. Note that rule order is important in this setup.

Best regards,
Victor

Hi!

Looks like your database runs out of space and is not configured for automatic growth. You have to manually add new data file or enable automatic growth.

Best regards,
Victor

Just fixed the issue, fix will be included into release 5.1.0.

Best regards,
Victor

GITEX started today in Dubai, and our team is participating. If you happen to be there and want to chat with us or get first hand answers to your questions, feel free to visit us at stand H1-C30 (Hall 1).
 

Пока как workaround можно сделать configuration poll hook, в котором находить нужные интерфейсы, и на них вызывать setExcludeFromTopology(true). Что-то вроде этого:

if ($node)
{
   for(iface : $node.interfaces)
   {
      for(a : iface.ipAddressList)
      {
         if (a == "0.1.134.160" or a == "192.168.1.1")
         {
            iface.setExcludeFromTopology(true);
            break;
         }
      }
   }
}

В версии 5.2 добавим какой-то более удобный встроенный механизм.

Task handler Agent.DeployPackage expects parameter string as set of key=value entries separated by semicolons. Currently only one key is supported - "package". So if you have package with ID 123 then setting task parameter to
package=123
should do the trick.

Best regards,
Victor

I mean what NetXMS shows on overview page for those nodes in "Capabilities" section - to check how server sees those devices.

This is firewall design problem in my opinion, as this is perfectly normal traffic pattern. However, I think we can implement configurable option in our SNMP stack to keep pool of sockets and reuse them when possible.
Added feature request to the tracker: https://track.radensolutions.com/issue/NX-2614

Best regards,
Victor

Just fixed it. Official fix will be in 5.1, but if you need it to work in 5.0, you can rebuild web API from source branch stable-5.0 - fix is backported here as well.

Best regards,
Victor

Just added new handler type Agent.ExecuteCommand - it will be available in version 5.1.

Best regards,
Victor