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

Allow assignment of FHRP groups to tenants, sites, VLAN groups and vlans #6230

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

Originally created by @stephanblanke on GitHub (Mar 18, 2022).

NetBox version

v3.1.10-dev

Feature type

Change to existing functionality

Proposed functionality

It should be possible to assign FHRP groups to tenants, sites, VLAN groups and VLANs. This should resemble the way it is implemented for prefixes: Each FHRP group can be assigned to zero to one site, zero to one VLAN group, zero to one VLAN (contained in the assigned VLAN group). The assigned site, VLAN group and VLAN should be added as a column to the table view of FHRP groups.

I am willing to create a PR for this.

Use case

Currently FHRP groups with the same number, protocol and authentication properties cannot be further distinguished. It is pretty common to number an FHRP group by the associated VLAN ID on a specific site. Lets pretend we have an enterprise network with 100 sites, with each site resembling the same VLAN structure. This would lead to multiple FHRP groups with the same id, type and probably authentication properties. By allowing to assign FHRP Groups to organizational elements (sites, vlan groups and vlans) it is easy to find the FHRP group in question. This would make it much easier to automatically create, edit and delete those FHRP groups.

Database changes

Foreign keys for assigned site, vlan group & vlan

External dependencies

No response

Originally created by @stephanblanke on GitHub (Mar 18, 2022). ### NetBox version v3.1.10-dev ### Feature type Change to existing functionality ### Proposed functionality It should be possible to assign FHRP groups to tenants, sites, VLAN groups and VLANs. This should resemble the way it is implemented for prefixes: Each FHRP group can be assigned to zero to one site, zero to one VLAN group, zero to one VLAN (contained in the assigned VLAN group). The assigned site, VLAN group and VLAN should be added as a column to the table view of FHRP groups. I am willing to create a PR for this. ### Use case Currently FHRP groups with the same number, protocol and authentication properties cannot be further distinguished. It is pretty common to number an FHRP group by the associated VLAN ID on a specific site. Lets pretend we have an enterprise network with 100 sites, with each site resembling the same VLAN structure. This would lead to multiple FHRP groups with the same id, type and probably authentication properties. By allowing to assign FHRP Groups to organizational elements (sites, vlan groups and vlans) it is easy to find the FHRP group in question. This would make it much easier to automatically create, edit and delete those FHRP groups. ### Database changes Foreign keys for assigned site, vlan group & vlan ### External dependencies _No response_
adam added the type: featurepending closure labels 2025-12-29 19:38:18 +01:00
adam closed this issue 2025-12-29 19:38:19 +01:00
adam commented 2025-12-29 19:38:19 +01:00
Author
Owner
Copy Link

@stephanblanke commented on GitHub (Mar 19, 2022):

Since I need this feature in my local installation, I already implemented this:
https://github.com/stephanblanke/netbox/tree/8914-fhrp-assignments

When this issue is accepted, I will create a PR.

@stephanblanke commented on GitHub (Mar 19, 2022): Since I need this feature in my local installation, I already implemented this: https://github.com/stephanblanke/netbox/tree/8914-fhrp-assignments When this issue is accepted, I will create a PR.
adam commented 2025-12-29 19:38:19 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Mar 21, 2022):

It should be possible to assign FHRP groups to tenants, sites, VLAN groups and VLANs.

This would be redundant to the association which exist via assigned IP addresses and (via their interfaces) devices/VMs.

Currently FHRP groups with the same number, protocol and authentication properties cannot be further distinguished.

They can be distinguished by the interfaces and IP addresses with which they are associated.

@jeremystretch commented on GitHub (Mar 21, 2022): > It should be possible to assign FHRP groups to tenants, sites, VLAN groups and VLANs. This would be redundant to the association which exist via assigned IP addresses and (via their interfaces) devices/VMs. > Currently FHRP groups with the same number, protocol and authentication properties cannot be further distinguished. They can be distinguished by the interfaces and IP addresses with which they are associated.
adam commented 2025-12-29 19:38:19 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 21, 2022):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our contributing guide.

@github-actions[bot] commented on GitHub (May 21, 2022): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 19:38:20 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 20, 2022):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Jun 20, 2022): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure 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#6230
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?