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

Storage (or other devices/configurations) where there is an "Cluster-mgmt IP" and nodes underneath. #6171

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

Originally created by @airborneric on GitHub (Mar 4, 2022).

NetBox version

v2.9.3

Feature type

New functionality

Proposed functionality

Need to be able to have a cluster management IP "float" to all nodes under that cluster. Storage needs to have a container or virtual cluster that is not locked to one rack

For example NetApp Cluster 01 starts as a 2 node A800.

cluster-mgmt IP can be on any node e0M.

nodes 01-24 all have an e0M management port and IP (usually on the same subnet, but not always)

Currently, if I add and new NetApp system, that 2 node ha-pair is considered a cluster. It is physically located in rack-X. I need to add capacity, I install another NetApp system in rack-Y. There is no way to expand that cluster to include the newly installed hardware. I now have a NetApp Cluster 01, and NetApp Cluster 02 in Netbox, when in reality, it is still NetApp Cluster 01, with 2 more nodes added to it.

Use case

Any enterprise level users needs this functionality. VMware has a similar case where vCenter is the primary IP to manage all the nodes in the cluster, all those nodes are not necessarily in the same rack.

Maybe this already exists, but I am not finding any examples of how to accomplish this inside of Netbox, and only 1 discussion of this issue. (referenced)

Database changes

No response

External dependencies

No response

Originally created by @airborneric on GitHub (Mar 4, 2022). ### NetBox version v2.9.3 ### Feature type New functionality ### Proposed functionality Need to be able to have a cluster management IP "float" to all nodes under that cluster. Storage needs to have a container or virtual cluster that is not locked to one rack For example NetApp Cluster 01 starts as a 2 node A800. cluster-mgmt IP can be on any node e0M. nodes 01-24 all have an e0M management port and IP (usually on the same subnet, but not always) Currently, if I add and new NetApp system, that 2 node ha-pair is considered a cluster. It is physically located in rack-X. I need to add capacity, I install another NetApp system in rack-Y. There is no way to expand that cluster to include the newly installed hardware. I now have a NetApp Cluster 01, and NetApp Cluster 02 in Netbox, when in reality, it is still NetApp Cluster 01, with 2 more nodes added to it. ### Use case Any enterprise level users needs this functionality. VMware has a similar case where vCenter is the primary IP to manage all the nodes in the cluster, all those nodes are not necessarily in the same rack. Maybe this already exists, but I am not finding any examples of how to accomplish this inside of Netbox, and only 1 discussion of this issue. (referenced) ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:37:40 +01:00
adam closed this issue 2025-12-29 19:37:40 +01:00
adam commented 2025-12-29 19:37:41 +01:00
Author
Owner
Copy Link

@karolyczovek commented on GitHub (Mar 9, 2022):

model it as FHRP assigned IP

@karolyczovek commented on GitHub (Mar 9, 2022): model it as FHRP assigned IP
adam commented 2025-12-29 19:37:41 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 6, 2022):

v2.9.3

I'd strongly recommend upgrading to NetBox v3.2 as many new features have been released that are likely to better address your needs. As mentioned, FHRP groups seem ideal for this.

@jeremystretch commented on GitHub (Apr 6, 2022): > v2.9.3 I'd strongly recommend upgrading to NetBox v3.2 as many new features have been released that are likely to better address your needs. As mentioned, FHRP groups seem ideal for this.
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#6171
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?