user guide (console) - deutsche telekom · the sap hana studio provides management, monitoring, and...

SAP HANA

User Guide (Console)

Issue 02

Date 2016-10-29

Contents

1 Introduction.................................................................................................................................... 11.1 About This Document.................................................................................................................................................... 11.2 Introduction to SAP HANA........................................................................................................................................... 11.3 SAP HANA and Public Cloud........................................................................................................................................31.4 Common Concepts......................................................................................................................................................... 41.4.1 Node and Role............................................................................................................................................................. 41.4.2 Scale-up and Scale-out................................................................................................................................................ 61.4.3 Software Packages.......................................................................................................................................................6

2 Deployment.................................................................................................................................... 92.1 Deployment Scenarios....................................................................................................................................................92.1.1 Single-Node Scenario Where HA Is Not Required................................................................................................... 102.1.2 Single-Node Scenario Where HA Is Required.......................................................................................................... 122.1.3 Cluster Scenario (Single NFS Server Deployed)...................................................................................................... 142.1.4 Cluster Scenario (Two NFS Servers Deployed to Work in Active/Standby Mode)..................................................162.2 Data Planning............................................................................................................................................................... 182.2.1 HANA Nodes............................................................................................................................................................ 182.2.2 Other Nodes...............................................................................................................................................................212.2.3 Network Planning...................................................................................................................................................... 222.3 Preparing for Resources................................................................................................................................................302.3.1 Software and Tools.................................................................................................................................................... 312.3.2 License.......................................................................................................................................................................312.3.3 Creating a VPC..........................................................................................................................................................312.3.4 Applying for a Subnet and Configuring a Security Group........................................................................................322.4 Creating ECSs...............................................................................................................................................................342.4.1 Creating a HANA ECS..............................................................................................................................................342.4.2 Creating an SAP HANA Studio ECS........................................................................................................................ 392.4.3 Creating a NAT Server.............................................................................................................................................. 412.4.4 Creating an NFS Server.............................................................................................................................................432.4.5 Configuring SSH Switching Permissions..................................................................................................................462.4.6 Configuring the Mapping Between HANA ECSs and IP Addresses........................................................................ 472.5 Installing SAP HANA (Single-Node Deployment Without HA Required)................................................................. 482.5.1 Formatting a Disk...................................................................................................................................................... 482.5.2 Installing the SAP HANA Software..........................................................................................................................49

SAP HANAUser Guide (Console) Contents

Issue 02 (2016-10-29) ii

2.5.3 Installing the SAP HANA Studio on a Windows ECS..............................................................................................542.5.4 Installing the SAP HANA Studio on a Linux ECS................................................................................................... 552.5.5 Connecting SAP HANA Nodes to the SAP HANA Studio...................................................................................... 572.5.6 Configuring the Backup Path.................................................................................................................................... 622.6 Installing SAP HANA (Single-Node Deployment with HA Required)....................................................................... 652.6.1 Formatting a Disk...................................................................................................................................................... 652.6.2 Configuring Time Synchronization........................................................................................................................... 672.6.3 Installing the SAP HANA Software..........................................................................................................................692.6.4 Installing the SAP HANA Studio on a Windows ECS..............................................................................................732.6.5 Installing the SAP HANA Studio on a Linux ECS................................................................................................... 752.6.6 Connecting SAP HANA Nodes to the SAP HANA Studio...................................................................................... 772.6.7 Configuring the Backup Path.................................................................................................................................... 812.6.8 Configuring HANA HA............................................................................................................................................ 842.7 Installing SAP HANA (Cluster Deployment and Single NFS Server Deployed)........................................................872.7.1 Formatting the Disks Attached to an NFS Server..................................................................................................... 872.7.2 Formatting a HANA Disk..........................................................................................................................................882.7.3 Configuring Time Synchronization........................................................................................................................... 912.7.4 Installing the SAP HANA Software..........................................................................................................................932.7.5 Installing the SAP HANA Studio on a Windows ECS..............................................................................................982.7.6 Installing the SAP HANA Studio on a Linux ECS................................................................................................. 1002.7.7 Connecting SAP HANA Nodes to the SAP HANA Studio.................................................................................... 1022.7.8 Configuring the Backup Path.................................................................................................................................. 1062.8 Installing SAP HANA (Cluster Deployment and Two NFS Servers Deployed to Work in Active/Standby Mode). 1092.8.1 Configuring NFS Servers to Be Trusty to Each Other............................................................................................ 1092.8.2 Formatting the Disks Attached to an NFS Server....................................................................................................1102.8.3 Configuring HA on NFS Servers.............................................................................................................................1132.8.4 Formatting a HANA Disk........................................................................................................................................1242.8.5 Configuring Time Synchronization......................................................................................................................... 1272.8.6 Installing the SAP HANA Software........................................................................................................................1292.8.7 Installing the SAP HANA Studio on a Windows ECS............................................................................................1342.8.8 Installing the SAP HANA Studio on a Linux ECS................................................................................................. 1352.8.9 Connecting SAP HANA Nodes to the SAP HANA Studio.................................................................................... 1372.8.10 Configuring the Backup Path................................................................................................................................ 142

3 FAQs.............................................................................................................................................1463.1 What Should I Do If I Cannot Switch to an ECS or HANA ECS Using SSH?......................................................... 146

4 Appendix.....................................................................................................................................1484.1 Logging In to an ECS or HANA ECS Using VNC....................................................................................................1484.2 Obtaining the Password for Logging In to a Windows ECS...................................................................................... 1514.3 Logging In to a Linux ECS Using an SSH Key......................................................................................................... 1534.4 Querying the NIC IP Address of an ECS................................................................................................................... 154

A Change History......................................................................................................................... 156


Issue 02 (2016-10-29) iii

B Glossary...................................................................................................................................... 157


Issue 02 (2016-10-29) iv

1 Introduction

1.1 About This DocumentThis document provides instructions for you to prepare resources (such as ECSs and networkresources) on the Open Telekom Cloud platform, and install SAP HANA.

If you have any trouble installing and using SAP HANA due to its own problems, contact theSAP technical support.

1.2 Introduction to SAP HANA

What Is SAP HANA?

SAP High-Performance Analytic Appliance (SAP HANA) is a real-time data computingplatform launched by SAP in June 2011 for commercial use globally. Based on in-memorycomputing technologies, SAP HANA supports high-performance data query, allowing you toquery and analyze a large volume of real-time service data.

SAP HANA has the following features:

l Rapid data processing

SAP HANA data is stored in the in-memory database (IMDB), which features rapid datainput/output (I/O). Success stories show that the data processing rate provided by SAPHANA is 1,000 or even 10,000 times faster than that provided by customers' originaldatabase systems.

l Support for online analytical processing (OLAP) and online transaction processing(OLTP)

OLAP is a main application in data warehouse (DWH) systems. It supports complexanalysis, focuses on decision support, and provides query results that are easy tounderstand.

OLTP is a main application of traditional relational databases. It processes basic androutine transactions, such as banking transactions.

l Support for both structured and unstructured data

SAP HANAUser Guide (Console) 1 Introduction

Issue 02 (2016-10-29) 1

Structured data is a type of information represented using a unified structure, such asdigits and symbols. The other data that cannot be represented using a unified structure iscalled unstructured data, such as texts, images, audio, and HTML.

l Various peripheral application software

The application software includes data replication (DR) and business intelligence (BI).

l Structured query language (SQL), multidimensional expressions (MDX), and BIconsumer services (BICS) interfaces for the application layer

l Support for multiple data importing modes

Figure 1-1 shows the SAP HANA architecture.

Figure 1-1 SAP HANA architecture

SAP HANA Application Scenarios

SAP HANA applies to following scenarios:

l Accelerator for other databases

l Data source for report analysis

l OLAP DWH

l OLTP database

l Unified SAP database platform


Issue 02 (2016-10-29) 2

1.3 SAP HANA and Public Cloud

Why Deploying SAP HANA on the Public Cloud Has Become a Trend?

Traditional SAP HANA encounters the following issues:

l High costDuring software development, R&D engineers must commission the software with theSAP HANA system. After the development, test engineers must test the compatibilitybetween the software and the SAP HANA. The SAP HANA system must be purchased,though it is only used for software development and test, increasing operating expense(OPEX).

l Low deployment efficiencyThe duration from the time when you purchase the SAP HANA system to the time whenyou complete the deployment requires several days. This wastes time and manpower.

l Difficult expansionBefore expanding your SAP HANA system, you must purchase hardware and deployboth hardware and software. This requires longer time than that required for the initialdeployment.

l Inflexible configurationA set of SAP HANA system cannot be concurrently used by DEV, TST, and TRN. Toadapt to these application scenarios, you must change the HANA deployment mode. Thiswastes time and manpower.

Deploying the SAP HANA system on Open Telekom Cloud makes full use of ECSadvantages and brings you the following benefits:

l Low costYou only need to purchase the HANA resources required in such scenarios as DEV, TST,and TRN. This significantly reduces purchasing costs.

l High deployment efficiencyThe time required for deploying the HANA system on Open Telekom Cloud has beenshortened from several days to several hours. This significantly improves deploymentefficiency and reduces manpower costs.

l Simple expansionOn Open Telekom Cloud, you can flexibly expand the capacity of a single node orexpand resources from a single node to a cluster.

l Flexible configurationIf your HANA system is required to apply in such scenarios as DEV, TST, and TRN, youcan purchase different HANA deployment modes to suit the application requirements.

Relationships Between SAP HANA and Public Cloud Servicesl Elastic Cloud Server (ECS)

SAP HANA software is deployed on both ECSs and HANA ECSs. SAP HANA Studioand NAT server are deployed on ECSs. SAP HANA and NFS server are deployed onHANA ECSs.


Issue 02 (2016-10-29) 3

NOTE

l In SAP HANA cluster deployment mode, the NFS server shares its log and data volumes withall HANA nodes.

l A HANA ECS is a type of high-performance ECS.

l For details about the SAP HANA Studio and NAT server, see section Node and Role.

l Elastic Volume Service (EVS)All the ECSs used in SAP HANA scenarios have EVS disks attached.

l Virtual Private Cloud (VPC)All ECSs in SAP HANA scenarios locate in the same VPC. They are isolated fornetwork security using VPC subnets and network groups.

l Image Management Service (IMS)Image files are required for creating HANA ECSs and other ECSs.

1.4 Common Concepts

1.4.1 Node and Role

HANA Node

An SAP HANA system consists of one or multiple HANA nodes.

HANA nodes are logical units that constitute a HANA system. A HANA node contains theCPU, memory, and storage such as log volumes, data volumes, shared volumes, and backupvolumes) resources with specified specifications, as shown in Figure 1-2.

Figure 1-2 HANA Node

HANA Studio

The SAP HANA Studio provides management, monitoring, and information modeling of theHANA system. It can also function as a client and provides capabilities to access user data.The information that the SAP HANA Studio provides includes the system information (suchas software version), alarm information (generated by Statistics Server), and statistics of keysystem resources.

NAT Server

Provides the capability to switch to the HANA ECS using SSH. It allows you to switch to aHANA ECS from the NAT server using Secure Shell (SSH).


Issue 02 (2016-10-29) 4

NFS ServerProvides the file sharing capability. You can bind the shared and backup volumes to the NFSserver and share them with the HANA node.

HANA RolesIn SAP HANA cluster deployment mode, the roles assigned to HANA node are shown inFigure 1-3.

Figure 1-3 Roles assigned to HANA nodes

Each HANA node has the NameServer and IndexServer processes. Table 1-1 provides theroles of the processes.

Table 1-1 HANA roles

Process Type Description

NameServer ConfiguredRole

Initially configured rolesl MASTER: functions as a global transaction

coordinator, which coordinates global transactionsand stores the global metadata of the informationabout the computing node cluster. A cluster has threeMASTER nodes configured, but only one of them isactivated.

l SLAVE: An SAP HANA cluster can have one ormultiple SLAVE nodes configured in a distributedarchitecture to cache metadata and perform databaseoperations assigned by the MASTER node. A clusterhas multiple SLAVE nodes.

Actual Role Activated roles due to the election mechanisml MASTER: activated Master node elected from the

configured Master nodesl SLAVE: nodes except MASTER nodes


Issue 02 (2016-10-29) 5

Process Type Description

IndexServer ConfiguredRole

Initially configured rolesl WORKER: nodes that are running and performing

database operationsl STANDBY: takes over services of a faulty node. A

cluster can have no or any number of STANDBYnodes, and one STANDBY node by default. Innormal cases, software on the node is running, butthe node's memory database has no data and cannotprocess services. The STANDBY node takes overservices of a faulty node automatically.

Actual Role Activated roles due to the election mechanisml MASTER: node elected from WORKER nodes It is

the same as the MASTER node in Name Server.l SLAVE: WORKER nodes except the MASTER

nodesl STANDBY: same as parameter Config Role in Index

Server Any node can be the STANDBY node due tomultiple times of service switchovers.

1.4.2 Scale-up and Scale-outSAP HANA nodes can be expanded in scale-up or scale-out mode.

l Scale-up modeAlso called single-node system mode, in which an SAP HANA system contains only onevalid node. If high availability (HA) is required, construct such architecture using twosingle nodes through system replication. In scale-up mode, when the system requiresexpansion, add CPUs, memory capacity, and hard disks to the node.Open Telekom Cloud does not support expansion for a node on which SAP HANA isrunning.

l Scale-out modeAlso called cluster system mode, in which an SAP HANA system contains multiplenodes. In scale-out mode, when the system requires expansion, add more nodes to thesystem.

1.4.3 Software PackagesThe MASTER and SLAVE nodes of an SAP HANA system require the deployment ofdifferent software packages, as shown in Figure 1-4.


Issue 02 (2016-10-29) 6

Figure 1-4 Software packages deployed on SAP HANA nodes

Software deployed on a MASTER node is as follows:

l SAP HANA client: database client software, which provides database access interfaces,such as the open database connectivity (ODBC) interface.

l SAP HANA database: core software package of the SAP HANA system, whichimplements the IMDB.Key processes running in the SAP HANA database are as follows:– Daemon: monitors processes.– Nameserver: cluster management process, which maintains cluster status and

controls switchovers for clusters.– Preprocessor: pre-processes structured query language (SQL) statements.– Indexserver: carries out operations on databases, including saving and computing

data.– Statisticsserver: collects and reports the HANA database running data. This

process runs only on the MASTER node.– Xsengine: HTTP service process, which allows you to gain access to the SAP

HANA system using HTTP or HTTPS interfaces.l SAP SMD agent: unified system management agent, which manages the SAP HANA

system in the entire SAP integration solution.l SUM for SAP HANA: software upgrade manager, which allows the MASTER node to

automatically access the SAP software update platform and upgrade the SAP HANA


Issue 02 (2016-10-29) 7

software deployed on all MASTER, SLAVE, and STANDBY nodes. The OS and driveof the software upgrade manager are installed and upgraded by hardware vendors.

l SAP host agent: host agent, which runs the operation commands remotely issued to nodesoftware, such as restarting or stopping a node.

l SAPCAR: compression and decompression software used by SAP. The patch packagesand small software downloaded from the SAP website in .car or .sar format can bedecompressed using SAPCAR.

The software deployed on other nodes includes SAP host agent, SAP HANA client, SAPHANA database, and SAP SMD agent.


Issue 02 (2016-10-29) 8

2 Deployment

2.1 Deployment ScenariosSAP HANA can be deployed in the following scenarios:

l Single-node deployment: applies in OLTP scenarios. You can choose HA configurationas required. SAP HANA receives and processes data quickly, provides processing resultsin a short period of time, and rapidly responds to user operations.

l Cluster deployment: applies in OLAP scenarios. As a data warehouse, SAP HANAoffers support for decision-makers and senior managers. It can quickly and flexiblyprocess complex queries on a large amount of data based on the analysts' requests. It canalso provide decision makers with the query results intuitively and clearly. Using SAPHANA, decision makers can obtain accurate information about the enterprise operatingstatus, learn object demands, and make correct decisions.

Table 2-1 lists recommended deployment modes based on application scenarios.

l Production (PRD): indicates the production environment where HANA is formally used.l Quality Assure (QAS): indicates the quality assurance scenario where HANA functions,

performance, and reliability are fully verified.l Development (DEV): indicates the development scenario where the development

engineers configure and verify the compatibility between application software and SAPHANA and continuously optimize the application software.

l Training (TRN): indicates the training and demonstration scenario where you provide atraining or demonstration after deploying HANA.

l Test (TST): indicates the test scenario where the development engineers test applicationsoftware and HANA to verify the functions of application software after applicationsoftware development is complete.

SAP HANAUser Guide (Console) 2 Deployment

Issue 02 (2016-10-29) 9

NOTE

Open Telekom Cloud provides secure cloud environments, which help business users or developers inQAS or DEV scenarios to develop better and more lightweight applications within a shorter period oftime.

In Suite on HANA (SoH) scenario, SAP HANA works with SAP business suites, such as EnterpriseResource Planning (ERP) or Customer Requirement Management (CRM). In this scenario, SAP HANAprovides OLTP functions. The SAP HANA process latency is the key concern.

In Business Warehouse on HANA (BWoH) scenario, SAP HANA works with SAP Business Warehouse.In this scenario, SAP HANA provides OLAP functions and supports rapid computing and analyzing onmassive data. The SAP HANA processing performance and the network bandwidths between SAPHANA nodes are the key concern.

Table 2-1 Application scenarios and deployment modes

Scenario SoH BWoH (Single-Node) BWoH (Cluster)

PRD Single-node scenariowhere HA is required

Single-node scenariowhere HA is required

Cluster scenariowhere two NFSservers are deployed

QAS Single-node,regardless of whetherHA is required or not

Single-node, regardlessof whether HA isrequired or not

Single-node scenariowhere HA is notrequired or clusterscenario where twoNFS servers aredeployed

DEV Single-node scenariowhere HA is notrequired

Single-node scenariowhere HA is notrequired


TRN Single-node scenariowhere HA is notrequired



TST Single-node scenariowhere HA is notrequired



2.1.1 Single-Node Scenario Where HA Is Not RequiredFigure 2-1 shows the single-node scenario where HA is not required.


Issue 02 (2016-10-29) 10

Figure 2-1 Single-node scenario where HA is not required

The concepts involved in the preceding figures are as follows:

l VPC network: All SAP HANA nodes are deployed within a VPC network, and all ECSsin the HANA system belong to the same AZ to ensure network security.

l Public subnet:– Network Address Translation (NAT) instance ECS: allows you to access HANA

ECSs using Secure Shell (SSH).– SAP HANA Studio ECS: runs the SAP HANA Studio software. You can use the

Remote Desktop Protocol (RDP) or SSH to access the SAP HANA Studio ECS andmanage the HANA system.

l Private subnet:HANA ECS: used for deploying the SAP HANA software. A HANA ECS has thefollowing disks attached:– OS disk: provides the directory for installing the OS.– Data volume: periodically stores the data transmitted from the SAP HANA IMDB

(a database running in high-performance memory). The period is 5 minutes bydefault.

– Log volume: stores the data triggered by an event. When an event, for example, arecord or a batch of records are updated, is triggered for the server IMDB, thesystem will write the latest IMDB data into the log volume.

– Shared volume: stores the SAP HANA installation software and HANA databaselog files.

– Backup volume: stores backup files of the data and log volumes.

Figure 2-2 shows the deployment flowchart in the single-node scenario where HA is notrequired.


Issue 02 (2016-10-29) 11

Figure 2-2 Deployment flowchart in the single-node scenario where HA is not required

2.1.2 Single-Node Scenario Where HA Is RequiredFigure 2-3 shows the single-node scenario where HA is required.

NOTE

In the single-node scenario where HA is required, active/standby switchovers can only be manuallyperformed.


Issue 02 (2016-10-29) 12

Figure 2-3 Single-node scenario where HA is required

The concepts involved in this scenario are the same as those involved in Single-NodeScenario Where HA Is Not Required. The differences between the two deployment modesare as follows: In the single-node scenario where HA is required, two separate HANA nodesconnect to the SAP HANA Studio for management. In addition, the two nodes synchronizedata and implement HA using system replication.

Figure 2-4 shows the deployment flowchart in the single-node scenario where HA isrequired.


Issue 02 (2016-10-29) 13

Figure 2-4 Deployment flowchart in the single-node scenario where HA is required

Compared with the mode in which HA is not required in the single-node scenario, the modein which HA is required has the following requirements:

l You must create two HANA ECSs and synchronize time, format disks, and install theSAP HANA software on them.

l The two HANA ECSs must connect to the SAP HANA Studio.l You must manually configure HA on the two HANA ECSs using system replication.

2.1.3 Cluster Scenario (Single NFS Server Deployed)Figure 2-5 shows the cluster scenario where a single NFS server is deployed.


Issue 02 (2016-10-29) 14

Figure 2-5 Cluster scenario where a single NFS server is deployed

The concepts involved in this scenario are the same as those involved in Single-NodeScenario Where HA Is Not Required in addition to the following remarks:

l Cluster scenario: Three to eight HANA ECSs are required to constitute a cluster. Amongthese ECSs, one functions as the STANDBY node, and the others are WORKER nodes.

l Network File System (NFS) server: One HANA ECS is required to provide the filesharing service. The shared and backup volumes are provided by the NFS server forsharing with HANA ECSs.

Figure 2-6 shows the deployment flowchart in the cluster scenario where one NFS server isrequired.


Issue 02 (2016-10-29) 15

Figure 2-6 Deployment flowchart in the cluster scenario where one NFS server is required

2.1.4 Cluster Scenario (Two NFS Servers Deployed to Work inActive/Standby Mode)

Figure 2-7 shows the cluster scenario where two NFS servers are deployed to work in active/standby mode.


Issue 02 (2016-10-29) 16

Figure 2-7 Cluster scenario where two NFS servers are deployed to work in active/standbymode

The concepts involved in this scenario are the same as those involved in Cluster Scenario(Single NFS Server Deployed) in addition to the following remarks:

The two NFS servers constitute a cluster, which provides the file sharing service for theHANA cluster.

Figure 2-8 shows the deployment flowchart in the cluster scenario where two NFS servers aredeployed to work in active/standby mode.


Issue 02 (2016-10-29) 17

Figure 2-8 Deployment flowchart in the cluster scenario where two NFS servers are deployedto work in active/standby mode

2.2 Data PlanningBefore installing the SAP HANA, you must plan the following data:

l Data of HANA nodes: includes the OSs, specifications, and disk capacities of the HANAnodes used in SoH and BWoH scenarios.

l Data of other nodes: includes the OSs, specifications, and disk capacities of the HANAStudio, NAT server, and NFS servers.

l Network data: includes subnets and security group rules.l SAP HANA installation data: planned based SAP HANA requirements.

2.2.1 HANA NodesSAP poses specific requirements on HANA ECSs depending on application scenario.


Issue 02 (2016-10-29) 18

NOTE

The time zone of the server on which SAP NetWeaver is deployed must be the same as that of SAPHANA nodes, excepting the specifications described in this section.

Specifications in SoH Scenario

In SoH scenario, SAP HANA works with SAP business suites, such as ERP or CRM. In thisscenario, SAP HANA provides OLTP functions. The SAP HANA process latency is the keyconcern.

Table 2-2 lists the requirements on HANA ECSs in SoH scenario.

NOTE

The data volume capacity is three times as that of the memory size. However, this capacity can bechanged in public cloud scenarios, depending on the communication with the SAP support personnel.

Table 2-2 Requirements on HANA ECSs in SoH scenario

Flavor Name e1.xlarge e1.2xlarge e1.4xlarge e1.8xlarge

vCPUs 4 8 16 32

Memory (GB) 128 256 512 1024

OS Disk (GB) 100 100 100 100

Log Volume(GB)

64 128 512 512

Data Volume(GB)

384 768 1536 3072

Shared Volume(GB)

128 256 512 1024

Backup Volume(GB)

The backup disk capacity can be planned based on servicerequirements. The recommended value is at least three times as that ofthe memory size.

Specifications in BWoH Scenario

In BWoH scenario, SAP HANA works with SAP Business Warehouse. In this scenario, SAPHANA provides OLAP functions and supports rapid computing and analyzing on massivedata. The SAP HANA processing performance and the network bandwidths between SAPHANA nodes are the key concern.

Table 2-3 lists the requirements on HANA ECSs in BWoH scenario.

Table 2-3 Requirements on HANA ECSs in BWoH scenario

Flavor Name e2.2xlarge e2.3xlarge e2.6xlarge e2.12xlarge

vCPUs 8 12 24 48


Issue 02 (2016-10-29) 19

Memory (GB) 128 256 512 1024

OS Disk (GB) 100 100 100 100

Log Volume(GB)

64 128 512 512

Data Volume(GB)

384 768 1536 3072

Shared Volume(GB)

128 256 512 1024

Backup Volume(GB)

The backup disk capacity can be planned based on servicerequirements. The recommended value is at least three times as that ofthe memory size.

Requirements on OSs and Disks

Table 2-4 lists the requirements on HANA ECS disks.

NOTE

l HANA ECS volumes include log volumes, data volumes, shared volumes, and backup volumes.

l A shared disk can be attached to multiple ECSs at the same time, while a non-shared disk can onlybe attached to one ECS.

Table 2-4 Requirements on HANA ECS disks

Scenario Specifications

OS SUSE Linux Enterprise Server 11 SP4 for SAP

Available diskcapacity

Complies with the specifications specified in Table 2-2 and Table 2-3.

Single-nodescenario whereHA is notrequired

One HANA ECS with the following five disks attached is required:l OS disk: a non-shared disk in ext3 format.l Log volume: a shared disk in xfs format.l Data volume: a shared disk in xfs format.l Shared volume: a non-shared disk in xfs format.l Backup volume: a non-shared disk in ext3 format.

Single-nodescenario whereHA is required

Two HANA ECSs are required, each of which has the following fivedisks attached:l OS disk: a non-shared disk in ext3 format.l Log volume: a shared disk in xfs format.l Data volume: a shared disk in xfs format.l Shared volume: a non-shared disk in xfs format.l Backup volume: a non-shared disk in ext3 format.


Issue 02 (2016-10-29) 20

Scenario Specifications

Cluster Three to eight HANA ECSs are required to constitute a cluster.Among these ECSs, one functions as the STANDBY node, and theothers are WORKER nodes.The STANDBY node requires only one OS disk in ext3 formatattached. The WORKER nodes require the following three disksattached:l OS disk: a non-shared disk in ext3 format.l Log volume: a shared disk in xfs format.l Data volume: a shared disk in xfs format.

2.2.2 Other NodesOther nodes include the NAT server, SAP HANA Studio, and NFS server nodes. Table 2-5lists the requirements on these nodes.

Table 2-5 Data planning for other nodes

Node Specifications

SAP HANA Studio l OS:NOTE

Based on service requirements, use a Windows or Linux ECS to deploythe SAP HANA Studio.

– Windows: All Windows Server 2008 and Windows Server2012 OSs in the public image list of the Open Telekom Cloudcan be used.

– Linux: SUSE Linux Enterprise Server 11 SP4l Flavor: s1.xlarge (4 vCPUs and 16 GB memory capacity)l Disk: 80 GB system disk

NAT server l OS:SUSE Linux Enterprise Server 11 SP4

l Flavor: s1.medium (1 vCPU and 4 GB memory capacity) orhigher

l Disk: 40 GB system disk


Issue 02 (2016-10-29) 21

Node Specifications

NFS server The NFS server is required only in cluster scenarios.l OS:

SUSE Linux Enterprise Server 11 SP4 for SAPl Flavor: e1.xlarge (4 vCPUs and 128 GB memory capacity)l Disk:

NOTEIf two NFS servers are required to work in active/standby mode, each typeof the shared, backup, and SBD volumes requires one for the two NFSservers.

– System disk: 100 GB, a non-shared disk in ext3 format.– Shared volume: a shared disk in xfs format. The size of the

disk must comply with HANA ECS requirements. For details,see section HANA Nodes.

– Backup volume: a shared disk in ext3 format. The size of thedisk must comply with HANA ECS requirements. For details,see section HANA Nodes.

– SBD volume: 10 GB, a shared disk in ext3 format. Thisvolume is required only when NFS servers are deployed incluster and active/standby mode.

2.2.3 Network Planning

Network Plane Planning in the Single Node Scenario Where HA Is Not RequiredFigure 2-9 shows the network plane planning in the single node scenario where HA is notrequired.

NOTE

The network segments and IP addresses are for reference only.

Figure 2-9 Network plane planning in the single node scenario where HA is not required


Issue 02 (2016-10-29) 22

In this scenario, only one NIC is used for network communication.

Table 2-6 shows the planned network information.

Table 2-6 Network planning in the single node scenario where HA is not required

Parameter Description Example Value

IP address of the service orclient plane

Allows a HANA node tocommunicate with servicesoftware (such as ERP) orSAP HANA Studio clientsoftware.

HANA node: 10.0.3.2SAP HANA Studio:10.0.3.102NAT server: 10.0.3.202

Elastic IP address Allows you to access theSAP HANA Studio andNAT server.

Automatically allocated byOpen Telekom Cloud.

Network Plane Planning in the Single Node Scenario Where HA Is Required

Figure 2-10 shows the network plane planning in the single node scenario where HA isrequired.

NOTE


Figure 2-10 Network plane planning in the single node scenario where HA is required

In this scenario, only one NIC is used for network communication.

Table 2-7 shows the planned network information.


Issue 02 (2016-10-29) 23

Table 2-7 Network planning in the single node scenario where HA is required



Allows a HANA node tocommunicate with servicesoftware (such as ERP) orSAP HANA Studio clientsoftware.

HANA node: 10.0.3.2 to10.0.3.3SAP HANA Studio:10.0.3.102NAT server: 10.0.3.202



Network Plane Planning in the Cluster Scenario Where a Single NFS Server IsDeployed

Figure 2-11 shows the network plane planning in the cluster scenario where a single NFSserver is deployed.

NOTE


Figure 2-11 Network plane planning in the cluster scenario where a single NFS server isdeployed

Table 2-8 lists the entire network planning.


Issue 02 (2016-10-29) 24

Table 2-8 Network planning in the cluster scenario where a single NFS server is deployed



Specifies the IP address ofthe primary NIC plane.Allows a HANA node tocommunicate with servicesoftware (such as ERP) orSAP HANA Studio clientsoftware.NFS Server uses the primaryNIC plane to synchronizetime with the NTP server.

HANA node: 10.0.3.2 to10.0.3.6 (taking five HANAnodes as an example)NFS server: 10.0.3.101NAT server: 10.0.3.202



IP address of the internalcommunication plane

Allows HANA nodes, eachof which is equipped with asingle-root I/O virtualization(SR-IOV) NIC, to exchangedata.

HANA node: 10.0.2.2 to10.0.2.6 (taking five HANAnodes as an example)

IP address of the cloudmanagement or backupplane

Allows the shared andbackup volumes on the NFSserver to be attached to allSAP HANA ECSs.

HANA node: 10.0.1.2 to10.0.1.6 (taking five HANAnodes as an example)NFS server: 10.0.1.101

Network Plane Planning in the Cluster Scenario Where Two NFS Servers AreDeployed to Work in Active/Standby Mode

Figure 2-12 shows the network plane planning in the cluster scenario where two NFS serversare deployed to work in active/standby mode.

NOTE



Issue 02 (2016-10-29) 25

Figure 2-12 Network plane planning in the cluster scenario where two NFS servers aredeployed to work in active/standby mode

Figure 2-12 lists the planned network information.

Table 2-9 Network planning in the cluster scenario where two NFS servers are deployed towork in active/standby mode



Specifies the IP address ofthe primary NIC plane.Allows a HANA node tocommunicate with servicesoftware (such as ERP) orSAP HANA Studio clientsoftware.NFS Server uses the primaryNIC plane to synchronizetime with the NTP server.

HANA node: 10.0.3.2 to10.0.3.6 (taking five HANAnodes as an example)NFS server 1: 10.0.3.101NFS server 2: 10.0.3.102NAT server: 10.0.3.202


Issue 02 (2016-10-29) 26


Elastic IP address Allows you to access theSAP HANA Studio, NATServer, NFS Server, andHANA node.


IP address of the internalcommunication plane

Allows HANA nodes, eachof which is equipped with asingle-root I/O virtualization(SR-IOV) NIC, to exchangedata.

HANA node: 10.0.2.2 to10.0.2.6 (taking five HANAnodes as an example)NFS server 1: 10.0.2.101NFS server 2: 10.0.2.102

IP address of the cloudmanagement or backupplane

Allows the shared andbackup volumes on the NFSserver to be attached to allSAP HANA ECSs.

HANA node: 10.0.1.2 to10.0.1.6 (taking five HANAnodes as an example)NFS server 1: 10.0.1.101NFS server 2: 10.0.1.102NFS server floating IPaddress: 10.0.1.103

Security Group RulesNOTE

The network segments and IP addresses are for reference only. The following security group rules arerecommended practices. You can configure your own security group rule as you need.

Table 2-10, Table 2-11, Table 2-12, and Table 2-13 list security group rules.

NOTE

In the following table, ## stands for the SAP HANA instance ID, such as 00. Ensure that this ID is thesame as the instance ID specified when you install the SAP HANA software.

Table 2-10 Security group rules (SAP HANA)

Source Protocol Port Range Description

Inbound

10.0.3.0/24 TCP 5##13 to 5##14 Allows the SAPHANA Studio toaccess SAP HANA.

10.0.3.0/24 TCP 3##15 to 3##17 Provides ports forthe service plane.

10.0.2.0/24 TCP 3##00 to 3##10 Provides ports forinternalcommunicationbetween SAPHANA nodes.


Issue 02 (2016-10-29) 27


10.0.3.0/24 TCP 22 Allows SAP HANAto be accessed usingSSH.

10.0.3.0/24 UDP 123 Allows other serversto synchronize timewith SAP HANA.

Determined by OpenTelekom Cloud

ANY ANY Security group rulecreated by thesystem by defaultIt enables ECSs inthe same securitygroup tocommunicate witheach other.

Outbound

ANY ANY ANY Security group rulecreated by thesystem by defaultAllows all peers toaccess SAP HANA.

Table 2-11 Security group rules (SAP HANA Studio)


Inbound

0.0.0.0/0 TCP 3389 Allows users toaccess the SAPHANA Studio usingRDP.This rule is requiredonly when the SAPHANA Studio isdeployed on aWindows ECS.


Issue 02 (2016-10-29) 28


0.0.0.0/0 TCP 22 Allows users toaccess the SAPHANA Studio usingSSH.This rule is requiredonly when the SAPHANA Studio isdeployed on a LinuxECS.



Outbound

ANY ANY ANY Security group rulecreated by thesystem by defaultAllows all peers toaccess the SAPHANA Studio.

Table 2-12 Security group rules (NAT server)


Inbound

0.0.0.0/0 TCP 22 Allows users toaccess the NATserver using SSH.



Outbound


Issue 02 (2016-10-29) 29


ANY ANY ANY Security group rulecreated by thesystem by defaultAllows all peers toaccess the NATserver.

Table 2-13 Security group rules (NFS server)


Inbound

10.0.1.0/24 TCP/UDP 1 to 65535 Allows SAP HANAnodes to access theNFS server usingTCP or UDP.

10.0.3.0/24 TCP 22 Allows NFS serversto be accessed usingSSH.

10.0.3.0/24 UDP 123 Allows the NFSserver that functionsas an NTP client tocommunicate.



Outbound

ANY ANY ANY Security group rulecreated by thesystem by defaultAllows all peers toaccess the NFSserver.

2.3 Preparing for Resources


Issue 02 (2016-10-29) 30

2.3.1 Software and ToolsTable 2-14 lists the software and tools to be obtained.

Table 2-14 Required software and tools

Item Description How to Obtain

Local computer Runs a Windows OSwhich is Windows 7 orlater.

N/A

WinSCP Uploads key files toHANA ECSs.

https://www.winscp.net

PuTTY and PuTTYgen Used for logging in to aHANA ECS and runningcommands.

http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

SAP HANA SPS 11 SAP HANA installationpackage. SAP HANASPS 11 is recommended.

Access the following URL on aHANA ECS: http://obs.otc.t-systems.com/obs-sap/hana/software/

For detailed paths where the filescan be downloaded, see the sectionsdescribing how to install SAPHANA.

SAP HANA StudioNOTE

Install the required SAPHANA Studio versionbased on version mapping.

SAP HANA Studioinstallation package.

Configuration script Contains the script andconfiguration file usedfor installing andconfiguring SAPHANA.

Access the URL http://obs.otc.t-systems.com/obs-sap/hana/cfgandscript/scale_out_script.zipon a HANA ECS.

2.3.2 LicenseSAP HANA is authorized in Bring Your Own License (BYOL) mode. In this mode, you mustlog in to the SAP technical support website and apply for a license.

In addition to applying for a license, you must purchase public cloud-related resources.

2.3.3 Creating a VPC

ScenariosAll ECSs in an SAP HANA system must be in the same VPC. Therefore, you must apply aVPC for an SAP HANA system and specify the subnet segment for the VPC.


Issue 02 (2016-10-29) 31

https://support.sap.com/home.html

Procedure

Step 1 Log in to the Open Telekom Cloud management console.

Step 2 On the homepage, choose Network > Virtual Private Cloud.

Step 3 Click Create VPC on the right of the page.

Step 4 On the Create VPC page, configure VPC parameters.

The parameters are as follows:

l Name: specifies the VPC name.

l VPC CIDR: specifies the IP address segment for the VPC. The subnet segment in theVPC must be within this IP address segment. Therefore, you must configure thisparameter according to the deployment plan described in section Network Planning. Forexample, set this parameter value to 10.0.0.0/8.

l AZ: specifies the availability zone (AZ) for the VPC subnet. The AZ must support SAPHANA.

l Name: specifies the name of the default VPC subnet. You are recommended to set thisparameter value to the name of the service or client plane subnet, for example, 10.0.3.x.

l CIDR: specifies the IP address segment for the default VPC subnet. Ensure that the IPaddress segment for the default VPC subnet is within the IP address segment for theVPC subnet. Configure this parameter based on the deployment plan described in sectionNetwork Planning.

l DHCP: specifies whether Dynamic Host Configuration Protocol (DHCP) is enabled. Setthis parameter to Enabled.

l Gateway: specifies the gateway address of the subnet.

Step 5 Click Create Now to complete the VPC creation.

----End

2.3.4 Applying for a Subnet and Configuring a Security Group

Scenarios

To ensure proper communication between the ECSs in an SAP HANA system, apply a subnetfor the ECSs and configure a proper security group.

Procedure

Step 1 Apply for a subnet.

1. Log in to the Open Telekom Cloud management console.

2. On the homepage, choose Network > Virtual Private Cloud.

3. In the VPC navigation tree, choose the VPC name and switch to the VPC to which SAPHANA belongs.

4. Click Subnets on the left and then Create Subnet on the Subnets page in the right pane.The Create Subnet page is displayed, as shown in Figure 2-13.


Issue 02 (2016-10-29) 32

Figure 2-13 Create Subnet page

5. In the Create Subnet pane, configure parameters as prompted.– DHCP: Set this parameter to Enabled.– AZ: Set the AZ in which the SAP HANA ECSs locate.– Name: Configure the subnet name that is easy to identify, for example,

service_subnet.– CIDR: Configure this parameter according to the deployment plan described in

section Network Planning.– Gateway: Use the default setting for this parameter.

6. Click OK to complete the subnet configuration.7. Repeat Step 1.4 to Step 1.6 to create all required subnets according to the requirements

specified in section Network Planning.

Step 2 Set security groups.

SAP HANA, NFS server, NAT server, and SAP HANA Studio require security groups.

1. Click Security Group on the left and then Create Security Group on the right side ofthe page. The Create Security Group page is displayed, as shown in Figure 2-14.

Figure 2-14 Create Security Group page

2. Enter the security group name and click OK to complete the security groupconfiguration.Name the security group that is easy to identify, for example, studio_security_group.

3. Repeat Step 2.1 to Step 2.2 to create other security groups.4. In the security group list on the right of the page, expand the security group for which a

rule is to be added.


Issue 02 (2016-10-29) 33

5. Click Add Rule. The Add Rule page is displayed, as shown in Figure 2-15.

Figure 2-15 Add Rule page

6. Add the rule according to the requirements specified in section Network Planning.The default security group rules cannot be deleted. Figure 2-16 shows some defaultsecurity group rules.

Figure 2-16 Some default security group rules

Step 3 Repeat Step 2.4 to Step 2.6 to configure all security groups.

----End

2.4 Creating ECSs

2.4.1 Creating a HANA ECS

ScenariosSAP HANA software runs on HANA ECSs. Depending on deployment scenarios, you need tocreate one or multiple HANA ECSs for deploying the SAP HANA software.


Issue 02 (2016-10-29) 34

For details about the number of HANA ECSs to be created and their planned data, seesections Deployment Scenarios and Data Planning. If multiple HANA ECSs are created incluster scenarios, you need to create multiple HANA ECSs which will function as theWORKER nodes, and create another one HANA ECS which will function as the STANDBYnode.

Procedure

Step 1 On the Open Telekom Cloud management console, choose Computing > Elastic CloudServer to enter the Elastic Cloud Server page.

Step 2 Click Create HANA ECS on the right. The Create HANA ECS page is displayed.

Step 3 Configure the parameters listed in Table 2-15.

Table 2-15 HANA ECS parameters

Parameter Description

ECS Name Specify the ECS name.When you create ECSs in batches, the ECS Name isgenerated automatically in ascending order based on theQuality value that you filled in. For example, if you fillhana in ECS Name, the first ECS is hana-0001, and thesecond ECS is hana-0002.

AZ Specify the AZ in which HANA ECSs locate. The AZmust support SAP HANA. Choose the AZ as required.All ECSs in the HANA system must be within the sameAZ.

ECS Type Retain the default setting Large-memory for HANA ECSType.

vCPU and Memory Set these parameters as required.For details, see section HANA Nodes.

Image Type and Image Select Public Image and an SAP HANA ECS image thatmatches the HANA ECS OS, SUSE Linux EnterpriseServer 11 SP4 for SAP.


Issue 02 (2016-10-29) 35


Disk l In single-node scenarios, regardless of whether HA isrequired, a total of five disks are required: one is thesystem disk, and the other four ones are data disks. Thedata disks are as follows:– Log volume: a shared disk– Data volume: a shared disk– Shared volume: a non-shared disk– Backup volume: a non-shared disk

l In cluster deployment mode, a total of three disks arerequired: one system disk, and two data disks. The datadisks are as follows:NOTE

If a STANDBY node is created in cluster deployment mode,only a system disk is required. In such a case, you must deletethe two shared volumes that are selected by default.

– Log volume: a shared disk– Data volume: a shared disk

If additional disks are required, you can click Add DataDisk to add more disks.For details about disk capacities, see section HANANodes.

VPC and Security Group Use the VPC and security group that are created in sectionApplying for a Subnet and Configuring a SecurityGroup.

NIC Determine the number of NICs according to thedeployment plan provided in section Network Planning.l The first NIC is the primary NIC, which is the service

or client plane NIC.l The second NIC is the internal communication plane

NIC, which is required only in cluster scenarios.l The third NIC is the cloud management or backup

plane NIC, which is required only in cluster scenarios.

EIP Do not bind an elastic IP address to the HANA ECS.


Issue 02 (2016-10-29) 36


Key Pair In this mode, the Secure Shell (SSH) key certificate is usedfor authenticating users who attempt to log in to HANAECSs. To do so, click View Key Pair and create a key pairon the Key Pair page.Ensure that the HANA ECSs/ECSs where SAP HANA,SAP HANA Studio, NFS servers, and NAT servers are tobe deployed use the same key. Otherwise, SAP HANAinstallation will fail.NOTE

If you choose an existing SSH key certificate from the drop-downlist, make sure that you have saved the certificate locally.Otherwise, you may fail to log in to the HANA ECS or ECS.

To create a key, do as follows:

Click View Key Pair. On the Key Pair page that is displayed,click Create Key Pair, specify the key pair name, and click OK.In the Information dialog box that is displayed, click OK. Then,you can query and save the private key.

User Data Injection This parameter is displayed only after you click Showbehind Advanced Settings.Select Text and enter the following content in the text boxto assign permissions to user root so that the user can login to a HANA ECS using a private key through SSH:#cloud-config

disable_root: falseruncmd:- sed -i 's/^PermitRootLogin.*$/PermitRootLoginwithout-password/' /etc/ssh/sshd_config- sed -i '/^KexAlgorithms.*$/d' /etc/ssh/sshd_config- service sshd restart


Issue 02 (2016-10-29) 37


ECS Group This parameter is displayed only after you click Showbehind Advanced Settings.Specifies a HANA ECS group. When you create ECSs, thesystem will allocate the HANA ECSs in the same servergroup to different physical servers to ensure the runningreliability of these HANA ECSs.Determine the policy of a HANA ECS group based on thescenario:l Single node without HA required: ECS Group is not

required.l Single node with HA required: The two HANA ECSs

must belong to the same ECS Group.l Cluster: All HANA ECSs must belong to the same

ECS Group.NOTE

If no ECS group is available, perform the following operations tocreate one:

Click View ECS Group. On the page that is displayed, clickCreate ECS Group, specify the ECS group name, and click OK.

Quantity Set this parameter as required.NOTE

For the HANA ECSs created in batches in cluster scenarios, theHANA ECS that functions as the STANDBY node does notrequire the data and log volumes. This configuration is differentfrom that of the HANA ECSs functioning as the WORKERnodes. Due to this requirement, you are recommended to createthe HANA ECSs that function as the WORKER nodes and thencreate the HANA ECS that functions as the STANDBY node.

Step 4 Click Create Now. On the page that is displayed, click Submit.

Step 5 The system returns to the Elastic Cloud Server page. Check the status of the created taskfrom Task Status on the right of the page.

After the HANA ECS is created, you can view the ECS from the ECS list on the right of thepage.

Step 6 Create other HANA ECSs as required.

Step 7 Change the password of user root for logging in to all HANA ECSs.

Securely keep the password of user root. In addition, ensure that the passwords of user rootfor logging in to all HANA ECSs are the same.

1. Use VNC to log in to the SAP HANA ECS as user linux, whose default password iscloud.1234.

2. Run the following command to switch to user root:sudo su -

3. Change the password of user root.passwd


Issue 02 (2016-10-29) 38

Enter the new password as prompted and confirm it.

----End

2.4.2 Creating an SAP HANA Studio ECS

Scenarios

An SAP HANA system requires an ECS for deploying the SAP HANA Studio software.

Procedure


Step 2 Click Create ECS on the right. A page for creating ECSs is displayed.


Table 2-16 ECS parameters


ECS Name Specify the ECS name.

AZ Specify the AZ in which an ECS or HANA ECS locates.Choose an AZ as required.All ECSs and HANA ECSs in the HANA system must bewithin the same AZ.

ECS Type Select General-purpose.

vCPU and Memory s1.xlarge (4 vCPUs and 16 GB memory capacity)

Image Type Select Public Image and an image as required.l Windows: All Windows Server 2008 and Windows

Server 2012 OSs in the public image list of the OpenTelekom Cloud can be used.

l Linux: SUSE Linux Enterprise Server 11 SP4

Disk Choose Common I/O and 80 GB for the system disk.


NIC Select the correct NIC based on Network Planning.

EIP Select Automatically Assign.

Bandwidth This parameter is configured only after an elastic IPaddress is bound to an ECS. Specify the communicationchannel bandwidth when using EIP. Set the parameter asrequired, for example, 30 Mbit/s.


Issue 02 (2016-10-29) 39


Key Pair Use an SSH key certificate to authenticate the user whoattempts to log in to an ECS. To do so, click View KeyPair and create a key pair on the Key Pair page.Ensure that the HANA ECSs/ECSs where SAP HANA,SAP HANA Studio, NFS servers, and NAT servers are tobe deployed use the same key. Otherwise, SAP HANAinstallation will fail.NOTE


If you want to create an SSH key pair, do as follows:


Inject File These parameters are displayed only after you click Showbehind Advanced Settings.Do not configure them in this scenario.

User Data Injection These parameters are displayed only after you click Showbehind Advanced Settings.l When creating a Windows ECS, you do not need to

configure this parameter.l When creating a Linux ECS, assign permissions to user

root in user data injection mode so that the user can login to an ECS using a private key through SSH.To do so, select Text and enter the following content inthe text box:#cloud-config


Quantity 1



After the ECS is created, you can view the ECS from the ECS list on the right of the page.

----End


Issue 02 (2016-10-29) 40

2.4.3 Creating a NAT Server

ScenariosIn SAP HANA systems, you must create an ECS for deploying the NAT server. You can visitthe NAT server and then switch to an SAP HANA node using SSH for fault diagnosing andlocating.

Procedure


Step 2 Click Create ECS on the right. A page for creating ECSs is displayed.


Table 2-17 ECS parameters




ECS Type Select General-purpose.

vCPU and Memory s1.medium (1 vCPU and 4 GB memory capacity) or higher

Image Type Select Public Image and an image as required.Select an image that matches the NAT server OS SUSELinux Enterprise Server 11 SP4.

Disk Choose Common I/O and 40 GB for the system disk.


NIC Select the correct NIC based on Network Planning.

EIP Select Automatically Assign.

Bandwidth This parameter is configured only after an elastic IPaddress is bound to an ECS. Specify the communicationchannel bandwidth when using EIP. Set the parameter asrequired, for example, 30 Mbit/s.


Issue 02 (2016-10-29) 41


Key Pair Use an SSH key certificate to authenticate the user whoattempts to log in to an ECS. To do so, click View KeyPair and create a key pair on the Key Pair page.Ensure that the HANA ECSs/ECSs where SAP HANA,SAP HANA Studio, NFS servers, and NAT servers are tobe deployed use the same key. Otherwise, SAP HANAinstallation will fail.NOTE




Inject File These parameters are displayed only after you click Showbehind Advanced Settings.Do not configure them in this scenario.

User Data Injection Assign permissions to user root in user data injectionmode so that the user can log in to an ECS using a privatekey through SSH.Select Text and enter the following content in the text boxto assign permissions to user root so that the user can login to an ECS using a private key through SSH:#cloud-config


Quantity 1




----End


Issue 02 (2016-10-29) 42

2.4.4 Creating an NFS Server

ScenariosThe NFS server is required only in cluster scenarios.

In SAP HANA systems, you must create one HANA ECS for deploying the NFS server insingle-node deployment mode or two HANA ECSs for deploying the NFS servers in active/standby deployment mode. The NFS servers provide disks that can be shared with HANAnodes.

Procedure


Step 2 Click Create HANA ECS on the right. A page for creating a HANA ECS is displayed.


Table 2-18 Parameters of the HANA ECS where the NFS server is deployed




ECS Type Select Large-memory.

vCPU and Memory e1.xlarge (4 vCPUs and 128 GB memory capacity)

Image Type Select Public Image and an image as required. Choose theimage that is used to create the HANA ECS.

Disk Configure this parameter according to the deployment plandescribed in section Other Nodes.If two NFS servers are deployed to work in active/standbymode, when creating an NFS server, you must create theshared, backup, and SBD volumes. When creating theother NFS server, you do not need to create these disks.You only need to attach these disks to the other NFSserver. For details, see section Formatting the DisksAttached to an NFS Server.



Issue 02 (2016-10-29) 43


NIC When only one NFS server is deployed, a total of twoNICs are required.l The first NIC is the primary NIC, which is used on the

service or client plane. NFS Server uses the primaryNIC plane to synchronize time with the NTP server.

l The second NIC is an internal communication planeNIC. This NIC is added when you created an ECS orHANA ECS. However, this NIC will not be used.

l The third NIC is used on the cloud management orbackup plane.

When two NFS servers are deployed to work in active/standby mode, a total of three NICs are required.l The first NIC is the primary NIC, which is used on the

service or client plane.l The second NIC is the first extended NIC, which is

used on the internal communication plane forexchanging heartbeat signals between the active andstandby NFS servers.

l The third NIC is the second extended NIC, which isused on the cloud management or backup plane.

Create NICs based on the preceding requirements and thedeployment plan described in section Network Planning.

EIP Do not bind an elastic IP address to the HANA ECS.

Key Pair In this mode, the Secure Shell (SSH) key certificate is usedfor authenticating users who attempt to log in to HANAECSs. To do so, click View Key Pair and create a key pairon the Key Pair page.Ensure that the HANA ECSs/ECSs where SAP HANA,SAP HANA Studio, NFS servers, and NAT servers are tobe deployed use the same key. Otherwise, SAP HANAinstallation will fail.NOTE



Click Create Key Pair, specify the key pair name, and click OK.In the Information dialog box that is displayed, click OK. Then,you can query and save the private key.


Issue 02 (2016-10-29) 44


User Data Injection This parameter is displayed only after you click Showbehind Advanced Settings.Select Text and enter the following content in the text boxto assign permissions to user root so that the user can login to a HANA ECS using a private key through SSH:#cloud-config


ECS Group This parameter is displayed only after you click Showbehind Advanced Settings.Determine the policy of a HANA ECS group based on thescenario:l A Single NFS server: ECS Group is not required.l Two NFS servers in active/standby mode: The two

NFS servers must belong to the same ECS Group andit must be different from the ECS Group to which theHANA ECSs belong.

Quantity 1




Step 6 (Optional) Repeat Step 1 to Step 5 to create the other NFS server.

Step 7 This operation is performed only when two NFS servers are deployed to work in active/standby mode. When creating the other NFS server, you do not need to create a shared,backup, or SBD volume for it.

Step 8 Change the password of user root for logging in to the NFS server.

Step 9 Securely keep the password of user root.

1. Use VNC to log in to the SAP HANA ECS as user linux, whose default password iscloud.1234.

2. Run the following command to switch to user root:sudo su -

3. Change the password of user root.passwd


Issue 02 (2016-10-29) 45

Enter the new password as prompted and confirm it.

----End

2.4.5 Configuring SSH Switching Permissions

ScenariosTo allow SSH switchovers between HANA ECSs, NFS servers, and NAT servers, you mustconfigure the ECSs and HANA ECSs to be trusty.

Procedure

Step 1 Upload the key file to the NAT server.

1. On the local computer, generate the private key file for logging in to the NFS server.When creating the NAT server, you specify the certificate private key file (.pem file) forthe NAT server.The private key file is used to generate the private key file (.ppk file) for logging in tothe NFS server. For details, see section Logging In to a Linux ECS Using an SSH Key.

2. On the local computer, install the WinSCP software.3. Upload the certificate private key file (.pem file) to the NFS server.

Use WinSCP to upload the certificate private key file (.pem file) to the /usr directory onthe NAT server using an elastic IP address. Ensure that user root and the key file (.ppkfile) are used for authentication.

4. Use PuTTY to log in to the NAT server. Ensure that user root and the key file (.ppk file)are used for authentication.

5. Copy the certificate private key file (.pem file) to the /root/.ssh directory and rename thefile id_rsa.For example, if the original file name is private.pem, run the following command torename it:cp /usr/private.pem /root/.ssh/id_rsa

6. Run the following commands to generate a public key file:cd /root/.ssh/cat authorized_keys >>id_rsa.pubchmod 600 id_rsa

Step 2 Use the service or client plane IP address to allocate the locally stored public and private keyfiles to all HANA ECSs excepting the SAP HANA Studio. Specifically, allocate the files tothe HANA nodes and NFS servers. The NFS servers are available only in cluster scenarios.

The command is in the following format:

scp /root/.ssh/id_rsa Peer IP address:/root/.ssh/id_rsa

scp /root/.ssh/id_rsa.pub Peer IP address:/root/.ssh/

For example, if the peer IP address is 10.0.3.102, run the following commands:

scp /root/.ssh/id_rsa 10.0.3.102:/root/.ssh/id_rsa

scp /root/.ssh/id_rsa.pub 10.0.3.102:/root/.ssh/


Issue 02 (2016-10-29) 46

Step 3 Verify the switching.

Use SSH to switch from the NAT server to all ECSs and HANA ECSs excepting the SAPHANA Studio for verification. These ECSs and HANA ECSs include HANA nodes and NFSservers. The NFS servers are available only in cluster scenarios.

For example, the service or client plane IP address of the NFS server is 10.0.3.101. To switchfrom the NAT server to the NFS server, run the following command:

ssh 10.0.3.101

NOTE

After the switching, you must switch back to the NAT server. Then, verify the switching from the NATserver to other nodes.

----End

2.4.6 Configuring the Mapping Between HANA ECSs and IPAddresses

ScenariosDuring the SAP HANA installation, installation programs use ECS names forcommunication. Therefore, you must configure the mapping between the names and IPaddresses of ECSs.

Procedure

Step 1 Use PuTTY to log in to the NAT server with an elastic IP address bound. Ensure that userroot and the key file (.ppk file) are used for authentication. Then, use SSH to switch to theHANA ECS.

NOTE

In cluster scenarios, you will switch to the first HANA ECS. Then, you will perform operations on thisHANA ECS when installing SAP HANA.

Step 2 Run the following command to open the hosts file:

vi /etc/hosts

Step 3 Press i to enter editing mode and write the names and IP addresses of all SAP HANA ECSsinto the hosts file.l In single-node scenarios, IP-Address is the IP address of the service or client plane for

the HANA ECS. In cluster deployment mode, IP-Address is the IP address of theinternal communication plane for the HANA ECS.

l Both Full-Qualified-Hostname and Short-Hostname are the ECS name, for example,hana001.

The format is "IP-Address Full-Qualified-Hostname Short-Hostname".


Issue 02 (2016-10-29) 47

NOTICEIn a HANA system, you must write the mapping between all HANA node IP addresses andnode names into the hosts file.

Take the IP addresses 10.0.2.2 to 10.0.2.6 of the internal HANA communication plane for fiveHANA ECSs as an example.

The edited content is as follows:

... 10.0.2.2 hana001 hana00110.0.2.3 hana002 hana00210.0.2.4 hana003 hana00310.0.2.5 hana004 hana00410.0.2.6 hana005 hana005

Step 4 After you complete editing, press Esc, enter :x, and press Enter to exit the hosts file.

Step 5 (Optional) Repeat Step 1 to Step 4 to edit the hosts file on the other HANA ECS.

This operation is performed only in single-node scenarios where HA is required. In clusterscenarios, you can copy the hosts file to other HANA ECSs when installing SAP HANA tocomplete the configuration.

----End

2.5 Installing SAP HANA (Single-Node DeploymentWithout HA Required)

2.5.1 Formatting a Disk

Scenarios

In single-node deployment scenarios, the data disks of SAP HANA ECSs can be used onlyafter they are formatted and attached to required directories.

Procedure

Step 1 Log in a HANA ECS.

Use PuTTY to log in to the NAT server with an elastic IP address bound. Ensure that userroot and the key file (.ppk file) are used for authentication. Then, use SSH to switch to theHANA ECS.

Step 2 Format a disk.

1. Run the following command to query the disk to be formatted:fdisk -l

2. Determine the paths for the data volumes, log volumes, shared volumes, and backupvolumes according to disk capacities.


Issue 02 (2016-10-29) 48

3. Download the configuration script.

NOTE

Download the readme.txt file at http://obs.otc.t-systems.com/obs-sap/readme.txt on a localcomputer to obtain the location where the software and configuration file are stored.

wget http://obs.otc.t-systems.com/obs-sap/hana/cfgandscript/scale_out_script.zip -P /usr/sap

4. Run the following commands to switch to the folder and decompress the softwarepackage:

cd /usr/sapunzip scale_out_script.zip

5. Run the following command to modify the soh.cfg file:

vi /usr/sap/scale_out_script/soh.cfg6. Press i to enter editing mode and write the path into the file.


– log: specifies the path for the log volume.

– data: specifies the path for the data volume.

– shared: specifies the path for the shared volume.

– backup: specifies the path for the backup volume.

An example is provided as follows:log=/dev/sdddata=/dev/sdeshared=/dev/xvdbbackup=/dev/xvdc

7. After you complete editing, press Esc, enter :x, and press Enter to exit the soh.cfg file.

8. Run the following commands to switch to the directory where the soh.cfg file is storedand convert the file format:

cd /usr/sap/scale_out_scriptdos2unix installSoh.sh soh.cfg

9. Assign operation permissions to the soh.cfg file and run installSoh.sh to format disks.

chmod 777 installSoh.sh soh.cfgsh installSoh.sh

----End

2.5.2 Installing the SAP HANA Software

Scenarios

SAP HANA database software must be deployed on a HANA ECS.

Prerequisites

Required resources have been prepared. For details, see sections Preparing for Resourcesand Creating ECSs.


Issue 02 (2016-10-29) 49

Procedure

Step 1 Install the SAP HANA software.

1. Use PuTTY to log in to the NAT server with an elastic IP address bound. Ensure thatuser root and the key file (.ppk file) are used for authentication. Then, use SSH to switchto the HANA ECS on which the SAP HANA software is to be installed.

2. On the CLI, download the decompression software linux_x86_64_sapcar.zip and theSAP HANA installation package linux_x86_64_hdb.sar.

NOTE


wget http://obs.otc.t-systems.com/obs-sap/hana/software/sps11/112/sapcar/linux_x86_64_sapcar.zip -P /usr/sap

wget http://obs.otc.t-systems.com/obs-sap/hana/software/sps11/112/hdb/linux_x86_64_hdb.sar -P /usr/sap

3. Run the following commands to switch to the directory where the software packages arestored and decompress linux_x86_64_sapcar.zip:

cd /usr/sap

unzip linux_x86_64_sapcar.zip

4. Run the following command to assign execute permissions to the decompressedsoftware, for example, decompressed linux_x86_64_sapcar.zip isSAPCAR_712-80000935.EXE:

chmod +x SAPCAR_712-80000935.EXE

5. Run the following command to decompress the SAP installation package:

./SAPCAR_712-80000935.EXE -xvf linux_x86_64_hdb.sar

6. Run the following commands to decompress the generated package, for example,decompressed linux_x86_64_hdb.sar is IMDB_SERVER100_112_5-10009569.SAR:

./SAPCAR_712-80000935.EXE -xvf IMDB_SERVER100_112_5-10009569.SAR

7. Copy the generated SAP_HANA_DATABASE folder to the /hana/shared directory.

cp -R SAP_HANA_DATABASE /hana/shared

8. Run the following command to assign execute permissions to the directory:

chmod -R 777 /hana

9. Run the following command to switch to the directory where the SAP HANA softwarepackage is stored, taking /hana/shared as an example:

cd /hana/shared

10. Run the following command to enter the directory where the installation file is stored,taking SAP_HANA_DATABASE as an example:

cd SAP_HANA_DATABASE

11. Run the following command to perform the installation:

./hdbinst

The installation page is displayed, as shown in Figure 2-17.


Issue 02 (2016-10-29) 50

Figure 2-17 SAP HANA installation prompt

12. Configure parameters as prompted on the page one by one.

NOTE

– During the configuration, press Enter if you want to retain the default setting.

– If a parameter is incorrectly set and you have pressed Enter, you can press Ctrl+C to exit theconfiguration and run the ./hdbinst command to enter the installation page again.

Table 2-19 lists the parameter configuration requirements.

Table 2-19 Requirements for configuring SAP HANA installation parameters


Local Host Name Specifies the local host name.

Installation Path Specifies the installation path, which defaults to /hana/shared. The default value is recommended.

SAP HANA System ID Specifies the SAP HANA system ID, for example,S00.

Instance Number Specifies the HANA instance number, for example,00.The instance ID is used in Security Group Rules,which must be the same as the planned one.

Database Mode Specifies the database deployment mode. Retaindefault value single_container.

System Usage Specifies the HANA system type. Set this parameteras required. This parameter is stored in the global.inifile.

Location of Data VolumesSpecifies

Specifies the system data volume directory, which is /hana/data.

Location of Log Volumes Specifies the system log volume directory, which is /hana/log.

Restrict maximum memoryallocation?

Specifies whether maximum memory allocation isrestricted, which defaults to n.

Certificate Host Name Specifies the ECS name that is used to generate a self-signed SSL certificate for the SAP host agent.

System Administrator(s00adm) Password

Enter the system administrator password.


Issue 02 (2016-10-29) 51


System Administrator HomeDirectory

Use the default value.

System Administrator UserID


System Administrator LoginShell


ID of User Group Use the default value.

Database User (SYSTEM)Password

Enter the database user password.

13. After you complete the configuration, the system displays the message "Restart systemafter machine reboot?" Then, enter y and press Enter. The system displays theinstallation summary.

14. Verify that the installation information is correct. Then, enter y and press Enter to startthe SAP HANA installation after the system displays the message "Do you want tocontinue?"

After the installation is complete, the system displays the message "Installation done."

Step 2 Verify the installation.

1. Switch to the /usr/sap/$SID/HDB00/ directory.

An example is provided as follows:

cd /usr/sap/S00/HDB002. Switch to the database system administrator.

Account s00adm is displayed on the page during the installation. Run the followingcommand:

su - s00adm3. Query the database version.

If the version can be queried, the database software is installed.

./HDB -versionAfter the database is installed, the system returns the version. Figure 2-18 shows anexample.

Figure 2-18 SAP HANA version information


Issue 02 (2016-10-29) 52

4. Run the following command to switch to user root:exit

Step 3 Check whether the database process is running properly.

1. Switch to the directory where the SAP HANA installation file is stored.

For example, if the installation file is stored in SAP_HANA_DATABASE, run thefollowing command:

cd /hana/shared/SAP_HANA_DATABASE2. Run the following command to check the database process:

ps -le | grep hdbIf the process startup results similar to the information shown in Figure 2-19 arereturned, the database process is running properly.

Figure 2-19 Querying the SAP HANA database process

Step 4 Check the database startup and shutdown.

1. Run the following command to switch to the /usr/sap/$SID/HDB00/ directory:



Account s00adm is displayed on the page during the installation. Run the followingcommand:

su - s00adm3. Run the following command to start the SAP HANA database:

./HDB start4. Run the following command to stop the SAP HANA database:

./HDB stop5. Run the following command to restart the SAP HANA database:

./HDB restart6. Run the following command to switch to user root:

exit

----End


Issue 02 (2016-10-29) 53

2.5.3 Installing the SAP HANA Studio on a Windows ECS

Scenarios

The SAP HANA Studio manages SAP HANA. After SAP HANA nodes are deployed, youneed to install the SAP HANA Studio and use it to manage the SAP HANA nodes.

Prerequisitesl Required resources are available. For details, see section Preparing for Resources.

l You have created ECSs, formatted disks attached to them, and installed the SAP HANA.

l The firewall on the target ECS has been disabled.

l Remote login to the target ECS has been enabled.

Procedure

Step 1 Use the Remote Desktop Protocol (RDP) and elastic IP address to log in to the SAP HANAStudio ECS.

Use the username Administrator and the password obtained in Obtaining the Password forLogging In to a Windows ECS to log in to the SAP HANA Studio ECS.

Step 2 Launch the browser and download the decompression software windows_x86_64_sapcar.zipand the SAP HANA Studio installation package windows_x86_64_studio.zip.

NOTE

Download the readme.txt file at http://obs.otc.t-systems.com/obs-sap/readme.txt on a local computerto obtain the location where the software and configuration file are stored.

http://obs.otc.t-systems.com/obs-sap/hana/software/sps11/112/sapcar/windows_x86_64_sapcar.zip

http://obs.otc.t-systems.com/obs-sap/hana/software/sps11/112/studio/windows_x86_64_studio.zip

Step 3 Decompress windows_x86_64_sapcar.zip and windows_x86_64_studio.zip.

For example, the obtained files are SAPCAR_712-80000938.EXE in c:/windows_x86_64_sapcar/ and IMC_STUDIO2_112_5-80000323.SAR in c:/windows_x86_64_studio/.

Step 4 On the CLI, switch to the directory where SAPCAR_712-80000938.EXE is stored anddecompress the SAP HANA Studio installation package.

cd c:/windows_x86_64_sapcar

SAPCAR_712-80000938.EXE -xvf c:/windows_x86_64_studio/IMC_STUDIO2_112_5-80000323.SAR

Step 5 On the Windows page, switch to the directory where the SAP HANA Studio installationpackage is stored and double-click hdbsetup.exe to open the installation wizard page.


Issue 02 (2016-10-29) 54

Figure 2-20 SAP HANA Studio installation wizard page

Step 6 Select the installation path and click Next.

Step 7 On the Select Features page, select the features to be installed and click Next.

You are advised to select all features.

Step 8 Confirm all information on the Review & Confirm page and click Install.

Step 9 An installation page is displayed. Continue the installation. When the installation is complete,the system displays the message "You have successfully installed the SAP HANA Studio."

Step 10 Click Finish.

----End

2.5.4 Installing the SAP HANA Studio on a Linux ECS

Scenarios


This section describes how to install the SAP HANA Studio on a Linux ECS.


l You have created ECSs, formatted disks attached to them, and installed the SAP HANA.

l The firewall on the target ECS has been disabled.


Issue 02 (2016-10-29) 55

Procedure

Step 1 On the Open Telekom Cloud management console, log in to the target ECS using VNC.

The login username and password are linux and cloud.1234, respectively.

Step 2 Run the following command to switch to user root:

sudo su

Step 3 On the CLI, download the decompression software linux_x86_64_sapcar.zip and the SAPHANA Studio installation package linux_x86_64_studio.zip.

NOTE



wget http://obs.otc.t-systems.com/obs-sap/hana/software/sps11/112/studio/linux_x86_64_studio.zip -P /usr/sap

Step 4 Run the following commands to switch to the directory where the software packages arestored and decompress linux_x86_64_sapcar.zip and linux_x86_64_studio.zip:

cd /usr/sap


unzip linux_x86_64_studio.zip

Step 5 Run the following command to assign execute permissions to the decompressed software, forexample, decompressed linux_x86_64_sapcar.zip is SAPCAR_712-80000935.EXE:


Step 6 Decompress the SAP HANA Studio installation package.

For example, if decompressed linux_x86_64_studio.zip isIMC_STUDIO2_112_5-80000321.SAR, run the following command:

./SAPCAR_712-80000935.EXE -xvf IMC_STUDIO2_112_5-80000321.SAR

Step 7 Assign operation permissions to the directory where the installation packages are stored.

For example, if the directory is SAP_HANA_STUDIO, run the following command:

chmod 777 -R SAP_HANA_STUDIO

Step 8 Switch to the directory and perform the installation. The installation page is displayed, asshown in Figure 2-21.

cd SAP_HANA_STUDIO

./hdbsetup


Issue 02 (2016-10-29) 56








----End

2.5.5 Connecting SAP HANA Nodes to the SAP HANA Studio

Scenarios

SAP HANA nodes can be managed only after they are connected to the SAP HANA Studio.

This section uses a Windows ECS where the SAP HANA Studio is deployed as an example.


Issue 02 (2016-10-29) 57

Procedure

Step 1 Start the SAP HANA Studio.

On the ECS where the SAP HANA Studio is deployed, choose Start > SAP HANA > SAPHANA Studio. Then, the system displays the SAP HANA Studio management page and theWorkspace Launcher dialog box.

Figure 2-22 Workspace Launcher

Step 2 Specify the Workspace directory, select Use this as the default and do not ask me again,and click OK.

Step 3 The Security Storage dialog box is displayed, as shown in Figure 2-23. Click No.

Figure 2-23 Security Storage dialog box

Step 4 On the Overview page, click Open Administration Console to enter the SAP HANAAdministration Console page.

Step 5 Right-click the blank area under System, as shown in Figure 2-24.


Issue 02 (2016-10-29) 58

Figure 2-24 SAP HANA Administration Console page

Step 6 Choose Add System. The Specify System page is displayed, as shown in Figure 2-25.Configure parameters.

Key parameters are as follows:l Host Name: Enter the service or client plane IP address of the SAP HANA ECS.l Instance Number: Enter the number of the instance on the SAP HANA node.l Mode: Choose Single container.


Issue 02 (2016-10-29) 59

Figure 2-25 Specify System page

Step 7 Click Next to go to the System page, as shown in Figure 2-26. Choose Authentication bydatabase user and enter the username and password.

The username and password are those configured during HANA software installation. Theusername is consistently set to SYSTEM.


Issue 02 (2016-10-29) 60

Figure 2-26 System page

Step 8 Click Next and then Finish. Then, the SAP HANA Studio automatically connects to thedatabase.

If the connection fails, check whether the database instance on the SAP HANA node isrunning.

Step 9 Under System of the SAP HANA Administration Console page, double-click the node to bechecked.

Step 10 Click the Landscape tab on the right of the page and check the status of each process on theSAP HANA node.

Green indicates that the process is running properly.


Issue 02 (2016-10-29) 61

Figure 2-27 Landscape page

----End

2.5.6 Configuring the Backup Path

Scenarios

A path is required for backing up SAP HANA data.


Procedure

Step 1 On the HANA Studio ECS, choose Start > SAP HANA > SAP HANA Studio to start theSAP HANA Studio software.

Step 2 In the System area on the left, right-click the database node and choose Backup andRecovery > Open Backup Console, as shown in Figure 2-28.

Figure 2-28 Open Backup Console menu


Issue 02 (2016-10-29) 62

Step 3 Click the Configuration tab on the right and configure the backup path, as shown in Figure2-29.

NOTE

The backup path is the directory to which the backup volume is attached, that is, /hana/backup.

Click the save icon in the upper right corner to save the configuration.

Figure 2-29 Configuring the Backup Path

Step 4 In the System area on the left, right-click the database node and choose Backup andRecovery > Back Up System.... The Specify Backup Settings page is displayed.


Issue 02 (2016-10-29) 63

Figure 2-30 Specify Backup Settings page

Step 5 Use default settings and click Next. The Review Backup Settings page is displayed. Confirmconfigurations and click Finish. Then, the system starts the backup task, as shown in Figure2-31.

NOTE

According to SAP requirements, data must be backed up immediately after the HANA system isinstalled.


Issue 02 (2016-10-29) 64

Figure 2-31 Backing up data

Step 6 Click Close after the backup task is complete.

----End

2.6 Installing SAP HANA (Single-Node Deployment withHA Required)

2.6.1 Formatting a Disk

Scenarios

In single-node deployment scenarios, the data disks of SAP HANA ECSs can be used onlyafter they are formatted and attached to required directories.


Issue 02 (2016-10-29) 65

Procedure

Step 1 Log in a HANA ECS.

Use PuTTY to log in to the NAT server with an elastic IP address bound. Ensure that userroot and the key file (.ppk file) are used for authentication. Then, use SSH to switch to theHANA ECS.

Step 2 Formatting a Disk


2. Determine the paths for the data volumes, log volumes, shared volumes, and backupvolumes according to disk capacities.

3. Run the following command to download the configuration script:

NOTE



4. Run the following commands to switch to the folder and decompress the softwarepackage:cd /usr/sapunzip scale_out_script.zip

5. Run the following command to modify the soh.cfg file:vi /usr/sap/scale_out_script/soh.cfg

6. Press i to enter editing mode and write the path into the file.The parameters are as follows:– log: specifies the path for the log volume.– data: specifies the path for the data volume.– shared: specifies the path for the shared volume.– backup: specifies the path for the backup volume.An example is provided as follows:log=/dev/sdddata=/dev/sdeshared=/dev/xvdbbackup=/dev/xvdc

7. After you complete editing, press Esc, enter :x, and press Enter to exit the soh.cfg file.8. Run the following commands to switch to the directory where the soh.cfg file is stored

and convert the file format:cd /usr/sap/scale_out_scriptdos2unix installSoh.sh soh.cfg

9. Assign operation permissions to the soh.cfg file and run installSoh.sh to format disks.chmod 777 installSoh.sh soh.cfgsh installSoh.sh

Step 3 Format the data disks of the other SAP HANA ECS.


Issue 02 (2016-10-29) 66

Switch to the other SAP HANA ECS using SSH and format the data disks of the ECS byrepeating Step 1 to Step 2.

----End

2.6.2 Configuring Time Synchronization

Scenarios

Before installing SAP HANA, you must configure time synchronization on the HANA ECSswhere SAP HANA and NFS servers are to be deployed to ensure the proper running of theSAP HANA system.

l In single-node scenarios where HA is not required, only one node is used. As such, youdo not need to configure time synchronization.

l In single-node scenarios where HA is required, two nodes are used. Use either one as theclock source. The other node synchronizes time with it.

l In cluster scenarios, use the first HANA ECS as the clock source. The other HANAECSs and NFS servers synchronize time with it.

Procedure

Step 1 Configure the clock source.

1. Use PuTTY to log in to the NAT server with an elastic IP address bound. Ensure thatuser root and the key file (.ppk file) are used for authentication. Then, use SSH to switchto the HANA ECS that works as the clock source.

2. Run the following command to configure automatic NTP enabling when the NTP serverstarts:chkconfig ntp on

3. Configure the HANA ECS as the NTP server, which allows NTP clients (other HANAECSs) with specified IP addresses to synchronize time with it.Ensure that the IP addresses of other HANA ECSs are in the service or client planenetwork segment. For instructions about how to query the IP addresses of other HANAECSs, see section Querying the NIC IP Address of an ECS.vi /etc/ntp.confAn example is provided as follows:#### Miscellaneous stuff##restrict 10.0.3.3 255.255.255.0 nomodifyrestrict 10.0.3.4 255.255.255.0 nomodify...

4. Run the following command to restart the NTP service:service ntp restart

5. Run the following command to query the NTP status:ntpq -pFigure 2-32 shows an example of the command output.Ensure that the value of offset is within an appropriate range.


Issue 02 (2016-10-29) 67

NOTE

offset indicates the average time difference (s) between the ECS and the NTS. After timesynchronization is complete, the value of this parameter is generally less than 20 ms, andsometimes several hundred milliseconds.

Figure 2-32 NTP server information

Step 2 Configure NTP clients.

Configure all HANA nodes that function as NTP clients.

In single-node scenarios where HA is required, configure the NTP client on the other HANAECS.

In cluster scenarios, configure the NTP client on the NFS server and HANA nodes except theHANA node that functions as the time source.1. Log in to the HANA ECS.

Use PuTTY to log in to the NAT server with an elastic IP address bound. Ensure thatuser root and the key file (.ppk file) are used for authentication. Then, use SSH to switchto the HANA ECS.


3. Run the following command to edit the configuration file to specify an IP address for theNTP server:vi /etc/ntp.conf

4. Press i to enter editing mode and write the path for the NTP server into the configurationfile.An example is provided as follows:server 10.0.3.2

5. After you complete editing, press Esc, enter :x, and press Enter to exit the NTPconfiguration file.



NOTE


Figure 2-33 NTP client information


Issue 02 (2016-10-29) 68

8. Manually synchronize time with the NTP server.rcntp ntptimeset

9. Enable automatic time synchronization.crontab -ePress i to enter editing mode and add the following content:*/15 * * * * /usr/sbin/rcntp ntptimeset & > /dev/null; /sbin/hwclock -w


11. Run the following command to make the configuration take effect:/etc/init.d/cron restart

----End


Scenarios

SAP HANA database software must be deployed on a HANA ECS.

Prerequisites

Required resources are available. For details, see section Preparing for Resources.

Procedure


1. Use PuTTY to log in to the NAT server with an elastic IP address bound. Ensure thatuser root and the key file (.ppk file) are used for authentication. Then, use SSH to switchto the HANA ECS on which the SAP HANA software is to be installed.

2. On the CLI, download the decompression software linux_x86_64_sapcar.zip and theSAP HANA installation package linux_x86_64_hdb.sar.

NOTE


wget http://obs.otc.t-systems.com/obs-sap/hana/software/sps11/112/sapcar/linux_x86_64_sapcar.zip -P /usr/sapwget http://obs.otc.t-systems.com/obs-sap/hana/software/sps11/112/hdb/linux_x86_64_hdb.sar -P /usr/sap

3. Run the following commands to switch to the directory where the software packages arestored and decompress linux_x86_64_sapcar.zip:cd /usr/sapunzip linux_x86_64_sapcar.zip

4. Run the following command to assign execute permissions to the decompressedsoftware, for example, decompressed linux_x86_64_sapcar.zip isSAPCAR_712-80000935.EXE:chmod +x SAPCAR_712-80000935.EXE


Issue 02 (2016-10-29) 69

5. Run the following command to decompress the SAP installation package:

./SAPCAR_712-80000935.EXE -xvf linux_x86_64_hdb.sar

6. Run the following commands to decompress the generated package, for example,decompressed linux_x86_64_hdb.sar is IMDB_SERVER100_112_5-10009569.SAR:

./SAPCAR_712-80000935.EXE -xvf IMDB_SERVER100_112_5-10009569.SAR

7. Copy the generated SAP_HANA_DATABASE folder to the /hana/shared directory.

cp -R SAP_HANA_DATABASE /hana/shared

8. Run the following command to assign execute permissions to the directory:

chmod -R 777 /hana

9. Run the following command to switch to the directory where the SAP HANA softwarepackage is stored, taking /hana/shared as an example:

cd /hana/shared

10. Run the following command to enter the directory where the installation file is stored,taking SAP_HANA_DATABASE as an example:

cd SAP_HANA_DATABASE

11. Run the following command to perform the installation:

./hdbinst

The installation page is displayed, as shown in Figure 2-34.

Figure 2-34 SAP HANA installation prompt

12. Configure parameters as prompted on the page one by one.

NOTE

– During the configuration, press Enter if you want to retain the default setting.

– If a parameter is incorrectly set and you have pressed Enter, you can press Ctrl+C to exit theconfiguration and run the ./hdbinst command to enter the installation page again.

Table 2-20 lists the parameter configuration requirements.

Table 2-20 Requirements for configuring SAP HANA installation parameters


Local Host Name Specifies the local host name.

Installation Path Specifies the installation path, which defaults to /hana/shared. The default value is recommended.

SAP HANA System ID Specifies the SAP HANA system ID, for example,S00.


Issue 02 (2016-10-29) 70


Instance Number Specifies the HANA instance number, for example,00.The instance ID is used in Security Group Rules,which must be the same as the planned one.

Database Mode Specifies the database deployment mode. Retaindefault value single_container.

System Usage Specifies the HANA system type. Set this parameteras required. This parameter is stored in the global.inifile.

Location of Data VolumesSpecifies

Specifies the system data volume directory, which is /hana/data.

Location of Log Volumes Specifies the system log volume directory, which is /hana/log.

Restrict maximum memoryallocation?

Specifies whether maximum memory allocation isrestricted, which defaults to n.

Certificate Host Name Specifies the ECS name that is used to generate a self-signed SSL certificate for the SAP host agent.

System Administrator(s00adm) Password

Enter the system administrator password.

System Administrator HomeDirectory


System Administrator UserID


System Administrator LoginShell


ID of User Group Use the default value.

Database User (SYSTEM)Password

Enter the database user password.

13. After you complete the configuration, the system displays the message "Restart systemafter machine reboot?" Then, enter y and press Enter. The system displays theinstallation summary.

14. Verify that the installation information is correct. Then, enter y and press Enter to startthe SAP HANA installation after the system displays the message "Do you want tocontinue?"

After the installation is complete, the system displays the message "Installation done."

Step 2 Verify the installation.

1. Switch to the /usr/sap/$SID/HDB00/ directory.



Issue 02 (2016-10-29) 71


Account s00adm is displayed on the page during the installation. Run the followingcommand:su - s00adm

3. Query the database version.If the version can be queried, the database software is installed../HDB -versionAfter the database is installed, the system returns the version. Figure 2-35 shows anexample.

Figure 2-35 SAP HANA version information


Step 3 Check whether the database process is running properly.

1. Switch to the directory where the SAP HANA installation file is stored.For example, if the installation file is stored in SAP_HANA_DATABASE, run thefollowing command:cd /hana/shared/SAP_HANA_DATABASE

2. Run the following command to check the database process:ps -le | grep hdbIf the process startup results similar to the information shown in Figure 2-36 arereturned, the database process is running properly.

Figure 2-36 Querying the SAP HANA database process


Issue 02 (2016-10-29) 72

Step 4 Check the database startup and shutdown.

1. Run the following command to switch to the /usr/sap/$SID/HDB00/ directory:An example is provided as follows:cd /usr/sap/S00/HDB00

2. Switch to the database system administrator.Account s00adm is displayed on the page during the installation. Run the followingcommand:su - s00adm

3. Run the following command to start the SAP HANA database:./HDB start

4. Run the following command to stop the SAP HANA database:./HDB stop

5. Run the following command to restart the SAP HANA database:./HDB restart


Step 5 Install the SAP HANA software on the other SAP HANA ECS.

Switch to the other SAP HANA ECS using SSH and install the SAP HANA software on it byrepeating Step 1 to Step 4.

During the software installation, ensure that the installation information about this HANAECS is the same as that about the previous HANA ECS, excepting the host name.

----End


Scenarios


Prerequisitesl Required resources are available. For details, see section Preparing for Resources.l You have created ECSs, formatted disks attached to them, and installed the SAP HANA.l The firewall on the target ECS has been disabled.l Remote login to the target ECS has been enabled.

Procedure




Issue 02 (2016-10-29) 73


NOTE















Issue 02 (2016-10-29) 74




----End


Scenarios



Prerequisitesl Required resources are available. For details, see section Preparing for Resources.l You have created ECSs, formatted disks attached to them, and installed the SAP HANA.l The firewall on the target ECS has been disabled.

Procedure




sudo su


NOTE





cd /usr/sap





Issue 02 (2016-10-29) 75









cd SAP_HANA_STUDIO

./hdbsetup






Issue 02 (2016-10-29) 76




----End


ScenariosSAP HANA nodes can be managed only after they are connected to the SAP HANA Studio.


Procedure







Issue 02 (2016-10-29) 77






Key parameters are as follows:


Issue 02 (2016-10-29) 78

l Host Name: Enter the service or client plane IP address of the SAP HANA ECS.l Instance Number: Enter the number of the instance on the SAP HANA node.l Mode: Choose Single container.





Issue 02 (2016-10-29) 79








Issue 02 (2016-10-29) 80


Step 11 Connect the other HANA node to the SAP HANA Studio.

Repeat Step 5 to Step 10 to connect the other HANA node to the SAP HANA Studio.

----End


ScenariosA path is required for backing up SAP HANA data.


ProcedureStep 1 On the HANA Studio ECS, choose Start > SAP HANA > SAP HANA Studio to start the

SAP HANA Studio software.




Issue 02 (2016-10-29) 81


NOTE






Issue 02 (2016-10-29) 82



NOTE



Issue 02 (2016-10-29) 83



----End

2.6.8 Configuring HANA HA

ScenariosAfter installing two single HANA nodes for HA, configure system-replication-based HA onthem.

Prerequisitesl Before configuring HA, make sure that you have enabled data backup and backed up the

database on the two HANA nodes. For details, see section Configuring the BackupPath.

l Before configuring HA, make sure that you have written the mapping between the IPaddresses of the two HANA nodes and the node names (see section Configuring the


Issue 02 (2016-10-29) 84

Mapping Between HANA ECSs and IP Addresses) into the /etc/hosts files of the twonodes.

Procedure

Step 1 Configure the primary node.

1. Use PuTTY to log in to the NAT server with an elastic IP address bound. Ensure thatuser root and the key file (.ppk file) are used for authentication. Then, use SSH to switchto the HANA ECS that will work as the primary node.

2. Run the following command to switch to the administrator mode:su - $SIDadmAn example is provided as follows:su - s00admInformation similar to the following is displayed:hana001:/usr/sap/S00/HDB00>

3. Run the following command to switch to the exe directory:cd exe

4. Run the following command to configure the HANA node as the primary one:hdbnsutil -sr_enable --name=siteAIn the preceding command, siteA is the name of the primary HANA node, which can becustomized.For example, if the name of the primary HANA node is Primary, run the followingcommand:hdbnsutil -sr_enable --name=Primary

Step 2 Configure the secondary HANA node.

1. Switch to the other HANA ECS using SSH.2. Run the following command to enter the administrator mode:

su - $SIDadmAn example is provided as follows:su - s00admInformation similar to the following is displayed:hana002:/usr/sap/S00/HDB00>

3. Run the following command to stop the SAP HANA database:./HDB stop

4. Run the following command to switch to the exe directory:cd exe

5. Run the following command to enable system replication:./hdbnsutil -sr_register --remoteHost=remoteHostName --remoteInstance=remoteInstanceNumber --mode=sync --name=siteBIn the preceding command, remoteHostName is the name of the primary node,remoteInstanceNumber is the instance ID of the primary node, and SiteB is the nameof the secondary node, which can be customized.For example, if remoteHostName is hana001, remoteInstanceNumber is 00, andSiteB is Secondary, run the following command:


Issue 02 (2016-10-29) 85

./hdbnsutil -sr_register --remoteHost=hana001 --remoteInstance=00 --mode=sync --name=Secondary

6. Run the following commands to exit the exe directory and start the SAP HANAdatabase:cd .../HDB start

Step 3 Query the system replication status in the HANA system.

1. In the exe directory on the primary node, run the following command in theadministrator mode:./hdbnsutil -sr_stateInformation similar to the following is displayed:checking for active or inactive nameserver ...System Replication State~~~~~~~~~~~~~~~~~~~~~~~~mode: primarysite id: 1site name: hana001Host Mappings:~~~~~~~~~~~~~hana001 -> [hana001] hana001hana001 -> [hana002] hana002done.

2. Query the primary node status on the SAP HANA Studio.

Figure 2-49 Querying the primary node status

NOTE

In actual application scenarios, the service software has connected to the HANA node. If youmanually switch the HANA node, you must change the IP address of the HANA node on theservice software and restart the service software.

----End


Issue 02 (2016-10-29) 86

2.7 Installing SAP HANA (Cluster Deployment and SingleNFS Server Deployed)

2.7.1 Formatting the Disks Attached to an NFS Server

Scenarios

The disks attached to an NFS server must be formatted to comply with the SAP HANAinstallation requirements.

Procedure

Step 1 Format the disks of the NFS servers.

1. Use PuTTY to log in to the NAT server with an elastic IP address bound. Ensure thatuser root and the key file (.ppk file) are used for authentication. Then, use SSH to switchto an NFS server.


3. Determine the paths for the shared volumes, backup volumes, and SBD volumesaccording to disk capacities. The SBD volumes are used only when two NFS servers aredeployed to work in active/standby mode.


NOTE




6. Run the following command to modify the nfsserver.cfg file:vi /usr/sap/scale_out_script/nfsserver.cfg

7. Press i to enter editing mode. Write the paths and the HANA ECS IP addresses that areallowed to access the NFS servers into the nfsserver.cfg file.The parameters are as follows:– share: specifies the path for the shared volume.– backup: specifies the path for the backup volume.– sbd: specifies the path for the SBD volume. This parameter is required only when

two NFS servers are deployed to work in active/standby mode.– permithosts: specifies the HANA ECS that is accessible to the NFS servers. The IP

address of this HANA ECS is the cloud management or backup plane IP address,


Issue 02 (2016-10-29) 87

for example, 10.0.1.x. When multiple IP addresses are available, separate them witha comma (,).

– nfsServerIps: specifies the IP addresses (for example, 10.0.1.x) of the cloudmanagement or backup planes for the NFS servers. When two NFS servers aredeployed to work in active/standby mode, set this parameter value to the server IPaddresses and separate them with a comma (,).

The content of the configuration file is as follows when only one NFS server isdeployed:share=/dev/sdabackup=/dev/sdbsbd=permithosts=10.0.1.2,10.0.1.3,10.0.1.4,10.0.1.5,10.0.1.6nfsServerIps=10.0.1.101The content of the configuration file is as follows when two NFS servers are deployed towork in active/standby mode:share=/dev/sdabackup=/dev/sdbsbd=/dev/sdcpermithosts=10.0.1.2,10.0.1.3,10.0.1.4,10.0.1.5,10.0.1.6nfsServerIps=10.0.1.101,10.0.1.102

8. After you complete editing, press Esc, enter :x, and press Enter to exit the nfsserver.cfgfile.

9. Run the following commands to assign execute permissions, convert the file format, andformat the disk:cd /usr/sap/scale_out_scriptchmod 777 nfsserver.sh nfsserver.cfgdos2unix nfsserver.sh nfsserver.cfgsh nfsserver.sh

----End

2.7.2 Formatting a HANA Disk

Scenarios

In SAP HANA cluster scenarios, all data volumes and log volumes form a data volumeresource pool and a log volume resource pool, respectively, for all HANA ECSs. In this way,every data or log volume is attached to all HANA nodes.

After the attachment, the data disks, including the data and log volumes and the shared andbackup volumes on the NFS servers, can be used only after they are formatted and attached torequired directories.

Procedure

Step 1 Attach all data and log volumes to all HANA ECSs.

1. On the Open Telekom Cloud management console, choose Computing > Elastic CloudServer. Click Elastic Cloud Server on the left. Then, all ECSs are displayed on theright side of the page.

2. Locate the first HANA ECS by ECS name and click its name.


Issue 02 (2016-10-29) 88

3. On the page displayed for the HANA ECS details, click the EVS tab and then in frontof the first data disk (log or data volume).

4. In the expanded data disk pane, click the link following the data disk ID.5. On the page that is displayed, click Attach in the Operation column of the disk to be

attached. Then, the Attach Disk page is displayed.6. Select all target HANA ECSs and click Attach to attach the disk to them.

Ensure that the disk is attached to all HANA nodes.

7. Click to update the information. Then, check the information displayed inAttaching Information. Make sure that this disk has been attached to all HANA nodes.

8. Perform the preceding steps to attach the second disk (data or log volume) of the HANAECS to all other HANA nodes.

9. Perform the preceding steps to attach the log and data volumes of all HANA ECSs toother HANA nodes.

NOTE

The last HANA ECS is a STANDBY node. When creating this HANA ECS, you did not create orattach log and data volumes to it. Therefore, you do not need to attach the disks of this HANAECS to other HANA ECSs.

Step 2 Upload the local hosts file to other SAP HANA ECSs.

1. Use PuTTY to log in to the NAT server with an elastic IP address bound. Ensure thatuser root and the key file (.ppk file) are used for authentication. Then, use SSH to switchto the first HANA ECS.

2. The /etc/hosts file has been configured in section Configuring the Mapping BetweenHANA ECSs and IP Addresses. Therefore, you only need to transfer this file to otherHANA ECSs.The command is in the following format:scp /etc/hosts Peer IP address:/etc/hostsFor example, if the peer IP address of the SAP HANA ECS is 10.0.3.3, run the followingcommand:scp /etc/hosts 10.0.3.3:/etc/hosts

Step 3 Verify the SSH switching between HANA ECSs.

Use SSH to switch from every HANA ECS to any other HANA ECS and verify that theswitching is correct.

For example, if the name of the peer HANA ECS is hana002, run the following command:

ssh hana002

Step 4 Format the disks attached to a HANA node.

1. Run the following command on the first HANA ECS to query the disk to be formatted:fdisk -l

2. Determine the paths for the data and log volumes according to the disk capacities.3. Query the IP address (for example, 10.0.1.x) of the cloud management or backup plane

for the NFS server.For details, see section Querying the NIC IP Address of an ECS.


Issue 02 (2016-10-29) 89

4. Query the internal communication plane IP addresses (for example, 10.0.2.x) of allHANA ECSs.For details, see section Querying the NIC IP Address of an ECS.


NOTE



6. Run the following commands to switch to the folder and decompress the softwarepackage:cd /usr/sap/unzip scale_out_script.zip

7. Run the following command to modify the hanaCluster.cfg file:vi /usr/sap/scale_out_script/hanaCluster.cfg

8. Press i to enter editing mode. Write the path, cloud management or backup plane IPaddress of the NFS server, and internal communication plane IP address of all HANAECSs into the hanaCluster.cfg file.Parameters are as follows:– partition_1_data__volname: specifies the path for the data volume attached to the

first SAP HANA ECS. Apply this rule to other data volumes.– partition_1_log__volname: specifies the path for the log volume attached to the

first SAP HANA ECS. Apply this rule to other data volumes.– nfsserverIp: specifies the IP address (for example, 10.0.1.x) of the cloud

management or backup plane for the NFS server. When two NFS servers aredeployed to work in active/standby mode, the value of this parameter is the floatingIP address of the NFS servers.

– sid: specifies the SAP HANA system ID. After the configuration, ensure that thesystem ID is the same as this value when installing SAP HANA.

– hosts: specifies the internal communication plane IP addresses (for example,10.0.2.x) of HANA ECSs. When multiple IP addresses are available, separate themwith a comma (,).

Take five HANA ECSs as an example.

NOTE

Ensure that every volume path is unique.partition_1_data__volname=/dev/sdapartition_1_log__volname=/dev/sdbpartition_2_data__volname=/dev/sdcpartition_2_log__volname=/dev/sddpartition_3_data__volname=/dev/sdepartition_3_log__volname=/dev/sdfpartition_4_data__volname=/dev/sdgpartition_4_log__volname=/dev/sdhpartition_5_data__volname=/dev/sdipartition_5_log__volname=/dev/sdjnfsserverIp=10.0.1.103sid=S01hosts=10.0.2.2,10.0.2.3,10.0.2.4,10.0.2.5,10.0.2.6


Issue 02 (2016-10-29) 90

9. After you complete editing, press Esc, enter :x, and press Enter to exit thehanaCluster.cfg file.

10. Run the following commands to switch to the directory where the hanaCluster.cfg file isstored and convert the file format:cd /usr/sap/scale_out_scriptdos2unix installHanaCluster.sh hanaCluster.cfg

11. Assign operation permissions to the hanaCluster.cfg file and run installHanaCluster.shto format disks.chmod 777 installHanaCluster.sh hanaCluster.cfgsh installHanaCluster.sh

----End


Scenarios





Procedure




3. Configure the HANA ECS as the NTP server, which allows NTP clients (other HANAECSs) with specified IP addresses to synchronize time with it.Ensure that the IP addresses of other HANA ECSs are in the service or client planenetwork segment. For instructions about how to query the IP addresses of other HANAECSs, see section Querying the NIC IP Address of an ECS.vi /etc/ntp.confAn example is provided as follows:#### Miscellaneous stuff##restrict 10.0.3.3 255.255.255.0 nomodify


Issue 02 (2016-10-29) 91

restrict 10.0.3.4 255.255.255.0 nomodify...



NOTE






In cluster scenarios, configure the NTP client on the NFS server and HANA nodes except theHANA node that functions as the time source.

1. Log in to the HANA ECS.Use PuTTY to log in to the NAT server with an elastic IP address bound. Ensure thatuser root and the key file (.ppk file) are used for authentication. Then, use SSH to switchto the HANA ECS.






7. Run the following command to query the NTP status:ntpq -pFigure 2-51 shows an example of the command output.


Issue 02 (2016-10-29) 92

Ensure that the value of offset is within an appropriate range.

NOTE







----End


Scenarios

The SAP HANA software is installed using an installation script.

Prerequisitesl Required resources are available. For details, see section Preparing for Resources.l You have created and configured HANA ECSs and ECSs and formatted the disks

attached to them.

Procedure

Step 1 Download the installation package and generate the required configfile.cfg file.

1. Use PuTTY to log in to the NAT server with an elastic IP address bound. Ensure thatuser root and the key file (.ppk file) are used for authentication. Then, use SSH to switchto the first HANA ECS, for example, hana001.

2. Download the decompression software linux_x86_64_sapcar.zip and the SAP HANAinstallation package linux_x86_64_hdb.sar.

NOTE



Issue 02 (2016-10-29) 93



4. Run the following command to assign execute permissions to the decompressedsoftware, for example, decompressed linux_x86_64_sapcar.zip isSAPCAR_712-80000935.EXE:chmod +x SAPCAR_712-80000935.EXE

5. Run the following command to decompress the SAP installation package:./SAPCAR_712-80000935.EXE -xvf linux_x86_64_hdb.sar

6. Run the following commands to decompress the generated package, for example,decompressed linux_x86_64_hdb.sar is IMDB_SERVER100_112_5-10009569.SAR:./SAPCAR_712-80000935.EXE -xvf IMDB_SERVER100_112_5-10009569.SAR

7. Copy the generated SAP_HANA_DATABASE folder to the /hana/shared directory.cp -R SAP_HANA_DATABASE /hana/shared

8. Run the following command to assign permissions to the directory:chmod 777 -R /hana

9. Log in to the directory where the SAP HANA software package is stored.For example, if the directory is /hana/shared, run the following command:cd /hana/shared

10. Enter the directory where the installation file is stored.For example, if the installation file is stored in SAP_HANA_DATABASE, run thefollowing command:cd SAP_HANA_DATABASE

11. Run the following command to obtain the configfile.cfg file:./hdblcm --action=install --dump_configfile_template=/hana/shared/configfile.cfgAfter this command is executed, the configfile.cfg file is stored in the /hana/shareddirectory.

12. Run the following command and press i to enter the editing mode and edit theconfigfile.cfg file:vi /hana/shared/configfile.cfg

13. Modify parameter settings.The parameters are as follows:– remote_execution: specifies a remote execution mode, the default value of which

is ssh.– sapmnt: specifies the installation path, which is /hana/shared.– hostname: specifies the ECS name, such as hana001.– root_password: specifies the password of user root for logging in to the HANA

ECS.


Issue 02 (2016-10-29) 94

– storage_cfg: specifies the path in which the configfile.cfg file is stored. Set thevalue of this parameter to /hana/shared.

– sid: specifies the SAP HANA system ID, which must be the same as the sid valueconfigured in hanaCluster.cfg when the disk is formatted.

– number: specifies the SAP HANA instance ID. The instance ID is used in SecurityGroup Rules, which must be the same as the planned one.

– sapadm_password: specifies the password of the HostAgent software packageinstalled on the HANA ECS. Configure this parameter based on servicerequirements.

An example is provided as follows:[General]

# Location of SAP HANA Installation Mediumcomponent_medium=

# Comma separated list of component directoriescomponent_dirs=

# Directory root to search for componentscomponent_root=

# Components ( Valid values: all | client | es | ets | lcapps | server | smartda | streaming | rdsync | studio | afl | pos | sal | sca | sop | trd | udf )components=

# Remote Execution ( Default: ssh; Valid values: ssh | saphostagent )remote_execution=ssh

[Server]

# Enable the installation or upgrade of the SAP Host Agent ( Default: y )install_hostagent=y

# Non-standard Shared File Systemcheckmnt=

# Installation Path ( Default: /hana/shared )sapmnt=/hana/shared

# Local Host Name ( Default: hana001 )hostname=hana001

# Install SSH Key ( Default: y )install_ssh_key=y

# Root User Name ( Default: root )root_user=root

# Root User Passwordroot_password=Admin@123

# Directory containing a storage configurationstorage_cfg=/hana/shared

# Internal Network Addressinternal_network=

# SAP HANA System IDsid=S01

# Instance Numbernumber=00

# Database Mode ( Default: single_container; Valid values: single_container |


Issue 02 (2016-10-29) 95

multiple_containers )db_mode=single_container

# Database Isolation ( Default: low; Valid values: low | high )db_isolation=low

# System Usage ( Default: custom; Valid values: production | test | development | custom )system_usage=custom

# Location of Data Volumes ( Default: /hana/data/${sid} )datapath=/hana/data/${sid}

# Location of Log Volumes ( Default: /hana/log/${sid} )logpath=/hana/log/${sid}

# Restrict maximum memory allocation?restrict_max_mem=

# Maximum Memory Allocation in MBmax_mem=

# Certificate Host Namescertificates_hostmap=

# SAP Host Agent User (sapadm) Passwordsapadm_password=Password@123...

14. After you complete editing, press Esc, enter :x, and press Enter to exit the configfile.cfgfile.

Step 2 Save the installation script in /hana/shared.

1. Run the following commands to copy the fusionStorageClient.py andgetdiskbyidentifier.sh files to /hana/shared:cp /usr/sap/scale_out_script/fusionStorageClient.py /hana/sharedcp /usr/sap/scale_out_script/getdiskbyidentifier.sh /hana/shared

2. Run the following commands to convert the formats of fusionStorageClient.py andgetdiskbyidentifier.sh:dos2unix /hana/shared/fusionStorageClient.pydos2unix /hana/shared/getdiskbyidentifier.sh

3. Run the following command to identify the client.py file in the HANA installationdirectory:find /hana/shared -name client.py

4. Run the following command to copy the client.py file into the directory where thefusionStorageClient.py file is stored:cp Source file Destination fileAn example is provided as follows:cp /hana/shared/SAP_HANA_DATABASE/server/hdb_ha/client.py /hana/shared/client.py


1. Run the following command to switch to the SAP_HANA_DATABASE directory onSPA HANA ECS hana001:cd /hana/shared/SAP_HANA_DATABASE

2. Run the following command to assign permissions to the directory:


Issue 02 (2016-10-29) 96

chmod 777 -R /hana3. Start the installation.

The parameters are as follows:– Install the software on SPA HANA ECS hana001 and ensure that no description of

this ECS is contained in the CLI.– Every node must have the WORKER or STANDBY role assigned.Take five nodes as an example:./hdblcm --action=install --addhosts=hana002:role=worker,hana003:role=worker,hana004:role=worker,hana005:role=standby --configfile=/hana/shared/configfile.cfg --ignore=check_signature_fileThe following information is displayed:...Select additional components for installation:...

4. Use default settings and press Enter.The following information is displayed:...Enter comma-separated list of the selected indices [1]:

5. Use default settings and press Enter.The following information is displayed:...Restrict maximum memory allocation? [n]:...

6. Use default settings and press Enter.The following information is displayed:...Enter Certificate Host Name For Host 'hana001' [hana001]:

7. Use default settings and press Enter.The following information is displayed:...Enter System Administrator (s01adm) Password:

8. Set and confirm the password as prompted.The following information is displayed:...Enter System Administrator User ID [1000]:

9. Use default settings and press Enter.The following information is displayed:...Enter ID of User Group (sapsys) [79]:

10. Use default settings and press Enter.The following information is displayed:...Enter Database User (SYSTEM) Password:

11. Set and confirm the password as prompted. The system displays the brief installationinformation and a message asking you whether to continue the installation....Do you want to continue? (y/n):

12. After verifying the installation, enter y and press Enter to start the SAP HANA softwareinstallation.


Issue 02 (2016-10-29) 97

13. After the installation is complete, the system displays the following information:...SAP HANA system installed.

Step 4 Check the software installation.

1. Run the following command to enter the SAP HANA system administrator mode:su - $SIDadmAn example is provided as follows:su - s01adm

2. Run an SQL query statement.The format is as follows:hdbsql -i Instance ID -u SYSTEM -p Password of the database administrator -C"select * from M_LANDSCAPE_HOST_CONFIGURATION"An example is provided as follows:hdbsql -i 00 -u SYSTEM -p Password1234 -C "select * fromM_LANDSCAPE_HOST_CONFIGURATION"If the system displays the queried data, the SAP HANA software is installed.

----End


Scenarios



Procedure




NOTE




Issue 02 (2016-10-29) 98















----End


Issue 02 (2016-10-29) 99


Scenarios



Prerequisitesl Required resources are available. For details, see section Preparing for Resources.l You have created ECSs, formatted disks attached to them, and installed the SAP HANA.l The firewall on the target ECS has been disabled.

Procedure




sudo su


NOTE





cd /usr/sap









Issue 02 (2016-10-29) 100





cd SAP_HANA_STUDIO

./hdbsetup








----End


Issue 02 (2016-10-29) 101


ScenariosSAP HANA nodes can be managed only after they are connected to the SAP HANA Studio.


Procedure








Issue 02 (2016-10-29) 102





Key parameters are as follows:l Host Name: Enter the service or client plane IP address of the SAP HANA ECS. In the

cluster scenarios, you only need to enter the IP address of the first HANA node, onwhich installation has been performed.

l Instance Number: Enter the number of the instance on the SAP HANA node.l Mode: Choose Single container.


Issue 02 (2016-10-29) 103





Issue 02 (2016-10-29) 104








Issue 02 (2016-10-29) 105


----End


Scenarios



Procedure





Issue 02 (2016-10-29) 106


NOTE






Issue 02 (2016-10-29) 107



NOTE



Issue 02 (2016-10-29) 108



----End

2.8 Installing SAP HANA (Cluster Deployment and TwoNFS Servers Deployed to Work in Active/Standby Mode)

2.8.1 Configuring NFS Servers to Be Trusty to Each Other

ScenariosTwo NFS servers use HAE for active/standby deployment. HAE requires that the two NFSservers be trusty to each other.

The two NFS servers have been configured to be trusty in section Configuring SSHSwitching Permissions. In this section, you only need to configure the mapping between the


Issue 02 (2016-10-29) 109

host names of the HANA ECSs where the NFS servers are deployed and the cloudmanagement or backup plane IP addresses.

Procedure

Step 1 Modify the /etc/hosts file.

Use PuTTY to log in to the NAT server with an elastic IP address bound. Ensure that userroot and the key file (.ppk file) are used for authentication. Then, use SSH to switch to anNFS server.

Step 2 Modify the /etc/hosts file on the NFS server. Specifically, write the mapping between thecloud management or backup plane IP addresses (for example, 10.0.1.x) of the two NFSservers and the names of the HANA ECSs where the two NFS servers are deployed into thisfile.

For details, see section Configuring the Mapping Between HANA ECSs and IPAddresses.

Step 3 Upload the local hosts file to the other NFS server.

The command is in the following format:

scp /etc/hosts Peer IP address:/etc/hosts

For example, if the peer IP address of the SAP HANA ECS is 10.0.3.102, run the followingcommand:

scp /etc/hosts 10.0.1.102:/etc/hosts

Step 4 Verify the trusty relationship.

For example, if the local NFS server is nfs01, and the name of the other NFS server is nfs02,run the following commands:

ssh nfs02

ssh nfs01

NOTE

When an SSH connection is set up between two ECSs (where the two NFS servers are deployed) for thefirst time, the system displays the message "Are you sure you want to continue connecting (yes/no)?" onthe CLI. In such a case, you only need to select yes and press Enter.

----End

2.8.2 Formatting the Disks Attached to an NFS Server

Scenarios

The disks attached to an NFS server must be formatted to comply with the SAP HANAinstallation requirements.

Procedure

Step 1 Attach the shared, backup, and SBD volumes to an NFS server.


Issue 02 (2016-10-29) 110

This operation is performed only when two NFS servers are deployed to work in active/standby mode. The reason is as follows: When one NFS server is created, the shared, backup,and SBD volumes are attached to it. These disks must be attached to the other NFS server.


2. According to the HANA ECS name, locate the HANA ECS where the NFS server withdisks attached is deployed and click the HANA ECS name.

3. On the page displayed for the HANA ECS details, click the EVS tab and then in frontof the first data disk.

4. In the expanded data disk pane, take note of the Mount Point value and click the linkfollowing the data disk ID.

5. On the page that is displayed, click Attach in the Operation column of the disk to beattached. Then, the Attach Disk page is displayed.

6. Select the HANA ECS where the other NFS server is deployed and click Attach toattach the disk to the HANA ECS. Ensure that the Mount Point value is the same as thatobtained in Step 1.4.

7. Click to update the information. Then, check the information displayed inAttaching Information. Make sure that this disk has been attached to the NFS server.

8. Repeat Step 1.2 to Step 1.7 to attach all disks to the NFS server.

Step 2 Format the disks of the NFS servers.

1. Use PuTTY to log in to the NAT server with an elastic IP address bound. Ensure thatuser root and the key file (.ppk file) are used for authentication. Then, use SSH to switchto an NFS server.


3. Determine the paths for the shared volumes, backup volumes, and SBD volumesaccording to disk capacities. The SBD volumes are used only when two NFS servers aredeployed to work in active/standby mode.


NOTE




6. Run the following command to modify the nfsserver.cfg file:vi /usr/sap/scale_out_script/nfsserver.cfg

7. Press i to enter editing mode. Write the paths and the HANA ECS IP addresses that areallowed to access the NFS servers into the nfsserver.cfg file.


Issue 02 (2016-10-29) 111

The parameters are as follows:– share: specifies the path for the shared volume.– backup: specifies the path for the backup volume.– sbd: specifies the path for the SBD volume. This parameter is required only when

two NFS servers are deployed to work in active/standby mode.– permithosts: specifies the HANA ECS that is accessible to the NFS servers. The IP

address of this HANA ECS is the cloud management or backup plane IP address,for example, 10.0.1.x. When multiple IP addresses are available, separate them witha comma (,).

– nfsServerIps: specifies the IP addresses (for example, 10.0.1.x) of the cloudmanagement or backup planes for the NFS servers. When two NFS servers aredeployed to work in active/standby mode, set this parameter value to the server IPaddresses and separate them with a comma (,).

The content of the configuration file is as follows when only one NFS server isdeployed:share=/dev/sdabackup=/dev/sdbsbd=permithosts=10.0.1.2,10.0.1.3,10.0.1.4,10.0.1.5,10.0.1.6nfsServerIps=10.0.1.101The content of the configuration file is as follows when two NFS servers are deployed towork in active/standby mode:share=/dev/sdabackup=/dev/sdbsbd=/dev/sdcpermithosts=10.0.1.2,10.0.1.3,10.0.1.4,10.0.1.5,10.0.1.6nfsServerIps=10.0.1.101,10.0.1.102

8. After you complete editing, press Esc, enter :x, and press Enter to exit the nfsserver.cfgfile.

9. Run the following commands to assign execute permissions, convert the file format, andformat the disk:cd /usr/sap/scale_out_scriptchmod 777 nfsserver.sh nfsserver.cfgdos2unix nfsserver.sh nfsserver.cfgsh nfsserver.sh

Step 3 Configure the nfsserver.sh configuration script not to automatically start when the NFSserver starts.

This operation is performed only when two NFS servers are deployed to work in active/standby mode. Ensure that both the NFS servers require configuration.

chkconfig nfsserver off

service nfsserver stop

----End


Issue 02 (2016-10-29) 112

2.8.3 Configuring HA on NFS Servers

Scenarios

When NFS servers are deployed to work in active/standby mode, you must enable datasynchronization on the NFS servers so that they can properly support SAP HANA.

Prerequisites

You have configured NFS servers to be trusty to each other and formatted to the disksattached to NFS servers. For details, see sections Configuring NFS Servers to Be Trusty toEach Other and Formatting the Disks Attached to an NFS Server.

Procedure

Step 1 Initialize the cluster.

1. Use PuTTY to log in to the NAT server with an elastic IP address bound. Ensure thatuser root and the key file (.ppk file) are used for authentication. Then, use SSH to switchto the NFS server that will work as the active node. The name of the NFS server isassumed to be nfs01.

2. Run the following commands on the active node to disable automatic firewall enablingand disable the firewall:chkconfig SuSEfirewall2_setup offchkconfig SuSEfirewall2_init offSuSEfirewall2 stop

3. Log in to the standby NFS server from the active one using SSH.The name of the standby NFS server is assumed to be nfs02.ssh nfs02

4. Run the following commands on the standby node to disable automatic firewall enablingand disable the firewall:chkconfig SuSEfirewall2_setup offchkconfig SuSEfirewall2_init offSuSEfirewall2 stop

5. Run the following command to log in to the active node using SSH:ssh nfs01

6. Run the following command on the active node to enter the cluster configuration page:sleha-init

7. When the system displays the following information, enter y and press Enter:WARNING: NTP is not configured to start at system boot. Do you want to continue anyway?

8. When the system displays the following information, enter n and press Enter:/root/.ssh/id_rsa already exists - overwrite? [y/N]

9. Enter the internal NFS server communication network segment and press Enter.Take network segment 10.0.2.0 as an example:Network address to bind to (e.g.: 192.168.1.0) []


Issue 02 (2016-10-29) 113

10. Retain the default settings and press Enter.

NOTE

Take note of the default broadcast address, which will be used in Step 3.7.Multicast address (e.g.: 239.x.x.x) [239.97.171.218]

11. Retain the default settings and press Enter.Multicast port [5405]

12. When the system displays the following information, enter n and press Enter:Do you wish to use SBD? [y/N]

13. During the cluster initialization, the system displays the following information:Enabling hawk serviceHA Web Konsole is now running, to see cluster status go to:https://192.168.20.210:7630/Log in with username 'hacluster', password 'linux'WARNING: You should change the hacluster password to something more secure!Enabling openais serviceWaiting for cluster........doneLoading initial configurationDone (log saved to /var/log/sleha-bootstrap.log)

Step 2 Add the standby NFS server to the cluster.

1. On active NFS server nfs01, synchronize the corosync.conf configuration file to thestandby NFS server.To do so, run the following command:scp /etc/corosync/corosync.conf Name of the standby NFS server:/etc/corosync/An example is provided as follows:scp /etc/corosync/corosync.conf nfs02:/etc/corosync/

2. Log in to the standby NFS server from the active one using SSH.ssh nfs02

3. Run the following command to add the standby NFS server to the cluster:sleha-join

4. When the system displays the following information, enter y and press Enter:WARNING: NTP is not configured to start at system boot. Do you want to continue anyway?

5. When the system displays the following information, enter the internal communicationplane IP address of the active NFS server, for example, 10.0.2.101, and press Enter:IP address or hostname of existing node (e.g.: 192.168.1.1) []

6. When the system displays the following information, enter n and press Enter:/root/.ssh/id_rsa already exists - overwrite? [y/N]

7. When the system displays the following information, enter yes and press Enter:The following information is an example.The authenticity of host '10.0.2.101 (10.0.2.101)' can't be established.ECDSA key fingerprint is bf:dc:fc:98:63:d7:6d:bd:b2:da:ca:ba:1e:4e:c0:a7 [MD5].Are you sure you want to continue connecting (yes/no)?

8. During the cluster initialization after the standby NFS server is added to the cluster, thesystem displays the following information:...Log in with username 'hacluster', password 'linux'


Issue 02 (2016-10-29) 114

WARNING: You should change the hacluster password to something more secure!Enabling openais serviceWaiting for cluster...doneDone (log saved to /var/log/sleha-bootstrap.log)

Step 3 Configure basic cluster parameters.

1. Use VNC and user root password to log in to the active NFS server as user root andswitch to the CLI mode.

2. Run the yast2 command to enter the YaST2 Control Center page.

Figure 2-64 YaST2 Control Center page

3. Choose High Availability > Cluster to enter the cluster configuration page.4. On the left side of the page, select Communication Channels. Then, configure

parameters on the right side of the page. Figure 2-65 shows an example.The parameters are as follows:– Transport: Set this parameter to udpu.– In the Channel pane, set Bind Network Address to the network segment for the

NFS server heartbeat link, which is the network segment of the internalcommunication plane, for example, 10.0.2.0; retain the default setting of MulticastPort; use Add in Member Address to add internal communication plane IPaddresses of the active and standby NFS servers.

– Auto Generate Node ID: Select this parameter.– Redundant Channel: Select this parameter. Ensure that the Multicast Port value

is the same as that specified in the Channel pane. In addition, use Add to add thecloud management or backup plane IP addresses of the active and standby NFSservers to Member Address.


Issue 02 (2016-10-29) 115

Figure 2-65 Communication Channels page

5. On the left side of the page, select Security. Then, configure parameters on the right sideof the page.The parameters are as follows:– Enable Security Auth: Select this parameter.– Threads: Set this parameter to 16.Select Generate Auth Key File and press Enter. In the dialog box showing the filegeneration message, select OK and press Enter to generate the authentication key file.

Figure 2-66 Security page


Issue 02 (2016-10-29) 116

6. On the left side of the page, select Configure Csync2. Then, configure parameters onthe right side of the page.Select a Sync Host node and Generate Pre-Shared-Keys and press Enter to generatethe file. Then, select Add Suggested Files and press Enter to add the recommendedsynchronization files. Verify that Csync2 is enabled (Turn csync2 OFF in the lowerright corner is displayed).

Figure 2-67 Configure Csync2 page

7. On the left side of the page, select Configure conntrackd. Then, configure parameterson the right side of the page.The parameters are as follows:– Dedicated interface: Select the internal communication plane NIC of the active

NFS server.– Multicast Address: Enter the default broadcast address involved in Step 1.– Group Number: Set this parameter to 1.Select Generate /etc/conntrackd/contrackd.conf and press Enter. In the dialog boxshowing the file generation message, select OK and press Enter to generate the .conffile.


Issue 02 (2016-10-29) 117

Figure 2-68 Configure contrackd page

8. On the left side of the page, select Service. Then, configure parameters on the right sideof the page.The parameters are as follows:– Booting: On is selected by default, which indicates that the cluster is automatically

started when the server starts.– Switch on and off: Ensure that the cluster has been started.– Management Tool: Ensure that Enable mgmtd. The GUI client requires this. is

selected.– Firewall settings: Ensure that the firewall is disabled.


Issue 02 (2016-10-29) 118

Figure 2-69 Service page

9. Select Finish and press Enter to complete the configuration.10. Copy the key_hagroup and csync2.cfg files on the active NFS server to the standby

NFS server.Log in to the active NFS server as user root and run the following command:scp /etc/csync2/key_hagroup /etc/csync2/csync2.cfg Name of the standby NFSserver:/etc/csync2An example is provided as follows:scp /etc/csync2/key_hagroup /etc/csync2/csync2.cfg nfs02:/etc/csync2

11. Run the following commands on the active NFS server:chkconfig csync2 onchkconfig xinetd onrcxinetd start

12. Log in to the standby NFS server as user root and run the following commands:chkconfig csync2 onchkconfig xinetd onrcxinetd start

13. Run the following command on the active NFS server to synchronize the configurationfile:csync2 -xv

14. Run the following command on the active NFS server to check the cluster status:rcopenais statusEnsure that the cluster status is Running.

15. Run the following command on the active NFS server to restart the cluster:rcopenais restart


Issue 02 (2016-10-29) 119

16. Run the following command on the standby NFS server to check the cluster status:rcopenais statusEnsure that the cluster status is Running.

17. Run the following command on the standby NFS server to restart the cluster:rcopenais restart

18. Run the following command on the active NFS server to check the cluster heartbeatstatus:corosync-cfgtool -sThe system displays the heartbeats of the active and standby links. Ensure that theconfigurations are correct. An example is provided as follows:Printing ring status.Local node ID 167772739RING ID 0id= 10.0.2.101status= ring 0 active with no faultsRING ID 1id= 10.0.1.101status= ring 1 active with no faults

19. Check the cluster status on the active NFS server.crm_mon - r1The terminal display is as follows, where two NFS servers are in Online state, indicatingthat the cluster is functional:Last updated: Wed Oct 19 17:40:31 2016Last change: Tue Oct 18 15:32:00 2016 by root via cibadmin on hana01Stack: classic openais (with plugin)Current DC: nfs01 - partition with quorumVersion: 1.1.12-f47ea562 Nodes configured, 2 expected votes8 Resources configured

Online: [ nfs01 nfs02 ]

Step 4 Configure kernel parameters.

1. Run the following command on the active NFS server to open the file and press i to enterediting mode:vi /etc/sysconfig/kernel

2. Configure kernel parameters.Set MODULES_LOADED_ON_BOOT to softdog.MODULES_LOADED_ON_BOOT="softdog"

3. Press Esc, enter :x!, and press Enter to exit the configuration.4. Repeat Step 4.1 to Step 4.3 to configure kernel parameters on the standby NFS server.

Step 5 Configure SBD on the Fense devices.

1. Run the following command on the active NFS server:modprobe softdog

2. Run the following command to create an SBD partition:sbd -d /dev/disk/by-id/Partition ID dump


Issue 02 (2016-10-29) 120

NOTE

To query an SBD disk ID, run the ll /dev/disk/by-id |grep Partition name|grep scsi-3 command.For example, if the partition name is /dev/sdb1, run the ll /dev/disk/by-id |grep sdb|grep scsi-3command to query the ID corresponding to sdb1.

An example is provided as follows:sbd -d /dev/disk/by-id/scsi-36888603000000db7fa179ea56210049-part1 create

3. Run the following command to allocate the partition to the active NFS server:sbd -d /dev/disk/by-id/Partition ID allocate Active node host nameAn example is provided as follows:sbd -d /dev/disk/by-id/scsi-36888603000000db7fa179ea56210049-part1 allocatenfs01

4. Run the following command to allocate the partition to the standby NFS server:sbd -d /dev/disk/by-id/Partition ID allocate Standby node host nameAn example is provided as follows:sbd -d /dev/disk/by-id/scsi-36888603000000db7fa179ea56210049-part1 allocatenfs02

5. Run the following command to query the allocated partition:sbd -d /dev/disk/by-id/Partition ID listAn example is provided as follows:sbd -d /dev/disk/by-id/scsi-36888603000000db7fa179ea56210049-part1 listThe command output is as follows:0 nfs01 clear1 nfs02 clear

6. Run the following command to dump the partition:sbd -d /dev/disk/by-id/Partition ID dumpAn example is provided as follows:sbd -d /dev/disk/by-id/scsi-36888603000000db7fa179ea56210049-part1 dump

7. Create an SBD file.Run the vi /etc/sysconfig/sbd command to create the file and add data to the file.An example is provided as follows:

NOTE

Enter the SBD partition in SDB_DEVICE. The partition in the following terminal display is forreference only.

SBD_DEVICE="/dev/disk/by-id/scsi-36888603000000db7fa179ea56210049-part1"SBD_OPTS="-W"

8. On active NFS server, synchronize the configuration file to the standby NFS server.scp /etc/sysconfig/sbd Standby NFS server:/etc/sysconfigAn example is provided as follows:scp /etc/sysconfig/sbd nfs02:/etc/sysconfig

9. Run the following command on the active NFS server to restart the cluster:rcopenais restart

10. Run the following command on the standby NFS server to restart the cluster:


Issue 02 (2016-10-29) 121

rcopenais restart11. Check cluster configurations.

crm_mon - r1The terminal display is as follows, where two NFS servers are in Online state, indicatingthat the cluster is functional:Last updated: Wed Oct 19 17:40:31 2016Last change: Tue Oct 18 15:32:00 2016 by root via cibadmin on hana01Stack: classic openais (with plugin)Current DC: nfs01 - partition with quorumVersion: 1.1.12-f47ea562 Nodes configured, 2 expected votes8 Resources configured

Online: [ nfs01 nfs02 ]

Step 6 Add Fence SBD resources.

1. Run the following command on the active NFS server to switch to the CRMconfiguration mode:crmInformation similar to the following is displayed:crm(live)#

2. Run the following command to switch to the configuration mode:configure

3. Run the following commands to add SBD resources to the active NFS server:primitive r_sbd stonith:external/sbd params pcmk_delay_max=40commit

Step 7 Assign a virtual service IP address.

1. On the Open Telekom Cloud management console, choose Computing > Elastic CloudServer. Click Elastic Cloud Server on the left. Then, the Elastic Cloud Server page isdisplayed on the right.

2. Locate the HANA ECS on which an NFS server is deployed and click the HANA ECSname. Then, the page for the HANA ECS details is displayed.

3. Click the NIC tab and then Manage Private IP in the row of the cloud management orbackup plane NIC. Then, the system displays the Manage Private IP page.

4. Select Bind floating private IP address, enter the planned virtual service IP address(floating IP address of the NFS servers, for example, 10.0.1.103. For details, see sectionNetwork Planning) in IP Address, and click OK to complete the configuration.

5. Repeat Step 7.2 to Step 7.4 to configure the virtual service IP address (floating IPaddress of the same NFS server described in Step 7.4) on the other NFS server.

6. Run the following commands on the active NFS server in CRM configuration mode:primitive nfs_vip ocf:heartbeat:IPaddr2 params ip=10.0.1.103 op monitorinterval="10" timeout="20" on-fail=restartcommitIn the preceding commands, params ip is the virtual service IP address of the NFSserver. This value is for reference only.


Issue 02 (2016-10-29) 122

Step 8 Configure cluster shared volume file systems.

Run the following commands on the active NFS server to create the cluster shared disk filesystem for the shared and backup volumes, respectively:

primitive nfs_shared ocf:heartbeat:Filesystem params device="/dev/disk/by-id/scsi-368886030000000fffa17e21071682979-part1" directory="/shared" fstype=xfs opmonitor interval="10" timeout="40" on-fail=restart

primitive nfs_bak ocf:heartbeat:Filesystem params device="/dev/disk/by-id/scsi-36888603000000120fa17e21071682979-part1" directory="/backup" fstype=ext3 opmonitor interval="10" timeout="40" on-fail=restart

commit

In the preceding commands, params device and directory specify the IDs and paths of theshared and backup disks, respectively, and the values provided are for reference only. Forinstructions about how to query a disk ID, see Step 5.2.

Step 9 Run the following commands on the active NFS server in CRM configuration mode to createresource nfsserver:

In CRM configuration mode on the active NFS server, create the nfsserver resource.

If the floating IP address (specified by nfs_ip) of the NFS server is 10.0.1.103, run thefollowing command:

primitive nfsserver nfsserver params nfs_ip=10.0.1.103 nfs_init_script="/etc/init.d/nfsserver" nfs_shared_infodir="/shared" nfs_shared_infodir="/backup" operations$id=nfsserver-operations op monitor interval="10" timeout="20" on-fail=restart

commit

Step 10 Run the following commands on the active NFS server in CRM configuration mode to createresource group nfs_group for the resource created in Step 7.6 to Step 9:

group nfs_group nfs_vip nfs_shared nfs_bak nfsserver

commit

Step 11 Run the following commands on the active NFS server in CRM configuration mode to createClone Ping:

primitive r_ping ocf:pacemaker:ping params multiplier="100" dampen="5"host_list="10.0.1.1" op monitor interval="15" timeout="60" start="60" op startinterval="0" timeout="60"

clone PING r_ping

commit


l r_ping: specifies the Clone Ping resource name.l Multiplier: an efficiency enhancer that uses the benchmark of 100. When packet loss

occurs during the ping operation between two nodes, the multiplier decreases a certainvalue from 100 to determine the service NIC communication status of the nodes.

l dampen: indicates that the ping operation is performed once every 5s.l 10.0.1.1: indicates the gateway IP address of the cloud management or backup plane

network segment for the NFS servers.


Issue 02 (2016-10-29) 123

l monitor: monitors resources; interval: indicates that if pinging the upper-layer switchfails within 15s, the system will migrate resources at most 60s (timeout) later.

Step 12 Run the following commands on the active NFS server in CRM configuration mode to createrestraint nfs_conn on resource group nfs_group:

location nfs_conn nfs_group rule -inf: not_defined pingd or pingd lte 0

commit

Step 13 Configure other information.

1. Configure the Stonith parameter:property startup-fencing=trueproperty stonith-enabled=trueproperty stonith-action=offcommit

2. Configure the failure timeout duration:rsc_defaults failure-timeout=600commit

3. Press Ctrl+C on the active NFS server to exit the CRM configuration mode.

----End

2.8.4 Formatting a HANA Disk

Scenarios

In SAP HANA cluster scenarios, all data volumes and log volumes form a data volumeresource pool and a log volume resource pool, respectively, for all HANA ECSs. In this way,every data or log volume is attached to all HANA nodes.

After the attachment, the data disks, including the data and log volumes and the shared andbackup volumes on the NFS servers, can be used only after they are formatted and attached torequired directories.

Procedure

Step 1 Attach all data and log volumes to all HANA ECSs.


2. Locate the first HANA ECS by ECS name and click its name.

3. On the page displayed for the HANA ECS details, click the EVS tab and then in frontof the first data disk (log or data volume).

4. In the expanded data disk pane, click the link following the data disk ID.5. On the page that is displayed, click Attach in the Operation column of the disk to be

attached. Then, the Attach Disk page is displayed.6. Select all target HANA ECSs and click Attach to attach the disk to them.

Ensure that the disk is attached to all HANA nodes.


Issue 02 (2016-10-29) 124

7. Click to update the information. Then, check the information displayed inAttaching Information. Make sure that this disk has been attached to all HANA nodes.

8. Perform the preceding steps to attach the second disk (data or log volume) of the HANAECS to all other HANA nodes.

9. Perform the preceding steps to attach the log and data volumes of all HANA ECSs toother HANA nodes.

NOTE

The last HANA ECS is a STANDBY node. When creating this HANA ECS, you did not create orattach log and data volumes to it. Therefore, you do not need to attach the disks of this HANAECS to other HANA ECSs.

Step 2 Upload the local hosts file to other SAP HANA ECSs.

1. Use PuTTY to log in to the NAT server with an elastic IP address bound. Ensure thatuser root and the key file (.ppk file) are used for authentication. Then, use SSH to switchto the first HANA ECS.

2. The /etc/hosts file has been configured in section Configuring the Mapping BetweenHANA ECSs and IP Addresses. Therefore, you only need to transfer this file to otherHANA ECSs.The command is in the following format:scp /etc/hosts Peer IP address:/etc/hostsFor example, if the peer IP address of the SAP HANA ECS is 10.0.3.3, run the followingcommand:scp /etc/hosts 10.0.3.3:/etc/hosts

Step 3 Verify the SSH switching between HANA ECSs.

Use SSH to switch from every HANA ECS to any other HANA ECS and verify that theswitching is correct.

For example, if the name of the peer HANA ECS is hana002, run the following command:

ssh hana002

Step 4 Format the disks attached to a HANA node.

1. Run the following command on the first HANA ECS to query the disk to be formatted:fdisk -l

2. Determine the paths for the data and log volumes according to the disk capacities.3. Query the IP address (for example, 10.0.1.x) of the cloud management or backup plane

for the NFS server.For details, see section Querying the NIC IP Address of an ECS.

4. Query the internal communication plane IP addresses (for example, 10.0.2.x) of allHANA ECSs.For details, see section Querying the NIC IP Address of an ECS.


NOTE



Issue 02 (2016-10-29) 125


6. Run the following commands to switch to the folder and decompress the softwarepackage:cd /usr/sap/unzip scale_out_script.zip

7. Run the following command to modify the hanaCluster.cfg file:vi /usr/sap/scale_out_script/hanaCluster.cfg

8. Press i to enter editing mode. Write the path, cloud management or backup plane IPaddress of the NFS server, and internal communication plane IP address of all HANAECSs into the hanaCluster.cfg file.Parameters are as follows:– partition_1_data__volname: specifies the path for the data volume attached to the

first SAP HANA ECS. Apply this rule to other data volumes.– partition_1_log__volname: specifies the path for the log volume attached to the

first SAP HANA ECS. Apply this rule to other data volumes.– nfsserverIp: specifies the IP address (for example, 10.0.1.x) of the cloud

management or backup plane for the NFS server. When two NFS servers aredeployed to work in active/standby mode, the value of this parameter is the floatingIP address of the NFS servers.

– sid: specifies the SAP HANA system ID. After the configuration, ensure that thesystem ID is the same as this value when installing SAP HANA.

– hosts: specifies the internal communication plane IP addresses (for example,10.0.2.x) of HANA ECSs. When multiple IP addresses are available, separate themwith a comma (,).

Take five HANA ECSs as an example.

NOTE

Ensure that every volume path is unique.partition_1_data__volname=/dev/sdapartition_1_log__volname=/dev/sdbpartition_2_data__volname=/dev/sdcpartition_2_log__volname=/dev/sddpartition_3_data__volname=/dev/sdepartition_3_log__volname=/dev/sdfpartition_4_data__volname=/dev/sdgpartition_4_log__volname=/dev/sdhpartition_5_data__volname=/dev/sdipartition_5_log__volname=/dev/sdjnfsserverIp=10.0.1.103sid=S01hosts=10.0.2.2,10.0.2.3,10.0.2.4,10.0.2.5,10.0.2.6

9. After you complete editing, press Esc, enter :x, and press Enter to exit thehanaCluster.cfg file.

10. Run the following commands to switch to the directory where the hanaCluster.cfg file isstored and convert the file format:cd /usr/sap/scale_out_scriptdos2unix installHanaCluster.sh hanaCluster.cfg

11. Assign operation permissions to the hanaCluster.cfg file and run installHanaCluster.shto format disks.


Issue 02 (2016-10-29) 126

chmod 777 installHanaCluster.sh hanaCluster.cfgsh installHanaCluster.sh

----End


Scenarios





Procedure




3. Configure the HANA ECS as the NTP server, which allows NTP clients (other HANAECSs) with specified IP addresses to synchronize time with it.Ensure that the IP addresses of other HANA ECSs are in the service or client planenetwork segment. For instructions about how to query the IP addresses of other HANAECSs, see section Querying the NIC IP Address of an ECS.vi /etc/ntp.confAn example is provided as follows:#### Miscellaneous stuff##restrict 10.0.3.3 255.255.255.0 nomodifyrestrict 10.0.3.4 255.255.255.0 nomodify...




Issue 02 (2016-10-29) 127

NOTE






In cluster scenarios, configure the NTP client on the NFS server and HANA nodes except theHANA node that functions as the time source.1. Log in to the HANA ECS.

Use PuTTY to log in to the NAT server with an elastic IP address bound. Ensure thatuser root and the key file (.ppk file) are used for authentication. Then, use SSH to switchto the HANA ECS.







NOTE




Issue 02 (2016-10-29) 128





----End


ScenariosThe SAP HANA software is installed using an installation script.

Prerequisitesl Required resources are available. For details, see section Preparing for Resources.l You have created and configured HANA ECSs and ECSs and formatted the disks

attached to them.

Procedure

Step 1 Download the installation package and generate the required configfile.cfg file.

1. Use PuTTY to log in to the NAT server with an elastic IP address bound. Ensure thatuser root and the key file (.ppk file) are used for authentication. Then, use SSH to switchto the first HANA ECS, for example, hana001.

2. Download the decompression software linux_x86_64_sapcar.zip and the SAP HANAinstallation package linux_x86_64_hdb.sar.

NOTE




4. Run the following command to assign execute permissions to the decompressedsoftware, for example, decompressed linux_x86_64_sapcar.zip isSAPCAR_712-80000935.EXE:


Issue 02 (2016-10-29) 129

chmod +x SAPCAR_712-80000935.EXE5. Run the following command to decompress the SAP installation package:

./SAPCAR_712-80000935.EXE -xvf linux_x86_64_hdb.sar6. Run the following commands to decompress the generated package, for example,

decompressed linux_x86_64_hdb.sar is IMDB_SERVER100_112_5-10009569.SAR:./SAPCAR_712-80000935.EXE -xvf IMDB_SERVER100_112_5-10009569.SAR

7. Copy the generated SAP_HANA_DATABASE folder to the /hana/shared directory.cp -R SAP_HANA_DATABASE /hana/shared


9. Log in to the directory where the SAP HANA software package is stored.For example, if the directory is /hana/shared, run the following command:cd /hana/shared

10. Enter the directory where the installation file is stored.For example, if the installation file is stored in SAP_HANA_DATABASE, run thefollowing command:cd SAP_HANA_DATABASE

11. Run the following command to obtain the configfile.cfg file:./hdblcm --action=install --dump_configfile_template=/hana/shared/configfile.cfgAfter this command is executed, the configfile.cfg file is stored in the /hana/shareddirectory.

12. Run the following command and press i to enter the editing mode and edit theconfigfile.cfg file:vi /hana/shared/configfile.cfg

13. Modify parameter settings.The parameters are as follows:– remote_execution: specifies a remote execution mode, the default value of which

is ssh.– sapmnt: specifies the installation path, which is /hana/shared.– hostname: specifies the ECS name, such as hana001.– root_password: specifies the password of user root for logging in to the HANA

ECS.– storage_cfg: specifies the path in which the configfile.cfg file is stored. Set the

value of this parameter to /hana/shared.– sid: specifies the SAP HANA system ID, which must be the same as the sid value

configured in hanaCluster.cfg when the disk is formatted.– number: specifies the SAP HANA instance ID. The instance ID is used in Security

Group Rules, which must be the same as the planned one.– sapadm_password: specifies the password of the HostAgent software package

installed on the HANA ECS. Configure this parameter based on servicerequirements.

An example is provided as follows:[General]


Issue 02 (2016-10-29) 130

# Location of SAP HANA Installation Mediumcomponent_medium=

# Comma separated list of component directoriescomponent_dirs=

# Directory root to search for componentscomponent_root=

# Components ( Valid values: all | client | es | ets | lcapps | server | smartda | streaming | rdsync | studio | afl | pos | sal | sca | sop | trd | udf )components=

# Remote Execution ( Default: ssh; Valid values: ssh | saphostagent )remote_execution=ssh

[Server]

# Enable the installation or upgrade of the SAP Host Agent ( Default: y )install_hostagent=y

# Non-standard Shared File Systemcheckmnt=

# Installation Path ( Default: /hana/shared )sapmnt=/hana/shared

# Local Host Name ( Default: hana001 )hostname=hana001

# Install SSH Key ( Default: y )install_ssh_key=y

# Root User Name ( Default: root )root_user=root

# Root User Passwordroot_password=Admin@123

# Directory containing a storage configurationstorage_cfg=/hana/shared

# Internal Network Addressinternal_network=

# SAP HANA System IDsid=S01

# Instance Numbernumber=00

# Database Mode ( Default: single_container; Valid values: single_container | multiple_containers )db_mode=single_container

# Database Isolation ( Default: low; Valid values: low | high )db_isolation=low

# System Usage ( Default: custom; Valid values: production | test | development | custom )system_usage=custom

# Location of Data Volumes ( Default: /hana/data/${sid} )datapath=/hana/data/${sid}

# Location of Log Volumes ( Default: /hana/log/${sid} )logpath=/hana/log/${sid}


Issue 02 (2016-10-29) 131

# Restrict maximum memory allocation?restrict_max_mem=

# Maximum Memory Allocation in MBmax_mem=

# Certificate Host Namescertificates_hostmap=

# SAP Host Agent User (sapadm) Passwordsapadm_password=Password@123...

14. After you complete editing, press Esc, enter :x, and press Enter to exit the configfile.cfgfile.

Step 2 Save the installation script in /hana/shared.

1. Run the following commands to copy the fusionStorageClient.py andgetdiskbyidentifier.sh files to /hana/shared:cp /usr/sap/scale_out_script/fusionStorageClient.py /hana/sharedcp /usr/sap/scale_out_script/getdiskbyidentifier.sh /hana/shared

2. Run the following commands to convert the formats of fusionStorageClient.py andgetdiskbyidentifier.sh:dos2unix /hana/shared/fusionStorageClient.pydos2unix /hana/shared/getdiskbyidentifier.sh

3. Run the following command to identify the client.py file in the HANA installationdirectory:find /hana/shared -name client.py

4. Run the following command to copy the client.py file into the directory where thefusionStorageClient.py file is stored:cp Source file Destination fileAn example is provided as follows:cp /hana/shared/SAP_HANA_DATABASE/server/hdb_ha/client.py /hana/shared/client.py


1. Run the following command to switch to the SAP_HANA_DATABASE directory onSPA HANA ECS hana001:cd /hana/shared/SAP_HANA_DATABASE


3. Start the installation.The parameters are as follows:– Install the software on SPA HANA ECS hana001 and ensure that no description of

this ECS is contained in the CLI.– Every node must have the WORKER or STANDBY role assigned.Take five nodes as an example:./hdblcm --action=install --addhosts=hana002:role=worker,hana003:role=worker,hana004:role=worker,hana005:role=standby --configfile=/hana/shared/configfile.cfg --ignore=check_signature_file


Issue 02 (2016-10-29) 132

The following information is displayed:...Select additional components for installation:...

4. Use default settings and press Enter.The following information is displayed:...Enter comma-separated list of the selected indices [1]:

5. Use default settings and press Enter.The following information is displayed:...Restrict maximum memory allocation? [n]:...

6. Use default settings and press Enter.The following information is displayed:...Enter Certificate Host Name For Host 'hana001' [hana001]:

7. Use default settings and press Enter.The following information is displayed:...Enter System Administrator (s01adm) Password:

8. Set and confirm the password as prompted.The following information is displayed:...Enter System Administrator User ID [1000]:

9. Use default settings and press Enter.The following information is displayed:...Enter ID of User Group (sapsys) [79]:

10. Use default settings and press Enter.The following information is displayed:...Enter Database User (SYSTEM) Password:

11. Set and confirm the password as prompted. The system displays the brief installationinformation and a message asking you whether to continue the installation....Do you want to continue? (y/n):

12. After verifying the installation, enter y and press Enter to start the SAP HANA softwareinstallation.

13. After the installation is complete, the system displays the following information:...SAP HANA system installed.

Step 4 Check the software installation.

1. Run the following command to enter the SAP HANA system administrator mode:su - $SIDadmAn example is provided as follows:su - s01adm

2. Run an SQL query statement.


Issue 02 (2016-10-29) 133

The format is as follows:hdbsql -i Instance ID -u SYSTEM -p Password of the database administrator -C"select * from M_LANDSCAPE_HOST_CONFIGURATION"An example is provided as follows:hdbsql -i 00 -u SYSTEM -p Password1234 -C "select * fromM_LANDSCAPE_HOST_CONFIGURATION"If the system displays the queried data, the SAP HANA software is installed.

----End


ScenariosThe SAP HANA Studio manages SAP HANA. After SAP HANA nodes are deployed, youneed to install the SAP HANA Studio and use it to manage the SAP HANA nodes.


Procedure




NOTE









Issue 02 (2016-10-29) 134










----End


Scenarios





Issue 02 (2016-10-29) 135

l You have created ECSs, formatted disks attached to them, and installed the SAP HANA.l The firewall on the target ECS has been disabled.

Procedure




sudo su


NOTE





cd /usr/sap












cd SAP_HANA_STUDIO

./hdbsetup


Issue 02 (2016-10-29) 136








----End


Scenarios

SAP HANA nodes can be managed only after they are connected to the SAP HANA Studio.



Issue 02 (2016-10-29) 137

Procedure










Issue 02 (2016-10-29) 138



Key parameters are as follows:l Host Name: Enter the service or client plane IP address of the SAP HANA ECS. In the

cluster scenarios, you only need to enter the IP address of the first HANA node, onwhich installation has been performed.

l Instance Number: Enter the number of the instance on the SAP HANA node.l Mode: Choose Single container.


Issue 02 (2016-10-29) 139





Issue 02 (2016-10-29) 140








Issue 02 (2016-10-29) 141


----End


Scenarios



Procedure





Issue 02 (2016-10-29) 142


NOTE






Issue 02 (2016-10-29) 143



NOTE



Issue 02 (2016-10-29) 144



----End


Issue 02 (2016-10-29) 145

3 FAQs

3.1 What Should I Do If I Cannot Switch to an ECS orHANA ECS Using SSH?

SymptomWhen I switched from a Linux ECS/HANA ECS to another Linux ECS/HANA ECS usingSSH, the system displayed a message indicating the switching failed.

The message is as follows:

@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!Someone could be eavesdropping on you right now (man-in-the-middle attack)!It is also possible that a host key has just been changed.The fingerprint for the RSA key sent by the remote host is2c:d0:17:8a:82:4c:23:d6:14:be:d0:1d:88:8b:8b:03 [MD5].Please contact your system administrator.Add correct host key in /root/.ssh/known_hosts to get rid of this message.Offending ECDSA key in /root/.ssh/known_hosts:1You can use following command to remove all keys for this IP:ssh-keygen -R fanhana-0002 -f /root/.ssh/known_hostsRSA host key for fanhana-0002 has changed and you have requested strict checking.Host key verification failed.

Possible Causesl OpenSSH has been reinstalled on the target ECS/HANA ECS.l The node IP address or name has been changed.l Other issues have occurred.

SAP HANAUser Guide (Console) 3 FAQs

Issue 02 (2016-10-29) 146

Handling MethodDelete the known_hosts file on the local end to resolve this issue. To do so, perform thefollowing operations:

1. On the local ECS/HANA ECS, switch to the CLI as user root.2. Run the following command to delete the known_hosts file:

rm /root/.ssh/known_hosts

NOTE

After the file deletion, when you attempt to switch to the target ECS/HANA ECS using SSH, thesystem displays the fingerprint as well as the message "Are you sure you want to continueconnecting (yes/no)?". In such a case, enter yes and continue the switching.

SAP HANAUser Guide (Console) 3 FAQs

Issue 02 (2016-10-29) 147

4 Appendix

4.1 Logging In to an ECS or HANA ECS Using VNC

Login Notes1. Before logging in to an ECS or HANA ECS using VNC, you must have obtained the

login password.

For instructions about how to obtain a password for logging in to a Windows ECS orWindows HANA ECS, see section Obtaining the Password for Logging In to aWindows ECS. To obtain a password for logging in to a Linux ECS or Linux HANAECS, perform the following operations:

– If the image based on which the ECS or HANA ECS is created meets the followingrequirements, the default image password is the password for logging in to theLinux ECS or Linux HANA ECS using VNC: When Cloud-init is installed,lock_passwd is set to false, indicating that the password authentication mode isenabled. In addition, passwd is set to the default image password.

– If no default image password is set when Cloud-init is installed, you must log in tothe ECS or HANA ECS by following the instructions provided in section LoggingIn to a Linux ECS Using an SSH Key, set the ECS or HANA ECS loginpassword, and then use VNC to log in to the ECS or HANA ECS.

2. When you log in to the ECS using VNC, an English keyboard is used by default. Thesystem also supports keyboards of other languages.

– If using the default keyboard, log in to the ECS without changing the OS keyboard.

– If using a keyboard of another language, select your language of keyboard on theVNC login page and change the keyboard language of the OS to ensure that thekeyboard language configured on the VNC login page is the same as the keyboardlanguage of the OS.

Logging In to an ECS Using an English Keyboard1. Log in to the management console.

2. Click . Under Computing, click Elastic Cloud Server.

SAP HANAUser Guide (Console) 4 Appendix

Issue 02 (2016-10-29) 148

3. In the upper right corner of the ECS list, enter the ECS name and click .

Figure 4-1 Searching for an ECS

4. Locate the row that contains the identified ECS and click Remote Login in theOperation column.

5. In the displayed Configure Keyboard Layout for Remote Login dialog box, select theEnglish keyboard.

Figure 4-2 Configure Keyboard Layout for Remote Login

6. Click Remote Login.7. After the configuration is successful, click Start Remote Login in the displayed dialog

box.

Figure 4-3 Start Remote Login


Issue 02 (2016-10-29) 149

8. On the Linux OS, enter the username and password for logging in to the ECS. Forinstructions about how to obtain the login password, see section Login Notes.On the Windows OS, enter the password for logging in to the ECS. For instructionsabout how to obtain the login password, see section Obtaining the Password forLogging In to a Windows ECS.

Logging In to an ECS Using a Non-English Keyboard1. Log in to the management console.

2. Click . Under Computing, click Elastic Cloud Server.3. In the upper right corner of the ECS list, enter the ECS name, IP address, or ECS ID, and

click .

Figure 4-4 Searching for an ECS

4. Locate the row that contains the identified ECS and click Remote Login in theOperation column.

5. In the displayed Configure Keyboard Layout for Remote Login dialog box, select thekeyboard of your language.– If you log in to the ECS using VNC for the first time, select the default English

keyboard because the ECS OS uses the English keyboard by default.– If you have changed the keyboard language of the ECS OS, select Use another

keyboard layout and the changed keyboard language.

Figure 4-5 Configure Keyboard Layout for Remote Login


Issue 02 (2016-10-29) 150

6. Click Remote Login.7. After the configuration is successful, click Start Remote Login in the displayed dialog

box.

Figure 4-6 Start Remote Login

8. Enter the password for logging in to the ECS.– If you log in to the ECS using VNC for the first time, use the English keyboard to

enter the password. After you have logged in to the ECS, see Changing the OSKeyboard Language to change the keyboard language of the ECS OS so that youcan select the keyboard language and enter the password in your next login.

– If you have changed the keyboard language of the ECS OS, ensure that thekeyboard language in use, the keyboard language selected in 5, and the changed OSkeyboard language are the same.

Changing the OS Keyboard Languagel If the ECS is running Linux, run the following command:

loadkeys keymapfilekeymapfile indicates the name of the mapping file between keyboard keys and displayedcharacters.For example, if the name of a German keyboard mapping file is de, run the loadkeys decommand.

l If the ECS is running Windows, perform the following operations:Switch the input method or open the on-screen keyboard before entering characters.

4.2 Obtaining the Password for Logging In to a WindowsECS

ScenariosPassword authentication mode is required to log in to a Windows ECS. Therefore, you mustuse the key file used when you created the ECS to obtain the administrator password


Issue 02 (2016-10-29) 151

generated when the ECS was initially installed. The administrator user is Administrator orthe user configured using Cloudbase-Init. This password is randomly generated, offering highsecurity.

You can obtain the initial password for logging in to a Windows ECS using either themanagement console or API. For details, see this section.

Obtaining the Password Using the Management Console1. Obtain the private key file (.pem file) used when you created the ECS.2. Log in to the management console.3. Under Computing, click Elastic Cloud Server.4. In the ECS list, select the ECS for which the password is to be obtained.5. In the Operation column, click More and choose Get Password.

Figure 4-7 Obtaining a password

6. Use either of the following methods to obtain the password through the key file:– Click Select File and upload the key file from a local directory.– Copy the key file content to the text field.

7. Click Get Password to obtain a random password.

Obtaining the Password Using the API1. Obtain the private key file (.pem file) used when you created the ECS.2. Set up the API calling environment.3. For details, see section "API Calling" in Elastic Cloud Server API Reference.4. Obtain the ciphertext password.

Call the password calling API to obtain the ciphertext password of the public keyencrypted using RSA. The API URI is in the format "GET /v2/{tenant_id}/servers/{server_id}/os-server-password".

NOTE

For instructions about how to call the API, see section "Retrieving the Password of a WindowsECS (Native OpenStack API)" in Elastic Cloud Server API Reference.

5. Decrypt the ciphertext password.Use the private key file used when you created the ECS to decrypt the ciphertextpassword obtained in step 4.

a. Run the following command to convert the ciphertext password format to ".key -nocrypt" using OpenSSL:


Issue 02 (2016-10-29) 152

https://docs.otc.t-systems.com/api/ecs/en-us_topic_0020805967.html



openssl pkcs8 -topk8 -inform PEM -outform DER -in rsa_pem.key -outpkcs8_der.key -nocrypt

b. Invoke the Java class libraryorg.bouncycastle.jce.provider.BouncyCastleProvider and use the private key fileto edit the code decryption ciphertext.

4.3 Logging In to a Linux ECS Using an SSH Key

Prerequisitesl You have obtained the key file of the ECS.l An elastic IP address has been bound to the ECS.

l You have configured the inbound rules of the security group. For details, see sectionApplying for a Subnet and Configuring a Security Group.

Logging In to the Linux ECS from a Windows Computer

This section describes how to log in to the Linux ECS from a Windows computer.

The following operations use PuTTY as an example to log in to the ECS. Before the login,you must convert the private key format.

1. Visit the following website and download PuTTY and PuTTYgen:http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

NOTE

PuTTYgen is a private key generator, which is used to create an SSH key pair that consists of apublic key and a private key for PuTTY.

2. Run PuTTYgen.3. In the Actions area, click Load and import the private key file stored during HANA ECS

creation.The file to be imported must be in the format of "All files (*.*)".

4. Click Save private key.5. Save the converted private key to the local computer. For example, kp-123.ppk.6. Run PuTTY.7. Choose Connection > data and enter :root in Auto-login username.8. Choose Connection > SSH > Auth. In the last configuration item Private key file for

authentication, click Browse and select the private key converted in step 5.9. Click Session and enter the elastic IP address of the ECS under Host Name (or IP

address).10. Click Open.

The ECS is logged in.

Logging In to the Linux ECS from a Linux Computer

This section describes how to log in to the Linux ECS from a Linux computer. The followingoperations use private key file kp-123.pem as an example to log in to the ECS.


Issue 02 (2016-10-29) 153

1. On the Linux CLI, run the following command to change the permission:chmod 600 /path/kp-123

NOTE

In the preceding command, path specifies where the private key file is saved.

2. Run the following command to log in to the ECS:ssh -i /path/kp-123 root@Elastic IP address

NOTE

l In the preceding command, path specifies where the private key file is saved.

l Elastic IP address is the elastic IP address bound to the ECS.

4.4 Querying the NIC IP Address of an ECS

ScenariosThe IP address of an ECS is required.

Procedure

Step 1 On the Open Telekom Cloud management console, choose Computing > Elastic CloudServer. Click Elastic Cloud Server on the left. Then, all ECSs are displayed on the right sideof the page.

Step 2 Click the name of the HANA ECS to be queried. Then, the page for the HANA ECS details isdisplayed.

Step 3 Click the NIC tab and then in front of the NIC to be queried. Then, query the IP addressin the expanded pane. Figure 4-8 shows an example.

NOTE

l EIP: specifies the EIP bound to the ECS.

l Private IP Address: specifies the private IP address of the ECS NIC.


Issue 02 (2016-10-29) 154

Figure 4-8 NIC IP addresses

----End


Issue 02 (2016-10-29) 155

A Change History

ReleaseDate

What's New

2016-10-29 This issue is the second official release, which incorporates the followingchanges:Added the description of installing the SAP HANA Studio on Linux ECSs.

2016-10-19 This is the first official release.

SAP HANAUser Guide (Console) A Change History

Issue 02 (2016-10-29) 156

B Glossary

For details about the terms involved in this document, see Glossary.

SAP HANAUser Guide (Console) B Glossary

Issue 02 (2016-10-29) 157

https://docs.otc.t-systems.com/en-us/glossary/index.html

user guide (console) - deutsche telekom · the sap hana studio provides management, monitoring, and...

Documents