NetXMS Support Forum

It works as following. First of all, you have to enable TCP proxy on a proxy agent. By default it will be agent running on NetXMS server, or if zoning is enabled, agent running on zone proxy. When you run object tool with TCP proxy option, client will open random local port for listening, then establish tunnel to proxy agent, and when you open TCP connection to this random local port, proxy agent will establish TCP connection to target node on port set in object tool configuration.

So, for example, let's say you have Synology device reachable at 192.168.1.10 by the server. You will do the following steps:
1. You Synology device to NetXMS as a node, and specify 192.168.1.10 as primary IP address.
2. Enable TCP proxy on server's agent.
3. Enable TCP port forwarding option in object tool, and use URL http://${local-address}:${local-port}

When running on Synology node, this tool should open browser on local host which will be forwarded to Synology device.

Best regards,
Victor

Hi,

it looks to be disk space issue. You probably can truncate biggest tables (possible candidates are event_log and top idata_ tables). 
If you are ok with losing all alarms and event history, you can truncate tables event_log, alarms, alarm_events, and alarm_notes.

What database you are using?

Best regards,
Victor

Sure, we can add it, question is how agent can detect that it is running on Nutanix VM. Can we rely on BIOS vendor information for that? If yes, then change is quite easy.

Best regards,
Victor

We just published NetXMS version 4.5.3. It is purely bug fix release that fixes few important issues. Full change log since 4.5.2:

- Fixed server crash during passive network discovery
- Fixed bug in dashboard chart data source editor
- Fixed bug in TCP proxy session setup
- Fixed issues:
   - NX-2509 (productVersion does not display value correctly with Ethernet-IP)

I just fixed that. We will publish patch release with the fix shortly.

Best regards,
Victor

We just published patch release 2 for version 4.5. It contains few important fixes and some small improvements. Full change log is following:

- Fixed server crash on client session disconnect
- Fixed updated issues in new web UI
- Cosmetic fixes in UI
- Fixed issues:
   - NX-2490 (Server tries to read from tdata_xxxx table when TimescaleDB is used as backend)
   - NX-2502 (nxagentd uses UDP port 4700 to exchange hearthbeat messages and listens on address 0.0.0.0)

You can create scheduled task that will run NXSL script on any top level object ("entire network" or "infrastructure services"). In that script you can do something like this:

for(a : $object->alarms)
{
   a->terminate();
}

Alternatively you can use FindObejct(2) to refer to "infrastructure services" instead of $object - then you can run script in any context.

You can add additional logic to terminate only old alarms, etc.

Best regards,
Victor

Can you show full agent config?

Hi all!

NetXMS team is participating in FOSDEM 2024. You can catch us there today or tomorrow, or visit my talk on topology discovery in room UB5.230 at 12:10 today.

Best regards,
Victor

We just published patch release 1 for version 4.5. Changes since 4.5.0:

-  Driver for Edgecore enterprise switches
-  Driver for HPE Aruba Networking switches and wireless controllers
-  Chart height in performance view automatically adjusted to accomodate large legend
-  New NXSL class "MacAddress"
-  Attribute "state" of NXSL class "AccessPoint" renamed to "apState" (to avoid conflict with attribute "state" from parent class)
-  Context object views can be hidden
-  Configurable timeout for client session first packet
-  Improved VLAN handling by generic driver
-  Updated Eltex driver
-  Fix missing object synchronization for ad-hock maps (drill down)
-  Fixed server crash when interface list cannot be read from SNMP device and option to ignore interfaces in NOT PRESENT state is on
-  Fixed bug in EPP rule copying
-  Fixed line numbering bug in desktop UI script editor
- Fixed issues:
   -  NX-2491 (Add alarm category attribute to NXSL alarm class)
   -  NX-2493 (Activation / Deactivation event not shown in threshold editor)

Finally get to check this - works fine for me (using API token). Maybe the problem was in using password instead of API token.

I changed /rest/auth/1/session to /rest/api/2/myself for checking connection for the future though, as former URL supposed to be removed in the future.

Best regards,
Victor

I think that I found what could have caused server crash. Fix will be included in patch release 4.5.1.

Best regards,
Victor

Hi,

I've updated Nexus driver to recognize this model. Change will be included into next patch release.

Best regards,
Victor

NetXMS version 4.5.0 is just published. It is intermediate release on a way to version 5.0, and it includes improvements and fixes that are too big to be considered for patch release but important enough to be published before 5.0 is ready.

Full change list since version 4.4.5:

- XPath can be used for querying XML-based web services
- New NXSL operation "?." (safe dereference)
- New method "join" in NXSL arrays
- Server-side custom attributes (not visible by clients)
- Additional argument in NXSL method createSNMPTransport to control if it should fail when node is marked as unreachable via SNMP
- Updated drivers for Eltex and TP-Link switches
- Added agent metric Agent.LocalDatabase.FileSize
- Fixed internal metrics PollTime.\*
- Fixed issues:
   - NX-1409 (Implement separate access right for editing object comments)
   - NX-2275 (Option for ignoring interfaces in NOT PRESENT state)
   - NX-2412 (Separate access right for editing agent configuration file)
   - NX-2440 (Wildcard imports in NXSL)
   - NX-2485 (XPath support in web service queries)
   - NX-2487 (Any changes to object from UI or via Java API wipe out responsible users list)

Could you please explain where you configuring it and what exception are you getting? I have little experience with Tomcat, but I can check if I can adapt packages to it if I'll be able to setup test environment.

Best regards,
Victor