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

Logical MUX ability in switches #9693

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

Originally created by @TheWidowLicker on GitHub (May 17, 2024).

NetBox version

v4.0.2

Feature type

New functionality

Proposed functionality

Allow logical MUX and replication group options in switches.

Use case

On Arista 7130L and 7130LB switches (as well as other switches), you can have multiple interfaces be the ingress (RX) of a MUX group and a single interface be the egress (TX) of the same MUX group. This is good if you want to have multiple hosts sending onto the same line.
In reverse of this you can have 1 port be the ingress (RX) from a line and then have it send to the egress (TX) on multiple ports so that a line can be replicated to multiple hosts.

Database changes

None that I know of

External dependencies

None that I know of

Originally created by @TheWidowLicker on GitHub (May 17, 2024). ### NetBox version v4.0.2 ### Feature type New functionality ### Proposed functionality Allow logical MUX and replication group options in switches. ### Use case On Arista 7130L and 7130LB switches (as well as other switches), you can have multiple interfaces be the ingress (RX) of a MUX group and a single interface be the egress (TX) of the same MUX group. This is good if you want to have multiple hosts sending onto the same line. In reverse of this you can have 1 port be the ingress (RX) from a line and then have it send to the egress (TX) on multiple ports so that a line can be replicated to multiple hosts. ### Database changes None that I know of ### External dependencies None that I know of
adam added the type: featurepending closurestatus: revisions needed labels 2025-12-29 21:21:00 +01:00
adam closed this issue 2025-12-29 21:21:00 +01:00
adam commented 2025-12-29 21:21:00 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 17, 2024):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@jeremystretch commented on GitHub (May 17, 2024): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
adam commented 2025-12-29 21:21:01 +01:00
Author
Owner
Copy Link

@TheWidowLicker commented on GitHub (May 17, 2024):

Updated now

@TheWidowLicker commented on GitHub (May 17, 2024): Updated now
adam commented 2025-12-29 21:21:01 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 17, 2024):

Allow logical MUX and replication group options in switches.

This is not an actionable feature request. Please spend some time thinking through exactly what change(s) you're proposing and provide enough detail in your description above that they can be sufficiently considered and discussed. If you have not fully formed your proposed implementation yet, please try starting a discussion instead.

@jeremystretch commented on GitHub (May 17, 2024): > Allow logical MUX and replication group options in switches. This is not an actionable feature request. Please spend some time thinking through exactly what change(s) you're proposing and provide enough detail in your description above that they can be sufficiently considered and discussed. If you have not fully formed your proposed implementation yet, please try starting a [discussion](https://github.com/netbox-community/netbox/discussions/new/choose) instead.
adam commented 2025-12-29 21:21:01 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (May 25, 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 (May 25, 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:21:01 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jun 1, 2024):

This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.

@github-actions[bot] commented on GitHub (Jun 1, 2024): This issue is being closed as no further information has been provided. If you would like to revisit this topic, please first modify your original post to include all the requested detail, and then ask that the issue be reopened.
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 status: revisions needed type: feature
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#9693
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?