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 "Primary IP" assignment option for OOBM/IDRAC/ILO etc #6302

New Issue
Closed
opened 2025-12-29 19:39:06 +01:00 by adam · 8 comments
adam commented 2025-12-29 19:39:06 +01:00
Owner
Copy Link

Originally created by @ITJamie on GitHub (Apr 6, 2022).

NetBox version

v3.2.0

Feature type

New functionality

Proposed functionality

UI Changes:

  • Create another checkbox for marking an IP as OOBM(Out Of Band Management)/ILO/DRAC/OPENBMC etc (specific term to be chosen). to the assignment view / edit ip view / edit device view

Config:

  • maybe an option in the configuration.py to define if "Primary" ip is OS or is OOBM.

Models:
devices / ipam- additional "primary" ip assignment. lets call this the secondary management ip for now

Use case

Servers (and some newer switches) generally have two types of management.

  • BMC/OOBM/ILO/DRAC/OPENBMC - for directly managing the hardware health, installing new os's etc
  • OS Management IP - the primary ip to connect to the OS / OS Mgmt context

Right now we have to assign one or the other as the "primary" ip.
It would be really useful to have a "secondary" option to allow folks to decide on which suits them more.
For Dedi/Server rental companies the primary would probably be the DRAC/OOBM.
For ISP's / Networking orgs it would probably be the OS Mgmt ip.

Example of newer networking gear coming with drac/ilo style oob mgmt (openbmc): https://www.edge-core.com/productsInfo.php?cls=1&cls2=5&cls3=181&id=334

Database changes

No response

External dependencies

No response

Originally created by @ITJamie on GitHub (Apr 6, 2022). ### NetBox version v3.2.0 ### Feature type New functionality ### Proposed functionality UI Changes: - Create another checkbox for marking an IP as OOBM(Out Of Band Management)/ILO/DRAC/OPENBMC etc (specific term to be chosen). to the assignment view / edit ip view / edit device view Config: - maybe an option in the configuration.py to define if "Primary" ip is OS or is OOBM. Models: devices / ipam- additional "primary" ip assignment. lets call this the secondary management ip for now ### Use case Servers (and some newer switches) generally have two types of management. - BMC/OOBM/ILO/DRAC/OPENBMC - for directly managing the hardware health, installing new os's etc - OS Management IP - the primary ip to connect to the OS / OS Mgmt context Right now we have to assign one or the other as the "primary" ip. It would be really useful to have a "secondary" option to allow folks to decide on which suits them more. For Dedi/Server rental companies the primary would probably be the DRAC/OOBM. For ISP's / Networking orgs it would probably be the OS Mgmt ip. Example of newer networking gear coming with drac/ilo style oob mgmt (openbmc): https://www.edge-core.com/productsInfo.php?cls=1&cls2=5&cls3=181&id=334 ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: duplicate labels 2025-12-29 19:39:06 +01:00
adam closed this issue 2025-12-29 19:39:07 +01:00
adam commented 2025-12-29 19:39:07 +01:00
Author
Owner
Copy Link

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

This would be super useful and seems like a really elegant small change.

@gleeblezoid commented on GitHub (Apr 6, 2022): This would be super useful and seems like a really elegant small change.
adam commented 2025-12-29 19:39:08 +01:00
Author
Owner
Copy Link

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

This would be great, putting more important info on the front device page.

@corriganalan commented on GitHub (Apr 6, 2022): This would be great, putting more important info on the front device page.
adam commented 2025-12-29 19:39:08 +01:00
Author
Owner
Copy Link

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

https://github.com/netbox-community/netbox/issues/8864 this was already proposed, see my comments there on how to do it with custom links.
You could also work with Tags or services instead, if you want.

@martinum4 commented on GitHub (Apr 6, 2022): https://github.com/netbox-community/netbox/issues/8864 this was already proposed, see my comments there on how to do it with custom links. You could also work with Tags or services instead, if you want.
adam commented 2025-12-29 19:39:08 +01:00
Author
Owner
Copy Link

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

Yes Please! This would be a fantastic QoL improvement.

@gifnotgif commented on GitHub (Apr 6, 2022): Yes Please! This would be a fantastic QoL improvement.
adam commented 2025-12-29 19:39:08 +01:00
Author
Owner
Copy Link

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

As noted under #8864, whether an IP address has been designated for our-of-band management depends on the interface to which it has been assigned. NetBox provides the option to designate an interface as a management interface via the mgmt_only boolean: Any IPs assigned to management interfaces can be considered management IPs.

It sounds like you want what has already been proposed under #8137, which would add to the device and VM models a new field designating a particular IP address for out-of-band management.

@jeremystretch commented on GitHub (Apr 6, 2022): As noted under #8864, whether an IP address has been designated for our-of-band management depends on the interface to which it has been assigned. NetBox provides the option to designate an interface as a management interface via the `mgmt_only` boolean: Any IPs assigned to management interfaces can be considered management IPs. It sounds like you want what has already been proposed under #8137, which would add to the device and VM models a new field designating a particular IP address for out-of-band management.
adam commented 2025-12-29 19:39:09 +01:00
Author
Owner
Copy Link

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

That makes sense. Right now internally our teams are split on which is the correct primary ip to assign. The oob ip or the os management ip.
I personally view that the current primary ip is the os mgmt ip and that an oob would be another.

While a computed custom field or link could be a way to work around this. It does feel a bit hacky vs extending the model to account for a pretty common usecase.

Tangent: It would be interesting to be able to attach different "services" to the primary ip vs the oobm ip.

@ITJamie commented on GitHub (Apr 6, 2022): That makes sense. Right now internally our teams are split on which is the correct primary ip to assign. The oob ip or the os management ip. I personally view that the current primary ip is the os mgmt ip and that an oob would be another. While a computed custom field or link could be a way to work around this. It does feel a bit hacky vs extending the model to account for a pretty common usecase. Tangent: It would be interesting to be able to attach different "services" to the primary ip vs the oobm ip.
adam commented 2025-12-29 19:39:09 +01:00
Author
Owner
Copy Link

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

Duplicate of #8137

@DanSheps commented on GitHub (Apr 6, 2022): Duplicate of #8137
adam commented 2025-12-29 19:39:09 +01:00
Author
Owner
Copy Link

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

We should keep all discussion under #8137. I am going to close this out as a duplicate.

@DanSheps commented on GitHub (Apr 6, 2022): We should keep all discussion under #8137. I am going to close this out as a duplicate.
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 status: duplicate 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#6302
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?