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

Displaying multiport cables isn't displayed correctly. #8211

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

Originally created by @davesbell on GitHub (Jun 19, 2023).

NetBox version

v3.5.1

Python version

3.9

Steps to Reproduce

We are running 3.5.1, but have also tested in the demo instance running 3.5.3 which has the same issues.

We are trying to model using MPO <> 4xLC cables for breaking out a single port into 4 ports within Netbox, and having a few issues.

Our topology is
Router -> Cable -> 4x Patch Panel Rear, then we use the front of the patch panel to plug into other things at the single lane speeds. While we can connect this all up within netbox, the rendering of the information seems to be a little broken.

  1. Create router 1
  2. Create router 2
  3. Create patch panel
  4. Create cable going from port 0 of router 1 to patch panel rear ports 1-4
  5. create cable going from port 0 of router 2 to patch panel front port 1

Expected Behavior

I expect to see router 2 port 0 in the connection column on the interfaces page on router 1.

image

This is how router 2 looks which is correct.
image

This may be a related issue, when tracing a circuit, if one of the ports is connected to a circuit which is attached to a provider network, the path breaks.
image

image

Observed Behavior

On router 2, you see that it is cabled up correctly to the correct port on router 1 in the 'Connection' column.
On router 1, you don't see any information as to where it is cabled up to in the connection column. The field is empty.

This also happens if the connection point is a circuit.

Originally created by @davesbell on GitHub (Jun 19, 2023). ### NetBox version v3.5.1 ### Python version 3.9 ### Steps to Reproduce We are running 3.5.1, but have also tested in the demo instance running 3.5.3 which has the same issues. We are trying to model using MPO <> 4xLC cables for breaking out a single port into 4 ports within Netbox, and having a few issues. Our topology is Router -> Cable -> 4x Patch Panel Rear, then we use the front of the patch panel to plug into other things at the single lane speeds. While we can connect this all up within netbox, the rendering of the information seems to be a little broken. 1. Create router 1 2. Create router 2 3. Create patch panel 4. Create cable going from port 0 of router 1 to patch panel rear ports 1-4 5. create cable going from port 0 of router 2 to patch panel front port 1 ### Expected Behavior I expect to see router 2 port 0 in the connection column on the interfaces page on router 1. ![image](https://github.com/netbox-community/netbox/assets/101636305/1f2b3867-f21e-4338-bd27-c544c46b7097) This is how router 2 looks which is correct. ![image](https://github.com/netbox-community/netbox/assets/101636305/ea677294-0ffc-40bf-a589-99073630e458) This may be a related issue, when tracing a circuit, if one of the ports is connected to a circuit which is attached to a provider network, the path breaks. ![image](https://github.com/netbox-community/netbox/assets/101636305/0192e944-e6cd-4cfa-82d9-a0bc3d017ee1) ![image](https://github.com/netbox-community/netbox/assets/101636305/d9808fa3-b107-4e0b-aa06-b0f30d3b26e6) ### Observed Behavior On router 2, you see that it is cabled up correctly to the correct port on router 1 in the 'Connection' column. On router 1, you don't see any information as to where it is cabled up to in the connection column. The field is empty. This also happens if the connection point is a circuit.
adam closed this issue 2025-12-29 20:33:50 +01:00
adam commented 2025-12-29 20:33:50 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 26, 2023):

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 (Sep 26, 2023): 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/develop/CONTRIBUTING.md).
adam commented 2025-12-29 20:33:50 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Oct 26, 2023):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@github-actions[bot] commented on GitHub (Oct 26, 2023): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure severity: low status: under review 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#8211
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?