NetXMS Forum

thanks, easy when you know how.

After some trial and error got some json output from this command: curl -k -u admin http://netxms:8080/webapi/alarms -X GET -d '{"alarm":"outstanding"}' It is returning all alarms regardless of whether they are NORMAL, WARNING, CRITICAL but its a start.

@pvo, thanks that did the trick.

I just double-checked on one of our servers and can confirm that at least Windows 2016 isn't using the ifX table (which you are trying to query). Considering SNMP on Windows has been deprecated for a while now, I wouldn't expect that to change. That also means using SNMP is probably not the best way to get this data from a Windows system in general. For the ifTable, you'd want to query .1.3.6.1.2.1.2.2.1.10 for inbound and .1.3.6.1.2.1.2.2.1.16 for outbound. Again, I would not recommend doing this on busy Gigabit or faster connections as counters are going to overflow every few minutes and you won't be able to trust the data you're receiving. There are two ways to setup Agents. The original way is for the NetXMS server to connect to the client. This doesn't require any certificates at all, just a port forward for TCP 4700. If you only have one agent at the other end, this will work just fine for you. The other way are Agent Tunnels, in which case the Agent will connect to the NetXMS server. This one requires certificates on the server (the server will then generate certificates for the clients as needed). There are some guides available on the forum and at least on Linux it looks more complicated than it really is.

SMTP Authentication was added in 4.3, please see updated documentation: https://www.netxms.org/documentation/adminguide/event-processing.html#notification-channels

Looks like "server already configured" marker is missing from the registry. Check key HKLM\Software\NetXMS\Server, there should be DWORD value "ServerIsConfigured" (actual value does not matter, it just should exist). If "ServerIsConfigured" does not exist - wizard will start in interactive mode.

I don't think the system "queues" alerts during maintenance and upon leaving maintenance checks which ones are still valid. For all I recall maintenance mode simply stops alerts from going out. Result in your case: NetXMS will detect the change from Up to Down. As the devices are in maintenance mode at the time, the alert won't be sent. As the status then doesn't change (i.e. it stays down) there is no alert. I think the repeat interval will eventually trigger a new alert, but that could be a while.

Upgraded to 2.2.4 didn't help. What I found though is if I rename the container and then press enter it fixes the issue. Also noticed that if I select Help \ About in nxmc.exe window it reports version 2.2.3 but on the splash screen at login it reports 2.2.4

Hi, either server process is actually running (in that case you should shutdown server process first), or crashed (in that case you can answer "yes" and remove stalled lock). Best regards, Victor

Thanks for clarify, fair enough reason Was running SQLite on a Test/Demo server (proof of concept) because it was fast and easy to rollback/maintaine But as i now understand the problem i will migrate to another DB

opted to restore from backup. system back up and running again on v2.1.2

Hi Is it possible to hover over a line chart value and have a tooltip popup with the name of the node name or the label that it refers to in the Legend. Thanks Carl