NetXMS Support Forum

I like it all, and the enhanced Mikrotik support will be especially appreciated.

Really appreciate all the work that goes into this product.

Thanks to the whole team.

We recently had a switch replaced at night in a storm and all our port name aliases got reset when NetXMS polled the new switch. I was thinking there should be a way to see the old port names, but I can't find it.

Is there a place I could view the previous aliases for the switch ports?

What exactly do you mean by traffic monitoring? If you want to gather stats from the router interfaces then you can look in the forum to see if there is an existing template for your router which does what you want, or you can configure DCIs that poll the router for interface counters and track stats that way.

If you want to monitor traffic more specifically then you might need a different kind of tool. I am pretty sure there is a thread on this topic within the last couple of months or so. Try searching for netflow or ipfix.

120 pps seems awfully low to trigger a broadcast storm warning. That's only about 3Mbps of traffic if my calcs are correct.

Is that 120 number restricted to only certain kinds of packets or was there any other specifics?

3.9.280 is what I'm using atm, but I may have updated once since I had the MIB issue. I am not sure.

The MIB is here.

https://www.ui.com/downloads/firmwares/ufiber/EdgeMAX-MIB.zip

I also am seeing this behavior. I have quite a few unsupported DCI Alarms that do not resolve even after a later poll will successfully poll those same DCIs.

I was wondering if there was a way to suppress these alarms on a per DCI basis or even a per node basis? I would be fine if it just didn't generate these alarms for certain things. I don't think I would want to turn them off entirely though.

I have no experience with this particular feature, but if it were me I'd try escaping the brackets and see if that helps. I think those are special chars in some cases. This is just a hot take as I didn't check the docs or anything, but thought it was worth a try in case you haven't already thought of it.

\[   \]

I am trying to add in the MIB for EdgeMAX and when compiling I get an error.

/usr/share/netxms/mibs/UBNT-EdgeMAX-MIB.txt: ERROR 003: Parser error - syntax error in line 323

The line in question is

DISPLAY-HINT    "d-2"

If I comment out that line it compiles fine. I was unable to find an explanation when I searched for one and from what I've seen when reading up on this particular statement it looks like it should be OK. Anyone have any ideas why it would cause an error?

A restart of the server seems to have cleared the duplicate MAC alarms. So it looks like it was an artifact from some previous version somehow. Thanks.

I sent you a PM with the info. Let me know if you need any more info.

Thanks.

I've recently gotten back to working on moving our monitoring to NetXMS and am having some good success so far. One thing I haven't been able to figure out so far is the Duplicate MAC issue. I have quite a few Mikrotik routers with vlans, tunnels, and bridges on them. NetXMS gives Duplicate MAC address alarms for interfaces that have vlans and also tunnel interfaces in a bridge. I don't think this is an actual problem network wise I think it's just an issue with NetXMS determines what is a duplicate MAC.

I'm running version 3.9.235. Should this have been fixed by the update mentioned in the changelog or am I making a mistake that could be fixed with a config change of some sort?

TIA

I'm glad you posted this. Helped me figure out why I couldn't get my performance tab working the way I wanted. I guess it must be this way for historical reasons or something, but it wasn't what I expected based on what was working in other parts of my DCI configuration.

I'm using an older MBP with 10.15.7 so no retina resolution or anything too special. I can't run Big Sur on this laptop so no way to test if the OS makes a difference.

Some of the icons in the Mac client are showing up with a thick black border and look damaged. This is happening in the latest client version (3.8.262) but I think started around 3.7.150 maybe. I'm not entirely sure though.

Is this a problem with the build or is it just me? Anyone else seeing this?

The Mac OS X client linked on the download page doesn't seem to exist. I did find the 3.7.92 version in the older release directory, but it has a path problem on launch. I was able to fix that with a symlink in the lib directory back to itself, so it seems that should be an easy fix for the current version when it's uploaded if it's not already fixed.

cd /Applications/NetXMS Console.app/Contents/jre/zulu-15.jre/Contents/Home/lib
ln -s . jli

Thanks for all the hard work and Happy New Year!