Topology map not recognizing LLDP/IS-IS links from Huawei devices
Description
Acceptance / Success Criteria
Attachments
Activity
Mark Mahacek June 1, 2023 at 7:44 PM
Closing this as the customer has confirmed that v32 is drawing topology lines as expected.
Many thanks to for your help.
Antonio Russo June 1, 2023 at 4:48 AM
I have investigated the ISIS protocol, and I have not found any issues.
At least with the snmpwalk I have investigated there are 4 connections and these connections are all properly persisted into the database.
Antonio Russo May 31, 2023 at 7:24 PM
To be a little it explicit consider the following lines:
Consder the following snmpwali lines:
AC01.txt:.1.0.8802.1.1.2.1.4.1.1.9.1121.127.1 = STRING: "BBNVAG01H-Laboratorio"
AC01.txt:.1.0.8802.1.1.2.1.4.1.1.9.1121.128.1 = STRING: "BBNVAC02-Laboratorio"
We should persist as unique identifier the AC01 nodeid and as lldplocalportnum for the forst line 127 and the second line 128,
but the Db tells:
opennms=# select nodeid, lldplocalportnum from lldplink where nodeid= 11;
nodeid | lldplocalportnum
We are persisting the wrong index and because of the unique index
"lldplink_pk_idx" btree (nodeid, lldplocalportnum)
The second row overwrites the the first.
It is a bug bbut as I say i checke the code and I am quite sure that this has een fixed (I remeber an issue…for that)
Antonio Russo May 31, 2023 at 7:19 PM
I am going to check ISIS too!
Antonio Russo May 31, 2023 at 7:14 PM
I have investigated the problem.
I noticed this and I’m quite sure it has been fixed in Horizon 32.
It is related to the fact that we are using the wrong portid as identifier.
Consder the following snmpwali lines:
AC01.txt:.1.0.8802.1.1.2.1.4.1.1.9.1121.127.1 = STRING: "BBNVAG01H-Laboratorio"
AC01.txt:.1.0.8802.1.1.2.1.4.1.1.9.1121.128.1 = STRING: "BBNVAC02-Laboratorio"
in database there is a unique index for nodeid and portid in lldplink table.
But in horizon 31 we use the last index as portid while we should persist the before index.
Please check if this issue has been resolved in Horizon32.
Working with Horizon on a testing environment before going to production with Meridian, we are not able to get a full topology layout, which is a critical feature that our client needs to approve the final solution deployment.
We are currently working with Huawei devices (NE8000 and ATN910 models).
LLDP Remote Table Links displays information for single links, but not all of them are creating a link in the topology page.
Links that are part of a link aggregation (LAG), are not recognized as links.
Doing a snmp-walk for the OIDs listed in the Horizon topology provides results.
We tested on an internal lab using the same Horizon version, but Cisco devices, and everything works just fine.