HPE Storage Users Group

Hi,

Hope someone can maybe help.

We have inherited a 3PAR 8200 that has a node failure on it, We have manged to get a “new” node however the board revision is higher than the current and looks to be causing a software issue as we are running on 3.2.2 software...

The unit has been working fine but now we have the job of trying to "fix" this to get redudancy back. The company that provided the "new" node said we need todo sofatware upgrades. But we no contact we cant get the software todo the upgrades.. Do we just need to write the units off or is there another way that isnt going to break the bank ?

Release version 3.2.2 (MU4)
Patches: P51,P56,P59,P92,P94,P98,P101

Component Name Version
CLI Server 3.2.2 (P94)
CLI Client 3.2.2
System Manager 3.2.2 (P98)
Kernel 3.2.2 (MU4)
TPD Kernel Code 3.2.2 (MU4)
TPD Kernel Patch 3.2.2 (P98)

How did the old node die? Did the actual node die or did the internal drive fail?

If the node itself died, you could try and move the old internal disk to the new node. You probably need to follow the WHACK instructions here:
https://www.3parug.com/viewtopic.php?p=14666#p14666

If the old internal disk died, you can move the internal drive from the new node to the old node and do node rescue: https://support.hpe.com/hpesc/public/do ... cale=en_US

Hi,

Thanks for responding. So we moved the unit from one DC to another and it node 1 just loops. I have tried the recovery proccess and have also tried swapping disk and recovering again. Would seeing some logs help ?

Sure.

Console logs from the looping node could tell why it is rebooting and not integrating into the cluster.

Hi,

This is the log

https://pastebin.com/MGpqQNyU

Yeah, I'm blank on this one.

Is the serial number of your array CZ3711LMC5 and the node in question node1 in the system?

If yes, I have no idea.

If no, you need to enter WHACK menu to reset those values to the correct one and do a node rescue.

Hi,

Yesh that is correct on the serial and the node number