Thoughts that's escape, only details.

pSeries Firmware Upgrade

root@localhost:/home/root/code#rpm -Uhv --ignoreos 01SF240_418_382.rpm
user fspbld does not exist - using root
group fspbld does not exist - using root
01SF240_418_382             ##################################################
root@localhost:/home/root/code#/usr/lpp/diagnostics/bin/update_flash -f /tmp/fwupdate/01SF240_418_382
The image is valid and would update the temporary image to SF240_418.
The new firmware level for the permanent image would be SF235_214.

The current permanent system firmware image is SF235_214.
The current temporary system firmware image is SF235_214.

***** WARNING: Continuing will reboot the system! *****

Do you wish to continue?
Enter 1=Yes or 2=No

Fri Feb  8 10:16:44 CST 2013
0513-044 The sshd Subsystem was requested to stop.
root@localhost:/home/root#/usr/lpp/diagnostics/bin/update_flash -c
The commit operation is in progress. Please stand by.

The commit operation was successful.

AIX – loopmount

Finally on aix 6.1 ibm have introduced mounting of iso directly without raw copy on lv:

Check if necessary loopback device is available

# lsdev -C | grep loop

if nothing returned, run:

# mkdev -c loopback -s node -t loopback
loop0 Available

If the device is not present on system you get this error:

1320-003 loopmount: Specified loopback device is not found in ODM

Now for mount:

# loopmount -i /iso/dvd.iso -l loop0 -o "-V cdrfs -o ro" -m /mnt/dvd

And umount:

# loopumount -l loop0 -m /mnt/dvd

Attention: an image file can be associated with only one loopback device.

VIO – iso virtual DVD

Example of PowerVM virtual dvd setup:

login: padmin
padmin's Password:
1 unsuccessful login attempt since last login.
Last unsuccessful login: Mon Jan 31 18:51:28 CST 2011 on /dev/vty0
Last login: Mon Jan 31 18:28:29 CST 2011 on /dev/vty0

$ mkrep -sp rootvg -size 10G
Virtual Media Repository Created
Repository created within "VMLibrary" logical volume
$ mkvopt -name 6_1_6osp.iso -dev cd0 -ro
$ mkvdev -vadapter vhost1 -fbo -dev vcd1
vcd0 Available
$ loadopt -vtd vcd0 -disk 6_1_6osp.iso
$ unloadopt -vtd vcd0

AIX – lpp incosistent

# lppchk –v

lppchk: The following filesets need to be installed or corrected to bring the system to a consistent state:
9a33182fe26f1beae04e59e5cb6d3cdb (COMMITTED)

# lslpp -L

Backup the ODM using the following command:

# tar -cvf /tmp/odm.tar ./etc/objrepos ./usr/lib/objrepos
# export ODMDIR=/usr/lib/objrepos
# odmget -q name= lpp
# odmdelete -q name= -o lpp
# odmdelete -q lpp_name= -o product
# odmdelete -q lpp_id= -o history
# odmdelete -q lpp_id= -o inventory
# export ODMDIR=/etc/objrepos
# odmdelete -q name= -o lpp
# odmdelete -q lpp_name= -o product
# odmdelete -q lpp_id= -o history
# odmdelete -q lpp_id= -o inventory
# export ODMDIR=/etc/objrepos

Check lppchk -v again to see if those entries are gone from ODM

AIX – Warning, savebase failed

0516-1734 extendlv: Warning, savebase failed. Please manually run ‘savebase’ before rebooting.

If you run savebase -v and you get “non-bootable LV name given” try reconstucting your /dev/ipldevice file.

Run savebase -v again and if you get the same error, try follow procedure:

# bosboot -ad /dev/hdiskX (a disk that has hd5 on it)
# bosboot -ad /dev/hdiskY (a disk that has hd5 on it)
# ipl_varyon -i

[You’ll get a return on every physical disk on the system]

You will then get a return similar to this:

# savebase -v

saving to ‘/dev/hd5’
99 CuDv objects to be saved
240 CuAt objects to be saved
44 CuDep objects to be saved
51 CuVPD objects to be saved
407 CuDvDr objects to be saved
5 CuPath objects to be saved
0 CuPathAt objects to be saved
0 CuData objects to be saved
0 CuAtDef objects to be saved
Number of bytes of data to save = 49587
Compressing data
Compressed data size is = 12069
bi_start = 0x3600
bi_size = 0x1820000
bd_size = 0x1800000
ram FS start = 0x8d6ca0
ram FS size = 0xea34cf
sba_start = 0x1803600
sba_size = 0x20000
sbd_size = 0x2f29
Checking boot image size:
new save base byte cnt = 0x2f29
Wrote 12073 bytes
Successful completion

AIX – lslpp

Memo: lslpp

List the package that owns a file

# lslpp -w

List the files in a package

# lslpp -f

List all packages installed

# lslpp -L

AIX – DLPAR connection lost to HMC

Sometime during AIX migration/alt_clone or HMC upgrade, it can happen that RMC ID get lost or duplicated, the the rsct process is unable to re stabilize the connection.

You can reset the key and restart that service as follows:

Reset RMC unique ID:

# /usr/sbin/rsct/install/bin/recfgct
# /usr/sbin/rsct/bin/rmcctrl -z
# /usr/sbin/rsct/bin/rmcctrl -A

Then you can check the rmc status:

# /usr/sbin/rsct/bin/rmcdomainstatus -s ctrmc

AIX – ODM Object Classes

AIX – ODM Device Configuration Object Classes

A list of the ODM Device Configuration Object Classes follows:

Predefined Devices

Predefined Connection

Predefined Attribute

Configuration Rules

Customized Devices

Customized Dependency

Customized Attribute

Customized Device Driver

Customized Vital Product Data

AIX – Mounting ISO images

There is a known problem with mounting ISO images on the AIX platform. To workaround the problem, complete the following instructions:

Obtain the size of the image, then identify the nearest multiple of 128 MB that will provide enough space for the image. For example, the image of CD-ROM is approximately 650/700 MB, so use 768 MB as an image size.

Make a logical volume of this size. Ensure that there is enough space on the physical volume. For example, hdisk0.

# mklv -y cdlv -s n -L /dev/cdlv rootvg 768M hdisk0

If the command fails, increase the volume size by a multiple of 128.

Use the dd command to create a pseudo-device. Ensure that the partition has enough space for the pseudo-device. In the following example command, the pseudo-device is /dev/cdlv.

# dd if=/opt/iso/cd.iso of=/dev/cdlv

Note that this command may take a long time and will create two dd processes.

Mount the device like a CD-ROM in AIX. Ensure that the mount point exists.

# mount -v cdrfs -o ro /dev/cdlv /mnt/iso

AIX LPAR – CDROM device relase

When AIX will not release /dev/cd0 device (after umount any associted filesystems), and you get busy device error on dlpar operations, use this command to kill all processes that take busy resource:

# fuser -k -x -u -c /dev/cd0

Usually in pSeries hardware configuration is connected to a scsi controller by scsi-to-ide/sas/sata or other terrible solution bridge.

To made all this operation faster you can identify pci parent adapter and remove recursively all device.


# lsdev -l cd0 -F parent
# lsdev -l scsi0 -F parent
# lsdev -l sisscsia0 -F parent


# rmdev -Rdl pci10
cd0 deleted
ses0 deleted
scsi0 deleted
sisscsia0 deleted
pci10 deleted

Then you can move the controller from HMC to another LPAR