starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Support to move interface to another device #5410

New Issue
Closed
opened 2025-12-29 19:27:40 +01:00 by adam · 6 comments
adam commented 2025-12-29 19:27:40 +01:00
Owner
Copy Link

Originally created by @ypid on GitHub (Sep 22, 2021).

NetBox version

v3.0.3

Feature type

New functionality

Proposed functionality

Currently an Interface is bound to a Device. Interfaces cannot be moved to another Device while in reality, this is possible. For Inventory Items, moving between devices is already supported.

A question is how to handle Interfaces with Cables plugged in. I would suggest to not allow to move such Interfaces. Just like in reality, an Interface (card) is not moved with a cable plugged in.

Front/Rear Ports, this could also be possible in reality (moving Keystones), but I expect this to get tricky so lets leave it out of this feature request.

Use case

A Interface was installed in Device A and is physically removed from it and installed in Device B.

Database changes

No.

External dependencies

No.

Originally created by @ypid on GitHub (Sep 22, 2021). ### NetBox version v3.0.3 ### Feature type New functionality ### Proposed functionality Currently an Interface is bound to a Device. Interfaces cannot be moved to another Device while in reality, this is possible. For Inventory Items, moving between devices is already supported. A question is how to handle Interfaces with Cables plugged in. I would suggest to not allow to move such Interfaces. Just like in reality, an Interface (card) is not moved with a cable plugged in. Front/Rear Ports, this could also be possible in reality (moving Keystones), but I expect this to get tricky so lets leave it out of this feature request. ### Use case A Interface was installed in Device A and is physically removed from it and installed in Device B. ### Database changes No. ### External dependencies No.
adam added the type: feature label 2025-12-29 19:27:40 +01:00
adam closed this issue 2025-12-29 19:27:40 +01:00
adam commented 2025-12-29 19:27:40 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Sep 23, 2021):

A question is how to handle Interfaces with Cables plugged in. I would suggest to not allow to move such Interfaces. Just like in reality, an Interface (card) is not moved with a cable plugged in.

Netbox replicates real-life scenarios in most instances. With Inventory Items, most (Fans, PSU, etc) can be removed and moved. However an interface on a switch can 99% of the time never be removed (exception is a expansion module like NM's for Cisco, however it is easier to handle the majority then the exceptions).

So, the process of how to handle this is simple: You create new interfaces, remove the cables and re-attach them to the new interface.

This likely isn't going to be a feature we take up. We might handle NM's via a different PR that deals with "expansion" equipment, can't remember the number but it is slated I think for 3.1?

@DanSheps commented on GitHub (Sep 23, 2021): > A question is how to handle Interfaces with Cables plugged in. I would suggest to not allow to move such Interfaces. Just like in reality, an Interface (card) is not moved with a cable plugged in. Netbox replicates real-life scenarios in most instances. With Inventory Items, most (Fans, PSU, etc) can be removed and moved. However an interface on a switch can 99% of the time never be removed (exception is a expansion module like NM's for Cisco, however it is easier to handle the majority then the exceptions). So, the process of how to handle this is simple: You create new interfaces, remove the cables and re-attach them to the new interface. This likely isn't going to be a feature we take up. We might handle NM's via a different PR that deals with "expansion" equipment, can't remember the number but it is slated I think for 3.1?
adam commented 2025-12-29 19:27:40 +01:00
Author
Owner
Copy Link

@ypid commented on GitHub (Sep 23, 2021):

I agree that with network equipment like switches and routers, moving Interfaces is uncommon. However, for a Server Device, it happens that you move NICs to another server. The reason I am proposing to support moving is that some attributes like "MAC address" and possibly "Label" and "Description" are attached to the physical NIC.

@ypid commented on GitHub (Sep 23, 2021): I agree that with network equipment like switches and routers, moving Interfaces is uncommon. However, for a Server Device, it happens that you move NICs to another server. The reason I am proposing to support moving is that some attributes like "MAC address" and possibly "Label" and "Description" are attached to the physical NIC.
adam commented 2025-12-29 19:27:41 +01:00
Author
Owner
Copy Link

@ziggekatten commented on GitHub (Sep 23, 2021):

This is where you create a custom script where you select interface, preserve necessary info, delete it on current device and add it to the new device with a press of a button

No need to change basic features in Netbox when there are tools to handle the outliers.

This is the real feature of Netbox. There is almost always a way to solve the challenges and adapt it to your business need.

@ziggekatten commented on GitHub (Sep 23, 2021): This is where you create a custom script where you select interface, preserve necessary info, delete it on current device and add it to the new device with a press of a button No need to change basic features in Netbox when there are tools to handle the outliers. This is the real feature of Netbox. There is almost always a way to solve the challenges and adapt it to your business need.
adam commented 2025-12-29 19:27:41 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Sep 24, 2021):

This is where you create a custom script where you select interface, preserve necessary info, delete it on current device and add it to the new device with a press of a button

This is the way

@DanSheps commented on GitHub (Sep 24, 2021): > This is where you create a custom script where you select interface, preserve necessary info, delete it on current device and add it to the new device with a press of a button This is the way
adam commented 2025-12-29 19:27:41 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 26, 2021):

I'm afraid implementing the proposed simply would not be worth the development effort required to do so reliably. As others have mentioned, the preferred approach is to replicate & delete interfaces in the relatively infrequent cases where this is needed.

@jeremystretch commented on GitHub (Sep 26, 2021): I'm afraid implementing the proposed simply would not be worth the development effort required to do so reliably. As others have mentioned, the preferred approach is to replicate & delete interfaces in the relatively infrequent cases where this is needed.
adam commented 2025-12-29 19:27:42 +01:00
Author
Owner
Copy Link

@ypid commented on GitHub (Sep 26, 2021):

This is where you create a custom script where you select interface, preserve necessary info, delete it on current device and add it to the new device with a press of a button.

Nice idea. I have not considered that. I will do that and update this comment when I have something working.

@ypid commented on GitHub (Sep 26, 2021): > This is where you create a custom script where you select interface, preserve necessary info, delete it on current device and add it to the new device with a press of a button. Nice idea. I have not considered that. I will do that and update this comment when I have something working.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label type: feature
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#5410
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?