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

Add VXLANs/VNIs to IPAM #2304

New Issue
Closed
opened 2025-12-29 17:24:39 +01:00 by adam · 3 comments
adam commented 2025-12-29 17:24:39 +01:00
Owner
Copy Link

Originally created by @hellerve on GitHub (Jan 18, 2019).

Environment

  • Python version: 3.7.2
  • NetBox version: 2.4.3

VXLANs are not representable in Netbox. There have been issues opened that talk about adding them (e.g. #1725, #1800), but they’ve either been abandoned or were too general. This issue tries to provide a more focused, pragmatic solution in the hopes that this is generally useful.

Nota bene: if there is sufficient interest, I’d be open to work on this feature myself.

Proposed Functionality

The IPAM part of Netbox is currently able to handle VLANs and assign them to tenants. Often these VLANs are internally connected via VXLAN IDs (VNI), though, and having them be representable would help giving an overview over which VLANs are connected in such a way.

Concretely, VLANs would be connected to a VXLAN; these new entities have a connection to multiple VLANs and their view would provide an overview of which VLANs are part of them.

Use Case

A user wants to find out which VLANS are internally connected by a specific VXLAN. They go to the VXLAN view, find the VXLAN they want to examine, and see the VLANs that are potentially tagged with that VXLAN.

Optionally, there could also be a connection to a tenant, though I’m not sure how generalizable this is.

Database Changes

This change would require a new model in the database, and create/edit/delete views. Ideally they would also be part of the API.

External Dependencies

Probably none.

Cheers

Originally created by @hellerve on GitHub (Jan 18, 2019). ### Environment * Python version: 3.7.2 * NetBox version: 2.4.3 VXLANs are not representable in Netbox. There have been issues opened that talk about adding them (e.g. #1725, #1800), but they’ve either been abandoned or were too general. This issue tries to provide a more focused, pragmatic solution in the hopes that this is generally useful. Nota bene: if there is sufficient interest, I’d be open to work on this feature myself. ### Proposed Functionality The IPAM part of Netbox is currently able to handle VLANs and assign them to tenants. Often these VLANs are internally connected via VXLAN IDs (VNI), though, and having them be representable would help giving an overview over which VLANs are connected in such a way. Concretely, VLANs would be connected to a VXLAN; these new entities have a connection to multiple VLANs and their view would provide an overview of which VLANs are part of them. ### Use Case A user wants to find out which VLANS are internally connected by a specific VXLAN. They go to the VXLAN view, find the VXLAN they want to examine, and see the VLANs that are potentially tagged with that VXLAN. Optionally, there could also be a connection to a tenant, though I’m not sure how generalizable this is. ### Database Changes This change would require a new model in the database, and create/edit/delete views. Ideally they would also be part of the API. ### External Dependencies Probably none. Cheers
adam closed this issue 2025-12-29 17:24:39 +01:00
adam commented 2025-12-29 17:24:40 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 18, 2019):

This would amount to a major new feature, and unfortunately we're not currently accepting requests which would extend NetBox's scope (see the contributing guide). It's a topic we'll almost certainly revisit at some point in the future once the current backlog of feature requests has been addressed.

@jeremystretch commented on GitHub (Jan 18, 2019): This would amount to a major new feature, and unfortunately we're not currently accepting requests which would extend NetBox's scope (see the [contributing guide](https://github.com/digitalocean/netbox/blob/develop/CONTRIBUTING.md)). It's a topic we'll almost certainly revisit at some point in the future once the current backlog of feature requests has been addressed.
adam commented 2025-12-29 17:24:40 +01:00
Author
Owner
Copy Link

@hellerve commented on GitHub (Jan 18, 2019):

Fair enough. I was aware of the contributing guide, but apparently didn’t read the second part of the sentence.

Out of necessity, I will work on this feature in a fork of Netbox. Should you ever revisit this, feel free to notify me and we can talk about getting this back into mainline!

@hellerve commented on GitHub (Jan 18, 2019): Fair enough. I was aware of the contributing guide, but apparently didn’t read the second part of the sentence. Out of necessity, I will work on this feature in a fork of Netbox. Should you ever revisit this, feel free to notify me and we can talk about getting this back into mainline!
adam commented 2025-12-29 17:24:40 +01:00
Author
Owner
Copy Link

@jcbrandis commented on GitHub (Jun 4, 2019):

Oh no, this is sad news. Was looking to map VLAN to VNI ID's. I will use the description field for now. Fingers crossed it may be added one day.

@jcbrandis commented on GitHub (Jun 4, 2019): Oh no, this is sad news. Was looking to map VLAN to VNI ID's. I will use the description field for now. Fingers crossed it may be added one day.
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#2304
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?