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 support for Infiniband GUIDs #10588

New Issue
Open
opened 2025-12-29 21:33:27 +01:00 by adam · 2 comments
adam commented 2025-12-29 21:33:27 +01:00
Owner
Copy Link

Originally created by @ccope on GitHub (Dec 27, 2024).

NetBox version

v3.5.9 (but we plan to upgrade soon)

Feature type

Data model extension

Triage priority

I'm a NetBox Labs customer

Proposed functionality

I would like to be able to configure an Infiniband System GUID on Devices, as well as a Node GUID and Port GUID for each Infiniband Interface (ex: the Nvidia Bluefield card).

In practice the 3 GUID types may all be the same on a device with a single Infiniband interface, but we want to support the other cases as well, such as:

  • An independent switch has one System+Node GUID but many interfaces, and each interface has a different Port GUID
  • An HCA may have one System+Node GUID, but multiple interfaces, and each interface will have a Port GUID
  • A server may have multiple HCAs (interface cards), each with their own Node GUID, but they all share a single System GUID
  • A modular Infiniband switch will have a Node GUID for each module, but they share a single System GUID. Each module will have multiple interfaces with their own Port GUIDs.

Use case

This would allow recording physical port and device addresses, which will enable mapping logical links to physical locations.

Database changes

From database point of view, varchar 59 seems fine.
Relevant RFC:
http://www.rfcreader.com/#rfc4391_line472
http://www.rfcreader.com/#rfc4392_line84

IB Specs
IB Specification Vol 2-Release-1.4-2020-04-07.pdf
IB Specification Vol 1-Release-1.4-2020-04-07 (3).pdf

Originally posted by @zeronewb in https://github.com/netbox-community/netbox/issues/9781#issuecomment-1231705535

External dependencies

No response

Originally created by @ccope on GitHub (Dec 27, 2024). ### NetBox version v3.5.9 (but we plan to upgrade soon) ### Feature type Data model extension ### Triage priority I'm a NetBox Labs customer ### Proposed functionality I would like to be able to configure an Infiniband System GUID on Devices, as well as a Node GUID and Port GUID for each Infiniband Interface (ex: the [Nvidia Bluefield](https://docs.nvidia.com/networking/display/bf3dpu/finding+the+guid/mac+on+the+board#src-2449222587_safe-id-RmluZGluZ3RoZUdVSUQvTUFDb250aGVCb2FyZC1TdXBlck5JQ3NCb2FyZExhYmVs) card). In practice the 3 GUID types may all be the same on a device with a single Infiniband interface, but we want to support the other cases as well, such as: - An independent switch has one System+Node GUID but many interfaces, and each interface has a different Port GUID - An HCA may have one System+Node GUID, but multiple interfaces, and each interface will have a Port GUID - A server may have multiple HCAs (interface cards), each with their own Node GUID, but they all share a single System GUID - A modular Infiniband switch will have a Node GUID for each module, but they share a single System GUID. Each module will have multiple interfaces with their own Port GUIDs. ### Use case This would allow recording physical port and device addresses, which will enable mapping logical links to physical locations. ### Database changes > From database point of view, varchar 59 seems fine. > Relevant RFC: > http://www.rfcreader.com/#rfc4391_line472 > http://www.rfcreader.com/#rfc4392_line84 > IB Specs > [IB Specification Vol 2-Release-1.4-2020-04-07.pdf](https://github.com/netbox-community/netbox/files/9453429/IB.Specification.Vol.2-Release-1.4-2020-04-07.pdf) > [IB Specification Vol 1-Release-1.4-2020-04-07 (3).pdf](https://github.com/netbox-community/netbox/files/9453428/IB.Specification.Vol.1-Release-1.4-2020-04-07.3.pdf) Originally posted by @zeronewb in https://github.com/netbox-community/netbox/issues/9781#issuecomment-1231705535 ### External dependencies _No response_
adam added the type: featurenetboxneeds milestonestatus: backlogcomplexity: low labels 2025-12-29 21:33:27 +01:00
adam commented 2025-12-29 21:33:28 +01:00
Author
Owner
Copy Link

@rboucher-me commented on GitHub (Feb 13, 2025):

Could a custom field satisfy the need?

@rboucher-me commented on GitHub (Feb 13, 2025): Could a custom field satisfy the need?
adam commented 2025-12-29 21:33:28 +01:00
Author
Owner
Copy Link

@ccope commented on GitHub (Feb 13, 2025):

We might look into that as a workaround, but this isn't a custom thing. Ethernet interfaces have a MAC address field, infiniband ports should have a GUID field.

@ccope commented on GitHub (Feb 13, 2025): We might look into that as a workaround, but this isn't a custom thing. Ethernet interfaces have a MAC address field, infiniband ports should have a GUID field.
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 complexity: low needs milestone netbox status: backlog 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#10588
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?