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

Prefix Role / VLAN Role #177

New Issue
Closed
opened 2025-12-29 16:18:52 +01:00 by adam · 3 comments
adam commented 2025-12-29 16:18:52 +01:00
Owner
Copy Link

Originally created by @x-zeroflux-x on GitHub (Jul 8, 2016).

Hi Guys,

Just looking at the work flow here as per below

  1. Create VLAN - give it a number for example 100
  2. When creating a VLAN it asks you for a role - this role could be Management.
  3. We then go to create a prefix which could be 192.168.1.0/24
  4. You assign the VLAN 100 as created previously.
  5. You then have the option to set a role again?

Isn't this redundant since the VLAN already defined the role?

I know in our case we provide a VLAN per customer or if internally VLAN per role.

Thoughts?

Originally created by @x-zeroflux-x on GitHub (Jul 8, 2016). Hi Guys, Just looking at the work flow here as per below 1. Create VLAN - give it a number for example 100 2. When creating a VLAN it asks you for a role - this role could be Management. 3. We then go to create a prefix which could be 192.168.1.0/24 4. You assign the VLAN 100 as created previously. 5. You then have the option to set a role again? Isn't this redundant since the VLAN already defined the role? I know in our case we provide a VLAN per customer or if internally VLAN per role. Thoughts?
adam closed this issue 2025-12-29 16:18:52 +01:00
adam commented 2025-12-29 16:18:53 +01:00
Author
Owner
Copy Link

@bellwood commented on GitHub (Jul 8, 2016):

Prefixes and VLAN's can have separate roles

E.g you can have a prefix that is a "private network" role but then have multiple vlans within that have additional roles "pdus", "upss" etc

@bellwood commented on GitHub (Jul 8, 2016): Prefixes and VLAN's can have separate roles E.g you can have a prefix that is a "private network" role but then have multiple vlans within that have additional roles "pdus", "upss" etc
adam commented 2025-12-29 16:18:53 +01:00
Author
Owner
Copy Link

@x-zeroflux-x commented on GitHub (Jul 8, 2016):

Hi Bell,

OK ... fair enough - I will close this issue as it is designed to be this way.

Thanks
Shaun

@x-zeroflux-x commented on GitHub (Jul 8, 2016): Hi Bell, OK ... fair enough - I will close this issue as it is designed to be this way. Thanks Shaun
adam commented 2025-12-29 16:18:53 +01:00
Author
Owner
Copy Link

@bellwood commented on GitHub (Jul 8, 2016):

No worries, I assume it's the intended functionality - I hope I'm right =)

@bellwood commented on GitHub (Jul 8, 2016): No worries, I assume it's the intended functionality - I hope I'm right =)
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#177
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?