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

Use Napalm to point out inconsistencies #2210

New Issue
Closed
opened 2025-12-29 17:23:38 +01:00 by adam · 1 comment
adam commented 2025-12-29 17:23:38 +01:00
Owner
Copy Link

Originally created by @brianatlarge on GitHub (Dec 14, 2018).

Environment

  • Python version: 3.6.7
  • NetBox version: 2.5.1

Proposed Functionality

Use Napalm to access live data and compare the live environment with what is in Netbox. Any inconsistencies will be pointed out in Napalm to be rectified.

Use Case

If you have entered in an MTU setting of 9396 on an interface in Netbox but Napalm detects that interface is actually set for 1500, a warning/notice will show next to that interface in Netbox indicating an inconsistency with the Netbox data and the live environment. This will allow you to bring the environment into compliance.

Database Changes

Unknown at this time.

External Dependencies

Napalm

Originally created by @brianatlarge on GitHub (Dec 14, 2018). ### Environment * Python version: 3.6.7 * NetBox version: 2.5.1 ### Proposed Functionality Use Napalm to access live data and compare the live environment with what is in Netbox. Any inconsistencies will be pointed out in Napalm to be rectified. ### Use Case If you have entered in an MTU setting of 9396 on an interface in Netbox but Napalm detects that interface is actually set for 1500, a warning/notice will show next to that interface in Netbox indicating an inconsistency with the Netbox data and the live environment. This will allow you to bring the environment into compliance. ### Database Changes Unknown at this time. ### External Dependencies Napalm
adam closed this issue 2025-12-29 17:23:39 +01:00
adam commented 2025-12-29 17:23:40 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 14, 2018):

This is well outside NetBox's scope, and there are already well-established tools for this (Ansible, Salt, etc.). You can, however, leverage NetBox's REST API as a proxy to NAPALM for access to live devices.

@jeremystretch commented on GitHub (Dec 14, 2018): This is well outside NetBox's scope, and there are already well-established tools for this (Ansible, Salt, etc.). You can, however, leverage NetBox's REST API as a proxy to NAPALM for access to live devices.
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
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#2210
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?