NetXMS Support Forum

nothing special just added all the required packages to compile and compiled on the device ..Im trying to to either do a static compile or create a deb package but im having trouble.  The static compilation fails and if any one has some good docs on building a deb please let me know. but other than that it works great no problems at all

maybe add support for mqtt in order to recieve sensor and other data easily with out having to compile nxevent etc for embedded devices..

ah hah 

Works now  this is running on a Rasberry pi and I left everything at defaults when i compiled it so i was running

nxmibc -d /usr/local/share/netxms/mibs -o /usr/local/share/netxms/mibs/netxms.mib


but data directory was  /usr/local/var/lib/netxms


Thanks for the help

sorry just realized after i posted

Maybe a bug in mib import for 2.0  tried importing mib that  was successfull in 1.2.17 but never shows up in mib explorer on 2.0  it does compile without error but just never shows up in the tree

Hey guys,

I was looking into getting support for these devices added  but thought I would give a go at compiling the agent and was successfully able to install the agent/client  on the ERL I havent tried the ER PRO yet but I know it almost the same. My idea was throw one of these inexpensive boxes in each segment or remote location doing icmp checks or snmp checks and ship that info back to the server to allow the server to focus on more demanding tasks ...If any one has any thoughts on this as to why this may not be a good idea please let me know...



Thanks,

Quick question is the GPS tracking feature only supported for mobile devices ? Im not seeing any reference to GPS any where any any of the Manuals ... is it possible for  regular laptop with gps attached to update coordinates back to the server via the agent ?  If so I dont see any configuration params in the conf file ..


Thanks

And by the way thank you for the quick fix ....you mentioned the fix will be released in 2.0 ... ive been wanting to move to 2.0 rc but wasnt sure how stable things are and didnt want to have to migrate everything from 1.2  .. how far along would you guess 2.0 is from being stable release

could you provide me the patch

Is it possible to do IP and Mac address lookups vi nxshell or other command line tools.  I would like to be able to use a script to query where a particular mac address is connected with out having to log in using the client .  I didnt see any options listed in the nxadm  or in the nxshell api  but I could have over looked something.


Thanks

Awesome     By chance would monitoring of the ToughSwitch and Edge Routers be possible  since they too have the same JSON  response.  Let me know if you need access to these types of devices.  Here at work we have Both as well as an extensive collection of UBNT AP's 

Victor,

is there a way to pass variables through the nxevent tool ?  as a test I basically set up an unmanaged node in order for me to be able to send an event to that specific id but I want to be able to dynamically change the event notification for instance  when arpalert detects a new macaddress I want to be able to pass the macaddress to netxms which will show up as a pop saying New Mac address of %mac  detected   then based off that create an action that will trigger a mac find to show me what port that mac address is attached to ...Sorry for all the posts but im at a loss here ....Do you guys have a donation page ? I really need to at least buy you a beer for all this hard work and time put into this software and assistance you provide


Thanks again ...

Here you go.. Its seems worse with 2.0-RC2  I had to reboot my switch several times because it was continually trying several times per second and by default the ruggedcoms will quit responding after so many failed attempts. I also attached the switch debug screen. I have also tried 1.2.17 linux version running on ubuntu thinking maybe it was a windows thing

1.2.17   I also tried 2.0  with out any luck but I did not do any captures

ok after doing some packet captures there does seem to be a slight difference in response from netxms .. after the initial report from the switch which includes the engineid nextxms fails to include the engineid in following get request messages.  I have verified that both snmpb and using net-snmp command line from my laptop both work and all but netxms includes the engineid.  Not sure if this is still a vendor issues or not but the specific  switch i am testing is a Ruggedcom RS900