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

Ports created in device type not reflected in devices #358

New Issue
Closed
opened 2025-12-29 16:21:16 +01:00 by adam · 7 comments
adam commented 2025-12-29 16:21:16 +01:00
Owner
Copy Link

Originally created by @harsh-kotak on GitHub (Aug 12, 2016).

I created a new device type and added few devices of that type. Then I went to the device type and added console and management port but it did not reflect on the devices I already created. It does reflect on devices I create now. Bug? I would like it to be reflected on all devices created before and after.

Originally created by @harsh-kotak on GitHub (Aug 12, 2016). I created a new device type and added few devices of that type. Then I went to the device type and added console and management port but it did not reflect on the devices I already created. It does reflect on devices I create now. Bug? I would like it to be reflected on all devices created before and after.
adam closed this issue 2025-12-29 16:21:16 +01:00
adam commented 2025-12-29 16:21:17 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 12, 2016):

This behavior is intentional to avoid unintended consequences. From the docs:

Note that assignment of components from templates occurs only at the time of device creation: If you modify the templates of a device type, it will not affect devices which have already been created. However, you always have the option of adding, modifying, or deleting components of existing devices individually.

@jeremystretch commented on GitHub (Aug 12, 2016): This behavior is intentional to avoid unintended consequences. From [the docs](http://netbox.readthedocs.io/en/latest/data-model/dcim/#device-types): > Note that assignment of components from templates occurs only at the time of device creation: If you modify the templates of a device type, it will not affect devices which have already been created. However, you always have the option of adding, modifying, or deleting components of existing devices individually.
adam commented 2025-12-29 16:21:17 +01:00
Author
Owner
Copy Link

@harsh-kotak commented on GitHub (Aug 12, 2016):

Can we have an option to select if we want to reflect the template on all the devices or only for future devices. This will save a lot of effort for people like me who have already created 150 devices.

@harsh-kotak commented on GitHub (Aug 12, 2016): Can we have an option to select if we want to reflect the template on all the devices or only for future devices. This will save a lot of effort for people like me who have already created 150 devices.
adam commented 2025-12-29 16:21:17 +01:00
Author
Owner
Copy Link

@LBegnaud commented on GitHub (Aug 12, 2016):

you can bulk-add interfaces from the devices listing

select multiple devices, click add interface

@LBegnaud commented on GitHub (Aug 12, 2016): you can bulk-add interfaces from the devices listing select multiple devices, click add interface
adam commented 2025-12-29 16:21:18 +01:00
Author
Owner
Copy Link

@harsh-kotak commented on GitHub (Aug 12, 2016):

Thank you. This helps in adding interfaces (which sometimes work and sometimes doesn't) but not console ports.

@harsh-kotak commented on GitHub (Aug 12, 2016): Thank you. This helps in adding interfaces (which sometimes work and sometimes doesn't) but not console ports.
adam commented 2025-12-29 16:21:18 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 12, 2016):

To be clear, device types are supposed to be defined once and rarely (if ever) modified. A device type represents a make and model of physical device, which never changes. For instance, every Juniper EX4300-48T ever made has the exact same console port, power supplies, and interfaces. There should be no need to ever modify these unless you made a mistake when originally creating them (but I'm hoping to mitigate that in the near future with #451).

@jeremystretch commented on GitHub (Aug 12, 2016): To be clear, device types are supposed to be defined once and rarely (if ever) modified. A device type represents a make and model of physical device, which never changes. For instance, every Juniper EX4300-48T ever made has the exact same console port, power supplies, and interfaces. There should be no need to ever modify these unless you made a mistake when originally creating them (but I'm hoping to mitigate that in the near future with #451).
adam commented 2025-12-29 16:21:18 +01:00
Author
Owner
Copy Link

@padavrexi commented on GitHub (Oct 2, 2016):

Just a quick heads up: at least on v1.6.2, when creating a new device type, the buttons to add interfaces/console ports/power ports/device bays are missing. In order to reinstate them, I had to go to admin site, add a dummy template and then go back. Same thing works fine on a v1.1.0 installation (not sure about interims).

@padavrexi commented on GitHub (Oct 2, 2016): Just a quick heads up: at least on v1.6.2, when creating a new device type, the buttons to add interfaces/console ports/power ports/device bays are missing. In order to reinstate them, I had to go to admin site, add a dummy template and then go back. Same thing works fine on a v1.1.0 installation (not sure about interims).
adam commented 2025-12-29 16:21:18 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 3, 2016):

See #591 for above. Will be fixed shortly.

@jeremystretch commented on GitHub (Oct 3, 2016): See #591 for above. Will be fixed shortly.
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
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#358
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?