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

Add Cassettes (fiber/copper) device types to Netbox #333

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

Originally created by @swickstrom on GitHub (Aug 5, 2016).

Request to add cassette device types.
The user would create the cassette device type in two different racks and then specify the interconnection trace the cassette group hosts.
e.g.:
The user would create a cassette in rack101, specify the cassettes mate was in rack 102. Next they would specify the two device interfaces the cassettes host i.e.: serial.console.server.01-rack101/port.01 is connected to server.01-rack102/serial.01.
So cassette.01-rack101/port.01 would show serial.console.server.01-rack101/port.01 and cassette.02-rack102/port.01 would show server.01-rack102/serial.01.
It is most important that the cassette interfaces have no associated type; that they would be able to host whatever interface type the user specifies; this would allow representation of serial-over-RJ45 and Ethernet over RJ45 in the same interface list.

Originally created by @swickstrom on GitHub (Aug 5, 2016). Request to add cassette device types. The user would create the cassette device type in two different racks and then specify the interconnection trace the cassette group hosts. e.g.: The user would create a cassette in rack101, specify the cassettes mate was in rack 102. Next they would specify the two device interfaces the cassettes host i.e.: `serial.console.server.01-rack101/port.01` is connected to `server.01-rack102/serial.01`. So `cassette.01-rack101/port.01` would show `serial.console.server.01-rack101/port.01` and `cassette.02-rack102/port.01` would show `server.01-rack102/serial.01`. It is most important that the cassette interfaces have no associated type; that they would be able to host whatever interface type the user specifies; this would allow representation of serial-over-RJ45 and Ethernet over RJ45 in the same interface list.
adam added the status: duplicate label 2025-12-29 16:21:00 +01:00
adam closed this issue 2025-12-29 16:21:00 +01:00
adam commented 2025-12-29 16:21:01 +01:00
Author
Owner
Copy Link

@swickstrom commented on GitHub (Aug 5, 2016):

This issue could also be solved by creating a passthrough interface type.
A passthrough interface setup would look like:

Device.01|Interface.01->Cassette.01|Passthrough.01<-->Cassette.02|Passthrough.01<-Device.02|Interface.01

This means the passthrough interface type would have connections on either side to illustrate the full linkage.
It is imperative that the passthrough interface type have no required port type; allowing anything to be represented as passed through (this includes console/management/interface/PSU connections).

@swickstrom commented on GitHub (Aug 5, 2016): This issue could also be solved by creating a `passthrough` interface type. A `passthrough` interface setup would look like: ``` Device.01|Interface.01->Cassette.01|Passthrough.01<-->Cassette.02|Passthrough.01<-Device.02|Interface.01 ``` This means the `passthrough` interface type would have connections on either side to illustrate the full linkage. It is imperative that the `passthrough` interface type have no required port type; allowing anything to be represented as passed through (this includes console/management/interface/PSU connections).
adam commented 2025-12-29 16:21:01 +01:00
Author
Owner
Copy Link

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

It sounds like you're describing physical plant tracking, which is covered by #20

@jeremystretch commented on GitHub (Aug 6, 2016): It sounds like you're describing physical plant tracking, which is covered by #20
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 status: duplicate
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#333
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?