3.1.3 controlled release

[ascheale]

Just for Information Sharing ...

On Friday we did an update to our 7200 starting from 3.1.2 MU2.
All went Fine until node 0 was rebooted by SP.

Id did not come up again. Management is totally unavailable at the moment.
Good thing is, that HP Support Center called me a few minutes later.

Next step is to reboot node 0 by serial connection on monday.

Strange thing is that node 1 is still serving IO but management is totally unavailable.

Keep you up2date

Alex

[Darking]

We did have our array upgraded to 3.1.3

I cant claim it went totally uneventfull, but my upgrade succeded, though with a strange task failed error:

2014-04-04 123330 CEST Error t2cpg NL_r6 is already associated with an AO configuration.
2014-04-04 123330 CEST Error Task exited with status 1
2014-04-04 123330 CEST Failed Could not complete task.

It made little sense to my why it would fail, since i only have a single AO, which is a three tier one. albeit it is not the one the array originally came with.

Its been running now for the last week without issue, and im moving into production tomorrow.

So crossing fingers ofcause

[hdtvguy]

Great, now I am getting nervous we have our arrays set for 3.1.3 at the end of the month. And we just had a huge array outage on top of that.

[ascheale]

Be aware that it is a controlled release and not the final one - HP told me this several times.

I solved my problem today.
It seems that the inserv cluster lost its ip address after reboot of node 1.
After setting the correct address per serial console i was able to ping the node.
Both nodes seemed to be at 3.1.3.

My SP told me another thing ... It was on 3.1.2 MU3.
Well, i did the upgrade a second time and now it worked.

Glad to see, that IO was served all the time, even when ip access was lost.

Regards,
Alex