jpaul wrote:
I have a five-rack Onyx2 that I've had for some time now that I'm trying to bring back to the land of the living....Difficulty: I appear to have only one working MMSC, so I'm doing this all by hand.
Having a working MMSC per rack would make setting up a five-rack configuration a more user-friendly proposition. If you have non-working MMSCs in the other four racks, you may be able to revive them. The power supply in the MMSC is not known for longevity. There have been a number of topics on nekochan that discuss replacing the OEM power supply with an ATX-style PS (
Pontus has even supplied a few photos of the conversion). If you'd rather not use an external supply, some MMSCs used an Artesyn NFN40-7608 PS, if you'd like additional details or specifications,
the data sheet for that PS is available as a PDF. This nekochan post mentions the
Mean Well PT-65B as a drop in replacement for the MMSC power supply. The Mean Well PT-65B
seems to be readily available in the $20 - $30 range (depending on the source).
Quote:
My problem seems to be working out how to dictate the Global Master so I know who the head-node is. I seem to have fairly good luck bringing up three racks and getting it booting into IRIX, but when I add the other two racks, the Global Master tends to waffle around (/hw/module/2/n/1? No, wait, now it's 3/n/1. Make a decision!)
I had initially assumed that the last rack powered on would always become the Master, but this isn't the case, so there must be some way of telling it what's what when manually bringing things up. Any help would be gratefully received.
Haven't ever tried a multi-rack O2k/Onyx2 without using a linked MMSC per rack, but it might be possible the module numbers assigned in each individual PROM conflict, and the assignment of master ends up being which ever module that completes power on diagnostics first. If that's the case, (and you haven't already done so), you might take a look at the PROM commands "modnum" and "mvmodule". Depending on your PROM revision, you should be able to bring up brief usage synopses at the PROM command line by querying "help modnum" or "help mvmodule" (you may find assigning module numbers easier if you connect directly to the MSC of each unlinked compute module separately).
O2K/Onyx2 hardware stores an inventory found during the last successful power-on diagnostics session, if you change the location or configuration of what the inventory expects, the power-on diagnostics routine doesn't always play nice and may disable relocated, unexpected or unconfigured hardware as a fail-safe. If that happens, or you'd like to make sure any changes you've made have been assimilated,
there's some background on the process of clearing stale entries from the power-on diagnostic (POD) logs in this thread. And for what its worth, If I were faced with the same situation I'd probably work on getting each individual rack up and running to minimize headaches when you CrayLink all five.
Good luck with the system!