-
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
Add Extreme Networks SummitStack as port types #2168
Comments
I think it was unwise to have Cisco and Juniper stacking interfaces in the Netbox core, as this opens the door to every possible vendor's type of proprietary stacking port being requested. A user-customisable table of interface types (similar to Device Type) would be the ideal solution. Then if you have (say) GPON interfaces, you can document those too. In the absence of that, I'd suggest adding a generic "Other" under Stacking Port. That doesn't completely help people whose vendors have more than one port type, but there is already a free-form "Description" field that can say whether it's a type Foo or Bar. |
My rule is that if it's a legitimately unique physical interface type in common usage, we'll add it. Sometimes "stacking" ports are really just standard Ethernet interfaces which have been designated for a specific function. Extreme appears to use a combination of standard and proprietary interfaces, so we can add the proprietary ones (taken from this data sheet):
|
I agree with @candlerb that having a table would be the ideal solution (this is how RackTables does it). That would give room for having server interconnects (SAS HBA -> Disk Shelf). |
Closes #2168: Add Extreme SummitStack interface form factors
Revert "Closes #2168: Add Extreme SummitStack interface form factors"
Issue type
[X] Feature request
[ ] Bug report
[ ] Documentation
Environment
Description
Adding support for Extreme stacking ports is fairly easy, just requires updating the constants.py to include the SummitStack, SummitStack128, and SummitStack512 port types under stacking.
The text was updated successfully, but these errors were encountered: