-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
OOB IP bulk import #16801
Comments
Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed. |
Hi Jeremy, The main point of the request is to assign out-of-band IPs during the bulk process. Like when you are importing new IPs you can assign if it is primary or not. I don't know if this is useful for you and your team. |
@PelochoV please modify your original post above to clearly indicate what field(s) you're proposing be added to which bulk import forms. |
This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically. |
This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened. |
NetBox version
v4.0.3
Feature type
New functionality
Proposed functionality
Can assign OOB IP to a server on IP Adress bulk import like you can assign primary ipv4
Use case
Import BMC IPs as OOB IP
Database changes
No response
External dependencies
No response
The text was updated successfully, but these errors were encountered: