Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
swickstrom opened this issue Aug 5, 2016 · 2 comments
Closed

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

swickstrom opened this issue Aug 5, 2016 · 2 comments
Labels
status: duplicate This issue has already been raised

Comments

@swickstrom
Copy link

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.

@swickstrom
Copy link
Author

swickstrom commented 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).

@jeremystretch
Copy link
Member

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

@jeremystretch jeremystretch added the status: duplicate This issue has already been raised label Aug 6, 2016
@lock lock bot locked as resolved and limited conversation to collaborators Jan 19, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
status: duplicate This issue has already been raised
Projects
None yet
Development

No branches or pull requests

2 participants