vpar rebuild

[Leon Smith, Jr]

I have a clobbered /stand/pdb.dv3_1c_4g.and.pd3_7c_12g
file and as a result, I am unable to boot this vpar configuration. If I restore a previous version of if the file and copy it into the /stand/vpdb will I be able to boot to the old configuration or should I look to rebuild the configuration?

[Tim Nelson]

The other systems in the vPar should also have copies of this file.

It is usually updated with a vparstatus. What do you get when you execute vparstatus ?

[Leon Smith, Jr]

I have reconfigured it to a 4/4 cpu split so vparstatus shows the current configuration however if I try to use the clobbered file to boot from I get 7 cpu's plus memory up on one vpar and the other vpar is dead but should have 1 cpu plus memory

[Tim Nelson]

Is the vpar db ok on any of the other vPars ?

Are the other vPars up and running ?

If they are all down and you whacked the vpar database then you will just have to re-issue the vPar configuration commands. You will probably need to boot the first vPar out of vPar mode to do this. Once done go back and boot the vpmon and the other vPars.

[Leon Smith, Jr]

The vpars will boot using other configuration setups like vpdb.dv3_4c_8g.and.pd3_4c_8g only when i try to use vpdb.dv3_7c_12g.and.pd3_1c_4g is hang on the 1 cpu and wont come up. I want to move an old vpdb.dv3_7c_12g.and.pd3_1c_4g into /stand/vpdb and see if it will boot using an old unclobbered file.