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

Netbox - Adding information for a circuit running through 1 rack to another #740

Closed
himanisilva opened this issue Dec 13, 2016 · 4 comments

Comments

@himanisilva
Copy link

Currently I am adding information on Netbox on Patch ports. There are circuits which runs from one rack to another rack (internally). when trying to add details it is duplicate circuits as I cannot add information on either the A -end or Z-end. Is there anywhere I could add this sort of information in the circuit?

@jeremystretch
Copy link
Member

Work is underway on #49 to extend the Circuit model to connect two discrete interfaces. However, data circuits typically run between buildings, not adjacent racks. Are you sure you want to represent this connection using a circuit (with a provider and circuit ID)? If you just want to establish a connection, you can create a regular interface connection.

@himanisilva
Copy link
Author

Thank you for your response. The cross connects goes from one rack to another and in a regular interface there are no options to add the cross connect information or the patch panel information. That is the reason why I was trying to use a circuit instead. Also I have Inter rack cross connects which are not used but its for backups. Is there any best practices you suggest for this sort of issue? Your feedback is very helpful as I am new to Netbox.
Thank you.

@jeremystretch
Copy link
Member

You probably want to stick with normal interface connections. We don't yet have the ability to track cross-connect information in NetBox, but it's on the roadmap.

@jeremystretch
Copy link
Member

Going to close this out, but if you need any more help please post on the mailing list.

@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
None yet
Projects
None yet
Development

No branches or pull requests

2 participants