VPAR Console switch

[Daniel M. Gonzales]

We have an npar with 6 vpars (v4.05). According to "vparstatus -m", the console path belonged to the first vpar. We then deleted the first vpar and now the console path shows as a free resource (vparstatus -A). We were expecting to see problems on the console (switching from vpar to vpar with Ctrl-a), but everything seems normal. Did something change with v4.05? What happens with the console with the next reboot of the npar? Do we need to re-assign the console path to one of the existing vpars as a precautionary measure?

[melvyn burnard]

What system type are you running the Vpars on?
Integrity? If so then you do not have to specifically assign the physial console like on a PA-RISC server.

[likid0]

If you are using Integrity servers, there is no need to have the console path assigned to any vpar, but I allways assign it to the machine that boots the vpar monitor, but that's legacy vices.

[Daniel M. Gonzales]

Thanks guys, but the model type is 9000/800/SD64B.

[Torsten.]

This is a sx2000 superdome.

From the manual:

"vPars Console Assignment on sx2000-based Servers The consoleUART for sx2000-based servers
is no longer on a PCI card, and the system console is memory mapped and moved to PDH.
Hence, there is no LBA component for the console to be assigned to a virtual partition."



The path must be owned by the first vPar only on PA-RISC systems, not on Integrities.