Success!
Analysis of the serial port boot logs of the replacement node revealed the following error:
Code:
Prom Node ID Value and Slot ID mismatch. NodeID: 0 SlotID: 1
Which leads me to think there is a node ID value store in the EEPROM along with the serial numbers. Running
prom edit steps through a different set of values than
prom hp edit I tried yesterday, and sure enough Node ID is one of them:
Code:
Whack>prom edit
Board Spin: 04
Size * 256 bytes: 04
Board Class: 920
Board Base: 200040
Board Rev: A8
Assembly Vendor: FXN
Assembly Year: 2013
Assembly Week: 44
Assembly Day: 04
Assembly Serial: 02021391
System Serial: 1610528
Node ID: 00
Midplane Type: 1b
Node Type: 40
W19: 0fffffff
Whack>
Now this isn't node 0 it's supposed to be node 1, so I changed Node ID to 01, ran a quick
prom checksum which returned PASS instead of a fatal error, and then ran
go to complete the boot process. The node came up and after a few moments joined the cluster!
Code:
cli% shownode -i -svc
-------------------------------------------------------------------------Nodes--------------------------------------------------------------------------
Node --Name--- -Manufacturer- ---Assem_Part--- --Assem_Serial-- -Saleable_Serial- --Saleable_PN--- ----Spare_PN---- -------Model_Name------- -Assem_Rev-
0 1610528-0 FXN QR483-63001 PCMBUA3TM3K03U 2MD25201SL QR483A 683246-001 HP_3PAR 7400 004
1 1610528-1 FXN QR483-63001 PCMBUA8TM5M0ZV 2MD25201SL QR483A 683246-001 HP_3PAR 7400 004
There is still an error in the management console
Code:
Cage 0, Interface Card 1 Failed (Interface Card Firmware Unknown {0x0} )
that needs further troubleshooting but that may be a separate issue. Needless to say I am *very* relieved to have this up and running. Thanks everyone for your ideas and suggestions through this process.