NetXMS Support Forum

I realize that this has been brought up in the past but never really see a definitive response.  Not having a client for ios devices is really a negative as this is most of the devices in our organization.  I noticed in github there is an inactive project (2 years) but wondering if this has any hope of being resurrected?

In addition to what Filipp stated the screenshot attached does not actually match the code in the message.  You simply have return; and not return true;.  I would probably not include the return false; in an else clause either, but simply as the last statement so that anything falling through gets tagged like this. 

Thanks as always!

Yes, the access point object exists under this node.

I had cleared them all, but will as new ones pop up.  Here is one and the error message is on the wireless interface MAC.

I believe the fix NX-2073 may be overzealous or not working as expected.  Since upgrading to this release many of our Cambium ePMP devices have started reporting this on the wireless interface and there definitely is not an issue that I can determine.  If there is some information we can collect to help let us know.  Thanks as always!

The "fix" was to write a small NXSL script to delete these nodes at which point they were rediscovered and added properly. 

Currently if you bring up the server console window inside of the Management Console there is no way that I could find to copy or paste into that window.  When providing information from this it would be nice to be able to copy the text instead of having to transcribe it all.

Filipp,

Thanks for the ideas, we definitely did not have enough threads setup for discovery and restarting the server did indeed clear that queue, but it just shot back up after restart.  We have now been able to get the queue to a point where it sits near 0 but now see the issue that started us down this path.  We KNOW there is a device (well 6+ of them) that needs to be discovered but is not getting discovered.  Just going to focus on one though.  So we set debug to 6 and started an active scan of that subnet.  We end up getting:

2021.08.03 07:35:44.589 *D* [poll.discovery     ] Active discovery - node 10.0.154.19 responded to ICMP ping
2021.08.03 07:35:44.589 *D* [poll.discovery     ] Checking address 10.0.154.19 in zone 0 (source: Active Discovery)
2021.08.03 07:35:44.589 *D* [poll.discovery     ] Potential node 10.0.154.19 rejected (IP address already known at node 10.0.154.19 [29153])

From the console search by IP for that IP and it only shows that it is connected to the switch and port where it really is, but there is not a node that shows this information in the management console.  However from the server console if I run the command show objects 10.0.154.19 I can see the following:

Object ID 29153 "10.0.154.19"
    Class=Node Status=CRITICAL IsModified=0 IsDeleted=0
    Parents: <>
    Children: <>
    Last Change.....: 03.Aug.2021 07:56:29
    State flags........: 0x00000001
    Primary IP........: 10.0.154.19
    Primary Hostname...: ups.mydomain.com
    Capabilities.......: isSNMP=0 isAgent=0 isLocalMgmt=0
    SNMP ObjectId..:
    ICMP Polling......: ON
    ICMP statistics (PRI):
        RTT last....: 57 ms
        RTT min....: 56 ms
        RTT max....: 62 ms
        RTT average: 57 ms
        Packet loss...: 0

Providing this was a PAIN seeing that the Server Console window does not appear to allow copying, so hand typed it all.  So system thinks it is there, but it is NOWHERE to be found.

We are having some problems with active discovery and looked at messages that might help.  Running debug level 6 I see the nodes we are hoping to get discovered showing IP address already queued for polling.  From the server console and show queues I see the Node discovery poller with 6,370 entries and growing!  It does go down 1 or 2 once in a while, but for the most part it is going up.  Server is not loaded.   Can this be cleared and start again?  We are running the latest 3.9.156 but the issue was happening prior to that.

We just performed an nxdbmgr -d check and allowed all items to be cleaned up.  Restarted the server and immediately received a large number of these:

2021.07.30 16:27:36.329 *E* [                   ] Failed to load access point object with ID 21714 from database
2021.07.30 16:27:36.329 *E* [                   ] Inconsistent database: access point MYSSID [21715] linked to non-existent node [2371]


Seems the cleanup tool might need to expand into this and clean things up.  Thanks!

Figured out what was happening!  One node (working) was discovered with SNMP v2c and the other node (not working) v1.  Changed it to v2c and immediately they all worked!

So, collected some data and it returns:

2021.07.23 08:08:19.842 *D* [                   ] Node(MyNode)->getMetricFromSNMP(.1.3.6.1.4.1.17713.21.2.1.65.0): snmpResult=6
2021.07.23 08:08:19.843 *D* [event.corr         ] CorrelateEvent: event SYS_DCI_UNSUPPORTED id 15599447 source MyNode [23754]
2021.07.23 08:08:19.843 *D* [event.corr         ] CorrelateEvent: finished, rootId=0
2021.07.23 08:08:19.843 *D* [client.session.0   ] Sending message CMD_SET_DCI_STATUS (80 bytes)
2021.07.23 08:08:19.843 *D* [event.proc         ] EVENT SYS_DCI_UNSUPPORTED [53] at {0} (ID:15599447 F:0x0001 S:2 TAGS:"") FROM MyNode: Status of DCI 33334 (SNMP: .1.3.6.1.4.1.17713.21.2.1.65.0) changed to UNSUPPORTED

It would be great if there was a facility to allow you to debug on just one node or maybe just one DCI.  If we are looking for something and turn up the debug level (say 6 for example) it generates about 4K+ lines per second!  Not really useful to get information on a specific issue.

From the server console it is reporting V3.8-405-gdf0e338d8a.  We are collecting directly.

I tried to do what you were asking but in just the few seconds from the time I set the debug until after running the DCI poll this generated about 7K lines of debug!  Not even sure what in there I would be looking for and cannot post the log due to the need to scrub and the difficulty that would cause.  Is there some other way to get something and what specifically might we be looking for?