......................................................................
First Created - Mar 23, 2013 - Raj Patel
Rev 1: - Mar 24, 2013 - Raj Patel - Add FSPDUMP and SYSDUMP.
Rev 2: - Apr 03, 2013 - Raj Patel - Added, FSPDUMP details.
Add lshwres
Below to be colleced for IVM / LPM Performance related issues.
1) Setup PERFPMR data within oem_setup_env
# Install prfmpr per below link for your IVM levels.
ftp://ftp.software.ibm.com/aix/tools/perftools/perfpmr/
# Create data directory
mkdir -p /home/padmin/ivm-perfdata
2) Provide lshres from BOTH Source and Target IVM
$ lshwres -r virtualio --rsubtype scsi -m [managed_system_name] --level lpar
$ lshwres -r virtualio --rsubtype fc -m [managed_system_name] --level lpar
** $ lssyscfg -r sys -F name ( to get managed system name ) **
3) Provide client LPAD ID and name before LPM
4) Provide client LPAD ID and name after LPM
5) Provide IVM lpar ID and name from BOTH Source and Target Blades.
$ lssyscfg -r sys -F name ( to get managed system name )
6) Start LPM using CLI with -d 5 flag
date ; time migrlpar -o m -m [src_ivm_managed_system] -t
[des_ivm__managed_system] --id [client_partiton_ID]
-i source msp_name=[src-msp>,dest_msp_name=[des-msp]
-d 5 -v
7) Collect perfpmr data from BOTH Source & Target IVMs with oem_setup_env
# Collect perf data
cd /home/padmin/ivm-perfdata
perfpmr.sh 120
# Tar perfdata
cd /home/padmin
pax -xpax -vw ivm-perfdata | gzip -c > prm#.vio.src.pax.gz
# For Target tar perfdata and rename
cd /home/padmin
pax -xpax -vw ivm-perfdata | gzip -c > prm#.vio.des.pax.gz
8) Collect VASI data within oem_setup_env from BOTH Source & Target IVMs
# Enable component traces ( enough time since LPM takes 2.5 hrs )
ctctrl -c vasi memtracedetail
ctctrl -c vasi memtracebufsize=409600
# Create directory for VASI
for i in 1 2 3 4 5 6 7 8 9 10
do
mkdir -p /home/padmin/vasi-trace-data/run$i
done
# Capute VASI component traces and generate report.
for i in 1 2 3 4 5 6 7 8 9 10
do
ctctrl -D -d /home/padmin/vasi-trace-data/run$i/vasi -c vasi ;
trcrpt -t /etc/trcfmt /home/padmin/vasi-trace-data/run$i/vasi > /home/padmin/vasi-trace-data/vasi-trace-data.run$i.rpt
sleep 15
done
# Tar VASI files
cd /home/padmin
pax -xpax -vw vasi-trace-data > gzip -c > prm#.vio.src.vasi.pax.gz
pax -xpax -vw vasi-trace-data > gzip -c > prm#.vio.des.vasi.pax.gz
9) Collect MOVER data within oem_setup_env from BOTH Source and Target IVMs
# Enable component traces ( enough time since LPM takes 2.5 hrs )
ctctrl -c mover memtracedetail
ctctrl -c mover memtracebufsize=409600
# Create directory for MOVER
for i in 1 2 3 4 5 6 7 8 9 10
do
mkdir -p /home/padmin/mover-trace-data/run$i
done
# Capute MOVER component traces and generate report.
for i in 1 2 3 4 5 6 7 8 9 10
do
ctctrl -D -d /home/padmin/mover-trace-data/run$i/mover -c mover ;
trcrpt -t /etc/trcfmt /home/padmin/mover-trace-data/run$i/mover > /home/padmin/mover-trace-data/mover-trace-data.run$i.rpt
sleep 15
done
# Tar MOVER files
cd /home/padmin
pax -xpax -vw mover-trace-data > gzip -c > prm#.vio.src.mover.pax.gz
pax -xpax -vw mover-trace-data > gzip -c > prm#.vio.des.mover.pax.gz
10) Provide lshres from BOTH Source and Target IVM
$ lshwres -r virtualio --rsubtype scsi -m [managed_system_name] --level lpar
$ lshwres -r virtualio --rsubtype fc -m [managed_system_name] --level lpar
** $ lssyscfg -r sys -F name ( to get managed system name ) **
11) IVM snaps from Both Source and Target Blades
$ snap ( creates /home/padmin.pax.Z )
rename pmr#.vio.src.snap.msp.pax.Z
rename pmr#.vio.des.snap.msp.pax.Z
12) Ctsnaps from Both Source and Target Blades
$ oem_setup_env
# ctsnap -x runrpttr
This will create => /tmp/ctsupt/ctsnap*.tar.gz
rename pmr#.vio.src.ctsnap.msp.pax.Z
rename pmr#.vio.des.ctsnap.msp.pax.Z
13) Snaps from Client LPAR.
# snap -r
# snap -ac ( creates /tmp/ibmsupt/snap.pax.Z )
rename pmr#.client.snap.pax.Z
14) Ctsnaps from client lpar after LPM.
$ oem_setup_env
# ctsnap -x runrpttr
This will create => /tmp/ctsupt/ctsnap*.tar.gz
rename pmr#.client.ctsnap.pax.Z
15) FSPDUMP ( this will NOT reboot IVM )
# Access AMM using Firefox
# Access IVM from AMM
console -T blade[blade#] -o
# Select Service Tool on left of menu
# Select "Blade Service Data"
# Select Blade Bay
# Under Blade Dump, Select "Service Processor"
# Select Initiate
# Copy FSPDUMP within oem_setup_env
cp /var/adm/ras/platform/
CONFIRM FILE GENERATED BY ABOVE.
NOTE: Selecting "Partition" collects FSPDUMP also but for partition.
16) SYSDUMP ( this will reboot IVM )
# Access AMM using Firefox
# Access IVM from AMM
console -T blade[blade#] -o
# Select Service Tool on left of menu
# Select "Blade Service Data"
# Select Blade Bay
# Under Blade Dump, Select "Platform"
# Select Initiate
# Copy SYSDUMP within oem_setup_env ( after IVM reboots )
cp /var/adm/ras/platform/
CONFIRM FILE GENERATED BY ABOVE.
17) Place all above files in single directory and tar and ftp to testcase.
Example:
mkdir /tmp/all-data
cd /tmp
pax -xpax -vw all-data | gzip -c > PMR#.pax.gz
ftp testcase.software.ibm.com,
login: anonymous,
passwd: your email address,
ftp> cd /toibm/aix
ftp> bin
ftp> put PMR#.pax.gz)
ftp> quit