<![CDATA[How to discover all peer nodes completely?]]>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!

]]>https://forum.netxms.org/topic/7645/how-to-discover-all-peer-nodes-completelyRSS for NodeFri, 13 Nov 2026 08:23:56 GMTThu, 16 Mar 2023 07:32:16 GMT60<![CDATA[Reply to How to discover all peer nodes completely? on Wed, 19 Jul 2023 05:12:46 GMT]]>@victor said in How to discover all peer nodes completely?:

I have made some changes in reading LLDP information in upcoming release 4.4.1. FIrst of all there were few bugs left in reading LLDP-V2 MIB. Also, now server will use both LLDP-MIB and LLDP-V2-MIB if supported by device, and LLDP-MIB takes precedence. This should solve discovery issues.

Best regards,
Victor

We've updated to version 4.4.1 and it looks like H3C's Neighborhood Discovery feature should be working fine, fantastic, thanks so much!

]]>https://forum.netxms.org/post/32601https://forum.netxms.org/post/32601Wed, 19 Jul 2023 05:12:46 GMT<![CDATA[Reply to How to discover all peer nodes completely? on Mon, 17 Jul 2023 03:00:34 GMT]]>@victor said in How to discover all peer nodes completely?:

I have made some changes in reading LLDP information in upcoming release 4.4.1. FIrst of all there were few bugs left in reading LLDP-V2 MIB. Also, now server will use both LLDP-MIB and LLDP-V2-MIB if supported by device, and LLDP-MIB takes precedence. This should solve discovery issues.

Best regards,
Victor

Thank you very much！

]]>https://forum.netxms.org/post/32589https://forum.netxms.org/post/32589Mon, 17 Jul 2023 03:00:34 GMT<![CDATA[Reply to How to discover all peer nodes completely? on Fri, 14 Jul 2023 08:07:26 GMT]]>I have made some changes in reading LLDP information in upcoming release 4.4.1. FIrst of all there were few bugs left in reading LLDP-V2 MIB. Also, now server will use both LLDP-MIB and LLDP-V2-MIB if supported by device, and LLDP-MIB takes precedence. This should solve discovery issues.

Best regards,
Victor

]]>https://forum.netxms.org/post/32581https://forum.netxms.org/post/32581Fri, 14 Jul 2023 08:07:26 GMT<![CDATA[Reply to How to discover all peer nodes completely? on Tue, 11 Jul 2023 00:15:14 GMT]]>@victor said in How to discover all peer nodes completely?:

Hi,
I was able to reproduce and fix this issue (yet another bug in LLDPv2 MIB handling). Fix will be included into next patch release (we likely will publish it this week).
Best regards,
Victor

Since under 4.2.* version, all peer nodes can be discovered normally, and the topology is shown completely (more than 30 nodes), but after 4.3 version can only discover part of the nodes (about 7 nodes), and as the time becomes longer, only two nodes are left at last,  is  it possible to turn off the LLDP V2, and revert back to the recognition mechanism of 4.2.* version, or there is any way to solve the problem. Thank you very much!

]]>https://forum.netxms.org/post/32569https://forum.netxms.org/post/32569Tue, 11 Jul 2023 00:15:14 GMT<![CDATA[Reply to How to discover all peer nodes completely? on Fri, 30 Jun 2023 04:51:19 GMT]]>@justrest said in How to discover all peer nodes completely?:

@victor said in How to discover all peer nodes completely?:

Hi,
I've found a bug introduced in 4.3 which may cause incorrect decoding of strings received via SNMP (SNMP codepage was ignored in some cases). Fix will be included into upcoming patch release 4.3.6.
Best regards,
Victor

I'm very excited to try the just released version 4.3.6, but the network device still can't seem to discover all neighboring devices ...... I uploaded the latest walk result of SNMP, please help me to see it, thank you very much!

Thank you so much for your great help! I tried the latest version 4.3.7 today and the problem with lldp v2 still seems to exist, please help me with the attached logs, much appreciated! Or is it possible to force the use of lldp v1 version? Looking forward to your reply!

]]>https://forum.netxms.org/post/32478https://forum.netxms.org/post/32478Fri, 30 Jun 2023 04:51:19 GMT<![CDATA[Reply to How to discover all peer nodes completely? on Tue, 23 May 2023 02:17:23 GMT]]>Thanks very much！

]]>https://forum.netxms.org/post/32473https://forum.netxms.org/post/32473Tue, 23 May 2023 02:17:23 GMT<![CDATA[Reply to How to discover all peer nodes completely? on Mon, 22 May 2023 16:01:04 GMT]]>Hi,

I was able to reproduce and fix this issue (yet another bug in LLDPv2 MIB handling). Fix will be included into next patch release (we likely will publish it this week).

Best regards,
Victor

]]>https://forum.netxms.org/post/32471https://forum.netxms.org/post/32471Mon, 22 May 2023 16:01:04 GMT<![CDATA[Reply to How to discover all peer nodes completely? on Tue, 09 May 2023 07:59:52 GMT]]>Could you also provide server log file with debug level 6 for the duration of topology poll on that switch (i.e. set debug level to 6, go to Poll -> Topology on the switch node, set debug back)?

]]>https://forum.netxms.org/post/32438https://forum.netxms.org/post/32438Tue, 09 May 2023 07:59:52 GMT<![CDATA[Reply to How to discover all peer nodes completely? on Sat, 17 Jun 2023 01:48:24 GMT]]>@victor said in How to discover all peer nodes completely?:

Hi,
I've found a bug introduced in 4.3 which may cause incorrect decoding of strings received via SNMP (SNMP codepage was ignored in some cases). Fix will be included into upcoming patch release 4.3.6.
Best regards,
Victor

I'm very excited to try the just released version 4.3.6, but the network device still can't seem to discover all neighboring devices ...... I uploaded the latest walk result of SNMP, please help me to see it, thank you very much!

]]>https://forum.netxms.org/post/32437https://forum.netxms.org/post/32437Sat, 17 Jun 2023 01:48:24 GMT<![CDATA[Reply to How to discover all peer nodes completely? on Sat, 06 May 2023 00:43:42 GMT]]>@victor said in How to discover all peer nodes completely?:

Hi,
I've found a bug introduced in 4.3 which may cause incorrect decoding of strings received via SNMP (SNMP codepage was ignored in some cases). Fix will be included into upcoming patch release 4.3.6.
Best regards,
Victor

thanks very much！！

]]>https://forum.netxms.org/post/32430https://forum.netxms.org/post/32430Sat, 06 May 2023 00:43:42 GMT<![CDATA[Reply to How to discover all peer nodes completely? on Fri, 05 May 2023 14:03:08 GMT]]>Hi,

I've found a bug introduced in 4.3 which may cause incorrect decoding of strings received via SNMP (SNMP codepage was ignored in some cases). Fix will be included into upcoming patch release 4.3.6.

Best regards,
Victor

]]>https://forum.netxms.org/post/32429https://forum.netxms.org/post/32429Fri, 05 May 2023 14:03:08 GMT<![CDATA[Reply to How to discover all peer nodes completely? on Tue, 02 May 2023 03:25:27 GMT]]>@victor said in How to discover all peer nodes completely?:

Yes, it actually could be related to codepage. Depending on entry type, NetXMS server may require to search for peers using texts (interface descriptions for example), and if it is received incorrectly search will fail. To be able to diagnose it I likely will need exact walk outputs though. We can move discussion to private messages or Telegram if you don't like to share such data publicly.
Best regards,
Victor

Currently the server configuration file netxmsd.conf as well as snmp.codepage and syslog.codepage are CP936, except that previously under version 4.2.461, the same configuration did not have this problem.

]]>https://forum.netxms.org/post/32421https://forum.netxms.org/post/32421Tue, 02 May 2023 03:25:27 GMT<![CDATA[Reply to How to discover all peer nodes completely? on Sat, 06 May 2023 00:44:31 GMT]]>@victor said in How to discover all peer nodes completely?:

Yes, it actually could be related to codepage. Depending on entry type, NetXMS server may require to search for peers using texts (interface descriptions for example), and if it is received incorrectly search will fail. To be able to diagnose it I likely will need exact walk outputs though. We can move discussion to private messages or Telegram if you don't like to share such data publicly.
Best regards,
Victor

No, actually none of this information is considered private, it just seems like too much. Thank you very much for your reply, I've uploaded the relevant attachments, so please take the trouble to guide me, thank you very much!

]]>https://forum.netxms.org/post/32420https://forum.netxms.org/post/32420Sat, 06 May 2023 00:44:31 GMT<![CDATA[Reply to How to discover all peer nodes completely? on Fri, 28 Apr 2023 10:02:12 GMT]]>I don't want to hijack a thread, but for example, Cisco C9200L-24P-4X switch peer discovery doesn't work 100%. Only other Cisco switches are discovered, but no other device directly connected to the switch. It broke with a newer version of NetXms, but I don't remember which version exactly.

]]>https://forum.netxms.org/post/32414https://forum.netxms.org/post/32414Fri, 28 Apr 2023 10:02:12 GMT<![CDATA[Reply to How to discover all peer nodes completely? on Fri, 28 Apr 2023 06:57:57 GMT]]>Yes, it actually could be related to codepage. Depending on entry type, NetXMS server may require to search for peers using texts (interface descriptions for example), and if it is received incorrectly search will fail. To be able to diagnose it I likely will need exact walk outputs though. We can move discussion to private messages or Telegram if you don't like to share such data publicly.

Best regards,
Victor

]]>https://forum.netxms.org/post/32412https://forum.netxms.org/post/32412Fri, 28 Apr 2023 06:57:57 GMT<![CDATA[Reply to How to discover all peer nodes completely? on Fri, 28 Apr 2023 00:20:06 GMT]]>@victor said in How to discover all peer nodes completely?:

Hi!
It could be related to LLDPv2 MIB support that we have added in 4.3. Could you please check if device responds to OID .1.3.111.2.802.1.1.13.1.3.2.0? If yes, could you provide result of SNMP walk on .1.3.111.2.802.1.1.13.1.4.1.1 and .1.0.8802.1.1.2.1.4.1.1?
Best regards,
Victor

Thank you very much for developing such an excellent network management software, could you please help to optimize the new version of LLDP protocol support, thank you very much!

]]>https://forum.netxms.org/post/32411https://forum.netxms.org/post/32411Fri, 28 Apr 2023 00:20:06 GMT<![CDATA[Reply to How to discover all peer nodes completely? on Tue, 18 Apr 2023 06:13:21 GMT]]>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?

]]>https://forum.netxms.org/post/32376https://forum.netxms.org/post/32376Tue, 18 Apr 2023 06:13:21 GMT<![CDATA[Reply to How to discover all peer nodes completely? on Wed, 12 Apr 2023 07:15:44 GMT]]>Hi!

It could be related to LLDPv2 MIB support that we have added in 4.3. Could you please check if device responds to OID .1.3.111.2.802.1.1.13.1.3.2.0? If yes, could you provide result of SNMP walk on .1.3.111.2.802.1.1.13.1.4.1.1 and .1.0.8802.1.1.2.1.4.1.1?

Best regards,
Victor

]]>https://forum.netxms.org/post/32366https://forum.netxms.org/post/32366Wed, 12 Apr 2023 07:15:44 GMT<![CDATA[Reply to How to discover all peer nodes completely? on Sun, 19 Mar 2023 00:31:03 GMT]]>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.

]]>https://forum.netxms.org/post/32334https://forum.netxms.org/post/32334Sun, 19 Mar 2023 00:31:03 GMT<![CDATA[Reply to How to discover all peer nodes completely? on Sat, 17 Jun 2023 01:49:47 GMT]]>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!

]]>https://forum.netxms.org/post/32330https://forum.netxms.org/post/32330Sat, 17 Jun 2023 01:49:47 GMT<![CDATA[Reply to How to discover all peer nodes completely? on Fri, 17 Mar 2023 00:49:59 GMT]]>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]

]]>https://forum.netxms.org/post/32325https://forum.netxms.org/post/32325Fri, 17 Mar 2023 00:49:59 GMT<![CDATA[Reply to How to discover all peer nodes completely? on Thu, 16 Mar 2023 07:48:08 GMT]]>version 4.3.2 ,debian 11

]]>https://forum.netxms.org/post/32324https://forum.netxms.org/post/32324Thu, 16 Mar 2023 07:48:08 GMT