-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Patch Terminaison Câbles #18146
Comments
@LeCooperTLC Can you please provide the reproduction steps in text instead of screenshots. I.E. The first part "I created switches, then created the interfaces." can you please list out the interfaces needed, for example:
It allows us to quickly try and reproduce the issue without having to decode screenshots and figure out what you might have entered. |
I created a switch "Switch01", then added 54 interfaces from [01-54] of type 1000BASE-T. Next, I created a patch panel "Panel01". I created rear ports [01-24] and front ports [01-24]. The rear ports are automatically detected (make sure to create the rear ports first). Now, I go to my switch, select the interface I want, and click "connect cable" on the front port, then select my patch panel and connect the desired front port. I create a PC "pc01", create an interface "LAN0" of type 1000BASE-T, then connect the cable to the rear port of Panel01. Normally, after that, everything is properly connected and the trace is visible, but when the A-end of the cable connecting the PC to the patch panel is removed and patched, the trace disappears. a_termination_id=$(curl -skH "Authorization: Token """ \ (This command allows you to get the ID of the A-end of the cable that connects the PC to the patch panel.) |
This is a reminder that additional information is needed in order to further triage this issue. If the requested details are not provided, the issue will soon be closed automatically. |
Deployment Type
Self-hosted
Triage priority
N/A
NetBox Version
v4.1.7
Python Version
3.12
Steps to Reproduce
I have now created a script that retrieves data such as the hostname, the switch, and the port it is connected to. However, when these details change, I want everything to be reconnected to the correct switch.
Let me explain: let's say PC-1 is connected to Switch-1, Port-1. If my file is updated and the new configuration shows that PC-1 should be connected to Switch-2, Port-1, then I delete the termination on side A and patch it with the LAN0 interface ID of the PC I want to connect.
Script :
delete_response=$(curl -skX 'DELETE'
"https://netbox.""/api/dcim/cable-terminations/$a_termination_id/"
-H 'accept: application/json'
-H 'Content-Type: application/json'
-H "Authorization: Token "" ")
I would like to clarify that when I delete the termination and reconnect it to the cable, it works. I get the trace, and in the "Connection" column of the PC, the switch and port it is connected to appear correctly.
Expected Behavior
Observed Behavior
The text was updated successfully, but these errors were encountered: