Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FHRP Group names #9892

Closed
chrisclarke6710 opened this issue Aug 1, 2022 · 0 comments · Fixed by #10424
Closed

FHRP Group names #9892

chrisclarke6710 opened this issue Aug 1, 2022 · 0 comments · Fixed by #10424
Assignees
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Milestone

Comments

@chrisclarke6710
Copy link

NetBox version

v3.2.5

Feature type

Change to existing functionality

Proposed functionality

Firstly - Netbox is a great product and continues to evolve well.

It would be very useful for FHRP Groups to have a name assigned rather than just numeric ID.
In multi-tenant environment with several (100's) of HA Pair/cluster type devices (eg Active / Passive devices), adding an IP to a HA pair by the groupId is cumbersome as the group ID has to be found first. Even if a name field could be added and then the name just listed alongside the group ID would be immensely helpful.

Use case

FHRP groups are setup currently using description to associated with a pair of devices
In order to add an IP to the FHRP group the Netbox user has to lookup the group id separately first and then edit either the IP or interface and assign the (previously looked up) group IP.

By listing the groups by name (or with a name in brackets with the groupID) the Netbox user wont have to lookup the group ID separately which would make assigning the IP much simpler.

Database changes

Extra field for group name

External dependencies

none

@chrisclarke6710 chrisclarke6710 added the type: feature Introduction of new functionality to the application label Aug 1, 2022
@jeremystretch jeremystretch added the status: accepted This issue has been accepted for implementation label Aug 24, 2022
@jeremystretch jeremystretch added this to the v3.4 milestone Aug 24, 2022
@arthanson arthanson self-assigned this Sep 16, 2022
jeremystretch added a commit that referenced this issue Sep 27, 2022
jsenecal pushed a commit to jsenecal/netbox that referenced this issue Sep 28, 2022
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: accepted This issue has been accepted for implementation type: feature Introduction of new functionality to the application
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants