starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Allow prefixes to be assigned to VLAN in other/no site #6866

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

Originally created by @heiko-ma on GitHub (Aug 24, 2022).

NetBox version

v3.2.9

Feature type

Change to existing functionality

Proposed functionality

As described in #10104, it is currently not possible to assign a prefix to a VLAN in a VLAN group that isn't in the same site/site group. For some usecases (described below) it would be practical, if the prefix could be assigned to a VLAN which is either:

  • in no site (i believe this is currently possible with VLANs -> they can be assigned to devices if they have no site)

  • in a site which is higher up in the hierarchy of site groups/region, for example
    region "global" -> VLAN group is scoped to region and set to global
    region "south"
    site "A" -> Prefix is assigned to site which is child of the region

    site group "global" -> VLAN group is scoped to site group and set to global
    site group "campus A"
    site "A" -> Prefix is assigned to site which is child of the site group

Site groups or regions provide some kind of constraint in which objects can be assigned. If VLAN/VLAN group and prefix are in the same hierarchy, I see no issue in this.

Use case

In our company, every site has a basic set of VLANs that need to be implemented. To skip the need of creating this set for every new site, it would be beneficial if a "global scoped" set could be used and the prefixes would be assigned to this set. This would eliminate the need of creating the same VLAN all over again.

Database changes

No response

External dependencies

No response

Originally created by @heiko-ma on GitHub (Aug 24, 2022). ### NetBox version v3.2.9 ### Feature type Change to existing functionality ### Proposed functionality As described in #10104, it is currently not possible to assign a prefix to a VLAN in a VLAN group that isn't in the same site/site group. For some usecases (described below) it would be practical, if the prefix could be assigned to a VLAN which is either: - in no site (i believe this is currently possible with VLANs -> they can be assigned to devices if they have no site) - in a site which is higher up in the hierarchy of site groups/region, for example region "global" -> VLAN group is scoped to region and set to global region "south" site "A" -> Prefix is assigned to site which is child of the region ------------------------------------------------------------------------- site group "global" -> VLAN group is scoped to site group and set to global site group "campus A" site "A" -> Prefix is assigned to site which is child of the site group Site groups or regions provide some kind of constraint in which objects can be assigned. If VLAN/VLAN group and prefix are in the same hierarchy, I see no issue in this. ### Use case In our company, every site has a basic set of VLANs that need to be implemented. To skip the need of creating this set for every new site, it would be beneficial if a "global scoped" set could be used and the prefixes would be assigned to this set. This would eliminate the need of creating the same VLAN all over again. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closure labels 2025-12-29 19:46:11 +01:00
adam closed this issue 2025-12-29 19:46:12 +01:00
adam commented 2025-12-29 19:46:12 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 24, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Oct 24, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:46:12 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 24, 2022):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Nov 24, 2022): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure type: feature
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#6866
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?