Hi, just commented in the issue. Best regards, Victor

It might help if I show the "after" with the trap now in NetXMS. Excluding the effort to get it there - the Alert Detail is now absolutely fantastic from a readability perspective and usability perspective. [image: formatted ucs trap - the netxms version.png]

Thanks, Victor. I can confirm that this works for both base stations and clients: [jaustin@jaustin applications]$ snmpwalk -v1 -c xxxxx <mgmt address> 1.3.6.1.4.1.4458.1000.1.1.6 iso.3.6.1.4.1.4458.1000.1.1.6.0 = IpAddress: <mgmt IPv4 address> [jaustin@jaustin applications]$ snmpwalk -v1 -c xxxxx <mgmt address> 1.3.6.1.4.1.4458.1000.1.1.7 iso.3.6.1.4.1.4458.1000.1.1.7.0 = IpAddress: <mgmt IPv4 mask> Would a Radwin driver fix the problem of the response to the ping3 driver? Currently I'm having to disable the ping3 driver, as I don't have any ping3 devices, and the Radwins reject the entire SNMP discovery query (currently three OIDs, two in mib2 and one from ping3 private, IIRC).

Thanks, Victor; duplicate detection makes sense. For some reason I had thought that it was enabled by default. Will let you know if we still have issues.

Hi, from version information for the client it seems that client is of much older version. Make sure that you have deployed new version correctly. You can see web client version on login screen in bottom right corner. Best regards, Victor

OK - Windows threshold is working with only having to use the first three chars of the file system name at either Node level or at Persistent Storage level. [/if ( left($dci->instance,3) != NULL ) { shortdci = left($dci->instance,3); } if ( GetCustomAttribute($node,"fileSystem_Warning_".shortdci) != NULL ) { threshold = GetCustomAttribute($node,"fileSystem_Warning_".shortdci); } else if ( GetCustomAttribute($node,"fileSystem_Warning") != NULL ) { threshold = GetCustomAttribute($node,"fileSystem_Warning"); } else if ( ReadPersistentStorage("fileSystem_Warning_".shortdci) != "" ) { threshold = ReadPersistentStorage("fileSystem_Warning_".shortdci); } else { threshold = ReadPersistentStorage("fileSystem_Warning"); } if ( ( threshold == null ) || ( threshold == "" ) ) { return null; } if ( $1 >= threshold ) return 1; else return 0;code] And this is what it looks like from Object Details - Infrastructure Services as the object - Thresholds tab. I have set the overall warning threshold to 65% - and - on that first node, I set node specific Custom Attribute settings for C:\, D:\ and P:\  with different severity levels so I would know that it was each setting being picked up and each setting was being applied independently only to the file system specified. [image: customised space monitoring - all working.png]

I don't use that template but others have had this type of problem and there are a number of ways you can do this. Given the drive monitoring under the NetXMS Windows template is generated based on instances, here are two ways I know of. Better option: To add override capability to that template - this thread explains how to do that. https://www.netxms.org/forum/configuration/dci-template-manual-override/ Not so good option: You may have to do this for all your drives as the template item to disable may also need to be the instance version. If you want to disable the template and simply add your own - the following thread explains the disable part. Duplicate the template version first - update the duplicated one - then disable the template one. https://www.netxms.org/forum/configuration/changing-template-reapply/ As Victor explained - the warning is correct - you are trying to update the template version - which can, and will, get overridden. What you need - Duplicate, update the duplicate, and disable the template one - try that first. Below is how I would do it - or at least try it. Find DCI item you want to change. Right click - Duplicate Right click - Disable (Goes yellow) - Template version now disabled. Right click on the Duplicate (At bottom of the list of DCI's) - Edit Make changes in Thresholds as per what you want Click Apply and then OK All done This should work on the basis disabled template items stay disabled even after e template update.

Fantastic - thanks again Deprecated but still included. As much as no changes will be made - not really expecting any. Things like this will just have to be lived with. Will import and see how I go funny thing is that my switch that I apply it to - only picks up Fa0 and Nu0 Will update the server config and see what happens then *** Magic *** Both the Windows devices and the switch is showing for all ports now - excluding those that are disabled as per the scripts design. Thanks again Tursiops - another fantastic piece of assistance that I had no chance on my own of ever working out. Note to self - remember the 5 second polling and change to 600

Well, between the excitement of success and the agony of defeat or which there has been plenty of both - I am still here - just! NetXMS is a fantastic product with some fantastic capabilities - but - the initial learning curve is hard - for most, probably too hard. I persisted due to a particular annoyance with traps but even then, without the invaluable assistance from Tursiops, absolutely invaluable, I would have also given up. All I needed was two generic templates - Windows and Linux - both based on HOST-RESOURCE-MIB - tailored for the nuances of Linux and Windows. Although templates exist for agents, the fact none exist for SNMP suggest potential SNMP based users never got over that initial hump and simply went elsewhere and found something else. A shame really as NetXMS can do so much!. I am at the point where my Linux generic SNMP template is about 98% there (just needs some tidy up) and my Windows generic SNMP template is about 80% there - some cleanup plus getting customized threshold per drive using first three letters of drive working - and that is it. Elapsed time for this part is just 8 days from when I first got my hands on the old Linux SNMP template. With the assistance of both Tursiops and Victor as I bumbled my way forward with questions that to others would seem very simple, but to me - stumped - these templates will now become a reality. An immense thank you to both of you. Had these templates been available on day one - I would never have considered leaving. It is not that they do everything I would like - but they do provide me with the minimum that I need and that is the point - unless I can see a clear path from the problem I am trying to solve and the minimum that I need - I move on to any one of the many alternatives. I was lucky - very lucky. I hope to return the favor once the templates are complete and post them where others can use them. As Tursiops has pointed out - these templates do not claim to be the best / fastest / neatest / cleanest ways of doing this - they are simply a start that can be built on and evolve over time so that better ones can be created. So, two weeks on - I am still here. There is still plenty for me to do, but at least I know now that those who follow, who use SNMP for monitoring, will find a much easier experience getting up and going.

yep - imatch works

You have to write the reports yourself. There are some sample reports on this thread: https://www.netxms.org/forum/installation/reporting-server-4315/

Done - all working!! Overkill to have this on the Overview page - but doing so just to demonstrate it working on an 8 CPU server. Victor and Tursiops - thank you both - a fantastic outcome [image: windows - snmp - all working.png]

I just HATE when this happens - I was a guinea pig for a scripted deployment of JRE, which pushed the same version to my system but gave me a 32 bit instead of 64 bit. <In my best Roseanne Rosannadanna voice> "Never mind."

I have done this....its a bit of work to get started. To begin with I created 4 x 1 colour 24x24 pixel png's. Black, green, yellow, and red.  I uploaded them to my image library.  Next I create a Network map->custom, with a black background color, but for now just leave it white and turn off "auto arrange".  You can now add "dci images" that map to your data source, with a default image of the black png, and place it where you want it.  You now setup "rules" on the "dci image" so different thresholds show a different colour image.  I usually go back after placing everything and turn the background black, but you can put a geo map or other image as your background.  My original goal was to make a LCARS display but real work took over and I just made a grid status display for a small number of systems/process indicators.  I also did a similar indicator setup on a picture of a switch with the indicators on the actual port lights to indicate status.  NetXMS has proved to be too good of a tool and we expanded to far too many devices to make this manual way worth it ( I ended up with a LOT of network maps that people just weren't using).  Now if I could dynamically feed a DCI summary table into a custom network map template that would be awsome. Have Fun!

Over the last 15 years I have used or tried many, many NMS. Ironically, I stumbled onto Netxms when I went looking for an old favorite "the dude", having become frustrated with the latest NMS we are using. We seem to have the knack of finding NMS solutions that are either become too expensive, become split into numerous products, discontinued when vendor buys new NMS and tries to force swap to their latest NMS - and the latest - cannot handle SNMP traps with special characters - a comma or a forward slash. I have spent a week now with Netxms and to be completely honest - I was just about to give up and move on again. As Tursiops correctly points out - without templates, Netxms is hard - really hard. I know SNMP traps and I know SNMP - but I do not know Netxms and as powerful as it is - intuitive is certainly not one of its features. Why am I still here? - Tursiops - plain and simple. I have a couple of thousands devices that I use SNMP to monitor yet there was no SNMP template. I was surprised and shocked. First off though - SNMP traps. There is so little out there that does this well. CA Spectrum lost its best friend in CA Ehealth who got EOL. ORION has a trap listing, OpManager cannot handle special characters, NNM scrolls just one line at a time - BUT - NetXMS looked promising!! I imported my unique mib I built. Even though I had formatted it as per RFC and all descriptions and fields declared, NetXMS requires each trap to be manually and painstakingly entered for each parameter. As bad and as horrible a time wasting task that is - the upside is that I was able to get it loaded - and see what my traps looked like. First off - send some traps with special characters. No point beating around the bush - either it can handles it or it cannot. Passed with flying colors!!! Absolutely fantastic. Second off - I want traps from my Production devices to have a different severity than my Dev devices - or at least be able to filter them somehow. Absolutely fantastic again!! I created containers using includes and matchs / imatch and !imatch - option 2; and then worked out how to use event processing policy to create one policy for Prod and a different one for Dev. Option 1 solved. Again - Tursiops assistance was required to get syntax working. Even though adding trap processing is incredibly manual - unnecessarily so (the mibs have the oids for each trap - just import them by default) - I had the minimum that I needed. So what was I to do about the lack of templates for SNMP - start from scratch? - yep!!. Tried that and after asking about why no SNMP template was included - a miracle!! - Tursiops mentioned that there used to be a Linux template. As Windows SNMP and Linux SNMP are both based on RFC 2790 - that "old" template held out the hope that usability would be possible without the monstrous learning curve envisioned. Tursiops was kind enough to locate that template and posted it. Ten minutes after I saw that - it was downloaded, imported, in and running!!! Linux - was now covered!! For Windows - I have copied across the file system DCI which is working perfectly for file systems and memory(with a little mod of my own - unassisted!!). CPU is "in progress" Even though NetXMS solved by trap processing problem - the lack of basic templates for Windows and Linux for SNMP would have been a show stopper. Yes there were templates for agents - but agents are another level of complexity. If I was going to be forced into agents, I would have probably gone Grafana / Prometheus and wmi export etc.. All I wanted was decent snmp trap processing and basic snmp monitoring - CPU / Storage / Memory. Once I get the Windows CPU worked out, I will have that. For the many sites in the world that needed a SNMP based CDM monitoring option once CA Ehealth (snmp based CDM monitoring) went EOL 2 years ago - NetXMS would have been a fantastic drop in solution - if it had those two simple templates - Linux and Windows.  It is  a fantastic product with great capabilities - but getting started is just too hard. I was lucky - I was annoyed enough with traps to persevere - and the miracle of Tursiops with the template meant that I could get over that initial hump. Whats next? - if / when I get the Windows template up and working - customizable thresholds by mount point included - I might just see how many of my other monitoring products NetXMs can replace in addition to the three I am currently looking at.

We have a mid-June deadline, so should be soon. Best regards, Victor

@egert143 said in First time installing NetXMS: I would like to ask one additional question, but not sure if i should start new thread for that. Is there possibility to have a "safe / know" list of devices per "site / subnet" for example known good mac + ip combo and when new device appears with network discovery it will get flagged? Yes, it's possible with some scripting. Rough idea is to create mapping table with good MACs, setup script action to SYS_NODE_ADDED event, and in that script check if one of node's MAC addresses is in that table. Best regards, Victor

The check did not fix anything and when looking at Data Collection Configuration, the DCI items were still showing template as unknown. Now, thanks to the generosity of Tursiops, I have a Linux snmp template - so thought a clean install in case of the unknown templates. The new template is in and already live - a fantastic day for an absolutely fantastic product.  

Hi, predefined graphs and dashboards configurations are completely independent now. Adding predefined graph to dashboard seems like a good idea, I'll add it as feature request. Best regards, Victor

This should be moved to Feature Request - this cannot currently be done. This would / could / should? be implemented as follows: Add extra option in , for SNMP trap mapping, to pass each of the varbinds pass through as both the name, and the value, to Event Configuration.  This information is already available and known via the parameters in the SNMP trap definition. In the Event Configuration - a tick box option for the parameters from the trap to be passed through to Event Processing. Alternatively, a box which can be selected, that loads up the varbind descriptions and their position i.e. %name %1. In Event processing, an additional option for displaying the trap details in the Detailed Alarm view in a separate field called Alarm Details. This would also allow the Alarm Description to be reduced in size from %m which is the whole message down to one or two varbinds - making the alarm display much more readable.