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

Enable assignment of VLAN during Prefix import #26

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

Originally created by @Gelob on GitHub (Jun 27, 2016).

The Prefix Import functionality does not currently accept the VLAN field

Originally created by @Gelob on GitHub (Jun 27, 2016). The Prefix Import functionality does not currently accept the VLAN field
adam closed this issue 2025-12-29 15:29:58 +01:00
adam commented 2025-12-29 15:29:58 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 28, 2016):

This was intentional. Since a site can have multiple VLANs with the same VID and name, there's no way to specify a unique VLAN in CSV. I suppose we could implement it anyway, and simply return an error if duplicate VLANs are found.

@jeremystretch commented on GitHub (Jun 28, 2016): This was intentional. Since a site can have multiple VLANs with the same VID and name, there's no way to specify a unique VLAN in CSV. I suppose we could implement it anyway, and simply return an error if duplicate VLANs are found.
adam commented 2025-12-29 15:30:00 +01:00
Author
Owner
Copy Link

@topside844 commented on GitHub (Jun 28, 2016):

IMHO, you should not be allowing multiple VLANs that have the exact same identifying information (VLAN name, VLAN ID, site) without adding some other piece of identifying information to the table.

Maybe we utilize a 'Default' VLAN database that's used automatically within each site, with the ability to instantiate additional VLAN (or VXLAN) domains in a location if necessary? This would allow network admins to create "PODs" within each site that each contain their own unique set of L2 networks.

@topside844 commented on GitHub (Jun 28, 2016): IMHO, you should not be allowing multiple VLANs that have the exact same identifying information (VLAN name, VLAN ID, site) without adding some other piece of identifying information to the table. Maybe we utilize a 'Default' VLAN database that's used automatically within each site, with the ability to instantiate additional VLAN (or VXLAN) domains in a location if necessary? This would allow network admins to create "PODs" within each site that each contain their own unique set of L2 networks.
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#26
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?