Aix

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.

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

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

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

# 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

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

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

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 Device Configuration Object Classes 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