NetXMS Support Forum

Hi,

Fairly new to NetXMS and running the latest version 3.8.193.  Have been running it since 3.8-ish and am just now digging into some of the layer 2 topology mapping.

We use Mikrotik switches almost exclusively and I've noticed that NetXMS can't seem to find the port a device is connected to on a Mikrotik switch.

For instance, at home I have a simple network configuration:  Mikrotik CCR Router -> ProCurve Switch -> Mikrotik CRS324 switch -> NetXMS Agent PC.

If I right-click on the Agent PC and select "Find switch port", it tells me it is "indirectly connected to Procurve Port 5".

If I right-click on the CRS324 switch and do the same.  It also tells me it is "indirectly connected to Procurve Port 5".

The topology maps also tend to be a bit goofy and I suspect whatever is causing the above, is also causing the mapping issue.

Any idea where I should start looking?  I'm running RouterOS 6.48.1 on all Mikrotik devices, and they all have a bridge configured for switching (with hardware offloading).

Thanks!

-zeb

I can't seem to get an agent to execute a web service check.  It seems fairly simple:  Define the Web Service Definition, then add it as a DCI for a specific agent, including the additional web service path (ie. webservice:/path) as the URL.

It seems to add the DCI and mark it as greent, but never does anything on the agent side if I enable debugging.

I'm using 3.7.145 on the server, 3.7.130 on the agent.

-Zeb

Is there an easy way to identify uplink ports on switching devices?  We'd like to automatically set the expected state on these interfaces to "UP" and all other ports to "IGNORE", as well as potentially add DCI automatically to these same "UP" ports.

I've started working through a server side script to add during polling, but thought I'd ask if there's an easier way I'm missing?

Thanks!

-Zeb

Everything we use we now mandate to have some sort of Multifactor authentication.  Simple TOTP would be great.  Cisco Duo integration would be even better for us, but not necessary.

I added this note to my original "Network Discovery" thread, but this is a new issue so thought I'd start a new thread!

If I enable filtering to Network Discovery, specifically in this case, turning on "Accept Node if it has NetXms Agent" and "Accept Node if it has SNMP agent":

-  Starts a ping scan.
-  Starts an SNMP scan.
-  Does not start an Agent scan.

The same happens if I only turn on "Accept Node if it has NetXms Agent" (and turn off "Accept Node if has SNMP agent").

If I set to "No filtering", it does all three scans (ping, snmp and Agent) and adds the node as expected.

Sounds like a logic problem where it won't do an Agent scan if filtering is enabled?  I'll take a look at the code, but hopefully this makes sense and can be repeated on someone else's network.

-Zeb

Hi,

I've read a few posts on how to get this to work and nothing seems to work properly for discovery of a remote network through a proxy.

I have the proxy work, and am able to manually add remote nodes, but discovery doesn't seem to happen. I've tried active and passive discovery and they appear to get queued on the proxy agent but nothing gets discovered.

Any hints on where I should start looking first?

-Zeb