Update hardware requirements doc. Add compute node UUID work around #49
Update hardware requirements doc. Add compute node UUID work around #49jbarfield wants to merge 3 commits intoTritonDataCenter:masterfrom
Conversation
…or SmartOS/Triton.
|
Whoops, looks like I screwed up the 'make check' step. Will resubmit shortly. |
bahamat
left a comment
bahamat
left a comment
There was a problem hiding this comment.
First pass.
Do we know if this works on any system with IPMI, or only some classes of hardware?
docs/hardware-requirements.md
Outdated
| `ipmitool` preinstalled so this is as easy as: | ||
|
|
||
| 1. SSH to the affected compute node | ||
| 2. On your local desktop, randomly generate, as unicast as possible, |
There was a problem hiding this comment.
Unicast? Did you mean unique?
There was a problem hiding this comment.
haha whoops...will update tomorrow
docs/hardware-requirements.md
Outdated
| `pwgen -sB 7 1` | ||
| 3. On each node run the following three commands: | ||
| `ipmitool fru edit 0 field c 1 <NEW_SERIAL>` | ||
| `ipmitool fru edit 0 field b 2 <NEW_SERIAL>` |
There was a problem hiding this comment.
This should be a command block. Double indent under a list item to get a command block.
Also, should the same number be put in each field? Should they be different numbers? Just want to double check on this. It’s not what I would have expected, but if you confirm this is correct, I’ll trust you.
docs/hardware-requirements.md
Outdated
| `ipmitool fru edit 0 field b 2 <NEW_SERIAL>` | ||
| `ipmitool fru edit 0 field p 4 <NEW_SERIAL>` | ||
| 4. Double check that the new serial number has been set: | ||
| `ipmitool fru print 0` |
There was a problem hiding this comment.
Also make this a code block
docs/hardware-requirements.md
Outdated
| serial number is likely the cause of the issue. You can also verify | ||
| the duplicate serial numbers on each node with the following: | ||
|
|
||
| `ipmitool fru print 0` |
docs/hardware-requirements.md
Outdated
| by "cnapi" and consequently, the "Operator Portal" on boot, while the | ||
| other 3 quietly PXE boot without detection by Triton. To determine if | ||
| a duplicate server UUID is the cause of your issue, simply ssh into | ||
| each of the compute nodes in question, and run: `sysinfo | json UUID`. |
There was a problem hiding this comment.
Make sysinfo command a code block
| Chassis Type : Rack Mount Chassis | ||
| Chassis Part Number : | ||
| Chassis Serial : | ||
| Board Mfg Date : Wed Nov 7 02:43:00 2012 | ||
| Board Mfg : Dell Inc. | ||
| Board Product : PowerEdge | ||
| Board Serial : CN0D61XP747512B60255A08 | ||
| Board Part Number : 282BNP0616 | ||
| Product Manufacturer : Dell Inc. | ||
| Product Name : C6100 | ||
| Product Part Number : | ||
| Product Version : | ||
| Product Serial : DB3KYV1 | ||
| Product Asset Tag: |
There was a problem hiding this comment.
This block needs to be further indented to be a code block
There was a problem hiding this comment.
It must be something with the browser cache when reviewing with 'make serve'. They were all code blocks but refreshes would break the formatting. Ill put them back in.
|
My understanding is any system with IPMI. I cannot confirm without additional systems to test it against. This is due to a lack of "other" systems to test with. I do have access to a few sunfire x4170's and several Dell servers, but that is all. I can test reading the fru on some Joyent systems if youd like. |
|
As far as I can tell I'm pretty sure that I addressed all of the requested changes. In my browser it looks correct at least on my local machine. Let me know if I missed anything. The double indent code blocks seem to work sporadically at best. So I had to leave the majority of them as backticked blocks. On a side note I reworded quite a bit so the commit may look a little messy. I can kill it and refork if you prefer more clean commits. |
2 participants
As requested by @bahamat on sdc-discuss list...updated smartos-docs with the 'ipmitool' work around for undetected Triton compute nodes, caused by duplicate bios serial numbers in SmartOS
sysinfocommand.https://smartdatacenter.topicbox.com/groups/sdc-discuss/Tab6106d9af955d74/servers-not-appearing-in-sdc-server-list-or-operator-portal