NetXMS Forum

Hi, does Mikrotik switch support LLDP (that should allow NetXMS server to find connection between ProCurve and Mikrotik). DOes NetXMS server see correct FDB on Mikrotik switch? You can check that by right-click on it, and select Topology -> Forwarding database. What is output f manual topology poll for both ProCurve and Mikrotik? Best regards, Victor

For Debuan/Ubuntu the best practice is to install and upgrade by means of OS package manager (apt / apt-get). There are tools to automate deployment of packages like Puppet, Chef, etc. Installing using apt and upgrading from NetXMS Package Manager should not be done - location of binary/configuration/log file could be different and there'll be mess on the target system.

Just in case, it's possible to read port forwarding database from NXSL - it's available in Topology.SwitchForwardingDatabase internal table. There's no access to L3 routing information yet, but it's planned to add https://track.radensolutions.com/issue/NX-1999

Depending on your setup, you may already be able to utilise MFA via RADIUS authentication, for example syncing users into NetXMS via LDAP with RADIUS auth against an NPS server which talks to AzureAD for MFA.

Thanks Filipp! If you need any additional details or a guinea pig for testing, just let me know. We're really starting to get deep into NetXMS and the more we use it, the more we're amazed.  Great work.

Thanks to Victor's help, all this required was some tuning on the NetXMS server.  Turning on parallel processing and increasing the Discovery.BaseSize from 1 to 8 seems to have helped immensely.  The root cause seems to be the large number of subnets we had on our Default zone.  It couldn't keep up with the discovery process for subsequent zones. I am now having an issue with discovery filters.  We want to only add devices that have SNMP enabled or the Agent installed.  However, when we turn these filters on in 3.7.116, nothing gets added.  If I restrict it to active scan only on a single test IP, and then turn off all filters, the device with agent gets added as expected. If I check debug logs on the proxy agent, it does ping the device but never seems to try to connect via SNMP or Agent. What it looks like is that if the filter is set to SNMP or Agent only, it only attempts a ping scan and since it hasn't seen it so far as an SNMP or Agent device, it doesn't bother scanning (a Catch 22). -Zeb