Paging Space Handling in IBM AIX and Hp_UNIX

Paging Space in IBM AIX: Recorded at "/etc/swapspace" file

# lsps -a : List the available paging space.

# lsps -s : Summary about the paging space.

# mkps -a -n -s <No.of PP's> <Volume_Group_Name> <Physical_Volume_Name> : Command to create a Paging Space.

# swapon <paging_device> : Activate a paging space.

# swapoff /dev/<paging_device> : Deactivate a paging space.

# rmps <paging_device> : Remove a paging device.

# chps -a y/n : Enable/Disable Auto on feature of the paging device.

# chps -d <PP Count> <paging_space> : Decrease the size of the paging device.

# chps -s <PP Count> <paging_space> : Increase the size of the paging device

Swap Space in Hp_Unix: Recorded in "/etc/fstab"

# swapinfo -dtm : Command to list the swap space on the machine.

# lvcreate -L <Size of Swap> -n <Swap_Name> -C y <Volume_Group_Name> : Command to create a swap space. -C refer to continous logical space.

# swapon /dev/volume_group_name/swap_space_name

Handling Stale Partitions in AIX and HP_Unix

IBM AIX :

# syncvg -v <Volume Group name> : Syncronize all the stale partition on the volume group.

# syncvg -p <Physical Volume name> : Syncronize all the stale partition on the physical volume.

# syncvg -l <Logical Volume name> : Syncronize all the stale partition on the logical volume.


Hp_UNIX:

# vgsync /dev/<volume group name> : Syncronize the volume group.

# lvsync /dev/volume_group_name/logical_volume_name : Syncronize the logical volume.

Mirrroing Constraints in IBM AIX and HP_UNIX

Steps to mirroring in IBM AIX:

1) # lspv : Command to view the Physical volume in none state.

2) # mkvg -y <vgname> -s <PP Size> <Physical Volumes.....> : Command to create a Volume Group.

3) # mklv -y <lvname> -t <filesystem type> -c <no.of. copies> <volume group name> <no.of PP's> <Physical Volume Names> : Command to create a logical volume.

4) # crfs -v <filesystem type> -d </dev/logical_volume_name> -m <mount point> -A y : Command to create a file system.

5) # mount /<mount point> : Command to mount a file system.

Hp_Unix

1) # isocan -funC disk : Command to view the disk available in the machine.

2) # pvcreate /dev/rdsk/c0t0d0 : Command to create a physical volume.
    # pvcreate /dev/rdsk/c0t0d1 : Command to create a physical volume.

3) # vgcreate <Volume Group name> /dev/dsk/c0t0d0 /dev/dsk/c0t0d1 : Command to create a volume group.

4) # vgdisplay -v <Volume Group name> | grep "PV Name" : View the physical volumes that created this volume group.

5) # lvcreate -n <Name of the logical volume> -L <Size of the logical volume> -m <no.of.copies> <volume group name>

6) # lvdisplay -v <logical volume name> : View the created a logcial volume with copies on the physical volume.

7) # newfs -F vxfs <Raw logical volume name> : Command to format the logical volume.

8) # mount <logical volume name > <mount point> : Command to mount.

Migration of Stand Alone SCSI Data to Virtual SCSI Data _ IBM AIX Part III

Now we modify the VIOS Profile to add the SCSI Adapter which we removed from the AIX_Server.

Select the adapter and click on "Add as Required".


1) Login to VIOS as "padmin" and execute $ cfgdev


$ lsdev | grep vhost : Command to locate the newly created vhost adapter.

host0 Available Virtual SCSI Server Adapter

vhost1 Available Virtual SCSI Server Adapter

vhost2 Available Virtual SCSI Server Adapter

vhost3 Available Virtual SCSI Server Adapter

vhost4 Available Virtual SCSI Server Adapter


vhost4 is the newly created Virutal SCSI Server Adapter.


$ lsmap -vadapter vhost4


2) Now locate the new disk mapped to the VIOS.


$ lsdev -type disk

name status description

hdisk0 Available SAS Disk Drive

hdisk1 Available SAS Disk Drive

hdisk2 Available SAS Disk Drive

hdisk3 Available SAS Disk Drive

hdisk4 Available SAS Disk Drive

hdisk5 Available SAS Disk Drive

hdisk6 Available SAS Disk Drive

hdisk7 Available SAS Disk Drive

hdisk8 Available 16 Bit LVD SCSI Disk Drive


hdisk8 has been added and is a SCSI disk.


3) Confirm that the hdisk8 has the same UDID of the one found in AIX_Server.


$ chkdev -dev hdisk8 -verbose

NAME: hdisk8

IDENTIFIER: 22080004B9710BST3146807LC03IBMscsi

PHYS2VIRT_CAPABLE: YES

VIRT2NPIV_CAPABLE: NA

VIRT2PHYS_CAPABLE: NA

IEEE:

VTD:


4) Now, map the disk from the VIOS to the Client Partition.


$ mkvdev -vdev hdisk8 -vadapter vhost4
vtscsi0 Available


5) Verify the mapping.


$ lsmap -all or lsmap -vadapter vhost4

$ lsmap -vadapter vhost4

SVSA Physloc Client Partition ID

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

vhost4 U8204.E8A.10FE401-V1-C15 0x00000000

VTD vtscsi0

Status Available

LUN 0x8100000000000000

Backing device hdisk8

Physloc U78A0.001.0000000-P1-C4-T2-L1-L0


Now login into the client partition and execute # cfgmgr and # lspv to locate the new disk.

PVID: 002631cd31ad04f50000000000000000

UDID: 22080004B9710BST3146807LC03IBMscsi

Migration of Stand Alone SCSI Data to Virtual SCSI Data _ IBM AIX Part II

On HMC:


1) Modify the AIX_Server partition profile, So that the SCSI Adapter is removed. Upon removing the adapter, Save the partition profile.

Select the adapter with the slot number obtained from the # lscfg -vpl ssiscsia0 output. Once the adapter is selected then click on "Remove".


Next we need to create virtual server SCSI adapter and virtual client SCSI adpter to map the disk.


Select the VIOS Server. The "vhost#" adapter could be added through Dynamic Operation or through Manage Profiles.


Select the "VIOS Server"-->Tasks-->Configurations-->Manage Profile-->Virtual Adapter-->Action-->Create-->Virtual SCSI Adapter.

Same the same process to add a virtual SCSI client adapter on the client LPAR.


Continued...Part III

Migration of Stand Alone SCSI Data to Virtual SCSI Data _ IBM AIX Part I

The below process shows the migration of data from a Standalone SCSI Disk to a LPAR Managed by a VIOS.

Step 1 on AIX_Server:

1) Identify the disk that has to be moved to the LPAR.

# lspv

hdisk0 002631cd31ad04f5 rootvg

active

2) Check the disk to be migrated have a unique UDID.

# lsattr  -EHL hdisk0

PCM PCM/friend/scsiscsd Path Control Module

False

algorithm fail_over Algorithm

True

dist_err_pcnt 0 Distributed Error Percentage

True

dist_tw_width 50 Distributed Error Sample Time

True

hcheck_interval 0 Health Check Interval

True

hcheck_mode nonactive Health Check Mode

True

max_transfer 0x40000 Maximum TRANSFER Size

True

pvid 002631cd31ad04f5

False

queue_depth 3 Queue DEPTH

False

reserve_policy single_path Reserve Policy

True

size_in_mb 146800 Size in Megabytes

False

0000000000000000 Physical volume identifier

unique_id 22080004B9710BST3146807LC03IBMscsi

False

3) Identify the parent of the hdisk0

# lsdev -Cl hdisk0 -F parent

scsi1

# lsdev -l scsi1 -F parent

sisscsia0

So the hdisk0 is attached to the scsi1 which has the parent sisscsia0.

4) Next step is to identify any the resources attached to the same sisscsia0.

# lsdev | grep -i siscsia0
sisscsia0 Available 00-08 PCI-X Dual Channel Ultra320 SCSI Adapter

# lsdev | grep "00-08"

hdisk0 Available 00-08-01-1,0 16 Bit LVD SCSI Disk Drive

scsi0 Available 00-08-00 PCI-X Dual Channel Ultra320 SCSI Adapter bus

scsi1 Available 00-08-01 PCI-X Dual Channel Ultra320 SCSI Adapter bus

ses0 Available 00-08-00-14,0 SCSI Enclosure Services Device

ses1 Available 00-08-00-15,0 SCSI Enclosure Services Device

ses2 Available 00-08-01-14,0 SCSI Enclosure Services Device

ses3 Available 00-08-01-15,0 SCSI Enclosure Services Device

sisscsia0 Available 00-08 PCI-X Dual Channel Ultra320 SCSI Adapter

So only one hdisk is allocated to the sisscsia0.

5) Obtain the hardware location code of the drive.

# lscf g -vpl siscsia0

sisscsia0 U78A0.001.0000000-P1-C4 PCI-X Dual Channel Ultra320 SCSI

Adapter

PCI-X Dual Channel Ultra320 SCSI Adapter:

Part Number.................97P3359

FRU Number..................97P3359Hardware Location Code......U78A0.001.0000000-P1-C4

6) Shutdown the AIX_Server with the shutdown command.

Continued...in Part II

Serial Number...............YL10C4061142

Manufacture ID..............000C

EC Level....................0

ROM Level.(alterable).......05080092

Product Specific.(Z0).......5702

Unique device identifier