NetXMS Support Forum

Server.QueueSize.Current(NodeDiscoveryPoller) history over last 30 days is always in range 800-900. Does this indicate a resource issue on the server or do I need to increase the number of pollers somewhere?

Anyway. It still will not acquire this node, even though all the conditions appear to be right.


2022.07.01 14:12:52.785 *D* [poll.discovery     ] Starting active discovery check on range 10.127.10.3 - 10.127.10.3 (snmp=true tcp=true bs=1024 delay=0)
2022.07.01 14:12:54.291 *D* [poll.discovery     ] Active discovery - node 10.127.10.3 responded to ICMP probe
2022.07.01 14:12:54.291 *D* [poll.discovery     ] Checking address 10.127.10.3 in zone 0 (source: Active Discovery)
2022.07.01 14:12:54.292 *D* [poll.discovery     ] New node queued: 10.127.10.3/24
2022.07.01 14:12:54.292 *D* [poll.discovery     ] Starting SNMP check on range 10.127.10.3 - 10.127.10.3
2022.07.01 14:12:54.293 *D* [poll.discovery     ] NodePoller: processing address 10.127.10.3/24 in zone 0 (source type Active Discovery, source node [0])
2022.07.01 14:12:55.806 *D* [poll.discovery     ] Active discovery - node 10.127.10.3 responded to SNMP probe
2022.07.01 14:12:55.806 *D* [poll.discovery     ] Checking address 10.127.10.3 in zone 0 (source: Active Discovery)
2022.07.01 14:12:55.808 *D* [poll.discovery     ] Potential node 10.127.10.3 rejected (IP address already queued for polling)
2022.07.01 14:12:57.320 *D* [poll.discovery     ] Active discovery - node 10.127.10.3 responded to SNMP probe
2022.07.01 14:12:57.320 *D* [poll.discovery     ] Checking address 10.127.10.3 in zone 0 (source: Active Discovery)
2022.07.01 14:12:57.321 *D* [poll.discovery     ] Potential node 10.127.10.3 rejected (IP address already queued for polling)
2022.07.01 14:13:04.879 *D* [poll.discovery     ] Starting TCP check on range 10.127.10.3 - 10.127.10.3
2022.07.01 14:13:04.968 *D* [poll.discovery     ] Finished active discovery check on range 10.127.14.3 - 10.127.10.3



'show queues':
Node discovery poller            : 887

So is that 887 nodes waiting to be added?

It doesn't seem to like a /32 netmask for this purpose. I get no error in the GUI when adding and scanning a test discovery target with a /32 but this is logged:


2022.07.01 14:00:08.686 *D* [poll.discovery     ] Invalid address range 10.127.10.3/32


[Yes, "Subnet" is ticked and not "Address range"].
Changed it to a range of one IP address and the discovery runs as expected.

The active discovery interval is 1800s, passive is 900s. I last made any changes to NetXMS around 18:00 then posted here. 04:48 the next day, it's discovered.

2022.06.17 04:48:44.046 *D* [event.proc         ] EVENT SYS_NODE_ADDED [1] at {0} (ID:12649088 F:0x0001 S:0 TAGS:"NewObjects") FROM SW6: Node added
2022.06.17 04:48:44.046 *D* [                   ] Name for node 118685 was resolved to SW6
2022.06.17 04:48:44.046 *D* [poll.conf          ] ConfPoll(SW6 [118685]): node name resolved


Doesn't make any sense! Similar story [probably] with the other switch on site that wasn't discovering, but in that case because I increased the log level my logs only go back to 0200 and it seems to have been added before then.
Version is 4.1.377

Currently have debug level on 5.
Have a /24 subnet with multiple nodes that NetXMS has discovered previously. Two new hosts were added to this network but I just cannot get NetXMS to discover them automatically.
"Active discovery - node 172.22.141.37 responded to ICMP probe via proxy" is logged but that's it, it doesn't log that it took any further action on that specific IP.
If I add the node manually it works instantly, ie, the host is configured with the correct SNMP community.
"Starting SNMP check on range" is logged for the IP range that covers that host, but that's it.
It also mentions that it knows this host from another node's ARP cache.

https://github.com/netxms/netxms/blob/master/src/flow-collector/nxflowd/nxflowd.h

Looks like it? But has been there perhaps since 2009, maybe?

Yes, the VLANs are reported against the switchports correctly with both GENERIC and CISCO-SB driver [here I am discussing CBS350-24FP-4X].
The "Location" field is no longer populated once switching to CISCO-SB. I think this is not a problem, with GENERIC it shows the location as "0/1/0/29" for interface te1/0/1, I am not sure that location is correct.

The driver is detected as GENERIC and the Node type is Unknown.
But...it actually does an OK job anyway as GENERIC as it finds the name/version/Serial, so I think this is really just a cosmetic issue.
I have overridden the driver with the CISCO-SB one and done a configuration (full) poll.

Not at this time unfortunately as they belong to customers and are deployed on customer sites. When I get one in my hands I will provide access.

Cisco CBS series switches are the successor to the Cisco Small Business series switches.
I think it would probably make sense to use CISCO-SB driver for these switches.
Do you want some snmpwalk output or similar to help add support for these switches to the CISCO-SB driver?

Great work, Victor.
Added snmp.ignore.ipAddressTable as custom param on this example Sonicwall, re-polled and it now shows the correct IPs after a "Configuration (full)" poll.

OK, Unifi APs don't support this MIB.

If I check "include end nodes" in an L2 map, I get printers and APs.
In my opinion, printers are definitely end nodes and switches are definitely not.
What about APs? I reckon in the context of an L2 map that an AP is not an end node - it provides a L2 connectivity to wireless clients.
How does NetXMS determine what an end node is?

Yes, they do:


RFC1213-MIB::ipAdEntAddr.88.xx.xx.142 = IpAddress: 88.xx.xx.142
RFC1213-MIB::ipAdEntAddr.94.xx.xx.34 = IpAddress: 94.xx.xx.34
RFC1213-MIB::ipAdEntAddr.172.22.40.1 = IpAddress: 172.22.40.1
RFC1213-MIB::ipAdEntAddr.172.22.140.1 = IpAddress: 172.22.140.1
RFC1213-MIB::ipAdEntAddr.172.22.240.1 = IpAddress: 172.22.240.1



Address Map is a useful tool but I think a few things could enhance it:

• Some way of representing DHCP scopes. I guess this would just be a parameter on the "Subnet" Object class rather than a dummy host that has 50 IP addresses
• Populate it from ARP cache as well
• Colour the above two things with different colours or symbols to distinguish how "true" they might be
• Tooltip when hovering over an IP if it's a known node, click on it to jump to it, etc
• Right click on a "free" IP with option to ping from an agent if there is one in that network with ICMP subagent, and report back if IP was free and no ARP response seen