NetXMS Support Forum

Thank you very much for your reply! 

I'm on a business trip and can't import the list, but I had a colleague try and the SNMP walk results for .1.3.111.2.802.1.1.13.1.4.1.1 and .1.0.8802.1.1.1.2.1.4.1.1 seems containing  all the neighbor information, just some information that shows up as garbled. The current codepage setting of snmp is CP936 (Chinese), could this problem be related to the codepage setting?

When the port opens the security policy, the port's mac address status will change from "learned" to "secure", which seems to be the official definition, but I don't know why it can't be learned by netxms。
Thanks for your replies!

I tried different versions from 4.2.461 to 4.3.2, both windows and debian systems. The result is that 4.2.461 does not have the above problem, 4.3.0-4.3.2 are unable to get the complete peer node list.

I have tried different versions from 4.2.461 to 4.3.2, including windows and debian systems, and found the same result.

We need to locate the IP or mac address quickly, but if we configure a port security policy on the switch interface (as shown in the figure), the mac address status on the switch is "secure" instead of "learned". The problem is that netxms only learns the mac address of the "learned" state ( Switch Forwarding Database  ), the mac address of the "security" state seems to be ignored, please ask what is the way to learn all the mac addresses, thank you very much!

I compared the nodes with normal and abnormal LLDP discovery and found that the difference is whether the VLAN list can be obtained during topology discovery. To test, I installed a new netxms, added only test node, and set the value of custom attribute " snmp.driver " to "H3C". Although SNMP can get vlan information normally through either public OID or private OID of H3C, the topology discovery still prompts: unable to get vlan list, and there is no more information in the debug 5 log.

Very eager for your help, thank you!

2023.03.16 15:21:07.881 *D* [poll.topology      ] Started topology poll of node SW-HJ[241]
2023.03.16 15:21:07.942 *D* [poll.topology      ] Cannot retrieve VLAN list from node SW-HJ[241]
2023.03.16 15:21:10.998 *D* [topology.fdb      ] GetSwitchForwardingDatabase(SW-HJ[241]): 76 entries read from dot1qTpFdbTable
2023.03.16 15:21:11.001 *D* [topology.fdb      ] GetSwitchForwardingDatabase(SW-HJ[241]): 0 entries read from dot1dTpFdbTable
2023.03.16 15:21:11.002 *D* [poll.topology      ] Switch forwarding database retrieved for node SW-HJ[241]
2023.03.16 15:21:11.002 *D* [topology.lldp      ] Collecting LLDP topology information for node SW-HJ[241]
2023.03.16 15:21:25.630 *D* [topology.lldp      ] 550 entries in LLDP connection database for node SW-HJ[241]
2023.03.16 15:21:25.631 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID D494E8582820
2023.03.16 15:21:25.631 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 000E5EB9CF4F
2023.03.16 15:21:25.631 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 441AFACF4400
2023.03.16 15:21:25.631 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 441AFACF4400
2023.03.16 15:21:25.631 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 441AFACF4400
2023.03.16 15:21:25.631 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 441AFACF4400
2023.03.16 15:21:25.631 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID D494E8582820
2023.03.16 15:21:25.631 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 441AFACF9A00
2023.03.16 15:21:25.631 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 9CE895D9F420
2023.03.16 15:21:25.631 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID D494E8582820
2023.03.16 15:21:25.631 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID D494E8582820
2023.03.16 15:21:25.631 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 9CE895DA0B40
2023.03.16 15:21:25.631 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 9CE895DA0B40
2023.03.16 15:21:25.632 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 9CE895D9F420
2023.03.16 15:21:25.632 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 90E710C7DA68
2023.03.16 15:21:25.632 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 000E5EB9CF51
2023.03.16 15:21:25.632 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 74258ABEAA4D
2023.03.16 15:21:25.632 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 90E710C7C0A0
2023.03.16 15:21:25.632 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 90E710C7C0A0
2023.03.16 15:21:25.632 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 90E710C789A0
2023.03.16 15:21:25.632 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 3897D6B7DF24
2023.03.16 15:21:25.632 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 9CE895DA1A40
2023.03.16 15:21:25.632 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 441AFACF4200
2023.03.16 15:21:25.632 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 441AFACF4200
2023.03.16 15:21:25.632 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 7485C436A73C
2023.03.16 15:21:25.632 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 5CC999FFEEC3
2023.03.16 15:21:25.632 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 586AB153E7F6
2023.03.16 15:21:25.632 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 90E710C7F220
2023.03.16 15:21:25.632 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID B0F9634FA800
2023.03.16 15:21:25.632 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 703D155488DC
2023.03.16 15:21:25.632 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 48BD3D3B64F6
2023.03.16 15:21:25.632 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 703D155464EC
2023.03.16 15:21:25.633 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 70BAEFA16213
2023.03.16 15:21:25.633 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 441AFACF9600
2023.03.16 15:21:25.633 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 441AFACF9600
2023.03.16 15:21:25.633 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 9CE895DA0550
2023.03.16 15:21:25.633 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 04D7A51DF26A
2023.03.16 15:21:25.633 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 3897D6B7DF24
2023.03.16 15:21:25.633 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 9CE895DA1A40
2023.03.16 15:21:25.633 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 9CE895DA1A90
2023.03.16 15:21:25.633 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 90E710C7DA68
2023.03.16 15:21:25.633 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 9CE895D9F970
2023.03.16 15:21:25.633 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 5CC999FFEEC3
2023.03.16 15:21:25.633 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID B0F9634FA800
2023.03.16 15:21:25.633 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 90E710C79C30
2023.03.16 15:21:25.633 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 9CE895D9F330
2023.03.16 15:21:25.633 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 74258A14CE9F
2023.03.16 15:21:25.633 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 441AFACF9A00
2023.03.16 15:21:25.633 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID B0F9634BE400
2023.03.16 15:21:25.633 *D* [topology.lldp      ] ProcessLLDPConnectionEntry(SW-HJ[241]): SNMP get failed for remote ID 9CE895D9F330
2023.03.16 15:21:25.633 *D* [topology.lldp      ] Finished collecting LLDP topology information for node SW-HJ[241]
2023.03.16 15:21:25.634 *D* [topology.stp      ] Collecting STP topology information for node SW-HJ[241]
2023.03.16 15:21:26.248 *D* [topology.stp      ] Finished collecting STP topology information for node SW-HJ[241]
2023.03.16 15:21:26.248 *D* [poll.topology      ] Node::addHostConnections(SW-HJ[241]): FDB retrieved
2023.03.16 15:21:26.249 *D* [poll.topology      ] Link layer topology retrieved for node SW-HJ[241] (7 connections found)
2023.03.16 15:21:26.249 *D* [poll.topology      ] Link layer topology processed for node SW-HJ[241]

version 4.3.2 ,debian 11

Take an aggregation device as an example, it is down-connected to dozens of devices, all of which have LLDP and SNMP working normal and have added nodes in netxms, but regardless of the peer node column in the NIC list or in the network topology, only part of peer nodes can be found, and the debug log shows: ProcessLLDPConnectionEntry( :SNMP get failed for remote ID D494E8582820). Your help is urgently needed, thank you very much!

Why are the epel and fedora sources not updated to the latest 4.3.2 version, thank you very much! Also, there seems to be a peer node recognition problem in 4.3.1, for example, aggregated devices can only recognize individual downlinked devices, while in the previous version 4.3.0 they could be fully recognized.

In centos8.5 system, it is prompted that netxms cannot be installed because of the missing "libjansson.so.4", but the file does exist, please ask the experts to guide, thank you very much!

 Thanks very much,  I will try again！

NetXMS Server Remote Console V4.3.1 Ready
Enter "help" for command list

netxmsd: show stat
Objects............: 28053
Monitored nodes....: 557
Collectible DCIs...: 783
Active alarms......: 0
Uptime.............: 0 days,  0:07:58

netxmsd: show q
Data collector                  : 0
DCI cache loader                : 0
Template updater                : 0
Database writer                  : 0
Database writer (IData)          : 0
Database writer (raw DCI values) : 17
Event processor                  : 0
Event log writer                : 0
Poller                          : 0
Node discovery poller            : 0
Syslog processor                : 0
Syslog writer                    : 0
Scheduler                        : 0
Windows event processor          : 0
Windows event writer            : 0

netxmsd: sh thr
MAIN
  Threads.............. 24 (24/768)
  Load average......... 0.00 0.01 0.00
  Current load......... 0%
  Usage................ 3%
  Active requests...... 0
  Scheduled requests... 1
  Total requests....... 27
  Thread starts........ 0
  Thread stops......... 0
  Wait time EMA........ 0 ms
  Wait time SMA........ 0 ms
  Wait time SD......... 0 ms
  Queue size EMA....... 0
  Queue size SMA....... 0
  Queue size SD........ 0

AGENT
  Threads.............. 32 (32/256)
  Load average......... 0.00 0.00 0.00
  Current load......... 0%
  Usage................ 12%
  Active requests...... 0
  Scheduled requests... 0
  Total requests....... 2475
  Thread starts........ 0
  Thread stops......... 0
  Wait time EMA........ 0 ms
  Wait time SMA........ 0 ms
  Wait time SD......... 0 ms
  Queue size EMA....... 0
  Queue size SMA....... 0
  Queue size SD........ 0

NPE
  Threads.............. 1 (1/1024)
  Load average......... 0.00 0.00 0.00
  Current load......... 0%
  Usage................ 0%
  Active requests...... 0
  Scheduled requests... 0
  Total requests....... 0
  Thread starts........ 0
  Thread stops......... 0
  Wait time EMA........ 0 ms
  Wait time SMA........ 0 ms
  Wait time SD......... 0 ms
  Queue size EMA....... 0
  Queue size SMA....... 0
  Queue size SD........ 0

DATACOLL
  Threads.............. 30 (30/750)
  Load average......... 0.05 0.10 0.04
  Current load......... 0%
  Usage................ 4%
  Active requests...... 0
  Scheduled requests... 0
  Total requests....... 6136
  Thread starts........ 0
  Thread stops......... 0
  Wait time EMA........ 0 ms
  Wait time SMA........ 0 ms
  Wait time SD......... 0 ms
  Queue size EMA....... 0
  Queue size SMA....... 0
  Queue size SD........ 0

CLIENT
  Threads.............. 16 (16/2048)
  Load average......... 0.00 0.00 0.00
  Current load......... 0%
  Usage................ 0%
  Active requests...... 0
  Scheduled requests... 0
  Total requests....... 2213
  Thread starts........ 0
  Thread stops......... 0
  Wait time EMA........ 0 ms
  Wait time SMA........ 0 ms
  Wait time SD......... 1 ms
  Queue size EMA....... 0
  Queue size SMA....... 0
  Queue size SD........ 0

SYNCER
  Threads.............. 11 (10/100)
  Load average......... 0.00 0.00 0.00
  Current load......... 0%
  Usage................ 11%
  Active requests...... 0
  Scheduled requests... 0
  Total requests....... 2646
  Thread starts........ 1
  Thread stops......... 0
  Wait time EMA........ 83 ms
  Wait time SMA........ 39 ms
  Wait time SD......... 24 ms
  Queue size EMA....... 0
  Queue size SMA....... 0
  Queue size SD........ 0

DISCOVERY
  Threads.............. 192 (24/192)
  Load average......... 415.48 1596.52 946.05
  Current load......... 0%
  Usage................ 100%
  Active requests...... 0
  Scheduled requests... 0
  Total requests....... 5511
  Thread starts........ 168
  Thread stops......... 0
  Wait time EMA........ 242677 ms
  Wait time SMA........ 0 ms
  Wait time SD......... 0 ms
  Queue size EMA....... 904
  Queue size SMA....... 0
  Queue size SD........ 0

POLLERS
  Threads.............. 63 (30/750)
  Load average......... 2.76 36.67 29.92
  Current load......... 0%
  Usage................ 8%
  Active requests...... 0
  Scheduled requests... 0
  Total requests....... 10282
  Thread starts........ 33
  Thread stops......... 0
  Wait time EMA........ 104 ms
  Wait time SMA........ 84 ms
  Wait time SD......... 226 ms
  Queue size EMA....... 26
  Queue size SMA....... 0
  Queue size SD........ 0

SCHEDULER
  Threads.............. 3 (3/192)
  Load average......... 0.00 0.00 0.00
  Current load......... 0%
  Usage................ 1%
  Active requests...... 0
  Scheduled requests... 1
  Total requests....... 2
  Thread starts........ 0
  Thread stops......... 0
  Wait time EMA........ 0 ms
  Wait time SMA........ 0 ms
  Wait time SD......... 0 ms
  Queue size EMA....... 0
  Queue size SMA....... 0
  Queue size SD........ 0

MOBILE
  Threads.............. 4 (4/256)
  Load average......... 0.00 0.00 0.00
  Current load......... 0%
  Usage................ 1%
  Active requests...... 0
  Scheduled requests... 0
  Total requests....... 0
  Thread starts........ 0
  Thread stops......... 0
  Wait time EMA........ 0 ms
  Wait time SMA........ 0 ms
  Wait time SD......... 0 ms
  Queue size EMA....... 0
  Queue size SMA....... 0
  Queue size SD........ 0

netxmsd:  sh watc
Thread                                          Interval Status
----------------------------------------------------------------------------
Item Poller                                      10      Running
Syncer Thread                                    30      Sleeping
Poll Manager                                    5        Sleeping
Ad hoc scheduler                                5        Sleeping
Recurrent scheduler                              5        Sleeping

netxmsd: sh watchdog
Thread                                          Interval Status
----------------------------------------------------------------------------
Item Poller                                      10      Running
Syncer Thread                                    30      Sleeping
Poll Manager                                    5        Sleeping
Ad hoc scheduler                                5        Sleeping
Recurrent scheduler                              5        Sleeping

netxmsd:  sh poller
Type | Object ID | Object name                    | Status
-----+-----------+--------------------------------+--------------------------
STAT |      7292 | guangyuwang                    | child poll
ICMP |      7292 | guangyuwang                    | awaiting execution
STAT |    24835 | 5HaoXianCT                    | check SNMP
....

...
netxmsd:  show dbcp
0 database connections in use

netxmsd: show dbst
SQL query counters:
  Total .......... 571758
  SELECT ......... 309204
  Non-SELECT ..... 262554
  Long running ... 0
  Failed ......... 0
Background writer requests:
  DCI data ....... 6842
  DCI raw data ... 6842
  Others ......... 2031
netxmsd: show flags
Flags: 0x200425A001385CF1
  AF_DAEMON                              = 1
  AF_USE_SYSLOG                          = 0
  AF_PASSIVE_NETWORK_DISCOVERY          = 0
  AF_ACTIVE_NETWORK_DISCOVERY            = 0
  AF_ENABLE_8021X_STATUS_POLL            = 1
  AF_DELETE_EMPTY_SUBNETS                = 1
  AF_ENABLE_SNMP_TRAPD                  = 1
  AF_ENABLE_ZONING                      = 1
  AF_SYNC_NODE_NAMES_WITH_DNS            = 0
  AF_CHECK_TRUSTED_OBJECTS              = 0
  AF_ENABLE_NXSL_CONTAINER_FUNCTIONS    = 1
  AF_USE_FQDN_FOR_NODE_NAMES            = 1
  AF_APPLY_TO_DISABLED_DCI_FROM_TEMPLATE = 1
  AF_DEBUG_CONSOLE_DISABLED              = 0
  AF_AUTOBIND_ON_CONF_POLL              = 1
  AF_WRITE_FULL_DUMP                    = 1
  AF_RESOLVE_NODE_NAMES                  = 1
  AF_CATCH_EXCEPTIONS                    = 1
  AF_HELPDESK_LINK_ACTIVE                = 0
  AF_DB_LOCKED                          = 1
  AF_DB_CONNECTION_LOST                  = 0
  AF_NO_NETWORK_CONNECTIVITY            = 0
  AF_EVENT_STORM_DETECTED                = 0
  AF_SNMP_TRAP_DISCOVERY                = 0
  AF_TRAPS_FROM_UNMANAGED_NODES          = 0
  AF_PERFDATA_STORAGE_DRIVER_LOADED      = 0
  AF_BACKGROUND_LOG_WRITER              = 0
  AF_CASE_INSENSITIVE_LOGINS            = 0
  AF_TRAP_SOURCES_IN_ALL_ZONES          = 0
  AF_SYSLOG_DISCOVERY                    = 0
  AF_CACHE_DB_ON_STARTUP                = 1
  AF_ENABLE_NXSL_FILE_IO_FUNCTIONS      = 0
  AF_DB_SUPPORTS_MERGE                  = 1
  AF_PARALLEL_NETWORK_DISCOVERY          = 1
  AF_SINGLE_TABLE_PERF_DATA              = 0
  AF_MERGE_DUPLICATE_NODES              = 1
  AF_SYSTEMD_DAEMON                      = 0
  AF_USE_SYSTEMD_JOURNAL                = 0
  AF_COLLECT_ICMP_STATISTICS            = 1
  AF_LOG_IN_JSON_FORMAT                  = 0
  AF_LOG_TO_STDOUT                      = 0
  AF_DBWRITER_HK_INTERLOCK              = 0
  AF_LOG_ALL_SNMP_TRAPS                  = 0
  AF_ALLOW_TRAP_VARBIND_CONVERSION      = 1
  AF_TSDB_DROP_CHUNKS_V2                = 0
  AF_DISABLE_AGENT_PROBE                = 0
  AF_DISABLE_ETHERNETIP_PROBE            = 0
  AF_DISABLE_SNMP_V1_PROBE              = 0
  AF_DISABLE_SNMP_V2_PROBE              = 0
  AF_DISABLE_SNMP_V3_PROBE              = 0
  AF_DISABLE_SSH_PROBE                  = 0
  AF_SERVER_INITIALIZED                  = 1
  AF_SHUTDOWN                            = 0

When I manually disconnect a switch, the system quickly detects SNMP and ICMP errors, but then the node status becomes UNKNOWN, and then the polling of that node seems to stop, and the SYS_NODE_DOWN event cannot be generated,  the node status cannot become CRITICAL, please tell me under what circumstances the node status will become UNKNOWN and how to solve this problem, thanks a lot!

Thank you very much for the pointers!