PUBLIC SAP HANA Platform SPS 09 Document Version: 1.1 – 2015-02-16 Red Hat Enterprise Linux (RHEL) 6.
Content 1 How to Use This Document. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 2 Install SAP HANA Manually on RHEL for SAP HANA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 2.1 Synonyms for Different Hosts. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 2.2 Prepare the Host. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
1 How to Use This Document This guide is divided into three main parts: 1. Manual installation of a RHEL host with SAP HANA 2. Installation with a kickstart file 3. Appendixes that provide shortcuts to more detailed information Read the entire chapter first, and then follow the instructions. Some steps depend to a large extent on your environment and the devices used in your servers. In this case, we can only instruct you what to do, but not how.
2 Install SAP HANA Manually on RHEL for SAP HANA A manual SAP HANA installation on RHEL for SAP HANA needs to be prepared. 2.1 Synonyms for Different Hosts The following host names have to be substituted with the corresponding host names in your environment: ● Mandatory hosts They need to be accessible, as the installation fails without them ○ Host to install: .example.com ○ Without using a RHN Satellite Server ○ Webserver for kickstart files: .example.
● Check the availability of the NTP server # service ntpd stop # ntpdate ntp.example.com # service ntpd start ○ Check if the NTP service is enabled # chkconfig | grep ntpd ntpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off ntpdate 0:off 1:off 2:off 3:off 4:off 5:off 6:off ○ If not, enable the NTP service # chkconfig ntpd on ● The ntpdate service script adjusts the time according to the NTP server every time when the system starts.
○ The firmware package should be in sync with the kernel revision. If it is not installed, Install it with: # yum -y update kernel kernel-firmware ○ Now you can erase the old kernel. ○ Reboot the machine and use the new kernel: # reboot ○ The old kernel can be erased with: # package-cleanup --oldkernels --count=1 -y ○ For technical details on updating RHEL 6.5 for SAP HANA please refer also to: ○ Red Hat Enterprise Linux for SAP HANA: system updates and supportability https://access.redhat.
● Create mount points # mkdir -p /hana/{shared,data,log} # mkdir -p /usr/sap ● On these Logical Volumes, create four file systems based on xfs. For more information about creating and tuning XFS file systems, have a look at the manpage of the mkfs.xfs executable. ○ XFS is a good file system for large files or for extremely small files. One disadvantage is the the lack of tuning support once you have created the file system. This means that you have to tune the file system while creating it.
# chkconfig kdump off If it should be enabled for support purposes, keep it enabled. Any settings can be made in /etc/ sysconfig/kdump. Restart it to apply the new settings.
# tuned-adm profile latency-performance # chkconfig tuned on # service tuned start ● For hardware with 8 IvyTown sockets and larger, the maximum number of processes for the sapsys group is not sufficient. This causes the the installation of SAP HANA to fail. The solution is to create the /etc/security/limits.d/99-sapsys.conf file: @sapsys soft nproc unlimited By default, RHEL for SAP HANA is configured in such a way as to prevent "fork bombs".
3 SAP HANA Installation On the following pages, the steps to install SAP HANA are explained in detail. Please substitute the parameters shown in . The installation is straightforward, but please read the SAP HANA Server Installation and Update Guide before you begin. 3.1 Prerequisites Below you can find the prerequisites which must be met before you can install the SAP HANA system. The official SAP HANA packages can be downloaded from the SAP Service Marketplace.
3.1.2 SAP HANA The table below shows information about SAP HANA.
3.2.1 Install SAP HANA Interactively Using hdblcm In this chapter, we install an SAP HANA instance on the system. You have to make sure that the system itself is installed as described in the “Preparation of the host” section, and that all preconditions from the tables above are met. Unless stated otherwise, the name of the volume groups, users and paths are examples that can be replaced to meet the needs of the OEM.
● Note If you are using the official SAP HANA SPS 08 installation archive from the SAP Service Marketplace, you need to replace the HanaHWCheck.py file as described in SAP Note 1658845, so that the SAP HANA installer can recognize Red Hat Enterprise Linux 6.5 as a valid operating system. In revisions higher than 80 this problem does not occur. Launch the installer. # .
3.2.2 Install SAP HANA Interactively Using hdblcmgui You can install an SAP HANA system from a graphical interface by running the SAP HANA lifecycle management tool hdblcmgui. This tool is available as an interactive tool for GNOME and as a command line tool (hdblcm) to be used in a kickstart session.
square brackets is used to install a Multi-tenant database holding multiple containers. By default, a singlecontainer database will be installed. For a complete guide to all parameters, see the SAP HANA Server Installation and Update Guide. Note If you are using the official SAP HANA SPS 08 installation archive from the SAP Service Marketplace, you need to replace the HanaHWCheck.py file as described in SAP Note 1658845, so that the SAP HANA installer can recognize Red Hat Enterprise Linux 6.
● Add the following parameters: ○ ksdevice=, for example ○ ksdevice=link (for the first network device with a link) ○ ksdevice=eth3 ○ ks=, for example ○ ks=https://192.168.0.200/kickstart.php?instance=01&sid=RHT ○ ks=http://192.168.0.200/hana.cfg ○ ip=, for example ip=192.168.0.101 ○ netmask=, for example netmask=255.255.255.0 ○ gateway=, for example gateway=192.168.0.
○ The network interfaces and the udev numbering are defined. If the kickstart process uses DHCP/PXE, the network parameters used here must be the ones used later on. All parameters must be set by the OEM. Avoid network directives using fixed IP on the kernel command line when using DHCP/PXE. ○ Set the host name. In a real environment, this could also be obtained using DNS/BIND. The SAP HANA installer expects the short version of the hostname without the domain (no FQDN). ○ Modify the file /etc/hosts.
If the product is installed using kickstart, the following variables are set in /etc/sysctl.cfg: Table 3: Parameter RHEL for SAP HANA Remarks net.ipv4.tcp_slow_start_after_idle 1 Default for RHEL* net.ipv4.conf.all.rp_filter 0 Default for RHEL net.ipv4.ip_local_port_range 40000 65300 Set by installer* net.ipv4.neigh.default.gc_thresh{1,2,3} {128,512,1024} Default for RHEL** net.ipv6.neigh.default.gc_thresh{1,2,3} {128,512,1024} Default for RHEL** kernel.
3.7 The Kickstart Process The kickstart process can be initiated using PXE or with a physical or virtual DVD. When the system boots, the user sees a selection of options. The first option Install or upgrade an existing system is highlighted by default. ● Depending on the hardware manufacturer and your country, set your keyboard to the appropriate mapping so that you can access certain special characters more easily. You do this in the main menu, under Keyboard.
4 Appendix The appendix provides additional information. 4.1 Appendix A - Networking Ports The table below shows the TCP/IP ports used in the SAP HANA environment. The firewall is not yet part of the kickstart mechanism and will be added later on request. The placeholder "xx" must be replaced with the SAP HANA instance number.
● tcsh ● libssh2 ● expect ● cairo ● graphviz ● iptraf ● krb5-workstation ● krb5-libs.i686 ● nfs-utils ● lm_sensors ● rsyslog ● openssl098e ● openssl ● xauth ● PackageKit-gtk-module ● libcanberra-gtk2 ● libtool-ltdl ● gcc ● glib ● glib-devel ● glibc ● glibc-devel ● zlib-devel ● libstdc++-devel ● kernel-devel ● rpm-build ● redhat-rpm-config ● numactl ● iperf Additionally, the packages iperf and numactl must be installed if the benchmark HWCCT is intended to be used.
4.3 Appendix C – Additional Packages for SAP HANA Support The following program is used for SAP support. It is usually not shipped on a DVD/Channel for the plain RHEL 6.x installation. This program has to be downloaded from the SAP Service Marketplace: ● niping See the table below for details of what these programs are used for. Table 5: Name Description niping SAP tool used for testing the network 4.
4.5 Appendix E – Tunable Kernel Parameters The following tunable kernel parameter should be set in /etc/sysctl.conf in order to optimize the performance of the database. Table 7: Parameter RHEL 6.5 net.ipv4.tcp_slow_start_after_idle 0 net.ipv4.conf.all.rp_filter 0 net.ipv4.ip_local_port_range 40000 61000 net.ipv4.neigh.default.gc_thresh{1,2,3} {256,1024,4096} net.ipv6.neigh.default.gc_thresh{1,2,3} {256,1024,4096} kernel.shmmax 137438953472* kernel.shmall 33554432* kernel.
The size entries in the tables are an example for the logical volumes: Table 8: Logical Volume Size Mount Point lv_hana_shared System memory /hana/shared lv_hana_data 3 * System memory /hana/data lv_hana_log System memory /hana/log lv_usr_sap At least 50 GiB /usr/sap Example calculation: System memory: 96 GiB ● /hana/shared = Size of system memory = 96 GiB ● /hana/data = 3 times the size of system memory = 288 GiB ● /hana/log = Size of system memory = 96 GiB ● /usr/sap = At least 50 GiB = 50
File: /etc/sysconfig/network-scripts/ifcfg- DEVICE= HWADDR= IPADDR= PREFIX= ONBOOT=yes BOOTPROTO=static ● Next configure the dhcp server to listen on the correct network interface (only necessary if the server has more than one network card and should only provide the service on a specific card) File: /etc/sysconfig/dhcpd DHCPDARGS= ● You then have to provide a minimal se
○ SSH ○ DHCP ○ Save your configuration # service iptables save Configure the rest of the required services and initialize the tftp storage to provide the files needed to start up the system. ● Configure TFTP ○ Append to file: /etc/xinetd.d/tftp bind = <192.168.0.100> ○ Activate tftp # chkconfig tftp on ○ Restart xinetd # service xinetd restart ● Configure PXE ○ Copy PXE base files # mkdir -p /var/lib/tftpboot/linux-install/pxelinux.cfg # cp /usr/share/syslinux/pxelinux.
○ Is the kickstart file in place? # ls /var/www/html/hana.cfg ○ Are the permissions set correctly? # chmod 644 /var/www/html/hana.cfg ○ Does the URL point to the PXE installer machine? ○ Before partitioning, ensure that the disk is erased entirely. Check the kickstart file if it contains the following keywords in the partitioning section. ○ zerombr ○ clearpart –all ○ Make a syntax check of the kickstart file # ksvalidator
zerombr clearpart --all --drives=sde,sdf,sdg reboot # Additional RH SFS and SAP repositories # 20140430 uncommented SMS # This usually has to be modified by the OEM repo --name=sfs --baseurl=ftp://192.168.0.100/pub/repos/sfs/ --cost=1 repo --name=sap --baseurl=ftp://192.168.0.100/pub/rhel6/sap/ --cost=2 # Create LVs and filesystems.
# Additional packages from the SAP repository cpufrequtils compat-sap-c++ unixODBC # ********** Post-Installation 1: Modify grub.conf, install grub and custom xfs format for HANA_DISK ********** %post --interpreter /bin/bash # Part 1: Modify grub.conf sed -i 's/splashimage=(hd1,0)/splashimage=(hd0,0)/g' /boot/grub/grub.conf sed -i 's/root (hd1,0)/root (hd0,0)/g' /boot/grub/grub.conf # Part 2: Install the boot loader properly.
enabled=1 gpgcheck=1 gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release EOF # The SAP-Repository, which is needed for SAP HANA cat > /etc/yum.repos.d/rhel-sap.repo << EOF [sap] name=Red Hat Enterprise Linux for SAP baseurl=ftp://${SERVER}/pub/rhel6/sap enabled=1 gpgcheck=0 EOF %end # ********** Post-Installation 4: Create the resolv.conf file ********** %post --interpreter /bin/bash # Part 1: Declaration of the network parameters. !!!!!!!!!! To be modified by OEM. !!!!!!!!!! DOMAINS=example.com,sap.
BOOTPROTO=${BPROTO[${i}]} IPADDR=${IPADDR[${i}]} PREFIX=${PREFIX[${i}]} HWADDR=${HWADDR[${i}]} ONBOOT=${bootstart} TYPE=Ethernet EOF echo "# Network card ${i}" >> /etc/udev/rules.d/70-persistent-net.rules echo "SUBSYSTEM==\"net\", ACTION==\"add\", DRIVERS==\"?*\", ATTR{address}==\"$ {HWADDR[${i}]}\", ATTR{type}==\"1\", KERNEL==\"eth"'*'"\", NAME=\"eth${i}\"" >> /etc/udev/rules.d/70-persistent-net.rules echo "" >> /etc/udev/rules.d/70-persistent-net.rules i=$(expr ${i} + 1); done cp /etc/udev/rules.
%end # 20140430 SAP HANA off # ********** Post-Installation 8: Install the SAP HANA database software ********** %post --interpreter /bin/bash # Part 1: Set the installation server. !!!!!!!!!! To be modified by OEM. !!!!!!!!!! SERVER=192.168.0.100 # Part 2: Copy the archive and the password file cd /tmp wget ftp://${SERVER}/pub/hana/HanaInstall_WS.29.04.2014.tar cd /root wget ftp://${SERVER}/pub/hana/password.xml chmod 400 /root/password.xml cd /tmp tar xvf HanaInstall_WS.29.04.2014.
esac ;; fi done # Part 2: Delete variables not known to RHEL 6.5. This must be revised when new releases are published declare -a errors=(net.bridge.bridge-nf-call-{ip6tables,iptables,arptables} net.ipv6.neigh.default.gc_thresh{1,2,3}) for parm in "${errors[@]}"; do if $(cat $KernelParamFile | grep -v \# $KernelParamFile | grep -q $parm $KernelParamFile > /dev/null); then sed -i /$parm/d $KernelParamFile fi done %end 4.
Schema Calculated port Description 3xx01 39901 Primary Site for Clustering 3xx07 39907 4.9.2 Common Networks When creating the firewall, do not forget to ask the customer which different networks s/he will need the services in. You can use the list of usual networks from the table below as a basis. These networks are also used in the sample kickstart script.
--state NEW --dport # /sbin/iptables -I --state NEW --dport # /sbin/iptables -I --state NEW --dport # /sbin/iptables -I --state NEW --dport # /sbin/iptables -I --state NEW --dport # /sbin/iptables -I --state NEW --dport # /sbin/iptables -I --state NEW --dport # /sbin/iptables -I --state NEW --dport 39917 -j ACCEPT INPUT 2 -s 39915 -j ACCEPT INPUT 2 -s 1128 -j ACCEPT INPUT 2 -s 1129 -j ACCEPT INPUT 2 -s 59913 -j ACCEPT INPUT 2 -s
Related Information SAP Note 1995460 - Single SAP HANA VM on VMware vSphere in production SAP Note 2024433 - Multiple SAP HANA VMs on VMware vSphere in production (controlled availability) WMware Best Practices on SAP HANA Prepare the Host [page 4] 4.11 Apendix K - Important SAP Notes Read the following SAP Notes. These SAP Notes contain the latest information about the installation.
Important Disclaimer for Features in SAP HANA Options There are several types of licenses available for SAP HANA. Depending on the license type of your SAP HANA installation, some of the features and tools that are described in the SAP HANA platform documentation may only be available via the SAP HANA options, which may be released independently of an SAP HANA Platform Support Package Stack (SPS).
Important Disclaimers and Legal Information Coding Samples Any software coding and/or code lines / strings ("Code") included in this documentation are only examples and are not intended to be used in a productive system environment. The Code is only intended to better explain and visualize the syntax and phrasing rules of certain coding.
Red Hat Enterprise Linux (RHEL) 6.5 Configuration Guide for SAP HANA Important Disclaimers and Legal Information PUBLIC © 2015 SAP SE or an SAP affiliate company. All rights reserved.
www.sap.com/contactsap © 2015 SAP SE or an SAP affiliate company. All rights reserved. No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an SAP affiliate company. The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors. National product specifications may vary.
