NetXMS Support Forum

Tested version 4.4.4 and the problem remains... Looking forward to it, thanks a lot!

Tried version 4.4.3 today and the problem persists, is it possible that I may have misconfigured it somewhere? Please advise, thank you very much!

netxms peernode shows up on wrong interface

System version: debian 11

netxms version: 4.4.1

Device Model : System Description=H3C Comware Platform Software, Software Version 7.1.070, Release 7557P03 H3C S7506E-V Copyright (c) 2004-2017 New H3C All rights reserved.

Problem:
The interface FortyGigE1/0/0/1 of the device is not in use and the status is down, but the interface shows that the peernode of this interface is juyuwang-10.61.252.221:10GE2/2/0/4, but the interface connected to juyuwang-10.61.252.221:10GE2/2/0/0/4 should be Te1/2/0/47. Try to set the snmp.driver property of the device to H3C or clear it, the problem still remains. Attached is the snmp walk result and debug 7 log, please point me in the right direction, thank you very much!

Quote from: Victor Kirhenshtein on July 14, 2023, 11:07:26 AMI 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!

Quote from: Victor Kirhenshtein on July 14, 2023, 11:07:26 AMI 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！

Quote from: Victor Kirhenshtein on May 22, 2023, 07:01:04 PMHi,
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!

Quote from: justrest on May 09, 2023, 10:37:16 AM

Quote from: Victor Kirhenshtein on May 05, 2023, 05:03:08 PMHi,
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!

Thanks very much！

Quote from: Victor Kirhenshtein on May 05, 2023, 05:03:08 PMHi,
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!

Quote from: Victor Kirhenshtein on April 26, 2023, 06:38:35 PMI've added processing of FDB record status 6 - next patch release should process them in a same way as status 3 (dynamic).
Best regards,
Victor

The problem has been solved in the just released version 4.3.6, thank you very much!

Quote from: Victor Kirhenshtein on May 05, 2023, 05:03:08 PMHi,
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！！

Quote from: Victor Kirhenshtein on April 28, 2023, 09:57:57 AMYes, 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.

Quote from: Victor Kirhenshtein on April 28, 2023, 09:57:57 AMYes, 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!

Quote from: Victor Kirhenshtein on April 12, 2023, 10:15:44 AMHi!
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!

Quote from: Victor Kirhenshtein on April 26, 2023, 06:38:35 PMI've added processing of FDB record status 6 - next patch release should process them in a same way as status 3 (dynamic).

Best regards,
Victor

thanks very much！！