SANDEEP TANTI'S UNIX-AIX WORLD: 11/11/13

DOCUMENT TO CREATE LOGICAL PARTITION (LPAR )

GO TO HMC SELECT MANAGED SYSTEM IN WHICH YOU WANT TO CREATE LPAR
>> SELECT THE MENU SHORTCUT BESIDES THE MANAGED SERVER OR SELECT TASKS FROM TOP >> SELECT CONFIGURATUONS >> SELECT CREATE LOGICAL PARTITION

PROVIDE THE NAME OF LPAR AND LPAR PROFILE NAME AS SHOWED IN THE NEXT SCREEN

PLEASE SELECT THE NAME OF THE LPAR AND PROFILE NAME BY DETERMINING A NAMING SCHEME THAT SUITS FOR YOUR ENVIRONMENT

THE NEXT OPTION GIVES YOU DETAILS ABOUT SELECTING PROCESSOR SCHEME
THE CURRENT OPTIONS ARE SHARED AND DEDICATED
IF YOU SELECT SHARED PROCESSOR YOU CAN CONFIGURE MICRO PROCESSOR
IF YOU SELECT DEDICATED PROCESSOR YOU CAN ASSIGN WHOLE (PHYSICAL) PROCESSOR ONLY
NOTE IF APV IS NOT ACTIVATED ON THE PARTITION THE SHARED OPTION COULD NOT BE SELECTED AS SHOWN IN THE FIGURE BELOW

SELECT MINIMUM MAXIMUM AND DESIRED PROCESSOR VALUE
MINIMUM PROCESSOR IS THE VALUE WITHOUT WHICH THE LPAR COULD NOT BE STARTED
DESIRED IS THE OPTIMUM VALUE IN IDEAL CONDITION IF THE RESOURCES IS AVAILABLE AND LPAR WILL TRY TO AQUIRE THAT VALUE IF AVAILABLE
MAXIMUM VALUE IS THE VALUE ABOVE WHICH THE LPAR CANNOT AQUIRE EVEN IF THE RESOURCE IS AVAILABLE IN SHARED POOL

READ THE LINK TO KNOW MORE ABOUT SHARED PROCESSOR

http://publib.boulder.ibm.com/infocenter/powersys/v3r1m5/index.jsp?topic=/iphat/iphatsharedproc.htm

IF APV ACTIVATION CODE IS PROVIDED YOU CAN SELECT SHARED OPTION ALSO
SELECT SHARED OPTION AND YOU CAN SEE LOTS OF NEW OPTIONS IN THE NEXT IMAGE

IN THE ABOVE IMAGE THE OPTIONS WERE MIN PROC DES PROC AND MAX PROC

NOW YOU CAN FIND MIN PROC UNITS DES PROC UNITS AND MAX PROC UNITS IT CLEARLY SHOWS THAT NOW YOU CAN CONFIGURE MICRO PARTITIONS

YOU ALSO HAVE TO ASSIGN VIRTUAL PROCESSORS ACCORDING TO THE PHYSICAL PROCESSOR PROVIDED

YOU CAN KNOW MORE ABOUT VIRTUAL PROCESSORS BY READING FOLLOWING DOCUMENT

http://publib.boulder.ibm.com/infocenter/powersys/v3r1m5/index.jsp?topic=/iphat/iphatvirtualproc.htm

TO KNOW HOW MUCH VIRTUAL PROCESSOR YOU NEED READ THE DOCUMENT
http://publib.boulder.ibm.com/infocenter/idshelp/v10/index.jsp?topic=/com.ibm.admin.doc/admin242.htm

PROVIDE MINIMUM MAXIMUM AND DESIRED MEMORY SETTING FOR THE LPAR
THE CONCEPT FOR MINIMUM MAXIMUM AND DESIRED VALUES ARE SAME AS PROCESSOR

PROVIDE THE IO ADAPTER , FOR EXAMPLE IN A TYPICAL CONFIGURATION PROVIDE A FC ADAPTER AS REQUIRED AND A CDROM/DVD ADAPTER IF AVAILABLE AS DESIRED , ALSO PROVIDE A NETWORK ADAPTER AS REQUIRED

OR CREATE VIRTUAL SCSI ADAPTER AND VIRTUAL ETHERNET ADAPTER ON THE LPAR

SELECT BOOT MODE AND OPTIONAL SETTING OF THE LPAR

IN THE END IT WILL SHOW YOU SUMMARY OF LPAR JUST CREATED

YOU CAN NOW FIND THE NEWLY LPAR CREATED , SELECT THE FAST PATH MENU BESIDES THE LPAR AND SELECT ACTIVATE

STEP BY STEP DOCUMENT TO UNDERSTAND DISK ASSIGNMENT

Get “Lpar id” very useful in detecting lpar on managed system

root@reports[/]-> uname -L

17 reporting

Get serial number helpful in detecting in which managed system lpar resides

root@reports[/]-> uname -a

AIX reports 1 6 00C5FE554C00

Check all the pv present on lpar

root@reports[/]-> lspv

hdisk0 00c5fe55cfd2b2a5 rootvg active

hdisk1 00c5fe55cfd2b31d swapvg active

hdisk2 00c5fe55cfd2b394 swapvg active

hdisk22 00c5fe55cfd2c441 suptoolsvg active

hdisk23 00c5fe55c57a7348 altinst_rootvg

GETTING INFORMATON ON VIO

Get all the pv present on the vio

padmin@and001vio[/home/padmin]-> lspv

NAME PVID VG STATUS

hdisk0 00c5fe5572e3b206 rootvg active

hdisk1 00c5fe5520c5f6a3 rootvg active

hdisk2 00c5fe65af1240bc None

hdisk3 00c5fe55cff110f1 None

hdisk4 00c5fe55cff111b6 None

hdisk5 00c5fe55cff11276 None

hdisk6 00c5fe55cff1133d None

hdisk113 none None

hdisk114 none None

Detect New Device

padmin@and001vio[/home/padmin]-> cfgdev

Some error messages may contain invalid information

for the Virtual I/O Server environment.

cfgmgr: 0514-621 WARNING: The following device packages are required for

device support but are not currently installed.

devices.fcp.array

Now again check the New disk

padmin@and001vio[/home/padmin]-> lsdev -type disk|grep hdisk

hdisk0 Available SAS Disk

hdisk1 Available SAS Disk

hdisk2 Available SAS Disk

hdisk3 Available MPIO 2810 XIV

hdisk4 Available MPIO 2810 XIV

hdisk112 Available MPIO 2810 XIV

hdisk113 Available MPIO 2810 XIV Disk

hdisk114 Available MPIO 2810 XIV Disk

Check that Whether the disk is provided to any other vhost or not

padmin@and001vio[/home/padmin]-> lsmap -all -field backing|grep hdisk113

Backing device hdisk113

padmin@and001vio[/home/padmin]-> lsmap -all -field backing|grep hdisk114

or run command lspv -free

Check the vhost related to lpar

As these vhosts are related with lpar id 11(hex) , 17(decimal) , this means these vhosts are provided to lpar id 17 (we saw the lpar id at lpar by typing uname –L)

padmin@and001vio[/home/padmin]-> lsmap -all -field svsa clientid

SVSA Client Partition ID

--------------- -------------------

vhost18 0x00000010

SVSA Client Partition ID

--------------- -------------------

vhost19 0x00000011

SVSA Client Partition ID

--------------- -------------------

vhost20 0x00000011

SVSA Client Partition ID

--------------- -------------------

vhost21 0x00000011

SVSA Client Partition ID

--------------- -------------------

vhost22 0x00000011

SVSA Client Partition ID

--------------- -------------------

vhost23 0x00000003

Check details of the vhost adapters associated with the lpar

padmin@and001vio[/home/padmin]-> for x in vhost19 vhost20 vhost21 vhost22

> do

> lsmap -vapter $x

> done

SVSA Physloc Client Partition ID

--------------- -------------------------------------------- ------------------

vhost19 U8204.E8A.105FE55-V1-C71 0x00000011

VTD
repbi01_1

Status Available

LUN 0x8500000000000000

Backing device hdisk72

Physloc U78A0.001.DNWHL4W-P1-C2-T1-W50017380053D0140-L460000000000

VTD repbi02_1

Status Available

LUN 0x8600000000000000

Backing device hdisk73

Physloc U78A0.001.DNWHL4W-P1-C2-T1-W50017380053D0140-L470000000000

VTD repptmp_1

Status Available

LUN 0x8400000000000000

Backing device hdisk71

Physloc U78A0.001.DNWHL4W-P1-C2-T1-W50017380053D0140-L450000000000

VTD reprootvg_1

Status Available

LUN 0x8100000000000000

Backing device hdisk13

Physloc U78A0.001.DNWHL4W-P1-C2-T1-W50017380053D0140-LB00000000000

VTD reprootvg_2

Status Available

LUN 0x8800000000000000

Backing device hdisk105

Physloc U78A0.001.DNWHL4W-P1-C2-T1-W50017380053D0140-L670000000000

VTD repswap_1

Status Available

LUN 0x8200000000000000

Backing device hdisk14

Physloc U78A0.001.DNWHL4W-P1-C2-T1-W50017380053D0140-LC00000000000

VTD repswap_2

Status Available

LUN 0x8300000000000000

Backing device hdisk15

Physloc U78A0.001.DNWHL4W-P1-C2-T1-W50017380053D0140-LD00000000000

VTD reptsuptool_1

Status Available

LUN 0x8700000000000000

Backing device hdisk70

Physloc U78A0.001.DNWHL4W-P1-C2-T1-W50017380053D0140-L440000000000

SVSA Physloc Client Partition ID

--------------- -------------------------------------------- ------------------

vhost20 U8204.E8A.105FE55-V1-C73 0x00000011

VTD repdb01_1

Status Available

LUN 0x8100000000000000

Backing device hdisk74

Physloc U78A0.001.DNWHL4W-P1-C2-T1-W50017380053D0140-L480000000000

VTD repdb02_1

Status Available

LUN 0x8200000000000000

Backing device hdisk75

Physloc U78A0.001.DNWHL4W-P1-C2-T1-W50017380053D0140-L490000000000

VTD repdb03_1

Status Available

LUN 0x8300000000000000

Backing device hdisk76

Physloc U78A0.001.DNWHL4W-P1-C2-T1-W50017380053D0140-L4A0000000000

VTD repdb04_1

Status Available

LUN 0x8400000000000000

Backing device hdisk77

Physloc U78A0.001.DNWHL4W-P1-C2-T1-W50017380053D0140-L4B0000000000

VTD repdb05_1

Status Available

LUN 0x8500000000000000

Backing device hdisk78

Physloc U78A0.001.DNWHL4W-P1-C2-T1-W50017380053D0140-L4C0000000000

VTD repdb13_1

Status Available

LUN 0x8300000000000000

Backing device hdisk86

Physloc U78A0.001.DNWHL4W-P1-C2-T1-W50017380053D0140-L540000000000

VTD repdb14_1

Status Available

LUN 0x8400000000000000

Backing device hdisk87

Physloc U78A0.001.DNWHL4W-P1-C2-T1-W50017380053D0140-L550000000000

VTD repdb15_1

Status Available

LUN 0x8500000000000000

Backing device hdisk88

Physloc U78A0.001.DNWHL4W-P1-C2-T1-W50017380053D0140-L560000000000

VTD repdb16_1

Status Available

LUN 0x8600000000000000

Backing device hdisk89

Physloc U78A0.001.DNWHL4W-P1-C2-T1-W50017380053D0140-L570000000000

Above output shows that the lpar id 11 (decimal 17 ) is associated with vhost 19 20 21 and 22

LPAR side configuration

Check for all the vscsi available on the LPAR

root@reports[/]-> lsdev -Cc adapter|grep vscsi

vscsi0 Defined Virtual SCSI Client Adapter

vscsi1 Available Virtual SCSI Client Adapter

vscsi2 Available Virtual SCSI Client Adapter

vscsi3 Available Virtual SCSI Client Adapter

vscsi4 Available Virtual SCSI Client Adapter

vscsi5 Available Virtual SCSI Client Adapter

vscsi6 Available Virtual SCSI Client Adapter

vscsi7 Available Virtual SCSI Client Adapter

vscsi8 Available Virtual SCSI Client Adapter

Check for "adapter id" for all the vscsi adapters . After checking adapters id we can go to the properties of lpar and see which adapter is provided by which vio , (adapter client id “C11” is the identification), After recognizing the vio server we can go to vio server properties and verify which server adapter connects with which client scsi adapter .Hence we can decide to which server scsi adapter the disk needs to be provided

root@reports[/]-> for x in $(lsdev -Cc adapter|grep vscsi|awk '{print $1}')

> do

> echo $x

> lscfg -vl $x

> done

vscsi0

vscsi0 U8204.E8A.105FE55-V17-C11-T1 Virtual SCSI Client Adapter

Hardware Location Code......U8204.E8A.105FE55-V17-C11-T1

vscsi1

vscsi1 U8204.E8A.105FE55-V17-C71-T1 Virtual SCSI Client Adapter

Hardware Location Code......U8204.E8A.105FE55-V17-C71-T1

vscsi2

vscsi2 U8204.E8A.105FE55-V17-C72-T1 Virtual SCSI Client Adapter

Hardware Location Code......U8204.E8A.105FE55-V17-C72-T1

vscsi3

vscsi3 U8204.E8A.105FE55-V17-C73-T1 Virtual SCSI Client Adapter

Hardware Location Code......U8204.E8A.105FE55-V17-C73-T1

vscsi4

vscsi4 U8204.E8A.105FE55-V17-C74-T1 Virtual SCSI Client Adapter

Hardware Location Code......U8204.E8A.105FE55-V17-C74-T1

vscsi5

vscsi5 U8204.E8A.105FE55-V17-C75-T1 Virtual SCSI Client Adapter

Hardware Location Code......U8204.E8A.105FE55-V17-C75-T1

vscsi6

vscsi6 U8204.E8A.105FE55-V17-C76-T1 Virtual SCSI Client Adapter

Hardware Location Code......U8204.E8A.105FE55-V17-C76-T1

vscsi7

vscsi7 U8204.E8A.105FE55-V17-C77-T1 Virtual SCSI Client Adapter

Hardware Location Code......U8204.E8A.105FE55-V17-C77-T1

vscsi8

vscsi8 U8204.E8A.105FE55-V17-C78-T1 Virtual SCSI Client Adapter

Hardware Location Code......U8204.E8A.105FE55-V17-C78-T1

VIO SIDE CONFIGURATION

We can use command lspv -free to know about free disk in vio server

Make sure that hdisk114 is not provided to any of vhost

padmin@and001vio[/home/padmin]-> lsmap -all -field backing|grep hdisk114

MAP hdisk114 to vhost19

padmin@and001vio[/home/padmin]->mkvdev –vadapter vhost 19 -vdev hdisk114 -dev repbi02_2

repbi02_2 Available

padmin@and001vio[/home/padmin]->

ON THE LPAR SIDE

See the disks at LPAR

root@reports[/]-> lspv

hdisk0 00c5fe55cfd2b2a5 rootvg active

hdisk1 00c5fe55cfd2b31d swapvg active

hdisk2 00c5fe55cfd2b394 swapvg active

hdisk22 00c5fe55cfd2c441 suptoolsvg active

hdisk23 00c5fe55c57a7348 altinst_rootvg

Run Device configuration utility

root@reports[/]-> cfgmgr

Method error (/usr/lib/methods/cfg_vclient -l vscsi0 ):

0514-040 Error initializing a device into the kernel.

Check for the assigned disk

root@reports[/]-> lspv

hdisk0 00c5fe55cfd2b2a5 rootvg active

hdisk1 00c5fe55cfd2b31d swapvg active

hdisk2 00c5fe55cfd2b394 swapvg active

hdisk23 00c5fe55c57a7348 altinst_rootvg

hdisk24 none None

Now rest is the simple task

root@reports[/]-> extendvg repbi02vg hdisk24

0516-1254 extendvg: Changing the PVID in the ODM.

root@reports[/]->

SANDEEP TANTI'S UNIX-AIX WORLD

Tanti Technology

Monday 11 November 2013

STEP BY STEP -CREATION OF LPAR

UNDERSTANDING DISK ASSIGNMENT FROM VIO TO LPAR