NPar won't reset

[Jakes Louw]

I have 2 nPar's configured on a SuperDome. The second nPar is split into 2 VPar's.
One of the VPar's died this morning, due to excessive use of resources (out of memory and out of swap), so couldn't do a "reboot", as it obviously couldn't spawn a process....
We managed to get a console connected to the GSP, got onto the right Admin console, and did a Reset (rs). The console then displays "Resetting partition", and that's all.

What are we doing wrong?

[melvyn burnard · Accepted solution]

have you tried doing a vparreset from hte other vpar system?
do vparstatus to check hte status of both vpars, get the vpar name of the "hung" vpar, hten vparreset it

[Alzhy]

The correct procedure would have been to go to the remaining vPar and issue checks from their -- vparstatus, etc.. To reboot the hung vPar -- you can do a vaparreset to fore a TOC. If the other vPar is dead as well and the nPar's Console is unresponsive (ie. you cannot get the MON prompt) -- then that i sthe only time you need to do an RS or a TC from GSP.

If it has not completely rebooted, chances are you will need to acknowledge alerts on the Console (CL) or chassis Logs (SL) so all error prompts are cleared out. Do a SL and CL and acknowledge what needs to be acknowelgded and you whould be on your way up... If the nPar's bootdisk (essentially the 1st vPar or vParmonitor loader) is configured to do an automatic load of VPMON (ie. Auto file is set to run "hpux /stand/vpmon" AND vpmon is configured to auto boot all the vPars -- then all vpars should come back up...

[Steve Robinson_12]

What version of vpars are you using? I suspect A.02.01. Suggest you update to A.02.02. You appear to have a problem with vpmon due to excessive io calls. vpmon is more robust at A.02.02, note further improvements to vpmon will be included in A.02.03 of vpars expected soon?

[Jakes Louw]

Hi guys: of course, being a Monday, I forgot all my sketchy training on Vpars.
At the end of the day, after dragging the manual closer (RTFM, eh?), we detected a related problem that would have bitten us later: even though our reset of the Npar from the console was a stupid move, we did find that the hard partition did not have "hpux /stand/vpmon" as the boot option, so we had to set that anyway, THEN we got the 2 vpars up. Thanks for the heads-up.