NetXMS Support Forum

Netxms is not able to fetch lldp neighbor from Huawei device even if huawei supports lldp protocol & its enabled in device.
<MBinternet> display lldp neighbor brief
Local Intf      Neighbor Dev            Neighbor Intf            Exptime(s)
GE0/0/1          MBInternet              ether2                    114
XGE0/0/1        TISAI_KHADAKPADA        e001-a60d-34f2            96
XGE0/0/2        Tisai_Gauripada_Kalyan  34ef-b698-0dec            117
but if we check the capability of that device in netxms it shows NO in front of LLDP.

that means that NetXMS server cannot read LLDP information via standard MIB. Server checks the following OIDs to test if LLDP MIN is supported by device:
1.0.8802.1.1.2.1.3.2.0
1.0.8802.1.1.2.1.3.6.0
1.3.111.2.802.1.1.13.1.3.2.0
You can check with any SNMP walk tool if device responds on any of those OIDs
Also, if you can provide SNMP access to test device, we can test it ourselves adn update server as necessary

At least it is not responding to the above 3 OIDs.. 
[python@mipl-srv-py ~]$  snmpwalk -v2c -c VOVICOM 192.168.98.39 1.0.8802.1.1.2.1.3.2.0
iso.0.8802.1.1.2.1.3.2.0 = No Such Object available on this agent at this OID
[python@mipl-srv-py ~]$  snmpwalk -v2c -c VOVICOM 192.168.98.39 1.0.8802.1.1.2.1.3.6.0
iso.0.8802.1.1.2.1.3.6.0 = No Such Object available on this agent at this OID
[python@mipl-srv-py ~]$  snmpwalk -v2c -c VOVICOM 192.168.98.39 1.3.111.2.802.1.1.13.1.3.2.0
SNMPv2-SMI::org.111.2.802.1.1.13.1.3.2.0 = No more variables left in this MIB View (It is past the end of the MIB tree)
[python@mipl-srv-py ~]$

Ok, so that explains.
If you can provide access to a test device, that would be great (but we would have someone who can work with it after 17-th of March). If providing access is not possible, then we would ask to perform walk for some OID branches.

Problem got resolved after putting below command in huawei switches.

snmp-agent mib-view included view-name iso
snmp-agent community read community_name mib-view view-name

thanks