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

Extend Backplane communication options to FC switches and cards #7948

New Issue
Closed
opened 2025-12-29 20:30:24 +01:00 by adam · 4 comments
adam commented 2025-12-29 20:30:24 +01:00
Owner
Copy Link

Originally created by @stavr666 on GitHub (Apr 27, 2023).

NetBox version

v3.4.3

Feature type

Change to existing functionality

Proposed functionality

Addition to this FR: https://github.com/netbox-community/netbox/issues/10356

Add ability to document backplane connections for Fiber Channel in blade systems.

Use case

In out case, we have HPE C7000 and HPE C12000 blade frames.
First one have HPE B-series 8/24c AJ821B onboard (8 external SFP+, 16 internal backplane-mapped ports), second one - HPE Brocade 16Gb/12 FC Switch Module K2Q83A (24 external SFP+, 12 internal backplane-mapped ports).

Right now, we have no way to distinguish external ports from backplane "virtual" ports, except naming scheme or putting something to description.
But we'd like to have more consistent way to filter external connections for reports, monitoring (and provisioning at some point).

Database changes

No response

External dependencies

No response

Originally created by @stavr666 on GitHub (Apr 27, 2023). ### NetBox version v3.4.3 ### Feature type Change to existing functionality ### Proposed functionality Addition to this FR: https://github.com/netbox-community/netbox/issues/10356 Add ability to document backplane connections for Fiber Channel in blade systems. ### Use case In out case, we have HPE C7000 and HPE C12000 blade frames. First one have HPE B-series 8/24c AJ821B onboard (8 external SFP+, 16 internal backplane-mapped ports), second one - HPE Brocade 16Gb/12 FC Switch Module K2Q83A (24 external SFP+, 12 internal backplane-mapped ports). Right now, we have no way to distinguish external ports from backplane "virtual" ports, except naming scheme or putting something to description. But we'd like to have more consistent way to filter external connections for reports, monitoring (and provisioning at some point). ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurepending closurestatus: revisions needed labels 2025-12-29 20:30:24 +01:00
adam closed this issue 2025-12-29 20:30:24 +01:00
adam commented 2025-12-29 20:30:25 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 5, 2023):

What are the specific changes you are proposing?

@jeremystretch commented on GitHub (May 5, 2023): What are the specific changes you are proposing?
adam commented 2025-12-29 20:30:25 +01:00
Author
Owner
Copy Link

@stavr666 commented on GitHub (May 10, 2023):

What are the specific changes you are proposing?

  1. Add new interface type group "FibreChannel (backplace)"
  2. Duplicate list of FC types with bonus label "internal" to clearly (filtrable) indicate, that ports have no any external optical cable connections.

Last part arguable must have declared standard types, but I didn't find any clues about industry-level standard for things like this:

image

@stavr666 commented on GitHub (May 10, 2023): > What are the specific changes you are proposing? 1. Add new interface type group "FibreChannel (backplace)" 2. Duplicate list of FC types with bonus label "internal" to clearly (filtrable) indicate, that ports have no any external optical cable connections. Last part arguable must have declared standard types, but I didn't find any clues about industry-level standard for things like this: ![image](https://github.com/netbox-community/netbox/assets/84839985/aa81f64f-7d40-4939-a716-29bf17270899)
adam commented 2025-12-29 20:30:25 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Aug 9, 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 (Aug 9, 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:30:26 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Sep 9, 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 (Sep 9, 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 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#7948
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?