Clone a device including the same installed modules #8239

New Issue

adam · 2025-12-29T20:34:13+01:00

adam commented

2025-12-29 20:34:13 +01:00

Originally created by @lucatortiglione on GitHub (Jun 23, 2023).

NetBox version

v3.5.4

Feature type

New functionality

Proposed functionality

Hi what about to clone a device including the same installed modules ?

Use case

It's useful when i have 30 devices with the same installed modules, i don't have to add them 1 by 1

Database changes

I don't know

External dependencies

I don't know

Originally created by @lucatortiglione on GitHub (Jun 23, 2023). ### NetBox version v3.5.4 ### Feature type New functionality ### Proposed functionality Hi what about to clone a device including the same installed modules ? ### Use case It's useful when i have 30 devices with the same installed modules, i don't have to add them 1 by 1 ### Database changes I don't know ### External dependencies I don't know

adam added the type: feature label 2025-12-29 20:34:13 +01:00

adam closed this issue

2025-12-29 20:34:13 +01:00

adam commented

2025-12-29 20:34:14 +01:00

@martinum4 commented on GitHub (Jun 26, 2023):

(Edited Crosspost from my discussion post https://github.com/netbox-community/netbox/discussions/12957#discussioncomment-6263383)

I don't have the correct words for it, but some kind of "collection"/"set"/"superset" for devicetypes that nests them together with modules and inventory items would be nice.

Example-Problem: You order a lot of two different server configurations (but same base model) from one vendor, one contains better PSUs (Tracked in NetBox as Module) and accelerator cards (which you want to track as inventory item since they cost you quite a lot).

You then would create two "sets", one containing the basic server and normal PSUs and some kind of order-identifier and the other contains the base server, a different order-identifier, the better PSUs and your accelerator cards.

Rest of the process when importing a device works just as normal, but instead of selecting the base-server devicetype and populating them afterwards you get to select the new collections instead, after import all the modules and inventory items will be included automatically.

@martinum4 commented on GitHub (Jun 26, 2023): (Edited Crosspost from my discussion post https://github.com/netbox-community/netbox/discussions/12957#discussioncomment-6263383) I don't have the correct words for it, but some kind of "collection"/"set"/"superset" for devicetypes that nests them together with modules and inventory items would be nice. Example-Problem: You order a lot of two different server configurations (but same base model) from one vendor, one contains better PSUs (Tracked in NetBox as Module) and accelerator cards (which you want to track as inventory item since they cost you quite a lot). You then would create two "sets", one containing the basic server and normal PSUs and some kind of order-identifier and the other contains the base server, a different order-identifier, the better PSUs and your accelerator cards. Rest of the process when importing a device works just as normal, but instead of selecting the base-server devicetype and populating them afterwards you get to select the new collections instead, after import all the modules and inventory items will be included automatically.

adam commented

2025-12-29 20:34:14 +01:00

@abhi1693 commented on GitHub (Jun 26, 2023):

This does not sound like a good idea as you would also replicate the serial numbers and asset tags. Both these fields will duplicate the data and increase the effort to fix these after the cloning is finished.

@abhi1693 commented on GitHub (Jun 26, 2023): This does not sound like a good idea as you would also replicate the serial numbers and asset tags. Both these fields will duplicate the data and increase the effort to fix these after the cloning is finished.

adam commented

2025-12-29 20:34:15 +01:00

@lucatortiglione commented on GitHub (Jun 26, 2023):

This does not sound like a good idea as you would also replicate the serial numbers and asset tags. Both these fields will duplicate the data and increase the effort to fix these after the cloning is finished.

Maybe the programmers can avoid duplicating serial number field :)

@lucatortiglione commented on GitHub (Jun 26, 2023): > This does not sound like a good idea as you would also replicate the serial numbers and asset tags. Both these fields will duplicate the data and increase the effort to fix these after the cloning is finished. > This does not sound like a good idea as you would also replicate the serial numbers and asset tags. Both these fields will duplicate the data and increase the effort to fix these after the cloning is finished. Maybe the programmers can avoid duplicating serial number field :)

adam commented

2025-12-29 20:34:15 +01:00

@laimaretto commented on GitHub (Jun 30, 2023):

This would definitively be a very good feature.

@laimaretto commented on GitHub (Jun 30, 2023): This would definitively be a very good feature.

adam commented

2025-12-29 20:34:15 +01:00

@marcusyuri commented on GitHub (Jul 27, 2023):

I think that it was a wonderfull ideia, and may be implemented using the following steps:

(1) Clone the device, except the serial numbers / asset tags
(2) Clone the inventory itens attached to the device, except the serial numbers / asset tags
(3) Populate the new device with the same module types that the original device. Note that this will not fetch the serial/asset tags
(4) Clone the inventory itens attached to the original modules, except the serial numbers / asset tags, and assign them to the new created modules.

;)

@marcusyuri commented on GitHub (Jul 27, 2023): I think that it was a wonderfull ideia, and may be implemented using the following steps: (1) Clone the device, except the serial numbers / asset tags (2) Clone the inventory itens attached to the device, except the serial numbers / asset tags (3) Populate the new device with the same module types that the original device. Note that this will not fetch the serial/asset tags (4) Clone the inventory itens attached to the original modules, except the serial numbers / asset tags, and assign them to the new created modules. ;)

adam commented

2025-12-29 20:34:16 +01:00

@jeremystretch commented on GitHub (Oct 13, 2023):

It sounds like there's some interest in the general idea, however this issue does not come close to embodying an actionable feature request, so I'm going to close is out. If anyone would like to spend some time drafting a detailed implementation proposal, you are welcome to present it for consideration in a new issue.

@jeremystretch commented on GitHub (Oct 13, 2023): It sounds like there's some interest in the general idea, however this issue does not come close to embodying an actionable feature request, so I'm going to close is out. If anyone would like to spend some time drafting a detailed implementation proposal, you are welcome to present it for consideration in a new issue.

Sign in to join this conversation.

Branches Tags

main

21102-fix-graphiql-explorer

update-changelog-comments-docs

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#8239