NetXMS Support Forum

Hi,

I noticed that the threshold settings in SNMP tables are somewhat limited compared to other DCIs, i.e. I can't do things like "trigger threshold if value is above X for Y checks".

Last night I received a whole range of alerts as a status variable switched from OK to something else for a single check (without looking at the database, I can't see what that something else was, as Tables don't have a "History" option for showing previous data). It would be preferable if I could configure the threshold to only trigger if the status is not "OK" for say three checks. Any chance to achieve this within NetXMS?

Thanks

I got it to work somewhat. I kept overlooking the word "Template". It really only works if I apply the DCI to a template which is then applied to the node, at which time the macro is interpreted. So if I change the custom attribute, it won't auto-update the DCI - which is how it's documented.
Auto-updating would be a nice feature.

I then tried to create a script that returns a specific custom attribute and used that in a DCI: all good.
Now I want to use this on a whole range of custom attributes - but don't want one script per attribute. Rather I want to pass the name of the attribute to fetch to the script. That way one script can return any custom attribute value, all I need to do is pass the name to the script macro.
But that doesn't work.
Not sure if scripts can't take parameters, if the macro doesn't handle passing them to the script or I'm missing something (again)?

Thanks

Hi,

When a DCI that has the option Show last value in object overview ticked is disabled, the last value collected remains visible in the object overview.
Not sure if that is on purpose, but it seems a bit counter intuitive to show something that's been disabled in the overview, especially as it's not indicated in that overview that this DCI has been disabled. I did not double-check the Show last value in object tooltips, but I would guess it will have the same behaviour.

Windows Server does not have Security Center, hence you can't query this information on servers.

I've been monitoring UPS runtime, and as that really should never go into a negative value, I thought I'd use an unsigned integer for the DCI.
I also used a threshold to alert if the runtime dropped by 20 minutes within 1 minute, kind of as an indicator that the battery is on its way out.

The result of the above setup is that the threshold gets triggered a lot. Every time the runtime goes down, it triggers.
For all I can tell this is due to the unsigned integer. If the the difference to the previous value is negative (i.e. from 120 to 116, a difference of -4), it compares the threshold of 20 with 4294967292 (i.e. 2^32 - diff). I don't think the unsigned integer class for the actual value should apply to the result of the diff?
Or did is this some other odd issue I ran into? Since switching from Unsigned Int to Integer, I'm not getting these alerts anymore.

That doesn't seem to work for me.

I have done the following:
- Configured a (Linux) node with a custom attribute called "testParameter", value is "Hello World".
- Created a script called "GetAttribute", which returns the value for that attribute:
sub main()
{
return GetCustomAttribute($node, "testParameter");
}
- Running the same code via Execute Server Script against the node returns "Hello World".
- Configured an ExternalParameter on the node as follows:
ExternalParameter = HelloWorld(*):echo $1
- Created a DCI called "TESTING", with following Parameter: HelloWorld(%{script:GetAttribute}) (I tried it like that, with single and double quotes).

I expected to see the DCI return "Hello World", but instead I see "%{script:GetAttribute}", i.e. the Macro is not being interpreted at all? Guess I'm still missing something?   

Hi,

I am trying to achieve the following:
- Create a single template with a DCI
- The DCI needs to be passed multiple parameters. These will differ per node.
- Assign the template to a system based on the existence of a number of custom attributes on a node. That part is not a problem.
- Use the values of these custom attributes as parameters for the DCI. That's the part that I can't get to work.

I've been searching and ran into this old post from 2013: https://www.netxms.org/forum/general-support/custom-attributes-2446/
But it doesn't really seem to help me. Not sure if I misunderstood the %{script:<scriptname>} part mentioned. Where would I put that in the above scenario, if that would even work in this case?

Any other ways to achieve what I'm trying to do?

Thanks

Yes, that worked for me as well.

Thanks

Hi,

When trying to look at previous values in DCI tables, I only see the options "Line chart", "Bar chart" and "Pie chart".
For a standard DCI, there is also a "History" option which doesn't seem to exist for tables. Considering the data is already stored in the database, it would be nice to be able to access it using that "History" as well. For example certain values may be strings, which won't really work with any of the charts. So without "History", there is really no way of looking at changes over time.

Cheers

We are currently also using additional software for flow data.
Our use case is less about alerting on DDoS or similar, but retroactively searching through the available data to identify specific data flows at a given time.
Either way, it would certainly be a nice to have.

Hi,

I've been gradually adding devices to NetXMS and now that I have three firewall clusters in the system, I stumbled over the fact that they are all using VRRP with the same MAC addresses (VRRP using 00:00:5E:00:01:XX for MAC addresses). As they belong to completely different networks that's not a problem for the firewalls themselves, but it does cause NetXMS to move firewalls into other networks on Layer 2 Topology maps and you can't really use the MAC address finder tool on them either.
I have been excluding the relevant interfaces from Topology Discovery to avoid the Topology map issue, but at the same time that means the firewalls are invisible on any such maps.

Is it possible to restrict Topology Discovery for devices or interfaces to specific zones?
That way switches could be configured to only see the VRRP MACs in their zone, which would fix Topology mapping.
I guess the Find MAC Address tool would then also need a Zone selector (probably an optional setting for the search, as most MACs "should" be unique).

Is that already possible in some way?

Cheers

Hi,

Just to answer my own question around devices dropping off maps when they go offline (in case anyone else stumbles over that): Setting the "TopologyExpirationTime" in the Server Configuration to a reasonably high enough value fixes that. Default value I believe was 3600, I changed it to 259200 at our end.

Cheers

Hi,

I have been wondering why I had several systems constantly come back with BytesOut/BytesIn being unsupported on their interfaces.
However after going through them, I found all of them had brackets in their names, i.e. "RAS (Dial In)" or "Ethernet (Production)".

So I am guessing this is actually an issue with using "Net.InterfaceNames" for Instance Discovery, i.e. it does not escape the brackets properly?
Or is there something else I am missing?

Cheers

Awesome! Looking forward to it. 

Hi Victor,

Yes, an ExternalTable like an ExternalParameter.
For example such a command could return multiple rows of comma separated values. First row defines the "Column Names" which could then be referenced in the DCI table.
Such a command will likely take longer to run than a "standard" one (e.g. getting data from WMI or PowerShell). So not sure how that would work with the standard command timeout.

Cheers