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

Support Device groups and vlans per device/device group #58

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

Originally created by @loganbest on GitHub (Jun 28, 2016).

Ideally we'd like to have the ability to group devices together and have Unique vlans per device or device group.

In a traditional campus network topology you have core -> distribution -> access. Often times you have router pairs at core/distro layers and HSRP/GLBP on those pairs. Supporting a unique Vlan 500 on distrogrp1 (distro1a/distro1b) and a unique Vlan 500 on distrogrp2 (distro2a/distro2b) would be ideal in many implementations of this software. Each unique Vlan can have it's own associations as they currently do.

Originally created by @loganbest on GitHub (Jun 28, 2016). Ideally we'd like to have the ability to group devices together and have Unique vlans per device or device group. In a traditional campus network topology you have core -> distribution -> access. Often times you have router pairs at core/distro layers and HSRP/GLBP on those pairs. Supporting a unique Vlan 500 on distrogrp1 (distro1a/distro1b) and a unique Vlan 500 on distrogrp2 (distro2a/distro2b) would be ideal in many implementations of this software. Each unique Vlan can have it's own associations as they currently do.
adam added the status: duplicate label 2025-12-29 15:31:01 +01:00
adam closed this issue 2025-12-29 15:31:01 +01:00
adam commented 2025-12-29 15:31:02 +01:00
Author
Owner
Copy Link

@bellwood commented on GitHub (Jun 29, 2016):

We do something similar:

Juniper Edge -> VSRP -> Cisco Distribution -> HSRP -> Cisco Core

For our distribution groups we prefix the vlans by the group number so everthing in group one has a vlan 1xx, group 2 vlan 2xx and so on

HSRP version 2 gives you almost endless possibilities

@bellwood commented on GitHub (Jun 29, 2016): We do something similar: Juniper Edge -> VSRP -> Cisco Distribution -> HSRP -> Cisco Core For our distribution groups we prefix the vlans by the group number so everthing in group one has a vlan 1xx, group 2 vlan 2xx and so on HSRP version 2 gives you almost endless possibilities
adam commented 2025-12-29 15:31:03 +01:00
Author
Owner
Copy Link

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

FYI, @jeremystretch seems to have made a duplicate of this request in issue #111

@mpenning commented on GitHub (Jun 30, 2016): FYI, @jeremystretch seems to have made a duplicate of this request in issue #111
adam commented 2025-12-29 15:31:04 +01:00
Author
Owner
Copy Link

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

#99 might tie into this too; being able to logically link/group devices for the purposes of stacking, high availability, etc.

@peelman commented on GitHub (Jun 30, 2016): #99 might tie into this too; being able to logically link/group devices for the purposes of stacking, high availability, etc.
adam commented 2025-12-29 15:31:04 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 29, 2016):

Seems like this was implemented by #111.

@jeremystretch commented on GitHub (Jul 29, 2016): Seems like this was implemented by #111.
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 status: duplicate
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#58
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?