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

VLAN “Service Identifier” field (VXLAN or ISID) #607

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

Originally created by @DouglasHeriot on GitHub (Jan 5, 2017).

We have an Avaya fabric core network, where ISIDs are mapped to VLANs on the access switches. We have many VLANs created in Netbox, and need a way to map them back to unique ISIDs.

When we have the same VID used across multiple sites, they each have unique ISIDs.
This is similar to VXLAN trunks, or Q-in-Q ​​#116 service VLANs.

I propose a "Service Identifier" field that can be used to track this unique number. (VXLAN and ISIDs are both 24-bit)

I plan to have a go at implementing this myself.

Originally created by @DouglasHeriot on GitHub (Jan 5, 2017). We have an Avaya fabric core network, where ISIDs are mapped to VLANs on the access switches. We have many VLANs created in Netbox, and need a way to map them back to unique ISIDs. When we have the same VID used across multiple sites, they each have unique ISIDs. This is similar to VXLAN trunks, or Q-in-Q ​​#116 service VLANs. I propose a "Service Identifier" field that can be used to track this unique number. (VXLAN and ISIDs are both 24-bit) I plan to have a go at implementing this myself.
adam closed this issue 2025-12-29 16:23:46 +01:00
adam commented 2025-12-29 16:23:49 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 5, 2017):

Tagging this as potentially related to #116.

@jeremystretch commented on GitHub (Jan 5, 2017): Tagging this as potentially related to #116.
adam commented 2025-12-29 16:23:49 +01:00
Author
Owner
Copy Link

@candlerb commented on GitHub (Jan 23, 2017):

Would creating a "Custom Field" on the ipam > VLAN object be usable for this? Or if not, maybe the Custom Field functionality can be enhanced to make it usable?

@candlerb commented on GitHub (Jan 23, 2017): Would creating a "Custom Field" on the ipam > VLAN object be usable for this? Or if not, maybe the Custom Field functionality can be enhanced to make it usable?
adam commented 2025-12-29 16:23:49 +01:00
Author
Owner
Copy Link

@DouglasHeriot commented on GitHub (Jan 27, 2017):

I think you’re right – a custom field probably is the right way to do this. Most people don’t need to track ISIDs or VXLANs, so it doesn’t make sense to have it cluttering up the interface.

There are a few enhancements to custom fields that would be good to make it more usable however:

  • #568 bulk import
  • #492 organising columns, or option to display custom fields as columns
  • #609 validator on custom fields (ie. want to restrict ISID and VXLAN to 24-bit positive integer)

But for now, I think custom fields will work well enough for us to get started tracking this information better.
I’ll start investigating how difficult it would be to implement some of these things.

@DouglasHeriot commented on GitHub (Jan 27, 2017): I think you’re right – a custom field probably is the right way to do this. Most people don’t need to track ISIDs or VXLANs, so it doesn’t make sense to have it cluttering up the interface. There are a few enhancements to custom fields that would be good to make it more usable however: * #568 bulk import * #492 organising columns, or option to display custom fields as columns * #609 validator on custom fields (ie. want to restrict ISID and VXLAN to 24-bit positive integer) But for now, I think custom fields will work well enough for us to get started tracking this information better. I’ll start investigating how difficult it would be to implement some of these things.
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#607
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?