Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - squeezypiano

#16
Genius! Thank you. Tested that and it all started working.  Switched CheckTrustedNodes back to 1 and added Trusted Nodes to the node containing the DCI and that is working now too.  It seems slightly strange, however, that to use the -o option to send a value for the node doing the actual sending requires it to list itself in Trusted Nodes.

Thanks again :)
P
#17
I have spun up another box in case there was a problem with something on it and can now get data from, for example,

nxapush param1=4

Still cannot get anything using -o to push on behalf of another node.  I can work around this but it would nice if I could work it as it would keep a cleaner config.

Thanks for your help.
#18
I am using the paramater not description so should be good there.  Can you confirm which ID the object ID is, please?  Is it the ID of the DCI?
#19
Thanks for replying.  I have tried now with -o using DCI ID and node ID but neither is working still.
#20
Hello,

I am having trouble getting the push DCIs to receive values.  I followed these steps so far.


  • Set your DCI's origin to Push Agent and configure other properties as usual, excluding polling interval which is meaningless in case of pushed data.
  • Create separate user account or pick an existing one and give "Push Data" access right on the DCI owning node to that user.
  • Use nxapush utility for pushing data.

I have tried nxapush with and without the user account I created, e.g.:

./nxapush param1=5

and

./nxapush -u user -P password param1=5

but I do not get any data in NetXMS.  I have used tcpdump on the agent and server machines (both Ubuntu) and can see the data bent sent and received by the OS.  I have also tried the same commands using nxapush on the NetXMS server too.

If I run nxapush with -vv I get only one line out saying 'Connected to NetXMS agent' and that is all (was expecting a full debug).

I guess I'm missing something but I cannot work out what.  Can anyone give me some guidance, please?

Thanks in advance,
P
#21
General Support / Re: Count SNMP walk results
June 08, 2016, 12:00:59 AM
Thanks, Tomas.  Works perfectly  :)
#22
Quote from: tomaskir on June 07, 2016, 11:12:00 PM
You can actually get per-ssid client-count on MikroTik.
Check out the .1.3.6.1.4.1.14988.1.1.1.3.1.6 tree.
(each SSID has its own instance, and then client count as value)

Hi Tomas, thanks for replying.  This OID does not work when the APs are centrally managed, only on standalone access points.  I will try to track down the documentation for nxapush and give it a try.  Thanks.
#23
Hi,

As a new user to NetXMS I still cannot believe just how easy it is to use.  I have been looking for a replacement to the old RRD based systems for a while and this is blowing everything else away.  I just have a couple of things I am struggling to get worked out (custom scripting seems the way to go with these) that I would like to iron out before I add it to my production.  I have split them in to two posts to keep it simpler.

This topic is about reading data from a text file.  I am using MikroTik APs managed from a central device.  It is possible, using SNMP, to get a count of all clients attached across all the radios but I am looking to go in to more detail, e.g. clients per radio or clients per SSID.  I cannot get this from SNMP so have scripted the MikroTik to dump a text file at regular intervals listing the SSID and radio ID for each active client.  Here is an example of what it looks like.

ssid1::cap001-1
ssid1::cap001-2
ssid1::cap002-1
ssid1::cap002-2
ssid1::cap001-2
ssid1::cap001-1
ssid1::cap002-2
ssid1::cap001-2
ssid2::cap002-1-1
ssid2::cap001-2-1


The big question is how can I filter that in to results.  So maybe counting all the lines containing cap001 or cap001-2 (for the specific radio in a dual band device) or even more granular for ssid1::cap001-2 for all client connected to that SSID on that band on that radio.

Anything to point me in the right direction would be appreciated.

Many thanks.
#24
General Support / Count SNMP walk results
June 07, 2016, 10:50:53 PM
Hi,

As a new user to NetXMS I still cannot believe just how easy it is to use.  I have been looking for a replacement to the old RRD based systems for a while and this is blowing everything else away.  I just have a couple of things I am struggling to get worked out (custom scripting seems the way to go with these) that I would like to iron out before I add it to my production.  I have split them in to two posts to keep it simpler.

This topic is an SNMP Walk query.  I am trying to work out how I can count the lines in a SNMP Walk.  For example, I might want to count the number of Arp entries where no SNMP OID exists.  I would like to be able to get just a count as an integer from walking 1.3.6.1.2.1.4.22.1.2.  Is this possible?

Many thanks.
#25
Hi Tomas,

Thanks for the reply (and the excellent videos that got me going with NetXMS).  I think you are spot on.  I added a bridge and it now responds but only with info from the bridge, not from the switch.

Not to worry, just another CRS thing that would have been nice.

Thanks.
#26
Hi Victor,
Neither OID responds on that device (.1.3.6.1.2.1.17.4.3.1 responds on another MikroTik device though).  I will ask the question on the MikroTik forum instead.
Thanks for helping.
#27
I have to confess I have assumed it does. I can see the FDB in the GUI and another device (although a different model) does show it in NetXMS running the same version of RouterOS.
#28
Hi,
I have been trying to work out why my NetXMS install is not giving me a Layer 2 map.  It is only a small test network with a Mikrotik CRS in the centre (sat between a Mikrotik router and a couple of Mikrotik access points).  I think I have narrowed it down to NetXMS being unable to retrieve the forwarding database from the switch.  Does anyone else have a similar experience and/or what can I do to get these values so NetXMS can retrieve it.
Many thanks.