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

Add device group to represent Network topologys #2246

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

Originally created by @snowie-swe on GitHub (Dec 22, 2018).

Environment.
NetBox version: v2.4.8

Proposed Functionality.

Current site refer to a physical location.
Within a site there may be multiple VLAN groups and this binds to a SITE.

Would be great if there was a way to assign a device to one or more VLAN group.
This way to keep track of L2 domains within devices.

Suggested way.
Add "device groups" in the same way VLAN Groups are built.

Use Case
Within a site there may be multiple networks ie, PROD, OOB, MGMT.
These are normally separate L2 TOP.
As the network can be multiple types of devices and device roles the current way to filter it would be via tags

Adding device groups would also be a way to represent an environment spanning over multiple sites in an easy way.

Database Changes
Dont know

External Dependencies
Dont know

Originally created by @snowie-swe on GitHub (Dec 22, 2018). **Environment.** NetBox version: v2.4.8 **Proposed Functionality.** Current site refer to a physical location. Within a site there may be multiple VLAN groups and this binds to a SITE. Would be great if there was a way to assign a device to one or more VLAN group. This way to keep track of L2 domains within devices. Suggested way. Add "device groups" in the same way VLAN Groups are built. **Use Case** Within a site there may be multiple networks ie, PROD, OOB, MGMT. These are normally separate L2 TOP. As the network can be multiple types of devices and device roles the current way to filter it would be via tags Adding device groups would also be a way to represent an environment spanning over multiple sites in an easy way. **Database Changes** Dont know **External Dependencies** Dont know
adam closed this issue 2025-12-29 17:24:04 +01:00
adam commented 2025-12-29 17:24:04 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 2, 2019):

NetBox already provides several mechanisms for classifying devices, including sites, racks, types, roles, and tags. Modeling L2 topology is beyond the scope of NetBox's functionality.

@jeremystretch commented on GitHub (Jan 2, 2019): NetBox already provides several mechanisms for classifying devices, including sites, racks, types, roles, and tags. Modeling L2 topology is beyond the scope of NetBox's functionality.
adam commented 2025-12-29 17:24:04 +01:00
Author
Owner
Copy Link

@snowie-swe commented on GitHub (Jan 5, 2019):

usercase:
2 Sites (physical locations) (streached datacenter)
2 Environment (stage and prod)
Within the environment the same type of Devices are used for example CPE, OOB Switch, Datacenter Switch, Servers etc.

I would like in an easy way to get out all OOB Switches within an environment that is on multiple sistes,
I see this as the same reason why the VLAN groups was made.

VLAN groups are binded towards a SITE or nothing.
We uses VLAN groups to represent an L2 environment, and then it cant be binded towards a site.
If a VLAN group also can be binded to a Device group it would be even mote flexible. :)

image

If i have groups of devices i believe it would fix multiple issues with fairly little extra work as its already within netbox in several locations.

it would also give more consistency across the plattform

@snowie-swe commented on GitHub (Jan 5, 2019): usercase: 2 Sites (physical locations) (streached datacenter) 2 Environment (stage and prod) Within the environment the same type of Devices are used for example CPE, OOB Switch, Datacenter Switch, Servers etc. I would like in an easy way to get out all OOB Switches within an environment that is on multiple sistes, I see this as the same reason why the VLAN groups was made. VLAN groups are binded towards a SITE or nothing. We uses VLAN groups to represent an L2 environment, and then it cant be binded towards a site. If a VLAN group also can be binded to a Device group it would be even mote flexible. :) ![image](https://user-images.githubusercontent.com/41901413/50722472-d76c8980-10cf-11e9-9054-3cd08e267992.png) If i have groups of devices i believe it would fix multiple issues with fairly little extra work as its already within netbox in several locations. it would also give more consistency across the plattform
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#2246
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?