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

Implement discrete layer two domains with a site #77

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

Originally created by @jeremystretch on GitHub (Jun 29, 2016).

Currently, a user can create multiple VLANs with the same VID and name within a site. This is allowed to provide the maximum flexibility when documenting real-world networks. However, it can also be very confusing, as there is no additional information to differentiate "VLAN 100 (ToR P2P)" from another "VLAN 100 (ToR P2P)," for example.

The proposal here is to implement a new model to represent a discrete zone within a site, within which each VLAN must have a unique VID (and name?). It should be fairly straightforward to extend the current schema to support this.

Originally created by @jeremystretch on GitHub (Jun 29, 2016). Currently, a user can create multiple VLANs with the same VID and name within a site. This is allowed to provide the maximum flexibility when documenting real-world networks. However, it can also be very confusing, as there is no additional information to differentiate "VLAN 100 (ToR P2P)" from another "VLAN 100 (ToR P2P)," for example. The proposal here is to implement a new model to represent a discrete zone within a site, within which each VLAN must have a unique VID (and name?). It should be fairly straightforward to extend the current schema to support this.
adam closed this issue 2025-12-29 15:31:41 +01:00
adam commented 2025-12-29 15:31:42 +01:00
Author
Owner
Copy Link

@mdlayher commented on GitHub (Jun 30, 2016):

https://github.com/digitalocean/netbox/issues/147 was filed recently as a duplicate of this issue. Linking it here because it provides some great details that may be useful in designing this feature.

@mdlayher commented on GitHub (Jun 30, 2016): https://github.com/digitalocean/netbox/issues/147 was filed recently as a duplicate of this issue. Linking it here because it provides some great details that may be useful in designing this feature.
adam commented 2025-12-29 15:31:42 +01:00
Author
Owner
Copy Link

@rdujardin commented on GitHub (Jul 12, 2016):

Accordingly with #235, we could drop the VLAN site assignment and replace it with an optional discrete zone assignment, discrete zones being assigned to a site (maybe optionnally too) ?

@rdujardin commented on GitHub (Jul 12, 2016): Accordingly with #235, we could drop the VLAN site assignment and replace it with an optional discrete zone assignment, discrete zones being assigned to a site (maybe optionnally too) ?
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#77
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?