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

Clarification on devices, device types and how interfaces work #17

New Issue
Closed
opened 2025-12-29 15:29:43 +01:00 by adam · 3 comments
adam commented 2025-12-29 15:29:43 +01:00
Owner
Copy Link

Originally created by @bellwood on GitHub (Jun 27, 2016).

I've added a device type for one of my edge routers and added all the line card ports.

When I add the actual device and associate it to the device type I am left needing to define all the ports again.

What is the purpose of populating ports on the device type if I'll need to redefine the ports when creating the device?

I presumed device type was a template such that when associating it to an actual device the interfaces would be there by default?

Thanks =)

Originally created by @bellwood on GitHub (Jun 27, 2016). I've added a device type for one of my edge routers and added all the line card ports. When I add the actual device and associate it to the device type I am left needing to define all the ports again. What is the purpose of populating ports on the device type if I'll need to redefine the ports when creating the device? I presumed device type was a template such that when associating it to an actual device the interfaces would be there by default? Thanks =)
adam closed this issue 2025-12-29 15:29:44 +01:00
adam commented 2025-12-29 15:29:44 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 27, 2016):

I presumed device type was a template such that when associating it to an actual device the interfaces would be there by default?

That is the intended behavior: You define a device type with its console/power ports and interfaces, and each instantiation of that device type should have those components created automatically.

It seems to be working normally as far as I can tell. Can you walk me through exactly what you did?

@jeremystretch commented on GitHub (Jun 27, 2016): > I presumed device type was a template such that when associating it to an actual device the interfaces would be there by default? That is the intended behavior: You define a device type with its console/power ports and interfaces, and each instantiation of that device type should have those components created automatically. It seems to be working normally as far as I can tell. Can you walk me through exactly what you did?
adam commented 2025-12-29 15:29:45 +01:00
Author
Owner
Copy Link

@bellwood commented on GitHub (Jun 27, 2016):

@jeremystretch I ended up deleting/recreating and interfaces showed up as intended

Thanks... I'll try to slow down on these...

Trying to figure out the workflow with mandatory fields, menu positions, etc.

@bellwood commented on GitHub (Jun 27, 2016): @jeremystretch I ended up deleting/recreating and interfaces showed up as intended Thanks... I'll try to slow down on these... Trying to figure out the workflow with mandatory fields, menu positions, etc.
adam commented 2025-12-29 15:29:45 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 27, 2016):

No worries, thanks for all the feedback!

@jeremystretch commented on GitHub (Jun 27, 2016): No worries, thanks for all the feedback!
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#17
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?