The secldapclntd daemon is not running.
Starting the secldapclntd daemon.
exec(): 0509-036 Cannot load program /usr/sbin/secldapclntd because of the following errors:
0509-150 Dependent module libibmldap.a could not be loaded.
0509-022 Cannot load module libibmldap.a.
0509-026 System error: A file or directory in the path name does not exist.
exec(): 0509-036 Cannot load program /usr/sbin/secldapclntd because of the following errors:
0509-150 Dependent module libibmldap.a could not be loaded.
0509-022 Cannot load module libibmldap.a.
0509-026 System error: A file or directory in the path name does not exist.
The secldapclntd daemon failed to start.
root@aix01:/opt/IBM/ldap/V6.2/lib#ln -s /opt/IBM/ldap/V6.2/lib/libibmldap.a /usr/lib/libibmldap.a
root@aix01:/opt/IBM/ldap/V6.2/lib#ln -f -s /opt/IBM/ldap/V6.2/lib/libibmldap.a /usr/lib/libibmldap.a

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
1
SHUTDOWN PROGRAM
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.

http://www-304.ibm.com/support/docview.wss?uid=isg3T1012204

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.

# lppchk –v

lppchk: The following filesets need to be installed or corrected to bring the system to a consistent state: 9a33182fe26f1beae04e59e5cb6d3cdb 0.0.0.0 (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

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

List the package that owns a file

# lslpp -w

List the files in a package

# lslpp -f

List all packages installed

# lslpp -L

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

A list of the ODM Device Configuration Object Classes follows:

PdDv Predefined Devices

PdCn Predefined Connection

PdAt Predefined Attribute

Config_Rules Configuration Rules

CuDv Customized Devices

CuDep Customized Dependency

CuAt Customized Attribute

CuDvDr Customized Device Driver

CuVPD Customized Vital Product Data

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

# 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.

Identify:

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

Remove:

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

Then you can move the controller from HMC to another LPAR

SYSTEM POWER CONTROL MENU
1. Enable/Disable Unattended Start Mode:
Currently Enabled
2. Ring Indicate Power-On Menu
3. Reboot/Restart Policy Setup Menu
4. Power-On System
5. Power-Off System
6. Enable/Disable Fast System Boot:
Currently Slow Boot
7. Boot Mode Menu
98. Return to Previous Menu
99. Exit from Menus

After digits “4”

Please wait....
System Powering On.  Exiting menus.
9022
9101
90FD
10117611        U0.1-F1
B0FF
OK               x

The error on planar was located on FAN module, for resolution unplug entire block and single fans, then replug into the planar after cleaning up, then power on your pSeries.