Veritas InfoScale™ 7.4.1 Virtualization Guide - AIX

To create an LPAR profile

1. Identify the disk on which the AIX OS is to be installed for the LPAR. This disk should be on shared storage in order for LPAR to be capable of failover across physical servers. Change the following attributes of the disk on all VIOS of the physical servers that the LPAR will be configured to boot on.

   vio1#chdev -a hcheck_cmd=inquiry -l hdisk7 
   vio1#chdev -a hcheck_interval=60 -l hdisk7 -P
   vio1#chdev -a pv=yes -l hdisk7
   vio1#chdev -a reserve_policy=no_reserve

2. Create the Virtual SCSI Host adapter on all VIOS on which the LPAR will be configured to boot on. Reboot the VIO, and then map the OS disk to this host adapter.
3. Log in to HMC and create the LPAR profile. The following example shows creating an LPAR profile.

   hscadmin1@hmc2.veritas.com:~> lssyscfg -r sys -F name
   	PServer1-SN100129A
   	PServer2-SN100130A
   
   hscadmin1@hmc2.veritas.com:~> lssyscfg -m PServer1-SN100129A -r lpar \
    -F name
   Pserver1_VIO1
   
   hscadmin1@hmc2.veritas.com:~> mksyscfg -m PServer1-SN100129A -r lpar \
   -i name=lpar_test,lpar_env=aixlinux,profile_name=lpar_test,min_mem=512,\
   desired_mem=512,max_mem=512,proc_mode=shared,sharing_mode=uncap,\
   uncap_weight=128,min_proc_units=0.1,desired_proc_units=0.4,\
   max_proc_units=2.0,min_procs=1,desired_procs=2,max_procs=4,\
   lpar_io_pool_ids=none,max_virtual_slots=10,auto_start=1,\
   boot_mode=norm,power_ctrl_lpar_ids=none,conn_monitoring=0,\
   virtual_eth_adapters=2/1/1//0/1,virtual_scsi_adapters=3/client/1//10/1"
   
   hscadmin1@hmc2.veritas.com:~> lssyscfg -m PServer1-SN100129A \
   -r lpar -F name        
   	Pserver1_VIO1
   	lpar_test

   The virtual Ethernet adapter's VLAN ID should match that of VIO server in order for connectivity to outside network, the virtual scsi adapter's remote-lpar-ID/remote-lpar-name/remote-slot-number should match with that of VIO's partition ID, VIO's name and VIO's virtual SCSI Host adapter ID that has the OS disk mapped for this LPAR. Note: The VIO's virtual SCSI Host adapter that is assigned for this LPAR should have any partition and any slot option if this LPAR is capable and might be used for LPM in future (in addition to VCS failover capability).

4. Create the same profile on all physical servers where the LPAR can fail over.
5. Verify that the LPAR can boot on the physical servers where the profile has been created.