| Advertise on warmetal.nl! Click for more information about advertising here. |
Did you find this website useful? Did I save you a lot of time? |
|
IVM storage has to be MPIO or has to be part of a volume group, as in, it need a PVID, a Physical Volume Identifier. If those requirements are not met you cannot assign storage to a LPAR in IVM. Since we also boot from the IQstor it's not possible to install the MPIO software from IQstor, booting is not supported and will fail (we tried, it won't work). So MPIO is not an option, so the only solution is to create a PVID for the hdisks.
$ oem_setup_env
List current physical volumes:
# lspv hdisk0 000a447aa92d7d0a rootvg active hdisk1 none None hdisk2 000a447ab395ffe2 None hdisk3 none None
Discover new physical volumes:
# cfgmgr # lspv hdisk0 000a447aa92d7d0a rootvg active hdisk1 none None hdisk2 000a447ab395ffe2 None hdisk3 none None hdisk4 none None hdisk5 none None
Create a volume group (this will create a PVID for the disk) and then remove the volume group:
# mkvg -y testvg hdisk4 0516-1254 mkvg: Changing the PVID in the ODM. testvg # lspv hdisk0 000a447aa92d7d0a rootvg active hdisk1 none None hdisk2 000a447ab395ffe2 None hdisk3 none None hdisk4 000a447ac234793d testvg active hdisk5 none None # reducevg testvg hdisk4 ldeletepv: Volume Group deleted since it contains no physical volumes.
Now the disk has a PVID:
# lspv hdisk0 000a447aa92d7d0a rootvg active hdisk1 none None hdisk2 000a447ab395ffe2 None hdisk3 none None hdisk4 000a447ac234793d None hdisk5 none None
Discussion