NetXMS Support Forum

Hi,

yes if you are expanding parameter from template. When template is applied on node, you can use %{node_primary_ip} macro (see https://www.netxms.org/documentation/adminguide/data-collection.html#macros-in-template-items for details).

Best regards,
Victor

Hi,

server caches object data in memory, so direct DB changes while server is working will not be picked up. You can use NetXMS API to modify object custom attributes (either Java API or Python scripts using nxshell).

Best regards,
Victor

Hi,

is it possible to provide us remote access to test device over SNMP? That will greatly simplify driver development.

Best regards,
Victor

Hi,

I've added this as feature request (https://track.radensolutions.com/issue/NX-1235). I'll think how we can implement this.

Best regards,
Victor

Hi,

is is implemented in 2.1-M3 (called agent tunnels), although currently it is a bit complicated to configure and maintain. But ww already have few deployments. Next release will contain tools for simplified agent tunnel management.

Best regards,
Victor

Hi all!

NetXMS version 2.1-M3 is officially released. This is planned to be last milestone release in 2.1 branch, next release will be RC1. Changes since 2.1-M2:

- Improved event correlation based on network topology
- Improved the usability of the Server Configuration, by adding descriptions and recognition for data types and possible values
- Alternative core configuration section can be set for nxagentd using -G command line option
- Implicit external subagent registartion using EXT:* sections in agent configuration file
- Unknown syslog sources can be automatically added as nodes
- Server startup scripts
- New method "setMapImage" in NXSL class "NetObj"
- New attribute "mapImage" in NXSL class "NetObj"
- New NXSL class "Container"
- New NXSL function AgentExecuteActionWithOutput
- Container autobind mode and script can be set from NXSL
- Fixed bug in NXSL string concatenation
- Events generated when interface expected state changed
- Situations functionality is replaced with persistent storage that is included in each execution environment
- Compression support in communication protocol
- Switch forwarding database show correct interfaces for Mikrotik devices
- Driver for Juniper Networks switches
- Driver for Extreme Networks switches
- Experimental MQTT support
- Experimental agent-to-server connections (agent tunnels)
- Experimental Grafana integration
- Management console:
   - Mutiple files can be scheduled for upload to agent at once
   - DCIs created from templates made visually distinguishable in data collection editor
   - "Inverted" flag ignored in event processing policy if event or object list is empty
   - Object tools can be filtered by custom attribute presence
   - Configurable list of external URLs for each object
   - Sound for outstanding alarm reminder can be configured
- Fixed issues: NX-60, NX-630, NX-743, NX-916, NX-1119, NX-1123, NX-1129, NX-1151, NX-1161, NX-1165, NX-1171, NX-1174, NX-1178, NX-1
188, NX-1190, NX-1191, NX-1192, NX-1193, NX-1197, NX-1198, NX-1213, NX-1216, NX-1217

Best regards,
Victor

Hi,

I've added a feature request for that: https://track.radensolutions.com/issue/NX-1234. Should be an easy fix.

Best regards,
Victor

Hi,

yes, that's a bug in 2.1-M2. Should be fixed in 2.1-M3.

Best regards,
Victor

Hi,

no, currently there is no fine grained control on agent level for that. You can however override actions provided by platform subagent using Action option in configuration file, like

Action = System.Restart:/bin/false

(or any other harmless command).

Best regards,
Victor

Hi,

most likely a bug. Somebody will take a look at it )I've registered it as a bug - https://track.radensolutions.com/issue/NX-1233).

Best regards,
Victor

Sounds really weird, I'll try to reproduce it.

Best regards,
Victor

Added it as feature request (https://track.radensolutions.com/issue/NX-1232).

Best regards,
Victor

All notifications controlled by your event processing policy. Make sure you have a rule for notifications on SYS_NODE_DOWN event without additional filtering on source node. If notification rule is correct, check that there were actually SYS_NODE_DOWN events for all nodes (you can tight click on node and choose "Event log" to see all events for that node).

Best regards,
Victor

Hi,

yes, it is ready. We had enormous load last week so I had no time for finishing downloads and so didn't make official announce.

Best regards,
Victor

Yes, it is still considered. But it is much more complicated then template graphs, so we need more time/resources for implementation.
Best regards,
Victor