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

Allow System and Motherboard Serial Number for Devices #2321

New Issue
Closed
opened 2025-12-29 17:24:49 +01:00 by adam · 2 comments
adam commented 2025-12-29 17:24:49 +01:00
Owner
Copy Link

Originally created by @a31amit on GitHub (Jan 29, 2019).

Environment

  • Python version: 3.7
  • NetBox version: 2.5.3

Proposed Functionality

Currently, Netbox Have a Single Serial Number which has a description as "Chassis Serial Number". For servers which are Commodity Hardware vendors such as Supermicro, There is not a real way to know this because they either don't update these values or update with useless values Neither it is consistent.

We have lots of Commodity Hardware & Custom Assembled where we are tracking them based on Motherboard Serial Numbers, System Serial numbers, Chassis Numbers, So either all 3 or partial information help us to uniquely found the server. Also in Blade Servers for they have Same Chassis / System Numbers for all of the blade, So Only things left is Motherboard Serial number.

So it would great if Netbox allows all 3 serial number field natively in devices. While this can be added to the custom field but I see its make more sense in devices

  • It will allow lookup servers based on all serial numbers as we could have either all / partial / one
  • Because we needed this for all devices, Custom fields will add up to extra queries and native support could be better for it.

Use Case

To see Serial numbers for Motherboard, System, Chassis all together

Database Changes

Yes, New fields required. However seems to easy to implement.

External Dependencies

None

Originally created by @a31amit on GitHub (Jan 29, 2019). <!-- NOTE: This form is only for proposing specific new features or enhancements. If you have a general idea or question, please post to our mailing list instead of opening an issue: https://groups.google.com/forum/#!forum/netbox-discuss NOTE: Due to an excessive backlog of feature requests, we are not currently accepting any proposals which significantly extend NetBox's feature scope. Please describe the environment in which you are running NetBox. Be sure that you are running an unmodified instance of the latest stable release before submitting a bug report. --> ### Environment * Python version: 3.7 * NetBox version: 2.5.3 <!-- Describe in detail the new functionality you are proposing. Include any specific changes to work flows, data models, or the user interface. --> ### Proposed Functionality Currently, Netbox Have a Single Serial Number which has a description as "Chassis Serial Number". For servers which are Commodity Hardware vendors such as Supermicro, There is not a real way to know this because they either don't update these values or update with useless values Neither it is consistent. We have lots of Commodity Hardware & Custom Assembled where we are tracking them based on Motherboard Serial Numbers, System Serial numbers, Chassis Numbers, So either all 3 or partial information help us to uniquely found the server. Also in Blade Servers for they have Same Chassis / System Numbers for all of the blade, So Only things left is Motherboard Serial number. So it would great if Netbox allows all 3 serial number field natively in devices. While this can be added to the custom field but I see its make more sense in devices - It will allow lookup servers based on all serial numbers as we could have either all / partial / one - Because we needed this for all devices, Custom fields will add up to extra queries and native support could be better for it. <!-- Convey an example use case for your proposed feature. Write from the perspective of a NetBox user who would benefit from the proposed functionality and describe how. ---> ### Use Case To see Serial numbers for Motherboard, System, Chassis all together <!-- Note any changes to the database schema necessary to support the new feature. For example, does the proposal require adding a new model or field? (Not all new features require database changes.) ---> ### Database Changes Yes, New fields required. However seems to easy to implement. <!-- List any new dependencies on external libraries or services that this new feature would introduce. For example, does the proposal require the installation of a new Python package? (Not all new features introduce new dependencies.) --> ### External Dependencies None
adam closed this issue 2025-12-29 17:24:49 +01:00
adam commented 2025-12-29 17:24:50 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 29, 2019):

The serial number field is to hold whatever you designate as the system serial number of a device. This is the one typically used e.g. for warranty purposes. Individual components should be tracked as inventory items, each of which can be assigned its own serial number. Please post to the mailing list if you'd like further assistance with this approach.

@jeremystretch commented on GitHub (Jan 29, 2019): The serial number field is to hold whatever you designate as the system serial number of a device. This is the one typically used e.g. for warranty purposes. Individual components should be tracked as inventory items, each of which can be assigned its own serial number. Please post to the mailing list if you'd like further assistance with this approach.
adam commented 2025-12-29 17:24:50 +01:00
Author
Owner
Copy Link

@a31amit commented on GitHub (Jan 29, 2019):

@jeremystretch I guess Custom Fields are better choices for our case. but Can you please reconsider to change Description for Serial Number From "Chassis Serial Number" To just "Serial Number". Something more generic name would be helpful for WebUI User to not to confuse.

@a31amit commented on GitHub (Jan 29, 2019): @jeremystretch I guess Custom Fields are better choices for our case. but Can you please reconsider to change Description for Serial Number From "Chassis Serial Number" To just "Serial Number". Something more generic name would be helpful for WebUI User to not to confuse.
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
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#2321
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?