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

Advice on how to add componenets to hardware #146

New Issue
Closed
opened 2025-12-29 15:35:20 +01:00 by adam · 2 comments
adam commented 2025-12-29 15:35:20 +01:00
Owner
Copy Link

Originally created by @greavette on GitHub (Jul 4, 2016).

Hello All,

Great system here..thanks very much for making it available for all to use!

I'd like to be able to add to my physical servers such components as:
Disk Information (Manufacture) Size, speed, Drive bay installed, Model #, Date installed, Warranty end date)
Ram Information (Manufacturer, Speed, DIMM slot, Model #, Date installed).

And I'd like to be able to add in as a hardware my Supermicro Fat Twin Servers (https://www.supermicro.com/products/nfo/FatTwin.cfm). These aren't blade servers, but they have individual nodes (servers) installed so being able to identify the Fat Twin box and assign a node to each box (with the details of the CPU, Ram, Disks, Nics that come with each node).

Could someone point me in the right direction here on how I can configure netbox so I can get this level of detail.

Thank you in advance for any advice you can provide.

Originally created by @greavette on GitHub (Jul 4, 2016). Hello All, Great system here..thanks very much for making it available for all to use! I'd like to be able to add to my physical servers such components as: Disk Information (Manufacture) Size, speed, Drive bay installed, Model #, Date installed, Warranty end date) Ram Information (Manufacturer, Speed, DIMM slot, Model #, Date installed). And I'd like to be able to add in as a hardware my Supermicro Fat Twin Servers (https://www.supermicro.com/products/nfo/FatTwin.cfm). These aren't blade servers, but they have individual nodes (servers) installed so being able to identify the Fat Twin box and assign a node to each box (with the details of the CPU, Ram, Disks, Nics that come with each node). Could someone point me in the right direction here on how I can configure netbox so I can get this level of detail. Thank you in advance for any advice you can provide.
adam added the status: duplicate label 2025-12-29 15:35:20 +01:00
adam closed this issue 2025-12-29 15:35:20 +01:00
adam commented 2025-12-29 15:35:21 +01:00
Author
Owner
Copy Link

@peelman commented on GitHub (Jul 5, 2016):

FatTwins are, for all intents and purposes, blade servers. #91 and #51 discuss that request in more detail.

Right now there isn't really a way to document things like the CPU speed, RAM, Disks, etc. NICs certainly (though not their MAC addresses).

I think expanding the Component details has probably been discussed somewhat in #157

Fleshing out the DCIM component into a full blown asset-management system is on my agenda, but right now that is probably a 2.0 goal and not something that will happen in the near-term.

@peelman commented on GitHub (Jul 5, 2016): FatTwins are, for all intents and purposes, blade servers. #91 and #51 discuss that request in more detail. Right now there isn't really a way to document things like the CPU speed, RAM, Disks, etc. NICs certainly (though not their MAC addresses). I think expanding the Component details has probably been discussed somewhat in #157 Fleshing out the DCIM component into a full blown asset-management system is on my agenda, but right now that is probably a 2.0 goal and not something that will happen in the near-term.
adam commented 2025-12-29 15:35:21 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 6, 2016):

Going to close this as a duplicate since it's covered by the individual issues @peelman linked above.

@jeremystretch commented on GitHub (Jul 6, 2016): Going to close this as a duplicate since it's covered by the individual issues @peelman linked above.
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 status: duplicate
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#146
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?