for varSys in $(lssyscfg -r sys -F names) do
for varLpar in $(lssyscfg -r lpar -m $varSys -F ‘name,state’ |grep “Not Activated” |cut -d “,” -f1)
varMem=$(lshwres -r mem -m $varSys –level lpar –filter “lpar_names=$varLpar” -F curr_mem)
if [ “$varMem” -ne “0” ]
echo “$varSys $varLpar – removing Mem $varMem”
chhwres -r mem -m $varSys -o r -q $varMem -p $varLpar
varProcunits=$(lshwres -r proc -m $varSys –level lpar –filter “lpar_names=$varLpar” -F curr_proc_units)
if [ “$varProcunits” != “null” -a “$varProcunits” != “0.0” ]
echo “$varSys $varLpar – removing Procunits $varProcunits”
chhwres -r proc -m $varSys -o r –procunits $varProcunits -p $varLpar
Something that was used this morning as TSM died with logvolume being 100% used and no DB backup possible as library is offline.
Determining if the log is full
Start TSM (dsmserv) from the command line so that the startup messages can be seen. A message stating that log space cannot be allocated will be seen if the server is out of log space just prior to dsmserv dumping core.
So your log is full
From a command line on the TSM server, execute:
dsmfmt –m –log /tsmlog01/log911.tsm 1000
dsmserv extend log /tsmlog01/log911.tsm 1000
The log will be extended by 1000 meg. This is very little room (room=time) to fix the problem.
Start the TSM server in quiet mode. If TSM fails to start, see section Determining if the log is full.
From a TSM command prompt execute:
This command will stop ALL client activity.
TSM is up, now what?
Now that TSM is running, determine the cause of the log becoming full, most likely causes are no scratch tapes, no tape drives, and a large archive conversion. Remember, you only have 1000 megs of log space. (Q log f=d)
Now that everything is cool again
After the server is running normally, you must remove the 911 log file. Failure to do this will render the system unrecoverable should the log become full again.
1. Change the log mode to normal
2. Reduce the log size by 1000 meg – (REDUCE LOG 1000)
3. DELETE LOGVOLUME /tsmlog01/log911.tsm (the file is not deleted, just the TSM reference)
4. Change the log mode to Rollforward, this will cause a DB backup
5. From a TSM command line run: enable sessions
thanks to adsm.org for the procedure
Migrationg data (profile,network settings,etc) from one HMC to another can be done by following process:
1. Save data on current hmc with “upgrade data” via the menu or command line “saveupgdata -r diskdvd” to DVD-RAM
2. startup the new HMC and insert the DVD-RAM and transfer the upgrade data to the local disk via “mount /media/cdrom & rstupgdata -r dvd”
3. restart hmc
Just needed this last weekend after a productive oracle crash:
Since TL4 in AIX 6 loopmount is a new tool to mount ISO files :
loopmount -i cdrom.iso -o “-V cdrfs -o ro” -m /mnt
A useful document on how to work with HMC and powersystems (very old but still valid) which also describes how to reset the passwords for a powersystem if the ASMI user/pass is known.
I just read the PowerVM best practice redbook which has been released and updated last week.
IBM now officially recommends using NPIV instead of VSCSI. Seems time flies when I first installed a VIOS with VSCSI. Still do like it a bit more, as NPIV does have some downsides when it comes to FCS utilisation and SAN Paths.
Here is the link to the redbook: