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

Add Aruba and Generic stacking port choices #6284

New Issue
Closed
opened 2025-12-29 19:38:54 +01:00 by adam · 7 comments
adam commented 2025-12-29 19:38:54 +01:00
Owner
Copy Link

Originally created by @cmcknz77 on GitHub (Apr 2, 2022).

NetBox version

v3.2.0-beta2

Feature type

Change to existing functionality

Proposed functionality

Currently NetBox already supports many Cisco stacking interface types but none for Aruba or other existing manuacturer switches.

For reference:
The Aruba 2500 and 2900M series of switches use a different stacking cable to the Aruba 3800&3810M series of switches
https://buy.hpe.com/uk/en/options/cables-cable-kits/stacking-cables/stacking-cables/hpe-switch-stacking-cables/p/4179896

https://support.hpe.com/resource3/docDisplay/pdfjs/web/viewer.html?file=%2Fhpesc%2Fpublic%2Fapi%2Fdocument%2Fa00015161en_us%3FdocVersion%3D6.0&locale=en-US&rangeChunkSize=256000&disableAutoFetch=false&disableCache=false&version=20220308085252#_OPENTOPIC_TOC_PROCESSING_d95e10681

I propose adding interface types for Aruba 2xx0 and 38x0 switch types as well as a generic that could be used for manufacturers that are currently unlisted.

Use case

New interfaces types to model connections between member switches of stacks (virtual chassis).

Database changes

I don't believe that database changes are required. I added the 6 lines of code to my "choices.py" and although it took a little while for netbox to restart, that appears to have done the trick.

External dependencies

None

Originally created by @cmcknz77 on GitHub (Apr 2, 2022). ### NetBox version v3.2.0-beta2 ### Feature type Change to existing functionality ### Proposed functionality Currently NetBox already supports many Cisco stacking interface types but none for Aruba or other existing manuacturer switches. For reference: The Aruba 2500 and 2900M series of switches use a different stacking cable to the Aruba 3800&3810M series of switches https://buy.hpe.com/uk/en/options/cables-cable-kits/stacking-cables/stacking-cables/hpe-switch-stacking-cables/p/4179896 https://support.hpe.com/resource3/docDisplay/pdfjs/web/viewer.html?file=%2Fhpesc%2Fpublic%2Fapi%2Fdocument%2Fa00015161en_us%3FdocVersion%3D6.0&locale=en-US&rangeChunkSize=256000&disableAutoFetch=false&disableCache=false&version=20220308085252#_OPENTOPIC_TOC_PROCESSING_d95e10681 I propose adding interface types for Aruba 2xx0 and 38x0 switch types as well as a generic that could be used for manufacturers that are currently unlisted. ### Use case New interfaces types to model connections between member switches of stacks (virtual chassis). ### Database changes I don't believe that database changes are required. I added the 6 lines of code to my "choices.py" and although it took a little while for netbox to restart, that appears to have done the trick. ### External dependencies None
adam added the type: featurepending closurestatus: revisions needed labels 2025-12-29 19:38:54 +01:00
adam closed this issue 2025-12-29 19:38:54 +01:00
adam commented 2025-12-29 19:38:55 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 4, 2022):

What are the exact name(s) being proposed? We will only add to NetBox proprietary connector types that have been well-defined by their manufacturers. (Using the name of a switch series in place of the connector name is not sufficient.)

@jeremystretch commented on GitHub (Apr 4, 2022): What are the exact name(s) being proposed? We will only add to NetBox proprietary connector types that have been well-defined by their manufacturers. (Using the name of a switch series in place of the connector name is not sufficient.)
adam commented 2025-12-29 19:38:55 +01:00
Author
Owner
Copy Link

@cmcknz77 commented on GitHub (Apr 5, 2022):

Hi Jeremy.
Sorry for jumping the gun with the PR.
As far as I understand those suggested are the connector names as defined by the manufacturer Aruba/HPE as shown here: https://buy.hpe.com/uk/en/options/cables-cable-kits/stacking-cables/stacking-cables/hpe-switch-stacking-cables/p/4179896

I have not been able to find any other description for the two connector types but they are the ones used for all of the Aruba & HPE(formerly HP Procurve) switches that use proprietary connectors to stack. I'll ask HPE to clarify.

@cmcknz77 commented on GitHub (Apr 5, 2022): Hi Jeremy. Sorry for jumping the gun with the PR. As far as I understand those suggested are the connector names as defined by the manufacturer Aruba/HPE as shown here: https://buy.hpe.com/uk/en/options/cables-cable-kits/stacking-cables/stacking-cables/hpe-switch-stacking-cables/p/4179896 I have not been able to find any other description for the two connector types but they are the ones used for all of the Aruba & HPE(formerly HP Procurve) switches that use proprietary connectors to stack. I'll ask HPE to clarify.
adam commented 2025-12-29 19:38:55 +01:00
Author
Owner
Copy Link

@cmcknz77 commented on GitHub (Apr 6, 2022):

image

@jeremystretch Can't get more clear than the attached. Aruba/HPE (formally HP Procurve) have no name for the proprietary stacking connector types used for the stacking modules for the 2920,2930M,3800 and 3810M series' of switches.

As such, I propose naming them after the switch series that use them, as the manufacturer does

TYPE_ARUBA29XXSTACK = 'aruba-29xx-stacking'
(TYPE_ARUBA29XXSTACK, 'Aruba 2920/2930 Stacking')
TYPE_ARUBA38XXSTACK = 'aruba-38xx-stacking'
(TYPE_ARUBA38XXSTACK, 'Aruba 3800/3810 Stacking')

I've uninstalled Netgear enterprise switches previously that used HDMI cables for stacking which is what I was thinking of when I suggested the 'generic' type but I can appreciate any hesitance to implement that because I agree that it's not conducive to descriptive and accurate documentation if overused.

TYPE_GENERICSTACK = 'generic-stacking-port'
(TYPE_GENERICSTACK, 'Generic Stacking Port')
@cmcknz77 commented on GitHub (Apr 6, 2022): ![image](https://user-images.githubusercontent.com/8886905/162036178-0ac1e06b-d927-4d2d-ba7f-ae89de56716a.png) @jeremystretch Can't get more clear than the attached. Aruba/HPE (formally HP Procurve) have no name for the proprietary stacking connector types used for the stacking modules for the 2920,2930M,3800 and 3810M series' of switches. As such, I propose naming them after the switch series that use them, as the manufacturer does TYPE_ARUBA29XXSTACK = 'aruba-29xx-stacking' (TYPE_ARUBA29XXSTACK, 'Aruba 2920/2930 Stacking') TYPE_ARUBA38XXSTACK = 'aruba-38xx-stacking' (TYPE_ARUBA38XXSTACK, 'Aruba 3800/3810 Stacking') I've uninstalled Netgear enterprise switches previously that used HDMI cables for stacking which is what I was thinking of when I suggested the 'generic' type but I can appreciate any hesitance to implement that because I agree that it's not conducive to descriptive and accurate documentation if overused. TYPE_GENERICSTACK = 'generic-stacking-port' (TYPE_GENERICSTACK, 'Generic Stacking Port')
adam commented 2025-12-29 19:38:57 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jul 18, 2022):

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 (Jul 18, 2022): 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.
adam commented 2025-12-29 19:38:59 +01:00
Author
Owner
Copy Link

@cmcknz77 commented on GitHub (Aug 31, 2022):

image

With there failing to be a more elaborate 'public' name for these cables/connectors and Aruba HPE having said that they agree with my descriptions of them, I am at a loss as to how to resolve the hesitance to add the necessary 4 lines of code above.

@cmcknz77 commented on GitHub (Aug 31, 2022): ![image](https://user-images.githubusercontent.com/8886905/187559015-5259870b-71a9-4c7f-a880-62b1e3013fd4.png) With there failing to be a more elaborate 'public' name for these cables/connectors and Aruba HPE having said that they agree with my descriptions of them, I am at a loss as to how to resolve the hesitance to add the necessary 4 lines of code above.
adam commented 2025-12-29 19:38:59 +01:00
Author
Owner
Copy Link

@cmcknz77 commented on GitHub (Sep 13, 2022):

@DanSheps @jeremystretch Hi gents, I understand that you are busy but I need to move this forward and would respectfully request any advice that you have that would allow me to do so. What do I do? Copy the contents to a new issue? If so, by my understanding we're still at the same impasse so how do we resolve it?
Thanks for your momentary attention to this matter.
Clay

@cmcknz77 commented on GitHub (Sep 13, 2022): @DanSheps @jeremystretch Hi gents, I understand that you are busy but I need to move this forward and would respectfully request any advice that you have that would allow me to do so. What do I do? Copy the contents to a new issue? If so, by my understanding we're still at the same impasse so how do we resolve it? Thanks for your momentary attention to this matter. Clay
adam commented 2025-12-29 19:38:59 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Sep 13, 2022):

@cmcknz77 As I noted above, this won't be accepted without a canonical name for the interface type from the manufacturer. If you'd like to modify your NetBox instance to add a fabricated interface type you are free to do so, but we are unable to add any types to the core product that are not backed by an authoritative definition.

@jeremystretch commented on GitHub (Sep 13, 2022): @cmcknz77 As I noted above, this won't be accepted without a canonical name for the interface type from the manufacturer. If you'd like to modify your NetBox instance to add a fabricated interface type you are free to do so, but we are unable to add any types to the core product that are not backed by an authoritative definition.
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#6284
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?