NetXMS Support Forum

Alarm key can be the same as most probably you have either toner or others and it is not required to make distinction here as they can't coexist
simultaneously for the same device.  

Скорее всего, существует маршрутизатор/хост, который был обнаружен первым NetXMS и сообщил маску сети 255.255.255.0. Поскольку сервер NetXMS не может точно знать, у кого правильная сетевая маска, а у кого нет, он предполагает, что первый обнаруженный узел, подключенный к некоторой подсети, имеет правильную сетевую маску для этой подсети.

We do not have SMTP service monitoring. Usually Node with SNMP is just created and credentials are correctly configured and then NetXMS is automatically detects if SNMP is no more responsing.
If we are talking about service - we do not have special service for SMTP. But you can use telnet. I tested this approach by creating next DCI on my management node with IP of SNMP device:
NetworkService.Status(telnet://10.5.5.11:22)

As for the service I've just created service object under the node with SNMP with telnet + 22 port options and it is working. 

One option is to generate separate event for low tonner and separate event for all other errors - in this case you will just create multiple rules: one for toner (send e-mail) and something else for others (for example to create alarm).

Filtering in in EPP is harder option and for it you should use left side of EPP - filtering side. I would suggest to write filtering script, that will check current DCI value that is available in $event script parameter. 

 

You can set debug level to 6 on agent, where requests should go through and check agent log. There should be messages like: 
2024.07.22 16:44:06.575 *D* [comm.cs.1250      ] Requesting metric "NetworkService.Status(https://netxms.org)"
2024.07.22 16:44:06.995 *D* [netsvc            ] NetworkServiceStatus_HTTP(https://netxms.org): got reply (807 bytes, response code 302)

Hi,
Looks like it is required to create driver for this type of devices. I wander if it possible to get remote access to this device (this way it is much faster to create and debug new driver)?

Hi, 

Issue created: https://track.radensolutions.com/issues#%20

Quote from: jdowney on November 17, 2021, 03:58:11 PMI managed to get this working just need a few tweeks as sometime receive 0 randomly. Any ideas welcome.

You can add trace command to trace data to server log when incorrect data is obtained. Like:
trace(1, "Incorrect value");

If we are talking about Windows servers, then I would advice to use Windows Event log monitoring: https://www.netxms.org/documentation/adminguide/windows-event-log-synchronization.html
Agent config should contain something like:
SubAgent=wineventsync.nsm

[WinEventSync]
EventLog=Security
[WinEventSync/Security]
IncludeEvent=4624-4625
IncludeEvent=4634
IncludeEvent=4779

You will be able to see login and logout operations in Windows Event Log of this node. When it's done you should add rules to create events on login and log out Windows Events in Configuration->Windows Events Log parser.

There might be 2 different problems. Either there is too many notification form server and client was out of sync (this status not yet mooed to new UI) or there is something bad happening with server. 
If objects are just out of sync you can drag and drop object (it should work), then close and reopen console again - if objects are properly moved after re-login - then it's just synchronization problem. If they are not - then there are some delays on the server side, chat can be investigated further more. 

Hi,

We will add it to then next release as server option.

Thank you,
Tatjana 

Hi,
HPE Aruba switch driver is selected only if it's SNMP object ID starts with "1.3.6.1.4.1.14823.1.1", we also check if we can get ".1.3.6.1.4.1.14823.2.2.1.2.1.3.0" OID form this device (model name).

Do you have any problems with Generic driver (like hardware information is not obtained,  wireless capabilities not detected, access point or wireless clients not shown)?

Tatjana

It was implemented "Query..." for SNMP Table in "Table Columns" property page in 4.4 version. So starting from NetXMS 4.4 it will be possible to query all possible SNMP coluns if metric OID is configured correctly.
I also created another issue to create SNMP table directly from the MIB Browser ( https://track.radensolutions.com/issue/NX-2429 ). 

Hi,

If you have custom attribute with name: "Region" and you want filter all nodes where custom attribute value is "Latvia" your request URL should look like: API_BASE/objects?@Region=Latvia

Then you for bug report.
Fixed in documentation (wiki is not updated anymore).