IPAM | VRF add VNI field #744

New Issue

MrUnknownDE · 2026-04-05T17:24:31+02:00

MrUnknownDE commented

2026-04-05 17:24:31 +02:00

Originally created by @c-po on 12/11/2025

NetBox version

v4.4.8

Feature type

Data model extension

Proposed functionality

In EVPN‑VXLAN deployments the VNI is the identifier that ties a VRF to its overlay segment. VRF VNI uniqueness is mandatory to not mix different routing domains within a fabric.
NetBox currently captures only VRF import/export route-targets, so the VNI must be stored in e.g. free‑form notes or a custom field.

Use case

In EVPN VXLAN deployments a VRF also receives a VNI (VXLAN Network Identifier), add a VNI field with 24bit support

Single source of truth - VRF to VNI relationship is stored centrally
Ansible/Terraform can pull vrf.vni directly from the API
"Which VRFs use VNI 5001"?
Built‑in filters and validation for VNI range/uniqueness

Database changes

Add an optional vni (PositiveIntegerField) to the VRF model, unique across the site/tenant
Enforce VXLAN range (1‑16,777,215) and uniqueness; add a simple tooltip for users

Why should it go on the VRF model (as opposed to the L2VPN model)

L2VPN model also only has route-targets for import/export
L2VPN carries a general "Identifier" field thich translates into different languages but does not explicitly match to VNI, also the field has no upper boundary constraint (24bit for VXLAN VNI) 16777218

External dependencies

No response

*Originally created by @c-po on 12/11/2025* ### NetBox version v4.4.8 ### Feature type Data model extension ### Proposed functionality * In EVPN‑VXLAN deployments the VNI is the identifier that ties a VRF to its overlay segment. VRF VNI uniqueness is mandatory to not mix different routing domains within a fabric. * NetBox currently captures only VRF import/export route-targets, so the VNI must be stored in e.g. free‑form notes or a custom field. ### Use case In EVPN VXLAN deployments a VRF also receives a VNI (VXLAN Network Identifier), add a VNI field with 24bit support * Single source of truth - VRF to VNI relationship is stored centrally * Ansible/Terraform can pull `vrf.vni` directly from the API * "Which VRFs use VNI 5001"? * Built‑in filters and validation for VNI range/uniqueness ### Database changes * Add an optional vni (PositiveIntegerField) to the VRF model, unique across the site/tenant * Enforce VXLAN range (1‑16,777,215) and uniqueness; add a simple tooltip for users > Why should it go on the VRF model (as opposed to the L2VPN model) * L2VPN model also only has route-targets for import/export * L2VPN carries a general "Identifier" field thich translates into different languages but does not explicitly match to VNI, also the field has no upper boundary constraint (24bit for VXLAN VNI) 16777218 ### External dependencies _No response_

MrUnknownDE closed this issue

2026-04-05 17:24:31 +02:00

Sign in to join this conversation.

Branches Tags

main

21455-sql-indexes-audit

21357-register-model-actions

feature

20924-plugin-ui-components

21766-improve-test-coverage-for-sortable-table-columns

21157-export-template-public-models

21025-pre-render-config-contexts

21364-swagger

feature-ip-prefix-link

20911-dropdown-3

fix_module_substitution

21160-filterset

20911-dropdown-2

20044-elevation-stuck-lightmode

7604-filter-modifiers-v3

20660-script-load

19724-graphql

14884-script

19720-macaddress-interface-generic-relation

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

No Label netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox netbox pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure pending closure status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed status: revisions needed type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature type: feature

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github/netbox#744