3PAR 8200 set perm sys_serial= only accepts numeric values.

[Alex rogozin]

set perm sys_serial_10= has no effect and even correct cluster serial is set in HP PROM, the OS still reports system serial as 0 once booted.

both nodes are botched so node rescue is a moot point.

while on the subject, a side question - who gave "nemoe" name to nemoe? in russian it means "not mine'. whack is appropriate.

[SUBHAJIT KHANBARMAN_1]

sys_serial is not applicable for 3PAR 8000 or later model of arrays. This is applicable for 3PAR 7000 or earlier models. That's why for 3PAR 8000 or later models always sys_serial should show 0 only.

For 3PAR 8000 or later models sys_serial_10 is applicable and if this value is set then Cluster serial number will visible.

Regarding naming of nemoe is not a technical query. It's HPE internal so can't comment on this.

Hope this helps!
Regards
Subhajit

I am an HPE employee

If you feel this was helpful please click the KUDOS! thumb below!

************************************************************************

[Alex rogozin]

that's what i've already figured out. now how do i fix it? tried prom hp edit to set the correct serial in hp prom, sys_serial_10, run ootb, performed deinstallation - all the same.

many thanks for your attention to this.

[SUBHAJIT KHANBARMAN_1]

you check if all nodes saleable serial number properly reflecting or not. use below command,

shownode -i -svc

If all nodes Saleable serial number fine then no need to do anything.

sys_serial_10 is to set Cluster serial number String if you want to see in banner output. If sys_serial_10 is not set then from banner output you will see Saleable serial number as String instead of Cluster Serial number as String.

From WHACK you can see banner output.

Request you not to use prom hp edit to correct Cluster serial number. This is to fix Saleable serial number only

Hope this helps!
Regards
Subhajit

I am an HPE employee

If you feel this was helpful please click the KUDOS! thumb below!

**********************************************************************

[Alex rogozin]

it wasn't.

the trouble was that whack w19 number didn't match OS - after set perm w19= to correct number system comes up as it should.

[tapelibraryfixr]

How do you work out the w19 variable?

[Alex rogozin]

it needs to match the W19 number of the boot disk.

[tapelibraryfixr]

Hi

So i made 2 boot disks, one works in the system, being the original and the other doesnt, it has the same os version.

but the new ssd doesnt have the same serial number that shows when you get to the login on the console, i couldnt change it.

Can you show a basic guide on what you did?

im not sure when you find the w19

Thanks

[Alex rogozin]

boot disks? if you have one controller with known console or 3paradm password, do the node recovery for the other one. in whack you need the node number to be correct. you can find me on instock901. Ale.

[tapelibraryfixr]

im thinking more about when im in the same situation as you were in you original post and cant node rescover etc.