Cisco Scale-Up Solution for SAP HANA with the …...This section describes the SAP HANA system...

White Paper

© 2017 Cisco and/or its affiliates. All rights reserved. This document is Cisco Public. of 106

Cisco Scale-Up Solution for SAP HANA with the Cisco C880 M4 Server

Design and Deploy a SAP HANA Single-Node Solution Based on Cisco C880 M4

Servers with SUSE Linux Enterprise Server 12 for SAP SP1

April 2017

Contents

Executive Summary

Solution Overview Introduction Audience Purpose of This Document Solution Summary

Infrastructure Overview Cisco C880 M4 Server

Power Cabling Network Components

Solution Design SAP HANA System

Hardware Requirements for the SAP HANA Database SAP HANA File System Layout Operating System

Deployment Hardware and Software Configuration Guidelines

Preparing the SAP HANA Scale-Up Node Configure the Cisco IMC for the Cisco C880 M4 Server Connect to the Management Board Set the Cisco IMC IP Address Log in to the Web User Interface Configure Cisco C880 M4 IMC Settings Configure Cisco C880 M4 BIOS CPU Settings Configure Cisco C880 M4 BIOS Memory Settings Configure Cisco C880 M4 BIOS EFI Boot Settings Configure Cisco C880 M4 BIOS Disk (RAID) Settings for the SAP HANA File System Configure RAID 5 for SAP HANA

Installing the Operating System Boot from OS Installation Media Start the OS Installation for SAP HANA Partition the Disk for the Cisco C880 M4 Intel Broadwell–Based SAP HANA Appliance Create the Boot File Partition Create the Volume Group for SAP HANA Configure the Time Zone Set the Root User Password


Select the Package for the Installation Disable the Firewall and Kernel Dump Set the Default Systemd Target and Run Level Install the Operating System

OS Post-Installation Tasks Start and Register the System Create Logical Volumes and File Systems for SAP HANA Check the /etc/hosts File Set Up Network Time Protocol Service Create High Availability for the Network

Performance Tuning Parameters for SAP HANA Tune the /etc/init.d/after.local File Tune the sysctl. Conf File Disable C-States: Add Parameter to the Bootloader Reboot the Appliance

Patching the Appliance Register the System for Patching Patch SLES for SAP Applications SP1 Reboot the Appliance

Installing SAP HANA Important SAP Notes

SAP HANA In-Memory Database (IMDB) Notes Linux Notes SAP Application Notes Third-Party Software Notes SAP HANA Virtualization Notes

SAP HANA Post-Installation Checkup

SAP HANA Post-Installation Tasks Check the SAP HANA Services Check the HANA Database Information Maintain the Operating System

Prerequisites Updating the OS and Kernel Updating SUSE and the Kernel Online Option 1: Using YaST

SAP HANA Operation and Maintenance Monitoring SAP HANA Starting and Stopping SAP HANA Downloading Revisions

For More Information

Appendix: Solution Variables Used for This Document


Executive Summary

Organizations in every industry are generating and using more data than ever before: from customer transactions

and supplier delivery details to real-time user-consumption statistics. Without reliable infrastructure that can store,

process, and analyze big data sets in real time, companies cannot use this information to their advantage. The

Cisco® C880 M4 Server provides a powerful foundation for scale-up or scale-out SAP HANA solutions. With eight

Intel® Xeon

® processor E7-8890 v2, E7-8880 v3, or E7-8890 v4 series CPUs, the C880 is configured for SAP

HANA deployments, including analytic workloads such as SAP Business Warehouse and transactional workloads

such as SAP Enterprise Resource Planning (ERP), Customer Relationship Management (CRM), and SAP

Business Suite 4 SAP HANA (S4/HANA).

Solution Overview

Introduction

The Cisco C880 M4 Server scale-up solution provides prevalidated, ready-to-deploy infrastructure, reducing the

time and complexity involved in configuring and validating a traditional data center deployment. The reference

architecture detailed in this document highlights the resiliency and ease of deployment of a SAP HANA solution.

SAP HANA is SAP’s implementation of in-memory database technology. The SAP HANA database takes

advantage of the low-cost main memory (RAM), faster access, and data-processing capabilities of multicore

processors to provide better performance for analytical and transactional applications. SAP HANA offers a multiple-

engine query-processing environment that supports relational data (with both row- and column-oriented physical

representations in a hybrid engine) as well as graph and text processing for semistructured and unstructured data

management within the same system. As an appliance, SAP HANA combines software components from SAP

optimized for certified hardware. However, this solution has a preconfigured hardware setup and preinstalled

software package that is dedicated to SAP HANA. In 2013, SAP introduced the SAP HANA Tailored Datacenter

Integration (TDI) option. TDI offers a more open and flexible way to integrate SAP HANA into the data center by

reusing existing enterprise storage hardware, thereby reducing hardware costs. With the introduction of SAP HANA

TDI for shared infrastructure, the Cisco UCS® Integrated Infrastructure solution provides the advantages of an

integrated computing, storage, and network stack and the programmability of the Cisco Unified Computing

System™ (Cisco UCS®) platform. The TDI option enables organizations to run multiple SAP HANA production

systems on a shared infrastructure. It also enables customers to run SAP application servers and SAP HANA

databases hosted on the same infrastructure.

For more information about SAP HANA, see the SAP help portal: http://help.sap.com/hana/.

Audience

The intended audience for this document includes sales engineers, field consultants, professional services staff, IT

managers, partner engineers, and customers deploying the Cisco solution for SAP HANA. External references are

provided wherever applicable, but readers are expected to be familiar with the technology, infrastructure, and

database security policies of the customer installation.

Purpose of This Document

This document describes the steps required to deploy and configure a Cisco data center solution for SAP HANA.

This document showcases one of the variants of Cisco’s solution for SAP HANA. Although readers of this

document are expected to have sufficient knowledge to install and configure the products used, the document

provides configuration details that are important to the deployment of this solution.

http://help.sap.com/hana/


Solution Summary

The Cisco Scale-Up Solution for SAP HANA is based on the Cisco C880 M4 Server. Tables 1, 2, and 3 summarize

the server specifications and show proposed disk configurations for the SAP HANA use case.

Table 1. Overview of Cisco C880 M4 Server Configuration

Item Configuration

CPU 8 x 2.20-GHz Intel Xeon processor E7-8890 v4 CPUs

Possible memory configurations ● 64 x 32-GB DDR4 (2 TB)

● 96 x 32-GB DDR4 (3 TB)

● 128 x 32-GB DDR4 (4 TB)

● 192 x 32-GB DDR4 (6 TB)

Hard-disk drive (HDD) type and quantity 44 x 1.2-TB 10,000-rpm SAS drives (in 2 x JXS2 JBODs)

BIOS Release 1.21 or later

Unified firmware Release BC160063 or later

LSI MegaRAID controller LSI EP420e 12-Gbps SAS modular RAID controller

Network card ● Onboard Intel 1 Gigabit Ethernet controller (4 ports)

● PCIe Intel 10 Gigabit Ethernet controller (8 ports)

Power supply 4 redundant power supplies

Table 2. Cisco C880 M4 Proposed Disk Layout

Disk Disk Type Drive Group RAID Level Virtual Drive

2 x JXS2 (44 drives)

SAS DG 0 to DG 5

(6 drives per group)

5 VD 0 to VD 5

Table 3. Cisco C880 M4 Proposed Disk Configuration

Drives Used RAID Type Used for File System

44 x 1.2-TB SAS drives RAID 5 Operating system ext3

Data file system XFS

Log file system XFS

SAP HANA shared file system XFS


Infrastructure Overview

Cisco C880 M4 Server

The images below and Figure 1 show the Cisco C880 M4 Server.

Cisco C880 M4 Front View: System Boards


Figure 1. Cisco C880 M4 Rear View: Connectors

Make sure that the power supplies and fan units are placed in the slots as shown in Figure 2.

The slot next to the SAS controller is used by the battery pack from the SAS controller (Figure 3).

Figure 2. Installed SAS Adapter with I/O Unit (IOU)

Connect the SAS “In” port of the JBOD to the SAS RAID connector in the chassis as shown in Figure 3.


Figure 3. Cisco C880 M4 and JBOD Connectivity

Power Cabling

The standard power supply setup is 3+1. Therefore, power supplies must be connected to one grid, and the server

tolerates the failure of one power supply. However, a grid failure is not protected.

To protect against a grid failure, each power supply must be connected to a completely separate grid connection.

This setup is the preferred installation and is recommended to the customer.

Table 4 shows the power supply requirements and redundancy.

Table 4. Power Supply and Redundancy

AC Power Input Power Feed Redundancy Number of PSUs PSU Slot

240V Single Nonredundant 3 0, 1, and 3

Single Redundant 4 0, 1, 3, and 4

Dual - 6 All

As shown in Table 4, to have redundancy at least a pair of power supplies from the same row—that is, 0 and 1 or 3

and 4—should be available as a pair.

Table 5 shows possible the PSU and fan unit combinations.


Table 5. PSU and Fan Unit Combinations

Number of PSUs and Fans

PSU Fan

3 3

4 2

6 No

Network Components

The Cisco UCS C880 M4 Server is equipped with a management board (MMB) for remote management over the

network. This board includes virtual keyboard, video, and mouse (KVM) access at the hardware level (Figure 4).

Figure 4. Cisco C880 M4 MMB 0 Connectors

User port 0 or 1 of the IMC must be connected to the console network at the customer’s location.

Solution Design

This section describes the SAP HANA system requirements defined by SAP and the architecture of the Cisco UCS

solution for SAP HANA.

SAP HANA System

An SAP HANA scale-up system on a single server is the simplest of the installation types. It is possible to run an

SAP HANA system entirely on one host and then scale the system up as needed. All data and processes are

located on the same server and can be accessed locally. The network requirements for this option are at least one

1 Gigabit Ethernet access network and one 10 Gigabit Ethernet storage network.

Hardware Requirements for the SAP HANA Database

SAP defines hardware and software requirements for running SAP HANA systems. For the latest information about

the CPU and memory configurations supported for SAP HANA, refer to

https://global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/index.html.

Note: This document does not cover the updated information published by SAP. Additional information is

available at http://saphana.com.

SAP HANA File System Layout

Figure 5 shows the file system layout and the required storage sizes for installing and operating SAP HANA. When

installing SAP HANA on a host, specify the mount point for the installation binary files (/hana/shared/<sid>), data

files (/hana/data/<sid>), and log files (/hana/log/<sid>), where sid is the instance identifier of the SAP HANA

installation.

https://global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/index.html

http://saphana.com/


Figure 5. Proposed Disk Layout with Partition Mapping

/dev/sda2, /dev/sdb1, /dev/sdc1, /dev/sdd1, /dev/sde1, /dev/sdf1

JBOD 1

RAID 5 (/dev/sda)

RAID 5 (/dev/sdb)

RAID 5 (/dev/sdc)

Hot Spare

Disk 21

JBOD 2

RAID 5 (/dev/sdd)

RAID 5 (/dev/sde)

RAID 5 (/dev/sdf)

Hot Spare

Disk 21

/dev/sda1

/dev/sda1|P

/boot/efi

hanavg|

VG

rootvol|

LV/

swapvol|

LV“swap”

datavol|

LV/hana/data

sapmnt|

LV/hana/shared

logvol|

LV/hana/log

The storage size for the file system is based on the amount of memory on the SAP HANA host.

The following list shows sample file system sizes for a single-node system with 2 TB of memory:

● /hana/shared: 1 x memory (2 TB)

● /hana/data: 3 x memory (6 TB)

● /hana/log: 1 x memory (512 GB)

For solutions based on the Intel Xeon processor E7-88x0 v4 CPU, the size of the log volume must be as follows:

● Half of the server memory for systems ≤ 256 GB of memory

● Minimum of 512 GB for systems with ≥ 512 GB of memory

Operating System

SAP HANA supports the following operating systems:

● SUSE Linux Enterprise Server (SLES) for SAP applications

● Red Hat Enterprise Linux (RHEL) for SAP HANA

Note: This document provides installation steps for SLES 12 for SAP SP1.


Deployment Hardware and Software Configuration Guidelines

This section is intended to enable you to fully configure the customer environment. In this process, various steps

require you to insert customer-specific naming conventions, IP addresses, and VLAN schemes, as well as to

record appropriate MAC addresses. Table 6 lists the configuration variables that are used throughout this

document. This table can be completed based on the specific site variables and used in implementing the

configuration steps presented in this document.

Table 6. Configuration Variables

Variable Description Customer Implementation Value

<<var_imc_ip_address>> Cisco C880 M4 Server’s IMC IP address

<<var_imc_ip_netmask>> Cisco C880 M4 Server’s IMC network netmask

<<var_imc_gateway_ip>> Cisco C880 M4 Server’s IMC network gateway IP address

<<var_console_redirection_ip_address>> Cisco C880 M4 Server’s KVM console redirection IP address

<<var_console_redirection_ntmask>> Cisco C880 M4 Server’s KVM console redirection netmask

<<var_raid5_vd_name>> Name for virtual drive VD 0 during RAID configuration

<<var_hostname.domain>> SAP HANA node’s fully qualified domain name (FQDN)

<<var_sys_root-pw>> SAP HANA node’s root password

<<var_lvm_vg_name>> SAP HANA node’s OS logical volume management (LVM) volume group name

<<var_mgmt_ip_address>> SAP HANA node’s management and administration IP address

<<var_mgmt_nw_netmask>> SAP HANA node’s management network netmask

<<var_mgmt_gateway_ip>> Cisco C880 M4 Server’s management and administrative network gateway IP address

<<var_mgmt_netmask_prefix>> Netmask prefix in Classless Inter-Domain Routing (CIDR) notation

<<var_suse_reg_key>> SuSE License key for the system registration

Preparing the SAP HANA Scale-Up Node

This section describes how to prepare the Cisco C880 M4 Server for the SAP HANA scale-up solution.

Configure the Cisco IMC for the Cisco C880 M4 Server

To configure the on-board IMC, connect a RS-232 cable to the COM port for the initial setup.

The user ports (IMC ports) will be connected to the customer management network and VLAN to access the IMC

over a web browser. These two ports work as clustered ports (Figure 6).


Figure 6. Cisco C880 M4 and MMB Connections

Note: After turning on the power, wait for the Ready (RDY) and Active (ACT) LEDs to be in a stable green state

before performing the initial setup.

Connect to the Management Board

Follow these steps to connect to the MMB:

1. After you turn on the power, the MMB initialization process starts. During the initialization process, verify that

the MMB RDY LED flashes and that the Alarm LED of the unit in the front is on.

2. After the initialization process is complete, verify that the MMB RDY LED changes from a flashing light to a

steady light.

3. Verify that the COM port of the MMB is connected to the technicians system.

4. To set the IP address for the IMC, open a new serial connection using PuTTY with the settings shown in Table

7.

Table 7. Cisco IMC Settings

Item Value

Baud rate 19200

Data bit 8

Parity bit None

Stop bit 1

Flow control None

Emulation VT100

Note: The initialization process for the MMB takes about 6 minutes to complete.

5. After the serial connection has been opened, you will see an initial message and login prompt on the terminal

software screen. Enter the login name Administrator. This is a preset default administrator user account name.

After you enter this user name, you are requested to change your password immediately.

6. Enter a new password and reenter the same password for confirmation.

Cisco-1541432026 login: Administrator

You are required to change the password immediately (root enforced)

MMB Connectors View

RS - 232 Cable

RJ - 45 Connection

Customer Management Network

Cisco IMC Ports

100 MB ps


New password:

Retype New password:

Administrator >

Set the Cisco IMC IP Address

Now set the IMC IP address.

1. Verify that the IMC ports are connected to the Customer management network as shown in Figure 6 above.

2. After resetting the password as shown in the preceding section, enter the commands shown here to set the

IMC IP address and enable HTTP and Telnet access:

Administrator> set ip <<var_imc_ip_address>> <<var_imc_ip_netmask>>

Administrator> set gateway <<var_imc_gateway_ip>>

Administrator> set http enable

Administrator> set telnet enable

3. The default HTTP port is 8081. You can change this setting if necessary by entering the following command:

Administrator> set http_port 80

4. Set the host name of the system:

Administrator > set hostname cishanar08-c880

Log in to the Web User Interface

Now log in to the web user interface and make some initial settings.

1. Use Table 8 to log in to the web user interface. Figure 7 shows the login screen.

Table 8. Web User Interface Login Settings

Item Value

URL http://<IMC IP address>

User name Administrator

Password Administrator’s password


Figure 7. Cisco C880 M4: Cisco IMC Web User Interface Login Screen

After you log in, the System Status page appears (Figure 8).

Figure 8. Cisco C880 M4: System Status and Health Page After Initial Login

2. Configure the power supply mode as shown in Figure 9.


Figure 9. Configuring the Power Supply Mode

For Power Feed Mode:

● Single-feed mode = 4 PSUs

● Dual-feed mode = 6 PSUs

3. Set PSU Redundant Mode to Redundant. The system status should change to Normal.

Configure Cisco C880 M4 IMC Settings

Configure the IMC.

1. Open a web browser and connect to the IMC web user Interface as explained in the previous section.

2. From the homepage, choose System > Console Redirection Setup > IPv4 Console Redirection Setup (Figure

10).


Figure 10. Cisco C880 M4: Console Redirection for KVM

3. Enter the IP address <<var_console_redirection_ip_address>> and

<<var_console_redirection_netmask>> on the page. Select Enable for both the Video Redirection and

Virtual Media options. Then click the Apply button at the bottom of the page.

4. On the side menu, select Console Redirection.

5. Select the Video Direction check box and click the Apply button at the bottom of the page. The KVM pop-up

window will open (Figure 11).

Figure 11. Cisco C880 M4: Opening the KVM Window

6. Configure the memory performance mode as shown in Figure 12.


Figure 12. Configuring Memory Performance Mode

7. Ignore the wake-on-LAN (WOL) settings. These should all be disabled.

8. Power on the system and start the EFI boot manager (Figure 13).

Figure 13. Cisco C880 M4: Powering on the System


9. For Power Control, choose Power On, and set Boot Selector to Force Boot into EFI Boot Manager. Then click

Apply at the bottom of the page. The KVM initial screen appears (Figure 14).

Note: The virtual console can take up to 20 minutes before it displays the initial boot screen.

Figure 14. Cisco C880 M4: KVM Initial Screen

10. Select the Media menu and choose Virtual Media Wizard (Figure 15).


Figure 15. Cisco C880 M4: Selecting the Media Menu

11. Select and mount the ISO image. Browse the SLES 12 for SAP SP1 ISO file and click Connect CD/DVD

(Figure 16).


Figure 16. Cisco C880 M4: Selecting and Mounting the ISO Image

Configure Cisco C880 M4 BIOS CPU Settings

Follow these steps to configure the CPU settings:

1. After the server boots, it displays the BIOS menu. Select Device Manager from the menu (Figure 17).


Figure 17. EFI Boot Manager: Select Device Manager

2. Select the CPU Configuration option (Figure 18).


Figure 18. Select CPU Configuration

The CPU Configuration screen appears (Figure 19).

Figure 19. CPU Configuration Screen


2. Disable Intel Virtualization Technology (if you not plan to use this system with VMware).

3. Set Power Technology to Custom and disable all C-states (Figure 20).

Figure 20. CPU Configuration Settings

4. Enable Uncore Frequency Override.

5. Select Commit Changes and Exit and press Enter (Figure 21).


Figure 21. Commit the CPU Configuration Settings

6. Press Esc to exit from the menu and return to the main BIOS menu.

Configure Cisco C880 M4 BIOS Memory Settings

Follow these steps to configure the memory settings:

1. Select Memory Configuration from the BIOS menu (Figure 22).


Figure 22. Select Memory Configuration

2. Configure the memory settings as shown in Figure 23.


Figure 23. Configure the Performance Mode for the DDR4 Memory

3. Select Commit Changes and Exit and press Enter.

4. Press Esc to exit from the menu and return to the main BIOS menu.

Configure Cisco C880 M4 BIOS EFI Boot Settings

Follow these steps to configure the EFI boot settings:

1. Select Device Manager from the main BIOS menu (Figure 24).

Figure 24. Configuring the System for EFI Boot Mode Only

2. Select PCI Subsystem Configuration (Figure 25).


Figure 25. Configuring Boot Settings

3. Select EFI Compatible ROM for PCI ROM Priority (Figure 26).

Figure 26. Selecting the ROM Priority

4. Select Commit Changes and Exit and press Enter.

5. From the Main Menu, select Boot Maintenance Manager (Figure 27).

Figure 27. Selecting Boot Maintenance Manager

6. Select Boot Mode from the list of options (Figure 28).

Figure 28. Selecting Boot Mode

7. For Boot Mode, select Only UEFI (Figure 29).

Figure 29. Selecting UEFI Boot Mode

8. Select Reset System to make the changes take effect (Figure 30).


Figure 30. Selecting Reset System to Make the Changes Effective

Configure Cisco C880 M4 BIOS Disk (RAID) Settings for the SAP HANA File System

Follow these steps to configure the RAID settings for the SAP HANA file system:

1. Select Device Manager from the menu (Figure 31).

Figure 31. Select Device Manager from the Cisco C880 M4 BIOS Main Menu


2. Select the LSI Mega Raid Configuration utility to create the virtual disk (Figure 32).

Figure 32. Cisco C880 M4 RAID Configuration Utility

You will be creating six RAID 5 groups with seven drives in each group. These six groups will be placed as three

groups per JBOD.

Refer the disk layout image in Figure 6 to better understand the proposed disk layout for the Cisco C880 M4

Server.

Configure RAID 5 for SAP HANA

Now create six virtual drives with RAID 5. Each virtual drive will have seven drives associated with it. Follow the

steps here until all six virtual drives are created.

Be sure that the settings for the virtual drives are identical. If they are not, SAP HANA performance will be

degraded.

Refer the proposed disk layout in Figure 6.

Note: The steps in this section create a single RAID 5 virtual drive. Repeat these steps to create six RAID 5

virtual drives for the appliance installation.

1. Select Configuration Management from the Main Menu (Figure 33).


Figure 33. Cisco C880 M4 RAID Configuration 1

2. Select Create Virtual Drive – Advanced (Figure 34).



Note: You need to create six virtual drives, each with seven physical disks, so repeat the steps here until all six

virtual drives are created.

3. Select RAID5 from the list (Figure 35).



4. Choose Select Drives and press Return (Figure 36).



5. Select the first seven drives. Be sure that the drives are from the same JBOD.

6. Select Apply Changes and press Enter (Figure 37).



7. After the changes are applied, you will see a confirmation screen. Click OK to proceed with the next steps

(Figure 38).



8. Enter the virtual drive name. The Virtual Drive Size field is autopopulated.

Note: The parameters in steps 9 through 13 are very important. They will manage the performance of the SAP

HANA that will be installed. Hence, be sure to set the correct values.

9. For Strip Size, specify 256 KB.

10. For Read Policy, specify Read Ahead.

11. For Write Policy, specify Write Back.

12. For I/O Policy, specify Direct.

13. For Drive Cache, specify Unchanged.

14. Select Save Configuration and press Enter (Figure 39).



Note: There are six RAID 5 virtual drives in total to be created with the same steps just described.

15. Select Confirm and then Yes to save the configuration (Figure 40).



16. Repeat the same RAID 5 configuration process for the SAP HANA file system to create all six virtual drives.

17. Proceed to the next section only after all six virtual drives are created.

Installing the Operating System

This section describes how to install the OS.

Boot from OS Installation Media

Follow these steps to boot the OS from the installation media:

1. Select Boot Manager from the Main Menu (Figure 41).


Figure 41. Cisco C880 M4 BIOS Main Menu

2. Since we are mapping the ISO to the first virtual CD-ROM, Select the EFI: Fujitsu Virtual CD-ROM0 1.00

drive to install the OS in EFI mode (Figure 42).


Figure 42. Cisco C880 M4 EFI Boot CD-ROM

Start the OS Installation for SAP HANA

Now start the OS installation process.

1. On the initial OS screen, select the Installation option and press Enter to continue (Figure 43).


Figure 43. Installing SLES

2. Accept the license terms by checking the box and clicking Next (Figure 44).


Figure 44. Cisco C880 M4 OS Installation for SAP HANA: Accept License Terms

The installer will now initialize the network configuration (Figure 45).


Figure 45. Cisco C880 M4 OS Installation for SAP HANA: Network Initialization

Note: You can apply the network settings at this time, or you can skip this process and assign the settings after

the OS installation process is complete. In this document, the network settings are configured at the time of OS

installation.

3. Configure the server to have two bond interfaces: one with a 1-Gbps interface for the administrative network,

and one with a 10-Gbps interface for the application network. This configuration can be changed as needed

according to the customer’s network infrastructure and requirements.

4. Check for the interface to which the network cables are connected. This step is important because you will be

creating the bond interfaces for network redundancy.

5. Click Skip Registration (Figure 46). You can skip the Registration page at this time. You can perform

registration after you successfully complete the OS installation process.


Figure 46. Cisco C880 M4 OS Installation for SAP HANA: Registration Page

6. A prompt will appear asking whether you want to skip registration. Click Yes on this screen (Figure 47).


Figure 47. Cisco C880 M4 OS Installation for SAP HANA: Skip Registration

7. For the installation mode, select Standard SLES for SAP Applications Installation (Figure 48).


Figure 48. Cisco C880 M4 OS Installation for SAP HANA: Installation Mode

8. On the Add On Product screen, leave the defaults and click Next (Figure 49).


Figure 49. Cisco C880 M4 OS Installation for SAP HANA: Add On Product Screen

Partition the Disk for the Cisco C880 M4 Intel Broadwell–Based SAP HANA Appliance

Refer the proposed disk layout for the Cisco C880 M4 in Figure 6 to understand the disk partitioning scheme.

The boot, root, and swap volumes will be created during the installation process. The remaining volumes and file

systems can be created after the OS installation is complete.

1. On the Suggested Partitioning screen, select Create Partition Setup (Figure 50).


Figure 50. Cisco C880 M4 OS Installation for SAP HANA: Disk Partitioning 1

2. The installer probes for the hard drives that are available from the RAID card. Six drives should be available.

On the Preparing Hard Disk screen, select Custom Partitioning. Then click Next (Figure 51).



The installer lists the available drives (Figure 52).



Create the Boot File Partition

Follow these steps to create the boot partition:

1. With the disk /dev/sda, create the partition /dev/sda1 for /boot/efi. Create the partition /dev/sda2 for the LVM.

2. For the boot partition file system type, specify file allocation table (FAT). For the file system ID, specify 0x103

(EFI Boot), as shown in Table 9 and Figure 53.

Table 9. Boot File Partition Settings

Mount Point File System Size

/boot/efi FAT 200 MB



Create the Volume Group for SAP HANA

After the boot partition is created, the next step is to create the volume group for the operating system. Table 10

shows the volume group settings for SAP HANA.

Table 10. Volume Group Settings

Logical Volume File System Size

/ Ext3 100 GB

Swap Swap 2 GB

1. Under System View, select Volume Management.

2. Click Add and choose Volume Group (Figure 54).


Figure 54. Cisco C880 M4 OS Installation for SAP HANA: LVM Setup 1

3. Enter the volume group name and leave the physical extent size set to 4 MB.

4. From the available physical drives, choose the six virtual drives that were created with the RAID 5: that is,

/dev/sda2 to /dev/sdf1.

5. Click Add All and then click Finish (Figure 55).



6. Now create the logical volumes. In the Logical Management pane, click Add and choose Logical Volume

(Figure 56).



7. For the logical volume name, enter rootvol. Then click Next (Figure 57).



8. Select Custom Size.

9. For the size, enter 100 GB. Then click Next (Figure 58).



10. For the role, select Raw Volume. Then click Next (Figure 59).



11. Select the Format Partition option. For the file system type, choose Ext3. For the mount point, choose /. Then

click Next (Figure 60).



12. The root volume is now created. Next step is to create the swap volume.

13. Click on Add -> Logical volume



14. Name the logical volume for the swap file swapvol. Click Next (Figure 62).



15. For the size, enter 2 GB. Click Next (Figure 63).


16. For the role, select Swap. Then click Next (Figure 64).


17. Configure the settings as shown in Figure 65.



18. Click Finish.

19. Click Accept (Figure 66) to return to the Installation Settings page.



Note: You have created only the volume group and not the logical volumes. Because you are going to use

striped logical volumes, you will create them after the OS installation is complete.

Configure the Time Zone

The next step is to set the time zone.

1. Select the appropriate time zone.

2. Select the check box for Hardware Clock Set to UTC (Figure 67).


Figure 67. Cisco C880 M4 OS Installation for SAP HANA: Time Zone Configuration

Set the Root User Password

Enter a password <<var_sys_root_pwd>> for the root user (Figure 68).


Figure 68. Cisco C880 M4 OS Installation for SAP HANA: Set Root Password

Select the Package for the Installation

Now select the installation package.

1. On the Installation Settings page, click Software to select the Software installation package (Figure 69)


Figure 69. Cisco C880 M4 OS Installation for SAP HANA: Installation Settings

2. Unselect GNOME Desktop Environment.

3. Select C/C++ Compiler and Tools.

4. Select SAP HANA Server Base.

5. Click OK (Figure 70).


Figure 70. Cisco C880 M4 OS Installation for SAP HANA: Package Selection

Disable the Firewall and Kernel Dump

Follow these steps to disable the firewall and kernel dump (kdump):

1. On the Installation Settings screen, click Firewall and SSH (Figure 71).


Figure 71. Cisco C880 M4 OS Installation for SAP HANA: Disabling the Firewall 1

2. Uncheck the Enable Firewall box and click OK (Figure 72).


Figure 72. Cisco C880 M4 OS Installation for SAP HANA: Disabling the Firewall 2

3. Click Kdump and select Disable Kdump to disable this feature. Then click OK (Figure 73).


Figure 73. Cisco C880 M4 OS Installation for SAP HANA: Disabling Kdump

Set the Default Systemd Target and Run Level

Follow these steps to set the default boot mode and run level:

1. On the Installation Settings screen, click Default systemd Target to change the run level.

2. Select Text Mode to set run-level 3. Then click OK (Figure 74).


Figure 74. Cisco C880 M4 OS Installation for SAP HANA: Setting the Default Boot Mode

Install the Operating System

After you have completed all the preceding steps, the OS is ready for installation.

1. Click the Install button to start the installation (Figure 75).


Figure 75. Cisco C880 M4 OS Installation for SAP HANA: Ready to Install the OS

2. The installer will ask for confirmation to install the dependency packages that are required. Click Continue.

3. The next screen will ask for the confirmation to install the release notes for SLES for SAP. Click Continue. The

installation will start from the disk partitioning process as defined in the previous steps (Figure 76).


Figure 76. Cisco C880 M4 OS Installation for SAP HANA: Starting the Installation

After the installer completes the installation of the packages, the server will reboot automatically, completing the

installation (Figure 77).


Figure 77. Cisco C880 M4 OS Installation for SAP HANA: Installation Complete

OS Post-Installation Tasks

After installing the OS, you should perform several tasks.

Start and Register the System

Start at the KVM console welcome screen (Figure 78).

Figure 78. KVM Console Welcome Screen


1. Use the KVM console to log in to the installed system as the user root with the password <<var_sys_root-

pw>> (Figure 79).

Figure 79. Log in as root

2. Configure the host name and disable IPv6. Enter the following command:

#yast2

3. Choose System > Network Settings (Figure 80).

Figure 80. YaST Control Center: Network Settings

4. Press Alt+S to select the Hostname/DNS tab (Figure 81).

Figure 81. YaST Control Center: Hostname/DNS

5. Enter <<var_hostname.domain>>. Also enter the DNS server address of your network for resolution, if any.

Press Alt+O.


6. Press Alt+G to select the Global Options tab. Disable IPv6 by unselecting the Enable IPv6 option as shown in

Figure 83. Note that changing the IPv6 setting requires a reboot to make effect the change take effect.

Figure 82. YaST: Disabling IPv6 Setting

7. Press Alt+O to save the network configuration. Press Alt+Q to quit the YaST Control center.

8. Reboot the system to make the IPv6 change and the host name settings take effect:

#reboot

9. Identify the Ethernet interface port that is connected to the top-of-the-rack (ToR) switch. For now, you can use

that port for management connectivity to the host. You can also check the port by using ifconfig command, as

shown in Figure 83.

Figure 83. Network Interface Configuration

10. Assign <<var_mgmt_ip_address>> as the IP address and enter <<var_mgmt_nw_netmask>> as the

subnet mask for the available interface (for example, eth5 as in Figure 84. You can use this configuration

temporarily until you port it to a high-availability bond device and create another with the Cisco VIC’s 10-Gbps

ports.

Go to the network configuration directory and create a configuration for eth5:

#cd /etc/sysconfig/network

#vi ifcfg-eth5

BOOTROTO=’static’

IPADDR=’<<var_mgmt_ip_address>>’


NETMASK=’<<var_mgmt_nw_netmask>>’

NETWORK=’’

MTU=’’

REMOTE_IPADDR=’’

STARTMODE=’auto’

USERCONTROL=’no’

11. Add the default gateway:

#cd /etc/sysconfig/network

# vi routes

default <<var_mgmt_gateway_ip>> - -

Note: Be sure that the system has access to the Internet or a SUSE update server to install the patches.

12. Set up a proxy service if no direct Internet connection is available so that the appliance can reach the Internet

(Figure 84):

#yast2

Figure 84. YaST: Proxy Configuration 1

13. Enter the proxy server and port as shown in the sample configuration in Figure 86. Select OK and then quit

YaST to save the configuration.


Figure 85. YaST Proxy Configuration 2

14. Register the system with SUSE to get the latest patches. For more information, refer to the SUSE

knowledgebase article at https://www.suse.com/de-de/support/kb/doc?id=7016626.

The system must have access to the Internet to proceed with this step.

#SUSEConnect -r <<registration_code>> -e <<email_address>>

Create Logical Volumes and File Systems for SAP HANA

The system does not have the file systems needed to install and start SAP HANA. To create the logical volumes

and file systems, follow the instructions here.

1. Log on to the system as the root user.

2. Check the partitions:

cishanar08-c880:~ # df -h

Filesystem Size Used Avail Use% Mounted on

/dev/hanavg/rootvol 99G 18G 76G 20% /

udev 3.0T 644K 3.0T 1% /dev

tmpfs 3.0T 652K 3.0T 1% /dev/shm

/dev/sda1 195M 13M 183M 7% /boot/efi

cishanar08-c880:~ #

3. Before creating the logical volumes and the file system, you need to align all six virtual disks to get optimal

performance. Enter the parted console to perform the disk alignment for /dev/sdb and run the commands

shown here. Align all the virtual drives in a similar way.

cishanar08-c880:~ # parted /dev/sda2

GNU Parted 2.3

Using /dev/sdb

https://www.suse.com/de-de/support/kb/doc?id=7016626


Welcome to GNU Parted! Type 'help' to view a list of commands.

(parted) align-check

alignment type(min/opt) [optimal]/minimal? optimal

Partition number? 1

1 aligned

(parted) quit

cishanar08-c880:~ #

Note: Perform step 3 for all six virtual drives individually: /dev/sdb, /dev/sdc, /dev/sdd, /dev/sde, and /dev/sdf.

4. Check the volume group:

cishanar08-c880:~ # vgdisplay

--- Volume group ---

VG Name hanavg

System ID

Format lvm2

Metadata Areas 6

Metadata Sequence No 6

VG Access read/write

VG Status resizable

MAX LV 0

Cur LV 0

Open LV 0

Max PV 0

Cur PV 6

Act PV 6 (represents the 6 RAID5 Virtual drives)

VG Size 32.50 TiB

PE Size 4.00 MiB

Total PE 6422520

Alloc PE / Size 0 / 0

Free PE / Size 6422520 / 32.40 TiB

VG UUID NiEThW-Haup-kI8s-E0ux-3YB6-5lbn-fXCpux

cishanar08-c880:~ #

5. Create striped logical volumes for the SAP HANA file systems to achieve optimal performance.

cishanar08-c880:~ # lvcreate -L 6T -i 6 -I 256k -n datavol hanavg

Logical volume “datavol” successfully created

cishanar08-c880:~ # lvcreate -L 512G -i 6 -I 256k -n logvol hanavg

Logical volume “logvol” successfully created

cishanar08-c880:~ # lvcreate -L 2T -i 6 -I 256k -n sapmnt hanavg

Logical volume “sapmnt” successfully created


cishanar08-c880:~ #

Note that the size parameter specified here is for an appliance with a 2-TB memory configuration. Adapt this size

parameter as needed to match the memory configuration of the appliance that is being installed. See Table 11 for

reference.

Table 11. SAP Recommended File System Sizes

File System SAP Recommended Size

/hana/data 3 x physical memory

/hana/shared 1 x physical memory

/hana/log 512 GB for physical memory: ≥ 512 GB

Half of RAM for physical memory: < 512 GB

Now create the file systems for SAP HANA.

6. After the logical volumes have been created, format these volumes for the file systems. Here, XFS is used as

the file system for all three logical volumes:

cishanar08-c880:~ # mkfs.xfs -b size=4096 /dev/hanavg/datavol

<…. Output Truncated…..>

cishanar08-c880:~ # mkfs.xfs -b size=4096 /dev/hanavg/logvol


cishanar08-c880:~ # mkfs.xfs -b size=4096 /dev/hanavg/sapmnt


cishanar08-c880:~ #

Now update the /etc/fstab file.

7. Create the mount-point directories to mount the file systems:

cishanar08-c880:~ # mkdir –p /hana/{data,log,shared}

cishanar08-c880:~ #

8. Edit the /etc/fstab file to add these mount points and file systems with the following parameters:

cishanar08-c880:~ # cat /etc/fstab

/dev/hanavg/swapvol swap swap defaults 0 0

/dev/hanavg/rootvol / ext3 acl,user_xattr 1 1

/dev/sda1 /boot/efi vfat umask=0002,utf8=true 0 0

/dev/hanavg/datavol /hana/data xfs

nobarrier,noatime,nodiratime,logbufs=8,logbsize=256k,async 1 2

/dev/hanavg/logvol /hana/log xfs

nobarrier,noatime,nodiratime,logbufs=8,logbsize=256k,async 1 2

/dev/hanavg/sapmnt /hana/shared xfs defaults 1 2

proc /proc proc defaults 0 0

sysfs /sys sysfs noauto 0 0


debugfs /sys/kernel/debug debugfs noauto 0 0

usbfs /proc/bus/usb usbfs noauto 0 0

devpts /dev/pts devpts mode=0620,gid=5 0 0

cishanar08-c880:~ # mount -a

9. Turn on LVM service:

cishanar08-c880:~ # service boot.lvm start

cishanar08-c880:~ # chkconfig boot.lvm on

Check the /etc/hosts File

Check /etc/hosts for the FQDN host name and the short name as shown in the

following example:

cishanar08-c880:~ # cat /etc/hosts

#

# hosts This file describes a number of hostname-to-address

# mappings for the TCP/IP subsystem. It is mostly

# used at boot time, when no name servers are running.

# On small systems, this file can be used instead of a

# "named" name server.

# Syntax:

#

# IP-Address Full-Qualified-Hostname Short-Hostname

#

127.0.0.1 localhost localhost

172.16.1.199 cishanar08-c880.wdf.sap.corp cishanar08-c880

10.68.205.18 cishanar08-c880.wdf.sap.corp cishanar08-c880

cishanar08-c880:~ #

Set Up Network Time Protocol Service

Edit the file /etc/ntp.conf to reflect the appropriate Network Time Protocol (NTP) servers for the region and start the

NTP service:

cishanar08-c880:~ # service ntp start

Starting network time protocol daemon (NTPD) done

cishanar08-c880:~ # ps -ef | grep ntp

ntp 58119 1 0 13:18 ? 00:00:00 /usr/sbin/ntpd -p

/var/run/ntp/ntpd.pid -g -u ntp:ntp -i /var/lib/ntp -c /etc/ntp.conf

root 58124 58027 0 13:18 pts/1 00:00:00 grep ntp

cishanar08-c880:~ #


Create High Availability for the Network

Follow the steps here to create a high-availability network.

1. Create 1-Gbps bond device ifcfg-bond0 with two interfaces as slaves.

a. Create a bond0 configuration file (eth4 and eth5 are used as examples here):

# vi /etc/sysconfig/network/ifcfg-bond0

BONDING_MASTER='yes'

BONDING_MODULE_OPTS='mode=active-backup miimon=100'

BOOTPROTO='static'

BROADCAST=''

ETHTOOL_OPTIONS=''

IPADDR=’<<var_mgmt_ip_address>>/<<var_mgmt_netmask_prefix>>’

MTU=''

NAME=''

NETWORK=''

REMOTE_IPADDR=''

STARTMODE='auto'

USERCONTROL='no'

BONDING_SLAVE0='eth4'


b. Modify the eth4 and eth5 configuration files:

# vi /etc/sysconfig/network/ifcfg-eth4

BOOTPROTO='none'

BROADCAST=''

ETHTOOL_OPTIONS=''

IPADDR=''

MTU=''

NAME='VIC Ethernet NIC'

NETMASK=''

NETWORK=''

REMOTE_IPADDR=''

STARTMODE='hotplug'

USERCONTROL='no'


BOOTPROTO='none'

BROADCAST=''

ETHTOOL_OPTIONS=''

IPADDR=''

MTU=''


NETMASK=''

NETWORK=''

REMOTE_IPADDR=''


STARTMODE='hotplug'

USERCONTROL='no'

c. Test the configuration.

Restart the network service to bring up the bond0 interface. Then enter the following command:

# rcnetwork restart

To query the current status of the Linux kernel bounding driver, enter the following command:

# cat /proc/net/bonding/bond0

Figure 86 shows sample output.

Figure 86. Sample bond0 Configuration Test Output

2. Create 10-Gbps bond device ifcfg-bond1 with two interfaces as slaves.

a. Create a bond1 configuration file (eth0 and eth2 are used as examples here):

# vi /etc/sysconfig/network/ifcfg-bond1

BONDING_MASTER='yes'

BONDING_MODULE_OPTS='mode=active-backup miimon=100'

BOOTPROTO='static'

BROADCAST=''

ETHTOOL_OPTIONS=''

IPADDR='<<ip_address_customer_usecase>>/<<netmask_prefix>>'

MTU=''

NAME=''

NETWORK=''


REMOTE_IPADDR=''

STARTMODE='auto'

USERCONTROL='no'



b. Modify the eth0 and eth2 configuration files:


BOOTPROTO='none'

BROADCAST=''

ETHTOOL_OPTIONS=''

IPADDR=''

MTU=''


NETMASK=''

NETWORK=''

REMOTE_IPADDR=''

STARTMODE='hotplug'

USERCONTROL='no'


BOOTPROTO='none'

BROADCAST=''

ETHTOOL_OPTIONS=''

IPADDR=''

MTU=''


NETMASK=''

NETWORK=''

REMOTE_IPADDR=''

STARTMODE='hotplug'

USERCONTROL='no'

c. Test the configuration.

Restart the networking service to bring up the bond0 interface. Enter the following command:

# rcnetwork restart

To query the current status of Linux kernel bounding driver, enter the following command:

# cat /proc/net/bonding/bond1

Figure 87 shows sample output.


Figure 87. Sample bond1 Configuration Test Output

Performance Tuning Parameters for SAP HANA

Use the parameters in this section to tune SAP HANA performance.

Tune the /etc/init.d/after.local File

Create the /etc/init.d/after.local file and grant executable permission.

For SAP HANA to run with optimal performance on the appliance, you need to change a few parameters.

Add the following parameters to the /etc/init.d/after.local file:

cishanar08-c880:~ # vi /etc/init.d/after.local

### Performance Tuning for SAP HANA

# IO scheduler

echo deadline > /sys/block/sda/queue/scheduler

echo deadline > /sys/block/sdb/queue/scheduler

echo deadline > /sys/block/sdc/queue/scheduler

echo deadline > /sys/block/sdd/queue/scheduler

echo deadline > /sys/block/sde/queue/scheduler

echo deadline > /sys/block/sdf/queue/scheduler

#

#nr requests

echo 4096 > /sys/block/sda/queue/nr_requests

echo 4096 > /sys/block/sdb/queue/nr_requests


echo 4096 > /sys/block/sdc/queue/nr_requests

echo 4096 > /sys/block/sdd/queue/nr_requests

echo 4096 > /sys/block/sde/queue/nr_requests

echo 4096 > /sys/block/sdf/queue/nr_requests

#

echo 4096 > /sys/block/sda/queue/read_ahead_kb

echo 4096 > /sys/block/sdb/queue/read_ahead_kb

echo 4096 > /sys/block/sdc/queue/read_ahead_kb

echo 4096 > /sys/block/sdd/queue/read_ahead_kb

echo 4096 > /sys/block/sde/queue/read_ahead_kb

echo 4096 > /sys/block/sdf/queue/read_ahead_kb

#

#

echo "Setting the CPU Speed to PERFORMANCE for SAP HANA"

cpupower set -b 0

#

# Disable THP

echo never > /sys/kernel/mm/transparent_hugepage/enabled

Tune the sysctl. Conf File

Copy the following parameters to the /etc/sysctl.conf file:

# Disable response to broadcasts.

net.ipv4.icmp_echo_ignore_broadcasts = 1

# enable route verification on all interfaces

net.ipv4.conf.all.rp_filter = 1

# increase the number of possible inotify(7) watches

fs.inotify.max_user_watches = 65536

# avoid deleting secondary IPs on deleting the primary IP

net.ipv4.conf.default.promote_secondaries = 1

net.ipv4.conf.all.promote_secondaries = 1

# SAP Install guide Settings

net.ipv4.tcp_slow_start_after_idle=0

#Controls IP packet forwarding

net.ipv4.ip_forward = 0

# Do not accept source routing

net.ipv4.conf.default.accept_source_route = 0

# added for SAP HANA Database

net.ipv4.tcp_syncookies = 1

fs.inotify.max_user_watches = 65536

kernel.shmmax = 9223372036854775807

kernel.sem = 1250 256000 100 8192

kernel.shmall = 1152921504606846720

kernel.shmmni = 524288


vm.max_map_count=607000000


fs.file-max = 20000000

fs.aio-max-nr = 196608

vm.memory_failure_early_kill = 1

# Linux SAP swappiness recommendation

vm.swappiness=10


net.ipv4.ip_local_port_range=40000 65300

# XFS Daemon Tuning

fs.xfs.xfssyncd_centisecs = 15000

fs.xfs.xfsbufd_centisecs = 3000

fs.xfs.age_buffer_centisecs = 9000

Disable C-States: Add Parameter to the Bootloader

Because SAP HANA can occasionally fail when transparent hugepages are enabled, you should deactivate this

option until you have verified its function. You should also disable the C-states for the CPU.

1. Modify the /etc/default/grub file. Find the line starting with:

GRUB_CMDLINE_LINUX

2. Append the following parameter:

transparent_hugepage=never intel_idle.max_cstate=1

3. To implement these changes, rebuild the GRUB2 configuration:

# grub2-mkconfig -o /boot/efi/EFI/sles_sap/grub.cfg

After the system reboots, the use of C-states C2 and higher will be disabled.

Reboot the Appliance

After you have added all the necessary performance tuning parameters, before proceeding further you need to

reboot the appliance to make the parameters take effect.

Reboot the appliance now:

cishanar08-c880:~ # init 6

cishanar08-c880:~ #

Patching the Appliance

After the appliance has been rebooted with the performance tuning settings, the system must be patched to use

the latest available packages.

Register the System for Patching

To patch the system, you must update the repository. Note that the installed system does not include any update

information. To connect to the Novell update repository, you must use an active activation key.

The following code registers the installation and updates the repository information:

cishanar08-c880:~ # zypper refresh

All services have been refreshed.

All repositories have been refreshed.

Refreshing service 'nu_novell_com'.

Adding repository 'SLES12-SP1-Updates' [done]


Adding repository 'SLES12-Extras' [done]

Adding repository 'SLES12-SP1-Pool' [done]

Adding repository 'SLES12--Updates' [done]

Adding repository 'SLE12-HAE-SP1-Pool' [done]

Adding repository 'SLE12-HAE-SP1-Updates' [done]

Adding repository 'SLE12-SP1-SAP-Updates' [done]

Adding repository 'SLES12-SP1-Pool' [done]

Adding repository 'SLES12--Extension-Store' [done]

Adding repository 'SLE12-SP1-SAP-Pool' [done]

Adding repository 'SLE12-SP1-Debuginfo-Pool' [done]

Adding repository 'SLE12--WebYaST-1.3-Pool' [done]

Adding repository 'SLE12-SP1-Debuginfo-Updates' [done]

Adding repository 'SLES12--Core' [done]

Adding repository 'SLES12-SP1-Updates' [done]

Adding repository 'SLES12-SP1-Extension-Store' [done]

Adding repository 'SLE12--WebYaST-1.3-Updates' [done]

Adding repository 'SLE12-SP1-Debuginfo-Pool' [done]

Adding repository 'SLE12-SP1-Debuginfo-Updates' [done]

All services have been refreshed.

Retrieving repository 'SLE12-HAE-SP1-Pool' metadata [done]

Building repository 'SLE12-HAE-SP1-Pool' cache [done]

Retrieving repository 'SLE12-HAE-SP1-Updates' metadata [done]

Building repository 'SLE12-HAE-SP1-Updates' cache [done]

Retrieving repository 'SLE12--WebYaST-1.3-Pool' metadata [done]

Building repository 'SLE12--WebYaST-1.3-Pool' cache [done]

Retrieving repository 'SLE12--WebYaST-1.3-Updates' metadata [done]

Building repository 'SLE12--WebYaST-1.3-Updates' cache [done]

Retrieving repository 'SLE12-SP1-SAP-Pool' metadata [done]

Building repository 'SLE12-SP1-SAP-Pool' cache [done]

Retrieving repository 'SLE12-SP1-SAP-Updates' metadata [done]

Building repository 'SLE12-SP1-SAP-Updates' cache [done]

Retrieving repository 'SLES12-SP1-Pool' metadata [done]

Building repository 'SLES12-SP1-Pool' cache [done]

Retrieving repository 'SLES12-SP1-Updates' metadata [done]

Building repository 'SLES12-SP1-Updates' cache [done]

All repositories have been refreshed.

Registration finished successfully

cishanar08-c880:~ #


Patch SLES for SAP Applications SP1

Now patch the system:

cishanar08-c880:~ # zypper update

Loading repository data...

Reading installed packages...

The following NEW package is going to be installed:

libtevent0-32bit

The following packages are going to be upgraded:

Mesa Mesa-32bit MozillaFirefox MozillaFirefox-branding-SLED MozillaFirefox-

translations aaa_base apparmor-docs apparmor-parser apparmor-utils augeas-lenses

autofs automake bash bash-doc bind-libs bind-libs-32bit bind-utils binutils

blktrace checkmedia coreutils coreutils-lang cpupower crash crash-sial ctags

cups cups-client cups-libs cups-libs-32bit curl elilo ethtool facter fastjar

fontconfig fontconfig-32bit glib2 glib2-lang glibc glibc-32bit glibc-devel

glibc-devel-32bit glibc-i18ndata glibc-info glibc-locale glibc-locale-32bit

gpg2 gpg2-lang grub gvfs gvfs-backends gvfs-fuse gvfs-lang hal hal-32bit hplip-

hpijs ipmitool iproute2 irqbalance java-1_6_0-ibm java-1_6_0-ibm-fonts

java-1_6_0-ibm-plugin kdump kernel-default kernel-default-base kernel-default-

devel kernel-firmware kernel-source kpartx krb5 krb5-32bit ksh lcms

libMagickCore1 libapparmor1 libaugeas0 libcurl4 libcurl4-32bit libdrm libdrm-

32bit

libfprint0 libfreebl3 libfreebl3-32bit libgcrypt11 libgcrypt11-32bit libgio-

2_0-0 libgio-2_0-0-32bit libglib-2_0-0 libglib-2_0-0-32bit libgmodule-2_0-0

libgmodule-2_0-0-32bit libgnutls26 libgobject-2_0-0 libgobject-2_0-0-32bit

libgthread-2_0-0 libgthread-2_0-0-32bit libgvfscommon0 liblcms1 liblcms1-32bit

libldap-2_4-2 libldap-2_4-2-32bit libldb1 libmysqlclient_r15 libopenssl0_9_8

libopenssl0_9_8-32bit libpixman-1-0 libpixman-1-0-32bit libpulse0

libpython2_6-1_0 libpython2_6-1_0-32bit libqt4 libqt4-32bit libqt4-qt3support

libqt4-qt3support-32bit libqt4-sql libqt4-sql-32bit libqt4-sql-mysql libqt4-x11

libqt4-x11-32bit libreadline5 libsmbclient0 libsnmp15 libsoftokn3

libsoftokn3-32bit libtalloc2 libtalloc2-32bit libtdb1 libtdb1-32bit libtevent0

libtiff3 libtiff3-32bit libudev0 libudev0-32bit libwbclient0 libwbclient0-32bit

libxml2 libxml2-32bit libxml2-python libxslt libxslt-32bit libzypp

logrotate lsscsi mailx mcelog mdadm microcode_ctl mkinitrd mozilla-nspr

mozilla-nspr-32bit mozilla-nss mozilla-nss-32bit multipath-tools mutt nfs-client

nfs-doc nscd openldap2-client openssl openssl-certs perl-Bootloader perl-apparmor

postfix pulseaudio pulseaudio-esound-compat pulseaudio-lang puppet python

python-base python-xml readline-doc release-notes-sles rsh ruby samba samba-32bit

samba-client samba-client-32bit sblim-sfcb sg3_utils snmp-mibs star sudo

supportutils suseRegister sysstat tcsh timezone udev xinetd xkeyboard-config

xorg-x11-Xvnc xorg-x11-driver-input xorg-x11-driver-video xorg-x11-libX11 xorg-

x11-libX11-32bit xorg-x11-libXext xorg-x11-libXext-32bit xorg-x11-libXfixes

xorg-x11-libXfixes-32bit xorg-x11-libXp xorg-x11-libXp-32bit xorg-x11-

libXrender xorg-x11-libXrender-32bit xorg-x11-libXt xorg-x11-libXt-32bit xorg-

x11-libXv xorg-x11-libXv-32bit xorg-x11-libs xorg-x11-libs-32bit xorg-x11-server

yast2

yast2-bootloader yast2-ldap-client yast2-pkg-bindings yast2-storage yast2-

storage-lib yelp yelp-lang zsh zypper zypper-log

The following package needs additional customer contract to get support:

libmysqlclient_r15


223 packages to upgrade, 1 new.

Overall download size: 466.3 MiB. After the operation, additional 24.3 MiB will

be used.

Continue? [y/n/?] (y):

Kernel image: /boot/vmlinuz-3.0.101-68-default

Initrd image: /boot/initrd-3.0.101-68-default

KMS drivers: mgag200

Root device: /dev/sda2 (mounted on / as ext3)

Resume device: /dev/sda3

Kernel Modules: hwmon thermal_sys thermal processor fan scsi_mod megaraid_sas

scsi_tgt scsi_transport_fc libfc libfcoe fnic dm-mod dm-log dm-region-hash dm-

mirror dm-snapshot scsi_dh scsi_dh_hp_sw scsi_dh_alua scsi_dh_rdac scsi_dh_emc

mbcache jbd ext3 syscopyarea i2c-core sysfillrect sysimgblt i2c-algo-bit drm

drm_kms_helper ttm mgag200 usb-common usbcore ohci-hcd uhci-hcd ehci-hcd xhci-hcd

hid usbhid linear crc-t10dif sd_mod

Features: acpi dm kms block usb lvm2 resume.userspace resume.kernel

Bootsplash: SLES (800x600)

42738 blocks

>>> Network: auto

>>> Calling mkinitrd -k /boot/vmlinuz-3.0.101-68-default -i

/tmp/mkdumprd.gkWFsyOWBb -f 'kdump network' -B -s ''

Regenerating kdump initrd ...

Kernel image: /boot/vmlinuz-3.0.101-68-default

Initrd image: /tmp/mkdumprd.gkWFsyOWBb

KMS drivers: mgag200

Root device: /dev/sda2 (mounted on / as ext3)

Resume device: /dev/sda3

Boot device: /dev/disk/by-uuid/5b825220-506d-4815-b52d-c6015c448824

(/dev/sda1)

Kernel Modules: hwmon thermal_sys thermal processor fan scsi_mod megaraid_sas

scsi_tgt scsi_transport_fc libfc libfcoe fnic dm-mod dm-log dm-region-hash dm-

mirror dm-snapshot scsi_dh scsi_dh_hp_sw scsi_dh_alua scsi_dh_rdac scsi_dh_emc

mbcache jbd ext3 syscopyarea i2c-core sysfillrect sysimgblt i2c-algo-bit drm

drm_kms_helper ttm mgag200 usb-common usbcore ohci-hcd uhci-hcd ehci-hcd xhci-hcd

hid usbhid af_packet bonding pps_core ptp dca igb mdio ixgbe linear nls_utf8 crc-

t10dif sd_mod

Features: acpi dm kms block usb network lvm2 resume.userspace resume.kernel

kdump

56162 blocks

Installing: kernel-default-base-3.0.101-68.1 [done]

cishanar08-c880:~ #


Reboot the Appliance

After successful updating the OS, you need to reboot the server so that it uses the new, updated kernel.

Reboot the appliance now:

cishanar08-c880:~ # init 6

cishanar08-c880:~ #

Installing SAP HANA

To install SAP HANA, use the official SAP documentation, which describes the installation process with and

without the SAP unified installer.

For SAP HANA installation documentation, see SAP HANA Server Installation Guide.

All other SAP installation and administration documentation is available at http://service.sap.com/instguides.

Important SAP Notes

Read the following SAP Notes before you start the installation. These SAP Notes contain the latest information

about the installation, as well as corrections to the installation documentation.

The latest SAP Notes can be found at: https://service.sap.com/notes.

SAP HANA In-Memory Database (IMDB) Notes

SAP Note 1514967: SAP HANA: Central note

SAP Note 2004651: SAP HANA platform SPS 08 release note

SAP Note 2075266: SAP HANA platform SPS 09 release note

SAP Note 1523337: SAP HANA database: Central note

SAP Note 2000003: FAQ: SAP HANA

SAP Note 1730999: Configuration changes in SAP HANA appliance

SAP Note 1514966: SAP HANA 1.0: Sizing SAP in-memory database

SAP Note 1780950: Connection problems due to host name resolution

SAP Note 1780950: SAP HANA SPS 06: Network setup for external communication

SAP Note 1743225: SAP HANA: Potential failure of connections with scale-out nodes

SAP Note 1755396: Released disaster tolerant (DT) solutions for SAP HANA with disk replication

SAP Note 1890444: HANA system slow due to CPU power save mode

SAP Note 1681092: Support for multiple SAP HANA databases on a single SAP HANA appliance

SAP Note 1514966: SAP HANA: Sizing the SAP HANA database

SAP Note 1637145: SAP BW on HANA: Sizing the SAP HANA database

SAP Note 1793345: Sizing for Suite on HANA

http://help.sap.com/hana/SAP_HANA_Server_Installation_Guide_en.pdf

http://service.sap.com/instguides

https://service.sap.com/notes

https://service.sap.com/sap/support/notes/1514967

















Linux Notes

SAP Note 2205917: SAP HANA DB: Recommended OS settings for SLES 12 and SLES for SAP Applications 12

SAP Note 2235581: SAP HANA: Supported operating systems

SAP Note 1944799: SAP HANA guidelines for the SLES operating system

SAP Note 1731000: Nonrecommended configuration changes

SAP Note 1557506: Linux paging improvements

SAP Note 1726839: SAP HANA database: Potential crash when using XFS file system

SAP Note 1740136: SAP HANA: Wrong mount option may lead to corrupt persistency

SAP Note 1829651: Time-zone settings in SAP HANA scale-out landscapes

SAP Application Notes

SAP Note 1658845: SAP HANA database hardware check

SAP Note 1637145: SAP BW on SAP HANA: Sizing SAP in-memory database

SAP Note 1661202: Support for multiple applications on SAP HANA

SAP Note 1681092: Support for multiple SAP HANA databases on one SAP HANA appliance (also known as Multi

SID)

SAP Note 1577128: Supported clients for SAP HANA 1.0

SAP Note 1808450: Homogenous system landscape for on SAP BW on SAP HANA

SAP Note 1976729: Application component hierarchy for SAP HANA

SAP Note 1927949: Standard behavior for SAP logon tickets

SAP Note 1577128: Supported clients for SAP HANA

Third-Party Software Notes

SAP Note 1730928: Using external software in an SAP HANA appliance

SAP Note 1730929: Using external tools in an SAP HANA appliance

SAP Note 1730930: Using antivirus software in an SAP HANA appliance

SAP Note 1730932: Using backup tools with Backint for SAP HANA

SAP HANA Virtualization Notes

SAP Note 1788665: SAP HANA running on VMware vSphere virtual machines

SAP HANA Post-Installation Checkup

For a SAP HANA system installed with <SID> set to BWL and the system number <nr> set to 00, log in as

<sid>adm ir bwladm and run the commands presented here.

https://launchpad.support.sap.com/#/notes/2205917/E

http://service.sap.com/sap/support/notes/2235581





















SAP HANA Post-Installation Tasks

After SAP HANA has been installed, you should perform the tasks described in this section.

Check the SAP HANA Services

Run the following command to check the SAP HANA services:

cishanar08-c880:/usr/sap/BWL/HDB00> /usr/sap/hostctrl/exe/sapcontrol -nr 00 -

function GetProcessList

17.02.2016 17:52:57

GetProcessList

OK

name, description, dispstatus, textstatus, starttime, elapsedtime, pid

hdbdaemon, HDB Daemon, GREEN, Running, 2016 02 17 17:50:17, 0:02:40, 36971

hdbcompileserver, HDB Compileserver, GREEN, Running, 2016 02 17 17:50:23,

0:02:34, 37110

hdbindexserver, HDB Indexserver, GREEN, Running, 2016 02 17 17:50:28, 0:02:29,

37133

hdbnameserver, HDB Nameserver, GREEN, Running, 2016 02 17 17:50:18, 0:02:39,

36985

hdbpreprocessor, HDB Preprocessor, GREEN, Running, 2016 02 17 17:50:23, 0:02:34,

37112

hdbwebdispatcher, HDB Web Dispatcher, GREEN, Running, 2016 02 17 17:50:55,

0:02:02, 38388

hdbxsengine, HDB XSEngine, GREEN, Running, 2016 02 17 17:50:28, 0:02:29, 37135

cishanar08-c880:/usr/sap/BWL/HDB00>

Check the HANA Database Information

Run the HDB info command to check the HANA database information:

cishanar08-c880:/usr/sap/BWL/HDB00> HDB info

USER PID PPID %CPU VSZ RSS COMMAND

BWLadm 36758 36757 0.0 13896 2804 -sh

BWLadm 38911 36758 0.0 12912 1764 \_ /bin/sh /usr/sap/BWL/HDB00/HDB info

BWLadm 38934 38911 0.0 4960 876 \_ ps fx -U BWLadm -o

user,pid,ppid,pcpu,vsz,rss,args

BWLadm 36961 1 0.0 22656 1604 sapstart

pf=/hana/shared/BWL/profile/BWL_HDB00_cishanar08-c880

BWLadm 36985 36971 12.2 6046704 1687168 \_ hdbnameserver

BWLadm 37110 36971 56.2 5052896 1106960 \_ hdbcompileserver

BWLadm 37112 36971 208 7815656 4228576 \_ hdbpreprocessor

BWLadm 37133 36971 301 11947188 7396664 \_ hdbindexserver

BWLadm 37135 36971 51.3 6433120 2040932 \_ hdbxsengine

BWLadm 38388 36971 26.4 5082544 845320 \_ hdbwebdispatcher

BWLadm 13070 1 0.0 211220 61700 /usr/sap/BWL/HDB00/exe/sapstartsrv

pf=/hana/shared/BWL/profile/BWL_HDB00_cishanar08-c880 -D -u BWLadm


Maintain the Operating System

The customer is responsible for implementing security updates and patches, adding software components, and

changing OS settings that may be requested by SAP for future releases of SAP HANA or that may be required by

SUSE to help ensure system security and stability. See the related SAP OS notes for required OS settings.

This section describes how to update the OS and the implications of updating OS components. It is not meant to

replace the Linux administration documentation.

Prerequisites

Whenever you change the OS or parts of the OS such as drivers and kernel parameters, be sure that you have at

least a backup copy of your SAP HANA system, preferably not stored on the appliance. You also should check the

related OS notes and Cisco support channels for additional information.

Some changes may require a reboot and should be applied when SAP HANA is shut down.

Updating the OS and Kernel

Not all updates and patches update the OS kernel. But if a kernel update is necessary, you need to take specific

precautions. During the entire update process, SAP HANA must be shut down.

These are the general steps for updating the kernel:

● Perform these tasks before updating the kernel:

◦ Stop SAP HANA and back up the existing log area (in case the device causes a problem and needs to

be re-created).

◦ Unmount /hana/log and clean /etc/fstab.

● Update the kernel using YaST (or a manual procedure).

● Perform these tasks after updating the kernel:

◦ Check the GRUB file and boot sector (menu.lst).

◦ Reboot and check /etc/fstab.

The following steps present the tasks in more detail.

1. Back up the SAP HANA log area.

a. Stop SAP HANA. Then move to the log area and back up the HANA log partition.

cishanar08-c880 :~ # cd /hana/log

cishanar08-c880 :/hana/log # find . –xdev | cpio –oav > /backup/hana.log.cpio

b. If the backup partition has enough room, choose it. Otherwise, choose an appropriate location for the

backup.

2. Unmount /hana/log.

cishanar08-c880 :~ #umount /hana/log


Updating SUSE and the Kernel Online

You can update the operating system and kernel either through YaST or manually.

Option 1: Using YaST

You can update the OS online using YaST. This method will update all OS components; a kernel update may also

be included.

1. Set up a proxy service, if necessary, so that the appliance can reach the Internet. Make sure that

PROXY_ENABLED is set to “yes” and that the appropriate proxy server host and IP address along with the

port configured is used.

cishanar08-c880:~ # cd /etc/sysconfig/

cishanar08-c880:/etc/sysconfig # vi proxy

PROXY_ENABLED="yes"

HTTP_PROXY="http://<Proxy_server_IP>:<Proxy_Service_port>"

HTTPS_PROXY="http://<Proxy_server_IP>:<Proxy_service_port>"

FTP_PROXY="http://<Proxy_server_IP>:<Proxy_service_port>"

2. Start YaST and choose Software > Online Update.

a. Select Yes to configure the update repository (Figure 88).

Figure 88. YaST—Online Update

b. Log in with your Novell account used for licensing to register the server. Click Next (Figure 90).


Figure 89. YaST—Online Update: Registration

c. An overview of the available extension and modules is displayed (Figure 90). Click Next.


Figure 90. YaST—Online Update: Extension and Module Selection

d. A list of the patches available from the online repository is displayed (Figure 92). Click Accept.


Figure 91. YaST—Online Update: Patch List

The system downloads all available patches (Figures 92 and 93).


Figure 92. YaST—Online Update: Package Update


Figure 93. YaST—Online Update: List of Packages Updated

e. Some patches may require a reboot after installation. Select Continue (Figure 95).


Figure 94. YaST—Online Update: Package Update with Reboot

Patches are downloaded and installed at this time (Figure 96).


Figure 95. YaST—Online Update: Package Update Progress

f. The Release Notes are displayed (Figure 97). Click Close.


Figure 96. YaST—Online Update: Release Notes

g. Click OK to acknowledge the reboot prompt (Figure 98).


Figure 97. YaST—Online Update: Reboot Message

h. Quit YaST.

i. Reboot the system to make the patch installation take effect.

SAP HANA Operation and Maintenance

SAP HANA operation and maintenance are described in detail in many related SAP documents. For a complete list

of documentation, see http://help.sap.com/hana.

This document summarizes only a few important operation and maintenance procedures. Most of the procedures

described in this document are CLI procedures and are independent of any GUI requiring an X terminal or other

GUI front end (Microsoft Windows PC, Linux desktop, etc.). CLI procedures can be started using the KVM or any

SSH tool such as PuTTY (for Windows) or Terminal (for Mac OS), or any Linux terminal window to connect to the

SAP HANA database system (the appliance).

Monitoring SAP HANA

Three easy CLI methods are available to check the running SAP HANA database.

saphostagent

1. Start a shell and connect to the SAP HANA system as the root user.

cishanar08-c880:~ # /usr/sap/hostctrl/exe/saphostctrl -function ListDatabases

Instance name: HDB00, Hostname: cishanar08-c880, Vendor: HDB, Type: hdb, Release:

1.00.60.0379371

Database name: HAN, Status: Error

cishanar08-c880:~ #

http://help.sap.com/hana


2. Get a list of installed HANA instances or databases.

cishanar08-c880:~ # /usr/sap/hostctrl/exe/saphostctrl -function ListInstances

Inst Info : HAN - 00 - cishanar08-c880 - 740, patch 17, changelist 1413428

cishanar08-c880:~ #

3. Using this information (SID and system number), you can use sapcontrol to gather more information about the

running HANA database.

sapcontrol

1. In a shell, use the sapcontrol function GetProcessList to display a list of running HANA OS processes.

cishanar08-c880:~ # /usr/sap/hostctrl/exe/sapcontrol -nr 00 -function

GetProcessList

19.07.2016 14:54:45

GetProcessList

OK

name, description, dispstatus, textstatus, starttime, elapsedtime, pid

hdbdaemon, HDB Daemon, GREEN, Running, 2016 07 15 11:57:45, 98:57:00, 8545

hdbnameserver, HDB Nameserver, GREEN, Running, 2016 07 15 12:05:27, 98:49:18,

11579

hdbpreprocessor, HDB Preprocessor, GREEN, Running, 2013 08 15 12:05:27, 98:49:18,

11580

hdbindexserver, HDB Indexserver, GREEN, Running, 2016 07 15 12:05:27, 98:49:18,

11581

hdbstatisticsserver, HDB Statisticsserver, GREEN, Running, 2016 07 15 12:05:27,

98:49:18, 11582

hdbxsengine, HDB XSEngine, GREEN, Running, 2016 07 15 12:05:27, 98:49:18, 11583

sapwebdisp_hdb, SAP WebDispatcher, GREEN, Running, 2016 07 15 12:05:27, 98:49:18,

11584

hdbcompileserver, HDB Compileserver, GREEN, Running, 2016 07 15 12:05:27,

98:49:18, 11585

You see processes such as hdbdaemon, hdbnameserver, and hdbindexserver that belong to a running HANA

database.

2. You can also get a system instance list, which is more useful for a scale-out appliance.


GetSystemInstanceList

19.07.2016 15:03:12


OK

hostname, instanceNr, httpPort, httpsPort, startPriority, features, dispstatus

cishanar08-c880, 0, 50013, 0, 0.3, HDB, GREEN

HDB Info

Another important tool is the HDB command, which needs to be issued by the <SID>adm user: the OS user who

owns the HANA database.

As the root user on the HANA appliance, enter the following command:


cishanar08-c880:~ # su – hanadm

cishanar08-c880:/usr/sap/HAN/HDB00> HDB info


hanadm 61208 61207 1.6 13840 2696 -sh

hanadm 61293 61208 0.0 11484 1632 \_ /bin/sh /usr/sap/HAN/HDB00/HDB info

hanadm 61316 61293 0.0 4904 872 \_ ps fx -U hanadm -o


hanadm 8532 1 0.0 20048 1468 sapstart

pf=/hana/shared/HAN/profile/HAN_HDB00_cishanar08-c880

hanadm 8545 8532 1.5 811036 290140 \_ /usr/sap/HAN/HDB00/cishanar08-

c880/trace/hdb.sapHAN_HDB00 -d -nw -f /usr/sap/HAN/HDB00/cis

hanadm 11579 8545 6.6 16616748 1789920 \_ hdbnameserver

hanadm 11580 8545 1.5 5675392 371984 \_ hdbpreprocessor

hanadm 11581 8545 10.9 18908436 6632128 \_ hdbindexserver

hanadm 11582 8545 8.7 17928872 3833184 \_ hdbstatisticsserver

hanadm 11583 8545 7.4 17946280 1872380 \_ hdbxsengine

hanadm 11584 8545 0.0 203396 16000 \_ sapwebdisp_hdb

pf=/usr/sap/HAN/HDB00/cishanar08-c880/wdisp/sapwebdisp.pfl -f /usr/sap/H

hanadm 11585 8545 1.5 15941688 475708 \_ hdbcompileserver

hanadm 8368 1 0.0 216268 75072 /usr/sap/HAN/HDB00/exe/sapstartsrv

pf=/hana/shared/HAN/profile/HAN_HDB00_cishanar08-c880 -D -u

This command produces output similar to that from the sapcontrol GetProcessList function, with a little more

information about the process hierarchy.

Starting and Stopping SAP HANA

Before you stop the SAP HANA appliance, you must be able to stop and start the HANA database. You can use

the commands shown here.

sapcontrol

You can use the sapcontrol functions StartSystem and StopSystem to start and stop a HANA database.

Stop the system with the StopSystem function.

cishanar08-c880:~ # /usr/sap/hostctrl/exe/sapcontrol -nr 00 -function StopSystem

HDB

19.07.2016 15:05:35

StopSystem

OK

Use the following command to check that the database has stopped:



19.07.2016 15:05:58



OK


cishanar08-c880, 0, 50013, 0, 0.3, HDB, YELLOW

Wait for the status to be “GRAY.”



19.07.2016 15:07:52


OK


cishanar08-c880, 0, 50013, 0, 0.3, HDB, GRAY

You can also use the HDB info command:

cishanar08-c880:~ # su -l hanadm

cishanar08-c880:/usr/sap/HAN/HDB00> HDB info


hanadm 61477 61476 2.0 13840 2692 -sh

hanadm 61562 61477 0.0 11484 1632 \_ /bin/sh /usr/sap/HAN/HDB00/HDB info

hanadm 61585 61562 0.0 4904 872 \_ ps fx -U hanadm -o


hanadm 8368 1 0.0 216784 75220 /usr/sap/HAN/HDB00/exe/sapstartsrv

pf=/hana/shared/HAN/profile/HAN_HDB00_cishanar08-c880 -D -u

cishanar08-c880:/usr/sap/HAN/HDB00>

You can start the database again with the sapcontrol command StartSystem function:

cishanar08-c880:~ # /usr/sap/hostctrl/exe/sapcontrol -nr 00 -function StartSystem

HDB

19.07.2016 15:08:48

StartSystem

OK

To check the system status, use the sapcontrol command GetSystemInstanceList function. Wait for status to be

“GREEN.”



19.07.2016 15:10:19


OK


cishanar08-c880, 0, 50013, 0, 0.3, HDB, GREEN


HDB

You can use the HDB start and stop commands to stop and start the HANA database.

Use HDB stop to stop the database:

cishanar08-c880:~ # su - hanadm

cishanar08-c880:/usr/sap/HAN/HDB00> HDB stop

hdbdaemon will wait maximal 300 seconds for NewDB services finishing.

Stopping instance using: /usr/sap/HAN/SYS/exe/hdb/sapcontrol -prot NI_HTTP -nr 00

-function StopWait 400 2

19.07.2016 19:10:37

Stop

OK

In contrast to sapcontrol, this command waits until the database is stopped or started.

cishanar08-c880:/usr/sap/HAN/HDB00> HDB start

StartService

Impromptu CCC initialization by 'rscpCInit'.

See SAP note 1266393.

OK

OK

Starting instance using: /usr/sap/HAN/SYS/exe/hdb/sapcontrol -prot NI_HTTP -nr 00

-function StartWait 2700 2

19.07.2016 19:11:20

Start

OK

Downloading Revisions

To download revisions, you need to connect to the service marketplace and select the software download area to

search for available patches.

Refer to http://help.sap.com/hana/SAP_HANA_Master_Update_Guide_en.pdf for update procedures for SAP

HANA.

For More Information

For information about SAP HANA, see https://hana.sap.com/abouthana.html.

For information about certified and supported SAP HANA hardware, see

https://global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/index.html.

http://help.sap.com/hana/SAP_HANA_Master_Update_Guide_en.pdf

https://hana.sap.com/abouthana.html

https://global.sap.com/community/ebook/2014-09-02-hana-hardware/enEN/index.html


Appendix: Solution Variables Used for This Document

Before starting the configuration process, you need to collect some specific configuration information. Table 12

provides information to help you assemble the required network and host address, numbering, and naming

information. This worksheet can also be used as a “leave behind” document for future reference.

Table 12. Solution Variables Used in This Document

Variable Description Value Used in the Lab for This Document

<<var_imc_ip_address>> Cisco C880 M4 Server’s IMC IP address 173.36.215.117

<<var_imc_ip_netmask>> Cisco C880 M4 Server’s IMC network netmask 255.255.255.0

<<var_imc_gateway_ip>> Cisco C880 M4 Server’s IMC network gateway IP address 173.36.215.1

<<var_raid5_vd_name>> Name for virtual drive VD <<0–5>> during RAID configuration ucs_hana<<1–6>>

<<var_hostname.domain>> SAP HANA node FQDN cishanar08-c880.custdom.local

<<var_sys_root-pw>> SAP HANA node’s root password Saphana1!

<<var_lvm_vg_name>> SAP HANA node’s OS LVM volume group name hanavg

<<var_mgmt_ip_address>> SAP HANA node’s management and administration IP address 173.36.215.118

<<var_mgmt_nw_netmask>> SAP HANA node’s management network netmask 255.255.255.0

<<var_mgmt_gateway_ip>> Cisco C880 M4 Server’s management and administration network gateway IP address

173.36.215.1

<<var_mgmt_netmask_prefix>> Netmask prefix in CIDR notation 24

Printed in USA C11-7388438-00 04/17

Cisco Scale-Up Solution for SAP HANA with the …...This section describes the SAP HANA system...

Documents

Transcript of Cisco Scale-Up Solution for SAP HANA with the …...This section describes the SAP HANA system...