Add backup_ip field similar to primary_ip #2450

New Issue

adam · 2025-12-29T18:18:57+01:00

adam commented

2025-12-29 18:18:57 +01:00

Originally created by @dgarros on GitHub (Mar 11, 2019).

Environment

Python version: 3.6
NetBox version: 2.5.7

Proposed Functionality

The proposal is to add support to define an IP per device as backup_ip, implemented in a similar way than primary_ip currently.

Use Case

I can see couple of use cases for this request. In our environment we often have more than 1 interfaces to access a device:

via the out of band management (ipmi for server)
via the production network (can have multiple)

Some devices also have a private and a public IPs

Usually we are using the production interface as the primary IP but in few cases, like when we need to copy large file into the device, it's better to use the OOB interface.
Also in failure scenario, it's useful to be able to access the device on another interface.

The primary IP is very handy because it's returned with the device object and doesn't require an additional query. in our case, the name of the device and the primary IP are retrieved from an ansible dynamic inventory and we can't pull all Ips from all devices.

Database Changes

Not sure

External Dependencies

Originally created by @dgarros on GitHub (Mar 11, 2019). ### Environment * Python version: 3.6 * NetBox version: 2.5.7 ### Proposed Functionality The proposal is to add support to define an IP per device as `backup_ip`, implemented in a similar way than `primary_ip` currently. ### Use Case I can see couple of use cases for this request. In our environment we often have more than 1 interfaces to access a device: - via the out of band management (ipmi for server) - via the production network (can have multiple) > Some devices also have a private and a public IPs Usually we are using the production interface as the primary IP but in few cases, like when we need to copy large file into the device, it's better to use the OOB interface. Also in failure scenario, it's useful to be able to access the device on another interface. The primary IP is very handy because it's returned with the device object and doesn't require an additional query. in our case, the name of the device and the primary IP are retrieved from an ansible dynamic inventory and we can't pull all Ips from all devices. ### Database Changes Not sure ### External Dependencies

adam closed this issue

2025-12-29 18:18:57 +01:00

adam commented

2025-12-29 18:18:58 +01:00

@jeremystretch commented on GitHub (Apr 8, 2019):

It seems like filtering the set of assigned IPs by interface would be much more flexible.

@jeremystretch commented on GitHub (Apr 8, 2019): It seems like filtering the set of assigned IPs by interface would be much more flexible.

adam commented

2025-12-29 18:18:58 +01:00

@candlerb commented on GitHub (Aug 16, 2019):

OOB management interfaces are already marked with a checkbox.

Although you could argue it would be consistent to link it to the device with "primary_oob_ip", that seems pointless when almost always there will only be a single OOB interface with a single IP address on it. I'd say it's simpler to have a computed property on device which extracts this. (It can return null if there's more than one).

It guess it might be nice to show the primary OOB IP address in device listings; however the device list table is already overcrowded and missing more important things, like tags.

@candlerb commented on GitHub (Aug 16, 2019): OOB management interfaces are already marked with a checkbox. Although you could argue it would be consistent to link it to the device with "primary_oob_ip", that seems pointless when almost always there will only be a single OOB interface with a single IP address on it. I'd say it's simpler to have a computed property on device which extracts this. (It can return null if there's more than one). It guess it might be nice to show the primary OOB IP address in device listings; however the device list table is already overcrowded and missing more important things, like [tags](#3064).

adam commented

2025-12-29 18:18:58 +01:00

@jeremystretch commented on GitHub (Dec 13, 2019):

Closing due to inactivity.

@jeremystretch commented on GitHub (Dec 13, 2019): Closing due to inactivity.

Sign in to join this conversation.

Branches Tags

main

update-changelog-comments-docs

feature-removal-issue-type

20911-dropdown

20239-plugin-menu-classes-mutable-state

21097-graphql-id-lookups

feature

fix_module_substitution

20923-dcim-templates

20044-elevation-stuck-lightmode

feature-ip-prefix-link

v4.5-beta1-release

20068-import-moduletype-attrs

20766-fix-german-translation-code-literals

20378-del-script

7604-filter-modifiers-v3

circuit-swap

12318-case-insensitive-uniqueness

20637-improve-device-q-filter

20660-script-load

19724-graphql

20614-update-ruff

14884-script

02496-max-page

19720-macaddress-interface-generic-relation

19408-circuit-terminations-export-templates

20203-openapi-check

fix-19669-api-image-download

7604-filter-modifiers

19275-fixes-interface-bulk-edit

fix-17794-get_field_value_return_list

11507-show-aggregate-and-rir-on-api

9583-add_column_specific_search_field_to_tables

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/netbox#2450