Lab Exercise: Installing SAP HANA On Power: Come and Do It Yourself!

2015 IBM Systems Technical University
Lab Exercise:
Installing SAP HANA on Power: Come and Do It Yourself!
Introduction:
This Lab Exercise provides you a hands-on experience with three major topics: (a) install Linux on
Power and tune it for a HANA installation; (b) perform a HANA on Power installation; (c) and
finally run the required tests to verify whether the environment meets the required SAP KPIs to run
HANA on the system you installed.
© Copyright IBM Corporation 2016 1

Materials may not be reproduced in whole or in part
without the prior written permission of IBM.
Exercises Guide
Exercise instructions
As you enter the room and settle down, take some time to get to know your Lab partner. We would love if you worked
together to achieve the goals of these exercises.
Take this chance to exchange business cards. You might have just met a valuable partner for business.
Your instructor will provide the information you need to access this lab environment. As you might have guessed, the
hardware is located remote to the conference, so you will have to access it over a VPN.
Use the next section to take a note of your VPN access after briefed by the instructor:
My VPN username: _____________________

My VPN password: _____________________
In addition to that, you will need to know the information about the Logical Partition (LPAR) that you will use during
this exercise. Take a note below after briefed by the instructor:
My Power server name: ________________________

My LPAR name: _______________________________
My LPAR hostname: ___________________________
My LPAR domain name: ________________________
My LPAR IP address / mask: _____________________
My LPAR gateway: _____________________________
My LPAR DNS: _________________________________
Other useful information (random notes for lab access):

HMC IP address:____________ HMC user: __________HMC password: ___________
root password: ____________________________________________________________
_________________________________________________________________________
_________________________________________________________________________
2 © Copyright IBM Corporation 2016

Course materials may not be reproduced in whole or in part
1. Linux on Power installation
Getting a console terminal
1. Use SSH to access the HMC (use putty on windows or a shell on Linux):
________________________________________________________
ceron@curly ~ $ ssh hscroot@172.26.40.40
hscroot@172.26.40.40's password:
Last login: Wed Sep 9 16:23:36 2015 from 10.17.0.9
________________________________________________________
2. Now invoke the vtmenu command to select your LPAR console. Here, you might be given the option of which
server you would like to connect to. Use your Power server name as provided in the exercise instructions. If there's
only one server in your lab environment you can skip this step and go to step 3.
_______________________________________________________________
hscroot@hmc01:~> vtmenu
Retrieving name of managed system(s) . . .

Power550__Up_8204- E8A_SN1079035 Power 780 -
----------------------------------------------------------
Managed Systems:
----------------------------------------------------------
1) Power550__Up_8204-E8A_SN1079035
2) Power 780 - The Beast
3) Power 750 - SN100828P
4) Server-8286-42A-SN10400CV
Enter Number of Managed System. (q to quit): 2

________________________________________________________________
Have in mind that the name of your Power server will definitely differ from the ones presented in the example above.
3. Now, select the number associated with your Power server. This provides you a list of LPARs to which you can
connect over the serial console. Use the information provided in the exercise instruction to connect to your LPAR.
Please, be polite and avoid getting the consoles of other people ;-). Select the LPAR number to which you'd like to
connect.
Exercises Guide
_________________________________________________________________
----------------------------------------------------------
Partitions On Managed System: Sp85001-8408-E8E-SN21C48AV
OS/400 Partitions not listed
----------------------------------------------------------
1) Sp8501v1 Running
2) hana01-5ac74e73-00000017 Running
3) hana02-9bc84c74-00000018 Running
4) hana03-90e56462-00000019 Running
5) hana04-f7174a68-0000001a Running
6) hana05-b31faf1b-0000001b Running
7) hana06-7f39e282-0000001c Running
8) hana07-a4326ec8-0000001d Running
9) hana08-44b28efd-0000001e Running
10) hana09-7c646262-0000001f Running
11) hana10-a6bd900f-00000020 Running
12) hana11-12462dfe-00000021 Running
13) hana12-cd3e2b17-00000022 Running
14) hana13-ec78cd1a-00000023 Running
15) hana14-99de0990-00000024 Running
Enter Number of Running Partition (q to quit): 2

________________________________________________________________
4. Your LPAR will already be installed, so you will be faced with a Linux login prompt. Log in as the root user, then
reboot the system. Use the access information provided in the exercise instructions to log in.
_______________________________________________________________
Welcome to SUSE Linux Enterprise Server 11 SP4 (ppc64) -
Kernel 3.0.101-71-ppc64 (console).
hana01.smc.iic.ihost.com login: root

Password: xxxxxx

Last login: Tue Jun 7 18:38:54 EDT 2016 from vpnc-104-

140.iic.ihost.com on pts/0
____________________________________________________
Rebooting the system and getting into the SMS menu
You now need to reboot your system as we're going to reinstall it from scratch. Follow the next
steps to do so and get into the SMS menu to select the boot device.
1. While logged in as the root user, reboot the LPAR as shown below. Once the SMS menu comes
up, you will have to be quick and press “1” to enter it.
_____________________________________________________
hana01:~ # shutdown -h now
Broadcast message from root (console) (Wed Sep 9 17:53:41

2015):
The system is going down for system halt NOW!

INIT: Switching to runlevel: 0
INIT: Sending processes the TERM signal
INIT: Sending processes the KILL signal
_____________________________________________________
2. Watch for the SMS menu to come up, and be quick to press “1” to enter it. The next example
displays the SMS menu screen where you need to press 1.
_________________________________________________________________
IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM

Exercises Guide
IBM IBM IBM
1 = SMS Menu 5 = Default Boot List

8 = Open Firmware Prompt 6 = Stored Boot List
Memory Keyboard Network SCSI Speaker

_______________________________________________________________________
3. The SMS menu main screen looks like the example shown below. If you missed the SMS screen
timing to press “1”, reboot your system and start over.
__________________________________________________________________
PowerPC Firmware
Version AM780_040
SMS 1.7 (c) Copyright IBM Corp. 2000,2008 All rights reserved.
------------------------------------------------------------------
-------------
Main Menu
1. Select Language
2. Setup Remote IPL (Initial Program Load)
3. Change SCSI Settings

4. Select Console
5. Select Boot Options
-----------------------------------------------------------------
Navigation Keys:
X = eXit System Management Services

-----------------------------------------------------------------
Type menu item number and press Enter or select Navigation key:
__________________________________________________________________
We are now going to boot the LPAR from its virtual DVD drive. The underlying Virtual I/O Server
in your environment already has a SLES11 SP3 ppc64 installation medium loaded onto your virtual
DVD drive. So, all you need to do is select the DVD drive as the boot device. Follow the
instructions below to accomplish this.
4. In the SMS menu, follow the menu sequence: Select boot options  Select Install/Boot device
 List all devices
One of the devices listed should be the virtual DVD drive. In the example below, it's displayed as
the 3rd element in the list. Yours might differ and use a different number.
5. Select the virtual DVD drive as the boot device and press “enter”, as shown below.
__________________________________________________________________
PowerPC Firmware
Version AM780_040
SMS 1.7 (c) Copyright IBM Corp. 2000,2008 All rights reserved.
------------------------------------------------------------------
Select Device
Device Current Device
Number Position Name
1. - Interpartition Logical LAN
( loc=U9179.MHB.82F5DEP-V18-C32-T1 )
2. 1 SCSI 31 GB Harddisk

Exercises Guide
( loc=U9179.MHB.82F5DEP-V18-C2-T1-L8100000000000000 )
3. - SCSI CD-ROM
4. 2 SCSI 31 GB Harddisk
-----------------------------------------------------------------
Navigation keys:
M = return to Main Menu
ESC key = return to previous screen
X = eXit System Management Services
-----------------------------------------------------------------
Type menu item number and press Enter or select Navigation key:3
________________________________________________________________
6. In order to finalize the DVD boot process, select the options Normal mode boot  Yes
This final step takes you to the SLES11 SP3 installation medium boot loader as shown below. Click
the “tab” key to hold the menu at this step and prevent auto-booting.
______________________________________________________________
yaboot starting: loaded at 00040000 000676d8 (0/0/00c3ba70; sp:
01d3ffd0)
Config file 'yaboot.cnf' read, 285 bytes
Welcome to SuSE Linux Enterprise 11!
Type "install" to start the YaST installer on this CD/DVD

Type "slp" to start the YaST install via network
Type "rescue" to start the rescue system on this CD/DVD
Welcome to yaboot version r22.8-r1190.SuSE

booted from '/vdevice/v-
scsi@30000003/disk@8300000000000000:1,\suseboot\yaboot.ibm'

running with firmware 'IBM,AM780_040' on model 'IBM,9179-MHB',

serial 'IBM,0282F5DEP', partition 'HanaOnPower-a7efb49c-000001e2'
Enter "help" to get some basic usage information
boot:
install slp rescue
__________________________________________________________________
Starting a Linux on Power installation with VNC
Use style Heading 4 for minor subsections where you do not want to restart numbering.
It is possible to install Linux in text-only mode. It provides you with all of the features you would
find during a graphical mode installation. However, the instructor prefers to provide you with a
smoother installation experience by using a graphical installation. Therefore, you have to boot up
your Linux installation and configure the system networking parameters in order to access it by
VNC over the network.
1. While at the Linux boot loader menu, use the following options to configure networking and
enable VNC:
______________________________________________________________________
install vnc=1 vncpassword=<passwd> hostip=<ip> netmask=<netmask>
gateway=<gw> netdevice=<dev>
_________________________________________________________________
The example below shows how to perform it. Replace the networking information with the values
provided in this exercise instructions. The device is kept unchanged (eth0) as it's your LPAR's
single network device.
_________________________________________________________________
boot:
install slp rescue
boot: install vnc=1 vncpassword=rootroot hostip=172.26.40.11
netmask=255.255.255.128 gateway=172.26.40.1 netdevice=eth0
Please wait, loading kernel...
Allocated 02000000 bytes for executable @ 02580000
______________________________________________________________________

Exercises Guide
Once the boot process is complete, the system informs you that it's possible to connect to it over
VNC by using the IP address you configured during boot and the screen number :1. A YaST screen
with the installation steps in graphical mode is then available once you connect over VNC.
_____________________________________________________________
starting VNC server...
A log file will be written to: /var/log/YaST2/vncserver.log ...
*** You can connect to <host>, display :1 now with vncviewer

*** Or use a Java capable browser on http://<host>:5801/
***
(When YaST2 is finished, close your VNC viewer and return to this
window.)
Active interfaces:
eth0 Link encap:Ethernet HWaddr FA:4B:BD:37:1B:20
inet addr:172.26.40.11 Bcast:172.26.40.128
Mask:255.255.255.127
--
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
*** Starting YaST2 ***
_________________________________________________________________
Resuming the installation in graphical mode over VNC: phase 1
Now that the Linux installation is being served in graphical mode over VNC, use the VNC client
available at your workstation to connect to your system. The protocol you should use is vnc and the
host should be x.x.x.x:1, where x.x.x.x is the IP address of your system.
Once connected, the VNC client prompts you for the password you used to configure the VNC-
based installation with (rootroot in the examples), then you should see the welcome screen as
shown below.

Agree to the license terms and click “Next” in order to proceed with the installation.

Exercises Guide
The second screen is simply an option available for you to test the installation media.
2. Skip the installation media step and click “Next” to proceed.
The next step is important. If your system has SAN disks, which is probably the case for most
HANA on Power installations, the installer prompts you to activate multipath during installation.
This is shown in the figure below.

3. Answer “Yes” to the prompt below and proceed.

Exercises Guide
4. The next step is to instruct the installer to perform a new installation. Select this option and click
“Next”. Do not include any add-on products from separate media.

5. Select your timezone and click “Next”. There is no need to further set up the current time or an
NTP server as this is only a lab exercise. In real installations, it is mandatory to do so.

Exercises Guide
Your next step is partitioning the boot disk. There are four disks in your environment setup:
a. The boot disk _____________________

b. The HANA data disk ________________
c. The HANA log disk _________________
d. The HANA shared disk ______________
Ask your instructor as to which disk you should use to install your system on. Fill in with the
information above.
6. Select the “expert” tab at this step of the installation, as shown below. Then click on
“partitioning”.

7. In order to partition the disk, select custom partitioning. You are then given the expert
partitioner screen as shown below. Select the “hard disks” entry in the left side menu.
8. Clean up any partitions from the previous lab session. Partitions appear with the suffix “_partN”
on the screen above. Select one by one and use the “Delete” button. If unsure how to perform this,
ask the instructor for help.
You now have to partition the boot disk according to the following guidelines:
a. a 512MB primary partition configured as a PreP boot partition
b. a 2nd primary partition with the remaining of the disk space as an LVM device
c. within the LVM, we need to create:
d. a 2GB swap partition
e. a 50GB /usr/sap partition (ext3)
f. a 32GB / partition (ext3)

Exercises Guide
9. Use the “Add Partition” button as shown in the previous figure to create a primary. Then, follow
the steps as shown in the figures below to create the PreP boot partition.
Use the Finish button at the right bottom to complete the creation of this partition.

10. Repeat the process and create another primary partition, but this time use all of the remaining
disk space and set it up to be used as an LVM device. The figures below show how the setup should
look like.
Click “Finish” to complete the creation of this partition.

Exercises Guide
11. You now have to create the volume group and logical volumes that host the swap and root
partitions. Select the LVM entry in the left side menu, and then click “add volume group” as shown
in the figure below.

12. Give the volume group a name (suggestion: rootvg) and select the partition you assigned as
LVM in the previous steps. Then click “Add” to use that partition in the volume group you are
creating.
These steps should place the partition you selected to the right side of the screen under “selected
physical volumes”. Click “Finish” when complete.

Exercises Guide
13. Back to the partitioner, you now need to create “Logical Volumes” within the volume group you
created. Follow the leads given by the figure below and create two logical volumes: a 2GB one as
the swap partition, a 50GB one as /usr/sap, and another with the remaining space of the volume
group as the root filesystem.
The next figures give you a hint on the steps to create the three logical volumes.

14. Create the swap logical volume and filesystem:

Exercises Guide
15. Create the /usr/sap filesystem:

16. Create the root logical volume and filesystem:
17. Click the “Accept” button at the bottom right to accept the partitioning scheme.
You are now done creating the partitions. The next step is to choose the software to be installed
onto the system.

Exercises Guide
18. Back at the Installation Settings, select “Software” as shown in the figure below.
You must select the following software patterns:

a. Base System
b. 32-bit runtime environment
c. Help and Support Documentation
d. Minimal System (Appliances)
e. Gnome Desktop Environment

f. X Window System
g. File Server
h. Print Server
I. SAP Application Server Base
j. Web-Based Enterprise Management
k. C/C++ Compiler and Tools
The figure below shows all of these patterns, and only these ones, selected.
19. You must also ensure the following packages are individually selected:
a. papi

Exercises Guide
b. powerpc-utils
c. gmp-32bit
d. libmpfr1-32bit
Use the “Details” button as shown in the previous figure and then select individual packages as
shown below under the “search” tab. Select all of the individual packages outlined above before
clicking the “accept” button at the bottom right.
20. Accept any prompt questions the system may ask you and proceed back to the installation
settings screen.
21. Optional step: disable Kdump. As the last option in the expert menu, you may choose to disable
kdump.

22. You're now ready to start the installation. You may check your settings and then click the
“Install” button at the right bottom of the screen. Confirm it and watch as the system gets installed.
Resuming the installation in graphical mode over VNC: phase 2
Once done installing the packages, the system reboots. At this step you lose the VNC connection.
Simply follow the boot process from the text-mode console you opened on the HMC.
At some point, the installer prompts you to re-engage the VNC session as shown below.

Exercises Guide
_______________________________________________________________________
***
*** Please return to your X-Server screen to finish installation
***
starting VNC server...
A log file will be written to: /var/log/YaST2/vncserver.log ...
***
*** You can connect to <host>, display :1 now with vncviewer
*** Or use a Java capable browser on http://<host>:5801/
***
(When YaST2 is finished, close your VNC viewer and return to this
window.)
Active interfaces:
eth0 Link encap:Ethernet HWaddr FA:4B:BD:37:1B:20

inet addr:172.26.40.11 Bcast:172.26.40.127
Mask:255.255.255.128
--
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
*** Starting YaST2 ***
_______________________________________________________________________
1. Reconnect to the VNC session to resume the installation.

2. The next step is to set the root password. Simply pick up a password, type it in twice and click
“Next” at the bottom right of the installation screen.
3. Give your system a hostname. Use the one provided to you at the exercise instructions. Uncheck
the box to change the hostname by DHCP.
4. Network has been previously configured, so simply disable the firewall at this step. Click the
blue link where it says “disable” as shown in the figure below. Make sure it gets disabled, then
click “Next”.
In the next few screens, you simply accept the

default configurations.

Exercises Guide
5. Skip the network test and click “Next” to proceed.
6. Do not make any changes at the step of CA management / OpenLDAP server / Services settings.
Simply click “Next” to proceed.
7. Do not make any changes to the user authentication method screen. Leave the local method
selected and click “Next” to proceed.
8. Do not create any users. HANA installation will create these for you. Simply click “Next” to
proceed and agree to any prompt questions.
9. On the next screen, you have the opportunity to check the release notes. Whenever you are ready
to proceed, click “Next”.
10. At the step of scanning for printers, none will be found. Click “Next” to proceed.

11. At the last screen, unselect the box to clone the system and finish the installation by clicking
the “Finish” button. At this step, the VNC connection gets broken and you should now return to
the console.
Unselect this!

Exercises Guide
12. The installation finishes and you are left with a login prompt in the system console. Log onto
the system as the root user with the password you configured in the previous steps.
______________________________________________________________________
Welcome to SUSE Linux Enterprise Server 11 SP4 (ppc64) - Kernel
3.0.76-0.11-ppc64 (console).
hana01 login: root

Password:
hana01:~ #
_______________________________________________________________________
Congratulations! You just installed Linux on Power!!
Proceed to the next exercises.

2. Tuning Linux on Power for a HANA on Power installation
There is a little tuning to Linux and some pre-requisites that you should complete before attempting
to install HANA on Power. They are:
a. Install the value added Linux on Power RAS software
b. Install the HANA on Power required OS library patches
c. Install the HANA on Power required OS kernel patches
d. Optionally create LUN aliases
e. Create HANA LVM volume groups and format the LUNs to be used by HANA
Installing the value-added Linux on Power packages
The value-added Linux on Power packages can be downloaded from the website:
http://public.dhe.ibm.com/software/server/POWER/Linux/yum/OSS/SLES/11/ppc64/
Installing these packages is important to ensure the proper functioning of all of the Power
Reliability, Availability and Serviceability (RAS) features for Linux on Power (LoP).
For the purpose of this exercise, they are already available at our staging server. Ask for the
instructor the information below to access the packages:
a. staging server IP address: ___________________
b. staging server root password: ________________
c. staging server LoP directory: _________________
1. Copy the contents of the staging server over to your system:
__________________________________________________________________
hana01:~ # scp -r padmin@172.26.40.40:~/RAS .
The authenticity of host '10.17.201.56 (10.17.201.56)' can't be established.
ECDSA key fingerprint is 8a:75:0a:96:81:65:25:c0:d9:77:8c:84:93:f0:a8:67 [MD5].
Are you sure you want to continue connecting (yes/no)? yes
Warning: Permanently added '10.17.201.56' (ECDSA) to the list of known hosts.
Password: xxxxxxx
ppc64-diag-2.6.10-1.ppc64.rpm 100% 1166KB 1.1MB/s 00:00
devices.chrp.base.ServiceRM-2.4.0.0-15161.ppc 100% 98KB 97.8KB/s 00:00
libservicelog-1.1.14-1.ppc64.rpm 100% 15KB 15.3KB/s 00:00

Exercises Guide
src-3.1.5.11-15161.ppc.rpm 100% 285KB 285.3KB/s 00:00

DynamicRM-1.3.9-9.ppc.rpm 100% 43KB 42.7KB/s 00:00
IBMinvscout-3.1.0-2.ppc64.rpm 100% 97KB 96.8KB/s 00:00
rsct.core.utils-3.1.5.11-15161.ppc.rpm 100% 1079KB 1.1MB/s 00:00
libservicelog-1_1-1-32bit-1.1.14-1.ppc64.rpm 100% 90KB 90.5KB/s 00:00
librtas-1.3.10-1.ppc64.rpm 100% 122KB 121.6KB/s 00:00
iprutils-2.3.20-1.ppc64.rpm 100% 484KB 484.4KB/s 00:00
libservicelog-32bit-1.1.14-1.ppc64.rpm 100% 13KB 12.7KB/s 00:00
powerpc-utils-1.2.20-6.ppc64.rpm 100% 315KB 314.9KB/s 00:00
libservicelog-devel-32bit-1.1.14-1.ppc64.rpm 100% 3885 3.8KB/s 00:00
libservicelog-devel-1.1.14-1.ppc64.rpm 100% 9017 8.8KB/s 00:00
librtas-32bit-1.3.10-1.ppc64.rpm 100% 119KB 119.4KB/s 00:00
libvpd2-devel-2.2.3-0.ppc64.rpm 100% 18KB 18.5KB/s 00:00
lsvpd-1.7.4-0.ppc64.rpm 100% 706KB 706.2KB/s 00:00
rsct.core-3.1.5.11-15161.ppc.rpm 100% 14MB 13.7MB/s 00:00
servicelog-1.1.12-1.ppc64.rpm 100% 65KB 65.3KB/s 00:00
libvpd2-2.2.3-0.ppc64.rpm 100% 246KB 245.7KB/s 00:00
libservicelog-1_1-1-1.1.14-1.ppc64.rpm 100% 90KB 90.4KB/s 00:00
_________________________________________________________________
2. Get into the directory where the LoP tools are located and update them with the “rpm -Uvh”
command.
__________________________________
hana01:~ # cd RAS/
hana01:~/RAS # rpm -Uvh *.rpm
warning: DynamicRM-1.3.9-9.ppc.rpm: Header V4 DSA signature: NOKEY, key ID
3e6e42be
Preparing... ########################################### [100%]
1:src ########################################### [ 8%]
Adding srcmstr to inittab...
2:rsct.core.utils ########################################### [ 17%]
3:libvpd2 ########################################### [ 25%]
4:libservicelog-1_1-1 ########################################### [ 33%]
5:lsvpd ########################################### [ 42%]
6:rsct.core ########################################### [ 50%]
0513-071 The ctcas Subsystem has been added.

0513-071 The ctrmc Subsystem has been added.

0513-059 The ctrmc Subsystem has been started. Subsystem PID is 10167.
7:servicelog ########################################### [ 58%]
8:DynamicRM ########################################### [ 67%]
9:IBMinvscout ########################################### [ 75%]
10:devices.chrp.base.Servi########################################### [ 83%]
11:libservicelog ########################################### [ 92%]
12:ppc64-diag ########################################### [100%]
__________________________________
Installing the HANA on Power required OS library packages
HANA on Power requires the following minimal package levels to be installed / updated on the
system prior to HANA installation:
a. glibc-2.11.3-17.87.3.ppc64.rpm
b. glibc-32bit-2.11.3-17.87.3.ppc64.rpm
c. libgcc_s1-32bit-4.7.2_20130108-0.17.2.ppc64.rpm
d. libgcc_s1-4.7.2_20130108-0.17.2.ppc64.rpm
e. libmpc2-0.8.2-1.7.1.ppc64.rpm
f. libmpc2-32bit-0.8.2-1.7.1.ppc64.rpm
g. libstdc++6-32bit-4.7.2_20130108-0.17.2.ppc64.rpm
h. libstdc++6-4.7.2_20130108-0.17.2.ppc64.rpm
These packages can be downloaded from https://download.suse.com/patch/finder/ . You need a

Suse account to be able to download them.
In order to make our lab experience smooth, these packages were previously downloaded to the
staging server and placed into a folder along with the HANA on Power code. Use the next section
to take a note of the location of the staging server and directory where you can find the software.
a. staging server IP address: ________________________
b. staging server root password: _____________________
c. staging server Hana code directory: _________________

Exercises Guide
1. Copy the entire HANA folder over to your system:
_____________________________________________________________________
hana01:~ # scp -r root@10.17.201.56:~/hana .
Password: xxxxxx
kernel-default-devel-3.0.101-0.42.1.7881.0.PTF.913433.p 100% 5757KB 5.6MB/s 00:00
kernel-source-vanilla-3.0.101-0.42.1.7881.0.PTF.913433. 100% 84MB 41.9MB/s 00:02
kernel-default-extra-3.0.101-0.42.1.7881.0.PTF.913433.p 100% 11MB 10.9MB/s 00:00
kernel-default-3.0.101-0.42.1.7881.0.PTF.913433.nosrc.r 100% 6715KB 6.6MB/s 00:00
[… we have saved the environment twice today ;-) …]
libgcc_s1-32bit-4.7.2_20130108-0.17.2.ppc64.rpm 100% 44KB 43.8KB/s 00:00

libgcc_s1-4.7.2_20130108-0.17.2.ppc64.rpm 100% 38KB 37.8KB/s 00:00
libstdc++6-4.7.2_20130108-0.17.2.ppc64.rpm 100% 287KB 286.6KB/s 00:00
glibc-2.11.3-17.82.11.ppc64.rpm 100% 4913KB 4.8MB/s 00:00
lvm.conf 100% 20KB 20.3KB/s 00:00
hana01:~ #
________________________________________________________________
2. Change directories to where you downloaded the software above, into the “extra” directory, and
update the packages with the “rpm -Uvh” command.
_____________________________________________________
hana01:~/hana/extra # rpm -Uvh *.rpm
Preparing... ########################################### [100%]
1:glibc-32bit ####################################### [ 13%]
2:glibc #################################### [ 25%]
3:libgcc_s1 #################################### [ 38%]
4:libgcc_s1-32bit ############################### [ 50%]
5:libmpc2 ######################################## [ 63%]
6:libmpc2-32bit ######################################## [ 75%]
7:libstdc++6-32bit ################################## [ 88%]
8:libstdc++6 ######################################### [100%]
hanaonpower:~/hana/extra #
______________________________________________________

Installing the HANA on Power kernel patches
When working with HANA on Power8 servers, a kernel patch is required. It can be downloaded
from http://download.suse.com
Download the following packages:
a. kernel-default-3.0.101-73.1.ppc64.rpm
b. kernel-default-base-3.0.101-73.1.ppc64.rpm
c. kernel-default-devel-3.0.101-73.1.ppc64.rpm
d. kernel-source-3.0.101-73.1.ppc64.rpm
For your convenience, these packages are already located in the hana directory you transferred
from the staging server. All you need to do is to install them. Follow the next steps to accomplish
it.
1. Change directories to where the HANA on Power kernel patches are and install them with the
command “rpm -ivh”.
_____________________________________________________________________
hanaonpower:~ # cd hana/kernel/
hanaonpower:~/hana/kernel_patches # rpm -ivh *.rpm
Preparing... ########################################### [100%]
1:kernel-source ########################################### [ 25%]
Changing symlink /usr/src/linux from linux-3.0.101-63 to linux-3.0.101-71
2:kernel-ppc64-base ########################################### [ 50%]
Kernel image: /boot/vmlinux-3.0.101-71-ppc64

Initrd image: /boot/initrd-3.0.101-71-ppc64
Root device: /dev/rootvg/rootlv (mounted on / as ext3)

Exercises Guide
[… we are getting good at saving the environment :-D …]
Kernel Modules: scsi_mod scsi_tgt scsi_transport_srp ibmvscsic

scsi_dh dm-mod dm-multipath dm-log dm-region-hash dm-mirror dm-
snapshot scsi_dh_hp_sw scsi_dh_rdac scsi_dh_alua scsi_dh_emc
mbcache jbd ext3 dm-round-robin dm-queue-length dm-least-pending
dm-service-time scsi_transport_fc ibmvfc usb-common usbcore ohci-
hcd uhci-hcd ehci-hcd xhci-hcd hid usbhid linear crc-t10dif sd_mod
Features: dm multipathd block usb multipath kpartx lvm2
resume.userspace resume.kernel
59386 blocks
4:kernel-ppc64-devel
########################################### [100%]
Changing symlink /usr/src/linux-obj/ppc64/ppc64 from ../../linux-
3.0.101-63-obj/ppc64/ppc64 to ../../linux-3.0.101-71-
obj/ppc64/ppc64
_______________________________________________________________________
You may ignore any warning messages at this point.
2. Adjust the /etc/lilo.conf configuration file to have the boot loader point to the new kernel by
default. The example below outlines the changes you have to make in bold green. Use vi to edit the
file, or another editor or your preference. Save the file once done.
_______________________________________________________________________
# Modified by YaST2. Last modification on Thu Sep 10 12:08:09 EDT 2015
activate
timeout = 80
boot = /dev/disk/by-id/scsi-SIBM_3303_NVDISc9e906d9a10521c920f7063c2adb2eb7-
part1
default = SLES11_SP4_1
image = /boot/vmlinux-3.0.101-71-ppc64
###Don't change this comment - YaST2 identifier: Original name: linux###
label = SLES11_SP4_1
append = " quiet sysrq=1 insmod=sym53c8xx insmod=ipr"
initrd = /boot/initrd-3.0.101-71-ppc64
root = /dev/rootvg/rootlv

image = /boot/vmlinux-3.0.101-63-ppc64
###Don't change this comment - YaST2 identifier: Original name: linux###
label = SLES11_SP4
append = " quiet sysrq=1 insmod=sym53c8xx insmod=ipr"
initrd = /boot/initrd-3.0.101-63-ppc64
root = /dev/rootvg/rootlv
_________________________________________________________________
3. Now run the command “lilo” at the command prompt for the changes to take effect.
________________________________________________
hanaonpower:~ # lilo
running on chrp
Boot target is /dev/dm-1
add note section for RS6K
MKDOSFS options: -s 16 -F 16 -n 'rootlv'
mkfs.msdos 2.11 (12 Mar 2005)
unable to get drive geometry, using default 255/63
`/lib/lilo/chrp/yaboot.chrp' -> `boot/yaboot'
`/tmp/ppc_lilo/yaboot.conf' -> `boot/yaboot.cnf'
`/boot/vmlinux-3.0.101-0.42.1.7881.0.PTF-default' ->
`boot/vmlinux.001'
`/boot/initrd-3.0.101-0.42.1.7881.0.PTF-default' ->
`boot/initrd.001'
`/boot/vmlinux-3.0.76-0.11-ppc64' -> `boot/vmlinux.002'
`/boot/initrd-3.0.76-0.11-ppc64' -> `boot/initrd.002'
Prepending '/vdevice/v-
scsi@30000002/disk@8100000000000000:1,yaboot' to open firmware
variable boot-device
_______________________________________________________________
3. Reboot the LPAR using the “shutdown -r now” command. At the boot loader prompt, verify
that the new kernel is being booted.

Exercises Guide
_______________________________________________________________________
yaboot starting: loaded at 00040000 000676d8 (0/0/00c3ba70; sp:
01d3ffd0)
Config file 'yaboot.cnf' read, 597 bytes
Welcome to yaboot version r22.8-r1190.SuSE

booted from '/vdevice/v-
scsi@30000002/disk@8100000000000000:1,yaboot'
running with firmware 'IBM,AM780_040' on model 'IBM,9179-MHB',
serial 'IBM,0282F5DEP', partition 'HanaOnPower-a7efb49c-000001e2'
boot: SLES11_SP4_1
Using 00601f94 bytes for initrd buffer
Please wait, loading kernel...
_______________________________________________________________________
3. Finally, log back onto the system and use the “uname -a” command to validate that the running
kernel is the patched one.
_______________________________________________________________________
hana01:~ # uname -a
Linux hana01 3.0.101-63-ppc64 #1 SMP Tue Jun 23 16:02:31 UTC 2015
(4b89d0c) ppc64 ppc64 ppc64 GNU/Linux
_______________________________________________________________________
Creating name aliases to the HANA LUNs (optional)
Creating aliases to the HANA LUNs that hold the database data, log and shared areas is optional,
but strongly recommended for the purpose of easier environment management later on.
1. Take note of your data, shared and log LUN wwids with the “multipath -ll” command. The
example below shows the output for one of these LUNs. It doesn't matter which one is going to be
which (data, log, shared) at this point.
__________________________________________________________________
hanaonpower:~ # multipath -ll
36005076802810187a8000000000002c3 dm-6 IBM ,2145
size=90G features='1 queue_if_no_path' hwhandler='0' wp=rw

|-+- policy='service-time 0' prio=50 status=active
| |- 4:0:0:1 sdi 8:128 active ready running
| `- 5:0:0:1 sdk 8:160 active ready running
`-+- policy='service-time 0' prio=10 status=enabled
|- 2:0:0:1 sde 8:64 active ready running
`- 3:0:0:1 sdh 8:112 active ready running
___________________________________________________________________
2. Take note of the four LUN wwids below
My rootvg LUN wwid: __________________________________

My data LUN wwid: __________________________________
My log LUN wwid: ___________________________________
My shared LUN wwid: ________________________________
3 . Create the /etc/multipath.conf file according to the example below. Replace the wwids in green
with your LUNs wwids above.
Hint: the staging server already has a working /etc/multipath.conf file. You can copy it over the
network to your system and simply replace the wwids of the LUNs. This might save you some
time.
________________________________________________________________
hanaonpower:/etc # cat /etc/multipath.conf
defaults {
polling_interval 30
failback immediate
no_path_retry queue
rr_min_io 100
path_checker tur
user_friendly_names yes
}
blacklist {
devnode "^(ram|raw|loop|fd|md|dm-|sr|scd|st)[0-9]*"
devnode "^(hd|xvd|vd)[a-z]*"
}

Exercises Guide
multipaths {
# ROOTVG VOLUME
multipath {
wwid 36005076802810187a8000000000002c0
alias ROOTVG
}
# HANA VOLUMES
multipath {
wwid 36005076802810187a8000000000002c3
alias HANA_DATA01
}
multipath {
wwid 36005076802810187a8000000000002c2
alias HANA_LOG01
}
multipath {
wwid 36005076802810187a8000000000002c1
alias HANA_SHARED01
}
}
devices {
device {
vendor "IBM"
product "2145"
path_grouping_policy group_by_prio
prio_callout "/sbin/mpath_prio_alua /dev/%n"
}
}
__________________________________________________________________
3 . Save the file and restart the multipath service.

________________________________________________________________
hanaonpower:/etc # /etc/init.d/multipathd restart
Shutting down multipathd done
Starting multipathd done
____________________________________________________________
3 . Verify that your LUNs are now named after the aliases you provided in /etc/multipath.conf. Run
the “multipath -ll” command again. The output below is for one of the three LUNs only. Validate
all of them.
______________________________________________________________________
hanaonpower:/etc # multipath -ll
HANA_LOG01 (36005076802810187a8000000000002c2) dm-5 IBM ,2145
size=90G features='1 queue_if_no_path' hwhandler='0' wp=rw
|-+- policy='service-time 0' prio=50 status=active
| |- 2:0:0:0 sdc 8:32 active ready running
| `- 3:0:0:0 sdd 8:48 active ready running
`-+- policy='service-time 0' prio=10 status=enabled
|- 4:0:0:0 sdf 8:80 active ready running
`- 5:0:0:0 sdg 8:96 active ready running
_______________________________________________________________________
4. You can now use the names like /dev/mapper/HANA_LOG01 and so on when managing these
LUNs.
______________________________________________________________________
hanaonpower:~ # ls /dev/mapper/HANA_*
/dev/mapper/HANA_DATA01 /dev/mapper/HANA_LOG01 /dev/mapper/HANA_SHARED01
______________________________________________________________________

Exercises Guide
Creating the HANA LVM volume groups and formatting the disks
Each one of the data, log and shared areas will have its own volume group. Each volume group
should hold all disks for a particular filesystem (our lab has only one disk for each of the data, log
and shared filesystems) and contain a single logical volume with all available space.
Follow the next steps to create the volume groups and logical volumes for the data, log and shared
filesystems.
1. Prepare the physical volumes with the “pvcreate” command.
_______________________________________________________________________
hanaonpower:~ # pvcreate /dev/mapper/HANA_DATA01
Physical volume "/dev/mapper/HANA_DATA01" successfully created
hanaonpower:~ # pvcreate /dev/mapper/HANA_LOG01
Physical volume "/dev/mapper/HANA_LOG01" successfully created
hanaonpower:~ # pvcreate /dev/mapper/HANA_SHARED01
Physical volume "/dev/mapper/HANA_SHARED01" successfully created
_______________________________________________________________________
2. Create three volume groups with the “vgcreate” command.
___________________________________________________________________
hanaonpower:~ # vgcreate -s 4M --dataalignment 1M hanadata
/dev/mapper/HANA_DATA01
Volume group "hanadata" successfully created
hanaonpower:~ # vgcreate -s 4M --dataalignment 1M hanalog
/dev/mapper/HANA_LOG01
Volume group "hanalog" successfully created
hanaonpower:~ # vgcreate -s 4M --dataalignment 1M hanashared
/dev/mapper/HANA_SHARED01
Volume group "hanashared" successfully created
____________________________________________________________________

3. Create three logical volumes with the “lvcreate” command.
____________________________________________________________________
hanaonpower:~ # lvcreate -i <paths> -I 256K -l 100%FREE -n datalv
hanadata
Logical volume "datalv" created
hanaonpower:~ # lvcreate -i <paths> -I 256K -l 100%FREE -n loglv
hanalog
Logical volume "loglv" created
hanaonpower:~ # lvcreate -i <paths> -I 256K -l 100%FREE -n
sharedlv hanashared
Logical volume "sharedlv" created
_____________________________________________________________________
4. Format the three logical volumes with XFS, the only currently supported filesystem for HANA
on Power.
____________________________________________________________________
hanaonpower:~ # mkfs.xfs /dev/mapper/hanadata-datalv
meta-data=/dev/mapper/hanadata-datalv isize=256 agcount=4, agsize=5897984
blks
= sectsz=512 attr=2, projid32bit=0
data = bsize=4096 blocks=23591936, imaxpct=25
= sunit=0 swidth=0 blks
naming =version 2 bsize=4096 ascii-ci=0
log =internal log bsize=4096 blocks=11519, version=2
= sectsz=512 sunit=0 blks, lazy-count=1
realtime =none extsz=4096 blocks=0, rtextents=0
hanaonpower:~ # mkfs.xfs /dev/mapper/hanalog-loglv
meta-data=/dev/mapper/hanalog-loglv isize=256 agcount=4, agsize=5897984 blks

Exercises Guide

hanaonpower:~ # mkfs.xfs /dev/mapper/hanashared-sharedlv
meta-data=/dev/mapper/hanashared-sharedlv isize=256 agcount=4,
agsize=5897984 blks
__________________________________________________________________
5. Use “vi” to create the entries in /etc/fstab to automatically mount the filesystems upon boot.
Include the following entries:
______________________________________________________________________
/dev/mapper/hanadata-datalv /hana/data xfs defaults 0 0
/dev/mapper/hanalog-loglv /hana/log xfs defaults 0 0
/dev/mapper/hanashared-sharedlv /hana/shared xfs defaults 0 0
______________________________________________________________________
You need to create mount points for each of these filesystems. As an SAP convention, use the
following mount points:
a. for data: /hana/data
b. for log: /hana/log
c. for shared: /hana/shared
6. Create the mount points, then mount the filesystems with the “mount” command and validate
they are mounted.
_________________________________________________________________
hanaonpower:~ # mkdir -p /hana/data /hana/log /hana/shared
hanaonpower:~ # mount /hana/data/
hanaonpower:~ # mount /hana/shared/
hanaonpower:~ # mount /hana/log/
hanaonpower:~ #
hanaonpower:~ # mount
/dev/mapper/rootvg-rootlv on / type ext3 (rw,acl,user_xattr)
proc on /proc type proc (rw)
sysfs on /sys type sysfs (rw)
debugfs on /sys/kernel/debug type debugfs (rw)
udev on /dev type tmpfs (rw,mode=0755)
tmpfs on /dev/shm type tmpfs (rw,relatime,mode=1777,size=8g)
devpts on /dev/pts type devpts (rw,mode=0620,gid=5)
fusectl on /sys/fs/fuse/connections type fusectl (rw)
/dev/mapper/hanadata-datalv on /hana/data type xfs (rw)
/dev/mapper/hanashared-sharedlv on /hana/shared type xfs (rw)
/dev/mapper/hanalog-loglv on /hana/log type xfs (rw)
_____________________________________________________________
You have successfully done all of the pre-requisites in Linux before installing HANA on Power.
Congratulations!
Proceed to the next exercise.

Exercises Guide
3. Installing the HANA on Power software
It is now time to install HANA on your Linux on Power system. To do so, verify that the HANA
code has been copied over to the folder “~/hana/hana_sps11”.
Within that folder there is a rar archive composed of 3 files. Uncompress it:
_______________________________________________________________________
hana01:~/hana/hana_sps11 # unrar x 51050839_part1.exe
UNRAR 3.80 beta 2 freeware Copyright (c) 1993-2008 Alexander Roshal
Extracting from 51050839_part1.exe
Creating 51050839 OK
Creating 51050839/DATA_UNITS OK
Creating 51050839/DATA_UNITS/HDB_CLIENT_LINUX_S390X_64 OK
Extracting 51050839/DATA_UNITS/HDB_CLIENT_LINUX_S390X_64/hdbsetup OK
[…]
Extracting 51050839/COPY_TM.TXT OK
Extracting 51050839/COPY_TM.HTM OK
Extracting 51050839/MD5FILE.DAT OK
Extracting 51050839/SHAFILE.DAT OK
All OK
_______________________________________________________________________
Once complete you can seee a directory named

“51050839/DATA_UNITS/HDB_LCM_LINUX_PPC64”. This is where the installer is located. The
installer is called “hdblcm”.
Before we continue, take some notes as to the parameters to use to drive the HANA installation
(suggestions made for you in parenthesis):
HANA SAP ID: (HN1) _____________________________

HANA instance number: (00) _______________________
HANA passwords (all): (Hibm2016) __________________
Restart instance after reboot: yes
Modules to install: server and client only___________

For all other parameters that are prompted during installation, accept the default values.
Let's get started. Go to the “DATA_UNITS/HDB_LCM_LINUX_PPC64” directory and call the
“hdblcm” installer. Answer to the questions according to the information you took notes above and
follow the bold guidance in the example below to answer to the questions. Install only the server
and client components and use a single container.
_______________________________________________________________________
hana01:~/hana/hana_sps11/51050839/DATA_UNITS/HDB_LCM_LINUX_PPC64 # ./hdblcm
SAP HANA Lifecycle Management - SAP HANA 1.00.112.00.1457525470

***************************************************************
Scanning Software Locations...
Detected components:
SAP HANA Database (1.00.112.00.1457525470) in
/root/hana/hana_sps11/51050839/DATA_UNITS/HDB_SERVER_LINUX_PPC64/server
SAP HANA AFL (incl.PAL,BFL,OFL,HIE) (1.00.112.00.1457538927) in
/root/hana/hana_sps11/51050839/DATA_UNITS/HDB_AFL_LINUX_PPC64/packages
SAP TRD AFL FOR HANA (1.00.112.00.1457538927) in
/root/hana/hana_sps11/51050839/DATA_UNITS/HDB_TRD_AFL_LINUX_PPC64/packages
SAP HANA Database Client (1.00.112.00.1457525470) in
/root/hana/hana_sps11/51050839/DATA_UNITS/HDB_CLIENT_LINUX_PPC64/client
SAP HANA XS Advanced Runtime (1.0.13.262519) in
/root/hana/hana_sps11/51050839/DATA_UNITS/XSA_RT_10_LINUX_PPC64/packages
XS Monitoring 1 (1.001.2) in
/root/hana/hana_sps11/51050839/DATA_UNITS/XSA_CONTENT_10/XSAC_MONITORING-
1.1.2.zip
XS Services 1 (1.001.1) in
/root/hana/hana_sps11/51050839/DATA_UNITS/XSA_CONTENT_10/XSAC_SERVICES-
1.1.1.zip
SAP Hana Demo Model for XS Advanced 1.0 (1.001.5) in
/root/hana/hana_sps11/51050839/DATA_UNITS/XSA_CONTENT_10/XSAC_SHINE-
1.1.5.zip
Choose installation
Index | System | Database Properties

------------------------------------------------
1 | Install new system |
| |
2 | Extract components |

Exercises Guide
3 | Exit (do nothing) |
Enter selected system index [3]: 1
SAP HANA Database version '1.00.112.00.1457525470' will be installed.
Select additional components for installation:
Index | Components | Description
----------------------------------------------------------------------------
-------------------
1 | server | No additional components
2 | all | All components
3 | client | Install SAP HANA Database Client version 1.00.112.00.1457525470
4 | afl | Install SAP HANA AFL (incl.PAL,BFL,OFL,HIE) version
1.00.112.00.1457538927
5 | trd | Install SAP TRD AFL FOR HANA version 1.00.112.00.1457538927
6 | xs | Install SAP HANA XS Advanced Runtime version 1.0.13.262519
Enter comma-separated list of the selected indices [3]: 1,3
Enter Installation Path [/hana/shared]:

Enter Local Host Name [hana01]:
Do you want to add additional hosts to the system? (y/n): n
Enter SAP HANA System ID: HN1
Enter Instance Number [00]:
Index | Database Mode | Description
----------------------------------------------------------------------------
-------------------
1 | single_container | The system contains one database
2 | multiple_containers | The system contains one system database and
1..n tenant databases
Select Database Mode / Enter Index [1]: 1

Index | System Usage | Description
----------------------------------------------------------------------------
---
1 | production | System is used in a production environment
2 | test | System is used for testing, not production
3 | development | System is used for development, not production
4 | custom | System usage is neither production, test nor
development
Select System Usage / Enter Index [4]: 2
Enter Location of Data Volumes [/hana/data/HN1]:

Enter Location of Log Volumes [/hana/log/HN1]:
Restrict maximum memory allocation? [n]: n
Enter Certificate Host Name For Host 'hana01' [hana01]:
Enter SAP Host Agent User (sapadm) Password: Hibm2016
Confirm SAP Host Agent User (sapadm) Password: Hibm2016
Enter System Administrator (hn1adm) Password: Hibm2016
Confirm System Administrator (hn1adm) Password: Hibm2016
Enter System Administrator Home Directory [/usr/sap/HN1/home]:
Enter System Administrator Login Shell [/bin/sh]:
Enter System Administrator User ID [1000]:
Enter ID of User Group (sapsys) [79]:
Enter Database User (SYSTEM) Password: Hibm2016
Confirm Database User (SYSTEM) Password: Hibm2016
Restart system after machine reboot? [n]: n
Summary before execution:

=========================
SAP HANA Components Installation

Installation Parameters
Remote Execution: ssh
Installation Path: /hana/shared
Local Host Name: hana01
SAP HANA System ID: HN1

Exercises Guide
Instance Number: 00
Database Mode: single_container
System Usage: test
Location of Data Volumes: /hana/data/HN1
Location of Log Volumes: /hana/log/HN1
Certificate Host Names: hana01 -> hana01
System Administrator Home Directory: /usr/sap/HN1/home
System Administrator Login Shell: /bin/sh
System Administrator User ID: 1000
ID of User Group (sapsys): 79
SAP HANA Database Client Installation Path: /hana/shared/HN1/hdbclient
Software Components
SAP HANA Database
Install version 1.00.112.00.1457525470
Location:
/root/hana/hana_sps11/51050839/DATA_UNITS/HDB_SERVER_LINUX_PPC64/server
SAP HANA AFL (incl.PAL,BFL,OFL,HIE)
Do not install
SAP TRD AFL FOR HANA
Do not install
SAP HANA Database Client
Install version 1.00.112.00.1457525470
Location:
/root/hana/hana_sps11/51050839/DATA_UNITS/HDB_CLIENT_LINUX_PPC64/client
SAP HANA XS Advanced Runtime
Do not install
Do you want to continue? (y/n): y

_______________________________________________________________________
At this point, a summary screen is presented and you can validate your installation settings before
proceeding. If you would like to make changes, simply abort the process and start over. Once
ready, go on and perform the installation.
It take about 15 to 20 minutes to have the code installed. Your mileage may vary. Validate that the
system was successfully installed as shown in the next example.
_______________________________________________________________________

[...]
Updating SAP HANA instance integration on local host...
Regenerating SSL certificates...
Deploying SAP Host Agent configurations...
SAP HANA system installed.
Log file written to '/var/tmp/hdb_HN1_hdblcm_install_115-08-
10_14.06.14/hdblcm.log' on host 'hanaonpower'.
hanaonpower:~/hana/HANA_r92/51049220/DATA_UNITS/HDB_LCM_LINUX_PPC64 #
_______________________________________________________________________
Congratulations, you have just installed HANA on Power. In order to check whether it is running
or not, you can SSH into your system as the <sid>adm user and bring up the “HDBAdmin”
interface. Doing so is much simpler from another Linux based host with an X11 environment.
1. Log onto the system as the <sid>adm user and bring up the “HDBAdmin” interface. In the
example below, the instructor used a Linux-based laptop and exported X11 directly with the -X flag
for SSH. Hint: ask your instructor on how to perform this action if you are using a windows system
for this exercise.
______________________________________________________________
ceron@curly ~ $ ssh -X hn1adm@9.18.180.241
Password: xxxxxxx
/usr/bin/xauth: creating new authority file
/usr/sap/HN1/home/.Xauthority
hanaonpower:/usr/sap/HN1/HDB00> ./HDBAdmin.sh
Starting HDBAdmin on display localhost:10.0, please wait.
NewIndexInfo: No module named _fuzzypy
indexAdmin: No module named _fuzzypy
topoInfo: No module named _fuzzypy
searchGui: No module named _fuzzypy
minerGui: No module named _fuzzypy
___________________________________________________________
2. A window like the one below is displayed. Click on the “services” tab and validate that all
services are up and running (green square lights to the left).

Exercises Guide
Congratulations! Your HANA on Power system is installed!
Proceed to the next exercise.

4. Running the HWCCT tool
The HWCCT is a HANA provided tool that you can run to check whether the environment you
plan to install HANA on Power on is compliant to the hardware specifications and I/O KPIs from
SAP.
This tool should actually be run before you attempt to install HANA onto the system in a way to
validate that the system meets the requirements prior to installation. Here at this lab session, we run
it afterwards. After all, the instructor hopes the audience was interested in installing HANA anyway
;-).
Follow these steps in order to uncompress the HWCCT tool.
1. As the root user, uncompress the tool using the SAPCAR binary (installed in the system by
HANA). You first need to change directory to the location of the HWCCT tool within the HANA
installation binary folder “~/hana” you copied over from the staging server at earlier steps. Check
the example below. Replace <SID> below with your HANA system's SAP ID.
________________________
hanaonpower:~ # cd
hana/hana_sps11/51050839/DATA_UNITS/SAP_HANA_HWCCT_LINUX_PPC64/
hanaonpower:~/hana/hana_sps11/51050839/DATA_UNITS/SAP_HANA_HWCCT_L
INUX_PPC64 # /usr/sap/<SID>/HDB00/exe/SAPCAR -xvf HWCCT.SAR
SAPCAR: processing archive HWCCT.SAR (version 2.01)
x hwcct
x hwcct/manifest
[ … ]
x hwcct/lib/Python/man/mann/lassign.n
SAPCAR: 3433 file(s) extracted
______________________________________
2. Patch the LandscapeTest.py file. Ask your instructor on where this file is on the staging server
and copy it over to overwrite the existing one.
3. Within the directory where HWCCT was extracted, create two text files, one called system.json
and the other fs-short.json. The contents of each file can be found below.

Exercises Guide
system.json: (edit the hostname in bold green below. Use your system's hostname).
___________________________________________________
{
"use_hdb":false,
"blades":["hana01"],
"tests": [{
"package": "LandscapeTest",
"test_timeout": 0,
"id": 1,
"config": {},
"class": "EvalOs"
}]
}
___________________________________________________
fs-short.json: (edit the hostname and path to the filesystems according to your system's values.
They are highlighted in bold green below)
____________________________________________________________________
{
"use_hdb":false,
"blades":["hana01"],
"tests": [{
"package": "FilesystemTest",
"test_timeout": 0,
"id": 1,
"config": {"mount":{"hana01":["/hana/data/HN1"]},
"duration":"short"},
"class": "DataVolumeIO"
},{
"package": "FilesystemTest",
"test_timeout": 0,
"id": 2,
"config": {"mount":{"hana01":["/hana/log/HN1"]},
"duration":"short"},
"class": "LogVolumeIO"
}
]
}
___________________________________________________________________

4. To run each test, perform the following actions in the directory where HWCCT was extracted to.
Run once for system.json and another for fs-short.json.
____________________________
# source envprofile.sh
# ./hwval -f <file>.json
____________________________
Check the output of each command. Also, each one creates a sub-folder with the date and time in
which the command was run. Within it you can find more information about the tests results.
Specifically for the file system short I/O test, you must compare the output KPIs with the following
table:
End of exercise
Congratulations! You have successfully completed a full HANA on Power installation!
End of exercise

Exercises Guide
Exercise review and wrap-up
In these exercises, you learned the following points:
a. install Linux on Power onto an LPAR

b. install the Linux on Power value-added RAS tools
c. apply the required patches for a HANA on Power installations
d. tune the OS multipath configuration to work with LUN aliasing
e. create and format the HANA disks for the data, log and shared areas.
f. install HANA on Power
g. verify that HANA is running
I. validate the installed environment with the HWCCT tool
The instructor hopes this lab exercise was useful and insightful to your job role. Also, remember that all of us have the
responsibility of caring about our environment. Think about a sustainable life, and put it to practice! The future of
everyone depends on you!
THANK YOU!


Lab Exercise: Installing SAP HANA On Power: Come and Do It Yourself!

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Lab Exercise: Installing SAP HANA On Power: Come and Do It Yourself!

Uploaded by

Copyright:

Available Formats

2015 IBM Systems Technical University

© Copyright IBM Corporation 2016 1

My VPN username: _____________________

My Power server name: ________________________

Other useful information (random notes for lab access):

2 © Copyright IBM Corporation 2016

1. Linux on Power installation

Getting a console terminal

Retrieving name of managed system(s) . . .

Enter Number of Managed System. (q to quit): 2

Enter Number of Running Partition (q to quit): 2

hana01.smc.iic.ihost.com login: root

4 © Copyright IBM Corporation 2016

Last login: Tue Jun 7 18:38:54 EDT 2016 from vpnc-104-

Rebooting the system and getting into the SMS menu

Broadcast message from root (console) (Wed Sep 9 17:53:41

The system is going down for system halt NOW!

© Copyright IBM Corporation 2016 5

1 = SMS Menu 5 = Default Boot List

Memory Keyboard Network SCSI Speaker

6 © Copyright IBM Corporation 2016

X = eXit System Management Services

© Copyright IBM Corporation 2016 7

Welcome to SuSE Linux Enterprise 11!

Type "install" to start the YaST installer on this CD/DVD

Welcome to yaboot version r22.8-r1190.SuSE

8 © Copyright IBM Corporation 2016

running with firmware 'IBM,AM780_040' on model 'IBM,9179-MHB',

Starting a Linux on Power installation with VNC

© Copyright IBM Corporation 2016 9

*** You can connect to <host>, display :1 now with vncviewer

Resuming the installation in graphical mode over VNC: phase 1

10 © Copyright IBM Corporation 2016

© Copyright IBM Corporation 2016 11

2. Skip the installation media step and click “Next” to proceed.

12 © Copyright IBM Corporation 2016

3. Answer “Yes” to the prompt below and proceed.

© Copyright IBM Corporation 2016 13

14 © Copyright IBM Corporation 2016

© Copyright IBM Corporation 2016 15

a. The boot disk _____________________

16 © Copyright IBM Corporation 2016

© Copyright IBM Corporation 2016 17

18 © Copyright IBM Corporation 2016

Click “Finish” to complete the creation of this partition.

© Copyright IBM Corporation 2016 19

20 © Copyright IBM Corporation 2016

© Copyright IBM Corporation 2016 21

22 © Copyright IBM Corporation 2016

14. Create the swap logical volume and filesystem:

© Copyright IBM Corporation 2016 23

15. Create the /usr/sap filesystem:

24 © Copyright IBM Corporation 2016

16. Create the root logical volume and filesystem:

© Copyright IBM Corporation 2016 25

You must select the following software patterns:

26 © Copyright IBM Corporation 2016

© Copyright IBM Corporation 2016 27

28 © Copyright IBM Corporation 2016

Resuming the installation in graphical mode over VNC: phase 2

© Copyright IBM Corporation 2016 29

eth0 Link encap:Ethernet HWaddr FA:4B:BD:37:1B:20

1. Reconnect to the VNC session to resume the installation.