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

Logical MUX ability in switches #16175

Closed
TheWidowLicker opened this issue May 17, 2024 · 5 comments
Closed

Logical MUX ability in switches #16175

TheWidowLicker opened this issue May 17, 2024 · 5 comments
Labels
pending closure Requires immediate attention to avoid being closed for inactivity status: revisions needed This issue requires additional information to be actionable type: feature Introduction of new functionality to the application

Comments

@TheWidowLicker
Copy link

TheWidowLicker commented 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

@TheWidowLicker TheWidowLicker added status: needs triage This issue is awaiting triage by a maintainer type: feature Introduction of new functionality to the application labels May 17, 2024
@jeremystretch
Copy link
Member

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 jeremystretch added status: revisions needed This issue requires additional information to be actionable and removed status: needs triage This issue is awaiting triage by a maintainer labels May 17, 2024
@TheWidowLicker
Copy link
Author

Updated now

@jeremystretch
Copy link
Member

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.

Copy link
Contributor

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 github-actions bot added the pending closure Requires immediate attention to avoid being closed for inactivity label May 25, 2024
Copy link
Contributor

github-actions bot commented 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 github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jun 1, 2024
@jeremystretch jeremystretch removed their assignment Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pending closure Requires immediate attention to avoid being closed for inactivity status: revisions needed This issue requires additional information to be actionable type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

2 participants