NetXMS Support Forum

Hi all,

We have a network with >1000 devices. I was asked to display all node down alerts for 24 hours, and our "critical" alerts alone surpassed the amount NetXMS will put in one list (i.e., it went from 24 hours ago to 12 hours ago, instead of 24 hours to now). I assume this is a limit somewhere on number of events NetXMS will display in the event log. Since it already scrolls, is there a way we could increase this amount? We'd love to at least be able to show 24 hours of events.

Before you ask, they were generated mostly by a small set of devices that are flapping, and not because our entire network goes down on a nightly basis.

Also, how does NetXMS sort when you choose to sort by "Source?" It groups events from the same node, but otherwise seems to sort the groups arbitrarily. Is there a way I can make it sort alphabetically?

Thanks,
Zach

I noticed that like ten minutes after I posted and tried it, and it does indeed fix the scaling issue, which is great!

It's good to know there's a ticket. Thank you for letting me know!

Zach

For reference, I'm on 2.0.3 (console and server), which claims to have fixed "object selection on network maps." Not sure what that means but it hasn't solved it for me yet.

Thanks,
Zach

Hi all,

I was wondering if anyone has a fix for either of the two problems we encountered. The first is that if you right click on a network map item and choose "Object Details" it will not go to the correct object details. However, this works from the alarm browser, so I would hope someone has a fix?

The second is that if a network map is scaled at all (or on my co-worker's awful low-res display) the mouse clicks in the wrong place. I know that's probably in a lower-level library, but has anyone encountered a solution?

Thanks,
Zach

Problem solved, for those curious:

The other NetXMS engineer figured it out. Apparently, NetXMS grabs the IP address from SNMP. If there isn't one, it walks interfaces to find their IPs. However, many of our devices (Ubiquiti AirOS radios, Netonix switches) do not report these things the way NetXMS expects. When  it can't find these things, it uses SNMP availability to determine status. We only noticed on Netonix switches since they often (~1/day) drop SNMP capability.

The solution that he came up with was to write an nxshell script that loops over devices, determines if we can find an IP address on it, and if not, builds a dummy interface with the main IP address.

Hope this helps someone else!

Hi there,

Do you have a server plugged into your router? Is this a residential setup? If you're really interested in doing it with netXMS, you could add "8.8.8.8" as a node (the Google DNS server, which should never go down). Whenever that node is unreachable, you don't have internet.

As a sidenote, I'm sure there are other ways to do this that don't involve netXMS, but they might involve working with your router or some scripting, so if you're not super comfortable with that netXMS is a reasonable solution.

Hope that helps!

Hi Victor,

It appears that I am running netxmsd as root, when I run ps -aux | grep netxmsd I get the following:

root      4001 21.9  6.0 3177548 492060 ?      Ssl  May27 1388:22 /usr/bin/netxmsd -d

Which would suggest to me that it's running under root. Is there something else I should check? It's possible we have an odd firewall rule that would fight it, I'll double check that with the other engineer working on NetXMS.

Thanks again for all the help, it's much appreciated.
Zach

Hello!
Thanks for the quick response.

It's odd. The last time I walked it the switches appeared to return nothing at all, not "unknown."  I have set the interfaces to IGNORE. However, when it does not respond to SNMP, the node goes down. For example, if I check the option "stop using SNMP for all polls" in the properties tab of this node, it goes critical because it can't ping any interfaces. However, we can still ping the node from the server. We set up a ping Object Tool with the command ping -D -O -c5 -W1.2 -i1.5 %a.

You can see from my attachments what is returned in my SNMPwalk, the result of a status poll, and the result of the above ping command. Now that you mention it, it seems the ICMP poll is working differently from my ping command. The node is only down because I asked it to not use SNMP on any poll. If I uncheck that option it will go back to the unknown state. Any thoughts?

Thanks,
Zach

Hi all,

I have a set of switches that are always reported in the "UNKNOWN" state, due to some issues with snmp (they report IfOperState, not IfAdminState). Also, on random nights between 11pm-6am, the switches will stop responding to snmp. However, they're still functioning and continuing to pass ICMP ping checks.

Is there any way to force a node to only care about its ping status, not interface snmp status? Alternatively, can I force interfaces to poll IfOperState, not IfAdminState?


Thanks,
Zach

Great! That was exactly what I needed. I wrote an nxshell script to enable/disable the DCIs. It's unfortunate that I can't do it in NXSL but at least it works.

Thanks!

Hi all,

I may have missed this somewhere, but I can't set the status of a DCI to disabled from a script. Is there a specific way to do this? I'd like to disable certain interface DCIs after the configuration poll. Just trying to assign a number to the DCI->status variable results in an error.

Thanks!

Of course! That makes sense. I was wondering why it worked sometimes...

Thanks for clearing it up!

Ah, I found out my problem. It's for DCI's that are using instancing. That's a bit different I would bet. What I mean is, I'm able to have (say) a graph with in/out bits/second by using two instanced DCI's that fetch those numbers from every interface. However, if I put those DCI's on a template, I get that earlier invalid DCI ID error when I open it up on a node's data configuration.

You were right about the regular graphs, though. I'm not sure what was wrong with that last attempt, but I got templated DCI's on the same performance graph, with my version, which is definitely nice.

Are you able to graph with instanced DCI's? Or should I log a bug report and move on?

Thanks,
Zach

Good to know. You mean a snapshot of source, from here:

https://www.netxms.org/download/

right? I'll make sure to upgrade before we push to a production server. Thanks for the info!

That's heartening. What version of NetXMS / OS are you using? We have 2.0.3 on an Ubuntu 14.04 server.

Could I see a screenshot of your template DCI's performance tab? Mine is attached. I just want to be sure that I'm not doing something out of the ordinary.

Thanks for the help!