Hana Ha

Huawei SAP HANA Appliance Cluster Installation
Guide (RH5885H V3&RH8100 V3 +5500

V3+Redhat7.2)
Issue 02
Date 2017-04-10
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2015. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in th e
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://e.huawei.com
Issue 02 (2017-04-10) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
Guide (RH5885H&RH8100 V3+5500 V3+Redhat7.2) About This Document
About This Document
Purpose
This document describes how to install SAP HANA cluster on the Huawei FusionServer
RH5885H V3/RH8100 V3(RH5885H V3/RH8100 V3 for short) SLES12 SP1 and Huawei
OcanStor 5500 V3 (5500 V3 for short). It covers the software and hardware planning and
configurations on the RH5885H V3/RH8100 V3and 5500 V3, dedicated operating system
(OS) installation, and database installation and installation verification of the SAP HANA.
This document provides guidance on installing SAP HANA Database Software SP09_091.0
or later and SAP HANA Database Software SP10_100.0 or later.
Intended Audience
This document is intended for:
 Technical support engineers
 Maintenance engineers
 Users
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates an imminently hazardous situation which, if not

avoided, will result in death or serious injury.
Indicates a potentially hazardous situation which, if not

avoided, could result in death or serious injury.

avoided, may result in minor or moderate injury.
Issue 02 (2017-04-10) Huawei Proprietary and Confidential ii

Guide (RH5885H&RH8100 V3+5500 V3+Redhat7.2) About This Document
Symbol Description

avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to personal
injury.
Calls attention to important information, best practices and

tips.
NOTE is used to address information not related to personal
injury, equipment damage, and environment deterioration.
Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes made in earlier issues.
Issue 01 (2016-11-18)
This issue is the first office release.
Issue 02 (2017-04-10)
Update LVM partitioner.
Issue 02 (2017-04-10) Huawei Proprietary and Confidential iii

Guide (RH5885H&RH8100 V3+5500 V3+Redhat7.2) Contents
Contents
About This Document ............................................................................................................ ii

Contents .................................................................................................................................. iv
1 Installation Planning ............................................................................................................. 1
1.1 Hardware Planning ............................................................................................................................................................... 1
1.2 Software Planning .................................................................................................................................................................1
1.3 Capacity Planning .................................................................................................................................................................2
1.3.1 RH5885H/RH8100 V3 OS disk planning ..................................................................................................................... 2
1.3.2 5500V3 Capacity Planning for RH5885 H V3 ................................................................................................................ 3
1.3.3 5500V3 Capacity Planning for RH8100 V3 .................................................................................................................... 3
1.4 Storage Planning ................................................................................................................................................................... 4
1.4.1 Storage Planning for RH5885H V3 .................................................................................................................................. 4
1.4.2 Storage Planning for RH8100 V3 ..................................................................................................................................... 5
1.4.3 Storage pool Planning........................................................................................................................................................ 5
1.4.4 File system planning andLogical port planning............................................................................................................... 6
1.5 Network Planning .................................................................................................................................................................9
1.6 Default Parameters.............................................................................................................................................................. 12
1.7 Installation Process ............................................................................................................................................................. 13
2 5500 V3 Deployment ........................................................................................................... 14

2.1 5500 V3 Installation ........................................................................................................................................................... 14
2.2 Configuration Overview ..................................................................................................................................................... 14
2.3 Physical Environment Deployment ................................................................................................................................... 14
2.4 Storage Space Configuration.............................................................................................................................................. 14
3 RH5885H V3/RH8100 V3 Deployment .............................................................................. 29

3.1 Installing the OS ................................................................................................................................................................. 29
3.1.1 Preparing for Installation................................................................................................................................................. 29
3.1.2 Logging In to the RH5885H V3/RH8100 V3 Remote Control Interface .................................................................... 29
3.1.3 Setting the BIOS .............................................................................................................................................................. 30
3.1.4 Configuring the RAID Controller Card.......................................................................................................................... 36
3.1.5 Mounting the OS ISO File .............................................................................................................................................. 41
3.2 Installing an OS................................................................................................................................................................... 42
3.3 Basic configuration ............................................................................................................................................................. 54
Issue 02 (2017-04-10) Huawei Proprietary and Confidential iv

3.3.1 Network Configure .......................................................................................................................................................... 54

3.3.2 Use PuTTY....................................................................................................................................................................... 55
3.3.3 Modifying the hosts File ................................................................................................................................................. 57
3.4 Install system fix package and OS setting ......................................................................................................................... 58
3.4.1 Mount the image file ....................................................................................................................................................... 58
3.5 Install system fix package(the script included ,you can skip this chapter ) .................................................................... 59
3.5.1 Configure YUM source ................................................................................................................................................... 59
3.5.2 Install system fix package ............................................................................................................................................... 60
3.5.3 SAP HANA configuration ............................................................................................................................................... 60
3.6 Configuring Network IP Addresses ................................................................................................................................... 62
3.7 Configuring the SSH Interconnection Service .................................................................................................................. 64
3.8 Configuring the NFS Service ............................................................................................................................................. 64
3.9 Configuring grub Parameters ............................................................................................................................................. 65
3.10 Configuring the DM Multipath Service .......................................................................................................................... 67
4 Switch Configuration .......................................................................................................... 74

4.1 CE6800 Switch Stacking .................................................................................................................................................... 74
4.2 SNS2124 FC Switch Zone Configuration ......................................................................................................................... 75
5 Basic Service Configuration ............................................................................................... 77

5.1 Configuring the NTP Service ............................................................................................................................................. 77
5.1.1 Configurations on the Server .......................................................................................................................................... 77
5.1.2 Configuring the NTP Client ............................................................................................................................................ 78
5.2 Configuring the DNS Service ............................................................................................................................................ 80
5.2.1 Configurations on the Server (for Linux)....................................................................................................................... 80
5.2.2 Configurations on the DNS Client.................................................................................................................................. 82
6 Performance Optimization ................................................................................................. 84

6.1 Configuring THP ................................................................................................................................................................ 84
6.2 Configuring the UUID Service .......................................................................................................................................... 85
6.3 Configuring Process Resource Restriction........................................................................................................................ 85
6.4 Optimizing Sysctrl.conf Parameters .................................................................................................................................. 85
6.5 Optimizing Network Performance ..................................................................................................................................... 86
6.6 Optimizing Storage Performance....................................................................................................................................... 87
6.6.1 Optimization on the Storage ........................................................................................................................................... 87
6.6.2 Optimization on the Server ............................................................................................................................................. 87
7 SAP HANA Database Installation ..................................................................................... 88

7.1 Preparing for the Installation.............................................................................................................................................. 88
7.1.1 Configuring sudoers ........................................................................................................................................................ 88
7.1.2 Obtaining HANA Software Packages ............................................................................................................................ 88
7.1.3 Installing the SAP Host Agent (Optional) ...................................................................................................................... 88
7.1.4 Configuring global.ini ..................................................................................................................................................... 88
7.1.5 Creating HANA Installation Paths ................................................................................................................................. 90
Issue 02 (2017-04-10) Huawei Proprietary and Confidential v

7.2 Installing a SAP HANA Database ..................................................................................................................................... 90

7.2.1 One-Click Installation on the Master Node ................................................................................................................... 90
7.2.2 Installation on Nodes One by One.................................................................................................................................. 98
7.3 Checking the Database Installation .................................................................................................................................103
7.4 Adjusting hdbparam parameter ........................................................................................................................................104
7.4.1 HANA1.0 DataBase parameter: ...................................................................................................................................104
7.4.2 HANA2.0 DataBase parameter.....................................................................................................................................105
7.5 Checking the HANA Cluster Status ................................................................................................................................106
7.6 Adjusting the performance of the Cluster........................................................................................................................107
8 SAP HANA Database Uninstallation .............................................................................. 108

8.1 Preparing for the Uninstallation .......................................................................................................................................108
8.1.1 Stopping Services ..........................................................................................................................................................108
8.1.2 Backing Up Data............................................................................................................................................................108
8.2 Uninstalling the SAP HANA Database ...........................................................................................................................108
8.2.1 One-Click Uninstallation...............................................................................................................................................108
8.2.2 Uninstallation from Nodes One by One ....................................................................................................................... 110
A ntp.conf .............................................................................................................................. 112

B global.ini ............................................................................................................................ 115
Issue 02 (2017-04-10) Huawei Proprietary and Confidential vi

Guide (RH5885H&RH8100 V3+5500 V3+Redhat7.2) 1 Installation Planning
1 Installation Planning
1.1 Hardware Planning

Table 1-1 describes the hardware planning for SAP HANA.
Table 1-1 Hardware planning

Hardware Model Type Description
RH5885H Rack server Provides computing resources.

V3/RH8100 V3
5500 V3 Storage system Provides the Network File System

(NFS) service and storage resources.
CE6800 10GE switch Provides service and high availability

(HA) networks.
/ (Optional) Domain Provides the Network Time Protocol

name server (NTP) and domain name server (DNS)
services.
/ (Optional) Management Provides the device management

switch network.
Cable Power cable Connects hardware devices or used for

PGND cable configuring parameters.
10GE stacking cable
Ethernet cable
Optical fiber
1.2 Software Planning

Table 1-2 describes the software planning for SAP HANA.
Issue 02 (2017-04-10) Huawei Proprietary and Confidential 1

Table 1-2 Software planning
Software Name and Version Source Description
SLE-12-SP1-SAP-DVD-x86_64-G https://www.suse.com/ Customized SAP

M-DVD.iso OS
multipath-tools-0.5.0-46.1.x86_64. https://www.suse.com/ Multipath

rpm package
kpartx-0.5.0-46.1.x86_64.rpm
kernel-default-3.12.67-60.64.24.1. https://www.suse.com/ SUSE kernel

x86_64.rpm patch file
IMDB_SERVER100_122_5-10009 https://launchpad.support.sap. HAHA database

569.SAR com/#/softwarecenter software
SAPCAR_617-80000935_Linux_6
4bit.EXE
1.3 Capacity Planning

1.3.1 RH5885H/RH8100 V3 OS disk planning
Table 1-3 Built-in disk planning
Raid Physical Volume Partition File Mount Description
Volume. Group Size System Point
VD0 — — 1GB Ext4 /boot Standard Partition

(Raid 1)
600GB
lv_usrsap vg_os 200GB Ext4 /usr/sap
Used to
install the lv_swap vg_os 20GB swap swap
OS
lv_root vg_os Remaining Ext4 /

space

1.3.2 5500V3 Capacity Planning for RH5885 H V3

Table 1-4 SAN storage mount planning (using 2 TB memory capacity as an example)
Partition File System Partition Partition Source Description
Type planning Size
/hana/data xfs 3 x RAM 6 TB SAN Used for a

storage single HANA
node.
/hana/log xfs >=512G 512 GB SAN Used for a

storage single HANA
node.
Table 1-5 File system mount planning (using eight 2 TB nodes as an example)

Type planning Size
/hana/shar nfs 2x RAM(every 4 TB File engine Used for a

ed 4 nodes need HANA cluster.
1xRAM)
1.3.3 5500V3 Capacity Planning for RH8100 V3

Table 1-6 SAN storage mount planning (using 2 TB memory capacity as an example)
Type planning Size
/hana/data xfs 3 x RAM 12 TB SAN Used for a single

storage HANA node.
/hana/log xfs >=512G 512 GB SAN Used for a single

storage HANA node.
Table 1-7 File system mount planning (using eight 2 TB nodes as an example)
Type planning Size
/hana/shared nfs 2x RAM(every 8 TB File Used for a

4 nodes need engine HANA cluster.
1xRAM)

1.4 Storage Planning

1.4.1 Storage Planning for RH5885H V3
Table 1-8 Disk domain planning—the first storage
Disk Domain ID Number of Hard Disks(See the Hard Disk Type
configuration description.)
DiskDomain_Shared 0 8 SAS, 900G
DiskDomain _Data_1 1 12 SAS, 900G

DiskDomain _Log 4 8 SSD, 600G
Table 1-9 Disk domain planning—the second storage

---
configuration description:
 Rules for configuring the number of disks in the shared volume: The value is calculated based on the
number of HANA nodes and memory capacity of each HANA node. All disks in the shared
volume are installed in the first set of SAN+NAS storage.
8*900G SAS (RAID5,4D+1P);
 Rules for configuring the number of disks in the data volume: The value is calculated based on the
memory capacity of HANA nodes.
5500 V3_1 (SAN+NAS):
DiskDomain _Data_1: 12*900G SAS ; (512GB/1TB/1.5TB/2TB RAM per node); (RAID5,8D+1P);
DiskDomain _Data_2: 12*900G SAS ; (512GB/1TB/1.5TB/2TB RAM per node); (RAID5,8D+1P);
DiskDomain _Data_3: 12*900G SAS ; (512GB/1TB/1.5TB/2TB RAM per node) ;(RAID5,8D+1P);
5500 V3_2...N(SAN):

 Rules for configuring the number of disks in the log volume: The value is calculated based on the
memory capacity of HANA nodes.
5500 V3_1 (SAN+NAS):
8*600G SSD(512GB/1TB/1.5TB/2TB RAM per node) (RAID5,4D+1P);
5500 V3_2…N(SAN):
8*600G SSD(512GB/1TB/1.5TB/2TB RAM per node) (RAID5,4D+1P);
1.4.2 Storage Planning for RH8100 V3

Table 1-10 Disk domain planning—the first storage

DiskDomain_Shared 0 14 SAS, 900G
Table 1-11 Disk domain planning—the second storage

1.4.3 Storage pool Planning

Table 1-12 Storage pool planning for the first 5500 V3
Storage Pool ID stripe_depth Function Disk Domain
StoragePool_Shared 0 128KB File storage service HANA_Shared
StoragePool_Data_01 1 128KB Block storage service HANA _Data_1

StoragePool_Log 4 128KB Block storage service HANA _Log
Table 1-13 Storage pool planning for the second 5500 V3
StoragePool_Data_04 0 128KB File storage service HANA _Data_4
StoragePool_Log 4 128KB Block storage service HANA _Log
1.4.4 File system planning andLogical port planning

Table 1-14 File system planning(eg.8 nodes RH5885H V3)
File System ID Capacity Thin Function Storage Pool
HANA_Shared 0 4 TB Disabled StoragePool_Shared
Table 1-15 Logical port planning
Port IP Address Subnet Gateway Active Others

Name Mask Port
Bond0 192.168.2.19 255.255.240.0 255.255.255.0 bond0 Default

Bond1 192.168.2.20 255.255.240.0 255.255.255.0 bond1 Default
Ensure that IP addresses of the logical ports and that of the client which used to access the NAS file
system are on the same network segment.
Table 1-16 NFS shared planning
Shared File Client Type Rights Write Mode Rights Root

Path System Name Level Permission Rights
Control Control
/HANA_ HANA_ 192.168. Host Read/ Asynchronous no_all_squash no_root_s

shared shared 2.11 Write quash

Shared File Client Type Rights Write Mode Rights Root

Path System Name Level Permission Rights
Control Control
192.168. Host Read/ Asynchronous no_all_squash no_root_s

2.12 Write quash
… … … … … …
192.168. Host Read/ Asynchronous no_all_squash no_root_s

2.18 Write quash
The NFS shared planning uses a HANA cluster configured with eight 2 TB nodes as an example.
Table 1-17 LUN planning (for the first 5500 V3)
Name ID Type Capacity Controller Cache Prefetch Storage Pool

Policy Policy
LUN_Data 1 thick 6 TB CTE.A Default Non-prefetch StoragePool_

_001 Data01
LUN_Data 2 thick 6 TB CTE.B Default Non-prefetch StoragePool_

_002 Data02
LUN_Data 3 thick 6 TB CTE.B Default Non-prefetch StoragePool_

_003 Data03
LUN_Log 4 thick 512 GB CTE.A Default Intelligent StoragePool_L

_001 prefetch og
LUN_Log 5 thick 512 GB CTE.A Default Intelligent
_002 prefetch
LUN_Log 6 thick 512 GB CTE.B Default Intelligent

_003 prefetch
Table 1-18 LUN planning (for the second 5500 V3)
Name ID Type Capacity Controller Cache Prefetch Storage

Policy Policy Pool
LUN_Data 1 thick 6 TB CTE.A Default Non-prefetch StoragePool

_004 _Data04
… … … … … … … …
LUN_Data 4 thick 6 TB CTE.A Default Non-prefetch StoragePool
_007 _ Data07
LUN_Log 5 thick 512 GB CTE.A Default Intelligent StoragePool

_004 prefetch _Log

Name ID Type Capacity Controller Cache Prefetch Storage

Policy Policy Pool
… … … … … … …
LUN_Log 8 thick 512 GB CTE.B Default Intelligent
_007 prefetch
The LUN planning uses a HANA cluster configured with eight 2 TB nodes (including seven worker
nodes) as an example. Seven data LUNs and seven log LUNs are planned.
Table 1-19 LUN group planning (for the first 5500 V3)
Name ID LUN
LUN_Group_HANA 0 LUN_Data_001
LUN_Data_002
LUN_Data_003
LUN_Log_001
LUN_Log_002
LUN_Log_003
Table 1-20 LUN group planning (for the second 5500 V3)
Name ID LUN
LUN_Group_HANA 0 LUN_Data_004
…
LUN_Data_007
LUN_Log_004
…
LUN_Log_007
Table 1-21 Host planning

Name OS IP Address Initiator 1 Initiator 2
(Optional)
HANA01 Linux 192.168.2.11 21000024ff8f5016 21000024ff8f5017
HANA02 Linux 192.168.2.12 21000024ff8f5000 21000024ff8f5001

Name OS IP Address Initiator 1 Initiator 2

(Optional)
… … … … …
… … … … …
HANA08 Linux 192.168.2.18 21000024ff89ec2f 21000024ff89ac2c
You can run the following commands to check the host initiator information in Linux.
 Command for checking world wide name (WWN): cat /sys/class/fc_host/host*/port_name
 Command for checking Fibre Channel (FC) port status: cat /sys/class/fc_host/host*/port_state
 Command for checking FC port rate: cat /sys/class/fc_host/host*/speed
Table 1-22 Host group planning

Host Group ID Host
HANA 0 HANA01
HANA02
HANA08
Table 1-23 Mapping view planning

Name LUN Group Host Group
MappingView_HANA LUN_Group_HANA HANA
1.5 Network Planning

This document describes the planning of the test network in a laboratory. Customers can make
plans for related IP addresses based on the site requirements.

Figure 1-1 Network
Table 1-24 Network planning
Device Name Type Host Name IP Address Planning
RH5885H V3 BMC /(Node 1) 192.168.34.51, 255.255.255.0,

management 192.168.32.1
… …
/(Node 8) 192.168.34.58, 255.255.255.0,

192.168.32.1
Service HW00001MG 192.168.34.61, 255.255.255.0,

management 192.168.32.1
… …
HW00008MG 192.168. 34.68, 255.255.255.0,

192.168.32.1
Cluster intranet NODE01 192.168.1.11, 255.255.255.0
… …
NODE08 192.168.1.18, 255.255.255.0
NFS network HANA01 192.168.2.11, 255.255.255.0
… …
HANA08 192.168.2.18, 255.255.255.0
Uplink service HW00001 10.10.1.11, 255.255.255.0,

10.10.1.254
… …
HW00008 10.10.1.18, 255.255.255.0,

10.10.1.254

Device Name Type Host Name IP Address Planning
5500 V3 Management N/A Control board A: 192.168.34.69

network Control board B: 192.168.34.70
Logical ports N/A Bond0: 192.168.2.19

of the NFS file Bond1: 192.168.2.20
system
The host name of the cluster intranet can be the same as that of the uplink service.
Table 1-25 NIC binding planning
Node No. Network Type Mode IP Address Bond Slaves
1 Cluster Bond0 2 (Active-Active) 192.168.1.11 eth4, eth7

intranet
NAS Bond1 2 (Active-Active) 192.168.2.11 eth6, eth9

network
Uplink Bond2 2 (Active-Active) 10.10.1.11 eth5, eth8

service

intranet

network
service
… … … … … …

intranet

network

service
 The binding mode of uplink service bond ports can be adjusted according to configuration rules of
the customer's live network; however, those of the cluster intranet and NAS network are always
Active-Active, and you are not advised to change them.
 The NIC binding rule is that a bond port must consist of two different physical NIC ports. Figure 1-2
shows the 10GE ports on the rear of the RH5885H V3.

Figure 1-2 NIC binding rule
1.6 Default Parameters

Table 1-26 lists the default IP address parameters, and Table 1-27 describes the default user
parameters.
Table 1-26 Default IP address parameters
Component Parameter Default Value
RH5885H iBMC management module Default IP address:

V3/ RH8100 192.168.2.100
V3 Subnet mask: 255.255.255.0
5500 V3 FC SAN storage array controller Default IP addresses:

 Active controller:
192.168.128.101
 Standby controller:
192.168.128.102
Subnet mask: 255.255.0.0
Table 1-27 Default user parameters
Componen Parameter Description Example

t
RH5885H iBMC Used for logging in to Username: root

V3/ RH8100 management the WebUI, SSH, and Password: Huawei12#$
V3 module SNMP through a serial
port or a network port.
5500 V3 Storage array Used for logging in to Username: admin
the 5500 V3 storage Password: Huawei12#$
array.

Componen Parameter Description Example

t
SNS2124 Used for logging in to Username: admin

switch the management port on Password: Huawei12#$
the switch
CE6810 Used for logging in to Username: root
switch the management port on Password: Huawei12#$
the switch
1.7 Installation Process

Figure 1-3 shows the SAP HANA cluster installation process.
Figure 1-3 Installation process

Guide (RH5885H&RH8100 V3+5500 V3+Redhat7.2) 2 5500 V3 Deployment
2 5500 V3 Deployment
2.1 5500 V3 Installation

This section describes how to remove and install all components (including 2 U controller
enclosures and disk enclosures) and cables of the 5500 V3. For details about how to install
and initialize the 5500 V3, see OceanStor 5300, 5500, 5600, 5800, 6800 V3 Storage Series
Product Description.
2.2 Configuration Overview

This section provides an overview of the 5500 V3 configuration process.
The 5500 V3 (SAN+NAS storage) can be categorized into a file engine and a storage unit and
provides the NFS shared service and storage space for the SAP HANA system. Consisting of
a control subrack cascaded by a hard disk subrack, the storage unit can be independently used
as a SAN storage system, or be used as a unified storage system with the file engine
configured.
2.3 Physical Environment Deployment

 Prepare servers, switches, and storage devices, and set up a network according to a
planned solution architecture.
 Install the OS, software packages, and software licenses.
2.4 Storage Space Configuration

For an 8-node cluster, you need to configure two 5500 V3s.
Figure 2-1 shows the process of configuring storage space (data_01/02/03, log_01/02/03, and
hana_shared) for the first 5500 V3.

Figure 2-1 Process of configuring storage space for the first 5500 V3
Figure 2-2 shows the process of configuring storage space (data_04/05/06/07 and
log_04/05/06/07) for the second 5500 V3.
Figure 2-2 Process of configuring storage space for the second 5500 V3
Step 2 Create disk domains.

Log in to the DeviceManager, choose Huawei Storage > Provisioning > Disk Domain, click
Create, and create all disk domains according to Table 1-8.
Figure 2-3 Creating disk domains (1)
Figure 2-4 Creating disk domains (2)
Or log in to the 5500 V3 CLI, and run the following commands to create disk domains:
For the first 5500 V3:
create disk_domain name=HANA_shared disk_number=8 disk_type=SAS disk_domain_id=0
create disk_domain name=HANA_Data_1 disk_number=12 disk_type=SAS disk_domain_id=1
create disk_domain name=HANA_Log disk_number=8 disk_type=SSD disk_domain_id=4

For the second 5500 V3:

create disk_domain name=HANA_Log disk_number=8 disk_type=SSD disk_domain_id=4
Disk domain information similar to the following is displayed on the CLI:
Step 3 Create storage pools.

Log in to the DeviceManager, choose Huawei Storage > Provisioning > Storage Pool, click
Create, and create all storage pools according to Table 1-12 and Table 1-13.
Figure 2-5 Creating storage pools (1)
Figure 2-6 Creating storage pools (2)
For the required hard disk capacity, the following RAID5 attributes are recommended:
StoragePool_Shared: 4D+1P;
StoragePool_Data: 8D+1P;
StoragePool_Log: 4D+1P;
Or log in to the 5500 V3 CLI, and run the following commands to create storage pools:
Switch to an advanced user and obtain corresponding rights.
change user_mode current_mode user_mode=developer

create storage_pool name=StoragePool_Shared disk_type=SAS capacity=4400GB

raid_level=RAID5-5 disk_domain_id=0 pool_id=0 usage_type=file_system
full_threshold=85
create storage_pool name=StoragePool_Data_001 disk_type=SAS capacity=7TB
raid_level=RAID5-9 disk_domain_id=1 pool_id=1 stripe_depth=128KB usage_type=lun
full_threshold=85
full_threshold=85
full_threshold=85
create storage_pool name= StoragePool_Log disk_type=SSD capacity=2500GB
raid_level=RAID5-5 disk_domain_id=4 pool_id=4 usage_type=lun full_threshold=85

full_threshold=85
full_threshold=85
full_threshold=85
full_threshold=85
create storage_pool name= StoragePool_Log disk_type=SSD capacity=2500GB
raid_level=RAID5-5 disk_domain_id=4 pool_id=5 usage_type=lun full_threshold=85
Storage pool information similar to the following is displayed on the CLI:
Step 4 Create a file system.

Log in to the DeviceManager, choose Huawei Storage > Provisioning > File System, click
Create, and create a file system according to Table 1-14.

Figure 2-7 Creating a file system
Or log in to the 5500 V3 CLI, and run the following command to create a file system:
create file_system general name=HANA_share pool_id=0

initial_distribute_policy=automatic capacity=8TB alloc_type=thick
File system information similar to the following is displayed on the CLI:
Step 5 Check the Ethernet ports whose running status is Link up.
Log in to the DeviceManager, choose Huawei Storage > Provisioning > Port > Ethernet
Ports, and check the Ethernet ports whose running status is Link up.
Figure 2-8 Ethernet port view
Step 6 Create bond ports.

Log in to the DeviceManager, and choose Huawei Storage > Provisioning > Port > Bond
Ports > Create. In the dialog box displayed, bind CTE0.A.IOM0.P0 to CTE0.A.IOM0.P1
and CTE0.B.IOM0.P0 to CTE0.B.IOM0.P1. The two bond ports are named Bond0 and
Bond1 respectively.
Figure 2-9 Creating bond ports (1)
Creating bond ports (2)

Step 7 Create a logical port.

Log in to the DeviceManager, and choose Huawei Storage > Provisioning > Port > Logical
Ports > Create. In the dialog box shown in Figure 2-10, enter logical port properties
according to 0.
Figure 2-10 Creating a logical port
Figure 2-11 Logical port view
Step 8 Create an NFS shared path.

Prerequisites:
 You have imported an NFS license and enabled the NFS service.
 You have created an NFS.
 Data required for the NFS sharing configuration has been ready.
1 Log in to the DeviceManager, choose Huawei Storage > Provisioning > Share > NFS
(Linux/UNIX/MAC) > Create.
Figure 2-12 File sharing
2 In the dialog box shown in Figure 2-13, enter related information according to Table
1-16.
Figure 2-13 Creating an NFS shared path
3 In the dialog box shown in Figure 2-14, add clients.

Figure 2-14 Add Client
In the Name or IP Address text box, enter the IP addresses of clients to be accessed. If you enter *, any
host can access the NFS shared path.
Figure 2-15 Setting permissions

Figure 2-16 Confirming your settings
Step 9 Create LUNs.

Log in to the DeviceManager, choose Huawei Storage > Provisioning > LUN > LUN >
Create. In the dialog box displayed, create all LUNs according to Table 1-17 and Table 1-18.
Figure 2-17 LUN (1)
Figure 2-18 LUN (2)
Or log in to the 5500 V3 CLI, and run the following commands to create LUNs:


create lun name=LUN_Data_001 pool_id=1 capacity=6TB owner_controller=0A
create lun name=LUN_Data_002 pool_id=2 capacity=6TB owner_controller=0B
create lun name=LUN_Log_001 pool_id=4 capacity=512GB owner_controller=0A
create lun name=LUN_Log_002 pool_id=4 capacity=512GB owner_controller=0B

LUN information similar to the following is displayed on the CLI:
Step 10 Create LUN groups.

Log in to the DeviceManager, choose Huawei Storage > Provisioning > LUN > LUN
Group > Create. In the dialog box displayed, create all LUN groups according to Table 1-19
and Table 1-20, and add LUNs to the LUN groups.
Figure 2-19 LUN Group (1)

Figure 2-20 LUN Group (2)
Or log in to the 5500 V3 CLI, and run the following commands to create LUN groups:
create lun_group name=HANA lun_id_list=0,1,2,3,4,5 lun_group_id=0
create lun_group name=HANA lun_id_list=0,1,2,3,4,5,6,7 lun_group_id=0
Step 11 Create hosts.

Log in to the DeviceManager, choose Huawei Storage > Provisioning > Host > Host >
Create. In the dialog box displayed, create all hosts and add host initiators according to Table
1-21.
Figure 2-21 Host (1)
Figure 2-22 Host (2)
Or log in to the 5500 V3 CLI, and run the following commands to create hosts:
create host name=HANA01 operating_system=Linux host_id=0 ip_address=192.168.2.11
…

Step 12 Enable ALUA.

Log in to the DeviceManager, choose Huawei Storage > Provisioning > Host, select a host,
select a host initiator, and modify it. In the Modify Initiator dialog box, select Enable
ALUA.
Figure 2-23 Enable ALUA
If there are multiple host initiators to be modified, you can run the following commands using
the CLI:
admin:/>change initiator initiator_type=FC wwn=21000024ff89ac2c multipath_type=ALUA
admin:/>change initiator initiator_type=FC wwn=21000024ff89ac2d multipath_type=ALUA
admin:/>change initiator initiator_type=FC wwn=21000024ff89ac8a multipath_type=ALUA
admin:/>change initiator initiator_type=FC wwn=21000024ff89ac8b multipath_type=ALUA
admin:/>change initiator initiator_type=FC wwn=21000024ff89adbe multipath_type=ALUA
admin:/>change initiator initiator_type=FC wwn=21000024ff89adbf multipath_type=ALUA
Or log in to the 5500 V3 CLI, and run the following commands to add host initiators and
enable ALUA:
add host initiator host_id=0 initiator_type=FC wwn=10000090fa502b0a multipath_type=ALUA
add host initiator host_id=0 initiator_type=FC wwn=10000090fa502b0b multipath_type=ALUA
add host initiator host_id=1 initiator_type=FC wwn=21000024ff4a5170 multipath_type=ALUA
add host initiator host_id=1 initiator_type=FC wwn=21000024ff4a5171 multipath_type=ALUA
add host initiator host_id=2 initiator_type=FC wwn=21000024ff4bc554 multipath_type=ALUA
add host initiator host_id=2 initiator_type=FC wwn=21000024ff4bc555 multipath_type=ALUA
…
add host initiator host_id=7 initiator_type=FC wwn=21000024ff36b932 multipath_type=ALUA
add host initiator host_id=7 initiator_type=FC wwn=21000024ff36b933 multipath_type=ALUA
Step 13 Create host groups.

Log in to the DeviceManager, choose Huawei Storage > Provisioning > Host > Host
Group > Create. In the dialog box displayed, create all host groups and add hosts according
to Table 1-22.

Figure 2-24 Host Group (1)
Figure 2-25 Host Group (2)
Or log in to the 5500 V3 CLI, and run the following commands to create host groups:
create host_group name=HANA host_id_list=0,1,2,3,4,5,6,7 host_group_id=0
Step 14 Create a mapping view.

Log in to the DeviceManager, choose Huawei Storage > Provisioning > Mapping View >
Create. In the dialog box displayed, create a mapping view according to Table 1-23.
Figure 2-26 Mapping View (1)

Figure 2-27 Mapping View (2)
Or log in to the 5500 V3 CLI, and run the following command to create a mapping view:
create mapping_view name=HANA host_group_id=0 lun_group_id=0
Step 15 Configure a device to automatically synchronize time with the NTP server.
Figure 2-28 Clicking Basic Information
Figure 2-29 Configuring time synchronization

Except production storage devices, all hardware devices (such as backup storage devices) in a HANA
environment are configured to synchronize time with the same NTP server, to avoid system abnormality
caused by inconsistent time.
----End

Guide (RH5885H&RH8100 V3+5500 V3+Redhat7.2) 3 RH5885H V3/RH8100 V3 Deployment
3 RH5885H V3/RH8100 V3 Deployment
3.1 Installing the OS

This section describes how to install the Redhat7.2 for SAP by using the image file.
3.1.1 Preparing for Installation

 Prepare an RH5885H V3/RH8100 V3 server running normally, which has no alarms
generated on the iBMC management page.
 Prepare a PC running Windows, which is used to access the RH5885H V3/RH8100 V3.
 Obtain the Linux ISO image. (Redhat7.2 For SAP.iso is used as an example in this
section.)
3.1.2 Logging In to the RH5885H V3/RH8100 V3 Remote Control

Interface
Step 1 In the browser address bar, enter the iBMC IP address of node 1 https://192.168.2.100. If the
message "There is a problem with this website's security certificate." is displayed, click
Continue to this website (not recommended).
The iBMC login page of the RH5885H V3/RH8100 V3 is displayed, as shown in Figure 3-1.
Figure 3-1 Logging in to iBMC
Step 2 Enter the user name and password for logging in to iBMC (the default user name is root, and
the default password is Huawei12#$).
The iBMC page is displayed.

Step 3 Choose Remote Control > Remote Virtual Console (shared mode).
Figure 3-2 Opening the KVM console
Step 4 The remote keyboard, video, and mouse (KVM) screen is displayed, as shown in Figure 3-3.
Figure 3-3 Remote KVM screen
----End
3.1.3 Setting the BIOS

Step 1 On the toolbar, click to restart the server.
If the server is powered off, click Power On.
If the server has been powered on, click Cold Reset from the drop-down list
Step 2 When the screen show as Figure 3-4 during the server startup, press Delete to open the BIOS
setup screen.

Figure 3-4 Startup screen
Step 3 When a screen show as Figure 3-5, enter the BIOS password (sensitive to uppercase and
lowercase) in the dialog box.
NOTE
The BIOS default password is "Huawei12#$". If you have not configured any BIOS password, the
BIOS screen is displayed, as shown in Figure 3-6.
Figure 3-5 Entering the BIOS password

Figure 3-6 BIOS screen
Step 4 Select IntelRCSetup on the menu, select Advanced Power Management Configuration
using the downward arrow, and press Enter, as shown in Figure 3-7.
Figure 3-7 Selecting Advanced Power Management Configuration
Step 5 Turning off Power Policy Select: Select Custom, and press Enter, as shown in Figure 3-8.

Figure 3-8 Selecting Custom
Step 6 In the displayed list box, select Disable, and press Enter to turn off P State, as shown in
Figure 3-9.
Figure 3-9 Turning off P State

Step 7 Turning off C-States: Press Esc to exit the CPU P State Control screen, select CPU C State
Control using the downward arrow, and press Enter, as shown in Figure 3-10.
Figure 3-10 Selecting CPU C State Control
 Turning off CPU C3 State: Select CPU C3 report, and press Enter. Select Disable, and
press Enter to turn off CPU C3 State.
 Turning off CPU C6 State: Select CPU C6 report, and press Enter. Select Disable, and
press Enter to turn off CPU C6 State.
 Turning off Enhanced Halt State: Select Enhanced Halt State, and press Enter. Select
Disable, and press Enter to turn off Enhanced Halt State.
Step 8 Turning off T-States: Press Esc to exit the CPU C State Control screen, select CPU T State
Control using the downward arrow, and press Enter, Press Esc to exit the CPU T State
Control screen , as shown in Figure 3-11.

Figure 3-11 Selecting CPU T State Control
Step 9 Press F10, select Yes, and press Enter to save the BIOS settings and restart the server, as
shown in Figure 3-12.
Figure 3-12 Saving the BIOS settings and restarting the server
The BIOS parameter configuration is complete.

----End

3.1.4 Configuring the RAID Controller Card

The RH5885H V3/RH8100 V3 SAP HANA cluster server is configured with two 600 GB
SAS hard disks. Before installing the OS, you need to configure the two hard disks as RAID
1.
The RAID controller type could be found in the iBMC : Information  Component Info 
RAID Card.
Step 1 During the server startup, when "Press <Ctrl><R> for Run MegaRAID Configuration Utility"
is displayed, press Ctrl+R to open the RAID configuration screen, as shown in Figure 3-13.
Figure 3-13 Opening the RAID configuration screen
Step 2 On the RAID configuration page, as shown in Figure 3-14.
Figure 3-14 VD Mgmt page
If this RAID controller card has been configured (has been used in maintenance and OS
reinstallation scenarios before), we need to clear the "old RAID configured".

Caution: All hard disk data and RAID information will be lost after you Del the RAID
Configured. Back up data before this operation.
Step 3 Press "F2", On the displayed page, select Create Virtual Drive, as shown in Figure 3-15.
Figure 3-15 Create Virtual Drive
Step 4 Users can perform RAID configuration according to the requirements specific parameter, for
example as shown in Figure 3-16.
RAID level: RAID-1;

PD per Span: N/A;

Drivers: 2*600G hard disks;
Figure 3-16 Selecting a configuration parameter
RAID Configuration Parameter Item Description:

RAID Level: RAID level representing the configuration, such as RAID 1,RAID-5, RAID-50;
PD per Span: This Configuration items in the user selects RAID-50 or RAID-60 level
after ,it configure the number of the hard disks packet, e.g. RH5885H V3 Sizing 4T
configuration, the configuration 14 hard disks for HANA Storage, RAID level is RAID-50,
"PD per Span "parameter should be set to "7";
Drives: displays hard disk information available, on the left there is a "[ ]" indicates whether
you select this hard drive to make RAID configuration. It can be selected through the "Enter"
key;
Basic Settings: expressed the need for configuration or can be configured VD storage space;
Advanced: Advanced Parameters RAID configuration page, you can configure the "Strip
Size", "Read Policy", "Write Policy", "I / O Policy", "Disk cache Policy", "Initialize" and
"Configure HotSpare" parameters, as follows Figure 3-17;
Step 5 Complete Advanced Parameter Items then click OK as Figure 3-17.
Strip Size=128KB
Read Policy=Normal
Write Policy=Write Back with BBU
I/O Policy = Direct
Disk cache Policy = Disable
Emulation = Default
Initialize=[X]

Figure 3-17 Advanced Parameter Items
Caution: When you select "Initialize" item will prompt the need for initialization page, and
prompts to initialize will delete all data, here select "OK", as shown in Figure 3-18
Figure 3-18 Initialization page
Step 6 After configuring the "Advanced" page ,click "OK" in the "Create New VD" page as Figure
3-19.And then choose No in the "enable SSD caching" page as Figure 3-19.

Figure 3-19 Complete Advanced Configuration
Step 7 It will return to the main administration page , and will be prompted to "Initialization
complete on VD 0", here only need to select "OK", as shown in Figure 3-20.
If you complete to create the VD0, the main administration page will show the VD0 all
information, as shown in Figure 3-20;
Figure 3-20 VD Mgmt page
Step 8 Set the Boot device : Press Ctrl-N to Ctrl Mgmt Page and set VD0 as the Boot device; as
shown in Figure 3-21.Then select "Apply" press "Enter".

Figure 3-21 Set boot device
Step 9 Choose Warm Reset from the drop-down list, as shown in Figure 3-22. Restart the system.
Figure 3-22 Restart the system
----End
3.1.5 Mounting the OS ISO File

Mount the OS ISO file to the virtual DVD-ROM drive. See Figure 3-23.
Step 1 Click .

Step 2 Select Image File.

Step 3 Click Browse next to Image File.
Step 4 In the dialog box displayed, select Redhat7.2 For SAP.iso and click Open.
Step 5 Click Connect.
Figure 3-23 Mounting an OS ISO file to the virtual DVD-ROM drive
----End
3.2 Installing an OS
Step 1 On the installation page, select Install Red Hat Enterprise Linux 7.2, and press Enter, as
Figure 3-24 Installation page
Step 2 Use default language configuration , and click Continue, as shown in Figure 3-25.

Figure 3-25 Selecting default language configuration
Step 3 On INSTALLATION SUMMARY page, click DATE&TIME, the as shown in Figure 3-26.
Figure 3-26 INSTALLATION SUMMARY
Step 4 Select a time zone, and click Done, as shown inFigure 3-27.
NOTE
You can set the time zone based on the actual condition.

Figure 3-27 Select a time zone
Step 5 On INSTALLATION SUMMARY page, click SOFTWARE SELECTION, as shown in

Figure 3-28.
Figure 3-28 SOFTWARE SELECTION
Step 6 On SOFTWARE SELECTION page, In Base Environment list, choose Infrastructure

Server ,In Add-Ons for Selection Environment list, choose Large Systems Performance,
Network File System Client ,Performance Tool, Compatibility Libraries, then click Done,
as shown in Figure 3-29.

Figure 3-29 SOFTWARE SELECTION
Step 7 On INSTALLATION SUMMARY page, click Installation Destination, as shown in Figure

3-30.
Figure 3-30 Available Storage on linux
Step 8 On INSTALLATION DESTINATION page, click sda Disks, and click I will configure
partitioning , then click Done , as shown in Figure 3-31.

Figure 3-31 INSTALLATION DESTINATION
Step 9 Choose Standard Partition, and Click + to add a partition, click Modify and choose sda for
partitioning, as shown in Figure 3-32.
Figure 3-32 Manual Partitioning
Step 10 Input /boot to mount, and Click Add mount point, as shown in Figure 3-33.

Figure 3-33 Add Partition on /dev/sda
Step 11 Input /boot to mount point row , Input 1 GiB to Desired Capacity ,choose Standard
Partition , and choose ext4 file system , click Modify and choose sda for partitioning , as
Figure 3-34 New Partition Size
Step 12 Click + ,Select swap, and Click Add mount point, as shown in Figure 3-35.
Figure 3-35 swap

Step 13 Input 20 GiB to Desired Capacity ,choose LVM , and choose swap file system ,select Create
a new volume group in the Volume Group and choose sda to create vg_os , as shown in
Figure 3-36 Figure 3-37.
Figure 3-36 swap
Figure 3-37 create volume group vg_os
Step 14 After Save the vg_os, click Update Setting, as shown in Figure 3-38.

Figure 3-38 swap
Step 15 then click +, Input /usr/sap to mount point row, and Click Add mount point.Input 200 GiB
to Desired Capacity ,choose LVM , and choose ext4 file system ,then select vg_os in the
Volume Group. Click update setting, as shown in Figure 3-39 Figure 3-40.
Figure 3-39 usr/sap partition
Figure 3-40 /usr/sap partition

Step 16 Click + and Input / to mount point row , then Click Add mount point . Input 336.85 GiB to
Desired Capacity, choose LVM , and choose ext4 file system, then select vg_os in the
Volume Group. Click update setting, as shown in Figure 3-41 Figure 3-42.
Figure 3-41 / partition
Figure 3-42 / partition
Step 17 Complete partition as shown in Figure 3-43, then click Done.

Figure 3-43 Complete partition for /dev/sdb
Step 18 On SUMMARY OF CHANGES page, Click Accept Changes, as shown inFigure 3-44.
Figure 3-44 Create Format
Step 19 After completing format partition, On INSTALLATION SUMMARY page, Click

NETWORK &HOST NAME, as shown in Figure 3-45.

Figure 3-45 Network & host name
Step 20 Input a Host name, such as HW00001, and click Done, as shown in Figure 3-46.
Figure 3-46 Hostname
Step 21 On INSTALLATION SUMMARY page, click Begin Installation, as shown in Figure 3-47

Figure 3-47 Begin Installation
Step 22 On the displayed page shown in Figure 3-48, click USER SETTINGS , set a password of
user root, as shown in Figure 3-49
The password must consist of uppercase, lowercase, digits, and special characters, for
example, Huawei_123.
Figure 3-48 Setting a password for user root

Figure 3-49 Setting a password for user root
Step 23 The system will reboot after installation finish, The page shown in Figure 3-50 is displayed,
indicating that OS installation is complete.
Figure 3-50 Installation complete
----End
3.3 Basic configuration

To run SAP HANA on a RHEL system, you need to make some configuration changes at the
OS level to provide the best performance and a stable system.
3.3.1 Network Configure

Step 1 Log in to the server as user root in the KVM.
Step 2 Make sure you want to plug in the network cable .Configurations in the vi
/etc/sysconfig/network-scripts/ifcfg-ens18f0 file(The file maybe other name if you plug in
other port):
[root@HW00001 ~]# vi /etc/sysconfig/network-scripts/ifcfg-ens18f0

TYPE=Ethernet
BOOTPROTO=static
DEFROUTE=yes
PEERDNS=yes
PEERROUTES=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=yes
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_PEERDNS=yes
IPV6_PEERROUTES=yes
IPV6_FAILURE_FATAL=no
NAME=ens18f0
UUID=a9770467-b59a-458a-b3c3-91fe63b5ad63
DEVICE=ens18f0
ONBOOT=yes
IPADDR=192.168.34.61
NETMASK=255.255.255.0
Step 3 Restart the service network

[root@hw00001 network-scripts]# service network restart
Restarting network (via systemctl): [ OK ]
Step 4 Run the "systemctl stop firewalld" "systemctl disable firewalld" command to close the
firewall, and press Enter.
[root@hw00001 home]# systemctl stop firewalld

[root@hw00001 home]# systemctl disable firewalld
Step 5 Repeat step1~step4 to configure other nodes.

----End
3.3.2 Use PuTTY

Step 1 Connect a network cable to the first network port on the RH5885H V3/RH8100 V3.
Use PuTTY to log in to the server. Enter a user name and password (user root and its
password of the OS) for login, as shown in Figure 3-51 and Figure 3-52.The language
displayed in Figure 3-53 is related to the OS language of the host where the tool is located.

Figure 3-51 Double-clicking PUTTY.EXE
Enter IP address and port then click Open, as shown in Figure 3-52.
Figure 3-52 Connecting to the server
Enter the user name and password, and press Enter, as shown in Figure 3-53.

Figure 3-53 Logging in to the server
3.3.3 Modifying the hosts File

Edit the hosts files on the HANA server node to implement hostname resolution.
Step 1 Log in to server and run the vi /etc/hosts command to edit the hosts file.
Step 2 Enter i to enter the editing mode, add parsing statements to the end of the file.
The actual statements vary according to the host name and IP address (service IP address) of
the customer's environment. This section uses the following as an example:
192.168.1.11 NODE01 NODE01
192.168.2.11 HANA01 HANA01
10.10.1.11 HW00001 HW00001
192.168.34.61 HW00001MG HW00001MG
192.168.1.12 NODE02 NODE02

192.168.2.12 HANA02 HANA02
10.10.1.12 HW00002 HW00002
192.168.34.62 HW00002MG HW00002MG
192.168.1.13 NODE03 NODE03

192.168.2.13 HANA03 HANA03
10.10.1.13 HW00003 HW00003
192.168.34.63 HW00003MG HW00003MG
192.168.1.14 NODE04 NODE04

192.168.2.14 HANA04 HANA04
10.10.1.14 HW00004 HW00004
192.168.34.64 HW00004MG HW00004MG
192.168.1.15 NODE05 NODE05

192.168.2.15 HANA05 HANA05
10.10.1.15 HW00005 HW00005
192.168.34.65 HW00005MG HW00005MG
192.168.1.16 NODE06 NODE06

192.168.2.16 HANA06 HANA06

10.10.1.16 HW00006 HW00006
192.168.34.66 HW00006MG HW00006MG
192.168.1.17 NODE07 NODE07

192.168.2.17 HANA07 HANA07
10.10.1.17 HW00007 HW00007
192.168.34.67 HW00007MG HW00007MG
192.168.1.18 NODE08 NODE08

192.168.2.18 HANA08 HANA08
10.10.1.18 HW00008 HW00008
Step 3 Press ESC and enter wq! to save the file and exit.
Step 4 Repeat step1~step3 to configure every node in /etc/hosts. (create mapping relation about IP
address and hostname).
----End
3.4 Install system fix package and OS setting

3.4.1 Mount the image file
Step 1 Click Browse to choose the ISO and click Connect to mount the image file in the KVM.
Step 2 Run mount /dev/sr0 /mnt/ to mount the CD-ROM drive to the /mnt/ directory.
In the command, sr0 indicates a CD-ROM path. Set the path based on actual situations:
[root@hw00001]# mount /dev/sr0 /mnt
mount: /dev/sr0 is write-protected, mounting read-only
Step 3 Run cd /mnt command , to enter mnt directory.Then copy the prepare_hana_host.sh to
/home

[root@hw00001 mnt]# cd /mnt

[root@hw00001 mnt]# cp prepare_hana_host.sh /home
Step 4 Enter home directory and add execute permission .Run ./prepare_hana_host.sh the script .
[root@hw00001 mnt]# cd /home
[root@hw00001 mnt]# chmod +x *
[root@hw00001 mnt]# ./prepare_hana_host.sh
Remarks: If you run the script , it will install " kernel upgrade, all the required patches,
installing installation packages, OS parameters required for HA configuration".
You can skip chapter 3.5.
----End
3.5 Install system fix package(the script included ,you can

skip this chapter )
CAUTION
If you have run the script, skip operations in this chapter.
3.5.1 Configure YUM source

Step 1 Mount the ISO by using the KVM.
Step 2 Run mkdir -p /mnt/cdrom to create the cdrom directory in /mnt for mounting the ISO file.
[root@HW00001 ~]# mkdir -p /mnt/cdrom
[root@HW00001 ~]#

Step 3 Run mount /dev/sr0 /mnt/cdrom to mount the CD-ROM drive to the /mnt/cdrom directory.
In the command, sr0 indicates a CD-ROM path. Set the path based on actual situations.
[root@HW00001 ~]# mount /dev/sr0 /mnt/cdrom/
mount: block device /dev/sr0 is write-protected, mounting read-only
Step 4 Run vi /etc/yum.repos.d/rhel.repo to edit the rhel.repo file and add HA component
directories to the rhel.repo file.
Add actual HA file paths to the file, like the information in red.
[root@HW00001 yum.repos.d]# vi /etc/yum.repos.d/rhel.repo
[rhel-rpms]
name=Red Hat Enterprise Linux $releasever - $basearch - Source
baseurl=file:///mnt/cdrom
enabled=1
gpgcheck=0
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-redhat-release
----End
3.5.2 Install system fix package

Step 1 Run yum install -y tuned tuned-utils libtool-ltdl ntp to install the system fix package.
Step 2 Download some necessary package from redhat official web ,the package include
resource-agents-sap-hana-3.9.5-54.el7_2.10.x86_64,
tuned-profiles-sap-hana-2.5.1-4.el7_2.3.noarch, tuned-2.5.1-4.el7_2.3.noarch,
tuned-utils-2.5.1-4.el7_2.3.noarch, resource-agents-3.9.5-54.el7_2.10.x86_64 (1),
systemd-libs-219-19.el7_2.9.x86_64, systemd-python-219-19.el7_2.9.x86_64,
systemd-219-19.el7_2.9.x86_64, systemd-sysv-219-19.el7_2.9.x86_64,
libgudev1-219-19.el7_2.9.x86_64, uuid-1.6.2-26.el7.x86_64,
compat-libstdc++-33-3.2.3-72.el7.x86_64, libstdc++-4.8.5-4.el7.x86_64,
libuuid-2.23.2-26.el7.x86_64, uuidd-2.23.2-26.el7.x86_64 ;
Step 3 Copy the downloaded package into the server /home directory by WINSCP tool;
Step 4 Run cd /home to go into the home directory ,the run yum localinstall -y *.rpm to install the
downloaded rpm package;
----End
3.5.3 SAP HANA configuration

Step 1 Configure tuned to use profile "sap-hana" . The tuned profile "sap-hana", which is provided
by RedHat as part of RHEL for SAP HANA 7.2, contains many of the settings mentioned
below.
tuned-adm profile sap-hana
systemctl start tuned
systemctl enable tuned
Step 2 Turn off auto-numa balancing. Run vi /etc/sysctl.d/sap_hana.conf to edit the file, insert
kernel.numa_balancing = 0 into this file.
vi /etc/sysctl.d/sap_hana.conf
kernel.numa_balancing = 0

Step 3 Run sysctl -p /etc/sysctl.d/sap_hana.conf to make it active.

sysctl -p /etc/sysctl.d/sap_hana.conf
Step 4 To disable the usage of transparent hugepages during runtime, set the kernel settings at
runtime with the command ,Run echo never >
/sys/kernel/mm/transparent_hugepage/enabled .
echo never > /sys/kernel/mm/transparent_hugepage/enabled
Step 5 It is nessesary to edit the OS bootloader configuration to make it valid until the next system
start ,Run vi /etc/default/grub to edit this file ,insert the red part to he line starting with
"GRUB_CMDLINE_LINUX".
[root@HW00011 home]# vi /etc/default/grub
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)"
GRUB_DEFAULT=saved
GRUB_DISABLE_SUBMENU=true
GRUB_TERMINAL_OUTPUT="console"
GRUB_CMDLINE_LINUX="crashkernel=auto rhgb quiet transparent_hugepage=never intel_idle.max_cstate=0
processor.max_cstate=0"
GRUB_DISABLE_RECOVERY="true"
Step 6 Then, in case of a non-UEFI configuration, activate the new configuration by issuing the
Command ,Run grub2-mkconfig -o /boot/grub2/grub.cfg .
grub2-mkconfig -o /boot/grub2/grub.cfg
Step 7 Security-Enhanced Linux (SELinux) is an implementation of a mandatory access control

mechanism in the Linux kernel, checking for allowed operations after standard discretionary
access controls are checked. It was created by the National Security Agency and can enforce
rules on files and processes in a Linux system, and on their actions, based on defined policies.
Run vi /etc/sysconfig/selinux , To disable SELinux change the line: SELINUX=enforcing to
SELINUX=disabled.
[root@HW00011 home]# vi /etc/sysconfig/selinux
# This file controls the state of SELinux on the system.

# SELINUX= can take one of these three values:
# enforcing - SELinux security policy is enforced.
# permissive - SELinux prints warnings instead of enforcing.
# disabled - No SELinux policy is loaded.
SELINUX=disabled
# SELINUXTYPE= can take one of three two values:
# targeted - Targeted processes are protected,
# minimum - Modification of targeted policy. Only selected processes are protected.
# mls - Multi Level Security protection.
SELINUXTYPE=targeted
Step 8 Run vi /etc/systemd/logind.conf to edit this file ,insert the following line to the file.
vi /etc/systemd/logind.conf
RemoveIPC=no
Step 9 Run systemctl restart systemd-logind.service to make it active.

systemctl restart systemd-logind.service
Step 10 Run the follow command to create sap hana link.

ln -s /usr/lib64/libldap-2.3.so.0 /usr/lib64/libldap.so.199
ln -s /usr/lib64/liblber-2.3.so.0 /usr/lib64/liblber.so.199
ln -s /usr/lib64/libssl.so.0.9.8e /usr/lib64/libssl.so.0.9.8
ln -s /usr/lib64/libssl.so.1.0.1e /usr/lib64/libssl.so.1.0.1
ln -s /usr/lib64/libcrypto.so.0.9.8e /usr/lib64/libcrypto.so.0.9.8
ln -s /usr/lib64/libcrypto.so.1.0.1e /usr/lib64/libcrypto.so.1.0.1
Step 11 Run vi /etc/sudoers to replacing <sidadm> by the respective user name:

Cmnd_Alias SIDALIAS = /sbin/multipath, /sbin/multipathd, /etc/init.d/multipathd,
/usr/bin/sg_persist, /bin/mount, /bin/umount, /bin/kill, /usr/bin/lsof, /sbin/vgchange,
/sbin/vgscan
Defaults!SIDALIAS !requiretty
<sidadm> ALL=NOPASSWD: SIDALIAS
Step 12 Run vi hdbenv.csh as <SID>adm user , Remove the following line in the file 'hdbenv.csh' in
the home directory of the <SID>adm user:
setenv LD_PRELOAD /opt/rh/SAP/lib64/compat-sap-c++.so
Step 13 Run vi hdbenv.sh as <SID>adm user , Remove the following line in the file 'hdbenv.sh' in the
home directory of the <SID>adm user:
if [[ $RHEL -eq 6 ]]; then
LD_PRELOAD=/opt/rh/SAP/lib64/compat-sap-c++.so
export LD_PRELOAD
fi
----End
3.6 Configuring Network IP Addresses

In the HANA environment, three network segments need to be allocated, and three NICs, each
of which provides two 10GE ports, need to be configured for port binding to achieve an HA
network. The network segment plan is as follows:
 Bond0: 192.168.1.11. This network segment is allocated for cluster intranet and is used
by two 10GE ports on two NICs (P0 on NIC1 and P3 on NIC2) of the RH5885H V3.
 Bond1: 192.168.2.11. This network segment is allocated for NAS file sharing and is used
by two 10GE ports on two NICs (P2 on NIC2 and P5 on NIC3) of the RH5885H V3.
 Bond2: 10.10.1.11. This network segment is allocated for the uplink service network and
is used by two 10GE ports on two NICs (P1 on NIC1 and P4 on NIC3) of the RH5885H
V3.

Figure 3-54 Port binding
Configuration on the CLI
This section uses port bond2 (physical ports eth4 and eth5) as an example to describe how to configure
network IP addresses.
Step 1 Run nmcli con add type bond ifname bond0 mode balance-xor to create bond0 .
Step 2 Run nmcli connection modify bond-bond0 ipv4.addresses 192.168.1.11/24 to set an IP
address for bond0.
Step 3 Run nmcli connection modify bond-bond0 ipv4.method manual .
Step 4 Run nmcli con add type bond-slave ifname ens1f0 master bond-bond0 to add a slave
ethernet port. The ‘ens1f0’ vary according to the customer's environment.
Step 5 Run nmcli con add type bond-slave ifname ens2f1 master bond-bond0 to add a slave
ethernet port. The ‘ens2f1’ vary according to the customer's environment:
Step 6 Run nmcli connection show command to check the information like this:.
bond-slave-ens1f0 1c88d785-b280-4999-96d5-237d4e761e43 802-3-ethernet ens1f0

bond-slave-ens2f1 e6845549-b897-4cb8-9487-9004c71e3741 802-3-ethernet ens2f1
bond-bond0 5a3cb631-be4c-44d5-ae9a-95b01d6a6c03 bond bond0
Step 7 Repeat step1~step6 to create bond1 and bond2:

Step 8 In the /etc/sysconfig/ directory, create the default uplink service route.
[root@ hw00001 sysconfig] # vi network
Step 9 Add the following gateway information to network:
default 10.10.1.254
Step 10 Restart the network.

[root@ hw00001 sysconfig] # /etc/init.d/network restart
Step 11 Repeat the preceding steps to configure other nodes.

----End

3.7 Configuring the SSH Interconnection Service

The Secure Shell (SSH) interconnection service needs to be configured for SAP HANA
cluster servers. Run the following commands on nodes hw00001 to hw00008 on the CLI:
ssh-keygen -t rsa
ssh-keygen -t dsa
ssh HW00001 "echo $(cat /root/.ssh/id_dsa.pub) >>/root/.ssh/authorized_keys"

……
ssh HW00001 "echo $(cat /root/.ssh/id_rsa.pub) >>/root/.ssh/authorized_keys"

……
3.8 Configuring the NFS Service

Step 1 Run the following command to check the setting of the shared path of a NAS server.
Information similar to the following is displayed:
[root@HW00001 ~]# showmount -e 192.168.2.19
Export List for 192.168.2.19
FileSystem_Shared *
Step 2 Create a shared file system on the NAS server.

[root@HW00001 ~]# mkdir -p /hana/shared/
Step 3 Mount the NFS service.
[root@HW00001 ~]# mount -t nfs -o

vers=3,intr,nolock,rsize=1048576,wsize=1048576,timeo=10
192.168.2.19:/FileSystem_shared /hana/shared/
According to the NFS network plan, the IP addresses of the NAS file shared networks can be
192.168.2.19 and 192.168.2.20. Therefore, HANA cluster nodes can be evenly mounted. For example,
nodes 1 to 4 are mounted to 192.168.2.19, and nodes 5 to 8 are mounted to 192.168.2.20.
Step 4 Run the following command to check the mounting status:

[root@hw00001]# mount

192.168.2.19:/FileSystem_Shared on /hana/shared type nfs
(rw,intr,nolock,rsize=1024,wsize=1024,timeo=10,addr=192.168.2.19)
Step 5 Run the following command to check the space usage:

[root@hw00001]# df

Filesystem 1K-blocks Used Available Use% Mounted on
/dev/sda4 502496584 7969556 469001680 2% /

udev 529332048 396 529331652 1% /dev

tmpfs 529332048 72 529331976 1% /dev/shm
/dev/sda2 1036108 93036 890440 10% /boot
/dev/sda3 51605116 289792 48693936 1% /usr/sap
192.168.2.19:/HANA_share 3355443200 14430208 3341012992 1% /hana/shared
Step 6 The NFS service is automatically mounted after the server restarts.
It takes a period of time to establish communication between network services and a NAS
server after network services are started up. The NFS service cannot be successfully mounted
before the communication is established. To enable the NFS service to be automatically
mounted after the network communication is established and before the sapinit service is
started, add the following information to the /etc/fstab script needs to be added.
[root@HW00002 network-scripts]# cat /etc/fstab
#
# /etc/fstab
# Created by anaconda on Thu Aug 25 02:38:11 2016
#
# Accessible filesystems, by reference, are maintained under '/dev/disk'
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info
#
UUID=ac27e19c-4437-4012-b280-50f7a928bbeb / ext4 defaults 11
UUID=8b80a44a-43bd-43af-83a5-93a2f36d1499 /boot ext4 defaults 12
UUID=ef1beb53-19aa-4023-ab1e-b41186b5cff9 /usr/sap ext4 defaults 12
UUID=c6d3f38f-0d43-4327-a1ac-b9ec51c0c55c swap swap defaults 00
192.168.2.19:/ FileSystem_share /hana/shared/ nfs intr,nolock,nfsvers=3,timeo=10,rsize=1048576,wsize=1048576,_netdev
00
Step 7 Perform the preceding configurations on other nodes.

----End
3.9 Configuring grub Parameters

Step 1 Log in to the OS as user root.
Step 2 Run the vi /etc/default/grub command.
The information similar to that in Figure 3-55 is displayed.

Figure 3-55 Running the vi /etc/default/grub command
Step 3 On line GRUB_CMDLINE_LINUX_DEFAULT ,add three parameter before showopts; as

intel_idle.max_cstate=0 processor.max_cstate=0 nohz=off
Step 4 On the CLI shown in Figure 3-57, press Esc, run :wq, and press Enter to save the
information.
Figure 3-57 Editing the file

Step 5 Run the grub2-mkconfig -o /boot/grub2/grub.cfg command, to generating grub

configuration file,as shown in Figure 3-58.
Figure 3-58 generating grub configuration file
----End
3.10 Configuring the DM Multipath Service

Step 1 Configure the DM service to start upon OS startup.
[root@hw00001]# systemctl enable multipathd
[root@hw00001]# systemctl list-unit-files multipathd.service
multipathd 0:off 1:off 2:off 3:on 4:off 5:on 6:off
Step 2 Configure a multipath.conf file in /etc.

The file needs to be manually created after installation. You can copy a template from the
following path in the SUSE OS to create a multipath.conf file.
[root@hw00001]# cp /usr/share/doc/packages/multipath-tools/multipath.conf.synthetic
/etc/multipath.conf
Step 3 Edit the multipath.conf file as follows: Write 5500 V3 disk array information to the file
without modifying other statements.
The World Wide Identifiers (WWIDs) of data_n and log_n are determined by the scanned LUNs in Step
7 in 2.2
combining with the LUN IDs generated in 2.4 Step 9 in 2.4 Storage Space Configuration.
[root@hw00001]# vi /etc/multipath.conf
------------------------------------------------------------------
devices {
device {
vendor "HUAWEI"
product "XSG1"
path_grouping_policy group_by_prio
getuid_callout "/lib/udev/scsi_id --whitelisted --device=/dev/%n"
prio alua
path_checker tur
path_selector "round-robin 0"
failback immediate
rr_min_io 1
}
}

Step 4 Restart the DM service.

[root@hw00001]# service multipathd restart
Shutting down multipathd
done
Starting multipathd
Step 5 Search for devices.

[root@hw00001]# rescan-scsi-bus.sh
/usr/bin/rescan-scsi-bus.sh: line 647: [: 1.11: integer expression expected ]
Host adapter 0 (megaraid_sas) found.
Host adapter 1 (ahci) found.
Host adapter 7 (qla2xxx) found.
Host adapter 8 (qla2xxx) found.
….
Step 6 Load LUNs.

[root@hw00001]# multipath -F
[root@hw00001]# multipath -v2
[root@hw00001]# multipath -ll
Step 7 Query the LUN WWIDs.

Run the following commands to query the WWIDs of corresponding mappers:
[root@hw00001]# ll /dev/mapper
[root@hw00001]# ll /dev/disk/by-id/
Step 8 Update WWIDs in the multipath.conf file. And sda WWID into blacklist in the
multipath.conf.
Update the multipath.conf file based on the scanned LUN WWIDs in Step 7 in 3.9
Configuring grub Parameters
Step 9 Log in to the OS as user root.
Step 10 Run the vi /etc/default/grub command.
The information similar to that in Figure 3-55 is displayed.

Step 11 On line GRUB_CMDLINE_LINUX_DEFAULT ,add three parameter before showopts; as

intel_idle.max_cstate=0 processor.max_cstate=0 nohz=off
Step 12 On the CLI shown in Figure 3-57, press Esc, run :wq, and press Enter to save the
information.
Figure 3-61 Editing the file

Step 13 Run the grub2-mkconfig -o /boot/grub2/grub.cfg command, to generating grub

configuration file,as shown in Figure 3-58.
Figure 3-62 generating grub configuration file
----End
combining with the LUN IDs generated in 2.4 Step 9 in 2.4 Storage Space Configuration.
------------------------------------------------------------------
devices {
device {
vendor "HUAWEI"
product " XSG1"
getuid_callout "/lib/udev/scsi_id --whitelisted --device=/dev/%n"
prio alua
path_checker tur
failback immediate
rr_min_io 1
}
}
multipaths {
multipath {
wwid 36fce33c100a68ff30003a50400000001
alias data_1
}
multipath {
wwid 36fce33c100a68ff30003b4b800000002
alias data_2
}
multipath {
wwid 36fce33c100a68ff30003c18900000003
alias data_3
}
multipath {
wwid 36fce33c100ad38740006401800000000
alias data_4
}
multipath {
wwid 36fce33c100ad387400064c5900000001
alias data_5
}
multipath {
wwid 36fce33c100ad38740006526100000002

alias data_6
}
multipath {
wwid 36fce33c100ad387400065c5600000003
alias data_7
}
multipath {
wwid 36fce33c100a68ff30003d9fb00000004
alias log_1
}
multipath {
wwid 36fce33c100a68ff30003daab00000005
alias log_2
}
multipath {
wwid 36fce33c100a68ff30003db6300000006
alias log_3
}
multipath {
wwid 36fce33c100ad38740006e76f00000004
alias log_4
}
multipath {
wwid 36fce33c100ad38740006e7c300000005
alias log_5
}
multipath {
wwid 36fce33c100ad38740006e86e00000006
alias log_6
}
multipath {
wwid 36fce33c100ad38740006e92000000007
alias log_7
}
}
blacklist {
wwid "360030130f090000001e3c3997c3c794a"
}
------------------------------------------------------------------
Step 14 Add the OS disk wwid to multipath blacklist,run ll /dev/disk/by-id/ |grep sda to get sda wwid
like this:
[root@hw00001]# ll /dev/disk/by-id/ |grep "sda"
lrwxrwxrwx 1 root root 9 Sep 18 15:23 scsi-36101b5442bcc70001f4ed57112e0c501 -> ../../sda
Step 15 Update blacklist wwids in the multipath.conf file. Add red font into the multipath.conf as
flowing information:
devices {
device {

vendor "HUAWEI"
product " XSG1"
prio alua
path_checker tur
failback immediate
rr_min_io 1
}
}
blacklist {
wwid 36101b5442bcc70001f4ed57112e0c501
}
multipaths {
multipath {
wwid 36fce33c100ad387406524b5200000004
alias data_1
}
multipath {
wwid 36fce33c100ad387406524f2200000005
alias data_2
}
multipath {
wwid 36fce33c100ad387406525f4000000006
alias data_3
}
multipath {
wwid 36fce33c100a68ff30007e22f00000000
alias data_4
}
multipath {
wwid 36fce33c100a68ff30007e5a400000001
alias data_5
}
multipath {
wwid 36fce33c100a68ff30007e97a00000002
alias data_6
}
multipath {
wwid 36fce33c100a68ff3000804be00000003
alias data_7
}
multipath {
wwid 36fce33c100ad38740651c1ea00000001
alias log_1
}
multipath {
wwid 36fce33c100ad38740651e32a00000002
alias log_2
}
multipath {
wwid 36fce33c100ad38740651f7bf00000003
alias log_3
}
multipath {

wwid 36fce33c100a68ff3000807ee00000004
alias log_4
}
multipath {
wwid 36fce33c100a68ff300080b2500000005
alias log_5
}
multipath {
wwid 36fce33c100a68ff300080db400000006
alias log_6
}
multipath {
wwid 36fce33c100a68ff3000810a000000007
alias log_7
}
}
Step 16 Reload the multipathd service.

[root@hw00001]# service multipathd reload
Step 17 Log in to the OS as user root in other nodes,and repeat step1~step11 to complete DM
multipath service configuration .
Step 18 Create XFS file systems for DM devices on one node.
Run the ll /dev/disks/by-id/ command to find out DM devices corresponding to the preceding
LUNs. For example, if the DM devices are dm-0, dm-1, dm-2, dm-3…, dm-13, run the
following commands:
mkfs.xfs -f -d agcount=60 /dev/dm-0
----End

Guide (RH5885H&RH8100 V3+5500 V3+Redhat7.2) 4 Switch Configuration
4 Switch Configuration
The standard switches of the RH5885H V3+5500 V3 SAP HANA cluster are Huawei S6700
series switches. The entire cluster supports HANA internal communication and provides NAS
and upper-layer service ports using the 10GE Ethernet network. Two CE6800 switches need
to be stacked to form an HA network, as shown in Figure 4-1.
Figure 4-1 RH5885H V3+5500 V3 network
4.1 CE6800 Switch Stacking

Step 1 Configure a stack port on each CE6800 switch. Generally, the port with the largest port
number is used as the stack port. For a four-node HANA solution, you are advised to
configure four stack ports.
Step 2 Configure the stacking of two CE6800 switches. For details, see CE6800 User Guide.
----End

4.2 SNS2124 FC Switch Zone Configuration

The SNS2124 FC switch is used to prevent other storage from accessing the HANA cluster
storage network temporarily or for a long time. You are advised to configure zones for each
HANA node and storage.
Configure zones based on the minimum zone principle. See Table 4-1.
Table 4-1 Zone configuration
FC Switch Zone Name Zone Member
SNS2124_01 RH01_FC1_TO_A_H0 "10,0;10,6"

RH01_FC1_TO_A_H3 "10,1;10,6"
RH01_FC1_TO_B_H0 "10,2;10,6"
RH01_FC1_TO_B_H3 "10,3;10,6"
RH02_FC1_TO_A_H0 "10,0;10,7"
RH02_FC1_TO_A_H3 "10,1;10,7"
RH02_FC1_TO_B_H0 "10,2;10,7"
RH02_FC1_TO_B_H3 "10,3;10,7"
RH03_FC1_TO_A_H0 "10,0;10,8"
RH03_FC1_TO_A_H3 "10,1;10,8"
RH03_FC1_TO_B_H0 "10,2;10,8"
RH03_FC1_TO_B_H3 "10,3;10,8"
RH04_FC1_TO_A_H0 "10,0;10,9"
RH04_FC1_TO_A_H3 "10,1;10,9"
RH04_FC1_TO_B_H0 "10,2;10,9"
RH04_FC1_TO_B_H3 "10,3;10,9"
RH05_FC1_TO_A_H0 "10,0;10,10"
RH05_FC1_TO_A_H3 "10,1;10,10"
RH05_FC1_TO_B_H0 "10,2;10,10"
RH05_FC1_TO_B_H3 "10,3;10,10"
SNS2124_01 RH01_FC2_TO_A_H1 "20,0;20,6"
RH01_FC2_TO_A_H4 "20,1;20,6"
RH01_FC2_TO_B_H1 "20,2;20,6"
RH01_FC2_TO_B_H4 "20,3;20,6"
RH02_FC2_TO_A_H1 "20,0;20,7"

FC Switch Zone Name Zone Member
RH02_FC2_TO_A_H4 "20,1;20,7"
RH02_FC2_TO_B_H1 "20,2;20,7"
RH02_FC2_TO_B_H4 "20,3;20,7"
RH03_FC2_TO_A_H1 "20,0;20,8"
RH03_FC2_TO_A_H4 "20,1;20,8"
RH03_FC2_TO_B_H1 "20,2;20,8"
RH03_FC2_TO_B_H4 "20,3;20,8"
RH04_FC2_TO_A_H1 "20,0;20,9"
RH04_FC2_TO_A_H4 "20,1;20,9"
RH04_FC2_TO_B_H1 "20,2;20,9"
RH04_FC2_TO_B_H4 "20,3;20,9"
RH05_FC2_TO_A_H1 "20,0;20,10"
RH05_FC2_TO_A_H4 "20,1;20,10"
RH05_FC2_TO_B_H1 "20,2;20,10"
RH05_FC2_TO_B_H4 "20,3;20,10"
For details about the zone configuration commands of the SNS2124 FC switch, see SNS2124
Switch User Guide.

Guide (RH5885H&RH8100 V3+5500 V3+Redhat7.2) 5 Basic Service Configuration
5 Basic Service Configuration
Before installing a SAP HANA database, configure required basic services for the HANA
nodes to ensure that the SAP HANA database can be successfully installed. In the operating
environment of the RH5885H V3+5500 V3 SAP HANA, RH5885 servers are used as NTP
server and DNSs. If NTP and DNSs already exist on the live network, use the live network
environment directly. Configuration file parameters on the server need to be modified as
required.
5.1 Configuring the NTP Service

5.1.1 Configurations on the Server
Independent NTP Server
You are advised to configure an NTP server independent from the cluster, used for time synchronization
between each server and storage.
Step 1 Determine the NTP server, for example, the RH2288 whose IP address is 192.168.34.8 and
host name is WIN-EJMB5JAMNVN.
Step 2 Configure the NTP server configuration file. For details, see A ntp.conf.
Note that the configuration parameters need to be modified based on the IP address of the live
network.
Step 3 Enable the NTP service on the server.
chkconfig ntpd on
Step 4 Add the host name of the NTP server to the hosts file in /etc of each node.
192.168.34.8 WIN-EJMB5JAMNVN WIN-EJMB5JAMNVN
----End

No Independent NTP Server
You are advised to configure an NTP server independent from the cluster, used for time synchronization
between each server and storage. If there is no independent NTP server, you can use a node (standby
node is recommended) in the cluster as the NTP server. If the node is faulty and cannot synchronize with
other nodes, the running of the cluster database will be affected.
The IP address of the NTP server (standby node, using the internal network of the HANA
cluster database) is 192.168.1.18.
Perform the following steps on the standby node:
Step 1 Configure the NTP service to start upon OS startup.
[root@hw00008 ~]# chkconfig ntpd on
Step 2 Configure the configuration file on the NTP server to allow the NTP clients of specified IP
addresses to automatically synchronize time with the NTP server.
[root@hw00008 ~]# vi /etc/ntp.conf
----------------------------------------------------------------------------------
……
##
## Miscellaneous stuff
##
restrict 192.168.1.11 255.255.255.0 nomodify
…
……
----------------------------------------------------------------------------------
Step 3 Restart the NTP service.

[root@hw00008 ~]# systemctl restart ntpd.service
Step 4 View the NTP configuration information.
ntpq –p
----End
5.1.2 Configuring the NTP Client

To implement NTP server time synchronization, the NTP client must be configured for the
two HANA servers in the HA cluster.
Step 1 Log in to a server node as the root user and run the following command to configure the NTP
service to start with the startup of Redhat Linux:

systemctl enable ntpd.service
Step 2 Run "systemctl enable ntpdate.service" to start ntpdate service:

systemctl enable ntpdate.service
Step 3 Run the vi /etc/ntp.conf command to open the NTP configuration file ntp.conf.
#vi /etc/ntp.conf
Step 4 Press i to switch to the insertion mode.

Step 5 Insert server <NTP server IP address>. This procedure uses 192.168.20.9 as an example, and
you need to change the IP address to the actual NTP server IP address.
server 192.168.20.9
Step 6 Press ESC to switch to the CLI mode.
Step 7 Press the colon (:) to switch to the bottom line mode, type wq, and press Enter to save the
modification and exit the vi editor.
The following is an example of the configured ntp.conf file:
HW00001:/hana/shared # vi /etc/ntp.conf
# Clients from this (example!) subnet have unlimited access, but only if
# cryptographically authenticated.
#restrict 192.168.123.0 mask 255.255.255.0 notrust
##
##
driftfile /var/lib/ntp/drift/ntp.drift # path for drift file
logfile /var/log/ntp # alternate log file
# logconfig =syncstatus + sysevents
# logconfig =all
# statsdir /tmp/ # directory for statistics files
# filegen peerstats file peerstats type day enable
# filegen loopstats file loopstats type day enable
# filegen clockstats file clockstats type day enable
#
# Authentication stuff
#
keys /etc/ntp.keys # path for keys file
trustedkey 1 # define trusted keys
requestkey 1 # key (7) for accessing server variables
# controlkey 15 # key (6) for accessing server variables
restrict 127.0.0.1
restrict -6 ::1
server 192.168.20.9
Step 8 Run the systemctl restart ntpd.service command to restart the NTP service.
systemctl restart ntpd.service
Step 9 Run the ntpq -p command to check the NTP running status.
#ntpq -p
Example:
HW00001: # ntpq -p

remote refid st t when poll reach delay offset jitter

==============================================================================
*192.168.20.9 LOCAL(0) 11 u 53 64 7 0.141 0.968 0.296
Main parameters in the command output are described as follows:

 remote: indicates the name of the NTP server that responds to the request.
 when: indicates the number of seconds since the last successful request.
 poll: indicates the interval (in seconds) for the local host to synchronize time with the
remote server.
 offset: indicates the time offset (in milliseconds) between the local host and the time
source.
Step 10 Log in to the other HANA node and repeat the preceding steps to configure the NTP server.
----End
5.2 Configuring the DNS Service

5.2.1 Configurations on the Server (for Linux)
Step 1 Determine the DNS, for example, the server whose IP address is 192.168.34.8.
Step 2 Install the DNS package.
DNSServer:/home/ # rpm -ivh bind-chrootenv-9.6ESVR5P1-0.8.1.x86_64.rpm

DNSServer:/home/ # rpm -ivh bind-9.6ESVR5P1-0.8.1.x86_64.rpm
Step 3 Check whether the installation is successful.
Step 4 In the /var/lib/named directory, create the site.zone and 192.168.255.zone files.

The HANA cluster can be connected to the DNS through an uplink service port or a service management
port (recommended).
In this document, the host names of cluster service management ports range from HW00001MG to
HW00008MG, and corresponding IP addresses range from 192.168.34.61 to 192.168.34.68.
Step 5 Modify the named.conf file in /etc/.

----End
5.2.2 Configurations on the DNS Client

Step 1 Add the DNS IP address to HANA node configuration.
[root@hw00001]# vi /etc/resolv.conf
search site
nameserver 192.168.34.8
Step 2 Add the following information (IP addresses and host names of all HANA nodes and the DNS)
to the hosts file in /etc:
192.168.34.8 WIN-EJMB5JAMNVN WIN-EJMB5JAMNVN
192.168.1.11 NODE01 NODE01

192.168.2.11 HANA01 HANA01
10.10.1.11 HW00001 HW00001
192.168.34.61 HW00001MG HW00001MG
192.168.1.12 NODE02 NODE02

192.168.2.12 HANA02 HANA02
10.10.1.12 HW00002 HW00002
192.168.34.62 HW00002MG HW00002MG
192.168.1.13 NODE03 NODE03

192.168.2.13 HANA03 HANA03
10.10.1.13 HW00003 HW00003
192.168.34.63 HW00003MG HW00003MG
192.168.1.14 NODE04 NODE04

192.168.2.14 HANA04 HANA04
10.10.1.14 HW00004 HW00004
192.168.34.64 HW00004MG HW00004MG

192.168.1.15 NODE05 NODE05

192.168.2.15 HANA05 HANA05
10.10.1.15 HW00005 HW00005
192.168.34.65 HW00005MG HW00005MG
192.168.1.16 NODE06 NODE06

192.168.2.16 HANA06 HANA06
10.10.1.16 HW00006 HW00006
192.168.34.66 HW00006MG HW00006MG
192.168.1.17 NODE07 NODE07

192.168.2.17 HANA07 HANA07
10.10.1.17 HW00007 HW00007
192.168.34.67 HW00007MG HW00007MG
192.168.1.18 NODE08 NODE08

192.168.2.18 HANA08 HANA08
10.10.1.18 HW00008 HW00008
192.168.34.68 HW00008MG HW00008MG
----End

Guide (RH5885H&RH8100 V3+5500 V3+Redhat7.2) 6 Performance Optimization
6 Performance Optimization
6.1 Configuring THP

Step 1 Run the following commands to disable the memory Transparent Huge Pages (THP) function:
echo never > /sys/kernel/mm/transparent_hugepage/defrag
Step 2 To make the configuration take effect automatically upon system startup, add the following
commands to the boot.local file in /etc/init.d.
[root@hw00001]# cat /etc/init.d/boot.local
#! /bin/sh
#
# Copyright (c) 2002 SuSE Linux AG Nuernberg, Germany. All rights reserved.
#
# Author: Werner Fink <werner@suse.de>, 1996
# Burchard Steinbild, 1996
#
# /etc/init.d/boot.local
#
# script with local commands to be executed from init on system startup
#
# Here you should add things, that should happen directly after booting
# before we're going to the first run level.
#
echo never > /sys/kernel/mm/transparent_hugepage/defrag
Step 3 After the system is started, run the following commands to check whether THP is disabled.
[root@hw00001]# cat /sys/kernel/mm/transparent_hugepage/enabled
always madvise [never]
[root@hw00001]# cat /sys/kernel/mm/transparent_hugepage/defrag
always madvise [never]
In the preinstalled environment, RH5885H V3/RH8100 V3hardware uses the default configuration. You
need to run only the xxxx/enabled commands.
----End

6.2 Configuring the UUID Service

If the sapconf package is configured, the UUID service is activated automatically. Configure
the UUID service by performing the following steps:
Step 1 Add the following command at the end of the permissions.local file in /etc.
/usr/sbin/uuidd uuidd:uuidd 6755
Step 2 Configure the permission of the UUID service.

chkstat --set /etc/permissions.local
Step 3 Enable the UUID service.

insserv uuidd
/etc/init.d/uuidd start
----End
6.3 Configuring Process Resource Restriction

During the running of some programs, such as the SAP J2EE engine and Oracle RDBMS
software, a large number of file handles need to be opened simultaneously. If the number of
opened file handles is limited, the program performance may be affected. By default, the
number of opened file handles is limited to 1024. For HANA data applications, you need to
change the value by adding the following commands to the /etc/security/limits.conf file:
@root soft nofile 32768
@root hard nofile 32768
@anaadm soft nofile 1024768
@anaadm hard nofile 1024768
@sapsys soft nofile 32800
@sapsys hard nofile 32800
@sdba soft nofile 32800
@sdba hard nofile 32800
@dba soft nofile 32800
@dba hard nofile 32800
Replace ana with the actual database ID.
6.4 Optimizing Sysctrl.conf Parameters

Step 1 In /etc/sysctl.conf on each HANA node, add the following commands:
kernel.sem = 1250 256000 100 8192
kernel.shmmax = 137438953472
kernel.shmall = 714773160
kernel.shmmni = 524288
fs.file-max = 20000000
fs.aio-max-nr = 131072
vm.max_map_count = 203000000
vm.memory_failure_early_kill = 1
sysctl -p /etc/sysctl.conf

Step 2 On the CLI, run the following command to make the configuration take effect:
sysctl -p
----End
6.5 Optimizing Network Performance

Step 1 In /etc/sysctl.conf, add the following commands:
net.ipv4.tcp_no_metrics_save = 1
net.ipv4.tcp_sack = 1
net.ipv4.tcp_timestamps = 0
net.ipv4.tcp_fin_timeout = 15
net.ipv4.tcp_window_scaling = 1
net.ipv4.ip_forward = 0
net.ipv4.conf.default.rp_filter = 0
net.ipv4.conf.default.accept_source_route = 0
net.ipv4.tcp_syncookies = 1
net.ipv4.tcp_slow_start_after_idle = 0
net.ipv4.conf.all.rp_filter = 0
net.ipv4.neigh.default.gc_thresh1 = 256
net.ipv4.ip_local_port_range = 40000 61000
net.ipv4.tcp_mem = 9830400 9830400 16777216

net.ipv4.tcp_rmem = 9830400 9830400 16777216
net.ipv4.tcp_wmem = 9830400 9830400 16777216
net.core.wmem_max = 16777216
net.core.rmem_max = 16777216
net.core.optmem_max = 16777216
net.core.wmem_default = 16777216
net.core.rmem_default = 16777216
net.core.netdev_max_backlog = 500000
net.core.rps_sock_flow_entries = 4194304
net.ipv4.tcp_timestamps = 0
net.ipv4.tcp_fin_timeout = 15
net.ipv4.tcp_sack = 0
net.ipv4.tcp_tso_win_divisor = 32
net.ipv4.conf.all.promote_secondaries = 0
net.ipv4.conf.default.promote_secondaries = 0
net.ipv4.conf.lo.rp_filter = 1
net.ipv4.conf.lo.accept_source_route = 0
net.ipv4.conf.bond0.rp_filter = 1
net.ipv4.conf.bond0.accept_source_route = 0
net.ipv4.conf.bond0.promote_secondaries = 0
Step 2 Run the following command to make the configuration take effect:

sysctl –p
Step 3 For port bond0 in the cluster (for example, consisting of physical ports eth6 and eth9), add the
following commands to /etc/rc.d/boot.local to make the configuration take effect
automatically:
ethtool -C eth6 rx-usecs 25
ethtool -C eth9 rx-usecs 25
ethtool -G eth6 rx 4096 tx 4096
ethtool -G eth9 rx 4096 tx 4096
service irqbalance stop
----End
6.6 Optimizing Storage Performance

6.6.1 Optimization on the Storage
Step 1 Log in to the 5500 V3 CLI and switch to an advanced user to obtain corresponding rights:
change user_mode current_mode user_mode=developer
Step 2 Run the following command to optimize storage performance:
developer:/>change cpu frequency enabled=no

developer:/change dif_verify_level general mid=all level=invalid
----End
6.6.2 Optimization on the Server

Step 1 Run the following commands to change the scheduling algorithms of log and data block
devices to noop:
HW00001: for sd in `ls -lha /dev/disk/by-id/scsi-data_* | awk -F '/' '{print $NF}'`;
do echo noop > /sys/block/$sd/queue/scheduler; done
HW00001: for sd in `ls -lha /dev/disk/by-id/scsi-log_* | awk -F '/' '{print $NF}'`; do
echo noop > /sys/block/$sd/queue/scheduler; done
Step 2 Add the following commands to /etc/init.d/mountinit created in 3.9 to make the
configuration take effect upon startup:
for sd in `ls -lha /dev/disk/by-id/scsi-data_* | awk -F '/' '{print $NF}'`; do echo noop >
/sys/block/$sd/queue/scheduler; done
for sd in `ls -lha /dev/disk/by-id/scsi-log_* | awk -F '/' '{print $NF}'`; do echo noop >
/sys/block/$sd/queue/scheduler; done
----End

Guide (RH5885H&RH8100 V3+5500 V3+Redhat7.2) 7 SAP HANA Database Installation
7 SAP HANA Database Installation
7.1 Preparing for the Installation

7.1.1 Configuring sudoers
Add the following information in /etc/sudoers in every node.Use the database SID (for
example anaadm) to replace <sidadm>:
Cmnd_Alias SIDALIAS = /sbin/multipath, /sbin/multipathd, /usr/bin/sg_persist, /bin/mount,
/bin/umount, /bin/kill, /usr/sbin/lsof, /sbin/vgchange, /sbin/vgscan
Defaults!SIDALIAS !requiretty
<sidadm> ALL=NOPASSWD: SIDALIAS
7.1.2 Obtaining HANA Software Packages

Download required HANA software packages according to Table 1-2 or obtain them from the
customer.
Run the following command to decompresses the IMDB package:
./SAPCAR_617-80000935_Linux_64bit.EXE -manifest SIGNATURE.SMF -xvf
IMDB_SERVER100_122_5-10009569.SAR
This document uses SAP HANA SP12 (1.00.122.05.1481577062) as an example to describe SAP HANA
database installation.
7.1.3 Installing the SAP Host Agent (Optional)

In the SAP Host Agent installation path, run the ./saphostexec –install command.
The installation mode of the latest SAP Host Agent software has been updated. After decompression, run
the RPM package installation command to install the SAP Host Agent.
For the HANA database of the latest version, install the SAP Host Agent by setting database installation
command parameters.
7.1.4 Configuring global.ini

Copy the global.ini file to the /hana/shared/ directory and modify Storage HA
configuration, Persistence configuration and Communication in the file.

 Storage HA configuration:
partition_1_data__wwid indicates the WWID (starting with 3) of Data_01,
partition_1_log__wwid indicates the WWID (starting with 3) of Log_01, and other
parameters follow the same rule.partition_*_data__mountoptions and
partition_*_log__mountoptions are mount parameters.
###########################################################################
# Storage HA configuration
############################################################################ .short
_desc
# name of python HA provider script
[storage]
ha_provider = hdb_ha.fcClient
# ha_provider_path = /hana/shared/
# these parameters name the WWIDs of the devices for each partition/usage_type combination
# if you have more nodes, add your LUNs here.
# for proper usage, replace the '...' with specified WWID in your system.
partition_*_*__prType = 5
partition_1_data__wwid = data_1
partition_1_log__wwid = log_1
…
…
#Set mount parameters.
partition_*_data__mountoptions = -o noatime,nodiratime
partition_*_log__mountoptions = -o noatime,nodiratime
 Persistence configuration:
Change the red part in the following to the actual database SID, for example, ANA.
###########################################################################
# Persistence configuration
###########################################################################
[persistence]
basepath_datavolumes=/hana/data/ANA/
basepath_logvolumes=/hana/log/ANA/
basepath_shared=yes
 Communication:
Change the red part in the following to the actual internal network IP addresses and host
names.
###########################################################################
# Communication
###########################################################################
[communication]

listeninterface = .global
[internal_hostname_resolution]
192.168.1.11 = NODE01
192.168.1.12 = NODE02
192.168.1.13 = NODE03
…
192.168.1.18 = NODE08
For detailed configuration, see B global.ini.
7.1.5 Creating HANA Installation Paths

Run the following commands on each node to create a persistent database installation path.
Replace ANA with the actual database SID.
[root@hw00001]# mkdir -p /hana/data/ANA /hana/log/ANA
[root@hw00001]# chmod o+w /hana/data/ANA /hana/log/ANA
HW00002:~ # mkdir -p /hana/data/ANA /hana/log/ANA

HW00002:~ # chmod o+w /hana/data/ANA /hana/log/ANA

…
…
7.2 Installing a SAP HANA Database

You can install a SAP HANA database by using either of the following methods:
 One-click distributed installation: Run the distributed installation command on the
master node to install a database on the entire cluster.
 Installation on nodes one by one: Perform installation on the master node first, and then
slave nodes, and standby nodes last.
7.2.1 One-Click Installation on the Master Node
This section uses SAP HANA SP10_100.0 as an example to describe how to install a database on the
master node.
Run the cd command to switch to the directory where the SAP HANA database file is saved.
The following command output is an example (the detailed password and parameters vary
according to the actual situation):
HW00001: /hana/shared/51049354/DATA_UNITS/HDB_LCM_LINUX_X86_64/ # ./hdblcm
--action=install --sid=ANA --number=00 --sapmnt=/hana/shared/
--storage_cfg=/hana/shared/ --root_user=root --autostart=on --restrict_max_mem=off
--max_mem=0 --logpath=/hana/log/ANA --nostart=off --datapath=/hana/data/ANA
--shell=/bin/sh --hostname=NODE01 --remote_execution=ssh --install_hostagent=on
--db_mode=singledb --install_ssh_key=on

--addhosts=NODE02:role=worker:group=default:storage_partition=2,NODE03:role=worker:
group=default:storage_partition=3,NODE04:role=worker:group=default:storage_partitio
n=4,NODE05:role=worker:group=default:storage_partition=5,NODE06:role=worker:group=d
efault:storage_partition=6,NODE07:role=worker:group=default:storage_partition=7,NOD
E08:role=standby:group=default --password=Huawei123 --system_user_password=Huawei123
--root_password=Huawei123 --internal_network=192.168.1.0/24
The installation procedure is similar to the following (parameter options are specified by the
customer):
SAP HANA Lifecycle Management - SAP HANA 1.00.122.05.1481577062
***************************************************************
Scanning Software Locations...

Detected components:
SAP HANA Database (1.00.122.05.1481577062) in
/hana/shared/51049932_SP10_100/DATA_UNITS/HDB_SERVER_LINUX_X86_64/server
SAP HANA AFL (Misc) (1.00.122.05.1481577062) in
/hana/shared/51049932_SP10_100/DATA_UNITS/HDB_AFL_LINUX_X86_64/packages
SAP HANA LCAPPS (1.00.122.05.1481577062) in
/hana/shared/51049932_SP10_100/DATA_UNITS/HANA_LCAPPS_10_LINUX_X86_64/packages
SAP TRD AFL FOR HANA (1.00.122.05.1481577062) in
/hana/shared/51049932_SP10_100/DATA_UNITS/HDB_TRD_AFL_LINUX_X86_64/packages
SAP HANA Database Client (1.00.122.05.1481577062) in
/hana/shared/51049932_SP10_100/DATA_UNITS/HDB_CLIENT_LINUX_X86_64/client
SAP HANA Studio (2.1.4.000000) in
/hana/shared/51049932_SP10_100/DATA_UNITS/HDB_STUDIO_LINUX_X86_64/studio
SAP HANA Smart Data Access (1.00.4.004.0) in
/hana/shared/51049932_SP10_100/DATA_UNITS/SAP_HANA_SDA_10/packages
SAP HANA Database version '1.00.122.05.1481577062' 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.122.05.1481577062
4 | afl | Install SAP HANA AFL (Misc) version 1.00.122.05.1481577062
5 | lcapps | Install SAP HANA LCAPPS version 1.00.122.05.1481577062
6 | smartda | Install SAP HANA Smart Data Access version 1.00.4.004.0
7 | studio | Install SAP HANA Studio version 2.1.4.000000
8 | trd | Install SAP TRD AFL FOR HANA version 1.00.122.05.1481577062
Enter comma-separated list of the selected indices [3]: 1,3

For HANA database applications, select only the first and third options (server and client) by
default. You can select the second option (all) to install all components based on customer
requirements.
Collecting information from host 'NODE02'...

Information collected from host 'NODE02'.
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]: 1
Select a system environment type, such as production, test, development, and custom based
on customer requirements.
Enter Certificate Host Name For Host 'NODE01' [NODE01]:

Enter SAP Host Agent User (sapadm) Password:
Confirm SAP Host Agent User (sapadm) Password:

Enter a database password based on customer requirements.
Enter System Administrator Home Directory [/usr/sap/ANA/home]:

Enter System Administrator User ID [1000]:
Enter ID of User Group (sapsys) [79]:
Summary before execution:

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

Installation Parameters
Remote Execution: ssh
Installation Path: /hana/shared
Local Host Name: node01
Root User Name: root
Directory containing a storage configuration: /hana/shared/
Internal Network Address: 192.168.1.0/24
SAP HANA System ID: ANA
Instance Number: 00
Database Mode: single_container
System Usage: production
Location of Data Volumes: /hana/data/ANA
Location of Log Volumes: /hana/log/ANA
Certificate Host Names: node07 -> node07, node06 -> node06, node03 -> node03, node05
-> node05, node04 -> node04, node01 -> node01, node08 -> node08, node02 -> node02
System Administrator Home Directory: /usr/sap/ANA/home
System Administrator Login Shell: /bin/sh
System Administrator User ID: 1000
ID of User Group (sapsys): 79
Restart instance after machine reboot?: Yes
Software Components
SAP HANA Database
Install version 1.00.122.05.1481577062
Location:
SAP HANA AFL (Misc)
Do not install
SAP HANA LCAPPS
Do not install
SAP TRD AFL FOR HANA
Do not install
SAP HANA Database Client
Do not install
SAP HANA Studio
Do not install
SAP HANA Smart Data Access
Do not install
Additional Hosts
node05
Role: Database Worker (worker)
High-Availability Group: default
Storage Partition: 5

node02
node03
node08
Role: Database Standby (standby)
Storage Partition: N/A
node06
node04
node07
Do you want to continue? (y/n):

Invalid input "". Please type "y" or "n": y
Installing components...
Installing SAP HANA Database...
Preparing package 'Saphostagent Setup'...
Preparing package 'Python Support'...
Preparing package 'Python Runtime'...
Preparing package 'Product Manifest'...
Preparing package 'Binaries'...
Preparing package 'Installer'...
Preparing package 'Ini Files'...
Preparing package 'HWCCT'...
Preparing package 'Emergency Support Package'...
Preparing package 'EPM'...
Preparing package 'Documentation'...
Preparing package 'Delivery Units'...
Preparing package 'DAT Languages'...
Preparing package 'DAT Configfiles'...
Creating System...
Extracting software...
Installing package 'Saphostagent Setup'...
Installing package 'Python Support'...
Installing package 'Python Runtime'...
Installing package 'Product Manifest'...
Installing package 'Binaries'...
Installing package 'Installer'...
Installing package 'Ini Files'...
Installing package 'HWCCT'...
Installing package 'Emergency Support Package'...

Installing package 'EPM'...

Installing package 'Documentation'...
Installing package 'Delivery Units'...
Installing package 'DAT Languages'...
Installing package 'DAT Configfiles'...
Creating instance...
Starting SAP HANA Database system...
Starting 1 process on host 'node01':
Starting on 'node01': hdbdaemon
Starting 7 processes on host 'node01':
Starting on 'node01': hdbcompileserver, hdbdaemon, hdbindexserver, hdbnameserver,
hdbpreprocessor, hdbwebdispatcher, hdbxsengine
Starting on 'node01': hdbcompileserver, hdbdaemon, hdbindexserver, hdbpreprocessor,
hdbwebdispatcher, hdbxsengine
Starting on 'node01': hdbcompileserver, hdbdaemon, hdbindexserver,
Starting on 'node01': hdbdaemon, hdbindexserver, hdbwebdispatcher, hdbxsengine
Starting on 'node01': hdbdaemon, hdbwebdispatcher, hdbxsengine
Starting on 'node01': hdbdaemon, hdbwebdispatcher
All server processes started on host 'node01'.
Importing delivery units...
Importing delivery unit HCO_INA_SERVICE
Importing delivery unit HANA_DT_BASE
Importing delivery unit HANA_IDE_CORE
Importing delivery unit HANA_TA_CONFIG
Importing delivery unit HANA_UI_INTEGRATION_SVC
Importing delivery unit HANA_UI_INTEGRATION_CONTENT
Importing delivery unit HANA_XS_BASE
Importing delivery unit HANA_XS_DBUTILS
Importing delivery unit HANA_XS_EDITOR
Importing delivery unit HANA_XS_IDE
Importing delivery unit HANA_XS_LM
Importing delivery unit HDC_ADMIN
Importing delivery unit HDC_IDE_CORE
Importing delivery unit HDC_SEC_CP
Importing delivery unit HDC_XS_BASE
Importing delivery unit HDC_XS_LM
Importing delivery unit SAPUI5_1
Importing delivery unit SAP_WATT
Importing delivery unit HANA_BACKUP
Importing delivery unit HANA_HDBLCM
Importing delivery unit HANA_SEC_BASE
Importing delivery unit HANA_SEC_CP
Importing delivery unit HANA_ADMIN
Adding 7 additional hosts in parallel
Adding host 'node08'...
node08: Adding host 'node08' to instance '00'...


node08: Starting SAP HANA Database...
node08: Starting 1 process on host 'node08':
node08: Starting on 'node08': hdbdaemon
node08: Starting 5 processes on host 'node08':
node08: Starting on 'node08': hdbcompileserver, hdbdaemon, hdbindexserver,
hdbnameserver, hdbpreprocessor
hdbpreprocessor
node08: Starting on 'node08': hdbcompileserver, hdbdaemon, hdbindexserver
node08: Starting on 'node08': hdbdaemon, hdbindexserver
node08: All server processes started on host 'node08'.
hdbpreprocessor
hdbpreprocessor


hdbpreprocessor
hdbpreprocessor
hdbpreprocessor
hdbpreprocessor
Installing Resident hdblcm...
Creating Component List...
Regenerating SSL certificates...
Deploying SAP Host Agent configurations...
Updating SAP HANA instance integration on host 'node05'...
SAP HANA system installed
You can send feedback to SAP with this form:
https://node01:1129/lmsl/HDBLCM/ANA/feedback/feedback.html
Log file written to '/var/tmp/hdb_ANA_hdblcm_install_2015-09-20_17.24.39/hdblcm.log'
on host 'node01'.
When the message "Creating System..." is displayed, run the following commands on each
node:
ll /usr/sap
chmod u+w /usr/sap/ANA/HDB00/exe
chown anaadm:sapsys -R /hana/data/ /hana/log/

7.2.2 Installation on Nodes One by One
This section uses SAP HANA SP10_100.0 as an example to describe how to perform database
installation on nodes one by one.
Master Node
HW00001:/hana/shared/51049932_SP10_100/DATA_UNITS/HDB_LCM_LINUX_X86_64 # ./hdblcm
--action=install --sid=ANA --number=00 --sapmnt=/hana/shared/
--storage_cfg=/hana/shared/ --root_user=root --autostart=on --restrict_max_mem=off
--max_mem=0 --logpath=/hana/log/ANA --nostart=off --datapath=/hana/data/ANA
--shell=/bin/sh --hostname=NODE01 --remote_execution=ssh --install_hostagent=on
--db_mode=singledb --install_ssh_key=on --password=Huawei123
--system_user_password=Huawei123 --root_password=Huawei123
--internal_network=192.168.1.0/24
Enter a database name and password based on customer requirements.
SAP HANA Lifecycle Management - SAP HANA 1.00.122.05.1481577062

***************************************************************
Scanning Software Locations...

Detected components:
SAP HANA Database (1.00.122.05.1481577062) in
SAP HANA AFL (Misc) (1.00.122.05.1481577062) in
/hana/shared/51049932_SP10_100/DATA_UNITS/HDB_AFL_LINUX_X86_64/packages
SAP HANA LCAPPS (1.00.122.05.1481577062) in
/hana/shared/51049932_SP10_100/DATA_UNITS/HANA_LCAPPS_10_LINUX_X86_64/packages
SAP TRD AFL FOR HANA (1.00.122.05.1481577062) in
/hana/shared/51049932_SP10_100/DATA_UNITS/HDB_TRD_AFL_LINUX_X86_64/packages
SAP HANA Database Client (1.00.122.05.1481577062) in
SAP HANA Studio (2.1.4.000000) in
/hana/shared/51049932_SP10_100/DATA_UNITS/HDB_STUDIO_LINUX_X86_64/studio
SAP HANA Smart Data Access (1.00.4.004.0) in
/hana/shared/51049932_SP10_100/DATA_UNITS/SAP_HANA_SDA_10/packages
SAP HANA Database version '1.00.122.05.1481577062' 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.122.05.1481577062

4 | afl | Install SAP HANA AFL (Misc) version 1.00.122.05.1481577062
5 | lcapps | Install SAP HANA LCAPPS version 1.00.122.05.1481577062
6 | smartda | Install SAP HANA Smart Data Access version 1.00.4.004.0
7 | studio | Install SAP HANA Studio version 2.1.4.000000
8 | trd | Install SAP TRD AFL FOR HANA version 1.00.122.05.1481577062
Enter comma-separated list of the selected indices [3]: 1,3
For HANA database applications, select only the first and third options (server and client) by
default. You can select the second option (all) to install all components based on customer
requirements.
Do you want to add additional hosts to the system? (y/n): n
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]: 1
Select a system environment type, such as production, test, development, and custom based
on customer requirements.
Enter Certificate Host Name For Host 'node01' [node01]:

Enter System Administrator Home Directory [/usr/sap/ANA/home]:
Enter System Administrator User ID [1000]:

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

Installation Parameters
Remote Execution: ssh
Directory containing a storage configuration: /hana/shared/
Internal Network Address: 192.168.1.0/24
Instance Number: 00
Database Mode: single_container
System Usage: production
Location of Data Volumes: /hana/data/ANA

Location of Log Volumes: /hana/log/ANA

Certificate Host Names: node01 -> node01
System Administrator Home Directory: /usr/sap/ANA/home
System Administrator Login Shell: /bin/sh
System Administrator User ID: 1000
ID of User Group (sapsys): 79
Restart instance after machine reboot?: Yes
SAP HANA Database Client Installation Path: /hana/shared/ANA/hdbclient
Software Components
SAP HANA Database
Install version 1.00.122.05.1481577062
Location:
SAP HANA AFL (Misc)
Do not install
SAP HANA LCAPPS
Do not install
SAP TRD AFL FOR HANA
Do not install
SAP HANA Database Client
Install version 1.00.122.05.1481577062
Location:
SAP HANA Studio
Do not install
SAP HANA Smart Data Access
Do not install
Do you want to continue? (y/n): y
Installing components...
Installing SAP HANA Database...
Preparing package 'Saphostagent Setup'...
Preparing package 'Python Support'...
Preparing package 'Binaries'...
Preparing package 'Installer'...
Preparing package 'Ini Files'...
Preparing package 'HWCCT'...
Preparing package 'Emergency Support Package'...
Preparing package 'EPM'...
Preparing package 'Documentation'...
Preparing package 'Delivery Units'...
Preparing package 'DAT Languages'...
Preparing package 'DAT Configfiles'...
Creating System...
Extracting software...
Installing package 'Saphostagent Setup'...
Installing package 'Python Support'...
Installing package 'Binaries'...
Installing package 'Installer'...
Installing package 'Ini Files'...

Installing package 'HWCCT'...

Installing package 'Emergency Support Package'...
Installing package 'EPM'...
Installing package 'Documentation'...
Installing package 'Delivery Units'...
Installing package 'DAT Languages'...
Installing package 'DAT Configfiles'...
Creating instance...
Starting SAP HANA Database system...
hdbpreprocessor, hdbwebdispatcher, hdbxsengine
Starting on 'node01': hdbcompileserver, hdbdaemon, hdbindexserver, hdbpreprocessor,
Starting on 'node01': hdbdaemon, hdbindexserver, hdbwebdispatcher, hdbxsengine
Starting on 'node01': hdbdaemon, hdbwebdispatcher, hdbxsengine
Starting on 'node01': hdbdaemon, hdbwebdispatcher
All server processes started on host 'node01'.
Importing delivery units...
Importing delivery unit HCO_INA_SERVICE
Importing delivery unit HANA_DT_BASE
Importing delivery unit HANA_IDE_CORE
Importing delivery unit HANA_TA_CONFIG
Importing delivery unit HANA_UI_INTEGRATION_SVC
Importing delivery unit HANA_UI_INTEGRATION_CONTENT
Importing delivery unit HANA_XS_BASE
Importing delivery unit HANA_XS_DBUTILS
Importing delivery unit HANA_XS_EDITOR
Importing delivery unit HANA_XS_IDE
Importing delivery unit HANA_XS_LM
Importing delivery unit HDC_ADMIN
Importing delivery unit HDC_IDE_CORE
Importing delivery unit HDC_SEC_CP
Importing delivery unit HDC_XS_BASE
Importing delivery unit HDC_XS_LM
Importing delivery unit SAPUI5_1
Importing delivery unit SAP_WATT
Importing delivery unit HANA_BACKUP
Importing delivery unit HANA_HDBLCM
Importing delivery unit HANA_SEC_BASE
Importing delivery unit HANA_SEC_CP
Importing delivery unit HANA_ADMIN
Installing Resident hdblcm...
Installing SAP HANA Database Client...
Preparing package 'SQLDBC'...
Preparing package 'REPOTOOLS'...
Preparing package 'Python DB API'...
Preparing package 'ODBC'...
Preparing package 'JDBC'...
Preparing package 'HALM Client'...
Preparing package 'Client Installer'...
Installing SAP HANA Database Client to /hana/shared/ANA/hdbclient...


Installing package 'SQLDBC'...
Installing package 'REPOTOOLS'...
Installing package 'Python DB API'...
Installing package 'ODBC'...
Installing package 'JDBC'...
Installing package 'HALM Client'...
Installing package 'Client Installer'...
Creating Component List...
Registering SAP HANA Database Client...
Deploying SAP Host Agent configurations...
SAP HANA system installed
You can send feedback to SAP with this form:
https://node01:1129/lmsl/HDBLCM/ANA/feedback/feedback.html
Log file written to '/var/tmp/hdb_ANA_hdblcm_install_2015-10-09_16.42.31/hdblcm.log'
on host 'HW00001'.
When the message "Creating System..." is displayed, run the following commands on each
node:
ll /usr/sap
chmod u+w /usr/sap/ANA/HDB00/exe
chown anaadm:sapsys -R /hana/data/ /hana/log/
Slave Node
HW00002:/hana/shared/ANA/global/hdb/install/bin # ./hdbaddhost --hostname=NODE02
--install_hostagent --role=worker --storage_partition=2 --group=default
SAP HANA Lifecycle Management - Database Addhost 1.00.122.05.1481577062

***********************************************************************
Enter System Administrator (anaadm) Password:

Confirm System Administrator (anaadm) Password:

Host Role: worker
Host Failover Group: default
Storage Partition Number: 2
Enable the installation or upgrade of the SAP Host Agent: Yes
Do you want to continue? (y/n): y

Add new host 'node02' to SAP HANA Database system 'ANA'
Adding host 'node02' to instance '00'...

hdbnsutil: adding host node02 to distributed landscape with role=worker, group=default,

subpath=2 ...
Upgrading SAP Host Agent to version '7.21.2'...
Starting SAP HANA Database...
hdbpreprocessor
Starting on 'node02': hdbcompileserver, hdbdaemon, hdbindexserver, hdbpreprocessor
Starting on 'node02': hdbcompileserver, hdbdaemon, hdbindexserver
Starting on 'node02': hdbdaemon, hdbindexserver
All server processes started on host 'NODE02'.
hdbaddhost done
Log file written to '/var/tmp/hdb_ANA_addhost_2015-09-22_17.59.00/hdbaddhost.log' on
host 'NODE02'.
For nodes 3 to 7, run the following commands in sequence:

./hdbaddhost --hostname=node03 --install_hostagent --role=worker
--storage_partition=3 --group=default
The installation paths on slave nodes are /hana/shared/ANA/global/hdb/install/bin.
Standby Node
HW00008:/hana/shared/ANA/global/hdb/install/bin # ./hdbaddhost --hostname=NODE08
--install_hostagent --role=standby --group=default
7.3 Checking the Database Installation

After the installation is complete, run the following commands to check the service startup
status:
[root@hw00001]# su - anaadm
HW00001:/usr/sap/ANA/HDB00> HDB info

USER PID PPID %CPU VSZ RSS COMMAND
anaadm 7414 7413 1.4 13884 2768 -sh
anaadm 7501 7414 0.0 12900 1756 \_ /bin/sh /usr/sap/ANA/HDB00/HDB info
anaadm 7524 7501 0.0 4944 880 \_ ps fx -U anaadm -o
user,pid,ppid,pcpu,vsz,rss,args

anaadm 1973 1 0.0 23092 1572 sapstart

pf=/hana/shared/ANA/profile/ANA_HDB00_hw00001
anaadm 1981 1973 0.0 483256 287908 \_
/usr/sap/ANA/HDB00/hw00001/trace/hdb.sapANA_HDB00 -d -nw -f
/usr/sap/ANA/HDB00/hw00001/daemon.ini pf=/usr/sap/ANA/SYS/profile/ANA_HDB00_hw00001
anaadm 1995 1981 0.8 5925460 1679088 \_ hdbnameserver
anaadm 3286 1981 1.8 6702960 3275084 \_ hdbcompileserver
anaadm 3289 1981 2.4 18675228 15623640 \_ hdbpreprocessor
anaadm 3344 1981 12.0 53385920 49202120 \_ hdbindexserver
anaadm 3347 1981 1.0 6630052 2425256 \_ hdbxsengine
anaadm 5872 1981 0.2 5160288 720756 \_ hdbwebdispatcher
anaadm 1781 1 0.0 214144 61492 /usr/sap/ANA/HDB00/exe/sapstartsrv
pf=/hana/shared/ANA/profile/ANA_HDB00_hw00001 -D -u anaadm
HW00001:/usr/sap/ANA/HDB00>
You can run the following commands to start or stop the database:
HW00001:/usr/sap/ANA/HDB00> HDB start
HW00001:/usr/sap/ANA/HDB00> HDB stop
7.4 Adjusting hdbparam parameter

After installed database, the customer should change the parameter of the HANA DataBase as
described below:
7.4.1 HANA1.0 DataBase parameter:

parameters for DATA volume:
async_write_submit_active:on
async_read_submit:on
async_write_submit_blocks:all
max_parallel_io_requests=128
parameters for LOG volume:

Login to any of the HANA nodes, and use the command below to adjust the access parameter
of the HANA DataBase:
hw00001:~ # su – s00adm
s00adm@hw00001:/usr/sap/S00/HDB00> HDB start

s00adm@hw00001:/usr/sap/S00/HDB00> hdbparam --paramset

fileio[DATA].async_write_submit_active=on

fileio[DATA].async_write_submit_blocks=all

fileio[DATA].async_read_submit=on

fileio[DATA].max_parallel_io_requests=128

fileio[LOG].async_write_submit_active=on

fileio[LOG].async_write_submit_blocks=all

fileio[LOG].async_read_submit=on

fileio[LOG].max_parallel_io_requests=128
7.4.2 HANA2.0 DataBase parameter

After Installing HANA database,you should change the parameter as following information:
parameters for DATA volume:
parameters for LOG volume:

Log in <sid>adm in putty, and change the parameter as following command:

hw00001:~ # su – s00adm
s00adm@hw00001:/usr/sap/S00/HDB00>hdbsql -u SYSTEM -p Huawei123
Welcome to the SAP HANA Database interactive terminal.
Type: \h for help with commands

\q to quit
hdbsql S00=> ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET

('fileio','max_parallel_io_requests[DATA]') = '128';
hdbsql S00=> ALTER SYSTEM ALTER CONFIGURATION ('global.ini', 'SYSTEM') SET
('fileio','max_parallel_io_requests[LOG]') = '128';
7.5 Checking the HANA Cluster Status

There are multiple method to check the cluster status.
OS command line
Run the following commands on any node to invoke the HANA cluster service verification
program:
[root@HW00001 ~]# su - anaadm
anaadm@HW00011:/usr/sap/ANA/HDB00> cdpy
anaadm@HW00011:/usr/sap/ANA/HDB00/exe/python_support> python
landscapeHostConfiguration.py
HANA Studio
Login to the HANA Studio, and go to the overview, or LandscapeHosts to check the
HANA DataBase status.
HDB Admin
Run the following commands on any node to invoke the HANA cluster service verification
program:
HW00001:/ # su – anaadm
HW00001: /usr/sap/ANA/HDB00> export DISPLAY=192.168.32.50:0.0
HW00001: /usr/sap/ANA/HDB00> HDB admin
1. 192.168.32.50 is the IP address of the PC used to log in to the service management port on a
node remotely.
2. the Xmanager should be installed in the PC.

7.6 Adjusting the performance of the Cluster

Login to any of the HANA nodes, and use the command below to adjust the access parameter
of the HANA DataBase:
[root@HW00001 ~]# su - anaadm
HW00001:/usr/sap/ANA/HDB00> hdbparam --paramset
fileio[DATA].async_write_submit_active=on

fileio[DATA].async_write_submit_blocks=all

fileio[DATA].async_read_submit=on

fileio[DATA].max_parallel_io_requests=128

fileio[LOG].async_write_submit_active=on

fileio[LOG].async_write_submit_blocks=all
HW00001:/usr/sap/ANA/HDB00> hdbparam --paramset fileio[LOG].async_read_submit=on

fileio[LOG].max_parallel_io_requests=128

Guide (RH5885H&RH8100 V3+5500 V3+Redhat7.2) 8 SAP HANA Database Uninstallation
8 SAP HANA Database Uninstallation
8.1 Preparing for the Uninstallation

8.1.1 Stopping Services
WARNING
Before uninstalling a SAP HANA database, ensure that you have obtained customers'
approval and customer (cluster) services have been stopped and backed up.
8.1.2 Backing Up Data
WARNING
Before uninstalling a SAP HANA database, ensure that key data of the database has been
backed up.
8.2 Uninstalling the SAP HANA Database

8.2.1 One-Click Uninstallation
Prerequisites:
Nodes in the SAP HANA database to be uninstalled are communicating with each other
properly, and the SAP HANA database is normal.
Step 1 Access the installation instance directory of the database.
/hana/shared/ANA/global/hdb/install/bin

The installation path of a SAP HANA database is different from its uninstallation path. The
uninstallation path is under the installation instance directory.
Step 2 Run the uninstallation command.
This section uses SAP HANA SP10_100.0 as an example to describe how to uninstall a SAP HANA
database in one-click mode.
HW00001:/hana/shared/ANA/global/hdb/install/bin # ./hdbuninst
SAP HANA Lifecycle Management - Uninstallation 1.00.122.05.1481577062

*********************************************************************
Automatic uninstallation of remote hosts [y]: y

Enter Root User Name [root]:
Do you want to uninstall the following installation?
ANA /hana/shared/ANA HDB_ALONE

HDB00
version: 1.00.122.05.1481577062
hosts: node01 (Database Worker (worker)), node02 (Database Worker (worker)), node03
(Database Worker (worker)), node04 (Database Worker (worker)), node05 (Database Worker
(worker)), node06 (Database Worker (worker)), node07 (Database Worker (worker)), node08
(Database Standby (standby))
All data volumes and all log volumes will be removed!

Data and log backup files in directory '/hana/shared/ANA' and its subdirectories will
be removed as well.
Confirm (y/n): y
Uninstalling SAP HANA Database...
Removing SAP HANA Database instance...
Uninstalling hosts...
Uninstalling host 'node06'...
Uninstallation of host 'node06' done.


Uninstalling package DAT Configfiles...
Uninstalling package DAT Languages...
Uninstalling package Delivery Units...
Uninstalling package Documentation...
Uninstalling package EPM...
Uninstalling package Emergency Support Package...
Uninstalling package HWCCT...
Uninstalling package Ini Files...
Uninstalling package Installer...
Uninstalling package Binaries...
Uninstalling package Product Manifest...
Uninstalling package Python Runtime...
Uninstalling package Python Support...
Uninstalling package Saphostagent Setup...
Uninstallation done.
Log file written to '/var/tmp/hdb_ANA_uninstall_2015-09-22_17.39.06/hdbuninst.log' on
host 'HW00001'.
----End
8.2.2 Uninstallation from Nodes One by One

Prerequisites:
A serious exception occurs on a SAP HANA database, and nodes in the database cannot
communicate with each other normally. You cannot uninstall the database by using the
method in section 8.2.1 One-Click Uninstallation.
Step 1 Access the installation source directory of the database.
For example, if the Server option is selected during the database installation (for details, see
section 7.2.1 One-Click Installation on the Master Node), access
HDB_SERVER_LINUX_X86_64. This document assumes that
HDB_SERVER_LINUX_X86_64 is stored in the /hana/shared directory.
hw00001:/hana/shared/51049967/DATA_UNITS/HDB_SERVER_LINUX_X86_64 #
Step 2 Run the uninstallation command.
This section uses SAP HANA SP10_100.0 as an example to describe how to perform database
uninstallation on nodes one by one.
Run the following command on a single node:

hw00001:/hana/shared/51049967/DATA_UNITS/HDB_SERVER_LINUX_X86_64 # ./hdbuninst
--scope=instance
SAP HANA Lifecycle Management - Uninstallation 1.00.122.05.1481577062

*********************************************************************
Installed SAP HANA installations:
0: SAP HANA Database ANA /hana/shared/ANA HDB_ALONE

HDB00
version: 1.00.122.05.1481577062
hosts: hw00001 (worker), hw00002 (worker), hw00003 (worker), hw00004

(worker),hw00005 (worker), hw00006 (worker), hw00007 (worker),hw00008 (standby)
1: None (Abort uninstallation)
Enter SAP HANA installation Id [1]: 0
Do you want to uninstall the following installation?
ANA /hana/shared/ANA HDB_ALONE

HDB00 version: 1.00.122.05.1481577062 hosts: hw00001 (worker), hw00002 (worker),
hw00003 (worker), hw00004 (worker),hw00005 (worker), hw00006 (worker), hw00007
(worker),hw00008 (standby)
All data volumes and all log volumes will be removed!

Data and log backup files in directory '/hana/shared/ANA' and its subdirectories will
be removed as well.
Confirm (y/n): y
Uninstalling SAP HANA Database...
Removing SAP HANA Database instance...
Uninstallation of SAP HANA System is not yet finished.
To complete uninstallation, run 'hdbuninst --scope=instance' on host: hw00002
(worker), hw00003 (worker), hw00004 (worker),hw00005 (worker), hw00006 (worker), hw00007
(worker),hw00008 (standby)
Uninstallation done.
Log file written to '/var/tmp/hdb_ANA_uninstall_2015-08-05_09.07.06/hdbuninst.log' on
host 'hw00001'.
Step 3 Repeat steps 1 and 2 on other nodes to uninstall the database.

----End

Guide (RH5885H&RH8100 V3+5500 V3+Redhat7.2) A ntp.conf
A ntp.conf
NTP server configuration file:
 The following dimmed information is the content of the ntp.conf configuration file.
 The red information needs to be modified based on the customer's environment.
################################################################################
## /etc/ntp.conf
##
## Sample NTP configuration file.
## See package 'ntp-doc' for documentation, Mini-HOWTO and FAQ.
## Copyright (c) 1998 S.u.S.E. GmbH Fuerth, Germany.
##
## Author: Michael Andres, <ma@suse.de>
## Michael Skibbe, <mskibbe@suse.de>
##
################################################################################
##
## Radio and modem clocks by convention have addresses in the
## form 127.127.t.u, where t is the clock type and u is a unit
## number in the range 0-3.
##
## Most of these clocks require support in the form of a
## serial port or special bus peripheral. The particular
## device is normally specified by adding a soft link
## /dev/device-u to the particular hardware device involved,
## where u correspond to the unit number above.
##
## Generic DCF77 clock on serial port (Conrad DCF77)
## Address: 127.127.8.u
## Serial Port: /dev/refclock-u
##
## (create soft link /dev/refclock-0 to the particular ttyS?)
##
# server 127.127.8.0 mode 5 prefer
##
## Undisciplined Local Clock. This is a fake driver intended for backup
## and when no outside source of synchronized time is available.
##
server 127.127.1.0

# local clock (LCL)

fudge 127.127.1.0 stratum 10
server 192.168.1.230 prefer
broadcastdelay 0.008
driftfile /var/lib/ntp/drift/ntp.drift
# path for drift file
logfile /var/log/ntp
# alternate log file
# logconfig =syncstatus + sysevents
# logconfig =all
# statsdir /tmp/ # directory for statistics files

# filegen peerstats file peerstats type day enable
# filegen loopstats file loopstats type day enable
# filegen clockstats file clockstats type day enable
#
# Authentication stuff
#
keys /etc/ntp.keys
# path for keys file
trustedkey 1
# define trusted keys
requestkey 1
restrict 127.0.0.1
restrict 192.168.40.0 mask 255.255.255.0 nomodify
restrict 198.168.1.230
##
## Add external Servers using
## # rcntp addserver <yourserver>
##
##
##
restrict default ignore

restrict 127.0.0.1
restrict 192.168.50.0 mask 255.255.255.0 nomodify
restrict 198.168.1.230
##
## Add external Servers using
## # rcntp addserver <yourserver>
##
##
##

restrict default ignore

# key (7) for accessing server variables
# controlkey 15 # key (6) for accessing server variables

Guide (RH5885H&RH8100 V3+5500 V3+Redhat7.2) B global.ini
B global.ini
global.ini configuration file:
 The following dimmed information is the content of the global.ini configuration file.
 The red information needs to be modified based on the customer's environment.
# .short_desc
# Global landscape configuration
# .full_desc
# This configuration file describes global parameters for each service in the
# landscape.
# .file
###############################################################################
# Persistence configuration
###############################################################################
# .short_desc
# Configuration of persistence
# .full_desc
# This section contains various parameters which are related to configuration
# of data and log location as well as data and log backup.
[persistence]
# .short_desc
# Base path for data volumes
# .full_desc
# All data volumes will be stored under this path.
# .type path
# .change offline
# basepath_datavolumes=$(DIR_GLOBAL)/hdb/data
basepath_datavolumes=/hana/data/ANA/
# .short_desc
# Base path for log volumes
# .full_desc
# All log volumes will be stored under this path.
#
# \see \ref logger
# .type path
# .change offline

basepath_logvolumes=/hana/log/ANA/
basepath_shared=yes
# .short_desc
# Directory layout of volumes
# .full_desc
# Determines whether there should be an extra subpath bewteen base path and volumes or
not
# .type path
# .change offline
use_mountpoints = yes
# .short_desc
# Data backup path
# .full_desc
# Data backups will be stored in this directory.
# .type path
# .change offline
basepath_databackup=$(DIR_INSTANCE)/backup/data
# .short_desc
# Log backup path
# .full_desc
# Log backups will be stored in this directory.
# .type path
# .change offline
basepath_logbackup=$(DIR_INSTANCE)/backup/log
# .short_desc
# Enable automatic log backup (IN DEVELOPMENT)
# .full_desc
# Automatic log backup is permanently backing up closed log segments of the
# database. Generated backups will be stored in
# \ref param_persistence_basepath_logbackup.
#
# \see \ref param_persistence_log_backup_timeout_s, \ref logger
# .type bool
# .change offline
enable_auto_log_backup=yes
# .short_desc
# Checksum algorithm to use for writing out data pages and log
# .full_desc
# This parameter defines which checksum algorithm will be used to write newly-modified
data
# pages to the disk. Data pages already on the disk will not get new checksum. Similarly,
new
# log buffers will be written using this checksum algorithm.
#
# Following checksum algorithms are available:
# - CRC32 - CRC32 over whole page (default, faster than ADLER32 for CPUs with CRC32
instruction)
# - ADLER32 - Adler checksum over whole page (faster than CRC32 on CPUs lacking CRC32
instruction)

# - CRC32_SPARSE - CRC32 over first 64 bytes in each 512 byte block (to speed up
checksumming, unsafe)
# - NULL - checksum off (completely unsafe)
#
# It is strongly recommended to use CRC32 to checksum whole pages and log buffers.
# .change online
# .range CRC32,ADLER32,CRC32_SPARSE,NULL
# .dev
checksum_algorithm=CRC32
# .short_desc
# Savepoint interval
# .full_desc
# Sets savepoint interval. Setting to 0 will disable the savepoint for testing
# purposes (e.g., log I/O performance tests; DO NOT USE for productive settings).
#
# Savepoint interval controls how often the internal buffers are flushed to
# the disk and a restart record is written. Upon restart after a power failure
# or crash, the log since the last savepoint needs to be replayed. Thus, this
# parameter indirectly controls restart time.
#
# \see \ref pers_u_savepoint, \ref pers_u
# .type integer
# .unit second
# .range 0,10-7200
# .change online
savepoint_interval_s = 300
# .short_desc
# Maximal number of job execution threads used by garbage collection
# .full_desc
# Sets the number of maximal parallel executed garbage collection jobs.
# A value of 0 will cause the maximum number of threads be set to a default value
# equal to the actual number of logical CPUs (up to a maximum of 256).
#
# Decreasing number too much can lead to "database full" situations because
# historical data may grow faster than garbage collection is able to clean up.
#
# Garbage collection uses job executer threads for execution. Therefore number
# of threads used may depend as well on executer configuration.
# Only an upper limit of threads used can be specified using this parameter.
#
# .type integer
# .range 0-256
# .change offline
max_gc_parallelity = 0
# .short_desc
# Number of recovery queues to use
# .full_desc
# Sets the number of parallel recovery queues to speed up database log replay.
# Value 0 signifies to use number of CPUs (up to a maximum of 64).
#
# Increasing recovery queue count also increases memory demand for various
# control structures and possibly increases synchronization overhead in higher

# layers during recovery, resulting in higher CPU usage per log amount processed
# (which amortizes itself by using more CPUs in parallel). Since the log replay
# is normally I/O bound, default settings should be sufficient.
#
# \see \ref logger, \ref pers_u
# .type integer
# .range 0-64
# .change offline
recovery_queue_count = 0
# .short_desc
# Log mode
# .full_desc
# Sets logging mode. Following logging modes are supported:
# - normal: normal mode, log segments must be backed up (default for HANA DB
1.0 SPS03+),
# - overwrite: overwrite mode, log segments are freed by the savepoint (e.g.,
# useful for test installations without backup/recovery),
# - legacy: legacy HANA 1.0 pre-SPS03 mode, segments will be kept until full
# backup is executed to allow recovery from full backup + log in the log
# area.
#
# You can optionally release free log files explicitly (e.g., after backup
# in log mode legacy or after savepoint in other log modes) using
# \ref sql_reclaim_log SQL command.
#
# \see \ref logger
# .type enum
# .range normal,overwrite,legacy
# .change offline
log_mode=normal
# .short_desc
# Log segment size in megabytes
# .full_desc
# Sets one log segment size in megabytes.
#
# A segment is backup/recovery
# and restart unit. Only whole segments are considered there, thus increasing
# the segment size may lead to longer restart times, since even after correct
# shutdown, a complete log segment must be read at restart (to be optimized).
#
# \note After changing this parameter online, it will only affect new segments.
# I.e., current segment will be finished as-is and any new or reused
# segments will be set to this new size. You can force closing current
# segment for instance by forcing log segment backup, e.g., using
# management_console command \ref pgm_console_log "log backup".
#
# \see \ref param_persistence_log_buffer_size_kb,
# \ref param_persistence_log_buffer_count,
# \ref param_persistence_log_preformat_segment_count, \ref logger
# .type integer
# .unit MB
# .range 8-4096
# .change online

log_segment_size_mb=1024
# .short_desc
# Size of one in-memory buffer in kilobytes
# .full_desc
# Sets size of one in-memory log buffer in kilobytes.
#
# Setting higher buffer size may increase throughput at the cost of COMMIT
# latency. During COMMIT of a transaction, at most this much data must be
# flushed to the I/O subsystem (provided all preceding buffers are already
# flushed).
#
# \see \ref param_persistence_log_segment_size_mb,
# \ref param_persistence_log_buffer_count, \ref logger
# .type integer
# .unit KB
# .range 128-16384
# .change online
log_buffer_size_kb=1024
# .short_desc
# Count of in-memory buffers per log partition
# .full_desc
# Sets count of log buffers per physical partition.
#
# Increasing this parameter will allow buffering an additional peak load at
# the cost of possibly increasing latency of parallel short transactions.
# If the I/O subsystem allows highly-parallel writes, you might consider
# increasing this parameter to allow better throughput for large
# transactions.
#
# \see \ref param_persistence_log_buffer_size_kb,
# \ref param_persistence_log_segment_size_mb, \ref logger
# .type integer
# .range 4-128
# .change offline
log_buffer_count=8
# .short_desc
# Log segment backup timeout in seconds
# .full_desc
# Sets log backup timeout in seconds (0 = disabled).
#
# Log backup timeout specifies, how much time may pass since a
# COMMIT until the log segment containing this COMMIT is put into log segment
# backup queue. In case this amount of time passes before the segment is
# full, the segment will be closed prematurely and put to the log segment
# backup queue. Thus, the administrator may indicate how much work can get
# lost in case of catastrophic failure (backup timeout + actual log segment
# backup time).
#
# \see \ref param_persistence_enable_auto_log_backup, \ref logger
# .type integer
# .unit second
# .change online

log_backup_timeout_s=900
# .short_desc
# Number of log segments to preformat in each partition at the initialization
# .full_desc
# Sets count of log segments to preformat at the startup of the database, when
# using directory-based log partitions.
#
# Normally, log segments are preformatted on-demand, so there is no need to
# change this parameter, except maybe for performance tests to make sure
# there is no logging slowdown due to preformatting of log segments. You have
# to wait with the test, until the segments are preformatted, to get the full
# speed.
#
# \see \ref param_persistence_log_segment_size_mb, \ref logger
# .type integer
# .change offline
log_preformat_segment_count=2
# .short_desc
# Number of log entries per log replay step
# .full_desc
# Sets the number of log entries that are processed in one log replay step
# during log recovery.
#
# This parameter sets how many log entries the master index server is ahead
# of the slave servers during log replay in case of log recovery.
#
# .type integer
# .range 64-2147483648
# .change offline
log_replay_step_size=1073741824
# .short_desc
# Handle page corruptions
# .full_desc
# This parameter decides how to deal with page corruptions. Following ways are supported:
# - ignore: Ignore error (if possible) NOT RECOMMENDED FOR PRODUCTIVE SYSTEMS
# - exception: Throw exception, upper layers decide how to handle this.
# - crash: Crash
#
# .type enum
# .range ignore,exception,crash
# .change online
handle_corrupt_pages=ignore
# .short_desc
# Retry corrupted pages
# .full_desc
# This parameter decides if the PageIO layer tries to reload corrupted pages.
#
# .type bool
# .change online
retry_corrupt_pages=true

# .short_desc
# Dump corrupted pages
# .full_desc
# This parameter decides if corrupted pages should be dumped to the instance's trace
directory.
# if \ref retry_corrupt_pages is TRUE and a retry is successful, this page is also dumped.
#
# .type bool
# .change online
dump_corrupt_pages=true
# .short_desc
# Write runtime dump for corrupted pages
# .full_desc
# This parameter decides if a runtime dump (suffix "page") should be written when
encountering
# a corrupted page.
#
# .type bool
# .change online
runtimedump_corrupt_pages=true
# .short_desc
# Initialize pages with pattern for read
# .full_desc
# This parameter decides if a page that is to be read from disk is initialized with
# a memory pattern. Setting this parameter to true comes with a certain performance
penalty.
#
# .type bool
# .change online
initialize_pages_before_read=false
# .short_desc
# Data volume encryption
# .full_desc
# Defines if the data volume will be encrypted
# .type bool
# .change online
data_encryption=false
# .short_desc
# M_DISKS summation logic
# .full_desc
# Defines how the M_DISKS view handles the storage configuration of data and log:
# auto: guessing logic, which concludes disk IDs from /proc/mounts
# shared: same ID for all storages, because the data and log storage is shared across
all hosts
# nonshared: distinct ID for each storage, because each host has its own storage partition
# .type string
# .change online
m_disks_summation_logic = auto
###############################################################################
# Basis configuration

###############################################################################
# .short_desc
# Various parameters which are related to configuration of how threads behave.
[threads]
# .short_desc
# Default stack size for newly-generated threads.
# .type integer
# .unit KB
# .range 128-16384
# .change online
default_stack_size_kb = 1024
# .short_desc
# Default stack size for newly-generated worker threads.
# .type integer
# .unit KB
# .range 128-16384
# .change online
worker_stack_size_kb = 1024
# .short_desc Defines which and how execution time values are measure
# .full_desc
# Execution like user, system, wait and io time can be measure to analyze
# performance bottlenecks. These values can be obtained by system call
# or in user space. System call are much more expensive, user space does
# not consider thread preemption by the system scheduler.
# Possible values are:
# NONE = 0,
# SYS_USER_TIME = 1,
# SYS_KERNEL_TIME = 2,
# SYS_WAIT_TIME = 4,
# SYS_IO_TIME = 8,
#
# ALL_SYS_TIMES = 15,
#
# CONTEXT_USER_TIME = 16,
# CONTEXT_KERNEL_TIME = 32,
# CONTEXT_WAIT_TIME = 64,
# CONTEXT_IO_TIME = 128,
#
# ALL_CONTEXT_TIMES = 240,
#
# CONTEXT_AND_SYS_TIMES = 255,
#
# L2_CACHE_MISSES = 256,
#
# ALL_VALUES = 511
#
# .type integer
# .change online
#
instrumentation_config = 0

###############################################################################
# Memory management configuration
###############################################################################
# .short_desc
# Configuration of memory management
# .full_desc
# This section contains parameters which are related to configuration
# of memory management
[memorymanager]
# .short_desc
# Global alloation limit in megabytes
# .full_desc
# Sets global allocation limit in megabytes.
#
# Default value is 0 (a reasonable alloation limit according to the physical ram
# is chosen - usually 90% of the physical memory)
#
# .type integer
# .unit MB
# .change offline
global_allocation_limit=0
# .short_desc
# Threshold to start memory garbage collection proactively
# .full_desc
# Starts memory garbage collection when async_free_threshold percent of
# the global allocation limit has been allocated.
#
# Default value is 100 (proactive memory garbage collection is disabled)
#
# .type integer
# .unit percent
# .change offline
async_free_threshold=100
# .short_desc
# Target of proactive memory garbage collection
# .full_desc
# Proactive garbage collection tries to reduce allocated memory below
# async_free_target percent of the global allocation limit.
#
# Default value is 95 (% of the global allocation limit).
#
# .type integer
# .unit percent
# .change offline
async_free_target=95
# .short_desc
# Parameter for statement memory limitation
# .full_desc
# The memory that can be allocated in connection with a statement is
# limited by this parameter. If the memory allocated exceeds this limit,

# the statement is aborted.

#
# By default this value is not set.
#
# .type integer
# .unit GB
# .change online
statement_memory_limit=0
###############################################################################
# Memory objects configuration
###############################################################################
# .short_desc
# Configuration of memory object manager and memory objects
# .full_desc
# of memory object manager and memory objects
[memoryobjects]
# .short_desc
# Weight of disposition early_unload.
# .full_desc
# Sets weight of disposition early_unload for LRU strategy.
# The higher the weight the more important the memory object is regarded.
# Memory object container tends to unload memory objects with lower weights earlier
# in case of memory shortage than memory objects with higher weights.
#
# Default value is 100
#
# .type integer
# .change online
disposition_weight_early_unload=100
###############################################################################
# Backup configuration
###############################################################################
# .short_desc
# Configuration of backup and recovery
# .full_desc
# data and log backup and recovery.
[backup]
# .short_desc
# Buffer size for copying log backups
# .full_desc
# Defines the buffer size used to copy
# log segments into backups.
#
# Default value is 128MB.
#
# .unit MB
# .range 16-4096

# .change online
log_backup_buffer_size=128
# .short_desc
# Log backups done over backint.
# .full_desc
# Defines whether log backup are done
# using backint.
#
# Default value is false.
#
# .type bool
# .change online
log_backup_using_backint=false
# .short_desc
# Backint parameter file for log backups.
# .full_desc
# Defines the parameter file which is used
# while log backup using backint.
#
# Default value is not defined.
#
# .type string
# .change online
log_backup_parameter_file=$(DIR_INSTANCE)/backup/log
# .short_desc
# Buffer size for copying data backups
# .full_desc
# Defines the buffer size used to copy
# data for page into backups.
#
# Default value is 512MB.
#
# .unit MB
# .range 16-4096
# .change online
data_backup_buffer_size=512
# .short_desc
# Backint parameter file for data backups.
# .full_desc
# Defines the parameter file which is used
# while data backup using backint.
#
# Default value is not defined.
#
# .type string
# .change online
data_backup_parameter_file=$(DIR_INSTANCE)/backup/data
# .short_desc
# Maximum age of the recovery file
# .full_desc

# Defines the maximum age of a valid recovery file.

#
# Default value is 300 seconds.
#
# .type integer
# .unit second
# .change online
max_recoveryfile_age=300
# .short_desc
# Max number of parallel backint channels per request
# .full_desc
# Defines the maximum number of backint channels while recovery per
# backint request.
#
# Default value is 64 channels.
#
# .type integer
# .unit channels
# .change online
max_recovery_backint_channels = 64
###############################################################################
# Watchdog configuration
###############################################################################
[self_watchdog]
# set interval to 0 to disable self_watchdog
interval=10
initial_sleep=180
ping_timeout=180
retries_before_abort=5
###############################################################################
# Job executor configuration
###############################################################################
# .short_desc
# Configuration of job executor
# .full_desc
# This section contains parameters related to the job executor.
[execution]
# .short_desc
# Maximum number of parallel threads in job executor.
# .full_desc
# Sets the maximum number of parallel threads to execute jobs in the job executor
# system. This number is a hint for the job executor to not start more than the
# specified number of JobWorker threads, however if it becomes necessary to start
# more threads, the job executor will do so.
#
# A value of 0 will cause the maximum number of threads be set to a default value
# derived from the actual number of logical CPUs, which currently is half of them.
#

# .type integer
# .range 0-number_of_logical_CPUs
# .change online
max_concurrency=0
###############################################################################
# Tracer configuration
###############################################################################
# .short_desc
# Configuration of tracer
# .full_desc
# This section contains parameters related to tracing various messages to
# database trace file and trace levels for individual components.
[trace]
formatter=connection
#
saptracelevel = 1
#
maxfilesize = 10000000
maxfiles = 10
#
maxalertfilesize = 50000000
#
flushinterval = 5
#
default = error
alert = error
#
basis=info
fileio=info
eventhandler=info
historymanager=info
logger=info
memory=info
persistencemanager=info
assign=info
tracecontext=info
###############################################################################
# . short_desc
# inifile configuration
[inifile]
# .short_desc
# delay between inifile modification and reconfig in distributed landscapes
# .full_desc
# to reduce problems with visibility of inifile updates due to NFS caching, some time
# should be waited betweeen save and distributed reconfigure
# .type integer
# .unit milliseconds
distributed_reconfig_delay=0
###############################################################################
# Storage HA configuration

###############################################################################
# . short_desc
# storage HA configuration
[storage]
# .short_desc
# name of python HA provider script
ha_provider = hdb_ha.fcClient
# ha_provider_path = /hana/shared/
# these parameters name the WWIDs of the devices for each partition/usage_type combination
# if you have more nodes, add your LUNs here.
# for proper usage, replace the '...' with specified WWID in your system.
partition_*_*__prType = 5
partition_*_data__mountoptions = -o noatime,nodiratime
partition_*_log__mountoptions = -o noatime,nodiratime
###############################################################################
# EventHandler
###############################################################################
# .short_desc
# Configuration of EventHandler
# .full_desc
# This section contains parameters related to (automatic) handling of events
[event_handler]
# .short_desc
# AutoEventHandler period
# .full_desc
# This parameter controls the time interval between automatic retries of events
# A value of 0 means no automatic retries
# .type integer
# .unit second
auto_retry_interval=60
###############################################################################
# Resource tracking
###############################################################################
# .short_desc

# Configuration for resource tracking

# .full_desc
# This section contains the configuration parameters for resource tracking in
# association with threads, statements and sessions. Among the resources
# tracked are CPU time and memory. Please note that the configuration
# parameters may be ignored by resource tracking tools that need to collect
# detailed information (e.g. Plan Visualizer).
[resource_tracking]
# .short_desc
# Main switch for resource tracking.
# .full_desc
# This parameter controls the resource tracking and allows deactivation of
# all resource tracking without having to change the individual settings.
#
# Possible values:
#
# - off/0:
# This disables all resource tracking. This is the default for
# performance reasons.
#
# - on/1:
# If this parameter is set to "on", all resources for which tracking has
# been enabled will be measured and are available in the pertinent views
# and traces.
#
# .type bool
# .unit online
enable_tracking=off
# .short_desc
# Mode of CPU time measurement.
# .full_desc
# This parameter controls if and how the CPU times are measured. A greater
# precision incurs a higher performance impact.
#
# Possible values:
#
# - off:
# In this case, no CPU times are determined for threads, statements or
# sessions. This is the default.
#
# - fast:
# In fast mode the collected CPU times provide ballpark figures. The
# measured values may be too high.
#
# - detailed:
# Detailed mode provides exact CPU times which can be used for finding
# CPU bottlenecks. The performance impact is much higher than in fast
# mode.
#
# .type string
# .unit online
cpu_time_measurement_mode=off

# .short_desc
# Enables/disables memory tracking.
# .full_desc
# This parameter controls whether memory consumption for statements and
# sessions will be tracked. If memory consumption is tracked, memory used
# for computing query results as well as shared resources will be tracked.
#
# Possible values:
#
# - off/0:
# The tracking of the memory usage is disabled if this parameter is set
# to "off". This is the default.
#
# - on/1:
# If set to on, memory tracking is enabled. The performance may be
# impacted noticeably.
#
# .type bool
# .unit online
memory_tracking=off
###############################################################################
# System Replication Configuration
###############################################################################
# .short_desc
# Configuration of System Replication
# .full_desc
# of system replication.System replication itself cannot be activated by
# public configuration parameters; this must be done hdbnsutil commands
# starting with "sr_".
# The configuration parameters described here affect only the behaviour
# of a system with system replication configured.
[system_replication]
# .short_desc
# Minimum time interval between two data shipping requests from the secondary.
# .full_desc
# If data shipping_logsize_threshold is rached first, the data shipping request
# will be sent before the time interval is elapsed, when the logsize threshold is reached.
# This parameter is set on the secondary.
# .type integer
# .change online
datashipping_min_time_interval = 600
# .short_desc
# Minimum amount of log shipped between two data shipping requests from the secondary.
# .full_desc
# If the time defined by datashipping_min_time_interval has passed before reaching this
threshhold,
# the data shipping request will be sent before this threshhold is reached,
# when the time interval has elapsed.
# This parameter is set on the secondary.
# .type integer

# .change online
datashipping_logsize_threshold = 5368709120
# .short_desc
# Activate preloading of column tables.
# .full_desc
# When this parameter is set, preloading of column table main parts is activated.
# The parameter can be set on the primary as well as on the secondary.
# If set on the primary, the loaded table info is collected and stored in the snapshot,
that is shipped.
# If set on the secondary, this information is evaluated and the tables are actually
preloaded
# there according to the information in the loaded table info.
# .type bool
# .change online
preload_column_tables = true
# .short_desc
# Log shipping timeout for the primary.
# .full_desc
# Number of seconds, the primary waits for shipping of a single log buffer.
# If the log shipping request is not handled within the configured time frame, it is
assumed,
# that a error situation occurred. In this case the log buffer is freed and the replication
session is canceled.
# .type integer
# .change online
logshipping_timeout = 30
# .short_desc
# Reconnect timeout for the secondary
# .full_desc
# If a secondary is disconnected from the primary due to network problems, the secondary
tries to reconnect periodically
# after the time interval specified in this parameter has passed
# .type integer
# .change online
reconnect_time_interval = 30
###############################################################################
# Debug configuration
###############################################################################
# .short_desc
# Configuration of some debug settings
# .full_desc
# of various debug settings
[debug]
# .short_desc
# Sets the debug break mode to control debug break handling
# .full_desc
#


# - on: turn debug break on
# - off: turn debug break off
# - abort: turn debug break on and abort on debug break
# - nostop_on_emergency_dump: turn debug break on, but does not raise SIGSTOP in case
of emergency shutdown
# - system_value: the mode set by environment variable will be used
#
# system_value is the default mode
#
# .type string
# .unit online
# .dev
debug_break_mode=system_value
###############################################################################
# . short_desc
# crashdump configuration
[crashdump]
# .short_desc
# Timeout until each crash dump section needs to be finished
# .full_desc
# To prevent dead lock and to avoid too long running crashdumps the section_timeout
# parameter defines the time in seconds which will spend at most for writing each
# crashdump section. Zero defines no timeout.
# .type integer
# .unit seconds
section_timeout=30
# .short_desc
# Timeout until a running crashdump is killed
# .full_desc
# To prevent dead locks and to kill too long running crashdumps the kill_timeout
# parameter defines the time in seconds which will spend at most for
# the whole crashdump writing. After this timeout the process is going to be
# killed. Zero defines no timeout.
# .type integer
# .unit seconds
kill_timeout=300
###############################################################################
# Communication
###############################################################################
# .short_desc
# Configuration of communication settings
# .full_desc
# of various communication settings
[communication]
# .short_desc
# the network interface the processes shall listen on
# .full_desc
#

# - .all: all interfaces like INADDR_ANY

# - .global: all interfaces
# - .internal: all interfaces that are listed in [internal_hostname_resolution] or local
# - .local: only local interfaces (e. g. 127.0.0.1)
# - a list of netmask specification in CIDR notation (e. g. 192.168.100.0/24)
# default is .global
listeninterface = .global
# .short_desc
# specifies the resolution of hostnames to addresses
# .full_desc
# This section mimics the behaviour of /etc/hosts. IP addresses might be assigned to
# a list of hostname aliases. If an interface address is found in this list it is
# considered internal.
# The format should be ipaddress = hostname[,alias].
# e. g. 192.168.100.1 = hanahost01, hanahost01.example.com
[internal_hostname_resolution]
192.168.1.11 = NODE01
192.168.1.12 = NODE02
192.168.1.13 = NODE03
192.168.1.14 = NODE04
192.168.1.15 = NODE05
192.168.1.16 = NODE06
192.168.1.17 = NODE07
192.168.1.18 = NODE08

Hana Ha

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

Hana Ha

Uploaded by

Copyright:

Available Formats

Huawei SAP HANA Appliance Cluster Installation

Guide (RH5885H V3&RH8100 V3 +5500

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 02 (2017-04-10) Huawei Proprietary and Confidential i

About This Document

Indicates an imminently hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Issue 02 (2017-04-10) Huawei Proprietary and Confidential ii

Indicates a potentially hazardous situation which, if not

Calls attention to important information, best practices and

Issue 02 (2017-04-10) Huawei Proprietary and Confidential iii

About This Document ............................................................................................................ ii

2 5500 V3 Deployment ........................................................................................................... 14

3 RH5885H V3/RH8100 V3 Deployment .............................................................................. 29

Issue 02 (2017-04-10) Huawei Proprietary and Confidential iv

3.3.1 Network Configure .......................................................................................................................................................... 54

4 Switch Configuration .......................................................................................................... 74

5 Basic Service Configuration ............................................................................................... 77

6 Performance Optimization ................................................................................................. 84

7 SAP HANA Database Installation ..................................................................................... 88

Issue 02 (2017-04-10) Huawei Proprietary and Confidential v

7.2 Installing a SAP HANA Database ..................................................................................................................................... 90

8 SAP HANA Database Uninstallation .............................................................................. 108

A ntp.conf .............................................................................................................................. 112

Issue 02 (2017-04-10) Huawei Proprietary and Confidential vi

1.1 Hardware Planning

Table 1-1 Hardware planning

RH5885H Rack server Provides computing resources.

5500 V3 Storage system Provides the Network File System

CE6800 10GE switch Provides service and high availability

/ (Optional) Domain Provides the Network Time Protocol

/ (Optional) Management Provides the device management

Cable Power cable Connects hardware devices or used for

1.2 Software Planning

Issue 02 (2017-04-10) Huawei Proprietary and Confidential 1

Table 1-2 Software planning

Software Name and Version Source Description

SLE-12-SP1-SAP-DVD-x86_64-G https://www.suse.com/ Customized SAP

multipath-tools-0.5.0-46.1.x86_64. https://www.suse.com/ Multipath

kernel-default-3.12.67-60.64.24.1. https://www.suse.com/ SUSE kernel

IMDB_SERVER100_122_5-10009 https://launchpad.support.sap. HAHA database

1.3 Capacity Planning

VD0 — — 1GB Ext4 /boot Standard Partition

lv_root vg_os Remaining Ext4 /

Issue 02 (2017-04-10) Huawei Proprietary and Confidential 2

1.3.2 5500V3 Capacity Planning for RH5885 H V3

/hana/data xfs 3 x RAM 6 TB SAN Used for a

/hana/log xfs >=512G 512 GB SAN Used for a

Partition File System Partition Partition Source Description

/hana/shar nfs 2x RAM(every 4 TB File engine Used for a

1.3.3 5500V3 Capacity Planning for RH8100 V3

/hana/data xfs 3 x RAM 12 TB SAN Used for a single

/hana/log xfs >=512G 512 GB SAN Used for a single

/hana/shared nfs 2x RAM(every 8 TB File Used for a

Issue 02 (2017-04-10) Huawei Proprietary and Confidential 3

1.4 Storage Planning

DiskDomain_Shared 0 8 SAS, 900G

DiskDomain _Data_1 1 12 SAS, 900G

DiskDomain _Data_3 3 12 SAS, 900G

DiskDomain _Log 4 8 SSD, 600G