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

Cable Trace not working in both directions #9950

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

Originally created by @mat-vc on GitHub (Jul 5, 2024).

Deployment Type

Self-hosted

NetBox Version

4.0.6

Python Version

3.11

Steps to Reproduce

Create 1 patch-device with 1 front and 1 rear port.

Create 2 devices with 1 interface on each device.
Connect both devices to their corresponding rear/front port.

Press the "trace cable" button to produce a result.

Expected Behavior

I am expecting both trace directions to show the same output. This is not the case.

I'm using a fresh docker environment to test this issue. I've observed this on another environment too.

Observed Behavior

The trace from both sides is giving a different output.
One shows the expected (full) result. The other shows only 1 out of 2 connected patch-cables.
image
image

Originally created by @mat-vc on GitHub (Jul 5, 2024). ### Deployment Type Self-hosted ### NetBox Version 4.0.6 ### Python Version 3.11 ### Steps to Reproduce Create 1 patch-device with 1 front and 1 rear port. Create 2 devices with 1 interface on each device. Connect both devices to their corresponding rear/front port. Press the "trace cable" button to produce a result. ### Expected Behavior I am expecting both trace directions to show the same output. This is not the case. I'm using a fresh docker environment to test this issue. I've observed this on another environment too. ### Observed Behavior The trace from both sides is giving a different output. One shows the expected (full) result. The other shows only 1 out of 2 connected patch-cables. ![image](https://github.com/netbox-community/netbox/assets/77629312/043656dc-b14a-4914-801d-71c3aa2b39d6) ![image](https://github.com/netbox-community/netbox/assets/77629312/05c00897-8a3f-4245-8011-09da2b4cae92)
adam closed this issue 2025-12-29 21:24:50 +01:00
adam commented 2025-12-29 21:24:50 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (Jul 8, 2024):

@mat-vc Can you please check the steps to reproduce and maybe give a more in-depth step by step - I tried a scenario like you listed but can see the trace from both sides (see below):
| NetBox 2024-07-08 09-52-26
| NetBox 2024-07-08 09-53-05

@arthanson commented on GitHub (Jul 8, 2024): @mat-vc Can you please check the steps to reproduce and maybe give a more in-depth step by step - I tried a scenario like you listed but can see the trace from both sides (see below): <img width="438" alt="| NetBox 2024-07-08 09-52-26" src="https://github.com/netbox-community/netbox/assets/99642/a67b2eb2-d4f8-43c9-9b28-1d037afa5315"> <img width="470" alt="| NetBox 2024-07-08 09-53-05" src="https://github.com/netbox-community/netbox/assets/99642/a99c7020-7e24-4583-85f8-3db0c76bd0f9">
adam commented 2025-12-29 21:24:50 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 15, 2024):

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.

@github-actions[bot] commented on GitHub (Jul 15, 2024): 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.
adam commented 2025-12-29 21:24:51 +01:00
Author
Owner
Copy Link

@dfex commented on GitHub (Jul 16, 2024):

I am seeing this issue intermittently as well. Netbox 4.0.7 via netbox-docker.

I have a slightly more complex scenario where I have modelled two FOBOT Devices with Front and Rear ports, with "Switch" Device Interfaces connected to the FOBOT Front Ports and the FOBOT Rear Ports connected to each other:

Device [SWITCH1] -> interface -> Cable -> front-port -> device [FOBOT1] -> rear-port -> Cable -> rear-port -> device [FOBOT2] -> front-port -> Cable -> interface -> Device [SWITCH2]

Earlier when I was looking at the SWITCH1 interface list, it showed the nominated interface connected through to the far-end SWITCH2 interface (solving all the intermediate passive device connectivity), however looking at the SWITCH2 interface, it only showed the CableName and the Connected column was blank. Running Trace showed the same one-way results as @mat-vc was seeing (eg: a split after FOBOT2) - and this is when I searched on the cause of the split error message and found this GitHub Issue.

Docker (and thus netbox) has restarted during this time as my laptop was closed.

However, just now, I re-created @arthanson 's test scenario above on separate test devices with a simple back-to-back device in the middle, and trace worked in both directions for that scenario.

Now all of a sudden I can also see a bidirectional connection on my more complex scenario as well! So I'm not sure if that was the restart or something else that is causing it to trace both ways correctly.

@dfex commented on GitHub (Jul 16, 2024): I am seeing this issue intermittently as well. Netbox 4.0.7 via netbox-docker. I have a slightly more complex scenario where I have modelled two FOBOT Devices with Front and Rear ports, with "Switch" Device Interfaces connected to the FOBOT Front Ports and the FOBOT Rear Ports connected to each other: Device [SWITCH1] -> interface -> Cable -> front-port -> device [FOBOT1] -> rear-port -> Cable -> rear-port -> device [FOBOT2] -> front-port -> Cable -> interface -> Device [SWITCH2] Earlier when I was looking at the SWITCH1 interface list, it showed the nominated interface connected through to the far-end SWITCH2 interface (solving all the intermediate passive device connectivity), however looking at the SWITCH2 interface, it only showed the CableName and the Connected column was blank. Running Trace showed the same one-way results as @mat-vc was seeing (eg: a split after FOBOT2) - and this is when I searched on the cause of the split error message and found this GitHub Issue. Docker (and thus netbox) has restarted during this time as my laptop was closed. However, just now, I re-created @arthanson 's test scenario above on separate test devices with a simple back-to-back device in the middle, and trace worked in both directions for that scenario. Now all of a sudden I can also see a bidirectional connection on my more complex scenario as well! So I'm not sure if that was the restart or something else that is causing it to trace both ways correctly.
adam commented 2025-12-29 21:24:51 +01:00
Author
Owner
Copy Link

@mat-vc commented on GitHub (Jul 30, 2024):

My apologies for my late reply.

I have just deployed netbox-docker (4.0.8) on another fresh docker environment.
So far, I've observed this issue on versions v3.7.4, 4.0.6, 4.0.7 and 4.0.8.

After testing a few cables it happened again. It only happens sometimes, I can't quiet put my finger on what specifically triggers it, to thow this error...

A few screenshots: Cables 1-2 and 3-4 are OK. Cable 5+6 throw the error only in 1 trace direction.
image
image

Trace directions:
image
image

Cable 1+2 (works)
image

Patchpanel used for cable 1-4. Positions are always 1. On both front & rear ports.
image

Patchpanel used for cable 5-6. Positions are dynamic but do match on front&rear for this device
image
image

Could the device template's position have anything to do with it?

@mat-vc commented on GitHub (Jul 30, 2024): My apologies for my late reply. I have just deployed netbox-docker (4.0.8) on another fresh docker environment. So far, I've observed this issue on versions v3.7.4, 4.0.6, 4.0.7 and 4.0.8. After testing a few cables it happened again. It only happens sometimes, I can't quiet put my finger on what specifically triggers it, to thow this error... A few screenshots: Cables 1-2 and 3-4 are OK. Cable 5+6 throw the error only in 1 trace direction. ![image](https://github.com/user-attachments/assets/740b348c-08c4-4254-bf4b-7ae7c8dd0986) ![image](https://github.com/user-attachments/assets/e6a9d68b-cae1-4b7f-8182-7547d4ca65f4) Trace directions: ![image](https://github.com/user-attachments/assets/5925cfc0-3288-43a7-8c7f-ae9ef86bc836) ![image](https://github.com/user-attachments/assets/3360dc8b-d462-44b1-b30a-c19e01348b75) Cable 1+2 (works) ![image](https://github.com/user-attachments/assets/47ed21be-8b06-48f7-bd8b-d402feccd8d3) Patchpanel used for cable 1-4. Positions are always 1. On both front & rear ports. ![image](https://github.com/user-attachments/assets/f7e2f859-c645-4573-813d-47a2b8921da2) Patchpanel used for cable 5-6. Positions are dynamic but do match on front&rear for this device ![image](https://github.com/user-attachments/assets/8514d715-7f96-4f7e-bdd1-3552dcd2ff74) ![image](https://github.com/user-attachments/assets/6cc5ac60-fdb8-4ca3-8556-632e6100238c) Could the device template's position have anything to do with it?
adam commented 2025-12-29 21:24:51 +01:00
Author
Owner
Copy Link

@oyvindruud commented on GitHub (Mar 6, 2025):

Hi,
I have the same problem now in version 4.2.4. I have 12 such lines. In 8 of the 12 lines, trace works both ways, while on 4 of them, it only works one way. I forced a trace recalculation in NetBox, and now only 4 out of 12 lines trace in both directions. Everything looks identical on the ones that work and those that don’t, so this is strange.

@oyvindruud commented on GitHub (Mar 6, 2025): Hi, I have the same problem now in version 4.2.4. I have 12 such lines. In 8 of the 12 lines, trace works both ways, while on 4 of them, it only works one way. I forced a trace recalculation in NetBox, and now only 4 out of 12 lines trace in both directions. Everything looks identical on the ones that work and those that don’t, so this is strange.
adam commented 2025-12-29 21:24:51 +01:00
Author
Owner
Copy Link

@Poletuch commented on GitHub (Apr 11, 2025):

Hi all,

we have the same problem in version 4.2.6. (See #19148 )
Is there any progress with this issue ? Because no new information has been published here since Jul 30, 2024

Thanks a lot in advance for any "positive" reply ;-)

@Poletuch commented on GitHub (Apr 11, 2025): Hi all, we have the same problem in version 4.2.6. (See #19148 ) Is there any progress with this issue ? Because no new information has been published here since Jul 30, 2024 Thanks a lot in advance for any "positive" reply ;-)
adam commented 2025-12-29 21:24:51 +01:00
Author
Owner
Copy Link

@TheFlyingCorpse commented on GitHub (Jul 3, 2025):

I'm worried I'll come across this error. I've made close to 100 cables now in a setup without meeting the bug though and a bit stumped as to what is causing this.

To one of you who have this bug, can you do provide an output similar to this so I can dig deeper:
If the URL is "http://localhost/dcim/front-ports/61/trace/", change it to "http://localhost/api/dcim/front-ports/61/" and provide the output, of both ends.
My thinking is that if its missing from the endpoint in the API its something to investigate on the api and backwards, if its present there its likely some error in the SVG generator and thats something to be investigated.

Thanks in advance!

@TheFlyingCorpse commented on GitHub (Jul 3, 2025): I'm worried I'll come across this error. I've made close to 100 cables now in a setup without meeting the bug though and a bit stumped as to what is causing this. To one of you who have this bug, can you do provide an output similar to this so I can dig deeper: If the URL is "http://localhost/dcim/front-ports/61/trace/", change it to "http://localhost/api/dcim/front-ports/61/" and provide the output, of both ends. My thinking is that if its missing from the endpoint in the API its something to investigate on the api and backwards, if its present there its likely some error in the SVG generator and thats something to be investigated. Thanks in advance!
adam commented 2025-12-29 21:24:51 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 2, 2025):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Oct 2, 2025): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/main/CONTRIBUTING.md).
adam commented 2025-12-29 21:24:52 +01:00
Author
Owner
Copy Link

@RedShift1 commented on GitHub (Oct 22, 2025):

I'm new to Netbox but I think I just came across this issue myself. Fresh install of version 4.4.4.

Image

API data for rear port:

HTTP 200 OK
Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "id": 1,
    "url": "http://docker1-adbe:5002/api/dcim/rear-ports/1/",
    "display_url": "http://docker1-adbe:5002/dcim/rear-ports/1/",
    "display": "3",
    "device": {
        "id": 3,
        "url": "http://docker1-adbe:5002/api/dcim/devices/3/",
        "display": "p13",
        "name": "p13",
        "description": ""
    },
    "module": null,
    "name": "3",
    "label": "",
    "type": {
        "value": "8p8c",
        "label": "8P8C"
    },
    "color": "",
    "positions": 1,
    "description": "",
    "mark_connected": false,
    "cable": {
        "id": 1,
        "url": "http://docker1-adbe:5002/api/dcim/cables/1/",
        "display": "#1",
        "label": "",
        "description": ""
    },
    "cable_end": "B",
    "link_peers": [
        {
            "id": 25,
            "url": "http://docker1-adbe:5002/api/dcim/interfaces/25/",
            "display": "GigabitEthernet0",
            "device": {
                "id": 2,
                "url": "http://docker1-adbe:5002/api/dcim/devices/2/",
                "display": "ap-adbe-academy-1",
                "name": "ap-adbe-academy-1",
                "description": ""
            },
            "name": "GigabitEthernet0",
            "description": "",
            "cable": {
                "id": 1,
                "url": "http://docker1-adbe:5002/api/dcim/cables/1/",
                "display": "#1",
                "label": "",
                "description": ""
            },
            "_occupied": true
        }
    ],
    "link_peers_type": "dcim.interface",
    "tags": [],
    "custom_fields": {},
    "created": "2025-10-22T12:58:44.919548Z",
    "last_updated": "2025-10-22T13:43:57.549209Z",
    "_occupied": true
}

API data for front port:

HTTP 200 OK
Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "id": 1,
    "url": "http://docker1-adbe:5002/api/dcim/front-ports/1/",
    "display_url": "http://docker1-adbe:5002/dcim/front-ports/1/",
    "display": "3",
    "device": {
        "id": 3,
        "url": "http://docker1-adbe:5002/api/dcim/devices/3/",
        "display": "p13",
        "name": "p13",
        "description": ""
    },
    "module": null,
    "name": "3",
    "label": "",
    "type": {
        "value": "8p8c",
        "label": "8P8C"
    },
    "color": "",
    "rear_port": {
        "id": 1,
        "url": "http://docker1-adbe:5002/api/dcim/rear-ports/1/",
        "display_url": "http://docker1-adbe:5002/dcim/rear-ports/1/",
        "display": "3",
        "name": "3",
        "label": "",
        "description": ""
    },
    "rear_port_position": 1,
    "description": "",
    "mark_connected": false,
    "cable": {
        "id": 5,
        "url": "http://docker1-adbe:5002/api/dcim/cables/5/",
        "display": "#5",
        "label": "",
        "description": ""
    },
    "cable_end": "B",
    "link_peers": [
        {
            "id": 3,
            "url": "http://docker1-adbe:5002/api/dcim/interfaces/3/",
            "display": "GigabitEthernet1/0/3",
            "device": {
                "id": 1,
                "url": "http://docker1-adbe:5002/api/dcim/devices/1/",
                "display": "sw-adbe-academy-1",
                "name": "sw-adbe-academy-1",
                "description": ""
            },
            "name": "GigabitEthernet1/0/3",
            "description": "",
            "cable": {
                "id": 5,
                "url": "http://docker1-adbe:5002/api/dcim/cables/5/",
                "display": "#5",
                "label": "",
                "description": ""
            },
            "_occupied": true
        }
    ],
    "link_peers_type": "dcim.interface",
    "tags": [],
    "custom_fields": {},
    "created": "2025-10-22T12:59:25.763703Z",
    "last_updated": "2025-10-22T13:23:29.929127Z",
    "_occupied": true
}
@RedShift1 commented on GitHub (Oct 22, 2025): I'm new to Netbox but I think I just came across this issue myself. Fresh install of version 4.4.4. <img width="1899" height="1073" alt="Image" src="https://github.com/user-attachments/assets/4c8ce43b-0399-4924-9a99-739af6a0bb92" /> API data for rear port: ```json HTTP 200 OK Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS Content-Type: application/json Vary: Accept { "id": 1, "url": "http://docker1-adbe:5002/api/dcim/rear-ports/1/", "display_url": "http://docker1-adbe:5002/dcim/rear-ports/1/", "display": "3", "device": { "id": 3, "url": "http://docker1-adbe:5002/api/dcim/devices/3/", "display": "p13", "name": "p13", "description": "" }, "module": null, "name": "3", "label": "", "type": { "value": "8p8c", "label": "8P8C" }, "color": "", "positions": 1, "description": "", "mark_connected": false, "cable": { "id": 1, "url": "http://docker1-adbe:5002/api/dcim/cables/1/", "display": "#1", "label": "", "description": "" }, "cable_end": "B", "link_peers": [ { "id": 25, "url": "http://docker1-adbe:5002/api/dcim/interfaces/25/", "display": "GigabitEthernet0", "device": { "id": 2, "url": "http://docker1-adbe:5002/api/dcim/devices/2/", "display": "ap-adbe-academy-1", "name": "ap-adbe-academy-1", "description": "" }, "name": "GigabitEthernet0", "description": "", "cable": { "id": 1, "url": "http://docker1-adbe:5002/api/dcim/cables/1/", "display": "#1", "label": "", "description": "" }, "_occupied": true } ], "link_peers_type": "dcim.interface", "tags": [], "custom_fields": {}, "created": "2025-10-22T12:58:44.919548Z", "last_updated": "2025-10-22T13:43:57.549209Z", "_occupied": true } ``` API data for front port: ```json HTTP 200 OK Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS Content-Type: application/json Vary: Accept { "id": 1, "url": "http://docker1-adbe:5002/api/dcim/front-ports/1/", "display_url": "http://docker1-adbe:5002/dcim/front-ports/1/", "display": "3", "device": { "id": 3, "url": "http://docker1-adbe:5002/api/dcim/devices/3/", "display": "p13", "name": "p13", "description": "" }, "module": null, "name": "3", "label": "", "type": { "value": "8p8c", "label": "8P8C" }, "color": "", "rear_port": { "id": 1, "url": "http://docker1-adbe:5002/api/dcim/rear-ports/1/", "display_url": "http://docker1-adbe:5002/dcim/rear-ports/1/", "display": "3", "name": "3", "label": "", "description": "" }, "rear_port_position": 1, "description": "", "mark_connected": false, "cable": { "id": 5, "url": "http://docker1-adbe:5002/api/dcim/cables/5/", "display": "#5", "label": "", "description": "" }, "cable_end": "B", "link_peers": [ { "id": 3, "url": "http://docker1-adbe:5002/api/dcim/interfaces/3/", "display": "GigabitEthernet1/0/3", "device": { "id": 1, "url": "http://docker1-adbe:5002/api/dcim/devices/1/", "display": "sw-adbe-academy-1", "name": "sw-adbe-academy-1", "description": "" }, "name": "GigabitEthernet1/0/3", "description": "", "cable": { "id": 5, "url": "http://docker1-adbe:5002/api/dcim/cables/5/", "display": "#5", "label": "", "description": "" }, "_occupied": true } ], "link_peers_type": "dcim.interface", "tags": [], "custom_fields": {}, "created": "2025-10-22T12:59:25.763703Z", "last_updated": "2025-10-22T13:23:29.929127Z", "_occupied": true } ```
adam commented 2025-12-29 21:24:52 +01:00
Author
Owner
Copy Link

@RedShift1 commented on GitHub (Oct 22, 2025):

I deleted the cable connections and redid it via Connections > Cables > Add:

Image

API data rear port:

HTTP 200 OK
Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "id": 1,
    "url": "http://docker1-adbe:5002/api/dcim/rear-ports/1/",
    "display_url": "http://docker1-adbe:5002/dcim/rear-ports/1/",
    "display": "3",
    "device": {
        "id": 3,
        "url": "http://docker1-adbe:5002/api/dcim/devices/3/",
        "display": "p13",
        "name": "p13",
        "description": ""
    },
    "module": null,
    "name": "3",
    "label": "",
    "type": {
        "value": "8p8c",
        "label": "8P8C"
    },
    "color": "",
    "positions": 1,
    "description": "",
    "mark_connected": false,
    "cable": {
        "id": 7,
        "url": "http://docker1-adbe:5002/api/dcim/cables/7/",
        "display": "#7",
        "label": "",
        "description": ""
    },
    "cable_end": "A",
    "link_peers": [
        {
            "id": 25,
            "url": "http://docker1-adbe:5002/api/dcim/interfaces/25/",
            "display": "GigabitEthernet0",
            "device": {
                "id": 2,
                "url": "http://docker1-adbe:5002/api/dcim/devices/2/",
                "display": "ap-adbe-academy-1",
                "name": "ap-adbe-academy-1",
                "description": ""
            },
            "name": "GigabitEthernet0",
            "description": "",
            "cable": {
                "id": 7,
                "url": "http://docker1-adbe:5002/api/dcim/cables/7/",
                "display": "#7",
                "label": "",
                "description": ""
            },
            "_occupied": true
        }
    ],
    "link_peers_type": "dcim.interface",
    "tags": [],
    "custom_fields": {},
    "created": "2025-10-22T12:58:44.919548Z",
    "last_updated": "2025-10-22T14:01:54.903059Z",
    "_occupied": true
}

API data front port:

HTTP 200 OK
Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS
Content-Type: application/json
Vary: Accept

{
    "id": 1,
    "url": "http://docker1-adbe:5002/api/dcim/front-ports/1/",
    "display_url": "http://docker1-adbe:5002/dcim/front-ports/1/",
    "display": "3",
    "device": {
        "id": 3,
        "url": "http://docker1-adbe:5002/api/dcim/devices/3/",
        "display": "p13",
        "name": "p13",
        "description": ""
    },
    "module": null,
    "name": "3",
    "label": "",
    "type": {
        "value": "8p8c",
        "label": "8P8C"
    },
    "color": "",
    "rear_port": {
        "id": 1,
        "url": "http://docker1-adbe:5002/api/dcim/rear-ports/1/",
        "display_url": "http://docker1-adbe:5002/dcim/rear-ports/1/",
        "display": "3",
        "name": "3",
        "label": "",
        "description": ""
    },
    "rear_port_position": 1,
    "description": "",
    "mark_connected": false,
    "cable": {
        "id": 6,
        "url": "http://docker1-adbe:5002/api/dcim/cables/6/",
        "display": "#6",
        "label": "",
        "description": ""
    },
    "cable_end": "B",
    "link_peers": [
        {
            "id": 3,
            "url": "http://docker1-adbe:5002/api/dcim/interfaces/3/",
            "display": "GigabitEthernet1/0/3",
            "device": {
                "id": 1,
                "url": "http://docker1-adbe:5002/api/dcim/devices/1/",
                "display": "sw-adbe-academy-1",
                "name": "sw-adbe-academy-1",
                "description": ""
            },
            "name": "GigabitEthernet1/0/3",
            "description": "",
            "cable": {
                "id": 6,
                "url": "http://docker1-adbe:5002/api/dcim/cables/6/",
                "display": "#6",
                "label": "",
                "description": ""
            },
            "_occupied": true
        }
    ],
    "link_peers_type": "dcim.interface",
    "tags": [],
    "custom_fields": {},
    "created": "2025-10-22T12:59:25.763703Z",
    "last_updated": "2025-10-22T14:01:05.667820Z",
    "_occupied": true
}

I'm not sure what changed, if anything?

@RedShift1 commented on GitHub (Oct 22, 2025): I deleted the cable connections and redid it via Connections > Cables > Add: <img width="1914" height="1056" alt="Image" src="https://github.com/user-attachments/assets/1c6672cb-e38f-489c-a2c2-73a46670a8f8" /> API data rear port: ```json HTTP 200 OK Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS Content-Type: application/json Vary: Accept { "id": 1, "url": "http://docker1-adbe:5002/api/dcim/rear-ports/1/", "display_url": "http://docker1-adbe:5002/dcim/rear-ports/1/", "display": "3", "device": { "id": 3, "url": "http://docker1-adbe:5002/api/dcim/devices/3/", "display": "p13", "name": "p13", "description": "" }, "module": null, "name": "3", "label": "", "type": { "value": "8p8c", "label": "8P8C" }, "color": "", "positions": 1, "description": "", "mark_connected": false, "cable": { "id": 7, "url": "http://docker1-adbe:5002/api/dcim/cables/7/", "display": "#7", "label": "", "description": "" }, "cable_end": "A", "link_peers": [ { "id": 25, "url": "http://docker1-adbe:5002/api/dcim/interfaces/25/", "display": "GigabitEthernet0", "device": { "id": 2, "url": "http://docker1-adbe:5002/api/dcim/devices/2/", "display": "ap-adbe-academy-1", "name": "ap-adbe-academy-1", "description": "" }, "name": "GigabitEthernet0", "description": "", "cable": { "id": 7, "url": "http://docker1-adbe:5002/api/dcim/cables/7/", "display": "#7", "label": "", "description": "" }, "_occupied": true } ], "link_peers_type": "dcim.interface", "tags": [], "custom_fields": {}, "created": "2025-10-22T12:58:44.919548Z", "last_updated": "2025-10-22T14:01:54.903059Z", "_occupied": true } ``` API data front port: ```json HTTP 200 OK Allow: GET, PUT, PATCH, DELETE, HEAD, OPTIONS Content-Type: application/json Vary: Accept { "id": 1, "url": "http://docker1-adbe:5002/api/dcim/front-ports/1/", "display_url": "http://docker1-adbe:5002/dcim/front-ports/1/", "display": "3", "device": { "id": 3, "url": "http://docker1-adbe:5002/api/dcim/devices/3/", "display": "p13", "name": "p13", "description": "" }, "module": null, "name": "3", "label": "", "type": { "value": "8p8c", "label": "8P8C" }, "color": "", "rear_port": { "id": 1, "url": "http://docker1-adbe:5002/api/dcim/rear-ports/1/", "display_url": "http://docker1-adbe:5002/dcim/rear-ports/1/", "display": "3", "name": "3", "label": "", "description": "" }, "rear_port_position": 1, "description": "", "mark_connected": false, "cable": { "id": 6, "url": "http://docker1-adbe:5002/api/dcim/cables/6/", "display": "#6", "label": "", "description": "" }, "cable_end": "B", "link_peers": [ { "id": 3, "url": "http://docker1-adbe:5002/api/dcim/interfaces/3/", "display": "GigabitEthernet1/0/3", "device": { "id": 1, "url": "http://docker1-adbe:5002/api/dcim/devices/1/", "display": "sw-adbe-academy-1", "name": "sw-adbe-academy-1", "description": "" }, "name": "GigabitEthernet1/0/3", "description": "", "cable": { "id": 6, "url": "http://docker1-adbe:5002/api/dcim/cables/6/", "display": "#6", "label": "", "description": "" }, "_occupied": true } ], "link_peers_type": "dcim.interface", "tags": [], "custom_fields": {}, "created": "2025-10-22T12:59:25.763703Z", "last_updated": "2025-10-22T14:01:05.667820Z", "_occupied": true } ``` I'm not sure what changed, if anything?
adam commented 2025-12-29 21:24:52 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Nov 20, 2025):

I'm going to close this as stale, since no one has volunteered a fix. However, I also want to note that we're planning to ship some substantial improvements to the cabling logic in NetBox v4.5 (see #20564 and #20788) which will likely address some of the issues cited here.

@jeremystretch commented on GitHub (Nov 20, 2025): I'm going to close this as stale, since no one has volunteered a fix. However, I also want to note that we're planning to ship some substantial improvements to the cabling logic in NetBox v4.5 (see #20564 and #20788) which will likely address some of the issues cited here.
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 netbox pending closure severity: low status: needs owner topic: cabling type: bug
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#9950
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?