Professional Documents
Culture Documents
1 / 18
2013-02-07
Table of Contents
1
2
3
3.1
3.2
3.3
3.4
3.5
3.6
3.7
4
4.1
4.2
4.3
Introduction.......................................................................................................................................... 3
Scope and architecture environment. ................................................................................................... 4
Performing Actions and Verifications before Starting the Demo ........................................................ 5
HMC ................................................................................................................................................. 5
Check LPAR location ....................................................................................................................... 6
Asynchronous IO .............................................................................................................................. 6
Starting db2 Database ....................................................................................................................... 6
Stopping db2 Database ..................................................................................................................... 7
Starting VPS Application.................................................................................................................. 7
Lparmon tool..................................................................................................................................... 7
Demo steps detailed ............................................................................................................................. 9
Demo Step1...................................................................................................................................... 9
Demo Step2.................................................................................................................................... 12
Demo Step3.................................................................................................................................... 13
2 / 18
2013-02-07
Version 1.1
1 Introduction
The goal of this document is to help you demonstrate to your customer the benefits they can get using
PowerVM Live Partition Mobility.
We provide two IBM Power 750 Express systems, one LPAR is running a DB2 database workload
on the first Power 750, the demonstration will show that we are able to relocate this workload on the
second Power 750 Server without even stopping the transactions processing using PowerVM Live
Partition Mobility feature of Power Systems, this demonstration illustrates the continuity of specific
applications running on an AIX partition, during this live migration.
This document is the user manual of that demonstration. the following chapters describe the
architecture used and propose utilization scenario as well as tips to explain better a particular topic and,
eventually, to anticipate questions.
3 / 18
2013-02-07
Version 1.1
This demo needs one Virtual I/O Server on each Power 750 to be able to create Logical partitions.
Partition named CB-CPT-VIOS1 is on Power 750 system with serial number ????06753A5 named CPT.
Partition named CB-MGT-VIOS2 is on Power 750 system with serial number ?????0675395 named
MGT.
During this demo, well generate a database workload using the IBM VPS application
http://db2vps.torolab.ibm.com/html/D_Welcome.shtml installed on the WAS partition We have a
configuration where the database server and the Websphere Application Server are not on the same
logical partition. There is one partition named WAS and a DB2 partition on MGT.
For the Power VM Live Partition Mobility demonstration, we will move the DB2 partition from MGT to
CPT. The storage and network of the mobile logical partition DB2 used for the Power VM Live Partition
Mobility have to be virtualized ie accessed through a Virtual I/O Server
4 / 18
2013-02-07
Version 1.1
5 / 18
2013-02-07
Version 1.1
3.3 Asynchronous IO
Verify on the DB2 partition that the asynchronous IO are Available. They are needed in order to start the
DB2 database. They are normally started at partition boot time.
To do so, we have to :
Log on as root ( use putty ) (password: demo4ibm)
{db2:root}/ -> lsdev -Cc aio
aio0 Available Asynchronous I/O (Legacy)
6 / 18
2013-02-07
Version 1.1
7 / 18
2013-02-07
Version 1.1
Troubleshooting lparmon: if you cannot get the graph for one partition or for all of them , you need to check if
the lparmon agent is running on the partitions.
How to check that the lparmon agent is running :
{was:root}/ -> ps -aef | grep lparmon |grep -v grep
root 282848 319646
0 16:23:18
- 0:01 /usr/sbin/lparmon
root 319646
1
0
Mar 14
- 0:00 /usr/sbin/lparmon
root 340176 282848
0 16:23:18
- 0:00 /usr/sbin/lparmon
If the lparmon processes are not running then you need to start them by executing the following command :
{was:root}/ -> /usr/bin/lparmon
8 / 18
2013-02-07
Version 1.1
Connect to the HMC through Firefox using the bookmark named HMC
Start the lparmon tool on windows (lparmon icon on desktop).
Start the VPS application through Internet Explorer using the bookmark named VPS or use the URL
http://10.3.54.74:9080/VirtualProductionSystem/html/Demo.jsp
9 / 18
2013-02-07
Version 1.1
db2
50000
vps
db2inst1
db2inst1
JDBC Type 4
Select OLTP Scenario on the left. Check the parameters for the connection as follow here under
Refresh Rate :
Workload :
Users :
Think Time :
Every 10 seconds
Only Reads
500
20 ms
10 / 18
2013-02-07
Version 1.1
Click on Reset then on Start buttons to start the DB2 workload, the number of Transactions should increase
and reach 7000 Transactions/Second.
While the Virtual Production System for DB2 9 is running, show the CPU consumption with LPARMON.
11 / 18
2013-02-07
Version 1.1
Run the script /u/script/cpuid.sh to show the serial number of the system on which the DB2 partition is
running. Serial number of CIRRUS-MGT System is 0210D9EDP.
{db2:root}/root -> /u/script/cpuid.sh
systemid IBM,0210D9EDP Hardware system
systemid IBM,0210D9EDP Hardware system
systemid IBM,0210D9EDP Hardware system
systemid IBM,0210D9EDP Hardware system
identifier
identifier
identifier
identifier
False
False
False
False
12 / 18
2013-02-07
Version 1.1
On the HMC window show that the DB2 partition is running on CIRRUS-MGT system and not on STRATUSCPT system.
13 / 18
2013-02-07
Version 1.1
14 / 18
2013-02-07
Version 1.1
15 / 18
2013-02-07
Version 1.1
Check on the HMC that the DB2 partition is created on STRATUS-CPT and is in the migrating-running state.
Check that the DB2 partition has moved from CIRRUS-MGT to STRATUS-CPT in the putty screen. The
serial number of DB2 partition has changed from 0210D9EDP to 0210D9EBP
{db2:root}/ -> /u/script/cpuid.sh
..
systemid IBM,0210D9EDP Hardware system identifier False
systemid IBM,0210D9EDP Hardware system identifier False
systemid IBM,0210D9EDP Hardware system identifier False
systemid IBM,0210D9EDP Hardware system identifier False
systemid IBM,0210D9EBP Hardware system identifier False
systemid IBM,0210D9EBP Hardware system identifier False
systemid IBM,0210D9EBP Hardware system identifier False
systemid IBM,0210D9EBP Hardware system identifier False
systemid IBM,0210D9EBP Hardware system identifier False
systemid
systemid
systemid
systemid
systemid
IBM,0306753A5
IBM,0306753A5
IBM,030675395
IBM,030675395
IBM,030675395
Hardware
Hardware
Hardware
Hardware
Hardware
system
system
system
system
system
identifier
identifier
identifier
identifier
identifier
16 / 18
False
False
False
False
False
2013-02-07
Version 1.1
Show on the VPS window that the migration has a low impact on the workload. The number of transactions
decreases during 2 seconds.
17 / 18
2013-02-07
Version 1.1
END of Demo
Stop the VPS application (click on Stop button on VPS interface window IE
browser)
18 / 18
2013-02-07