Netbox UI status and LLDP pages are not showing up, the API works fine #1769

New Issue

adam · 2025-12-29T17:18:58+01:00

adam commented

2025-12-29 17:18:58 +01:00

Originally created by @AmbicaY on GitHub (Jun 4, 2018).

Issue type

[ ] Bug report

Environment

Python version: 3.5.2
NetBox version: v2.3.3

Description

I am able to query the device status details via the API call:
http://sc-netbox-test-01/api/dcim/devices/402/napalm/?method=get_facts

But on the UI:
http://sc-netbox-test-01/dcim/devices/402/status/
I get the error:
{"detail":"Error connecting to the device at *****: "}

I checked this on a Cisco Nexus device (napalm driver: nxos_ssh)

Here is my napalm config:
NAPALM_USERNAME = ''
NAPALM_PASSWORD = ''
NAPALM_TIMEOUT = 60
NAPALM_ARGS = {
'secret': NAPALM_PASSWORD,
}

Similarly, for LLDP Neighbors, there is no error, but it does not show up any data. But the API call works fine: http://sc-netbox-test-01/api/dcim/devices/402/napalm/?method=get_lldp_neighbours

The configuration tab opens up fine though.

Originally created by @AmbicaY on GitHub (Jun 4, 2018). ### Issue type [ ] Bug report  ### Environment * Python version: 3.5.2 * NetBox version: v2.3.3 ### Description I am able to query the device status details via the API call: http://sc-netbox-test-01/api/dcim/devices/402/napalm/?method=get_facts But on the UI: http://sc-netbox-test-01/dcim/devices/402/status/ I get the error: {"detail":"Error connecting to the device at *****: "} I checked this on a Cisco Nexus device (napalm driver: nxos_ssh) Here is my napalm config: NAPALM_USERNAME = '*********' NAPALM_PASSWORD = '*********' NAPALM_TIMEOUT = 60 NAPALM_ARGS = { 'secret': NAPALM_PASSWORD, } Similarly, for LLDP Neighbors, there is no error, but it does not show up any data. But the API call works fine: http://sc-netbox-test-01/api/dcim/devices/402/napalm/?method=get_lldp_neighbours The configuration tab opens up fine though.

adam closed this issue

2025-12-29 17:18:58 +01:00

adam commented

2025-12-29 17:18:59 +01:00

@jeremystretch commented on GitHub (Jun 6, 2018):

I get the error:
{"detail":"Error connecting to the device at *****: "}

This indicates that either NetBox cannot reach the device, or there is an issue with the NAPALM driver. (Neither of these can be addressed in NetBox.)

Similarly, for LLDP Neighbors, there is no error, but it does not show up any data.

LLDP neighbors will only display if your device's interfaces are correctly named. You'll need to post the list of configured interfaces as well as the full API response (not a link).

@jeremystretch commented on GitHub (Jun 6, 2018): > I get the error: > {"detail":"Error connecting to the device at *****: "} This indicates that either NetBox cannot reach the device, or there is an issue with the NAPALM driver. (Neither of these can be addressed in NetBox.) > Similarly, for LLDP Neighbors, there is no error, but it does not show up any data. LLDP neighbors will only display if your device's interfaces are correctly named. You'll need to post the list of configured interfaces as well as the full API response (not a link).

adam commented

2025-12-29 17:18:59 +01:00

@AmbicaY commented on GitHub (Jun 7, 2018):

I think I understood the problem about the LLDP neighbors:
when I do a "show lldp neighbors", the interfaces are listed as like: "Eth1/50", but in the "show interface" command the interface name is like "Ethernet1/50".

Is there anything netbox can do to fix this?

Coming to the netbox status page, if there was an issue with connectivity to the device or the NAPALM driver, even the api page should not work, right?

@AmbicaY commented on GitHub (Jun 7, 2018): I think I understood the problem about the LLDP neighbors: when I do a "show lldp neighbors", the interfaces are listed as like: "Eth1/50", but in the "show interface" command the interface name is like "Ethernet1/50". Is there anything netbox can do to fix this? Coming to the netbox status page, if there was an issue with connectivity to the device or the NAPALM driver, even the api page should not work, right?

adam commented

2025-12-29 17:18:59 +01:00

@jeremystretch commented on GitHub (Jun 21, 2018):

when I do a "show lldp neighbors", the interfaces are listed as like: "Eth1/50", but in the "show interface" command the interface name is like "Ethernet1/50".

You'll need to rename the interfaces as you have them defined in NetBox so that they match what the device is reporting. This can be scripted out in the shell to rename everything automatically.

@jeremystretch commented on GitHub (Jun 21, 2018): > when I do a "show lldp neighbors", the interfaces are listed as like: "Eth1/50", but in the "show interface" command the interface name is like "Ethernet1/50". You'll need to rename the interfaces as you have them defined in NetBox so that they match what the device is reporting. This can be scripted out in the shell to rename everything automatically.

Sign in to join this conversation.

Branches Tags

main

update-changelog-comments-docs

feature-removal-issue-type

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#1769