Replies: 1 comment 2 replies
-
Most likely causes are browser to API authentication, or a problem with interface naming. If your Netbox interface is called "100GE1/0/1", but the response from the Huawei is different, then it can't find a matching row in the table to update. LLDP results for unknown interfaces are unfortunately thrown away. However your example seems to show it's correct. Try opening your browser's developer tools, and seeing what happens when you switch to the LLDP Neighbors tab.
The second - see above. The first URL displays the HTML with the database-derived table of interfaces. The second is called from Javascript to update the table with LLDP neighbor information. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,

please help to tshoot Netbox empty lldp neighbor tab for Huawei switch. I'm using napalm-ce module.
When I exec GET to Netbox API I'm receiving switch LLDP neighbors(/napalm/?method=get_lldp_neighbors).
{ "get_lldp_neighbors": { "100GE1/0/1": [ { "port": "100GE1/0/1", "hostname": "tas-ldc-leaf-sw-01" } ], "100GE1/0/2": [ { "port": "100GE1/0/2", "hostname": "tas-ldc-leaf-sw-01" } ] } }
But in netbox device tab is empty:
Interface names are matching. What I'm doing wrong?
Also, what method Netbox uses for this tab - get_lldp_neighbors_detail or get_lldp_neighbors ?
Beta Was this translation helpful? Give feedback.
All reactions