vparmodify syntax to delete a specific CPU from a vPar

[Alzhy]

Anyone? Trying to remove a deemed "bad CPU" from a running vPar. It is "unbound" so it should be removable - right?

Syntax that have failed:

vparmodify -p goofy -d cpu:3.12

or

vparmodify -p goofy -d cpu:3/12


Or am I getting the syntax wrong?

[Tim Nelson]

I would have thought that if it was truely bad there would have been an HPMC panic and the cpu deconfigured at the MP ?

[Alzhy]

There were no HPMC issues. HP just concluded that its a bad CPU. I quote their response:

"Analysis of the dump shows us that one of the CPU's registers didn't update correctly.
I would recommend that we open a hardware case to have the cpu at 3/12 CPU 1A replaced."

and to our question whtether there is an urgent need:

"A CPU problem can re-occur at any time. It could be in 10 minutes or 10 months. If you would like to try to wait till the weekend, that would be fine."

So, I thought to reduce the risk of a recurrence - and since CPU 3/12 is not "bound" that I can remove it and have it unused on any vPar.

FYI - this is a 64-cpu SuperDome - single nPar and 5-vPars. Very large memory environments.

And the vparmodify syntax does show that there is a "-d" and "cpu:path" option. But I tried it and it is complaining:

# vparmodify -p goofy -d cpu:3/12
vparmodify: Error: "-d cpu:3/11":Virtual partition fhp003e does not own the resource at this path.

root@mickey # vparstatus -v -p goofy|more
[Virtual Partition Details]
Name: goofy
State: Up
Attributes: Dynamic,Autoboot,Nosearch
Kernel Path: /stand/vmunix
Boot Opts:

[CPU Details]
Min/Max: 4/24
Bound by User [Path]:
Bound by Monitor [Path]: 0.10
0.11
0.12
0.13
Unbound [Path]: 3.12
3.13
3.14
3.15
3.16
3.17


Any ideas?

[Tim Nelson]

Now I am getting it.. Quite a delemma..

single out a non-bound, not currently used CPU.

Maybe it is not doable..

How about hard assigning all the other good procs ?
This would effectively leave the other out of the mix ?

The other option is to shutdown and disable that CPU from the BCH config option.

[melvyn burnard]

If you specify a cpu by it's hardware path, this immediately implies a bound cpu.
Since this cpu is not bound, you cannot use that syntax to remove it.
You will have to reduce the cpu count until it is no longer used, then mark it as unused aqt the BCH level I believe.