IPMI Interface #3604

Closed
opened 2025-12-29 18:30:06 +01:00 by adam · 5 comments
Owner

Originally created by @Sislik on GitHub (Apr 25, 2020).

Environment

  • Python version: 3.6.4
  • NetBox version: 2.8

Proposed Functionality

Add IMPI interface to default selections of interfaces types

Use Case

Each physical server is having IPMI interface (iLO, iDRAC, iLOM). These interfaces are used for management only and there is no point of having for them specific as 100base-tx or 1000base-t. Also it will be easier for searching for these IPMI interfaces across all servers.

Database Changes

External Dependencies

Originally created by @Sislik on GitHub (Apr 25, 2020). <!-- NOTE: IF YOUR ISSUE DOES NOT FOLLOW THIS TEMPLATE, IT WILL BE CLOSED. This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.6.4 * NetBox version: 2.8 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Add IMPI interface to default selections of interfaces types <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case Each physical server is having IPMI interface (iLO, iDRAC, iLOM). These interfaces are used for management only and there is no point of having for them specific as 100base-tx or 1000base-t. Also it will be easier for searching for these IPMI interfaces across all servers. <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies
adam closed this issue 2025-12-29 18:30:06 +01:00
Author
Owner

@tioan commented on GitHub (Apr 25, 2020):

First i think you mean IPMI not IMPI.
Second this issue is needless because IPMI interface also have an interface type.

@tioan commented on GitHub (Apr 25, 2020): First i think you mean IPMI not IMPI. Second this issue is needless because IPMI interface also have an interface type.
Author
Owner

@Sislik commented on GitHub (Apr 25, 2020):

Yes it is having interface type, but all depend for the whole purpose of the IPMI (thx for correction :)) It can then be up to the user if he want to have them specified by exact type of interface or just by basic definition.
As i want to be adding by scripts around 100k devices (just discovery by ipmitool on linux or powershell in windows) im just more than happy to receive the IP/Mask/MAC and that it is IPMI.
Anyway it is just suggestion :)

@Sislik commented on GitHub (Apr 25, 2020): Yes it is having interface type, but all depend for the whole purpose of the IPMI (thx for correction :)) It can then be up to the user if he want to have them specified by exact type of interface or just by basic definition. As i want to be adding by scripts around 100k devices (just discovery by ipmitool on linux or powershell in windows) im just more than happy to receive the IP/Mask/MAC and that it is IPMI. Anyway it is just suggestion :)
Author
Owner

@DanSheps commented on GitHub (Apr 25, 2020):

IPMI is not an interface type, we only track interface types like ethernet

@DanSheps commented on GitHub (Apr 25, 2020): IPMI is not an interface type, we only track interface types like ethernet
Author
Owner

@jeremystretch commented on GitHub (Apr 27, 2020):

The interface model also has a "OOB management" boolean field specifically for this purpose.

@jeremystretch commented on GitHub (Apr 27, 2020): The interface model also has a "OOB management" boolean field specifically for this purpose.
Author
Owner

@schmitmd commented on GitHub (Apr 30, 2020):

@jeremystretch , I know this issue is closed, I just want to ask a related question: Is there already a way to add something like a Custom Link to a /dcim/device/ object that would do something like open the OOB management URL? I'm not seeing anything that I can use in the existing device model that would help my Jinja2 template be able to get the correct data for this (except primary_ip which isn't quite right). Am I missing something? Would you suggest I make a new issue for this?

Edit: Nevermind, please disregard. I found the answer I was seeking in the mailing list archives at https://groups.google.com/forum/#!searchin/netbox-discuss/ipmi$20custom$20link|sort:date/netbox-discuss/5IjoocvDCCM/LBk8hpocBwAJ . I will try to make a pull request for the documentation to clarify to others that the templating can be used to query other related objects, not just utilize the contents of that particular object model. Sorry!

@schmitmd commented on GitHub (Apr 30, 2020): @jeremystretch , I know this issue is closed, I just want to ask a related question: Is there already a way to add something like a Custom Link to a /dcim/device/ object that would do something like open the OOB management URL? I'm not seeing anything that I can use in the existing device model that would help my Jinja2 template be able to get the correct data for this (except primary_ip which isn't quite right). Am I missing something? Would you suggest I make a new issue for this? Edit: Nevermind, please disregard. I found the answer I was seeking in the mailing list archives at https://groups.google.com/forum/#!searchin/netbox-discuss/ipmi$20custom$20link|sort:date/netbox-discuss/5IjoocvDCCM/LBk8hpocBwAJ . I will try to make a pull request for the documentation to clarify to others that the templating can be used to query other related objects, not just utilize the contents of that particular object model. Sorry!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#3604