NetXMS Support Forum

Good point on the duplicate option - will need to watch out for that and rethink the duplicate option completely.

Having a server configuration option of SNMP / Agent is the better option.

For SNMP, what about the option of displaying a list of the mibs loaded so you can select the one you want - or - what about setting the default oid to load? Auto fill in .1.3.6.1.4.1 would be 12 keystrokes every time I add from a mib. 

More often than not, I know the enterprise so being able to type in the enterprise number only would be fantastic.

Whilst I am here, it would also be nice to be able to display the mib tree numerically as I know I want to get to .1.3.6.1.4.1 for enterprise but remembering what each one is in order to navigate - hurts my head .

Being able to edit multiple DCI's and apply a common change to all of those DCI's in one hit was one of the few nice features of CA-Ehealth - may it RIP.

Although there was a Linux template previously included - it is not now.

As a site that is SNMP based, I have had to start from scratch was lucky to have been provided with the old Linux template which has helped greatly. A windows one would also help.

Even though agents provide more details, SNMP is very quick and easy - especially if you already use SNMP via an alternate product.

With the Linux template and my 1st cut Windows template - plus some containers based on some criteria -  I was able to add over 500 devices tonight without touching any of them.

I disable discovery and simply set add node via trap to yes - switched a CNAME over to my netxms - and let the existing product poll my devices - which then sent SNMP auth fail traps - which now go to netxms - which then auto added them and auto assigned the templates.

It is likely that I will look into netxms agents, but as it stands - I can get 99% of my existing SNMP based monitoring transitioned by using two SNMP templates.

Considering the front page of the netxms screen says that netxms includes the "basics" of CPU / disk / Memory - I genuinely was surprised these two templates did not exist.

I suggest that each template include the capability for custom override such as specific file systems / mounts being excluded and having different thresholds.

The benefit to any prospective person that has windows devices is that they can add / modify the snmp settings on their devices via group policy and once that is pushed out - however discovery happens - the SNMP template will work immediately without having to install the agents.

I had a look at those links however many of the items do not have an example - especially the ones I want.

My latest dumb question - how do I match on rawd or RAWD ?

imatch instead of of ~=

A couple of ways to do this.

For me - I would prefer when in a  template - right click - add SNMP parameter.

This already happens when you add a new parameter to a nodes data collection configuration, so should be easy to add as an addition right click option at template level.

As it stands, given I am already in a template that has SNMP DCI's - right click - duplicate - works even better as it already has an OID filled in and I can easily navigate to the OID I want.

The assumption is - that you have the MIB loaded

Actually - this is probably more like a bug than just a feature request.

In Alarm Details view, thee is a section for DCI Data however for a SNMP trap, there is no DCI data - there is trap data.

For a trap, the description of the trap should be being displayed as more often than not, many traps include in their description what action is suggested. The description is stored in netxms at the trap definition level - but not transferred to Alarm Detail.

so two things needed where Alarm type = trap
1) Display the description information from the trap definition.
2) Use the description field of the Event Configuration as the formatted display and display it - one line at a time - in the Alarm Detail screen.

Thanks for the tip - be patient!!! I lost hours today expecting instance refresh - I know better now!.

Well...so how am I progressing?  it gets soooo much better

The template already had a number of exclusions so I can update / alter that as required.

But that is not the best bit....

Given that Windows uses the same HOST-RESOURCE-TABLE - I have been able to make a huge start on a Windows template.

Created a new template object and copied across the three file system DCI's.
Updated Instance Discovery to delete the return false check for the file system to start with a / - replaced it with an exclusion for our CD drives - y: drive.
if (mountPoint->value ~= "^Y:(*.*)?" ) return false;

Which leaves me 75% towards a fully functioning Windows SNMP template.

CPU is proving tricky as Windows has CPU utilization for each processor rather than overall so need to be able to collect each processor as well as do an aggregated total for all processors.
The OID in question is .1.3.6.1.2.1.25.3.3.1.2 - will see how I go.

Also of note - in the template there is code for a driveAlertCustom - which I have yet to play with. I assume that it is there to allow for different thresholds for different mounts?

And apart from duplicates for the file system entries, everything is now green.

So what did I do to get it working? - apart from the correcting the community string - which is a netxms discovery issue, not the template - nothing. Just needed to wait

And even more now green.

Absolutely fantastic day - thanks all :0

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.

The excitement of the template - followed by the agony of "unsupported"

but.... a snmpwalk using snmpwalk utility showed it working - but netxms walk was blank...

hmmm...

Even though device was recognized as snmp and details showing - it decided fault community.

Updated community..... and yes - I have data!!

It is only File System so far, and it does have duplicates for some reason - but thank you very much - made my whole year!!!

Absolutely fantastic - made my day

Having completed my fresh install - ready to get this going.

Todays answer - add the wild card!!.

return $node-> sysDescription like "*Windows*";

Thanks Victor:
https://www.netxms.org/forum/configuration/snmp-traps-handling/msg4957/#msg4957

OK...lets make this even simpler.

Can somebody point me at the old SNMP template for Linux that existed previously.

That would be enough to get me going and I can work out the Windows equivalent by using the Windows equivalent OIDs.

I told you it was a dumb question!!

It is confusing because auto bind asks for a script - but it accepts code as well - which is just one part of what is confusing.

From a solution perspective - fantastic - it works perfectly!! I use it not in a script - just using it "as is"

As much as I think netxms is fantastic, some basic tutorials that demonstrate the syntax and basic script functionality would be a great benefit to those new to netxms.

Another example of something that I should be able to do better. My Windows container uses the following auto bind but I would rather just search for Windows in sysDescription - but I do not know the name of that variable at a netxms level and I do not know the syntax for "contains". I tried like, but that did not work.

So todays dumb question

What is wrong with return $node->sysDescription  like "Windows";

The server has these two attributes in Object view:
System Description=Hardware: Intel64 Family 6 Model 79 Stepping 1 AT/AT COMPATIBLE - Software: Windows Version 6.2 (Build 9200 Multiprocessor Free)
SNMP Object ID=.1.3.6.1.4.1.311.1.1.3.1.2

For my Windows container:
works
return $node->snmpOID == ".1.3.6.1.4.1.311.1.1.3.1.2";

does not work
return $node->sysDescription  like "Windows";

What am I doing wrong here? - the OR is not working in Automatic Bind Rules.
left($node->name,4) == "rawd" || left($node->name,4) == "rawq";

These on their own work. left($node->name,4) == "rawd"; and left($node->name,4) == "rawq";   but not when I add the OR (or what I thing is the OR).

my understanding is based on this:
https://www.netxms.org/documentation/adminguide/data-collection.html#instance

Can anyone point me in the direction of where any of this is in any doco?