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

Additional fields for interfaces - bpduguard #6875

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

Originally created by @ITJamie on GitHub (Aug 25, 2022).

NetBox version

v3.2.9

Feature type

Data model extension

Proposed functionality

Additional field on interface model for bpduguard.
selection options:

  • null (default)
  • disabled
  • filtered
  • enabled

Use case

Most networking equipment has the option of bpdu guard/filtering. Having a native config option built into netbox would be nice.

I understand that this could just be a custom field. however it seems like a fairly common config option. similar to recently added poe fields

Database changes

Additional field on interface model

External dependencies

No response

Originally created by @ITJamie on GitHub (Aug 25, 2022). ### NetBox version v3.2.9 ### Feature type Data model extension ### Proposed functionality Additional field on interface model for bpduguard. selection options: - null (default) - disabled - filtered - enabled ### Use case Most networking equipment has the option of bpdu guard/filtering. Having a native config option built into netbox would be nice. I understand that this could just be a custom field. however it seems like a fairly common config option. similar to recently added poe fields ### Database changes Additional field on interface model ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:46:16 +01:00
adam closed this issue 2025-12-29 19:46:16 +01:00
adam commented 2025-12-29 19:46:17 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 25, 2022):

BPDUGuard is a Cisco-proprietary feature and thus not eligible for inclusion into NetBox. Other vendors offer analogous features (e.g. bpdu-block on Junos), however they use different terminology and there are differences in how they operate. This is not something that we can reasonably attempt to model in NetBox.

What I recommend to facilitate automated device configuration is to leverage a tag to identify edge/access ports where configuration of this feature is desired, and infer the desired configuration within the template being rendered.

@jeremystretch commented on GitHub (Aug 25, 2022): BPDUGuard is a Cisco-proprietary feature and thus not eligible for inclusion into NetBox. Other vendors offer analogous features (e.g. `bpdu-block` on Junos), however they use different terminology and there are differences in how they operate. This is not something that we can reasonably attempt to model in NetBox. What I recommend to facilitate automated device configuration is to leverage a tag to identify edge/access ports where configuration of this feature is desired, and infer the desired configuration within the template being rendered.
adam commented 2025-12-29 19:46:17 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Aug 25, 2022):

In addition to tags, you could also store the state of these features in custom fields.

@DanSheps commented on GitHub (Aug 25, 2022): In addition to tags, you could also store the state of these features in custom fields.
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 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#6875
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?