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

VRF as a per-node database schema #1954

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

Originally created by @adamv0025 on GitHub (Aug 19, 2018).

Looks like netbox is looking at the VRF thing from a wrong angle unfortunately.
It seem to treat it as a network-wide thing, where in fact VRF is very much a per-node thing.

All the parameters you can define for a VRF are per-node specific::

Name: vrfa-a-on-rtr-a & vrf-a-on-rtrb (we just tend to use common names for clarity)
RD: vrfa-a-on-rtr-a & vrf-a-on-rtrb (once again just an operators choice on how many unique sets of routes they need, and what RD format they’ll use for that (Type-1/2/3 RDs)
Export RT/policy: (again just an operator’s choice to make these unique or common across nodes and for a particular set of prefixes –as defined by the policy)
Import RT/policy: (again just an operator’s choice to make these unique or common across nodes and for a particular set of prefixes –as defined by the policy)
Interfaces: list of interfaces associated with a vrf which is very different on each node

And really don’t understand what’s this thing with assigning prefixes to VRFs
-where do I configure that on a router?
-or is it supposed to be replica of VRFs routing table? -good luck with keeping internet vrf records up to date then ;)
-I’d assign a prefix to customer or an interface, but never to a VRF
-the only place I could see related to a prefix in VRF realm is to record the import/export policy in the database –again unique per node (where a specific prefix gets a specific RT, or route is accepted only if both RT as well as prefix matches)

This is related to: #1215

adam

Originally created by @adamv0025 on GitHub (Aug 19, 2018). Looks like netbox is looking at the VRF thing from a wrong angle unfortunately. It seem to treat it as a network-wide thing, where in fact VRF is very much a per-node thing. All the parameters you can define for a VRF are per-node specific:: **Name:** vrfa-a-on-rtr-a & vrf-a-on-rtrb (we just tend to use common names for clarity) **RD:** vrfa-a-on-rtr-a & vrf-a-on-rtrb (once again just an operators choice on how many unique sets of routes they need, and what RD format they’ll use for that (Type-1/2/3 RDs) **Export RT/policy:** (again just an operator’s choice to make these unique or common across nodes and for a particular set of prefixes –as defined by the policy) **Import RT/policy:** (again just an operator’s choice to make these unique or common across nodes and for a particular set of prefixes –as defined by the policy) **Interfaces:** list of interfaces associated with a vrf which is very different on each node And really don’t understand what’s this thing with assigning prefixes to VRFs -where do I configure that on a router? -or is it supposed to be replica of VRFs routing table? -good luck with keeping internet vrf records up to date then ;) -I’d assign a prefix to customer or an interface, but never to a VRF -the only place I could see related to a prefix in VRF realm is to record the import/export policy in the database –again unique per node (where a specific prefix gets a specific RT, or route is accepted only if both RT as well as prefix matches) This is related to: #1215 adam
adam closed this issue 2025-12-29 17:20:54 +01:00
adam commented 2025-12-29 17:20:55 +01:00
Author
Owner
Copy Link

@lampwins commented on GitHub (Aug 20, 2018):

Thank you for your interest in NetBox. We require that all issues be submitted using one of the templates provided here. This is to ensure that only valid issues are reported and that each issue includes all the information necessary for a developer to act on it. Please update your issue so that it matches the appropriate template (this may require rewriting your issue entirely). This issue will be closed in one week if it has not been updated. Thanks!

Additionally, please take a look at the docs for the VRF model. This will give you an idea of NetBox's intentions when modeling a VRF.

@lampwins commented on GitHub (Aug 20, 2018): Thank you for your interest in NetBox. We require that all issues be submitted using one of the templates provided [here](https://github.com/digitalocean/netbox/issues/new/choose). This is to ensure that only valid issues are reported and that each issue includes all the information necessary for a developer to act on it. Please update your issue so that it matches the appropriate template (this may require rewriting your issue entirely). This issue will be closed in one week if it has not been updated. Thanks! Additionally, please take a look at the docs for the [VRF model](https://netbox.readthedocs.io/en/latest/core-functionality/ipam/#virtual-routing-and-forwarding-vrf). This will give you an idea of NetBox's intentions when modeling a VRF.
adam commented 2025-12-29 17:20:55 +01:00
Author
Owner
Copy Link

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

It sounds like NetBox isn't the right solution for you.

@jeremystretch commented on GitHub (Aug 21, 2018): It sounds like NetBox isn't the right solution for you.
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#1954
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?