Option to select ip directly from prefix/vlan for management primary ip #2350

Closed
opened 2025-12-29 17:25:09 +01:00 by adam · 4 comments
Owner

Originally created by @deku-m on GitHub (Feb 6, 2019).

Environment

  • Python version: 3.5.2
  • NetBox version: 2.5.5

Proposed Functionality

In our environment we configure on the switch the vlan interface with a IP address. This is then reachable as management. So if it is possible, that we directly select the IP address when editing the switch for its primary ip and then the option to select the ip from the prefix/vlan. As now you first need to configure an interface with an IP address. So we now configure them on the port channel.

Use Case

As above

Database Changes

Don't know what has to change

External Dependencies

N/A

Originally created by @deku-m on GitHub (Feb 6, 2019). <!-- NOTE: 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.5.2<!-- Example: 3.5.4 --> * NetBox version: 2.5.5<!-- Example: 2.3.6 --> <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality In our environment we configure on the switch the vlan interface with a IP address. This is then reachable as management. So if it is possible, that we directly select the IP address when editing the switch for its primary ip and then the option to select the ip from the prefix/vlan. As now you first need to configure an interface with an IP address. So we now configure them on the port channel. <!-- 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 As above <!-- 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 Don't know what has to change <!-- 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 N/A
adam closed this issue 2025-12-29 17:25:09 +01:00
Author
Owner

@jeremystretch commented on GitHub (Feb 6, 2019):

I don't follow what's being proposed here. Could you elaborate on exactly what you're trying to do please?

@jeremystretch commented on GitHub (Feb 6, 2019): I don't follow what's being proposed here. Could you elaborate on exactly what you're trying to do please?
Author
Owner

@deku-m commented on GitHub (Feb 6, 2019):

To clearify a bit hope this helps:
When you edit a device you can assign a ip address under the section management as primary/secondary IP. This is only allowed when you assign this to an interface for example a portchannel, etc. Then you can select this address at the primary ip.

What im trying to explain is, if it is possible to assign it directly when you enter or select the ip address as primary IP. So that it doesn't have to be assigned to a interface. Just directly select from the ip addresses. As in our environment we didn`t assign it to the a physical interface but assigned it to a vlan interface (management).

@deku-m commented on GitHub (Feb 6, 2019): To clearify a bit hope this helps: When you edit a device you can assign a ip address under the section management as primary/secondary IP. This is only allowed when you assign this to an interface for example a portchannel, etc. Then you can select this address at the primary ip. What im trying to explain is, if it is possible to assign it directly when you enter or select the ip address as primary IP. So that it doesn't have to be assigned to a interface. Just directly select from the ip addresses. As in our environment we didn`t assign it to the a physical interface but assigned it to a vlan interface (management).
Author
Owner

@DanSheps commented on GitHub (Feb 6, 2019):

@deku-m

This is a support question and should be redirected to the mailing list or the NetworkToCode Slack in the #netbox channel

You would want to model that in Netbox, by naming it whatever it is named in your switch. For example, on Cisco switches, you would have the following configuration:

interface Vlan1212
 ip address 10.12.12.1 255.255.255.0

You would model this in Netbox by creating a interface named Vlan1212 and assigning it the IP address 10.12.12.1/24. The type would be "Virtual".

@DanSheps commented on GitHub (Feb 6, 2019): @deku-m This is a support question and should be redirected to the [mailing list](https://groups.google.com/forum/#!forum/netbox-discuss) or the [NetworkToCode Slack](https://networktocode.slack.com/) in the #netbox channel You would want to model that in Netbox, by naming it whatever it is named in your switch. For example, on Cisco switches, you would have the following configuration: ``` interface Vlan1212 ip address 10.12.12.1 255.255.255.0 ``` You would model this in Netbox by creating a interface named Vlan1212 and assigning it the IP address 10.12.12.1/24. The type would be "Virtual".
Author
Owner

@jeremystretch commented on GitHub (Feb 6, 2019):

As @DanSheps points out, IP addresses must be assigned to an interface before they can be designated as the primary IP for a device. There is no mechanism by which to create and designate an IP in one action, as that would greatly complicate validation.

@jeremystretch commented on GitHub (Feb 6, 2019): As @DanSheps points out, IP addresses must be assigned to an interface before they can be designated as the primary IP for a device. There is no mechanism by which to create _and_ designate an IP in one action, as that would greatly complicate validation.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#2350