Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement discrete layer two domains with a site #111

Closed
jeremystretch opened this issue Jun 29, 2016 · 2 comments
Closed

Implement discrete layer two domains with a site #111

jeremystretch opened this issue Jun 29, 2016 · 2 comments
Milestone

Comments

@jeremystretch
Copy link
Member

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.

@mdlayher mdlayher changed the title [Feature] Implement discrete layer two domains with a site Implement discrete layer two domains with a site Jun 30, 2016
@mdlayher
Copy link
Contributor

#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.

@rdujardin
Copy link

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) ?

@jeremystretch jeremystretch added this to the v1.3 milestone Jul 12, 2016
jeremystretch added a commit that referenced this issue Jul 15, 2016
if-fi pushed a commit to if-fi/netbox that referenced this issue Oct 1, 2016
if-fi pushed a commit to if-fi/netbox that referenced this issue Oct 1, 2016
@lock lock bot locked as resolved and limited conversation to collaborators Jan 22, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants