Can I vparmodify a boot path without taking down the vPar?

[Robert Bennett_3]

The alternate boot path is wrong on one of our vPars and I would like to issue the following command:
vparmodify -p vpar1 -d io:x/x/x/x -a io:y/y/y/y/y.

From what I've read, the only vpar modification that can be done while the vpar is up is add/delete unbound CPUs.

Any work arounds?

[Jeff Schussele]

Hi Robert,

No....I'm pretty sure you can do this online.
BUT - you don't need the -d AND you need to add :ALTBOOT *immediately* following the HW path - NO space.
You just need the par_name "-p" & alternate boot path "-a" parms....and....you could designate both by appending either :BOOT or :ALTBOOT to -a parm HW path.

HTH,
Jeff

[Jeff Schussele]

OH...and I forgot to add that IF you're IN the vpar you wish to modify - you can use the setboot command as you normally would...

setboot -a 0/8/0/0/0.2

for example.

HTH,
Jeff

[Robert Bennett_3]

vparmodify -p vpar1 -a io:7.0.9.0.0.4.0.0.0:ALTBOOT

gives:
vparmodify: Error: Virtual partition dnux071 must be in the Down state.

[Robert Bennett_3]

setboot gives me:
Alternate bootpath : 7/0/9/0/0.4.0

I understand that this path - which is different than 7/0/9/0/0/4/0.0.0 - is a result of using the setboot command.

So the question remains, but as an addition, why is the setboot command giving us a bad result?

[Robert Bennett_3]

I'm putting in our procedures that all vpars are to have their boot paths checked during reboot, simple enough, and repaired as needed during that time. Probably a good procedure on any server, but other servers can be fixed with a setboot command while up and vpars have their own little quirks. Downtime gets rarer and rarer in these parts.

Thanks Jeff for the help - but it doesn't look like a vpar bootpath can be changed unless the vpar is down. It sure would be nice to be able to do it hot though.