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

VNI ranges #7858

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

Originally created by @ciroiriarte on GitHub (Apr 4, 2023).

NetBox version

v3.4.5

Feature type

Data model extension

Proposed functionality

It's currently possible to document VXLAN Network Identifiers (VNI) using the Overlay logic/module:

image

But we're missing the range tracking as we have for VLANs. The proposed functionality would be to track VNI assignment to be able to request "next available in range".

Use case

Proper tracking for VNI assignments, as done with VLAN ranges.

Database changes

No proficient in the DB schema, but would asume at least range definition & VNI to range relationship.

External dependencies

No response

Originally created by @ciroiriarte on GitHub (Apr 4, 2023). ### NetBox version v3.4.5 ### Feature type Data model extension ### Proposed functionality It's currently possible to document VXLAN Network Identifiers (VNI) using the Overlay logic/module: ![image](https://user-images.githubusercontent.com/1750260/229821474-719c11e8-2108-4e0f-8d53-dcdcfc0b935f.png) But we're missing the range tracking as we have for VLANs. The proposed functionality would be to track VNI assignment to be able to request "next available in range". ### Use case Proper tracking for VNI assignments, as done with VLAN ranges. ### Database changes No proficient in the DB schema, but would asume at least range definition & VNI to range relationship. ### External dependencies _No response_
adam added the type: featurestatus: revisions needed labels 2025-12-29 20:29:05 +01:00
adam closed this issue 2025-12-29 20:29:05 +01:00
adam commented 2025-12-29 20:29:06 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Apr 4, 2023):

Can you give me an example of how a VNI range is used in production or is this more of an organizational thing?

@DanSheps commented on GitHub (Apr 4, 2023): Can you give me an example of how a VNI range is used in production or is this more of an organizational thing?
adam commented 2025-12-29 20:29:06 +01:00
Author
Owner
Copy Link

@ciroiriarte commented on GitHub (Apr 5, 2023):

Can you give me an example of how a VNI range is used in production or is this more of an organizational thing?

Hello!, yes it's more an organization thing. The current use case:

  • Ranges are assigned to different datacenters, in case EVPN type 2 is required at some point in time, we won't have a clash.
    Site A: Range1
    Site B: Range2
    Site C: Range3
    Cross datacenters: Range 4
  • In some scenarios, we have more than one provisioning team per site (different business units), so we also need to assign more than one range per site so those teams can provision independently in the same IP Fabric.
  • Domain is tracked via tags, with a domain being an administrative domain or network (Datacenter IPFabric vs IPRAN vs ISP core vs Fixed access). That's used for all the constructions and doesn't require any change in Netbox.
  • Also, for provisioning we need a way of tracking VNI usage. The idea would be for a script to:
  1. ask Netbox "give me next VLAN in range for X site & Y domain"
  2. ask Netbox "give me next VNI in range for X site & Y domain"
  3. set the VNI to VLAN relationship
  4. provision the VNI within the fabric & matching VLANs towards the servers (trunk mode)
  5. provisiong the VLAN tagging configuration on the server side
@ciroiriarte commented on GitHub (Apr 5, 2023): > Can you give me an example of how a VNI range is used in production or is this more of an organizational thing? Hello!, yes it's more an organization thing. The current use case: - Ranges are assigned to different datacenters, in case EVPN type 2 is required at some point in time, we won't have a clash. Site A: Range1 Site B: Range2 Site C: Range3 Cross datacenters: Range 4 - In some scenarios, we have more than one provisioning team per site (different business units), so we also need to assign more than one range per site so those teams can provision independently in the same IP Fabric. - Domain is tracked via tags, with a domain being an administrative domain or network (Datacenter IPFabric vs IPRAN vs ISP core vs Fixed access). That's used for all the constructions and doesn't require any change in Netbox. - Also, for provisioning we need a way of tracking VNI usage. The idea would be for a script to: 1. ask Netbox "give me next VLAN in range for X site & Y domain" 2. ask Netbox "give me next VNI in range for X site & Y domain" 3. set the VNI to VLAN relationship 4. provision the VNI within the fabric & matching VLANs towards the servers (trunk mode) 5. provisiong the VLAN tagging configuration on the server side
adam commented 2025-12-29 20:29:07 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 4, 2023):

Thanks for the proposal, but I'm afraid it's too short on detail. What would the proposed VNI range model look like?

@jeremystretch commented on GitHub (May 4, 2023): Thanks for the proposal, but I'm afraid it's too short on detail. What would the proposed VNI range model look like?
adam commented 2025-12-29 20:29:07 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 25, 2023):

Closing this out as OP has provided no further detail on the proposed implementation.

@jeremystretch commented on GitHub (May 25, 2023): Closing this out as OP has provided no further detail on the proposed implementation.
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: revisions needed type: feature
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#7858
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?