NetXMS Forum

We are installing from nxagent-4.1.377-linux-x86_64.tar.gz on a server running FreePBX and were hoping to start monitoring the asterisk server that is running.  However the subagent for this does not appear to be included as part of the build.  Would prefer not to compile from source and wondering what our options might be?

While I did not see anything in either of the release notes we are running 4.1.377 and this issue appears to be resolved.  Suspect there was some change and maybe not significant enough to make the notes.  Thanks!

Thanks as always Victor!

If we select a node in the Objects tree and then under the Object Details look at any tab and then click back to the Overview tab it can take upwards of 10 seconds before displaying anything besides the header tabs.  However when clicking from the Objects tree it is immediately visible for the node.  This is the latest version of the console / server (4.1.283) and console is MacOS.  I have attached a screen shot of what we see.

While I am all in favor of the new SSH monitoring that was implemented it just seems to be reporting false positives way to frequently.  Not sure if it is timing out too quickly, but there does not seem to be any sort of "control" for how it works.  For us every time this has triggered the SYS_SSH_UNREACHABLE event we have been able to SSH in from the NetXMS server.

Thanks!

Yes, 3 bytes is working.  We typically always just searched on the last 2 bytes and would like that to work, but we will use this in the meantime.  Thanks for clarifying!

Per the 4.1 release notes this was supposed to be fixed.  Cannot figure out how to use it though as any partial MAC address combination I try comes back with:

MAC address entered is incorrect.  Please enter correct MAC address.

This is 4.1.283 console / server.  Thanks!

Thanks for the link.  I tried calling this function a million different ways and it always caused my script to crash.

It would be very difficult to provided access to the Cambium devices as they are all private IP space.  However, we have determined that it is firmware version related and so therefore definitely on the Cambium side.  Version 4.6.1 works with AES (though you must set R/W enabled) but 4.6.2 / 4.7-RC14 do not work.  I have submitted this to Cambium.

While the scripting did indeed work to set the settings, NetXMS would report the SNMP agent as not responding until we did a Poll -> Configuration (Full) on the node.  Can this be triggered from the script as well?  Is this interface documented somewhere we can look to see what is all available?

Also, only partially related but with Cambium ePMP radios if we used SHA / AES combination NetXMS would not ever talk to the device.  It works fine with SHA / DES.  However, running the command line snmpget from the NetXMS box has no issues with the SHA / AES setup.  Almost seems an issue in either NetXMS or Cambium AES implementation?  Thoughts?

This will work, thanks!  Now I just need to figure out how to pattern match on the node name in that language to filter the nodes, but assuming that should be trivial. 

I would still vote for making NXSL capable of fully managing the system as that is of course what we spend most of our time writing with for all of the other processing.

Thanks as always for the solution!

We are in the process of making some SNMP changes and during the process many devices will continue responding on v2 as well as v3 (new).  What we have discovered is that since NetXMS discovered them with v2 it just continues to chug along using that which for the most part is fine until we turn v2 off which is the plan.  HOWEVER, once we enabled v3 on the devices they started sending out SNMP Traps using v3 and NetXMS just blindly ignored them because it did not have SNMP v3 setup for the devices.

So, we were looking to mass update these under the Properties -> Communications -> SNMP section of the node.  We are talking 1000's of devices and looked to automate this through a NXSL script.  However, those properties do not appear exposed from what we have been able to discern and therefore cannot be updated. 

Looking for thoughts on how to accomplish this without adjusting the settings 1 by one on each of the nodes.  Thanks!

Dumped it and found out the response is CRLF (0a 0d).  Sure enough monitored for that and works.

Threw the agent into debug 9 and see the following which does not help:

2022.04.21 14:13:54.851 *D* [comm.cs.17         ] Requesting metric "Service.Check(pop3://username:[email protected]/,^.*OK Authenticated.*)"
2022.04.21 14:13:54.851 *D* [netsvc             ] H_CheckService(pop3://username:[email protected]/): pattern=^.*OK Authenticated.*
2022.04.21 14:13:54.977 *D* [netsvc             ] H_CheckService(pop3://username:[email protected]/): got reply: 2 bytes
2022.04.21 14:13:54.977 *D* [netsvc             ] H_CheckService(pop3://username:[email protected]/): not matched
2022.04.21 14:13:54.977 *D* [comm.cs.17         ] GetParameterValue("Service.Check(pop3://username:[email protected]/,^.*OK Authenticated.*)"): 0 (SUCCESS) value = "3"

If only I knew what the 2 bytes were...

Unfortunately that does not seem to be the issue.  This is the NetXMS agent on Windows server:

2022.04.21 07:47:13.062 *D* [init.curl          ] cURL initialized (version: libcurl/7.56.1 WinSSL zlib/1.2.11 WinIDN)
2022.04.21 07:47:13.062 *D* [init.curl          ] cURL supported protocols: dict file ftp ftps gopher http https imap imaps ldap pop3 pop3s rtsp smb smbs smtp smtps telnet tftp
2022.04.21 07:47:13.062 *D* [netsvc             ] Using cURL version: libcurl/7.56.1 WinSSL zlib/1.2.11 WinIDN
2022.04.21 07:47:13.062 *D* [netsvc             ] Supported protocols: dict file ftp ftps gopher http https imap imaps ldap pop3 pop3s rtsp smb smbs smtp smtps telnet tftp
2022.04.21 07:47:13.062 *I* [subagents          ] Subagent "NETSVC" (netsvc.nsm) loaded successfully (version 4.0.2157)

We are working to monitor a number of services that per the manual have cURL support and hence should be using the Service.Check agent command.

We are working to get POP3 working at the moment and have:

Service.Check(pop3://username:[email protected]/,^.*OK Authenticated.*)

If we put in actual values and run this using from the command line using the curl -v command we get valid results.  However, when we run it from a DCI it always comes up with 3.  How can we see the value being returned from the check.  Also, it states the Service.Check.XXXXX are to be considered deprecated in the documentation.  Wondering why since they seem to offer more complete testing of common protocols?

Thanks!

If I actually remove the agent and let it poll directly from the server with the node containing the credentials I seem to be getting the results now.  Will test this on a larger batch of devices, but hoping with that configuration setup it will work.  No agent involved at all.  Thanks for checking into this!

Yes, that was exactly the issue and it just caused of course inconsistent results depending on when each applied themselves.  Thanks!

We seem to be having a strange issue, that likely has been recently introduced.  We are running the latest 4.0.2227 version.

We have a number of Custom Attributes defined on the Infrastructure Services folder with values that we use on nodes to control scripts.  They are all setup to be Inheritable.  Underneath we have a folder called "Telephone Customers" where we setup some custom attributes with the same names but override the values to be specific to that group. 

The issue is that Nodes under that folder seem to at times be getting the values from Infrastructures Services folder and at other times getting them as expected from the Telephone Customers folder.  If we open that folder and edit the attribute followed by Apply & Close it is applied to all nodes.  We just need it to get the attributes from Telephone Customers from the start and then not change.  One of them is where it might post messages into Slack and when they go to the wrong spot confuse the responsible people.

Looking for suggestions what might be happening and how to resolve this.

It is simply: $node->sysDescription