Supermicro big-twin and fat twins.. #46
Labels
No labels
help wanted
need testing
status: accepted
status: discussing
type: bug
type: documentation
type: duplicate
type: enhancement
type:hardware
type: invalid
type: major feature
type: minor feature
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: DGNum/netbox-agent#46
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Got several different Supermicro's, here's some dmi information:
This is a Fat twin (4u, 8 nodes)
it's missing the slot information... not filled in; so we've been setting part of the hostname to chassis slot ie, the hostname is row-rack-chassis-node aka 'd8-r13-c1-n1' - row d8, rack 13, chassis 1, node 1
I also prefer to use the base board for the blade type, not the system information product name. allows me to keep the chassis separate from the blades.
Power DMI; there is actually 4 power supplies in this chassis, but
two are for 4 nodes, and the other 2 are for a different node.
A big twin (2u, 4 node chassis/server)
and the power from them:
Thanks for sharing the dmidecode infos!
Would you be able to gist the whole stuff ? in case Supermicro did something like HP by creating a new dmi type for the location
I've added infos about the power supply behavior to the issue #37
In case there's no location infos in the dmidecode, do you think that a slot location in the configuration file would be enough?
Something like this:
There's nothing else slot wise for the Supermicro; I've checked.. and checked. and tried to see if we could set it. I also have set of Gigabyte hyper-converged servers (that's what they are called..) and they also don't have the slot number in the DMI information..
So, yes, that slot_location configuration is a good start.
Also, I'd added chassis_name to it; using the serial number is ok, but the operations people would get lost with that.