starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

LLDP Neighbour portmap broken since Netbox 2.6.7 #2989

New Issue
Closed
opened 2025-12-29 18:24:28 +01:00 by adam · 4 comments
adam commented 2025-12-29 18:24:28 +01:00
Owner
Copy Link

Originally created by @garnser on GitHub (Nov 2, 2019).

Environment

  • Python version: 3.6.8
  • NetBox version: 2.6.7
  • Arista EOS

Steps to Reproduce

  1. Go into the LLDP Neighbour Tab of a DCIM with LLDP configured
  2. Look at the port-map table

Expected Behavior

Expected and previous behaviour is that LLDP port-mapping retreived from the switch was populated in the table.

Observed Behavior

Although the Napalm is still function (retreiving config works for example). Netbox is no longer populating the port-map table based on LLDP neighbours. This is true for all Napalm enabled devices.

This issue seams to be caused by https://github.com/netbox-community/netbox/pull/3645 which was introduced with 2.6.7, reverting the patch restores previous behaviour.

Old view:
Screenshot 2019-11-02 at 18 06 11

New view:
Screenshot 2019-11-02 at 18 07 32

Log attached during page-load:
lldp_neighbour_log.txt

Originally created by @garnser on GitHub (Nov 2, 2019). ### Environment * Python version: 3.6.8 * NetBox version: 2.6.7 * Arista EOS ### Steps to Reproduce 1. Go into the LLDP Neighbour Tab of a DCIM with LLDP configured 2. Look at the port-map table ### Expected Behavior Expected and previous behaviour is that LLDP port-mapping retreived from the switch was populated in the table. ### Observed Behavior Although the Napalm is still function (retreiving config works for example). Netbox is no longer populating the port-map table based on LLDP neighbours. This is true for all Napalm enabled devices. This issue seams to be caused by https://github.com/netbox-community/netbox/pull/3645 which was introduced with 2.6.7, reverting the patch restores previous behaviour. Old view: <img width="1573" alt="Screenshot 2019-11-02 at 18 06 11" src="https://user-images.githubusercontent.com/3099060/68074504-f5605480-fd9b-11e9-8a6e-6ed4e85ad82d.png"> New view: <img width="1570" alt="Screenshot 2019-11-02 at 18 07 32" src="https://user-images.githubusercontent.com/3099060/68074505-f8f3db80-fd9b-11e9-81f7-a6a65aad2cf6.png"> Log attached during page-load: [lldp_neighbour_log.txt](https://github.com/netbox-community/netbox/files/3800867/lldp_neighbour_log.txt)
adam added the status: under review label 2025-12-29 18:24:28 +01:00
adam closed this issue 2025-12-29 18:24:28 +01:00
adam commented 2025-12-29 18:24:28 +01:00
Author
Owner
Copy Link

@kobayashi commented on GitHub (Nov 3, 2019):

Thanks to let us know this issue.
Could you let me know both versions?

  • napalm version
  • Arista EOS version

From napalm docs, get_lldp_neibors_detail should work for all devices.
Napalm itself seems to support at least EOS version 4.15.0F.

@kobayashi commented on GitHub (Nov 3, 2019): Thanks to let us know this issue. Could you let me know both versions? - napalm version - Arista EOS version From [napalm docs](https://napalm.readthedocs.io/en/latest/support/index.html#getters-support-matrix), `get_lldp_neibors_detail` should work for all devices. Napalm itself seems to support at least EOS version 4.15.0F.
adam commented 2025-12-29 18:24:28 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Nov 4, 2019):

@garnser Where does that log come from exactly? It looks like the response from the ajax request but it doesn't correspond 100% to what I would expect.

Could you print out the exception from the ajax request? If you want you can go to:

/api/dcim/devices/<device id>/napalm/?method=get_lldp_neighbors_detail

@DanSheps commented on GitHub (Nov 4, 2019): @garnser Where does that log come from exactly? It looks like the response from the ajax request but it doesn't correspond 100% to what I would expect. Could you print out the exception from the ajax request? If you want you can go to: /api/dcim/devices/\<device id\>/napalm/?method=get_lldp_neighbors_detail
adam commented 2025-12-29 18:24:29 +01:00
Author
Owner
Copy Link

@garnser commented on GitHub (Nov 4, 2019):

As pointed out in the previous post the issue boiled down to SW version on the switch.

Daniel if you’d like I can perform the request you’ve mentioned, otherwise this can be closed.

From: Daniel Sheppard notifications@github.com
Sent: Monday, November 4, 2019 5:02 PM
To: netbox-community/netbox
Cc: garnser; Mention
Subject: Re: [netbox-community/netbox] LLDP Neighbour portmap broken since Netbox 2.6.7 (#3662)

@garnserhttps://github.com/garnser Where does that log come from exactly? It looks like the response from the ajax request but it doesn't correspond 100% to what I would expect.

Could you print out the exception from the ajax request? If you want you can go to:

/api/dcim/devices/433/napalm/?method=get_lldp_neighbors_detail

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/netbox-community/netbox/issues/3662?email_source=notifications&email_token=AAXUTNAJ5Z5WAZCZCQRQRVTQSBBPRA5CNFSM4JIGU4KKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC7YD5Q#issuecomment-549421558, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAXUTNAWKCIYPBO66IIYKIDQSBBPRANCNFSM4JIGU4KA.

@garnser commented on GitHub (Nov 4, 2019): As pointed out in the previous post the issue boiled down to SW version on the switch. Daniel if you’d like I can perform the request you’ve mentioned, otherwise this can be closed. ________________________________ From: Daniel Sheppard <notifications@github.com> Sent: Monday, November 4, 2019 5:02 PM To: netbox-community/netbox Cc: garnser; Mention Subject: Re: [netbox-community/netbox] LLDP Neighbour portmap broken since Netbox 2.6.7 (#3662) @garnser<https://github.com/garnser> Where does that log come from exactly? It looks like the response from the ajax request but it doesn't correspond 100% to what I would expect. Could you print out the exception from the ajax request? If you want you can go to: /api/dcim/devices/433/napalm/?method=get_lldp_neighbors_detail — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub<https://github.com/netbox-community/netbox/issues/3662?email_source=notifications&email_token=AAXUTNAJ5Z5WAZCZCQRQRVTQSBBPRA5CNFSM4JIGU4KKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEC7YD5Q#issuecomment-549421558>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AAXUTNAWKCIYPBO66IIYKIDQSBBPRANCNFSM4JIGU4KA>.
adam commented 2025-12-29 18:24:29 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Nov 4, 2019):

As pointed out in the previous post the issue boiled down to SW version on the switch.

If you are confident of that, then all good

@DanSheps commented on GitHub (Nov 4, 2019): > As pointed out in the previous post the issue boiled down to SW version on the switch. If you are confident of that, then all good
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: under review
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#2989
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?