Future of this blog – AIX articles

As you might have noticed I have not written that many articles of the last year. Reason is after 7 great years I left the AIX division of my company and moved forward, therefore not that much AIX stuff will be added to this blog in the future. 

 

Expect to have new articles regarding SAP Installations and Monitoring SAP with Nagios. 

Posted in Uncategorized | Leave a comment

[QNAP] TwonkeyMedia Sony BD Player

To enable MKV on newly Twonky Releases with a Sony BD Player (or any other cartiva enabled device, you need to modify the .xml file

Sony_Blu-Ray_Player.xml in your twonkeyserver/devicedb folder.

Check that the feature of “additional picture size” is removed – final config should look like

POLL_AVT_STATE
BROKEN_SETNEXT
SUPPRESS_STATE_EVENTS
NEED_NO_PLAY_4_SETAVT

Have fun 🙂

Posted in Uncategorized | Tagged , , ,

[QNAP] No-IP Update

Appareantly the No-ip update service does not work properly.

therefore I did some changes to the scripts:

/etc/init.d/ddns_update_for_cgi.sh
added line 66
/sbin/daemon_mgr noip2 stop /usr/sbin/noip2 1>/dev/null 2>/dev/null

/etc/init.d/check_ddns_external_ip.sh
uncomment lines:

#SEVER_TYPE=`grep “Server Type” ${DDNS_TMP_FILE} | /bin/tr -cs ‘[0-9\.]’ ’12’`
#if [ ${SEVER_TYPE} = 5 ]; then
# /bin/echo “no-ip don’t need use this functin”
# exit 0
#fi

seems to work now 🙂

Posted in Uncategorized | Tagged | Leave a comment

[Ganglia] Installation demistified

Find within this entry a ganglia setup I just created today after reading lots of different webpages.

The goal is to have 1 gmetad installation with only gmond serving the data.

Installation and design is for IBM Powersystems, but should be adapted to any other platform.

Continue reading

Posted in aix, Ganglia | Tagged , , , , , , , | Leave a comment

Quite interesting read

This article is about “stuff you know” , “stuff you think you should know” and “stuff you dont know you dont know”.
It is personally about people realising to stop pushing them to know everything and ALL of their heads and get a bit more relaxed.

http://jangosteve.com/post/380926251/no-one-knows-what-theyre-doing

Posted in Uncategorized | Leave a comment

[HMC] HMC and IBM blades

Today I installed HMC V7.7.6 SP1 and tried to connect IBM Blade p701 to it.

With given information that was an easy job (once you have all network config done), you just need to remember some stuff:

  • FSP within Blade is a SPOF, even with 2 FSPs within a dual-frame blade, only 1 FSP will be connected to the HMC
  • FSP needs to be routed through the AMM Module to the HMC.
  • Blade needs to be on latest FW (p70x 01AA730 _094 / jsXX 01EA350_132)
  • A blade already configured will loose its complete configuration (IVM config) and needs to be rebuild “from scratch”

Guide on how to do the connection from IBM:

http://www-01.ibm.com/support/docview.wss?uid=nas113d68c8773f5013886257a8600531440

Also ASMI config for IBM blades:

http://www-912.ibm.com/s_dir/SLKBase.nsf/1ac66549a21402188625680b0002037e/057800440ee4dae4862573e9005ad197?OpenDocument&ExpandSection=-1

Posted in Uncategorized | Tagged , , | Leave a comment

[AIX] Change FC settings without taking the system offline

If you need to change FC attributes try this little ‘one-liner’

for i in `lspv | awk '{print $1}'`; do chpath -l $i -s disable -p fscsi0;done
rmdev -l fcs0 -R
chdev -l fcs0 -a num_cmd_elems=2048 
cfgmgr
chdev –l fcs0 –a max_xfer_size=0x200000 -P
for i in `lspv | awk '{print $1}'`; do chpath -l $i -s disable -p fscsi1;done
rmdev -l fcs1 -R
chdev -l fcs1 -a num_cmd_elems=2048 –a max_xfer_size=0x200000
cfgmgr
chdev –l fcs1 –a max_xfer_size=0x200000 -P
for i in $(lspv | awk '{print $1}'); do;chdev -l $i -a max_transfer=0x100000 –P;done
Posted in Uncategorized | Tagged , , , | Leave a comment

HMC: Cleanup unused memory/cpu assignment on offline LPARs

Short script:

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)
do
varMem=$(lshwres -r mem -m $varSys –level lpar –filter “lpar_names=$varLpar” -F curr_mem)
if [ “$varMem” -ne “0” ]
then
echo “$varSys $varLpar – removing Mem $varMem”
chhwres -r mem -m $varSys -o r -q $varMem -p $varLpar
fi
varProcunits=$(lshwres -r proc -m $varSys –level lpar –filter “lpar_names=$varLpar” -F curr_proc_units)
if [ “$varProcunits” != “null” -a “$varProcunits” != “0.0” ]
then
echo “$varSys $varLpar – removing Procunits $varProcunits”
chhwres -r proc -m $varSys -o r –procunits $varProcunits -p $varLpar
fi
done
done

Posted in Uncategorized | Tagged , , , , | Leave a comment

TSM: extend logvolume via commandline

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:
disable sessions
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

Posted in Uncategorized | Tagged , , , , | Leave a comment

HMC Migration process

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

Done

Posted in Uncategorized | Tagged , , , | Leave a comment