Add field for infiniband MAC address #8712

Closed
opened 2025-12-29 20:40:15 +01:00 by adam · 2 comments
Owner

Originally created by @itzsimpl on GitHub (Oct 4, 2023).

NetBox version

v3.6.3

Feature type

New functionality

Proposed functionality

The mac addresses field is limited to a 6 byte values. Therefore one can not use it to store InfinBand MAC addresses which are 20 bytes long. Since the field is stored as macaddr8 in the PostgreSQL database and enforced during validation, the filed will not change (See related issue https://github.com/netbox-community/netbox/issues/9781). The only solution is to add an additional field like in the case of FiberChanell WWN (https://github.com/netbox-community/netbox/issues/1337), so we request for a similar addition, the field can be named InfiniBand MAC or ibMAC for short.

Use case

Keeping track of InfiniBand interfaces and their MAC addresses.

Database changes

add one varchar 59 field, ibmac

External dependencies

No response

Originally created by @itzsimpl on GitHub (Oct 4, 2023). ### NetBox version v3.6.3 ### Feature type New functionality ### Proposed functionality The mac addresses field is limited to a 6 byte values. Therefore one can not use it to store InfinBand MAC addresses which are 20 bytes long. Since the field is stored as `macaddr8` in the PostgreSQL database and enforced during validation, the filed will not change (See related issue https://github.com/netbox-community/netbox/issues/9781). The only solution is to add an additional field like in the case of FiberChanell WWN (https://github.com/netbox-community/netbox/issues/1337), so we request for a similar addition, the field can be named InfiniBand MAC or ibMAC for short. ### Use case Keeping track of InfiniBand interfaces and their MAC addresses. ### Database changes add one varchar 59 field, ibmac ### External dependencies _No response_
adam added the type: featurepending closure labels 2025-12-29 20:40:15 +01:00
adam closed this issue 2025-12-29 20:40:15 +01:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 3, 2024):

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 (Jan 3, 2024): 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).
Author
Owner

@github-actions[bot] commented on GitHub (Feb 2, 2024):

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 (Feb 2, 2024): 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.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#8712